--- a/model/comments/issue-459-paul.txt Tue Aug 07 11:36:31 2012 +0100
+++ b/model/comments/issue-459-paul.txt Tue Aug 07 12:01:40 2012 +0100
@@ -89,6 +89,9 @@
> Additionally, to get things to work I had to make sure the inferences
> were done in one pass, which may go against what is specified in the
> document.
+
+@James, is there something you want to add here?
+
>
> My major concern is the lack of intuition about what valid provenance
> is. I would describe it as follows: valid provenance identifies
@@ -107,11 +110,31 @@
> these precedences relations first and then check for cycles. So I
> guess, are these really constraints? At any rate, the notion of
> checking for cycles needs to be brought out more.
+
+@James:
+we define 'inference' and 'definition' but we don't seem to define constraint.
+
+An inference is a rule that can be applied to PROV instances to add new PROV statements.
+A definition is a rule that can be applied to PROV instances to replace defined expressions with definitions.
+
+@James: Should we add a definition:
+
+An ordering constraint (should we say rule?) is a rule that can be applied to PROV instances
+to add new precedes/strictly precedes statements.
+
+@James Should we add a constraint box, since this is the actual constraint to be satisfied.
+
+Ordering constraints require that the directed graph from ordering statements contains no cycle containing a strictly precedes edge.
+
+
>
> Overall, I think an implementor could use some examples that show the
> results of inference and the subsequent constraint checking and just
> more intuition about what a valid and invalid provenance graphs look
> like.
+
+hhm, this would make the document very long.
+
>
> ==Some comments per section==
>
@@ -123,16 +146,35 @@
>
> Does this imply that I have to implement this to be compatible with
> PROV-DM? I would use SHOULD…
+
+
+Note, text possibly being rephrased, following stian's input.
+
+However, it's not problematic. If you determine wheher two prov instances are equivalence,
+you must determine whehter the NF are equal. Your application may not need to check equivalence.
+
+
>
> Section 5.1
> - From an RDF perspective, do I need to worry about merging? If the
> assumption is that I'm provided an RDF serialization to check then no
> merging is necessary. I guess the question is merging PROV-N specific?
+
+Yes you do, because prov:qualifiedXXX and prov:influencer are not functional.
+So, effectively, this constraint makes them functional.
+
>
> Section 6.1
> - Why do we need to talk about a hierarchy of bundles? Isn't just the
> point that you want a set of provenance descriptions independent of
> bundles?
+
+It's a flat hierarchy: a toplevel, unamed bundle, possibly containing
+named bundles. Named bundles dont contain bundles.
+
+As per prov-dm/prov-n.
+
+
>
> Minor Notes:
>
@@ -141,6 +183,11 @@
> "-inference". See Inference 11 (derivation-generation-use) and
> Inference 10 (wasEndedBy-inference)
>
+
+The terminology 'prov construct' is not present (anymore) in the document.
+
+@TODO: make rule names more uniform.
+
>
> Thanks
> Paul
--- a/model/prov-constraints.html Tue Aug 07 11:36:31 2012 +0100
+++ b/model/prov-constraints.html Tue Aug 07 12:01:40 2012 +0100
@@ -798,7 +798,7 @@
<a class="rule-text" href="#derivation-generation-generation-ordering"><span>TBD</span></a><br>
<a class="rule-text" href="#wasStartedBy-ordering"><span>TBD</span></a><br>
<a class="rule-text" href="#wasEndedBy-ordering"><span>TBD</span></a><br>
- <a class="rule-text" href="#specialization-generation"><span>TBD</span></a><br>
+ <a class="rule-text" href="#specialization-generation-ordering"><span>TBD</span></a><br>
<a class="rule-text" href="#wasAssociatedWith-ordering"><span>TBD</span></a><br>
<a class="rule-text" href="#wasAttributedTo-ordering"><span>TBD</span></a><br>
<a class="rule-text" href="#actedOnBehalfOf-ordering"><span>TBD</span></a><br>
@@ -872,7 +872,7 @@
<a class="rule-text" href="#usage-precedes-invalidation"><span>TBD</span></a><br>
<a class="rule-text" href="#wasStartedBy-ordering"><span>TBD</span></a><br>
<a class="rule-text" href="#wasEndedBy-ordering"><span>TBD</span></a><br>
- <a class="rule-text" href="#specialization-invalidation"><span>TBD</span></a><br>
+ <a class="rule-text" href="#specialization-invalidation-ordering"><span>TBD</span></a><br>
<a class="rule-text" href="#wasAssociatedWith-ordering"><span>TBD</span></a><br>
<a class="rule-text" href="#wasAttributedTo-ordering"><span>TBD</span></a><br>
<a class="rule-text" href="#actedOnBehalfOf-ordering"><span>TBD</span></a><br>
@@ -983,8 +983,8 @@
<td><a class="rule-text" href="#specialization-transitive"><span>TBD</span></a><br>
<a class="rule-text" href="#specialization-alternate"><span>TBD</span></a><br>
<a class="rule-text" href="#specialization-attributes"><span>TBD</span></a><br>
- <a class="rule-text" href="#specialization-generation"><span>TBD</span></a><br>
- <a class="rule-text" href="#specialization-invalidation"><span>TBD</span></a><br>
+ <a class="rule-text" href="#specialization-generation-ordering"><span>TBD</span></a><br>
+ <a class="rule-text" href="#specialization-invalidation-ordering"><span>TBD</span></a><br>
<a class="rule-text" href="#impossible-specialization-reflexive"><span>TBD</span></a><br>
<a class="rule-text" href="#typing"><span>TBD</span></a><br>
</td>
@@ -2827,12 +2827,12 @@
</div>
<hr />
-<p id="specialization-generation_text">
+<p id="specialization-generation-ordering_text">
If an entity is a specialization of another, then the more
specific entity must have been generated after the
less specific entity was generated.
</p>
-<div class="constraint" id="specialization-generation">
+<div class="constraint" id="specialization-generation-ordering">
<p>
<span class="conditional">IF</span> <span
class="name">specializationOf(e2,e1)</span> and <span
@@ -2844,12 +2844,12 @@
<p>
<hr />
-<p id="specialization-invalidation_text">
+<p id="specialization-invalidation-ordering_text">
Similarly, if an entity is a specialization of another entity, and
then
the invalidation event of the more specific entity precedes that of
the less specific entity.
-</p><div class="constraint" id="specialization-invalidation">
+</p><div class="constraint" id="specialization-invalidation-ordering">
<p>
<span class="conditional">IF</span> <span
class="name">specializationOf(e1,e2)</span> and <span