updated Communication and Start by Activity
authorLuc Moreau <l.moreau@ecs.soton.ac.uk>
Wed, 21 Mar 2012 21:08:30 +0000
changeset 1957 76c1b0f81959
parent 1956 966bb518d2b9
child 1958 b3f7be492a4b
updated Communication and Start by Activity
model/glossary.html
model/glossary.js
model/working-copy/wd5-prov-dm-components.html
model/working-copy/wd5-prov-n.html
--- a/model/glossary.html	Wed Mar 21 13:15:20 2012 +0000
+++ b/model/glossary.html	Wed Mar 21 21:08:30 2012 +0000
@@ -128,6 +128,13 @@
 <dfn id="concept-attribution">Attribution</dfn> is the ascribing of an entity to an agent.
 </span>
 
+<span class="glossary" id="glossary-communication">  
+<dfn id="concept-communication">Communication</dfn> is the exchange of an entity by two activities, one activity using the entity generated by the other.
+</span>
 
+
+<span class="glossary" id="glossary-startByActivity">  
+<dfn id="concept-startByActivity">Start by Activity</dfn> is when an activity is deemed to have started, triggered by another activity.
+</span>
 </html>
 
--- a/model/glossary.js	Wed Mar 21 13:15:20 2012 +0000
+++ b/model/glossary.js	Wed Mar 21 21:08:30 2012 +0000
@@ -3,7 +3,7 @@
 //  with <script src="glossary.js" class="remove"></script>
 //Insert glossary definitions with the following 
 // <div class="glossary-ref" ref="glossary-generation"></div>
-glossary_hg='http://dvcs.w3.org/hg/prov/file/7cdea0df91fd/model/glossary.html';
+glossary_hg='http://dvcs.w3.org/hg/prov/file/966bb518d2b9/model/glossary.html';
 glossary_string= 
 ' ' + 
 '<html> ' + 
@@ -135,7 +135,14 @@
 '<dfn id="concept-attribution">Attribution</dfn> is the ascribing of an entity to an agent. ' + 
 '</span> ' + 
 ' ' + 
+'<span class="glossary" id="glossary-communication">   ' + 
+'<dfn id="concept-communication">Communication</dfn> is the exchange of an entity by two activities, one activity using the entity generated by the other. ' + 
+'</span> ' + 
 ' ' + 
+' ' + 
+'<span class="glossary" id="glossary-startByActivity">   ' + 
+'<dfn id="concept-startByActivity">Start by Activity</dfn> is when an activity is deemed to have started, triggered by another activity. ' + 
+'</span> ' + 
 '</html> ' + 
 ' ' + 
 ' ' ;
--- a/model/working-copy/wd5-prov-dm-components.html	Wed Mar 21 13:15:20 2012 +0000
+++ b/model/working-copy/wd5-prov-dm-components.html	Wed Mar 21 21:08:30 2012 +0000
@@ -905,8 +905,8 @@
 <tr class="component1-color"><td><a>Usage</a></td><td><a title="used">used(id,a,e,t,attrs)</a></td></tr>
 <tr class="component1-color"><td><a>Start</a></td><td><a title="wasStartedBy">wasStartedBy(id,a,e,t,attrs)</a></td></tr>
 <tr class="component1-color"><td><a>End</a></td><td><a title="wasEndedBy">wasEndedBy(id,a,e,t,attrs)</a></td></tr>
-<tr class="component1-color"><td>Information flow ordering</td><td><a title="wasInformedBy">wasInformedBy(id,a2,a1,attrs)</a></td></tr>
-<tr class="component1-color"><td>Control flow ordering</td><td><a title="wasStartedByActivity">wasStartedByActivity(id, a2, a1, attrs)</a></td></tr>
+<tr class="component1-color"><td><a>Communication</a></td><td><a title="wasInformedBy">wasInformedBy(id,a2,a1,attrs)</a></td></tr>
+<tr class="component1-color"><td><a>Start by Activity</a></td><td><a title="wasStartedByActivity">wasStartedByActivity(id, a2, a1, attrs)</a></td></tr>
 <tr class="component2-color"><td><a>Agent</a></td><td><a title="dfn-agent">agent(id, [ attr1=val1, ...])</a></td></tr>
 <tr class="component2-color"><td><a>Attribution</a></td><td><a title="wasAttributedTo">wasAttributedTo(id,e,ag,attr)</a></td></tr>
 <tr class="component2-color"><td><a>Association</a></td><td><a title="wasAssociatedWith">wasAssociatedWith(id,a,ag,pl,attrs)</a></td></tr>
