--- a/model/comments/lc-ack-robert.txt Fri Oct 26 13:22:18 2012 +0100
+++ b/model/comments/lc-ack-robert.txt Fri Oct 26 13:55:12 2012 +0100
@@ -13,7 +13,7 @@
clarification.
New change implemented.
-Further ack to obtain.
+Acknowledgement expected.
1.1.4 ISSUE-504 (collection/bundle)
@@ -49,6 +49,8 @@
Suggested change implemented.
Further response added.
+Acknowledgement expected.
+
1.1.15 ISSUE-516 (DerivationAsBundle) Section 5.2.1 states, "there
must be some underpinning activities performing the necessary
actions resulting in such a derivation". Note both "activities"
@@ -111,7 +113,18 @@
change would invalidate the entity. This example seems to
contradict the working group's response to the question.
-TODO
+I added the following to our response.
+
+In the follow-on message, the reviewer discusses the traffic light example. As the light changes from red to green, the green traffic light is invalidated and the red traffic light is generated. Both are specializations of the traffic-light, which continues its existence across this change state, since color is not one of its attributes.
+entity(ex:traffic-light)
+entity(ex:green-traffic-light, [ex:color="green"])
+entity(ex:red-traffic-light, [ex:color="red"])
+specializationOf(ex:green-traffic-light, ex:traffic-light)
+specializationOf(ex:red-traffic-light, ex:traffic-light)
+wasGeneratedBy(ex:red-traffic-light,-,2011-11-16T16:00:00)
+wasInvalidatedBy(ex:green-traffic-light,-,2011-11-16T16:00:00)
+
+I proposed to close this issue.
1.1.23 ISSUE-530 (attributes) I understand the group's difficulty
in reaching consensus on this issue. Since it is possible to
@@ -158,7 +171,7 @@
delegation. If these bounds need to be made explicit, than an
activity also needs to be made explicit.
-Acknowledgment expected
+Acknowledgment expected.
1.1.27 ISSUE-526 (Alternate) The text in the working group's
response to this comment (see below) is helpful. It might be
@@ -172,7 +185,10 @@
specific application context, alternateOf, or a subtype of it,
could allow you to infer more."
-TODO
+Change made
+http://dvcs.w3.org/hg/prov/diff/60b6ee097555/model/prov-dm.html
+Acknowledgment expected.
+
1.1.28 ISSUE-502 (Derivation) In my opinion, the initial
emphasis on transformation may muddle the definition. The
@@ -184,7 +200,7 @@
Sentence was added to the text explaining the notion of derivation:
http://dvcs.w3.org/hg/prov/diff/780b82818bcf/model/prov-dm.html
-Acknowledgment expected
+Acknowledgment expected.
----------------------------------------------------------------------
--- a/model/diff.html Fri Oct 26 13:22:18 2012 +0100
+++ b/model/diff.html Fri Oct 26 13:55:12 2012 +0100
@@ -1026,7 +1026,7 @@
pre.sh_sourceCode .sh_attribute { color: #006400; }
</style><link href="./extra-dm.css" rel="stylesheet" type="text/css" charset="utf-8"><link href="http://www.w3.org/StyleSheets/TR/W3C-ED" rel="stylesheet" type="text/css" charset="utf-8"></head>
- <body style="display: inherit; "><div class="head"><p><a href="http://www.w3.org/"><img width="72" height="48" src="http://www.w3.org/Icons/w3c_home" alt="W3C"></a></p><h1 class="title" id="title">PROV-DM: The PROV Data Model</h1><h2 id="subtitle"><a href="diff.html"><span class="insert">Changes</span></a><span class="insert"> since LC release</span></h2><h2 id="w3c-editor-s-draft-22-october-2012"><acronym title="World Wide Web Consortium">W3C</acronym> <span class="delete">Working</span><span class="insert">Editor's</span> Draft <span class="delete">24 July</span><span class="insert">22 October</span> 2012</h2><dl><dt>This version:</dt><dd><span class="delete">http://www.w3.org/TR/2012/WD-prov-dm-20120724/</span><a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html"><span class="insert">http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html</span></a></dd><dt>Latest published version:</dt><dd><a href="http://www.w3.org/TR/prov-dm/">http://www.w3.org/TR/prov-dm/</a></dd><dt>Latest editor's draft:</dt><dd><a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html">http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html</a></dd><dt>Previous version:</dt><dd><span class="delete">http://www.w3.org/TR/2012/WD-prov-dm-20120503/</span><span class="delete"> (</span><span class="delete">color-coded diffs</span><span class="delete">)</span><a href="http://www.w3.org/TR/2012/WD-prov-dm-20120724/"><span class="insert">http://www.w3.org/TR/2012/WD-prov-dm-20120724/</span></a></dd><dt>Editors:</dt><dd><a href="http://www.ecs.soton.ac.uk/~lavm/">Luc Moreau</a>, University of Southampton</dd>
+ <body style="display: inherit; "><div class="head"><p><a href="http://www.w3.org/"><img width="72" height="48" src="http://www.w3.org/Icons/w3c_home" alt="W3C"></a></p><h1 class="title" id="title">PROV-DM: The PROV Data Model</h1><h2 id="subtitle"><a href="diff.html"><span class="insert">Changes</span></a><span class="insert"> since LC release</span></h2><h2 id="w3c-editor-s-draft-26-october-2012"><acronym title="World Wide Web Consortium">W3C</acronym> <span class="delete">Working</span><span class="insert">Editor's</span> Draft <span class="delete">24 July</span><span class="insert">26 October</span> 2012</h2><dl><dt>This version:</dt><dd><span class="delete">http://www.w3.org/TR/2012/WD-prov-dm-20120724/</span><a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html"><span class="insert">http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html</span></a></dd><dt>Latest published version:</dt><dd><a href="http://www.w3.org/TR/prov-dm/">http://www.w3.org/TR/prov-dm/</a></dd><dt>Latest editor's draft:</dt><dd><a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html">http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html</a></dd><dt>Previous version:</dt><dd><span class="delete">http://www.w3.org/TR/2012/WD-prov-dm-20120503/</span><span class="delete"> (</span><span class="delete">color-coded diffs</span><span class="delete">)</span><a href="http://www.w3.org/TR/2012/WD-prov-dm-20120724/"><span class="insert">http://www.w3.org/TR/2012/WD-prov-dm-20120724/</span></a></dd><dt>Editors:</dt><dd><a href="http://www.ecs.soton.ac.uk/~lavm/">Luc Moreau</a>, University of Southampton</dd>
<dd><a href="http://www.cs.ncl.ac.uk/people/Paolo.Missier">Paolo Missier</a>, Newcastle University</dd>
<dt><span class="delete">Contributors:</span><span class="insert">Authors:</span></dt><dd><a href="http://semanticweb.org/wiki/Khalid_Belhajjame">Khalid Belhajjame</a>, University of Manchester</dd>
<dd><span>Reza B'Far</span>, Oracle Corporation</dd>
@@ -1503,7 +1503,9 @@
</div>
-<p>
+<p><span class="insert">
+The focus of derivation is on connecting a generated entity to a used
+entity.</span>
While the basic idea is simple, the concept of derivation can be quite
subtle: implicit is the notion that the generated entity was affected
in some way by the used entity.
@@ -1659,9 +1661,10 @@
-<p>To illustrate expanded relations, we consider the concept of
-association, described
-in <a class="section-ref" href="#section-agents-attribution-association-delegation"><span>Section 2.1.3</span></a>. Agents may <span class="delete">adopt</span><span class="insert">rely on</span> <em>plans</em>, i.e. sets of actions or steps, to achieve their
+<p>To illustrate expanded relations, we <span class="delete">consider</span><span class="insert">revisit</span> the concept of
+association, <span class="delete">described</span><span class="insert">introduced</span>
+in <a class="section-ref" href="#section-agents-attribution-association-delegation"><span>Section 2.1.3</span></a><span class="delete">.</span><span class="insert"> (full definition of the expanded association can be found
+in </span><a class="section-ref" href="#term-Association"><span><span class="insert">Section 5.3.3</span></span></a><span class="insert">).</span> Agents may <span class="delete">adopt</span><span class="insert">rely on</span> <em>plans</em>, i.e. sets of actions or steps, to achieve their
goals in the context of an activity.
Hence, an expanded form of
association relation allows for a plan to be specified. Plan is defined by subtyping and
@@ -1758,7 +1761,7 @@
<h4><span class="secno">2.2.3 </span>Collections</h4>
<p>
-<span class="glossary-ref"> A <span class="dfn">collection</span> is an entity that provides a structure to some constituents, which are themselves entities. These constituents are said to be <span class="dfn">member of</span> the collections. </span> Many different types of collections exist, such as <em>sets</em>, <em>dictionaries</em>, or <em>lists</em>.
+<span class="glossary-ref"> A <span class="dfn">collection</span> is an entity that provides a structure to some <span class="delete">constituents, which are</span><span class="insert">constituents that must</span> themselves<span class="insert"> be</span> entities. These constituents are said to be <span class="dfn">member of</span> the collections. </span> Many different types of collections exist, such as <em>sets</em>, <em>dictionaries</em>, or <em>lists</em>.
Using Collections, one can express the provenance of the collection itself in addition to that of the members. </p>
<div class="anexample conceptexample" id="collection-example"><div class="anexampleTitle">Example <span class="delete">14</span><span class="insert">15</span><sup><a class="internalDFN" href="#collection-example"><span class="diamond"> ◊</span></a></sup></div>
@@ -2151,11 +2154,11 @@
<div id="secondary-elements-relations-at-a-glance-div" style="text-align: center;">
<table class="thinborder" style="margin-left: auto; margin-right: auto;">
<caption id="secondary-elements-relations-at-a-glance"><span><span class="insert">Table 5</span><sup><a class="internalDFN" href="#secondary-elements-relations-at-a-glance"><span class="diamond"><span class="insert"> ◊:</span></span></a></sup> </span><span class="insert">Secondary optional elements in PROV-DM Relations</span></caption>
-<tbody><tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td colspan="6"><span class="insert">Secondary Object</span></td></tr>
+<tbody><tr><td style="border-width: 0px; "></td><td style="border-width: 0px;§> "></td><td colspan="6"><span class="insert">Secondary Object</span></td></tr>
<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td><span class="insert">Entity</span></td><td><span class="insert">Activity</span></td><td><span class="insert">Agent</span></td></tr>
-<tr><td rowspan="3"><span class="insert">Subject</span></td><td><span class="insert">Entity</span></td><td class="component5-color"><a href="#dfn-mentionof" class="internalDFN"><span class="insert">MentionOf</span></a><span class="insert"> (bundle)</span></td><td class="component2-color"><a href="#dfn-wasderivedfrom" class="internalDFN"><span class="insert">WasDerivedFrom</span></a><span class="insert"> (activity)</span><br><a><span class="insert">Revision (activity)</span></a><br><a><span class="insert">Quotation (activity)</span></a><br><a><span class="insert">PrimarySource (activity)</span></a></td><td colspan="2"><span class="insert">—</span></td></tr>
-<tr><td><span class="insert">Activity</span></td><td class="component3-color"><a href="#dfn-wasassociatedwith" class="internalDFN"><span class="insert">WasAssociatedWith</span></a><span class="insert"> (plan)</span></td><td class="component1-color"><a href="#dfn-wasstartedby" class="internalDFN"><span class="insert">WasStartedBy</span></a><span class="insert"> (starter)</span><br><a href="#dfn-wasendedby" class="internalDFN"><span class="insert">WasEndedBy</span></a><span class="insert"> (ender)</span></td><td colspan="2"><span class="insert">—</span></td></tr>
-<tr><td><span class="insert">Agent</span></td><td><span class="insert">—</span></td><td class="component3-color"><a href="#dfn-actedonbehalfof" class="internalDFN"><span class="insert">ActedOnBehalfOf</span></a><span class="insert"> (activity)</span></td><td><span class="insert">—</span></td></tr>
+<tr><td rowspan="3"><span class="insert">Subject</span></td><td><span class="insert">Entity</span></td><td class="component5-color"><a href="#dfn-mentionof" class="internalDFN"><span class="insert">MentionOf</span></a><span class="insert"> (</span><a href="#mention.bundle"><span class="insert">bundle</span></a><span class="insert">)</span></td><td class="component2-color"><a href="#dfn-wasderivedfrom" class="internalDFN"><span class="insert">WasDerivedFrom</span></a><span class="insert"> (</span><a href="#derivation.activity"><span class="insert">activity</span></a><span class="insert">)</span></td><td colspan="2"><span class="insert">—</span></td></tr>
+<tr><td><span class="insert">Activity</span></td><td class="component3-color"><a href="#dfn-wasassociatedwith" class="internalDFN"><span class="insert">WasAssociatedWith</span></a><span class="insert"> (</span><a href="#association.plan"><span class="insert">plan</span></a><span class="insert">)</span></td><td class="component1-color"><a href="#dfn-wasstartedby" class="internalDFN"><span class="insert">WasStartedBy</span></a><span class="insert"> (</span><a href="#start.starter"><span class="insert">starter</span></a><span class="insert">)</span><br><a href="#dfn-wasendedby" class="internalDFN"><span class="insert">WasEndedBy</span></a><span class="insert"> (</span><a href="#end.ender"><span class="insert">ender</span></a><span class="insert">)</span></td><td colspan="2"><span class="insert">—</span></td></tr>
+<tr><td><span class="insert">Agent</span></td><td><span class="insert">—</span></td><td class="component3-color"><a href="#dfn-actedonbehalfof" class="internalDFN"><span class="insert">ActedOnBehalfOf</span></a><span class="insert"> (</span><a href="#delegation.activity"><span class="insert">activity</span></a><span class="insert">)</span></td><td><span class="insert">—</span></td></tr>
</tbody></table>
</div>
@@ -2691,7 +2694,7 @@
<p>According to <a href="#section-prov-overview">Section 2</a>, for an entity to be transformed from, created from, or resulting from an update to another, there must be some
-underpinning activities performing the necessary actions resulting in such a derivation.
+underpinning <span class="insert">activity or </span>activities performing the necessary <span class="delete">actions</span><span class="insert">action(s)</span> resulting in such a derivation.
A derivation can be described at various levels of precision. In its simplest form, derivation relates two entities. Optionally, attributes can be added to represent further information about the derivation. If the derivation is the result of a single known activity, then this activity can also be optionally expressed. To provide a completely accurate description of the derivation, the generation and usage of the generated and used entities, respectively, can be provided, so as to make the derivation path, through usage, activity, and generation, explicit. Optional information such as activity, generation, and usage can be linked to derivations to aid analysis of provenance and to facilitate provenance-based reproducibility. </p>
@@ -2892,6 +2895,9 @@
<div class="glossary-ref"> An <dfn id="concept-agent" class="internalDFN">agent</dfn><sup><a class="internalDFN" href="#concept-agent"><span class="diamond"> ◊</span></a></sup> is something that bears some form of responsibility for an activity taking place, for the existence of an entity, or for another agent's activity. </div>
+<p><span class="insert">An agent may be a particular type of entity or activity. This means that the model can be
+ used to express provenance of the agents themselves. </span></p>
+
<p></p><div class="attributes" id="attributes-agent">An <dfn title="dfn-agent" id="dfn-agent" class="internalDFN">agent</dfn><sup><a class="internalDFN" href="#dfn-agent"><span class="diamond"> ◊</span></a></sup><span class="withPn">, written <span class="pnExpression" id="pn-agent">agent(id, [attr1=val1, ...])</span> in PROV-N,</span> has:
<ul>
@@ -3360,6 +3366,12 @@
</div>
+
+
+<p><span class="insert">Specialization is not defined as Influence, and therefore does not have an id and attributes.</span></p>
+
+
+
<div class="anexample" id="anexample-specialization"><div class="anexampleTitle">Example <span class="delete">42</span><span class="insert">43</span><sup><a class="internalDFN" href="#anexample-specialization"><span class="diamond"> ◊</span></a></sup></div>
<p>
The BBC news home page on 2012-03-23 <span class="name">ex:bbcNews2012-03-23</span>
@@ -3388,6 +3400,10 @@
+
+
+
+
<p></p><div class="attributes" id="attributes-alternate">An <dfn title="alternateOf" id="dfn-alternateof" class="internalDFN">alternate</dfn><sup><a class="internalDFN" href="#dfn-alternateof"><span class="diamond"> ◊</span></a></sup> relation<span class="withPn">, written <span class="pnExpression">alternateOf(e1, e2)</span> in PROV-N,</span> has:
<ul>
<li><span class="attribute" id="alternate.alternate1">alternate1</span>: an identifier (<span class="name">e1</span>) of the first of the two entities;</li>
@@ -3395,6 +3411,19 @@
</ul>
</div>
+<p><span class="insert">Alternate is not defined as Influence, and therefore does not have an id and attributes.</span></p>
+
+<p><span class="insert">
+Note that </span><a title="alternateOf" href="#dfn-alternateof" class="internalDFN"><span class="insert">alternateOf</span></a><span class="insert"> is a necessarily very general
+relationship that, in reasoning, only states that the two
+alternate entities fix different aspects of some common thing
+(possibly evolving over time), and so there is some relevant
+connection between the provenance of the alternates. In a
+specific application context, </span><a title="alternateOf" href="#dfn-alternateof" class="internalDFN"><span class="insert">alternateOf</span></a><span class="insert">, or a subtype of it,
+could allow more inferences.
+</span></p>
+
+
<div class="anexample" id="anexample-alternate"><div class="anexampleTitle">Example <span class="delete">43</span><span class="insert">44</span><sup><a class="internalDFN" href="#anexample-alternate"><span class="diamond"> ◊</span></a></sup></div>
<p>
A given news item on the BBC News site
@@ -3464,6 +3493,11 @@
+
+
+
+
+
<p></p><div class="attributes" id="attributes-mention">A <dfn title="mentionOf" id="dfn-mentionof" class="internalDFN">mention</dfn><sup><a class="internalDFN" href="#dfn-mentionof"><span class="diamond"> ◊</span></a></sup> relation<span class="withPn">, written <span class="pnExpression">mentionOf(infra, supra, b)</span> in PROV-N,</span> has:
<ul>
<li><span class="attribute" id="mention.specificEntity">specificEntity</span>: an identifier (<span class="name">infra</span>)
@@ -3473,6 +3507,8 @@
</ul>
</div>
+<p><span class="insert">Mention is not defined as Influence, and therefore does not have an id and attributes.</span></p>
+
<div class="anexample" id="anexample-mention-rating"><div class="anexampleTitle">Example <span class="delete">45</span><span class="insert">46</span><sup><a class="internalDFN" href="#anexample-mention-rating"><span class="diamond"> ◊</span></a></sup></div>
<p>This example is concerned with a performance rating tool that reads and processes provenance to determine the performance of agents. To keep the example simple, an agent's performance is determined by the duration of the activities it is associated with. </p>
<p>As an illustration, we consider that two bundles <span class="name">ex:run1</span> and <span class="name">ex:run2</span> refer to an agent <span class="name">ex:Bob</span> that controlled two activities <span class="name">ex:a1</span> and <span class="name">ex:a2</span>. </p>
@@ -3575,7 +3611,7 @@
<div id="term-collection" class="section">
<h4><span class="secno">5.6.1 </span>Collection</h4>
-<span class="glossary-ref"> A <dfn id="concept-collection" class="internalDFN">collection</dfn><sup><a class="internalDFN" href="#concept-collection"><span class="diamond"> ◊</span></a></sup> is an entity that provides a structure to some constituents, which are themselves entities. These constituents are said to be <dfn id="dfn-member-of" class="internalDFN">member of</dfn><sup><a class="internalDFN" href="#dfn-member-of"><span class="diamond"> ◊</span></a></sup> the collections. </span>
+<span class="glossary-ref"> A <dfn id="concept-collection" class="internalDFN">collection</dfn><sup><a class="internalDFN" href="#concept-collection"><span class="diamond"> ◊</span></a></sup> is an entity that provides a structure to some <span class="delete">constituents, which are</span><span class="insert">constituents that must</span> themselves<span class="insert"> be</span> entities. These constituents are said to be <dfn id="dfn-member-of" class="internalDFN">member of</dfn><sup><a class="internalDFN" href="#dfn-member-of"><span class="diamond"> ◊</span></a></sup> the collections. </span>
<span class="glossary-ref"> An <dfn id="concept-empty-collection" class="internalDFN">empty collection</dfn><sup><a class="internalDFN" href="#concept-empty-collection"><span class="diamond"> ◊</span></a></sup> is a collection without members. </span>
@@ -3620,6 +3656,12 @@
+
+
+
+<p><span class="insert">Membership is not defined as Influence, and therefore does not have an id and attributes.</span></p>
+
+
<div class="anexample" id="example_49"><div class="anexampleTitle">Example <span class="delete">48</span><span class="insert">49</span><sup><a class="internalDFN" href="#example_49"><span class="diamond"> ◊</span></a></sup></div>
<p>In this example, <span class="name">c</span> is a collection known to have <span class="name">e0</span>, <span class="name">e1</span>, and <span class="name">e2</span> as members, and may have other members.</p>
<pre class="codeexample">entity(e0)
@@ -4307,6 +4349,16 @@
</span></li><li> <a href="http://www.w3.org/2011/prov/track/issues/499"><span class="insert">ISSUE-499</span></a><span class="insert">: Made explicit that generation/usage/invalidation/start/end are implicit.
</span></li><li> <a href="http://www.w3.org/2011/prov/track/issues/449"><span class="insert">ISSUE-449</span></a><span class="insert">: Clarified definition of prov:value attribute and added an example.
</span></li><li> <a href="http://www.w3.org/2011/prov/track/issues/495"><span class="insert">ISSUE-495</span></a><span class="insert">: added paragraph about 'relations opening up'. Clarified the role of '-' in example. Fixed dates in biblio. Fixed space issue in prov-n examples
+</span></li><li> <a href="http://www.w3.org/2011/prov/track/issues/516"><span class="insert">ISSUE-516</span></a><span class="insert">: Stating that there moust be some underpinning activity or activities for a derivation, instead of just activities.
+</span></li><li> <a href="http://www.w3.org/2011/prov/track/issues/525"><span class="insert">ISSUE-525</span></a><span class="insert">: Made it explicit that Membership, Alternate, Specialization are not Influence
+</span></li><li><span class="insert"> Copied the sentence " An agent may be a particular type of entity or activity. This means that the model can be
+ used to express provenance of the agents themselves. " from the informative section into the normative section.
+</span></li><li> <a href="http://www.w3.org/2011/prov/track/issues/504"><span class="insert">ISSUE-504</span></a><span class="insert">: Updated definition of collection.
+</span></li><li> <a href="http://www.w3.org/2011/prov/track/issues/503"><span class="insert">ISSUE-503</span></a><span class="insert">: Rephrased the introduction of expanded association in section 2.2.1.2 Expanded Relations.
+</span></li><li> <a href="http://www.w3.org/2011/prov/track/issues/514"><span class="insert">ISSUE-514</span></a><span class="insert">: added links to the attributes listed in the secondary element table. Also removed PrimarySource, Quotation, Revision.
+</span></li><li> <a href="http://www.w3.org/2011/prov/track/issues/502"><span class="insert">ISSUE-502</span></a><span class="insert">: Added sentence in section 2.1.2 explaining that the focus
+ of derivation is on connecting a generated entity to a used entity.
+</span></li><li> <a href="http://www.w3.org/2011/prov/track/issues/526"><span class="insert">ISSUE-526</span></a><span class="insert">: Added sentence clarifying sentence in section 5.5.2.
</span></li></ul>
</div>