--- a/model/ProvenanceModel.html Thu Sep 15 22:59:27 2011 +0100
+++ b/model/ProvenanceModel.html Fri Sep 16 00:02:36 2011 +0100
@@ -664,7 +664,7 @@
<span class="name">(</span>
<span class="nonterminal">identifier</span>
[ <span class="name">,</span>
-<span class="nonterminal">recipe</span> ]
+<span class="nonterminal">recipeLink</span> ]
<span class="name">,</span>
[ <span class="nonterminal">time</span> ]
<span class="name">,</span>
@@ -1841,10 +1841,12 @@
<section id="expression-other">
<h3>Other Expressions</h3>
+This section specifies the productions of sub-expressions of PROV-DM expressions.
<section id="expression-qualifier">
<h4>Qualifier</h4>
+<p>A <dfn id="dfn-qualifier">qualifier</dfn> is an ordered list of name-value pairs, used to qualify use expressions, generation expressions and control expressions.</p>
<div class='grammar'>
<span class="nonterminal">useQualifier</span> :=
@@ -1853,22 +1855,47 @@
<span class="nonterminal">qualifier</span> <br/>
<span class="nonterminal">controlQualifier</span> :=
<span class="nonterminal">qualifier</span> <br/>
+<br/>
<span class="nonterminal">qualifier</span> :=
<span class="nonterminal">name-values</span> <br/>
<!-- -->
<span class="nonterminal">name-values</span> :=
<span class="nonterminal">name-value</span>
-|<span class="nonterminal">name-value</span> <span class="name">,</span> <span class="nonterminal">name-values</span>
+| <span class="nonterminal">name-value</span> <span class="name">,</span> <span class="nonterminal">name-values</span>
<br/>
<span class="nonterminal">name-value</span> :=
<span class="nonterminal">name</span>
-<span class="name">:</span>
+<span class="name">=</span>
<span class="nonterminal">Literal</span></div>
+
+
+<p>Use, generation, and control expressions MUST contain a qualifier,
+though a qualifier MAY contain no name-value pair. </p>
+
+<div class='note'>LUC TO ADAPT to QUALIFIER</div>
+
+<p>
+If one wants to annotate a use (resp. generation) edge expression or if one wants express a pe-linked-derivationExpression referring to this entity and process execution expressions, the qualifier occuring in this use assertion must be unique among the qualifiers qualifiying use expressions for this process execution.
+
+
+The set of all use (resp. generation, control) expressions that refer to a given process execution execution MUST contain at most one occurrence of a given role. The rationale for this requirement is that when provenance is used to replay execution, roles are used to determine which values must be associated with which input (resp. output, control channel) of a process execution.</p>
+
+<div class='resolved'>Decide the level of requirements: MUST/SHOULD and justify. This is <a href="http://www.w3.org/2011/prov/track/issues/40">ISSUE-40</a> and <a href="http://www.w3.org/2011/prov/track/issues/41">ISSUE-41</a>. MUST is confirmed. </div>
+
+
+<p>The interpretation of a role is specific to the process execution it relates
+to, which means that a same role may appear in relation to two different process executions with different interpretations.
+From this specification's viewpoint, a role's interpretation is out of
+scope.</p>
+
+
</section>
<section id="expression-attribute">
<h4>Attribute</h4>
+<p>An <dfn id="dfn-attribute">attribute</dfn> is a finite sequence of characters. (Exact production TBD).</p>
+
<div class='grammar'>
<span class="nonterminal">attribute</span> :=
<em>a qualified name</em></div>
@@ -1878,19 +1905,33 @@
<section id="expression-name">
<h4>Name</h4>
-</section>
+
+
+<p>A <dfn id="dfn-name">name</dfn> is a finite sequence of characters. (Exact production TBD).</p>
<div class='grammar'>
<span class="nonterminal">name</span> :=
<em>a qualified name</em></div>
<p>If a namespace prefix occurs in the qualified name, it refers to a namespace declared in the provenance container.</p>
+
+<div class='note'>Proposed to adopt the abbreviatedIRI definition of OWL2 [[!OWL2-SYNTAX]]
+(see section <a href="http://www.w3.org/TR/2009/REC-owl2-syntax-20091027/#IRIs">IRIs</a>).
+</div>
+
+<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. We seek inputs on how to resolve this issue. </div>
+
</section>
<section id="expression-literal">
<h4>Literal</h4>
-<div class='note'>It is proposed to use the definition of Literal as in OWL2. Add URL here.</div>
+Literals represent data values such as particular string or integers.
+
+<div class='note'>It is proposed to use the definition of OWL2 Literal [[!OWL2-SYNTAX]]
+(see section <a href="http://www.w3.org/TR/2009/REC-owl2-syntax-20091027/#Literals">Literals</a>).
+</div>
</section>
@@ -1933,10 +1974,22 @@
<section id="expression-Asserter">
<h3>Asserter</h3>
+
+<p>An <dfn id="dfn-asserter">asserter</dfn> is a creator of PROV-DM expressions. An asserter is denoted by an IRI.</p>
+
+<div class='grammar'>
+<span class="nonterminal">asserter</span> := <em>an IRI</em>
+</div>
</section>
<section id="expression-NamespaceDeclaration">
<h3>Namespace Declaration</h3>
+
+<p>A <dfn id="dfn-namespaceDeclaration">namespace declaration</dfn> declares a namespace and a prefix to denote it.</p>
+
+<div class='grammar'>
+<span class="nonterminal">namespaceDeclaration</span> := ... <em>TBD</em>
+</div>
</section>
@@ -1947,6 +2000,10 @@
<p>A <dfn id="dfn-RecipeLink">recipe link</dfn> is an association between a process execution and a process specification that underpins the process execution.
</p>
+<div class='grammar'>
+<span class="nonterminal">recipeLink</span> := <em>an IRI</em>
+</div>
+
<p>
It is OPTIONAL to assert recipe links in process executions.
</p>
@@ -1958,62 +2015,24 @@
</section>
-<section id="expression-Role">
-<h3>Role</h3>
-
-
-<p>A <dfn id="dfn-Role">role</dfn> is a label that names the function assumed by an entity or
-an agent with respect to a specific process execution.</p>
-
-<div class='note'>It may be useful to distinguish between a role name and a role type, similarly to
- parameter names and parameter types in a programming language procedure.
-Currently, all the constraints and definitions pertaining to roles in the
-specification should be understood as role names.</div>
-
-
-
-<p>Use, Generation, and Control assertions MUST contain a role. Roles
-are mandatory since they allow for uniform data structures. To facilitate
-the writing of these assertions when a role is unknown by the
-asserter, syntactic notations MAY allow these to be written without a role. In such a case, a default, uniquely named role from the set
-'unspecified role' will be assumed. A countable set of unique labels can be used to denote unspecified roles, as in:
-<span class="name">unspecified0</span>, <span class="name">unspecified1</span>, <span class="name">unspecified2</span>, ....
-
-<pre class="example">
- used(pe,e) expands to used(pe,e,unspecified1)
-</pre>
-where unspecified1 is an unspecified role.
-</p>
-
-<p> The set of all Use (resp. Generation, Control) assertions that refer to a given process execution MUST contain at most one occurrence of a given role. The rationale for this requirement is that when provenance is used to replay execution, roles are used to determine which values must be associated with which input (resp. output, control channel) of a process execution.</p>
-
-<div class='resolved'>Decide the level of requirements: MUST/SHOULD and justify. This is <a href="http://www.w3.org/2011/prov/track/issues/40">ISSUE-40</a> and <a href="http://www.w3.org/2011/prov/track/issues/41">ISSUE-41</a>. MUST is confirmed. </div>
-
-
-<p>The interpretation of a role is specific to the process execution it relates
-to, which means that a same role may appear in relation to two different process executions with different interpretations.
-From this specification's viewpoint, a role's interpretation is out of
-scope.</p>
-
-
-
-
-
-</section>
+
+
+
+
<section id="expression-Location">
<h3>Location</h3>
-<p><dfn id="dfn-Location">Location</dfn> is an identifiable geographic place (ISO 19112). As such, there are numerous ways in which location can be specified, such as by a coordinate, address, landmark, row, column, and so forth.</p>
+<p><dfn id="dfn-Location">Location</dfn> is an identifiable geographic place (ISO 19112). As such, there are numerous ways in which location can be expressed, such as by a coordinate, address, landmark, row, column, and so forth. This document does not specify how to concretely express locations, but instead provide a mechanism to introduce locations in assertions. </p>
<p>
-Location is an OPTIONAL characteristics of
-entity, process execution, and agent.
+Location is an OPTIONAL attribute of entity expressions and process execution expressions. The value associated with a location attribute is expected to be a location.
</p>
+
</section>
</section>