@@ -924,7 +924,7 @@
 <tr class="component5-color"><td></td><td>derivedByBulkInsertionFrom(id, collAfter, collBefore, key-value-set, attrs)</td></tr>
 <tr class="component5-color"><td></td><td>derivedByBulkRemovalFrom(id, collAfter, collBefore, key-set, attrs)</td></tr>
 <tr class="component5-color"><td></td><td>containedBulk(id, coll, key-value-set, attrs)</td></tr>
-<tr class="component6-color"><td></td><td><a title="note">note(id, [ attr1=val1, ...])</a></td></tr>
+<tr class="component6-color"><td><a>Note</a></td><td><a title="note">note(id, [ attr1=val1, ...])</a></td></tr>
 <tr class="component6-color"><td><a>Annotation</a></td><td><a title="hasAnnotation">hasAnnotation(r,n)</a></td></tr>
 </table>
 </div>
@@ -1212,17 +1212,18 @@
 </section>
 
 <section id="term-wasInformedBy">
-<h3>Information flow ordering</h3>
-
-<div class="note">Need english definition here</div>
-
-
-<p>An <dfn title="InformationFlowOrdering">information flow ordering relation</dfn> states that activity  <span class="name">a2</span> is dependent on another <span class="name">a1</span>, by way of some entity <span class="name">e</span> that is generated by <span class="name">a1</span> and used by <span class="name">a2</span>.</p>
-
-
-
-<p>
-An <dfn title="wasInformedBy">information flow</dfn> ordering relation<span class="withPn">, written as 
+<h3>Communication</h3>
+
+<div class="glossary-ref" ref="glossary-communication"></div>
+
+
+<p>A communication implies that activity  <span class="name">a2</span> is dependent on another <span class="name">a1</span>, by way of some entity <span class="name">e</span> that is generated by <span class="name">a1</span> and used by <span class="name">a2</span>.</p>
+
+
+
+
+<div class="attributes" id="attributes-wasInformedBy">
+A <dfn title="wasInformedBy">communication</dfn> <span class="withPn">, written as 
 <span class="pnExpression">wasInformedBy(id,a2,a1,attrs)</span> in PROV-N,</span> contains: 
 <ul>
 <li><span class='attribute'>id</span>:  an OPTIONAL identifier  identifying the relation;</li> 
@@ -1230,6 +1231,8 @@
 <li><span class='attribute'>informant</span>: the identifier of the informant activity;
 <li><span class='attribute'>attributes</span>: an OPTIONAL set of attribute-value pairs to further describe properties of the relation.</li>
 </ul>
+</div>
+
 <p> Relation <span class="name">wasInformedBy</span> is not transitive.</p>
 
 
@@ -1246,20 +1249,22 @@
 </section>
 
 <section id="term-wasStartedByActivity">
-<h3>Control ordering</h3>
-
-<p>A <dfn title="ControlOrdering">control ordering relation</dfn> states that  activity <span class="name">a2</span> was initiated by another activity <span class="name">a1</span>.</p>
-
-<p>
-A <dfn title="wasStartedByActivity">control ordering</dfn> relation<span class="withPn">, written as 
+<h3>Start by Activity</h3>
+
+<div class="glossary-ref" ref="glossary-startByActivity"></div>
+
+
+
+<p><div class="attributes" id="attributes-startByActivity">
+A <dfn title="wasStartedByActivity">start by activity</dfn><span class="withPn">, written as 
 <span class="pnExpression">wasStartedByActivity(id, a2, a1, attrs)</span> in PROV-N,</span> contains: </p>
 <ul>
-<li><span class='attribute'>id</span>:  an OPTIONAL identifier of the relation;</li> 
-<li><span class='attribute'>started</span>: the identifier of  the started activity;
-<li><span class='attribute'>starter</span>: the identifier of the activity that started the other;</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="startByActivity.id">id</span>:  an OPTIONAL identifier of the relation;</li> 
+<li><span class='attribute' id="startByActivity.started">started</span>: the identifier of  the started activity;
+<li><span class='attribute' id="startByActivity.starter">starter</span>: the identifier of the activity that started the other;</li>
+<li><span class='attribute' id="startByActivity.attributes">attributes</span>: an OPTIONAL set of attribute-value pairs to further describe the properties of the relation.</li>
 </ul>
