--- a/model/ProvenanceModel.html Thu Dec 08 15:56:55 2011 +0000
+++ b/model/ProvenanceModel.html Thu Dec 08 21:27:58 2011 +0000
@@ -378,7 +378,7 @@
</p>
-<p>An <dfn id="dfn-usage-event">entity generation event</dfn> is the <a>event</a> that marks the final instant of an entity's creation timespan, after which it becomes available for use.</p>
+<p>An <dfn id="dfn-generation-event">entity generation event</dfn> is the <a>event</a> that marks the final instant of an entity's creation timespan, after which it becomes available for use.</p>
<p>An <dfn id="dfn-usage-event">entity usage event</dfn> is the <a>event</a> that marks the first instant of an entity's consumption timespan by an activity.</p>
@@ -580,7 +580,7 @@
<ul>
<li>An <a title="entity record">Entity Record</a> (noted <samp>entity</samp> in the diagram, to reflect the term used in the ASN) is a representation of an <em>entity</em>.
- <li>An <a title="activity record">Activity Record</a> </strong>(noted <samp>activity</samp> in the diagram) represents an activity that has an effect on entities, namely it either <em>generates</em> or <em>uses</em> one or more entities. Usage and generation are modelled by means of the <a title="usage record">used</a> and the <a title="generation record">wasGeneratedBy</a> relationships. Activities may include not only computations, but also any other type of activity that can be described in terms of their effect on <samp>entities</samp>.
+ <li>An <a title="activity record">Activity Record</a>(noted <samp>activity</samp> in the diagram) represents an activity that has an effect on entities, namely it either <em>generates</em> or <em>uses</em> one or more entities. Usage and generation are modelled by means of the <a title="usage record">used</a> and the <a title="generation record">wasGeneratedBy</a> relationships. Activities may include not only computations, but also any other type of activity that can be described in terms of their effect on <samp>entities</samp>.
Note that multiple <samp>activities</samp> may <em>use</em> the same <samp>entity</samp>, and each activity may use multiple <samp>entities</samp>. Finally, entities can be derived from other entities, and this is specified using the <a title="derivation record">wasDerivedFrom</a> relation.</li>
<li>An <a title="agent record">Agent Record</a> represents a particular <samp>entity</samp> that can be associated to activities, meaning that it can be assigned some degree of responsibility for an <samp>activity</samp> taking place.
@@ -808,7 +808,7 @@
<img src="example-graphical.png" alt="example"/>
-</br>
+<br/>
<img src="timeline.png" alt="example"/>
</section>
@@ -1169,12 +1169,12 @@
<div class="table">
<table border="1" align="center">
+<caption>PROV-DM Core Relation Summary</caption>
<tr><td></td><td>Entity</td><td>Activity</td><td>Agent</td><td>Note</td></tr>
-<tr><td>Entity</td><td><a title="derivation record">wasDerivedFrom</a><br><a title="complementarity record">wasComplementOf</a></td><td><a title="generation record">wasGeneratedBy<a></td><td>-</td><td><a title="annotation record">hasAnnotation</a></td></tr>
+<tr><td>Entity</td><td><a title="derivation record">wasDerivedFrom</a><br><a title="complementarity record">wasComplementOf</a></td><td><a title="generation record">wasGeneratedBy</a></td><td>-</td><td><a title="annotation record">hasAnnotation</a></td></tr>
<tr><td>Activity</td><td><a title="usage record">used</a></td><td>-</td><td><a title="start record">wasStartedBy</a><br><a title="end record">wasEndedBy</a><br><a title="activity association record">wasAssociatedWith</a></td><td><a title="annotation record">hasAnnotation</a></td></tr>
<tr><td>Agent</td><td>-</td><td>-</td><td><a title="responsibility record">actedOnBehalfOf</a></td><td><a title="annotation record">hasAnnotation</a></td></tr>
<tr><td>Note</td><td>-</td><td>-</td><td>-</td><td><a title="annotation record">hasAnnotation</a></td></tr>
-<caption>PROV-DM Core Relation Summary</caption>
</table>
</div>
@@ -1640,11 +1640,11 @@
Out of the four possibilities, PROV-DM offers three forms of derivation, while the fourth one is not meaningful. The following table summarises names for the three kinds of derivation, which we then explain.</p>
<div class="table">
<table border="1" align="center">
+<caption>PROV-DM Derivation Type Summary</caption>
<tr><td colspan=2 rowspan=2></td><td colspan=2>precision axis</td></tr>
<tr><td>precise</td><td>imprecise</td></tr>
<tr><td rowspan=2>activity<br>axis</td><td>one activity</td><td><a>precise-1 derivation record</a></td><td><a>imprecise-1 derivation record</a></td></tr>
<tr><td>n activities</td><td>---</td><td><a>imprecise-n derivation record</a></td></tr>
-<caption>PROV-DM Derivation Type Summary</caption>
</table>
</div>
@@ -1781,7 +1781,7 @@
<p>
<p>If a derivation record holds for <span class="name">e2</span> and <span class="name">e1</span>, then
this means that the entity represented by entity record identified by <span class="name">e1</span> has an influence on the entity represented entity record identified by <span class="name">e2</span>,
- which at the minimum implies temporal ordering, specified as follows.</p>
+ which at the minimum implies temporal ordering, specified as follows.
First, we consider one-activity derivations.</p>
<div class='interpretation' id='derivation-usage-generation-ordering'>Given an activity record identified by <span class="name">a</span>, entity records identified by <span class="name">e1</span> and <span class="name">e2</span>, generation record identified by <span class="name">g2</span>, and usage record identified by <span class="name">u1</span>, <span class='conditional'>if</span> the record <span class="name">wasDerivedFrom(e2,e1,a,g2,u1,attrs)</span>
@@ -2355,7 +2355,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>. </p>
+<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>
<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>
@@ -2373,7 +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>. </p>
+<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>
</section>
@@ -2412,12 +2412,12 @@
<p>In PROV-ASN, a Literal's text matches the <span class="nonterminal">Literal</span> production of the grammar defined in this specification document.</p>
<div class='grammar'>
-<span class="nonterminal">Literal</span> ::= <span class="nonterminal">typedLiteral</span> | <span class="nonterminal">convenienceNotation</span> </br>
+<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">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>
-<span class="nonterminal">quotedString</span> ::= <em>a finite sequence of characters in which " (U+22) and \ (U+5C) occur only in pairs of the form \" (U+5C, U+22) and \\ (U+5C, U+5C), enclosed in a pair of " (U+22) characters</em></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/>
+<span class="nonterminal">quotedString</span> ::= <em>a finite sequence of characters in which " (U+22) and \ (U+5C) occur only in pairs of the form \" (U+5C, U+22) and \\ (U+5C, U+5C), enclosed in a pair of " (U+22) characters</em><br/>
<span class="nonterminal">intLiteral</span> ::= <em>a finite-length sequence of decimal digits (#x30-#x39) with an optional leading negative sign (-)</em>
</div>
@@ -2479,7 +2479,7 @@
<p>An <dfn id="dfn-asserter">asserter</dfn> is a creator of PROV-DM records. An asserter is denoted by an IRI. Such IRI has no specific interpretation in the context of PROV-DM.</p>
<div class='grammar'>
-<span class="nonterminal">asserter</span> ::= <span class="nonterminal">IRI</span></br>
+<span class="nonterminal">asserter</span> ::= <span class="nonterminal">IRI</span><br/>
<span class="nonterminal">IRI</span> ::= <em>an IRI compatible with production IRI in [[!IRI]], enclosed in a pair of < (U+3C) and > (U+3E) characters </em>
</div>
@@ -2713,7 +2713,7 @@
<p>A traceability record can be inferred from existing relations, or can be asserted stating that such a dependency path exists without the asserter knowing its individual steps, as expressed by the following constraints.
-<div class='constraint' id='traceability inference'>
+<div class='constraint' id='traceability-inference'>
Given two identifiers <span class="name">e2</span> and <span class="name">e1</span> identifying entity records,
the following statements hold:
@@ -2727,7 +2727,7 @@
</ol>
</div>
-<div class='constraint' id='traceability assertion'>
+<div class='constraint' id='traceability-assertion'>
<span class='conditional'>If</span> the record <span class="name">tracedTo(r2,r1)</span> holds
for two identifiers <span class="name">r2</span> and <span class="name">r1</span> identifying entity records,
<span class='conditional'>then</span> there exist
@@ -2807,7 +2807,7 @@
<p> An information flow ordering record is formally defined as follows.</p>
-<div class='constraint' id='wasInformedBy Definition'>Given two activity records identified by <span class="name">a1</span> and <span class="name">a2</span>,
+<div class='constraint' id='wasInformedBy-Definition'>Given two activity records identified by <span class="name">a1</span> and <span class="name">a2</span>,
the record <span class="name">wasInformedBy(a2,a1)</span>
holds, <span class='conditional'>if and only if</span>
there is an entity record identified by <span class="name">e</span> and sets of attribute-value pairs <span class="name">attrs1</span> and <span class="name">attrs2</span>,