--- a/model/working-copy/wd5-prov-dm-components.html Sun Mar 18 22:40:31 2012 +0000
+++ b/model/working-copy/wd5-prov-dm-components.html Mon Mar 19 10:30:03 2012 +0000
@@ -845,7 +845,7 @@
<section id="data-model-components">
-<h2>PROV-DM Concepts</h2>
+<h2>PROV-DM Concepts and Relations</h2>
<p>PROV-DM Concepts are structured according to six components that are introduced here.
Components and their dependencies are illustrated in Figure <a href="#prov-dm-components">prov-dm-components</a>. A component that relies on concepts defined in another also sits above it, in this figure.
@@ -1127,12 +1127,12 @@
<section id="term-Start">
-<h4>Activity Start</h4>
+<h4>Start</h4>
<div class="glossary-ref" ref="glossary-start"></div>
-<p>An <dfn title="wasStartedBy">activity start</dfn><span class="withPn">, written <span class="pnExpression">wasStartedBy(id,a,e,t,attrs)</span> in PROV-N,</span> contains:</p>
+<p>An activity <dfn title="wasStartedBy">start</dfn><span class="withPn">, written <span class="pnExpression">wasStartedBy(id,a,e,t,attrs)</span> in PROV-N,</span> contains:</p>
<ul>
<li><span class='attribute' id="start.id">id</span>: an OPTIONAL identifier for the activity start;</li>
<li><span class='attribute' id="start.activity">activity</span>: an identifier for the started activity;</li>
@@ -1174,12 +1174,12 @@
</section>
<section id="term-End">
-<h4>Activity End</h4>
+<h4>End</h4>
<div class="glossary-ref" ref="glossary-end"></div>
-<p>An <dfn title="wasEndedBy">activity end</dfn><span class="withAsn">, written <span class="pnExpression">wasEndedBy(id,a,e,t,attrs)</span> in PROV-ASN,</span> contains:</p>
+<p>An activity <dfn title="wasEndedBy">end</dfn><span class="withAsn">, written <span class="pnExpression">wasEndedBy(id,a,e,t,attrs)</span> in PROV-ASN,</span> contains:</p>
<ul>
<li><span class='attribute' id="end.id">id</span>: an OPTIONAL identifier for the activity end;</li>
<li><span class='attribute' id="end.activity">activity</span>: an identifier for the ended activity;
@@ -1284,8 +1284,8 @@
<p><div class="attributes" id="attributes-agent">An <dfn title="dfn-agent">agent</dfn><span class="withPn">, noted <span class="pnExpression" id="pn-agent">agent(id, [ attr1=val1, ...])</span> in PROV-N,</span> contains:
<ul>
-<li><span class='attribute'>id</span>: an identifier for an agent;</li>
-<li><span class='attribute'>attributes</span>: a set of attribute-value pairs representing this agent's situation in the world.
+<li><span class='attribute' id="agent.id>id</span>: an identifier for an agent;</li>
+<li><span class='attribute' id="agent.attributes>attributes</span>: a set of attribute-value pairs representing this agent's situation in the world.
</li>
</ul></div>
@@ -1326,10 +1326,10 @@
<p> An <dfn title="wasAttributedTo">attribution relation</dfn><span class="withPn">, written <span class="pnExpression">wasAttributedTo(id,e,ag,attr)</span> in PROV-N,</span> contains the following elements:</p>
<ul>
-<li><span class='attribute'>id</span>: an OPTIONAL identifier for the relation;</li>
-<li><span class='attribute'>entity</span>: an entity identifier;</li>
-<li><span class='attribute'>agent</span>: the identifier of the agent whom the entity is ascribed to;</li>
-<li><span class='attribute'>attributes</span>: an OPTIONAL set of attribute-value pairs to further describe the properties of the relation.</li>
+<li><span class='attribute' id="attribution.id>id</span>: an OPTIONAL identifier for the relation;</li>
+<li><span class='attribute' id="attribution.entity>entity</span>: an entity identifier;</li>
+<li><span class='attribute' id="attribution.agent>agent</span>: the identifier of the agent whom the entity is ascribed to;</li>
+<li><span class='attribute' id="attribution.attributes>attributes</span>: an OPTIONAL set of attribute-value pairs to further describe the properties of the relation.</li>
</ul>
<div class="anexample">
@@ -1349,7 +1349,7 @@
<section id="term-ActivityAssociation">
-<h4>Activity Association</h4>
+<h4>Association</h4>
<div class="glossary-ref" ref="glossary-activityAssociation"></div>
@@ -1357,11 +1357,11 @@
<p><div class="attributes" id="attributes-activity-association">An <dfn title="wasAssociatedWith">activity association</dfn><span class="withPn">, written <span class="pnExpression">wasAssociatedWith(id,a,ag,pl,attrs)</span> in PROV-N,</span> has the following
constituents:
<ul>
-<li><span class='attribute'>id</span>: an OPTIONAL identifier for the association between an activity and an agent;</li>
-<li><span class='attribute'>activity</span>: an identifier for the activity;</li>
-<li><span class='attribute'>agent</span>: an OPTIONAL identifier for the agent associated with the activity;</li>
-<li><span class='attribute'>plan</span>: an OPTIONAL identifier for the plan adopted by the agent in the context of this activity;
-<li><span class='attribute'>attributes</span>: an OPTIONAL set of attribute-value pairs that describe the modalities of association of this activity with this agent.</li>
+<li><span class='attribute' id="association.id>id</span>: an OPTIONAL identifier for the association between an activity and an agent;</li>
+<li><span class='attribute' id="association.activity>activity</span>: an identifier for the activity;</li>
+<li><span class='attribute' id="association.agent>agent</span>: an OPTIONAL identifier for the agent associated with the activity;</li>
+<li><span class='attribute' id="association.plan>plan</span>: an OPTIONAL identifier for the plan adopted by the agent in the context of this activity;
+<li><span class='attribute' id="association.attributes>attributes</span>: an OPTIONAL set of attribute-value pairs that describe the modalities of association of this activity with this agent.</li>
</ul></div>
<div class="anexample id="anexample-wasAssociateWith">
@@ -1433,12 +1433,12 @@
<p><div class="attributes" id="attributes-responsibility-chain">A <dfn title="actedOnBehalfOf">responsibility</dfn> relation<span class="withPn">, written <span class="pnExpression">actedOnBehalfOf(id,ag2,ag1,a,attrs)</span> in PROV-N,</span> has the following constituents:
<ul>
-<li><span class='attribute'>id</span>: an OPTIONAL identifier for the responsibility chain;</li>
-<li><span class='attribute'>subordinate</span>: an identifier for the agent associated with an activity, acting on behalf of the responsible
+<li><span class='attribute' id="responsibility.id>id</span>: an OPTIONAL identifier for the responsibility chain;</li>
+<li><span class='attribute' id="responsibility.subordinate>subordinate</span>: an identifier for the agent associated with an activity, acting on behalf of the responsible
agent;</li>
-<li><span class='attribute'>responsible</span>: an identifier for the agent, on behalf of which the subordinate agent acted;</li>
-<li><span class='attribute'>activity</span>: an OPTIONAL identifier of an activity for which the responsibility chain holds;</li>
-<li><span class='attribute'>attributes</span>: an OPTIONAL set of attribute-value pairs that describe the modalities of this relation.</li>
+<li><span class='attribute' id="responsibility.responsible>responsible</span>: an identifier for the agent, on behalf of which the subordinate agent acted;</li>
+<li><span class='attribute' id="responsibility.activity>activity</span>: an OPTIONAL identifier of an activity for which the responsibility chain holds;</li>
+<li><span class='attribute' id="responsibility.attributes>attributes</span>: an OPTIONAL set of attribute-value pairs that describe the modalities of this relation.</li>
</ul></div>
@@ -1489,13 +1489,13 @@
<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> contains:
<ul>
-<li><em>id</em>: an OPTIONAL identifier for a derivation;</li>
-<li><em>generatedEntity</em>: the identifier of the entity generated by the derivation;</li>
-<li><em>usedEntity</em>: the identifier of the entity used by the derivation;</li>
-<li><em>activity</em>: an OPTIONAL identifier for the activity using and generating the above entities;</li>
-<li><em>generation</em>: an OPTIONAL identifier for the generation involving the generated entity and activity;</li>
-<li><em>usage</em>: an OPTIONAL identifier for the usage involving the used entity and activity;</li>
-<li><em>attributes</em>: an OPTIONAL set of attribute-value pairs that describe the modalities of this derivation.</li>
+<li><span class='attribute' id="derivation.id">id</span>: an OPTIONAL identifier for a derivation;</li>
+<li><span class='attribute' id="derivation.generatedEntity">generatedEntity</span>: the identifier of the entity generated by the derivation;</li>
+<li><span class='attribute' id="derivation.usedEntity">usedEntity</span>: the identifier of the entity used by the derivation;</li>
+<li><span class='attribute' id="derivation.activity">activity</span>: an OPTIONAL identifier for the activity using and generating the above entities;</li>
+<li><span class='attribute' id="derivation.generation">generation</span>: an OPTIONAL identifier for the generation involving the generated entity and activity;</li>
+<li><span class='attribute' id="derivation.usage">usage</span>: an OPTIONAL identifier for the usage involving the used entity and activity;</li>
+<li><span class='attribute' id="derivation.attributes">attributes</span>: an OPTIONAL set of attribute-value pairs that describe the modalities of this derivation.</li>
</ul>
</div>
@@ -1543,16 +1543,16 @@
<p> A <dfn title="wasRevisionOf">revision</dfn> relation<span class="withPn">, written <span class="pnExpression">wasRevisionOf(id,e2,e1,ag,attrs)</span> in PROV-N,</span> contains:</p>
<ul>
-<li><span class='attribute'>id</span>: an OPTIONAL identifier for the relation;</li>
-<li><span class='attribute'>newer</span>: the identifier of the revised entity;
-<li><span class='attribute'>older</span>: the identifier of the older entity;
-<li><span class='attribute'>responsibility</span>: an OPTIONAL identifier for the agent who approved the newer entity as a variant of the older;
-<li><span class='attribute'>attributes</span>: an OPTIONAL set of attribute-value pairs to further describe the properties of this relation.</li>
+<li><span class='attribute' id="revision.id">id</span>: an OPTIONAL identifier for the relation;</li>
+<li><span class='attribute' id="revision.newer">newer</span>: the identifier of the revised entity;
+<li><span class='attribute' id="revision.older">older</span>: the identifier of the older entity;
+<li><span class='attribute' id="revision.responsibility">responsibility</span>: an OPTIONAL identifier for the agent who approved the newer entity as a variant of the older;
+<li><span class='attribute' id="revision.attributes">attributes</span>: an OPTIONAL set of attribute-value pairs to further describe the properties of this relation.</li>
</ul>
-<div class="anexample">
+<div class="anexample" id="anexample-revision">
<p>
Revisiting the example of <a href="#section-example-a">Section 3.1</a>,
we can now state that the report
@@ -1581,12 +1581,12 @@
is a particular case of <a href="#Derivation-Relation">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.
A <dfn title="wasQuotedFrom">quotation</dfn> relation <span class="withPn">, written <span class="pnExpression">wasQuotedFrom(id,e2,e1,ag2,ag1,attrs)</span> in PROV-N,</span> contains:</p>
<ul>
-<li><span class='attribute'>id</span>: an OPTIONAL identifier for the relation;</li>
-<li><span class='attribute'>quote</span>: an identifier (<span class="name">e2</span>) for the entity that represents the quote (the partial copy);
-<li><span class='attribute'>original</span>: an identifier (<span class="name">e1</span>) for the original entity being quoted;
-<li><span class='attribute'>quoterAgent</span>: an OPTIONAL identifier (<span class="name">ag2</span>) for the agent who performs the quote;
-<li><span class='attribute'>originalAgent</span>: an OPTIONAL identifier (<span class="name">ag1</span>) for the agent to whom the original entity is attributed;
-<li><span class='attribute'>attributes</span>: an OPTIONAL set of attribute-value pairs to further describe the properties of the relation.</li>
+<li><span class='attribute' id="quotation.id">id</span>: an OPTIONAL identifier for the relation;</li>
+<li><span class='attribute' id="quotation.quote">quote</span>: an identifier (<span class="name">e2</span>) for the entity that represents the quote (the partial copy);
+<li><span class='attribute' id="quotation.original">original</span>: an identifier (<span class="name">e1</span>) for the original entity being quoted;
+<li><span class='attribute' id="quotation.quoterAgent">quoterAgent</span>: an OPTIONAL identifier (<span class="name">ag2</span>) for the agent who performs the quote;
+<li><span class='attribute' id="quotation.originalAgent">originalAgent</span>: an OPTIONAL identifier (<span class="name">ag1</span>) for the agent to whom the original entity is attributed;
+<li><span class='attribute' id="quotation.attributes">attributes</span>: an OPTIONAL set of attribute-value pairs to further describe the properties of the relation.</li>
</ul>
@@ -1594,7 +1594,7 @@
<p>
The following paragraph is a quote from one of <a href="http://thinklinks.wordpress.com/2012/03/07/thoughts-from-the-dagstuhl-principles-of-provenance-workshop/">the author's blogs</a>.
<blockquote id="paul-quote"><em>
-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>
+"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">ex:blog</span></a> denotes the original blog by agent <span class="name">ex:Paul</span>, and
<a href="#paul-quote"><span class="name">ex:blockquote</span></a> denotes the above paragraph, then the following descriptions express that the above paragraph is copied by agent <span class="name">ex:Luc</a> from a part of the blog, attributed to the agent <span class="name">ex:Paul</a>.</p>
@@ -1629,10 +1629,10 @@
<p> An <dfn title="hadOriginalSource">original source</dfn> relation<span class="withPn">, written <span class="pnExpression">hadOriginalSource(id,e2,e1,attrs)</span>,</span> contains:</p>
<ul>
-<li><span class='attribute'>id</span>: an OPTIONAL identifier for the relation;</li>
-<li><span class='attribute'>derived</span>: an identifier for the derived entity; </li>
-<li><span class='attribute'>source</span>: an identifier for the original source entity;</li>
-<li><span class='attribute'>attributes</span>: an OPTIONAL set of attribute-value pairs to further describe the properties of the relation.</li>
+<li><span class='attribute' id="originalSource.id">id</span>: an OPTIONAL identifier for the relation;</li>
+<li><span class='attribute' id="originalSource.derived">derived</span>: an identifier for the derived entity; </li>
+<li><span class='attribute' id="originalSource.source">source</span>: an identifier for the original source entity;</li>
+<li><span class='attribute' id="originalSource.attributes">attributes</span>: an OPTIONAL set of attribute-value pairs to further describe the properties of the relation.</li>
</ul>
<div class="anexample">
@@ -1659,10 +1659,10 @@
<p> A <dfn title="tracedTo">traceability relation</dfn><span class="withPn">, written <span class="pnExpression">tracedTo(id,e2,e1,attrs)</span> in PROV-N,</span> contains:</p>
<ul>
-<li><span class='attribute'>id</span>: an OPTIONAL identifier identifying the relation;</li>
-<li><span class='attribute'>entity</span>: an identifier identifying an entity;
-<li><span class='attribute'>ancestor</span>: an identifier identifying an ancestor entity that the former depends on;
-<li><span class='attribute'>attributes</span>: an OPTIONAL set of attribute-value pairs to further describe properties of the relation.</li>
+<li><span class='attribute' id="traceability.id">id</span>: an OPTIONAL identifier identifying the relation;</li>
+<li><span class='attribute' id="traceability.entity">entity</span>: an identifier identifying an entity;
+<li><span class='attribute' id="traceability.ancestor">ancestor</span>: an identifier identifying an ancestor entity that the former depends on;
+<li><span class='attribute' id="traceability.attributes">attributes</span>: an OPTIONAL set of attribute-value pairs to further describe properties of the relation.</li>
</ul>
<p>We note that the ancestor is allowed to be an agent since agents are entities. </p>