--- a/model/comments/issue-274-gk.txt Mon Mar 12 11:09:38 2012 -0400
+++ b/model/comments/issue-274-gk.txt Mon Mar 12 16:54:25 2012 +0000
@@ -15,6 +15,12 @@
> I'd wish to see all references to "things in the world" expunged: it's
> an ugly expression that begs more questions than it answers, and IMO
> runs the risk of confusing readers.
+
+
+Do you want to remove reference to "things" too?
+
+
+
>
> Section 1 intro: rewording in 1st 3 paras.
>
@@ -22,10 +28,22 @@
> separate part/document. Drop references to ASN - it's *not* an
> *abstract* syntax notion; indeed, I think that very expression is an
> oxymoron.
+
+The WG needs to make a decision on this.
+
+My preference, at this stage, is to leave it in a separate document.
+1. Past experience has shown that readers confuse prov-dm and prov-n
+2. PROV-N definition is just a grammar, and the grammar is not useful
+ to understand prov-dm
+
+
>
> Part 2 is *not* an upgrade path. Please don't say this. (It's a
> refinement of use that allows provenance information from different
> sources to be combined in meaningful ways.)
+
+We can, though, others were supportive of the statements ...
+
>
> More text refinement in section 1.
>
@@ -34,6 +52,12 @@
>
> Saying "Activity is anything ..." is confusing. It suggests a
> continuant rather than an occurrent.
+
+Why not make this explicit:
+
+An activity is something that occurs and acts upon or with entities.
+
+
>
> Sub-editing would improve this.
>
@@ -43,12 +67,24 @@
> I think it would be clearer if generation and usage were introduced as
> events associated with activities. (Discussion of them being
> instantaneous can come in Part 2)
+
+It was agreed at F2F2 that we shouldn't introduce event in part 1.
+We followed this guidance.
+
+
>
> Introducing generation as "completed production" reads really
> strangely to me, and sounds as if it could be a produced artifact. I
> think a form like "completion of production" is clearer. Similarly
> for usage, something like "starting to consume".
>
+
+We can write:
+Generation is the completion of production of a new entity by an activity.
+
+Usage is the beginning of consumption of a new entity by an activity.
+
+
> Sub-editing would improve this.
>
>
@@ -56,15 +92,29 @@
>
> "AccountEntity" - why not just "Account". Also, I understood this was
> to *be* a bundle, not a container for a bundle.
+
+To be addressed, once other editing work for WD5 is completed.
+
+The two notions (container vs bundle) are useful, for different purposes.
+To be investigated.
+
+
>
> The example given has no clear relationship to the description. I
> understood the key use-case here was to express provenance of
> procenance, and that is why we have accounts. I think that should be
> stated clearly; e.g.
+
>
> "An account is a bundle of provenance statements treated as an entity
> which may itself have some associated provenance."
>
+
+Subtle difference again: "... treated as an entity ..." vs " ... is an entity ..."
+
+We can definitely add "... which may itself have some associated provenance "
+
+
>
> Agents. I think the notion of responsibility here is so loose as to
> be of no practical value. When we say a text editor is "responsible
@@ -77,6 +127,11 @@
> agents. I suggest that the text here should "stick to the knitting":
> just state that these are commonly encountered kinds of agent, and
> leave it at that.
+
+I am not exactly sure what needs to be addressed here.
+ "accountable system" is definitely topical.
+
+
>
>
> Section 2.4
--- a/model/releases/WD-prov-dm-20120309/prov-dm.html Mon Mar 12 11:09:38 2012 -0400
+++ b/model/releases/WD-prov-dm-20120309/prov-dm.html Mon Mar 12 16:54:25 2012 +0000
@@ -2034,8 +2034,7 @@
-<p></p><div class="attributes" id="attributes-alternate">
-An <dfn title="dfn-Alternate" id="dfn-dfn-alternate">alternate relation</dfn><span class="withPn">, written <span class="pnExpression">alternateOf(alt1, alt2)</span> in PROV-N,</span> addresses case (1). It has the following constituents:
+<p></p><div class="attributes" id="attributes-alternate">An <dfn title="dfn-Alternate" id="dfn-dfn-alternate">alternate relation</dfn><span class="withPn">, written <span class="pnExpression">alternateOf(alt1, alt2)</span> in PROV-N,</span> addresses case (1). It has the following constituents:
<ul>
<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>
@@ -2053,8 +2052,7 @@
<p>
-</p><div class="attributes" id="attributes-specialization">
-A <dfn title="dfn-Specialization" id="dfn-dfn-specialization">specialization relation</dfn><span class="withPn">, written <span class="pnExpression">specializationOf(sub, super)</span> in PROV-N,</span> addresses case (2). It has the following constituents:
+</p><div class="attributes" id="attributes-specialization">A <dfn title="dfn-Specialization" id="dfn-dfn-specialization">specialization relation</dfn><span class="withPn">, written <span class="pnExpression">specializationOf(sub, super)</span> in PROV-N,</span> addresses case (2). It has the following constituents:
<ul>
<li><span class="attribute">specializedEntity</span>: an identifier of the specialized entity;</li>
@@ -2093,11 +2091,12 @@
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" id="dfn-dfn-annotation">annotation relation</dfn><span class="withPn">, written <span class="pnExpression">hasAnnotation(r,n)</span> in PROV-N,</span> has the following constituents:</p>
+<p><div class="attributes" id="attributes-annotation">An <dfn title="dfn-annotation" id="dfn-dfn-annotation">annotation relation</dfn><span class="withPn">, written <span class="pnExpression">hasAnnotation(r,n)</span> in PROV-N,</span> has the following constituents:</p>
<ul>
<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>
</ul>
+</div>
<div class="anexample">
<p>