--- a/model/ProvenanceModel.html Tue Jan 17 10:17:58 2012 +0000
+++ b/model/ProvenanceModel.html Tue Jan 17 11:51:58 2012 +0000
@@ -436,7 +436,7 @@
rules allowing the derivation of <a title="event">instantaneous event</a> ordering constraints from
provenance records. According to such temporal interpretation,
provenance records MUST satisfy such constraints. We note that the
-actual verification of such ordering constraints is also outside the
+actual verification of such ordering constraints is outside the
scope of this specification. </p>
<p>PROV-DM also allows for time observations to be inserted in specific
@@ -860,7 +860,7 @@
<div class="note">
-Paolo, TODO: update the two figure. Replace wasComplementOf by alternateOf/specializationOf. Can we move key below figure to make better use of space?
+Paolo, TODO: update the two figure. Replace wasComplementOf by alternateOf/specializationOf. Can we move key below figure to make better use of space? Can you remove the capture from the image, and add it in html using figcaption.
</div>
<div style="text-align: center; ">
@@ -2754,43 +2754,7 @@
</section>
-<!--
-<section id="record-RecipeLink">
-<h3>Recipe Link</h3>
-
-<div class="note">
-At the teleconference of 12/08/2012, the WG decided that the word Plan
-should be used, instead of recipe. Given that a plan can change, it
-is useful to track its provenance. So a Plan is a kind of entity.
-Furthermore, a new relationship between activity and Plan is going to
-be introduced. This relationship is a specialization of
-wasAssociatedWith. By entailment, this makes a Plan an agent, since
-associated with an activity.
-</div>
-
-
-<p>A <dfn id="dfn-RecipeLink">recipe link</dfn> is an association between an activity record and a process specification that underpins the represented activity. Such IRI has no specific interpretation in the context of PROV-DM.
-</p>
-
-<div class='grammar'>
-<span class="nonterminal">recipeLink</span> ::= <span class="nonterminal">IRI</span>
-</div>
-
-<p>
-It is OPTIONAL to assert recipe links in activities.
-</p>
-
-
-<p>
-Process specifications, as referred to by recipe links, are out of scope of this specification.
-</p>
-
-
-<div class='issue'> Simplify the references to recipe link. This is <a href="http://www.w3.org/2011/prov/track/issues/131">ISSUE-131</a></div>
-
-</section>
-
--->
+
@@ -2829,8 +2793,6 @@
<figcaption>PROV-DM Common Relations</figcaption>
</div>
-<div class='issue'>We have defined a set of common relation, in response to <a href="http://www.w3.org/2011/prov/track/issues/44">ISSUE-44</a>. Is this set complete?</div>
-
<section id="record-traceability">
<h3>Traceability Record</h3>
@@ -2987,11 +2949,11 @@
</pre>
<p> We cannot infer <span class="name">wasInformedBy(a3,a1)</span> from them. Indeed,
from
-<span class="name">wasInformedBy(a2,a1)</span>, we know that there exists <span class="name">e1</span> such that <span class="name">e1</span> was generated by <span class="name">a1</span> and used by <span class="name">a2</span>. Likewise, from <span class="name">wasInformedBy(a3,a2)</span>, we know that there exists <span class="name">e2</span> such that <span class="name">e2</span> was generated by <span class="name">a2</span> and used by <span class="name">a3</span>. The following illustration shows a case where transitivity cannot hold. The horizontal axis represents time. We see that <span class="name">e1</span> was generated after <span class="name">e2</span> was used. Furthermore, the illustration also shows that <span class="name">a3</span> completes before <span class="name">a1</span>. So it is impossible for <span class="name">a3</span> to have used an entity generated by <span class="name">a1</span>.</p>
+<span class="name">wasInformedBy(a2,a1)</span>, we know that there exists <span class="name">e1</span> such that <span class="name">e1</span> was generated by <span class="name">a1</span> and used by <span class="name">a2</span>. Likewise, from <span class="name">wasInformedBy(a3,a2)</span>, we know that there exists <span class="name">e2</span> such that <span class="name">e2</span> was generated by <span class="name">a2</span> and used by <span class="name">a3</span>. The following illustration shows a case for which transitivity cannot hold. The horizontal axis represents the event line. We see that <span class="name">e1</span> was generated after <span class="name">e2</span> was used. Furthermore, the illustration also shows that <span class="name">a3</span> completes before <span class="name">a1</span>. So it is impossible for <span class="name">a3</span> to have used an entity generated by <span class="name">a1</span>.</p>
<div style="text-align: center;">
<img src="informedByNonTransitive.png" alt="non transitivity of wasInformedBy" />
-
+<figcaption>Counter-example for transitivity of wasInformedBy</figcaption>
</div>
<p>
@@ -3041,17 +3003,6 @@
For the interpretation of a control flow ordering record, see <a href="#wasStartedBy-ordering">wasStartedBy-ordering</a>.
</div>
-<!--
-<div class='interpretation' id='wasStartedBy-ordering'>
-Given two activity records denoted by <span class="name">a1</span> and <span class="name">a2</span>, <span class='conditional'>if</span> the record <span class="name">wasStartedBy(a2,a1)</span>
- holds, <span class='conditional'>then</span> the following temporal constraint holds: the
-<a title="activity start event">start</a> event of the activity record denoted by <span class="name">a1</span> <a>precedes</a> the <a title="activity start event">start event</a> of
-the activity record denoted by <span class="name">a2</span>.
-</div>
--->
-
-
-<div class='pending'>Suggested definition for process ordering. This is <a href="http://www.w3.org/2011/prov/track/issues/50">ISSUE-50</a>.</div>
</section>
@@ -3131,10 +3082,10 @@
<section id="recod-attribution">
<h3>Attribution Record</h3>
-<p>An attribution record represents that an entity is ascribed to an agent and is compliant with the <span class="nonterminal">attributionRecord</span> production.</p>
-
-
-<p> An attribution record, written <span class="name"> wasAttributedTo(e,ag,attr)</span>, contains the following components:</p>
+<p>An <dfn>attribution record</dfn> represents that an entity is ascribed to an agent.</p>
+
+
+<p> An attribution record, written <span class="name"> wasAttributedTo(e,ag,attr)</span> in PROV-ASN, contains the following components:</p>
<ul>
<li><em>entity</em>: an identifier <span class="name">e</span> of an entity record;</li>
<li><em>agent</em>: an identifier <span class="name">ag</span> of an agent whom the entity is attributed to;</li>
@@ -3147,11 +3098,11 @@
<span class='conditional'>If</span>
<span class="name">wasAttributedTo(e,ag)</span> holds for some identifiers
<span class="name">e</span> and <span class="name">ag</span>,
-<span class='conditional'>then</span> there exists an activity identified by <span class="name">pe</span> such that the following statements hold:
+<span class='conditional'>then</span> there exists an activity identified by <span class="name">a</span> such that the following statements hold:
<pre>
-activity(pe,t1,t2,attr1)
-wasGenerateBy(e,pe)
-wasAssociatedWith(pe,ag,attr2)
+activity(a,t1,t2,attr1)
+wasGenerateBy(e,a)
+wasAssociatedWith(a,ag,attr2)
</pre>
for some sets of attribute-value pairs <span class="name">attr1</span> and <span class="name">attr2</span>, time <span class="name">t1</span>, and <span class="name">t2</span>.
</div>
@@ -3176,11 +3127,10 @@
<h3>Quotation Record</h3>
-<p> A quotation record is a representation of the repeating or copying of some part of an entity, compatible with
-the <span class="nonterminal">quotationRecord</span> production.</p>
-
-
-<p> A quotation record, written <span class="name"> wasQuotedFrom(e2,e1,ag2,ag1,attrs)</span>, contains:</p>
+<p> A <dfn>quotation record</dfn> is a representation of the repeating or copying of some part of an entity.</p>
+
+
+<p> A quotation record, written <span class="name"> wasQuotedFrom(e2,e1,ag2,ag1,attrs)</span> in PROV-ASN, contains:</p>
<ul>
<li><em>quote</em>: an identifier <span class="name">e2</span>, identifying an entity record that represents the quote;
<li><em>quoted</em>: an identifier <span class="name">e1</span>, identifying an entity record representing what is being quoted;
@@ -3230,7 +3180,7 @@
-<p> An assertion wasSummaryOf, written <span class="name"> wasSummaryOf(e2,e1,attrs)</span>, contains:</p>
+<p> A summary record, written <span class="name"> wasSummaryOf(e2,e1,attrs)</span> in PROV-ASN, contains:</p>
<ul>
<li><em>summarizedEntity</em>: an identifier <span class="name">e2</span> for the entity record that represents the summary;
<li><em>fullEntity</em>: an identifier <span class="name">e1</span> for the entity record that represents what is being summarized;
@@ -3255,6 +3205,8 @@
<span class="name">)</span>
</div>
+<div class='issue'>Drop this relation <a href="http://www.w3.org/2011/prov/track/issues/220">ISSUE-220</a>.</div>
+
</section>
@@ -3263,9 +3215,7 @@
<h3>Original Source Record</h3>
<p>An <dfn>original source record</dfn> represents an entity in
-which another entity first appeared. A original-source
-record is compliant with the
-<span class="nonterminal">originalSourceRecord</span> production.</p>
+which another entity first appeared. </p>
<p> An assertion hadOriginalSource, written <span class="name"> hadOriginalSource(e2,e1,attrs)</span>, contains:</p>
@@ -3297,6 +3247,16 @@
<section id="record-Collection">
<h3>Collections</h3>
+<div class='issue'>
+Section in flux to address
+various comments about collections:
+<a href="http://www.w3.org/2011/prov/track/issues/135">ISSUE-135</a>,
+<a href="http://www.w3.org/2011/prov/track/issues/135">ISSUE-136</a>,
+<a href="http://www.w3.org/2011/prov/track/issues/135">ISSUE-137</a>,
+<a href="http://www.w3.org/2011/prov/track/issues/135">ISSUE-138</a>
+<a href="http://www.w3.org/2011/prov/track/issues/135">ISSUE-139</a>
+</div>
+
Activity-entity assertions account for the provenance of entities in terms of how they are produced and consumed. The <em>collection</em> assertions introduced in this section complement those by offering a family of entity-entity assertions that can be used to express structural relationships amongst entities. Specifically, their purpose is to enable modelling of part-of relationships amongst entities. In particular, a form of <strong>collection</strong> entity type is introduced, consisting of a <strong>set of key-value pairs</strong>. Key-value pairs provide a generic indexing structure that can be used to model commonly used data structures, including associative lists (also known as "dictionaries" in some programming languages), relational tables, ordered lists, and more.<p/>
Collections are entities that contain <strong>sets</strong> of key-value pairs. Both keys and values are also entities.