--- a/model/working-copy/prov-asn.html Tue Feb 07 16:26:33 2012 +0000
+++ b/model/working-copy/prov-asn.html Tue Feb 07 16:50:34 2012 +0000
@@ -226,7 +226,7 @@
<section id="record-Activity">
-<h3>Activity Record</h3>
+<h3>Activity</h3>
<div class="withAsn">
@@ -253,7 +253,7 @@
</section>
<section id="record-Agent">
-<h3>Agent Record</h3>
+<h3>Agent</h3>
<div class="withAsn">
@@ -275,7 +275,7 @@
<section id="record-note">
-<h4>Note Record</h4>
+<h4>Note</h4>
<div class="withAsn">
<p>In PROV-ASN, a note record's text matches the <span class="nonterminal">noteRecord</span> production of the grammar defined in this specification document.
@@ -612,8 +612,6 @@
</div>
</div>
-<div class='issue'>A discussion on alternative definition of these relations has not reached a satisfactory conclusion yet. This is <a
-href="http://www.w3.org/2011/prov/track/issues/29">ISSUE-29</a>. Also <a href="http://www.w3.org/2011/prov/track/issues/96">ISSUE-96</a>.</div>
</section>
@@ -621,50 +619,6 @@
-<!--
-<section>
-<h4>Transitive Derivation Record</h4>
-
-
-<p>
-If <span class="name">wasDerivedFrom(e2,e1)</span> holds because attribute <span class="name">a2.1</span> of <span class="name">e2</span> is determined by attribute <span
-class="name">a1.1</span> of <span class="name">e1</span>,
-and if <span class="name">wasDerivedFrom(e3,e2)</span> holds because attribute <span class="name">a3.1</span>of <span class="name">e3</span> is determined by attribute <span
-class="name">a2.2</span> of <span class="name">e1</span>, it is not necessarily the case that an attribute of <span class="name">e3</span> is determined by an attribute of <span
-class="name">e1</span>; so, an asserter may not be able to assert <span class="name">wasDerivedFrom(e3,e1)</span>, since it would fail to satisfy constraint <a
-href="#derivation-attributes">derivation-attributes</a>. Hence, the constraint on attributes as expressed in <a href="#derivation-attributes">derivation-attributes</a> invalidates
-transitivity in the general case.
-</p>
-
-<p>However, there is sense that <span class="name">e3</span> still depends on <span class="name">e1</span>, since <span class="name">e3</span> could not be generated without <span
-class="name">e1</span> existing. Hence, we introduce a weaker notion of derivation record, which is transitive.</p>
-
-A transitive derivation record, written <span class="name">dependedOn(e2, e1)</span> in PROV-ASN:
-<ul>
-<li> contains an identifier <span class="name">e2</span>, denoting an entity record, which represents the entity that is the result of the derivation;
-<li> contains an identifier <span class="name">e1</span>, denoting an entity record, which represents the entity that the derivation relies upon.
-</ul>
-<p>The record <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>
-
-<div class='constraint' id='transitive-derivation'>
-<ul>
-<li><span class='conditional'>If</span> <span class="name">wasDerivedFrom(e2,e1)</span> or <span class="name">wasDerivedFrom(e2,e1,pe,attrs2,attrs1)</span> holds, <span
-class='conditional'>then</span> <span class="name">dependedOn(e2,e1)</span> holds.</li>
-<li><span class='conditional'>If</span> <span class="name">wasEventuallyDerivedFrom(e2,e1)</span> holds, <span class='conditional'>then</span> <span class="name">dependedOn(e2,e1)</span>
-holds.</li>
-<li><span class='conditional'>If</span> <span class="name">dependedOn(e3,e2)</span> and <span class="name">dependedOn(e2,e1)</span> hold, <span class='conditional'>then</span> <span
-class="name">dependedOn(e3,e1)</span> holds.</li>
-</ul>
-</div>
-
-</section>
--->
-
-
-
-
@@ -672,19 +626,6 @@
<h4>Annotation Record</h4>
-<p>An <dfn id="dfn-annotation">annotation record</dfn> establishes a link between an identifiable PROV-DM record and a note record referred to by its identifier. Multiple note records can
-be associated with a given PROV-DM record; symmetrically, multiple PROV-DM records can be associated with a given note record. Since note records have identifiers, they can also be
-annotated. The annotation mechanism (with note record and the annotation record) forms a key aspect of the extensibility mechanism of PROV-DM (see <a
-href="#extensibility-section">extensibility section</a>).</p>
-
-<p>An annotation record, written <span class="name">hasAnnotation(r,n,attrs)</span> in PROV-ASN, has the following constituents:</p>
-<ul>
-<li><em>record</em>: an identifier <span class="name">r</span> of the record being annnotated;</li>
-<li><em>note</em>: an identifier <span class="name">n</span> of a note record;</li>
-<li><em>attributes</em>: an OPTIONAL set <span class="name">attrs</span> of attribute-value pairs to further describe this record.</li>
-</ul>
-
-</div>
<p>In PROV-ASN, a note record's text matches the <span class="nonterminal">noteRecord</span> production of the grammar defined in this specification document.
</p>
@@ -700,36 +641,173 @@
</div>
</div>
-<p>The interpretation of notes is application-specific. See Section <a href="#record-note">Note</a> for a discussion of the difference between note attributes and other records attributes.
-We also note the present tense in this term to indicate that it may not denote something in the past.</p>
-
-<div class="anexample">
-<p>
-The following records</p>
-<pre class="codexample">
-entity(e1,[prov:type="document"])
-entity(e2,[prov:type="document"])
-activity(a,t1,t2)
-used(u1,a,e1,[ex:file="stdin"])
-wasGeneratedBy(e2, a, [ex:file="stdout"])
-note(n1,[ex:icon="doc.png"])
-hasAnnotation(e1,n1)
-hasAnnotation(e2,n1)
+</section>
+</section>
-note(n2,[ex:style="dotted"])
-hasAnnotation(u1,n2)
-</pre>
-<p>assert the existence of two documents in the world (attribute-value pair: <span class="name">prov:type="document"</span>) identified by <span class="name">e1</span> and <span
-class="name">e2</span>, and annotate these records with a note indicating that the icon (an application specific way of rendering provenance) is <span class="name">doc.png</span>. It also
-asserts an activity, its usage of the first entity, and its generation of the second entity. The <span class="name">usage</span> record is annotated with a style (an application specific way
-of rendering this edge graphically). To be able to express this annotation, the usage record was provided with an identifier <span class="name">u1</span>, which was then referred to in <span
-class="name">hasAnnotation(u1,n2)</span>.
-</p>
+
+<section id="sub-record">
+<h3>Further Terms in Records</h3>
+
+This section further terms in PROV-DM records.
+
+
+
+<section id="record-attribute">
+<h4>Attribute</h4>
+
+
+<p>In PROV-ASN, an attribute's text matches the <span class="nonterminal">attribute</span> production of the grammar defined in this specification document.</p>
+
+<div class='grammar'>
+<span class="nonterminal">attribute</span> ::= <span class="nonterminal">qualifiedName</span><br/>
+<span class="nonterminal">qualifiedName</span> ::= <span class="nonterminal">prefixedName</span> | <span class="nonterminal">unprefixedName</span><br/>
+<span class="nonterminal">prefixedName</span> ::= <span class="nonterminal">prefix</span> <span class="name">:</span> <span class="nonterminal">localPart</span><br/>
+<span class="nonterminal">unprefixedName</span> ::= <span class="nonterminal">localPart</span><br/>
+<span class="nonterminal">prefix</span> ::= <em>a name without colon compatible with the <a href="http://www.w3.org/TR/2009/REC-xml-names-20091208/#NT-NCName">NC_NAME</a> production
+[[!XML-NAMES]]</em><br/>
+<span class="nonterminal">localPart</span> ::= <em>a name without colon compatible with the <a href="http://www.w3.org/TR/2009/REC-xml-names-20091208/#NT-NCName">NC_NAME</a> production
+[[!XML-NAMES]]</em>
+</div>
+
+
+<div class="note">Note that XML NC_NAME don't allow local identifiers to start with a number. Instead, should we use the productions used in SPARQL or TURTLE?</div>
+
+
+<ul>
+
+<li> The attribute <dfn id="dfn-type"><span class="name">prov:type</span></dfn> provides further typing information for the element or relation asserted in the record. </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">"single"</span> or <span class="name">"any"</span>. The attribute <span class="name">prov:step</span> occurs at most
+once in a derivation record. A derivation record without attribute <span class="name">prov:step</span> is considered to be equivalent to the same record extended with an extra attribute
+<span class="name">prov:step</span> and associated value <span class="name">"any"</span>. </li>
+
+<li> The attribute <dfn id="dfn-label"><span class="name">prov:label</span></dfn> provides a human-readable representation of a PROV-DM element or relation.</li>
+
+</ul>
+</section>
+
+
+
+<section id="record-identifier">
+<h4>Identifier</h4>
+
+
+<div class='grammar'>
+<span class="nonterminal">identifier</span> ::= <span class="nonterminal">qualifiedName</span><br/>
+<span class="nonterminal">eIdentifier</span> ::= <span class="nonterminal">identifier</span> <em>(intended to denote an entity record)</em><br/>
+<span class="nonterminal">aIdentifier</span> ::= <span class="nonterminal">identifier</span> <em>(intended to denote an activity record)</em><br/>
+<span class="nonterminal">agIdentifier</span> ::= <span class="nonterminal">identifier</span> <em>(intended to denote an agent record)</em><br/>
+<span class="nonterminal">gIdentifier</span>::= <span class="nonterminal">identifier</span> <em>(intended to denote a generation record)</em><br/>
+<span class="nonterminal">uIdentifier</span>::= <span class="nonterminal">identifier</span> <em>(intended to denote a usage record)</em><br/>
+<span class="nonterminal">nIdentifier</span>::= <span class="nonterminal">identifier</span> <em>(intended to denote a note record)</em><br/>
+<span class="nonterminal">accIdentifier</span>::= <span class="nonterminal">identifier</span> <em>(intended to denote an account record)</em>
</div>
</section>
+
+<section id="record-literal">
+<h4>Literal</h4>
+
+<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">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">intLiteral</span> ::= <em>a finite-length sequence of decimal digits (#x30-#x39) with an optional leading negative sign (-)</em>
+</div>
+
+<p>The non terminals <span class="nonterminal">stringLiteral</span> and
+<span class="nonterminal">intLiteral</span>
+are syntactic sugar for quoted strings with datatype <span class="name">xsd:string</span> and <span class="name">xsd:int</span>, respectively.
+</p>
+
+<p> In particular, a PROV-DM Literal may be an 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" (expressed using the convenience notation), the string "abc", the integer number 1, the integer number 1 (expressed using the
+convenience notation) and the IRI "http://example.org/foo".
+<pre class="codeexample">
+ "abc"
+ "abc" %% xsd:string
+ "1" %% xsd:int
+ 1
+ "http://example.org/foo" %% xsd:anyURI
+</pre>
+The following example shows a literal of type <span class="name">xsd:QName</span> (see
+<a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#QName">QName</a> [[!XMLSCHEMA-2]]).
+The prefix <span class="name">ex</span> MUST be bound to a <a>namespace</a> declared in the
+ record container.
+<pre class="codeexample">
+ "ex:value" %% xsd:QName
+</pre>
+</div>
+
+
+<div class='note'>Should we define structural equivalence of literals as in OWL2? [[!OWL2-SYNTAX]]
+(see section <a href="http://www.w3.org/TR/2009/REC-owl2-syntax-20091027/#Literals">Literals</a>).
+</div>
+
+</section>
+
+
+
+
+<section id="record-Time">
+<h4>Time</h4>
+
+<p><dfn id="dfn-time">Time instants</dfn> are defined according to xsd:dateTime [[!XMLSCHEMA-2]].</p>
+
+
+
+
+</section>
+
+
+
+<section id="record-NamespaceDeclaration">
+<h3>Namespace Declaration</h3>
+
+
+<div class='grammar'>
+<span class="nonterminal">namespaceDeclarations</span> ::=
+ | <span class="group"><span class="nonterminal">defaultNamespaceDeclaration</span> | <span class="nonterminal">namespaceDeclaration</span></span> <span class="star"> <span
+class="nonterminal">namespaceDeclaration</span></span><br>
+<span class="nonterminal">namespaceDeclaration</span> ::=
+<span class="name">prefix</span> <span class="nonterminal">prefix</span> <span class="nonterminal">IRI</span><br/>
+<span class="nonterminal">defaultNamespaceDeclaration</span> ::=
+ <span class="name">default</span> <span class="nonterminal">IRI</span> <br/>
+</div>
+</section>
+
+
+
+
+
+
+<section id="record-Location">
+<h3>Location</h3>
+
+<p>
+Location is an OPTIONAL attribute of entity records and activity records. The value associated with a attribute <span class="name">location</span> MUST be a <span
+class="nonterminal">Literal</span>, expected to denote a location.
+</p>
+
+
+
+
+</section>
+
</section>
<section id="bundle">
@@ -834,271 +912,6 @@
</section>
</section>
-
-<section id="sub-record">
-<h3>Further Terms in Records</h3>
-
-This section further terms in PROV-DM records.
-
-
-
-<section id="record-attribute">
-<h4>Attribute</h4>
-
-<p>An <dfn id="dfn-attribute">attribute</dfn> is a <em>qualified name</em>.
-An <dfn id="dfn-qualified name">qualified name</dfn> is a name subject to namespace interpretation. It consists of namespace, denoted by an optional prefix, and a local name. The namespace
-is denoted by an IRI [[!IRI]].</p>
-
-
-<p>PROV-DM stipulates that 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>
-
-<p>A qualified name's prefix is OPTIONAL. If a prefix occurs in a
- qualified name, it refers to a <a>namespace</a> declared in the
- record container. In the absence of prefix, the qualified name
- refers to the default namespace declared in the container.</p>
-
-<p>In PROV-ASN, an attribute's text matches the <span class="nonterminal">attribute</span> production of the grammar defined in this specification document.</p>
-
-<div class='grammar'>
-<span class="nonterminal">attribute</span> ::= <span class="nonterminal">qualifiedName</span><br/>
-<span class="nonterminal">qualifiedName</span> ::= <span class="nonterminal">prefixedName</span> | <span class="nonterminal">unprefixedName</span><br/>
-<span class="nonterminal">prefixedName</span> ::= <span class="nonterminal">prefix</span> <span class="name">:</span> <span class="nonterminal">localPart</span><br/>
-<span class="nonterminal">unprefixedName</span> ::= <span class="nonterminal">localPart</span><br/>
-<span class="nonterminal">prefix</span> ::= <em>a name without colon compatible with the <a href="http://www.w3.org/TR/2009/REC-xml-names-20091208/#NT-NCName">NC_NAME</a> production
-[[!XML-NAMES]]</em><br/>
-<span class="nonterminal">localPart</span> ::= <em>a name without colon compatible with the <a href="http://www.w3.org/TR/2009/REC-xml-names-20091208/#NT-NCName">NC_NAME</a> production
-[[!XML-NAMES]]</em>
-</div>
-
-
-<div class="note">Note that XML NC_NAME don't allow local identifiers to start with a number. Instead, should we use the productions used in SPARQL or TURTLE?</div>
-
-
-<p>
-For each attribute in a record, its namespace also declares the number of occurrences it
-may have in a list of attributes. The
-property <dfn>attribute occurrence validity</dfn> holds for a record
-if the actual number of occurrences of each attribute in this record is compatible with
-this attribute's declaration it its namespace. How to handle records
-that do not satisfy the <a>attribute occurrence validity</a> property
-is beyond the scope of this specification.</p>
-
-
-<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>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 attribute <span class="name">prov:role</span> is allowed to occur multiple times in such records. 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>
-<pre class="codeexample">
- wasStartedBy(a,ag, [prov:role="program-operator"])
-</pre>
-</div>
- </li>
-
-<li> The attribute <dfn id="dfn-type"><span class="name">prov:type</span></dfn> provides further typing information for the element or relation asserted in the record. PROV-DM liberally
-defines a type as a category of things having common characteristics. PROV-DM is agnostic about the representation of types, and only states that
-the value associated with a <span class="name">prov:type</span> attribute MUST be conformant with <span class="nonterminal">Literal</span>. The attribute <span class="name">prov:type</span>
-is allowed to occur multiple times in a record.</li>
-
-<div class="anexample">
-<p>The following record declares an agent of type software agent</p>
-<pre class="codeexample">
- agent(ag, [prov:type="prov:SoftwareAgent" %% xsd:QName])
-</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">"single"</span> or <span class="name">"any"</span>. The attribute <span class="name">prov:step</span> occurs at most
-once in a derivation record. A derivation record without attribute <span class="name">prov:step</span> is considered to be equivalent to the same record extended with an extra attribute
-<span class="name">prov:step</span> and associated value <span class="name">"any"</span>. </li>
-
-<div class="anexample">
-<p>The following record declares an imprecise-1 derivation, which is known to involve one activity, though its identity, usage details of <span class="name">ex:e1</span>, and generation
-details of <span class="name">ex:e2</span> are not asserted.</p>
-<pre class="codeexample">
- wasDerivedFrom(ex:e2, ex:e1, [prov:steps="single"])
-</pre>
-</div>
-
-<li> The attribute <dfn id="dfn-label"><span class="name">prov:label</span></dfn> provides a human-readable representation of a PROV-DM element or relation.</li>
-
-<div class='issue'>
- This is <a href="http://www.w3.org/2011/prov/track/issues/219">ISSUE-219</a>. </div>
-
-
-</ul>
-</section>
-
-
-
-<section id="record-identifier">
-<h4>Identifier</h4>
-
-
-<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> ::= <span class="nonterminal">qualifiedName</span><br/>
-<span class="nonterminal">eIdentifier</span> ::= <span class="nonterminal">identifier</span> <em>(intended to denote an entity record)</em><br/>
-<span class="nonterminal">aIdentifier</span> ::= <span class="nonterminal">identifier</span> <em>(intended to denote an activity record)</em><br/>
-<span class="nonterminal">agIdentifier</span> ::= <span class="nonterminal">identifier</span> <em>(intended to denote an agent record)</em><br/>
-<span class="nonterminal">gIdentifier</span>::= <span class="nonterminal">identifier</span> <em>(intended to denote a generation record)</em><br/>
-<span class="nonterminal">uIdentifier</span>::= <span class="nonterminal">identifier</span> <em>(intended to denote a usage record)</em><br/>
-<span class="nonterminal">nIdentifier</span>::= <span class="nonterminal">identifier</span> <em>(intended to denote a note record)</em><br/>
-<span class="nonterminal">accIdentifier</span>::= <span class="nonterminal">identifier</span> <em>(intended to denote an account record)</em>
-</div>
-
-
-</section>
-
-<section id="record-literal">
-<h4>Literal</h4>
-
-<p>
-A PROV-DM Literal represents a data value such as a particular string
-or number. A PROV-DM Literal represents a value whose interpretation is outside the scope of PROV-DM.
-</p>
-
-<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">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">intLiteral</span> ::= <em>a finite-length sequence of decimal digits (#x30-#x39) with an optional leading negative sign (-)</em>
-</div>
-
-<p>The non terminals <span class="nonterminal">stringLiteral</span> and
-<span class="nonterminal">intLiteral</span>
-are syntactic sugar for quoted strings with datatype <span class="name">xsd:string</span> and <span class="name">xsd:int</span>, respectively.
-</p>
-
-<p> In particular, a PROV-DM Literal may be an 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" (expressed using the convenience notation), the string "abc", the integer number 1, the integer number 1 (expressed using the
-convenience notation) and the IRI "http://example.org/foo".
-<pre class="codeexample">
- "abc"
- "abc" %% xsd:string
- "1" %% xsd:int
- 1
- "http://example.org/foo" %% xsd:anyURI
-</pre>
-The following example shows a literal of type <span class="name">xsd:QName</span> (see
-<a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#QName">QName</a> [[!XMLSCHEMA-2]]).
-The prefix <span class="name">ex</span> MUST be bound to a <a>namespace</a> declared in the
- record container.
-<pre class="codeexample">
- "ex:value" %% xsd:QName
-</pre>
-</div>
-
-
-
-<div class='note'>Should we define structural equivalence of literals as in OWL2? [[!OWL2-SYNTAX]]
-(see section <a href="http://www.w3.org/TR/2009/REC-owl2-syntax-20091027/#Literals">Literals</a>).
-</div>
-
-</section>
-
-
-
-
-<section id="record-Time">
-<h4>Time</h4>
-
-<p><dfn id="dfn-time">Time instants</dfn> are defined according to xsd:dateTime [[!XMLSCHEMA-2]].</p>
-
-
-
-<p>It is OPTIONAL to assert time in usage, generation, and activity records.</p>
-
-
-
-
-</section>
-
-<section id="record-Asserter">
-<h3>Asserter</h3>
-
-<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">IRI</span> ::= <em>an IRI compatible with production IRI in [[!IRI]], enclosed in a pair of < (U+3C) and > (U+3E) characters </em>
-</div>
-
-<div class='issue'>
-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. This is <a href="http://www.w3.org/2011/prov/track/issues/217">ISSUE-217</a></div>
-
-</section>
-
-<section id="record-NamespaceDeclaration">
-<h3>Namespace Declaration</h3>
-
-<p>A PROV-DM <dfn id="dfn-namespace">namespace</dfn> is identified by an IRI reference [[!IRI]]. In PROV-DM, attributes, identifiers, and literals of with datatype <span
-class="name">xsd:QName</span> can be placed in a namespace using the mechanisms described in this specification. </p>
-
-
-<p>A <dfn id="dfn-namespaceDeclaration">namespace declaration</dfn> consists of a binding between a prefix and a namespace. Every qualified name with this prefix in the scope of this
-declaration refers to this namespace.
-A <dfn id="dfn-defaultNamespaceDeclaration">default namespace declaration</dfn> consists of a namespace. Every unprefixed qualified name in the scope of this default namespace declaration
-refers to this namespace.</p>
-
-<div class='grammar'>
-<span class="nonterminal">namespaceDeclarations</span> ::=
- | <span class="group"><span class="nonterminal">defaultNamespaceDeclaration</span> | <span class="nonterminal">namespaceDeclaration</span></span> <span class="star"> <span
-class="nonterminal">namespaceDeclaration</span></span><br>
-<span class="nonterminal">namespaceDeclaration</span> ::=
-<span class="name">prefix</span> <span class="nonterminal">prefix</span> <span class="nonterminal">IRI</span><br/>
-<span class="nonterminal">defaultNamespaceDeclaration</span> ::=
- <span class="name">default</span> <span class="nonterminal">IRI</span> <br/>
-</div>
-</section>
-
-
-
-
-
-
-<section id="record-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 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 attribute of entity records and activity records. The value associated with a attribute <span class="name">location</span> MUST be a <span
-class="nonterminal">Literal</span>, expected to denote a location.
-</p>
-
-
-
-
-</section>
-
-</section>
-
</section>
--- a/model/working-copy/towards-wd4.html Tue Feb 07 16:26:33 2012 +0000
+++ b/model/working-copy/towards-wd4.html Tue Feb 07 16:50:34 2012 +0000
@@ -1114,7 +1114,7 @@
<section id="record-alternate-specialization">
-<h4>Alternate and Specialization</h4>
+<h4>Alternate and Specialization</h4>
<p>The purpose of this section is to introduce relations between two entities that provide different characterizations for the same thing.
Consider for example three entities:
@@ -1169,7 +1169,7 @@
</ul>
-<p>A <dfn id="dfn-Specialization">specialization relation</dfn><span class="withAsn">, written <span class="name">specializationOf(id, sub, super, attrs)</span> in PROV-ASN,</span>, addresses case (2). It has the following constituents:</p>
+<p>A <dfn id="dfn-Specialization">specialization relation</dfn><span class="withAsn">, written <span class="name">specializationOf(id, sub, super, attrs)</span> in PROV-ASN,</span> addresses case (2). It has the following constituents:</p>
<ul>
<li><em>id</em>: an OPTIONAL identifier for the association between the two entities;</li>
@@ -1243,9 +1243,9 @@
<section id="sub-record">
-<h3>Further Terms in Records</h3>
+<h3>Further Terms of PROV-DM</h3>
-This section further terms in PROV-DM records.
+This section introduces further terms of PROV-DM.
@@ -1258,62 +1258,34 @@
<p>PROV-DM stipulates that 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>
+ by concatenating the IRI associated with the prefix and the local part.</p>
<p>A qualified name's prefix is OPTIONAL. If a prefix occurs in a
qualified name, it refers to a <a>namespace</a> declared in the
record container. In the absence of prefix, the qualified name
refers to the default namespace declared in the container.</p>
-<p>In PROV-ASN, an attribute's text matches the <span class="nonterminal">attribute</span> production of the grammar defined in this specification document.</p>
-
-<div class='grammar'>
-<span class="nonterminal">attribute</span> ::= <span class="nonterminal">qualifiedName</span><br/>
-<span class="nonterminal">qualifiedName</span> ::= <span class="nonterminal">prefixedName</span> | <span class="nonterminal">unprefixedName</span><br/>
-<span class="nonterminal">prefixedName</span> ::= <span class="nonterminal">prefix</span> <span class="name">:</span> <span class="nonterminal">localPart</span><br/>
-<span class="nonterminal">unprefixedName</span> ::= <span class="nonterminal">localPart</span><br/>
-<span class="nonterminal">prefix</span> ::= <em>a name without colon compatible with the <a href="http://www.w3.org/TR/2009/REC-xml-names-20091208/#NT-NCName">NC_NAME</a> production
-[[!XML-NAMES]]</em><br/>
-<span class="nonterminal">localPart</span> ::= <em>a name without colon compatible with the <a href="http://www.w3.org/TR/2009/REC-xml-names-20091208/#NT-NCName">NC_NAME</a> production
-[[!XML-NAMES]]</em>
-</div>
-
-
-<div class="note">Note that XML NC_NAME don't allow local identifiers to start with a number. Instead, should we use the productions used in SPARQL or TURTLE?</div>
-<p>
-For each attribute in a record, its namespace also declares the number of occurrences it
-may have in a list of attributes. The
-property <dfn>attribute occurrence validity</dfn> holds for a record
-if the actual number of occurrences of each attribute in this record is compatible with
-this attribute's declaration it its namespace. How to handle records
-that do not satisfy the <a>attribute occurrence validity</a> property
-is beyond the scope of this specification.</p>
-
-
-<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>The PROV data model introduces a fixed set of attributes in the <a href="#prov-dm-namespace">PROV-DM namespace</a>:</p>
+<p>The PROV data model introduces a fixed set of attributes in the <a href="#prov-dm-namespace">PROV-DM namespace</a>, which we define below.
+The interpretation of any attribute declared in another namespace is out of scope.</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 attribute <span class="name">prov:role</span> is allowed to occur multiple times in such records. The value associated with a <span
+activity association, activity start, and activity end. The attribute <span class="name">prov:role</span> is allowed to occur multiple times in such assertions. 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>
+<p>The following activity start 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>
</div>
</li>
-<li> The attribute <dfn id="dfn-type"><span class="name">prov:type</span></dfn> provides further typing information for the element or relation asserted in the record. PROV-DM liberally
+<li> The attribute <dfn id="dfn-type"><span class="name">prov:type</span></dfn> provides further typing information for an element or relation. PROV-DM liberally
defines a type as a category of things having common characteristics. PROV-DM is agnostic about the representation of types, and only states that
the value associated with a <span class="name">prov:type</span> attribute MUST be conformant with <span class="nonterminal">Literal</span>. The attribute <span class="name">prov:type</span>
-is allowed to occur multiple times in a record.</li>
+is allowed to occur multiple times.</li>
<div class="anexample">
<p>The following record declares an agent of type software agent</p>
@@ -1323,14 +1295,14 @@
</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
+<li> The attribute <dfn id="dfn-steps"><span class="name">prov:steps</span></dfn> defines the level of precision associated with a derivation. The value associated with a <span
class="name">prov:steps</span> attribute MUST be <span class="name">"single"</span> or <span class="name">"any"</span>. The attribute <span class="name">prov:step</span> occurs at most
-once in a derivation record. A derivation record without attribute <span class="name">prov:step</span> is considered to be equivalent to the same record extended with an extra attribute
+once in a derivation. A derivation without attribute <span class="name">prov:step</span> is considered to be equivalent to the same derivation extended with an extra attribute
<span class="name">prov:step</span> and associated value <span class="name">"any"</span>. </li>
<div class="anexample">
-<p>The following record declares an imprecise-1 derivation, which is known to involve one activity, though its identity, usage details of <span class="name">ex:e1</span>, and generation
-details of <span class="name">ex:e2</span> are not asserted.</p>
+<p>The following expression declares an imprecise-1 derivation, which is known to involve one activity, though its identity, usage details of <span class="name">ex:e1</span>, and generation
+details of <span class="name">ex:e2</span> are not explicit.</p>
<pre class="codeexample">
wasDerivedFrom(ex:e2, ex:e1, [prov:steps="single"])
</pre>
@@ -1351,21 +1323,10 @@
<h4>Identifier</h4>
-<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> ::= <span class="nonterminal">qualifiedName</span><br/>
-<span class="nonterminal">eIdentifier</span> ::= <span class="nonterminal">identifier</span> <em>(intended to denote an entity record)</em><br/>
-<span class="nonterminal">aIdentifier</span> ::= <span class="nonterminal">identifier</span> <em>(intended to denote an activity record)</em><br/>
-<span class="nonterminal">agIdentifier</span> ::= <span class="nonterminal">identifier</span> <em>(intended to denote an agent record)</em><br/>
-<span class="nonterminal">gIdentifier</span>::= <span class="nonterminal">identifier</span> <em>(intended to denote a generation record)</em><br/>
-<span class="nonterminal">uIdentifier</span>::= <span class="nonterminal">identifier</span> <em>(intended to denote a usage record)</em><br/>
-<span class="nonterminal">nIdentifier</span>::= <span class="nonterminal">identifier</span> <em>(intended to denote a note record)</em><br/>
-<span class="nonterminal">accIdentifier</span>::= <span class="nonterminal">identifier</span> <em>(intended to denote an account record)</em>
-</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.</p>
</section>
@@ -1377,42 +1338,19 @@
or number. A PROV-DM Literal represents a value whose interpretation is outside the scope of PROV-DM.
</p>
-<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">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">intLiteral</span> ::= <em>a finite-length sequence of decimal digits (#x30-#x39) with an optional leading negative sign (-)</em>
-</div>
-
-<p>The non terminals <span class="nonterminal">stringLiteral</span> and
-<span class="nonterminal">intLiteral</span>
-are syntactic sugar for quoted strings with datatype <span class="name">xsd:string</span> and <span class="name">xsd:int</span>, respectively.
-</p>
-
-<p> In particular, a PROV-DM Literal may be an 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" (expressed using the convenience notation), the string "abc", the integer number 1, the integer number 1 (expressed using the
-convenience notation) and the IRI "http://example.org/foo".
+The following examples respectively are the string "abc", the string "abc", the integer number 1, and the IRI "http://example.org/foo".
<pre class="codeexample">
"abc"
- "abc" %% xsd:string
- "1" %% xsd:int
1
"http://example.org/foo" %% xsd:anyURI
</pre>
The following example shows a literal of type <span class="name">xsd:QName</span> (see
<a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#QName">QName</a> [[!XMLSCHEMA-2]]).
The prefix <span class="name">ex</span> MUST be bound to a <a>namespace</a> declared in the
- record container.
+ container.
<pre class="codeexample">
"ex:value" %% xsd:QName
</pre>
@@ -1420,10 +1358,6 @@
-<div class='note'>Should we define structural equivalence of literals as in OWL2? [[!OWL2-SYNTAX]]
-(see section <a href="http://www.w3.org/TR/2009/REC-owl2-syntax-20091027/#Literals">Literals</a>).
-</div>
-
</section>
@@ -1454,23 +1388,8 @@
declaration refers to this namespace.
A <dfn id="dfn-defaultNamespaceDeclaration">default namespace declaration</dfn> consists of a namespace. Every unprefixed qualified name in the scope of this default namespace declaration
refers to this namespace.</p>
-
-<div class='grammar'>
-<span class="nonterminal">namespaceDeclarations</span> ::=
- | <span class="group"><span class="nonterminal">defaultNamespaceDeclaration</span> | <span class="nonterminal">namespaceDeclaration</span></span> <span class="star"> <span
-class="nonterminal">namespaceDeclaration</span></span><br>
-<span class="nonterminal">namespaceDeclaration</span> ::=
-<span class="name">prefix</span> <span class="nonterminal">prefix</span> <span class="nonterminal">IRI</span><br/>
-<span class="nonterminal">defaultNamespaceDeclaration</span> ::=
- <span class="name">default</span> <span class="nonterminal">IRI</span> <br/>
-</div>
</section>
-
-
-
-
-
<section id="record-Location">
<h3>Location</h3>