--- a/model/working-copy/wd5-prov-dm-components.html Fri Mar 09 17:49:20 2012 +0000
+++ b/model/working-copy/wd5-prov-dm-components.html Sat Mar 10 09:30:55 2012 +0000
@@ -850,8 +850,6 @@
<section id="component1">
<h3>Component 1: Entities and Activities</h3>
-<section id="term-element">
-<h3>Element</h3>
@@ -942,8 +940,6 @@
</ul>
-</section>
-
</section>
<section id="term-Generation">
@@ -1045,6 +1041,56 @@
</section>
+
+<section id="term-Start-End">
+<h4>Activity Start and Activity End (Voting in Progress)</h4>
+
+<p> A <dfn title="dfn-Start">activity start</dfn> is a representation of an agent starting an activity.
+ An <dfn title="dfn-End">activity end</dfn> is a representation of an agent ending an activity. Both relations are specialized forms of <span class="name">wasAssociatedWith</span>. They contain
+attributes describing the modalities of acting/ending activities.</p>
+
+
+
+<p>An activity start<span class="withPn">, written <span class="pnExpression">wasStartedBy(id,a,ag,attrs)</span> in PROV-N,</span> contains:</p>
+<ul>
+<li><span class='attribute'>id</span>: an OPTIONAL identifier for the activity start;</li>
+<li><span class='attribute'>activity</span>: an identifier for the started activity;
+<li><span class='attribute'>agent</span>: an identifier for the agent starting the activity;
+<li><span class='attribute'>attributes</span>: an OPTIONAL set of attribute-value pairs describing modalities according to which the agent started the activity.
+</ul>
+
+<p>An activity end<span class="withPn">, written <span class="pnExpression">wasEndedBy(id,a,ag,attrs)</span> in PROV-N,</span> contains:</p>
+<ul>
+<li><span class='attribute'>id</span>: an OPTIONAL identifier for the activity end;</li>
+<li><span class='attribute'>activity</span>: an identifier for the ended activity;
+<li><span class='attribute'>agent</span>: an identifier for the agent ending the activity;
+<li><span class='attribute'>attributes</span>: an OPTIONAL set of attribute-value pairs describing modalities according to which the agent ended the activity.
+</ul>
+
+
+<div class="anexample">
+<p>
+In the following example,</p>
+<pre class="codeexample">
+wasStartedBy(a,ag,[ex:mode="manual"])
+wasEndedby(a,ag,[ex:mode="manual"])
+</pre>
+<p>there is an activity denoted by <span class="name">a</span>
+that was started and ended by an agent denoted by <span class="name">ag</span>, in "manual" mode, an application specific characterization of these relations.
+</p>
+</div>
+
+<div class='issue'>
+Should we define start/end records as representation of activity start/end events.
+Should time be associated with these events rather than with activities. This will be similar to what
+we do for entities. This is issue <a href="http://www.w3.org/2011/prov/track/issues/207">ISSUE-207</a>.</div>
+
+
+
+
+
+</section>
+
<section id="term-OrderingOfActivities">
<h3>Activity Ordering</h3>
@@ -1431,6 +1477,41 @@
</section> <!-- end original source -->
+<section id="term-traceability">
+<h3>Traceability</h3>
+
+<p> A <dfn title="dfn-Traceability">traceability relation</dfn> between two entities <span class="name">e2</span> and <span class="name">e1</span> is a generic dependency of <span class="name">e2</span>
+on <span class="name">e1</span> that indicates either that <span class="name">e1</span> was necessary for <span class="name">e2</span> to be created, or that <span class="name">e1</span> bears
+some responsibility for <span class="name">e2</span>'s existence.
+
+
+<p> A traceability relation<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>
+</ul>
+<p>We note that the ancestor is allowed to be an agent since agents are entities. </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 prov-tech-report</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> or to
+<span class="name">pr: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,pr:rec-advance)
+</pre>
+</div>
+
+
+<p>
+<a href="#Derivation-Relation">Derivation</a> and association are particular cases of traceability.
+</p>
+
+
+</section>
</section>
@@ -1719,105 +1800,6 @@
</section>
-</section>
-
-
-<section id="data-model-concepts">
-
-<h2>PROV-DM Concepts Unassigned to Components Yet</h2>
-
-<p>In this section, we revisit each concept introduced in <a href="'#conceptualization'">Section 2</a>, and provide its detailed definition in the PROV data model, in terms of its various constituents. </p>
-
-<p>In PROV-DM, we distinguish elements from relations, which are respectively discussed in
-<a href="'#term-element'">Section 4.1</a> and <a href="'#term-relation'">Section 4.2</a>.</p>
-
-
-
-<section id="term-relation">
-<h3>Relation</h3>
-
-<p>
-This section describes all the PROV-DM relations between the elements introduced in <a href="#term-element">Section Element</a>. While these relations are not
-binary, they all involve two primary elements. They can be summarized as follows. </p>
-
-
-<div style="text-align: center;">
-<table border="1" style="margin-left: auto; margin-right: auto;">
-<caption>PROV-DM Core Relation Summary</caption>
-<tr><td></td><td>Entity</td><td>Activity</td><td>Agent</td><td>Note</td></tr>
-<tr><td>Entity</td><td><a title="derivations">wasDerivedFrom</a><br><a title="dfn-alternate">alternateOf</a><br><a title="dfn-specialization">specializationOf</a></td><td><a
-title="dfn-Generation">wasGeneratedBy</a></td><td>—</td><td><a title="dfn-annotation">hasAnnotation</a></td></tr>
-<tr><td>Activity</td><td><a title="usage">used</a></td><td>—</td><td><a title="start record">wasStartedBy</a><br><a title="end record">wasEndedBy</a><br><a title="dfn-activity-association">wasAssociatedWith</a></td><td><a title="dfn-annotation">hasAnnotation</a></td></tr>
-<tr><td>Agent</td><td>—</td><td>—</td><td><a title="dfn-responsibility-chain">actedOnBehalfOf</a></td><td><a title="dfn-annotation">hasAnnotation</a></td></tr>
-<tr><td>Note</td><td>—</td><td>—</td><td>—</td><td><a title="dfn-annotation">hasAnnotation</a></td></tr>
-</table>
-</div>
-
-
-
-
-
-
-
-
-<section id="activity-agent-relation">
-<h3>Activity-Agent Relation</h3>
-
-
-<section id="term-Start-End">
-<h4>Activity Start and Activity End</h4>
-
-<p> A <dfn title="dfn-Start">activity start</dfn> is a representation of an agent starting an activity.
- An <dfn title="dfn-End">activity end</dfn> is a representation of an agent ending an activity. Both relations are specialized forms of <span class="name">wasAssociatedWith</span>. They contain
-attributes describing the modalities of acting/ending activities.</p>
-
-
-
-<p>An activity start<span class="withPn">, written <span class="pnExpression">wasStartedBy(id,a,ag,attrs)</span> in PROV-N,</span> contains:</p>
-<ul>
-<li><span class='attribute'>id</span>: an OPTIONAL identifier for the activity start;</li>
-<li><span class='attribute'>activity</span>: an identifier for the started activity;
-<li><span class='attribute'>agent</span>: an identifier for the agent starting the activity;
-<li><span class='attribute'>attributes</span>: an OPTIONAL set of attribute-value pairs describing modalities according to which the agent started the activity.
-</ul>
-
-<p>An activity end<span class="withPn">, written <span class="pnExpression">wasEndedBy(id,a,ag,attrs)</span> in PROV-N,</span> contains:</p>
-<ul>
-<li><span class='attribute'>id</span>: an OPTIONAL identifier for the activity end;</li>
-<li><span class='attribute'>activity</span>: an identifier for the ended activity;
-<li><span class='attribute'>agent</span>: an identifier for the agent ending the activity;
-<li><span class='attribute'>attributes</span>: an OPTIONAL set of attribute-value pairs describing modalities according to which the agent ended the activity.
-</ul>
-
-
-<div class="anexample">
-<p>
-In the following example,</p>
-<pre class="codeexample">
-wasStartedBy(a,ag,[ex:mode="manual"])
-wasEndedby(a,ag,[ex:mode="manual"])
-</pre>
-<p>there is an activity denoted by <span class="name">a</span>
-that was started and ended by an agent denoted by <span class="name">ag</span>, in "manual" mode, an application specific characterization of these relations.
-</p>
-</div>
-
-<div class='issue'>
-Should we define start/end records as representation of activity start/end events.
-Should time be associated with these events rather than with activities. This will be similar to what
-we do for entities. This is issue <a href="http://www.w3.org/2011/prov/track/issues/207">ISSUE-207</a>.</div>
-
-
-</section>
-
-
-
-
-</section>
-
-
-
-</section>
@@ -1937,15 +1919,9 @@
</section>
-
-
-</section>
-
-
-
<section id="term-literal">
-<h4>Literal</h4>
+<h4>Value</h4>
<div class='note'>
Usually, in programming languages, Literal are a notation for values. So, Literals should probably be moved to the serialization. Here, instead, we should define the types of values. Thoughts?
@@ -1975,13 +1951,13 @@
-</section>
+
<section id="term-Time">
-<h4>Time</h4>
+<h4>Time (to be folded in Value section)</h4>
<div class='note'>
It's a legacy of the charter that time is a top level section. Time is a specific kind of value, and should be folded into the "value" section.
@@ -1996,17 +1972,72 @@
+</section>
+
+</section>
+
+
+</section>
+
</section>
+<section id="data-model-concepts">
+
+<h2>OLD Introductory Material PROV-DM Concepts</h2>
+
+<p>In this section, we revisit each concept introduced in <a href="'#conceptualization'">Section 2</a>, and provide its detailed definition in the PROV data model, in terms of its various constituents. </p>
+
+<p>In PROV-DM, we distinguish elements from relations, which are respectively discussed in
+<a href="'#term-element'">Section 4.1</a> and <a href="'#term-relation'">Section 4.2</a>.</p>
+
+
+
+<section id="term-relation">
+<h3>Table on Relation</h3>
+
+<p>
+This section describes all the PROV-DM relations between the elements introduced in <a href="#term-element">Section Element</a>. While these relations are not
+binary, they all involve two primary elements. They can be summarized as follows. </p>
+
+
+<div style="text-align: center;">
+<table border="1" style="margin-left: auto; margin-right: auto;">
+<caption>PROV-DM Core Relation Summary</caption>
+<tr><td></td><td>Entity</td><td>Activity</td><td>Agent</td><td>Note</td></tr>
+<tr><td>Entity</td><td><a title="derivations">wasDerivedFrom</a><br><a title="dfn-alternate">alternateOf</a><br><a title="dfn-specialization">specializationOf</a></td><td><a
+title="dfn-Generation">wasGeneratedBy</a></td><td>—</td><td><a title="dfn-annotation">hasAnnotation</a></td></tr>
+<tr><td>Activity</td><td><a title="usage">used</a></td><td>—</td><td><a title="start record">wasStartedBy</a><br><a title="end record">wasEndedBy</a><br><a title="dfn-activity-association">wasAssociatedWith</a></td><td><a title="dfn-annotation">hasAnnotation</a></td></tr>
+<tr><td>Agent</td><td>—</td><td>—</td><td><a title="dfn-responsibility-chain">actedOnBehalfOf</a></td><td><a title="dfn-annotation">hasAnnotation</a></td></tr>
+<tr><td>Note</td><td>—</td><td>—</td><td>—</td><td><a title="dfn-annotation">hasAnnotation</a></td></tr>
+</table>
+</div>
+
+
+
+
+
+
+
+
+
+
+
+</section>
+
+
+
+
+
+
<section id="common-relations">
-<h2>PROV-DM Common Relations</h2>
+<h2>Figures on PROV-DM Common Relations</h2>
<p>The following figure summarizes the additional relations described in this section.
</p>
@@ -2026,41 +2057,6 @@
-<section id="term-traceability">
-<h3>Traceability</h3>
-
-<p> A <dfn title="dfn-Traceability">traceability relation</dfn> between two entities <span class="name">e2</span> and <span class="name">e1</span> is a generic dependency of <span class="name">e2</span>
-on <span class="name">e1</span> that indicates either that <span class="name">e1</span> was necessary for <span class="name">e2</span> to be created, or that <span class="name">e1</span> bears
-some responsibility for <span class="name">e2</span>'s existence.
-
-
-<p> A traceability relation<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>
-</ul>
-<p>We note that the ancestor is allowed to be an agent since agents are entities. </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 prov-tech-report</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> or to
-<span class="name">pr: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,pr:rec-advance)
-</pre>
-</div>
-
-
-<p>
-<a href="#Derivation-Relation">Derivation</a> and association are particular cases of traceability.
-</p>
-
-
-</section>
</section>