--- a/model/ProvenanceModel.html Thu Dec 08 21:27:58 2011 +0000
+++ b/model/ProvenanceModel.html Thu Dec 08 21:31:54 2011 +0000
@@ -178,7 +178,7 @@
<div class="buttonpanel">
-<form action=""><p>
+<form action="#"><p>
<input id="hide-bnf" onclick="set_display_by_class('div','grammar','none'); set_display_by_id('hide-bnf','none'); set_display_by_id('show-bnf','');" type="button" value="Hide Grammar" />
<input id="show-bnf" onclick="set_display_by_class('div','grammar',''); set_display_by_id('hide-bnf',''); set_display_by_id('show-bnf','none');" style="display: none" type="button" value="Show Grammar" />
<input id="hide-examples" onclick="set_display_by_class('div','anexample','none'); set_display_by_id('hide-examples','none'); set_display_by_id('show-examples','');" type="button" value="Hide Examples" />
@@ -1941,8 +1941,8 @@
An assertion "wasComplementOf(B,A)" holds over the temporal intersection of A and B, <span class='conditional'>only if</span>:
<ol>
<li> if a mapping can be established from an attribute X of entity record identified by B to an attribute Y of entity record identified by A, then the values of A and B must be consistent with that mapping;</li>
- <li>entity record identified by B has some attribute that entity record identified by A does not have.
-</li></ol>
+<li>entity record identified by B has some attribute that entity record identified by A does not have.</li>
+</ol>
</div>
<p>The complementarity relation is not transitive. Let us consider identifiers <span class="name">e1</span>, <span class="name">e2</span>, and <span class="name">e3</span> identifying three entity records such that
@@ -1979,7 +1979,6 @@
An entity record identifier can optionally be accompanied by an account identifier. When this is the case, it becomes possible to link two entity record identifiers that are appear in different accounts. (In particular, the entity record identifiers in two different account are allowed to be the same.). When account identifiers are not available, then the linking of entity records through complementarity can only take place within the scope of a single account.
</p>
-</p>
<div class="anexample">
<p>In the following example, the same description of the Royal Society is structured according to two different accounts. In the second account, we find a complementarity record linking <span class="name">rs_m1</span> in account <span class="name">ex:acc2</span> to
@@ -2355,7 +2354,7 @@
<p>The PROV data model introduces a fixed set of attributes in the <a href="#prov-dm-namespace">PROV-DM namespace</a>:</p>
<ul>
-<li> The attribute <dfn id="dfn-role"><span class="name">prov:role</span></dfn> denotes the function of an entity with respect to an activity, in the context of a usage, generation, activity association, start, end record. The value associated with a <span class="name">prov:role</span> attribute MUST be conformant with <span class="nonterminal">Literal</span>. </li>
+<li> The attribute <dfn id="dfn-role"><span class="name">prov:role</span></dfn> denotes the function of an entity with respect to an activity, in the context of a usage, generation, activity association, start, end record. The value associated with a <span class="name">prov:role</span> attribute MUST be conformant with <span class="nonterminal">Literal</span>.
<div class="anexample">
<p>The following start record describes the role of the agent identified by <span class="name">ag</span> in this start relation with activity <span class="name">a</span>. </p>
@@ -2363,8 +2362,9 @@
wasStartedBy(a,ag, [prov:role="program-operator"])
</pre>
</div>
-
-<li> The attribute <dfn id="dfn-type"><span class="name">prov:type</span></dfn> provides further typing information for the element or relation asserted in the record. The value associated with a <span class="name">prov:type</span> attribute MUST be conformant with <span class="nonterminal">Literal</span>. </p>
+ </li>
+
+<li> The attribute <dfn id="dfn-type"><span class="name">prov:type</span></dfn> provides further typing information for the element or relation asserted in the record. The value associated with a <span class="name">prov:type</span> attribute MUST be conformant with <span class="nonterminal">Literal</span>.
<div class="anexample">
<p>The following record declares an agent of type software agent</p>
@@ -2373,6 +2373,7 @@
</pre>
</div>
+
<li> The attribute <dfn id="dfn-steps"><span class="name">prov:steps</span></dfn> defines the level of precision associated with a derivation record. The value associated with a <span class="name">prov:steps</span> attribute MUST be <span class="name">"1"</span> or <span class="name">"n"</span>. </li>
</ul>
@@ -2413,7 +2414,7 @@
<div class='grammar'>
<span class="nonterminal">Literal</span> ::= <span class="nonterminal">typedLiteral</span> | <span class="nonterminal">convenienceNotation</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">qualifiedName</span><br/>
<span class="nonterminal">convenienceNotation</span> ::= <span class="nonterminal">stringLiteral</span> | <span class="nonterminal">intLiteral</span><br/>
<span class="nonterminal">stringLiteral</span> ::= <span class="nonterminal">quotedString</span><br/>