--- a/model/ProvenanceModel.html Tue Sep 06 14:47:19 2011 +0100
+++ b/model/ProvenanceModel.html Tue Sep 06 14:48:46 2011 +0100
@@ -168,7 +168,7 @@
In this section, the example is encoded according to the provenance data model (specified in section <a href="#data-model-concepts">concepts</a>) and expressed in the Provenance Abstract Syntax Notation. Details about the Provenance Abstract Syntax Notation can be found in <a href="#PASN-convention">appendix</a>.
<p>
-Entities (construct described in <a href="#concept-Entity">Section Entity</a>). The file in its various forms and its copies are modelled as entities.
+Entities (construct described in <a href="#expression-Entity">Section Entity</a>). The file in its various forms and its copies are modelled as entities.
<pre>
entity(e0, [ type: "File", location: "/shared/crime.txt", creator: "Alice" ])
entity(e1, [ type: "File", location: "/shared/crime.txt", creator: "Alice", content: "" ])
@@ -197,7 +197,7 @@
</p>
<p>
-Derivations (construct described in <a href="#concept-Derivation">Section Derivation</a>): derivations express that an entity is derived from another.
+Derivations (construct described in <a href="#expression-Derivation">Section Derivation</a>): derivations express that an entity is derived from another.
<pre>
wasDerivedFrom(e2,e1)
wasDerivedFrom(e3,e2)
@@ -207,7 +207,7 @@
</p>
<p>
-Process Executions (construct described in <a href="#concept-ProcessExecution">Section Process Execution</a>): process execution represents an activity in the scenario.
+Process Executions (construct described in <a href="#expression-ProcessExecution">Section Process Execution</a>): process execution represents an activity in the scenario.
<pre>
processExecution(pe0,create-file,t)
processExecution(pe1,add-crime-in-london,t+1)
@@ -219,7 +219,7 @@
</p>
<p>
-Generations (construct described in <a href="#concept-Generation">Section Generation</a>): generation is the event at which a file is created in a specific form. To distinguish the function that the various entities generated by a given process execution have in the context of this process execution, a role (construct described in <a href="#concept-Role">Section Role</a>) is introduced. Illustrations of such roles are outFile, outContent, out, attachment.
+Generations (construct described in <a href="#expression-Generation">Section Generation</a>): generation is the event at which a file is created in a specific form. To distinguish the function that the various entities generated by a given process execution have in the context of this process execution, a role (construct described in <a href="#expression-Role">Section Role</a>) is introduced. Illustrations of such roles are outFile, outContent, out, attachment.
<pre>
wasGeneratedBy(e0,pe0,outFile)
wasGeneratedBy(e1,pe0,outContent)
@@ -233,7 +233,7 @@
<p>
-Used (construct described in <a href="#concept-Use">Section Use</a>): use is the event by which a file is read by a process execution. To distinguish the various entities used by a given process execution, a role (construct described in <a href="#concept-Role">Section Role</a>) is introduced. Illustrations of such roles are in and fileIn.
+Used (construct described in <a href="#expression-Use">Section Use</a>): use is the event by which a file is read by a process execution. To distinguish the various entities used by a given process execution, a role (construct described in <a href="#expression-Role">Section Role</a>) is introduced. Illustrations of such roles are in and fileIn.
<pre>
used(pe1,e1,in)
used(pe3,e2,in)
@@ -246,7 +246,7 @@
<p>
-wasComplementOf: (this relation is described in <a href="#concept-complement-of">Section wasComplementOf</a>). The crime statistics file (e0) has various contents over its existence (e1,e2,e3); the entites e1,e2,e3 complement e0 with an attribute content. Likewise, e6 complements e3 with an attributed spellchecked.
+wasComplementOf: (this relation is described in <a href="#expression-complement-of">Section wasComplementOf</a>). The crime statistics file (e0) has various contents over its existence (e1,e2,e3); the entites e1,e2,e3 complement e0 with an attribute content. Likewise, e6 complements e3 with an attributed spellchecked.
<pre>
wasComplementOf(e1,e0)
wasComplementOf(e2,e0)
@@ -257,7 +257,7 @@
<p>
-Agents (construct described at <a href="#concept-Agent">Section Agent</a>): the various users are represented as agents, themselves being a type of entity.
+Agents (construct described at <a href="#expression-Agent">Section Agent</a>): the various users are represented as agents, themselves being a type of entity.
<pre>
entity(a1, [ type: "Person", name: "Alice" ])
agent(a1)
@@ -278,7 +278,7 @@
<p>
-Control (construct described in <a href="#concept-Control">Section Control</a>): the influence of an agent over a process execution is expressed as control, and the nature of this influence is described by a role (construct described in <a href="#concept-Role">Section Role</a>). Illustrations of such roles are creator, author and communicator.
+Control (construct described in <a href="#expression-Control">Section Control</a>): the influence of an agent over a process execution is expressed as control, and the nature of this influence is described by a role (construct described in <a href="#expression-Role">Section Role</a>). Illustrations of such roles are creator, author and communicator.
<pre>
wasControlledBy(pe0,a1, creator)
wasControlledBy(pe1,a2, author)
@@ -393,7 +393,7 @@
<div class='issue'>Conceptual model needs a high level overview <a href="http://www.w3.org/2011/prov/track/issues/86">ISSUE-86</a>.</div>
- <section id="concept-Entity">
+ <section id="expression-Entity">
<h3>Entity</h3>
@@ -482,7 +482,7 @@
</section>
- <section id="concept-ProcessExecution">
+ <section id="expression-ProcessExecution">
<h3>Process Execution</h3>
<p>A <dfn id="dfn-ProcessExecution">process execution</dfn> represents an identifiable activity, which performs a piece of work.</p>
@@ -492,7 +492,7 @@
<p> A process execution assertion, noted <span class="name">processExecution(id,rl,st,et)</span>:
<ul>
<li> contains an identifier <span class="name">id</span>;
-<li> MAY contain a <a href="#concept-RecipeLink">recipe link</a> <span class="name">rl</span>;
+<li> MAY contain a <a href="#expression-RecipeLink">recipe link</a> <span class="name">rl</span>;
<li> MAY contain a start time <span class="name">st</span>;
<li> MAY contain an end time <span class="name">et</span>.
</ul>
@@ -525,7 +525,7 @@
<div class='pending'>Should process execution be defined as a subclass of BOB. This is <a href="http://www.w3.org/2011/prov/track/issues/66">ISSUE-66</a>.</div>
</section>
-<section id="concept-Generation">
+<section id="expression-Generation">
<h3>Generation<br>
</h3>
@@ -539,7 +539,7 @@
<ul>
<li> refers to an entity <span class="name">e</span>, which represents the characterized thing that is created;
<li> refers to a process execution <span class="name">pe</span>;
-<li> contains a <a href="#concept-Role">role</a> <span class="name">r</span>;
+<li> contains a <a href="#expression-Role">role</a> <span class="name">r</span>;
<li> MAY contain a "generation time" <span class="name">t</span>, the time at which the characterized thing was created.</p>
</ul>
</p>
@@ -550,7 +550,7 @@
</pre>
</p>
-<p>A given entity can be generated at most by one process execution in the scope of a given <a href="#concept-Account">account</a>.
+<p>A given entity can be generated at most by one process execution in the scope of a given <a href="#expression-Account">account</a>.
The rationale for this constraint is as follows.
If two process executions sequentially set different values to some attribute by means of two different generate events, then they generate distinct entities. Alternatively, for two process executions to generate an entity simultaneously, they would require some synchronization by which they agree the entity is released for use; the end of this synchronization would constitute the actual generation of the entity, but is performed by a single process execution. </p>
</p>
@@ -583,7 +583,7 @@
</section>
-<section id="concept-Use">
+<section id="expression-Use">
<h3>Use</h3>
<div class='resolved'>Various comments raised at <a href="http://www.w3.org/2011/prov/track/issues/64">ISSUE-64</a>.</div>
@@ -595,7 +595,7 @@
<ul>
<li> refers to a process execution <span class="name">pe</span>;
<li> refers to an entity <span class="name">e</span>, representing the characterized thing that is used;
-<li> contains a <a href="#concept-Role">role</a> <span class="name">r</span>;
+<li> contains a <a href="#expression-Role">role</a> <span class="name">r</span>;
<li> MAY contain a "use time" <span class="name">t</span>, the time at which the characterized thing was used.</p>
</ul>
</p>
@@ -638,7 +638,7 @@
-<section id="concept-Derivation">
+<section id="expression-Derivation">
<h3>Derivation</h3>
@@ -846,7 +846,7 @@
-<section id="concept-Agent">
+<section id="expression-Agent">
<h3>Agent</h3>
@@ -877,7 +877,7 @@
</section>
-<section id="concept-Control">
+<section id="expression-Control">
<h3>Control</h3>
<p> <dfn id="dfn-Control">Control</dfn> represents the involvement of an agent or an entity in a process execution; a role qualifies this involvement.</p>
@@ -899,7 +899,7 @@
</section>
-<section id="concept-complement-of">
+<section id="expression-complement-of">
<h3>was Complement Of</h3>
@@ -967,7 +967,7 @@
</section>
-<section id="concept-Time">
+<section id="expression-Time">
<h3>Time</h3>
<p><dfn id="dfn-time">Time instants</dfn> are defined according to xsd:dateTime [[!XMLSCHEMA-2]].</p>
@@ -1001,7 +1001,7 @@
</section>
-<section id="concept-RecipeLink">
+<section id="expression-RecipeLink">
<h3>Recipe Link</h3>
@@ -1019,7 +1019,7 @@
</section>
-<section id="concept-Role">
+<section id="expression-Role">
<h3>Role</h3>
@@ -1062,7 +1062,7 @@
</section>
-<section id="concept-Location">
+<section id="expression-Location">
<h3>Location</h3>
<p><dfn id="dfn-Location">Location</dfn> is an identifiable geographic place (ISO 19112). As such, there are numerous ways in which location can be specified, such as by a coordinate, address, landmark, row, column, and so forth.</p>
@@ -1077,7 +1077,7 @@
</section>
-<section id="concept-OrderingOfProcesses">
+<section id="expression-OrderingOfProcesses">
<h3>Ordering of Process Executions</h3>
</section>
@@ -1132,7 +1132,7 @@
</p>
-<section id="concept-Revision">
+<section id="expression-Revision">
<h3>Revision</h3>
<p> <dfn id="dfn-Revision">Revision</dfn> represents the creation of a characterized thing considered to be a variant of another. Deciding whether something is made available as a revision of something else usually involves an agent who is responsible for declaring that the former is variant of the latter. </p>
@@ -1171,7 +1171,7 @@
</section>
-<section id="concept-Participation">
+<section id="expression-Participation">
<h3>Participation</h3>
<p> <dfn id="dfn-Participation">Participation</dfn> represents the involvment of a thing in an activity. It can be asserted or inferred.</p>
@@ -1205,7 +1205,7 @@
</section>
-<section id="concept-ProvenanceContainer">
+<section id="expression-ProvenanceContainer">
<h3>Provenance Container</h3>
<p>A <dfn id="dfn-ProvenanceContainer">Provenance Container</dfn> is an identifiable wrapper for a set of PIDM constructs, which allows for additional meta-information pertaining to these constructs to be expressed. A provenance container MAY contain other provenance containers.</p>
@@ -1219,7 +1219,7 @@
<li> contains a set of provenance constructs <span class="name">constructs</span>.</li>
</ul>
-<p>How general meta-information is expressed is beyond the scope of this specification, except for a few key metatypes specified in the <a href="#concept-Account">Account</a> construct.</p>
+<p>How general meta-information is expressed is beyond the scope of this specification, except for a few key metatypes specified in the <a href="#expression-Account">Account</a> construct.</p>
<div class='pending'>Asserter needs to be defined. This is <a href="http://www.w3.org/2011/prov/track/issues/51">ISSUE-51</a>.</div>
@@ -1228,7 +1228,7 @@
</section>
-<section id="concept-Account">
+<section id="expression-Account">
<h3>Account</h3>
<p>An <dfn id="dfn-Account">Account</dfn> is a special kind of provenance container forming a perspective on the world. </p>
@@ -1254,7 +1254,7 @@
</section>
-<section id="concept-Collection">
+<section id="expression-Collection">
<h3>Collection</h3>
<div class='note'>To be written in september.</div>