--- a/model/comments/issue-274-tim.txt Thu Mar 01 14:53:55 2012 +0100
+++ b/model/comments/issue-274-tim.txt Thu Mar 01 19:16:30 2012 +0100
@@ -90,18 +90,34 @@
>
>
> Sections entitled "Activity-Entity Relation" seem a bit unnatural. Perhaps something like "Relations between Activities and Entities" would be clearer.
+
+Title will change when components are introduced.
+
>
> The phrase "when the data it is about changes" is unclear.
+
+Updated to:
+ However, if data changes, it is challenging to express its provenance precisely, like it would be for any other form of metadata.
+
>
> "To address this challenge, an upgrade path is proposed to enrich simple provenance..." This paragraph is nice. I'd suggest including "specific subject" in "qualify the subject of provenance".
+
+Done.
+
>
>
> Is it okay to use ASN before it is defined? "In section 3, PROV-DM is applied to a short scenario, encoded in PROV-ASN, and illustrated graphically."
>
> "Section 4 provides the definition of PROV-DM." is a bit ambiguous. Please elaborate.
+
+of PROV-DM constructs.
+
>
>
> The following duplicates: "Activities that operate on digital entities may for example move, copy, or duplicate them. Activities that operate on digital entities may for example move, copy, or duplicate them."
+
+Done.
+
>
> I propose to change the Agent definition from->to:
> "An agent is a type of entity that can be associated to an activity, to indicate that it bears some form of responsibility for the activity taking place."
--- a/model/glossary.html Thu Mar 01 14:53:55 2012 +0100
+++ b/model/glossary.html Thu Mar 01 19:16:30 2012 +0100
@@ -10,7 +10,7 @@
<span class="glossary" id="glossary-activity">
An <dfn id="concept-activity">activity</dfn> is anything that acts upon or with entities.
-This action can take multiple forms: consuming, processing, transforming, modifying, relocating, using, generating, or being associated with entities. Activities that operate on digital entities may for example move, copy, or duplicate them.
+This action can take multiple forms: consuming, processing, transforming, modifying, relocating, using, generating, or being associated with entities.
</span>
<span class="glossary" id="glossary-agent">
--- a/model/glossary.js Thu Mar 01 14:53:55 2012 +0100
+++ b/model/glossary.js Thu Mar 01 19:16:30 2012 +0100
@@ -17,7 +17,7 @@
' ' +
'<span class="glossary" id="glossary-activity"> ' +
'An <dfn id="concept-activity">activity</dfn> is anything that acts upon or with entities. ' +
-'This action can take multiple forms: consuming, processing, transforming, modifying, relocating, using, generating, or being associated with entities. Activities that operate on digital entities may for example move, copy, or duplicate them. ' +
+'This action can take multiple forms: consuming, processing, transforming, modifying, relocating, using, generating, or being associated with entities. ' +
'</span> ' +
' ' +
'<span class="glossary" id="glossary-agent"> ' +
--- a/model/prov-dm.html Thu Mar 01 14:53:55 2012 +0100
+++ b/model/prov-dm.html Thu Mar 01 19:16:30 2012 +0100
@@ -300,7 +300,7 @@
<p>This specification intentionally presents the key concepts of the PROV Data Model, without drilling down into all its subtleties. Using these key concepts, it becomes possible to write useful provenance assertions very quickly, and publish or embed them along side the data they relate to. </p>
-<p>However, it becomes challenging for provenance, like for any other form of metadata, when the data it is about changes. To address this challenge, an <em>upgrade path</em> is proposed to enrich simple provenance, with extra-descriptions that help qualify the subject of provenance and provenance itself, with attributes and interval, intended to satisfy a comprehensive set of constraints. These aspects are covered in the companion specification [[PROV-DM-CONSTRAINTS]].
+<p>However, if data changes, then it is challenging to express its provenance precisely, like it would be for any other form of metadata. To address this challenge, an <em>upgrade path</em> is proposed to enrich simple provenance, with extra-descriptions that help qualify the specific subject of provenance and provenance itself, with attributes and interval, intended to satisfy a comprehensive set of constraints. These aspects are covered in the companion specification [[PROV-DM-CONSTRAINTS]].
</p>
@@ -313,7 +313,7 @@
applied to a short scenario, encoded in PROV-ASN, and illustrated
graphically.</p>
-<p><a href="#data-model-concepts">Section 4</a> provides the definition of PROV-DM.</p>
+<p><a href="#data-model-concepts">Section 4</a> provides the definition of PROV-DM constructs.</p>
<p><a href="#common-relations">Section 5</a> introduces further relations offered by PROV-DM, including relations for data collections and domain-independent common relations.</p>
@@ -1503,13 +1503,11 @@
<p><div class="attributes" id="attributes-alternate">
-An <dfn title="dfn-Alternate">alternate relation</dfn><span class="withAsn">, written <span class="name">alternateOf(id, alt1, alt2, attrs)</span> in PROV-ASN,</span> addresses case (1). It has the following constituents:</p>
+An <dfn title="dfn-Alternate">alternate relation</dfn><span class="withAsn">, written <span class="name">alternateOf(alt1, alt2)</span> in PROV-ASN,</span> addresses case (1). It has the following constituents:</p>
<ul>
-<li><span class='attribute'>id</span>: an OPTIONAL identifier for the association between the two alternates;</li>
<li><span class='attribute'>firstAlternate</span>: an identifier of the first of the two entities;</li>
-<li><span class='attribute'>secondAlternate</span>: an identifier of the second of the two entities;</li>
-<li><span class='attribute'>attributes</span>: an OPTIONAL set of attribute-value pairs to further describe this relation.</li>
+<li><span class='attribute'>secondAlternate</span>: an identifier of the second of the two entities.</li>
</ul>
</div>
@@ -1526,13 +1524,11 @@
<p>
<div class="attributes" id="attributes-specialization">
-A <dfn title="dfn-Specialization">specialization relation</dfn><span class="withAsn">, written <span class="name">specializationOf(id, sub, super, attrs)</span> in PROV-ASN,</span> addresses case (2). It has the following constituents:</p>
+A <dfn title="dfn-Specialization">specialization relation</dfn><span class="withAsn">, written <span class="name">specializationOf(sub, super)</span> in PROV-ASN,</span> addresses case (2). It has the following constituents:</p>
<ul>
-<li><span class='attribute'>id</span>: an OPTIONAL identifier for the association between the two entities;</li>
<li><span class='attribute'>specializedEntity</span>: an identifier of the specialized entity;</li>
-<li><span class='attribute'>generalEntity</span>: an identifier of the entity that is being specialized;</li>
-<li><span class='attribute'>attributes</span>: an OPTIONAL set of attribute-value pairs to further describe this relation.</li>
+<li><span class='attribute'>generalEntity</span>: an identifier of the entity that is being specialized.</li>
</ul>
</div>
@@ -1569,12 +1565,10 @@
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 relation</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(r,n)</span> in PROV-ASN,</span> has the following constituents:</p>
<ul>
-<li><span class='attribute'>id</span>: an OPTIONAL identifier for this relation;</li>
<li><span class='attribute'>something</span>: the identifier of something being annotated;</li>
-<li><span class='attribute'>note</span>: an identifier of a note;</li>
-<li><span class='attribute'>attributes</span>: an OPTIONAL set of attribute-value pairs to further describe this annotation.</li>
+<li><span class='attribute'>note</span>: an identifier of a note.</li>
</ul>
<div class="anexample">