--- a/model/prov-dm.html Mon Apr 16 09:01:20 2012 -0400
+++ b/model/prov-dm.html Mon Apr 16 09:01:46 2012 -0400
@@ -400,7 +400,7 @@
examples. Since PROV-DM is a conceptual data
model, Section 2.5 maps the concepts to various types and relations,
which are illustrated graphically in
-a <a href="#prov-dm-overview">simplified UML diagram</a>. Section 2.6
+a simplified UML diagram in <a href="#prov-dm-overview">Figure 1</a>. Section 2.6
then summarizes the PROV notation allowing instances of PROV-DM to be
written down.
</p>
@@ -743,48 +743,41 @@
<section id="prov-dm-example">
<h2>Illustration of PROV-DM by an Example</h2>
-<p>Section <a href="#starting-points">starting-points</a> has introduced some provenance concepts, and how they are expressed as types or relations in the PROV data model. The purpose of this section is to put these concepts into practice in order to express the provenance of some document published on the Web.
+<p><a href="#starting-points">Section 2</a> has introduced some provenance concepts, and how they are expressed as types or relations in the PROV data model. The purpose of this section is to put these concepts into practice in order to express the provenance of some document published on the Web.
With this realistic example, PROV concepts are composed together, and a graphical illustration shows a provenance description forming a directed graph, rooted at the entity we want to explain the provenance of, and pointing to the entities, activities, and agents it depended on. This example also shows that, sometimes, multiple provenance descriptions about the same entity can co-exist, which then justifies the need for provenance of provenance.</p>
-<p>The World Wide Web Consortium publishes many technical reports. In this example, we consider a technical report, and describe its provenance.
-Specifically, we consider the second version of the PROV-DM document
-<a href="http://www.w3.org/TR/2011/WD-prov-dm-20111215">http://www.w3.org/TR/2011/WD-prov-dm-20111215</a>. Its provenance can be expressed from several perspectives: first, provenance takes the authors' viewpoint; second, it is concerned with the W3C process. Then, attribution of these two provenance descriptions is provided.</p>
-
-
-<section id="section-example-b">
+<p>In this example, we consider one of the many documents published by the World Wide Web Consortium, and describe its provenance.
+Specifically, we consider the document identified by
+<a href="http://www.w3.org/TR/2011/WD-prov-dm-20111215">http://www.w3.org/TR/2011/WD-prov-dm-20111215</a>. Its provenance can be expressed from several perspectives: first, provenance can take the authors' viewpoint; second, it can be concerned with the W3C process. Then, attribution of these two provenance descriptions is provided.</p>
+
+
+<section id="section-example-one">
<h3>The Authors View</h3>
-<p style="font-style:italic; " ><b>Description:</b> A technical report
+<p style="font-style:italic; " ><b>Description:</b> A document
is edited by some editor, using contributions from various
contributors.
</p>
-<p>In this perspective, provenance of the technical report
-<a href="http://www.w3.org/TR/2011/WD-prov-dm-20111215">http://www.w3.org/TR/2011/WD-prov-dm-20111215</a> is concerned with the document editing activity, as perceived by authors. This kind of information could be used by authors in their CV or in a narrative about this document. </p>
-
-
-
-
-<ul>
-<li> A technical report was involved: <span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111215">tr:WD-prov-dm-20111215</a></span>;</li>
-<li> An editing activity for <span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111215">tr:WD-prov-dm-20111215</a></span> was <span class="name">ex:edit1</span>;</li>
-<li> The report <span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111215">tr:WD-prov-dm-20111215</a></span> was generated by activity <span class="name">ex:edit1</span>;</li>
-<li> Several persons were associated with activity <span class="name">ex:edit1</span>, some in an editorial role, some in a contributor's role.</li>
-</ul>
-
-<p>We paraphrase some PROV-DM descriptions, and illustrate them with the PROV-N notation.
+<p>In this perspective, provenance of the document
+<a href="http://www.w3.org/TR/2011/WD-prov-dm-20111215">http://www.w3.org/TR/2011/WD-prov-dm-20111215</a> is concerned with the editing activity as perceived by authors. This kind of information could be used by authors in their CV or in a narrative about this document. </p>
+
+
+
+
+<p>We paraphrase some PROV-DM descriptions, express them with the PROV-N notation, and then depict them with a graphical illustration (see <a href="#prov-a-document1">Figure 1</a>).
Full details of the provenance record can be found <a href="examples/w3c-publication3.pn">here</a>.</p>
<ul>
-<li>There was a technical report, which from the author's perspective was a document in its second version.
+<li>There was a document <span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111215">tr:WD-prov-dm-20111215</a></span>, which from the author's perspective was a document in its second version.
<pre>
entity(tr:WD-prov-dm-20111215, [ prov:type="document", ex:version="2" ])
</pre>
-<p>This description is about the report <span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111215">tr:WD-prov-dm-20111215</a></span>. From the author's perspective, the description states: it was a document and it had a version number. </p></li>
+</li>
<li>There was an editing activity.
<pre>
@@ -792,7 +785,7 @@
</pre>
</li>
-<li>The technical report was generated by the editing activity: this was a <a title="concept-generation">Generation</a>.
+<li>The document was generated by the editing activity: this was a <a title="concept-generation">Generation</a>.
<pre>
wasGeneratedBy(tr:WD-prov-dm-20111215, ex:edit1, -)
</pre>
@@ -814,53 +807,62 @@
</li>
</ul>
+<p>
+Provenance descriptions can be <em>illustrated</em> graphically. The illustration is not intended to represent all the details of the model, but it is intended to show the essence of a set of
+provenance descriptions. Therefore, it should not be seen as an alternate notation for expressing provenance.</p>
+
+<p>The graphical illustration takes the form of a graph. Entities, activities and agents are represented as nodes, with oval, rectangular, and pentagonal shapes, respectively. Usage,
+Generation, Derivation, and Association are represented as directed edges.</p>
+
+<p>Entities are laid out according to the ordering of their generation. We endeavor to show time progressing from left to right. This means that edges for Usage, Generation,
+Derivation, Association typically point leftwards</p>
<div style="text-align: center; ">
<figure>
- <img src="images/w3-publication3.png" alt="Provenance of a Tech Report (b)" style="max-width: 98%; "/>
-<figcaption id="prov-tech-report">Figure 3: Provenance of a Tech Report (b)</figcaption>
+ <img src="images/w3-publication3.png" alt="Provenance of a Document (1)" style="max-width: 98%; "/>
+<figcaption id="prov-a-document1">Figure 2: Provenance of a Document (1)</figcaption>
</figure>
</div>
</section>
-<section id="section-example-a">
+<section id="section-example-two">
<h3>The Process View</h3>
<p style="font-style:italic; " ><b>Description:</b> The World Wide Web
-Consortium publishes technical reports according to its publication
+Consortium publishes documents according to its publication
policy. Working drafts are published regularly to reflect the work
accomplished by working groups. Every publication of a working draft
must be preceded by a "publication request" to the Webmaster. The
-very first version of a technical report must also be preceded by a
+very first version of a document must also be preceded by a
"transition request" to be approved by the W3C director. All working
-drafts are made available at a unique URI. In this scenario, we consider two successive versions of a given report, the policy according to which they were published, and the associated requests.
+drafts are made available at a unique URI. In this scenario, we consider two successive versions of a given document, the policy according to which they were published, and the associated requests.
</p>
<p>
We describe the kind of provenance record that the <a href="http://www.w3.org/Consortium">WWW Consortium</a> could keep for auditors to check that due processes are followed. All entities involved in this example are Web resources, with well defined URIs (some of which refer archived email messages, available to W3C Members).</p>
<ul>
-<li> Two versions of the technical report were involved: <span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111215">tr:WD-prov-dm-20111215</a></span> (second working draft) and <span class="name"><span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018">tr:WD-prov-dm-20111018</a></span></span> (first working draft);</li>
+<li> Two versions of a document were involved: <span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111215">tr:WD-prov-dm-20111215</a></span> (second working draft) and <span class="name"><span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018">tr:WD-prov-dm-20111018</a></span></span> (first working draft);</li>
<li> Both <span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111215">tr:WD-prov-dm-20111215</a></span> and <span class="name"><span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018">tr:WD-prov-dm-20111018</a></span></span> were published by the WWW Consortium (<span class="name"><a href="http://www.w3.org/Consortium">w3:Consortium</a></span>); </li>
<li> The publication activity for <span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111215">tr:WD-prov-dm-20111215</a></span> was <span class="name">ex:act2</span>;</li>
<li> The publication activity for <span class="name"><span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018">tr:WD-prov-dm-20111018</a></span></span> was <span class="name">ex:act1</span>;
</li>
-<li> The report <span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111215">tr:WD-prov-dm-20111215</a></span> was derived from <span class="name"><span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018">tr:WD-prov-dm-20111018</a></span></span>;</li>
+<li> The document <span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111215">tr:WD-prov-dm-20111215</a></span> was derived from <span class="name"><span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018">tr:WD-prov-dm-20111018</a></span></span>;</li>
<li> The publication activity <span class="name">ex:act1</span> used a <a href="http://www.w3.org/2005/08/01-transitions.html#pubreq">publication request</a> (<span class="name"><a href="https://lists.w3.org/Archives/Member/w3c-archive/2011Oct/0141">email:2011Oct/0141</a></span>) and a <a href="http://www.w3.org/2005/08/01-transitions.html#transreq">transition request</a> (<span class="name"><a href="https://lists.w3.org/Archives/Member/chairs/2011OctDec/0004">chairs:2011OctDec/0004</a></span>);</li>
<li> The publication activity <span class="name">ex:act2</span> used a <a href="http://www.w3.org/2005/08/01-transitions.html#pubreq">publication request</a> (<span class="name"><a href="https://lists.w3.org/Archives/Member/w3c-archive/2011Dec/0111">email:2011Dec/0111</a></span>);</li>
-<li> Technical reports were published according to the process rules (<span class="name"><a href="http://www.w3.org/2005/10/Process-20051014/tr.html#rec-advance">process:rec-advance</a></span>), a plan in PROV-DM terminology.</li>
+<li> Documents were published according to the process rules (<span class="name"><a href="http://www.w3.org/2005/10/Process-20051014/tr.html#rec-advance">process:rec-advance</a></span>), a plan in PROV-DM terminology.</li>
</ul>
<p>
-We now paraphrase some PROV descriptions, and illustrate them with the PROV-N notation. We then follow them with a graphical illustration. Full details of the provenance record can be found <a href="examples/w3c-publication1.pn">here</a>.
+We now paraphrase some PROV descriptions, and express them with the PROV-N notation, and then depict them with a graphical illustration (see <a href="#prov-a-document2">Figure 2</a>). Full details of the provenance record can be found <a href="examples/w3c-publication1.pn">here</a>.
<ul>
-<li>There was a technical report, a working draft on the recommendation track (<a href="http://www.w3.org/2005/10/Process-20051014/tr.html#RecsWD">process:RecsWD</a>), which is an entity so that we can describe its provenance. Similar descriptions exist for all entities.
+<li>There was a document, a working draft on the recommendation track (<a href="http://www.w3.org/2005/10/Process-20051014/tr.html#RecsWD">process:RecsWD</a>), which is an entity so that we can describe its provenance. Similar descriptions exist for all entities.
<pre>
entity(tr:WD-prov-dm-20111215, [ prov:type="process:RecsWD" %% xsd:QName ])
</pre>
@@ -871,20 +873,20 @@
</pre>
</li>
-<li>The technical report was generated by the publication activity: this is a <a title="concept-Generation">Generation</a>.
+<li>The document was generated by the publication activity: this was a <a title="concept-Generation">Generation</a>.
<pre>
wasGeneratedBy(tr:WD-prov-dm-20111215, ex:act2, -)
</pre>
</li>
-<li>The second draft of the technical report was derived from the first draft of the technical report: this is a <a title="concept-Derivation">Derivation</a>.
+<li>The second draft of the document was derived from the first draft: this was a <a title="concept-Derivation">Derivation</a>.
<pre>
wasDerivedFrom(tr:WD-prov-dm-20111215, tr:WD-prov-dm-20111018)
</pre>
</li>
-<li>The activity required a publication request: this is a <a title="concept-Usage">Usage</a>.
+<li>The activity required a publication request: this was a <a title="concept-Usage">Usage</a>.
<pre>
used(ex:act2, email:2011Dec/0111, -)
</pre>
@@ -897,15 +899,6 @@
</li>
</ul>
-<p>
-Provenance descriptions can be <em>illustrated</em> graphically. The illustration is not intended to represent all the details of the model, but it is intended to show the essence of a set of
-provenance descriptions. Therefore, it should not be seen as an alternate notation for expressing provenance.</p>
-
-<p>The graphical illustration takes the form of a graph. Entities, activities and agents are represented as nodes, with oval, rectangular, and pentagonal shapes, respectively. Usage,
-Generation, Derivation, and Association are represented as directed edges.</p>
-
-<p>Entities are laid out according to the ordering of their generation. We endeavor to show time progressing from left to right. This means that edges for Usage, Generation,
-Derivation, Association typically point leftwards</p>
@@ -914,13 +907,13 @@
<div style="text-align: center;">
<figure>
- <img src="images/w3-publication1.png" alt="Provenance of a Tech Report" style="max-width: 90%; "/>
-<figcaption>Figure 2: Provenance of a Tech Report</figcaption>
+ <img src="images/w3-publication1.png" alt="Provenance of a Document (2)" style="max-width: 90%; "/>
+<figcaption id="prov-a-document2">Figure 3: Provenance of a Document (2)</figcaption>
</figure>
</div>
-<p> This simple example has shown a variety of PROV concepts, such as Entity, Agent, Activity, Usage, Generation, Derivation, and Association. 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 generated, for instance <span class="name">ex:act2</span>, occurring 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 easy to relate the various versions with PROV-DM relations. We note that an Association is a ternary relation (represented by a multi-edge labeled wasAssociatedWith) from an activity to an agent and a plan.</p>
+<p> This simple example has shown a variety of PROV concepts, such as Entity, Agent, Activity, Usage, Generation, Derivation, and Association. 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 generated, for instance <span class="name">ex:act2</span>, occurring 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 documents, since each URI denotes a specific version of a document. It then becomes easy to relate the various versions with PROV-DM relations. We note that an Association is a ternary relation (represented by a multi-edge labeled wasAssociatedWith) from an activity to an agent and a plan.</p>
</section>
@@ -929,7 +922,7 @@
<section id="section-example-c">
<h3>Attribution of Provenance</h3>
-<p>The two previous sections provide two different perspectives on the provenance of a technical report. By design, the PROV approach allows for the provenance of a subject to be provided by multiple sources. For users to decide whether they can place their trust in the technical report, they may want to analyze its provenance, but also determine
+<p>The two previous sections provide two different perspectives on the provenance of a document By design, the PROV approach allows for the provenance of a subject to be provided by multiple sources. For users to decide whether they can place their trust in the document, they may want to analyze its provenance, but also determine
who the provenance is attributed to, and when it was
generated, etc. In other words, we need to be able to express the provenance of provenance.</p>
@@ -1457,7 +1450,7 @@
<div class="anexample">
<p>
-Revisiting the example of <a href="#section-example-b">Section 3.2</a>,
+Revisiting the example of <a href="#section-example-one">Section 3.1</a>,
we can ascribe <span class="name">tr:WD-prov-dm-20111215</span> to some agents without an explicit activity. The reserved attribute <span class="name">role</span> (see <a href="#term-attribute-role">Section 4.7.4.3</a>) allows for role of the agent in the attribution to be specified.
<pre class="codeexample">
agent(ex:Paolo, [ prov:type="Person" ])
@@ -1675,7 +1668,7 @@
<div class="anexample" id="anexample-revision">
<p>
-Revisiting the example of <a href="#section-example-a">Section 3.1</a>,
+Revisiting the example of <a href="#section-example-two">Section 3.2</a>,
we can now state that the report
<span class="name">tr:WD-prov-dm-20111215</span> is a revision of
the report <span class="name">tr:WD-prov-dm-20111018</span>, approved by
@@ -1796,7 +1789,7 @@
</p>
<div class="anexample">
-<p>We refer to the example of <a href="#section-example-a">Section 3.1</a>, and specifically to <a href="#prov-tech-report">Figure 3</a>. We can see that there is a path from
+<p>We refer to the example of <a href="#section-example-two">Section 3.1</a>, and specifically to <a href="#prov-a-document">Figure 2</a>. We can see that there is a path from
<span class="name">tr:WD-prov-dm-20111215</span> to
<span class="name">w3:Consortium</span> and to
<span class="name">process:rec-advance</span>. This is expressed as follows.