--- a/model/ProvenanceModel.html Wed Nov 23 13:06:38 2011 -0700
+++ b/model/ProvenanceModel.html Wed Nov 23 22:36:24 2011 +0000
@@ -1989,7 +1989,7 @@
<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>
+Currently, the non-terminal <span class="nonterminal">asserter</span> is defined as IRI. 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>
<div class="anexample">
<p>
@@ -2106,7 +2106,7 @@
<span class="nonterminal">recordContainer</span> :=
<span class="name">container</span>
<span class="name">(</span>
-{ <span class="nonterminal">namespaceDeclaration</span> }
+{ <span class="nonterminal">namespaceDeclarations</span> }
<span class="name">,</span>
{ <span class="nonterminal">identifier</span> }
<span class="name">,</span>
@@ -2155,11 +2155,16 @@
<section id="record-attribute">
<h4>Attribute</h4>
-<p>An <dfn id="dfn-attribute">attribute</dfn> is a finite sequence of characters. (Exact production TBD).</p>
+<p>An <dfn id="dfn-attribute">attribute</dfn> is a <em>qualified name</em>. A qualified name can be mapped into an IRI
+ by concatenating the IRI associated with the prefix and the local part (see detailed rule in [[!RDF-SPARQL-QUERY]], Section <a href="http://www.w3.org/TR/2008/REC-rdf-sparql-query-20080115/#QSynIRI">4.1.1</a>).</p>
<div class='grammar'>
<span class="nonterminal">attribute</span> :=
-<em>a qualified name</em></div>
+<em>a qualified name compatible with the production PNAME_LN of SPARQL [[!RDF-SPARQL-QUERY]]</em></div>
+
+<div class="note">
+Confirm the principle of qualified names. Explitly introduce the productions for prefix and local name, since they are used elsewhere. Note that SPARQL local names allow leading digits while XML local names do not.
+</div>
<p>If a namespace prefix occurs in the qualified name, it refers to a namespace declared in the record container.</p>
@@ -2167,39 +2172,14 @@
<p>The PROV data model introduces the attribute <span class="name">role</span> in the <a href="#prov-dm-namespace">PROV-DM namespace</a> to denote the function of an entity 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 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>
-<pre class="example">
+<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>
+<pre class="codeexample">
wasStartedBy(a,ag, [prov:role="program-operator"])
</pre>
-<p>From this specification's viewpoint, an the interpretation of an attribute declared in a namespace other than prov-dm is out of
+<p>From this specification's viewpoint, the interpretation of an attribute declared in a namespace other than prov-dm is out of
scope.</p>
-
-
-
-
-
-<p>
-By definition, a usage (resp. generation, control) record does not contain an identifier.
-If one wants to annotate a usage (resp. generation, control) record, this record MUST be identifiable from its constituents, i.e. its source's identifier, its destination's identifier, and its attributes.</p>
-
-<p> To be able to annotate usage (resp. generation, control) records that refer to a given activity identifier,
- any attribute-value set occurring in usage records (resp. generation, control) with this identifier and a given entity record identifier MUST be unique.</p>
-
-
-<p>Attribute-value are used in determining the exact source and destination of a <span class="nonterminal">pe-linked-derivationRecord</span>. Hence,
-if one wants to express a <span class="nonterminal">pe-linked-derivationRecord</span> referring to an entity record and an activity record, then:</p>
-<ul>
-<li>the set of attribute-values of a usage record MUST be unique among the set of attribute-values occurring in usage records for this activity;
-<li>the set of attribute-values of a generation record MUST be unique among the set of attribute-values occurring in generation records for this activity.
-</ul>
-
-
-
-
-
-
-
+</div>
</section>
@@ -2208,16 +2188,15 @@
<h4>Identifier</h4>
-<p>An <dfn id="dfn-identifier">identifier</dfn> is a finite sequence of characters. </p>
-
-<div class='note'>Do we require identifiers to be URIs? All the examples in this document so far use simple labels as identifiers? Would this be acceptable? Maybe understood as default namespace and local name?
-</div>
+<p>An <dfn id="dfn-identifier">identifier</dfn> is a <em>qualified name</em>. A qualified name can be mapped into an IRI
+ by concatenating the IRI associated with the prefix and the local part (see detailed rule in [[!RDF-SPARQL-QUERY]], Section <a href="http://www.w3.org/TR/2008/REC-rdf-sparql-query-20080115/#QSynIRI">4.1.1</a>).</p>
<div class='grammar'>
<span class="nonterminal">identifier</span> :=
-<em>?????</em></div>
-
-<div class='note'>We are going to introduce a notion of qualified identifier, which allows us to refer to an identifier in the scope of a given account. Given that accounts may be nested, a qualified identifier will be prefixed by a sequence of account identifiers, and then followed by an identifier, local to the innermost account.
+<em>a qualified name compatible with the production PNAME_LN of SPARQL [[!RDF-SPARQL-QUERY]]</em></div>
+
+
+<div class='note'>We are going to introduce a notion of "qualified identifier", which allows us to refer to a provenance record in the scope of a given account. Given that accounts may be nested, a qualified identifier will be prefixed by a sequence of account identifiers, and then followed by an identifier, local to the innermost account.
</div>
@@ -2250,12 +2229,12 @@
are syntactic sugar for quoted strings with datatype <span class="name">xsd:string</span>.
</p>
-<p> In particular, a PROV-DM Literal may be a URI-typed string (with datatype <span class="name">xsd:anyURI</span>), or URI-denoted resource (with datatype <span class="name">rdf:Resource</span>); in either case; such URI has no specific interpretation in the context of PROV-DM.</p>
+<p> In particular, a PROV-DM Literal may be a IRI-typed string (with datatype <span class="name">xsd:anyURI</span>); such IRI has no specific interpretation in the context of PROV-DM.</p>
<div class="anexample">
<p>
-The following examples respectively are the string "abc", the string "abc" with language english, the string "abc", the integer number "1", and the URI "http://example.org/foo".
+The following examples respectively are the string "abc", the string "abc" with language english, the string "abc", the integer number "1", and the IRI "http://example.org/foo".
<pre class="codeexample">
"abc"
"abc"@en
@@ -2300,17 +2279,20 @@
</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>
+Currently, the non-terminal <span class="nonterminal">asserter</span> is defined as IRI. 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="record-NamespaceDeclaration">
<h3>Namespace Declaration</h3>
-<p>A <dfn id="dfn-namespaceDeclaration">namespace declaration</dfn> declares a namespace and a prefix to denote it.</p>
+<p>A <dfn id="dfn-namespaceDeclaration">namespace declaration</dfn> consists of a namespace and a prefix to denote it.</p>
<div class='grammar'>
-<span class="nonterminal">namespaceDeclaration</span> := ... <em>TBD</em>
+<span class="nonterminal">namespaceDeclarations</span> :=
+ | <span class="nonterminal">namespaceDeclaration</span> (<span class="name">,</span> <span class="nonterminal">namespaceDeclaration</span>)*<br>
+<span class="nonterminal">namespaceDeclaration</span> :=
+ PREFIX <span class="name">:</span> IRI
</div>
</section>