--- a/model/ProvenanceModel.html Mon Dec 05 11:41:53 2011 +0000
+++ b/model/ProvenanceModel.html Mon Dec 05 11:50:13 2011 +0000
@@ -1141,7 +1141,7 @@
<p>
The following note record</p>
<pre class="codeexample">
-note(ann1,[ex:color="blue", ex:screenX="20" %% xsd:integer, ex:screenY="30" %% xsd:integer])
+note(ann1,[ex:color="blue", ex:screenX=20, ex:screenY=30])
</pre>
<p>consists of a set of application-specific attribute-value pairs, intended
to help the rendering of the record it is associated with, by
@@ -1232,8 +1232,8 @@
<p>
The following generation assertions</p>
<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)
+ wasGeneratedBy(e1,a1,[ex:port="p1", ex:order=1], 2001-10-26T21:32:52)
+ wasGeneratedBy(e2,a1,[ex:port="p1", ex:order=2], 2001-10-26T10:00:00)
</pre>
<p>state the existence of two <a title="event">events</a> 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.
@@ -1928,14 +1928,14 @@
<p>A complementarity record is written <span class="name">wasComplementOf(e2,e1)</span>, where <span class="name">e1</span> and <span class="name">e2</span> are two identifiers denoting entity records.</p>
<pre class="codeexample">
-entity(rs,[ex:created="1870" %% xsd:integer])
+entity(rs,[ex:created=1870])
entity(rs_l1,[prov:location="loc2"])
entity(rs_l2,[prov:location="The Mall"])
-entity(rs_m1,[ex:membership="250" %% xsd:integer, ex:year="1900" %% xsd:integer])
-entity(rs_m2,[ex:membership="300" %% xsd:integer, ex:year="1945" %% xsd:integer])
-entity(rs_m3,[ex:membership="270" %% xsd:integer, ex:year="2010" %% xsd:integer])
+entity(rs_m1,[ex:membership=250, ex:year=1900])
+entity(rs_m2,[ex:membership=300, ex:year=1945])
+entity(rs_m3,[ex:membership=270, ex:year=2010])
wasComplementOf(rs_m3, rs_l2)
wasComplementOf(rs_m2, rs_l1)
@@ -2157,8 +2157,8 @@
<pre class="codeexample">
account(ex:acc1,
http://example.org/id,
- entity(e,[prov:type="person", ex:age="20" %% xsd:integer])
- entity(e,[prov:type="person", ex:age="30" %% xsd:integer])
+ entity(e,[prov:type="person", ex:age=20])
+ entity(e,[prov:type="person", ex:age=30])
...)
</pre>
<p>Application of <a href="#identified-entity-in-account">identified-entity-in-account</a> results in an entity record containing the attribute-value pairs <span class="name">age=20</span> and <span class="name">age=30</span>. This results in an inconsistent characterization of a person. We note that deciding whether a set of attribute-values is consistent or not is application specific and outside the scope of this specification.
@@ -2392,7 +2392,7 @@
<div class="anexample">
<p>
-The following examples respectively are the string "abc" (expressed using the convenience notation), the string "abc", the integer number '1', the integer number '1' (expressed using the convenience notation) and the IRI "http://example.org/foo".
+The following examples respectively are the string "abc" (expressed using the convenience notation), the string "abc", the integer number 1, the integer number 1 (expressed using the convenience notation) and the IRI "http://example.org/foo".
<pre class="codeexample">
"abc"
"abc" %% xsd:string