--- a/model/ProvenanceModel.html Thu Oct 06 12:54:06 2011 +0100
+++ b/model/ProvenanceModel.html Thu Oct 06 13:50:44 2011 +0100
@@ -779,7 +779,7 @@
<p>Such start and end times constitute <em>attributes</em> of an activity, where the interpretation of attribute in the context of a process execution expression is the same as the interpretation of attribute for entity expression: a process execution expression's attribute remains constant for the duration of the activity it represents. Further characteristics of the activity in the world can be represented by other attribute-value pairs, which MUST also remain unchanged during the activity duration.</p>
-<p> An instance of a process execution expression, noted <span class="name">processExecution(id, rl, st, et, [ attr1=val1, ...])</span> in PROV-ASN:</p>
+<p> An instance of a process execution expression, written <span class="name">processExecution(id, rl, st, et, [ attr1=val1, ...])</span> in PROV-ASN:</p>
<ul>
<li> contains an identifier <span class="name">id</span>;</li>
<li> MAY contain a <a href="#expression-RecipeLink">recipe link</a> <span class="name">rl</span>, which consists of a domain specific description of the activity;</li>
@@ -818,7 +818,7 @@
-<p>An <dfn id="dfn-Agent">agent expression</dfn> is a representation a characterized thing capable of
+<p>An <dfn id="dfn-Agent">agent expression</dfn> is a representation of a characterized thing capable of
activity.</p>
<p>In PROV-ASN, an agent expression's text matches the <span class="nonterminal">agentExpression</span> production of the grammar defined in this specification document.
@@ -852,7 +852,7 @@
entity(e2) and wasControlledBy(pe,e2,qualifier(role="author"))
</pre>
-<p>the entity expression identified by <span class="name">e1</span> is accompanied by an explicit assertion of an agent expression, and this assertion holds irrespective of process executions it may be involved in. On the contrary, from the entity expression identified by <span class="name">e2</span>, one can inferred an agent expression, as per the following inference.
+<p>the entity expression identified by <span class="name">e1</span> is accompanied by an explicit assertion of an agent expression, and this assertion holds irrespective of process executions it may be involved in. On the other hand, from the entity expression identified by <span class="name">e2</span>, one can infer an agent expression, as per the following inference.
</p>
<div class='constraint' id='control-agent'>
@@ -911,7 +911,7 @@
</p>
<p>
-Name-value pairs occurring in annotations differ from attribute-value pairs (occurring in entity expressions and process execution expressions). Attribute-value pairs MUST be a representation of something in the world, which remain constant for the duration of the characterization interval (for entity expression) or the activity duration (for process execution expressions). It is OPTIONAL for name-value pairs to be representations of something in the world. If they are a representation of something in the world, then it MAY change value for the corresponding duration. If name-value pairs are a representation of something in the world that does not change, they are not regarded as determining characteristics of a characterized thing or activity, for the purpose of provenance. Indeed, it is not expectede that provenance would contain an explanation for these attribute-values.
+Name-value pairs occurring in annotations differ from attribute-value pairs (occurring in entity expressions and process execution expressions). Attribute-value pairs MUST be a representation of something in the world, which remain constant for the duration of the characterization interval (for entity expression) or the activity duration (for process execution expressions). It is OPTIONAL for name-value pairs to be representations of something in the world. If they are a representation of something in the world, then it MAY change value for the corresponding duration. If name-value pairs are a representation of something in the world that does not change, they are not regarded as determining characteristics of a characterized thing or activity, for the purpose of provenance. Indeed, it is not expected that provenance would contain an explanation for these attribute-values.
</p>
@@ -951,7 +951,7 @@
-<p>An instance of a generation expression, noted <span class="name">wasGeneratedBy(e,pe,q,t)</span> in PROV-ASN:</p>
+<p>An instance of a generation expression, written <span class="name">wasGeneratedBy(e,pe,q,t)</span> in PROV-ASN:</p>
<ul>
<li> contains an identifier <span class="name">e</span> identifying an entity expression that represents the characterized thing that is created; </li>
<li> contain an identifier <span class="name">pe</span> identifying a process execution expression that represents the activity that creates the characterized thing;</li>
@@ -1038,7 +1038,7 @@
</div>
-<p>An instance of a use expression, noted <span class="name">used(pe,e,q,t)</span> in PROV-ASN:</p>
+<p>An instance of a use expression, written <span class="name">used(pe,e,q,t)</span> in PROV-ASN:</p>
<ul>
<li> refers to a process execution expression identified by <span class="name">pe</span>, which represents the consuming activity;</li>
<li> refers to an entity expression identified by <span class="name">e</span>, which represents the characterized thing that is consumed;</li>
@@ -1143,7 +1143,7 @@
<p>A process execution linked derivation expression, which, by definition of a derivation expression, is a representation that some characterized thing is transformed from, created from, or affected by another characterized thing, also entails the existence of a process execution expression that represents an activity that transforms, creates or affects this characterized thing.</p>
-<p>In its full form, a process-execution linked derivation expression, noted <span class="name">wasDerivedFrom(e2,e1,pe,q2,q1)</span> in PROV-ASN:</p>
+<p>In its full form, a process-execution linked derivation expression, written <span class="name">wasDerivedFrom(e2,e1,pe,q2,q1)</span> in PROV-ASN:</p>
<ul>
<li> refers to an entity expression identified by <span class="name">e2</span>, which is a representation of the generated characterized thing;</li>
<li> refers to an entity expression identified by <span class="name">e1</span>, which is a representation of the used characterized thing;</li>
@@ -1325,7 +1325,7 @@
<li> contains an identifier <span class="name">e2</span>, denoting an entity expression, which represents the characterized thing that is the result of the derivation;
<li> contains an identifier <span class="name">e1</span>, denoting an entity expression, which represents the characterized thing that the derivation relies upon.
</ul>
-<p>The expression <span class="name">dependedOn</span> can only be inferred; in other word, it cannot be asserted. It is
+<p>The expression <span class="name">dependedOn</span> can only be inferred; in other words, it cannot be asserted. It is
transitive by definition and relies on the previously defined derivation assertions for its
base case.</p>
@@ -1385,7 +1385,7 @@
</div>
-<p>An instance of a control expression, noted <span class="name">wasControlledBy(pe,ag,q)</span> in PROV-ASN:</p>
+<p>An instance of a control expression, written <span class="name">wasControlledBy(pe,ag,q)</span> in PROV-ASN:</p>
<ul>
<li> contains an identifier <span class="name">pe</span> denoting a process execution expression, representing the controlled activity;
<li> refers to an agent expression or an entity expression identified by <span class="name">ag</span>, representing the controlling characterized thing;
@@ -1398,7 +1398,7 @@
<pre class="example">
wasControlledBy(pe3,a4,qualifier[role="author"])
</pre>
-<p>states that the activity, represented by the process execution expression denoted by <span class="name">pe3</span> saw the involvement of a characterized thing, represented by entity expression denoted by <span class="name">a4</span> in the capacity of author. This specification defines the qualifier name <span class="name">role</span> (see Section <a href="#expression-qualifier">Qualifier</a>) to denote the function of a characterized thing with respect to an activity.
+<p>states that the activity, represented by the process execution expression denoted by <span class="name">pe3</span> saw the involvement of a characterized thing, represented by entity expression denoted by <span class="name">a4</span> in the capacity of author. This specification reserves the qualifier name <span class="name">role</span> (see Section <a href="#expression-qualifier">Qualifier</a>) to denote the function of a characterized thing with respect to an activity.
</p>
</section>
@@ -1413,7 +1413,7 @@
<p>
-The rationale for introducing this relationship is that in general, at any given time, for a thing in the world, there may be multiple ways of characterizing it, and hence multiple representations can be asserted by different asserters. In the example that follows, suppose thing "Royal Society" is represented by two asserters, each using a different set of attributes. If the asserters agree that both representations refer to "The Royal Society", the question of whether any correspondence can be established between the two representations arises naturally. This is particularly relevant when (a) the sets of properties used by the two representations overlap partially, or (b) when one set is subsumed by the other. In both these cases, we have a situation where each of the two asserters has a partial view of "The Royal Society", and establishing a correspondence between them on the shared properties is beneficial, as in case (a) each of the two representation <em>complements</em> the other, and in case (b) one of the two (that with the additional properties) complements the other.</p>
+The rationale for introducing this relationship is that in general, at any given time, for a thing in the world, there may be multiple ways of characterizing it, and hence multiple representations can be asserted by different asserters. In the example that follows, suppose thing "Royal Society" is represented by two asserters, each using a different set of attributes. If the asserters agree that both representations refer to "The Royal Society", the question of whether any correspondence can be established between the two representations arises naturally. This is particularly relevant when (a) the sets of attributes used by the two representations overlap partially, or (b) when one set is subsumed by the other. In both these cases, we have a situation where each of the two asserters has a partial view of "The Royal Society", and establishing a correspondence between them on the shared attributes is beneficial, as in case (a) each of the two representation <em>complements</em> the other, and in case (b) one of the two (that with the additional attributes) complements the other.</p>
<p>This intuition is made more precise by considering the entities that form the representations of characterized things at a certain point in time.
@@ -1423,14 +1423,14 @@
<img src="complement-of.png" alt="illustration complementOf"/>
<p>
-Relation <em>complement-of</em> between two entity expressions is intended to capture these correspondences, as follows. Suppose entity expressions A and B share a set P of properties, and each of them has other properties in addition to P. If the values assigned to each property in P are <em>compatible</em> between A and B, then we say that <em>A is-complement-of B</em>, and <em>B is-complement-of A</em>, in a symmetrical fashion. In the particular case where the set P of properties of B is a strict superset of A's properties, then we say that <em>B is-complement-of A</em>, but in this case the opposite does not hold. In this case, the relation is not symmetric. (as a special case, A and B may not share any attributes at all, and yet the asserters may still stipulate that they are representing the same thing "Royal Society". The symmetric relation may hold trivially in this case).</p>
+Relation <em>complement-of</em> between two entity expressions is intended to capture these correspondences, as follows. Suppose entity expressions A and B share a set P of attributes, and each of them has other attributes in addition to P. If the values assigned to each attribute in P are <em>compatible</em> between A and B, then we say that <em>A is-complement-of B</em>, and <em>B is-complement-of A</em>, in a symmetrical fashion. In the particular case where the set P of attributes of B is a strict superset of A's attributes, then we say that <em>B is-complement-of A</em>, but in this case the opposite does not hold. In this case, the relation is not symmetric. (as a special case, A and B may not share any attributes at all, and yet the asserters may still stipulate that they are representing the same thing "Royal Society". The symmetric relation may hold trivially in this case).</p>
<p>The term <em>compatible</em> used above means that a mapping can be established amongst the values of attributes in P and found in the two entity expession. This generalizes to the case where attribute sets P1 and P2 of A, and B, respectively, are not identical but they can be mapped to one another. The simplest case is the identity mapping, in which A and B share attribute set P, and furthermore the values assigned to attributes in P match exactly.</p>
<p>It is important to note that the relation holds only for the characterization intervals of the entity expessions involved As soon as one attribute changes value in one of them, new correspondences need to be found amongst the new entities. Thus, the relation has a validity span that can be expressed in terms of the event lines of the thing.</p>
<!--
-The "IVP of" relationship is designed to represent pairs of entities that correspond to each other. By their own nature, an entity remains valid only as long as all of its attributes do not change their value. It follows that the correspondence "B IVP of A" is only valid within the time interval during which such invariance property holds for both A and B. When any of the property values change in either A or B, those entities are replaced by new ones, and a new correspondence may be established. Thus, "IVP of" is defined relative to the intersection of the temporal intervals for which A and B are valid.
+The "IVP of" relationship is designed to represent pairs of entities that correspond to each other. By their own nature, an entity remains valid only as long as all of its attributes do not change their value. It follows that the correspondence "B IVP of A" is only valid within the time interval during which such invariance attribute holds for both A and B. When any of the attribute values change in either A or B, those entities are replaced by new ones, and a new correspondence may be established. Thus, "IVP of" is defined relative to the intersection of the temporal intervals for which A and B are valid.
-->
@@ -1639,7 +1639,7 @@
-<p>An instance of a revision expression, noted <span class="name">wasRevisionOf(e2,e1,ag)</span> in PROV-ASN:</p>
+<p>An instance of a revision expression, written <span class="name">wasRevisionOf(e2,e1,ag)</span> in PROV-ASN:</p>
<ul>
<li> contains an identifier <span class="name">e2</span> identifying an entity that represents a newer version of a thing;
<li> contains an identifier <span class="name">e1</span> identifying an entity that represents an older version of a thing;
@@ -1703,7 +1703,7 @@
<p>An instance of a participation expression,
-noted <span class="name">hadParticipant(pe,e)</span> in PROV-ASN:
+written <span class="name">hadParticipant(pe,e)</span> in PROV-ASN:
<ul>
<li> contains to identifier <span class="name">pe</span> identifying a process execution expression representing an activity;
<li> contains an identifier <span class="name">e</span> identifying an entity expression, which is
@@ -1751,9 +1751,22 @@
<span class="nonterminal">identifier</span>
<span class="name">)</span><br/>
<span class="nonterminal">relationIdentification</span> :=
-<span class="nonterminal">identifier</span> <span class="nonterminal">identifier</span> <span class="nonterminal">qualifier</span>
+<span class="name">relation</span>
+<span class="name">(</span>
+<span class="nonterminal">identifier</span>
+<span class="name">,</span>
+<span class="nonterminal">identifier</span>
+<span class="name">,</span>
+<span class="nonterminal">qualifier</span>
+[<span class="name">,</span>
+<span class="nonterminal">qualifier</span>
+]
+<span class="name">)</span>
</div>
+<p>Since relations do not have identifiers but can be annotated, a <span class="nonterminal">relationIdentification</span> mechanism is provided allowing the constituents of relations to be listed so as to identify relations.
+</p>
+
<p>The interpretation of annotations is application-specific. See Section <a href="#expression-annotation">Annotation</a> for a discussion of the difference between attributes and annotations. </p>
<p>
@@ -1761,11 +1774,18 @@
<pre class="example">
entity(e1,[type="document"])
entity(e2,[type="document"])
+processExecution(pe,transform,t1,t2,[])
+used(pe,e1,qualifier(file="stdin"))
+wasGeneratedBy(e2, pe, qualifier(file="stdout"))
+
annotation(ann1,[icon="doc.png"])
hasAnnotation(e1,ann1)
hasAnnotation(e2,ann1)
+
+annotation(ann2,[style="dotted"])
+hasAnnotation(relation(pe,e1,qualifier(file="stdin")),ann2)
</pre>
-<p>assert the existence of two documents in the world (attribute-value pair: <span class="name">type="document"</span>) represented by entity expressions identified by <span class="name">e1</span> and <span class="name">e2</span>, and annotate these expressions with an annotation indicating that the icon (an application specific way of rendering provenance) is <span class="name">doc.png</span>.
+<p>assert the existence of two documents in the world (attribute-value pair: <span class="name">type="document"</span>) represented by entity expressions identified by <span class="name">e1</span> and <span class="name">e2</span>, and annotate these expressions with an annotation indicating that the icon (an application specific way of rendering provenance) is <span class="name">doc.png</span>. It also asserts a process execution, its use of the first entity, and its generation of the second entity. The <span class="name">used</span> relation is annotated with a style (an application specific way of rendering this edge graphically).
</p>
@@ -1808,7 +1828,7 @@
<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>
+<p>An instance of an account expression, written <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>
@@ -1919,7 +1939,7 @@
<section id="ProvenanceContainer">
<h4>Provenance Container</h4>
-<p>A <dfn id="dfn-ProvenanceContainer">provenance container</dfn> is a house-keeping construct of PROV-DM, also capable of bundling PROV-DM expressions. A provenance container is not an expression, but can be exploited to return all the provenance assertions in response to a request for the provenance of something ([[PROV-PAQ]]). </p>
+<p>A <dfn id="dfn-ProvenanceContainer">provenance container</dfn> is a house-keeping construct of PROV-DM, also capable of bundling PROV-DM expressions. A provenance container is not an expression, but can be exploited to return assertions in response to a request for the provenance of something ([[PROV-PAQ]]). </p>
<p>In PROV-ASN, a provenance container's text matches the <span class="nonterminal">provenanceContainer</span> production of the grammar defined in this specification document.</p>
@@ -1936,7 +1956,7 @@
<span class="name">)</span>
</div>
-<p>An instance of a provenance container, noted <span class="name">provenanceContainer(decls, ids, exprs)</span> in PROV-ASN:
+<p>An instance of a provenance container, written <span class="name">provenanceContainer(decls, ids, exprs)</span> in PROV-ASN:
<ul>
<li> contains a set of namespace declarations <span class="name">decls</span>, declaring namespaces and associated prefixes, which can be used in attributes (conformant to production <span class="nonterminal">attribute</span>) and in names (conformant to production <span class="nonterminal">name</span>) in <span class="name">exprs</span>;</li>
<li> contains a set of identifiers <span class="name">ids</span> naming all accounts occurring (at any nesting level) in <span class="name">exprs</span>;</li>
@@ -2368,7 +2388,7 @@
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>
+<p> An assertion wasQuoteOf, written <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;
@@ -2387,7 +2407,7 @@
Attribution represents that a characterized thing is ascribed to an agent.
-<p> An assertion wasAttributedTo, noted <span class="name"> wasAttributedTo(e1,ag)</span>:</p>
+<p> An assertion wasAttributedTo, written <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>.
@@ -2404,7 +2424,7 @@
<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>
+<p> An assertion wasSummaryOf, written <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.
@@ -2422,7 +2442,7 @@
Represents a characterized thing in which another characterized thing first appeared.
-<p> An assertion hasOriginalSource, noted <span class="name"> hasOriginalSource(e2,e1)</span>:</p>
+<p> An assertion hasOriginalSource, written <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.