--- a/model/examples/w3c-publication1.pn Fri May 25 08:07:53 2012 +0100
+++ b/model/examples/w3c-publication1.pn Fri May 25 08:48:19 2012 +0100
@@ -1,6 +1,6 @@
-container
+bundle ex:process-view
prefix ex <http://example.org/>
@@ -10,11 +10,11 @@
prefix email <https://lists.w3.org/Archives/Member/w3c-archive/>
prefix chairs <https://lists.w3.org/Archives/Member/chairs/>
prefix trans <http://www.w3.org/2005/08/01-transitions.html#>
+prefix rec54 <http://www.w3.org/2001/02pd/rec54#>
-
- entity(tr:WD-prov-dm-20111018, [ prov:type='process:RecsWD' ])
- entity(tr:WD-prov-dm-20111215, [ prov:type='process:RecsWD' ])
+ entity(tr:WD-prov-dm-20111018, [ prov:type='rec54:WD' ])
+ entity(tr:WD-prov-dm-20111215, [ prov:type='rec54:WD' ])
entity(process:rec-advance, [ prov:type='prov:Plan' ])
@@ -32,14 +32,13 @@
wasGeneratedBy(tr:WD-prov-dm-20111018, ex:act1, -)
wasGeneratedBy(tr:WD-prov-dm-20111215, ex:act2, -)
- used(ex:act1,chairs:2011OctDec/0004,-)
- used(ex:act1,email:2011Oct/0141,-)
- used(ex:act2,email:2011Dec/0111,-)
+ used(ex:act1, chairs:2011OctDec/0004, -)
+ used(ex:act1, email:2011Oct/0141, -)
+ used(ex:act2, email:2011Dec/0111, -)
agent(w3:Consortium, [ prov:type='prov:Organization' ])
wasAssociatedWith(ex:act1, w3:Consortium, process:rec-advance)
wasAssociatedWith(ex:act2, w3:Consortium, process:rec-advance)
-endContainer
-
+endBundle
--- a/model/examples/w3c-publication3.pn Fri May 25 08:07:53 2012 +0100
+++ b/model/examples/w3c-publication3.pn Fri May 25 08:48:19 2012 +0100
@@ -1,6 +1,6 @@
-container
+bundle ex:author-view
prefix ex <http://example.org/>
prefix w3 <http://www.w3.org/>
@@ -38,4 +38,4 @@
wasAssociatedWith(ex:edit1, ex:James, -, [prov:role="contributor"])
wasAssociatedWith(ex:edit1, ex:Satya, -, [prov:role="contributor"])
-endContainer
+endBundle
--- a/model/prov-dm.html Fri May 25 08:07:53 2012 +0100
+++ b/model/prov-dm.html Fri May 25 08:48:19 2012 +0100
@@ -1101,7 +1101,7 @@
<div style="text-align: center;">
- <figure>
+ <figure id="prov-a-document2-top">
<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>
@@ -1120,7 +1120,7 @@
<p>The two previous sections offer two different perspectives on the provenance of a document. PROV allows for multiple sources to provide the provenance of a subject. 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>
-<p>PROV-DM offers a construct to name a bundle of provenance descriptions. </p>
+<p>PROV-DM offers a construct to name a bundle of provenance descriptions (full details: <a href="examples/w3c-publication3.pn">ex:author-view</a>). </p>
<pre class="codeexample">
bundle ex:author-view
@@ -1134,7 +1134,7 @@
endBundle
</pre>
-Likewise, the process view can be expressed as a separate named bundle.
+Likewise, the process view can be expressed as a separate named bundle (full details: <a href="examples/w3c-publication1.pn">ex:process-view</a>).
<pre class="codeexample">
bundle ex:process-view
@@ -1155,11 +1155,6 @@
wasAttributedTo(ex:process-view, w3:Consortium)
</pre>
-<div class="note">
-<p>TODO: full details of bundles can be found at <a href="examples/w3c-publication1.pn">ex:process-view</a> and <a href="examples/w3c-publication3.pn">ex:author-view</a>.</p>
-</div>
-
-
</section>
</section>
@@ -1930,8 +1925,12 @@
-<p>The third component of PROV-DM is concerned with <a title="derivation">derivations</a> of <a title="entity">entities</a> from others, and derivation subtypes <a>Revision</a>, <a>Quotation</a>, <a>Original Source</a>, and <a>Trace</a>.
- <a href="#figure-component3">Figure 7</a> depicts the third component with three classes (Entity, Activity, and Agent) and associations between them. As before, the yellow are includes PROV core structures, whereas extended structures are found outside this area. UML association classes express expanded n-ary relations.
+<p>The third component of PROV-DM is concerned with: <a title="derivation">derivations</a> of <a title="entity">entities</a> from others; derivation subtypes <a>Revision</a>, <a>Quotation</a>, and <a>Original Source</a>; derivation-related <a>Trace</a>.
+ <a href="#figure-component3">Figure 7</a> depicts the third component
+with PROV core structures in the yellow area, including two classes
+(<a>Entity</a>, <a>Activity</a>) and binary association
+(<a>Derivation</a>). PROV extended structures are found outside this
+area. UML association classes express expanded n-ary relations.
</p>
@@ -1957,7 +1956,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.
-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. 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>
+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>
<p><div class="attributes" id="attributes-derivation">A <dfn title="wasDerivedFrom">derivation</dfn><span class="withPn">, written <span class="pnExpression" id="pn-wasDerivedFrom">wasDerivedFrom(id; e2, e1, a, g2, u1, attrs)</span> in PROV-N,</span> has:
@@ -2042,6 +2041,10 @@
<span class="glossary-ref" data-ref="glossary-quotation"></span>
</p>
+<p>Quotation
+ is a particular case of <a>derivation</a> in which an entity is derived from an original entity by copying, or "quoting", some or all of it.</p>
+
+
<!--
<p>Quotation
is a particular case of <a>derivation</a> in which entity <span class="name">e2</span> is derived from an original entity <span class="name">e1</span> by copying, or "quoting", some or all of it.
@@ -2065,9 +2068,10 @@
"During the workshop, it became clear to me that the consensus based models (which are often graphical in nature) can not only be formalized but also be directly connected to these database focused formalizations. I just needed to get over the differences in syntax. This could imply that we could have nice way to trace provenance across systems and through databases and be able to understand the mathematical properties of this interconnection."</em>
</blockquote>
<p>If <a href="http://thinklinks.wordpress.com/2012/03/07/thoughts-from-the-dagstuhl-principles-of-provenance-workshop/"><span class="name">wp:thoughts-from-the-dagstuhl-principles-of-provenance-workshop/</span></a> denotes the original blog by agent <span class="name">ex:Paul</span>, and
- <a href="#bl-dagstuhl"><span class="name">dm:bl-dagstuhl</span></a> denotes the above paragraph, then the following descriptions express that the above paragraph is copied by agent <span class="name">ex:Luc</span> from a part of the blog, attributed to the agent <span class="name">ex:Paul</span>.</p>
+ <a href="#bl-dagstuhl"><span class="name">dm:bl-dagstuhl</span></a> denotes the above paragraph, then the following descriptions express that the above paragraph was copied by agent <span class="name">ex:Luc</span> from a part of the blog, attributed to the agent <span class="name">ex:Paul</span>.</p>
<pre class="codeexample">
entity(wp:thoughts-from-the-dagstuhl-principles-of-provenance-workshop/)
+entity(dm:bl-dagstuhl)
agent(ex:Luc)
agent(ex:Paul)
wasDerivedFrom(dm:bl-dagstuhl,
@@ -2116,7 +2120,7 @@
<pre class="codeexample">
entity(dm:concept-original-source)
entity(go:credit-where-credit-is-due.html)
-wasDerivedFrom(dm:concept-original-source,go:credit-where-credit-is-due.html,
+wasDerivedFrom(dm:concept-original-source, go:credit-where-credit-is-due.html,
[ prov:type='prov:HadOriginalSource' ])
</pre>
</div>
@@ -2144,20 +2148,20 @@
<li><span class='attribute' id="trace.ancestor">ancestor</span>: an identifier (<span class="name">e1</span>) for an ancestor entity that the former depends on;
<li><span class='attribute' id="trace.attributes">attributes</span>: an OPTIONAL set (<span class="name">attrs</span>) of attribute-value pairs representing additional information about this relation.</li>
</ul>
-<p>We note that the ancestor is allowed to be an agent since agents are entities. </p>
+<p>We note that the ancestor MAY be an agent since agents may be entities. </p>
<p>
<a>Derivation</a> and <a>attribution</a> are particular cases of trace.
</p>
<div class="anexample">
-<p>We refer to the example of <a href="#section-example-two">Section 4.1</a>, and specifically to <a href="#prov-a-document2">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 4.2</a>, and specifically to <a href="#prov-a-document2-top">Figure 3</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.
<pre class="codeexample">
- tracedTo(tr:WD-prov-dm-20111215,w3:Consortium)
- tracedTo(tr:WD-prov-dm-20111215,process:rec-advance)
+ tracedTo(tr:WD-prov-dm-20111215, w3:Consortium)
+ tracedTo(tr:WD-prov-dm-20111215, process:rec-advance)
</pre>
</div>
--- a/model/prov-glossary.html Fri May 25 08:07:53 2012 +0100
+++ b/model/prov-glossary.html Fri May 25 08:48:19 2012 +0100
@@ -20,18 +20,19 @@
<script class="remove">
function updateGlossaryRefs() {
$('.glossary-ref').each(function(index) {
- var ref=$(this).attr('ref');
- var span=$(this).attr('withspan')
- // look up directly in the_glossary
- //$(this).html(the_glossary[ref]);
- // if glossary is in a string:
+ var ref=$(this).attr('data-ref');
+ var span=$(this).attr('data-withspan')
+ $(this).removeAttr('data-withspan');
+ $(this).removeAttr('data-ref');
+
$('#'+ref+'.glossary').contents().clone().appendTo($(this));
- $(this).attr('prov:hadOriginalSource',glossary_hg);
+// $(this).attr("prov:hadOriginalSource",glossary_hg);
if (span) {
$(this).children('dfn').replaceWith(function(){return $('<span>').addClass('dfn').append($(this).contents())});
- }
+ }
});
- }
+ }
+
$(document).ready(function(){
// if glossary is in a string:
$('#glossary_div').html(glossary_string)
@@ -83,8 +84,6 @@
editors: [
{ name: "Luc Moreau", url: "http://www.ecs.soton.ac.uk/~lavm/",
company: "University of Southampton" },
- { name: "Paolo Missier", url: "http://www.cs.ncl.ac.uk/people/Paolo.Missier",
- company: "Newcastle University" },
],
// authors, add as many as you like.
@@ -130,7 +129,71 @@
<section id="glossary" >
<h2>Glossary</h2>
-<div class="glossary-ref" ref="glossary-accountEntity"></div><p></p>
+<p style="font-size: 200%;">A</a>
+
+<div class="glossary-ref" data-ref="glossary-activity"></div><p></p>
+<div class="glossary-ref" data-ref="glossary-activityAssociation"></div><p></p>
+<div class="glossary-ref" data-ref="glossary-agent"></div><p></p>
+<div class="glossary-ref" data-ref="glossary-alternate"></div><p></p>
+<div class="glossary-ref" data-ref="glossary-attribution"></div><p></p>
+
+<p style="font-size: 200%;">B</a>
+
+<div class="glossary-ref" data-ref="glossary-bundle"></div><p></p>
+
+<p style="font-size: 200%;">C</a>
+<div class="glossary-ref" data-ref="glossary-collection"></div><p></p>
+<div class="glossary-ref" data-ref="glossary-communication"></div><p></p>
+
+<p style="font-size: 200%;">D</a>
+<div class="glossary-ref" data-ref="glossary-delegation"></div><p></p>
+<div class="glossary-ref" data-ref="glossary-derivation"></div><p></p>
+<div class="glossary-ref" data-ref="glossary-dictionary"></div><p></p>
+
+<p style="font-size: 200%;">E</a>
+<div class="glossary-ref" data-ref="glossary-end"></div><p></p>
+<div class="glossary-ref" data-ref="glossary-entity"></div><p></p>
+
+<p style="font-size: 200%;">G</a>
+<div class="glossary-ref" data-ref="glossary-generation"></div><p></p>
+
+<p style="font-size: 200%;">I</a>
+<div class="glossary-ref" data-ref="glossary-insertion"></div><p></p>
+<div class="glossary-ref" data-ref="glossary-invalidation"></div><p></p>
+
+<p style="font-size: 200%;">M</a>
+<div class="glossary-ref" data-ref="glossary-membership"></div><p></p>
+
+<p style="font-size: 200%;">O</a>
+<div class="glossary-ref" data-ref="glossary-organization"></div><p></p>
+<div class="glossary-ref" data-ref="glossary-original-source"></div><p></p>
+
+<p style="font-size: 200%;">P</a>
+<div class="glossary-ref" data-ref="glossary-person"></div><p></p></li>
+<div class="glossary-ref" data-ref="glossary-plan"></div><p></p>
+<div class="glossary-ref" data-ref="glossary-provenance-locator"></div><p></p>
+
+<p style="font-size: 200%;">Q</a>
+<div class="glossary-ref" data-ref="glossary-qualifiedName"></div><p></p>
+<div class="glossary-ref" data-ref="glossary-quotation"></div><p></p>
+
+<p style="font-size: 200%;">R</a>
+<div class="glossary-ref" data-ref="glossary-removal"></div><p></p>
+<div class="glossary-ref" data-ref="glossary-revision"></div><p></p></p>
+
+<p style="font-size: 200%;">S</a>
+<div class="glossary-ref" data-ref="glossary-software-agent"></div><p></p>
+<div class="glossary-ref" data-ref="glossary-specialization"></div><p></p>
+<div class="glossary-ref" data-ref="glossary-start"></div><p></p>
+
+<p style="font-size: 200%;">T</a>
+<div class="glossary-ref" data-ref="glossary-trace"></div><p></p>
+
+<p style="font-size: 200%;">U</a>
+<div class="glossary-ref" data-ref="glossary-usage"></div><p></p>
+
+
+<div class="glossary-ref" ref="glossary-accountEntity"></div><p></p><p></p>
<div class="glossary-ref" ref="glossary-activity"></div><p></p>
@@ -167,7 +230,6 @@
<div class="glossary-ref" ref="glossary-start"></div><p></p>
<div class="glossary-ref" ref="glossary-end"></div><p></p>
-
</section>