--- a/model/working-copy/towards-wd4.html Tue Feb 14 04:49:44 2012 +0000
+++ b/model/working-copy/towards-wd4.html Tue Feb 14 04:59:28 2012 +0000
@@ -1420,12 +1420,12 @@
<h4>Annotation</h4>
-<p>An <dfn title="concept-annotation">annotation</dfn> establishes a link between something that is identifiable and a note referred to by its identifier. Multiple notes can
+<p>An <dfn title="concept-annotation">annotation</dfn> is a link between something that is identifiable and a note referred to by its identifier. Multiple notes can
be associated with a given identified object; symmetrically, multiple objects can be associated with a given note. Since notes have identifiers, they can also be
annotated. The annotation mechanism (with note and annotation) forms a key aspect of the extensibility mechanism of PROV-DM (see <a
href="#extensibility-section">extensibility section</a>).</p>
-<p>An <dfn title="dfn-annotation">annotation</dfn><span class="withAsn">, written <span class="name">hasAnnotation(id,r,n,attrs)</span> in PROV-ASN,</span> has the following constituents:</p>
+<p>An <dfn title="dfn-annotation">annotation relation</dfn><span class="withAsn">, written <span class="name">hasAnnotation(id,r,n,attrs)</span> in PROV-ASN,</span> has the following constituents:</p>
<ul>
<li><em>id</em>: an OPTIONAL identifier for this relation;</li>
<li><em>something</em>: the identifier of something being annotated;</li>
@@ -1433,9 +1433,6 @@
<li><em>attributes</em>: an OPTIONAL set of attribute-value pairs to further describe this annotation.</li>
</ul>
-<p>The interpretation of notes is application-specific. See Section <a href="#term-note">Note</a> for a discussion of the difference between note attributes and other attributes in elements and relations.
-We also note the present tense in this term to indicate that it may not denote something in the past.</p>
-
<div class="anexample">
<p>
The following expressions</p>
@@ -1670,49 +1667,71 @@
<div class='note'>will turn into UML</div>
-<section id="term-traceability">
-<h3>Traceability</h3>
-
-<p> A <dfn title="dfn-Traceability">traceability relation</dfn> between two entities <span class="name">e2</span> and <span class="name">e1</span> states a generic dependency of <span class="name">e2</span>
-on <span class="name">e1</span>. Such dependency may indicate either that <span class="name">e1</span> was necessary for <span class="name">e2</span> to be created, or that <span class="name">e1</span> bears
-some responsibility for <span class="name">e2</span>'s existence.
-
-
-<p> A traceability relation<span class="withAsn">, written <span class="name">tracedTo(id,e2,e1,attrs)</span> in PROV-ASN,</span> contains:</p>
+
+
+
+<section id="term-Revision">
+<h3>Revision</h3>
+
+<p> A <dfn title="dfn-Revision">revision relation</dfn> is a particular case of <a href="#Derivation-Relation">derivation</a> that states that an entity is a revised version of another. The agent who is responsible for making the revision may optionally be specified.</p>
+
+<p> A revision relation<span class="withAsn">, written <span class="name">wasRevisionOf(id,e2,e1,ag,attrs)</span> in PROV-ASN,</span> contains:</p>
<ul>
-<li><em>id</em>: an OPTIONAL identifier identifying the relation;</li>
-<li><em>entity</em>: an identifier identifying an entity;
-<li><em>ancestor</em>: an identifier identifying an ancestor entity that the former depends on;
-<li><em>attributes</em>: an OPTIONAL set of attribute-value pairs to further describe properties of the relation.</li>
+<li><em>id</em>: an OPTIONAL identifier for the relation;</li>
+<li><em>newer</em>: the identifier of the revised entity;
+<li><em>older</em>: the identifier of the older entity;
+<li><em>responsibility</em>: an OPTIONAL identifier for the agent who approved that newer entity is a variant of the older;
+<li><em>attributes</em>: an OPTIONAL set of attribute-value pairs to further describe the properties of this relation.</li>
+</ul>
+
+
+
+<div class="anexample">
+<p>
+Revisiting the example of <a href="#section-example-a">Section 3.1</a>,
+we can now state that the report
+ <span class="name">tr:WD-prov-dm-20111215</span> is a revision of
+ the report <span class="name">tr:WD-prov-dm-20111018</span>, approved by
+agent <span class="name">w3:Consortium</span>.
+<pre class="codeexample">
+entity(tr:WD-prov-dm-20111215, [ prov:type="pr:RecsWD" %% xsd:QName ])
+entity(tr:WD-prov-dm-20111018, [ prov:type="pr:RecsWD" %% xsd:QName ])
+wasRevisionOf(tr:WD-prov-dm-20111215, tr:WD-prov-dm-20111018, w3:Consortium)
+</pre>
+</div>
+
+
+
+</section> <!-- end revision -->
+
+
+<section id="term-attribution">
+<h3>Attribution</h3>
+
+<p><dfn id="dfn-attribution">Attribution</dfn> is the ascribing of an entity to an agent. More precisely, when an entity <span class="name">e</span> is attributed to agent <span class="name">ag</span>, entity <span class="name">e</span> was generated by some activity <span class="name">a</span>, which in turn was associated to agent <span class="name">ag</span>. Thus, this relation is useful when the activity is not known, or irrelevant.
+
+<p> An attribution relation<span class="withAsn">, written <span class="name"> wasAttributedTo(id,e,ag,attr)</span> in PROV-ASN,</span> contains the following elements:</p>
+<ul>
+<li><em>id</em>: an OPTIONAL identifier for the relation;</li>
+<li><em>entity</em>: an entity identifier;</li>
+<li><em>agent</em>: the identifier of the agent whom the entity is ascribed to;</li>
+<li><em>attributes</em>: an OPTIONAL set of attribute-value pairs to further describe the properties of the relation.</li>
</ul>
<div class="anexample">
-<p>We refer to the example of <a href="#section-example-a">Section 3.1</a>, and specifically to <a href="#prov-tech-report">Figure prov-tech-report</a>. We can see that there is a path from
-<span class="name">tr:WD-prov-dm-20111215</span> to
-<span class="name">w3:Consortium</span> or to
-<span class="name">pr:rec-advance</span>. This is expressed as follows.
+<p>
+Revisiting the example of <a href="#section-example-b">Section 3.2</a>,
+we can ascribe <span class="name">tr:WD-prov-dm-20111215</span> to some agents without having to make an activity explicit.
<pre class="codeexample">
- tracedTo(tr:WD-prov-dm-20111215,w3:Consortium)
- tracedTo(tr:WD-prov-dm-20111215,pr:rec-advance)
+agent(ex:Paolo, [ prov:type="Person" ])
+agent(ex:Simon, [ prov:type="Person" ])
+entity(tr:WD-prov-dm-20111215, [ prov:type="pr:RecsWD" %% xsd:QName ])
+wasAttributedTo(tr:WD-prov-dm-20111215, ex:Paolo, [prov:role="editor"])
+wasAttributedTo(tr:WD-prov-dm-20111215, ex:Simon, [prov:role="contributor"])
</pre>
</div>
-
-
-
-<div class='note'>
- I propose to delete the following, given that this document does not mention inferences.
-<p>Further considerations:</p>
-<ul>
- <li>Traceability is more general than <a href="#Derivation-Relation">Derivation</a>. This means that an assertion of the form: <span class="name">tracedTo(...,e2,e1,...)</span> can be inferred from an assertion of the form:
- <span class="name">wasDerivedFrom(e2,e1,..)</span>. The precise inference rules are specified in [REF].
- <li>Traceability is related to responsibility by way of inference rules that involve <a href="#term-responsibility">responsibility chain</a> and <a href="#term-Generation">generation</a> relations.
- These rules are specified in [REF]
-</ul>
-</div>
-
-</section>
-
+</section> <!-- end attribution -->
<section id="term-OrderingOfActivities">
<h3>Activity Ordering</h3>
@@ -1774,66 +1793,49 @@
</section>
-
-<section id="term-Revision">
-<h3>Revision</h3>
-
-<p> A <dfn title="dfn-Revision">revision relation</dfn> is a particular case of <a href="#Derivation-Relation">derivation</a> that states that an entity is a revised version of another. The agent who is responsible for making the revision may optionally be specified.</p>
-
-<p> A revision relation<span class="withAsn">, written <span class="name">wasRevisionOf(id,e2,e1,ag,attrs)</span> in PROV-ASN,</span> contains:</p>
+<section id="term-traceability">
+<h3>Traceability</h3>
+
+<p> A <dfn title="dfn-Traceability">traceability relation</dfn> between two entities <span class="name">e2</span> and <span class="name">e1</span> states a generic dependency of <span class="name">e2</span>
+on <span class="name">e1</span>. Such dependency may indicate either that <span class="name">e1</span> was necessary for <span class="name">e2</span> to be created, or that <span class="name">e1</span> bears
+some responsibility for <span class="name">e2</span>'s existence.
+
+
+<p> A traceability relation<span class="withAsn">, written <span class="name">tracedTo(id,e2,e1,attrs)</span> in PROV-ASN,</span> contains:</p>
<ul>
-<li><em>id</em>: an OPTIONAL identifier for the relation;</li>
-<li><em>newer</em>: the identifier of the revised entity;
-<li><em>older</em>: the identifier of the older entity;
-<li><em>responsibility</em>: an OPTIONAL identifier for the agent who approved that newer entity is a variant of the older;
-<li><em>attributes</em>: an OPTIONAL set of attribute-value pairs to further describe the properties of this relation.</li>
-</ul>
-
-
-
-<div class="anexample">
-<p>
-Revisiting the example of <a href="#section-example-a">Section 3.1</a>,
-we can now state that the report
- <span class="name">tr:WD-prov-dm-20111215</span> is a revision of
- the report <span class="name">tr:WD-prov-dm-20111018</span>, approved by
-agent <span class="name">w3:Consortium</span>.
-<pre class="codeexample">
-wasRevisionOf(tr:WD-prov-dm-20111215, tr:WD-prov-dm-20111018, w3:Consortium)
-</pre>
-</div>
-
-
-
-</section> <!-- end revision -->
-
-
-<section id="term-attribution">
-<h3>Attribution</h3>
-
-<p><dfn id="dfn-attribution">Attribution</dfn> is the ascribing of an entity to an agent. More precisely, when an entity <span class="name">e</span> is attributed to agent <span class="name">ag</span>, entity <span class="name">e</span> was generated by some activity <span class="name">a</span>, which in turn was associated to agent <span class="name">ag</span>. Thus, this relation is useful when the activity is not known, or irrelevant.
-
-<p> An attribution relation<span class="withAsn">, written <span class="name"> wasAttributedTo(id,e,ag,attr)</span> in PROV-ASN,</span> contains the following elements:</p>
-<ul>
-<li><em>id</em>: an OPTIONAL identifier for the relation;</li>
-<li><em>entity</em>: an entity identifier;</li>
-<li><em>agent</em>: the identifier of the agent whom the entity is ascribed to;</li>
-<li><em>attributes</em>: an OPTIONAL set of attribute-value pairs to further describe the properties of the relation.</li>
+<li><em>id</em>: an OPTIONAL identifier identifying the relation;</li>
+<li><em>entity</em>: an identifier identifying an entity;
+<li><em>ancestor</em>: an identifier identifying an ancestor entity that the former depends on;
+<li><em>attributes</em>: an OPTIONAL set of attribute-value pairs to further describe properties of the relation.</li>
</ul>
<div class="anexample">
-<p>
- Suppose one knows that agent <span class="name">ag</span>, a document quality controller, has been responsible for the generation of a certain version <span class="name">e</span> of a document.
- This can be expressed simply as:
-
+<p>We refer to the example of <a href="#section-example-a">Section 3.1</a>, and specifically to <a href="#prov-tech-report">Figure prov-tech-report</a>. We can see that there is a path from
+<span class="name">tr:WD-prov-dm-20111215</span> to
+<span class="name">w3:Consortium</span> or to
+<span class="name">pr:rec-advance</span>. This is expressed as follows.
<pre class="codeexample">
-agent(ag,[prov:type="QualityController"])
-entity(e,[prov:type="document"])
-wasAttributedTo(e,ag)
+ tracedTo(tr:WD-prov-dm-20111215,w3:Consortium)
+ tracedTo(tr:WD-prov-dm-20111215,pr:rec-advance)
</pre>
</div>
-</section> <!-- end attribution -->
+
+
+
+<div class='note'>
+ I propose to delete the following, given that this document does not mention inferences.
+<p>Further considerations:</p>
+<ul>
+ <li>Traceability is more general than <a href="#Derivation-Relation">Derivation</a>. This means that an assertion of the form: <span class="name">tracedTo(...,e2,e1,...)</span> can be inferred from an assertion of the form:
+ <span class="name">wasDerivedFrom(e2,e1,..)</span>. The precise inference rules are specified in [REF].
+ <li>Traceability is related to responsibility by way of inference rules that involve <a href="#term-responsibility">responsibility chain</a> and <a href="#term-Generation">generation</a> relations.
+ These rules are specified in [REF]
+</ul>
+</div>
+
+</section>
+
<section id="term-quotation">