--- a/model/ProvenanceModel.html	Thu Aug 04 14:20:13 2011 +0100
+++ b/model/ProvenanceModel.html	Thu Aug 04 14:34:48 2011 +0100
@@ -166,7 +166,7 @@
 
 In this section, the example is encoded according to the Provenance data model (specified in section <a href="\data-model-concepts">concepts</a>), expressed in the Abstract Syntax Notation. Details about the Abstract Syntax Notation can be found in <a href="'#ASN-convention'">appendix</a>.
 <p>
-Entities (construct described at <a href="#concept-Entity">entity</a>). The file in its various forms and its copies are modelled as entities.
+Entities (construct described in <a href="#concept-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: "" ])
@@ -195,7 +195,7 @@
 </p>
 
 <p>
-Derivations (construct described at <a href="#concept-Derivation">derivation</a>): derivations express that an entity is derived from another.
+Derivations (construct described in <a href="#concept-Derivation">Section Derivation</a>): derivations express that an entity is derived from another.
 <pre>
 isDerivedFrom(e2,e1)
 isDerivedFrom(e3,e2)
@@ -205,7 +205,7 @@
 </p>
 
 <p>
-Process Executions (construct described at <a href="#concept-ProcessExecution">process execution</a>): process execution represents an activity in the scenario.
+Process Executions (construct described in <a href="#concept-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)
@@ -217,33 +217,34 @@
 </p>
 
 <p>
-Generations (construct described at <a href="#concept-Generation">generation</a>): generation is the event at which a file is created in a specific form.
+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 various entities generated by a given 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.
 <pre>
-isGeneratedBy(e0,pe0,out)     
-isGeneratedBy(e1,pe0,out)     
+isGeneratedBy(e0,pe0,outFile)     
+isGeneratedBy(e1,pe0,outContent)     
 isGeneratedBy(e2,pe1,out)     
 isGeneratedBy(e3,pe3,out)     
-isGeneratedBy(e4,pe2,out)     
-isGeneratedBy(e5,pe4,out)     
+isGeneratedBy(e4,pe2,attachment)     
+isGeneratedBy(e5,pe4,attachment)     
 isGeneratedBy(e6,pe5,out)     
 </pre>
 </p>
 
 
 <p>
-Uses (construct described at <a href="#concept-Use">use</a>): use is the event by which a file is read by a process execution.
+Uses (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.
 <pre>
 uses(pe1,e1,in)
 uses(pe3,e2,in)
 uses(pe2,e2,in)
 uses(pe4,e3,in)
+uses(pe5,e3,fileIn)
 </pre>
 </p>
 
 
 
 <p>
-isComplementOf:   (this relation is described at <a href="#concept-IVP-of">isComplementOf</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.
+isComplementOf:   (this relation is described in <a href="#concept-IVP-of">Section isComplementOf</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>
 isComplementOf(e1,e0)
 isComplementOf(e2,e0)
@@ -254,7 +255,7 @@
 
 
 <p>
-Agents (construct described at <a href="#concept-Agent">agent</a>): in the provenance model, the various users are represented as agents, themselves being a type of entity.
+Agents (construct described at <a href="#concept-Agent">Section Agent</a>): in the provenance model, the various users are represented as agents, themselves being a type of entity.
 <pre>
 entity(e7, [ type: "Person", name: "Alice" ])
 agent(e7)
@@ -275,13 +276,13 @@
 
 
 <p>
-Control (construct described at <a href="#concept-Control">control</a>):
+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.
 <pre>
-isControlledBy(pe0,e7,"creator")
-isControlledBy(pe1,e8,"author")
-isControlledBy(pe2,e9, "communicator")
-isControlledBy(pe3,e10,"author")
-isControlledBy(pe4,e11, "communicator")
+isControlledBy(pe0,e7, creator)
+isControlledBy(pe1,e8, author)
+isControlledBy(pe2,e9, communicator)
+isControlledBy(pe3,e10, author)
+isControlledBy(pe4,e11, communicator)
 </pre>
 </p>
 </section>