-
+</div>
 
 
 
@@ -1326,9 +1331,6 @@
 <p>It is optional to specify the type of an agent. When present, it is expressed using the <span class="name">prov:type</span> attribute.</p>
 </div>
 
-<div class='issue'> Shouldn't we allow for entities (not agent) to be associated with an activity?  Should we drop the inference association-agent? <a
-href="http://www.w3.org/2011/prov/track/issues/203">ISSUE-203</a>.</div>
-
 </section>
 
 <section id="term-attribution">
@@ -1761,8 +1763,8 @@
 
 <p><div class="attributes" id="attributes-alternate">An <dfn title="alternateOf">alternate relation</dfn><span class="withPn">, written <span class="pnExpression">alternateOf(alt1, alt2)</span> in PROV-N,</span> addresses case (1). It has the following constituents:
 <ul>
-<li><span class='attribute'>firstAlternate</span>: an identifier of the first of the two entities;</li>
-<li><span class='attribute'>secondAlternate</span>: an identifier of the second of the two entities.</li>
+<li><span class='attribute' id="alternate.firstAlternate">firstAlternate</span>: an identifier of the first of the two entities;</li>
+<li><span class='attribute' id="alternate.secondAlternate">secondAlternate</span>: an identifier of the second of the two entities.</li>
 </ul>
 </div>
 
@@ -1787,8 +1789,8 @@
 <div class="attributes" id="attributes-specialization">A <dfn title="specializationOf">specialization relation</dfn><span class="withPn">, written <span class="pnExpression">specializationOf(sub, super)</span> in PROV-N,</span> addresses case  (2). It  has the following constituents:
 
 <ul>
-<li><span class='attribute'>specializedEntity</span>: an identifier of the specialized entity;</li>
-<li><span class='attribute'>generalEntity</span>: an identifier of the entity that is being specialized.</li>
+<li><span class='attribute' id="specialization.specializedEntity">specializedEntity</span>: an identifier of the specialized entity;</li>
+<li><span class='attribute' id="specialization.generalEntity">generalEntity</span>: an identifier of the entity that is being specialized.</li>
 </ul>
 </div>
 
@@ -2116,8 +2118,8 @@
 
 <p><div class="attributes" id="attributes-note">A <dfn>note</dfn><span class="withPn">, noted <span class="pnExpression">note(id, [ attr1=val1, ...])</span> in PROV-N,</span> contains:
 <ul>
-<li><span class='attribute'>id</span>: an identifier for a note;</li>
-<li><span class='attribute'>attributes</span>: a set of attribute-value pairs, whose meaning is application specific.</li>
+<li><span class='attribute' id="note.id">id</span>: an identifier for a note;</li>
+<li><span class='attribute' id="note.attributes">attributes</span>: a set of attribute-value pairs, whose meaning is application specific.</li>
 </ul></div>
 
 
@@ -2170,8 +2172,8 @@
 
 <p></p><div class="attributes" id="attributes-annotation">An <dfn title="hasAnnotation">annotation relation</dfn><span class="withPn">, written <span class="pnExpression">hasAnnotation(r,n)</span> in PROV-N,</span> has the following constituents:
 <ul>
-<li><span class='attribute'>something</span>: the identifier of something being annotated;</li>
-<li><span class='attribute'>note</span>: an identifier of a note.</li>
+<li><span class='attribute' id="annotation.id">something</span>: the identifier of something being annotated;</li>
+<li><span class='attribute' id="annotation.note">note</span>: an identifier of a note.</li>
 </ul>
 </div>
 
--- a/model/working-copy/wd5-prov-n.html	Wed Mar 21 13:15:20 2012 +0000
+++ b/model/working-copy/wd5-prov-n.html	Wed Mar 21 21:08:30 2012 +0000
@@ -1719,17 +1719,6 @@
 
 </section>
 
-<!-- no longer necessary to say that.
-
-<p>All the records in <span class="name">recs</span> are implictly wrapped in a default account, scoping all the record identifiers they declare directly, and constituting a toplevel
-account, in the hierarchy of accounts.  Consequently, every provenance record is always expressed in the context of an account, either explicitly in an asserted account, or implicitly in a
-container's default account.</p>
+</body>
 
--->
-
-
-
-
-
-
- </body></html>
+</html>