--- a/model/ProvenanceModel.html Wed Oct 05 21:38:44 2011 +0100
+++ b/model/ProvenanceModel.html Wed Oct 05 21:47:06 2011 +0100
@@ -1696,13 +1696,13 @@
<section id="expression-Account">
<h3>Account</h3>
-<p>In PROV-DM, an <dfn id="dfn-Account">account expression</dfn> is a wrapper of expressions with a dual purpose:
+<p>In PROV-DM, an <dfn id="dfn-Account">account expression</dfn> is a wrapper of expressions with a dual purpose: </p>
<ul>
<li> It is the mechanism by which attribution of provenance can be assserted; it allows asserters to bundle up their assertions, and assert suitable attribution;
<li> It provides a scoping mechanism for expression identifiers and for some contraints (such as
<a href="#generation-unicity">generation-unicity</a> and <a href="#derivation-use">derivation-use</a>).
</ul>
- </p>
+
<p>In PROV-ASN, an account expression's text matches the <span class="nonterminal">accountExpression</span> production of the grammar defined in this specification document.</p>
@@ -1718,19 +1718,19 @@
<span class="name">)</span>
</div>
-<p>An instance of an account expression, noted <span class="name">account(id, uri, exprs)</span> in PROV-ASN:
+<p>An instance of an account expression, noted <span class="name">account(id, uri, exprs)</span> in PROV-ASN:</p>
<ul>
<li> contains an identifier <span class="name">id</span> to identify this account;</li>
<li> contains an asserter identified by URI denoted by <span class="name">uri</span>;</li>
<li> contains a <em>set</em> of provenance expressions denoted by <span class="name">exprs</span>.</li>
</ul>
-</p>
+
<div class='note'>
Currently, the non-terminal <span class="nonterminal">asserter</span> is defined as URI. We may want the asserter to be an agent instead, and therefore use PROV-DM to express the provenance of PROV-DM assertions. The editors seek inputs on how to resolve this issue. </div>
<p>
-The following account expression
+The following account expression</p>
<pre class="example">
account(acc0,
http://x.com/asserter,
@@ -1744,7 +1744,7 @@
...
wasControlledBy(pe4,a5, qualifier(role="communicator")) )
</pre>
-contains the set of provenance expressions of section <a href="#example-prov-asn-encoding">example-prov-asn-encoding</a>, is asserted by agent <span class="name">http://x.com/asserter</span>, and is identified by identifier <span class="name">acc0</span>.
+<p>contains the set of provenance expressions of section <a href="#example-prov-asn-encoding">example-prov-asn-encoding</a>, is asserted by agent <span class="name">http://x.com/asserter</span>, and is identified by identifier <span class="name">acc0</span>.
</p>
<p>Account expressions constitue a scope for identifiers. An identifier within the scope of an account is intended to denote a single expression. However, nothing prevents an asserter from asserting an account containing, for example, multiple entity expressions with a same identifier but different attribute-values. In that case, they should be understood as a single entity expression with this identifier and the union of all attributes values, as formalized in <a href="#identified-entity-in-account">identified-entity-in-account</a>.</p>
@@ -1757,7 +1757,7 @@
<p>Whilst constraint <a href="#identified-entity-in-account">identified-entity-in-account</a> specifies how to understand multiple entity expressions with a same identifier within a given account, it does not guarantee that the entity expression formed with the union of all attribute-value pairs is consistent. Indeed, a given attribute may be assigned multiple values, resulting in an inconsistent entity expression, as illustrated by the following example.</p>
<p>
-In the following account expression, we find two entity expressions with a same identifier <span class="name">e</span>.
+In the following account expression, we find two entity expressions with a same identifier <span class="name">e</span>.</p>
<pre class="example">
account(acc1,
http://x.com/id,
@@ -1765,7 +1765,7 @@
entity(e,[type="person",age=30])
...)
</pre>
-Application of <a href="#identified-entity-in-account">identified-entity-in-account</a> results in an entity expression 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.
+<p>Application of <a href="#identified-entity-in-account">identified-entity-in-account</a> results in an entity expression 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.
</p>
<p>Account expressions can be nested since an account expression can occur among the expressions being wrapped by another account. </p>
@@ -1785,7 +1785,7 @@
<p>
-Indeed, let us consider another account expression
+Indeed, let us consider another account expression</p>
<pre class="example">
account(acc2,
http://x.com/asserter2,
@@ -1796,12 +1796,12 @@
wasGeneratedBy(e0,pe1,outFile)
... )
</pre>
-with identifier <span class="name">acc2</span>, containing assertions by asserter by <span class="name">http://x.com/asserter2</span> stating that thing represented by entity expression identified by <span class="name">e0</span> was generated by an activity represented by process execution expression identified by <span class="name">pe1</span> instead of <span class="name">pe0</span> in the previous account <span class="name">acc0</span>. If accounts <span class="name">acc0</span> and <span class="name">acc2</span> are merged together, the resulting set of expressions violates <a href="#generation-unicity">generation-unicity</a>.</p>
+<p>with identifier <span class="name">acc2</span>, containing assertions by asserter by <span class="name">http://x.com/asserter2</span> stating that thing represented by entity expression identified by <span class="name">e0</span> was generated by an activity represented by process execution expression identified by <span class="name">pe1</span> instead of <span class="name">pe0</span> in the previous account <span class="name">acc0</span>. If accounts <span class="name">acc0</span> and <span class="name">acc2</span> are merged together, the resulting set of expressions violates <a href="#generation-unicity">generation-unicity</a>.</p>
<p>Account expressions constitue a scope for identifiers. Since accounts can be nested, their scope can also be nested; thus, the scope of identifiers should be understood in the context of such nested scopes. When an expression with an identifier occurs directly within an account, then its identifier denotes this expression in the scope of this account, except in sub-accounts where expressions with the same identifier occur. </p>
<p>
-The following account expression is inspired from section <a href="#example-prov-asn-encoding">example-prov-asn-encoding</a>. This account, identified by <span class="name">acc3</span>, declares entity expression identified by <span class="name">e0</span>, which is being referred to in the nested account <span class="name">acc4</span>. The scope of identifier <span class="name">e0</span> is account <span class="name">acc3</span>, including subaccount <span class="name">acc4</span>.
+The following account expression is inspired from section <a href="#example-prov-asn-encoding">example-prov-asn-encoding</a>. This account, identified by <span class="name">acc3</span>, declares entity expression identified by <span class="name">e0</span>, which is being referred to in the nested account <span class="name">acc4</span>. The scope of identifier <span class="name">e0</span> is account <span class="name">acc3</span>, including subaccount <span class="name">acc4</span>.</p>
<pre class="example">
account(acc3,
http://x.com/asserter1,
@@ -1815,7 +1815,7 @@
wasGeneratedBy(e1,pe0,outFile)
isComplement(e1,e0)))
</pre>
-Alternatively, a process execution expression identified by <span class="name">pe0</span> occurs in each of the two accounts. Therefore, each process execution expression is asserted in a separate scope, and therefore may represent different activities in the world.
+<p>Alternatively, a process execution expression identified by <span class="name">pe0</span> occurs in each of the two accounts. Therefore, each process execution expression is asserted in a separate scope, and therefore may represent different activities in the world.
</p>
<p>The account expression is the hook by which further meta information can be expressed about provenance, such as asserter, time of creation, signatures. How general meta-information is expressed is beyond the scope of this specification, except for asserters.</p>
@@ -1855,13 +1855,13 @@
<p>All the expressions in <span class="name">exprs</span> are implictly wrapped in a default account, scoping all the identifiers they declare directly, and constituting a toplevel account, in the hierarchy of accounts.</p>
<p>
-The following container
+The following container </p>
<pre class="example">
container([x http://x.com],[acc1,acc2]
account(acc1,http://x.com/asserter1,...)
account(acc2,http://x.com/asserter1,...))
</pre>
- illustrates how two accounts with identifiers <span class="name">acc1</span> and <span class="name">acc2</span> can be returned in a PROV-ASN serialization of the provenance of something.
+<p> illustrates how two accounts with identifiers <span class="name">acc1</span> and <span class="name">acc2</span> can be returned in a PROV-ASN serialization of the provenance of something.
</p>
@@ -1934,22 +1934,22 @@
</div>
<p>Qualifiers are used in determining the exact source and destination of a <span class="nonterminal">pe-linked-derivationExpression</span>. Hence,
-if one wants to express a <span class="nonterminal">pe-linked-derivationExpression</span> referring to an entity expression and a process execution expression,
+if one wants to express a <span class="nonterminal">pe-linked-derivationExpression</span> referring to an entity expression and a process execution expression, then:</p>
<ul>
<li>the useQualifier MUST be unique among the qualifiers occuring in use expressions for this process execution expression;
<li>the generationQualifier MUST be unique among the qualifiers occuring in generation expressions for this process execution expression.
</ul>
-</p>
+
<p>The PROV data model introduces a specific qualifier <span class="name">role</span> to denote the function of a characterized thing with respect to an activity, in the context of a use/generation/control relation. The value associated with a <span class="name">role</span> attribute MUST be conformant with <span class="nonterminal">Literal</span>. </p>
<p>
-The following control expression qualifies the role of the agent identified by <span class="name">a5</span> in this control relation.
+The following control expression qualifies the role of the agent identified by <span class="name">a5</span> in this control relation. </p>
<pre class="example">
wasControlledBy(pe4,a5, qualifier(role="communicator"))
</pre>
-</p>
+
@@ -2045,7 +2045,7 @@
<h4>Event Ordering</h4>
-<p><dfn id="dfn-follows">Follows</dfn> is a partial order between events, indicating that an event occurs after another. For convenience, <dfn id="dfn-follows">precedes</dfn> is defined as the symmetric of follows. </p>
+<p><dfn id="dfn-follows">Follows</dfn> is a partial order between events, indicating that an event occurs after another. For convenience, <dfn id="dfn-precedes">precedes</dfn> is defined as the symmetric of follows. </p>
<p>This specification introduces inference rules allowing such event ordering to be inferred from provenance constructs.</p>
</section>
@@ -2130,7 +2130,7 @@
<ul>
<li> Attributes are constructs of the data model that allow representations of aspects of the world's things and activities to be expressed. Applications are free to introduce application-specific attributes, according to their perspective on the world. Attributes for a given application can be distinguished by qualifying them with a prefix denoting a namespace declared in a namespace declaration.
-<p>The PROV DM namespace (TBD) declares a set of reserved attributes: <tt>type</tt>, <tt>location</tt>.</li>
+<p>The PROV DM namespace (TBD) declares a set of reserved attributes: <span class="name">type</span>, <span class="name">location</span>.</li>
<li>Annotation expressions allow arbitrary metadata to be associated with identifiable expressions of PROV-DM. Annotation expressions consist of name-value pairs. Like attributes, names are qualified by a namespace.</li>
@@ -2139,7 +2139,7 @@
They consist of ordered sequence of name-value pairs. Such names
are also qualified by namespaces.</li>
-<p>The PROV DM namespace (TBD) declares a reserved qualifier: <tt>role</tt>.</li>
+<p>The PROV DM namespace (TBD) declares a reserved qualifier: <span class="name">role</span>.</li>
<li>Namespaces allow attributes and names to be qualified. </li>
@@ -2148,7 +2148,7 @@
<p>The PROV data model is designed to be application and technology independent, but specializations of PROV-DM are welcome and encouraged. To ensure inter-operability, specializations of the PROV data model that exploit the extensibility points summarized in this section MUST preserve the semantics specified in this document. For instance, a qualified attribute on a domain specific entity expression MUST represent an aspect of a characterized thing and this aspect MUST remain unchanged during the characterization's interval of this entity expression.</p>
-</p>
+
</section>
@@ -2220,14 +2220,14 @@
<br/>
</div>
- Expression: <span class="name">wasAddedTo_Coll(c2,c1)</span> (resp. <span class="name">wasRemovedFrom_Coll(c2,c1)</span>) denotes that collection <span class="name">c2</span> is an updated version of collection <span class="name">c1</span>, following an insertion (resp. deletion) operation.<p/>
+<p> Expression: <span class="name">wasAddedTo_Coll(c2,c1)</span> (resp. <span class="name">wasRemovedFrom_Coll(c2,c1)</span>) denotes that collection <span class="name">c2</span> is an updated version of collection <span class="name">c1</span>, following an insertion (resp. deletion) operation.</p>
- Expression: <span class="name">wasAddedTo_Key(c,k)</span> (resp. <span class="name">wasRemovedFrom_Key(c,k)</span>) denotes that collection <span class="name">c</span> had
- a new value with key <span class="name">k</span> added to (resp. removed from) it.<p/>
+<p> Expression: <span class="name">wasAddedTo_Key(c,k)</span> (resp. <span class="name">wasRemovedFrom_Key(c,k)</span>) denotes that collection <span class="name">c</span> had
+ a new value with key <span class="name">k</span> added to (resp. removed from) it.</p>
- Expression: <span class="name">wasAddedTo_Entity(c,e)</span> denotes that collection <span class="name">c</span> had entity
+<p> Expression: <span class="name">wasAddedTo_Entity(c,e)</span> denotes that collection <span class="name">c</span> had entity
<span class="name">e</span> added to it.
- <p/>
+</p>
<pre class="example">
@@ -2247,16 +2247,16 @@
</pre>
The corresponding graphical representation is shown below.<p/>
-<img src="collections.png" align="center"/>
-
-
-<p/> With these assertions:
+<img src="collections.png" style="align=center;" alt="collections"/>
+
+
+<p> With these assertions:</p>
<ul>
<li><span class="name">c2</span> is known to contain the key-value pair <span class="name">(k1,e1)</span>
<li><span class="name">c3</span> is known to contain pairs <span class="name">(k1,e1)</span> and <span class="name">(k2,e2)</span>.
<li><span class="name">c4</span> is known <em>not</em> to contain pair <span class="name">(k1,e1)</span> and to contain pair <span class="name">(k2,e2)</span>.
</ul>
-</p>
+
</section>
@@ -2276,14 +2276,14 @@
Quotation represents the repeating or copying of some part of a characterized thing.
-<p> An assertion wasQuoteOf, noted <span class="name"> wasQuoteOf(e2,e1,ag,ag2)</span>:
+<p> An assertion wasQuoteOf, noted <span class="name"> wasQuoteOf(e2,e1,ag,ag2)</span>:</p>
<ul>
<li>refers to an entity <span class="name">e2</span>, denoting the quote;
<li>refers to an entity <span class="name">e1</span>, denoting the entity being quoted;
<li>MAY refer to an agent who is doing the quoting <span class="name">ag</span>;
<li>MAY refer to the agent that is quoted <span class="name">ag</span>
</ul>
-</p>
+
<p>
<span class="name">wasQuoteOf</span> is a sub-relation of <span class="name">wasRevisionOf</span>
</p>
@@ -2295,12 +2295,12 @@
Attribution represents that a characterized thing is ascribed to an agent.
-<p> An assertion wasAttributedTo, noted <span class="name"> wasAttributedTo(e1,ag)</span>:
+<p> An assertion wasAttributedTo, noted <span class="name"> wasAttributedTo(e1,ag)</span>:</p>
<ul>
<li>refers to an entity <span class="name">e2</span>, denoting the entity;
<li>refers to an agent who the entity is attributed to <span class="name">ag</span>.
</ul>
-</p>
+
<p>
<span class="name">wasQuoteOf</span> is a strict sub-relation of <span class="name">wasEventuallyDerivedFrom</span>
</p>
@@ -2312,12 +2312,12 @@
<h3>Summary</h3>
Represents a characterized thing that is a synopsis or abbreviation of another entity.
-<p> An assertion wasSummaryOf, noted <span class="name"> wasSummaryOf(e2,e1)</span>:
+<p> An assertion wasSummaryOf, noted <span class="name"> wasSummaryOf(e2,e1)</span>:</p>
<ul>
<li>refers to an entity <span class="name">e2</span>, denoting the summary;
<li>refers to an entity <span class="name">e1</span>, denoting the entity being summarized.
</ul>
-</p>
+
<p>
<span class="name">wasSummaryOf</span> is a strict sub-relation of <span class="name">wasEventuallyDerivedFrom</span>
</p>
@@ -2330,12 +2330,12 @@
Represents a characterized thing in which another characterized thing first appeared.
-<p> An assertion hasOriginalSource, noted <span class="name"> hasOriginalSource(e2,e1)</span>:
+<p> An assertion hasOriginalSource, noted <span class="name"> hasOriginalSource(e2,e1)</span>:</p>
<ul>
<li>refers to an entity <span class="name">e2</span>, denoting the entity that first appeared;
<li>refers to an entity <span class="name">e1</span>, denoting the entity where that entity first appeared.
</ul>
-</p>
+
<p>
<span class="name">hasOriginalSource</span> is a strict sub-relation of <span class="name">wasEventuallyDerivedFrom</span>
</p>