SC comments
authorLuc Moreau <l.moreau@ecs.soton.ac.uk>
Fri, 23 Mar 2012 11:43:21 +0000
changeset 1982 95085386014c
parent 1981 741851a15821
child 1983 1fb8f5b10f8d
SC comments
model/comments/issue-274-sam.txt
model/prov-dm.html
--- a/model/comments/issue-274-sam.txt	Fri Mar 23 11:26:28 2012 +0000
+++ b/model/comments/issue-274-sam.txt	Fri Mar 23 11:43:21 2012 +0000
@@ -99,6 +99,14 @@
  > because it is nowhere used in the remainder of the document, neither
  > in PROV-DM part 2. It is confusing at the moment.
  > 
+
+The term "upgrade path" was replaced by "refinement".
+
+The last section reuses the term. As the introduction states it, this
+is discussed in part 2.
+
+
+
  >  
  > 
  > Section 2, Subsection2.3: AccountEntity very shortly explained
@@ -110,6 +118,11 @@
  > terminilogy. Maybe replace it by `Entity`.
  > 
  >  
+
+
+More work to be done on this, to decide how we handle accounts.
+There is no reference to resource in the definition.  
+
  > 
  > 
  > 
@@ -122,12 +135,21 @@
  > and/or activity. `Thing` brings in some semantics.
  > 
  >  
+
+This sentence is now removed from section 4.6.1. 
+A sentence to that effect already exists in 4.6.2.
+
  > 
  > Section 5, Subsection 5.7: The added value of `Original Source` over
  > `Traceability` is not clear. It should be better explained why we need
  > this relation. IMO, it could be expressed as a traceability relation
  > or a specialization of the traceability relation.
  > 
+
+Definition of Original Source has been revised. It should avoid the ambiguity.
+
+
+
  >  
  > 
  > Spelling Corrections:
@@ -141,6 +163,9 @@
  > move, copy, or duplicate them. Activities that operate on digital
  > entities may for example move, copy, or duplicate them.`
  > 
+
+The latter sentence is a refinement of the previous one for digital entities.
+I think this is OK.
  >  
  > 
  > Section 2, Subsection 2.2: Usage definition: Usage is the beginning on
@@ -148,6 +173,8 @@
  > had not begun to consume or use to this entity (and could not have
  > been affected by the entity).
  > 
+
+on -> of
  >  
  > 
  > Section 4, Subsection 4.1.4: example: `The note is associated with the
@@ -155,6 +182,8 @@
  > discussed in Section Annotation). The note's identifier and attributes
  > are declares declared in a separate namespace denoted by prefix ex2.`
  > 
+
+Text updated.
  >  
  > 
  >  
@@ -173,6 +202,10 @@
  > is part of the core prov-dm model. Then PROV-DM part 2 focusses on the
  > additional constraints.
  > 
+
+We decided at F2F2 that the notion of event should not be discussed in the prov-dm document (part 1). 
+It is left to part 2 (semantics/constraints).
+
  >  
  > 
  > Section 2, Subsection 2.2: The example of different perspectives on a
@@ -185,6 +218,10 @@
  > 
  >  
  > 
+
+
+TODO
+
  > Spelling Corrections:
  > 
  >  
--- a/model/prov-dm.html	Fri Mar 23 11:26:28 2012 +0000
+++ b/model/prov-dm.html	Fri Mar 23 11:43:21 2012 +0000
@@ -2247,8 +2247,7 @@
 
 
 
-<p>A separate PROV-DM relation is used to associate a note with something that is identifiable (see <a href="#term-annotation">Section on annotation</a>). A given note may be associated with
-multiple identifiable things.
+<p>A separate PROV-DM relation is used to associate a note with something that is identifiable. 
 </p>
 
 
@@ -2261,8 +2260,9 @@
 note(ex2:n1,[ex2:color="blue", ex2:screenX=20, ex2:screenY=30])
 hasAnnotation(tr:WD-prov-dm-20111215,ex2:n1)
 </pre>
-<p>The note is associated with the entity <span class="name">tr:WD-prov-dm-20111215</span> previously introduced (<a title="annotation">hasAnnotation</a> is 
-discussed in Section <a href="#term-annotation">Annotation</a>).  The note's identifier and attributes are declared in a separate namespace denoted by prefix <span class="name">ex2</span>.
+<p>The note is associated with the entity <span class="name">tr:WD-prov-dm-20111215</span>.
+Relation <a title="annotation">hasAnnotation</a> is 
+discussed in Section <a href="#term-annotation">Annotation</a>.  The note's identifier and attributes are declared in a separate namespace denoted by prefix <span class="name">ex2</span>.
 </p>
 </div>
 
@@ -2591,7 +2591,7 @@
 <li>
 <p> The example of <a href="#prov-dm-example">section 3</a> contains identifiers such as <span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111215">tr:WD-prov-dm-20111215</a></span>, which denotes a specific version of a technical report.  On the other hand, a URI such as <a href="http://www.w3.org/TR/prov-dm/">http://www.w3.org/TR/prov-dm/</a> points to the latest version of a document. One needs to ensure that provenance descriptions for the latter document remain valid as denoted resources change. </p>
 
-<p>To this end, PROV-DM allows asserters to describe "<em>partial states</em>" of entities by means of attributes and associated values. Some further constraints apply to the use of these attributes, since the values associated with them are expected to remain unchanged for some period of time. The constraints associated to attributes are also specified in the companion specification [[PROV-DM-CONSTRAINTS]].</p>
+<p>To this end, PROV-DM allows asserters to describe "<em>partial states</em>" of entities by means of attributes and associated values. Some further constraints apply to the use of these attributes, since the values associated with them are expected to remain unchanged for some period of time. The constraints associated to attributes allow provenance descriptions to be refined, they can also be found in the companion specification [[PROV-DM-CONSTRAINTS]].</p>
 
 
 </li>