--- a/model/PROV-DM.html Wed Oct 05 22:22:21 2011 +0100
+++ b/model/PROV-DM.html Wed Oct 05 22:59:51 2011 +0100
@@ -481,154 +481,7 @@
pre.sh_sourceCode .sh_paren { color: red; }
pre.sh_sourceCode .sh_attribute { color: #006400; }
-</style><style type="text/css">
-/* --- EDITORIAL NOTES --- */
-.pending {
- padding: 1em;
- margin: 1em 0em 0em;
- border: 1px solid #f00;
- background: #BFEFFF;
-}
-
-.pending::before {
- content: "Pending Review";
- display: block;
- width: 150px;
- margin: -1.5em 0 0.5em 0;
- font-weight: bold;
- border: 1px solid #f00;
- background: #fff;
- padding: 3px 1em;
-}
-
-
-.resolved {
- padding: 1em;
- margin: 1em 0em 0em;
- border: 1px solid #f00;
- background: #9BCD9B;
-}
-
-.resolved::before {
- content: "Resolved";
- display: block;
- width: 150px;
- margin: -1.5em 0 0.5em 0;
- font-weight: bold;
- border: 1px solid #f00;
- background: #fff;
- padding: 3px 1em;
-}
-
-
-.inference {
- padding: 1em;
- margin: 1em 0em 0em;
- border: 1px solid #f00;
- background: #fff;
-}
-
-.inference::before {
- content: "Inference";
- display: block;
- width: 150px;
- margin: -1.5em 0 0.5em 0;
- font-weight: bold;
- border: 1px solid #f00;
- background: #fff;
- padding: 3px 1em;
-}
-
-.unamedconstraint {
- padding: 1em;
- margin: 1em 0em 0em;
- border: 1px solid #00f;
- background: #fff;
-}
-
-
-.unamedconstraint::before {
- content: "Constraint";
- display: block;
- width: 150px;
- margin: -1.5em 0 0.5em 0;
- font-weight: bold;
- border: 1px solid #00f;
- background: #fff;
- padding: 3px 1em;
-}
-
-
-
-.constraint {
- padding: 1em;
- margin: 1em 0em 0em;
- border: 1px solid #00f;
- background: #fff;
-}
-
-.constraint[id]::before {
- content: "Constraint: " attr(id);
- width: 380px; /* How can we compute the length of "Constraint: " attr(id) */
-}
-
-
-.constraint::before {
- content: "Constraint";
- display: block;
- width: 150px;
- margin: -1.5em 0 0.5em 0;
- font-weight: bold;
- border: 1px solid #00f;
- background: #fff;
- padding: 3px 1em;
-}
-
-
-
-.conditional {
- color: blue;
-}
-
-.grammar {
- margin-top: 1ex;
- margin-bottom: 1ex;
- padding-left: 1ex;
- padding-right: 1ex;
- padding-top: 1ex;
- padding-bottom: 0.6ex;
- border: 1px dashed #2f6fab;
- font-family: monospace;
-}
-.nonterminal {
- font-weight: bold;
- font-family: sans-serif;
- font-size: 95%;
-}
-
-.name {
- font-family: monospace;
-}
-
-
-.xmpl {
- padding: 1em;
- margin: 1em 0em 0em;
- border: 1px solid #f00;
- background: #fff;
-}
-
-.xmpl::before {
- content: "Example";
- display: block;
- width: 150px;
- margin: -1.5em 0 0.5em 0;
- font-weight: bold;
- border: 1px solid #f00;
- background: #fff;
- padding: 3px 1em;
-}
-</style><link href="http://www.w3.org/StyleSheets/TR/W3C-WD" rel="stylesheet" type="text/css" charset="utf-8"></head>
+</style><link href="./extra.css" rel="stylesheet" type="text/css" charset="utf-8"><link href="http://www.w3.org/StyleSheets/TR/W3C-WD" rel="stylesheet" type="text/css" charset="utf-8"></head>
<body style="display: inherit; "><div class="head"><p><a href="http://www.w3.org/"><img width="72" height="48" src="http://www.w3.org/Icons/w3c_home" alt="W3C"></a></p><h1 class="title" id="title">The PROV data model and abstract syntax notation</h1><h2 id="subtitle">Initial draft for internal discussion</h2><h2 id="w3c-working-draft-05-october-2011">W3C Working Draft 05 October 2011</h2><dl><dt>This version:</dt><dd><a href="http://www.w3.org/TR/2011/WD-PROV-DM-20111005/">http://www.w3.org/TR/2011/WD-PROV-DM-20111005/</a></dd><dt>Latest published version:</dt><dd><a href="http://www.w3.org/TR/PROV-DM/">http://www.w3.org/TR/PROV-DM/</a></dd><dt>Latest editor's draft:</dt><dd><a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html">http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html</a></dd><dt>Editors:</dt><dd><a href="http://www.ecs.soton.ac.uk/~lavm">Luc Moreau</a>, University of Southampton, UK</dd>
<dd><a href="http://www.cs.ncl.ac.uk/people/Paolo.Missier">Paolo Missier</a>, Newcastle University, UK</dd>
<dt>Author:</dt><dd><span>TBD</span></dd>
@@ -2217,7 +2070,7 @@
<p>
The following account expression</p>
<pre class="example">account(acc0,
- http://x.com/asserter,
+ http://example.org/asserter,
entity(e0, [ type="File", location="/shared/crime.txt", creator="Alice" ])
...
wasDerivedFrom(e2,e1)
@@ -2227,7 +2080,7 @@
wasGeneratedBy(e0,pe0,outFile)
...
wasControlledBy(pe4,a5, qualifier(role="communicator")) )</pre>
-<p>contains the set of provenance expressions of section <a href="#example-prov-asn-encoding">example-prov-asn-encoding</a>, is asserted by agent <span class="name">http://x.com/asserter</span>, and is identified by identifier <span class="name">acc0</span>.
+<p>contains the set of provenance expressions of section <a href="#example-prov-asn-encoding">example-prov-asn-encoding</a>, is asserted by agent <span class="name">http://example.org/asserter</span>, and is identified by identifier <span class="name">acc0</span>.
</p>
<p>Account expressions constitue a scope for identifiers. An identifier within the scope of an account is intended to denote a single expression. However, nothing prevents an asserter from asserting an account containing, for example, multiple entity expressions with a same identifier but different attribute-values. In that case, they should be understood as a single entity expression with this identifier and the union of all attributes values, as formalized in <a href="#identified-entity-in-account">identified-entity-in-account</a>.</p>
@@ -2242,7 +2095,7 @@
<p>
In the following account expression, we find two entity expressions with a same identifier <span class="name">e</span>.</p>
<pre class="example">account(acc1,
- http://x.com/id,
+ http://example.org/id,
entity(e,[type="person",age=20])
entity(e,[type="person",age=30])
...)</pre>
@@ -2268,26 +2121,26 @@
<p>
Indeed, let us consider another account expression</p>
<pre class="example">account(acc2,
- http://x.com/asserter2,
+ http://example.org/asserter2,
entity(e0, [ type="File", location="/shared/crime.txt", creator="Alice" ])
...
processExecution(pe1,create-file,t1)
...
wasGeneratedBy(e0,pe1,outFile)
... )</pre>
-<p>with identifier <span class="name">acc2</span>, containing assertions by asserter by <span class="name">http://x.com/asserter2</span> stating that thing represented by entity expression identified by <span class="name">e0</span> was generated by an activity represented by process execution expression identified by <span class="name">pe1</span> instead of <span class="name">pe0</span> in the previous account <span class="name">acc0</span>. If accounts <span class="name">acc0</span> and <span class="name">acc2</span> are merged together, the resulting set of expressions violates <a href="#generation-unicity">generation-unicity</a>.</p>
+<p>with identifier <span class="name">acc2</span>, containing assertions by asserter by <span class="name">http://example.org/asserter2</span> stating that thing represented by entity expression identified by <span class="name">e0</span> was generated by an activity represented by process execution expression identified by <span class="name">pe1</span> instead of <span class="name">pe0</span> in the previous account <span class="name">acc0</span>. If accounts <span class="name">acc0</span> and <span class="name">acc2</span> are merged together, the resulting set of expressions violates <a href="#generation-unicity">generation-unicity</a>.</p>
<p>Account expressions constitue a scope for identifiers. Since accounts can be nested, their scope can also be nested; thus, the scope of identifiers should be understood in the context of such nested scopes. When an expression with an identifier occurs directly within an account, then its identifier denotes this expression in the scope of this account, except in sub-accounts where expressions with the same identifier occur. </p>
<p>
The following account expression is inspired from section <a href="#example-prov-asn-encoding">example-prov-asn-encoding</a>. This account, identified by <span class="name">acc3</span>, declares entity expression identified by <span class="name">e0</span>, which is being referred to in the nested account <span class="name">acc4</span>. The scope of identifier <span class="name">e0</span> is account <span class="name">acc3</span>, including subaccount <span class="name">acc4</span>.</p>
<pre class="example">account(acc3,
- http://x.com/asserter1,
+ http://example.org/asserter1,
entity(e0, [ type="File", location="/shared/crime.txt", creator="Alice" ])
processExecution(pe0,create-file,t)
wasGeneratedBy(e0,pe0,outFile)
account(acc4,
- http://x.com/asserter2,
+ http://example.org/asserter2,
entity(e1, [ type="File", location="/shared/crime.txt", creator="Alice", content="" ])
processExecution(pe0,copy-file,t)
wasGeneratedBy(e1,pe0,outFile)
@@ -2333,9 +2186,9 @@
<p>
The following container </p>
-<pre class="example">container([x http://x.com],[acc1,acc2]
- account(acc1,http://x.com/asserter1,...)
- account(acc2,http://x.com/asserter1,...))</pre>
+<pre class="example">container([x http://example.org],[acc1,acc2]
+ account(acc1,http://example.org/asserter1,...)
+ account(acc2,http://example.org/asserter1,...))</pre>
<p> illustrates how two accounts with identifiers <span class="name">acc1</span> and <span class="name">acc2</span> can be returned in a PROV-ASN serialization of the provenance of something.
</p>
@@ -2858,6 +2711,6 @@
</dd><dt id="bib-XMLSCHEMA-2">[XMLSCHEMA-2]</dt><dd>Paul V. Biron; Ashok Malhotra. <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/"><cite>XML Schema Part 2: Datatypes Second Edition.</cite></a> 28 October 2004. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/">http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/</a>
</dd></dl></div><div id="informative-references" class="section"><h3><span class="secno">B.2 </span>Informative references</h3><dl class="bibliography"><dt id="bib-PROV-OWL2">[PROV-OWL2]</dt><dd>Satya Sahoo and Deborah McGuinness <a href="http://dvcs.w3.org/hg/prov/raw-file/default/ontology/ProvenanceFormalModel.html"><cite>Provenance Formal Model</cite></a>. 2011, Work in progress. URL: <a href="http://dvcs.w3.org/hg/prov/raw-file/default/ontology/ProvenanceFormalModel.html">http://dvcs.w3.org/hg/prov/raw-file/default/ontology/ProvenanceFormalModel.html</a>
</dd><dt id="bib-PROV-PAQ">[PROV-PAQ]</dt><dd>Graham Klyne and Paul Groth <a href="http://dvcs.w3.org/hg/prov/raw-file/tip/paq/provenance-access.html"><cite>Provenance Access and Query</cite></a>. 2011, Work in progress. URL: <a href="http://dvcs.w3.org/hg/prov/raw-file/tip/paq/provenance-access.html">http://dvcs.w3.org/hg/prov/tip/paq/provenance-access.html</a>
-</dd><dt id="bib-PROV-PRIMER">[PROV-PRIMER]</dt><dd>Yolanda Gil and Simon Miles <a href="http://dvcs.w3.org/hg/prov/raw-file/default/primer/Primer.html"><cite>Prov Model Primer</cite></a>. 2011, Work in progress. URL: <a href="http://www.w3.org/2011/prov/wiki/ProvenancePrimer">http://www.w3.org/2011/prov/wiki/ProvenancePrimer</a>
+</dd><dt id="bib-PROV-PRIMER">[PROV-PRIMER]</dt><dd>Yolanda Gil and Simon Miles <a href="http://dvcs.w3.org/hg/prov/raw-file/default/primer/Primer.html"><cite>Prov Model Primer</cite></a>. 2011, Work in progress. URL: <a href="http://dvcs.w3.org/hg/prov/raw-file/default/primer/Primer.html">http://dvcs.w3.org/hg/prov/raw-file/default/primer/Primer.html</a>
</dd><dt id="bib-PROV-SEMANTICS">[PROV-SEMANTICS]</dt><dd>James Cheney <a href="http://www.w3.org/2011/prov/wiki/FormalSemanticsStrawman"><cite>Formal Semantics Strawman</cite></a>. 2011, Work in progress. URL: <a href="http://www.w3.org/2011/prov/wiki/FormalSemanticsStrawman">http://www.w3.org/2011/prov/wiki/FormalSemanticsStrawman</a>
</dd></dl></div></div></body></html>
--- a/model/ProvenanceModel.html Wed Oct 05 22:22:21 2011 +0100
+++ b/model/ProvenanceModel.html Wed Oct 05 22:59:51 2011 +0100
@@ -31,7 +31,7 @@
"Yolanda Gil and Simon Miles "+
"<a href=\"http://dvcs.w3.org/hg/prov/raw-file/default/primer/Primer.html\"><cite>Prov Model Primer</cite></a>. "+
"2011, Work in progress. "+
- "URL: <a href=\"http://www.w3.org/2011/prov/wiki/ProvenancePrimer\">http://www.w3.org/2011/prov/wiki/ProvenancePrimer</a>",
+ "URL: <a href=\"http://dvcs.w3.org/hg/prov/raw-file/default/primer/Primer.html\">http://dvcs.w3.org/hg/prov/raw-file/default/primer/Primer.html</a>",
"PROV-OWL2":
"Satya Sahoo and Deborah McGuinness "+
@@ -1735,7 +1735,7 @@
The following account expression</p>
<pre class="example">
account(acc0,
- http://x.com/asserter,
+ http://example.org/asserter,
entity(e0, [ type="File", location="/shared/crime.txt", creator="Alice" ])
...
wasDerivedFrom(e2,e1)
@@ -1746,7 +1746,7 @@
...
wasControlledBy(pe4,a5, qualifier(role="communicator")) )
</pre>
-<p>contains the set of provenance expressions of section <a href="#example-prov-asn-encoding">example-prov-asn-encoding</a>, is asserted by agent <span class="name">http://x.com/asserter</span>, and is identified by identifier <span class="name">acc0</span>.
+<p>contains the set of provenance expressions of section <a href="#example-prov-asn-encoding">example-prov-asn-encoding</a>, is asserted by agent <span class="name">http://example.org/asserter</span>, and is identified by identifier <span class="name">acc0</span>.
</p>
<p>Account expressions constitue a scope for identifiers. An identifier within the scope of an account is intended to denote a single expression. However, nothing prevents an asserter from asserting an account containing, for example, multiple entity expressions with a same identifier but different attribute-values. In that case, they should be understood as a single entity expression with this identifier and the union of all attributes values, as formalized in <a href="#identified-entity-in-account">identified-entity-in-account</a>.</p>
@@ -1762,7 +1762,7 @@
In the following account expression, we find two entity expressions with a same identifier <span class="name">e</span>.</p>
<pre class="example">
account(acc1,
- http://x.com/id,
+ http://example.org/id,
entity(e,[type="person",age=20])
entity(e,[type="person",age=30])
...)
@@ -1790,7 +1790,7 @@
Indeed, let us consider another account expression</p>
<pre class="example">
account(acc2,
- http://x.com/asserter2,
+ http://example.org/asserter2,
entity(e0, [ type="File", location="/shared/crime.txt", creator="Alice" ])
...
processExecution(pe1,create-file,t1)
@@ -1798,7 +1798,7 @@
wasGeneratedBy(e0,pe1,outFile)
... )
</pre>
-<p>with identifier <span class="name">acc2</span>, containing assertions by asserter by <span class="name">http://x.com/asserter2</span> stating that thing represented by entity expression identified by <span class="name">e0</span> was generated by an activity represented by process execution expression identified by <span class="name">pe1</span> instead of <span class="name">pe0</span> in the previous account <span class="name">acc0</span>. If accounts <span class="name">acc0</span> and <span class="name">acc2</span> are merged together, the resulting set of expressions violates <a href="#generation-unicity">generation-unicity</a>.</p>
+<p>with identifier <span class="name">acc2</span>, containing assertions by asserter by <span class="name">http://example.org/asserter2</span> stating that thing represented by entity expression identified by <span class="name">e0</span> was generated by an activity represented by process execution expression identified by <span class="name">pe1</span> instead of <span class="name">pe0</span> in the previous account <span class="name">acc0</span>. If accounts <span class="name">acc0</span> and <span class="name">acc2</span> are merged together, the resulting set of expressions violates <a href="#generation-unicity">generation-unicity</a>.</p>
<p>Account expressions constitue a scope for identifiers. Since accounts can be nested, their scope can also be nested; thus, the scope of identifiers should be understood in the context of such nested scopes. When an expression with an identifier occurs directly within an account, then its identifier denotes this expression in the scope of this account, except in sub-accounts where expressions with the same identifier occur. </p>
@@ -1806,12 +1806,12 @@
The following account expression is inspired from section <a href="#example-prov-asn-encoding">example-prov-asn-encoding</a>. This account, identified by <span class="name">acc3</span>, declares entity expression identified by <span class="name">e0</span>, which is being referred to in the nested account <span class="name">acc4</span>. The scope of identifier <span class="name">e0</span> is account <span class="name">acc3</span>, including subaccount <span class="name">acc4</span>.</p>
<pre class="example">
account(acc3,
- http://x.com/asserter1,
+ http://example.org/asserter1,
entity(e0, [ type="File", location="/shared/crime.txt", creator="Alice" ])
processExecution(pe0,create-file,t)
wasGeneratedBy(e0,pe0,outFile)
account(acc4,
- http://x.com/asserter2,
+ http://example.org/asserter2,
entity(e1, [ type="File", location="/shared/crime.txt", creator="Alice", content="" ])
processExecution(pe0,copy-file,t)
wasGeneratedBy(e1,pe0,outFile)
@@ -1859,9 +1859,9 @@
<p>
The following container </p>
<pre class="example">
-container([x http://x.com],[acc1,acc2]
- account(acc1,http://x.com/asserter1,...)
- account(acc2,http://x.com/asserter1,...))
+container([x http://example.org],[acc1,acc2]
+ account(acc1,http://example.org/asserter1,...)
+ account(acc2,http://example.org/asserter1,...))
</pre>
<p> illustrates how two accounts with identifiers <span class="name">acc1</span> and <span class="name">acc2</span> can be returned in a PROV-ASN serialization of the provenance of something.
</p>