--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/model/examples/sculpture.pn Thu Mar 08 21:34:00 2012 +0000
@@ -0,0 +1,31 @@
+container
+
+prefix ex <http://example.org/>
+
+entity(ex:s, [ prov:type="sculpture" ])
+entity(ex:h, [ prov:type="hand" ])
+entity(ex:l, [ prov:type="leg" ])
+wasDerivedFrom(ex:s,ex:h, [ prov:type="contained" ])
+wasDerivedFrom(ex:s,ex:l, [ prov:type="contained" ])
+
+entity(ex:s_2, [ prov:type="sculpture" ])
+entity(ex:h_2, [ prov:type="hand" ])
+activity(ex:a1, ,, [ prov:type="sculptHand" ])
+
+wasDerivedFrom(ex:s_2,ex:h_2, [ prov:type="contained" ])
+wasDerivedFrom(ex:s_2,ex:l, [ prov:type="contained" ])
+wasDerivedFrom(ex:h_2,ex:h, [ prov:type="refinementOf" ])
+wasDerivedFrom(ex:s_2,ex:s, [ prov:type="refinementOf" ])
+wasGeneratedBy(ex:h_2,ex:a1)
+
+entity(ex:s_3, [ prov:type="sculpture" ])
+entity(ex:l_3, [ prov:type="leg" ])
+activity(ex:a2, ,, [ prov:type="sculptLeg" ])
+
+wasDerivedFrom(ex:s_3,ex:h_2, [ prov:type="contained" ])
+wasDerivedFrom(ex:s_3,ex:l_3, [ prov:type="contained" ])
+wasDerivedFrom(ex:l_3,ex:l, [ prov:type="refinementOf" ])
+wasDerivedFrom(ex:s_3,ex:s_2, [ prov:type="refinementOf" ])
+wasGeneratedBy(ex:l_3,ex:a2)
+
+endContainer
\ No newline at end of file
--- a/model/examples/sculpture.prov-asn Thu Mar 08 17:23:30 2012 +0000
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,31 +0,0 @@
-container
-
-prefix ex <http://example.org/>
-
-entity(ex:s, [ prov:type="sculpture" ])
-entity(ex:h, [ prov:type="hand" ])
-entity(ex:l, [ prov:type="leg" ])
-wasDerivedFrom(ex:s,ex:h, [ prov:type="contained" ])
-wasDerivedFrom(ex:s,ex:l, [ prov:type="contained" ])
-
-entity(ex:s_2, [ prov:type="sculpture" ])
-entity(ex:h_2, [ prov:type="hand" ])
-activity(ex:a1, ,, [ prov:type="sculptHand" ])
-
-wasDerivedFrom(ex:s_2,ex:h_2, [ prov:type="contained" ])
-wasDerivedFrom(ex:s_2,ex:l, [ prov:type="contained" ])
-wasDerivedFrom(ex:h_2,ex:h, [ prov:type="refinementOf" ])
-wasDerivedFrom(ex:s_2,ex:s, [ prov:type="refinementOf" ])
-wasGeneratedBy(ex:h_2,ex:a1)
-
-entity(ex:s_3, [ prov:type="sculpture" ])
-entity(ex:l_3, [ prov:type="leg" ])
-activity(ex:a2, ,, [ prov:type="sculptLeg" ])
-
-wasDerivedFrom(ex:s_3,ex:h_2, [ prov:type="contained" ])
-wasDerivedFrom(ex:s_3,ex:l_3, [ prov:type="contained" ])
-wasDerivedFrom(ex:l_3,ex:l, [ prov:type="refinementOf" ])
-wasDerivedFrom(ex:s_3,ex:s_2, [ prov:type="refinementOf" ])
-wasGeneratedBy(ex:l_3,ex:a2)
-
-endContainer
\ No newline at end of file
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/model/examples/w3c-publication1.pn Thu Mar 08 21:34:00 2012 +0000
@@ -0,0 +1,48 @@
+
+
+container
+
+prefix ex </http://example.org/>
+
+prefix w3 <http://www.w3.org/>
+prefix tr <http://www.w3.org/TR/2011/>
+prefix pr <http://www.w3.org/2005/10/Process-20051014/tr.html#>
+
+prefix ar1 <https://lists.w3.org/Archives/Member/chairs/2011OctDec/>
+prefix ar2 <https://lists.w3.org/Archives/Member/w3c-archive/2011Oct/>
+prefix ar3 <https://lists.w3.org/Archives/Member/w3c-archive/2011Dec/>
+
+
+entity(tr:WD-prov-dm-20111018, [ prov:type="pr:RecsWD" %% xsd:QName ])
+entity(tr:WD-prov-dm-20111215, [ prov:type="pr:RecsWD" %% xsd:QName ])
+entity(pr:rec-advance, [ prov:type="prov:Plan" %% xsd:QName ])
+
+
+entity(ar1:0004, [ prov:type="http://www.w3.org/2005/08/01-transitions.html#transreq" %% xsd:anyURI ])
+entity(ar2:0141, [ prov:type="http://www.w3.org/2005/08/01-transitions.html#pubreq" %% xsd:anyURI ])
+entity(ar3:0111, [ prov:type="http://www.w3.org/2005/08/01-transitions.html#pubreq" %% xsd:anyURI ])
+
+
+wasDerivedFrom(tr:WD-prov-dm-20111215,tr:WD-prov-dm-20111018)
+
+
+activity(ex:act1,,,[prov:type="publish"])
+activity(ex:act2,,,[prov:type="publish"])
+
+
+wasGeneratedBy(tr:WD-prov-dm-20111018, ex:act1)
+wasGeneratedBy(tr:WD-prov-dm-20111215, ex:act2)
+
+used(ex:act1,ar1:0004)
+used(ex:act1,ar2:0141)
+used(ex:act2,ar3:0111)
+
+agent(w3:Consortium, [ prov:type="Organization" ])
+
+wasAssociatedWith(ex:act1, w3:Consortium @ pr:rec-advance)
+wasAssociatedWith(ex:act2, w3:Consortium @ pr:rec-advance)
+
+
+
+endContainer
+
--- a/model/examples/w3c-publication1.prov-asn Thu Mar 08 17:23:30 2012 +0000
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,48 +0,0 @@
-
-
-container
-
-prefix ex </http://example.org/>
-
-prefix w3 <http://www.w3.org/>
-prefix tr <http://www.w3.org/TR/2011/>
-prefix pr <http://www.w3.org/2005/10/Process-20051014/tr.html#>
-
-prefix ar1 <https://lists.w3.org/Archives/Member/chairs/2011OctDec/>
-prefix ar2 <https://lists.w3.org/Archives/Member/w3c-archive/2011Oct/>
-prefix ar3 <https://lists.w3.org/Archives/Member/w3c-archive/2011Dec/>
-
-
-entity(tr:WD-prov-dm-20111018, [ prov:type="pr:RecsWD" %% xsd:QName ])
-entity(tr:WD-prov-dm-20111215, [ prov:type="pr:RecsWD" %% xsd:QName ])
-entity(pr:rec-advance, [ prov:type="prov:Plan" %% xsd:QName ])
-
-
-entity(ar1:0004, [ prov:type="http://www.w3.org/2005/08/01-transitions.html#transreq" %% xsd:anyURI ])
-entity(ar2:0141, [ prov:type="http://www.w3.org/2005/08/01-transitions.html#pubreq" %% xsd:anyURI ])
-entity(ar3:0111, [ prov:type="http://www.w3.org/2005/08/01-transitions.html#pubreq" %% xsd:anyURI ])
-
-
-wasDerivedFrom(tr:WD-prov-dm-20111215,tr:WD-prov-dm-20111018)
-
-
-activity(ex:act1,,,[prov:type="publish"])
-activity(ex:act2,,,[prov:type="publish"])
-
-
-wasGeneratedBy(tr:WD-prov-dm-20111018, ex:act1)
-wasGeneratedBy(tr:WD-prov-dm-20111215, ex:act2)
-
-used(ex:act1,ar1:0004)
-used(ex:act1,ar2:0141)
-used(ex:act2,ar3:0111)
-
-agent(w3:Consortium, [ prov:type="Organization" ])
-
-wasAssociatedWith(ex:act1, w3:Consortium @ pr:rec-advance)
-wasAssociatedWith(ex:act2, w3:Consortium @ pr:rec-advance)
-
-
-
-endContainer
-
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/model/examples/w3c-publication2.pn Thu Mar 08 21:34:00 2012 +0000
@@ -0,0 +1,45 @@
+
+
+container
+
+prefix ex <http://example.org/>
+prefix rec <http://example.org/record>
+
+prefix w3 <http://www.w3.org/TR/2011/>
+prefix hg <http://dvcs.w3.org/hg/prov/raw-file/9628aaff6e20/model/releases/WD-prov-dm-20111215/>
+prefix process <http://www.w3.org/2005/10/Process-20051014/tr.html#>
+
+
+
+entity(hg:Overview.html, [ prov:type="file in hg" ])
+
+entity(w3:WD-prov-dm-20111215, [ prov:type="html4" ])
+
+
+
+
+
+
+activity(ex:rcp,,,[prov:type="copy directory"])
+
+
+wasGeneratedBy(rec:g,w3:WD-prov-dm-20111215, ex:rcp)
+
+entity(ex:req3, [ prov:type="http://www.w3.org/2005/08/01-transitions.html#pubreq" %% xsd:anyURI ])
+
+used(rec:u, ex:rcp,hg:Overview.html)
+used(ex:rcp,ex:req3)
+
+
+wasDerivedFrom(w3:WD-prov-dm-20111215,hg:Overview.html, ex:rcp, rec:g, rec:u)
+
+agent(ex:webmaster, [ prov:type="Person" ])
+
+wasAssociatedWith(ex:rcp, ex:webmaster)
+
+endContainer
+
+
+#activity(ex:a5,,,[prov:type="grammarcheck"])
+#ex:version="1",
+#ex:version="2"
\ No newline at end of file
--- a/model/examples/w3c-publication2.prov-asn Thu Mar 08 17:23:30 2012 +0000
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,45 +0,0 @@
-
-
-container
-
-prefix ex <http://example.org/>
-prefix rec <http://example.org/record>
-
-prefix w3 <http://www.w3.org/TR/2011/>
-prefix hg <http://dvcs.w3.org/hg/prov/raw-file/9628aaff6e20/model/releases/WD-prov-dm-20111215/>
-prefix process <http://www.w3.org/2005/10/Process-20051014/tr.html#>
-
-
-
-entity(hg:Overview.html, [ prov:type="file in hg" ])
-
-entity(w3:WD-prov-dm-20111215, [ prov:type="html4" ])
-
-
-
-
-
-
-activity(ex:rcp,,,[prov:type="copy directory"])
-
-
-wasGeneratedBy(rec:g,w3:WD-prov-dm-20111215, ex:rcp)
-
-entity(ex:req3, [ prov:type="http://www.w3.org/2005/08/01-transitions.html#pubreq" %% xsd:anyURI ])
-
-used(rec:u, ex:rcp,hg:Overview.html)
-used(ex:rcp,ex:req3)
-
-
-wasDerivedFrom(w3:WD-prov-dm-20111215,hg:Overview.html, ex:rcp, rec:g, rec:u)
-
-agent(ex:webmaster, [ prov:type="Person" ])
-
-wasAssociatedWith(ex:rcp, ex:webmaster)
-
-endContainer
-
-
-#activity(ex:a5,,,[prov:type="grammarcheck"])
-#ex:version="1",
-#ex:version="2"
\ No newline at end of file
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/model/examples/w3c-publication3.pn Thu Mar 08 21:34:00 2012 +0000
@@ -0,0 +1,42 @@
+
+
+container
+
+prefix ex <http://example.org/>
+
+prefix w3 <http://www.w3.org/>
+prefix tr <http://www.w3.org/TR/2011/>
+
+entity(tr:WD-prov-dm-20111215, [ prov:type="document", ex:version="2" ])
+
+agent(ex:Luc, [ prov:type="Person" ])
+agent(ex:Paolo, [ prov:type="Person" ])
+agent(ex:Khalid, [ prov:type="Person" ])
+agent(ex:Stephen, [ prov:type="Person" ])
+agent(ex:Yolanda, [ prov:type="Person" ])
+agent(ex:Ryan, [ prov:type="Person" ])
+agent(ex:Paul, [ prov:type="Person" ])
+agent(ex:Graham, [ prov:type="Person" ])
+agent(ex:Jim, [ prov:type="Person" ])
+agent(ex:Simon, [ prov:type="Person" ])
+agent(ex:James, [ prov:type="Person" ])
+agent(ex:Satya, [ prov:type="Person" ])
+
+activity(ex:edit1,,,[prov:type="edit"])
+
+wasGeneratedBy(tr:WD-prov-dm-20111215, ex:edit1)
+
+wasAssociatedWith(ex:edit1, ex:Luc, [prov:role="editor"])
+wasAssociatedWith(ex:edit1, ex:Paolo, [prov:role="editor"])
+wasAssociatedWith(ex:edit1, ex:Khalid, [prov:role="contributor"])
+wasAssociatedWith(ex:edit1, ex:Stephen, [prov:role="contributor"])
+wasAssociatedWith(ex:edit1, ex:Yolanda, [prov:role="contributor"])
+wasAssociatedWith(ex:edit1, ex:Ryan, [prov:role="contributor"])
+wasAssociatedWith(ex:edit1, ex:Paul, [prov:role="contributor"])
+wasAssociatedWith(ex:edit1, ex:Graham, [prov:role="contributor"])
+wasAssociatedWith(ex:edit1, ex:Jim, [prov:role="contributor"])
+wasAssociatedWith(ex:edit1, ex:Simon, [prov:role="contributor"])
+wasAssociatedWith(ex:edit1, ex:James, [prov:role="contributor"])
+wasAssociatedWith(ex:edit1, ex:Satya, [prov:role="contributor"])
+
+endContainer
--- a/model/examples/w3c-publication3.prov-asn Thu Mar 08 17:23:30 2012 +0000
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,42 +0,0 @@
-
-
-container
-
-prefix ex <http://example.org/>
-
-prefix w3 <http://www.w3.org/>
-prefix tr <http://www.w3.org/TR/2011/>
-
-entity(tr:WD-prov-dm-20111215, [ prov:type="document", ex:version="2" ])
-
-agent(ex:Luc, [ prov:type="Person" ])
-agent(ex:Paolo, [ prov:type="Person" ])
-agent(ex:Khalid, [ prov:type="Person" ])
-agent(ex:Stephen, [ prov:type="Person" ])
-agent(ex:Yolanda, [ prov:type="Person" ])
-agent(ex:Ryan, [ prov:type="Person" ])
-agent(ex:Paul, [ prov:type="Person" ])
-agent(ex:Graham, [ prov:type="Person" ])
-agent(ex:Jim, [ prov:type="Person" ])
-agent(ex:Simon, [ prov:type="Person" ])
-agent(ex:James, [ prov:type="Person" ])
-agent(ex:Satya, [ prov:type="Person" ])
-
-activity(ex:edit1,,,[prov:type="edit"])
-
-wasGeneratedBy(tr:WD-prov-dm-20111215, ex:edit1)
-
-wasAssociatedWith(ex:edit1, ex:Luc, [prov:role="editor"])
-wasAssociatedWith(ex:edit1, ex:Paolo, [prov:role="editor"])
-wasAssociatedWith(ex:edit1, ex:Khalid, [prov:role="contributor"])
-wasAssociatedWith(ex:edit1, ex:Stephen, [prov:role="contributor"])
-wasAssociatedWith(ex:edit1, ex:Yolanda, [prov:role="contributor"])
-wasAssociatedWith(ex:edit1, ex:Ryan, [prov:role="contributor"])
-wasAssociatedWith(ex:edit1, ex:Paul, [prov:role="contributor"])
-wasAssociatedWith(ex:edit1, ex:Graham, [prov:role="contributor"])
-wasAssociatedWith(ex:edit1, ex:Jim, [prov:role="contributor"])
-wasAssociatedWith(ex:edit1, ex:Simon, [prov:role="contributor"])
-wasAssociatedWith(ex:edit1, ex:James, [prov:role="contributor"])
-wasAssociatedWith(ex:edit1, ex:Satya, [prov:role="contributor"])
-
-endContainer
--- a/model/prov-asn.html Thu Mar 08 17:23:30 2012 +0000
+++ b/model/prov-asn.html Thu Mar 08 21:34:00 2012 +0000
@@ -1,7 +1,6 @@
<!DOCTYPE html>
<html><head>
-<!-- <title>PROV-DM Part 3: PROV-ASN: The Provenance Abstract Syntax Notation</title> -->
<title>PROV-DM Part 3: PROV-N: The Provenance Notation</title>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<!--
@@ -117,7 +116,8 @@
// if your specification has a subtitle that goes below the main
// formal title, define it here
- subtitle : "Draft (WD4) for internal discussion",
+ subtitle : "About-to-be-frozen WD4 (for internal release)",
+
// if you wish the publication date to be other than today, set this
// publishDate: "2011-10-18",
@@ -132,7 +132,7 @@
//previousMaturity: "WD",
// if there a publicly available Editor's Draft, this is the link
- edDraftURI: "http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-asn.html",
+ edDraftURI: "http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-n.html",
// if this is a LCWD, uncomment and set the end of its review period
// lcEnd: "2009-08-05",
@@ -190,7 +190,7 @@
producing a piece of data or thing in the world. PROV-DM is
domain-agnostic, but is equipped with extensibility points allowing
further domain-specific and application-specific extensions to be
-defined. PROV-DM is accompanied by PROV-ASN, a technology-independent
+defined. PROV-DM is accompanied by PROV-N, a technology-independent
abstract syntax notation, which allows serializations of PROV-DM
instances to be created for human consumption, which facilitates its
mapping to concrete syntax, and which is used as the basis for a
@@ -207,7 +207,7 @@
instances of that data model for human consumption. Other documents are:
<ul>
<li> PROV-DM-CONSTRAINTS, a set of constraints applying to the PROV-DM data model,</li>
-<li> PROV-ASN, a notation for provenance aimed at human consumption,</li>
+<li> PROV-N, a notation for provenance aimed at human consumption,</li>
<li> PROV-O, the provenance ontology: by means of a mapping of PROV-DM to the OWL2 Web Ontology Language, this specification provides a normative serialization of PROV-DM in RDF</li>
<li> PROV-AQ, provenance access and query: the mechanisms for accessing and querying provenance; </li>
<li> PROV-PRIMER: a primer for the PROV-DM provenance data model,</li>
@@ -238,20 +238,20 @@
</p>
-<p>In this context, PROV-ASN was introduced as a notation to write instances of the data model, as close to its abstract syntax as possible. PROV-ASN is primarily aimed at human consumption. PROV-ASN allows
+<p>In this context, PROV-N was introduced as a notation to write instances of the data model, as close to its abstract syntax as possible. PROV-N is primarily aimed at human consumption. PROV-N allows
serializations of PROV-DM instances to be written in a technology independent manner.
-So far, PROV-ASN has been used in the following ways:</p>
+So far, PROV-N has been used in the following ways:</p>
<ul>
-<li> PROV-ASN is used to provide technology independent illustrations in [[PROV-DM]] and in the definition of PROV-DM constraints [[PROV-DM-CONSTRAINTS]];</li>
-<li> PROV-ASN is instrumental in defining the mapping mapping of PROV-DM to concrete syntaxes. Mappings translate each PROV-ASN expression to RDF [[PROV-RDF]] and to XML [[PROV-XML]];</li>
-<li> PROV-ASN is the basis for a
-formal semantics, in which each PROV-ASN expression is provided with an interpretation [[PROV-SEM]].
+<li> PROV-N is used to provide technology independent illustrations in [[PROV-DM]] and in the definition of PROV-DM constraints [[PROV-DM-CONSTRAINTS]];</li>
+<li> PROV-N is instrumental in defining the mapping mapping of PROV-DM to concrete syntaxes. Mappings translate each PROV-N expression to RDF [[PROV-RDF]] and to XML [[PROV-XML]];</li>
+<li> PROV-N is the basis for a
+formal semantics, in which each PROV-N expression is provided with an interpretation [[PROV-SEM]].
</ul>
-<p>PROV-ASN was designed to be as close as possible to PROV-DM without the syntactic bias and modelling constraints that concrete technologies bring with them, e.g., XML's choice between attribute and element, RDF's reliance on triples, or JSON's usage of dictionaries. </p>
+<p>PROV-N was designed to be as close as possible to PROV-DM without the syntactic bias and modelling constraints that concrete technologies bring with them, e.g., XML's choice between attribute and element, RDF's reliance on triples, or JSON's usage of dictionaries. </p>
-<p>The purpose of this document is solely to define the syntax of PROV-ASN.
-For each construct of PROV-DM, a corresponding ASN expression is introduced, by way of a production in the PROV-ASN grammar presented in this document. </p>
+<p>The purpose of this document is solely to define the syntax of PROV-N.
+For each construct of PROV-DM, a corresponding PROV-N expression is introduced, by way of a production in the PROV-N grammar presented in this document. </p>
<p>This specification is one of several specifications, referred to as the PROV family of specifications, defining the various aspects
@@ -261,7 +261,7 @@
<ul>
<li> PROV-DM (part I): the provenance data model itself, expressed in natural language [[PROV-DM]];
<li> PROV-DM-CONSTRAINTS (part II): constraints underpinning the data model [[PROV-DM-CONSTRAINTS]];
-<li> PROV-ASN (part III): a notation to express instances of that data model for human consumption (this document);
+<li> PROV-N (part III): a notation to express instances of that data model for human consumption (this document);
</ul>
</li>
@@ -315,7 +315,7 @@
<section id="grammar-notation">
<h3>Grammar Notation</h3>
-<p>This specification includes a grammar for PROV-ASN expressed using the Extended Backus-Naur Form (EBNF) notation.</p>
+<p>This specification includes a grammar for PROV-N expressed using the Extended Backus-Naur Form (EBNF) notation.</p>
<div class="grammar">
<p> Each production rule (or <dfn>production</dfn>, for short) in the grammar defines one non-terminal symbol, in the form:</p>
@@ -357,7 +357,7 @@
<h2>PROV-DM Core</h2>
-<p>Instances of the PROV-DM data model are expressed in PROV-ASN by a text conformant with the toplevel <a>production</a> <span class="nonterminal">expression</span> of the grammar. These <span
+<p>Instances of the PROV-DM data model are expressed in PROV-N by a text conformant with the toplevel <a>production</a> <span class="nonterminal">expression</span> of the grammar. These <span
class="nonterminal">expression</span>s are grouped in two categories:
<span class="nonterminal">elementExpression</span> (see section <a href="#expression-element">Element</a>) and
<span class="nonterminal">relationExpression</span> (see section <a href="#expression-relation">Relation</a>).</p>
@@ -403,7 +403,7 @@
<h4>Entity</h4>
-<div class="withAsn">
+<div class="withPn">
<p>
An entity's text matches the <span class="nonterminal">entityExpression</span> production.
</p>
@@ -450,7 +450,7 @@
<h3>Activity</h3>
-<div class="withAsn">
+<div class="withPn">
<p>An activity's text matches the <span class='nonterminal'>activityExpression</span> production.</p>
@@ -485,7 +485,7 @@
<h3>Agent</h3>
-<div class="withAsn">
+<div class="withPn">
<p>An agent's text matches the <span class="nonterminal">agentExpression</span> production.
</p>
@@ -514,7 +514,7 @@
<h4>Note</h4>
-<div class="withAsn">
+<div class="withPn">
<p>A note's text matches the <span class="nonterminal">noteExpression</span> production.
</p>
@@ -554,7 +554,7 @@
<h4>Generation</h4>
-<div class="withAsn">
+<div class="withPn">
<p>A generation's text matches the <span class='nonterminal'>generationExpression</span> production.</p>
<div class='grammar'>
@@ -884,7 +884,7 @@
<section id="subexpressions">
<h3>Further Expressions</h3>
-This section defines further expressions of PROV-ASN.
+This section defines further expressions of PROV-N.
<section id="expression-NamespaceDeclaration">
@@ -901,7 +901,7 @@
<span class="name">default</span> <span class="nonterminal">IRI</span> <br/>
</div>
-<p>In PROV-ASN, the prefix <span class="name">prov</span> is reserved and denotes the PROV namespace.</p>
+<p>In PROV-N, the prefix <span class="name">prov</span> is reserved and denotes the PROV namespace.</p>
</section>
@@ -1044,13 +1044,13 @@
<section id="ExpressionContainer">
<h4>Expression Container</h4>
-<p>An <dfn id="dfn-ExpressionContainer">expression container</dfn> is a house-keeping construct of PROV-ASN capable of packaging up PROV-ASN <a title="expression">expressions</a> and namespace declarations. An expression container forms a self-contained package of provenance descriptions for the purpose of <em>exchanging</em> them. An expression container may be used
- to package up PROV-ASN <a title="record">expressions</a> in response to a request for the provenance of something ([[PROV-AQ]]).</p>
+<p>An <dfn id="dfn-ExpressionContainer">expression container</dfn> is a house-keeping construct of PROV-N capable of packaging up PROV-N <a title="expression">expressions</a> and namespace declarations. An expression container forms a self-contained package of provenance descriptions for the purpose of <em>exchanging</em> them. An expression container may be used
+ to package up PROV-N <a title="record">expressions</a> in response to a request for the provenance of something ([[PROV-AQ]]).</p>
-<p> Given its status of house keeping construct for the purpose of exchanging provenance expressions, an expression container is not defined as a PROV-ASN expression (<a href="#data-model-concepts">production <span class="nonterminal">expression</span></a>).</p>
+<p> Given its status of house keeping construct for the purpose of exchanging provenance expressions, an expression container is not defined as a PROV-N expression (<a href="#data-model-concepts">production <span class="nonterminal">expression</span></a>).</p>
-<p>An expression container, written <span class="name">container decls exprs endContainer</span> in PROV-ASN, contains:
+<p>An expression container, written <span class="name">container decls exprs endContainer</span> in PROV-N, contains:
<ul>
<li><em>namespaceDeclarations</em>: a set <span class="name">decls</span> of namespace declarations, declaring namespaces and associated prefixes, which can be used in <a
title="attribute">attributes</a> and <a title="identifier">identifiers</a> occurring inside <span class="name">exprs</span>;</li>
@@ -1104,17 +1104,17 @@
<p>PROV-DM has introduced a notion of account by which a set of provenance descriptions can be bundled up and named. PROV-DM <em>assumes</em> the existence of mechanisms to implement accounts, but such mechanisms remain outside its scope. It is suggested that specific serializations may offer solutions to name bundles of descriptions. </p>
-<p>Given that the primary motivation for PROV-ASN is to provide a notation aimed at human consumption, it is therefore appropriate to introduce a notation for accounts, which would include an account name and a bundle of expressions.</p>
+<p>Given that the primary motivation for PROV-N is to provide a notation aimed at human consumption, it is therefore appropriate to introduce a notation for accounts, which would include an account name and a bundle of expressions.</p>
-<p>An account, written <span class="name">account(id, exprs)</span> in PROV-ASN, contains:</p>
+<p>An account, written <span class="name">account(id, exprs)</span> in PROV-N, contains:</p>
<ul>
<li><em>id</em>: an identifier <span class="name">id</span> that identifies this account;</li>
<li><em>expressions</em>: a set <span class="name">exprs</span> of expressions;</li>
</ul>
-<p>In PROV-ASN, an account's text matches the <span class="nonterminal">accountExpression</span> production of the grammar.</p>
+<p>In PROV-N, an account's text matches the <span class="nonterminal">accountExpression</span> production of the grammar.</p>
<div class='grammar'>
<span class="nonterminal">accountExpression</span> ::=
@@ -1154,7 +1154,7 @@
account(ex:acc2,...)
endContainer
</pre>
-<p> illustrates how two accounts with identifiers <span class="name">ex:acc1</span> and <span class="name">ex:acc2</span> can be returned in a PROV-ASN serialization of the provenance of
+<p> illustrates how two accounts with identifiers <span class="name">ex:acc1</span> and <span class="name">ex:acc2</span> can be returned in a PROV-N serialization of the provenance of
something.
</p>
</div>
--- a/model/prov-dm-constraints.html Thu Mar 08 17:23:30 2012 +0000
+++ b/model/prov-dm-constraints.html Thu Mar 08 21:34:00 2012 +0000
@@ -57,11 +57,11 @@
"2011, Working Draft. "+
"URL: <a href=\"http://www.w3.org/TR/prov-dm/\">http://www.w3.org/TR/prov-dm/</a>",
- "PROV-ASN":
+ "PROV-N":
"Luc Moreau and Paolo Missier (eds.) ... "+
- "<a href=\"http://www.w3.org/TR/prov-asn/\"><cite>PROV-ASN ....</cite></a>. "+
+ "<a href=\"http://www.w3.org/TR/prov-n/\"><cite>PROV-N ....</cite></a>. "+
"2011, Working Draft. "+
- "URL: <a href=\"http://www.w3.org/TR/prov-asn/\">http://www.w3.org/TR/prov-asn/</a>",
+ "URL: <a href=\"http://www.w3.org/TR/prov-n/\">http://www.w3.org/TR/prov-n/</a>",
"PROV-O":
@@ -85,8 +85,8 @@
// if your specification has a subtitle that goes below the main
// formal title, define it here
- subtitle : "Draft (WD4) for internal discussion",
-
+ subtitle : "About-to-be-frozen WD4 (for internal release)",
+
// if you wish the publication date to be other than today, set this
//publishDate: "2012-02-01",
@@ -100,7 +100,7 @@
//previousMaturity: "WD",
// if there a publicly available Editor's Draft, this is the link
- edDraftURI: "http://dvcs.w3.org/hg/prov/raw-file/default/model/working-copy/prov-dm-constraints.html",
+ edDraftURI: "http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm-constraints.html",
// if this is a LCWD, uncomment and set the end of its review period
// lcEnd: "2009-08-05",
@@ -158,7 +158,7 @@
producing a piece of data or thing in the world. PROV-DM is
domain-agnostic, but is equipped with extensibility points allowing
further domain-specific and application-specific extensions to be
-defined. PROV-DM is accompanied by PROV-ASN, a technology-independent
+defined. PROV-DM is accompanied by PROV-N, a technology-independent
abstract syntax notation, which allows serializations of PROV-DM
instances to be created for human consumption, which facilitates its
mapping to concrete syntax, and which is used as the basis for a
@@ -175,7 +175,7 @@
instances of that data model for human consumption. Other documents are:
<ul>
<li> PROV-DM-CONSTRAINTS, a set of constraints applying to the PROV-DM data model,</li>
-<li> PROV-ASN, a notation for provenance aimed at human consumption,</li>
+<li> PROV-N, a notation for provenance aimed at human consumption,</li>
<li> PROV-O, the provenance ontology: by means of a mapping of PROV-DM to the OWL2 Web Ontology Language, this specification provides a normative serialization of PROV-DM in RDF</li>
<li> PROV-AQ, provenance access and query: the mechanisms for accessing and querying provenance; </li>
<li> PROV-PRIMER: a primer for the PROV-DM provenance data model,</li>
@@ -222,7 +222,7 @@
<ul>
<li> PROV-DM (part I): the provenance data model itself, expressed in natural language [[PROV-DM]];
<li> PROV-DM-CONSTRAINTS (part II): constraints underpinning the data model (this document);
-<li> PROV-ASN (part III): a notation to express instances of that data model for human consumption [[PROV-ASN]];
+<li> PROV-N (part III): a notation to express instances of that data model for human consumption [[PROV-N]];
</ul>
</li>
@@ -1533,7 +1533,7 @@
Satya discussed the example of a sculpture, whose hand and leg are sculpted independently by two different sculptors. He suggested that the sculpture is generated by two distinct activities.
This section explains that it is not the case. The example can be formulated as follows.
-<p><a href="examples/sculpture.prov-asn">Sculpture example in ASN</a></p>
+<p><a href="examples/sculpture.pn">Sculpture example in PROV-N</a></p>
<p><a href="examples/sculpture.png">Sculpture example image</a></p>
@@ -1674,7 +1674,7 @@
<p>In the context of PROV-DM, a resource is just a thing in the world. One may take multiple perspectives on such a thing and its situation in the world, fixing some its aspects.</p>
<p> We refer to the <a href="#a-report-example">example</a> of section <a href="#conceptualization">2.1</a> for a resource (at some URL) and three different perspectives, referred to as
-entities. Three different entity records can be expressed for this report, which in the PROV-ASN sample below, are expressed within a same account.
+entities. Three different entity records can be expressed for this report, which in the PROV-N sample below, are expressed within a same account.
</p>
<pre>
--- a/model/prov-dm.html Thu Mar 08 17:23:30 2012 +0000
+++ b/model/prov-dm.html Thu Mar 08 21:34:00 2012 +0000
@@ -93,11 +93,11 @@
"2011, Working Draft. "+
"URL: <a href=\"http://www.w3.org/TR/prov-dm-constraints/\">http://www.w3.org/TR/prov-dm-constraints/</a>",
- "PROV-ASN":
+ "PROV-N":
"Luc Moreau and Paolo Missier (eds.) ... "+
- "<a href=\"http://www.w3.org/TR/prov-asn/\"><cite>PROV-ASN ....</cite></a>. "+
+ "<a href=\"http://www.w3.org/TR/prov-n/\"><cite>PROV-N ....</cite></a>. "+
"2011, Working Draft. "+
- "URL: <a href=\"http://www.w3.org/TR/prov-asn/\">http://www.w3.org/TR/prov-asn/</a>",
+ "URL: <a href=\"http://www.w3.org/TR/prov-n/\">http://www.w3.org/TR/prov-n/</a>",
"PROV-AQ":
"Graham Klyne and Paul Groth (eds.) Luc Moreau, Olaf Hartig, Yogesh Simmhan, James Meyers, Timothy Lebo, Khalid Belhajjame, and Simon Miles "+
@@ -206,7 +206,7 @@
producing a piece of data or thing in the world. PROV-DM is
domain-agnostic, but is equipped with extensibility points allowing
further domain-specific and application-specific extensions to be
-defined. PROV-DM is accompanied by PROV-ASN, a technology-independent
+defined. PROV-DM is accompanied by PROV-N, a technology-independent
abstract syntax notation, which allows serializations of PROV-DM
instances to be created for human consumption, which facilitates its
mapping to concrete syntax, and which is used as the basis for a
@@ -223,7 +223,7 @@
instances of that data model for human consumption. Other documents are:
<ul>
<li> PROV-DM-CONSTRAINTS, a set of constraints applying to the PROV-DM data model,</li>
-<li> PROV-ASN, a notation for provenance aimed at human consumption,</li>
+<li> PROV-N, a notation for provenance aimed at human consumption,</li>
<li> PROV-O, the provenance ontology: by means of a mapping of PROV-DM to the OWL2 Web Ontology Language, this specification provides a normative serialization of PROV-DM in RDF</li>
<li> PROV-AQ, provenance access and query: the mechanisms for accessing and querying provenance; </li>
<li> PROV-PRIMER: a primer for the PROV-DM provenance data model,</li>
@@ -282,7 +282,7 @@
<ul>
<li> PROV-DM (part I): the provenance data model itself, expressed in natural language (this document);
<li> PROV-DM-CONSTRAINTS (part II): constraints underpinning the data model [[PROV-DM-CONSTRAINTS]];
-<li> PROV-ASN (part III): a notation to express instances of that data model for human consumption [[PROV-ASN]];
+<li> PROV-N (part III): a notation to express instances of that data model for human consumption [[PROV-N]];
</ul>
</li>
@@ -310,7 +310,7 @@
<p><a href="#prov-dm-overview">Section 2</a> provides an overview of PROV-DM listing its core types and their relations.</p>
<p>In <a href="#prov-dm-example">section 3</a>, PROV-DM is
-applied to a short scenario, encoded in PROV-ASN, and illustrated
+applied to a short scenario, encoded in PROV-N, and illustrated
graphically.</p>
<p><a href="#data-model-concepts">Section 4</a> provides the definition of PROV-DM constructs.</p>
@@ -663,7 +663,7 @@
</ul>
<p>
-We now paraphrase some PROV-DM descriptions, and illustrate them with the PROV-ASN notation, a notation for PROV-DM aimed at human consumption. We then follow them with a graphical illustration. Full details of the provenance record can be found <a href="examples/w3c-publication1.prov-asn">here</a>.
+We now paraphrase some PROV-DM descriptions, and illustrate them with the PROV-N notation, a notation for PROV-DM aimed at human consumption. We then follow them with a graphical illustration. Full details of the provenance record can be found <a href="examples/w3c-publication1.prov-n">here</a>.
<ul>
<li>There is a technical report, a working draft on the recommendation track (<a href="http://www.w3.org/2005/10/Process-20051014/tr.html#RecsWD">pr:RecsWD</a>), which is regarded as an entity so that we can describe its provenance. Similar descriptions exist for all entities.
@@ -759,8 +759,8 @@
<li> Several persons are associated with activity <span class="name">ex:edit1</span>, some in an editorial role, some in a contributor's role.</li>
</ul>
-<p>Again, we paraphrase some PROV-DM assertions, and illustrate them with the PROV-ASN notation.
-Full details of the provenance record can be found <a href="examples/w3c-publication3.prov-asn">here</a>.</p>
+<p>Again, we paraphrase some PROV-DM assertions, and illustrate them with the PROV-N notation.
+Full details of the provenance record can be found <a href="examples/w3c-publication3.prov-n">here</a>.</p>
<ul>
<li>There is a technical report, which from the author's perspective is a document in its second version.
@@ -821,7 +821,7 @@
who the provenance is attributed to, and when it was
generated, etc. In other words, we need to be able to express the provenance of provenance.</p>
-<p>No new mechanism is required to support this requirement. PROV-DM makes the assumption that provenance statements have been bundled up, and named, by some mechanism outside the scope of PROV-DM. For instance, in this case, provenance statements were put in a file and exposed on the Web, respectively at <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/working-copy/examples/w3c-publication1.prov-asn">ex:prov1</a> and <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/working-copy/examples/w3c-publication3.prov-asn">ex:prov3</a>. To express their respective provenance, these resources must be seen as entities, and all the constructs of PROV-DM are now available to characterize their provenance. In the example below, <span class="name">ex:prov1</span> is attributed to the agent <span class="name">w3:Consortium</span>, whereas <span class="name">ex:prov3</span> to <span class="name">ex:Simon</span>.
+<p>No new mechanism is required to support this requirement. PROV-DM makes the assumption that provenance statements have been bundled up, and named, by some mechanism outside the scope of PROV-DM. For instance, in this case, provenance statements were put in a file and exposed on the Web, respectively at <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/working-copy/examples/w3c-publication1.pn">ex:prov1</a> and <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/working-copy/examples/w3c-publication3.pn">ex:prov3</a>. To express their respective provenance, these resources must be seen as entities, and all the constructs of PROV-DM are now available to characterize their provenance. In the example below, <span class="name">ex:prov1</span> is attributed to the agent <span class="name">w3:Consortium</span>, whereas <span class="name">ex:prov3</span> to <span class="name">ex:Simon</span>.
<pre>
entity(ex:prov1, [prov:type="prov:AccountEntity" %% xsd:QName ])
@@ -858,7 +858,7 @@
<div class="glossary-ref" ref="glossary-entity" withspan='true'></div>
-<p><div class="attributes" id="attributes-entity">An entity<span class="withAsn">, written <span class="pnExpression" id="pn-entity">entity(id, [ attr1=val1, ...])</span> in PROV-ASN, </span> contains:</p>
+<p><div class="attributes" id="attributes-entity">An entity<span class="withPn">, written <span class="pnExpression" id="pn-entity">entity(id, [ attr1=val1, ...])</span> in PROV-N, </span> contains:</p>
<ul>
<li><span class='attribute'>id</span>: an identifier for an entity; </li>
<li><span class='attribute'>attributes</span>: an OPTIONAL set of attribute-value pairs representing this entity's situation in the world.</li>
@@ -910,7 +910,7 @@
<div class="glossary-ref" ref="glossary-activity" withspan='true'></div>
-<p><div class="attributes" id="attributes-activity"> An activity<span class="withAsn">, written <span class="pnExpression" id="pn-activity">activity(id, st, et, [ attr1=val1, ...])</span> in PROV-ASN,</span> contains:</p>
+<p><div class="attributes" id="attributes-activity"> An activity<span class="withPn">, written <span class="pnExpression" id="pn-activity">activity(id, st, et, [ attr1=val1, ...])</span> in PROV-N,</span> contains:</p>
<ul>
<li><span class='attribute'>id</span>: an identifier for an activity;</li>
<li><span class='attribute'>startTime</span>: an OPTIONAL time for the start of the activity;</li>
@@ -948,7 +948,7 @@
<div class="glossary-ref" ref="glossary-agent" withspan='true'></div>
-<p><div class="attributes" id="attributes-agent">An agent<span class="withAsn">, noted <span class="pnExpression" id="pn-agent">agent(id, [ attr1=val1, ...])</span> in PROV-ASN,</span> contains:</p>
+<p><div class="attributes" id="attributes-agent">An agent<span class="withPn">, noted <span class="pnExpression" id="pn-agent">agent(id, [ attr1=val1, ...])</span> in PROV-N,</span> contains:</p>
<ul>
<li><span class='attribute'>id</span>: an identifier for an agent;</li>
<li><span class='attribute'>attributes</span>: a set of attribute-value pairs representing this agent's situation in the world.
@@ -991,7 +991,7 @@
trustworthiness of some of the entities or agents involved. Likewise, an interactive visualization component may want to enrich a set of provenance descriptions with information helping reproduce their
visual representation. To help with interoperability, PROV-DM introduces a simple annotation mechanism allowing anything that is identifiable to be associated with notes.</p>
-<p><div class="attributes" id="attributes-note">A <dfn title="dfn-note">note</dfn><span class="withAsn">, noted <span class="pnExpression">note(id, [ attr1=val1, ...])</span> in PROV-ASN,</span> contains:</p>
+<p><div class="attributes" id="attributes-note">A <dfn title="dfn-note">note</dfn><span class="withPn">, noted <span class="pnExpression">note(id, [ attr1=val1, ...])</span> in PROV-N,</span> contains:</p>
<ul>
<li><span class='attribute'>id</span>: an identifier for a note;</li>
<li><span class='attribute'>attributes</span>: a set of attribute-value pairs, whose meaning is application specific.</li>
@@ -1067,7 +1067,7 @@
<div class="glossary-ref" ref="glossary-generation" withspan='true'></div>
<p>
-<div class="attributes" id="attributes-generation"><dfn title="dfn-Generation">Generation</dfn><span class="withAsn">, written <span class="pnExpression">wasGeneratedBy(id,e,a,t,attrs)</span> in PROV-ASN,</span> has the following components:</p>
+<div class="attributes" id="attributes-generation"><dfn title="dfn-Generation">Generation</dfn><span class="withPn">, written <span class="pnExpression">wasGeneratedBy(id,e,a,t,attrs)</span> in PROV-N,</span> has the following components:</p>
<ul>
<li><span class='attribute'>id</span>: an OPTIONAL identifier for a generation;</li>
<li><span class='attribute'>entity</span>: an identifier for a created entity; </li>
@@ -1117,7 +1117,7 @@
<div class="glossary-ref" ref="glossary-usage" withspan='true'></div>
-<p><div class="attributes" id="attributes-usage"><dfn title="dfn-Usage">Usage</dfn><span class="withAsn">, written <span class="pnExpression">used(id,a,e,t,attrs)</span> in PROV-ASN,</span> has the following constituents:</p>
+<p><div class="attributes" id="attributes-usage"><dfn title="dfn-Usage">Usage</dfn><span class="withPn">, written <span class="pnExpression">used(id,a,e,t,attrs)</span> in PROV-N,</span> has the following constituents:</p>
<ul>
<li><span class='attribute'>id</span>: an OPTIONAL identifier for a usage;</li>
<li><span class='attribute'>activity</span>: an identifier for the consuming activity;</li>
@@ -1177,7 +1177,7 @@
href="#term-responsibility">Section Responsibility</a>, is a relation between agents expressing that an agent was acting on behalf of another, in the context of an activity. </p>
-<p><div class="attributes" id="attributes-activity-association">An <dfn title="dfn-activity-association">activity association</dfn><span class="withAsn">, written <span class="pnExpression">wasAssociatedWith(id,a,ag,pl,attrs)</span> in PROV-ASN,</span> has the following
+<p><div class="attributes" id="attributes-activity-association">An <dfn title="dfn-activity-association">activity association</dfn><span class="withPn">, written <span class="pnExpression">wasAssociatedWith(id,a,ag,pl,attrs)</span> in PROV-N,</span> has the following
constituents:</p>
<ul>
<li><span class='attribute'>id</span>: an OPTIONAL identifier for the association between an activity and an agent;</li>
@@ -1221,7 +1221,7 @@
-<p>An activity start<span class="withAsn">, written <span class="pnExpression">wasStartedBy(id,a,ag,attrs)</span> in PROV-ASN,</span> contains:</p>
+<p>An activity start<span class="withPn">, written <span class="pnExpression">wasStartedBy(id,a,ag,attrs)</span> in PROV-N,</span> contains:</p>
<ul>
<li><span class='attribute'>id</span>: an OPTIONAL identifier for the activity start;</li>
<li><span class='attribute'>activity</span>: an identifier for the started activity;
@@ -1229,7 +1229,7 @@
<li><span class='attribute'>attributes</span>: an OPTIONAL set of attribute-value pairs describing modalities according to which the agent started the activity.
</ul>
-<p>An activity end<span class="withAsn">, written <span class="pnExpression">wasEndedBy(id,a,ag,attrs)</span> in PROV-ASN,</span> contains:</p>
+<p>An activity end<span class="withPn">, written <span class="pnExpression">wasEndedBy(id,a,ag,attrs)</span> in PROV-N,</span> contains:</p>
<ul>
<li><span class='attribute'>id</span>: an OPTIONAL identifier for the activity end;</li>
<li><span class='attribute'>activity</span>: an identifier for the ended activity;
@@ -1295,7 +1295,7 @@
might be a need to define specific aspects of control that various
agents exert over a given activity.</p>
-<p><div class="attributes" id="attributes-responsibility-chain">A <dfn title="dfn-responsibility-chain">responsibility chain</dfn><span class="withAsn">, written <span class="pnExpression">actedOnBehalfOf(id,ag2,ag1,a,attrs)</span> in PROV-ASN,</span> has the following constituents:</p>
+<p><div class="attributes" id="attributes-responsibility-chain">A <dfn title="dfn-responsibility-chain">responsibility chain</dfn><span class="withPn">, written <span class="pnExpression">actedOnBehalfOf(id,ag2,ag1,a,attrs)</span> in PROV-N,</span> has the following constituents:</p>
<ul>
<li><span class='attribute'>id</span>: an OPTIONAL identifier for the responsibility chain;</li>
<li><span class='attribute'>subordinate</span>: an identifier for the agent associated with an activity, acting on behalf of the responsible
@@ -1343,7 +1343,7 @@
A derivation can be described at various levels of precision. In its simplest form, derivation relates two entities. Optionally, attributes can be added to describe modalities of derivation. If the derivation is the result of a single known activity, then this activity can also be optionally expressed. And to provide a completely accurate description of derivation, the generation and usage of the generated and used entities, respectively, can be provided. The reason for optional information such as activity, generation, and usage to be linked to derivations is to aid analysis of provenance and to facilitate provenance-based reproducibility. </p>
-<p><div class="attributes" id="attributes-derivation">A <dfn>derivation</dfn><span class="withAsn">, written <span class="pnExpression" id="pn-wasDerivedFrom">wasDerivedFrom(id, e2, e1, a, g2, u1, attrs)</span> in PROV-ASN,</span> contains:</p>
+<p><div class="attributes" id="attributes-derivation">A <dfn>derivation</dfn><span class="withPn">, written <span class="pnExpression" id="pn-wasDerivedFrom">wasDerivedFrom(id, e2, e1, a, g2, u1, attrs)</span> in PROV-N,</span> contains:</p>
<ul>
<li><em>id</em>: an OPTIONAL identifier for a derivation;</li>
<li><em>generatedEntity</em>: the identifier of the entity generated by the derivation;</li>
@@ -1420,7 +1420,7 @@
<p><div class="attributes" id="attributes-alternate">
-An <dfn title="dfn-Alternate">alternate relation</dfn><span class="withAsn">, written <span class="pnExpression">alternateOf(alt1, alt2)</span> in PROV-ASN,</span> addresses case (1). It has the following constituents:</p>
+An <dfn title="dfn-Alternate">alternate relation</dfn><span class="withPn">, written <span class="pnExpression">alternateOf(alt1, alt2)</span> in PROV-N,</span> addresses case (1). It has the following constituents:</p>
<ul>
<li><span class='attribute'>firstAlternate</span>: an identifier of the first of the two entities;</li>
@@ -1441,7 +1441,7 @@
<p>
<div class="attributes" id="attributes-specialization">
-A <dfn title="dfn-Specialization">specialization relation</dfn><span class="withAsn">, written <span class="pnExpression">specializationOf(sub, super)</span> in PROV-ASN,</span> addresses case (2). It has the following constituents:</p>
+A <dfn title="dfn-Specialization">specialization relation</dfn><span class="withPn">, written <span class="pnExpression">specializationOf(sub, super)</span> in PROV-N,</span> addresses case (2). It has the following constituents:</p>
<ul>
<li><span class='attribute'>specializedEntity</span>: an identifier of the specialized entity;</li>
@@ -1482,7 +1482,7 @@
annotated. The annotation mechanism (with note and annotation) forms a key aspect of the extensibility mechanism of PROV-DM (see <a
href="#extensibility-section">extensibility section</a>).</p>
-<p>An <dfn title="dfn-annotation">annotation relation</dfn><span class="withAsn">, written <span class="pnExpression">hasAnnotation(r,n)</span> in PROV-ASN,</span> has the following constituents:</p>
+<p>An <dfn title="dfn-annotation">annotation relation</dfn><span class="withPn">, written <span class="pnExpression">hasAnnotation(r,n)</span> in PROV-N,</span> has the following constituents:</p>
<ul>
<li><span class='attribute'>something</span>: the identifier of something being annotated;</li>
<li><span class='attribute'>note</span>: an identifier of a note.</li>
@@ -1744,7 +1744,7 @@
The agent who is responsible for the revision may optionally be specified.
Revision is a particular case of <a href="#Derivation-Relation">derivation</a> of an entity into its revised version.</p>
-<p> A revision relation<span class="withAsn">, written <span class="pnExpression">wasRevisionOf(id,e2,e1,ag,attrs)</span> in PROV-ASN,</span> contains:</p>
+<p> A revision relation<span class="withPn">, written <span class="pnExpression">wasRevisionOf(id,e2,e1,ag,attrs)</span> in PROV-N,</span> contains:</p>
<ul>
<li><span class='attribute'>id</span>: an OPTIONAL identifier for the relation;</li>
<li><span class='attribute'>newer</span>: the identifier of the revised entity;
@@ -1779,7 +1779,7 @@
<p><dfn id="dfn-attribution">Attribution</dfn> is the ascribing of an entity to an agent. More precisely, when an entity <span class="name">e</span> is attributed to agent <span class="name">ag</span>, entity <span class="name">e</span> was generated by some activity <span class="name">a</span>, which in turn was associated to agent <span class="name">ag</span>. Thus, this relation is useful when the activity is not known, or irrelevant.
-<p> An attribution relation<span class="withAsn">, written <span class="pnExpression"> wasAttributedTo(id,e,ag,attr)</span> in PROV-ASN,</span> contains the following elements:</p>
+<p> An attribution relation<span class="withPn">, written <span class="pnExpression"> wasAttributedTo(id,e,ag,attr)</span> in PROV-N,</span> contains the following elements:</p>
<ul>
<li><span class='attribute'>id</span>: an OPTIONAL identifier for the relation;</li>
<li><span class='attribute'>entity</span>: an entity identifier;</li>
@@ -1814,8 +1814,8 @@
</ul>
<p>
-An information flow ordering relation<span class="withAsn">, written as
-<span class="pnExpression">wasInformedBy(id,a2,a1,attrs)</span> in PROV-ASN,</span> contains:
+An information flow ordering relation<span class="withPn">, written as
+<span class="pnExpression">wasInformedBy(id,a2,a1,attrs)</span> in PROV-N,</span> contains:
<ul>
<li><span class='attribute'>id</span>: an OPTIONAL identifier identifying the relation;</li>
<li><span class='attribute'>informed</span>: the identifier of the informed activity;
@@ -1838,8 +1838,8 @@
<p>
-A control ordering relation<span class="withAsn">, written as
-<span class="pnExpression">wasStartedBy(id, a2, a1, attrs)</span> in PROV-ASN,</span> contains: </p>
+A control ordering relation<span class="withPn">, written as
+<span class="pnExpression">wasStartedBy(id, a2, a1, attrs)</span> in PROV-N,</span> contains: </p>
<ul>
<li><span class='attribute'>id</span>: an OPTIONAL identifier of the relation;</li>
<li><span class='attribute'>started</span>: the identifier of the started activity;
@@ -1870,7 +1870,7 @@
some responsibility for <span class="name">e2</span>'s existence.
-<p> A traceability relation<span class="withAsn">, written <span class="pnExpression">tracedTo(id,e2,e1,attrs)</span> in PROV-ASN,</span> contains:</p>
+<p> A traceability relation<span class="withPn">, written <span class="pnExpression">tracedTo(id,e2,e1,attrs)</span> in PROV-N,</span> contains:</p>
<ul>
<li><span class='attribute'>id</span>: an OPTIONAL identifier identifying the relation;</li>
<li><span class='attribute'>entity</span>: an identifier identifying an entity;
@@ -1910,7 +1910,7 @@
someone other that its original author. Quotation
is a particular case of <a href="#Derivation-Relation">derivation</a> in which entity <span class="name">e2</span> is derived from entity <span class="name">e1</span> by copying, or "quoting", parts of it.</p>
-<p> A quotation relation<span class="withAsn">, written <span class="pnExpression"> wasQuotedFrom(id,e2,e1,ag2,ag1,attrs)</span> in PROV-ASN,</span> contains:</p>
+<p> A quotation relation<span class="withPn">, written <span class="pnExpression"> wasQuotedFrom(id,e2,e1,ag2,ag1,attrs)</span> in PROV-N,</span> contains:</p>
<ul>
<li><span class='attribute'>id</span>: an OPTIONAL identifier for the relation;</li>
<li><span class='attribute'>quote</span>: an identifier of the entity that represents the quote (the partial copy);
@@ -1931,7 +1931,7 @@
<p> An <dfn>original source relation</dfn> is a particular case of <a href="#Derivation-Relation">derivation</a> that states that an entity <span class="name">e2</span> (derived) was originally part of some other entity <span class="name">e1</span> (the original source).</p>
-<p> An original source relation<span class="withAsn">, written <span class="pnExpression"> hadOriginalSource(id,e2,e1,attrs)</span>,</span> contains:</p>
+<p> An original source relation<span class="withPn">, written <span class="pnExpression"> hadOriginalSource(id,e2,e1,attrs)</span>,</span> contains:</p>
<ul>
<li><span class='attribute'>id</span>: an OPTIONAL identifier identifying the relation;</li>
<li><span class='attribute'>derived</span>: an identifier for the derived entity; </li>
@@ -1983,7 +1983,7 @@
</div>
-<p> A relation CollectionAfterInsertion<span class="withAsn">, written <span class="pnExpression"> CollectionAfterInsertion(collAfter, collBefore, key, value)</span>,</span> contains:</p>
+<p> A relation CollectionAfterInsertion<span class="withPn">, written <span class="pnExpression"> CollectionAfterInsertion(collAfter, collBefore, key, value)</span>,</span> contains:</p>
<ul>
<li><span class='attribute'>after</span>: an identifier for the collection <em>after</em> insertion; </li>
<li><span class='attribute'>before</span>: an identifier for the collection <em>before</em> insertion;</li>