--- a/model/working-copy/towards-wd4.html Mon Feb 13 09:01:58 2012 +0000
+++ b/model/working-copy/towards-wd4.html Mon Feb 13 09:47:17 2012 +0000
@@ -63,6 +63,12 @@
"2011, Working Draft. "+
"URL: <a href=\"http://www.w3.org/TR/prov-dm-constraints/\">http://www.w3.org/TR/prov-dm-constraints/</a>",
+ "PROV-ASN":
+ "Luc Moreau and Paolo Missier (eds.) ... "+
+ "<a href=\"http://www.w3.org/TR/prov-asn/\"><cite>PROV-ASN ....</cite></a>. "+
+ "2011, Working Draft. "+
+ "URL: <a href=\"http://www.w3.org/TR/prov-asn/\">http://www.w3.org/TR/prov-asn/</a>",
+
"PROV-AQ":
"Graham Klyne and Paul Groth (eds.) Luc Moreau, Olaf Hartig, Yogesh Simmhan, James Meyers, Timothy Lebo, Khalid Belhajjame, and Simon Miles "+
"<a href=\"http://www.w3.org/TR/prov-aq/\"><cite>Provenance Access and Query</cite></a>. "+
@@ -372,7 +378,7 @@
publication of a new version of a document.</p>
-<p>Usage examples include a procedure beginning to consume a parameter, a service starting to read a value on a port, a program beginning to read a configuration
+<p>Usage examples include a procedure beginning to consume an argument, a service starting to read a value on a port, a program beginning to read a configuration
file, or the point at which an ingredient, such as eggs, is being added in a baking activity. Usage may entirely consume an entity (e.g. eggs are no longer available after being added to
the mix); alternatively, a same entity may be used multiple times, possibly by different activities (e.g. a file on a file system can be read indefinitely).</p>
@@ -405,7 +411,7 @@
<div class="anexample" id="plan-example">
<p>
-A plan can be a blog post tutorial for how to set up a web server, a list of instructions for a micro-processor execution, a cook's written recipe for chocolate cake, or a workflow for a scientific experiment.
+A plan can be a blog post tutorial for how to set up a web server, a list of instructions for a micro-processor execution, a cook's written recipe for a chocolate cake, or a workflow for a scientific experiment.
</p>
</div>
@@ -424,8 +430,8 @@
<p>
Having found a resource, a user may want to retrieve its
provenance. For users to decide whether they can place their trust in
-that resource, they may to analyse its provenance, but also determine
-who this provenance is attributed to, and when it was
+that resource, they may want to analyse its provenance, but also determine
+who the provenance is attributed to, and when it was
generated. Hence, from the PROV-DM data model, the provenance is
regarded as an entity, an AccountEntity, for which provenance can be
sought.
@@ -433,7 +439,7 @@
</div>
-<p>Three types of agents are recognized by PROV-DM because they are commonly encountered in application making data and documents available on the Web: persons, software agents, and organizations.</p>
+<p>Three types of agents are recognized by PROV-DM because they are commonly encountered in applications making data and documents available on the Web: persons, software agents, and organizations.</p>
<div class="anexample" id="software-agents-example">
<p> Even software agents can be assigned some responsibility for the effects they have in the world, so for example if one is using a Text Editor and one's laptop crashes, then one would say
@@ -466,22 +472,28 @@
cases, those activities reflect the execution of a plan that was
designed in advance to guide the execution. PROV-DM allows attaching
a plan to an activity, which represents what was intended to
-happen. The plan can be useful for various tasks, for example to
+happen. Representing the plan explicitly in the provenance can be useful for various tasks: for example, to
validate the execution as represented in the provenance record, to
manage expectation failures, or to provide explanations.</p>
-<p>An <dfn title="concept-activityAssociation">activity association</dfn> is a relation between an activity and an agent, indicating that the agent had an active role in the activity. It further allow an activity to be associated with a plan, which a set of
-actions or steps intended by the agent to achieve some goals in the context of this activity.</p>
+<p>An <dfn title="concept-activityAssociation">activity association</dfn> is an assignment of responsibility to an agent for an activity, indicating that the agent had an active role in the activity. It further allows for a plan to be specified, which is the plan
+intended by the agent to achieve some goals in the context of this activity.</p>
<div class="anexample" id="association-example">
-<p>Examples of association between an activity and agent include designing, participation, initiation and termination, timetabling or sponsoring. </p>
+<p>Examples of association between an activity and agent are:
+<ul>
+<li>creation of a web page under the guidance of a designer;</li>
+<li>various forms of participation in a panel discussion, including audience member, panelist, or panel chair;</li>
+<li>a public event, sponsored by a company, and hosted by a museum;</li>
+<li>an XSLT transform initiated by a user;</li>
+</ul>
</div>
-<p>An <dfn title="concept-responsibilityChain">responsibility chain</dfn> is a relation between two agents,
-indicating that a "subordinate" agent acted on behalf of a "responsible" agent, in the context of an activity.</p>
+<p>A <dfn title="concept-responsibilityChain">responsibility chain</dfn> is a relation between two agents,
+indicating that a "subordinate" agent acted on behalf of a "responsible" agent, in the context of an activity. The nature of this relation is intended to be broad, and includes delegation, contractual relation</p>
@@ -578,7 +590,7 @@
</pre>
</li>
-<li>The activity was associated with the Consortium agent, and proceeded according to the publication policy
+<li>The activity was associated with the Consortium agent, and proceeded according to its publication policy
<pre>
wasAssociatedWith(ex:pub2, w3:Consortium @ pr:rec-advance)
</pre>
@@ -592,7 +604,7 @@
<p>The graphical illustration takes the form of a graph. Entities, activities and agents are represented as nodes, with oval, rectangular, and octogonal shapes, respectively. Usage,
Generation, Derivation, and Activity Association are represented as directed edges.</p>
-<p>Entities are layed out according to the ordering of their generation event. We endeavor to show time progressing from top to bottom This means that edges for Usage, Generation and
+<p>Entities are layed out according to the ordering of their generation event. We endeavor to show time progressing from top to bottom. This means that edges for Usage, Generation and
Derivation typically point upwards.</p>
@@ -612,11 +624,7 @@
</div>
-<p> This simple example has shown a variety of PROV-DM constructs, such as Entity, Agent, Activity, Usage, Generation, Derivation, and ActivityAssociation. In this example, it happens that all entities were already Web resources, with readily available URIs, which we used. We note that some of the resources are public, whereas others have restricted access: provenance statements only make use of their identifiers. When identifiers do not pre-exist, e.g. for activities, then they can be minted, for instance <span class="name">ex:pub2</span>, occuring in the namespace identified by prefix <span class="name">ex</span>.</p>
-
-<div class='note'>
-Need to say something about this example, where all urls are well behaved.
-</div>
+<p> This simple example has shown a variety of PROV-DM constructs, such as Entity, Agent, Activity, Usage, Generation, Derivation, and ActivityAssociation. In this example, it happens that all entities were already Web resources, with readily available URIs, which we used. We note that some of the resources are public, whereas others have restricted access: provenance statements only make use of their identifiers. If identifiers do not pre-exist, e.g. for activities, then they can be minted, for instance <span class="name">ex:pub2</span>, occuring in the namespace identified by prefix <span class="name">ex</span>. We note that the URI scheme developed by W3C is particularly suited for expressing provenance of these reports, since each URI denotes a specific version of a report. It then becomes very easy to relate the various versions, with PROV-DM constructs. </p>
</section>
@@ -643,7 +651,7 @@
</pre>
<p>While this description is about the same report <span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111215">tr:WD-prov-dm-20111215</a></span>, its details differ from the author's perspective: it is a document and it has a version number. </p></li>
-<li>There is a editing activity.
+<li>There is an editing activity.
<pre>
activity(ex:edit1,,,[prov:type="edit"])
</pre>
@@ -663,7 +671,7 @@
</pre>
</li>
-<li>The activity required a publication request: this is a <a title="concept-usage">Usage</a>.
+<li>Agents were assigned various responsibilities in the editing activity: contributor and editor.
<pre>
wasAssociatedWith(ex:edit1, ex:Paolo, [prov:role="editor"])
wasAssociatedWith(ex:edit1, ex:Simon, [prov:role="contributor"])