--- a/model/ProvenanceModel.html Wed Nov 16 12:14:08 2011 -0500
+++ b/model/ProvenanceModel.html Wed Nov 16 17:28:35 2011 +0000
@@ -1010,27 +1010,25 @@
</div>
-
-<div class='example'>
+<p>
+A generation record's id is OPTIONAL. It MUST be used when annotating generation records (see Section <a href="#record-annotationAssociation">Annotation Association Record</a>) or when defining derivations (see <a href="#pe-linked-derivationRecord"><span class='nonterminal'>pe-linked-derivationRecord</span></a>).
+</p>
+
+
+<div class='anexample'>
<p>
The following generation assertions</p>
-<pre class="example">
- wasGeneratedBy(e1,pe1,[ex:port="p1", ex:order=1),t1)
- wasGeneratedBy(e2,pe1,[ex:port="p1", ex:order=2),t2)
+<pre class="codeexample">
+ wasGeneratedBy(e1,a1,[ex:port="p1", ex:order="1" %% xsd:integer), 2001-10-26T21:32:52)
+ wasGeneratedBy(e2,a1,[ex:port="p1", ex:order="2" %% xsd:integer), 2001-10-26T10:00:00)
</pre>
-<p>state the existence of two events in the world (with respective times <span class="name">t1</span> and <span class="name">t2</span>), at which new entities, represented by entity records identified by <span class="name">e1</span> and <span class="name">e2</span>, are created by an activity, itself represented by an activity record identified by <span class="name">pe1</span>.
+<p>state the existence of two events in the world (with respective times <span class="name">2001-10-26T21:32:52</span> and <span class="name">2001-10-26T10:00:00</span>), at which new entities, represented by entity records identified by <span class="name">e1</span> and <span class="name">e2</span>, are created by an activity, itself represented by an activity record identified by <span class="name">a1</span>.
The first one is available as the first value on port p1, whereas the other is the second value on port p1. The semantics of <span class="name">port</span> and <span class="name">order</span> in these records are application specific.
</p>
</div>
-<p>
-A generation record's id is OPTIONAL. It MUST be used when annotating generation records (see Section <a href="#record-annotationAssociation">Annotation Association Record</a>) or when defining derivations (see <a href="#pe-linked-derivationRecord"><span class='nonterminal'>pe-linked-derivationRecord</span></a>).
-</p>
-
-
-
<p>The assertion of a generation event implies ordering of events in the world.</p>
@@ -1091,21 +1089,22 @@
</div>
-
-
-<p>The following usage records</p>
-<pre class="example">
- used(pe1,e1,[ex:parameter="p1"),t1)
- used(pe1,e2,[ex:parameter="p2"),t2)
-</pre>
-<p>state that the activity, represented by the activity record identified by <span class="name">pe1</span>, consumed two entities, represented by entity records identified by <span class="name">e1</span> and <span class="name">e2</span>, at times <span class="name">t1</span> and <span class="name">t2</span>, respectively; the first one was found as the value of parameter <span class="name">p1</span>, whereas the second was found as value of parameter <span class="name">p2</span>. The semantics of <span class="name">parameter</span> in these records is application specific.</p>
-
-
<p>
A usage record's id is OPTIONAL, but comes handy when annotating usage records (see Section <a href="#record-annotationAssociation">Annotation Association Record</a>) or when defining derivations (see <a href="#pe-linked-derivationRecord"><span class='nonterminal'>pe-linked-derivationRecord</span></a>).
</p>
+<div class='anexample'>
+<p>The following usage records</p>
+<pre class="codeexample">
+ used(a1,e1,[ex:parameter="p1"),2011-11-16T16:00:00)
+ used(a1,e2,[ex:parameter="p2"),2011-11-16T16:00:01)
+</pre>
+<p>state that the activity, represented by the activity record identified by <span class="name">a1</span>, consumed two entities, represented by entity records identified by <span class="name">e1</span> and <span class="name">e2</span>, at times <span class="name">2011-11-16T16:00:00</span> and <span class="name">2011-11-16T16:00:01</span>, respectively; the first one was found as the value of parameter <span class="name">p1</span>, whereas the second was found as value of parameter <span class="name">p2</span>. The semantics of <span class="name">parameter</span> in these records is application specific.</p>
+</div>
+
+
+
<p>A reference to a given entity record MAY appear in multiple usage records that share
@@ -1958,7 +1957,7 @@
<div class='grammar'>
<span class="nonterminal">Literal</span> := <span class="nonterminal">typedLiteral</span> | <span class="nonterminal">stringConvenienceNotation</span> </br>
-<span class="nonterminal">typedLiteral</span> := <span class="nonterminal">quotedString</span> <span class="name">^^</span> <span class="nonterminal">Datatype</span></br>
+<span class="nonterminal">typedLiteral</span> := <span class="nonterminal">quotedString</span> <span class="name">%%</span> <span class="nonterminal">Datatype</span></br>
<span class="nonterminal">Datatype</span> := <span class="nonterminal">IRI</span></br>
</br>
<span class="nonterminal">stringConvenienceNotation</span> := <span class="nonterminal">stringLiteralNoLanguage</span> | <span class="nonterminal">stringLiteralWithLanguage</span></br>
@@ -2673,6 +2672,7 @@
<section class="appendix">
<h2>Changes Since Previous Version</h2>
<ul>
+<li>11/16/11: Updated examples for usage and generation record.</li>
<li>11/16/11: Renamed use record into usage record.</li>
<li>11/16/11: Removed constraint generation-affects-attributes.</li>
<li>11/16/11: Removed constraint use-attributes.</li>