--- a/dc-note/releases/NOTE-prov-dc-20130430/Overview.html Fri Apr 26 09:26:16 2013 +0100
+++ b/dc-note/releases/NOTE-prov-dc-20130430/Overview.html Fri Apr 26 09:27:12 2013 +0100
@@ -860,7 +860,7 @@
<td><code>dct:isFormatOf</code> refers to another resource which is the same but in another format. Thus, the term is mapped to <code>prov:alternateOf</code>.</td>
</tr>
<tr>
- <td><b id="term_isFormatOf"><a href="http://purl.org/dc/terms/isFormatOf">dct:isFormatOf</a></b></td>
+ <td><b><a href="http://purl.org/dc/terms/isFormatOf">dct:isFormatOf</a></b></td>
<td>rdfs:subPropertyOf</td>
<td><a href="http://www.w3.org/TR/prov-o/#wasDerivedFrom">prov:wasDerivedFrom</a></td>
<td><code>dct:isFormatOf</code> refers to another "pre-existing" resource which is the same but in another format (according to <a href="http://purl.org/dc/terms/hasFormat"><code>cdt:hasFormat</code></a>),
@@ -963,8 +963,7 @@
<td>A <code>dct:LinguisticSystem</code> is a system of symbols, sounds, gestures, etc. used in communication. Therefore, the linguistic system
defines the plan to follow in order to learn a certain language.
</td>
- </tr>
- </tr>
+ </tr>
<tr>
<td><b id="term_Location"><a href="http://purl.org/dc/terms/Location">dct:Location</a></b></td>
<td>owl:equivalentClass</td>
@@ -1075,7 +1074,7 @@
described resource is derived").</td>
</tr>
<tr>
- <td><a href="http://www.w3.org/TR/prov-o/#wasRevisionOf">prov:wasRevisionOf</a></td>
+ <td id="term_isVersionOf"><a href="http://www.w3.org/TR/prov-o/#wasRevisionOf">prov:wasRevisionOf</a></td>
<td>rdfs:subPropertyOf</td>
<td><b><a href="http://purl.org/dc/terms/isVersionOf">dct:isVersionOf</a></b></td>
<td>Similar to the previous property, <code>prov:wasRevisionOf</code> is more restrictive in the sense that it refers to a revised version of a resource, while
@@ -1358,7 +1357,7 @@
</section>
<section id="dct-created">
<h5><span class="secno">3.3.2.2 </span> dct:created</h5>
- <p>As stated in <a href="entity-date-mappings-when">Section 3.3.2</a>, <code>dct:created</code> is mapped to PROV thusly:</p>
+ <p>As stated in <a href="#entity-date-mappings-when">Section 3.3.2</a>, <code>dct:created</code> is mapped to PROV thusly:</p>
<pre class="code">
CONSTRUCT{
?document a prov:Entity.
@@ -1383,9 +1382,8 @@
<section id="dct-issued">
<h5><span class="secno">3.3.2.3 </span>dct:issued</h5>
- <p>
- <p>As stated in <a href="entity-date-mappings-when">Section 3.3.2</a>, <code>dct:issued</code> is mapped to PROV thusly:</p>
- </p><pre class="code">
+ <p>As stated in <a href="#entity-date-mappings-when">Section 3.3.2</a>, <code>dct:issued</code> is mapped to PROV thusly:</p>
+ <pre class="code">
CONSTRUCT{
?document a prov:Entity.
@@ -1415,9 +1413,8 @@
</section>
<section id="dct-modified">
<h5><span class="secno">3.3.2.4 </span>dct:modified</h5>
- <p>
- <p>As stated in <a href="entity-date-mappings-when">Section 3.3.2</a>, <code>dct:modified</code> is mapped to PROV thusly:</p>
- </p><pre class="code">
+ <p>As stated in <a href="#entity-date-mappings-when">Section 3.3.2</a>, <code>dct:modified</code> is mapped to PROV thusly:</p>
+ <pre class="code">
CONSTRUCT{
?document a prov:Entity.
@@ -1447,9 +1444,9 @@
</section>
<section id="dct-dateaccepted">
<h5><span class="secno">3.3.2.5 </span>dct:dateAccepted</h5>
- <p>
- <p>As stated in <a href="entity-date-mappings-when">Section 3.3.2</a>, <code>dct:dateAccepted</code> is mapped to PROV thusly:</p>
- </p><pre class="code">
+
+ <p>As stated in <a href="#entity-date-mappings-when">Section 3.3.2</a>, <code>dct:dateAccepted</code> is mapped to PROV thusly:</p>
+ <pre class="code">
CONSTRUCT{
?document a prov:Entity.
@@ -1501,9 +1498,9 @@
</section>
<section id="dct-datesubmitted">
<h5><span class="secno">3.3.2.7 </span>dct:dateSubmitted</h5>
- <p>
- <p>As stated in <a href="entity-date-mappings-when">Section 3.3.2</a>, <code>dct:dateSubmitted</code> is mapped to PROV thusly:</p>
- </p><pre class="code">
+
+ <p>As stated in <a href="#entity-date-mappings-when">Section 3.3.2</a>, <code>dct:dateSubmitted</code> is mapped to PROV thusly:</p>
+ <pre class="code">
CONSTRUCT{
?document a prov:Entity.
@@ -1945,7 +1942,7 @@
</dd><dt id="bib-OWL2-OVERVIEW">[OWL2-OVERVIEW]</dt><dd>W3C OWL Working Group. <a href="http://www.w3.org/TR/2012/REC-owl2-overview-20121211/"><cite>OWL 2 Web Ontology Language: Overview</cite></a>. 11 December 2012. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2012/REC-owl2-overview-20121211/">http://www.w3.org/TR/2012/REC-owl2-overview-20121211/</a>
</dd><dt id="bib-PROV-AQ">[PROV-AQ]</dt><dd>Graham Klyne; Paul Groth; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/"><cite>Provenance Access and Query</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/">http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/</a>
</dd><dt id="bib-PROV-CONSTRAINTS">[PROV-CONSTRAINTS]</dt><dd>James Cheney; Paolo Missier; Luc Moreau; eds. <a href="http://www.w3.org/TR/2013/REC-prov-constraints-20130430/"><cite>Constraints of the PROV Data Model</cite></a>. 30 April 2013, W3C Recommendation. URL: <a href="http://www.w3.org/TR/2013/REC-prov-constraints-20130430/">http://www.w3.org/TR/2013/REC-prov-constraints-20130430/</a>
-</dd><dt id="bib-PROV-DICTIONARY">[PROV-DICTIONARY]</dt><dd>Tom De Nies; Sam Coppens; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><cite>PROV Dictionary</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/</a>
+</dd><dt id="bib-PROV-DICTIONARY">[PROV-DICTIONARY]</dt><dd>Tom De Nies; Sam Coppens; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><cite>PROV Dictionary: Modeling Provenance for Dictionary Data Structures</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/</a>
</dd><dt id="bib-PROV-DM">[PROV-DM]</dt><dd>Luc Moreau; Paolo Missier; eds. <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/"><cite>PROV-DM: The PROV Data Model</cite></a>. 30 April 2013, W3C Recommendation. URL: <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/">http://www.w3.org/TR/2013/REC-prov-dm-20130430/</a>
</dd><dt id="bib-PROV-LINKS">[PROV-LINKS]</dt><dd>Luc Moreau; Timothy Lebo; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-links-20130430/"><cite>Linking Across Provenance Bundles</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-links-20130430/">http://www.w3.org/TR/2013/NOTE-prov-links-20130430/</a>
</dd><dt id="bib-PROV-N">[PROV-N]</dt><dd>Luc Moreau; Paolo Missier; eds. <a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/"><cite>PROV-N: The Provenance Notation</cite></a>. 30 April 2013, W3C Recommendation. URL: <a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/">http://www.w3.org/TR/2013/REC-prov-n-20130430/</a>
--- a/dictionary/Overview.html Fri Apr 26 09:26:16 2013 +0100
+++ b/dictionary/Overview.html Fri Apr 26 09:27:12 2013 +0100
@@ -1232,7 +1232,7 @@
<h2>PROV-O Representation of Dictionary</h2>
<p>In this section, the ontological definition of <code>prov:Dictionary</code> is given, in order to extend [[PROV-O]] with dictionaries. For more information on the terminology, syntax and conventions used in this section, we refer to [[PROV-O]].</p>
<p>The classes and properties defined in this document are included in the default namespace of PROV.
- Users of the ontology have the option of importing <code><http://www.w3.org/ns/prov#></code>, which includes all extensions, including PROV-Dictionary. Additionally, the [<a href="prov-dictionary.owl">OWL file for PROV-Dictionary</a>] is available for download.</p>
+ Users of the ontology have the option of importing <code><http://www.w3.org/ns/prov#></code>, which includes all extensions, including PROV-Dictionary. Additionally, the [<a href="http://www.w3.org/ns/prov-dictionary">OWL file for PROV-Dictionary</a>] is available for download.</p>
<p> A <code><a class="qname"
href='#Dictionary'>prov:Dictionary</a></code> is a <code
@@ -2409,7 +2409,7 @@
<section id="dictionary-xml-schema">
<h2>PROV-XML Representation of Dictionary</h2>
This section details how to describe dictionaries with
-the [[PROV-XML]] serialization. The [<a href="http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/schema/prov-dictionary.xsd">XML schema for PROV-Dictionary</a>] is available for download, and includes <a href="http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/schema/prov-core.xsd">prov-core.xsd</a>, the core schema of PROV. Alternatively, the default schema, <a href="http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/schema/prov.xsd">prov.xsd</a> can be used, which imports <a href="http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/schema/prov-core.xsd">prov-core.xsd</a> and all extension schemas developed by the Working Group.
+the [[PROV-XML]] serialization. The [<a href="http://www.w3.org/ns/prov-dictionary.xsd">XML schema for PROV-Dictionary</a>] is available for download, and includes <a href="http://www.w3.org/ns/prov-core.xsd">prov-core.xsd</a>, the core schema of PROV. Alternatively, the default schema, <a href="http://www.w3.org/ns/prov.xsd">prov.xsd</a> can be used, which imports <a href="http://www.w3.org/ns/prov-core.xsd">prov-core.xsd</a> and all extension schemas developed by the Working Group.
<section id="term-Dictionary">
<h3>Dictionary</h3>
<div class="glossary-ref" data-ref="glossary-dictionary"></div>
@@ -3323,7 +3323,7 @@
xmlns:dbpedia="http://dbpedia.org/resource/"
xmlns:ex="http://example.com/"
xsi:schemaLocation="http://www.w3.org/ns/prov#
-http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/schema/prov.xsd ">
+http://www.w3.org/ns/prov.xsd ">
<!-- All Player Entities -->
... <!-- See complete provenance file -->
--- a/dictionary/example/example.provx Fri Apr 26 09:26:16 2013 +0100
+++ b/dictionary/example/example.provx Fri Apr 26 09:27:12 2013 +0100
@@ -6,7 +6,7 @@
xmlns:dbpedia="http://dbpedia.org/resource/"
xmlns:ex="http://example.com/"
xsi:schemaLocation="http://www.w3.org/ns/prov#
-http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/schema/prov.xsd ">
+http://www.w3.org/ns/prov.xsd ">
<!-- All Player Entities -->
<prov:entity prov:id="dbpedia:Marco_Scutaro"/>
<prov:entity prov:id="dbpedia:Jed_Lowrie"/>
--- a/dictionary/releases/NOTE-prov-dictionary-20130430/Overview.html Fri Apr 26 09:26:16 2013 +0100
+++ b/dictionary/releases/NOTE-prov-dictionary-20130430/Overview.html Fri Apr 26 09:27:12 2013 +0100
@@ -1363,7 +1363,7 @@
<!--OddPage--><h2><span class="secno">5. </span>PROV-O Representation of Dictionary</h2>
<p>In this section, the ontological definition of <code>prov:Dictionary</code> is given, in order to extend [<cite><a href="#bib-PROV-O" class="bibref">PROV-O</a></cite>] with dictionaries. For more information on the terminology, syntax and conventions used in this section, we refer to [<cite><a href="#bib-PROV-O" class="bibref">PROV-O</a></cite>].</p>
<p>The classes and properties defined in this document are included in the default namespace of PROV.
- Users of the ontology have the option of importing <code><http://www.w3.org/ns/prov#></code>, which includes all extensions, including PROV-Dictionary. Additionally, the [<a href="prov-dictionary.owl">OWL file for PROV-Dictionary</a>] is available for download.</p>
+ Users of the ontology have the option of importing <code><http://www.w3.org/ns/prov#></code>, which includes all extensions, including PROV-Dictionary. Additionally, the [<a href="http://www.w3.org/ns/prov-dictionary">OWL file for PROV-Dictionary</a>] is available for download.</p>
<p> A <code><a class="qname" href="#Dictionary">prov:Dictionary</a></code> is a <code class="repeated">prov:Entity</code> that acts as a container to some members,
which are themselves entities.
@@ -2530,7 +2530,7 @@
<section id="dictionary-xml-schema">
<!--OddPage--><h2><span class="secno">6. </span>PROV-XML Representation of Dictionary</h2>
This section details how to describe dictionaries with
-the [<cite><a href="#bib-PROV-XML" class="bibref">PROV-XML</a></cite>] serialization. The [<a href="http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/schema/prov-dictionary.xsd">XML schema for PROV-Dictionary</a>] is available for download, and includes <a href="http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/schema/prov-core.xsd">prov-core.xsd</a>, the core schema of PROV. Alternatively, the default schema, <a href="http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/schema/prov.xsd">prov.xsd</a> can be used, which imports <a href="http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/schema/prov-core.xsd">prov-core.xsd</a> and all extension schemas developed by the Working Group.
+the [<cite><a href="#bib-PROV-XML" class="bibref">PROV-XML</a></cite>] serialization. The [<a href="http://www.w3.org/ns/prov-dictionary.xsd">XML schema for PROV-Dictionary</a>] is available for download, and includes <a href="http://www.w3.org/ns/prov-core.xsd">prov-core.xsd</a>, the core schema of PROV. Alternatively, the default schema, <a href="http://www.w3.org/ns/prov.xsd">prov.xsd</a> can be used, which imports <a href="http://www.w3.org/ns/prov-core.xsd">prov-core.xsd</a> and all extension schemas developed by the Working Group.
<section id="term-Dictionary">
<h3><span class="secno">6.1 </span>Dictionary</h3>
<div class="glossary-ref"></div>
@@ -3416,7 +3416,7 @@
xmlns:dbpedia="http://dbpedia.org/resource/"
xmlns:ex="http://example.com/"
xsi:schemaLocation="http://www.w3.org/ns/prov#
-http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/schema/prov.xsd ">
+http://www.w3.org/ns/prov.xsd ">
<!-- All Player Entities -->
... <!-- See complete provenance file -->
--- a/dictionary/releases/NOTE-prov-dictionary-20130430/example/example.provx Fri Apr 26 09:26:16 2013 +0100
+++ b/dictionary/releases/NOTE-prov-dictionary-20130430/example/example.provx Fri Apr 26 09:27:12 2013 +0100
@@ -6,7 +6,7 @@
xmlns:dbpedia="http://dbpedia.org/resource/"
xmlns:ex="http://example.com/"
xsi:schemaLocation="http://www.w3.org/ns/prov#
-http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/schema/prov.xsd ">
+http://www.w3.org/ns/prov.xsd ">
<!-- All Player Entities -->
<prov:entity prov:id="dbpedia:Marco_Scutaro"/>
<prov:entity prov:id="dbpedia:Jed_Lowrie"/>
--- a/dictionary/releases/NOTE-prov-dictionary-20130430/prov-dictionary.owl Fri Apr 26 09:26:16 2013 +0100
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,358 +0,0 @@
-<?xml version="1.0"?>
-
-
-<!DOCTYPE rdf:RDF [
- <!ENTITY owl "http://www.w3.org/2002/07/owl#" >
- <!ENTITY xsd "http://www.w3.org/2001/XMLSchema#" >
- <!ENTITY xml "http://www.w3.org/XML/1998/namespace" >
- <!ENTITY rdfs "http://www.w3.org/2000/01/rdf-schema#" >
- <!ENTITY rdf "http://www.w3.org/1999/02/22-rdf-syntax-ns#" >
-]>
-
-
-<rdf:RDF xmlns="http://www.w3.org/ns/prov#"
- xml:base="http://www.w3.org/ns/prov"
- xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
- xmlns:owl="http://www.w3.org/2002/07/owl#"
- xmlns:xsd="http://www.w3.org/2001/XMLSchema#"
- xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
- xmlns:xml="http://www.w3.org/XML/1998/namespace">
- <owl:Ontology rdf:about="http://www.w3.org/ns/prov-dictionary#">
- <rdfs:label xml:lang="en">W3C PROVenance Interchange Ontology (PROV-O) Dictionary Extension</rdfs:label>
- <rdfs:comment xml:lang="en">This document is published by the Provenance Working Group (http://www.w3.org/2011/prov/wiki/Main_Page).
-
-If you wish to make comments regarding this document, please send them to public-prov-comments@w3.org (subscribe public-prov-comments-request@w3.org, archives http://lists.w3.org/Archives/Public/public-prov-comments/). All feedback is welcome.</rdfs:comment>
- <rdfs:seeAlso rdf:resource="http://www.w3.org/TR/prov-dictionary/"/>
- <rdfs:seeAlso rdf:resource="http://www.w3.org/ns/prov"/>
- </owl:Ontology>
-
- <owl:Ontology rdf:about="http://www.w3.org/ns/prov#"></owl:Ontology>
-
- <!--
- ///////////////////////////////////////////////////////////////////////////////////////
- //
- // Object Properties
- //
- ///////////////////////////////////////////////////////////////////////////////////////
- -->
-
-
-
-
- <!-- http://www.w3.org/ns/prov#derivedByInsertionFrom -->
-
- <owl:ObjectProperty rdf:about="http://www.w3.org/ns/prov#derivedByInsertionFrom">
- <rdfs:label>derivedByInsertionFrom</rdfs:label>
- <constraints rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#dictionary-constraints</constraints>
- <n rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#expression-dictionary-insertion</n>
- <dm rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#term-dictionary-insertion</dm>
- <definition>The dictionary was derived from the other by insertion. Can be qualified with prov:qualifiedInsertion, which shows details of the insertion, in particular the inserted key-entity pairs.</definition>
- <component>collections</component>
- <category>collections</category>
- <rdfs:isDefinedBy rdf:resource="http://www.w3.org/ns/prov#"/>
- <rdfs:range rdf:resource="http://www.w3.org/ns/prov#Dictionary"/>
- <rdfs:domain rdf:resource="http://www.w3.org/ns/prov#Dictionary"/>
- <rdfs:subPropertyOf rdf:resource="http://www.w3.org/ns/prov#wasDerivedFrom"/>
- </owl:ObjectProperty>
-
-
-
- <!-- http://www.w3.org/ns/prov#derivedByRemovalFrom -->
-
- <owl:ObjectProperty rdf:about="http://www.w3.org/ns/prov#derivedByRemovalFrom">
- <rdfs:label>derivedByRemovalFrom</rdfs:label>
- <constraints rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#dictionary-constraints</constraints>
- <n rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#expression-dictionary-removal</n>
- <dm rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#term-dictionary-removal</dm>
- <component>collections</component>
- <definition>The dictionary was derived from the other by removal. Can be qualified with prov:qualifiedRemoval, which shows details of the removal, in particular the removed keys.</definition>
- <category>collections</category>
- <rdfs:isDefinedBy rdf:resource="http://www.w3.org/ns/prov#"/>
- <rdfs:range rdf:resource="http://www.w3.org/ns/prov#Dictionary"/>
- <rdfs:domain rdf:resource="http://www.w3.org/ns/prov#Dictionary"/>
- <rdfs:subPropertyOf rdf:resource="http://www.w3.org/ns/prov#wasDerivedFrom"/>
- </owl:ObjectProperty>
-
-
-
- <!-- http://www.w3.org/ns/prov#dictionary -->
-
- <owl:ObjectProperty rdf:about="http://www.w3.org/ns/prov#dictionary">
- <rdfs:label>dictionary</rdfs:label>
- <constraints rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#dictionary-constraints</constraints>
- <n rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#expression-dictionary-insertion</n>
- <n rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#expression-dictionary-removal</n>
- <dm rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#term-dictionary-insertion</dm>
- <dm rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#term-dictionary-removal</dm>
- <category>collections</category>
- <component>collections</component>
- <definition>The property used by a prov:Insertion and prov:Removal to cite the prov:Dictionary that was prov:derivedByInsertionFrom or prov:derivedByRemovalFrom another dictionary.</definition>
- <rdfs:isDefinedBy rdf:resource="http://www.w3.org/ns/prov#"/>
- <rdfs:range rdf:resource="http://www.w3.org/ns/prov#Dictionary"/>
- <rdfs:domain rdf:resource="http://www.w3.org/ns/prov#Insertion"/>
- <rdfs:domain rdf:resource="http://www.w3.org/ns/prov#Removal"/>
- <rdfs:subPropertyOf rdf:resource="http://www.w3.org/ns/prov#entity"/>
- </owl:ObjectProperty>
-
-
- <!-- http://www.w3.org/ns/prov#hadDictionaryMember -->
-
- <owl:ObjectProperty rdf:about="http://www.w3.org/ns/prov#hadDictionaryMember">
- <rdfs:label>hadDictionaryMember</rdfs:label>
- <constraints rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#dictionary-constraints</constraints>
- <n rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#expression-dictionary-membership</n>
- <dm rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#term-dictionary-membership</dm>
- <definition>Describes the key-entity pair that was member of a prov:Dictionary. A dictionary can have multiple members.</definition>
- <component>collections</component>
- <category>collections</category>
- <rdfs:isDefinedBy rdf:resource="http://www.w3.org/ns/prov#"/>
- <rdfs:domain rdf:resource="http://www.w3.org/ns/prov#Dictionary"/>
- <rdfs:range rdf:resource="http://www.w3.org/ns/prov#KeyEntityPair"/>
- </owl:ObjectProperty>
-
-
-
- <!-- http://www.w3.org/ns/prov#insertedKeyEntityPair -->
-
- <owl:ObjectProperty rdf:about="http://www.w3.org/ns/prov#insertedKeyEntityPair">
- <rdfs:label>insertedKeyEntityPair</rdfs:label>
- <constraints rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#dictionary-constraints</constraints>
- <n rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#expression-dictionary-insertion</n>
- <dm rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#term-dictionary-insertion</dm>
- <component>collections</component>
- <category>collections</category>
- <definition>An object property to refer to the prov:KeyEntityPair inserted into a prov:Dictionary.</definition>
- <rdfs:isDefinedBy rdf:resource="http://www.w3.org/ns/prov#"/>
- <rdfs:domain rdf:resource="http://www.w3.org/ns/prov#Insertion"/>
- <rdfs:range rdf:resource="http://www.w3.org/ns/prov#KeyEntityPair"/>
- </owl:ObjectProperty>
-
-
-
- <!-- http://www.w3.org/ns/prov#pairEntity -->
-
- <owl:ObjectProperty rdf:about="http://www.w3.org/ns/prov#pairEntity">
- <rdf:type rdf:resource="&owl;FunctionalProperty"/>
- <rdfs:label>pairKey</rdfs:label>
- <constraints rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#dictionary-constraints</constraints>
- <n rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#expression-dictionary-membership</n>
- <dm rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#term-dictionary-membership</dm>
- <category>collections</category>
- <component>collections</component>
- <definition>The entity of a prov:KeyEntityPair, which is an element of a prov:Dictionary.</definition>
- <rdfs:isDefinedBy rdf:resource="http://www.w3.org/ns/prov#"/>
- <rdfs:range rdf:resource="http://www.w3.org/ns/prov#Entity"/>
- <rdfs:domain rdf:resource="http://www.w3.org/ns/prov#KeyEntityPair"/>
- </owl:ObjectProperty>
-
-
-
- <!-- http://www.w3.org/ns/prov#qualifiedInsertion -->
-
- <owl:ObjectProperty rdf:about="http://www.w3.org/ns/prov#qualifiedInsertion">
- <rdfs:label>qualifiedInsertion</rdfs:label>
- <constraints rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#dictionary-constraints</constraints>
- <n rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#expression-dictionary-insertion</n>
- <dm rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#term-dictionary-insertion</dm>
- <definition>prov:qualifiedInsertion shows the details of an insertion, in particular the inserted key-entity pairs.</definition>
- <category>collections</category>
- <component>collections</component>
- <rdfs:isDefinedBy rdf:resource="http://www.w3.org/ns/prov#"/>
- <rdfs:domain rdf:resource="http://www.w3.org/ns/prov#Dictionary"/>
- <rdfs:range rdf:resource="http://www.w3.org/ns/prov#Insertion"/>
- <rdfs:subPropertyOf rdf:resource="http://www.w3.org/ns/prov#qualifiedDerivation"/>
- </owl:ObjectProperty>
-
-
-
- <!-- http://www.w3.org/ns/prov#qualifiedRemoval -->
-
- <owl:ObjectProperty rdf:about="http://www.w3.org/ns/prov#qualifiedRemoval">
- <rdfs:label>qualifiedRemoval</rdfs:label>
- <constraints rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#dictionary-constraints</constraints>
- <n rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#expression-dictionary-removal</n>
- <dm rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#term-dictionary-removal</dm>
- <category>collections</category>
- <component>collections</component>
- <definition>prov:qualifiedRemoval shows the details of a removal, in particular the removed keys.</definition>
- <rdfs:isDefinedBy rdf:resource="http://www.w3.org/ns/prov#"/>
- <rdfs:domain rdf:resource="http://www.w3.org/ns/prov#Dictionary"/>
- <rdfs:range rdf:resource="http://www.w3.org/ns/prov#Removal"/>
- <rdfs:subPropertyOf rdf:resource="http://www.w3.org/ns/prov#qualifiedDerivation"/>
- </owl:ObjectProperty>
-
-
- <!--
- ///////////////////////////////////////////////////////////////////////////////////////
- //
- // Data properties
- //
- ///////////////////////////////////////////////////////////////////////////////////////
- -->
-
-
-
-
- <!-- http://www.w3.org/ns/prov#pairKey -->
-
- <owl:DatatypeProperty rdf:about="http://www.w3.org/ns/prov#pairKey">
- <rdf:type rdf:resource="&owl;FunctionalProperty"/>
- <rdfs:label>pairKey</rdfs:label>
- <constraints rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#dictionary-constraints</constraints>
- <n rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#expression-dictionary-membership</n>
- <dm rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#term-dictionary-membership</dm>
- <component>collections</component>
- <definition>The key of a prov:KeyEntityPair, which is an element of a prov:Dictionary.</definition>
- <category>collections</category>
- <rdfs:range rdf:resource="&rdfs;Literal"/>
- <rdfs:isDefinedBy rdf:resource="http://www.w3.org/ns/prov#"/>
- <rdfs:domain rdf:resource="http://www.w3.org/ns/prov#KeyEntityPair"/>
- </owl:DatatypeProperty>
-
-
-
- <!-- http://www.w3.org/ns/prov#removedKey -->
-
- <owl:DatatypeProperty rdf:about="http://www.w3.org/ns/prov#removedKey">
- <rdfs:label>removedKey</rdfs:label>
- <constraints rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#dictionary-constraints</constraints>
- <n rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#expression-dictionary-removal</n>
- <dm rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#term-dictionary-removal</dm>
- <category>collections</category>
- <definition>The key removed in a Removal.</definition>
- <component>collections</component>
- <rdfs:range rdf:resource="&rdfs;Literal"/>
- <rdfs:isDefinedBy rdf:resource="http://www.w3.org/ns/prov#"/>
- <rdfs:domain rdf:resource="http://www.w3.org/ns/prov#Removal"/>
- </owl:DatatypeProperty>
-
-
-
- <!--
- ///////////////////////////////////////////////////////////////////////////////////////
- //
- // Classes
- //
- ///////////////////////////////////////////////////////////////////////////////////////
- -->
-
-
- <!-- http://www.w3.org/ns/prov#Dictionary -->
-
- <owl:Class rdf:about="http://www.w3.org/ns/prov#Dictionary">
- <rdfs:label>Dictionary</rdfs:label>
- <dm rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#dictionary-conceptual-definition</dm>
- <constraints rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#dictionary-constraints</constraints>
- <n rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#expression-dictionary</n>
- <definition>A dictionary is an entity that provides a structure to some constituents, which are themselves entities. These constituents are said to be member of the dictionary.</definition>
- <rdfs:comment>A given dictionary forms a given structure for its members. A different structure (obtained either by insertion or removal of members) constitutes a different dictionary.</rdfs:comment>
- <component>collections</component>
- <category>collections</category>
- <rdfs:comment>This concept allows for the provenance of the dictionary, but also of its constituents to be expressed. Such a notion of dictionary corresponds to a wide variety of concrete data structures, such as a maps or associative arrays.</rdfs:comment>
- <rdfs:isDefinedBy rdf:resource="http://www.w3.org/ns/prov#"/>
- </owl:Class>
-
-
-
- <!-- http://www.w3.org/ns/prov#EmptyDictionary -->
-
- <owl:Class rdf:about="http://www.w3.org/ns/prov#EmptyDictionary">
- <rdfs:label>Empty Dictionary</rdfs:label>
- <rdfs:subClassOf rdf:resource="http://www.w3.org/ns/prov#Dictionary"/>
- <rdfs:subClassOf rdf:resource="http://www.w3.org/ns/prov#EmptyCollection"/>
- <dm rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#dictionary-conceptual-definition</dm>
- <constraints rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#dictionary-constraints</constraints>
- <n rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#expression-dictionary</n>
- <component>collections</component>
- <definition>An empty dictionary (i.e. has no members).</definition>
- <category>collections</category>
- <rdfs:isDefinedBy rdf:resource="http://www.w3.org/ns/prov#"/>
- </owl:Class>
-
-
-
- <!-- http://www.w3.org/ns/prov#Insertion -->
-
- <owl:Class rdf:about="http://www.w3.org/ns/prov#Insertion">
- <rdfs:label>Insertion</rdfs:label>
- <rdfs:subClassOf rdf:resource="http://www.w3.org/ns/prov#Derivation"/>
- <rdfs:subClassOf>
- <owl:Restriction>
- <owl:onProperty rdf:resource="http://www.w3.org/ns/prov#dictionary"/>
- <owl:cardinality rdf:datatype="&xsd;nonNegativeInteger">1</owl:cardinality>
- </owl:Restriction>
- </rdfs:subClassOf>
- <rdfs:subClassOf>
- <owl:Restriction>
- <owl:onProperty rdf:resource="http://www.w3.org/ns/prov#insertedKeyEntityPair"/>
- <owl:minCardinality rdf:datatype="&xsd;nonNegativeInteger">1</owl:minCardinality>
- </owl:Restriction>
- </rdfs:subClassOf>
- <constraints rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#dictionary-constraints</constraints>
- <n rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#expression-dictionary-insertion</n>
- <dm rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#term-dictionary-insertion</dm>
- <definition>Insertion is a derivation that describes the transformation of a dictionary into another, by insertion of one or more key-entity pairs.</definition>
- <category>collections</category>
- <component>collections</component>
- <rdfs:isDefinedBy rdf:resource="http://www.w3.org/ns/prov#"/>
- <unqualifiedForm rdf:resource="http://www.w3.org/ns/prov#derivedByInsertionFrom"/>
- </owl:Class>
-
-
-
- <!-- http://www.w3.org/ns/prov#KeyEntityPair -->
-
- <owl:Class rdf:about="http://www.w3.org/ns/prov#KeyEntityPair">
- <rdfs:label>Key-Entity Pair</rdfs:label>
- <rdfs:subClassOf>
- <owl:Restriction>
- <owl:onProperty rdf:resource="http://www.w3.org/ns/prov#pairEntity"/>
- <owl:cardinality rdf:datatype="&xsd;nonNegativeInteger">1</owl:cardinality>
- </owl:Restriction>
- </rdfs:subClassOf>
- <rdfs:subClassOf>
- <owl:Restriction>
- <owl:onProperty rdf:resource="http://www.w3.org/ns/prov#pairKey"/>
- <owl:cardinality rdf:datatype="&xsd;nonNegativeInteger">1</owl:cardinality>
- </owl:Restriction>
- </rdfs:subClassOf>
- <constraints rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#dictionary-constraints</constraints>
- <n rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#expression-dictionary-membership</n>
- <dm rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#term-dictionary-membership</dm>
- <definition>A key-entity pair. Part of a prov:Dictionary through prov:hadDictionaryMember. The key is any RDF Literal, the value is a prov:Entity.</definition>
- <component>collections</component>
- <category>collections</category>
- <rdfs:isDefinedBy rdf:resource="http://www.w3.org/ns/prov#"/>
- </owl:Class>
-
-
-
- <!-- http://www.w3.org/ns/prov#Removal -->
-
- <owl:Class rdf:about="http://www.w3.org/ns/prov#Removal">
- <rdfs:label>Removal</rdfs:label>
- <rdfs:subClassOf rdf:resource="http://www.w3.org/ns/prov#Derivation"/>
- <rdfs:subClassOf>
- <owl:Restriction>
- <owl:onProperty rdf:resource="http://www.w3.org/ns/prov#dictionary"/>
- <owl:cardinality rdf:datatype="&xsd;nonNegativeInteger">1</owl:cardinality>
- </owl:Restriction>
- </rdfs:subClassOf>
- <rdfs:subClassOf>
- <owl:Restriction>
- <owl:onProperty rdf:resource="http://www.w3.org/ns/prov#removedKey"/>
- <owl:minCardinality rdf:datatype="&xsd;nonNegativeInteger">1</owl:minCardinality>
- </owl:Restriction>
- </rdfs:subClassOf>
- <constraints rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#dictionary-constraints</constraints>
- <n rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#expression-dictionary-removal</n>
- <dm rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#term-dictionary-removal</dm>
- <category>collections</category>
- <definition>Removal is a derivation that describes the transformation of a dictionary into another, by removing one or more keys.</definition>
- <component>collections</component>
- <rdfs:isDefinedBy rdf:resource="http://www.w3.org/ns/prov#"/>
- <unqualifiedForm rdf:resource="http://www.w3.org/ns/prov#derivedByRemovalFrom"/>
- </owl:Class>
-</rdf:RDF>
-
-
--- a/dictionary/releases/NOTE-prov-dictionary-20130430/prov-dictionary.ttl Fri Apr 26 09:26:16 2013 +0100
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,246 +0,0 @@
-@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
-@prefix : <http://www.w3.org/ns/prov#> .
-@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
-@prefix owl: <http://www.w3.org/2002/07/owl#> .
-@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
-
-<http://www.w3.org/ns/prov-dictionary#>
- a owl:Ontology ;
- rdfs:comment """This document is published by the Provenance Working Group (http://www.w3.org/2011/prov/wiki/Main_Page).
-
-If you wish to make comments regarding this document, please send them to public-prov-comments@w3.org (subscribe public-prov-comments-request@w3.org, archives http://lists.w3.org/Archives/Public/public-prov-comments/). All feedback is welcome."""@en ;
- rdfs:label "W3C PROVenance Interchange Ontology (PROV-O) Dictionary Extension"@en ;
- rdfs:seeAlso <http://www.w3.org/TR/prov-dictionary/>, <http://www.w3.org/ns/prov> .
-
-<http://www.w3.org/ns/prov#>
- a owl:Ontology .
-
-:Dictionary
- a owl:Class ;
- rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
- rdfs:label "Dictionary" ;
- :definition "A dictionary is an entity that provides a structure to some constituents, which are themselves entities. These constituents are said to be member of the dictionary." ;
- rdfs:comment "This concept allows for the provenance of the dictionary, but also of its constituents to be expressed. Such a notion of dictionary corresponds to a wide variety of concrete data structures, such as a maps or associative arrays." ;
- rdfs:comment "A given dictionary forms a given structure for its members. A different structure (obtained either by insertion or removal of members) constitutes a different dictionary." ;
- :category "collections" ;
- :component "collections" ;
- :dm "http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#dictionary-conceptual-definition"^^xsd:anyURI ;
- :n "http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#expression-dictionary"^^xsd:anyURI ;
- :constraints "http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#dictionary-constraints"^^xsd:anyURI .
-
-:EmptyDictionary
- a owl:Class ;
- rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
- rdfs:label "Empty Dictionary" ;
- :definition "An empty dictionary (i.e. has no members)." ;
- rdfs:subClassOf :EmptyCollection ;
- rdfs:subClassOf :Dictionary ;
- :category "collections" ;
- :component "collections" ;
- :dm "http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#dictionary-conceptual-definition"^^xsd:anyURI ;
- :n "http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#expression-dictionary"^^xsd:anyURI ;
- :constraints "http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#dictionary-constraints"^^xsd:anyURI .
-
-:KeyEntityPair
- a owl:Class ;
- rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
- rdfs:label "Key-Entity Pair" ;
- :definition "A key-entity pair. Part of a prov:Dictionary through prov:hadDictionaryMember. The key is any RDF Literal, the value is a prov:Entity." ;
- rdfs:subClassOf
- [ a owl:Restriction ;
- owl:onProperty :pairKey ;
- owl:cardinality "1"^^xsd:int
- ] ;
- rdfs:subClassOf
- [ a owl:Restriction ;
- owl:onProperty :pairEntity ;
- owl:cardinality "1"^^xsd:int
- ] ;
- :category "collections" ;
- :component "collections" ;
- :dm "http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#term-dictionary-membership"^^xsd:anyURI ;
- :n "http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#expression-dictionary-membership"^^xsd:anyURI ;
- :constraints "http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#dictionary-constraints"^^xsd:anyURI .
-
-:Insertion
- a owl:Class ;
- rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
- rdfs:label "Insertion" ;
- :definition "Insertion is a derivation that transforms a dictionary into another, by insertion of one or more key-entity pairs." ;
- rdfs:subClassOf :Derivation ;
- rdfs:subClassOf
- [ a owl:Restriction ;
- owl:onProperty :dictionary ;
- owl:cardinality "1"^^xsd:int
- ] ;
- rdfs:subClassOf
- [ a owl:Restriction ;
- owl:onProperty :insertedKeyEntityPair ;
- owl:minCardinality "1"^^xsd:int
- ] ;
- :category "collections" ;
- :component "collections" ;
- :dm "http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#term-dictionary-insertion"^^xsd:anyURI ;
- :n "http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#expression-dictionary-insertion"^^xsd:anyURI ;
- :constraints "http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#dictionary-constraints"^^xsd:anyURI ;
- :unqualifiedForm :derivedByInsertionFrom .
-
-:Removal
- a owl:Class ;
- rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
- rdfs:label "Removal" ;
- :definition "Removal is a derivation that transforms a dictionary into another, by removing one or more key-entity pairs." ;
- rdfs:subClassOf :Derivation ;
- rdfs:subClassOf
- [ a owl:Restriction ;
- owl:onProperty :dictionary ;
- owl:cardinality "1"^^xsd:int
- ] ;
- rdfs:subClassOf
- [ a owl:Restriction ;
- owl:onProperty :removedKey ;
- owl:minCardinality "1"^^xsd:int
- ] ;
- :category "collections" ;
- :component "collections" ;
- :dm "http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#term-dictionary-removal"^^xsd:anyURI ;
- :n "http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#expression-dictionary-removal"^^xsd:anyURI ;
- :constraints "http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#dictionary-constraints"^^xsd:anyURI ;
- :unqualifiedForm :derivedByRemovalFrom .
-
-:dictionary
- a owl:ObjectProperty ;
- rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
- rdfs:label "dictionary" ;
- :definition "The property used by a prov:Insertion and prov:Removal to cite the prov:Dictionary that was prov:derivedByInsertionFrom or prov:derivedByRemovalFrom another dictionary." ;
- rdfs:subPropertyOf :entity ;
- rdfs:domain :Insertion, :Removal ;
- rdfs:range :Dictionary ;
- :category "collections" ;
- :component "collections" ;
- :dm "http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#term-dictionary-insertion"^^xsd:anyURI ;
- :dm "http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#term-dictionary-removal"^^xsd:anyURI ;
- :n "http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#expression-dictionary-insertion"^^xsd:anyURI ;
- :n "http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#expression-dictionary-removal"^^xsd:anyURI ;
- :constraints "http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#dictionary-constraints"^^xsd:anyURI .
-
-:derivedByInsertionFrom
- a owl:ObjectProperty ;
- rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
- rdfs:label "derivedByInsertionFrom" ;
- :definition "The dictionary was derived from the other by insertion. prov:qualifiedInsertion shows details of the insertion, in particular the inserted key-entity pairs." ;
- rdfs:subPropertyOf :wasDerivedFrom ;
- rdfs:domain :Dictionary ;
- rdfs:range :Dictionary ;
- :category "collections" ;
- :component "collections" ;
- :dm "http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#term-dictionary-insertion"^^xsd:anyURI ;
- :n "http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#expression-dictionary-insertion"^^xsd:anyURI ;
- :constraints "http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#dictionary-constraints"^^xsd:anyURI .
-
-:derivedByRemovalFrom
- a owl:ObjectProperty ;
- rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
- rdfs:label "derivedByRemovalFrom" ;
- :definition "The dictionary was derived from the other by removal. prov:qualifiedRemoval shows details of the removal, in particular the removed key-entity pairs." ;
- rdfs:subPropertyOf :wasDerivedFrom ;
- rdfs:domain :Dictionary ;
- rdfs:range :Dictionary ;
- :category "collections" ;
- :component "collections" ;
- :dm "http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#term-dictionary-removal"^^xsd:anyURI ;
- :n "http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#expression-dictionary-removal"^^xsd:anyURI ;
- :constraints "http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#dictionary-constraints"^^xsd:anyURI .
-
-:insertedKeyEntityPair
- a owl:ObjectProperty ;
- rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
- rdfs:label "insertedKeyEntityPair" ;
- :definition "An object property to refer to the prov:KeyEntityPair inserted into a prov:Dictionary." ;
- rdfs:domain :Insertion ;
- rdfs:range :KeyEntityPair ;
- :category "collections" ;
- :component "collections" ;
- :dm "http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#term-dictionary-insertion"^^xsd:anyURI ;
- :n "http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#expression-dictionary-insertion"^^xsd:anyURI ;
- :constraints "http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#dictionary-constraints"^^xsd:anyURI .
-
-:hadDictionaryMember
- a owl:ObjectProperty ;
- rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
- rdfs:label "hadDictionaryMember" ;
- :definition "Describes the key-entity pair that was member of a prov:Dictionary. A dictionary can have multiple members." ;
- rdfs:domain :Dictionary ;
- rdfs:range :KeyEntityPair ;
- :category "collections" ;
- :component "collections" ;
- :dm "http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#term-dictionary-membership"^^xsd:anyURI ;
- :n "http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#expression-dictionary-membership"^^xsd:anyURI ;
- :constraints "http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#dictionary-constraints"^^xsd:anyURI .
-
-:pairKey
- a owl:DatatypeProperty, owl:FunctionalProperty ;
- rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
- rdfs:label "pairKey" ;
- :definition "The key of a KeyEntityPair, which is an element of a prov:Dictionary." ;
- rdfs:domain :KeyEntityPair ;
- rdfs:range rdfs:Literal ;
- :category "collections" ;
- :component "collections" ;
- :dm "http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#term-dictionary-membership"^^xsd:anyURI ;
- :n "http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#expression-dictionary-membership"^^xsd:anyURI ;
- :constraints "http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#dictionary-constraints"^^xsd:anyURI .
-
-:pairEntity
- a owl:ObjectProperty, owl:FunctionalProperty ;
- rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
- rdfs:label "pairKey" ;
- :definition "The value of a KeyEntityPair." ;
- rdfs:domain :KeyEntityPair ;
- rdfs:range :Entity ;
- :category "collections" ;
- :component "collections" ;
- :dm "http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#term-dictionary-membership"^^xsd:anyURI ;
- :n "http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#expression-dictionary-membership"^^xsd:anyURI ;
- :constraints "http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#dictionary-constraints"^^xsd:anyURI .
-
-:qualifiedInsertion
- a owl:ObjectProperty ;
- rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
- rdfs:label "qualifiedInsertion" ;
- :definition "The dictionary was derived from the other by insertion. prov:qualifiedInsertion shows details of the insertion, in particular the inserted key-entity pairs." ;
- rdfs:subPropertyOf :qualifiedDerivation ;
- rdfs:domain :Dictionary ;
- rdfs:range :Insertion ;
- :category "collections" ;
- :component "collections" ;
- :dm "http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#term-dictionary-insertion"^^xsd:anyURI ;
- :n "http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#expression-dictionary-insertion"^^xsd:anyURI ;
- :constraints "http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#dictionary-constraints"^^xsd:anyURI .
-
-:qualifiedRemoval
- a owl:ObjectProperty ;
- rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
- rdfs:label "qualifiedRemoval" ;
- :definition "The dictionary was derived from the other by removal. prov:qualifiedRemoval shows details of the removal, in particular the removed keys." ;
- rdfs:subPropertyOf :qualifiedDerivation ;
- rdfs:domain :Dictionary ;
- rdfs:range :Removal ;
- :category "collections" ;
- :component "collections" ;
- :dm "http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#term-dictionary-removal"^^xsd:anyURI ;
- :n "http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#expression-dictionary-removal"^^xsd:anyURI ;
- :constraints "http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#dictionary-constraints"^^xsd:anyURI .
-
-:removedKey
- a owl:DatatypeProperty ;
- rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
- rdfs:label "removedKey" ;
- :definition "The key removed in a Removal." ;
- rdfs:domain :Removal ;
- rdfs:range rdfs:Literal ;
- :category "collections" ;
- :component "collections" ;
- :dm "http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#term-dictionary-removal"^^xsd:anyURI ;
- :n "http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#expression-dictionary-removal"^^xsd:anyURI ;
- :constraints "http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/#dictionary-constraints"^^xsd:anyURI .
\ No newline at end of file
--- a/links/diff.html Fri Apr 26 09:26:16 2013 +0100
+++ b/links/diff.html Fri Apr 26 09:27:12 2013 +0100
@@ -679,30 +679,59 @@
}
-/* --- --- */
-ol.algorithm { counter-reset:numsection; list-style-type: none; }
-ol.algorithm li { margin: 0.5em 0; }
-ol.algorithm li:before { font-weight: bold; counter-increment: numsection; content: counters(numsection, ".") ") "; }
-/* --- TOC --- */
-.toc a, .tof a {
- text-decoration: none;
-}
-a .secno, a .figno {
+/* --- <span class="insert">TOC </span>--- */
+<span class="delete">ol.algorithm</span><span class="insert">.toc a, .tof a</span> {<span class="delete"> counter-reset:numsection; list-style-type: </span><span class="insert">
+ text-decoration: </span>none;
+}<span class="delete">
+ol.algorithm li</span><span class="insert">
+
+a .secno, a .figno</span> {<span class="delete"> margin: 0.5em 0; </span><span class="insert">
color: #000;
-}
+</span>}<span class="delete">
+ol.algorithm li:before</span><span class="insert">
-ul.tof, ol.tof {
+ul.tof, ol.tof</span> {<span class="delete"> font-weight: bold; counter-increment: numsection; content: counters(numsection, ".") ") "; </span><span class="insert">
list-style: none outside none;
}
.caption {
margin-top: 0.5em;
font-style: italic;
+</span>}
+
+/* --- <span class="delete">TOC</span><span class="insert">TABLE</span> --- */
+<span class="delete">.toc a, .tof a</span><span class="insert">table.simple</span> {
+ <span class="delete">text-decoration:</span><span class="insert">border-spacing: 0;
+ border-collapse:</span> <span class="delete">none;</span><span class="insert">collapse;
+ border-bottom: 3px solid #005a9c;</span>
}
-/* --- TABLE --- */
+<span class="delete">a .secno, a .figno</span><span class="insert">.simple th</span> {<span class="insert">
+ background: #005a9c;</span>
+ color: <span class="delete">#000;</span><span class="insert">#fff;
+ padding: 3px 5px;
+ text-align: left;</span>
+}
+
+<span class="delete">ul.tof, ol.tof</span><span class="insert">.simple th[scope="row"]</span> {
+ <span class="delete">list-style: none outside none;</span><span class="insert">background: inherit;
+ color: inherit;
+ border-top: 1px solid #ddd;</span>
+}
+
+<span class="delete">.caption</span><span class="insert">.simple td</span> {
+ <span class="delete">margin-top: 0.5em;
+ font-style: italic;</span><span class="insert">padding: 3px 10px;
+ border-top: 1px solid #ddd;
+}
+
+.simple tr:nth-child(even) {
+ background: #f0f6ff;</span>
+}
+
+/* --- <span class="delete">TABLE --- */
table.simple {
border-spacing: 0;
border-collapse: collapse;
@@ -731,7 +760,7 @@
background: #f0f6ff;
}
-/* --- DL --- */
+/* --- </span>DL --- */
.section dd > p:first-child {
margin-top: 0;
}
@@ -1542,7 +1571,7 @@
<section id="references" class="appendix"><h2><span class="secno">C. </span>References</h2><section id="informative-references"><h3><span class="secno">C.1 </span>Informative references</h3><dl class="bibliography"><dt id="bib-PROV-AQ">[PROV-AQ]</dt><dd>Graham Klyne; Paul Groth; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/"><cite>Provenance Access and Query</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-aq-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/</span></a>
</dd><dt id="bib-PROV-CONSTRAINTS">[PROV-CONSTRAINTS]</dt><dd>James Cheney; Paolo Missier; Luc Moreau; eds. <a href="http://www.w3.org/TR/2013/REC-prov-constraints-20130430/"><cite>Constraints of the PROV Data Model</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, W3C <span class="delete">Proposed </span>Recommendation. URL: <span class="delete">http://www.w3.org/TR/2013/PR-prov-constraints-20130312/</span><a href="http://www.w3.org/TR/2013/REC-prov-constraints-20130430/"><span class="insert">http://www.w3.org/TR/2013/REC-prov-constraints-20130430/</span></a>
</dd><dt id="bib-PROV-DC">[PROV-DC]</dt><dd>Daniel Garijo; Kai Eckert; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/"><cite>Dublin Core to PROV Mapping</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-dc-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/</span></a>
-</dd><dt id="bib-PROV-DICTIONARY">[PROV-DICTIONARY]</dt><dd>Tom De Nies; Sam Coppens; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><cite>PROV Dictionary</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/</span></a>
+</dd><dt id="bib-PROV-DICTIONARY">[PROV-DICTIONARY]</dt><dd>Tom De Nies; Sam Coppens; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><cite>PROV <span class="insert">Dictionary: Modeling Provenance for </span>Dictionary<span class="insert"> Data Structures</span></cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/</span></a>
</dd><dt id="bib-PROV-DM">[PROV-DM]</dt><dd>Luc Moreau; Paolo Missier; eds. <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/"><cite>PROV-DM: The PROV Data Model</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, W3C <span class="delete">Proposed </span>Recommendation. URL: <span class="delete">http://www.w3.org/TR/2013/PR-prov-dm-20130312/</span><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/"><span class="insert">http://www.w3.org/TR/2013/REC-prov-dm-20130430/</span></a>
</dd><dt id="bib-PROV-N">[PROV-N]</dt><dd>Luc Moreau; Paolo Missier; eds. <a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/"><cite>PROV-N: The Provenance Notation</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, W3C <span class="delete">Proposed </span>Recommendation. URL: <span class="delete">http://www.w3.org/TR/2013/PR-prov-n-20130312/</span><a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/"><span class="insert">http://www.w3.org/TR/2013/REC-prov-n-20130430/</span></a>
</dd><dt id="bib-PROV-O">[PROV-O]</dt><dd>Timothy Lebo; Satya Sahoo; Deborah McGuinness; eds. <a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/"><cite>PROV-O: The PROV Ontology</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, W3C <span class="delete">Proposed </span>Recommendation. URL: <span class="delete">http://www.w3.org/TR/2013/PR-prov-o-20130312/</span><a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/"><span class="insert">http://www.w3.org/TR/2013/REC-prov-o-20130430/</span></a>
--- a/links/releases/NOTE-prov-links-20130430/Overview.html Fri Apr 26 09:26:16 2013 +0100
+++ b/links/releases/NOTE-prov-links-20130430/Overview.html Fri Apr 26 09:27:12 2013 +0100
@@ -671,12 +671,6 @@
color: #ff4500;
}
-
-/* --- --- */
-ol.algorithm { counter-reset:numsection; list-style-type: none; }
-ol.algorithm li { margin: 0.5em 0; }
-ol.algorithm li:before { font-weight: bold; counter-increment: numsection; content: counters(numsection, ".") ") "; }
-
/* --- TOC --- */
.toc a, .tof a {
text-decoration: none;
@@ -1498,7 +1492,7 @@
<section id="references" class="appendix"><!--OddPage--><h2><span class="secno">C. </span>References</h2><section id="informative-references"><h3><span class="secno">C.1 </span>Informative references</h3><dl class="bibliography"><dt id="bib-PROV-AQ">[PROV-AQ]</dt><dd>Graham Klyne; Paul Groth; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/"><cite>Provenance Access and Query</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/">http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/</a>
</dd><dt id="bib-PROV-CONSTRAINTS">[PROV-CONSTRAINTS]</dt><dd>James Cheney; Paolo Missier; Luc Moreau; eds. <a href="http://www.w3.org/TR/2013/REC-prov-constraints-20130430/"><cite>Constraints of the PROV Data Model</cite></a>. 30 April 2013, W3C Recommendation. URL: <a href="http://www.w3.org/TR/2013/REC-prov-constraints-20130430/">http://www.w3.org/TR/2013/REC-prov-constraints-20130430/</a>
</dd><dt id="bib-PROV-DC">[PROV-DC]</dt><dd>Daniel Garijo; Kai Eckert; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/"><cite>Dublin Core to PROV Mapping</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/">http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/</a>
-</dd><dt id="bib-PROV-DICTIONARY">[PROV-DICTIONARY]</dt><dd>Tom De Nies; Sam Coppens; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><cite>PROV Dictionary</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/</a>
+</dd><dt id="bib-PROV-DICTIONARY">[PROV-DICTIONARY]</dt><dd>Tom De Nies; Sam Coppens; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><cite>PROV Dictionary: Modeling Provenance for Dictionary Data Structures</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/</a>
</dd><dt id="bib-PROV-DM">[PROV-DM]</dt><dd>Luc Moreau; Paolo Missier; eds. <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/"><cite>PROV-DM: The PROV Data Model</cite></a>. 30 April 2013, W3C Recommendation. URL: <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/">http://www.w3.org/TR/2013/REC-prov-dm-20130430/</a>
</dd><dt id="bib-PROV-N">[PROV-N]</dt><dd>Luc Moreau; Paolo Missier; eds. <a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/"><cite>PROV-N: The Provenance Notation</cite></a>. 30 April 2013, W3C Recommendation. URL: <a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/">http://www.w3.org/TR/2013/REC-prov-n-20130430/</a>
</dd><dt id="bib-PROV-O">[PROV-O]</dt><dd>Timothy Lebo; Satya Sahoo; Deborah McGuinness; eds. <a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/"><cite>PROV-O: The PROV Ontology</cite></a>. 30 April 2013, W3C Recommendation. URL: <a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/">http://www.w3.org/TR/2013/REC-prov-o-20130430/</a>
--- a/links/releases/NOTE-prov-links-20130430/diff.html Fri Apr 26 09:26:16 2013 +0100
+++ b/links/releases/NOTE-prov-links-20130430/diff.html Fri Apr 26 09:27:12 2013 +0100
@@ -679,30 +679,59 @@
}
-/* --- --- */
-ol.algorithm { counter-reset:numsection; list-style-type: none; }
-ol.algorithm li { margin: 0.5em 0; }
-ol.algorithm li:before { font-weight: bold; counter-increment: numsection; content: counters(numsection, ".") ") "; }
-/* --- TOC --- */
-.toc a, .tof a {
- text-decoration: none;
-}
-a .secno, a .figno {
+/* --- <span class="insert">TOC </span>--- */
+<span class="delete">ol.algorithm</span><span class="insert">.toc a, .tof a</span> {<span class="delete"> counter-reset:numsection; list-style-type: </span><span class="insert">
+ text-decoration: </span>none;
+}<span class="delete">
+ol.algorithm li</span><span class="insert">
+
+a .secno, a .figno</span> {<span class="delete"> margin: 0.5em 0; </span><span class="insert">
color: #000;
-}
+</span>}<span class="delete">
+ol.algorithm li:before</span><span class="insert">
-ul.tof, ol.tof {
+ul.tof, ol.tof</span> {<span class="delete"> font-weight: bold; counter-increment: numsection; content: counters(numsection, ".") ") "; </span><span class="insert">
list-style: none outside none;
}
.caption {
margin-top: 0.5em;
font-style: italic;
+</span>}
+
+/* --- <span class="delete">TOC</span><span class="insert">TABLE</span> --- */
+<span class="delete">.toc a, .tof a</span><span class="insert">table.simple</span> {
+ <span class="delete">text-decoration:</span><span class="insert">border-spacing: 0;
+ border-collapse:</span> <span class="delete">none;</span><span class="insert">collapse;
+ border-bottom: 3px solid #005a9c;</span>
}
-/* --- TABLE --- */
+<span class="delete">a .secno, a .figno</span><span class="insert">.simple th</span> {<span class="insert">
+ background: #005a9c;</span>
+ color: <span class="delete">#000;</span><span class="insert">#fff;
+ padding: 3px 5px;
+ text-align: left;</span>
+}
+
+<span class="delete">ul.tof, ol.tof</span><span class="insert">.simple th[scope="row"]</span> {
+ <span class="delete">list-style: none outside none;</span><span class="insert">background: inherit;
+ color: inherit;
+ border-top: 1px solid #ddd;</span>
+}
+
+<span class="delete">.caption</span><span class="insert">.simple td</span> {
+ <span class="delete">margin-top: 0.5em;
+ font-style: italic;</span><span class="insert">padding: 3px 10px;
+ border-top: 1px solid #ddd;
+}
+
+.simple tr:nth-child(even) {
+ background: #f0f6ff;</span>
+}
+
+/* --- <span class="delete">TABLE --- */
table.simple {
border-spacing: 0;
border-collapse: collapse;
@@ -731,7 +760,7 @@
background: #f0f6ff;
}
-/* --- DL --- */
+/* --- </span>DL --- */
.section dd > p:first-child {
margin-top: 0;
}
@@ -1542,7 +1571,7 @@
<section id="references" class="appendix"><h2><span class="secno">C. </span>References</h2><section id="informative-references"><h3><span class="secno">C.1 </span>Informative references</h3><dl class="bibliography"><dt id="bib-PROV-AQ">[PROV-AQ]</dt><dd>Graham Klyne; Paul Groth; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/"><cite>Provenance Access and Query</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-aq-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/</span></a>
</dd><dt id="bib-PROV-CONSTRAINTS">[PROV-CONSTRAINTS]</dt><dd>James Cheney; Paolo Missier; Luc Moreau; eds. <a href="http://www.w3.org/TR/2013/REC-prov-constraints-20130430/"><cite>Constraints of the PROV Data Model</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, W3C <span class="delete">Proposed </span>Recommendation. URL: <span class="delete">http://www.w3.org/TR/2013/PR-prov-constraints-20130312/</span><a href="http://www.w3.org/TR/2013/REC-prov-constraints-20130430/"><span class="insert">http://www.w3.org/TR/2013/REC-prov-constraints-20130430/</span></a>
</dd><dt id="bib-PROV-DC">[PROV-DC]</dt><dd>Daniel Garijo; Kai Eckert; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/"><cite>Dublin Core to PROV Mapping</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-dc-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/</span></a>
-</dd><dt id="bib-PROV-DICTIONARY">[PROV-DICTIONARY]</dt><dd>Tom De Nies; Sam Coppens; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><cite>PROV Dictionary</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/</span></a>
+</dd><dt id="bib-PROV-DICTIONARY">[PROV-DICTIONARY]</dt><dd>Tom De Nies; Sam Coppens; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><cite>PROV <span class="insert">Dictionary: Modeling Provenance for </span>Dictionary<span class="insert"> Data Structures</span></cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/</span></a>
</dd><dt id="bib-PROV-DM">[PROV-DM]</dt><dd>Luc Moreau; Paolo Missier; eds. <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/"><cite>PROV-DM: The PROV Data Model</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, W3C <span class="delete">Proposed </span>Recommendation. URL: <span class="delete">http://www.w3.org/TR/2013/PR-prov-dm-20130312/</span><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/"><span class="insert">http://www.w3.org/TR/2013/REC-prov-dm-20130430/</span></a>
</dd><dt id="bib-PROV-N">[PROV-N]</dt><dd>Luc Moreau; Paolo Missier; eds. <a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/"><cite>PROV-N: The Provenance Notation</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, W3C <span class="delete">Proposed </span>Recommendation. URL: <span class="delete">http://www.w3.org/TR/2013/PR-prov-n-20130312/</span><a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/"><span class="insert">http://www.w3.org/TR/2013/REC-prov-n-20130430/</span></a>
</dd><dt id="bib-PROV-O">[PROV-O]</dt><dd>Timothy Lebo; Satya Sahoo; Deborah McGuinness; eds. <a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/"><cite>PROV-O: The PROV Ontology</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, W3C <span class="delete">Proposed </span>Recommendation. URL: <span class="delete">http://www.w3.org/TR/2013/PR-prov-o-20130312/</span><a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/"><span class="insert">http://www.w3.org/TR/2013/REC-prov-o-20130430/</span></a>
--- a/model/diff-c.html Fri Apr 26 09:26:16 2013 +0100
+++ b/model/diff-c.html Fri Apr 26 09:27:12 2013 +0100
@@ -5179,7 +5179,7 @@
</dd><dt id="bib-Logic">[Logic]</dt><dd>W. E. Johnson. <a href="http://www.ditext.com/johnson/intro-3.html"><cite>Logic: Part III</cite></a>.1924. URL: <a href="http://www.ditext.com/johnson/intro-3.html">http://www.ditext.com/johnson/intro-3.html</a>
</dd><dt id="bib-PROV-AQ">[PROV-AQ]</dt><dd>Graham Klyne; Paul Groth; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/"><cite>Provenance Access and Query</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-aq-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/</span></a>
</dd><dt id="bib-PROV-DC">[PROV-DC]</dt><dd>Daniel Garijo; Kai Eckert; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/"><cite>Dublin Core to PROV Mapping</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-dc-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/</span></a>
-</dd><dt id="bib-PROV-DICTIONARY">[PROV-DICTIONARY]</dt><dd>Tom De Nies; Sam Coppens; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><cite>PROV Dictionary</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/</span></a>
+</dd><dt id="bib-PROV-DICTIONARY">[PROV-DICTIONARY]</dt><dd>Tom De Nies; Sam Coppens; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><cite>PROV <span class="insert">Dictionary: Modeling Provenance for </span>Dictionary<span class="insert"> Data Structures</span></cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/</span></a>
</dd><dt id="bib-PROV-LINKS">[PROV-LINKS]</dt><dd>Luc Moreau; Timothy Lebo; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-links-20130430/"><cite>Linking Across Provenance Bundles</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-links-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-links-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-links-20130430/</span></a>
</dd><dt id="bib-PROV-OVERVIEW">[PROV-OVERVIEW]</dt><dd>Paul Groth; Luc Moreau; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/"><cite>PROV-OVERVIEW: An Overview of the PROV Family of Documents</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-overview-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/</span></a>
</dd><dt id="bib-PROV-PRIMER">[PROV-PRIMER]</dt><dd>Yolanda Gil; Simon Miles; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/"><cite>PROV Model Primer</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-primer-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/</span></a>
--- a/model/diff-n.html Fri Apr 26 09:26:16 2013 +0100
+++ b/model/diff-n.html Fri Apr 26 09:27:12 2013 +0100
@@ -3180,7 +3180,7 @@
</dd><dt id="bib-XMLSCHEMA11-2">[XMLSCHEMA11-2]</dt><dd>Henry S. Thompson et al. <a href="http://www.w3.org/TR/2012/REC-xmlschema11-2-20120405/"><cite>W3C XML Schema Definition Language (XSD) 1.1 Part 2: Datatypes</cite></a>. 5 April 2012. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2012/REC-xmlschema11-2-20120405/">http://www.w3.org/TR/2012/REC-xmlschema11-2-20120405/</a>
</dd></dl></section><section id="informative-references"><h3><span class="secno">C.2 </span>Informative references</h3><dl class="bibliography"><dt id="bib-PROV-AQ">[PROV-AQ]</dt><dd>Graham Klyne; Paul Groth; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/"><cite>Provenance Access and Query</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-aq-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/</span></a>
</dd><dt id="bib-PROV-DC">[PROV-DC]</dt><dd>Daniel Garijo; Kai Eckert; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/"><cite>Dublin Core to PROV Mapping</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-dc-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/</span></a>
-</dd><dt id="bib-PROV-DICTIONARY">[PROV-DICTIONARY]</dt><dd>Tom De Nies; Sam Coppens; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><cite>PROV Dictionary</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/</span></a>
+</dd><dt id="bib-PROV-DICTIONARY">[PROV-DICTIONARY]</dt><dd>Tom De Nies; Sam Coppens; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><cite>PROV <span class="insert">Dictionary: Modeling Provenance for </span>Dictionary<span class="insert"> Data Structures</span></cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/</span></a>
</dd><dt id="bib-PROV-LINKS">[PROV-LINKS]</dt><dd>Luc Moreau; Timothy Lebo; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-links-20130430/"><cite>Linking Across Provenance Bundles</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-links-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-links-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-links-20130430/</span></a>
</dd><dt id="bib-PROV-OVERVIEW">[PROV-OVERVIEW]</dt><dd>Paul Groth; Luc Moreau; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/"><cite>PROV-OVERVIEW: An Overview of the PROV Family of Documents</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-overview-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/</span></a>
</dd><dt id="bib-PROV-PRIMER">[PROV-PRIMER]</dt><dd>Yolanda Gil; Simon Miles; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/"><cite>PROV Model Primer</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-primer-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/</span></a>
--- a/model/diff.html Fri Apr 26 09:26:16 2013 +0100
+++ b/model/diff.html Fri Apr 26 09:27:12 2013 +0100
@@ -4160,7 +4160,7 @@
</dd><dt id="bib-Mappings">[Mappings]</dt><dd>Satya Sahoo; Paul Groth; Olaf Hartig; Simon Miles; Sam Coppens; James Myers; Yolanda Gil; Luc Moreau; Jun Zhao; Michael Panzer; Daniel Garijo <a href="http://www.w3.org/2005/Incubator/prov/wiki/Provenance_Vocabulary_Mappings"><cite>Provenance Vocabulary Mappings</cite></a>. August 2010 URL: <a href="http://www.w3.org/2005/Incubator/prov/wiki/Provenance_Vocabulary_Mappings">http://www.w3.org/2005/Incubator/prov/wiki/Provenance_Vocabulary_Mappings</a>
</dd><dt id="bib-PROV-AQ">[PROV-AQ]</dt><dd>Graham Klyne; Paul Groth; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/"><cite>Provenance Access and Query</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-aq-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/</span></a>
</dd><dt id="bib-PROV-DC">[PROV-DC]</dt><dd>Daniel Garijo; Kai Eckert; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/"><cite>Dublin Core to PROV Mapping</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-dc-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/</span></a>
-</dd><dt id="bib-PROV-DICTIONARY">[PROV-DICTIONARY]</dt><dd>Tom De Nies; Sam Coppens; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><cite>PROV Dictionary</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/</span></a>
+</dd><dt id="bib-PROV-DICTIONARY">[PROV-DICTIONARY]</dt><dd>Tom De Nies; Sam Coppens; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><cite>PROV <span class="insert">Dictionary: Modeling Provenance for </span>Dictionary<span class="insert"> Data Structures</span></cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/</span></a>
</dd><dt id="bib-PROV-LAYOUT">[PROV-LAYOUT]</dt><dd>W3C PROV Working Group. <a href="http://www.w3.org/2011/prov/wiki/Diagrams"><cite>PROV Graph Layout Conventions</cite></a>. 2012. URL: <a href="http://www.w3.org/2011/prov/wiki/Diagrams">http://www.w3.org/2011/prov/wiki/Diagrams</a>
</dd><dt id="bib-PROV-LINKS">[PROV-LINKS]</dt><dd>Luc Moreau; Timothy Lebo; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-links-20130430/"><cite>Linking Across Provenance Bundles</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-links-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-links-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-links-20130430/</span></a>
</dd><dt id="bib-PROV-OVERVIEW">[PROV-OVERVIEW]</dt><dd>Paul Groth; Luc Moreau; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/"><cite>PROV-OVERVIEW: An Overview of the PROV Family of Documents</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-overview-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/</span></a>
--- a/model/provbib.js Fri Apr 26 09:26:16 2013 +0100
+++ b/model/provbib.js Fri Apr 26 09:27:12 2013 +0100
@@ -100,7 +100,7 @@
"PROV-DICTIONARY":
"Tom De Nies; Sam Coppens; eds. "+
- "<a href=\"http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/\"><cite>PROV Dictionary</cite></a>. "+
+ "<a href=\"http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/\"><cite>PROV Dictionary: Modeling Provenance for Dictionary Data Structures</cite></a>. "+
"30 April 2013, W3C Note. "+
"URL: <a href=\"http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/\">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/</a>",
--- a/model/releases/REC-prov-constraints-20130430/Overview.html Fri Apr 26 09:26:16 2013 +0100
+++ b/model/releases/REC-prov-constraints-20130430/Overview.html Fri Apr 26 09:27:12 2013 +0100
@@ -595,12 +595,6 @@
color: #ff4500;
}
-
-/* --- --- */
-ol.algorithm { counter-reset:numsection; list-style-type: none; }
-ol.algorithm li { margin: 0.5em 0; }
-ol.algorithm li:before { font-weight: bold; counter-increment: numsection; content: counters(numsection, ".") ") "; }
-
/* --- TOC --- */
.toc a, .tof a {
text-decoration: none;
@@ -709,7 +703,7 @@
</dl>
<p>
- Please refer to the <a href="http://www.w3.org/2011/prov/errata.html">errata</a> for this document, which may include some normative corrections.
+ Please refer to the <a href="http://www.w3.org/2011/prov/errata.html"><strong>errata</strong></a> for this document, which may include some normative corrections.
</p>
@@ -2966,8 +2960,7 @@
class="name">e1</span> may be used multiple times by
<span class="name">a</span>, usage <span class="name">use</span>
may not be involved in the derivation (for example, it may well have taken place after
-the generation of <span
-class="name">e2</span>).</p>
+the generation of <span class="name">e2</span>).</p>
</div>
-->
@@ -5484,7 +5477,7 @@
</dd><dt id="bib-Logic">[Logic]</dt><dd>W. E. Johnson. <a href="http://www.ditext.com/johnson/intro-3.html"><cite>Logic: Part III</cite></a>.1924. URL: <a href="http://www.ditext.com/johnson/intro-3.html">http://www.ditext.com/johnson/intro-3.html</a>
</dd><dt id="bib-PROV-AQ">[PROV-AQ]</dt><dd>Graham Klyne; Paul Groth; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/"><cite>Provenance Access and Query</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/">http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/</a>
</dd><dt id="bib-PROV-DC">[PROV-DC]</dt><dd>Daniel Garijo; Kai Eckert; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/"><cite>Dublin Core to PROV Mapping</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/">http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/</a>
-</dd><dt id="bib-PROV-DICTIONARY">[PROV-DICTIONARY]</dt><dd>Tom De Nies; Sam Coppens; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><cite>PROV Dictionary</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/</a>
+</dd><dt id="bib-PROV-DICTIONARY">[PROV-DICTIONARY]</dt><dd>Tom De Nies; Sam Coppens; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><cite>PROV Dictionary: Modeling Provenance for Dictionary Data Structures</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/</a>
</dd><dt id="bib-PROV-LINKS">[PROV-LINKS]</dt><dd>Luc Moreau; Timothy Lebo; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-links-20130430/"><cite>Linking Across Provenance Bundles</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-links-20130430/">http://www.w3.org/TR/2013/NOTE-prov-links-20130430/</a>
</dd><dt id="bib-PROV-OVERVIEW">[PROV-OVERVIEW]</dt><dd>Paul Groth; Luc Moreau; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/"><cite>PROV-OVERVIEW: An Overview of the PROV Family of Documents</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/">http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/</a>
</dd><dt id="bib-PROV-PRIMER">[PROV-PRIMER]</dt><dd>Yolanda Gil; Simon Miles; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/"><cite>PROV Model Primer</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/">http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/</a>
--- a/model/releases/REC-prov-constraints-20130430/diff-c.html Fri Apr 26 09:26:16 2013 +0100
+++ b/model/releases/REC-prov-constraints-20130430/diff-c.html Fri Apr 26 09:27:12 2013 +0100
@@ -5179,7 +5179,7 @@
</dd><dt id="bib-Logic">[Logic]</dt><dd>W. E. Johnson. <a href="http://www.ditext.com/johnson/intro-3.html"><cite>Logic: Part III</cite></a>.1924. URL: <a href="http://www.ditext.com/johnson/intro-3.html">http://www.ditext.com/johnson/intro-3.html</a>
</dd><dt id="bib-PROV-AQ">[PROV-AQ]</dt><dd>Graham Klyne; Paul Groth; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/"><cite>Provenance Access and Query</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-aq-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/</span></a>
</dd><dt id="bib-PROV-DC">[PROV-DC]</dt><dd>Daniel Garijo; Kai Eckert; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/"><cite>Dublin Core to PROV Mapping</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-dc-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/</span></a>
-</dd><dt id="bib-PROV-DICTIONARY">[PROV-DICTIONARY]</dt><dd>Tom De Nies; Sam Coppens; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><cite>PROV Dictionary</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/</span></a>
+</dd><dt id="bib-PROV-DICTIONARY">[PROV-DICTIONARY]</dt><dd>Tom De Nies; Sam Coppens; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><cite>PROV <span class="insert">Dictionary: Modeling Provenance for </span>Dictionary<span class="insert"> Data Structures</span></cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/</span></a>
</dd><dt id="bib-PROV-LINKS">[PROV-LINKS]</dt><dd>Luc Moreau; Timothy Lebo; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-links-20130430/"><cite>Linking Across Provenance Bundles</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-links-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-links-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-links-20130430/</span></a>
</dd><dt id="bib-PROV-OVERVIEW">[PROV-OVERVIEW]</dt><dd>Paul Groth; Luc Moreau; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/"><cite>PROV-OVERVIEW: An Overview of the PROV Family of Documents</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-overview-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/</span></a>
</dd><dt id="bib-PROV-PRIMER">[PROV-PRIMER]</dt><dd>Yolanda Gil; Simon Miles; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/"><cite>PROV Model Primer</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-primer-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/</span></a>
--- a/model/releases/REC-prov-dm-20130430/Overview.html Fri Apr 26 09:26:16 2013 +0100
+++ b/model/releases/REC-prov-dm-20130430/Overview.html Fri Apr 26 09:27:12 2013 +0100
@@ -4114,7 +4114,7 @@
</dd><dt id="bib-Mappings">[Mappings]</dt><dd>Satya Sahoo; Paul Groth; Olaf Hartig; Simon Miles; Sam Coppens; James Myers; Yolanda Gil; Luc Moreau; Jun Zhao; Michael Panzer; Daniel Garijo <a href="http://www.w3.org/2005/Incubator/prov/wiki/Provenance_Vocabulary_Mappings"><cite>Provenance Vocabulary Mappings</cite></a>. August 2010 URL: <a href="http://www.w3.org/2005/Incubator/prov/wiki/Provenance_Vocabulary_Mappings">http://www.w3.org/2005/Incubator/prov/wiki/Provenance_Vocabulary_Mappings</a>
</dd><dt id="bib-PROV-AQ">[PROV-AQ]</dt><dd>Graham Klyne; Paul Groth; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/"><cite>Provenance Access and Query</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/">http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/</a>
</dd><dt id="bib-PROV-DC">[PROV-DC]</dt><dd>Daniel Garijo; Kai Eckert; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/"><cite>Dublin Core to PROV Mapping</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/">http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/</a>
-</dd><dt id="bib-PROV-DICTIONARY">[PROV-DICTIONARY]</dt><dd>Tom De Nies; Sam Coppens; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><cite>PROV Dictionary</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/</a>
+</dd><dt id="bib-PROV-DICTIONARY">[PROV-DICTIONARY]</dt><dd>Tom De Nies; Sam Coppens; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><cite>PROV Dictionary: Modeling Provenance for Dictionary Data Structures</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/</a>
</dd><dt id="bib-PROV-LAYOUT">[PROV-LAYOUT]</dt><dd>W3C PROV Working Group. <a href="http://www.w3.org/2011/prov/wiki/Diagrams"><cite>PROV Graph Layout Conventions</cite></a>. 2012. URL: <a href="http://www.w3.org/2011/prov/wiki/Diagrams">http://www.w3.org/2011/prov/wiki/Diagrams</a>
</dd><dt id="bib-PROV-LINKS">[PROV-LINKS]</dt><dd>Luc Moreau; Timothy Lebo; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-links-20130430/"><cite>Linking Across Provenance Bundles</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-links-20130430/">http://www.w3.org/TR/2013/NOTE-prov-links-20130430/</a>
</dd><dt id="bib-PROV-OVERVIEW">[PROV-OVERVIEW]</dt><dd>Paul Groth; Luc Moreau; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/"><cite>PROV-OVERVIEW: An Overview of the PROV Family of Documents</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/">http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/</a>
--- a/model/releases/REC-prov-dm-20130430/diff.html Fri Apr 26 09:26:16 2013 +0100
+++ b/model/releases/REC-prov-dm-20130430/diff.html Fri Apr 26 09:27:12 2013 +0100
@@ -4160,7 +4160,7 @@
</dd><dt id="bib-Mappings">[Mappings]</dt><dd>Satya Sahoo; Paul Groth; Olaf Hartig; Simon Miles; Sam Coppens; James Myers; Yolanda Gil; Luc Moreau; Jun Zhao; Michael Panzer; Daniel Garijo <a href="http://www.w3.org/2005/Incubator/prov/wiki/Provenance_Vocabulary_Mappings"><cite>Provenance Vocabulary Mappings</cite></a>. August 2010 URL: <a href="http://www.w3.org/2005/Incubator/prov/wiki/Provenance_Vocabulary_Mappings">http://www.w3.org/2005/Incubator/prov/wiki/Provenance_Vocabulary_Mappings</a>
</dd><dt id="bib-PROV-AQ">[PROV-AQ]</dt><dd>Graham Klyne; Paul Groth; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/"><cite>Provenance Access and Query</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-aq-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/</span></a>
</dd><dt id="bib-PROV-DC">[PROV-DC]</dt><dd>Daniel Garijo; Kai Eckert; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/"><cite>Dublin Core to PROV Mapping</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-dc-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/</span></a>
-</dd><dt id="bib-PROV-DICTIONARY">[PROV-DICTIONARY]</dt><dd>Tom De Nies; Sam Coppens; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><cite>PROV Dictionary</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/</span></a>
+</dd><dt id="bib-PROV-DICTIONARY">[PROV-DICTIONARY]</dt><dd>Tom De Nies; Sam Coppens; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><cite>PROV <span class="insert">Dictionary: Modeling Provenance for </span>Dictionary<span class="insert"> Data Structures</span></cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/</span></a>
</dd><dt id="bib-PROV-LAYOUT">[PROV-LAYOUT]</dt><dd>W3C PROV Working Group. <a href="http://www.w3.org/2011/prov/wiki/Diagrams"><cite>PROV Graph Layout Conventions</cite></a>. 2012. URL: <a href="http://www.w3.org/2011/prov/wiki/Diagrams">http://www.w3.org/2011/prov/wiki/Diagrams</a>
</dd><dt id="bib-PROV-LINKS">[PROV-LINKS]</dt><dd>Luc Moreau; Timothy Lebo; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-links-20130430/"><cite>Linking Across Provenance Bundles</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-links-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-links-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-links-20130430/</span></a>
</dd><dt id="bib-PROV-OVERVIEW">[PROV-OVERVIEW]</dt><dd>Paul Groth; Luc Moreau; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/"><cite>PROV-OVERVIEW: An Overview of the PROV Family of Documents</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-overview-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/</span></a>
--- a/model/releases/REC-prov-n-20130430/Overview.html Fri Apr 26 09:26:16 2013 +0100
+++ b/model/releases/REC-prov-n-20130430/Overview.html Fri Apr 26 09:27:12 2013 +0100
@@ -3151,7 +3151,7 @@
</dd><dt id="bib-XMLSCHEMA11-2">[XMLSCHEMA11-2]</dt><dd>Henry S. Thompson et al. <a href="http://www.w3.org/TR/2012/REC-xmlschema11-2-20120405/"><cite>W3C XML Schema Definition Language (XSD) 1.1 Part 2: Datatypes</cite></a>. 5 April 2012. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2012/REC-xmlschema11-2-20120405/">http://www.w3.org/TR/2012/REC-xmlschema11-2-20120405/</a>
</dd></dl></section><section id="informative-references"><h3><span class="secno">C.2 </span>Informative references</h3><dl class="bibliography"><dt id="bib-PROV-AQ">[PROV-AQ]</dt><dd>Graham Klyne; Paul Groth; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/"><cite>Provenance Access and Query</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/">http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/</a>
</dd><dt id="bib-PROV-DC">[PROV-DC]</dt><dd>Daniel Garijo; Kai Eckert; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/"><cite>Dublin Core to PROV Mapping</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/">http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/</a>
-</dd><dt id="bib-PROV-DICTIONARY">[PROV-DICTIONARY]</dt><dd>Tom De Nies; Sam Coppens; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><cite>PROV Dictionary</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/</a>
+</dd><dt id="bib-PROV-DICTIONARY">[PROV-DICTIONARY]</dt><dd>Tom De Nies; Sam Coppens; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><cite>PROV Dictionary: Modeling Provenance for Dictionary Data Structures</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/</a>
</dd><dt id="bib-PROV-LINKS">[PROV-LINKS]</dt><dd>Luc Moreau; Timothy Lebo; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-links-20130430/"><cite>Linking Across Provenance Bundles</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-links-20130430/">http://www.w3.org/TR/2013/NOTE-prov-links-20130430/</a>
</dd><dt id="bib-PROV-OVERVIEW">[PROV-OVERVIEW]</dt><dd>Paul Groth; Luc Moreau; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/"><cite>PROV-OVERVIEW: An Overview of the PROV Family of Documents</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/">http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/</a>
</dd><dt id="bib-PROV-PRIMER">[PROV-PRIMER]</dt><dd>Yolanda Gil; Simon Miles; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/"><cite>PROV Model Primer</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/">http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/</a>
--- a/model/releases/REC-prov-n-20130430/diff-n.html Fri Apr 26 09:26:16 2013 +0100
+++ b/model/releases/REC-prov-n-20130430/diff-n.html Fri Apr 26 09:27:12 2013 +0100
@@ -3180,7 +3180,7 @@
</dd><dt id="bib-XMLSCHEMA11-2">[XMLSCHEMA11-2]</dt><dd>Henry S. Thompson et al. <a href="http://www.w3.org/TR/2012/REC-xmlschema11-2-20120405/"><cite>W3C XML Schema Definition Language (XSD) 1.1 Part 2: Datatypes</cite></a>. 5 April 2012. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2012/REC-xmlschema11-2-20120405/">http://www.w3.org/TR/2012/REC-xmlschema11-2-20120405/</a>
</dd></dl></section><section id="informative-references"><h3><span class="secno">C.2 </span>Informative references</h3><dl class="bibliography"><dt id="bib-PROV-AQ">[PROV-AQ]</dt><dd>Graham Klyne; Paul Groth; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/"><cite>Provenance Access and Query</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-aq-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/</span></a>
</dd><dt id="bib-PROV-DC">[PROV-DC]</dt><dd>Daniel Garijo; Kai Eckert; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/"><cite>Dublin Core to PROV Mapping</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-dc-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/</span></a>
-</dd><dt id="bib-PROV-DICTIONARY">[PROV-DICTIONARY]</dt><dd>Tom De Nies; Sam Coppens; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><cite>PROV Dictionary</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/</span></a>
+</dd><dt id="bib-PROV-DICTIONARY">[PROV-DICTIONARY]</dt><dd>Tom De Nies; Sam Coppens; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><cite>PROV <span class="insert">Dictionary: Modeling Provenance for </span>Dictionary<span class="insert"> Data Structures</span></cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/</span></a>
</dd><dt id="bib-PROV-LINKS">[PROV-LINKS]</dt><dd>Luc Moreau; Timothy Lebo; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-links-20130430/"><cite>Linking Across Provenance Bundles</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-links-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-links-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-links-20130430/</span></a>
</dd><dt id="bib-PROV-OVERVIEW">[PROV-OVERVIEW]</dt><dd>Paul Groth; Luc Moreau; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/"><cite>PROV-OVERVIEW: An Overview of the PROV Family of Documents</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-overview-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/</span></a>
</dd><dt id="bib-PROV-PRIMER">[PROV-PRIMER]</dt><dd>Yolanda Gil; Simon Miles; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/"><cite>PROV Model Primer</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-primer-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/</span></a>
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/namespace/prov-aq.ttl Fri Apr 26 09:27:12 2013 +0100
@@ -0,0 +1,255 @@
+@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
+@prefix : <http://www.w3.org/ns/prov#> .
+@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
+@prefix owl: <http://www.w3.org/2002/07/owl#> .
+@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
+
+
+
+<http://www.w3.org/ns/prov-aq#>
+ a owl:Ontology ;
+ rdfs:comment "0.2"^^xsd:string, """This document is published by the Provenance Working Group (http://www.w3.org/2011/prov/wiki/Main_Page).
+
+If you wish to make comments regarding this document, please send them to public-prov-comments@w3.org (subscribe public-prov-comments-request@w3.org, archives http://lists.w3.org/Archives/Public/public-prov-comments/). All feedback is welcome."""@en ;
+ rdfs:label "PROV Access and Query Ontology"@en ;
+ rdfs:seeAlso <http://www.w3.org/TR/prov#>, <http://www.w3.org/TR/prov-aq/> ;
+ owl:versionIRI <http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/> .
+
+
+##prov-aq definitions
+
+
+:ServiceDescription
+ a owl:Class ;
+ rdfs:comment "Type for a generic provenance query service. Mainly for use in RDF provenance query service descriptions, to facilitate discovery in linked data environments." ;
+ rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
+ rdfs:label "ServiceDescription" ;
+ rdfs:subClassOf :SoftwareAgent ;
+ :aq "http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/#provenance-query-service-discovery"^^xsd:anyURI ;
+ :category "access-and-query" .
+
+:DirectQueryService
+ a owl:Class ;
+ rdfs:comment "Type for a generic provenance query service. Mainly for use in RDF provenance query service descriptions, to facilitate discovery in linked data environments." ;
+ rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
+ rdfs:label "ProvenanceService" ;
+ rdfs:subClassOf :SoftwareAgent ;
+ :aq "http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/#provenance-query-service-discovery"^^xsd:anyURI ;
+ :category "access-and-query" .
+
+:has_anchor
+ a owl:ObjectProperty ;
+ rdfs:comment "Indicates anchor URI for a potentially dynamic resource instance."@en ;
+ rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
+ rdfs:label "has_anchor" ;
+ :aq "http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/#resource-represented-as-html"^^xsd:anyURI ;
+ :category "access-and-query" ;
+ :inverse "anchorOf" .
+
+:has_provenance
+ a owl:ObjectProperty ;
+ rdfs:comment "Indicates a provenance-URI for a resource; the resource identified by this property presents a provenance record about its subject or anchor resource."@en ;
+ rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
+ rdfs:label "has_provenance" ;
+ :aq "http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/#resource-represented-as-html"^^xsd:anyURI ;
+ :category "access-and-query" ;
+ :inverse "provenanceOf" .
+
+:has_query_service
+ a owl:ObjectProperty ;
+ rdfs:comment "Indicates a provenance query service that can access provenance related to its subject or anchor resource."@en ;
+ rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
+ rdfs:label "hasProvenanceService" ;
+ :aq "http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/"^^xsd:anyURI ;
+ :category "access-and-query" ;
+ :inverse "provenanceQueryServiceOf" .
+
+:describesService
+ a owl:ObjectProperty ;
+ rdfs:comment "relates a generic provenance query service resource (type prov:ServiceDescription) to a specific query service description (e.g. a prov:DirectQueryService or a sd:Service)."@en ;
+ rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
+ rdfs:label "describesService" ;
+ :aq "http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/rovenance-query-service-description"^^xsd:anyURI ;
+ :category "access-and-query" ;
+ :inverse "serviceDescribedBy" .
+
+
+:provenanceUriTemplate
+ a owl:DatatypeProperty ;
+ rdfs:comment "Relates a provenance service to a URI template string for constructing provenance-URIs."@en ;
+ rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
+ rdfs:label "provenanceUriTemplate" ;
+ :aq "http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/"^^xsd:anyURI ;
+ :category "access-and-query" .
+
+:pingback
+ a owl:ObjectProperty ;
+ rdfs:comment "Relates a resource to a provenance pingback service that may receive additional provenance links about the resource."@en ;
+ rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
+ rdfs:label "provenance pingback" ;
+ :aq "http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/#provenance-pingback"^^xsd:anyURI ;
+ :category "access-and-query" .
+
+
+
+
+## Definitions from other ontologies
+rdfs:comment
+ a owl:AnnotationProperty ;
+ rdfs:comment ""@en ;
+ rdfs:isDefinedBy <http://www.w3.org/ns/prov#> .
+
+rdfs:isDefinedBy
+ a owl:AnnotationProperty .
+
+rdfs:label
+ a owl:AnnotationProperty ;
+ rdfs:comment ""@en ;
+ rdfs:isDefinedBy <http://www.w3.org/ns/prov#> .
+
+rdfs:seeAlso
+ a owl:AnnotationProperty ;
+ rdfs:comment ""@en .
+
+owl:Thing
+ a owl:Class .
+
+owl:topObjectProperty
+ a owl:ObjectProperty .
+
+owl:versionInfo
+ a owl:AnnotationProperty .
+
+<http://www.w3.org/ns/prov#>
+ a owl:Ontology .
+
+
+:SoftwareAgent
+ a owl:Class ;
+ rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
+ rdfs:label "SoftwareAgent" ;
+ rdfs:subClassOf owl:Thing ;
+ :category "expanded" ;
+ :component "agents-responsibility" ;
+ :definition "A software agent is running software."@en ;
+ :dm "http://www.w3.org/TR/2012/WD-prov-dm-20120703/prov-dm.html#term-agent"^^xsd:anyURI ;
+ :n "http://www.w3.org/TR/2012/WD-prov-dm-20120703/prov-n.html#expression-types"^^xsd:anyURI .
+
+:aq
+ a owl:AnnotationProperty ;
+ rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
+ rdfs:subPropertyOf rdfs:seeAlso .
+
+:category
+ a owl:AnnotationProperty ;
+ rdfs:comment "Classify prov-o terms into three categories, including 'starting-point', 'qualifed', and 'extended'. This classification is used by the prov-o html document to gently introduce prov-o terms to its users. "@en ;
+ rdfs:isDefinedBy <http://www.w3.org/ns/prov#> .
+
+:component
+ a owl:AnnotationProperty ;
+ rdfs:comment "Classify prov-o terms into six components according to prov-dm, including 'agents-responsibility', 'alternate', 'annotations', 'collections', 'derivations', and 'entities-activities'. This classification is used so that readers of prov-o specification can find its correspondence with the prov-dm specification."@en ;
+ rdfs:isDefinedBy <http://www.w3.org/ns/prov#> .
+
+:constraints
+ a owl:AnnotationProperty ;
+ rdfs:comment "A reference to the principal section of the PROV-CONSTRAINTS document that describes this concept."@en ;
+ rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
+ rdfs:subPropertyOf rdfs:seeAlso .
+
+:definition
+ a owl:AnnotationProperty ;
+ rdfs:comment "A definition quoted from PROV-DM or PROV-CONSTRAINTS that describes the concept expressed with this OWL term."@en ;
+ rdfs:isDefinedBy <http://www.w3.org/ns/prov#> .
+
+:dm
+ a owl:AnnotationProperty ;
+ rdfs:comment "A reference to the principal section of the PROV-DM document that describes this concept."@en ;
+ rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
+ rdfs:subPropertyOf rdfs:seeAlso .
+
+:editorialNote
+ a owl:AnnotationProperty ;
+ rdfs:comment "A note by the OWL development team about how this term expresses the PROV-DM concept, or how it should be used in context of semantic web or linked data."@en ;
+ rdfs:isDefinedBy <http://www.w3.org/ns/prov#> .
+
+:editorsDefinition
+ a owl:AnnotationProperty ;
+ rdfs:comment "When the prov-o term does not have a definition drawn from prov-dm, and the prov-o editor provides one."@en ;
+ rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
+ rdfs:subPropertyOf :definition .
+
+:hadUsage
+ a owl:ObjectProperty ;
+ rdfs:comment "The _optional_ Usage involved in an Entity's Derivation."@en ;
+ rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
+ rdfs:label "hadUsage" ;
+ :category "qualified" ;
+ :component "derivations" ;
+ :inverse "wasUsedInDerivation" ;
+ :sharesDefinitionWith :Usage .
+
+:inverse
+ a owl:AnnotationProperty ;
+ rdfs:comment "PROV-O does not define all property inverses. The directionalities defined in PROV-O should be given preference over those not defined. However, if users wish to name the inverse of a PROV-O property, the local name given by prov:inverse should be used."@en ;
+ rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
+ rdfs:seeAlso <http://www.w3.org/TR/prov-o/#names-of-inverse-properties> .
+
+:n
+ a owl:AnnotationProperty ;
+ rdfs:comment "A reference to the principal section of the PROV-M document that describes this concept."@en ;
+ rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
+ rdfs:subPropertyOf rdfs:seeAlso .
+
+:qualifiedForm
+ a owl:AnnotationProperty ;
+ rdfs:comment """This annotation property links a subproperty of prov:wasInfluencedBy with the subclass of prov:Influence and the qualifying property that are used to qualify it.
+
+Example annotation:
+
+ prov:wasGeneratedBy prov:qualifiedForm prov:qualifiedGeneration, prov:Generation .
+
+Then this unqualified assertion:
+
+ :entity1 prov:wasGeneratedBy :activity1 .
+
+can be qualified by adding:
+
+ :entity1 prov:qualifiedGeneration :entity1Gen .
+ :entity1Gen
+ a prov:Generation, prov:Influence;
+ prov:activity :activity1;
+ :customValue 1337 .
+
+Note how the value of the unqualified influence (prov:wasGeneratedBy :activity1) is mirrored as the value of the prov:activity (or prov:entity, or prov:agent) property on the influence class."""@en ;
+ rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
+ rdfs:subPropertyOf rdfs:seeAlso .
+
+:sharesDefinitionWith
+ a owl:AnnotationProperty ;
+ rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
+ rdfs:subPropertyOf rdfs:seeAlso .
+
+:specializationOf
+ a owl:ObjectProperty ;
+ rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
+ rdfs:label "specializationOf" ;
+ rdfs:seeAlso :alternateOf ;
+ rdfs:subPropertyOf owl:topObjectProperty ;
+ :category "expanded" ;
+ :component "alternate" ;
+ :constraints "http://www.w3.org/TR/2012/WD-prov-dm-20120703/prov-constraints.html#prov-dm-constraints-fig"^^xsd:anyURI ;
+ :definition "An entity that is a specialization of another shares all aspects of the latter, and additionally presents more specific aspects of the same thing as the latter. In particular, the lifetime of the entity being specialized contains that of any specialization. Examples of aspects include a time period, an abstraction, and a context associated with the entity."@en ;
+ :dm "http://www.w3.org/TR/2012/WD-prov-dm-20120703/prov-dm.html#term-specialization"^^xsd:anyURI ;
+ :inverse "generalizationOf" ;
+ :n "http://www.w3.org/TR/2012/WD-prov-dm-20120703/prov-n.html#expression-specialization"^^xsd:anyURI .
+
+:todo
+ a owl:AnnotationProperty .
+
+:unqualifiedForm
+ a owl:AnnotationProperty ;
+ rdfs:comment "Classes and properties used to qualify relationships are annotated with prov:unqualifiedForm to indicate the property used to assert an unqualified provenance relation."@en ;
+ rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
+ rdfs:subPropertyOf rdfs:seeAlso .
+
+
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/namespace/prov-core.xsd Fri Apr 26 09:27:12 2013 +0100
@@ -0,0 +1,484 @@
+<?xml version="1.0" encoding="utf-8"?>
+
+<!--
+ In PROV-DM, all ids are qualified names, specified as prov:QualifiedName in PROV-N.
+ In this schema, all ids are instead defined as xsd:QNames.
+ -->
+
+
+<xs:schema targetNamespace="http://www.w3.org/ns/prov#"
+ xmlns:xs="http://www.w3.org/2001/XMLSchema"
+ xmlns:prov="http://www.w3.org/ns/prov#"
+ xmlns:cu="http://www.w3.org/1999/xhtml/datatypes/"
+ xmlns:xml="http://www.w3.org/XML/1998/namespace"
+ elementFormDefault="qualified"
+ attributeFormDefault="unqualified">
+
+
+
+ <xs:import namespace="http://www.w3.org/1999/xhtml/datatypes/" />
+ <xs:import namespace="http://www.w3.org/XML/1998/namespace"
+ schemaLocation="http://www.w3.org/2001/xml.xsd"/>
+
+ <!-- Component 1 -->
+
+ <xs:complexType name="Entity">
+ <xs:sequence>
+ <!-- prov attributes -->
+ <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element ref="prov:location" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element ref="prov:value" minOccurs="0"/>
+ <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
+ </xs:sequence>
+ <xs:attribute ref="prov:id"/>
+ </xs:complexType>
+
+ <xs:complexType name="Activity">
+ <xs:sequence>
+ <xs:element name="startTime" type="xs:dateTime" minOccurs="0"/>
+ <xs:element name="endTime" type="xs:dateTime" minOccurs="0"/>
+ <!-- prov attributes -->
+ <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element ref="prov:location" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
+ </xs:sequence>
+ <xs:attribute ref="prov:id"/>
+ </xs:complexType>
+
+ <xs:complexType name="Generation">
+ <xs:sequence>
+ <xs:element name="entity" type="prov:IDRef"/>
+ <xs:element name="activity" type="prov:IDRef" minOccurs="0"/>
+ <xs:element name="time" type="xs:dateTime" minOccurs="0"/>
+ <!-- prov attributes -->
+ <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element ref="prov:location" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element ref="prov:role" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
+ </xs:sequence>
+ <xs:attribute ref="prov:id"/>
+ </xs:complexType>
+
+ <xs:complexType name="Usage">
+ <xs:sequence>
+ <xs:element name="activity" type="prov:IDRef"/>
+ <xs:element name="entity" type="prov:IDRef" minOccurs="0"/>
+ <xs:element name="time" type="xs:dateTime" minOccurs="0"/>
+ <!-- prov attributes -->
+ <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element ref="prov:location" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element ref="prov:role" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
+ </xs:sequence>
+ <xs:attribute ref="prov:id"/>
+ </xs:complexType>
+
+ <xs:complexType name="Communication">
+ <xs:sequence>
+ <xs:element name="informed" type="prov:IDRef"/>
+ <xs:element name="informant" type="prov:IDRef"/>
+ <!-- prov attributes -->
+ <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
+ </xs:sequence>
+ <xs:attribute ref="prov:id"/>
+ </xs:complexType>
+
+ <xs:complexType name="Start">
+ <xs:sequence>
+ <xs:element name="activity" type="prov:IDRef"/>
+ <xs:element name="trigger" type="prov:IDRef" minOccurs="0"/>
+ <xs:element name="starter" type="prov:IDRef" minOccurs="0"/>
+ <xs:element name="time" type="xs:dateTime" minOccurs="0"/>
+ <!-- prov attributes -->
+ <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element ref="prov:location" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element ref="prov:role" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
+ </xs:sequence>
+ <xs:attribute ref="prov:id"/>
+ </xs:complexType>
+
+ <xs:complexType name="End">
+ <xs:sequence>
+ <xs:element name="activity" type="prov:IDRef"/>
+ <xs:element name="trigger" type="prov:IDRef" minOccurs="0"/>
+ <xs:element name="ender" type="prov:IDRef" minOccurs="0"/>
+ <xs:element name="time" type="xs:dateTime" minOccurs="0"/>
+ <!-- prov attributes -->
+ <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element ref="prov:location" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element ref="prov:role" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
+ </xs:sequence>
+ <xs:attribute ref="prov:id"/>
+ </xs:complexType>
+
+ <xs:complexType name="Invalidation">
+ <xs:sequence>
+ <xs:element name="entity" type="prov:IDRef"/>
+ <xs:element name="activity" type="prov:IDRef" minOccurs="0"/>
+ <xs:element name="time" type="xs:dateTime" minOccurs="0"/>
+ <!-- prov attributes -->
+ <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element ref="prov:location" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element ref="prov:role" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
+ </xs:sequence>
+ <xs:attribute ref="prov:id"/>
+ </xs:complexType>
+
+ <!-- Component 2 -->
+
+ <xs:complexType name="Derivation">
+ <xs:sequence>
+ <xs:element name="generatedEntity" type="prov:IDRef"/>
+ <xs:element name="usedEntity" type="prov:IDRef"/>
+ <xs:element name="activity" type="prov:IDRef" minOccurs="0"/>
+ <xs:element name="generation" type="prov:IDRef" minOccurs="0"/>
+ <xs:element name="usage" type="prov:IDRef" minOccurs="0"/>
+ <!-- prov attributes -->
+ <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
+ </xs:sequence>
+ <xs:attribute ref="prov:id"/>
+ </xs:complexType>
+
+ <xs:complexType name="Revision">
+ <xs:complexContent>
+ <xs:extension base="prov:Derivation">
+ </xs:extension>
+ </xs:complexContent>
+ </xs:complexType>
+
+ <xs:complexType name="Quotation">
+ <xs:complexContent>
+ <xs:extension base="prov:Derivation">
+ </xs:extension>
+ </xs:complexContent>
+ </xs:complexType>
+
+ <xs:complexType name="PrimarySource">
+ <xs:complexContent>
+ <xs:extension base="prov:Derivation">
+ </xs:extension>
+ </xs:complexContent>
+ </xs:complexType>
+
+ <!-- Component 3 -->
+
+ <xs:complexType name="Agent">
+ <xs:sequence>
+ <!-- prov attributes -->
+ <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element ref="prov:location" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
+ </xs:sequence>
+ <xs:attribute ref="prov:id"/>
+ </xs:complexType>
+
+ <xs:complexType name="Person">
+ <xs:complexContent>
+ <xs:extension base="prov:Agent">
+ </xs:extension>
+ </xs:complexContent>
+ </xs:complexType>
+
+ <xs:complexType name="Organization">
+ <xs:complexContent>
+ <xs:extension base="prov:Agent">
+ </xs:extension>
+ </xs:complexContent>
+ </xs:complexType>
+
+ <xs:complexType name="SoftwareAgent">
+ <xs:complexContent>
+ <xs:extension base="prov:Agent">
+ </xs:extension>
+ </xs:complexContent>
+ </xs:complexType>
+
+ <xs:complexType name="Attribution">
+ <xs:sequence>
+ <xs:element name="entity" type="prov:IDRef"/>
+ <xs:element name="agent" type="prov:IDRef"/>
+ <!-- prov attributes -->
+ <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
+ </xs:sequence>
+ <xs:attribute ref="prov:id"/>
+ </xs:complexType>
+
+ <xs:complexType name="Association">
+ <xs:sequence>
+ <xs:element name="activity" type="prov:IDRef"/>
+ <xs:element name="agent" type="prov:IDRef" minOccurs="0"/>
+ <xs:element name="plan" type="prov:IDRef" minOccurs="0"/>
+ <!-- prov attributes -->
+ <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element ref="prov:role" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
+ </xs:sequence>
+ <xs:attribute ref="prov:id"/>
+ </xs:complexType>
+
+ <xs:complexType name="Delegation">
+ <xs:sequence>
+ <xs:element name="delegate" type="prov:IDRef"/>
+ <xs:element name="responsible" type="prov:IDRef"/>
+ <xs:element name="activity" type="prov:IDRef" minOccurs="0"/>
+ <!-- prov attributes -->
+ <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
+ </xs:sequence>
+ <xs:attribute ref="prov:id"/>
+ </xs:complexType>
+
+ <xs:complexType name="Influence">
+ <xs:sequence>
+ <xs:element name="influencee" type="prov:IDRef"/>
+ <xs:element name="influencer" type="prov:IDRef"/>
+ <!-- prov attributes -->
+ <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
+ </xs:sequence>
+ <xs:attribute ref="prov:id"/>
+ </xs:complexType>
+
+ <!-- Component 4 -->
+
+ <xs:complexType name="Bundle">
+ <xs:complexContent>
+ <xs:extension base="prov:Entity">
+ </xs:extension>
+ </xs:complexContent>
+ </xs:complexType>
+
+ <!-- bundle container and allowable PROV elements -->
+
+ <xs:complexType name="BundleConstructor">
+ <xs:choice minOccurs="0" maxOccurs="unbounded">
+ <xs:element ref="prov:entity"/>
+ <xs:element ref="prov:activity"/>
+ <xs:element ref="prov:wasGeneratedBy"/>
+ <xs:element ref="prov:used"/>
+ <xs:element ref="prov:wasInformedBy"/>
+ <xs:element ref="prov:wasStartedBy"/>
+ <xs:element ref="prov:wasEndedBy"/>
+ <xs:element ref="prov:wasInvalidatedBy"/>
+ <xs:element ref="prov:wasDerivedFrom"/>
+ <xs:element ref="prov:wasRevisionOf"/>
+ <xs:element ref="prov:wasQuotedFrom"/>
+ <xs:element ref="prov:hadPrimarySource"/>
+ <xs:element ref="prov:agent"/>
+ <xs:element ref="prov:person"/>
+ <xs:element ref="prov:organization"/>
+ <xs:element ref="prov:softwareAgent"/>
+ <xs:element ref="prov:wasAttributedTo"/>
+ <xs:element ref="prov:wasAssociatedWith"/>
+ <xs:element ref="prov:actedOnBehalfOf"/>
+ <xs:element ref="prov:wasInfluencedBy"/>
+ <xs:element ref="prov:bundle"/>
+ <xs:element ref="prov:specializationOf"/>
+ <xs:element ref="prov:alternateOf"/>
+ <xs:element ref="prov:collection"/>
+ <xs:element ref="prov:emptyCollection"/>
+ <xs:element ref="prov:hadMember"/>
+ <xs:element ref="prov:plan"/>
+ <xs:element ref="prov:other"/>
+ <xs:element ref="prov:internalElement"/>
+ </xs:choice>
+ <xs:attribute ref="prov:id"/>
+ </xs:complexType>
+
+ <!-- Component 5 -->
+
+ <xs:complexType name="Specialization">
+ <xs:sequence>
+ <xs:element name="specificEntity" type="prov:IDRef"/>
+ <xs:element name="generalEntity" type="prov:IDRef"/>
+ </xs:sequence>
+ </xs:complexType>
+
+ <xs:complexType name="Alternate">
+ <xs:sequence>
+ <xs:element name="alternate1" type="prov:IDRef"/>
+ <xs:element name="alternate2" type="prov:IDRef"/>
+ </xs:sequence>
+ </xs:complexType>
+
+ <!-- Component 6 -->
+
+ <xs:complexType name="Collection">
+ <xs:complexContent>
+ <xs:extension base="prov:Entity">
+ </xs:extension>
+ </xs:complexContent>
+ </xs:complexType>
+
+ <xs:complexType name="EmptyCollection">
+ <xs:complexContent>
+ <xs:extension base="prov:Collection">
+ </xs:extension>
+ </xs:complexContent>
+ </xs:complexType>
+
+ <xs:complexType name="Membership">
+ <xs:sequence>
+ <xs:element name="collection" type="prov:IDRef"/>
+ <xs:element name="entity" type="prov:IDRef" maxOccurs="unbounded"/>
+ </xs:sequence>
+ </xs:complexType>
+
+ <xs:complexType name="Plan">
+ <xs:complexContent>
+ <xs:extension base="prov:Entity">
+ </xs:extension>
+ </xs:complexContent>
+ </xs:complexType>
+
+ <xs:complexType name="InternationalizedString">
+ <xs:simpleContent>
+ <xs:extension base="xs:string">
+ <xs:attribute ref="xml:lang" use="optional"/>
+ </xs:extension>
+ </xs:simpleContent>
+ </xs:complexType>
+
+
+ <!--
+ Typed literals are encoded by means
+ of xsi:type that represent the prov:datatype.
+ -->
+
+ <xs:element name="label" type="prov:InternationalizedString"/>
+ <xs:element name="role" type="xs:anySimpleType"/>
+ <xs:element name="type" type="xs:anySimpleType"/>
+ <xs:element name="location" type="xs:anySimpleType"/>
+ <xs:element name="value" type="xs:anySimpleType"/>
+
+ <xs:attribute name="id" type="xs:QName"/>
+ <xs:attribute name="ref" type="xs:QName"/>
+
+ <xs:complexType name="IDRef">
+ <xs:attribute ref="prov:ref" use="required" />
+ </xs:complexType>
+
+ <!--
+ top-level definition of elements following the salami slice XSD design pattern
+ to encourage integration within existing non-prov XML documents.
+ -->
+
+ <!-- Component 1 elements -->
+
+ <xs:element name="entity" type="prov:Entity"/>
+ <xs:element name="activity" type="prov:Activity"/>
+ <xs:element name="wasGeneratedBy" type="prov:Generation"/>
+ <xs:element name="used" type="prov:Usage"/>
+ <xs:element name="wasInformedBy" type="prov:Communication"/>
+ <xs:element name="wasStartedBy" type="prov:Start"/>
+ <xs:element name="wasEndedBy" type="prov:End"/>
+ <xs:element name="wasInvalidatedBy" type="prov:Invalidation"/>
+
+ <!-- Component 2 elements -->
+
+ <xs:element name="wasDerivedFrom" type="prov:Derivation"/>
+ <xs:element name="wasRevisionOf" type="prov:Revision"/>
+ <xs:element name="wasQuotedFrom" type="prov:Quotation"/>
+ <xs:element name="hadPrimarySource" type="prov:PrimarySource"/>
+
+ <!-- Component 3 elements -->
+
+ <xs:element name="agent" type="prov:Agent"/>
+ <xs:element name="person" type="prov:Person"/>
+ <xs:element name="organization" type="prov:Organization"/>
+ <xs:element name="softwareAgent" type="prov:SoftwareAgent"/>
+ <xs:element name="wasAttributedTo" type="prov:Attribution"/>
+ <xs:element name="wasAssociatedWith" type="prov:Association"/>
+ <xs:element name="actedOnBehalfOf" type="prov:Delegation"/>
+ <xs:element name="wasInfluencedBy" type="prov:Influence"/>
+
+ <!-- Component 5 elements -->
+
+ <xs:element name="bundle" type="prov:Bundle"/>
+ <xs:element name="specializationOf" type="prov:Specialization"/>
+ <xs:element name="alternateOf" type="prov:Alternate"/>
+
+ <!-- Component 6 elements -->
+
+ <xs:element name="hadMember" type="prov:Membership"/>
+ <xs:element name="collection" type="prov:Collection"/>
+ <xs:element name="emptyCollection" type="prov:EmptyCollection"/>
+
+ <!-- Component 7 elements -->
+
+ <xs:element name="plan" type="prov:Plan"/>
+
+ <!-- document container and allowable PROV elements -->
+
+ <xs:element name="document" type="prov:Document" />
+
+ <xs:complexType name="Document">
+ <xs:choice minOccurs="0" maxOccurs="unbounded">
+ <xs:element ref="prov:entity"/>
+ <xs:element ref="prov:activity"/>
+ <xs:element ref="prov:wasGeneratedBy"/>
+ <xs:element ref="prov:used"/>
+ <xs:element ref="prov:wasInformedBy"/>
+ <xs:element ref="prov:wasStartedBy"/>
+ <xs:element ref="prov:wasEndedBy"/>
+ <xs:element ref="prov:wasInvalidatedBy"/>
+ <xs:element ref="prov:wasDerivedFrom"/>
+ <xs:element ref="prov:wasRevisionOf"/>
+ <xs:element ref="prov:wasQuotedFrom"/>
+ <xs:element ref="prov:hadPrimarySource"/>
+ <xs:element ref="prov:agent"/>
+ <xs:element ref="prov:person"/>
+ <xs:element ref="prov:organization"/>
+ <xs:element ref="prov:softwareAgent"/>
+ <xs:element ref="prov:wasAttributedTo"/>
+ <xs:element ref="prov:wasAssociatedWith"/>
+ <xs:element ref="prov:actedOnBehalfOf"/>
+ <xs:element ref="prov:wasInfluencedBy"/>
+ <xs:element ref="prov:bundle"/>
+ <xs:element ref="prov:specializationOf"/>
+ <xs:element ref="prov:alternateOf"/>
+ <xs:element ref="prov:collection"/>
+ <xs:element ref="prov:emptyCollection"/>
+ <xs:element ref="prov:hadMember"/>
+ <xs:element ref="prov:plan"/>
+ <xs:element ref="prov:other"/>
+ <xs:element ref="prov:internalElement"/>
+ <xs:element name="bundleContent" type="prov:BundleConstructor"/>
+ </xs:choice>
+ </xs:complexType>
+
+ <!-- abstract element used by PROV extensions -->
+
+ <xs:element name="internalElement" abstract="true" />
+
+ <!-- 'others' element used to contain non-PROV elements -->
+
+ <xs:element name="other" type="prov:Other"/>
+
+ <xs:complexType name="Other">
+ <xs:sequence>
+ <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
+ </xs:sequence>
+ </xs:complexType>
+
+</xs:schema>
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/namespace/prov-dictionary.owl Fri Apr 26 09:27:12 2013 +0100
@@ -0,0 +1,358 @@
+<?xml version="1.0"?>
+
+
+<!DOCTYPE rdf:RDF [
+ <!ENTITY owl "http://www.w3.org/2002/07/owl#" >
+ <!ENTITY xsd "http://www.w3.org/2001/XMLSchema#" >
+ <!ENTITY xml "http://www.w3.org/XML/1998/namespace" >
+ <!ENTITY rdfs "http://www.w3.org/2000/01/rdf-schema#" >
+ <!ENTITY rdf "http://www.w3.org/1999/02/22-rdf-syntax-ns#" >
+]>
+
+
+<rdf:RDF xmlns="http://www.w3.org/ns/prov#"
+ xml:base="http://www.w3.org/ns/prov"
+ xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
+ xmlns:owl="http://www.w3.org/2002/07/owl#"
+ xmlns:xsd="http://www.w3.org/2001/XMLSchema#"
+ xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+ xmlns:xml="http://www.w3.org/XML/1998/namespace">
+ <owl:Ontology rdf:about="http://www.w3.org/ns/prov-dictionary#">
+ <rdfs:label xml:lang="en">W3C PROVenance Interchange Ontology (PROV-O) Dictionary Extension</rdfs:label>
+ <rdfs:comment xml:lang="en">This document is published by the Provenance Working Group (http://www.w3.org/2011/prov/wiki/Main_Page).
+
+If you wish to make comments regarding this document, please send them to public-prov-comments@w3.org (subscribe public-prov-comments-request@w3.org, archives http://lists.w3.org/Archives/Public/public-prov-comments/). All feedback is welcome.</rdfs:comment>
+ <rdfs:seeAlso rdf:resource="http://www.w3.org/TR/prov-dictionary/"/>
+ <rdfs:seeAlso rdf:resource="http://www.w3.org/ns/prov"/>
+ </owl:Ontology>
+
+ <owl:Ontology rdf:about="http://www.w3.org/ns/prov#"></owl:Ontology>
+
+ <!--
+ ///////////////////////////////////////////////////////////////////////////////////////
+ //
+ // Object Properties
+ //
+ ///////////////////////////////////////////////////////////////////////////////////////
+ -->
+
+
+
+
+ <!-- http://www.w3.org/ns/prov#derivedByInsertionFrom -->
+
+ <owl:ObjectProperty rdf:about="http://www.w3.org/ns/prov#derivedByInsertionFrom">
+ <rdfs:label>derivedByInsertionFrom</rdfs:label>
+ <constraints rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#dictionary-constraints</constraints>
+ <n rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#expression-dictionary-insertion</n>
+ <dm rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#term-dictionary-insertion</dm>
+ <definition>The dictionary was derived from the other by insertion. Can be qualified with prov:qualifiedInsertion, which shows details of the insertion, in particular the inserted key-entity pairs.</definition>
+ <component>collections</component>
+ <category>collections</category>
+ <rdfs:isDefinedBy rdf:resource="http://www.w3.org/ns/prov#"/>
+ <rdfs:range rdf:resource="http://www.w3.org/ns/prov#Dictionary"/>
+ <rdfs:domain rdf:resource="http://www.w3.org/ns/prov#Dictionary"/>
+ <rdfs:subPropertyOf rdf:resource="http://www.w3.org/ns/prov#wasDerivedFrom"/>
+ </owl:ObjectProperty>
+
+
+
+ <!-- http://www.w3.org/ns/prov#derivedByRemovalFrom -->
+
+ <owl:ObjectProperty rdf:about="http://www.w3.org/ns/prov#derivedByRemovalFrom">
+ <rdfs:label>derivedByRemovalFrom</rdfs:label>
+ <constraints rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#dictionary-constraints</constraints>
+ <n rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#expression-dictionary-removal</n>
+ <dm rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#term-dictionary-removal</dm>
+ <component>collections</component>
+ <definition>The dictionary was derived from the other by removal. Can be qualified with prov:qualifiedRemoval, which shows details of the removal, in particular the removed keys.</definition>
+ <category>collections</category>
+ <rdfs:isDefinedBy rdf:resource="http://www.w3.org/ns/prov#"/>
+ <rdfs:range rdf:resource="http://www.w3.org/ns/prov#Dictionary"/>
+ <rdfs:domain rdf:resource="http://www.w3.org/ns/prov#Dictionary"/>
+ <rdfs:subPropertyOf rdf:resource="http://www.w3.org/ns/prov#wasDerivedFrom"/>
+ </owl:ObjectProperty>
+
+
+
+ <!-- http://www.w3.org/ns/prov#dictionary -->
+
+ <owl:ObjectProperty rdf:about="http://www.w3.org/ns/prov#dictionary">
+ <rdfs:label>dictionary</rdfs:label>
+ <constraints rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#dictionary-constraints</constraints>
+ <n rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#expression-dictionary-insertion</n>
+ <n rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#expression-dictionary-removal</n>
+ <dm rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#term-dictionary-insertion</dm>
+ <dm rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#term-dictionary-removal</dm>
+ <category>collections</category>
+ <component>collections</component>
+ <definition>The property used by a prov:Insertion and prov:Removal to cite the prov:Dictionary that was prov:derivedByInsertionFrom or prov:derivedByRemovalFrom another dictionary.</definition>
+ <rdfs:isDefinedBy rdf:resource="http://www.w3.org/ns/prov#"/>
+ <rdfs:range rdf:resource="http://www.w3.org/ns/prov#Dictionary"/>
+ <rdfs:domain rdf:resource="http://www.w3.org/ns/prov#Insertion"/>
+ <rdfs:domain rdf:resource="http://www.w3.org/ns/prov#Removal"/>
+ <rdfs:subPropertyOf rdf:resource="http://www.w3.org/ns/prov#entity"/>
+ </owl:ObjectProperty>
+
+
+ <!-- http://www.w3.org/ns/prov#hadDictionaryMember -->
+
+ <owl:ObjectProperty rdf:about="http://www.w3.org/ns/prov#hadDictionaryMember">
+ <rdfs:label>hadDictionaryMember</rdfs:label>
+ <constraints rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#dictionary-constraints</constraints>
+ <n rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#expression-dictionary-membership</n>
+ <dm rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#term-dictionary-membership</dm>
+ <definition>Describes the key-entity pair that was member of a prov:Dictionary. A dictionary can have multiple members.</definition>
+ <component>collections</component>
+ <category>collections</category>
+ <rdfs:isDefinedBy rdf:resource="http://www.w3.org/ns/prov#"/>
+ <rdfs:domain rdf:resource="http://www.w3.org/ns/prov#Dictionary"/>
+ <rdfs:range rdf:resource="http://www.w3.org/ns/prov#KeyEntityPair"/>
+ </owl:ObjectProperty>
+
+
+
+ <!-- http://www.w3.org/ns/prov#insertedKeyEntityPair -->
+
+ <owl:ObjectProperty rdf:about="http://www.w3.org/ns/prov#insertedKeyEntityPair">
+ <rdfs:label>insertedKeyEntityPair</rdfs:label>
+ <constraints rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#dictionary-constraints</constraints>
+ <n rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#expression-dictionary-insertion</n>
+ <dm rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#term-dictionary-insertion</dm>
+ <component>collections</component>
+ <category>collections</category>
+ <definition>An object property to refer to the prov:KeyEntityPair inserted into a prov:Dictionary.</definition>
+ <rdfs:isDefinedBy rdf:resource="http://www.w3.org/ns/prov#"/>
+ <rdfs:domain rdf:resource="http://www.w3.org/ns/prov#Insertion"/>
+ <rdfs:range rdf:resource="http://www.w3.org/ns/prov#KeyEntityPair"/>
+ </owl:ObjectProperty>
+
+
+
+ <!-- http://www.w3.org/ns/prov#pairEntity -->
+
+ <owl:ObjectProperty rdf:about="http://www.w3.org/ns/prov#pairEntity">
+ <rdf:type rdf:resource="&owl;FunctionalProperty"/>
+ <rdfs:label>pairKey</rdfs:label>
+ <constraints rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#dictionary-constraints</constraints>
+ <n rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#expression-dictionary-membership</n>
+ <dm rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#term-dictionary-membership</dm>
+ <category>collections</category>
+ <component>collections</component>
+ <definition>The entity of a prov:KeyEntityPair, which is an element of a prov:Dictionary.</definition>
+ <rdfs:isDefinedBy rdf:resource="http://www.w3.org/ns/prov#"/>
+ <rdfs:range rdf:resource="http://www.w3.org/ns/prov#Entity"/>
+ <rdfs:domain rdf:resource="http://www.w3.org/ns/prov#KeyEntityPair"/>
+ </owl:ObjectProperty>
+
+
+
+ <!-- http://www.w3.org/ns/prov#qualifiedInsertion -->
+
+ <owl:ObjectProperty rdf:about="http://www.w3.org/ns/prov#qualifiedInsertion">
+ <rdfs:label>qualifiedInsertion</rdfs:label>
+ <constraints rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#dictionary-constraints</constraints>
+ <n rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#expression-dictionary-insertion</n>
+ <dm rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#term-dictionary-insertion</dm>
+ <definition>prov:qualifiedInsertion shows the details of an insertion, in particular the inserted key-entity pairs.</definition>
+ <category>collections</category>
+ <component>collections</component>
+ <rdfs:isDefinedBy rdf:resource="http://www.w3.org/ns/prov#"/>
+ <rdfs:domain rdf:resource="http://www.w3.org/ns/prov#Dictionary"/>
+ <rdfs:range rdf:resource="http://www.w3.org/ns/prov#Insertion"/>
+ <rdfs:subPropertyOf rdf:resource="http://www.w3.org/ns/prov#qualifiedDerivation"/>
+ </owl:ObjectProperty>
+
+
+
+ <!-- http://www.w3.org/ns/prov#qualifiedRemoval -->
+
+ <owl:ObjectProperty rdf:about="http://www.w3.org/ns/prov#qualifiedRemoval">
+ <rdfs:label>qualifiedRemoval</rdfs:label>
+ <constraints rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#dictionary-constraints</constraints>
+ <n rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#expression-dictionary-removal</n>
+ <dm rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#term-dictionary-removal</dm>
+ <category>collections</category>
+ <component>collections</component>
+ <definition>prov:qualifiedRemoval shows the details of a removal, in particular the removed keys.</definition>
+ <rdfs:isDefinedBy rdf:resource="http://www.w3.org/ns/prov#"/>
+ <rdfs:domain rdf:resource="http://www.w3.org/ns/prov#Dictionary"/>
+ <rdfs:range rdf:resource="http://www.w3.org/ns/prov#Removal"/>
+ <rdfs:subPropertyOf rdf:resource="http://www.w3.org/ns/prov#qualifiedDerivation"/>
+ </owl:ObjectProperty>
+
+
+ <!--
+ ///////////////////////////////////////////////////////////////////////////////////////
+ //
+ // Data properties
+ //
+ ///////////////////////////////////////////////////////////////////////////////////////
+ -->
+
+
+
+
+ <!-- http://www.w3.org/ns/prov#pairKey -->
+
+ <owl:DatatypeProperty rdf:about="http://www.w3.org/ns/prov#pairKey">
+ <rdf:type rdf:resource="&owl;FunctionalProperty"/>
+ <rdfs:label>pairKey</rdfs:label>
+ <constraints rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#dictionary-constraints</constraints>
+ <n rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#expression-dictionary-membership</n>
+ <dm rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#term-dictionary-membership</dm>
+ <component>collections</component>
+ <definition>The key of a prov:KeyEntityPair, which is an element of a prov:Dictionary.</definition>
+ <category>collections</category>
+ <rdfs:range rdf:resource="&rdfs;Literal"/>
+ <rdfs:isDefinedBy rdf:resource="http://www.w3.org/ns/prov#"/>
+ <rdfs:domain rdf:resource="http://www.w3.org/ns/prov#KeyEntityPair"/>
+ </owl:DatatypeProperty>
+
+
+
+ <!-- http://www.w3.org/ns/prov#removedKey -->
+
+ <owl:DatatypeProperty rdf:about="http://www.w3.org/ns/prov#removedKey">
+ <rdfs:label>removedKey</rdfs:label>
+ <constraints rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#dictionary-constraints</constraints>
+ <n rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#expression-dictionary-removal</n>
+ <dm rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#term-dictionary-removal</dm>
+ <category>collections</category>
+ <definition>The key removed in a Removal.</definition>
+ <component>collections</component>
+ <rdfs:range rdf:resource="&rdfs;Literal"/>
+ <rdfs:isDefinedBy rdf:resource="http://www.w3.org/ns/prov#"/>
+ <rdfs:domain rdf:resource="http://www.w3.org/ns/prov#Removal"/>
+ </owl:DatatypeProperty>
+
+
+
+ <!--
+ ///////////////////////////////////////////////////////////////////////////////////////
+ //
+ // Classes
+ //
+ ///////////////////////////////////////////////////////////////////////////////////////
+ -->
+
+
+ <!-- http://www.w3.org/ns/prov#Dictionary -->
+
+ <owl:Class rdf:about="http://www.w3.org/ns/prov#Dictionary">
+ <rdfs:label>Dictionary</rdfs:label>
+ <dm rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#dictionary-conceptual-definition</dm>
+ <constraints rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#dictionary-constraints</constraints>
+ <n rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#expression-dictionary</n>
+ <definition>A dictionary is an entity that provides a structure to some constituents, which are themselves entities. These constituents are said to be member of the dictionary.</definition>
+ <rdfs:comment>A given dictionary forms a given structure for its members. A different structure (obtained either by insertion or removal of members) constitutes a different dictionary.</rdfs:comment>
+ <component>collections</component>
+ <category>collections</category>
+ <rdfs:comment>This concept allows for the provenance of the dictionary, but also of its constituents to be expressed. Such a notion of dictionary corresponds to a wide variety of concrete data structures, such as a maps or associative arrays.</rdfs:comment>
+ <rdfs:isDefinedBy rdf:resource="http://www.w3.org/ns/prov#"/>
+ </owl:Class>
+
+
+
+ <!-- http://www.w3.org/ns/prov#EmptyDictionary -->
+
+ <owl:Class rdf:about="http://www.w3.org/ns/prov#EmptyDictionary">
+ <rdfs:label>Empty Dictionary</rdfs:label>
+ <rdfs:subClassOf rdf:resource="http://www.w3.org/ns/prov#Dictionary"/>
+ <rdfs:subClassOf rdf:resource="http://www.w3.org/ns/prov#EmptyCollection"/>
+ <dm rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#dictionary-conceptual-definition</dm>
+ <constraints rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#dictionary-constraints</constraints>
+ <n rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#expression-dictionary</n>
+ <component>collections</component>
+ <definition>An empty dictionary (i.e. has no members).</definition>
+ <category>collections</category>
+ <rdfs:isDefinedBy rdf:resource="http://www.w3.org/ns/prov#"/>
+ </owl:Class>
+
+
+
+ <!-- http://www.w3.org/ns/prov#Insertion -->
+
+ <owl:Class rdf:about="http://www.w3.org/ns/prov#Insertion">
+ <rdfs:label>Insertion</rdfs:label>
+ <rdfs:subClassOf rdf:resource="http://www.w3.org/ns/prov#Derivation"/>
+ <rdfs:subClassOf>
+ <owl:Restriction>
+ <owl:onProperty rdf:resource="http://www.w3.org/ns/prov#dictionary"/>
+ <owl:cardinality rdf:datatype="&xsd;nonNegativeInteger">1</owl:cardinality>
+ </owl:Restriction>
+ </rdfs:subClassOf>
+ <rdfs:subClassOf>
+ <owl:Restriction>
+ <owl:onProperty rdf:resource="http://www.w3.org/ns/prov#insertedKeyEntityPair"/>
+ <owl:minCardinality rdf:datatype="&xsd;nonNegativeInteger">1</owl:minCardinality>
+ </owl:Restriction>
+ </rdfs:subClassOf>
+ <constraints rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#dictionary-constraints</constraints>
+ <n rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#expression-dictionary-insertion</n>
+ <dm rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#term-dictionary-insertion</dm>
+ <definition>Insertion is a derivation that describes the transformation of a dictionary into another, by insertion of one or more key-entity pairs.</definition>
+ <category>collections</category>
+ <component>collections</component>
+ <rdfs:isDefinedBy rdf:resource="http://www.w3.org/ns/prov#"/>
+ <unqualifiedForm rdf:resource="http://www.w3.org/ns/prov#derivedByInsertionFrom"/>
+ </owl:Class>
+
+
+
+ <!-- http://www.w3.org/ns/prov#KeyEntityPair -->
+
+ <owl:Class rdf:about="http://www.w3.org/ns/prov#KeyEntityPair">
+ <rdfs:label>Key-Entity Pair</rdfs:label>
+ <rdfs:subClassOf>
+ <owl:Restriction>
+ <owl:onProperty rdf:resource="http://www.w3.org/ns/prov#pairEntity"/>
+ <owl:cardinality rdf:datatype="&xsd;nonNegativeInteger">1</owl:cardinality>
+ </owl:Restriction>
+ </rdfs:subClassOf>
+ <rdfs:subClassOf>
+ <owl:Restriction>
+ <owl:onProperty rdf:resource="http://www.w3.org/ns/prov#pairKey"/>
+ <owl:cardinality rdf:datatype="&xsd;nonNegativeInteger">1</owl:cardinality>
+ </owl:Restriction>
+ </rdfs:subClassOf>
+ <constraints rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#dictionary-constraints</constraints>
+ <n rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#expression-dictionary-membership</n>
+ <dm rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#term-dictionary-membership</dm>
+ <definition>A key-entity pair. Part of a prov:Dictionary through prov:hadDictionaryMember. The key is any RDF Literal, the value is a prov:Entity.</definition>
+ <component>collections</component>
+ <category>collections</category>
+ <rdfs:isDefinedBy rdf:resource="http://www.w3.org/ns/prov#"/>
+ </owl:Class>
+
+
+
+ <!-- http://www.w3.org/ns/prov#Removal -->
+
+ <owl:Class rdf:about="http://www.w3.org/ns/prov#Removal">
+ <rdfs:label>Removal</rdfs:label>
+ <rdfs:subClassOf rdf:resource="http://www.w3.org/ns/prov#Derivation"/>
+ <rdfs:subClassOf>
+ <owl:Restriction>
+ <owl:onProperty rdf:resource="http://www.w3.org/ns/prov#dictionary"/>
+ <owl:cardinality rdf:datatype="&xsd;nonNegativeInteger">1</owl:cardinality>
+ </owl:Restriction>
+ </rdfs:subClassOf>
+ <rdfs:subClassOf>
+ <owl:Restriction>
+ <owl:onProperty rdf:resource="http://www.w3.org/ns/prov#removedKey"/>
+ <owl:minCardinality rdf:datatype="&xsd;nonNegativeInteger">1</owl:minCardinality>
+ </owl:Restriction>
+ </rdfs:subClassOf>
+ <constraints rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#dictionary-constraints</constraints>
+ <n rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#expression-dictionary-removal</n>
+ <dm rdf:datatype="&xsd;anyURI">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#term-dictionary-removal</dm>
+ <category>collections</category>
+ <definition>Removal is a derivation that describes the transformation of a dictionary into another, by removing one or more keys.</definition>
+ <component>collections</component>
+ <rdfs:isDefinedBy rdf:resource="http://www.w3.org/ns/prov#"/>
+ <unqualifiedForm rdf:resource="http://www.w3.org/ns/prov#derivedByRemovalFrom"/>
+ </owl:Class>
+</rdf:RDF>
+
+
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/namespace/prov-dictionary.ttl Fri Apr 26 09:27:12 2013 +0100
@@ -0,0 +1,246 @@
+@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
+@prefix : <http://www.w3.org/ns/prov#> .
+@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
+@prefix owl: <http://www.w3.org/2002/07/owl#> .
+@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
+
+<http://www.w3.org/ns/prov-dictionary#>
+ a owl:Ontology ;
+ rdfs:comment """This document is published by the Provenance Working Group (http://www.w3.org/2011/prov/wiki/Main_Page).
+
+If you wish to make comments regarding this document, please send them to public-prov-comments@w3.org (subscribe public-prov-comments-request@w3.org, archives http://lists.w3.org/Archives/Public/public-prov-comments/). All feedback is welcome."""@en ;
+ rdfs:label "W3C PROVenance Interchange Ontology (PROV-O) Dictionary Extension"@en ;
+ rdfs:seeAlso <http://www.w3.org/TR/prov-dictionary/>, <http://www.w3.org/ns/prov> .
+
+<http://www.w3.org/ns/prov#>
+ a owl:Ontology .
+
+:Dictionary
+ a owl:Class ;
+ rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
+ rdfs:label "Dictionary" ;
+ :definition "A dictionary is an entity that provides a structure to some constituents, which are themselves entities. These constituents are said to be member of the dictionary." ;
+ rdfs:comment "This concept allows for the provenance of the dictionary, but also of its constituents to be expressed. Such a notion of dictionary corresponds to a wide variety of concrete data structures, such as a maps or associative arrays." ;
+ rdfs:comment "A given dictionary forms a given structure for its members. A different structure (obtained either by insertion or removal of members) constitutes a different dictionary." ;
+ :category "collections" ;
+ :component "collections" ;
+ :dm "http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#dictionary-conceptual-definition"^^xsd:anyURI ;
+ :n "http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#expression-dictionary"^^xsd:anyURI ;
+ :constraints "http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#dictionary-constraints"^^xsd:anyURI .
+
+:EmptyDictionary
+ a owl:Class ;
+ rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
+ rdfs:label "Empty Dictionary" ;
+ :definition "An empty dictionary (i.e. has no members)." ;
+ rdfs:subClassOf :EmptyCollection ;
+ rdfs:subClassOf :Dictionary ;
+ :category "collections" ;
+ :component "collections" ;
+ :dm "http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#dictionary-conceptual-definition"^^xsd:anyURI ;
+ :n "http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#expression-dictionary"^^xsd:anyURI ;
+ :constraints "http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#dictionary-constraints"^^xsd:anyURI .
+
+:KeyEntityPair
+ a owl:Class ;
+ rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
+ rdfs:label "Key-Entity Pair" ;
+ :definition "A key-entity pair. Part of a prov:Dictionary through prov:hadDictionaryMember. The key is any RDF Literal, the value is a prov:Entity." ;
+ rdfs:subClassOf
+ [ a owl:Restriction ;
+ owl:onProperty :pairKey ;
+ owl:cardinality "1"^^xsd:int
+ ] ;
+ rdfs:subClassOf
+ [ a owl:Restriction ;
+ owl:onProperty :pairEntity ;
+ owl:cardinality "1"^^xsd:int
+ ] ;
+ :category "collections" ;
+ :component "collections" ;
+ :dm "http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#term-dictionary-membership"^^xsd:anyURI ;
+ :n "http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#expression-dictionary-membership"^^xsd:anyURI ;
+ :constraints "http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#dictionary-constraints"^^xsd:anyURI .
+
+:Insertion
+ a owl:Class ;
+ rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
+ rdfs:label "Insertion" ;
+ :definition "Insertion is a derivation that transforms a dictionary into another, by insertion of one or more key-entity pairs." ;
+ rdfs:subClassOf :Derivation ;
+ rdfs:subClassOf
+ [ a owl:Restriction ;
+ owl:onProperty :dictionary ;
+ owl:cardinality "1"^^xsd:int
+ ] ;
+ rdfs:subClassOf
+ [ a owl:Restriction ;
+ owl:onProperty :insertedKeyEntityPair ;
+ owl:minCardinality "1"^^xsd:int
+ ] ;
+ :category "collections" ;
+ :component "collections" ;
+ :dm "http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#term-dictionary-insertion"^^xsd:anyURI ;
+ :n "http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#expression-dictionary-insertion"^^xsd:anyURI ;
+ :constraints "http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#dictionary-constraints"^^xsd:anyURI ;
+ :unqualifiedForm :derivedByInsertionFrom .
+
+:Removal
+ a owl:Class ;
+ rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
+ rdfs:label "Removal" ;
+ :definition "Removal is a derivation that transforms a dictionary into another, by removing one or more key-entity pairs." ;
+ rdfs:subClassOf :Derivation ;
+ rdfs:subClassOf
+ [ a owl:Restriction ;
+ owl:onProperty :dictionary ;
+ owl:cardinality "1"^^xsd:int
+ ] ;
+ rdfs:subClassOf
+ [ a owl:Restriction ;
+ owl:onProperty :removedKey ;
+ owl:minCardinality "1"^^xsd:int
+ ] ;
+ :category "collections" ;
+ :component "collections" ;
+ :dm "http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#term-dictionary-removal"^^xsd:anyURI ;
+ :n "http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#expression-dictionary-removal"^^xsd:anyURI ;
+ :constraints "http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#dictionary-constraints"^^xsd:anyURI ;
+ :unqualifiedForm :derivedByRemovalFrom .
+
+:dictionary
+ a owl:ObjectProperty ;
+ rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
+ rdfs:label "dictionary" ;
+ :definition "The property used by a prov:Insertion and prov:Removal to cite the prov:Dictionary that was prov:derivedByInsertionFrom or prov:derivedByRemovalFrom another dictionary." ;
+ rdfs:subPropertyOf :entity ;
+ rdfs:domain :Insertion, :Removal ;
+ rdfs:range :Dictionary ;
+ :category "collections" ;
+ :component "collections" ;
+ :dm "http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#term-dictionary-insertion"^^xsd:anyURI ;
+ :dm "http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#term-dictionary-removal"^^xsd:anyURI ;
+ :n "http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#expression-dictionary-insertion"^^xsd:anyURI ;
+ :n "http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#expression-dictionary-removal"^^xsd:anyURI ;
+ :constraints "http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#dictionary-constraints"^^xsd:anyURI .
+
+:derivedByInsertionFrom
+ a owl:ObjectProperty ;
+ rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
+ rdfs:label "derivedByInsertionFrom" ;
+ :definition "The dictionary was derived from the other by insertion. prov:qualifiedInsertion shows details of the insertion, in particular the inserted key-entity pairs." ;
+ rdfs:subPropertyOf :wasDerivedFrom ;
+ rdfs:domain :Dictionary ;
+ rdfs:range :Dictionary ;
+ :category "collections" ;
+ :component "collections" ;
+ :dm "http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#term-dictionary-insertion"^^xsd:anyURI ;
+ :n "http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#expression-dictionary-insertion"^^xsd:anyURI ;
+ :constraints "http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#dictionary-constraints"^^xsd:anyURI .
+
+:derivedByRemovalFrom
+ a owl:ObjectProperty ;
+ rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
+ rdfs:label "derivedByRemovalFrom" ;
+ :definition "The dictionary was derived from the other by removal. prov:qualifiedRemoval shows details of the removal, in particular the removed key-entity pairs." ;
+ rdfs:subPropertyOf :wasDerivedFrom ;
+ rdfs:domain :Dictionary ;
+ rdfs:range :Dictionary ;
+ :category "collections" ;
+ :component "collections" ;
+ :dm "http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#term-dictionary-removal"^^xsd:anyURI ;
+ :n "http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#expression-dictionary-removal"^^xsd:anyURI ;
+ :constraints "http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#dictionary-constraints"^^xsd:anyURI .
+
+:insertedKeyEntityPair
+ a owl:ObjectProperty ;
+ rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
+ rdfs:label "insertedKeyEntityPair" ;
+ :definition "An object property to refer to the prov:KeyEntityPair inserted into a prov:Dictionary." ;
+ rdfs:domain :Insertion ;
+ rdfs:range :KeyEntityPair ;
+ :category "collections" ;
+ :component "collections" ;
+ :dm "http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#term-dictionary-insertion"^^xsd:anyURI ;
+ :n "http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#expression-dictionary-insertion"^^xsd:anyURI ;
+ :constraints "http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#dictionary-constraints"^^xsd:anyURI .
+
+:hadDictionaryMember
+ a owl:ObjectProperty ;
+ rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
+ rdfs:label "hadDictionaryMember" ;
+ :definition "Describes the key-entity pair that was member of a prov:Dictionary. A dictionary can have multiple members." ;
+ rdfs:domain :Dictionary ;
+ rdfs:range :KeyEntityPair ;
+ :category "collections" ;
+ :component "collections" ;
+ :dm "http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#term-dictionary-membership"^^xsd:anyURI ;
+ :n "http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#expression-dictionary-membership"^^xsd:anyURI ;
+ :constraints "http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#dictionary-constraints"^^xsd:anyURI .
+
+:pairKey
+ a owl:DatatypeProperty, owl:FunctionalProperty ;
+ rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
+ rdfs:label "pairKey" ;
+ :definition "The key of a KeyEntityPair, which is an element of a prov:Dictionary." ;
+ rdfs:domain :KeyEntityPair ;
+ rdfs:range rdfs:Literal ;
+ :category "collections" ;
+ :component "collections" ;
+ :dm "http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#term-dictionary-membership"^^xsd:anyURI ;
+ :n "http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#expression-dictionary-membership"^^xsd:anyURI ;
+ :constraints "http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#dictionary-constraints"^^xsd:anyURI .
+
+:pairEntity
+ a owl:ObjectProperty, owl:FunctionalProperty ;
+ rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
+ rdfs:label "pairKey" ;
+ :definition "The value of a KeyEntityPair." ;
+ rdfs:domain :KeyEntityPair ;
+ rdfs:range :Entity ;
+ :category "collections" ;
+ :component "collections" ;
+ :dm "http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#term-dictionary-membership"^^xsd:anyURI ;
+ :n "http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#expression-dictionary-membership"^^xsd:anyURI ;
+ :constraints "http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#dictionary-constraints"^^xsd:anyURI .
+
+:qualifiedInsertion
+ a owl:ObjectProperty ;
+ rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
+ rdfs:label "qualifiedInsertion" ;
+ :definition "The dictionary was derived from the other by insertion. prov:qualifiedInsertion shows details of the insertion, in particular the inserted key-entity pairs." ;
+ rdfs:subPropertyOf :qualifiedDerivation ;
+ rdfs:domain :Dictionary ;
+ rdfs:range :Insertion ;
+ :category "collections" ;
+ :component "collections" ;
+ :dm "http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#term-dictionary-insertion"^^xsd:anyURI ;
+ :n "http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#expression-dictionary-insertion"^^xsd:anyURI ;
+ :constraints "http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#dictionary-constraints"^^xsd:anyURI .
+
+:qualifiedRemoval
+ a owl:ObjectProperty ;
+ rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
+ rdfs:label "qualifiedRemoval" ;
+ :definition "The dictionary was derived from the other by removal. prov:qualifiedRemoval shows details of the removal, in particular the removed keys." ;
+ rdfs:subPropertyOf :qualifiedDerivation ;
+ rdfs:domain :Dictionary ;
+ rdfs:range :Removal ;
+ :category "collections" ;
+ :component "collections" ;
+ :dm "http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#term-dictionary-removal"^^xsd:anyURI ;
+ :n "http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#expression-dictionary-removal"^^xsd:anyURI ;
+ :constraints "http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#dictionary-constraints"^^xsd:anyURI .
+
+:removedKey
+ a owl:DatatypeProperty ;
+ rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
+ rdfs:label "removedKey" ;
+ :definition "The key removed in a Removal." ;
+ rdfs:domain :Removal ;
+ rdfs:range rdfs:Literal ;
+ :category "collections" ;
+ :component "collections" ;
+ :dm "http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#term-dictionary-removal"^^xsd:anyURI ;
+ :n "http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#expression-dictionary-removal"^^xsd:anyURI ;
+ :constraints "http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/#dictionary-constraints"^^xsd:anyURI .
\ No newline at end of file
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/namespace/prov-dictionary.xsd Fri Apr 26 09:27:12 2013 +0100
@@ -0,0 +1,81 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
+ targetNamespace="http://www.w3.org/ns/prov#" xmlns:prov="http://www.w3.org/ns/prov#"
+ elementFormDefault="qualified">
+
+ <xs:include schemaLocation="prov-core.xsd" />
+
+ <!-- Dictionary -->
+ <xs:complexType name="Dictionary">
+ <xs:complexContent>
+ <xs:extension base="prov:Collection">
+ </xs:extension>
+ </xs:complexContent>
+ </xs:complexType>
+
+ <xs:element name="dictionary" type="prov:Dictionary" substitutionGroup="prov:internalElement" />
+
+ <!-- Empty Dictionary -->
+ <xs:complexType name="EmptyDictionary">
+ <xs:complexContent>
+ <xs:extension base="prov:Dictionary">
+ </xs:extension>
+ </xs:complexContent>
+ </xs:complexType>
+
+ <xs:element name="emptyDictionary" type="prov:EmptyDictionary" substitutionGroup="prov:internalElement" />
+
+ <!-- Key-Entity Pair -->
+ <xs:complexType name="KeyEntityPair">
+ <xs:sequence>
+ <xs:element name="key" type="xs:anySimpleType" />
+ <xs:element name="entity" type="prov:IDRef" />
+ </xs:sequence>
+ </xs:complexType>
+
+ <!-- do we need to have this use the substitutionGroup? -->
+ <xs:element name="keyEntityPair" type="prov:KeyEntityPair" substitutionGroup="prov:internalElement"/>
+
+ <!-- Dictionary Membership -->
+ <xs:complexType name="DictionaryMembership">
+ <xs:sequence>
+ <xs:element name="dictionary" type="prov:IDRef"/>
+ <xs:element name="keyEntityPair" type="prov:KeyEntityPair" minOccurs="1" maxOccurs="unbounded"/>
+ </xs:sequence>
+ </xs:complexType>
+
+ <xs:element name="hadDictionaryMember" type="prov:DictionaryMembership" substitutionGroup="prov:internalElement"/>
+
+ <!-- Insertion -->
+ <xs:complexType name="Insertion">
+ <xs:sequence>
+ <xs:element name="newDictionary" type="prov:IDRef"/>
+ <xs:element name="oldDictionary" type="prov:IDRef"/>
+ <xs:element name="keyEntityPair" type="prov:KeyEntityPair" minOccurs="1" maxOccurs="unbounded"/>
+ <!-- prov attributes -->
+ <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
+ </xs:sequence>
+ <xs:attribute ref="prov:id"/>
+ </xs:complexType>
+
+ <xs:element name="derivedByInsertionFrom" type="prov:Insertion" substitutionGroup="prov:internalElement"/>
+
+ <!-- Removal -->
+ <xs:complexType name="Removal">
+ <xs:sequence>
+ <xs:element name="newDictionary" type="prov:IDRef"/>
+ <xs:element name="oldDictionary" type="prov:IDRef"/>
+ <xs:element name="key" type="xs:anySimpleType" minOccurs="1" maxOccurs="unbounded" />
+ <!-- prov attributes -->
+ <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
+ </xs:sequence>
+ <xs:attribute ref="prov:id"/>
+ </xs:complexType>
+
+ <xs:element name="derivedByRemovalFrom" type="prov:Removal" substitutionGroup="prov:internalElement"/>
+
+</xs:schema>
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/namespace/prov-links.xsd Fri Apr 26 09:27:12 2013 +0100
@@ -0,0 +1,18 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
+ targetNamespace="http://www.w3.org/ns/prov#" xmlns:prov="http://www.w3.org/ns/prov#"
+ elementFormDefault="qualified">
+
+ <xs:include schemaLocation="prov-core.xsd" />
+
+ <xs:complexType name="Mention">
+ <xs:sequence>
+ <xs:element name="specificEntity" type="prov:IDRef" />
+ <xs:element name="generalEntity" type="prov:IDRef" />
+ <xs:element name="bundle" type="prov:IDRef" />
+ </xs:sequence>
+ </xs:complexType>
+
+ <xs:element name="mentionOf" type="prov:Mention" substitutionGroup="prov:internalElement" />
+
+</xs:schema>
\ No newline at end of file
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/namespace/prov.xsd Fri Apr 26 09:27:12 2013 +0100
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="utf-8"?>
+<xs:schema targetNamespace="http://www.w3.org/ns/prov#"
+ xmlns:xs="http://www.w3.org/2001/XMLSchema"
+ xmlns:prov="http://www.w3.org/ns/prov#"
+ elementFormDefault="qualified"
+ attributeFormDefault="unqualified">
+
+ <xs:include schemaLocation="prov-core.xsd"/>
+ <xs:include schemaLocation="prov-dictionary.xsd"/>
+ <xs:include schemaLocation="prov-links.xsd"/>
+
+</xs:schema>
--- a/ontology/releases/REC-prov-o-20130430/Overview.html Fri Apr 26 09:26:16 2013 +0100
+++ b/ontology/releases/REC-prov-o-20130430/Overview.html Fri Apr 26 09:27:12 2013 +0100
@@ -10587,7 +10587,7 @@
-<dt id="bib-PROV-DICTIONARY">[PROV-DICTIONARY]</dt><dd>Tom De Nies; Sam Coppens; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><cite>PROV Dictionary</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/</a> </dd>
+<dt id="bib-PROV-DICTIONARY">[PROV-DICTIONARY]</dt><dd>Tom De Nies; Sam Coppens; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><cite>PROV-Dictionary: Modeling Provenance for Dictionary Data Structures</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/</a> </dd>
<dt id="bib-PROV-LINKS">[PROV-LINKS]</dt><dd>Luc Moreau; Timothy Lebo; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-links-20130430/"><cite>Linking Across Provenance Bundles</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-links-20130430/">http://www.w3.org/TR/2013/NOTE-prov-links-20130430/</a> </dd>
--- a/overview/NOTE-prov-overview-20130430/Overview.html Fri Apr 26 09:26:16 2013 +0100
+++ b/overview/NOTE-prov-overview-20130430/Overview.html Fri Apr 26 09:27:12 2013 +0100
@@ -185,7 +185,9 @@
.section dl.attrs dd, .section dl.eldef dd {
margin-bottom: 0;
}
-</style><link rel="stylesheet" href="http://www.w3.org/StyleSheets/TR/W3C-WG-NOTE"><!--[if lt IE 9]><script src='http://www.w3.org/2008/site/js/html5shiv.js'></script><![endif]--></head>
+</style><link rel="stylesheet" href="http://www.w3.org/StyleSheets/TR/W3C-WG-NOTE">
+<link rel="http://www.w3.org/ns/prov#has_provenance" href="http://www.w3.org/2011/prov/provenance/prov-overview">
+<!--[if lt IE 9]><script src='http://www.w3.org/2008/site/js/html5shiv.js'></script><![endif]--></head>
<body><div class="head">
<p>
@@ -210,7 +212,7 @@
<dt>Previous version:</dt>
- <dd><a href="http://www.w3.org/TR/2014/WD-prov-overview-20140312/">http://www.w3.org/TR/2014/WD-prov-overview-20140312/</a></dd>
+ <dd><a href="http://www.w3.org/TR/2013/WD-prov-overview-20130312/">http://www.w3.org/TR/2013/WD-prov-overview-20130312/</a></dd>
<dt>Editors:</dt>
@@ -367,10 +369,8 @@
<div style="text-align: center; ">
-<span class="figure" style="max-width: 70%; "><img alt="The Organization of PROV" src="./prov-family.png" style="max-width: 70%;">
-</span>
-<br>
- <span>Fig. <span class="figno">1</span> <span class="fig-title">The Organization of PROV</span></span>
+<span class="figure" id="fig-the-organization-of-prov"><img alt="The Organization of PROV" src="./prov-family.png" style="max-width: 70%;"></span><br>
+<span>Fig. <span class="figno">1</span> <span class="fig-title">The Organization of PROV</span></span>
</div>
</section>
@@ -532,7 +532,7 @@
</section><section id="references" class="appendix"><!--OddPage--><h2><span class="secno">B. </span>References</h2><section id="informative-references"><h3><span class="secno">B.1 </span>Informative references</h3><dl class="bibliography"><dt id="bib-PROV-AQ">[PROV-AQ]</dt><dd>Graham Klyne; Paul Groth; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/"><cite>Provenance Access and Query</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/">http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/</a>
</dd><dt id="bib-PROV-CONSTRAINTS">[PROV-CONSTRAINTS]</dt><dd>James Cheney; Paolo Missier; Luc Moreau; eds. <a href="http://www.w3.org/TR/2013/REC-prov-constraints-20130430/"><cite>Constraints of the PROV Data Model</cite></a>. 30 April 2013, W3C Recommendation. URL: <a href="http://www.w3.org/TR/2013/REC-prov-constraints-20130430/">http://www.w3.org/TR/2013/REC-prov-constraints-20130430/</a>
</dd><dt id="bib-PROV-DC">[PROV-DC]</dt><dd>Daniel Garijo; Kai Eckert; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/"><cite>Dublin Core to PROV Mapping</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/">http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/</a>
-</dd><dt id="bib-PROV-DICTIONARY">[PROV-DICTIONARY]</dt><dd>Tom De Nies; Sam Coppens; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><cite>PROV Dictionary</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/</a>
+</dd><dt id="bib-PROV-DICTIONARY">[PROV-DICTIONARY]</dt><dd>Tom De Nies; Sam Coppens; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><cite>PROV Dictionary: Modeling Provenance for Dictionary Data Structures</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/</a>
</dd><dt id="bib-PROV-DM">[PROV-DM]</dt><dd>Luc Moreau; Paolo Missier; eds. <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/"><cite>PROV-DM: The PROV Data Model</cite></a>. 30 April 2013, W3C Recommendation. URL: <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/">http://www.w3.org/TR/2013/REC-prov-dm-20130430/</a>
</dd><dt id="bib-PROV-IMPLEMENTATIONS">[PROV-IMPLEMENTATIONS]</dt><dd>Trung Dong Hynh, Paul Groth, Stephan Zednik; eds . <a href="http://www.w3.org/TR/2013/NOTE-prov-implementations-20130430/">PROV Implementation Reprot.</a> 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-implementations-20130430/">http://www.w3.org/TR/2013/NOTE-prov-implementations-20130430/'.</a>
</dd><dt id="bib-PROV-LINKS">[PROV-LINKS]</dt><dd>Luc Moreau; Timothy Lebo; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-links-20130430/"><cite>Linking Across Provenance Bundles</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-links-20130430/">http://www.w3.org/TR/2013/NOTE-prov-links-20130430/</a>
--- a/overview/prov-overview.html Fri Apr 26 09:26:16 2013 +0100
+++ b/overview/prov-overview.html Fri Apr 26 09:27:12 2013 +0100
@@ -323,7 +323,7 @@
// if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
// and its maturity status
- previousPublishDate: "2014-03-12",
+ previousPublishDate: "2013-03-12",
previousMaturity: "WD",
// if there a publicly available Editor's Draft, this is the link
@@ -449,9 +449,8 @@
<div style="text-align: center; ">
- <span class="figure" style="max-width: 70%; "><img alt="The Organization of PROV" src="./prov-family.png" style="max-width: 70%;">
-<br>
- </span>
+<span class="figure" style="max-width: 70%; "><img alt="The Organization of PROV" src="./prov-family.png" style="max-width: 70%;">
+</span>
</div>
</section>
--- a/paq/prov-aq.html Fri Apr 26 09:26:16 2013 +0100
+++ b/paq/prov-aq.html Fri Apr 26 09:27:12 2013 +0100
@@ -117,7 +117,7 @@
// subtitle : "an excellent document",
// if you wish the publication date to be other than today, set this
- publishDate: "2013-03-30",
+ publishDate: "2013-04-30",
// if the specification's copyright date is a range of years, specify
// the start date here:
@@ -125,7 +125,7 @@
// if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
// and its maturity status
- previousPublishDate: "2012-06-19",
+ previousPublishDate: "2013-03-12",
previousMaturity: "WD",
// if there a publicly available Editor's Draft, this is the link
@@ -146,7 +146,7 @@
{ name: "Graham Klyne", url: "",
company: "University of Oxford", companyURL: "http://www.ox.ac.uk/" },
- { name: "Paul Groth", url: "",
+ { name: "Paul Groth", url: "http://www.few.vu.nl/~pgroth/",
company: "VU University Amsterdam", companyURL: "http://www.vu.nl/" },
],
@@ -1315,11 +1315,9 @@
<section>
<h2>Changes since 20130312 publication</h2>
- <!--
hg log -r tip:b665bc9447ce \
- -template "<dt>{date|isodate} {node|short} {author}</dt><dd>{desc}</dd>\n" \
prov-aq.html
- - ->
<dl>
<dt>2013-04-12 12:07 +0100 dae5268c75c0 Graham Klyne</dt><dd>Add some text clarifying that pingback provenance may be about new entities; result of dereferencing 'target-URI' not specified</dd>
<dt>2013-04-12 11:32 +0100 a89cc91fa022 Graham Klyne</dt><dd>Remove 'at risk' note from section on pingback</dd>
@@ -1345,11 +1343,11 @@
<section>
<h2>Changes since 20120619 publication</h2>
- <!- -
+
hg log -r tip:d0af0446868d \
- -template "<dt>{date|isodate} {node|short} {author}</dt><dd>{desc}</dd>\n" \
prov-aq.html
- - ->
+
<dl>
<dt>2013-02-27 16:23 +0000 35385cbbfb9f Graham Klyne</dt><dd>Further refinements and bug fixes in the forward provenance section</dd>
<dt>2013-02-27 15:33 +0000 2dfd7fac85c9 Graham Klyne</dt><dd>Merge</dd>
--- a/paq/prov-aq.ttl Fri Apr 26 09:26:16 2013 +0100
+++ b/paq/prov-aq.ttl Fri Apr 26 09:27:12 2013 +0100
@@ -4,6 +4,96 @@
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
+
+
+<http://www.w3.org/ns/prov-aq#>
+ a owl:Ontology ;
+ rdfs:comment "0.2"^^xsd:string, """This document is published by the Provenance Working Group (http://www.w3.org/2011/prov/wiki/Main_Page).
+
+If you wish to make comments regarding this document, please send them to public-prov-comments@w3.org (subscribe public-prov-comments-request@w3.org, archives http://lists.w3.org/Archives/Public/public-prov-comments/). All feedback is welcome."""@en ;
+ rdfs:label "PROV Access and Query Ontology"@en ;
+ rdfs:seeAlso <http://www.w3.org/TR/prov#>, <http://www.w3.org/TR/prov-aq/> ;
+ owl:versionIRI <http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/> .
+
+
+##prov-aq definitions
+
+
+:ServiceDescription
+ a owl:Class ;
+ rdfs:comment "Type for a generic provenance query service. Mainly for use in RDF provenance query service descriptions, to facilitate discovery in linked data environments." ;
+ rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
+ rdfs:label "ServiceDescription" ;
+ rdfs:subClassOf :SoftwareAgent ;
+ :aq "http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/#provenance-query-service-discovery"^^xsd:anyURI ;
+ :category "access-and-query" .
+
+:DirectQueryService
+ a owl:Class ;
+ rdfs:comment "Type for a generic provenance query service. Mainly for use in RDF provenance query service descriptions, to facilitate discovery in linked data environments." ;
+ rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
+ rdfs:label "ProvenanceService" ;
+ rdfs:subClassOf :SoftwareAgent ;
+ :aq "http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/#provenance-query-service-discovery"^^xsd:anyURI ;
+ :category "access-and-query" .
+
+:has_anchor
+ a owl:ObjectProperty ;
+ rdfs:comment "Indicates anchor URI for a potentially dynamic resource instance."@en ;
+ rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
+ rdfs:label "has_anchor" ;
+ :aq "http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/#resource-represented-as-html"^^xsd:anyURI ;
+ :category "access-and-query" ;
+ :inverse "anchorOf" .
+
+:has_provenance
+ a owl:ObjectProperty ;
+ rdfs:comment "Indicates a provenance-URI for a resource; the resource identified by this property presents a provenance record about its subject or anchor resource."@en ;
+ rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
+ rdfs:label "has_provenance" ;
+ :aq "http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/#resource-represented-as-html"^^xsd:anyURI ;
+ :category "access-and-query" ;
+ :inverse "provenanceOf" .
+
+:has_query_service
+ a owl:ObjectProperty ;
+ rdfs:comment "Indicates a provenance query service that can access provenance related to its subject or anchor resource."@en ;
+ rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
+ rdfs:label "hasProvenanceService" ;
+ :aq "http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/"^^xsd:anyURI ;
+ :category "access-and-query" ;
+ :inverse "provenanceQueryServiceOf" .
+
+:describesService
+ a owl:ObjectProperty ;
+ rdfs:comment "relates a generic provenance query service resource (type prov:ServiceDescription) to a specific query service description (e.g. a prov:DirectQueryService or a sd:Service)."@en ;
+ rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
+ rdfs:label "describesService" ;
+ :aq "http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/rovenance-query-service-description"^^xsd:anyURI ;
+ :category "access-and-query" ;
+ :inverse "serviceDescribedBy" .
+
+
+:provenanceUriTemplate
+ a owl:DatatypeProperty ;
+ rdfs:comment "Relates a provenance service to a URI template string for constructing provenance-URIs."@en ;
+ rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
+ rdfs:label "provenanceUriTemplate" ;
+ :aq "http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/"^^xsd:anyURI ;
+ :category "access-and-query" .
+
+:pingback
+ a owl:ObjectProperty ;
+ rdfs:comment "Relates a resource to a provenance pingback service that may receive additional provenance links about the resource."@en ;
+ rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
+ rdfs:label "provenance pingback" ;
+ :aq "http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/#provenance-pingback"^^xsd:anyURI ;
+ :category "access-and-query" .
+
+
+
+
+## Definitions from other ontologies
rdfs:comment
a owl:AnnotationProperty ;
rdfs:comment ""@en ;
@@ -33,14 +123,6 @@
<http://www.w3.org/ns/prov#>
a owl:Ontology .
-:ProvenanceService
- a owl:Class ;
- rdfs:comment "Class for a service described by a provenance service description." ;
- rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
- rdfs:label "ProvenanceService" ;
- rdfs:subClassOf :SoftwareAgent ;
- :aq "http://dvcs.w3.org/hg/prov/raw-file/tip/paq/prov-aq.html#todo"^^xsd:anyURI ;
- :category "access-and-query" .
:SoftwareAgent
a owl:Class ;
@@ -95,7 +177,7 @@
rdfs:comment "When the prov-o term does not have a definition drawn from prov-dm, and the prov-o editor provides one."@en ;
rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
rdfs:subPropertyOf :definition .
-
+
:hadUsage
a owl:ObjectProperty ;
rdfs:comment "The _optional_ Usage involved in an Entity's Derivation."@en ;
@@ -106,33 +188,6 @@
:inverse "wasUsedInDerivation" ;
:sharesDefinitionWith :Usage .
-:hasAnchor
- a owl:ObjectProperty ;
- rdfs:comment "Indicates anchor URI for a potentially dynamic resource instance."@en ;
- rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
- rdfs:label "hadAnchor" ;
- :aq "http://dvcs.w3.org/hg/prov/raw-file/tip/paq/prov-aq.html#todo"^^xsd:anyURI ;
- :category "access-and-query" ;
- :inverse "anchorOf" .
-
-:hasProvenance
- a owl:ObjectProperty ;
- rdfs:comment "Relates a resource to its provenance."@en ;
- rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
- rdfs:label "hasProvenance" ;
- :aq "http://dvcs.w3.org/hg/prov/raw-file/tip/paq/prov-aq.html#todo"^^xsd:anyURI ;
- :category "access-and-query" ;
- :inverse "provenanceOf" .
-
-:hasProvenanceService
- a owl:ObjectProperty ;
- rdfs:comment "Relates a resource to a provenance service."@en ;
- rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
- rdfs:label "hasProvenanceService" ;
- :aq "http://dvcs.w3.org/hg/prov/raw-file/tip/paq/prov-aq.html#todo"^^xsd:anyURI ;
- :category "access-and-query" ;
- :inverse "provenanceAnchorOf" .
-
:inverse
a owl:AnnotationProperty ;
rdfs:comment "PROV-O does not define all property inverses. The directionalities defined in PROV-O should be given preference over those not defined. However, if users wish to name the inverse of a PROV-O property, the local name given by prov:inverse should be used."@en ;
@@ -145,14 +200,6 @@
rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
rdfs:subPropertyOf rdfs:seeAlso .
-:provenanceUriTemplate
- a owl:DatatypeProperty ;
- rdfs:comment "Relates a provenance service to a URI template string for constructing provenance-URIs."@en ;
- rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
- rdfs:label "provenanceUriTemplate" ;
- :aq "http://dvcs.w3.org/hg/prov/raw-file/tip/paq/prov-aq.html#todo"^^xsd:anyURI ;
- :category "access-and-query" .
-
:qualifiedForm
a owl:AnnotationProperty ;
rdfs:comment """This annotation property links a subproperty of prov:wasInfluencedBy with the subclass of prov:Influence and the qualifying property that are used to qualify it.
@@ -205,12 +252,4 @@
rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
rdfs:subPropertyOf rdfs:seeAlso .
-<http://www.w3.org/ns/prov-aq#>
- a owl:Ontology ;
- rdfs:comment "0.2"^^xsd:string, """This document is published by the Provenance Working Group (http://www.w3.org/2011/prov/wiki/Main_Page).
-If you wish to make comments regarding this document, please send them to public-prov-comments@w3.org (subscribe public-prov-comments-request@w3.org, archives http://lists.w3.org/Archives/Public/public-prov-comments/). All feedback is welcome."""@en ;
- rdfs:label "PROV Access and Query Ontology"@en ;
- rdfs:seeAlso <http://www.w3.org/TR/prov#>, <http://www.w3.org/TR/prov-aq/> ;
- owl:versionIRI <http://www.w3.org/TR/2012/WD-prov-o-2013MMDD> .
-
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/paq/releases/NOTE-prov-aq-20130430/Overview.html Fri Apr 26 09:27:12 2013 +0100
@@ -0,0 +1,1539 @@
+<!DOCTYPE html>
+<html lang="en" dir="ltr">
+<head>
+ <title>PROV-AQ: Provenance Access and Query</title>
+ <style>/* --- EXAMPLES --- */
+div.example-title {
+ min-width: 7.5em;
+ color: #b9ab2d;
+}
+div.example-title span {
+ text-transform: uppercase;
+}
+aside.example, div.example, div.illegal-example {
+ padding: 0.5em;
+ margin: 1em 0;
+ position: relative;
+ clear: both;
+}
+div.illegal-example { color: red }
+div.illegal-example p { color: black }
+aside.example, div.example {
+ padding: .5em;
+ border-left-width: .5em;
+ border-left-style: solid;
+ border-color: #e0cb52;
+ background: #fcfaee;
+}
+
+aside.example div.example {
+ border-left-width: .1em;
+ border-color: #999;
+ background: #fff;
+}
+aside.example div.example div.example-title {
+ color: #999;
+}
+</style><style>/* --- ISSUES/NOTES --- */
+div.issue-title, div.note-title {
+ padding-right: 1em;
+ min-width: 7.5em;
+ color: #b9ab2d;
+}
+div.issue-title { color: #e05252; }
+div.note-title { color: #2b2; }
+div.issue-title span, div.note-title span {
+ text-transform: uppercase;
+}
+div.note, div.issue {
+ margin-top: 1em;
+ margin-bottom: 1em;
+}
+.note > p:first-child, .issue > p:first-child { margin-top: 0 }
+.issue, .note {
+ padding: .5em;
+ border-left-width: .5em;
+ border-left-style: solid;
+}
+div.issue, div.note {
+ padding: 1em 1.2em 0.5em;
+ margin: 1em 0;
+ position: relative;
+ clear: both;
+}
+span.note, span.issue { padding: .1em .5em .15em; }
+
+.issue {
+ border-color: #e05252;
+ background: #fbe9e9;
+}
+.note {
+ border-color: #52e052;
+ background: #e9fbe9;
+}
+
+
+</style><link rel="stylesheet" type="text/css" href="css/prov-aq.css">
+ <link rel="http://www.w3.org/ns/prov#has_provenance" href="http://www.w3.org/2011/prov/provenance/prov-aq">
+ <meta http-equiv="Content-Type" content="text/html;charset=utf-8">
+<!-- Use common W3C-hosted version of ReSpec.js:
+-->
+
+<!--
+ <script src="http://dev.w3.org/2009/dap/ReSpec.js/js/respec.js" class="remove"></script>
+
+ Use local version of ReSpec.js for debugging:
+ <script src="js/respec.js" class="remove"></script>
+ <script src="file:///usr/workspace/w3c-provenance/prov/paq/js/respec.js" class="remove"></script>
+-->
+ <!-- Include bibliography file defined for PROV-DM: -->
+
+
+
+ <style>/*****************************************************************
+ * ReSpec 3 CSS
+ * Robin Berjon - http://berjon.com/
+ *****************************************************************/
+
+/* --- INLINES --- */
+em.rfc2119 {
+ text-transform: lowercase;
+ font-variant: small-caps;
+ font-style: normal;
+ color: #900;
+}
+
+h1 acronym, h2 acronym, h3 acronym, h4 acronym, h5 acronym, h6 acronym, a acronym,
+h1 abbr, h2 abbr, h3 abbr, h4 abbr, h5 abbr, h6 abbr, a abbr {
+ border: none;
+}
+
+dfn {
+ font-weight: bold;
+}
+
+a.internalDFN {
+ color: inherit;
+ border-bottom: 1px solid #99c;
+ text-decoration: none;
+}
+
+a.externalDFN {
+ color: inherit;
+ border-bottom: 1px dotted #ccc;
+ text-decoration: none;
+}
+
+a.bibref {
+ text-decoration: none;
+}
+
+cite .bibref {
+ font-style: normal;
+}
+
+code {
+ color: #ff4500;
+}
+
+/* --- TOC --- */
+.toc a, .tof a {
+ text-decoration: none;
+}
+
+a .secno, a .figno {
+ color: #000;
+}
+
+ul.tof, ol.tof {
+ list-style: none outside none;
+}
+
+.caption {
+ margin-top: 0.5em;
+ font-style: italic;
+}
+
+/* --- TABLE --- */
+table.simple {
+ border-spacing: 0;
+ border-collapse: collapse;
+ border-bottom: 3px solid #005a9c;
+}
+
+.simple th {
+ background: #005a9c;
+ color: #fff;
+ padding: 3px 5px;
+ text-align: left;
+}
+
+.simple th[scope="row"] {
+ background: inherit;
+ color: inherit;
+ border-top: 1px solid #ddd;
+}
+
+.simple td {
+ padding: 3px 10px;
+ border-top: 1px solid #ddd;
+}
+
+.simple tr:nth-child(even) {
+ background: #f0f6ff;
+}
+
+/* --- DL --- */
+.section dd > p:first-child {
+ margin-top: 0;
+}
+
+.section dd > p:last-child {
+ margin-bottom: 0;
+}
+
+.section dd {
+ margin-bottom: 1em;
+}
+
+.section dl.attrs dd, .section dl.eldef dd {
+ margin-bottom: 0;
+}
+</style><link rel="stylesheet" href="http://www.w3.org/StyleSheets/TR/W3C-WG-NOTE"><!--[if lt IE 9]><script src='http://www.w3.org/2008/site/js/html5shiv.js'></script><![endif]--></head>
+ <body><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">PROV-AQ: Provenance Access and Query</h1>
+
+ <h2 id="w3c-working-group-note-30-april-2013"><abbr title="World Wide Web Consortium">W3C</abbr> Working Group Note 30 April 2013</h2>
+ <dl>
+
+ <dt>This version:</dt>
+ <dd><a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/">http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/</a></dd>
+ <dt>Latest published version:</dt>
+ <dd><a href="http://www.w3.org/TR/prov-aq/">http://www.w3.org/TR/prov-aq/</a></dd>
+
+
+
+
+
+
+ <dt>Previous version:</dt>
+ <dd><a href="http://www.w3.org/TR/2013/WD-prov-aq-20130312/">http://www.w3.org/TR/2013/WD-prov-aq-20130312/</a> <a href="./diff.html">(color-coded diff)</a></dd>
+
+
+ <dt>Editors:</dt>
+ <dd><span>Graham Klyne</span>, <a href="http://www.ox.ac.uk/">University of Oxford</a></dd>
+<dd><a href="http://www.few.vu.nl/~pgroth/">Paul Groth</a>, <a href="http://www.vu.nl/">VU University Amsterdam</a></dd>
+
+
+ <dt>Authors:</dt>
+ <dd><a href="http://www.ecs.soton.ac.uk/~lavm/">Luc Moreau</a>, University of Southampton</dd>
+<dd><a href="http://olafhartig.de/">Olaf Hartig</a>, Invited Expert</dd>
+<dd><span>Yogesh Simmhan</span>, Invited Expert</dd>
+<dd><a href="http://www.rpi.edu/research/ccni/">James Myers</a>, Rensselaer Polytechnic Institute</dd>
+<dd><a href="http://tw.rpi.edu/web/person/TimLebo">Timothy Lebo</a>, Rensselaer Polytechnic Institute</dd>
+<dd><a href="http://semanticweb.org/wiki/Khalid_Belhajjame">Khalid Belhajjame</a>, <a href="http://www.cs.manchester.ac.uk/">University of Manchester</a></dd>
+<dd><a href="http://www.inf.kcl.ac.uk/staff/simonm/">Simon Miles</a>, Invited Expert</dd>
+<dd><a href="http://soiland-reyes.com/stian/">Stian Soiland-Reyes</a>, <a href="http://www.cs.manchester.ac.uk/">University of Manchester</a></dd>
+
+
+ </dl>
+
+
+
+
+
+ <p class="copyright">
+ <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> ©
+ 2013
+
+ <a href="http://www.w3.org/"><abbr title="World Wide Web Consortium">W3C</abbr></a><sup>®</sup>
+ (<a href="http://www.csail.mit.edu/"><abbr title="Massachusetts Institute of Technology">MIT</abbr></a>,
+ <a href="http://www.ercim.eu/"><abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr></a>,
+ <a href="http://www.keio.ac.jp/">Keio</a>, <a href="http://ev.buaa.edu.cn/">Beihang</a>), All Rights Reserved.
+ <abbr title="World Wide Web Consortium">W3C</abbr> <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>,
+ <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and
+ <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.
+ </p>
+
+
+ <hr>
+</div>
+
+
+ <section id="abstract" class="introductory"><h2>Abstract</h2>
+This document specifies how to use standard Web protocols,
+including HTTP, to obtain information about the provenance of
+resources on the Web. We describe both simple access mechanisms for
+locating provenance records associated with web pages or resources, and
+provenance query services for more complex deployments. This is
+part of the larger <abbr title="World Wide Web Consortium">W3C</abbr> PROV provenance family of documents.
+
+<p>The <a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/">PROV Document Overview</a> describes the overall state of PROV, and should be read before other PROV documents.</p>
+
+ </section><section id="sotd" class="introductory"><h2>Status of This Document</h2>
+
+
+
+ <p>
+ <em>This section describes the status of this document at the time of its publication. Other
+ documents may supersede this document. A list of current <abbr title="World Wide Web Consortium">W3C</abbr> publications and the latest revision
+ of this technical report can be found in the <a href="http://www.w3.org/TR/"><abbr title="World Wide Web Consortium">W3C</abbr> technical reports
+ index</a> at http://www.w3.org/TR/.</em>
+ </p>
+
+<h4 id="prov-family-of-documents">PROV Family of Documents</h4>
+This document is part of the PROV family of documents, a set of documents defining various aspects that are necessary to achieve the vision of inter-operable
+interchange of provenance information in heterogeneous environments such as the Web. These documents are listed below. Please consult the [<cite><a class="bibref" href="#bib-PROV-OVERVIEW">PROV-OVERVIEW</a></cite>] for a guide to reading these documents.
+<ul>
+<li> <a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/">PROV-OVERVIEW</a> (Note), an overview of the PROV family of documents [<cite><a class="bibref" href="#bib-PROV-OVERVIEW">PROV-OVERVIEW</a></cite>];</li>
+<li> <a href="http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/">PROV-PRIMER</a> (Note), a primer for the PROV data model [<cite><a class="bibref" href="#bib-PROV-PRIMER">PROV-PRIMER</a></cite>];</li>
+<li> <a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/">PROV-O</a> (Recommendation), the PROV ontology, an OWL2 ontology allowing the mapping of the PROV data model to RDF [<cite><a class="bibref" href="#bib-PROV-O">PROV-O</a></cite>];</li>
+<li> <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/">PROV-DM</a> (Recommendation), the PROV data model for provenance [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>];</li>
+<li> <a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/">PROV-N</a> (Recommendation), a notation for provenance aimed at human consumption [<cite><a class="bibref" href="#bib-PROV-N">PROV-N</a></cite>];</li>
+<li> <a href="http://www.w3.org/TR/2013/REC-prov-constraints-20130430/">PROV-CONSTRAINTS</a> (Recommendation), a set of constraints applying to the PROV data model [<cite><a class="bibref" href="#bib-PROV-CONSTRAINTS">PROV-CONSTRAINTS</a></cite>];</li>
+<li> <a href="http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/">PROV-XML</a> (Note), an XML schema for the PROV data model [<cite><a class="bibref" href="#bib-PROV-XML">PROV-XML</a></cite>];</li>
+<li> <a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/">PROV-AQ</a> (Note), mechanisms for accessing and querying provenance (this document); </li>
+<li> <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/">PROV-DICTIONARY</a> (Note) introduces a specific type of collection, consisting of key-entity pairs [<cite><a class="bibref" href="#bib-PROV-DICTIONARY">PROV-DICTIONARY</a></cite>];</li>
+<li> <a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/">PROV-DC</a> (Note) provides a mapping between PROV-O and Dublin Core Terms [<cite><a class="bibref" href="#bib-PROV-DC">PROV-DC</a></cite>];</li>
+<li> <a href="http://www.w3.org/TR/2013/NOTE-prov-sem-20130430/">PROV-SEM</a> (Note), a declarative specification in terms of first-order logic of the PROV data model [<cite><a class="bibref" href="#bib-PROV-SEM">PROV-SEM</a></cite>];</li>
+<li> <a href="http://www.w3.org/TR/2013/NOTE-prov-links-20130430/">PROV-LINKS</a> (Note) introduces a mechanism to link across bundles [<cite><a class="bibref" href="#bib-PROV-LINKS">PROV-LINKS</a></cite>].</li>
+</ul>
+
+<h4 id="implementations-encouraged">Implementations Encouraged</h4>
+<p>
+The Provenance Working Group encourages implementation of the material defined in this document.
+ Although work on this document by the Provenance Working Group is complete,
+errors may be recorded in the <a href="http://www.w3.org/2011/prov/errata.html">errata</a> or and these may be addressed in future revisions.
+</p>
+
+<h4 id="please-send-comments">Please Send Comments</h4>
+
+
+ <p>
+ This document was published by the <a href="http://www.w3.org/2011/prov">Provenance Working Group</a> as a Working Group Note.
+
+
+ If you wish to make comments regarding this document, please send them to
+ <a href="mailto:public-prov-comments@w3.org">public-prov-comments@w3.org</a>
+ (<a href="mailto:public-prov-comments-request@w3.org?subject=subscribe">subscribe</a>,
+ <a href="http://lists.w3.org/Archives/Public/public-prov-comments/">archives</a>).
+
+
+
+
+ All comments are welcome.
+
+
+ </p><p>
+ Publication as a Working Group Note does not imply endorsement by the <abbr title="World Wide Web Consortium">W3C</abbr> Membership.
+ This is a draft document and may be updated, replaced or obsoleted by other documents at
+ any time. It is inappropriate to cite this document as other than work in progress.
+ </p>
+
+
+ <p>
+
+ This document was produced by a group operating under the
+ <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 <abbr title="World Wide Web Consortium">W3C</abbr> Patent Policy</a>.
+
+
+
+
+ <abbr title="World Wide Web Consortium">W3C</abbr> maintains a <a href="http://www.w3.org/2004/01/pp-impl/46974/status" rel="disclosure">public list of any patent disclosures</a>
+
+ made in connection with the deliverables of the group; that page also includes instructions for
+ disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains
+ <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential Claim(s)</a> must disclose the
+ information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section
+ 6 of the <abbr title="World Wide Web Consortium">W3C</abbr> Patent Policy</a>.
+
+
+ </p>
+
+
+
+
+</section><section id="toc"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a href="#introduction" class="tocxref"><span class="secno">1. </span>Introduction</a><ul class="toc"><li class="tocline"><a href="#concepts" class="tocxref"><span class="secno">1.1 </span>Concepts</a></li><li class="tocline"><a href="#provenance-and-resources" class="tocxref"><span class="secno">1.2 </span>Provenance and resources</a></li><li class="tocline"><a href="#interpreting-provenance-records" class="tocxref"><span class="secno">1.3 </span>Interpreting provenance records</a></li><li class="tocline"><a href="#uri-types-and-dereferencing" class="tocxref"><span class="secno">1.4 </span>URI types and dereferencing</a></li></ul></li><li class="tocline"><a href="#accessing-provenance-records" class="tocxref"><span class="secno">2. </span>Accessing provenance records</a></li><li class="tocline"><a href="#locating-provenance-records" class="tocxref"><span class="secno">3. </span>Locating provenance records</a><ul class="toc"><li class="tocline"><a href="#resource-accessed-by-http" class="tocxref"><span class="secno">3.1 </span>Resource accessed by HTTP</a><ul class="toc"><li class="tocline"><a href="#specifying-provenance-query-services" class="tocxref"><span class="secno">3.1.1 </span>Specifying Provenance Query Services</a></li><li class="tocline"><a href="#content-negotiation-redirection-and-link-headers" class="tocxref"><span class="secno">3.1.2 </span>Content negotiation, redirection and Link: headers</a></li></ul></li><li class="tocline"><a href="#resource-represented-as-html" class="tocxref"><span class="secno">3.2 </span>Resource represented as HTML</a><ul class="toc"><li class="tocline"><a href="#specifying-provenance-query-services-1" class="tocxref"><span class="secno">3.2.1 </span>Specifying Provenance Query Services</a></li></ul></li><li class="tocline"><a href="#resource-represented-as-rdf" class="tocxref"><span class="secno">3.3 </span>Resource represented as RDF</a></li></ul></li><li class="tocline"><a href="#provenance-query-services" class="tocxref"><span class="secno">4. </span>Provenance query services</a><ul class="toc"><li class="tocline"><a href="#provenance-query-service-description" class="tocxref"><span class="secno">4.1 </span>Provenance query service description</a><ul class="toc"><li class="tocline"><a href="#direct-http-query-service-description" class="tocxref"><span class="secno">4.1.1 </span>Direct HTTP query service description</a></li><li class="tocline"><a href="#sparql-query-service-description" class="tocxref"><span class="secno">4.1.2 </span>SPARQL query service description</a></li><li class="tocline"><a href="#service-description-example" class="tocxref"><span class="secno">4.1.3 </span>Service description example</a></li></ul></li><li class="tocline"><a href="#direct-http-query-service-invocation" class="tocxref"><span class="secno">4.2 </span>Direct HTTP query service invocation</a></li><li class="tocline"><a href="#provenance-query-service-discovery" class="tocxref"><span class="secno">4.3 </span>Provenance query service discovery</a></li></ul></li><li class="tocline"><a href="#provenance-pingback" class="tocxref"><span class="secno">5. </span>Provenance pingback</a></li><li class="tocline"><a href="#security-considerations" class="tocxref"><span class="secno">6. </span>Security considerations</a></li><li class="tocline"><a href="#acknowledgements" class="tocxref"><span class="secno">A. </span>Acknowledgements</a></li><li class="tocline"><a href="#terms-added-to-prov-namespace" class="tocxref"><span class="secno">B. </span>Terms added to prov: namespace</a></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">C. </span>References</a><ul class="toc"><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">C.1 </span>Informative references</a></li></ul></li></ul></section>
+
+
+
+
+<!-- == Sect 1 =================================================================================== -->
+
+ <section id="introduction">
+ <!--OddPage--><h2><span class="secno">1. </span>Introduction</h2>
+ <p>
+ The Provenance Data Model [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>], Provenance Ontology [<cite><a class="bibref" href="#bib-PROV-O">PROV-O</a></cite>] and related specifications define how to represent provenance on the World Wide Web (see the [<cite><a class="bibref" href="#bib-PROV-OVERVIEW">PROV-OVERVIEW</a></cite>]).
+ </p>
+ <p>
+ This note describes how standard web protocols may be used to locate, retrieve and query provenance records:
+ </p>
+ <ul>
+ <li>
+ Simple mechanisms for retrieving and discovering provenance records are described in <a href="#accessing-provenance-records" class="sectionRef sec-ref">section 2. Accessing provenance records</a> and <a href="#locating-provenance-records" class="sectionRef sec-ref">section 3. Locating provenance records</a> .
+ </li>
+ <li>
+ Provenance query mechanisms that may be used for more demanding deployments are described in <a href="#provenance-query-services" class="sectionRef sec-ref">section 4. Provenance query services</a>.
+ </li>
+ <li>
+ A simple "ping-back" mechanism allowing for discovery of additional provenance that would otherwise be unknown to the publisher of the resource (e.g. provenance about future entities that are based upon or influenced by a resource) is described in <a href="#provenance-pingback" class="sectionRef sec-ref">section 5. Provenance pingback</a>.
+ </li>
+ </ul>
+ <p>
+ Most mechanisms described in this note are independent of the provenance format used, and may be used to access provenance in any available format. For interoperable provenance publication, use of PROV represented in any of its specified formats is recommended. Where alternative formats are available, selection may be made by HTTP content negotiation [<cite><a class="bibref" href="#bib-HTTP11">HTTP11</a></cite>].
+ </p>
+ <p>
+ For ease of reference, the main body of this document contains some links to external web pages. Such links are distinguished from internal references thus: <a href="http://www.w3.org/2011/prov/wiki/Main_Page" class="externalRef"><abbr title="World Wide Web Consortium">W3C</abbr> Provenance Working Group</a>.
+ </p>
+ <p>
+ This document is a <abbr title="World Wide Web Consortium">W3C</abbr> Note, not a formal <abbr title="World Wide Web Consortium">W3C</abbr> Specification. However, to clarify the description of intended behaviours, it does use the key words <em class="rfc2119" title="MUST">MUST</em>, <em class="rfc2119" title="MUST NOT">MUST NOT</em>, <em class="rfc2119" title="REQUIRED">REQUIRED</em>, <em class="rfc2119" title="SHOULD">SHOULD</em>, <em class="rfc2119" title="SHOULD NOT">SHOULD NOT</em>, <em class="rfc2119" title="RECOMMENDED">RECOMMENDED</em>, <em class="rfc2119" title="MAY">MAY</em> and <em class="rfc2119" title="OPTIONAL">OPTIONAL</em> as described in [<cite><a class="bibref" href="#bib-RFC2119">RFC2119</a></cite>].
+ </p>
+
+ <section id="concepts">
+ <h3><span class="secno">1.1 </span>Concepts</h3>
+ <p>
+ This document uses the term URI for web resource identifiers, as this is the term used in many of the currently ratified specifications that this document builds upon. In many situations, a URI may also be an IRI [<cite><a class="bibref" href="#bib-RFC3987">RFC3987</a></cite>], which is a generalisation of a URI allowing a wider range of Unicode characters. Every absolute URI is an IRI, but not every IRI is an URI. When IRIs are used in situations that require a URI, they must first be converted according to the mapping defined in section 3.1 of [<cite><a class="bibref" href="#bib-RFC3987">RFC3987</a></cite>]. A notable example is retrieval over the HTTP protocol. The mapping involves UTF-8 encoding of non-ASCII characters, %-encoding of octets not allowed in URIs, and Punycode-encoding of domain names.
+ </p>
+ <p>In defining the specification below, we make use of the following concepts.</p>
+ <dl>
+ <dt><a href="#dfn-resource"><dfn id="dfn-resource">Resource</dfn></a></dt>
+ <dd>a resource in the general sense of "whatever might be identified by a URI", as described by the Architecture of the World Wide Web [<cite><a class="bibref" href="#bib-WEBARCH">WEBARCH</a></cite>], <a href="http://www.w3.org/TR/webarch/#id-resources" class="externalRef">section 2.2</a>. A resource may be associated with multiple instances or views (<a class="internalDFN" href="#dfn-constrained-resource">constrained resource</a>s) with differing provenance.
+ </dd>
+ <dt><a href="#dfn-constrained-resource"><dfn id="dfn-constrained-resource">Constrained resource</dfn></a></dt>
+ <dd>a specialization (e.g. an aspect, version or instance) of a <a class="internalDFN" href="#dfn-resource">resource</a>, about which one may wish to present <a class="internalDFN" href="#dfn-provenance-record">provenance record</a>s. For example, a weather report for a given date may be an aspect of a resource that is maintained as the current weather report. A constrained resource is itself a <a class="internalDFN" href="#dfn-resource">resource</a>, and may have its own URI different from that of the original. See also <a class="sectionRef sec-ref" href="#provenance-and-resources">section 1.2 Provenance and resources</a>, [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>] <a href="http://www.w3.org/TR/prov-dm/#term-specialization" class="externalRef">section 5.5.1</a>, and [<cite><a class="bibref" href="#bib-WEBARCH">WEBARCH</a></cite>] <a href="http://www.w3.org/TR/webarch/#representation-reuse" class="externalRef">section 2.3.2</a>.
+ </dd>
+ <dt><a href="#dfn-target-uri"><dfn id="dfn-target-uri">Target-URI</dfn></a></dt>
+ <dd>
+ a URI denoting a <a class="internalDFN" href="#dfn-resource">resource</a> (including any <a class="internalDFN" href="#dfn-constrained-resource">constrained resource</a>), and which identifies that resource for the purpose of expressing provenance. Such a resource is typically an <a class="externalRef" href="http://www.w3.org/TR/prov-dm/#section-entity-activity">entity</a> in the sense of [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>], but may be something else described by provenance records, such as an <a class="externalRef" href="http://www.w3.org/TR/prov-dm/#section-entity-activity">activity</a>.
+ </dd>
+ <dt><a href="#dfn-provenance-record"><dfn id="dfn-provenance-record">Provenance record</dfn></a></dt>
+ <dd>
+ refers to provenance represented in some fashion.
+ </dd>
+ <dt><a href="#dfn-provenance-uri"><dfn id="dfn-provenance-uri">Provenance-URI</dfn></a></dt>
+ <dd>
+ a URI denoting some <a class="internalDFN" href="#dfn-provenance-record">provenance record</a>.
+ </dd>
+ <dt><a href="#dfn-provenance-query-service"><dfn id="dfn-provenance-query-service">Provenance query service</dfn></a></dt>
+ <dd>
+ a service that accesses provenance given a query containing a <a class="internalDFN" href="#dfn-target-uri">target-URI</a> or other information that identifies the desired provenance.
+ </dd>
+ <dt><a href="#dfn-service-uri"><dfn id="dfn-service-uri">Service-URI</dfn></a></dt>
+ <dd>
+ the URI of a <a class="internalDFN" href="#dfn-provenance-query-service">provenance query service</a>.
+ </dd>
+ <dt><a href="#dfn-pingback-uri"><dfn id="dfn-pingback-uri">Pingback-URI</dfn></a></dt>
+ <dd>
+ the URI of a provenance pingback service that can receive references to additional provenance related to an entity.
+ </dd>
+ <dt><a href="#dfn-accessing"><dfn id="dfn-accessing">Accessing</dfn></a> provenance records</dt>
+ <dd>
+ given the identity of a resource, the process of discovering and retrieving some <a class="internalDFN" href="#dfn-provenance-record">provenance record</a>(s) about that resource. This may involve <a class="internalDFN" href="#dfn-locating">locating</a> a provenance record, then performing an HTTP GET to retrieve it, or locating and using a query service for provenance about an identified resource, or some other mechanism not covered in this document.
+ </dd>
+ <dt><a href="#dfn-locating"><dfn id="dfn-locating">Locating</dfn></a> provenance records</dt>
+ <dd>
+ given the identity of a resource, discovery of a <a class="internalDFN" href="#dfn-provenance-uri">provenance-URI</a> or a <a class="internalDFN" href="#dfn-service-uri">service-URI</a> that may be used to obtain a <a class="internalDFN" href="#dfn-provenance-record">provenance record</a> about that resource.
+ </dd>
+ <dt>provenance <a href="#dfn-provider"><dfn id="dfn-provider">provider</dfn></a></dt>
+ <dd>
+ is an agent that makes available provenance records.
+ </dd>
+ <dt>provenance <a href="#dfn-consumer"><dfn id="dfn-consumer">consumer</dfn></a></dt>
+ <dd>
+ is an agent that receives and interprets provenance records.
+ </dd>
+ <!--
+ <a href="#dfn-..."><dt><dfn>...</dfn></dt></a>
+ <dd>
+ ...
+ </dd>
+ -->
+ </dl>
+
+ </section>
+
+ <section id="provenance-and-resources">
+ <h3 id="provenance-entities-resources"><span class="secno">1.2 </span>Provenance and resources</h3>
+ <p>
+ Fundamentally, a <a class="internalDFN" href="#dfn-provenance-record">provenance record</a> is <em>about</em> <a class="internalDFN" href="#dfn-resource">resource</a>s.
+ In general, resources may vary over time and context. E.g., a resource describing the weather in London changes from day-to-day, or a listing of restaurants near you will vary depending on your location.
+ </p>
+ <p>
+ Provenance records a history of the entities, activities, and people involved in producing an artifact, and may be collected from several sources at different times [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>]. In order to create a meaningful history, the individual provenance records used must retain their intended meaning when interpreted in a context other than that in which they were collected.
+ Yet, we may still want to make provenance assertions about dynamic or context-dependent resources (e.g. a weather forecast for London on a particular day may have been derived from a particular set of Meteorological Office data).
+ </p>
+ <p>
+ Provenance records for dynamic and context-dependent resources are possible through a notion of constrained resources. A <a class="internalDFN" href="#dfn-constrained-resource">constrained resource</a> is simply a resource (in the sense defined by [<cite><a class="bibref" href="#bib-WEBARCH">WEBARCH</a></cite>], <a href="http://www.w3.org/TR/webarch/#id-resources" class="externalRef">section 2.2</a>) that is a specialization or instance of some other resource. For example, a <abbr title="World Wide Web Consortium">W3C</abbr> specification typically undergoes several public revisions before it is finalized. A URI that refers to the "current" revision might be thought of as denoting the specification throughout its lifetime. Each individual revision would also have its own <a class="internalDFN" href="#dfn-target-uri">target-URI</a> denoting the specification at that particular stage in its development. Using these, we can make provenance assertions that a particular revision was published on a particular date, and was last modified by a particular editor. Target-URIs may use any URI scheme, and are not required to be dereferencable.
+ </p>
+ <p>
+ Requests for provenance about a resource may return provenance records that use one or more target-URIs to refer to versions of that resource, such as when there are assertions referring to the same underlying resource in different contexts. For example, a provenance record for a <abbr title="World Wide Web Consortium">W3C</abbr> document might include information about all revisions of the document using statements that use the different target-URIs of the various revisions.
+ </p>
+ <p>
+ These ideas are represented in the provenance data model [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>] by the concepts <a href="http://www.w3.org/TR/prov-dm/#term-entity" class="externalRef">entity</a> and <a href="http://www.w3.org/TR/prov-dm/#term-specialization" class="externalRef">specialization</a>. In particular, an entity may be a specialization of some resource whose "fixed aspects" provide sufficient constraint for expressed provenance about the resource to be invariant with respect to that entity. This entity is itself just another resource (e.g. the weather forecast for a give date as opposed to the current weather forecast), with its own URI for referring to it within a provenance record.
+ </p>
+ </section>
+
+ <section id="interpreting-provenance-records">
+ <h3><span class="secno">1.3 </span>Interpreting provenance records</h3>
+ <p>
+ The mechanisms described in this document are intended to allow a provider to supply information that allows a consumer to access <a class="internalDFN" href="#dfn-provenance-record">provenance record</a>s, which themselves explicitly identify the <a href="http://www.w3.org/TR/prov-dm/#term-entity" class="externalRef">entities</a> they describe.
+ A provenance record may contain information about several entities, referring to them using their various <a class="internalDFN" href="#dfn-target-uri">target-URI</a>s.
+ Thus, a consumer should be selective in its use of the information provided when interpreting a provenance record.
+ </p>
+ <p>
+ A provenance record consumer will need to isolate information about the specific entity or entities of interest. These may be <a class="internalDFN" href="#dfn-constrained-resource">constrained resource</a>s identified by separate target-URIs that differ from the resource URI, in which case the consumer needs to discover those target-URIs. The mechanisms defined later allow a provider to expose such URIs.
+ </p>
+ <p>
+ While a provider should avoid giving spurious information, there are no fixed semantics, particularly when multiple resources are indicated, and a client should not assume that a specific given provenance-URI will yield information about a specific target-URI. In the general case, a client presented with multiple provenance-URIs and multiple target-URIs should look at all of the provenance-URIs for information about any or all of the target-URIs.
+ </p>
+ <p>
+ A provenance record is not of itself guaranteed to be authoritative or correct. Trust in provenance records must be determined separately from trust in the original resource. Just as in the web at large, it is a user's responsibility to determine an appropriate level of trust in any other resource; e.g. based on the domain that serves it, or an associated digital signature. (See also <a href="#security-considerations" class="sectionRef sec-ref">section 6. Security considerations</a>.)
+ </p>
+ </section>
+
+ <section id="uri-types-and-dereferencing">
+ <h3><span class="secno">1.4 </span>URI types and dereferencing</h3>
+ <p>
+ A number of resource types are described above in <a href="#concepts" class="sectionRef sec-ref">section 1.1 Concepts</a>. The table below summarizes what these various URIs are intended to denote, and the kind of information that should be returned if they are dereferenced:
+ </p>
+ <table>
+ <tbody><tr>
+ <th></th>
+ <th>Denotes</th>
+ <th>Dereferences to</th>
+ </tr>
+ <tr style="vertical-align: top;">
+ <td><a class="internalDFN" href="#dfn-target-uri">Target-URI</a></td>
+ <td>Any resource that is described by some provenance - typically an <a class="externalRef" href="http://www.w3.org/TR/prov-dm/#section-entity-activity">entity</a> (in the sense of [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>]), but may be of another type (such as [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>] activity).</td>
+ <td>
+ Not specified (the URI is not even required to be dereferencable).
+ <!-- If the URI is dereferencable, it should return a representation or description of the resource for which provenance is provided. -->
+ </td>
+ </tr>
+ <tr style="vertical-align: top;">
+ <td><a class="internalDFN" href="#dfn-provenance-uri">Provenance-URI</a></td>
+ <td>A provenance record, or provenance description, in the sense described by [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>] (<a href="http://www.w3.org/TR/prov-dm/#section-prov-overview" class="externalRef">PROV Overview</a>).</td>
+ <td>A provenance record in any defined format, selectable via content negotiation.</td>
+ </tr>
+ <tr style="vertical-align: top;">
+ <td><a class="internalDFN" href="#dfn-service-uri">Service-URI</a></td>
+ <td>A provenance query service. The service-URI is the initial URI used when accessing a provenance query service; following REST API style [<cite><a class="bibref" href="#bib-REST-APIs">REST-APIs</a></cite>], URIs for accessing provenance are determined via the service description.</td>
+ <td>A provenance query service description per <a href="#provenance-query-service-description" class="sectionRef sec-ref">section 4.1 Provenance query service description</a>. Alternative formats may be offered via HTTP content negotiation.</td>
+ </tr>
+ <tr style="vertical-align: top;">
+ <td><a class="internalDFN" href="#dfn-pingback-uri">Pingback-URI</a></td>
+ <td>A provenance pingback service. This is a service to which provenance pingback information can be submitted using an HTTP POST operation per <a href="#provenance-pingback" class="sectionRef sec-ref">section 5. Provenance pingback</a>. No other operations are specified.</td>
+ <td>None specified (the owner of a provenance pingback URI may choose to return useful information, but is not required to do so.)</td>
+ </tr>
+ </tbody></table>
+ <p>
+ </p>
+ </section>
+
+ </section>
+
+<!-- == Sect 2 =================================================================================== -->
+
+ <section id="accessing-provenance-records">
+ <!--OddPage--><h2><span class="secno">2. </span>Accessing provenance records</h2>
+ <p>
+ This specification describes two ways to access <a class="internalDFN" href="#dfn-provenance-record">provenance record</a>s:
+ </p>
+ <ol>
+ <li>Direct access: given a <a class="internalDFN" href="#dfn-provenance-uri">provenance-URI</a>, simply dereference it, and</li>
+ <li>Indirectly via a query service: given the URIs of some resource (or maybe other information) and a <a class="internalDFN" href="#dfn-provenance-query-service">provenance query service</a>, use the service to access provenance of the resource.</li>
+ </ol>
+ <p>
+ Web applications may access a provenance record in the same way as any resource on the Web, by dereferencing its URI (commonly using an HTTP GET operation). Thus, any provenance record may be associated with a <a class="internalDFN" href="#dfn-provenance-uri">provenance-URI</a>, and may be accessed by dereferencing that URI using web mechanisms.
+ How much or how little provenance is returned in a provenance record is a matter for the provider, taking account that a provenance trace may extend as linked data across multiple provenance records.
+ </p>
+ <p>
+ When there is no easy way to associate a <a class="internalDFN" href="#dfn-provenance-uri">provenance-URI</a> with a resource (e.g. for resources not directly web-accessible, or whose publication mechanism is controlled by someone else), a provenance description may be obtained using a provenance query service at an indicated <a class="internalDFN" href="#dfn-service-uri">service-uri</a>.
+ A REST protocol for provenance queries is defined in Section <a href="#provenance-query-services" class="sectionRef sec-ref">section 4. Provenance query services</a>; also described there is a mechanism for locating a SPARQL query service [<cite><a class="bibref" href="#bib-SPARQL-SD">SPARQL-SD</a></cite>].
+ </p>
+ <p>
+ When publishing provenance, corresponding <a class="internalDFN" href="#dfn-provenance-uri">provenance-URI</a>s or <a class="internalDFN" href="#dfn-service-uri">service-URI</a>s should be discoverable using one or more of the mechanisms described in <a href="#locating-provenance-records" class="sectionRef sec-ref">section 3. Locating provenance records</a>.
+ </p>
+ <div class="note"><div class="note-title" role="heading" aria-level="3"><span>Note</span></div><p class="">
+ Provenance may be presented as a <a href="http://www.w3.org/TR/prov-dm/#component4" class="externalRef">bundle</a>, which is "<cite>a named set of provenance descriptions, and is itself an entity, so allowing provenance of provenance to be expressed</cite>" [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>]. A provenance description at a dereferencable provenance-URI may be treated as a bundle, and this is a good way to make provenance easily accessible. But there are other possible implementations of a bundle, such as a named graph in an RDF dataset [<cite><a class="bibref" href="#bib-RDF-CONCEPTS11">RDF-CONCEPTS11</a></cite>], for which the bundle URI may not be directly dereferencable.
+ <br><br>
+ When a bundle is published as part of an RDF Dataset, to access it would require accessing the RDF Dataset and then extracting the identified graph component; this in turn would require knowing a URI or some other way to retrieve the RDF dataset. This specification does not describe a specific mechanism for extracting components from a document containing multiple graphs.
+ <br><br>
+ The <abbr title="World Wide Web Consortium">W3C</abbr> Linked Data Platform group (<a href="http://www.w3.org/2012/ldp/" class="externalRef">www.w3.org/2012/ldp/</a>) is chartered to produce a <abbr title="World Wide Web Consortium">W3C</abbr> Recommendation for HTTP-based (RESTful) application integration patterns using read/write Linked Data; we anticipate that they may address access to RDF Datasets in due course.
+ </p></div>
+
+ </section>
+
+<!-- == Sect 3 =================================================================================== -->
+
+ <section id="locating-provenance-records">
+ <!--OddPage--><h2><span class="secno">3. </span>Locating provenance records</h2>
+ <p>
+ A <a class="internalDFN" href="#dfn-provenance-record">provenance record</a> can be accessed using direct web retrieval, given its <a class="internalDFN" href="#dfn-provenance-uri">provenance-URI</a>. If this is known in advance, there is nothing more to specify. If a provenance-URI is not known then a mechanism to discover one must be based on information that is available to the would-be accessor. Likewise, provenance may be exposed by a query service, in which case, the corresponding <a class="internalDFN" href="#dfn-service-uri">service-URI</a> must be discovered.
+ </p>
+ <p>
+ Three mechanisms are defined for a provenance <a class="internalDFN" href="#dfn-consumer">consumer</a> to find information about a <a class="internalDFN" href="#dfn-provenance-uri">provenance-URI</a> or <a class="internalDFN" href="#dfn-service-uri">service-URI</a>, along with a <a class="internalDFN" href="#dfn-target-uri">target-URI</a>:
+ </p>
+ <ol>
+ <li>The consumer knows the resource URI <em>and</em> the resource is accessible using HTTP</li>
+ <li>The consumer has a copy of a resource represented as HTML or XHTML</li>
+ <li>The consumer has a copy of a resource represented as RDF (including the range of possible RDF syntaxes, such as HTML with embedded RDFa)</li>
+ </ol>
+ <p>
+ These particular cases are selected as corresponding to current primary web protocol and data formats. Similar approaches may be defined for other protocols or resource formats.
+ </p>
+ <p>Provenance records may be offered by several <a class="internalDFN" href="#dfn-provider">provider</a>s other than that of the original resource publisher, each with different concerns, and presenting provenance at different locations. It is possible that these different providers may present contradictory provenance.
+ </p>
+
+ <section id="resource-accessed-by-http">
+ <h3><span class="secno">3.1 </span>Resource accessed by HTTP</h3>
+ <p>
+ For a resource accessible using HTTP, a provenance record may be indicated using an HTTP <code>Link</code> header field, as defined by <a href="http://tools.ietf.org/html/rfc5988#section-5" class="externalRef">Web Linking (RFC 5988)</a> [<cite><a class="bibref" href="#bib-LINK-REL">LINK-REL</a></cite>]. The <code>Link</code> header field is included in the HTTP response to a GET or HEAD operation (other HTTP operations are not excluded, but are not considered here).
+ </p>
+ <p>
+ A <code>has_provenance</code> link relation type for referencing a provenance record may be used thus:
+ </p>
+ <pre class="pattern">Link: <<cite>provenance-URI</cite>>;
+ rel="http://www.w3.org/ns/prov#has_provenance";
+ anchor="<cite>target-URI</cite>"</pre>
+ <p>When used in conjunction with an HTTP success response code (<code>2xx</code>), this HTTP header field indicates that <code><cite>provenance-URI</cite></code> is the URI of a provenance record about the originally requested resource, and that the requested resource is identified within the provenance record as <code><cite>target-URI</cite></code>. (See also <a href="#interpreting-provenance-records" class="sectionRef sec-ref">section 1.3 Interpreting provenance records</a>.)</p>
+ <p>
+ If no <code>anchor</code> parameter is provided then the <code><cite>target-URI</cite></code> is assumed to be the URI of the requested resource used in the corresponding HTTP request.
+ </p>
+ <p>
+ This note does not define the meaning of these links returned with other HTTP response codes: future revisions may define interpretations for these.
+ </p>
+ <p>
+ An HTTP response <em class="rfc2119" title="MAY">MAY</em> include multiple <code>has_provenance</code> link header fields, indicating a number of different provenance resources (and anchors) that are known to the responding server, each referencing a provenance record about the accessed resource.
+ </p>
+ <p>
+ The presence of a <code>has_provenance</code> link in an HTTP response does not preclude the possibility that other providers also may offer provenance records about the same resource. In such cases, discovery of the additional provenance records must use other means (e.g. see <a href="#provenance-query-services" class="sectionRef sec-ref">section 4. Provenance query services</a>).
+ </p>
+ <p>
+ An example HTTP response including provenance headers might look like this (where <code>C:</code> and <code>S:</code> prefixes indicate client and server emitted data respectively):
+ </p>
+ <div class="example"><div class="example-title"><span>Example 1</span></div><pre class="example code">C: GET http://example.com/resource123/ HTTP/1.1
+C: Accept: text/html
+
+S: HTTP/1.1 200 OK
+S: Content-type: text/html
+S: Link: <http://example.com/resource123/provenance/>;
+ rel="http://www.w3.org/ns/prov#has_provenance";
+ anchor="http://example.com/resource123/"
+S:
+S: <html ...>
+S: :
+S: </html></pre></div>
+
+ <section id="specifying-provenance-query-services">
+ <h4><span class="secno">3.1.1 </span>Specifying Provenance Query Services</h4>
+ <p>
+ The resource provider may indicate that provenance records about the resource are provided by a <a class="internalDFN" href="#dfn-provenance-query-service">provenance query service</a>. This is done through the use of a <code>has_query_service</code> link relation type following the same pattern as above:
+ </p>
+ <pre class="pattern">Link: <<cite>service-URI</cite>>;
+ rel="http://www.w3.org/ns/prov#has_query_service";
+ anchor="<cite>target-URI</cite>"
+</pre>
+ <p>
+ The <code>has_query_service</code> link identifies the <a class="internalDFN" href="#dfn-service-uri">service-URI</a>. Dereferencing this URI yields a service description that provides further information to enable a client to submit a query to retrieve a <a class="internalDFN" href="#dfn-provenance-record">provenance record</a> for a <a class="internalDFN" href="#dfn-resource">resource</a>; see <a href="#provenance-query-services" class="sectionRef sec-ref">section 4. Provenance query services</a> for more details.
+ </p>
+ <div class="example"><div class="example-title"><span>Example 2</span></div><pre class="example code">C: GET http://example.com/resource123/ HTTP/1.1
+C: Accept: text/html
+
+S: HTTP/1.1 200 OK
+S: Content-type: text/html
+S: Link: <http://example.com/resource123/provenance-query/>;
+ rel="http://www.w3.org/ns/prov#has_query_service";
+ anchor="http://example.com/resource123/"
+S:
+S: <html ...>
+S: :
+S: </html></pre></div>
+ <p>
+ There <em class="rfc2119" title="MAY">MAY</em> be multiple <code>has_query_service</code> link header fields, and these <em class="rfc2119" title="MAY">MAY</em> appear in an HTTP response together with <code>has_provenance</code> link header fields.
+ </p>
+ </section>
+
+ <section id="content-negotiation-redirection-and-link-headers">
+ <h4><span class="secno">3.1.2 </span>Content negotiation, redirection and Link: headers</h4>
+ <p>
+ When performing content negotiation for a resource, it is common for HTTP 302 or 303 redirect response codes to be used to direct a client to an appropriately-formatted resource. When accessing a resource for which provenance is available, link headers <em class="rfc2119" title="SHOULD">SHOULD</em> be included with the response to the final redirected request, and not on the intermediate 303 responses. (When accessing a resource from a browser using Javascript, the intermediate 303 responses are usually handled transparently by the browser and are not visible to the HTTP client code.)
+ </p>
+ <p>
+ Following content negotiation, any provenance link returned refers to the resource whose URI is used in the corresponding HTTP request, or the given anchor parameter if that is different.
+ </p>
+ <p>
+ An example transaction using content negotiation and redirection might look like this (where <code>C:</code> and <code>S:</code> prefixes indicate client and server emitted data respectively):
+ </p>
+ <div class="example"><div class="example-title"><span>Example 3</span></div><pre class="example code">C: GET http://example.com/resource123/ HTTP/1.1
+C: Accept: text/html
+
+S: HTTP/1.1 302 Found
+S: Location: /resource123/content.html
+S: Vary: Accept
+S:
+S: HTML content for http://example.com/resource123/
+S: is available at http://example.com/resource123/content.html
+
+C: GET http://example.com/resource123/content.html HTTP/1.1
+C: Accept: text/html
+
+S: HTTP/1.1 200 OK
+S: Content-type: text/html
+S: Link: <http://example.com/resource123/provenance/>;
+ rel="http://www.w3.org/ns/prov#has_provenance";
+ anchor="http://example.com/resource123/20130226/content.html"
+S:
+S: <html>
+S: <!-- HTML content here... -->
+S: </html></pre></div>
+ <p>
+ This example indicates a provenance record at <code>http://example.com/resource123/provenance/</code>, which uses <code>http://example.com/resource123/20130226/content.html</code> as the target-URI for the requested resource. If the <code>anchor=</code> parameter were to be omitted from the <code>Link</code> header field, the indicated target-URI would be <code>http://example.com/resource123/content.html</code>.
+ </p>
+ </section>
+
+ </section>
+
+ <section id="resource-represented-as-html">
+ <h3><span class="secno">3.2 </span>Resource represented as HTML</h3>
+ <div>
+ For a document presented as HTML or XHTML, without regard for how it has been obtained, a provenance record may be associated with a resource by adding a <code><link></code> element to the HTML <code><head></code> section.
+ Two link relation types for referencing provenance may be used:
+ <pre class="pattern"> <html>
+ <head>
+ <b><link rel="http://www.w3.org/ns/prov#has_provenance" href="<cite>provenance-URI</cite>"></b>
+ <b><link rel="http://www.w3.org/ns/prov#has_anchor" href="<cite>target-URI</cite>"></b>
+ <title>Welcome to example.com</title>
+ </head>
+ <body>
+ <!-- HTML content here... -->
+ </body>
+ </html></pre>
+ </div>
+ <p>
+ The <code><cite>provenance-URI</cite></code> given by the first link element (<code>#has_provenance</code> ) identifies the provenance-URI for the document.
+ </p>
+ <p>
+ The <code><cite>target-URI</cite></code> given by the second link element (<code>#has_anchor</code>) specifies an identifier for the document that may be used within the provenance record when referring to the document.
+ </p>
+ <p>
+ If no <code><cite>target-URI</cite></code> is provided (via a <code>#has_anchor</code> link element) then is it is assumed to be the URI of the document. It is <em class="rfc2119" title="RECOMMENDED">RECOMMENDED</em> that this convention be used only when the document has a URI that is reasonably expected to be known or easily discoverable by a consumer of the document (e.g. when delivered from a web server, or as part of a MIME structure containing content identifiers [<cite><a class="bibref" href="#bib-RFC2392">RFC2392</a></cite>]).
+ </p>
+ <p>
+ An HTML document header <em class="rfc2119" title="MAY">MAY</em> present multiple <code><cite>provenance-URI</cite></code>s over several <code>#has_provenance</code> link elements, indicating a number of different provenance records that are known to the publisher of the document, each of which may provide provenance about the document (see <a href="#interpreting-provenance-records" class="sectionRef sec-ref">section 1.3 Interpreting provenance records</a>).
+ </p>
+
+ <div class="note"><div class="note-title" role="heading" aria-level="4"><span>Note</span></div><p class="">
+ The mechanisms used with HTTP and HTML/RDF are slightly inconsistent in their approach to specifying <code><cite>target-URI</cite></code> values. In HTTP <code>Link</code> header fields, an optional <code>anchor=</code> parameter may be supplied for each such header. In HTML and RDF, separate <code>#has_anchor</code> relations are defined. It was felt that avoiding reinvention of existing mechanisms was more important than being completely consistent. If anchors are processed as described in <a href="#interpreting-provenance-records" class="sectionRef sec-ref">section 1.3 Interpreting provenance records</a> (3rd paragraph), observable behaviour across all approaches should be consistent.
+ </p></div>
+
+ <section id="specifying-provenance-query-services-1">
+ <h4><span class="secno">3.2.1 </span>Specifying Provenance Query Services</h4>
+ <p>
+ The document creator may specify that the provenance about the document is provided by a <a class="internalDFN" href="#dfn-provenance-query-service">provenance query service</a>. This is done through the use of a third link relation type following the same pattern as above:
+ </p>
+ <pre class="pattern"> <html xmlns="http://www.w3.org/1999/xhtml">
+ <head>
+ <b><link rel="http://www.w3.org/ns/prov#has_query_service" href="<cite>service-URI</cite>"></b>
+ <b><link rel="http://www.w3.org/ns/prov#has_anchor" href="<cite>target-URI</cite>"></b>
+ <title>Welcome to example.com</title>
+ </head>
+ <body>
+ <!-- HTML content here... -->
+ </body>
+ </html></pre>
+ <p>
+ The <code>has_query_service</code> link element identifies the <a class="internalDFN" href="#dfn-service-uri">service-URI</a>. Dereferencing this URI yields a service description that provides further information to enable a client to query for provenance about a resource; see <a href="#provenance-query-services" class="sectionRef sec-ref">section 4. Provenance query services</a> for more details.
+ </p>
+ <p>
+ There <em class="rfc2119" title="MAY">MAY</em> be multiple <code>#has_query_service</code> link elements, and these <em class="rfc2119" title="MAY">MAY</em> appear in the same document as <code>#has_provenance</code> link elements (though we do not anticipate that <code>#has_provenance</code> and <code>#has_query_service</code> link relations will commonly be used together).
+ </p>
+
+ </section>
+
+ </section>
+
+ <section id="resource-represented-as-rdf">
+ <h3><span class="secno">3.3 </span>Resource represented as RDF</h3>
+ <p>
+ If a resource is represented as RDF (in any of its recognized syntaxes, including RDFa), it may contain references to its own provenance using additional RDF statements.
+ For this purpose, the link relations introduced above (<a href="#locating-provenance-records" class="sectionRef sec-ref">section 3. Locating provenance records</a>) may be used as RDF properties: <code>prov:has_provenance</code>, <code>prov:has_anchor</code>, and <code>prov:has_query_service</code>, where the <code>prov:</code> prefix here indicates the PROV namespace URI <code>http://www.w3.org/ns/prov#</code>.
+ </p>
+ <p>
+ The RDF property <code>prov:has_provenance</code> is a relation between two resources, where the object of the property is a <a class="internalDFN" href="#dfn-provenance-uri">provenance-URI</a> that denotes a provenance record about the subject resource. Multiple <code>prov:has_provenance</code> assertions may be made about a subject resource.
+ </p>
+ <p>
+ Property <code>prov:has_anchor</code> specifies a <a class="internalDFN" href="#dfn-target-uri">target-URI</a> used in the indicated provenance to refer to the containing RDF document.
+ </p>
+ <p>
+ Property <code>prov:has_query_service</code> specifies a <a class="internalDFN" href="#dfn-service-uri">service-URI</a> for provenance queries.
+ </p>
+ <div class="example"><div class="example-title"><span>Example 4</span></div><pre class="example code">@prefix prov: <http://www.w3.org/ns/prov#>.
+
+<> dcterms:title "Welcome to example.com" ;
+ prov:has_anchor <http://example.com/data/resource.rdf> ;
+ prov:has_provenance <http://example.com/provenance/resource.rdf> ;
+ prov:has_query_service <http://example.com/provenance-query-service/> .
+
+ # (More RDF data ...)</pre></div>
+ <p>
+ (The above example uses Turtle RDF syntax [<cite><a class="bibref" href="#bib-TURTLE">TURTLE</a></cite>].)
+ </p>
+ <div class="note"><div class="note-title" role="heading" aria-level="4"><span>Note</span></div><p class="">
+ These terms (<code>prov:has_provenance</code>, <code>prov:has_anchor</code>, and <code>prov:has_query_service</code>) may be also used in RDF statements with other subjects to indicate provenance of other resources, but discussion of such use is beyond the scope of this document.
+ <br><br>
+ See also the note about target-URIs at the end of <a href="#resource-represented-as-html" class="sectionRef sec-ref">section 3.2 Resource represented as HTML</a>.
+ </p></div>
+ </section>
+
+ </section>
+
+<!-- == Sect 4 =================================================================================== -->
+
+ <section id="provenance-query-services">
+ <!--OddPage--><h2><span class="secno">4. </span>Provenance query services</h2>
+ <p>
+ This section describes a simple HTTP query protocol for accessing provenance records, and also a mechanism for locating a SPARQL service endpoint [<cite><a class="bibref" href="#bib-SPARQL-SD">SPARQL-SD</a></cite>]. The HTTP query protocol specifies HTTP operations [<cite><a class="bibref" href="#bib-HTTP11">HTTP11</a></cite>] for retrieving provenance records from a provenance query service, following the approach of the SPARQL Graph Store HTTP Protocol [<cite><a class="bibref" href="#bib-SPARQL-HTTP">SPARQL-HTTP</a></cite>].
+ </p>
+ <p>
+ The introduction of query services is motivated by the following possible considerations:
+ </p>
+ <ul>
+ <li>
+ third-party providers of provenance descriptions may be unable to use the mechanisms of Section 3 because the corresponding <a class="internalDFN" href="#dfn-target-uri">target-URI</a> is outside their control;
+ </li>
+ <li>
+ services unknown to the original publisher may have provenance records about the same resource;
+ </li>
+ <li>
+ there is no known dereferencable <a class="internalDFN" href="#dfn-provenance-uri">provenance-URI</a> or a particular entity;
+ </li>
+ <li>
+ query services may provide additional filters over what provenance is returned; and
+ </li>
+ <li>
+ query services may support more expressive selections, such as "which
+entities were derived from entities attributed to agent X".
+ </li>
+ </ul>
+ <p>
+ The patterns for using provenance query services are designed around REST principles [<cite><a class="bibref" href="#bib-REST">REST</a></cite>], which aim to minimize coupling between client and server implementation details.
+ </p>
+ <p>
+ The query mechanisms provided by a <a class="internalDFN" href="#dfn-provenance-query-service">provenance query service</a> are described by a service description, which is obtained by dereferencing a <a class="internalDFN" href="#dfn-service-uri">service-URI</a>. A service description may contain information about additional mechanisms that are not described here. In keeping with REST practice for web applications, alternative service descriptions using different formats may be offered and accessed using HTTP content negotiation. We describe below a service description format that uses RDF to describe two query mechanisms.
+ </p>
+ <p>
+ The general procedure for using a provenance query service is:
+ </p>
+ <ol>
+ <li>retrieve the service description;</li>
+ <li>within the service description, locate information about a recognized query mechanism (ignoring unrecognized descriptions if the description covers multiple service options);</li>
+ <li>if a recognized query mechanism is found, extract information needed to use that mechanism (e.g. a URI template or a SPARQL service endpoint URI); and</li>
+ <li>use the information obtained to query for required provenance, using the selected query mechanism.</li>
+ </ol>
+ <p>
+ The remainder of this section covers the following topics:
+ </p>
+ <ul>
+ <li>
+ <a class="sectionRef sec-ref" href="#provenance-query-service-description">section 4.1 Provenance query service description</a> - describes an RDF-based service description format and vocabularies to convey information about direct HTTP query and/or SPARQL service options.
+ <ul>
+ <li> <a class="sectionRef sec-ref" href="#direct-http-query-service-description">section 4.1.1 Direct HTTP query service description</a> - RDF structure for describing a direct HTTP query service. </li>
+ </ul>
+ <ul>
+ <li> <a class="sectionRef sec-ref" href="#sparql-query-service-description">section 4.1.2 SPARQL query service description</a> - RDF structure for describing a SPARQL query service.</li>
+ </ul>
+ </li>
+ <li><a class="sectionRef sec-ref" href="#direct-http-query-service-invocation">section 4.2 Direct HTTP query service invocation</a> - describes how to perform a direct HTTP query for provenance, using information obtained from the service description.</li>
+ <li><a class="sectionRef sec-ref" href="#provenance-query-service-discovery">section 4.3 Provenance query service discovery</a> - briefly discusses some possible approaches to discovery of provenance query services.
+ </li></ul>
+
+ <!-- <section class="informative"> -->
+ <section id="provenance-query-service-description">
+ <h3><span class="secno">4.1 </span>Provenance query service description</h3>
+ <p>
+ Dereferencing a <a class="internalDFN" href="#dfn-service-uri">service-URI</a> yields a service description. The service description may be in any format selectable through content negotiation, and it may contain descriptions of one or more available query mechanisms. The format described here uses RDF, serialized as Turtle [<cite><a class="bibref" href="#bib-TURTLE">TURTLE</a></cite>], but any selectable RDF serialization could be used. In this RDF service description, each query mechanism is associated with an RDF type, as explained below.
+ </p>
+ <p>
+ The overall structure of a service description is as follows:
+ </p>
+ <pre class="pattern"><<cite>service-URI</cite>> a prov:ServiceDescription ;
+ prov:describesService <<cite>direct-query-description</cite>>, <<cite>sparql-query-description</cite>> .
+
+<<cite>direct-query-description</cite>> a prov:DirectQueryService ;
+ prov:provenanceUriTemplate "<cite>direct-query-template</cite>"
+ .
+
+<<cite>sparql-query-description</cite>> a sd:Service ;
+ sd:endpoint <<cite>sparql-query</cite>> ;
+ # other details...
+ .
+</pre>
+ <p>
+ We see here that the <code><cite>service-URI</cite></code> identifies a resource of type <code>prov:ServiceDescription</code>, which collects descriptions of one or more provenance query mechanisms. Each associated mechanism is indicated by a <code>prov:describesService</code> statement.
+ </p>
+ <!--
+ <p class="note">
+ We expect the presentation of service descriptions to be considered by the W3C Linked Data Platform group (<a href="http://www.w3.org/2012/ldp/" class="externalRef">www.w3.org/2012/ldp/</a>); at the time of writing, there is no consensus (cf. message at <a href="http://lists.w3.org/Archives/Public/public-ldp/2012Nov/0036.html" class="externalRef">lists.w3.org/Archives/Public/public-ldp/2012Nov/0036.html</a> and responses). As and when such consensus emerges, we recommend that provenance query service implementers consider adopting it, or at least consider making their implementations compatible with it.
+ </p>
+ -->
+
+ <section id="direct-http-query-service-description">
+ <h4><span class="secno">4.1.1 </span>Direct HTTP query service description</h4>
+ <p>
+ A direct HTTP query service is described by an RDF resource of type <code>prov:DirectQueryService</code>.
+ It allows for accessing provenance about a specified <a class="internalDFN" href="#dfn-target-uri">target-URI</a>. The query URI to use is described by a URI Template [<cite><a class="bibref" href="#bib-URI-template">URI-template</a></cite>] (level 2 or above) in which the variable <cite><code>uri</code></cite> stands for the target-URI. The URI template is specified as:</p>
+ <pre class="pattern"><direct-query-description> a prov:DirectQueryService ;
+ prov:provenanceUriTemplate "<cite>uri-template</cite>" .
+</pre>
+ <p>
+ where <code><cite>direct-query-description</cite></code> is any distinct RDF subject node (i.e. a blank node or a URI), and <code><cite>uri-template</cite></code> is a URI template [<cite><a class="bibref" href="#bib-RFC3986">RFC3986</a></cite>].
+ </p>
+ <p>
+ The URI template indicated by <code>prov:provenanceUriTemplate</code> may expand to an absolute or relative URI reference. A URI for the desired provenance record is obtained by expanding the URI template with the variable <cite><code>uri</code></cite> set to the target-URI for which provenance is requested. In this example, if the target-URI contains '#' or '&' these must be %-escaped as <code>%23</code> or <code>%26</code> respectively before template expansion [<cite><a class="bibref" href="#bib-RFC3986">RFC3986</a></cite>]. If the result is a relative reference, it is interpreted per [<cite><a class="bibref" href="#bib-RFC3986">RFC3986</a></cite>] (section 5.2) using the URI of the service description as its base URI (which is generally the same as the query service-URI, unless HTTP redirection has been invoked).
+ </p>
+ <div class="example"><div class="example-title"><span>Example 5</span></div><pre class="example code"><http://example.com/prov/service> a prov:ServiceDescription;
+ prov:describesService _:direct .
+
+_:direct a prov:DirectQueryService ;
+ prov:provenanceUriTemplate
+ "http://www.example.com/provenance/service?target={uri}" .</pre></div>
+ <p>
+ A provenance query service <em class="rfc2119" title="MAY">MAY</em> recognize additional parameters encoded as part of a URI for the provenance record. If it does, it <em class="rfc2119" title="SHOULD">SHOULD</em> include these in the provenance URI template in the service description, so that clients may discover how a URI is formed using this additional information.
+ For example, a query service might offer to include just the immediate provenance of a target, or to also supply provenance of other resources from which the target is derived. Suppose a service accepts an additional parameter <code>steps</code> that defines the number of previous steps to include in a provenance trace, it might publish its service description thus:
+ </p>
+ <div class="example"><div class="example-title"><span>Example 6</span></div><pre class="example code"><http://example.com/prov/service> a prov:ServiceDescription;
+ prov:describesService _:direct .
+
+_:direct a prov:DirectQueryService ;
+ prov:provenanceUriTemplate
+ "http://www.example.com/provenance/service?target={uri}{&steps}" .</pre></div>
+ <p>
+ (Note that in this case, a "level 3" URI template feature is used [<cite><a class="bibref" href="#bib-URI-template">URI-template</a></cite>].)
+ </p>
+ <p>
+ Section <a href="#direct-http-query-service-invocation" class="sectionRef sec-ref">section 4.2 Direct HTTP query service invocation</a> discusses how a client interacts with a direct HTTP query service.
+ </p>
+
+ </section>
+
+ <section id="sparql-query-service-description">
+ <h4><span class="secno">4.1.2 </span>SPARQL query service description</h4>
+ <p>
+ A SPARQL query service is described by an RDF resource of type <code>sd:Service</code> [<cite><a class="bibref" href="#bib-SPARQL-SD">SPARQL-SD</a></cite>].
+ </p>
+ <p>
+ It allows for accessing provenance information using a SPARQL query, which may be constructed to retrieve provenance for a particular resource, or for multiple resources. The query may be formulated using the PROV-O vocabulary terms [<cite><a class="bibref" href="#bib-PROV-O">PROV-O</a></cite>], and others supported by the SPARQL endpoint as appropriate.
+ </p>
+ <p>
+ The SPARQL query service description is constructed as defined by <cite>SPARQL 1.1 Service Description</cite> [<cite><a class="bibref" href="#bib-SPARQL-SD">SPARQL-SD</a></cite>]; e.g.
+ </p>
+ <div class="example"><div class="example-title"><span>Example 7</span></div><pre class="example code"><http://example.com/prov/service> a prov:ServiceDescription;
+ prov:describesService _:sparql .
+
+_:sparql a sd:Service ;
+ sd:endpoint <http://www.example.com/provenance/sparql> ;
+ sd:supportedLanguage sd:SPARQL11Query .</pre></div>
+ <p>
+ where <code>http://www.example.com/provenance/sparql</code> is the URI of a provenance query SPARQL endpoint.
+ </p>
+ <p>
+ The SPARQL service description may be detailed or sparse, provided that it includes at least a <code>sd:endpoint</code> statement with the SPARQL service endpoint URI.
+ </p>
+ <p>
+ The endpoint may be given as an absolute or relative URI reference. If a relative reference is given, it is interpreted in the normal way for the RDF format used, which will commonly be relative to the URI of the service document itself.
+ </p>
+ </section>
+
+ <section id="service-description-example">
+ <h4><span class="secno">4.1.3 </span>Service description example</h4>
+ <p>
+ The following service description example uses Turtle [<cite><a class="bibref" href="#bib-TURTLE">TURTLE</a></cite>] syntax to describe both direct HTTP and SPARQL query services:
+ </p>
+ <div class="example"><div class="example-title"><span>Example 8</span></div><pre class="example code">@prefix prov: <http://www.w3c.org/ns/prov#> .
+@prefix dcterms: <http://purl.org/dc/terms/> .
+@prefix foaf: <http://xmlns.com/foaf/0.1/> .
+@prefix sd: <http://www.w3.org/ns/sparql-service-description#> .
+
+<> a prov:ServiceDescription ;
+ prov:describesService <#direct>, <#sparql> ;
+ dcterms:publisher <#us>
+ .
+
+<#us> a foaf:Organization ;
+ foaf:name "and not a service!"
+ .
+
+<#direct> a prov:DirectQueryService ;
+ prov:provenanceUriTemplate "/direct?target={+uri}"
+ .
+
+<#sparql> a sd:Service ;
+ sd:endpoint </sparql/> ;
+ sd:supportedLanguage sd:SPARQL11Query ;
+ sd:resultFormat <http://www.w3.org/ns/formats/RDF_XML> ,
+ <http://www.w3.org/ns/formats/Turtle> ,
+ <http://www.w3.org/ns/formats/SPARQL_Results_XML> ,
+ <http://www.w3.org/ns/formats/SPARQL_Results_JSON> ,
+ <http://www.w3.org/ns/formats/SPARQL_Results_CSV> ,
+ <http://www.w3.org/ns/formats/SPARQL_Results_TSV>
+ .</pre></div>
+ </section>
+ </section>
+
+ <section id="direct-http-query-service-invocation">
+ <h3><span class="secno">4.2 </span>Direct HTTP query service invocation</h3>
+ <p>
+ This section describes the interaction between a client and a direct HTTP query service whose service description is as presented in <a href="#direct-http-query-service-description" class="sectionRef sec-ref">section 4.1.1 Direct HTTP query service description</a>, once the service description has been analyzed and its URI template has been extracted.
+ </p>
+ <p>
+ The <a class="internalDFN" href="#dfn-target-uri">target-URI</a> for which provenance is required is used in the expansion of the supplied URI template [<cite><a class="bibref" href="#bib-RFC3986">RFC3986</a></cite>] to formulate an HTTP GET request.
+ </p>
+ <p>
+ Thus, in the first service description example in <a href="#direct-http-query-service-description" class="sectionRef sec-ref">section 4.1.1 Direct HTTP query service description</a>, the URI template is <code>http://www.example.com/provenance/service?target={uri}</code>. If the supplied target-URI is <code>http://www.example.com/entity123</code>, this would be used as the value for variable <code>uri</code> when expanding the template. The resulting HTTP request used to retrieve a provenance record would be:</p>
+ <div class="example"><div class="example-title"><span>Example 9</span></div><pre class="example code">GET /provenance/service?<b>target</b>=http%3A%2F%2Fwww.example.com%2Fentity123 HTTP/1.1
+Host: example.com</pre></div>
+ <p>
+ Any server that implements this protocol and receives a request URI in a form corresponding to its published URI template <em class="rfc2119" title="SHOULD">SHOULD</em> return a provenance record for the embedded target-URI. The target-URI is obtained by percent-decoding [<cite><a class="bibref" href="#bib-RFC3986">RFC3986</a></cite>] the part of the request URI corresponding to occurrences of the variable <code>uri</code> in the URI template. E.g., in the above example, the decoded target-URI is <code>http://www.example.com/entity123</code>. The target-URI <em class="rfc2119" title="MUST">MUST</em> be an absolute URI, and the server <em class="rfc2119" title="SHOULD">SHOULD</em> respond with <code>400 Bad Request</code> if it is not.
+ </p>
+ <p>
+ A server <em class="rfc2119" title="SHOULD NOT">SHOULD NOT</em> offer a template containing <code>{+uri}</code> or other non-simple variable expansion options [<cite><a class="bibref" href="#bib-URI-template">URI-template</a></cite>] unless all valid target-URIs for which it can provide provenance do not contain problematic characters like <code>'#'</code> or <code>'&'</code>.
+ </p>
+ <div class="note"><div class="note-title" role="heading" aria-level="4"><span>Note</span></div><p class="">
+ The defined URI template expansion process [<cite><a class="bibref" href="#bib-URI-template">URI-template</a></cite>] generally takes care of %-escaping characters that are not permitted in URIs. However, when expanding a template with <code>{+uri}</code> (or other non-simple variable expansion options), some permitted characters such as <code>'#'</code> and <code>'&'</code> are not escaped. If the supplied target-URI contains these characters, then they may disrupt interpretation of the resulting query URI. A generally more reliable approach is to use <code>{uri}</code> in the URI template string, which will cause all URI-reserved characters to be %-escaped as part of the URI-template expansion, as in the example above.
+ </p></div>
+ <p>
+ If the provenance described by the request is unknown to the server, a suitable error response code <em class="rfc2119" title="SHOULD">SHOULD</em> be returned. In the absence of any security of privacy concerns about the resource, that might be <code>404 Not Found</code>. But if the existence or non-existence of a resource is considered private or sensitive, an authorization failure or other response may be returned.
+ </p>
+ <p>
+ The direct HTTP query service may return provenance in any available format.
+ For interoperable provenance publication, use of PROV represented in any of its specified formats is recommended. Where alternative formats are available, selection may be made by content negotiation, using <code>Accept:</code> header fields in the HTTP request.
+ Services <em class="rfc2119" title="MUST">MUST</em> identify the <code>Content-Type</code> of the provenance returned.
+ </p>
+ <p>
+ Additional URI query parameters may be used as indicated by the service description in <a href="#direct-http-query-service-description" class="sectionRef sec-ref">section 4.1.1 Direct HTTP query service description</a>. The second service description example specifies a URI template with an additional variable which may be used to control the scope of provenance information returned: <code>http://www.example.com/provenance/service?target={+uri}{&steps}</code>. Following [<cite><a class="bibref" href="#bib-RFC3986">RFC3986</a></cite>], if no value for variable <code>steps</code> is provided when expanding the template, this extra element is effectively ignored. But if a <code>steps</code> value of (say) <code>2</code> is provided, then the resulting HTTP query would be:
+ </p>
+ <div class="example"><div class="example-title"><span>Example 10</span></div><pre class="example code">GET http://example.com/provenance/service?<b>target</b>=http://www.example.com/entity&<b>steps</b>=2 HTTP/1.1</pre></div>
+ <div class="note"><div class="note-title" role="heading" aria-level="4"><span>Note</span></div><p class="">
+ The use of any specific URI template variable other than <code>uri</code> for the target-URI is a matter for agreement between the client and query service, and is not specified in this note. It is mentioned here simply to show that the possibility exists to formulate more detailed queries.
+ </p></div>
+ </section>
+
+ <!-- <section class="informative"> -->
+ <section id="provenance-query-service-discovery">
+ <h3><span class="secno">4.3 </span>Provenance query service discovery</h3>
+ <p>
+ Previously, <a href="#locating-provenance-records" class="sectionRef sec-ref">section 3. Locating provenance records</a> has described use of HTTP <code>Link:</code> header fields, HTML <code><link></code> elements and RDF statements to indicate provenance query services. Beyond that, this specification does not define any specific mechanism for discovering query services. Applications may use any appropriate mechanism, including but not limited to: prior configuration, search engines, service registries, etc.
+ </p>
+ <p>
+ To facilitate service discovery, we recommend that RDF publication of dataset and service descriptions use the property <code>prov:has_query_service</code> and the provenance service type <code>prov:ServiceDescription</code> as appropriate (see the appendix <a href="#prov-namespace" class="sectionRef">section B. </a>).
+ </p>
+ <p>
+ For example, a VoID description [<cite><a class="bibref" href="#bib-VoID">VoID</a></cite>] of a dataset might indicate a provenance query service providing information about that dataset:
+ </p>
+ <pre class="pattern"> <http://example.org/dataset/> a void:Dataset ;
+ prov:has_query_service <http://example.org/provenance/> .</pre>
+ <p>
+ The RDF service description example in <a href="#service-description-example" class="sectionRef sec-ref">section 4.1.3 Service description example</a> shows use of the <code>prov:ServiceDescription</code> type.
+ </p>
+ </section>
+
+ </section>
+
+<!-- ==== Section 5 ===================================================================================== -->
+
+ <section id="provenance-pingback">
+ <!--OddPage--><h2><span class="secno">5. </span>Provenance pingback</h2>
+ <p>
+ This section describes a mechanism that may be used to discover related provenance information that the publisher of a resource does not otherwise know about; e.g. provenance describing how it is used after it has been created.
+ </p>
+ <p>
+ The mechanisms discussed in previous sections are primarily concerned with the publisher enabling access to known provenance about an entity, answering with questions such as:
+ </p>
+ <ul>
+ <li>what was this resource based upon?</li>
+ <li>how was it constructed?</li>
+ <li>who made it?</li>
+ <li>when was it made?</li>
+ </ul>
+ <p>
+ These questions can be opened up to consider provenance information created by unrelated third parties, like:
+ </p>
+ <ul>
+ <li>what new resources are based on this resource?</li>
+ <li>what has this resource been used for?</li>
+ <li>who has used it?</li>
+ <li>what other resources are derived from the same sources as this resource?
+ </li></ul>
+ <p>
+ The ability to answer such broader questions requires some cooperation among the parties who use a resource; for example, a consumer could report use directly to the publisher, or a search engine could discover and report downstream resource usage. To facilitate such cooperation, a resource publisher may receive provenance "ping-backs". (The mechanism described here is
+inspired by <a href="http://www.hixie.ch/specs/pingback/pingback" class="externalRef">blog pingbacks</a>, but avoids the need for XML-RPC and is specific for provenance records.)
+ </p>
+ <p>
+ A resource may have an associated provenance ping-back URI, which may be presented with references to provenance about the resource. The ping-back URI is associated with a resource using mechanisms similar to those used for presenting a <a class="internalDFN" href="#dfn-provenance-uri">provenance-URI</a>, but using a <code>prov:pingback</code> link relation instead of <code>prov:has_provenance</code>. A consumer of the resource, or some other system, may perform an HTTP POST operation to the pingback URI, with a request body containing a list of provenance-URIs for provenance records describing uses of the resource.
+ </p>
+ <p>
+ For example, consider a resource that is published by <code>acme.example.com</code>, and is subsequently used by <code>coyote.example.org</code> in the construction of some new entity; we might see an exchange along the following lines. We start with <code>coyote.example.org</code> retrieving a copy of <code>acme.example.org</code>'s resource:
+ </p>
+ <div class="example"><div class="example-title"><span>Example 11</span></div><pre class="example code">C: GET http://acme.example.org/super-widget123 HTTP/1.1
+
+S: 200 OK
+S: Link: <http://acme.example.org/super-widget123/provenance>;
+ rel="http://www.w3.org/ns/prov#has_provenance"
+S: Link: <http://acme.example.org/super-widget123/pingback>;
+ rel="http://www.w3.org/ns/prov#pingback"
+ :
+(super-widget123 resource data)</pre></div>
+ <p>
+ The first of the links in the response is a <code>has_provenance</code> link with a <a class="internalDFN" href="#dfn-provenance-uri">provenance-URI</a> that has been described previously (<a href="#resource-accessed-by-http" class="sectionRef sec-ref">section 3.1 Resource accessed by HTTP</a>). The second is a distinct resource that exists to receive provenance pingbacks. Later, when a new resource has been created or some related action performed based upon the <code>acme.example.org/super-widget123</code>, a client may post a pingback request to the supplied <code>pingback</code> URI:
+ </p>
+ <div class="example"><div class="example-title"><span>Example 12</span></div><pre class="example code">C: POST http://acme.example.org/super-widget123/pingback HTTP/1.1
+C: Content-Type: text/uri-list
+C:
+C: http://coyote.example.org/contraption/provenance
+C: http://coyote.example.org/another/provenance
+
+S: 204 No Content</pre></div>
+ <p>
+ The pingback request supplies a list of <a class="internalDFN" href="#dfn-provenance-uri">provenance-URI</a>s from which additional provenance may be retrieved. The pingback service may do as it chooses with these URIs; e.g., it may choose to save them for later use, to retrieve the associated provenance and save that, to publish the URIs along with other provenance information about the original entity to which they relate, or even to ignore them.
+ </p>
+ <p>
+ There is no required information in the server response to a pingback POST request.
+ In the examples here, the pingback service responds positively with <code>204 No Content</code> and an empty response body. Other HTTP status values like <code>200 OK</code>, <code>201 Created</code>, <code>202 Accepted</code>, and <code>303 See Other</code> might also be appropriate positive responses depending on the domain and application.
+ </p>
+ <p>
+ The only defined operation on a pingback-URI is POST, which supplies links to provenance information or services as described above. A pingback-URI <em class="rfc2119" title="MAY">MAY</em> respond to other requests, but no requirements are imposed on how it responds. In particular, it is not specified here how a pingback resource should respond to an HTTP GET request.
+ </p>
+ <p>
+ The pingback client <em class="rfc2119" title="MAY">MAY</em> include extra <code>has_provenance</code> links to indicate provenance records related to a different resources, specified with correspondingly different anchor URIs. These <em class="rfc2119" title="MAY">MAY</em> indicate further provenance about existing resources, or about new resources (such as new entities derived or specialized from that for which the pingback URI was provided). For example:
+ </p>
+ <div class="example"><div class="example-title"><span>Example 13</span></div><pre class="example code">C: POST http://acme.example.org/super-widget123/pingback HTTP/1.1
+C: Link: <http://coyote.example.org/extra/provenance>;
+ rel="http://www.w3.org/ns/prov#has_provenance";
+ anchor="http://acme.example.org/extra-widget"
+C: Content-Type: text/uri-list
+C:
+C: http://coyote.example.org/contraption/provenance
+C: http://coyote.example.org/another/provenance
+C: http://coyote.example.org/extra/provenance
+
+S: 204 No Content</pre></div>
+ <p>
+ The client <em class="rfc2119" title="MAY">MAY</em> also supply <code>has_query_service</code> links indicating provenance query services that can describe the target-URI. The anchor <em class="rfc2119" title="MUST">MUST</em> be included, and <em class="rfc2119" title="SHOULD">SHOULD</em> be either the target-URI of the resource for which the pingback URI was provided (from the examples above, that would be <code>http://acme.example.org/super-widget123</code>), or some related resource with relevant provenance. For example:
+ </p>
+ <div class="example"><div class="example-title"><span>Example 14</span></div><pre class="example code">C: POST http://acme.example.org/super-widget123/pingback HTTP/1.1
+C: Link: <http://coyote.example.org/sparql>;
+ rel="http://www.w3.org/ns/prov#has_query_service";
+ anchor="http://acme.example.org/super-widget123"
+C: Content-Type: text/uri-list
+C: Content-Length: 0
+C:
+
+S: 204 No Content</pre></div>
+ <p>
+ Here, the pingback client has supplied a query service URI, but did not submit any provenance-URIs and the URI list is therefore empty. The <code>Link</code> header field indicates that the resource <code>http://acme.example.org/super-widget123/provenance</code> contains provenance information relating to <code>http://acme.example.org/super-widget123</code> (that being the URI of the resource for which the pingback URI was provided).
+ </p>
+
+ <!-- also in Stian's proposal
+
+ The pingback service MAY resolve the submitted URIs to validate and
+ check the provenance data, however reasonable care should be taken to
+ prevent malicious use of the pingback service for attacks such as
+ distributed denial of service (DDoS) and cross-site request forgery
+ (CSRF).
+
+ The server MAY, immediately or at a later time, include the submitted
+ *provenance-URI*s in responses to subsequent request to the provenance
+ service for the target-URI. (insert usual blurb about not trust on
+ such provenance)
+
+ The server SHOULD include a self-referential prov:pingback Link
+ header, which MUST include the anchor for the target-URI this pingback
+ service corresponds to. This serves the purpose for the client to
+ verify it has submitted a pingback to the correct service, in case it
+ has followed an untrusted prov:pingback Link header. The client MAY
+ for this purpose POST an empty text/uri-list to avoid side effects.
+
+ The server SHOULD indicate immediate acceptance by including the
+ corresponding {prov:has_provenance} {Link} headers for the accepted
+ *provenance-URI*s. If all submitted provenance-URIs have been
+ immediately accepted, the server SHOULD respond with HTTP status {200
+ OK} or {204 No Content}.
+
+ If server acceptance is pending for any of the submitted URIs, for
+ instance because the provenance-URIs are being validated or due to be
+ approved by a moderator, the server SHOULD respond with HTTP status
+ {202 Accepted}, and only include corresponding {prov:has_provenance}
+ {Link} headers for those provenance-URIs that have been immediately
+ accepted.
+
+ The server MAY respond with {401 Unauthorized} and standard
+ {{WWW-Authenticate}} headers if authentication is needed. The server
+ SHOULD respond with {403 Forbidden} if for any reason it refuses to
+ accept one or more of the submitted provenance-URIs or
+ provenance-service-URIs. If some URIs were accepted, but others were
+ refused, the server SHOULD respond with {403 Forbidden} and include
+ generated prov:has_provenance and prov:has_query_service Link headers for
+ the immediately accepted URIs.
+
+ -->
+
+
+ </section>
+
+<!-- ==== Section 6 ===================================================================================== -->
+
+ <section id="security-considerations">
+ <!--OddPage--><h2><span class="secno">6. </span>Security considerations</h2>
+ <p>
+ Provenance is central to establishing trust in data. If provenance is corrupted, it may lead agents (human or software) to draw inappropriate and possibly harmful conclusions. Therefore, care is needed to ensure that the integrity of provenance is maintained. Just as provenance can help determine a level of trust in some information, a provenance record related to the provenance itself ("provenance of provenance") can help determine trust in the provenance.
+ </p>
+ <p>
+ The <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec15.html" class="externalRef">HTTP security considerations</a> [<cite><a class="bibref" href="#bib-HTTP11">HTTP11</a></cite>] generally apply for all of the resources and services located through the mechanism in this document.
+ </p>
+ <p>
+ Secure HTTP (https) <em class="rfc2119" title="SHOULD">SHOULD</em> be used across unsecured networks when accessing provenance that may be used as a basis for trust decisions, or to obtain a provenance URI for same.
+ </p>
+ <p>
+ When retrieving a provenance URI from a document, steps <em class="rfc2119" title="SHOULD">SHOULD</em> be taken to ensure the document itself is an accurate copy of the original whose author is being trusted (e.g. signature checking, or use of a trusted secure web service). (See also <a class="sectionRef sec-ref" href="#interpreting-provenance-records">section 1.3 Interpreting provenance records</a>.)
+ </p>
+ <p>
+ Provenance may present a route for leakage of privacy-related information, combining as it does a diversity of information types with possible personally-identifying information; e.g. editing timestamps may provide clues to the working patterns of document editors, or derivation traces might indicate access to sensitive materials. In particular, note that the fact that a resource is openly accessible does not mean that its provenance should also be. When publishing provenance, its sensitivity <em class="rfc2119" title="SHOULD">SHOULD</em> be considered and appropriate access controls applied where necessary. When a provenance-aware publishing service accepts some resource for publication, the contributors <em class="rfc2119" title="SHOULD">SHOULD</em> have some opportunity to review and correct or conceal any provenance that they don't wish to be exposed. Provenance management systems <em class="rfc2119" title="SHOULD">SHOULD</em> embody mechanisms for enforcement and auditing of privacy policies as they apply to provenance. Implementations <em class="rfc2119" title="MAY">MAY</em> choose to use standard HTTP authorization mechanisms to restrict access to resources, returning <code>401 Unauthorized</code>, <code>403 Forbidden</code> or <code>404 Not Found</code> as appropriate.
+ </p>
+ <p>Provenance may be used by audits to establish accountability for information use [<cite><a class="bibref" href="#bib-INFO-ACC">INFO-ACC</a></cite>] and to verify use of proper processes in information processing activities. Thus, provenance management systems can provide mechanisms to support auditing and enforcement of information handling policies. In such cases, provenance itself may be a valuable target for attack by malicious agents, and care must be taken to ensure it is stored securely and in a fashion that resists attempts to tamper with it.
+ </p>
+ <p>
+ The pingback service described in <a href="#provenance-pingback" class="sectionRef sec-ref">section 5. Provenance pingback</a> might be abused for "link spamming" (similar to the way that weblog ping-backs have been used to direct viewers to spam sites). As with many such services, an application needs to find a balance between maintaining ease of submission for useful information and blocking unwanted information. We have no easy solutions for this problem, and the caveats noted above about establishing integrity of provenance records apply similarly to information provided by ping-back calls.
+ </p>
+ <p>
+ When clients and servers are retrieving submitted URIs such as provenance descriptions and following or registering links; reasonable care should be taken to prevent malicious use such as distributed denial of service attacks (DDoS), cross-site request forgery (CSRF), spamming and hosting of inappropriate materials. Reasonable preventions might include same-origin policy, HTTP authorization, SSL, rate-limiting, spam filters, moderation queues, user acknowledgements and validation. It is out of scope for this document to specify how such mechanisms work and should be applied.
+ </p>
+ <p>
+ Provenance pingback uses an HTTP POST operation, which may be used for non-"safe" interactions in the sense of [<cite><a class="bibref" href="#bib-WEBARCH">WEBARCH</a></cite>] (<a href="http://www.w3.org/TR/2004/REC-webarch-20041215/#safe-interaction" class="externalRef">section 3.4</a>). Care needs to be taken that user agents are not tricked into POSTing to incorrect URIs in such a way that may incur unintended effects or obligations. For example, a malicious site may present a pingback URI that executes an instruction on a different web site. Risks of such abuse may be mitigated by: performing pingbacks only to URIs from trusted sources; performing pingbacks only to the same origin as the provider of the pingback URI (like in-browser javascript same-origin restrictions), not sending credentials with pingback requests that were not obtained specifically for that purpose, and any other measures that may be appropriate.
+ </p>
+ <p>Accessing provenance services might reveal to the service and third-parties information which is considered private, including which resources a client has taken interest in. For instance, a browser extension which collects all provenance data for a resource which is being saved to the local disk, could be revealing user interest in a sensitive resource to a third-party site listed by <code>prov:has_provenance</code> or <code>prov:has_query_service</code> relation. A detailed query submitted to a third-party provenance query service might be revealing personal information such as social security numbers. Accordingly, user agents in particular <em class="rfc2119" title="SHOULD NOT">SHOULD NOT</em> follow provenance and provenance service links without first obtaining the user's explicit permission to do so.
+ </p>
+ </section>
+
+<!-- ===================================================================================== -->
+
+ <section class="appendix" id="acknowledgements">
+ <!--OddPage--><h2><span class="secno">A. </span>Acknowledgements</h2>
+ <p>
+ The editors acknowledge the contribution and review from members of the <abbr title="World Wide Web Consortium">W3C</abbr> Provenance working group for their feedback throughout the development of this specification.
+ </p>
+ <p>
+ Thanks to Erik Wilde and other members of the <abbr title="World Wide Web Consortium">W3C</abbr> Linked Data Platform working group for an extended discussion of REST service design issues, which has informed some aspects of the provenance service mechanisms.
+ </p>
+ <p>
+ Thanks to Robin Berjon for making our lives easier with his <a href="http://dev.w3.org/2009/dap/ReSpec.js/documentation.html" class="externalRef">ReSpec</a> tool.
+ </p>
+ <p>
+Members of the PROV Working Group at the time of publication of this document were:
+
+Ilkay Altintas (Invited expert),
+Reza B'Far (Oracle Corporation),
+Khalid Belhajjame (University of Manchester),
+James Cheney (University of Edinburgh, School of Informatics),
+Sam Coppens (iMinds - Ghent University),
+David Corsar (University of Aberdeen, Computing Science),
+Stephen Cresswell (The National Archives),
+Tom De Nies (iMinds - Ghent University),
+Helena Deus (DERI Galway at the National University of Ireland, Galway, Ireland),
+Simon Dobson (Invited expert),
+Martin Doerr (Foundation for Research and Technology - Hellas(FORTH)),
+Kai Eckert (Invited expert),
+Jean-Pierre EVAIN (European Broadcasting Union, EBU-UER),
+James Frew (Invited expert),
+Irini Fundulaki (Foundation for Research and Technology - Hellas(FORTH)),
+Daniel Garijo (Ontology Engineering Group, Universidad Politécnica de Madrid, Spain),
+Yolanda Gil (Invited expert),
+Ryan Golden (Oracle Corporation),
+Paul Groth (Vrije Universiteit),
+Olaf Hartig (Invited expert),
+David Hau (National Cancer Institute, NCI),
+Sandro Hawke (<abbr title="World Wide Web Consortium">W3C</abbr>/<abbr title="Massachusetts Institute of Technology">MIT</abbr>),
+Jörn Hees (German Research Center for Artificial Intelligence (DFKI) Gmbh),
+Ivan Herman, (<abbr title="World Wide Web Consortium">W3C</abbr>/<abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr>),
+Ralph Hodgson (TopQuadrant),
+Hook Hua (Invited expert),
+Trung Dong Huynh (University of Southampton),
+Graham Klyne (University of Oxford),
+Michael Lang (Revelytix, Inc.),
+Timothy Lebo (Rensselaer Polytechnic Institute),
+James McCusker (Rensselaer Polytechnic Institute),
+Deborah McGuinness (Rensselaer Polytechnic Institute),
+Simon Miles (Invited expert),
+Paolo Missier (School of Computing Science, Newcastle university),
+Luc Moreau (University of Southampton),
+James Myers (Rensselaer Polytechnic Institute),
+Vinh Nguyen (Wright State University),
+Edoardo Pignotti (University of Aberdeen, Computing Science),
+Paulo da Silva Pinheiro (Rensselaer Polytechnic Institute),
+Carl Reed (Open Geospatial Consortium),
+Adam Retter (Invited Expert),
+Christine Runnegar (Invited expert),
+Satya Sahoo (Invited expert),
+David Schaengold (Revelytix, Inc.),
+Daniel Schutzer (FSTC, Financial Services Technology Consortium),
+Yogesh Simmhan (Invited expert),
+Stian Soiland-Reyes (University of Manchester),
+Eric Stephan (Pacific Northwest National Laboratory),
+Linda Stewart (The National Archives),
+Ed Summers (Library of Congress),
+Maria Theodoridou (Foundation for Research and Technology - Hellas(FORTH)),
+Ted Thibodeau (OpenLink Software Inc.),
+Curt Tilmes (National Aeronautics and Space Administration),
+Craig Trim (IBM Corporation),
+Stephan Zednik (Rensselaer Polytechnic Institute),
+Jun Zhao (University of Oxford),
+Yuting Zhao (University of Aberdeen, Computing Science).
+</p>
+ </section>
+
+<!-- ===================================================================================== -->
+
+ <section class="appendix" id="terms-added-to-prov-namespace">
+ <!--OddPage--><h2 id="prov-namespace"><span class="secno">B. </span>Terms added to prov: namespace</h2>
+
+ <p>
+ This specification defines the following additional names in the provenance namespace
+ with URI <a href="http://www.w3.org/ns/prov#" class="externalRef">http://www.w3.org/ns/prov#</a>.
+ </p>
+ <table>
+ <tbody><tr>
+ <th>Name</th><th>Description</th><th>Definition ref</th>
+ </tr>
+ <tr style="vertical-align: top;">
+ <td><code>ServiceDescription</code></td>
+ <td>Type for a generic provenance query service. Mainly for use in RDF provenance query service descriptions, to facilitate discovery in linked data environments.</td>
+ <td><a href="#provenance-query-service-discovery" class="sectionRef sec-ref">section 4.3 Provenance query service discovery</a></td>
+ </tr>
+ <tr style="vertical-align: top;">
+ <td><code>DirectQueryService</code></td>
+ <td>Type for a direct HTTP query service description. Mainly for use in RDF provenance query service descriptions, to distinguish direct HTTP query service descriptions from other query service descriptions.</td>
+ <td><a href="#direct-http-query-service-description" class="sectionRef sec-ref">section 4.1.1 Direct HTTP query service description</a></td>
+ </tr>
+ <tr style="vertical-align: top;">
+ <td><code>has_anchor</code></td>
+ <td>Indicates a <a class="internalDFN" href="#dfn-target-uri">target-URI</a> for an resource, used by an associated provenance record.</td>
+ <td><a href="#resource-represented-as-html" class="sectionRef sec-ref">section 3.2 Resource represented as HTML</a>, <a href="#resource-represented-as-rdf" class="sectionRef sec-ref">section 3.3 Resource represented as RDF</a></td>
+ </tr>
+ <tr style="vertical-align: top;">
+ <td><code>has_provenance</code></td>
+ <td>Indicates a <a class="internalDFN" href="#dfn-provenance-uri">provenance-URI</a> for a resource; the resource identified by this property presents a provenance record about its subject or anchor resource.
+ </td>
+ <td><a href="#resource-accessed-by-http" class="sectionRef sec-ref">section 3.1 Resource accessed by HTTP</a>, <a href="#resource-represented-as-html" class="sectionRef sec-ref">section 3.2 Resource represented as HTML</a></td>
+ </tr>
+ <tr style="vertical-align: top;">
+ <td><code>has_query_service</code></td>
+ <td>Indicates a <a class="internalDFN" href="#dfn-provenance-query-service">provenance query service</a> that can access provenance related to its subject or anchor resource.</td>
+ <td><a href="#specifying-provenance-query-services" class="sectionRef sec-ref">section 3.1.1 Specifying Provenance Query Services</a></td>
+ </tr>
+ <tr style="vertical-align: top;">
+ <td><code>describesService</code></td>
+ <td>relates a generic provenance query service resource (type <code>prov:ServiceDescription</code>) to a specific query service description (e.g. a <code>prov:DirectQueryService</code> or a <code>sd:Service</code>).</td>
+ <td><a href="#provenance-query-service-description" class="sectionRef sec-ref">section 4.1 Provenance query service description</a></td>
+ </tr>
+ <tr style="vertical-align: top;">
+ <td><code>provenanceUriTemplate</code></td>
+ <td>Indicates a URI template string for constructing provenance-URIs</td>
+ <td><a href="#direct-http-query-service-description" class="sectionRef sec-ref">section 4.1.1 Direct HTTP query service description</a></td>
+ </tr>
+ <tr style="vertical-align: top;">
+ <td><code>pingback</code></td>
+ <td>Relates a resource to a provenance pingback service that may receive additional provenance links about the resource.</td>
+ <td><a href="#provenance-pingback" class="sectionRef sec-ref">section 5. Provenance pingback</a></td>
+ </tr>
+
+ <!--
+ <tr style="vertical-align: top;">
+ <td><code>...</code></td>
+ <td>...</td>
+ <td><a href="#..." class="sectionRef"></a></td>
+ </tr>
+ <tr style="vertical-align: top;">
+ <td><code>...</code></td>
+ <td>...</td>
+ <td><a href="#..." class="sectionRef"></a></td>
+ </tr>
+ <tr style="vertical-align: top;">
+ <td><code>...</code></td>
+ <td>...</td>
+ <td><a href="#..." class="sectionRef"></a></td>
+ </tr>
+ -->
+
+ </tbody></table>
+
+ <p>
+ The ontology describing these terms is available <a href="http://www.w3.org/ns/prov-aq" class="externalRef">here</a>.
+ </p>
+
+
+ </section>
+
+<!-- ===================================================================================== -->
+
+<!--
+
+ <section class='appendix'>
+ <h2>Changes log</h2>
+
+ <p class=TODO>
+ Always update copy of mercurial change log in review copies.<br/>
+ Remove this section on final publication.
+ </p>
+
+ <section>
+ <h2>Changes since 20130312 publication</h2>
+ hg log -r tip:b665bc9447ce \
+ - -template "<dt>{date|isodate} {node|short} {author}</dt><dd>{desc}</dd>\n" \
+ prov-aq.html
+ <dl>
+<dt>2013-04-12 12:07 +0100 dae5268c75c0 Graham Klyne</dt><dd>Add some text clarifying that pingback provenance may be about new entities; result of dereferencing 'target-URI' not specified</dd>
+<dt>2013-04-12 11:32 +0100 a89cc91fa022 Graham Klyne</dt><dd>Remove 'at risk' note from section on pingback</dd>
+<dt>2013-04-12 11:31 +0100 318ae02bca82 Graham Klyne</dt><dd>Change example URIs in pingback description to make it clearer they are instances (e.g. http://acme.example.org/super-widget123)</dd>
+<dt>2013-04-08 10:33 +0100 3ddca8678084 Graham Klyne</dt><dd>Update change log</dd>
+<dt>2013-04-08 10:30 +0100 2de1db892bfc Graham Klyne</dt><dd>Various editorial fixes; drop note about possibility of service document description from LDP WG.</dd>
+<dt>2013-04-05 18:20 +0100 8b6a3e6e27c8 Graham Klyne</dt><dd>Additions and TODO in acknowledgements section.</dd>
+<dt>2013-04-05 18:15 +0100 2072b00f4563 Graham Klyne</dt><dd>Fix typo</dd>
+<dt>2013-04-05 18:11 +0100 04c325fb6e36 Graham Klyne</dt><dd>Update change log</dd>
+<dt>2013-04-05 18:10 +0100 eb85bfc53e09 Graham Klyne</dt><dd>Many editorial fixes suggested by Stian; add RFC2119 reference; revised service description examples and text; update SPARQL-SD reference; some re-organization and cross-linking of material relating to direct HTTP query service description and invocation; clean up description of URI template handling; dropped suggestion of escaping '#', etc. in target-URIs used with templates; updated pingback examples; dropped Link: headers from pingback responses in examples; some re-working of pingback description and examples; updated security considerations, esp. concern of POST to maliciously provided pingback URI</dd>
+<dt>2013-04-05 14:17 +0100 41eaac306f75 Graham Klyne</dt><dd>Updated examples and clarified description of pingback; removed 'third working draft' paragraph; moved note about handling of anchors in HTTP vs HTML/RDF; changed URIs in examples to make them more recognizable as instances</dd>
+<dt>2013-03-26 21:45 +0000 b223c6898726 Graham Klyne</dt><dd>Fix cross-references to provenance-pingbacks</dd>
+<dt>2013-03-26 20:17 +0000 0dcbb7275a70 Graham Klyne</dt><dd>Update change log</dd>
+<dt>2013-03-26 20:15 +0000 4c62e1f97edd Graham Klyne</dt><dd>First draft of changes to remove directionality of provenance pingback (previously described as forward provenance)</dd>
+<dt>2013-03-25 16:15 +0000 cd9d155c1be3 Graham Klyne</dt><dd>Allow publish date to 'float' for mworking copy</dd>
+<dt>2013-03-25 16:12 +0000 5389846eaf90 Graham Klyne</dt><dd>Merge</dd>
+<dt>2013-03-25 16:11 +0000 bb6113fa4e67 Graham Klyne</dt><dd>Clean up TODO flags</dd>
+<dt>2013-03-25 15:48 +0000 700014e20954 Graham Klyne</dt><dd>Add note in section 3 to acknowledge ISSUE-628 (but no substantive change)</dd>
+<dt>2013-03-25 15:30 +0000 4f3bbad454f0 Graham Klyne</dt><dd>Tune service description text to make it clear that service descriptions other than RDF are OK</dd>
+<dt>2013-03-25 15:21 +0000 b665bc9447ce Graham Klyne</dt><dd>Revised description of recommended provenance formats per WG discussion. Added reference to HTTP 1.1 spec.</dd>
+ </dl>
+ </section>
+
+ <section>
+ <h2>Changes since 20120619 publication</h2>
+
+ hg log -r tip:d0af0446868d \
+ - -template "<dt>{date|isodate} {node|short} {author}</dt><dd>{desc}</dd>\n" \
+ prov-aq.html
+
+ <dl>
+<dt>2013-02-27 16:23 +0000 35385cbbfb9f Graham Klyne</dt><dd>Further refinements and bug fixes in the forward provenance section</dd>
+<dt>2013-02-27 15:33 +0000 2dfd7fac85c9 Graham Klyne</dt><dd>Merge</dd>
+<dt>2013-02-27 15:19 +0000 bae275eaaf81 Stian Soiland-Reyes</dt><dd>Added Stian as PROV-AQ author</dd>
+<dt>2013-02-27 15:33 +0000 ecf3af571f1e Graham Klyne</dt><dd>Changed entity-URI back to target-URI, and updated concept definition to indicate it may also denote an activity</dd>
+<dt>2013-02-27 13:02 +0000 d6085196a22d Graham Klyne</dt><dd>Some tidying up of section decsribing provenance pingback</dd>
+<dt>2013-02-27 12:26 +0000 018e25f63183 Graham Klyne</dt><dd>Changed all normative references to informative (this being a NOTE)</dd>
+<dt>2013-02-27 12:23 +0000 33eea34f1863 Graham Klyne</dt><dd>Renamed link relations 'hasProvenance', 'hasAnchor' and 'hasQueryService' to 'has_provenance', 'has_anchor' and 'has_query_service' respectively. This is because RFC5988 strongly recommends link relations to be all lowercase.</dd>
+<dt>2013-02-26 18:42 +0000 25eb1149862f Graham Klyne</dt><dd>Add placeholder links to ontology; deleted note in Appendiox B</dd>
+<dt>2013-02-26 18:33 +0000 473af1a90df2 Graham Klyne</dt><dd>Added describesService in appendix B</dd>
+<dt>2013-02-26 18:24 +0000 211ff39ee699 Graham Klyne</dt><dd>Add to security considerations: possible malicious use of links; possible information leakage when provenance links are folloiwed, or services used. (Stian:58,59)</dd>
+<dt>2013-02-26 18:12 +0000 ec95bc31a43b Graham Klyne</dt><dd>Incorporate Stian's revised pingback proposal: accept links rather than actual provenance.</dd>
+<dt>2013-02-26 17:19 +0000 eadbf7c04b31 Graham Klyne</dt><dd>Renamed prov:provPingback as just prov:pingback (Stian:55)</dd>
+<dt>2013-02-26 17:07 +0000 4fd6242c151c Graham Klyne</dt><dd>Re-worked description of direct HTTP query, particularly escaping of URI special characters and provenance formats returned. Revise description of return codes. (Section 4.2)</dd>
+<dt>2013-02-26 16:10 +0000 bbef7256bc91 Graham Klyne</dt><dd>Rename prov:ProvenanceQueryService to prov:ServiceDescription</dd>
+<dt>2013-02-26 15:53 +0000 206caf60d43a Graham Klyne</dt><dd>Incorporarted Stian's proposal for a service description property</dd>
+<dt>2013-02-26 14:40 +0000 ae119d2377ca Graham Klyne</dt><dd>Query service - editorial updates per Stian's comments 35-41, including re-work of motivation</dd>
+<dt>2013-02-26 13:34 +0000 1a0bded232fb Graham Klyne</dt><dd>Edirtorial updates in response to Luc's comments; updated CSS for external link</dd>
+<dt>2013-02-26 11:26 +0000 52d0f60610aa Graham Klyne</dt><dd>Editorial updates in response to comments by Dong</dd>
+<dt>2013-02-26 10:44 +0000 a87d5f3c056c Graham Klyne</dt><dd>Moved entire discussion of bundles in section 2 to a NOTE, and simplified.</dd>
+<dt>2013-02-26 10:24 +0000 fd2f1476c795 Graham Klyne</dt><dd>Further editorial changes suggestred by Stian's comments 28,29,30,33; quote anchor parameters in Link: header examples</dd>
+<dt>2013-02-21 19:16 +0000 2a38eacd1735 Graham Klyne</dt><dd>Section 3, editorial changes and reorganization of text suggested by Stian's comments (15,16,17,18,19,20,21,22,23,24,25,26,27). Moved some more material from sect 3 to sect 1.3, and trimmed. Removed duplicate material about authority guarantees from section 2. Added URI/IRI discussion to concepts. Added HTTP examples. Included '#' in shorthand references to link relations.</dd>
+<dt>2013-02-21 17:27 +0000 6c7dc767652a Graham Klyne</dt><dd>More trimming of material onprovenance interpretation</dd>
+<dt>2013-02-21 15:57 +0000 be8f6ec8a2d5 Graham Klyne</dt><dd>Section 3, editorial changes and reorganization of text suggested by Stian's comments (10,11,12,13,14). provider abnd consumer definitions moved to 1.1. Further discussion of provenance interpretation moved to section 1.3.</dd>
+<dt>2013-02-21 15:31 +0000 7e2c896d5b3b Graham Klyne</dt><dd>Section 2, non-substantive editorial changes suggested by Stian's comments (8,9)</dd>
+<dt>2013-02-21 15:22 +0000 9afefa103a72 Graham Klyne</dt><dd>Non-substantive editorial changes suggested by Stian's comments (4,6,7)</dd>
+<dt>2013-02-21 15:07 +0000 27cf75d7a6f2 Graham Klyne</dt><dd>Changed 'target-URI' to 'entity-URI', and revised some associated text to describe provenance access with respect to entities. Stian's comment (2)</dd>
+<dt>2013-02-21 14:06 +0000 cc0ec03fed0e Graham Klyne</dt><dd>Update Turtle reference to CR</dd>
+<dt>2013-02-21 13:33 +0000 2d42fb73e214 Graham Klyne</dt><dd>Add placeholder appendix for change log</dd>
+<dt>2013-02-07 18:26 +0000 ae85f08dcda4 Graham Klyne</dt><dd>Further editorial fixes suggested by Tim</dd>
+<dt>2013-02-07 17:43 +0000 266d233ce54c Graham Klyne</dt><dd>Move text about isolating information from section 3 (locating) to 1.3 (interpreting). Tim's comment (13)</dd>
+<dt>2013-02-07 17:29 +0000 a53fb5b58d8f Graham Klyne</dt><dd>Section 2 editorial rework including suggestions by Tim</dd>
+<dt>2013-02-07 16:41 +0000 cf11871bb9ba Graham Klyne</dt><dd>Editorial fixes suggested by Tim, and replace 'provenance description' with 'provenance record', following PROV-DM</dd>
+<dt>2013-02-07 15:53 +0000 4d16b451fc1a Graham Klyne</dt><dd>Editorial fixes suggested by Simon</dd>
+<dt>2013-02-07 15:42 +0000 9406759adad3 Graham Klyne</dt><dd>Editorial fixes suggested by Simon</dd>
+<dt>2013-02-07 14:50 +0000 d5e7a0c76495 Graham Klyne</dt><dd>Minor editorial fixes suggested by Ivan</dd>
+<dt>2013-02-07 13:44 +0000 d4cf95c11dcd Graham Klyne</dt><dd>Minor editorial fixes suggested by Ivan</dd>
+<dt>2013-01-10 15:43 +0100 cb49c07522ff Paul Groth </dt><dd>updated to fix minor editorial errors</dd>
+<dt>2013-01-04 14:23 +0000 47a1f3baf67a Graham Klyne</dt><dd>Editorial tweaks</dd>
+<dt>2013-01-04 13:26 +0000 a374c48027b9 Graham Klyne</dt><dd>Separate prov:DirectQueryService (specifric mechanism) from prov:ProvenanceQueryService (generic)</dd>
+<dt>2013-01-04 13:11 +0000 7b4580bd6d52 Graham Klyne</dt><dd>Fix some section cross-references; rename 'prov:hasProvenanceService' as 'prov:hasQueryService'</dd>
+<dt>2013-01-04 13:03 +0000 f00efdbb4f6e Graham Klyne</dt><dd>Reorganize provenance query service description to accommodate SPARQL (ISSUE 601); 'rename provenance service' as 'provenance query service'; rename 'prov:ProvenanceService' as 'prov:ProivenanceQueryService'</dd>
+<dt>2012-12-10 22:40 +0000 08deb1462a7c Graham Klyne</dt><dd>Fix apostrophe</dd>
+<dt>2012-12-10 19:03 +0000 f0f315c6781c Graham Klyne</dt><dd>Fold in Jun's editorial comments. Remove reference to POWDER</dd>
+<dt>2012-11-26 14:43 +0000 23f86dc89992 Graham Klyne</dt><dd>Change 'provenance information' to 'provenance description' (ISSUE 601); extensive editorial changes should be reviewed</dd>
+<dt>2012-11-26 12:07 +0000 4bbf03ed4eff Graham Klyne</dt><dd>Add note about service description and LDP consideration thereof</dd>
+<dt>2012-11-26 11:49 +0000 72ec0c88ede8 Graham Klyne</dt><dd>Add non-commital paragraph about accessing provenance bundles</dd>
+<dt>2012-11-26 11:08 +0000 b811ccb53b45 Graham Klyne</dt><dd>Update forward provenance (pingback) in response to comments; fix text around VoID example</dd>
+<dt>2012-11-20 16:00 +0000 839d503bd064 Graham Klyne</dt><dd>Added specification for pingback link header (ISSUE 600)</dd>
+<dt>2012-11-20 14:15 +0000 0e668b4ce436 Graham Klyne</dt><dd>Tidy up some text</dd>
+<dt>2012-11-20 14:03 +0000 3cba6f76b797 Graham Klyne</dt><dd>Expanded discussion of provenance service discovery to include prov:hasProvenanceService</dd>
+<dt>2012-11-20 12:22 +0000 44586518f842 Graham Klyne</dt><dd>Remove speculative non-specification text to be covered in FAQ (ISSUES 426, 598)</dd>
+<dt>2012-11-20 11:36 +0000 2f1a8ca558a8 Graham Klyne</dt><dd>Added section with table of URIs and what they dereference to (ISSUE 424)</dd>
+<dt>2012-11-20 10:37 +0000 d2acceb63c0b Graham Klyne</dt><dd>Make treatment of direct retrieval and service for provenance access more equally visible (ISSUE 422)</dd>
+<dt>2012-11-19 18:53 +0000 69d2ba847f40 Graham Klyne</dt><dd>Point out that provenance services can accept paraneters other than just 'target' (ISSUE 420)</dd>
+<dt>2012-11-19 18:10 +0000 6a283fe7b70c Graham Klyne</dt><dd>Added definitions for accessung and locating (ISSUE 417)</dd>
+<dt>2012-11-19 13:23 +0000 45683a007809 Graham Klyne</dt><dd>More CSS tweaking to override RewSopec.js colouring</dd>
+<dt>2012-11-19 13:06 +0000 390df423d8b3 Graham Klyne</dt><dd>Formatting and CSS colour tweaks for examples</dd>
+<dt>2012-11-19 12:58 +0000 7f6c1a541631 Graham Klyne</dt><dd>Added section on Link: headers and content negotiation (ISSUE 416)</dd>
+<dt>2012-11-19 12:17 +0000 9c24773fd6c7 Graham Klyne</dt><dd>Revert to W3C-hosted ReSpec.js</dd>
+<dt>2012-11-19 11:48 +0000 10c290a46ee0 Graham Klyne</dt><dd>Added icon to distibguish external links (ISSUE 400)</dd>
+<dt>2012-11-16 16:29 +0000 5f35560288e7 Graham Klyne</dt><dd>Updsate and cross-link table of prov: URIs defined</dd>
+<dt>2012-11-16 16:01 +0000 3144d9093733 Graham Klyne</dt><dd>Changed link relations to URIs; removed IANA considerations section</dd>
+<dt>2012-11-10 19:03 +0000 77c849e3d67d Graham Klyne</dt><dd>Hyperlink concept definitions to themselves (per request from Tim 2012-06-05)</dd>
+<dt>2012-11-10 18:26 +0000 aff3d2fcf8f5 Graham Klyne</dt><dd>Update security considerations with note about use of provenance as part of audit/enforcement mechanism</dd>
+<dt>2012-11-10 18:07 +0000 84864eeceffb Graham Klyne</dt><dd>Update list of PROV documents, copied from PROV-DM</dd>
+<dt>2012-11-10 02:08 +0000 beb278a59b28 Graham Klyne</dt><dd>Revert JS import to W3C server</dd>
+<dt>2012-11-08 22:36 +0000 35ee2d7209ea Graham Klyne</dt><dd>Adjust TODO notes</dd>
+<dt>2012-11-08 22:27 +0000 d269fcdfc9fd Graham Klyne</dt><dd>Cut back on verbiage in sect 3,4 rbitrary data</dd>
+<dt>2012-11-08 22:24 +0000 aba651f6da5e Graham Klyne</dt><dd>Adjust TODO notes</dd>
+<dt>2012-11-08 22:20 +0000 06627e013264 Graham Klyne</dt><dd>Revised section 3 descriptions in terms of prodcuers and consumers</dd>
+<dt>2012-11-08 12:12 +0000 098e7be8b4d5 Graham Klyne</dt><dd>Updated security considerations to mention audit</dd>
+<dt>2012-11-06 17:04 +0000 96247e20c8b4 Graham Klyne</dt><dd>Add TODO for producer/consumer roles, add note about multiple links, add reference to RFC3986 for %-escaping</dd>
+<dt>2012-11-06 15:17 +0000 4fbe51a47591 Graham Klyne</dt><dd>Update security considerations, note about non-RDF service desription, PROV-O link, acknowledgements</dd>
+<dt>2012-06-20 14:27 -0700 d0af0446868d Paul Groth</dt><dd>updated to reflect newly published version</dd>
+ </dl>
+ </section>
+ </section>
+-->
+
+<!-- ===================================================================================== -->
+
+
+
+<section id="references" class="appendix"><!--OddPage--><h2><span class="secno">C. </span>References</h2><section id="informative-references"><h3><span class="secno">C.1 </span>Informative references</h3><dl class="bibliography"><dt id="bib-HTTP11">[HTTP11]</dt><dd>R. Fielding et al. <a href="http://www.ietf.org/rfc/rfc2616.txt"><cite>Hypertext Transfer Protocol - HTTP/1.1</cite></a>. June 1999. RFC 2616. URL: <a href="http://www.ietf.org/rfc/rfc2616.txt">http://www.ietf.org/rfc/rfc2616.txt</a>
+</dd><dt id="bib-INFO-ACC">[INFO-ACC]</dt><dd>Weitzner, Abelson, Berners-Lee, Feigenbaum, Hendler, and Sussman. <a href="http://dig.csail.mit.edu/2008/06/info-accountability-cacm-weitzner.pdf"><cite>Information Accountability</cite></a>. Communications of the ACM, Jun. 2008, 82-87, <a href="http://doi.acm.org/10.1145/1349026.1349043">http://doi.acm.org/10.1145/1349026.1349043</a>, <a href="http://dig.csail.mit.edu/2008/06/info-accountability-cacm-weitzner.pdf">http://dig.csail.mit.edu/2008/06/info-accountability-cacm-weitzner.pdf</a> (alt)
+</dd><dt id="bib-LINK-REL">[LINK-REL]</dt><dd>M. Nottingham, <a href="http://www.ietf.org/rfc/rfc5988.txt"><cite>Web Linking</cite></a>, October 2010, Internet RFC 5988. URL: <a href="http://www.ietf.org/rfc/rfc5988.txt">http://www.ietf.org/rfc/rfc5988.txt</a>
+</dd><dt id="bib-PROV-CONSTRAINTS">[PROV-CONSTRAINTS]</dt><dd>James Cheney; Paolo Missier; Luc Moreau; eds. <a href="http://www.w3.org/TR/2013/REC-prov-constraints-20130430/"><cite>Constraints of the PROV Data Model</cite></a>. 30 April 2013, W3C Recommendation. URL: <a href="http://www.w3.org/TR/2013/REC-prov-constraints-20130430/">http://www.w3.org/TR/2013/REC-prov-constraints-20130430/</a>
+</dd><dt id="bib-PROV-DC">[PROV-DC]</dt><dd>Daniel Garijo; Kai Eckert; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/"><cite>Dublin Core to PROV Mapping</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/">http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/</a>
+</dd><dt id="bib-PROV-DICTIONARY">[PROV-DICTIONARY]</dt><dd>Tom De Nies; Sam Coppens; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><cite>PROV Dictionary: Modeling Provenance for Dictionary Data Structures</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/</a>
+</dd><dt id="bib-PROV-DM">[PROV-DM]</dt><dd>Luc Moreau; Paolo Missier; eds. <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/"><cite>PROV-DM: The PROV Data Model</cite></a>. 30 April 2013, W3C Recommendation. URL: <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/">http://www.w3.org/TR/2013/REC-prov-dm-20130430/</a>
+</dd><dt id="bib-PROV-LINKS">[PROV-LINKS]</dt><dd>Luc Moreau; Timothy Lebo; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-links-20130430/"><cite>Linking Across Provenance Bundles</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-links-20130430/">http://www.w3.org/TR/2013/NOTE-prov-links-20130430/</a>
+</dd><dt id="bib-PROV-N">[PROV-N]</dt><dd>Luc Moreau; Paolo Missier; eds. <a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/"><cite>PROV-N: The Provenance Notation</cite></a>. 30 April 2013, W3C Recommendation. URL: <a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/">http://www.w3.org/TR/2013/REC-prov-n-20130430/</a>
+</dd><dt id="bib-PROV-O">[PROV-O]</dt><dd>Timothy Lebo; Satya Sahoo; Deborah McGuinness; eds. <a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/"><cite>PROV-O: The PROV Ontology</cite></a>. 30 April 2013, W3C Recommendation. URL: <a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/">http://www.w3.org/TR/2013/REC-prov-o-20130430/</a>
+</dd><dt id="bib-PROV-OVERVIEW">[PROV-OVERVIEW]</dt><dd>Paul Groth; Luc Moreau; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/"><cite>PROV-OVERVIEW: An Overview of the PROV Family of Documents</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/">http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/</a>
+</dd><dt id="bib-PROV-PRIMER">[PROV-PRIMER]</dt><dd>Yolanda Gil; Simon Miles; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/"><cite>PROV Model Primer</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/">http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/</a>
+</dd><dt id="bib-PROV-SEM">[PROV-SEM]</dt><dd>James Cheney; ed. <a href="http://www.w3.org/TR/2013/NOTE-prov-sem-20130430"><cite>Semantics of the PROV Data Model</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-sem-20130430">http://www.w3.org/TR/2013/NOTE-prov-sem-20130430</a>.
+</dd><dt id="bib-PROV-XML">[PROV-XML]</dt><dd>Hook Hua; Curt Tilmes; Stephan Zednik; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/"><cite>PROV-XML: The PROV XML Schema</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/">http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/</a>
+</dd><dt id="bib-RDF-CONCEPTS11">[RDF-CONCEPTS11]</dt><dd>Richard Cyganiak, David Wood, eds. <a href="http://www.w3.org/TR/rdf11-concepts/"><cite>RDF 1.1 Concepts and Abstract Syntax</cite></a>. Working Draft. URL: <a href="http://www.w3.org/TR/rdf11-concepts/">http://www.w3.org/TR/rdf11-concepts/</a>
+</dd><dt id="bib-REST">[REST]</dt><dd>R. Fielding. <a href="http://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm"><cite>Representational State Transfer (REST)</cite></a>. 2000, Ph.D. dissertation. URL: <a href="http://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm">http://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm</a>
+</dd><dt id="bib-REST-APIs">[REST-APIs]</dt><dd>R. Fielding. <a href="http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven"><cite>REST APIs must be hypertext driven</cite></a>. October 2008 (blog post), URL: <a href="http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven">http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven</a>
+</dd><dt id="bib-RFC2119">[RFC2119]</dt><dd>S. Bradner. <a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>Key words for use in RFCs to Indicate Requirement Levels.</cite></a> March 1997. Internet RFC 2119. URL: <a href="http://www.ietf.org/rfc/rfc2119.txt">http://www.ietf.org/rfc/rfc2119.txt</a>
+</dd><dt id="bib-RFC2392">[RFC2392]</dt><dd>E. Levinson. <a href="http://www.ietf.org/rfc/rfc2392.txt"><cite>Content-ID and Message-ID Uniform Resource Locators.</cite></a> August 1998. Internet RFC 2392. URL: <a href="http://www.ietf.org/rfc/rfc2392.txt">http://www.ietf.org/rfc/rfc2392.txt</a>
+</dd><dt id="bib-RFC3986">[RFC3986]</dt><dd>T. Berners-Lee; R. Fielding; L. Masinter. <a href="http://www.ietf.org/rfc/rfc3986.txt"><cite>Uniform Resource Identifier (URI): Generic Syntax (RFC 3986)</cite></a>. January 2005. RFC. URL: <a href="http://www.ietf.org/rfc/rfc3986.txt">http://www.ietf.org/rfc/rfc3986.txt</a>
+</dd><dt id="bib-RFC3987">[RFC3987]</dt><dd>M. Dürst; M. Suignard. <a href="http://www.ietf.org/rfc/rfc3987.txt"><cite>Internationalized Resource Identifiers (IRIs) (RFC 3987)</cite></a>. January 2005. RFC. URL: <a href="http://www.ietf.org/rfc/rfc3987.txt">http://www.ietf.org/rfc/rfc3987.txt</a>
+</dd><dt id="bib-SPARQL-HTTP">[SPARQL-HTTP]</dt><dd>Chimezie Ogbuji. <a href="http://www.w3.org/TR/sparql11-http-rdf-update/"><cite>SPARQL 1.1 Graph Store HTTP Protocol</cite></a>. 21 March 2013, W3C Recommendation. URL: <a href="http://www.w3.org/TR/sparql11-http-rdf-update/">http://www.w3.org/TR/sparql11-http-rdf-update/</a>
+</dd><dt id="bib-SPARQL-SD">[SPARQL-SD]</dt><dd>G. T. Williams. <a href="http://www.w3.org/TR/sparql11-service-description/"><cite>SPARQL 1.1 Service Description</cite></a>. 21 March 2013, W3C Recommendation. URL: <a href="http://www.w3.org/TR/sparql11-service-description/">http://www.w3.org/TR/sparql11-service-description/</a>
+</dd><dt id="bib-TURTLE">[TURTLE]</dt><dd>Eric Prud'hommeaux, Gavin Carothers. <a href="http://www.w3.org/TR/turtle/"><cite>Turtle: Terse RDF Triple Language</cite></a>. 19 February 2013. W3C Candidate Recommendation. URL: <a href="http://www.w3.org/TR/turtle/">http://www.w3.org/TR/turtle/</a>
+</dd><dt id="bib-URI-template">[URI-template]</dt><dd>J. Gregorio; R. Fielding; M. Hadley; M. Nottingham; D. Orchard. <a href="http://tools.ietf.org/html/rfc6570"><cite>URI Template</cite></a>. March 2012, Internet RFC 6570. URL: <a href="http://tools.ietf.org/html/rfc6570/"><cite>http://tools.ietf.org/html/rfc6570</cite></a>
+</dd><dt id="bib-VoID">[VoID]</dt><dd>Keith Alexander, Richard Cyganiak, Michael Hausenblas, Jun Zhao. <a href="http://www.w3.org/TR/void/"><cite>Describing Linked Datasets with the VoID Vocabulary</cite></a>, W3C Interest Group Note 03 March 2011, <a href="http://www.w3.org/TR/void/">http://www.w3.org/TR/void/</a>
+</dd><dt id="bib-WEBARCH">[WEBARCH]</dt><dd>Norman Walsh; Ian Jacobs. <a href="http://www.w3.org/TR/2004/REC-webarch-20041215/"><cite>Architecture of the World Wide Web, Volume One</cite></a>. 15 December 2004. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2004/REC-webarch-20041215/">http://www.w3.org/TR/2004/REC-webarch-20041215/</a>
+</dd></dl></section></section></body></html>
\ No newline at end of file
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/paq/releases/NOTE-prov-aq-20130430/css/prov-aq.css Fri Apr 26 09:27:12 2013 +0100
@@ -0,0 +1,199 @@
+/* --- Override ReSpec.css --- */
+
+code {
+ color: #224433;
+}
+
+ /* Be more specific: above override doesn't work */
+p code {
+ font-family: monospace;
+ color: #224433;
+}
+
+div code {
+ font-family: monospace;
+ color: #224433;
+}
+
+
+/* --- PATTERNS --- */
+
+pre.pattern {
+ border-top: 1px solid #224433;
+ border-bottom: 1px solid #224433;
+ color: #224433;
+ padding: 1em;
+ margin-top: 1em;
+}
+
+pre.code {
+ color: #224433;
+}
+
+pre.example.code {
+ border-bottom: 1px solid #224433;
+ border-top: 1px solid #224433;
+ margin-top: 1em;
+ padding: 1em;
+}
+
+pre.example.code:before {
+ background: #224433;
+}
+
+/*
+pre.pattern::before {
+ content: "";
+ display: block;
+ width: 150px;
+ background: #224433;
+ color: #fff;
+ font-family: initial;
+ padding: 3px;
+ font-weight: bold;
+ margin: -1em 0 1em -1em;
+}
+*/
+
+
+/* --- EDITORIAL NOTES (from model doc) --- */
+
+.issue {
+ padding: 1em;
+ margin: 1em 0em 0em;
+ border: 1px solid #f00;
+ background: #ffc;
+}
+
+.issue:before {
+ content: "Issue";
+ display: block;
+ width: 150px;
+ margin: -1.5em 0 0.5em 0;
+ font-weight: bold;
+ border: 1px solid #f00;
+ background: #fff;
+ padding: 3px 1em;
+}
+
+.TODO {
+ padding: 1em;
+ margin: 1em 0em 0em;
+ border: 1px solid #f00;
+ background: #ffc;
+}
+
+.TODO:before {
+ content: "TODO";
+ display: block;
+ width: 150px;
+ margin: -1.5em 0 0.5em 0;
+ font-weight: bold;
+ border: 1px solid #f00;
+ background: #fff;
+ padding: 3px 1em;
+}
+
+.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: 0px 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;
+}
+
+/* --- Labelled value layout --- */
+
+div.label-value {
+ display: block;
+ position: relative;
+ left: 1em;
+ height: auto;
+}
+
+span.label {
+ display: inline-block;
+ vertical-align: top;
+ font-style: italic;
+ min-width: 20%;
+}
+
+span.value {
+ display: inline-block;
+ vertical-align: top;
+ width: 80%;
+ height: auto;
+}
+
+span.code {
+ font-family: monospace;
+}
+
+
+/* "Macro" for provns namespace */
+
+provns:before {
+ content: "http://www.w3.org/ns/prov#";
+ display: inline;
+ font-family: monospace;
+}
+
+/* External link. CSS and image data copied from wikimedia.org. Thanks!
+a.externalRef {
+background:url(data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAoAAAAKCAYAAACNMs+9AAAAVklEQVR4Xn3PgQkAMQhDUXfqTu7kTtkpd5RA8AInfArtQ2iRXFWT2QedAfttj2FsPIOE1eCOlEuoWWjgzYaB/IkeGOrxXhqB+uA9Bfcm0lAZuh+YIeAD+cAqSz4kCMUAAAAASUVORK5CYII=) center right no-repeat;
+background:url(images/external-link-ltr-icon.png) center right no-repeat!ie;padding-right:13px
+}
+*/
+
+
+/*a.externalRef:after {
+content:url(data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAoAAAAKCAYAAACNMs+9AAAAVklEQVR4Xn3PgQkAMQhDUXfqTu7kTtkpd5RA8AInfArtQ2iRXFWT2QedAfttj2FsPIOE1eCOlEuoWWjgzYaB/IkeGOrxXhqB+uA9Bfcm0lAZuh+YIeAD+cAqSz4kCMUAAAAASUVORK5CYII=);
+}*/
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/paq/releases/NOTE-prov-aq-20130430/diff.html Fri Apr 26 09:27:12 2013 +0100
@@ -0,0 +1,14251 @@
+<!DOCTYPE html>
+<html lang="en" dir="ltr">
+<head>
+ <title>PROV-AQ: Provenance Access and Query</title>
+ <style>/* --- EXAMPLES --- */
+div.example-title {
+ min-width: 7.5em;
+ color: #b9ab2d;
+}
+div.example-title span {
+ text-transform: uppercase;
+}
+aside.example, div.example, div.illegal-example {
+ padding: 0.5em;
+ margin: 1em 0;
+ position: relative;
+ clear: both;
+}
+div.illegal-example { color: red }
+div.illegal-example p { color: black }
+aside.example, div.example {
+ padding: .5em;
+ border-left-width: .5em;
+ border-left-style: solid;
+ border-color: #e0cb52;
+ background: #fcfaee;
+}
+
+aside.example div.example {
+ border-left-width: .1em;
+ border-color: #999;
+ background: #fff;
+}
+aside.example div.example div.example-title {
+ color: #999;
+}
+</style><style>/* --- ISSUES/NOTES --- */
+div.issue-title, div.note-title {
+ padding-right: 1em;
+ min-width: 7.5em;
+ color: #b9ab2d;
+}
+div.issue-title { color: #e05252; }
+div.note-title { color: #2b2; }
+div.issue-title span, div.note-title span {
+ text-transform: uppercase;
+}
+div.note, div.issue {
+ margin-top: 1em;
+ margin-bottom: 1em;
+}
+.note > p:first-child, .issue > p:first-child { margin-top: 0 }
+.issue, .note {
+ padding: .5em;
+ border-left-width: .5em;
+ border-left-style: solid;
+}
+div.issue, div.note {
+ padding: 1em 1.2em 0.5em;
+ margin: 1em 0;
+ position: relative;
+ clear: both;
+}
+span.note, span.issue { padding: .1em .5em .15em; }
+
+.issue {
+ border-color: #e05252;
+ background: #fbe9e9;
+}
+.note {
+ border-color: #52e052;
+ background: #e9fbe9;
+}
+
+
+</style><link rel="stylesheet" type="text/css" href="css/prov-aq.css">
+ <link rel="http://www.w3.org/ns/prov#has_provenance" href="http://www.w3.org/2011/prov/provenance/prov-aq">
+ <meta http-equiv="Content-Type" content="text/html;charset=utf-8">
+<!-- Use common W3C-hosted version of ReSpec.js:
+-->
+
+<!--
+ <script src="http://dev.w3.org/2009/dap/ReSpec.js/js/respec.js" class="remove"></script>
+
+ Use local version of ReSpec.js for debugging:
+ <script src="js/respec.js" class="remove"></script>
+ <script src="file:///usr/workspace/w3c-provenance/prov/paq/js/respec.js" class="remove"></script>
+-->
+ <!-- Include bibliography file defined for PROV-DM: -->
+
+
+
+ <style>/*****************************************************************
+ * ReSpec 3 CSS
+ * Robin Berjon - http://berjon.com/
+ *****************************************************************/
+
+/* --- INLINES --- */
+em.rfc2119 {
+ text-transform: lowercase;
+ font-variant: small-caps;
+ font-style: normal;
+ color: #900;
+}
+
+h1 acronym, h2 acronym, h3 acronym, h4 acronym, h5 acronym, h6 acronym, a acronym,
+h1 abbr, h2 abbr, h3 abbr, h4 abbr, h5 abbr, h6 abbr, a abbr {
+ border: none;
+}
+
+dfn {
+ font-weight: bold;
+}
+
+a.internalDFN {
+ color: inherit;
+ border-bottom: 1px solid #99c;
+ text-decoration: none;
+}
+
+a.externalDFN {
+ color: inherit;
+ border-bottom: 1px dotted #ccc;
+ text-decoration: none;
+}
+
+a.bibref {
+ text-decoration: none;
+}
+
+cite .bibref {
+ font-style: normal;
+}
+
+code {
+ color: #ff4500;
+}
+
+/* --- TOC --- */
+.toc a, .tof a {
+ text-decoration: none;
+}
+
+a .secno, a .figno {
+ color: #000;
+}
+
+ul.tof, ol.tof {
+ list-style: none outside none;
+}
+
+.caption {
+ margin-top: 0.5em;
+ font-style: italic;
+}
+
+/* --- TABLE --- */
+table.simple {
+ border-spacing: 0;
+ border-collapse: collapse;
+ border-bottom: 3px solid #005a9c;
+}
+
+.simple th {
+ background: #005a9c;
+ color: #fff;
+ padding: 3px 5px;
+ text-align: left;
+}
+
+.simple th[scope="row"] {
+ background: inherit;
+ color: inherit;
+ border-top: 1px solid #ddd;
+}
+
+.simple td {
+ padding: 3px 10px;
+ border-top: 1px solid #ddd;
+}
+
+.simple tr:nth-child(even) {
+ background: #f0f6ff;
+}
+
+/* --- DL --- */
+.section dd > p:first-child {
+ margin-top: 0;
+}
+
+.section dd > p:last-child {
+ margin-bottom: 0;
+}
+
+.section dd {
+ margin-bottom: 1em;
+}
+
+.section dl.attrs dd, .section dl.eldef dd {
+ margin-bottom: 0;
+}
+<style type='text/css'>
+.diff-old-a {
+ font-size: smaller;
+ color: red;
+}
+
+.diff-new { background-color: yellow; }
+.diff-chg { background-color: lime; }
+.diff-new:before,
+.diff-new:after
+ { content: "\2191" }
+.diff-chg:before, .diff-chg:after
+ { content: "\2195" }
+.diff-old { text-decoration: line-through; background-color: #FBB; }
+.diff-old:before,
+.diff-old:after
+ { content: "\2193" }
+:focus { border: thin red solid}
+</style>
+</style><link rel="stylesheet" href="http://www.w3.org/StyleSheets/TR/W3C-WG-NOTE"><!--[if lt IE 9]><script src='http://www.w3.org/2008/site/js/html5shiv.js'></script><![endif]--></head>
+ <body><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">
+PROV-AQ:
+Provenance
+Access
+and
+Query
+</h1>
+<h2 id="w3c-working-group-note-30-april-2013">
+<abbr title="World Wide Web Consortium">
+W3C
+</abbr>
+Working
+<del class="diff-old">Draft
+12
+March
+</del>
+<ins class="diff-chg">Group
+Note
+30
+April
+</ins>
+2013
+</h2>
+<dl>
+<dt>
+This
+version:
+</dt>
+<dd>
+<del class="diff-old">http://www.w3.org/TR/2013/WD-prov-aq-20130312/
+</del>
+<a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/">
+<ins class="diff-chg">http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/
+</ins>
+</a>
+</dd>
+<dt>
+Latest
+published
+version:
+</dt>
+<dd>
+<a href="http://www.w3.org/TR/prov-aq/">
+http://www.w3.org/TR/prov-aq/
+</a>
+</dd>
+<dt>
+<del class="diff-old">Latest
+editor's
+draft:
+http://dvcs.w3.org/hg/prov/raw-file/tip/paq/prov-aq.html
+</del>
+Previous
+version:
+</dt>
+<dd>
+<del class="diff-old">http://www.w3.org/TR/2012/WD-prov-aq-20120619/
+</del>
+<a href="http://www.w3.org/TR/2013/WD-prov-aq-20130312/">
+<ins class="diff-chg">http://www.w3.org/TR/2013/WD-prov-aq-20130312/
+</ins>
+</a>
+</dd>
+<dt>
+Editors:
+</dt>
+<dd>
+<span>
+Graham
+Klyne
+</span>,
+<a href="http://www.ox.ac.uk/">
+University
+of
+Oxford
+</a>
+</dd>
+<dd>
+<a href="http://www.few.vu.nl/~pgroth/">
+Paul
+Groth
+<del class="diff-old">,
+</del>
+</a>,
+<a href="http://www.vu.nl/">
+VU
+University
+Amsterdam
+</a>
+</dd>
+<dt>
+Authors:
+</dt>
+<dd>
+<a href="http://www.ecs.soton.ac.uk/~lavm/">
+Luc
+Moreau
+</a>,
+University
+of
+Southampton
+</dd>
+<dd>
+<a href="http://olafhartig.de/">
+Olaf
+Hartig
+</a>,
+Invited
+Expert
+</dd>
+<dd>
+<span>
+Yogesh
+Simmhan
+</span>,
+Invited
+Expert
+</dd>
+<dd>
+<a href="http://www.rpi.edu/research/ccni/">
+James
+Myers
+</a>,
+Rensselaer
+Polytechnic
+Institute
+</dd>
+<dd>
+<a href="http://tw.rpi.edu/web/person/TimLebo">
+Timothy
+Lebo
+</a>,
+Rensselaer
+Polytechnic
+Institute
+</dd>
+<dd>
+<a href="http://semanticweb.org/wiki/Khalid_Belhajjame">
+Khalid
+Belhajjame
+</a>,
+<a href="http://www.cs.manchester.ac.uk/">
+University
+of
+Manchester
+</a>
+</dd>
+<dd>
+<a href="http://www.inf.kcl.ac.uk/staff/simonm/">
+Simon
+Miles
+</a>,
+Invited
+Expert
+</dd>
+<dd>
+<a href="http://soiland-reyes.com/stian/">
+Stian
+Soiland-Reyes
+</a>,
+<a href="http://www.cs.manchester.ac.uk/">
+University
+of
+Manchester
+</a>
+</dd>
+</dl>
+<p class="copyright">
+<a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">
+Copyright
+</a>
+©
+2013
+<a href="http://www.w3.org/">
+<abbr title="World Wide Web Consortium">
+W3C
+</abbr>
+</a>
+<sup>
+®
+</sup>
+(
+<a href="http://www.csail.mit.edu/">
+<abbr title="Massachusetts Institute of Technology">
+MIT
+</abbr>
+</a>,
+<a href="http://www.ercim.eu/">
+<abbr title="European Research Consortium for Informatics and Mathematics">
+ERCIM
+</abbr>
+</a>,
+<a href="http://www.keio.ac.jp/">
+Keio
+</a>,
+<a href="http://ev.buaa.edu.cn/">
+Beihang
+</a>
+),
+All
+Rights
+Reserved.
+<abbr title="World Wide Web Consortium">
+W3C
+</abbr>
+<a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">
+liability
+</a>,
+<a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">
+trademark
+</a>
+and
+<a href="http://www.w3.org/Consortium/Legal/copyright-documents">
+document
+use
+</a>
+rules
+apply.
+</p>
+<hr>
+</div>
+<section id="abstract" class="introductory">
+<h2>
+Abstract
+</h2>
+This
+document
+specifies
+how
+to
+use
+standard
+Web
+protocols,
+including
+HTTP,
+to
+obtain
+information
+about
+the
+provenance
+of
+resources
+on
+the
+Web.
+We
+describe
+both
+simple
+access
+mechanisms
+for
+locating
+provenance
+records
+associated
+with
+web
+pages
+or
+resources,
+and
+provenance
+query
+services
+for
+more
+complex
+deployments.
+This
+is
+part
+of
+the
+larger
+<abbr title="World Wide Web Consortium">
+W3C
+</abbr>
+PROV
+provenance
+family
+of
+documents.
+<p>
+The
+<a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/">
+PROV
+Document
+Overview
+</a>
+describes
+the
+overall
+state
+of
+PROV,
+and
+should
+be
+read
+before
+other
+PROV
+documents.
+</p>
+</section>
+<section id="sotd" class="introductory">
+<h2>
+Status
+of
+This
+Document
+</h2>
+<p>
+<em>
+This
+section
+describes
+the
+status
+of
+this
+document
+at
+the
+time
+of
+its
+publication.
+Other
+documents
+may
+supersede
+this
+document.
+A
+list
+of
+current
+<abbr title="World Wide Web Consortium">
+W3C
+</abbr>
+publications
+and
+the
+latest
+revision
+of
+this
+technical
+report
+can
+be
+found
+in
+the
+<a href="http://www.w3.org/TR/">
+<abbr title="World Wide Web Consortium">
+W3C
+</abbr>
+technical
+reports
+index
+</a>
+at
+http://www.w3.org/TR/.
+</em>
+</p>
+<h4 id="prov-family-of-documents">
+PROV
+Family
+of
+Documents
+</h4>
+This
+document
+is
+part
+of
+the
+PROV
+family
+of
+documents,
+a
+set
+of
+documents
+defining
+various
+aspects
+that
+are
+necessary
+to
+achieve
+the
+vision
+of
+inter-operable
+interchange
+of
+provenance
+information
+in
+heterogeneous
+environments
+such
+as
+the
+Web.
+These
+documents
+are
+listed
+below.
+Please
+consult
+the
+[
+<cite>
+<a class="bibref" href="#bib-PROV-OVERVIEW">
+PROV-OVERVIEW
+</a>
+</cite>
+]
+for
+a
+guide
+to
+reading
+these
+documents.
+<ul>
+<li>
+<a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/">
+PROV-OVERVIEW
+</a>
+<del class="diff-old">(To
+be
+published
+as
+Note),
+</del>
+<ins class="diff-chg">(Note),
+</ins>
+an
+overview
+of
+the
+PROV
+family
+of
+documents
+[
+<cite>
+<a class="bibref" href="#bib-PROV-OVERVIEW">
+PROV-OVERVIEW
+</a>
+</cite>
+];
+</li>
+<li>
+<a href="http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/">
+PROV-PRIMER
+</a>
+<del class="diff-old">(To
+be
+published
+as
+Note),
+</del>
+<ins class="diff-chg">(Note),
+</ins>
+a
+primer
+for
+the
+PROV
+data
+model
+[
+<cite>
+<a class="bibref" href="#bib-PROV-PRIMER">
+PROV-PRIMER
+</a>
+</cite>
+];
+</li>
+<li>
+<a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/">
+PROV-O
+</a>
+<del class="diff-old">(Proposed
+Recommendation),
+</del>
+<ins class="diff-chg">(Recommendation),
+</ins>
+the
+PROV
+ontology,
+an
+OWL2
+ontology
+allowing
+the
+mapping
+of
+<ins class="diff-new">the
+</ins>
+PROV
+<ins class="diff-new">data
+model
+</ins>
+to
+RDF
+[
+<cite>
+<a class="bibref" href="#bib-PROV-O">
+PROV-O
+</a>
+</cite>
+];
+</li>
+<li>
+<a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/">
+PROV-DM
+</a>
+<del class="diff-old">(Proposed
+Recommendation),
+</del>
+<ins class="diff-chg">(Recommendation),
+</ins>
+the
+PROV
+data
+model
+for
+<del class="diff-old">provenance;
+</del>
+<ins class="diff-chg">provenance
+</ins>
+[
+<cite>
+<a class="bibref" href="#bib-PROV-DM">
+PROV-DM
+</a>
+</cite>
+<del class="diff-old">]
+</del>
+<ins class="diff-chg">];
+</ins>
+</li>
+<li>
+<a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/">
+PROV-N
+</a>
+<del class="diff-old">(Proposed
+Recommendation),
+</del>
+<ins class="diff-chg">(Recommendation),
+</ins>
+a
+notation
+for
+provenance
+aimed
+at
+human
+consumption
+[
+<cite>
+<a class="bibref" href="#bib-PROV-N">
+PROV-N
+</a>
+</cite>
+];
+</li>
+<li>
+<a href="http://www.w3.org/TR/2013/REC-prov-constraints-20130430/">
+PROV-CONSTRAINTS
+</a>
+<del class="diff-old">(Proposed
+Recommendation),
+</del>
+<ins class="diff-chg">(Recommendation),
+</ins>
+a
+set
+of
+constraints
+applying
+to
+the
+PROV
+data
+model
+[
+<cite>
+<a class="bibref" href="#bib-PROV-CONSTRAINTS">
+PROV-CONSTRAINTS
+</a>
+</cite>
+];
+</li>
+<li>
+<a href="http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/">
+PROV-XML
+</a>
+<del class="diff-old">(To
+be
+published
+as
+Note),
+</del>
+<ins class="diff-chg">(Note),
+</ins>
+an
+XML
+schema
+for
+the
+PROV
+data
+model
+[
+<cite>
+<a class="bibref" href="#bib-PROV-XML">
+PROV-XML
+</a>
+</cite>
+];
+</li>
+<li>
+<a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/">
+PROV-AQ
+</a>
+<del class="diff-old">(To
+be
+published
+as
+Note),
+the
+</del>
+<ins class="diff-chg">(Note),
+</ins>
+mechanisms
+for
+accessing
+and
+querying
+provenance
+(this
+document);
+</li>
+<li>
+<a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/">
+PROV-DICTIONARY
+</a>
+<del class="diff-old">(To
+be
+published
+as
+Note)
+</del>
+<ins class="diff-chg">(Note)
+</ins>
+introduces
+a
+specific
+type
+of
+collection,
+consisting
+of
+key-entity
+pairs
+[
+<cite>
+<a class="bibref" href="#bib-PROV-DICTIONARY">
+PROV-DICTIONARY
+</a>
+</cite>
+];
+</li>
+<li>
+<a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/">
+PROV-DC
+</a>
+<del class="diff-old">(To
+be
+published
+as
+Note)
+</del>
+<ins class="diff-chg">(Note)
+</ins>
+provides
+a
+mapping
+between
+<del class="diff-old">PROV
+</del>
+<ins class="diff-chg">PROV-O
+</ins>
+and
+<del class="diff-old">Dublic
+</del>
+<ins class="diff-chg">Dublin
+</ins>
+Core
+Terms
+[
+<cite>
+<a class="bibref" href="#bib-PROV-DC">
+PROV-DC
+</a>
+</cite>
+];
+</li>
+<li>
+<a href="http://www.w3.org/TR/2013/NOTE-prov-sem-20130430/">
+PROV-SEM
+</a>
+<del class="diff-old">(To
+be
+published
+as
+Note),
+</del>
+<ins class="diff-chg">(Note),
+</ins>
+a
+declarative
+specification
+in
+terms
+of
+first-order
+logic
+of
+the
+PROV
+data
+model
+[
+<cite>
+<a class="bibref" href="#bib-PROV-SEM">
+PROV-SEM
+</a>
+</cite>
+];
+</li>
+<li>
+<a href="http://www.w3.org/TR/2013/NOTE-prov-links-20130430/">
+PROV-LINKS
+</a>
+<del class="diff-old">(To
+be
+published
+as
+Note)
+</del>
+<ins class="diff-chg">(Note)
+</ins>
+introduces
+a
+mechanism
+to
+link
+across
+bundles
+[
+<cite>
+<a class="bibref" href="#bib-PROV-LINKS">
+PROV-LINKS
+</a>
+</cite>
+].
+</li>
+</ul>
+<del class="diff-old">Third
+Public
+Working
+Draft
+</del>
+<h4 id="implementations-encouraged">
+<ins class="diff-chg">Implementations
+Encouraged
+</ins>
+</h4>
+<p>
+<del class="diff-old">This
+is
+the
+third
+public
+working.
+This
+revision
+introduces
+a
+new
+definition
+</del>
+<ins class="diff-chg">The
+Provenance
+Working
+Group
+encourages
+implementation
+</ins>
+of
+<del class="diff-old">a
+provenance
+pingback
+service
+as
+well
+as
+making
+various
+clarifications
+about
+</del>
+the
+<del class="diff-old">definition
+of
+service
+descriptions
+</del>
+<ins class="diff-chg">material
+defined
+in
+this
+document.
+Although
+work
+on
+this
+document
+by
+the
+Provenance
+Working
+Group
+is
+complete,
+errors
+may
+be
+recorded
+in
+the
+</ins><a href="http://www.w3.org/2011/prov/errata.html"><ins class="diff-chg">
+errata
+</ins></a><ins class="diff-chg">
+or
+</ins>
+and
+<del class="diff-old">how
+they
+are
+retrieved.
+</del>
+<ins class="diff-chg">these
+may
+be
+addressed
+in
+future
+revisions.
+</ins>
+</p>
+<h4 id="please-send-comments">
+<ins class="diff-new">Please
+Send
+Comments
+</ins></h4>
+<p>
+This
+document
+was
+published
+by
+the
+<a href="http://www.w3.org/2011/prov">
+Provenance
+Working
+Group
+</a>
+as
+a
+Working
+<del class="diff-old">Draft.
+</del>
+<ins class="diff-chg">Group
+Note.
+</ins>
+If
+you
+wish
+to
+make
+comments
+regarding
+this
+document,
+please
+send
+them
+to
+<a href="mailto:public-prov-comments@w3.org">
+public-prov-comments@w3.org
+</a>
+(
+<a href="mailto:public-prov-comments-request@w3.org?subject=subscribe">
+subscribe
+</a>,
+<a href="http://lists.w3.org/Archives/Public/public-prov-comments/">
+archives
+</a>
+).
+All
+comments
+are
+welcome.
+</p>
+<p>
+Publication
+as
+a
+Working
+<del class="diff-old">Draft
+</del>
+<ins class="diff-chg">Group
+Note
+</ins>
+does
+not
+imply
+endorsement
+by
+the
+<abbr title="World Wide Web Consortium">
+W3C
+</abbr>
+Membership.
+This
+is
+a
+draft
+document
+and
+may
+be
+updated,
+replaced
+or
+obsoleted
+by
+other
+documents
+at
+any
+time.
+It
+is
+inappropriate
+to
+cite
+this
+document
+as
+other
+than
+work
+in
+progress.
+</p>
+<p>
+This
+document
+was
+produced
+by
+a
+group
+operating
+under
+the
+<a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">
+5
+February
+2004
+<abbr title="World Wide Web Consortium">
+W3C
+</abbr>
+Patent
+Policy
+</a>.
+<del class="diff-old">The
+group
+does
+not
+expect
+this
+document
+to
+become
+a
+W3C
+Recommendation.
+</del>
+<abbr title="World Wide Web Consortium">
+W3C
+</abbr>
+maintains
+a
+<a href="http://www.w3.org/2004/01/pp-impl/46974/status" rel="disclosure">
+public
+list
+of
+any
+patent
+disclosures
+</a>
+made
+in
+connection
+with
+the
+deliverables
+of
+the
+group;
+that
+page
+also
+includes
+instructions
+for
+disclosing
+a
+patent.
+An
+individual
+who
+has
+actual
+knowledge
+of
+a
+patent
+which
+the
+individual
+believes
+contains
+<a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">
+Essential
+Claim(s)
+</a>
+must
+disclose
+the
+information
+in
+accordance
+with
+<a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">
+section
+6
+of
+the
+<abbr title="World Wide Web Consortium">
+W3C
+</abbr>
+Patent
+Policy
+</a>.
+</p>
+</section>
+<section id="toc">
+<h2 class="introductory">
+Table
+of
+Contents
+</h2>
+<ul class="toc">
+<li class="tocline">
+<a href="#introduction" class="tocxref">
+<span class="secno">
+1.
+</span>
+Introduction
+</a>
+<ul class="toc">
+<li class="tocline">
+<a href="#concepts" class="tocxref">
+<span class="secno">
+1.1
+</span>
+Concepts
+</a>
+</li>
+<li class="tocline">
+<a href="#provenance-and-resources" class="tocxref">
+<span class="secno">
+1.2
+</span>
+Provenance
+and
+resources
+</a>
+</li>
+<li class="tocline">
+<a href="#interpreting-provenance-records" class="tocxref">
+<span class="secno">
+1.3
+</span>
+Interpreting
+provenance
+records
+</a>
+</li>
+<li class="tocline">
+<a href="#uri-types-and-dereferencing" class="tocxref">
+<span class="secno">
+1.4
+</span>
+URI
+types
+and
+dereferencing
+</a>
+</li>
+</ul>
+</li>
+<li class="tocline">
+<a href="#accessing-provenance-records" class="tocxref">
+<span class="secno">
+2.
+</span>
+Accessing
+provenance
+records
+</a>
+</li>
+<li class="tocline">
+<a href="#locating-provenance-records" class="tocxref">
+<span class="secno">
+3.
+</span>
+Locating
+provenance
+records
+</a>
+<ul class="toc">
+<li class="tocline">
+<a href="#resource-accessed-by-http" class="tocxref">
+<span class="secno">
+3.1
+</span>
+Resource
+accessed
+by
+HTTP
+</a>
+<ul class="toc">
+<li class="tocline">
+<a href="#specifying-provenance-query-services" class="tocxref">
+<span class="secno">
+3.1.1
+</span>
+Specifying
+Provenance
+Query
+Services
+</a>
+</li>
+<li class="tocline">
+<a href="#content-negotiation-redirection-and-link-headers" class="tocxref">
+<span class="secno">
+3.1.2
+</span>
+Content
+negotiation,
+redirection
+and
+Link:
+headers
+</a>
+</li>
+</ul>
+</li>
+<li class="tocline">
+<a href="#resource-represented-as-html" class="tocxref">
+<span class="secno">
+3.2
+</span>
+Resource
+represented
+as
+HTML
+</a>
+<ul class="toc">
+<li class="tocline">
+<a href="#specifying-provenance-query-services-1" class="tocxref">
+<span class="secno">
+3.2.1
+</span>
+Specifying
+Provenance
+Query
+Services
+</a>
+</li>
+</ul>
+</li>
+<li class="tocline">
+<a href="#resource-represented-as-rdf" class="tocxref">
+<span class="secno">
+3.3
+</span>
+Resource
+represented
+as
+RDF
+</a>
+</li>
+</ul>
+</li>
+<li class="tocline">
+<a href="#provenance-query-services" class="tocxref">
+<span class="secno">
+4.
+</span>
+Provenance
+query
+services
+</a>
+<ul class="toc">
+<li class="tocline">
+<a href="#provenance-query-service-description" class="tocxref">
+<span class="secno">
+4.1
+</span>
+Provenance
+query
+service
+description
+</a>
+<ul class="toc">
+<li class="tocline">
+<a href="#direct-http-query-service-description" class="tocxref">
+<span class="secno">
+4.1.1
+</span>
+Direct
+HTTP
+query
+service
+description
+</a>
+</li>
+<li class="tocline">
+<a href="#sparql-query-service-description" class="tocxref">
+<span class="secno">
+4.1.2
+</span>
+SPARQL
+query
+service
+description
+</a>
+</li>
+<li class="tocline">
+<a href="#service-description-example" class="tocxref">
+<span class="secno">
+4.1.3
+</span>
+Service
+description
+example
+</a>
+</li>
+</ul>
+</li>
+<li class="tocline">
+<a href="#direct-http-query-service-invocation" class="tocxref">
+<span class="secno">
+4.2
+</span>
+Direct
+HTTP
+query
+service
+invocation
+</a>
+</li>
+<li class="tocline">
+<a href="#provenance-query-service-discovery" class="tocxref">
+<span class="secno">
+4.3
+</span>
+Provenance
+query
+service
+discovery
+</a>
+</li>
+</ul>
+</li>
+<li class="tocline">
+<a href="#provenance-pingback" class="tocxref">
+<span class="secno">
+5.
+</span>
+<del class="diff-old">Forward
+provenance
+</del>
+<ins class="diff-chg">Provenance
+pingback
+</ins>
+</a>
+</li>
+<li class="tocline">
+<a href="#security-considerations" class="tocxref">
+<span class="secno">
+6.
+</span>
+Security
+considerations
+</a>
+</li>
+<li class="tocline">
+<a href="#acknowledgements" class="tocxref">
+<span class="secno">
+A.
+</span>
+Acknowledgements
+</a>
+</li>
+<li class="tocline">
+<a href="#terms-added-to-prov-namespace" class="tocxref">
+<span class="secno">
+B.
+</span>
+Terms
+added
+to
+prov:
+namespace
+</a>
+</li>
+<li class="tocline">
+<del class="diff-old">C.
+Changes
+log
+C.1
+Changes
+since
+20120619
+publication
+</del>
+<a href="#references" class="tocxref">
+<span class="secno">
+<del class="diff-old">D.
+</del>
+<ins class="diff-chg">C.
+</ins>
+</span>
+References
+</a>
+<ul class="toc">
+<li class="tocline">
+<a href="#informative-references" class="tocxref">
+<span class="secno">
+<del class="diff-old">D.1
+</del>
+<ins class="diff-chg">C.1
+</ins>
+</span>
+Informative
+references
+</a>
+</li>
+</ul>
+</li>
+</ul>
+</section>
+<section id="introduction">
+<h2>
+<span class="secno">
+1.
+</span>
+Introduction
+</h2>
+<p>
+The
+Provenance
+Data
+Model
+[
+<cite>
+<a class="bibref" href="#bib-PROV-DM">
+PROV-DM
+</a>
+</cite>
+],
+Provenance
+Ontology
+[
+<cite>
+<a class="bibref" href="#bib-PROV-O">
+PROV-O
+</a>
+</cite>
+]
+and
+related
+specifications
+define
+how
+to
+represent
+provenance
+<del class="diff-old">in
+</del>
+<ins class="diff-chg">on
+</ins>
+the
+World
+Wide
+Web
+(see
+the
+[
+<cite>
+<a class="bibref" href="#bib-PROV-OVERVIEW">
+PROV-OVERVIEW
+</a>
+</cite>
+]).
+</p>
+<p>
+This
+note
+describes
+how
+standard
+web
+protocols
+may
+be
+used
+to
+locate,
+retrieve
+and
+query
+provenance
+records:
+</p>
+<ul>
+<li>
+Simple
+mechanisms
+for
+retrieving
+and
+discovering
+provenance
+records
+are
+described
+in
+<a href="#accessing-provenance-records" class="sectionRef sec-ref">
+section
+2.
+Accessing
+provenance
+records
+</a>
+and
+<a href="#locating-provenance-records" class="sectionRef sec-ref">
+section
+3.
+Locating
+provenance
+records
+</a>
+.
+</li>
+<li>
+Provenance
+query
+mechanisms
+that
+may
+be
+used
+for
+more
+demanding
+deployments
+are
+described
+in
+<a href="#provenance-query-services" class="sectionRef sec-ref">
+section
+4.
+Provenance
+query
+services
+</a>.
+</li>
+<li>
+A
+simple
+"ping-back"
+mechanism
+allowing
+for
+discovery
+of
+<del class="diff-old">"forward
+provenance"
+(i.e.
+</del>
+<ins class="diff-chg">additional
+provenance
+that
+would
+otherwise
+be
+unknown
+to
+the
+publisher
+of
+the
+resource
+(e.g.
+</ins>
+provenance
+about
+future
+entities
+that
+are
+based
+upon
+or
+influenced
+by
+a
+resource)
+is
+described
+in
+<a href="#provenance-pingback" class="sectionRef sec-ref">
+section
+5.
+<del class="diff-old">Forward
+provenance
+</del>
+<ins class="diff-chg">Provenance
+pingback
+</ins>
+</a>.
+</li>
+</ul>
+<p>
+Most
+mechanisms
+described
+in
+this
+note
+are
+independent
+of
+the
+provenance
+format
+used,
+and
+may
+be
+used
+to
+access
+provenance
+in
+any
+available
+format.
+For
+interoperable
+provenance
+publication,
+use
+of
+<del class="diff-old">PROV-O
+</del>
+<ins class="diff-chg">PROV
+</ins>
+represented
+in
+<del class="diff-old">a
+standardized
+RDF
+format
+</del>
+<ins class="diff-chg">any
+of
+its
+specified
+formats
+</ins>
+is
+recommended.
+Where
+alternative
+formats
+are
+available,
+selection
+may
+be
+made
+by
+<ins class="diff-new">HTTP
+</ins>
+content
+<del class="diff-old">negotiation.
+</del>
+<ins class="diff-chg">negotiation
+[
+</ins><cite><a class="bibref" href="#bib-HTTP11"><ins class="diff-chg">
+HTTP11
+</ins></a></cite><ins class="diff-chg">
+].
+</ins>
+</p>
+<p>
+For
+ease
+of
+reference,
+the
+main
+body
+of
+this
+document
+contains
+some
+links
+to
+external
+web
+pages.
+Such
+links
+are
+distinguished
+from
+internal
+references
+thus:
+<a href="http://www.w3.org/2011/prov/wiki/Main_Page" class="externalRef">
+<abbr title="World Wide Web Consortium">
+W3C
+</abbr>
+Provenance
+Working
+Group
+</a>.
+</p>
+<p>
+<ins class="diff-new">This
+document
+is
+a
+</ins><abbr title="World Wide Web Consortium"><ins class="diff-new">
+W3C
+</ins></abbr><ins class="diff-new">
+Note,
+not
+a
+formal
+</ins><abbr title="World Wide Web Consortium"><ins class="diff-new">
+W3C
+</ins></abbr><ins class="diff-new">
+Specification.
+However,
+to
+clarify
+the
+description
+of
+intended
+behaviours,
+it
+does
+use
+the
+key
+words
+</ins><em class="rfc2119" title="MUST"><ins class="diff-new">
+MUST
+</ins></em>,<em class="rfc2119" title="MUST NOT"><ins class="diff-new">
+MUST
+NOT
+</ins></em>,<em class="rfc2119" title="REQUIRED"><ins class="diff-new">
+REQUIRED
+</ins></em>,<em class="rfc2119" title="SHOULD"><ins class="diff-new">
+SHOULD
+</ins></em>,<em class="rfc2119" title="SHOULD NOT"><ins class="diff-new">
+SHOULD
+NOT
+</ins></em>,<em class="rfc2119" title="RECOMMENDED"><ins class="diff-new">
+RECOMMENDED
+</ins></em>,<em class="rfc2119" title="MAY"><ins class="diff-new">
+MAY
+</ins></em><ins class="diff-new">
+and
+</ins><em class="rfc2119" title="OPTIONAL"><ins class="diff-new">
+OPTIONAL
+</ins></em><ins class="diff-new">
+as
+described
+in
+[
+</ins><cite><a class="bibref" href="#bib-RFC2119"><ins class="diff-new">
+RFC2119
+</ins></a></cite><ins class="diff-new">
+].
+</ins></p>
+<section id="concepts">
+<h3>
+<span class="secno">
+1.1
+</span>
+Concepts
+</h3>
+<p>
+<ins class="diff-new">This
+document
+uses
+the
+term
+URI
+for
+web
+resource
+identifiers,
+as
+this
+is
+the
+term
+used
+in
+many
+of
+the
+currently
+ratified
+specifications
+that
+this
+document
+builds
+upon.
+In
+many
+situations,
+a
+URI
+may
+also
+be
+an
+IRI
+[
+</ins><cite><a class="bibref" href="#bib-RFC3987"><ins class="diff-new">
+RFC3987
+</ins></a></cite><ins class="diff-new">
+],
+which
+is
+a
+generalisation
+of
+a
+URI
+allowing
+a
+wider
+range
+of
+Unicode
+characters.
+Every
+absolute
+URI
+is
+an
+IRI,
+but
+not
+every
+IRI
+is
+an
+URI.
+When
+IRIs
+are
+used
+in
+situations
+that
+require
+a
+URI,
+they
+must
+first
+be
+converted
+according
+to
+the
+mapping
+defined
+in
+section
+3.1
+of
+[
+</ins><cite><a class="bibref" href="#bib-RFC3987"><ins class="diff-new">
+RFC3987
+</ins></a></cite><ins class="diff-new">
+].
+A
+notable
+example
+is
+retrieval
+over
+the
+HTTP
+protocol.
+The
+mapping
+involves
+UTF-8
+encoding
+of
+non-ASCII
+characters,
+%-encoding
+of
+octets
+not
+allowed
+in
+URIs,
+and
+Punycode-encoding
+of
+domain
+names.
+</ins></p><p>
+In
+defining
+the
+specification
+below,
+we
+make
+use
+of
+the
+following
+concepts.
+</p>
+<dl>
+<dt>
+<a href="#dfn-resource">
+<dfn id="dfn-resource">
+Resource
+</dfn>
+</a>
+</dt>
+<dd>
+a
+resource
+in
+the
+general
+sense
+of
+"whatever
+might
+be
+identified
+by
+a
+URI",
+as
+described
+by
+the
+Architecture
+of
+the
+World
+Wide
+Web
+[
+<cite>
+<a class="bibref" href="#bib-WEBARCH">
+WEBARCH
+</a>
+</cite>
+],
+<a href="http://www.w3.org/TR/webarch/#id-resources" class="externalRef">
+section
+2.2
+</a>.
+A
+resource
+may
+be
+associated
+with
+multiple
+instances
+or
+views
+(
+<a class="internalDFN" href="#dfn-constrained-resource">
+constrained
+resource
+</a>
+s)
+with
+differing
+provenance.
+</dd>
+<dt>
+<a href="#dfn-constrained-resource">
+<dfn id="dfn-constrained-resource">
+Constrained
+resource
+</dfn>
+</a>
+</dt>
+<dd>
+a
+specialization
+(e.g.
+an
+aspect,
+version
+or
+instance)
+of
+a
+<a class="internalDFN" href="#dfn-resource">
+resource
+</a>,
+about
+which
+one
+may
+wish
+to
+present
+<a class="internalDFN" href="#dfn-provenance-record">
+provenance
+record
+</a>
+s.
+For
+example,
+a
+weather
+report
+for
+a
+given
+date
+may
+be
+an
+aspect
+of
+a
+resource
+that
+is
+maintained
+as
+the
+current
+weather
+report.
+A
+constrained
+resource
+is
+itself
+a
+<a class="internalDFN" href="#dfn-resource">
+resource
+</a>,
+and
+may
+have
+its
+own
+URI
+different
+from
+that
+of
+the
+original.
+See
+also
+<a class="sectionRef sec-ref" href="#provenance-and-resources">
+section
+1.2
+Provenance
+and
+resources
+</a>,
+[
+<cite>
+<a class="bibref" href="#bib-PROV-DM">
+PROV-DM
+</a>
+</cite>
+]
+<a href="http://www.w3.org/TR/prov-dm/#term-specialization" class="externalRef">
+section
+5.5.1
+</a>,
+and
+[
+<cite>
+<a class="bibref" href="#bib-WEBARCH">
+WEBARCH
+</a>
+</cite>
+]
+<a href="http://www.w3.org/TR/webarch/#representation-reuse" class="externalRef">
+section
+2.3.2
+</a>.
+</dd>
+<dt>
+<a href="#dfn-target-uri">
+<dfn id="dfn-target-uri">
+Target-URI
+</dfn>
+</a>
+</dt>
+<dd>
+a
+URI
+denoting
+a
+<a class="internalDFN" href="#dfn-resource">
+resource
+</a>
+(including
+any
+<a class="internalDFN" href="#dfn-constrained-resource">
+constrained
+resource
+</a>
+),
+and
+which
+identifies
+that
+resource
+for
+the
+purpose
+of
+expressing
+provenance.
+Such
+a
+resource
+is
+typically
+an
+<a class="externalRef" href="http://www.w3.org/TR/prov-dm/#section-entity-activity">
+entity
+</a>
+in
+the
+sense
+of
+[
+<cite>
+<a class="bibref" href="#bib-PROV-DM">
+PROV-DM
+</a>
+</cite>
+],
+but
+may
+be
+something
+else
+described
+by
+provenance
+records,
+such
+as
+an
+<a class="externalRef" href="http://www.w3.org/TR/prov-dm/#section-entity-activity">
+activity
+</a>.
+</dd>
+<dt>
+<a href="#dfn-provenance-record">
+<dfn id="dfn-provenance-record">
+Provenance
+record
+</dfn>
+</a>
+</dt>
+<dd>
+refers
+to
+provenance
+represented
+in
+some
+fashion.
+</dd>
+<dt>
+<a href="#dfn-provenance-uri">
+<dfn id="dfn-provenance-uri">
+Provenance-URI
+</dfn>
+</a>
+</dt>
+<dd>
+a
+URI
+denoting
+some
+<a class="internalDFN" href="#dfn-provenance-record">
+provenance
+record
+</a>.
+</dd>
+<dt>
+<a href="#dfn-provenance-query-service">
+<dfn id="dfn-provenance-query-service">
+Provenance
+query
+service
+</dfn>
+</a>
+</dt>
+<dd>
+a
+service
+that
+accesses
+provenance
+given
+a
+query
+containing
+a
+<a class="internalDFN" href="#dfn-target-uri">
+target-URI
+</a>
+or
+other
+information
+that
+identifies
+the
+desired
+provenance.
+</dd>
+<dt>
+<a href="#dfn-service-uri">
+<dfn id="dfn-service-uri">
+Service-URI
+</dfn>
+</a>
+</dt>
+<dd>
+the
+URI
+of
+a
+<a class="internalDFN" href="#dfn-provenance-query-service">
+provenance
+query
+service
+</a>.
+</dd>
+<dt>
+<del class="diff-old">Forward
+provenance
+provenance
+describing
+how
+a
+resource
+is
+used
+after
+it
+has
+been
+created
+</del>
+<a href="#dfn-pingback-uri">
+<dfn id="dfn-pingback-uri">
+Pingback-URI
+</dfn>
+</a>
+</dt>
+<dd>
+the
+URI
+of
+a
+provenance
+pingback
+service
+that
+can
+receive
+references
+to
+<del class="diff-old">forward
+</del>
+<ins class="diff-chg">additional
+</ins>
+provenance
+<del class="diff-old">.
+</del>
+<ins class="diff-chg">related
+to
+an
+entity.
+</ins>
+</dd>
+<dt>
+<a href="#dfn-accessing">
+<dfn id="dfn-accessing">
+Accessing
+</dfn>
+</a>
+provenance
+records
+</dt>
+<dd>
+given
+the
+identity
+of
+a
+resource,
+the
+process
+of
+discovering
+and
+retrieving
+some
+<a class="internalDFN" href="#dfn-provenance-record">
+provenance
+record
+</a>
+(s)
+about
+that
+resource.
+This
+may
+involve
+<a class="internalDFN" href="#dfn-locating">
+locating
+</a>
+a
+provenance
+record,
+then
+performing
+an
+HTTP
+GET
+to
+retrieve
+it,
+or
+locating
+and
+using
+a
+query
+service
+for
+provenance
+about
+an
+identified
+resource,
+or
+some
+other
+mechanism
+not
+covered
+in
+this
+document.
+</dd>
+<dt>
+<a href="#dfn-locating">
+<dfn id="dfn-locating">
+Locating
+</dfn>
+</a>
+provenance
+records
+</dt>
+<dd>
+given
+the
+identity
+of
+a
+resource,
+discovery
+of
+a
+<a class="internalDFN" href="#dfn-provenance-uri">
+provenance-URI
+</a>
+or
+a
+<a class="internalDFN" href="#dfn-service-uri">
+service-URI
+</a>
+that
+may
+be
+used
+to
+obtain
+a
+<a class="internalDFN" href="#dfn-provenance-record">
+provenance
+record
+</a>
+about
+that
+resource.
+</dd>
+<dt>
+provenance
+<a href="#dfn-provider">
+<dfn id="dfn-provider">
+provider
+</dfn>
+</a>
+</dt>
+<dd>
+is
+an
+agent
+that
+makes
+available
+provenance
+records.
+</dd>
+<dt>
+provenance
+<a href="#dfn-consumer">
+<dfn id="dfn-consumer">
+consumer
+</dfn>
+</a>
+</dt>
+<dd>
+is
+an
+agent
+that
+receives
+and
+interprets
+provenance
+records.
+</dd>
+</dl>
+<del class="diff-old">The
+pingback
+definition
+is
+new.
+Review
+is
+encouraged.
+This
+document
+uses
+the
+term
+URI
+for
+web
+resource
+identifiers,
+as
+this
+is
+the
+term
+used
+in
+many
+of
+the
+currently
+ratified
+specifications
+that
+this
+document
+builds
+upon.
+In
+many
+situations,
+a
+URI
+may
+also
+be
+an
+IRI
+[
+RFC3987
+],
+which
+is
+a
+generalisation
+of
+a
+URI
+allowing
+a
+wider
+range
+of
+Unicode
+characters.
+Every
+absolute
+URI
+is
+an
+IRI,
+but
+not
+every
+IRI
+is
+an
+URI.
+When
+IRIs
+are
+used
+in
+situations
+that
+require
+a
+URI,
+they
+must
+first
+be
+converted
+according
+to
+the
+mapping
+defined
+in
+section
+3.1
+of
+[
+RFC3987
+].
+A
+notable
+example
+is
+retrieval
+over
+the
+HTTP
+protocol.
+The
+mapping
+involves
+UTF-8
+encoding
+of
+non-ASCII
+characters,
+%-encoding
+of
+octets
+not
+allowed
+in
+URIs,
+and
+Punycode-encoding
+of
+domain
+names.
+</del>
+</section>
+<section id="provenance-and-resources">
+<h3 id="provenance-entities-resources">
+<span class="secno">
+1.2
+</span>
+Provenance
+and
+resources
+</h3>
+<p>
+Fundamentally,
+a
+<a class="internalDFN" href="#dfn-provenance-record">
+provenance
+record
+</a>
+is
+<em>
+about
+</em>
+<a class="internalDFN" href="#dfn-resource">
+resource
+</a>
+s.
+In
+general,
+resources
+may
+vary
+over
+time
+and
+context.
+E.g.,
+a
+resource
+describing
+the
+weather
+in
+London
+changes
+from
+day-to-day,
+or
+a
+listing
+of
+restaurants
+near
+you
+will
+vary
+depending
+on
+your
+location.
+</p>
+<p>
+Provenance
+records
+a
+history
+of
+the
+entities,
+activities,
+and
+people
+involved
+in
+producing
+an
+artifact,
+and
+may
+be
+collected
+from
+several
+sources
+at
+different
+<del class="diff-old">times.
+</del>
+<ins class="diff-chg">times
+[
+</ins><cite><a class="bibref" href="#bib-PROV-DM"><ins class="diff-chg">
+PROV-DM
+</ins></a></cite><ins class="diff-chg">
+].
+</ins>
+In
+order
+to
+create
+a
+meaningful
+history,
+the
+individual
+provenance
+records
+used
+must
+<del class="diff-old">remain
+valid
+and
+correct
+</del>
+<ins class="diff-chg">retain
+their
+intended
+meaning
+</ins>
+when
+interpreted
+in
+a
+context
+other
+than
+that
+in
+which
+they
+were
+collected.
+<del class="diff-old">Yet
+</del>
+<ins class="diff-chg">Yet,
+</ins>
+we
+may
+still
+want
+to
+make
+provenance
+assertions
+about
+dynamic
+or
+context-dependent
+resources
+(e.g.
+a
+weather
+forecast
+for
+London
+on
+a
+particular
+day
+may
+have
+been
+derived
+from
+a
+particular
+set
+of
+Meteorological
+Office
+data).
+</p>
+<p>
+Provenance
+records
+for
+dynamic
+and
+context-dependent
+resources
+are
+possible
+through
+a
+notion
+of
+constrained
+resources.
+A
+<a class="internalDFN" href="#dfn-constrained-resource">
+constrained
+resource
+</a>
+is
+simply
+a
+resource
+(in
+the
+sense
+defined
+by
+[
+<cite>
+<a class="bibref" href="#bib-WEBARCH">
+WEBARCH
+</a>
+</cite>
+],
+<a href="http://www.w3.org/TR/webarch/#id-resources" class="externalRef">
+section
+2.2
+</a>
+)
+that
+is
+a
+specialization
+or
+instance
+of
+some
+other
+resource.
+For
+example,
+a
+<abbr title="World Wide Web Consortium">
+W3C
+</abbr>
+specification
+typically
+undergoes
+several
+public
+revisions
+before
+it
+is
+finalized.
+A
+URI
+that
+refers
+to
+the
+"current"
+revision
+might
+be
+thought
+of
+as
+denoting
+the
+specification
+throughout
+its
+lifetime.
+Each
+individual
+revision
+would
+also
+have
+its
+own
+<a class="internalDFN" href="#dfn-target-uri">
+target-URI
+</a>
+denoting
+the
+specification
+at
+that
+particular
+stage
+in
+its
+development.
+Using
+these,
+we
+can
+make
+provenance
+assertions
+that
+a
+particular
+revision
+was
+published
+on
+a
+particular
+date,
+and
+was
+last
+modified
+by
+a
+particular
+editor.
+Target-URIs
+may
+use
+any
+URI
+scheme,
+and
+are
+not
+required
+to
+be
+dereferencable.
+</p>
+<p>
+Requests
+for
+provenance
+about
+a
+resource
+may
+return
+provenance
+records
+that
+use
+one
+or
+more
+target-URIs
+to
+refer
+to
+versions
+of
+that
+resource,
+such
+as
+when
+there
+are
+assertions
+referring
+to
+the
+same
+underlying
+resource
+in
+different
+contexts.
+For
+example,
+a
+provenance
+record
+for
+a
+<abbr title="World Wide Web Consortium">
+W3C
+</abbr>
+document
+might
+include
+information
+about
+all
+revisions
+of
+the
+document
+using
+statements
+that
+use
+the
+different
+target-URIs
+of
+the
+various
+revisions.
+</p>
+<p>
+These
+ideas
+are
+represented
+in
+the
+provenance
+data
+model
+[
+<cite>
+<a class="bibref" href="#bib-PROV-DM">
+PROV-DM
+</a>
+</cite>
+]
+by
+the
+concepts
+<a href="http://www.w3.org/TR/prov-dm/#term-entity" class="externalRef">
+entity
+</a>
+and
+<a href="http://www.w3.org/TR/prov-dm/#term-specialization" class="externalRef">
+specialization
+</a>.
+In
+particular,
+an
+entity
+may
+be
+a
+specialization
+of
+some
+resource
+whose
+"fixed
+aspects"
+provide
+sufficient
+constraint
+for
+expressed
+provenance
+about
+the
+resource
+to
+be
+invariant
+with
+respect
+to
+that
+entity.
+This
+entity
+is
+itself
+just
+another
+resource
+(e.g.
+the
+weather
+forecast
+for
+a
+give
+date
+as
+opposed
+to
+the
+current
+weather
+forecast),
+with
+its
+own
+URI
+for
+referring
+to
+it
+within
+a
+provenance
+record.
+</p>
+</section>
+<section id="interpreting-provenance-records">
+<h3>
+<span class="secno">
+1.3
+</span>
+Interpreting
+provenance
+records
+</h3>
+<del class="diff-old">Review
+second
+para
+below.
+</del>
+<p>
+The
+mechanisms
+described
+in
+this
+document
+are
+intended
+to
+allow
+a
+provider
+to
+supply
+information
+that
+allows
+a
+consumer
+to
+access
+<a class="internalDFN" href="#dfn-provenance-record">
+provenance
+record
+</a>
+s,
+which
+themselves
+explicitly
+identify
+the
+<a class="internalDFN" href="#dfn-entity">
+entities
+</a>
+they
+describe.
+A
+provenance
+record
+may
+contain
+information
+about
+several
+entities,
+referring
+to
+them
+using
+their
+various
+<a class="internalDFN" href="#dfn-target-uri">
+target-URI
+</a>
+s.
+<del class="diff-old">Thus
+</del>
+<ins class="diff-chg">Thus,
+</ins>
+a
+consumer
+should
+be
+selective
+in
+its
+use
+of
+the
+information
+provided
+when
+interpreting
+a
+provenance
+record.
+</p>
+<p>
+A
+provenance
+record
+consumer
+will
+need
+to
+isolate
+information
+about
+the
+specific
+entity
+or
+entities
+of
+interest.
+These
+may
+be
+<a class="internalDFN" href="#dfn-constrained-resource">
+constrained
+resource
+</a>
+s
+identified
+by
+separate
+target-URIs
+<del class="diff-old">than
+</del>
+<ins class="diff-chg">that
+differ
+from
+</ins>
+the
+<del class="diff-old">original
+resource,
+</del>
+<ins class="diff-chg">resource
+URI,
+</ins>
+in
+which
+case
+<del class="diff-old">it
+will
+need
+to
+know
+about
+</del>
+the
+<del class="diff-old">target-URIs
+used.
+</del>
+<ins class="diff-chg">consumer
+needs
+to
+discover
+those
+target-URIs.
+</ins>
+The
+mechanisms
+defined
+later
+allow
+a
+provider
+to
+expose
+such
+URIs.
+</p>
+<p>
+While
+a
+provider
+should
+avoid
+giving
+spurious
+information,
+there
+are
+no
+fixed
+semantics,
+particularly
+when
+multiple
+resources
+are
+indicated,
+and
+a
+client
+should
+not
+assume
+that
+a
+specific
+given
+provenance-URI
+will
+yield
+information
+about
+a
+specific
+target-URI.
+In
+the
+general
+case,
+a
+client
+presented
+with
+multiple
+provenance-URIs
+and
+multiple
+target-URIs
+should
+look
+at
+all
+of
+the
+provenance-URIs
+for
+information
+about
+any
+or
+all
+of
+the
+target-URIs.
+</p>
+<p>
+A
+provenance
+record
+is
+not
+of
+itself
+guaranteed
+to
+be
+authoritative
+or
+correct.
+Trust
+in
+provenance
+records
+must
+be
+determined
+separately
+from
+trust
+in
+the
+original
+resource.
+Just
+as
+in
+the
+web
+at
+large,
+it
+is
+a
+user's
+responsibility
+to
+determine
+an
+appropriate
+level
+of
+trust
+in
+any
+other
+resource;
+e.g.
+based
+on
+the
+domain
+that
+serves
+it,
+or
+an
+associated
+digital
+signature.
+(See
+also
+<a href="#security-considerations" class="sectionRef sec-ref">
+section
+6.
+Security
+considerations
+</a>.)
+</p>
+</section>
+<section id="uri-types-and-dereferencing">
+<h3>
+<span class="secno">
+1.4
+</span>
+URI
+types
+and
+dereferencing
+</h3>
+<p>
+A
+number
+of
+resource
+types
+are
+described
+above
+in
+<a href="#concepts" class="sectionRef sec-ref">
+section
+1.1
+Concepts
+</a>.
+The
+table
+below
+summarizes
+what
+these
+various
+URIs
+are
+intended
+to
+denote,
+and
+the
+kind
+of
+information
+that
+should
+be
+returned
+if
+they
+are
+dereferenced:
+</p>
+<table>
+<tbody>
+<tr>
+<th>
+</th>
+<th>
+Denotes
+</th>
+<th>
+Dereferences
+to
+</th>
+</tr>
+<tr style="vertical-align: top;">
+<td>
+<a class="internalDFN" href="#dfn-target-uri">
+Target-URI
+</a>
+</td>
+<td>
+Any
+resource
+that
+is
+described
+by
+some
+provenance
+-
+typically
+an
+<a class="externalRef" href="http://www.w3.org/TR/prov-dm/#section-entity-activity">
+entity
+</a>
+(in
+the
+sense
+of
+[
+<cite>
+<a class="bibref" href="#bib-PROV-DM">
+PROV-DM
+</a>
+</cite>
+<del class="diff-old">],
+</del>
+<ins class="diff-chg">]),
+</ins>
+but
+may
+be
+<del class="diff-old">an
+</del>
+<ins class="diff-chg">of
+another
+type
+(such
+as
+[
+</ins><cite><a class="bibref" href="#bib-PROV-DM"><ins class="diff-chg">
+PROV-DM
+</ins></a></cite><ins class="diff-chg">
+]
+</ins>
+activity).
+</td>
+<td>
+<del class="diff-old">If
+the
+</del>
+<ins class="diff-chg">Not
+specified
+(the
+</ins>
+URI
+is
+<del class="diff-old">dereferencable,
+it
+should
+return
+a
+representation
+or
+description
+of
+the
+resource
+for
+which
+provenance
+is
+provided.
+</del>
+<ins class="diff-chg">not
+even
+required
+to
+be
+dereferencable).
+</ins>
+</td>
+</tr>
+<tr style="vertical-align: top;">
+<td>
+<a class="internalDFN" href="#dfn-provenance-uri">
+Provenance-URI
+</a>
+</td>
+<td>
+A
+provenance
+record,
+or
+provenance
+description,
+in
+the
+sense
+described
+by
+[
+<cite>
+<a class="bibref" href="#bib-PROV-DM">
+PROV-DM
+</a>
+</cite>
+]
+(
+<a href="http://www.w3.org/TR/prov-dm/#section-prov-overview" class="externalRef">
+PROV
+Overview
+</a>
+).
+</td>
+<td>
+A
+provenance
+record
+in
+any
+defined
+format,
+selectable
+via
+content
+negotiation.
+</td>
+</tr>
+<tr style="vertical-align: top;">
+<td>
+<a class="internalDFN" href="#dfn-service-uri">
+Service-URI
+</a>
+</td>
+<td>
+A
+provenance
+query
+service.
+The
+service-URI
+is
+the
+initial
+URI
+used
+when
+accessing
+a
+provenance
+query
+service;
+following
+REST
+API
+style
+[
+<cite>
+<a class="bibref" href="#bib-REST-APIs">
+REST-APIs
+</a>
+</cite>
+],
+URIs
+for
+accessing
+provenance
+are
+determined
+via
+the
+service
+description.
+</td>
+<td>
+A
+provenance
+query
+service
+description
+per
+<a href="#provenance-query-service-description" class="sectionRef sec-ref">
+section
+4.1
+Provenance
+query
+service
+description
+</a>.
+Alternative
+formats
+may
+be
+offered
+via
+HTTP
+content
+negotiation.
+</td>
+</tr>
+<tr style="vertical-align: top;">
+<td>
+<a class="internalDFN" href="#dfn-pingback-uri">
+Pingback-URI
+</a>
+</td>
+<td>
+A
+provenance
+pingback
+service.
+This
+is
+a
+service
+to
+which
+provenance
+pingback
+information
+can
+be
+submitted
+using
+an
+HTTP
+POST
+operation
+per
+<a href="#provenance-pingback" class="sectionRef sec-ref">
+section
+5.
+<del class="diff-old">Forward
+provenance
+</del>
+<ins class="diff-chg">Provenance
+pingback
+</ins>
+</a>.
+No
+other
+operations
+are
+specified.
+</td>
+<td>
+None
+specified
+(the
+owner
+of
+a
+provenance
+pingback
+URI
+may
+choose
+to
+return
+useful
+information,
+but
+is
+not
+required
+to
+do
+so.)
+</td>
+</tr>
+</tbody>
+</table>
+<p>
+</p>
+</section>
+</section>
+<section id="accessing-provenance-records">
+<h2>
+<span class="secno">
+2.
+</span>
+Accessing
+provenance
+records
+</h2>
+<p>
+This
+specification
+describes
+two
+ways
+to
+access
+<a class="internalDFN" href="#dfn-provenance-record">
+provenance
+record
+</a>
+s:
+</p>
+<ol>
+<li>
+Direct
+access:
+given
+a
+<a class="internalDFN" href="#dfn-provenance-uri">
+provenance-URI
+</a>,
+simply
+dereference
+it,
+and
+</li>
+<li>
+Indirectly
+via
+a
+query
+service:
+given
+the
+URIs
+of
+some
+resource
+(or
+maybe
+other
+information)
+and
+a
+<a class="internalDFN" href="#dfn-provenance-query-service">
+provenance
+query
+service
+</a>,
+use
+the
+service
+to
+access
+provenance
+of
+the
+resource.
+</li>
+</ol>
+<p>
+Web
+applications
+may
+access
+a
+provenance
+record
+in
+the
+same
+way
+as
+any
+resource
+on
+the
+Web,
+by
+dereferencing
+its
+URI
+(commonly
+using
+an
+HTTP
+GET
+operation).
+Thus,
+any
+provenance
+record
+may
+be
+associated
+with
+a
+<a class="internalDFN" href="#dfn-provenance-uri">
+provenance-URI
+</a>,
+and
+may
+be
+accessed
+by
+dereferencing
+that
+URI
+using
+web
+mechanisms.
+How
+much
+or
+how
+little
+provenance
+is
+returned
+in
+a
+provenance
+record
+is
+a
+matter
+for
+the
+provider,
+taking
+account
+that
+a
+provenance
+trace
+may
+extend
+as
+linked
+data
+across
+multiple
+provenance
+records.
+</p>
+<p>
+When
+there
+is
+no
+easy
+way
+to
+associate
+a
+<a class="internalDFN" href="#dfn-provenance-uri">
+provenance-URI
+</a>
+with
+a
+resource
+(e.g.
+for
+resources
+not
+directly
+web-accessible,
+or
+whose
+publication
+mechanism
+is
+controlled
+by
+someone
+else),
+a
+provenance
+description
+may
+be
+obtained
+using
+a
+provenance
+query
+service
+at
+an
+indicated
+<a class="internalDFN" href="#dfn-service-uri">
+service-uri
+</a>.
+A
+REST
+protocol
+for
+provenance
+queries
+is
+defined
+in
+Section
+<a href="#provenance-query-services" class="sectionRef sec-ref">
+section
+4.
+Provenance
+query
+services
+</a>
+;
+also
+described
+there
+is
+a
+mechanism
+for
+locating
+a
+SPARQL
+query
+service
+[
+<cite>
+<a class="bibref" href="#bib-SPARQL-SD">
+SPARQL-SD
+</a>
+</cite>
+].
+</p>
+<p>
+When
+publishing
+provenance,
+corresponding
+<a class="internalDFN" href="#dfn-provenance-uri">
+provenance-URI
+</a>
+s
+or
+<a class="internalDFN" href="#dfn-service-uri">
+service-URI
+</a>
+s
+should
+be
+discoverable
+using
+one
+or
+more
+of
+the
+mechanisms
+described
+in
+<a href="#locating-provenance-records" class="sectionRef sec-ref">
+section
+3.
+Locating
+provenance
+records
+</a>.
+</p>
+<div class="note">
+<div class="note-title" role="heading" aria-level="3">
+<span>
+Note
+</span>
+</div>
+<p class="">
+Provenance
+may
+be
+presented
+as
+a
+<a href="http://www.w3.org/TR/prov-dm/#component4" class="externalRef">
+bundle
+</a>,
+which
+is
+"
+<cite>
+a
+named
+set
+of
+provenance
+descriptions,
+and
+is
+itself
+an
+entity,
+so
+allowing
+provenance
+of
+provenance
+to
+be
+expressed
+</cite>
+"
+[
+<cite>
+<a class="bibref" href="#bib-PROV-DM">
+PROV-DM
+</a>
+</cite>
+].
+A
+provenance
+description
+at
+a
+dereferencable
+provenance-URI
+may
+be
+treated
+as
+a
+bundle,
+and
+this
+is
+a
+good
+way
+to
+make
+provenance
+easily
+accessible.
+But
+there
+are
+other
+possible
+implementations
+of
+a
+bundle,
+such
+as
+a
+named
+graph
+in
+an
+RDF
+dataset
+[
+<cite>
+<a class="bibref" href="#bib-RDF-CONCEPTS11">
+RDF-CONCEPTS11
+</a>
+</cite>
+],
+for
+which
+the
+bundle
+URI
+may
+not
+be
+directly
+dereferencable.
+<br>
+<br>
+When
+a
+bundle
+is
+published
+as
+part
+of
+an
+RDF
+Dataset,
+to
+access
+it
+would
+require
+accessing
+the
+RDF
+Dataset
+and
+then
+extracting
+the
+identified
+graph
+component;
+this
+in
+turn
+would
+require
+knowing
+a
+URI
+or
+some
+other
+way
+to
+retrieve
+the
+RDF
+dataset.
+This
+specification
+does
+not
+describe
+a
+specific
+mechanism
+for
+extracting
+components
+from
+a
+document
+containing
+multiple
+graphs.
+<br>
+<br>
+The
+<abbr title="World Wide Web Consortium">
+W3C
+</abbr>
+Linked
+Data
+Platform
+group
+(
+<a href="http://www.w3.org/2012/ldp/" class="externalRef">
+www.w3.org/2012/ldp/
+</a>
+)
+is
+chartered
+to
+produce
+a
+<abbr title="World Wide Web Consortium">
+W3C
+</abbr>
+Recommendation
+for
+HTTP-based
+(RESTful)
+application
+integration
+patterns
+using
+read/write
+Linked
+Data;
+we
+anticipate
+that
+they
+may
+address
+access
+to
+RDF
+Datasets
+in
+due
+course.
+</p>
+</div>
+</section>
+<section id="locating-provenance-records">
+<h2>
+<span class="secno">
+3.
+</span>
+Locating
+provenance
+records
+</h2>
+<p>
+A
+<a class="internalDFN" href="#dfn-provenance-record">
+provenance
+record
+</a>
+can
+be
+accessed
+using
+direct
+web
+retrieval,
+given
+its
+<a class="internalDFN" href="#dfn-provenance-uri">
+provenance-URI
+</a>.
+If
+this
+is
+known
+in
+advance,
+there
+is
+nothing
+more
+to
+specify.
+If
+a
+provenance-URI
+is
+not
+known
+then
+a
+mechanism
+to
+discover
+one
+must
+be
+based
+on
+information
+that
+is
+available
+to
+the
+would-be
+accessor.
+Likewise,
+provenance
+may
+be
+exposed
+by
+a
+query
+service,
+in
+which
+case,
+the
+corresponding
+<a class="internalDFN" href="#dfn-service-uri">
+service-URI
+</a>
+must
+be
+discovered.
+</p>
+<p>
+Three
+mechanisms
+are
+defined
+for
+a
+provenance
+<a class="internalDFN" href="#dfn-consumer">
+consumer
+</a>
+to
+find
+information
+about
+a
+<a class="internalDFN" href="#dfn-provenance-uri">
+provenance-URI
+</a>
+or
+<a class="internalDFN" href="#dfn-service-uri">
+service-URI
+</a>,
+along
+with
+a
+<a class="internalDFN" href="#dfn-target-uri">
+target-URI
+</a>:
+</p>
+<ol>
+<li>
+The
+consumer
+knows
+the
+resource
+URI
+<em>
+and
+</em>
+the
+resource
+is
+accessible
+using
+HTTP
+</li>
+<li>
+The
+consumer
+has
+a
+copy
+of
+a
+resource
+represented
+as
+HTML
+or
+XHTML
+</li>
+<li>
+The
+consumer
+has
+a
+copy
+of
+a
+resource
+represented
+as
+RDF
+(including
+the
+range
+of
+possible
+RDF
+syntaxes,
+such
+as
+HTML
+with
+embedded
+RDFa)
+</li>
+</ol>
+<p>
+These
+particular
+cases
+are
+selected
+as
+corresponding
+to
+current
+primary
+web
+protocol
+and
+data
+formats.
+Similar
+approaches
+may
+be
+defined
+for
+other
+protocols
+or
+resource
+formats.
+</p>
+<p>
+Provenance
+records
+may
+be
+offered
+by
+several
+<a class="internalDFN" href="#dfn-provider">
+provider
+</a>
+s
+other
+than
+that
+of
+the
+original
+resource
+publisher,
+each
+with
+different
+concerns,
+and
+presenting
+provenance
+at
+different
+locations.
+It
+is
+possible
+that
+these
+different
+providers
+may
+present
+contradictory
+provenance.
+</p>
+<section id="resource-accessed-by-http">
+<h3>
+<span class="secno">
+3.1
+</span>
+Resource
+accessed
+by
+HTTP
+</h3>
+<p>
+For
+a
+resource
+accessible
+using
+HTTP,
+a
+provenance
+record
+may
+be
+indicated
+using
+an
+HTTP
+<code>
+Link
+</code>
+header
+field,
+as
+defined
+by
+<a href="http://tools.ietf.org/html/rfc5988#section-5" class="externalRef">
+Web
+Linking
+(RFC
+5988)
+</a>
+[
+<cite>
+<a class="bibref" href="#bib-LINK-REL">
+LINK-REL
+</a>
+</cite>
+].
+The
+<code>
+Link
+</code>
+header
+field
+is
+included
+in
+the
+HTTP
+response
+to
+a
+GET
+or
+HEAD
+operation
+(other
+HTTP
+operations
+are
+not
+excluded,
+but
+are
+not
+considered
+here).
+</p>
+<p>
+A
+<code>
+has_provenance
+</code>
+link
+relation
+type
+for
+referencing
+a
+provenance
+record
+may
+be
+used
+thus:
+</p>
+ <pre class="pattern">Link: <<cite>provenance-URI</cite>>;
+ rel="http://www.w3.org/ns/prov#has_provenance";
+anchor="
+<cite>
+target-URI
+</cite>
+"
+</pre>
+<p>
+When
+used
+in
+conjunction
+with
+an
+HTTP
+success
+response
+code
+(
+<code>
+2xx
+</code>
+),
+this
+HTTP
+header
+field
+indicates
+that
+<code>
+<cite>
+provenance-URI
+</cite>
+</code>
+is
+the
+URI
+of
+a
+provenance
+record
+about
+the
+originally
+requested
+resource,
+and
+that
+the
+requested
+resource
+is
+identified
+within
+the
+provenance
+record
+as
+<code>
+<cite>
+target-URI
+</cite>
+</code>.
+(See
+also
+<a href="#interpreting-provenance-records" class="sectionRef sec-ref">
+section
+1.3
+Interpreting
+provenance
+records
+</a>.)
+</p>
+<p>
+If
+no
+<code>
+anchor
+</code>
+parameter
+is
+provided
+then
+the
+<code>
+<cite>
+target-URI
+</cite>
+</code>
+is
+assumed
+to
+be
+the
+URI
+of
+the
+requested
+resource
+used
+in
+the
+corresponding
+HTTP
+request.
+</p>
+<p>
+This
+<del class="diff-old">specification
+</del>
+<ins class="diff-chg">note
+</ins>
+does
+not
+define
+the
+meaning
+of
+these
+links
+returned
+with
+other
+HTTP
+response
+codes:
+future
+revisions
+may
+define
+interpretations
+for
+these.
+</p>
+<p>
+An
+HTTP
+response
+<em class="rfc2119" title="MAY">
+MAY
+</em>
+include
+multiple
+<code>
+has_provenance
+</code>
+link
+header
+fields,
+indicating
+a
+number
+of
+different
+provenance
+resources
+(and
+anchors)
+that
+are
+known
+to
+the
+responding
+server,
+each
+referencing
+a
+provenance
+record
+about
+the
+accessed
+resource.
+</p>
+<p>
+The
+presence
+of
+a
+<code>
+has_provenance
+</code>
+link
+in
+an
+HTTP
+response
+does
+not
+preclude
+the
+possibility
+that
+other
+providers
+<ins class="diff-new">also
+</ins>
+may
+offer
+provenance
+records
+about
+the
+same
+resource.
+In
+such
+cases,
+discovery
+of
+the
+additional
+provenance
+records
+must
+use
+other
+means
+(e.g.
+see
+<a href="#provenance-query-services" class="sectionRef sec-ref">
+section
+4.
+Provenance
+query
+services
+</a>
+).
+</p>
+<p>
+An
+example
+<del class="diff-old">request
+</del>
+<ins class="diff-chg">HTTP
+response
+</ins>
+including
+provenance
+headers
+<del class="diff-old">in
+its
+response
+</del>
+might
+look
+like
+this
+(where
+<code>
+C:
+</code>
+and
+<code>
+S:
+</code>
+prefixes
+indicate
+client
+and
+server
+emitted
+data
+respectively):
+</p>
+<del class="diff-old"> C: GET http://example.com/resource/ HTTP/1.1
+</del>
+ <div class="example"><div class="example-title"><span>Example 1</span></div><pre class="example code">C: GET http://example.com/resource123/ HTTP/1.1
+C: Accept: text/html
+S: HTTP/1.1 200 OK
+S: Content-type: text/html
+<del class="diff-old">S: Link: <http://example.com/resource/provenance/>;
+</del>
+<ins class="diff-chg">S: Link: <http://example.com/resource123/provenance/>;
+</ins>
+ rel="http://www.w3.org/ns/prov#has_provenance";
+<del class="diff-old"> anchor="http://example.com/resource/"
+</del>
+<ins class="diff-chg"> anchor="http://example.com/resource123/"
+</ins>
+S:
+S: <html ...>
+S: :
+S:
+</html>
+</pre>
+</div>
+<del class="diff-old">Tim
+comment
+(14):
+Should
+a
+reference
+to
+the
+forward
+provenance
+section
+be
+included,
+too?
+[GK]
+I
+don't
+see
+the
+need.
+Forward
+provenance
+is
+not
+primarily
+*about*
+the
+same
+resource,
+IMO,
+and
+I
+think
+mentioning
+it
+here
+could
+be
+more
+confusing
+than
+helpful.
+</del>
+<section id="specifying-provenance-query-services">
+<h4>
+<span class="secno">
+3.1.1
+</span>
+Specifying
+Provenance
+Query
+Services
+</h4>
+<p>
+The
+resource
+provider
+may
+indicate
+that
+provenance
+records
+about
+the
+resource
+are
+provided
+by
+a
+<a class="internalDFN" href="#dfn-provenance-query-service">
+provenance
+query
+service
+</a>.
+This
+is
+done
+through
+the
+use
+of
+a
+<code>
+has_query_service
+</code>
+link
+relation
+type
+following
+the
+same
+pattern
+as
+above:
+</p>
+ <pre class="pattern">Link: <<cite>service-URI</cite>>;
+ rel="http://www.w3.org/ns/prov#has_query_service";
+ anchor="<cite>target-URI</cite>"
+</pre>
+<p>
+The
+<code>
+has_query_service
+</code>
+link
+identifies
+the
+<a class="internalDFN" href="#dfn-service-uri">
+service-URI
+</a>.
+Dereferencing
+this
+URI
+yields
+a
+service
+description
+that
+provides
+further
+information
+to
+enable
+a
+client
+to
+submit
+a
+query
+to
+retrieve
+a
+<a class="internalDFN" href="#dfn-provenance-record">
+provenance
+record
+</a>
+for
+a
+<a class="internalDFN" href="#dfn-resource">
+resource
+</a>
+;
+see
+<a href="#provenance-query-services" class="sectionRef sec-ref">
+section
+4.
+Provenance
+query
+services
+</a>
+for
+more
+details.
+</p>
+ <div class="example"><div class="example-title"><span>Example 2</span></div><pre class="example code">C: GET http://example.com/resource123/ HTTP/1.1
+<ins class="diff-new">C: Accept: text/html
+S: HTTP/1.1 200 OK
+S: Content-type: text/html
+S: Link: <http://example.com/resource123/provenance-query/>;
+ rel="http://www.w3.org/ns/prov#has_query_service";
+ anchor="http://example.com/resource123/"
+S:
+S: <html ...>
+S: :
+S:
+</html>
+</ins></pre></div>
+<p>
+There
+<del class="diff-old">may
+</del>
+<em class="rfc2119" title="MAY">
+<ins class="diff-chg">MAY
+</ins></em>
+be
+multiple
+<code>
+has_query_service
+</code>
+link
+header
+fields,
+and
+these
+<em class="rfc2119" title="MAY">
+MAY
+</em>
+appear
+in
+an
+HTTP
+response
+together
+with
+<code>
+has_provenance
+</code>
+link
+header
+fields.
+</p>
+<del class="diff-old"> C: GET http://example.com/resource/ HTTP/1.1
+C: Accept: text/html
+S: HTTP/1.1 200 OK
+S: Content-type: text/html
+S: Link: <http://example.com/resource/provenance/>;
+ rel="http://www.w3.org/ns/prov#has_query_service";
+ anchor="http://example.com/resource/"
+S:
+S: <html ...>
+S: :
+S:
+</html>
+</del>
+</section>
+<section id="content-negotiation-redirection-and-link-headers">
+<h4>
+<span class="secno">
+3.1.2
+</span>
+Content
+negotiation,
+redirection
+and
+Link:
+headers
+</h4>
+<p>
+When
+performing
+content
+negotiation
+for
+a
+resource,
+it
+is
+common
+for
+HTTP
+302
+or
+303
+redirect
+response
+codes
+to
+be
+used
+to
+direct
+a
+client
+to
+an
+appropriately-formatted
+resource.
+When
+accessing
+a
+resource
+for
+which
+provenance
+is
+available,
+link
+headers
+<em class="rfc2119" title="SHOULD">
+SHOULD
+</em>
+be
+included
+with
+the
+response
+to
+the
+final
+redirected
+request,
+and
+not
+on
+the
+intermediate
+303
+responses.
+(When
+accessing
+a
+resource
+from
+a
+browser
+using
+Javascript,
+the
+intermediate
+303
+responses
+are
+usually
+handled
+transparently
+by
+the
+browser
+and
+are
+not
+visible
+to
+the
+HTTP
+client
+code.)
+</p>
+<p>
+Following
+content
+negotiation,
+any
+provenance
+link
+returned
+refers
+to
+the
+resource
+whose
+URI
+is
+used
+in
+the
+corresponding
+HTTP
+request,
+or
+the
+given
+anchor
+parameter
+if
+that
+is
+different.
+</p>
+<p>
+An
+example
+transaction
+using
+content
+negotiation
+and
+redirection
+might
+look
+like
+this
+(where
+<code>
+C:
+</code>
+and
+<code>
+S:
+</code>
+prefixes
+indicate
+client
+and
+server
+emitted
+data
+respectively):
+</p>
+<del class="diff-old"> C: GET http://example.com/resource/ HTTP/1.1
+</del>
+ <div class="example"><div class="example-title"><span>Example 3</span></div><pre class="example code">C: GET http://example.com/resource123/ HTTP/1.1
+C: Accept: text/html
+S: HTTP/1.1 302 Found
+<del class="diff-old">S: Location: /resource/content.html
+</del>
+<ins class="diff-chg">S: Location: /resource123/content.html
+</ins>
+S: Vary: Accept
+S:
+<del class="diff-old">S: HTML content for http://example.com/resource/
+S: is available at http://example.com/resource/content.html
+</del>
+<ins class="diff-chg">S: HTML content for http://example.com/resource123/
+S: is available at http://example.com/resource123/content.html
+</ins>
+<del class="diff-old">C: GET http://example.com/resource/content.html HTTP/1.1
+</del>
+<ins class="diff-chg">C: GET http://example.com/resource123/content.html HTTP/1.1
+</ins>
+C: Accept: text/html
+S: HTTP/1.1 200 OK
+S: Content-type: text/html
+<del class="diff-old">S: Link: <http://example.com/resource/provenance/>;
+</del>
+<ins class="diff-chg">S: Link: <http://example.com/resource123/provenance/>;
+</ins>
+ rel="http://www.w3.org/ns/prov#has_provenance";
+<del class="diff-old"> anchor="http://example.com/resource/20130226/content.html"
+</del>
+<ins class="diff-chg"> anchor="http://example.com/resource123/20130226/content.html"
+</ins>
+S:
+S: <html>
+S: <!-- HTML content here... -->
+S:
+</html>
+</pre>
+</div>
+<p>
+<ins class="diff-new">This
+example
+indicates
+a
+provenance
+record
+at
+</ins><code><ins class="diff-new">
+http://example.com/resource123/provenance/
+</ins></code>,<ins class="diff-new">
+which
+uses
+</ins><code><ins class="diff-new">
+http://example.com/resource123/20130226/content.html
+</ins></code><ins class="diff-new">
+as
+the
+target-URI
+for
+the
+requested
+resource.
+If
+the
+</ins><code><ins class="diff-new">
+anchor=
+</ins></code><ins class="diff-new">
+parameter
+were
+to
+be
+omitted
+from
+the
+</ins><code><ins class="diff-new">
+Link
+</ins></code><ins class="diff-new">
+header
+field,
+the
+indicated
+target-URI
+would
+be
+</ins><code><ins class="diff-new">
+http://example.com/resource123/content.html
+</ins></code>.</p>
+</section>
+</section>
+<section id="resource-represented-as-html">
+<h3>
+<span class="secno">
+3.2
+</span>
+Resource
+represented
+as
+HTML
+</h3>
+<div>
+For
+a
+document
+presented
+as
+HTML
+or
+XHTML,
+without
+regard
+for
+how
+it
+has
+been
+obtained,
+a
+provenance
+record
+may
+be
+associated
+with
+a
+resource
+by
+adding
+a
+<code>
+<link>
+</code>
+element
+to
+the
+HTML
+<code>
+<head>
+</code>
+section.
+Two
+link
+relation
+types
+for
+referencing
+provenance
+may
+be
+used:
+<del class="diff-old"> <html xmlns="http://www.w3.org/1999/xhtml">
+</del>
+ <pre class="pattern"> <html>
+ <head>
+ <b><link rel="http://www.w3.org/ns/prov#has_provenance" href="<cite>provenance-URI</cite>"></b>
+ <b><link rel="http://www.w3.org/ns/prov#has_anchor" href="<cite>target-URI</cite>"></b>
+ <title>Welcome to example.com</title>
+ </head>
+ <body>
+ <!-- HTML content here... -->
+ </body>
+</html>
+</pre>
+</div>
+<p>
+The
+<code>
+<cite>
+provenance-URI
+</cite>
+</code>
+given
+by
+the
+first
+link
+element
+(
+<code>
+#has_provenance
+</code>
+)
+identifies
+the
+provenance-URI
+for
+the
+document.
+</p>
+<p>
+The
+<code>
+<cite>
+target-URI
+</cite>
+</code>
+given
+by
+the
+second
+link
+element
+(
+<code>
+#has_anchor
+</code>
+)
+specifies
+an
+identifier
+for
+the
+document
+that
+may
+be
+used
+within
+the
+provenance
+record
+when
+referring
+to
+the
+document.
+</p>
+<p>
+If
+no
+<code>
+<cite>
+target-URI
+</cite>
+</code>
+is
+provided
+(via
+a
+<code>
+#has_anchor
+</code>
+link
+element)
+then
+is
+it
+is
+assumed
+to
+be
+the
+URI
+of
+the
+document.
+It
+is
+<em class="rfc2119" title="RECOMMENDED">
+RECOMMENDED
+</em>
+that
+this
+convention
+be
+used
+only
+when
+the
+document
+has
+a
+URI
+that
+is
+reasonably
+expected
+to
+be
+known
+or
+easily
+discoverable
+by
+a
+consumer
+of
+the
+document
+(e.g.
+when
+delivered
+from
+a
+web
+server,
+or
+as
+part
+of
+a
+MIME
+structure
+containing
+content
+identifiers
+[
+<cite>
+<a class="bibref" href="#bib-RFC2392">
+RFC2392
+</a>
+</cite>
+]).
+</p>
+<p>
+An
+HTML
+document
+header
+<em class="rfc2119" title="MAY">
+MAY
+</em>
+present
+multiple
+<code>
+<cite>
+provenance-URI
+</cite>
+</code>
+s
+over
+several
+<code>
+#has_provenance
+</code>
+link
+elements,
+indicating
+a
+number
+of
+different
+provenance
+records
+that
+are
+known
+to
+the
+publisher
+of
+the
+document,
+each
+of
+which
+may
+provide
+provenance
+about
+the
+document
+(see
+<a href="#interpreting-provenance-records" class="sectionRef sec-ref">
+section
+1.3
+Interpreting
+provenance
+records
+</a>
+).
+</p>
+<del class="diff-old">Check
+</del>
+<div class="note">
+<div class="note-title" role="heading" aria-level="4">
+<span>
+<ins class="diff-chg">Note
+</ins></span></div><p class=""><ins class="diff-chg">
+The
+mechanisms
+used
+</ins>
+with
+<del class="diff-old">Dong:
+I
+think
+the
+cross
+reference
+should
+make
+the
+assumptions
+explicit.
+I,
+too,
+feel
+this
+material
+is
+not
+strictly
+needed,
+but
+was
+previously
+asked
+</del>
+<ins class="diff-chg">HTTP
+and
+HTML/RDF
+are
+slightly
+inconsistent
+in
+their
+approach
+</ins>
+to
+<del class="diff-old">add
+some
+clarification
+about
+mutliple
+links.
+</del>
+<ins class="diff-chg">specifying
+</ins><code><cite><ins class="diff-chg">
+target-URI
+</ins></cite></code><ins class="diff-chg">
+values.
+In
+HTTP
+</ins><code><ins class="diff-chg">
+Link
+</ins></code><ins class="diff-chg">
+header
+fields,
+an
+optional
+</ins><code><ins class="diff-chg">
+anchor=
+</ins></code><ins class="diff-chg">
+parameter
+may
+be
+supplied
+for
+each
+such
+header.
+In
+HTML
+and
+RDF,
+separate
+</ins><code><ins class="diff-chg">
+#has_anchor
+</ins></code><ins class="diff-chg">
+relations
+are
+defined.
+It
+was
+felt
+that
+avoiding
+reinvention
+of
+existing
+mechanisms
+was
+more
+important
+than
+being
+completely
+consistent.
+If
+anchors
+are
+processed
+as
+described
+in
+</ins><a href="#interpreting-provenance-records" class="sectionRef sec-ref"><ins class="diff-chg">
+section
+1.3
+Interpreting
+provenance
+records
+</ins></a><ins class="diff-chg">
+(3rd
+paragraph),
+observable
+behaviour
+across
+all
+approaches
+should
+be
+consistent.
+</ins>
+</p>
+</div>
+<section id="specifying-provenance-query-services-1">
+<h4>
+<span class="secno">
+3.2.1
+</span>
+Specifying
+Provenance
+Query
+Services
+</h4>
+<p>
+The
+document
+creator
+may
+specify
+that
+the
+provenance
+about
+the
+document
+is
+provided
+by
+a
+<a class="internalDFN" href="#dfn-provenance-query-service">
+provenance
+query
+service
+</a>.
+This
+is
+done
+through
+the
+use
+of
+a
+third
+link
+relation
+type
+following
+the
+same
+pattern
+as
+above:
+</p>
+ <pre class="pattern"> <html xmlns="http://www.w3.org/1999/xhtml">
+ <head>
+ <b><link rel="http://www.w3.org/ns/prov#has_query_service" href="<cite>service-URI</cite>"></b>
+ <b><link rel="http://www.w3.org/ns/prov#has_anchor" href="<cite>target-URI</cite>"></b>
+ <title>Welcome to example.com</title>
+ </head>
+ <body>
+ <!-- HTML content here... -->
+ </body>
+</html>
+</pre>
+<p>
+The
+<code>
+has_query_service
+</code>
+link
+element
+identifies
+the
+<a class="internalDFN" href="#dfn-service-uri">
+service-URI
+</a>.
+Dereferencing
+this
+URI
+yields
+a
+service
+description
+that
+provides
+further
+information
+to
+enable
+a
+client
+to
+query
+for
+provenance
+about
+a
+resource;
+see
+<a href="#provenance-query-services" class="sectionRef sec-ref">
+section
+4.
+Provenance
+query
+services
+</a>
+for
+more
+details.
+</p>
+<p>
+There
+<em class="rfc2119" title="MAY">
+MAY
+</em>
+be
+multiple
+<code>
+#has_query_service
+</code>
+link
+elements,
+and
+these
+<em class="rfc2119" title="MAY">
+MAY
+</em>
+appear
+in
+the
+same
+document
+as
+<code>
+#has_provenance
+</code>
+link
+elements
+(though
+we
+do
+not
+anticipate
+that
+<code>
+#has_provenance
+</code>
+and
+<code>
+#has_query_service
+</code>
+link
+relations
+will
+commonly
+be
+used
+together).
+</p>
+<del class="diff-old">Check
+with
+Dong:
+This
+test
+was
+already
+revised
+in
+response
+to
+earlier
+comment.
+I,
+too,
+feel
+this
+material
+is
+not
+strictly
+needed,
+but
+was
+previously
+asked
+to
+add
+some
+clarification.
+</del>
+</section>
+</section>
+<section id="resource-represented-as-rdf">
+<h3>
+<span class="secno">
+3.3
+</span>
+Resource
+represented
+as
+RDF
+</h3>
+<p>
+If
+a
+resource
+is
+represented
+as
+RDF
+(in
+any
+of
+its
+recognized
+syntaxes,
+including
+RDFa),
+it
+may
+contain
+references
+to
+its
+own
+provenance
+using
+additional
+RDF
+statements.
+For
+this
+<del class="diff-old">purpose
+</del>
+<ins class="diff-chg">purpose,
+</ins>
+the
+link
+relations
+introduced
+above
+(
+<a href="#locating-provenance-records" class="sectionRef sec-ref">
+section
+3.
+Locating
+provenance
+records
+</a>
+)
+may
+be
+used
+as
+RDF
+properties:
+<code>
+prov:has_provenance
+</code>,
+<code>
+prov:has_anchor
+</code>,
+and
+<code>
+prov:has_query_service
+</code>,
+where
+the
+<code>
+prov:
+</code>
+prefix
+here
+indicates
+the
+PROV
+namespace
+URI
+<code>
+http://www.w3.org/ns/prov#
+</code>.
+</p>
+<p>
+The
+RDF
+property
+<code>
+prov:has_provenance
+</code>
+is
+a
+relation
+between
+two
+resources,
+where
+the
+object
+of
+the
+property
+is
+a
+<a class="internalDFN" href="#dfn-provenance-uri">
+provenance-URI
+</a>
+that
+denotes
+a
+provenance
+record
+about
+the
+subject
+resource.
+Multiple
+<code>
+prov:has_provenance
+</code>
+assertions
+may
+be
+made
+about
+a
+subject
+resource.
+</p>
+<p>
+Property
+<code>
+prov:has_anchor
+</code>
+specifies
+a
+<a class="internalDFN" href="#dfn-target-uri">
+target-URI
+</a>
+used
+in
+the
+indicated
+provenance
+to
+refer
+to
+the
+containing
+RDF
+document.
+</p>
+<p>
+Property
+<code>
+prov:has_query_service
+</code>
+specifies
+a
+<a class="internalDFN" href="#dfn-service-uri">
+service-URI
+</a>
+for
+provenance
+queries.
+</p>
+ <div class="example"><div class="example-title"><span>Example 4</span></div><pre class="example code">@prefix prov: <http://www.w3.org/ns/prov#>.
+<> dcterms:title "Welcome to example.com" ;
+ prov:has_anchor <http://example.com/data/resource.rdf> ;
+ prov:has_provenance <http://example.com/provenance/resource.rdf> ;
+ prov:has_query_service <http://example.com/provenance-query-service/> .
+#
+(More
+RDF
+data
+...)
+</pre>
+</div>
+<p>
+(The
+above
+example
+uses
+Turtle
+RDF
+syntax
+[
+<cite>
+<a class="bibref" href="#bib-TURTLE">
+TURTLE
+</a>
+</cite>
+].)
+</p>
+<div class="note">
+<div class="note-title" role="heading" aria-level="4">
+<span>
+Note
+</span>
+</div>
+<p class="">
+These
+terms
+(
+<code>
+prov:has_provenance
+</code>,
+<code>
+prov:has_anchor
+</code>,
+and
+<code>
+prov:has_query_service
+</code>
+)
+may
+be
+also
+used
+in
+RDF
+statements
+with
+other
+subjects
+to
+indicate
+provenance
+of
+other
+resources,
+but
+discussion
+of
+such
+use
+is
+beyond
+the
+scope
+of
+this
+document.
+<br>
+<br>
+<ins class="diff-new">See
+also
+the
+note
+about
+target-URIs
+at
+the
+end
+of
+</ins><a href="#resource-represented-as-html" class="sectionRef sec-ref"><ins class="diff-new">
+section
+3.2
+Resource
+represented
+as
+HTML
+</ins></a>.
+</p>
+</div>
+</section>
+</section>
+<section id="provenance-query-services">
+<h2>
+<span class="secno">
+4.
+</span>
+Provenance
+query
+services
+</h2>
+<p>
+This
+section
+describes
+a
+simple
+HTTP
+query
+protocol
+for
+accessing
+provenance
+records,
+and
+also
+a
+mechanism
+for
+locating
+a
+SPARQL
+service
+endpoint
+[
+<cite>
+<a class="bibref" href="#bib-SPARQL-SD">
+SPARQL-SD
+</a>
+</cite>
+].
+The
+HTTP
+<ins class="diff-new">query
+</ins>
+protocol
+specifies
+HTTP
+operations
+<ins class="diff-new">[
+</ins><cite><a class="bibref" href="#bib-HTTP11"><ins class="diff-new">
+HTTP11
+</ins></a></cite><ins class="diff-new">
+]
+</ins>
+for
+retrieving
+provenance
+records
+from
+a
+provenance
+query
+service,
+following
+the
+approach
+of
+the
+SPARQL
+Graph
+Store
+HTTP
+Protocol
+[
+<cite>
+<a class="bibref" href="#bib-SPARQL-HTTP">
+SPARQL-HTTP
+</a>
+</cite>
+].
+</p>
+<p>
+The
+introduction
+of
+query
+services
+is
+motivated
+by
+the
+following
+possible
+considerations:
+</p>
+<ul>
+<li>
+third-party
+providers
+of
+provenance
+descriptions
+may
+be
+unable
+to
+use
+the
+mechanisms
+of
+Section
+3
+because
+the
+corresponding
+<a class="internalDFN" href="#dfn-target-uri">
+target-URI
+</a>
+is
+outside
+their
+control;
+</li>
+<li>
+services
+unknown
+to
+the
+original
+publisher
+may
+have
+provenance
+records
+about
+the
+same
+resource;
+</li>
+<li>
+there
+is
+no
+known
+dereferencable
+<a class="internalDFN" href="#dfn-provenance-uri">
+provenance-URI
+</a>
+or
+a
+particular
+entity;
+</li>
+<li>
+query
+services
+may
+provide
+additional
+filters
+over
+what
+provenance
+is
+returned;
+and
+</li>
+<li>
+query
+services
+may
+support
+more
+expressive
+selections,
+such
+as
+"which
+entities
+were
+derived
+from
+entities
+attributed
+to
+agent
+X".
+</li>
+</ul>
+<p>
+The
+patterns
+for
+using
+provenance
+query
+services
+are
+designed
+around
+REST
+principles
+[
+<cite>
+<a class="bibref" href="#bib-REST">
+REST
+</a>
+</cite>
+],
+which
+aim
+to
+minimize
+coupling
+between
+client
+and
+server
+implementation
+details.
+</p>
+<p>
+The
+query
+mechanisms
+provided
+by
+a
+<a class="internalDFN" href="#dfn-provenance-query-service">
+provenance
+query
+service
+</a>
+are
+described
+by
+a
+service
+description,
+which
+is
+obtained
+by
+dereferencing
+a
+<a class="internalDFN" href="#dfn-service-uri">
+service-URI
+</a>.
+A
+service
+description
+may
+contain
+information
+about
+additional
+mechanisms
+that
+are
+not
+described
+here.
+In
+keeping
+with
+REST
+practice
+for
+web
+applications,
+alternative
+service
+descriptions
+using
+different
+formats
+may
+be
+offered
+and
+accessed
+using
+HTTP
+content
+negotiation.
+We
+describe
+below
+a
+service
+description
+format
+that
+uses
+RDF
+to
+describe
+two
+query
+mechanisms.
+</p>
+<p>
+The
+general
+procedure
+for
+using
+a
+provenance
+query
+service
+is:
+</p>
+<ol>
+<li>
+retrieve
+the
+service
+description;
+</li>
+<li>
+within
+the
+service
+description,
+locate
+information
+about
+a
+recognized
+query
+mechanism
+(ignoring
+unrecognized
+descriptions
+if
+the
+description
+covers
+multiple
+service
+options);
+</li>
+<li>
+if
+a
+recognized
+query
+mechanism
+is
+found,
+extract
+information
+needed
+to
+use
+that
+mechanism
+(e.g.
+a
+URI
+template
+or
+a
+SPARQL
+service
+endpoint
+URI);
+and
+</li>
+<li>
+use
+the
+information
+obtained
+to
+query
+for
+required
+provenance,
+using
+the
+selected
+query
+mechanism.
+</li>
+</ol>
+<p>
+The
+remainder
+of
+this
+section
+covers
+the
+following
+topics:
+</p>
+<ul>
+<li>
+<a class="sectionRef sec-ref" href="#provenance-query-service-description">
+section
+4.1
+Provenance
+query
+service
+description
+</a>
+-
+describes
+an
+RDF-based
+service
+description
+format
+and
+vocabularies
+to
+convey
+information
+about
+direct
+HTTP
+query
+and/or
+SPARQL
+service
+options.
+<ul>
+<li>
+<a class="sectionRef sec-ref" href="#direct-http-query-service-description">
+section
+4.1.1
+Direct
+HTTP
+query
+service
+description
+</a>
+-
+RDF
+structure
+for
+describing
+a
+direct
+HTTP
+query
+service.
+</li>
+</ul>
+<ul>
+<li>
+<a class="sectionRef sec-ref" href="#sparql-query-service-description">
+section
+4.1.2
+SPARQL
+query
+service
+description
+</a>
+-
+RDF
+structure
+for
+describing
+a
+SPARQL
+query
+service.
+</li>
+</ul>
+</li>
+<li>
+<a class="sectionRef sec-ref" href="#direct-http-query-service-invocation">
+section
+4.2
+Direct
+HTTP
+query
+service
+invocation
+</a>
+-
+describes
+how
+to
+perform
+a
+direct
+HTTP
+query
+for
+provenance,
+using
+information
+obtained
+from
+the
+service
+description.
+</li>
+<li>
+<a class="sectionRef sec-ref" href="#provenance-query-service-discovery">
+section
+4.3
+Provenance
+query
+service
+discovery
+</a>
+-
+briefly
+discusses
+some
+possible
+approaches
+to
+discovery
+of
+provenance
+query
+services.
+</li>
+</ul>
+<section id="provenance-query-service-description">
+<h3>
+<span class="secno">
+4.1
+</span>
+Provenance
+query
+service
+description
+</h3>
+<del class="diff-old">Review.
+Stian
+suggests
+recommending
+use
+of
+JSON-LD.
+I
+am
+resisting
+this
+because
+it
+is
+clearly
+allowed
+by
+"RDF
+(in
+any
+of
+its
+common
+serializations
+as
+determined
+by
+HTTP
+content
+negotiation)",
+focusing
+on
+a
+particular
+format
+as
+part
+of
+the
+underlying
+mechanism
+seems
+to
+go
+against
+REST
+principles,
+and
+at
+this
+stage
+it
+seems
+that
+promoting
+any
+particular
+format
+will
+draw
+objections
+from
+proponents
+of
+other
+formats.
+I've
+taken
+a
+different
+tack,
+making
+the
+text
+more
+open
+about
+possible
+service
+description
+formats,
+while
+specifically
+presenting
+a
+description
+based
+on
+the
+RDF
+model.
+</del>
+<p>
+Dereferencing
+a
+<a class="internalDFN" href="#dfn-service-uri">
+service-URI
+</a>
+yields
+a
+service
+description.
+The
+service
+description
+<del class="diff-old">presented
+here
+</del>
+may
+be
+<del class="diff-old">supplied
+as
+RDF
+(in
+</del>
+<ins class="diff-chg">in
+</ins>
+any
+<del class="diff-old">of
+its
+common
+serializations
+as
+determined
+by
+HTTP
+</del>
+<ins class="diff-chg">format
+selectable
+through
+</ins>
+content
+<del class="diff-old">negotiation),
+</del>
+<ins class="diff-chg">negotiation,
+</ins>
+and
+it
+may
+contain
+descriptions
+of
+one
+or
+more
+available
+query
+mechanisms.
+<del class="diff-old">Each
+</del>
+<ins class="diff-chg">The
+format
+described
+here
+uses
+RDF,
+serialized
+as
+Turtle
+[
+</ins><cite><a class="bibref" href="#bib-TURTLE"><ins class="diff-chg">
+TURTLE
+</ins></a></cite><ins class="diff-chg">
+],
+but
+any
+selectable
+RDF
+serialization
+could
+be
+used.
+In
+this
+RDF
+service
+description,
+each
+</ins>
+query
+mechanism
+is
+associated
+with
+an
+RDF
+type,
+as
+explained
+below.
+<del class="diff-old">(The
+presentation
+here
+of
+RDF
+service
+descriptions
+does
+not
+preclude
+use
+of
+non-RDF
+formats
+selectable
+by
+HTTP
+content
+negotiation.)
+</del>
+</p>
+<p>
+The
+overall
+structure
+of
+a
+service
+description
+is
+as
+follows:
+</p>
+ <pre class="pattern"><<cite>service-URI</cite>> a prov:ServiceDescription ;
+ prov:describesService <<cite>direct-query-description</cite>>, <<cite>sparql-query-description</cite>> .
+<<cite>direct-query-description</cite>> a prov:DirectQueryService ;
+ prov:provenanceUriTemplate "<cite>direct-query-template</cite>"
+ .
+<<cite>sparql-query-description</cite>> a sd:Service ;
+ sd:endpoint <<cite>sparql-query</cite>> ;
+ # other details...
+ .
+</pre>
+<p>
+We
+see
+here
+that
+the
+<code>
+<cite>
+service-URI
+</cite>
+</code>
+identifies
+a
+resource
+of
+type
+<code>
+prov:ServiceDescription
+</code>,
+which
+collects
+descriptions
+of
+one
+or
+more
+provenance
+query
+mechanisms.
+Each
+associated
+mechanism
+is
+indicated
+by
+a
+<code>
+prov:describesService
+</code>
+statement.
+</p>
+<del class="diff-old">Note
+We
+expect
+the
+presentation
+of
+service
+descriptions
+to
+be
+considered
+by
+the
+W3C
+Linked
+Data
+Platform
+group
+(
+www.w3.org/2012/ldp/
+);
+at
+the
+time
+of
+writing,
+there
+is
+no
+consensus
+(cf.
+message
+at
+lists.w3.org/Archives/Public/public-ldp/2012Nov/0036.html
+and
+responses).
+As
+and
+when
+such
+consensus
+emerges,
+we
+recommend
+that
+provenance
+query
+service
+implementers
+consider
+adopting
+it,
+or
+at
+least
+consider
+making
+their
+implementations
+compatible
+with
+it.
+</del>
+<section id="direct-http-query-service-description">
+<h4>
+<span class="secno">
+4.1.1
+</span>
+Direct
+HTTP
+query
+service
+description
+</h4>
+<p>
+A
+direct
+HTTP
+query
+service
+is
+described
+by
+an
+RDF
+resource
+of
+type
+<code>
+prov:DirectQueryService
+</code>.
+It
+allows
+for
+accessing
+provenance
+about
+a
+specified
+<a class="internalDFN" href="#dfn-target-uri">
+target-URI
+</a>.
+The
+query
+URI
+to
+use
+is
+described
+by
+a
+URI
+Template
+[
+<cite>
+<a class="bibref" href="#bib-URI-template">
+URI-template
+</a>
+</cite>
+]
+(level
+2
+or
+above)
+in
+which
+<del class="diff-old">which
+</del>
+the
+variable
+<cite>
+<code>
+uri
+</code>
+</cite>
+stands
+for
+the
+<del class="diff-old">target-URI;
+e.g.
+</del>
+<ins class="diff-chg">target-URI.
+The
+URI
+template
+is
+specified
+as:
+</ins>
+</p>
+<del class="diff-old"> @prefix prov: <http://www.w3c.org/ns/prov#>
+<direct-query-description> a prov:DirectQueryService ;
+ prov:provenanceUriTemplate "?target={+uri}" .
+</del>
+ <pre class="pattern"><direct-query-description> a prov:DirectQueryService ;
+<ins class="diff-chg"> prov:provenanceUriTemplate "<cite>uri-template</cite>" .
+</ins>
+</pre>
+<p>
+where
+<del class="diff-old">query-URI
+is
+the
+base
+URI
+of
+the
+direct
+query
+service,
+and
+</del>
+<code>
+<cite>
+direct-query-description
+</cite>
+</code>
+is
+any
+distinct
+RDF
+subject
+node
+(i.e.
+a
+blank
+node
+or
+a
+<del class="diff-old">URI).
+</del>
+<ins class="diff-chg">URI),
+and
+</ins><code><cite><ins class="diff-chg">
+uri-template
+</ins></cite></code><ins class="diff-chg">
+is
+a
+URI
+template
+[
+</ins><cite><a class="bibref" href="#bib-RFC3986"><ins class="diff-chg">
+RFC3986
+</ins></a></cite><ins class="diff-chg">
+].
+</ins>
+</p>
+<p>
+The
+URI
+template
+indicated
+by
+<code>
+prov:provenanceUriTemplate
+</code>
+may
+expand
+to
+an
+absolute
+or
+relative
+URI
+reference.
+A
+URI
+for
+the
+desired
+provenance
+record
+is
+obtained
+by
+expanding
+the
+URI
+template
+with
+the
+variable
+<cite>
+<code>
+uri
+</code>
+</cite>
+set
+to
+the
+target-URI
+for
+which
+provenance
+is
+requested.
+In
+this
+example,
+if
+the
+target-URI
+contains
+'#'
+or
+'&'
+these
+must
+be
+%-escaped
+as
+<code>
+%23
+</code>
+or
+<code>
+%26
+</code>
+respectively
+before
+template
+expansion
+[
+<cite>
+<a class="bibref" href="#bib-RFC3986">
+RFC3986
+</a>
+</cite>
+].
+If
+the
+result
+is
+a
+relative
+reference,
+it
+is
+interpreted
+per
+[
+<cite>
+<a class="bibref" href="#bib-RFC3986">
+RFC3986
+</a>
+</cite>
+]
+(section
+5.2)
+using
+the
+URI
+of
+the
+service
+description
+as
+its
+base
+URI
+(which
+is
+generally
+the
+same
+as
+the
+query
+service-URI,
+unless
+HTTP
+redirection
+has
+been
+invoked).
+</p>
+ <div class="example"><div class="example-title"><span>Example 5</span></div><pre class="example code"><http://example.com/prov/service> a prov:ServiceDescription;
+<ins class="diff-new"> prov:describesService _:direct .
+_:direct a prov:DirectQueryService ;
+ prov:provenanceUriTemplate
+"http://www.example.com/provenance/service?target={uri}"
+.
+</ins></pre></div>
+<p>
+A
+provenance
+query
+service
+<em class="rfc2119" title="MAY">
+MAY
+</em>
+recognize
+additional
+parameters
+encoded
+as
+part
+of
+a
+URI
+for
+the
+provenance
+record.
+If
+it
+does,
+it
+<em class="rfc2119" title="SHOULD">
+SHOULD
+</em>
+include
+these
+in
+the
+provenance
+URI
+template
+in
+the
+service
+description,
+so
+that
+clients
+may
+discover
+how
+a
+URI
+is
+formed
+using
+this
+additional
+information.
+For
+example,
+a
+query
+service
+might
+offer
+to
+include
+just
+the
+immediate
+provenance
+of
+a
+target,
+or
+to
+also
+supply
+provenance
+of
+other
+resources
+from
+which
+the
+target
+is
+derived.
+Suppose
+a
+service
+accepts
+an
+additional
+parameter
+<code>
+steps
+</code>
+that
+defines
+the
+number
+of
+previous
+steps
+to
+include
+in
+a
+provenance
+trace,
+it
+might
+publish
+its
+service
+description
+thus:
+</p>
+<del class="diff-old"> > a prov:DirectQueryService ;
+</del>
+ <div class="example"><div class="example-title"><span>Example 6</span></div><pre class="example code"><http://example.com/prov/service> a prov:ServiceDescription;
+<ins class="diff-chg"> prov:describesService _:direct .
+_:direct a prov:DirectQueryService ;
+</ins>
+ prov:provenanceUriTemplate
+<del class="diff-old">"http://www.example.com/provenance/service?target={+uri}{&steps}"
+</del>
+<ins class="diff-chg">"http://www.example.com/provenance/service?target={uri}{&steps}"
+</ins>
+.
+</pre>
+</div>
+<p>
+<del class="diff-old">which
+might
+result
+in
+an
+HTTP
+query
+for
+provenance
+information
+that
+looks
+like
+this:
+Example
+6
+GET
+http://example.com/provenance/service?
+target
+=http://www.example.com/entity&
+steps
+=2
+HTTP/1.1
+</del>
+(Note
+that
+in
+this
+case,
+a
+"level
+3"
+URI
+template
+feature
+is
+used
+[
+<cite>
+<a class="bibref" href="#bib-URI-template">
+URI-template
+</a>
+</cite>
+].)
+</p>
+<p>
+<ins class="diff-new">Section
+</ins><a href="#direct-http-query-service-invocation" class="sectionRef sec-ref"><ins class="diff-new">
+section
+4.2
+Direct
+HTTP
+query
+service
+invocation
+</ins></a><ins class="diff-new">
+discusses
+how
+a
+client
+interacts
+with
+a
+direct
+HTTP
+query
+service.
+</ins></p>
+</section>
+<section id="sparql-query-service-description">
+<h4>
+<span class="secno">
+4.1.2
+</span>
+SPARQL
+query
+service
+description
+</h4>
+<p>
+A
+SPARQL
+query
+service
+is
+described
+by
+an
+RDF
+resource
+of
+type
+<code>
+sd:Service
+</code>
+[
+<cite>
+<a class="bibref" href="#bib-SPARQL-SD">
+SPARQL-SD
+</a>
+</cite>
+].
+</p>
+<p>
+It
+allows
+for
+accessing
+provenance
+information
+using
+a
+SPARQL
+query,
+which
+may
+be
+constructed
+to
+retrieve
+provenance
+for
+a
+particular
+resource,
+or
+for
+multiple
+resources.
+The
+query
+may
+be
+formulated
+using
+the
+PROV-O
+vocabulary
+terms
+[
+<cite>
+<a class="bibref" href="#bib-PROV-O">
+PROV-O
+</a>
+</cite>
+],
+and
+others
+supported
+by
+the
+SPARQL
+endpoint
+as
+appropriate.
+</p>
+<p>
+The
+SPARQL
+query
+service
+description
+is
+constructed
+as
+defined
+by
+<cite>
+SPARQL
+1.1
+Service
+Description
+</cite>
+[
+<cite>
+<a class="bibref" href="#bib-SPARQL-SD">
+SPARQL-SD
+</a>
+</cite>
+];
+e.g.
+</p>
+<del class="diff-old"> a sd:Service ;
+ sd:endpoint </sparql/> ;
+</del>
+ <div class="example"><div class="example-title"><span>Example 7</span></div><pre class="example code"><http://example.com/prov/service> a prov:ServiceDescription;
+<ins class="diff-chg"> prov:describesService _:sparql .
+_:sparql a sd:Service ;
+ sd:endpoint <http://www.example.com/provenance/sparql> ;
+</ins>
+sd:supportedLanguage
+sd:SPARQL11Query
+.
+</pre>
+</div>
+<p>
+where
+<code>
+<del class="diff-old">query-URI
+</del>
+<ins class="diff-chg">http://www.example.com/provenance/sparql
+</ins>
+</code>
+is
+the
+<del class="diff-old">base
+</del>
+URI
+of
+<del class="diff-old">the
+</del>
+<ins class="diff-chg">a
+</ins>
+provenance
+query
+<del class="diff-old">service,
+and
+sparql-query-description
+is
+any
+distinct
+RDF
+subject
+node
+(i.e.
+a
+blank
+node
+or
+a
+URI).
+</del>
+<ins class="diff-chg">SPARQL
+endpoint.
+</ins>
+</p>
+<p>
+The
+SPARQL
+service
+description
+may
+be
+detailed
+or
+sparse,
+provided
+that
+it
+includes
+at
+<ins class="diff-new">least
+</ins>
+a
+<del class="diff-old">minimum
+</del>
+<code>
+<ins class="diff-chg">sd:endpoint
+</ins></code><ins class="diff-chg">
+statement
+with
+</ins>
+the
+<del class="diff-old">following:
+</del>
+<ins class="diff-chg">SPARQL
+service
+endpoint
+URI.
+</ins>
+</p>
+<del class="diff-old"> a sd:Service ;
+ sd:endpoint <(SPARQL service endpoint URI reference)> .
+</del>
+<p>
+The
+endpoint
+may
+be
+given
+as
+an
+absolute
+or
+relative
+URI
+reference.
+If
+a
+relative
+reference
+is
+given,
+it
+is
+interpreted
+in
+the
+normal
+way
+for
+the
+RDF
+format
+used,
+which
+will
+commonly
+be
+relative
+to
+the
+URI
+of
+the
+service
+document
+itself.
+</p>
+</section>
+<section id="service-description-example">
+<h4>
+<span class="secno">
+4.1.3
+</span>
+Service
+description
+example
+</h4>
+<p>
+The
+following
+service
+description
+example
+uses
+Turtle
+[
+<cite>
+<a class="bibref" href="#bib-TURTLE">
+TURTLE
+</a>
+</cite>
+]
+syntax
+to
+describe
+both
+direct
+HTTP
+and
+SPARQL
+query
+services:
+</p>
+<del class="diff-old"> @prefix prov: <http://www.w3c.org/ns/prov#>
+@prefix dcterms: <http://purl.org/dc/terms/>
+@prefix foaf: <http://xmlns.com/foaf/0.1/>
+@prefix sd: <http://www.w3.org/ns/sparql-service-description#>
+</del>
+ <div class="example"><div class="example-title"><span>Example 8</span></div><pre class="example code">@prefix prov: <http://www.w3c.org/ns/prov#> .
+<ins class="diff-chg">@prefix dcterms: <http://purl.org/dc/terms/> .
+@prefix foaf: <http://xmlns.com/foaf/0.1/> .
+@prefix sd: <http://www.w3.org/ns/sparql-service-description#> .
+</ins>
+<> a prov:ServiceDescription ;
+ prov:describesService <#direct>, <#sparql> ;
+ dcterms:publisher <#us>
+ .
+<#us> a foaf:Organization ;
+ foaf:name "and not a service!"
+ .
+<#direct> a prov:DirectQueryService ;
+ prov:provenanceUriTemplate "/direct?target={+uri}"
+ .
+<#sparql> a sd:Service ;
+ sd:endpoint </sparql/> ;
+ sd:supportedLanguage sd:SPARQL11Query ;
+ sd:resultFormat <http://www.w3.org/ns/formats/RDF_XML> ,
+ <http://www.w3.org/ns/formats/Turtle> ,
+ <http://www.w3.org/ns/formats/SPARQL_Results_XML> ,
+ <http://www.w3.org/ns/formats/SPARQL_Results_JSON> ,
+ <http://www.w3.org/ns/formats/SPARQL_Results_CSV> ,
+ <http://www.w3.org/ns/formats/SPARQL_Results_TSV>
+.
+</pre>
+</div>
+</section>
+</section>
+<section id="direct-http-query-service-invocation">
+<h3>
+<span class="secno">
+4.2
+</span>
+Direct
+HTTP
+query
+service
+invocation
+</h3>
+<p>
+This
+<del class="diff-old">protocol
+combines
+</del>
+<ins class="diff-chg">section
+describes
+</ins>
+the
+<ins class="diff-chg">interaction
+between
+a
+client
+and
+a
+direct
+HTTP
+query
+service
+whose
+service
+description
+is
+as
+presented
+in
+</ins><a href="#direct-http-query-service-description" class="sectionRef sec-ref"><ins class="diff-chg">
+section
+4.1.1
+Direct
+HTTP
+query
+service
+description
+</ins></a>,<ins class="diff-chg">
+once
+the
+service
+description
+has
+been
+analyzed
+and
+its
+URI
+template
+has
+been
+extracted.
+</ins></p><p><ins class="diff-chg">
+The
+</ins><a class="internalDFN" href="#dfn-target-uri">
+target-URI
+</a>
+<del class="diff-old">with
+a
+</del>
+<ins class="diff-chg">for
+which
+provenance
+is
+required
+is
+used
+in
+the
+expansion
+of
+the
+</ins>
+supplied
+URI
+template
+<ins class="diff-new">[
+</ins><cite><a class="bibref" href="#bib-RFC3986"><ins class="diff-new">
+RFC3986
+</ins></a></cite><ins class="diff-new">
+]
+</ins>
+to
+formulate
+an
+HTTP
+GET
+request.
+</p>
+<p>
+Thus,
+<del class="diff-old">if
+the
+URI
+template
+extracted
+from
+</del>
+<ins class="diff-chg">in
+</ins>
+the
+<ins class="diff-new">first
+service
+description
+example
+in
+</ins><a href="#direct-http-query-service-description" class="sectionRef sec-ref"><ins class="diff-new">
+section
+4.1.1
+Direct
+HTTP
+query
+</ins>
+service
+description
+</a>,
+<ins class="diff-new">the
+URI
+template
+</ins>
+is
+<code>
+<del class="diff-old">http://example.com/provenance/service?target={uri}
+and
+</del>
+<ins class="diff-chg">http://www.example.com/provenance/service?target={uri}
+</ins></code>.<ins class="diff-chg">
+If
+</ins>
+the
+supplied
+target-URI
+is
+<code>
+http://www.example.com/entity123
+</code>,
+<ins class="diff-new">this
+would
+be
+used
+as
+</ins>
+the
+<ins class="diff-new">value
+for
+variable
+</ins><code><ins class="diff-new">
+uri
+</ins></code><ins class="diff-new">
+when
+expanding
+the
+template.
+The
+</ins>
+resulting
+HTTP
+request
+<ins class="diff-new">used
+to
+retrieve
+a
+provenance
+record
+</ins>
+would
+be:
+</p>
+ <div class="example"><div class="example-title"><span>Example 9</span></div><pre class="example code">GET /provenance/service?<b>target</b>=http%3A%2F%2Fwww.example.com%2Fentity123 HTTP/1.1
+Host:
+example.com
+</pre>
+</div>
+<p>
+Any
+server
+that
+implements
+this
+protocol
+and
+receives
+a
+request
+URI
+in
+<del class="diff-old">this
+</del>
+<ins class="diff-chg">a
+</ins>
+form
+<ins class="diff-new">corresponding
+to
+its
+published
+URI
+template
+</ins>
+<em class="rfc2119" title="SHOULD">
+SHOULD
+</em>
+return
+a
+provenance
+record
+for
+the
+<del class="diff-old">target-URI
+</del>
+embedded
+<del class="diff-old">in
+the
+query
+component,
+where
+that
+URI
+</del>
+<ins class="diff-chg">target-URI.
+The
+target-URI
+</ins>
+is
+<del class="diff-old">the
+result
+of
+</del>
+<ins class="diff-chg">obtained
+by
+</ins>
+percent-decoding
+[
+<cite>
+<a class="bibref" href="#bib-RFC3986">
+RFC3986
+</a>
+</cite>
+]
+the
+part
+of
+the
+request
+URI
+corresponding
+to
+<ins class="diff-new">occurrences
+of
+the
+variable
+</ins>
+<code>
+<del class="diff-old">{var}
+</del>
+<ins class="diff-chg">uri
+</ins>
+</code>
+in
+the
+URI
+template.
+E.g.,
+in
+the
+above
+example,
+the
+decoded
+target-URI
+is
+<code>
+http://www.example.com/entity123
+</code>.
+The
+target-URI
+<em class="rfc2119" title="MUST">
+MUST
+</em>
+be
+an
+absolute
+URI,
+and
+the
+server
+<em class="rfc2119" title="SHOULD">
+SHOULD
+</em>
+respond
+with
+<code>
+400
+Bad
+Request
+</code>
+if
+it
+is
+not.
+</p>
+<p>
+A
+server
+<em class="rfc2119" title="SHOULD NOT">
+SHOULD
+NOT
+</em>
+offer
+a
+template
+containing
+<code>
+{+uri}
+</code>
+or
+other
+non-simple
+variable
+expansion
+options
+[
+<cite>
+<a class="bibref" href="#bib-URI-template">
+URI-template
+</a>
+</cite>
+]
+unless
+all
+valid
+target-URIs
+for
+which
+it
+can
+provide
+provenance
+do
+not
+contain
+problematic
+characters
+like
+<code>
+'#'
+</code>
+or
+<code>
+'&'
+</code>.
+</p>
+<div class="note">
+<div class="note-title" role="heading" aria-level="4">
+<span>
+Note
+</span>
+</div>
+<p class="">
+The
+defined
+URI
+template
+expansion
+process
+[
+<cite>
+<a class="bibref" href="#bib-URI-template">
+URI-template
+</a>
+</cite>
+]
+generally
+takes
+care
+of
+%-escaping
+characters
+that
+are
+not
+permitted
+in
+URIs.
+However,
+when
+expanding
+a
+template
+with
+<code>
+{+uri}
+<del class="diff-old">,
+</del>
+</code>
+<ins class="diff-chg">(or
+other
+non-simple
+variable
+expansion
+options),
+</ins>
+some
+permitted
+characters
+such
+as
+<code>
+'#'
+</code>
+and
+<code>
+'&'
+</code>
+are
+not
+escaped.
+If
+the
+supplied
+target-URI
+contains
+these
+characters,
+then
+they
+may
+disrupt
+interpretation
+of
+the
+resulting
+query
+URI.
+<del class="diff-old">To
+prevent
+this,
+'#'
+and
+'&'
+characters
+in
+the
+target-URI
+may
+be
+replaced
+with
+%23
+and
+%26
+respectively,
+before
+performing
+the
+URI
+template
+expansion.
+An
+alternative,
+simpler
+and
+</del>
+<ins class="diff-chg">A
+generally
+</ins>
+more
+reliable
+approach
+is
+to
+use
+<code>
+{uri}
+</code>
+in
+the
+URI
+template
+string,
+which
+will
+cause
+all
+URI-reserved
+characters
+to
+be
+%-escaped
+as
+part
+of
+the
+URI-template
+expansion,
+as
+in
+the
+example
+above.
+</p>
+</div>
+<p>
+If
+the
+provenance
+described
+by
+the
+request
+is
+unknown
+to
+the
+server,
+a
+suitable
+error
+response
+code
+<em class="rfc2119" title="SHOULD">
+SHOULD
+</em>
+be
+returned.
+In
+the
+absence
+of
+any
+security
+of
+privacy
+concerns
+about
+the
+resource,
+that
+might
+be
+<code>
+404
+Not
+Found
+</code>.
+But
+if
+the
+existence
+or
+non-existence
+of
+a
+resource
+is
+considered
+private
+or
+sensitive,
+an
+authorization
+failure
+or
+other
+<del class="diff-old">error
+</del>
+response
+may
+be
+returned.
+</p>
+<p>
+The
+direct
+HTTP
+query
+service
+may
+return
+provenance
+in
+any
+available
+format.
+For
+interoperable
+provenance
+publication,
+use
+of
+<del class="diff-old">the
+PROV-O
+vocabulary
+[
+PROV-O
+]
+</del>
+<ins class="diff-chg">PROV
+</ins>
+represented
+in
+<del class="diff-old">a
+standardized
+RDF
+format
+</del>
+<ins class="diff-chg">any
+of
+its
+specified
+formats
+</ins>
+is
+recommended.
+Where
+alternative
+formats
+are
+available,
+selection
+may
+be
+made
+by
+content
+negotiation,
+using
+<code>
+Accept:
+</code>
+header
+fields
+in
+the
+HTTP
+request.
+Services
+<em class="rfc2119" title="MUST">
+MUST
+</em>
+identify
+the
+<code>
+Content-Type
+</code>
+of
+the
+provenance
+returned.
+</p>
+<p>
+Additional
+URI
+query
+parameters
+may
+be
+used
+as
+indicated
+by
+the
+service
+description
+in
+<a href="#direct-http-query-service-description" class="sectionRef sec-ref">
+section
+4.1.1
+Direct
+HTTP
+query
+service
+description
+</a>.
+<ins class="diff-new">The
+second
+service
+description
+example
+specifies
+a
+URI
+template
+with
+an
+additional
+variable
+which
+may
+be
+used
+to
+control
+the
+scope
+of
+provenance
+information
+returned:
+</ins><code><ins class="diff-new">
+http://www.example.com/provenance/service?target={+uri}{&steps}
+</ins></code>.<ins class="diff-new">
+Following
+[
+</ins><cite><a class="bibref" href="#bib-RFC3986"><ins class="diff-new">
+RFC3986
+</ins></a></cite><ins class="diff-new">
+],
+if
+no
+value
+for
+variable
+</ins><code><ins class="diff-new">
+steps
+</ins></code><ins class="diff-new">
+is
+provided
+when
+expanding
+the
+template,
+this
+extra
+element
+is
+effectively
+ignored.
+But
+if
+a
+</ins><code><ins class="diff-new">
+steps
+</ins></code><ins class="diff-new">
+value
+of
+(say)
+</ins><code><ins class="diff-new">
+2
+</ins></code><ins class="diff-new">
+is
+provided,
+then
+the
+resulting
+HTTP
+query
+would
+be:
+</ins>
+</p>
+<div class="example">
+<div class="example-title">
+<span>
+<ins class="diff-new">Example
+10
+</ins></span></div><pre class="example code"><ins class="diff-new">
+GET
+http://example.com/provenance/service?
+</ins><b><ins class="diff-new">
+target
+</ins></b><ins class="diff-new">
+=http://www.example.com/entity&
+</ins><b><ins class="diff-new">
+steps
+</ins></b><ins class="diff-new">
+=2
+HTTP/1.1
+</ins></pre></div><div class="note"><div class="note-title" role="heading" aria-level="4"><span><ins class="diff-new">
+Note
+</ins></span></div><p class=""><ins class="diff-new">
+The
+use
+of
+any
+specific
+URI
+template
+variable
+other
+than
+</ins><code><ins class="diff-new">
+uri
+</ins></code><ins class="diff-new">
+for
+the
+target-URI
+is
+a
+matter
+for
+agreement
+between
+the
+client
+and
+query
+service,
+and
+is
+not
+specified
+in
+this
+note.
+It
+is
+mentioned
+here
+simply
+to
+show
+that
+the
+possibility
+exists
+to
+formulate
+more
+detailed
+queries.
+</ins></p></div>
+</section>
+<section id="provenance-query-service-discovery">
+<h3>
+<span class="secno">
+4.3
+</span>
+Provenance
+query
+service
+discovery
+</h3>
+<p>
+Previously,
+<a href="#locating-provenance-records" class="sectionRef sec-ref">
+section
+3.
+Locating
+provenance
+records
+</a>
+has
+described
+use
+of
+HTTP
+<code>
+Link:
+</code>
+header
+fields,
+HTML
+<code>
+<link>
+</code>
+elements
+and
+RDF
+statements
+to
+indicate
+provenance
+query
+services.
+Beyond
+that,
+this
+specification
+does
+not
+define
+any
+specific
+mechanism
+for
+discovering
+query
+services.
+Applications
+may
+use
+any
+appropriate
+mechanism,
+including
+but
+not
+limited
+to:
+prior
+configuration,
+search
+engines,
+service
+registries,
+etc.
+</p>
+<p>
+To
+facilitate
+service
+discovery,
+we
+recommend
+that
+RDF
+publication
+of
+dataset
+and
+service
+descriptions
+use
+the
+property
+<code>
+prov:has_query_service
+</code>
+and
+the
+provenance
+service
+type
+<code>
+prov:ServiceDescription
+</code>
+as
+appropriate
+(see
+the
+appendix
+<a href="#prov-namespace" class="sectionRef">
+section
+B.
+</a>
+).
+</p>
+<p>
+For
+example,
+a
+VoID
+description
+[
+<cite>
+<a class="bibref" href="#bib-VoID">
+VoID
+</a>
+</cite>
+]
+of
+a
+dataset
+might
+indicate
+a
+provenance
+query
+service
+providing
+information
+about
+that
+dataset:
+</p>
+ <pre class="pattern"> <http://example.org/dataset/> a void:Dataset ;
+prov:has_query_service
+<http://example.org/provenance/>
+.
+</pre>
+<p>
+The
+RDF
+service
+description
+example
+in
+<a href="#service-description-example" class="sectionRef sec-ref">
+section
+4.1.3
+Service
+description
+example
+</a>
+shows
+use
+of
+the
+<code>
+prov:ServiceDescription
+</code>
+type.
+</p>
+</section>
+</section>
+<section id="provenance-pingback">
+<h2>
+<span class="secno">
+5.
+</span>
+<del class="diff-old">Forward
+provenance
+</del>
+<ins class="diff-chg">Provenance
+pingback
+</ins>
+</h2>
+<del class="diff-old">REVIEW.
+</del>
+<p>
+This
+section
+describes
+<del class="diff-old">an
+"at-risk"
+feature
+whose
+final
+inclusion
+in
+this
+document
+is
+undecided.
+Does
+the
+use
+of
+</del>
+a
+<del class="diff-old">"ping-back"
+for
+discovering
+forward
+</del>
+<ins class="diff-chg">mechanism
+that
+may
+be
+used
+to
+discover
+related
+</ins>
+provenance
+<del class="diff-old">fall
+under
+</del>
+<ins class="diff-chg">information
+that
+</ins>
+the
+<del class="diff-old">remit
+</del>
+<ins class="diff-chg">publisher
+</ins>
+of
+<del class="diff-old">"provenance
+access
+and
+query"?
+Is
+it
+</del>
+a
+<del class="diff-old">useful
+feature
+to
+define?
+This
+section
+describes
+a
+discovery
+mechanism
+for
+forward
+provenance
+;
+i.e.
+</del>
+<ins class="diff-chg">resource
+does
+not
+otherwise
+know
+about;
+e.g.
+</ins>
+provenance
+describing
+how
+<del class="diff-old">a
+resource
+</del>
+<ins class="diff-chg">it
+</ins>
+is
+used
+after
+it
+has
+been
+<del class="diff-old">created
+.
+</del>
+<ins class="diff-chg">created.
+</ins>
+</p>
+<p>
+The
+mechanisms
+discussed
+in
+previous
+sections
+are
+primarily
+concerned
+with
+<ins class="diff-new">the
+publisher
+enabling
+</ins>
+access
+to
+<del class="diff-old">historical
+provenance,
+dealing
+</del>
+<ins class="diff-chg">known
+provenance
+about
+an
+entity,
+answering
+</ins>
+with
+questions
+such
+as:
+</p>
+<ul>
+<li>
+what
+was
+this
+resource
+based
+upon?
+</li>
+<li>
+how
+was
+it
+constructed?
+</li>
+<li>
+who
+made
+it?
+</li>
+<li>
+when
+was
+it
+made?
+</li>
+</ul>
+<p>
+These
+questions
+can
+be
+<del class="diff-old">turned
+around
+</del>
+<ins class="diff-chg">opened
+up
+</ins>
+to
+consider
+<del class="diff-old">a
+publisher's
+forward-looking
+use
+of
+a
+resource,
+</del>
+<ins class="diff-chg">provenance
+information
+created
+by
+unrelated
+third
+parties,
+</ins>
+like:
+</p>
+<ul>
+<li>
+what
+new
+resources
+are
+based
+on
+this
+resource?
+</li>
+<li>
+what
+has
+this
+resource
+been
+used
+for?
+</li>
+<li>
+who
+has
+used
+it?
+</li>
+<li>
+<del class="diff-old">etc.
+</del>
+<ins class="diff-chg">what
+other
+resources
+are
+derived
+from
+the
+same
+sources
+as
+this
+resource?
+</ins>
+</li>
+</ul>
+<p>
+The
+ability
+to
+answer
+<del class="diff-old">forward-looking
+</del>
+<ins class="diff-chg">such
+broader
+</ins>
+questions
+requires
+some
+cooperation
+among
+the
+parties
+who
+use
+a
+resource;
+for
+example,
+a
+consumer
+could
+report
+use
+directly
+to
+the
+publisher,
+or
+a
+search
+engine
+could
+discover
+and
+report
+<del class="diff-old">such
+</del>
+downstream
+resource
+usage.
+To
+facilitate
+such
+cooperation,
+a
+<del class="diff-old">publisher
+of
+a
+</del>
+resource
+<ins class="diff-new">publisher
+</ins>
+may
+<del class="diff-old">implement
+a
+"ping-back"
+capability.
+</del>
+<ins class="diff-chg">receive
+provenance
+"ping-backs".
+(The
+mechanism
+described
+here
+is
+inspired
+by
+</ins><a href="http://www.hixie.ch/specs/pingback/pingback" class="externalRef"><ins class="diff-chg">
+blog
+pingbacks
+</ins></a>,<ins class="diff-chg">
+but
+avoids
+the
+need
+for
+XML-RPC
+and
+is
+specific
+for
+provenance
+records.)
+</ins>
+</p>
+<p>
+A
+resource
+may
+have
+an
+associated
+<del class="diff-old">"ping-back"
+URI
+</del>
+<ins class="diff-chg">provenance
+ping-back
+URI,
+</ins>
+which
+<del class="diff-old">can
+</del>
+<ins class="diff-chg">may
+</ins>
+be
+presented
+with
+references
+to
+provenance
+about
+the
+resource.
+The
+ping-back
+URI
+is
+associated
+with
+a
+resource
+using
+mechanisms
+similar
+to
+those
+used
+for
+presenting
+a
+<a class="internalDFN" href="#dfn-provenance-uri">
+provenance-URI
+</a>,
+but
+using
+a
+<code>
+<del class="diff-old">pingback
+</del>
+<ins class="diff-chg">prov:pingback
+</ins>
+</code>
+link
+relation
+instead
+of
+<code>
+<del class="diff-old">has_provenance
+</del>
+<ins class="diff-chg">prov:has_provenance
+</ins>
+</code>.
+A
+consumer
+of
+the
+resource,
+or
+some
+other
+system,
+may
+perform
+an
+HTTP
+POST
+operation
+to
+the
+pingback
+URI,
+with
+a
+request
+body
+containing
+a
+list
+of
+provenance-URIs
+for
+provenance
+records
+describing
+uses
+of
+the
+resource.
+</p>
+<p>
+For
+example,
+consider
+a
+resource
+that
+is
+published
+by
+<code>
+acme.example.com
+</code>,
+and
+is
+subsequently
+used
+by
+<code>
+<del class="diff-old">wile-e.example.org
+</del>
+<ins class="diff-chg">coyote.example.org
+</ins>
+</code>
+in
+the
+construction
+of
+some
+new
+entity;
+we
+might
+see
+an
+exchange
+along
+the
+following
+lines.
+We
+start
+with
+<code>
+<del class="diff-old">wile-e.example.org
+</del>
+<ins class="diff-chg">coyote.example.org
+</ins>
+</code>
+retrieving
+a
+copy
+of
+<code>
+acme.example.org
+</code>
+'s
+resource:
+</p>
+<del class="diff-old"> C: GET http://acme.example.org/super-widget HTTP/1.1
+</del>
+ <div class="example"><div class="example-title"><span>Example 11</span></div><pre class="example code">C: GET http://acme.example.org/super-widget123 HTTP/1.1
+<del class="diff-old"> S: 200 OK
+ S: Link: <http://acme.example.org/super-widget/provenance>;
+ rel=http://www.w3.org/ns/prov#has_provenance
+ S: Link: <http://acme.example.org/super-widget/pingback>;
+ rel=http://www.w3.org/ns/prov#pingback
+ :
+(super-widget
+</del>
+<ins class="diff-chg">S: 200 OK
+S: Link: <http://acme.example.org/super-widget123/provenance>;
+ rel="http://www.w3.org/ns/prov#has_provenance"
+S: Link: <http://acme.example.org/super-widget123/pingback>;
+ rel="http://www.w3.org/ns/prov#pingback"
+ :
+(super-widget123
+</ins>
+resource
+data)
+</pre>
+</div>
+<p>
+The
+first
+of
+the
+links
+in
+the
+response
+is
+a
+<code>
+has_provenance
+</code>
+link
+with
+a
+<a class="internalDFN" href="#dfn-provenance-uri">
+provenance-URI
+</a>
+that
+has
+been
+described
+previously
+(
+<a href="#resource-accessed-by-http" class="sectionRef sec-ref">
+section
+3.1
+Resource
+accessed
+by
+HTTP
+</a>
+).
+The
+second
+is
+a
+distinct
+resource
+that
+exists
+to
+receive
+provenance
+pingbacks.
+Later,
+when
+a
+new
+resource
+has
+been
+created
+or
+<ins class="diff-new">some
+related
+</ins>
+action
+performed
+based
+upon
+the
+<code>
+<del class="diff-old">acme.example.org/super-widget
+</del>
+<ins class="diff-chg">acme.example.org/super-widget123
+</ins>
+</code>,
+a
+client
+<del class="diff-old">MAY
+</del>
+<ins class="diff-chg">may
+</ins>
+post
+a
+pingback
+request
+to
+<del class="diff-old">any
+</del>
+<ins class="diff-chg">the
+</ins>
+supplied
+<code>
+pingback
+</code>
+URI:
+</p>
+<del class="diff-old"> C: POST http://acme.example.org/super-widget/pingback HTTP/1.1
+</del>
+ <div class="example"><div class="example-title"><span>Example 12</span></div><pre class="example code">C: POST http://acme.example.org/super-widget123/pingback HTTP/1.1
+C: Content-Type: text/uri-list
+C:
+<del class="diff-old">C: http://wile-e.example.org/contraption/provenance
+C: http://wile-e.example.org/another/provenance
+</del>
+<ins class="diff-chg">C: http://coyote.example.org/contraption/provenance
+C: http://coyote.example.org/another/provenance
+</ins>
+<del class="diff-old">S: 204 No Content
+S: Link: <http://acme.example.org/super-widget/provenance>;
+ rel=http://www.w3.org/ns/prov#has_provenance;
+anchor="http://acme.example.org/super-widget"
+</del>
+<ins class="diff-chg">S:
+204
+No
+Content
+</ins>
+</pre>
+</div>
+<p>
+The
+pingback
+request
+supplies
+a
+list
+of
+<a class="internalDFN" href="#dfn-provenance-uri">
+provenance-URI
+</a>
+s
+from
+which
+<del class="diff-old">forward
+</del>
+<ins class="diff-chg">additional
+</ins>
+provenance
+may
+be
+retrieved.
+The
+pingback
+service
+may
+do
+as
+it
+chooses
+with
+these
+URIs;
+e.g.,
+it
+may
+choose
+to
+save
+them
+for
+later
+use,
+to
+retrieve
+the
+associated
+provenance
+and
+save
+that,
+to
+publish
+the
+URIs
+along
+with
+other
+provenance
+information
+about
+the
+original
+entity
+to
+which
+they
+relate,
+or
+even
+to
+ignore
+them.
+</p>
+<p>
+<del class="diff-old">The
+client
+MAY
+further
+supply
+has_query_service
+links
+indicating
+provenance
+query
+services
+that
+can
+describe
+the
+target-URI.
+The
+anchor
+MUST
+be
+included,
+and
+SHOULD
+be
+the
+target-URI
+of
+the
+resource
+to
+which
+this
+pingback
+service
+belongs,
+or
+some
+related
+resource
+with
+relevant
+provenance.
+ C: POST http://acme.example.org/super-widget/pingback HTTP/1.1
+C: Link: <http://wile-e.example.org/sparql>;
+ rel="http://www.w3.org/ns/prov#has_query_service";
+ anchor="http://acme.example.org/super-widget"
+C: Content-Type: text/uri-list
+C: Content-Length: 0
+C:
+S: 204 No Content
+S: Link: <http://acme.example.org/super-widget/provenance>;
+ rel=http://www.w3.org/ns/prov#has_provenance;
+anchor="http://acme.example.org/super-widget"
+In
+the
+above
+example,
+the
+client
+did
+not
+submit
+any
+provenance-URIs
+and
+the
+URI
+list
+is
+therefore
+empty.
+The
+client
+MAY
+similarly
+include
+has_provenance
+links
+to
+specify
+provenance
+records
+with
+a
+different
+anchor.
+The
+provenance-URIs
+of
+those
+headers
+SHOULD
+also
+be
+included
+in
+the
+content
+if
+the
+POSTed
+Content-type
+is
+text/uri-list
+.
+Does
+this
+SHOULD
+requirement
+serve
+any
+useful
+purpose?
+</del>
+There
+is
+no
+required
+information
+in
+the
+server
+response
+to
+a
+pingback
+POST
+request.
+In
+the
+examples
+<del class="diff-old">above,
+</del>
+<ins class="diff-chg">here,
+</ins>
+the
+pingback
+service
+responds
+<ins class="diff-new">positively
+</ins>
+with
+<code>
+<ins class="diff-new">204
+No
+Content
+</ins></code><ins class="diff-new">
+and
+</ins>
+an
+empty
+response
+<del class="diff-old">body,
+and
+links
+to
+provenance
+for
+the
+original
+resource.
+(Note
+that
+the
+</del>
+<ins class="diff-chg">body.
+Other
+HTTP
+status
+values
+like
+</ins>
+<code>
+<del class="diff-old">Link:
+header
+returned
+contains
+an
+explicit
+</del>
+<ins class="diff-chg">200
+OK
+</ins></code>,
+<code>
+<del class="diff-old">anchor
+parameter
+with
+the
+URI
+of
+the
+original
+resource;
+without
+this,
+the
+link
+would
+relate
+the
+indicated
+URI
+to
+the
+pingback
+URI
+</del>
+<ins class="diff-chg">201
+Created
+</ins></code>,
+<code>
+<del class="diff-old">http://acme.example.org/super-widget/pingback
+</del>
+<ins class="diff-chg">202
+Accepted
+</ins></code>,<ins class="diff-chg">
+and
+</ins><code><ins class="diff-chg">
+303
+See
+Other
+</ins>
+</code>
+<del class="diff-old">rather
+than
+</del>
+<ins class="diff-chg">might
+also
+be
+appropriate
+positive
+responses
+depending
+on
+</ins>
+the
+<del class="diff-old">original
+resource.)
+</del>
+<ins class="diff-chg">domain
+and
+application.
+</ins>
+</p>
+<p>
+The
+only
+defined
+operation
+on
+a
+pingback-URI
+is
+POST,
+which
+supplies
+links
+to
+provenance
+information
+or
+services
+as
+described
+above.
+A
+pingback-URI
+<em class="rfc2119" title="MAY">
+MAY
+</em>
+respond
+to
+other
+requests,
+but
+no
+requirements
+are
+imposed
+on
+how
+it
+responds.
+In
+particular,
+it
+is
+not
+specified
+here
+how
+a
+pingback
+resource
+should
+respond
+to
+an
+HTTP
+GET
+request.
+<del class="diff-old">This
+leaves
+open
+</del>
+</p>
+<p>
+<ins class="diff-chg">The
+pingback
+client
+</ins><em class="rfc2119" title="MAY"><ins class="diff-chg">
+MAY
+</ins></em><ins class="diff-chg">
+include
+extra
+</ins><code><ins class="diff-chg">
+has_provenance
+</ins></code><ins class="diff-chg">
+links
+to
+indicate
+provenance
+records
+related
+to
+</ins>
+a
+<del class="diff-old">possibility
+</del>
+<ins class="diff-chg">different
+resources,
+specified
+with
+correspondingly
+different
+anchor
+URIs.
+These
+</ins><em class="rfc2119" title="MAY"><ins class="diff-chg">
+MAY
+</ins></em><ins class="diff-chg">
+indicate
+further
+provenance
+about
+existing
+resources,
+or
+about
+new
+resources
+(such
+as
+new
+entities
+derived
+or
+specialized
+from
+</ins>
+that
+<ins class="diff-new">for
+which
+</ins>
+the
+pingback
+<del class="diff-old">resource
+</del>
+<ins class="diff-chg">URI
+was
+provided).
+For
+example:
+</ins></p> <div class="example"><div class="example-title"><span>Example 13</span></div><pre class="example code">C: POST http://acme.example.org/super-widget123/pingback HTTP/1.1<ins class="diff-chg">
+C: Link: <http://coyote.example.org/extra/provenance>;
+ rel="http://www.w3.org/ns/prov#has_provenance";
+ anchor="http://acme.example.org/extra-widget"
+C: Content-Type: text/uri-list
+C:
+C: http://coyote.example.org/contraption/provenance
+C: http://coyote.example.org/another/provenance
+C: http://coyote.example.org/extra/provenance
+S:
+204
+No
+Content
+</ins></pre></div><p><ins class="diff-chg">
+The
+client
+</ins>
+<em class="rfc2119" title="MAY">
+MAY
+</em>
+<del class="diff-old">have
+</del>
+<ins class="diff-chg">also
+supply
+</ins><code><ins class="diff-chg">
+has_query_service
+</ins></code><ins class="diff-chg">
+links
+indicating
+provenance
+query
+services
+that
+can
+describe
+</ins>
+the
+<del class="diff-old">same
+URI
+as
+</del>
+<ins class="diff-chg">target-URI.
+The
+anchor
+</ins><em class="rfc2119" title="MUST"><ins class="diff-chg">
+MUST
+</ins></em><ins class="diff-chg">
+be
+included,
+and
+</ins><em class="rfc2119" title="SHOULD"><ins class="diff-chg">
+SHOULD
+</ins></em><ins class="diff-chg">
+be
+either
+</ins>
+the
+<del class="diff-old">original
+resource,
+</del>
+<ins class="diff-chg">target-URI
+of
+the
+resource
+for
+which
+the
+pingback
+URI
+was
+</ins>
+provided
+<ins class="diff-new">(from
+the
+examples
+above,
+</ins>
+that
+<ins class="diff-new">would
+be
+</ins><code><ins class="diff-new">
+http://acme.example.org/super-widget123
+</ins></code><ins class="diff-new">
+),
+or
+some
+related
+resource
+with
+relevant
+provenance.
+For
+example:
+</ins></p> <div class="example"><div class="example-title"><span>Example 14</span></div><pre class="example code">C: POST http://acme.example.org/super-widget123/pingback HTTP/1.1<ins class="diff-new">
+C: Link: <http://coyote.example.org/sparql>;
+ rel="http://www.w3.org/ns/prov#has_query_service";
+ anchor="http://acme.example.org/super-widget123"
+C: Content-Type: text/uri-list
+C: Content-Length: 0
+C:
+S:
+204
+No
+Content
+</ins></pre></div><p><ins class="diff-new">
+Here,
+</ins>
+the
+<del class="diff-old">original
+does
+</del>
+<ins class="diff-chg">pingback
+client
+has
+supplied
+a
+query
+service
+URI,
+but
+did
+</ins>
+not
+<del class="diff-old">respond
+</del>
+<ins class="diff-chg">submit
+any
+provenance-URIs
+and
+the
+URI
+list
+is
+therefore
+empty.
+The
+</ins><code><ins class="diff-chg">
+Link
+</ins></code><ins class="diff-chg">
+header
+field
+indicates
+that
+the
+resource
+</ins><code><ins class="diff-chg">
+http://acme.example.org/super-widget123/provenance
+</ins></code><ins class="diff-chg">
+contains
+provenance
+information
+relating
+</ins>
+to
+<del class="diff-old">POST
+in
+some
+different
+way.
+</del>
+<code>
+<ins class="diff-chg">http://acme.example.org/super-widget123
+</ins></code><ins class="diff-chg">
+(that
+being
+the
+URI
+of
+the
+resource
+for
+which
+the
+pingback
+URI
+was
+provided).
+</ins>
+</p>
+</section>
+<section id="security-considerations">
+<h2>
+<span class="secno">
+6.
+</span>
+Security
+considerations
+</h2>
+<p>
+Provenance
+is
+central
+to
+establishing
+trust
+in
+data.
+If
+provenance
+is
+corrupted,
+it
+may
+lead
+agents
+(human
+or
+software)
+to
+draw
+inappropriate
+and
+possibly
+harmful
+conclusions.
+Therefore,
+care
+is
+needed
+to
+ensure
+that
+the
+integrity
+of
+provenance
+is
+maintained.
+Just
+as
+provenance
+can
+help
+determine
+a
+level
+of
+trust
+in
+some
+information,
+a
+provenance
+record
+related
+to
+the
+provenance
+itself
+("provenance
+of
+provenance")
+can
+help
+determine
+trust
+in
+the
+provenance.
+</p>
+<p>
+<ins class="diff-new">The
+</ins><a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec15.html" class="externalRef"><ins class="diff-new">
+HTTP
+security
+considerations
+</ins></a><ins class="diff-new">
+[
+</ins><cite><a class="bibref" href="#bib-HTTP11"><ins class="diff-new">
+HTTP11
+</ins></a></cite><ins class="diff-new">
+]
+generally
+apply
+for
+all
+of
+the
+resources
+and
+services
+located
+through
+the
+mechanism
+in
+this
+document.
+</ins></p><p>
+Secure
+HTTP
+(https)
+<em class="rfc2119" title="SHOULD">
+SHOULD
+</em>
+be
+used
+across
+unsecured
+networks
+when
+accessing
+provenance
+that
+may
+be
+used
+as
+a
+basis
+for
+trust
+decisions,
+or
+to
+obtain
+a
+provenance
+URI
+for
+same.
+</p>
+<p>
+When
+retrieving
+a
+provenance
+URI
+from
+a
+document,
+steps
+<em class="rfc2119" title="SHOULD">
+SHOULD
+</em>
+be
+taken
+to
+ensure
+the
+document
+itself
+is
+an
+accurate
+copy
+of
+the
+original
+whose
+author
+is
+being
+trusted
+(e.g.
+signature
+checking,
+or
+use
+of
+a
+trusted
+secure
+web
+service).
+(See
+also
+<a class="sectionRef sec-ref" href="#interpreting-provenance-records">
+section
+1.3
+Interpreting
+provenance
+records
+</a>.)
+</p>
+<p>
+Provenance
+may
+present
+a
+route
+for
+leakage
+of
+privacy-related
+information,
+combining
+as
+it
+does
+a
+diversity
+of
+information
+types
+with
+possible
+personally-identifying
+information;
+e.g.
+editing
+timestamps
+may
+provide
+clues
+to
+the
+working
+patterns
+of
+document
+editors,
+or
+derivation
+traces
+might
+indicate
+access
+to
+sensitive
+materials.
+In
+particular,
+note
+that
+the
+fact
+that
+a
+resource
+is
+openly
+accessible
+does
+not
+mean
+that
+its
+provenance
+should
+also
+be.
+When
+publishing
+provenance,
+its
+sensitivity
+<em class="rfc2119" title="SHOULD">
+SHOULD
+</em>
+be
+considered
+and
+appropriate
+access
+controls
+applied
+where
+necessary.
+When
+a
+provenance-aware
+publishing
+service
+accepts
+some
+resource
+for
+publication,
+the
+contributors
+<em class="rfc2119" title="SHOULD">
+SHOULD
+</em>
+have
+some
+opportunity
+to
+review
+and
+correct
+or
+conceal
+any
+provenance
+that
+they
+don't
+wish
+to
+be
+exposed.
+Provenance
+management
+systems
+<em class="rfc2119" title="SHOULD">
+SHOULD
+</em>
+embody
+mechanisms
+for
+enforcement
+and
+auditing
+of
+privacy
+policies
+as
+they
+apply
+to
+provenance.
+<ins class="diff-new">Implementations
+</ins><em class="rfc2119" title="MAY"><ins class="diff-new">
+MAY
+</ins></em><ins class="diff-new">
+choose
+to
+use
+standard
+HTTP
+authorization
+mechanisms
+to
+restrict
+access
+to
+resources,
+returning
+</ins><code><ins class="diff-new">
+401
+Unauthorized
+</ins></code>,<code><ins class="diff-new">
+403
+Forbidden
+</ins></code><ins class="diff-new">
+or
+</ins><code><ins class="diff-new">
+404
+Not
+Found
+</ins></code><ins class="diff-new">
+as
+appropriate.
+</ins>
+</p>
+<p>
+Provenance
+may
+be
+used
+by
+audits
+to
+establish
+accountability
+for
+information
+use
+[
+<cite>
+<a class="bibref" href="#bib-INFO-ACC">
+INFO-ACC
+</a>
+</cite>
+]
+and
+to
+verify
+use
+of
+proper
+processes
+in
+information
+processing
+activities.
+Thus,
+provenance
+management
+systems
+can
+provide
+mechanisms
+to
+support
+auditing
+and
+enforcement
+of
+information
+handling
+policies.
+In
+such
+cases,
+provenance
+itself
+may
+be
+a
+valuable
+target
+for
+attack
+by
+malicious
+agents,
+and
+care
+must
+be
+taken
+to
+ensure
+it
+is
+stored
+securely
+and
+in
+a
+fashion
+that
+resists
+attempts
+to
+tamper
+with
+it.
+</p>
+<p>
+The
+pingback
+service
+described
+in
+<a href="#provenance-pingback" class="sectionRef sec-ref">
+section
+5.
+<del class="diff-old">Forward
+provenance
+</del>
+<ins class="diff-chg">Provenance
+pingback
+</ins>
+</a>
+might
+be
+abused
+for
+"link
+spamming"
+(similar
+to
+the
+way
+that
+weblog
+ping-backs
+have
+been
+used
+to
+direct
+viewers
+to
+spam
+sites).
+As
+with
+many
+such
+services,
+an
+application
+needs
+to
+find
+a
+balance
+between
+maintaining
+ease
+of
+submission
+for
+useful
+information
+and
+blocking
+unwanted
+information.
+We
+have
+no
+easy
+solutions
+for
+this
+problem,
+and
+the
+caveats
+noted
+above
+about
+establishing
+integrity
+of
+provenance
+records
+apply
+similarly
+to
+information
+provided
+by
+ping-back
+calls.
+</p>
+<p>
+When
+clients
+and
+servers
+are
+retrieving
+submitted
+URIs
+such
+as
+provenance
+descriptions
+and
+following
+or
+registering
+links;
+reasonable
+care
+should
+be
+taken
+to
+prevent
+malicious
+use
+such
+as
+distributed
+denial
+of
+service
+attacks
+(DDoS),
+cross-site
+request
+forgery
+(CSRF),
+spamming
+and
+hosting
+of
+inappropriate
+materials.
+Reasonable
+preventions
+might
+include
+same-origin
+policy,
+HTTP
+authorization,
+SSL,
+rate-limiting,
+spam
+filters,
+moderation
+queues,
+user
+acknowledgements
+and
+validation.
+It
+is
+out
+of
+scope
+for
+this
+document
+to
+specify
+how
+such
+mechanisms
+work
+and
+should
+be
+applied.
+</p>
+<del class="diff-old">Is
+CSRF
+</del>
+<p>
+<ins class="diff-chg">Provenance
+pingback
+uses
+an
+HTTP
+POST
+operation,
+which
+may
+be
+used
+for
+non-"safe"
+interactions
+in
+the
+sense
+of
+[
+</ins><cite><a class="bibref" href="#bib-WEBARCH"><ins class="diff-chg">
+WEBARCH
+</ins></a></cite><ins class="diff-chg">
+]
+(
+</ins><a href="http://www.w3.org/TR/2004/REC-webarch-20041215/#safe-interaction" class="externalRef"><ins class="diff-chg">
+section
+3.4
+</ins></a><ins class="diff-chg">
+).
+Care
+needs
+to
+be
+taken
+that
+user
+agents
+are
+not
+tricked
+into
+POSTing
+to
+incorrect
+URIs
+in
+such
+</ins>
+a
+<del class="diff-old">real
+threat
+here?
+How?
+</del>
+<ins class="diff-chg">way
+that
+may
+incur
+unintended
+effects
+or
+obligations.
+For
+example,
+a
+malicious
+site
+may
+present
+a
+pingback
+URI
+that
+executes
+an
+instruction
+on
+a
+different
+web
+site.
+Risks
+of
+such
+abuse
+may
+be
+mitigated
+by:
+performing
+pingbacks
+only
+to
+URIs
+from
+trusted
+sources;
+performing
+pingbacks
+only
+to
+the
+same
+origin
+as
+the
+provider
+of
+the
+pingback
+URI
+(like
+in-browser
+javascript
+same-origin
+restrictions),
+not
+sending
+credentials
+with
+pingback
+requests
+that
+were
+not
+obtained
+specifically
+for
+that
+purpose,
+and
+any
+other
+measures
+that
+may
+be
+appropriate.
+</ins>
+</p>
+<p>
+Accessing
+provenance
+services
+might
+reveal
+to
+the
+service
+and
+third-parties
+information
+which
+is
+considered
+private,
+including
+which
+resources
+a
+client
+has
+taken
+interest
+in.
+For
+instance,
+a
+browser
+extension
+which
+collects
+all
+provenance
+data
+for
+a
+resource
+which
+is
+being
+saved
+to
+the
+local
+disk,
+could
+be
+revealing
+user
+interest
+in
+a
+sensitive
+resource
+to
+a
+third-party
+site
+listed
+by
+<code>
+prov:has_provenance
+</code>
+or
+<code>
+prov:has_query_service
+</code>
+relation.
+A
+detailed
+query
+submitted
+to
+a
+third-party
+provenance
+query
+service
+might
+be
+revealing
+personal
+information
+such
+as
+social
+security
+numbers.
+Accordingly,
+user
+agents
+in
+particular
+<em class="rfc2119" title="SHOULD NOT">
+SHOULD
+NOT
+</em>
+follow
+provenance
+and
+provenance
+service
+links
+without
+first
+obtaining
+the
+user's
+explicit
+permission
+to
+do
+so.
+</p>
+</section>
+<section class="appendix" id="acknowledgements">
+<h2>
+<span class="secno">
+A.
+</span>
+Acknowledgements
+</h2>
+<p>
+The
+editors
+acknowledge
+the
+contribution
+and
+review
+from
+members
+of
+the
+<abbr title="World Wide Web Consortium">
+W3C
+</abbr>
+Provenance
+working
+group
+for
+their
+feedback
+throughout
+the
+development
+of
+this
+specification.
+</p>
+<p>
+<del class="diff-old">The
+provenance
+query
+service
+description
+</del>
+<ins class="diff-chg">Thanks
+to
+Erik
+Wilde
+</ins>
+and
+<del class="diff-old">forward
+provenance
+specifications
+are
+substantially
+based
+on
+proposals
+by
+Stian
+Soiland-Reyes
+(University
+</del>
+<ins class="diff-chg">other
+members
+</ins>
+of
+<del class="diff-old">Manchester).
+</del>
+<ins class="diff-chg">the
+</ins><abbr title="World Wide Web Consortium"><ins class="diff-chg">
+W3C
+</ins></abbr><ins class="diff-chg">
+Linked
+Data
+Platform
+working
+group
+for
+an
+extended
+discussion
+of
+REST
+service
+design
+issues,
+which
+has
+informed
+some
+aspects
+of
+the
+provenance
+service
+mechanisms.
+</ins>
+</p>
+<p>
+Thanks
+to
+Robin
+Berjon
+for
+making
+our
+lives
+easier
+with
+his
+<a href="http://dev.w3.org/2009/dap/ReSpec.js/documentation.html" class="externalRef">
+ReSpec
+</a>
+tool.
+</p>
+<p>
+<ins class="diff-new">Members
+of
+the
+PROV
+Working
+Group
+at
+the
+time
+of
+publication
+of
+this
+document
+were:
+Ilkay
+Altintas
+(Invited
+expert),
+Reza
+B'Far
+(Oracle
+Corporation),
+Khalid
+Belhajjame
+(University
+of
+Manchester),
+James
+Cheney
+(University
+of
+Edinburgh,
+School
+of
+Informatics),
+Sam
+Coppens
+(iMinds
+-
+Ghent
+University),
+David
+Corsar
+(University
+of
+Aberdeen,
+Computing
+Science),
+Stephen
+Cresswell
+(The
+National
+Archives),
+Tom
+De
+Nies
+(iMinds
+-
+Ghent
+University),
+Helena
+Deus
+(DERI
+Galway
+at
+the
+National
+University
+of
+Ireland,
+Galway,
+Ireland),
+Simon
+Dobson
+(Invited
+expert),
+Martin
+Doerr
+(Foundation
+for
+Research
+and
+Technology
+-
+Hellas(FORTH)),
+Kai
+Eckert
+(Invited
+expert),
+Jean-Pierre
+EVAIN
+(European
+Broadcasting
+Union,
+EBU-UER),
+James
+Frew
+(Invited
+expert),
+Irini
+Fundulaki
+(Foundation
+for
+Research
+and
+Technology
+-
+Hellas(FORTH)),
+Daniel
+Garijo
+(Ontology
+Engineering
+Group,
+Universidad
+Politécnica
+de
+Madrid,
+Spain),
+Yolanda
+Gil
+(Invited
+expert),
+Ryan
+Golden
+(Oracle
+Corporation),
+Paul
+Groth
+(Vrije
+Universiteit),
+Olaf
+Hartig
+(Invited
+expert),
+David
+Hau
+(National
+Cancer
+Institute,
+NCI),
+Sandro
+Hawke
+(
+</ins><abbr title="World Wide Web Consortium"><ins class="diff-new">
+W3C
+</ins></abbr><ins class="diff-new">
+/
+</ins><abbr title="Massachusetts Institute of Technology"><ins class="diff-new">
+MIT
+</ins></abbr><ins class="diff-new">
+),
+Jörn
+Hees
+(German
+Research
+Center
+for
+Artificial
+Intelligence
+(DFKI)
+Gmbh),
+Ivan
+Herman,
+(
+</ins><abbr title="World Wide Web Consortium"><ins class="diff-new">
+W3C
+</ins></abbr><ins class="diff-new">
+/
+</ins><abbr title="European Research Consortium for Informatics and Mathematics"><ins class="diff-new">
+ERCIM
+</ins></abbr><ins class="diff-new">
+),
+Ralph
+Hodgson
+(TopQuadrant),
+Hook
+Hua
+(Invited
+expert),
+Trung
+Dong
+Huynh
+(University
+of
+Southampton),
+Graham
+Klyne
+(University
+of
+Oxford),
+Michael
+Lang
+(Revelytix,
+Inc.),
+Timothy
+Lebo
+(Rensselaer
+Polytechnic
+Institute),
+James
+McCusker
+(Rensselaer
+Polytechnic
+Institute),
+Deborah
+McGuinness
+(Rensselaer
+Polytechnic
+Institute),
+Simon
+Miles
+(Invited
+expert),
+Paolo
+Missier
+(School
+of
+Computing
+Science,
+Newcastle
+university),
+Luc
+Moreau
+(University
+of
+Southampton),
+James
+Myers
+(Rensselaer
+Polytechnic
+Institute),
+Vinh
+Nguyen
+(Wright
+State
+University),
+Edoardo
+Pignotti
+(University
+of
+Aberdeen,
+Computing
+Science),
+Paulo
+da
+Silva
+Pinheiro
+(Rensselaer
+Polytechnic
+Institute),
+Carl
+Reed
+(Open
+Geospatial
+Consortium),
+Adam
+Retter
+(Invited
+Expert),
+Christine
+Runnegar
+(Invited
+expert),
+Satya
+Sahoo
+(Invited
+expert),
+David
+Schaengold
+(Revelytix,
+Inc.),
+Daniel
+Schutzer
+(FSTC,
+Financial
+Services
+Technology
+Consortium),
+Yogesh
+Simmhan
+(Invited
+expert),
+Stian
+Soiland-Reyes
+(University
+of
+Manchester),
+Eric
+Stephan
+(Pacific
+Northwest
+National
+Laboratory),
+Linda
+Stewart
+(The
+National
+Archives),
+Ed
+Summers
+(Library
+of
+Congress),
+Maria
+Theodoridou
+(Foundation
+for
+Research
+and
+Technology
+-
+Hellas(FORTH)),
+Ted
+Thibodeau
+(OpenLink
+Software
+Inc.),
+Curt
+Tilmes
+(National
+Aeronautics
+and
+Space
+Administration),
+Craig
+Trim
+(IBM
+Corporation),
+Stephan
+Zednik
+(Rensselaer
+Polytechnic
+Institute),
+Jun
+Zhao
+(University
+of
+Oxford),
+Yuting
+Zhao
+(University
+of
+Aberdeen,
+Computing
+Science).
+</ins></p>
+</section>
+<section class="appendix" id="terms-added-to-prov-namespace">
+<h2 id="prov-namespace">
+<span class="secno">
+B.
+</span>
+Terms
+added
+to
+prov:
+namespace
+</h2>
+<del class="diff-old">Possible
+renaming
+of
+service
+description
+relations
+to
+lowercase-only
+forms?
+</del>
+<p>
+This
+specification
+defines
+the
+following
+additional
+names
+in
+the
+provenance
+namespace
+with
+URI
+<a href="http://www.w3.org/ns/prov#" class="externalRef">
+http://www.w3.org/ns/prov#
+</a>.
+</p>
+<table>
+<tbody>
+<tr>
+<th>
+Name
+</th>
+<th>
+Description
+</th>
+<th>
+Definition
+ref
+</th>
+</tr>
+<tr style="vertical-align: top;">
+<td>
+<code>
+ServiceDescription
+</code>
+</td>
+<td>
+Type
+for
+a
+generic
+provenance
+query
+service.
+Mainly
+for
+use
+in
+RDF
+provenance
+query
+service
+descriptions,
+to
+facilitate
+discovery
+in
+linked
+data
+environments.
+</td>
+<td>
+<a href="#provenance-query-service-discovery" class="sectionRef sec-ref">
+section
+4.3
+Provenance
+query
+service
+discovery
+</a>
+</td>
+</tr>
+<tr style="vertical-align: top;">
+<td>
+<code>
+DirectQueryService
+</code>
+</td>
+<td>
+Type
+for
+a
+direct
+HTTP
+query
+service
+description.
+Mainly
+for
+use
+in
+RDF
+provenance
+query
+service
+descriptions,
+to
+distinguish
+direct
+HTTP
+query
+service
+descriptions
+from
+other
+query
+service
+descriptions.
+</td>
+<td>
+<a href="#direct-http-query-service-description" class="sectionRef sec-ref">
+section
+4.1.1
+Direct
+HTTP
+query
+service
+description
+</a>
+</td>
+</tr>
+<tr style="vertical-align: top;">
+<td>
+<code>
+has_anchor
+</code>
+</td>
+<td>
+Indicates
+a
+<a class="internalDFN" href="#dfn-target-uri">
+target-URI
+</a>
+for
+an
+resource,
+used
+by
+an
+associated
+provenance
+record.
+</td>
+<td>
+<a href="#resource-represented-as-html" class="sectionRef sec-ref">
+section
+3.2
+Resource
+represented
+as
+HTML
+</a>,
+<a href="#resource-represented-as-rdf" class="sectionRef sec-ref">
+section
+3.3
+Resource
+represented
+as
+RDF
+</a>
+</td>
+</tr>
+<tr style="vertical-align: top;">
+<td>
+<code>
+has_provenance
+</code>
+</td>
+<td>
+Indicates
+a
+<a class="internalDFN" href="#dfn-provenance-uri">
+provenance-URI
+</a>
+for
+a
+resource;
+the
+resource
+identified
+by
+this
+property
+presents
+a
+provenance
+record
+about
+its
+subject
+or
+anchor
+resource.
+</td>
+<td>
+<a href="#resource-accessed-by-http" class="sectionRef sec-ref">
+section
+3.1
+Resource
+accessed
+by
+HTTP
+</a>,
+<a href="#resource-represented-as-html" class="sectionRef sec-ref">
+section
+3.2
+Resource
+represented
+as
+HTML
+</a>
+</td>
+</tr>
+<tr style="vertical-align: top;">
+<td>
+<code>
+has_query_service
+</code>
+</td>
+<td>
+Indicates
+a
+<a class="internalDFN" href="#dfn-provenance-query-service">
+provenance
+query
+service
+</a>
+that
+can
+access
+provenance
+related
+to
+its
+subject
+or
+anchor
+resource.
+</td>
+<td>
+<a href="#specifying-provenance-query-services" class="sectionRef sec-ref">
+section
+3.1.1
+Specifying
+Provenance
+Query
+Services
+</a>
+</td>
+</tr>
+<tr style="vertical-align: top;">
+<td>
+<code>
+describesService
+</code>
+</td>
+<td>
+relates
+a
+generic
+provenance
+query
+service
+resource
+(type
+<code>
+prov:ServiceDescription
+</code>
+)
+to
+a
+specific
+query
+service
+description
+(e.g.
+a
+<code>
+prov:DirectQueryService
+</code>
+or
+a
+<code>
+sd:Service
+</code>
+).
+</td>
+<td>
+<a href="#provenance-query-service-description" class="sectionRef sec-ref">
+section
+4.1
+Provenance
+query
+service
+description
+</a>
+</td>
+</tr>
+<tr style="vertical-align: top;">
+<td>
+<code>
+provenanceUriTemplate
+</code>
+</td>
+<td>
+Indicates
+a
+URI
+template
+string
+for
+constructing
+provenance-URIs
+</td>
+<td>
+<a href="#direct-http-query-service-description" class="sectionRef sec-ref">
+section
+4.1.1
+Direct
+HTTP
+query
+service
+description
+</a>
+</td>
+</tr>
+<tr style="vertical-align: top;">
+<td>
+<code>
+pingback
+</code>
+</td>
+<td>
+Relates
+a
+resource
+to
+a
+provenance
+pingback
+service
+that
+may
+receive
+<del class="diff-old">forward
+</del>
+<ins class="diff-chg">additional
+</ins>
+provenance
+links
+about
+the
+resource.
+</td>
+<td>
+<a href="#provenance-pingback" class="sectionRef sec-ref">
+section
+5.
+<del class="diff-old">Forward
+provenance
+</del>
+<ins class="diff-chg">Provenance
+pingback
+</ins>
+</a>
+</td>
+</tr>
+</tbody>
+</table>
+<p>
+The
+ontology
+describing
+these
+terms
+is
+<del class="diff-old">at
+paq/prov-aq.ttl
+or
+paq/prov-aq.owl
+Update
+when
+location
+and
+copy
+finalized.
+</del>
+<ins class="diff-chg">available
+</ins><a href="http://www.w3.org/ns/prov-aq" class="externalRef"><ins class="diff-chg">
+here
+</ins></a>.
+</p>
+</section>
+<section id="references" class="appendix">
+<h2>
+<span class="secno">
+C.
+</span>
+<del class="diff-old">Changes
+log
+</del>
+<ins class="diff-chg">References
+</ins>
+</h2>
+<del class="diff-old">Always
+update
+copy
+of
+mercurial
+change
+log.
+Below
+are
+changes
+since
+19
+June.
+</del>
+<section id="informative-references">
+<h3>
+<span class="secno">
+C.1
+</span>
+<del class="diff-old">Changes
+since
+20120619
+publication
+2013-02-27
+16:23
++0000
+35385cbbfb9f
+Graham
+Klyne
+Further
+refinements
+and
+bug
+fixes
+in
+the
+forward
+provenance
+section
+2013-02-27
+15:33
++0000
+2dfd7fac85c9
+Graham
+Klyne
+Merge
+2013-02-27
+15:19
++0000
+bae275eaaf81
+Stian
+Soiland-Reyes
+Added
+Stian
+as
+PROV-AQ
+author
+2013-02-27
+15:33
++0000
+ecf3af571f1e
+Graham
+Klyne
+Changed
+entity-URI
+back
+to
+target-URI,
+and
+updated
+concept
+definition
+to
+indicate
+it
+may
+also
+denote
+an
+activity
+2013-02-27
+13:02
++0000
+d6085196a22d
+Graham
+Klyne
+Some
+tidying
+up
+of
+section
+decsribing
+provenance
+pingback
+2013-02-27
+12:26
++0000
+018e25f63183
+Graham
+Klyne
+Changed
+all
+normative
+</del>
+<ins class="diff-chg">Informative
+</ins>
+references
+<del class="diff-old">to
+informative
+(this
+being
+a
+NOTE)
+2013-02-27
+12:23
++0000
+33eea34f1863
+Graham
+Klyne
+Renamed
+link
+relations
+'hasProvenance',
+'hasAnchor'
+and
+'hasQueryService'
+to
+'has_provenance',
+'has_anchor'
+and
+'has_query_service'
+respectively.
+This
+is
+because
+RFC5988
+strongly
+recommends
+link
+relations
+to
+be
+all
+lowercase.
+2013-02-26
+18:42
++0000
+25eb1149862f
+Graham
+Klyne
+Add
+placeholder
+links
+to
+ontology;
+deleted
+note
+in
+Appendiox
+B
+2013-02-26
+18:33
++0000
+473af1a90df2
+Graham
+Klyne
+Added
+describesService
+in
+appendix
+B
+2013-02-26
+18:24
++0000
+211ff39ee699
+Graham
+Klyne
+Add
+to
+security
+considerations:
+possible
+malicious
+use
+of
+links;
+possible
+information
+leakage
+when
+provenance
+links
+are
+folloiwed,
+or
+services
+used.
+(Stian:58,59)
+2013-02-26
+18:12
++0000
+ec95bc31a43b
+Graham
+Klyne
+Incorporate
+Stian's
+revised
+pingback
+proposal:
+accept
+links
+rather
+than
+actual
+provenance.
+2013-02-26
+17:19
++0000
+eadbf7c04b31
+Graham
+Klyne
+Renamed
+prov:provPingback
+as
+just
+prov:pingback
+(Stian:55)
+2013-02-26
+17:07
++0000
+4fd6242c151c
+Graham
+Klyne
+</del>
+</h3>
+<del class="diff-old">Re-worked
+description
+of
+direct
+HTTP
+query,
+particularly
+escaping
+of
+URI
+special
+characters
+and
+provenance
+formats
+returned.
+Revise
+description
+of
+return
+codes.
+(Section
+4.2)
+2013-02-26
+16:10
++0000
+bbef7256bc91
+Graham
+Klyne
+</del>
+<dl class="bibliography">
+<del class="diff-old">Rename
+prov:ProvenanceQueryService
+to
+prov:ServiceDescription
+2013-02-26
+15:53
++0000
+206caf60d43a
+Graham
+Klyne
+</del>
+<dt id="bib-HTTP11">
+<ins class="diff-chg">[HTTP11]
+</ins>
+</dt>
+<dd>
+<del class="diff-old">Incorporarted
+Stian's
+proposal
+for
+a
+service
+description
+property
+2013-02-26
+14:40
++0000
+ae119d2377ca
+Graham
+Klyne
+</del>
+<ins class="diff-chg">R.
+Fielding
+et
+al.
+</ins><a href="http://www.ietf.org/rfc/rfc2616.txt">
+<del class="diff-old">Query
+service
+</del>
+<cite>
+<ins class="diff-chg">Hypertext
+Transfer
+Protocol
+</ins>
+-
+<del class="diff-old">editorial
+updates
+per
+Stian's
+comments
+35-41,
+including
+re-work
+of
+motivation
+2013-02-26
+13:34
++0000
+1a0bded232fb
+Graham
+Klyne
+Edirtorial
+updates
+in
+response
+to
+Luc's
+comments;
+updated
+CSS
+for
+external
+link
+2013-02-26
+11:26
++0000
+52d0f60610aa
+Graham
+Klyne
+Editorial
+updates
+in
+response
+to
+comments
+by
+Dong
+2013-02-26
+10:44
++0000
+a87d5f3c056c
+Graham
+Klyne
+Moved
+entire
+discussion
+of
+bundles
+in
+section
+2
+to
+a
+NOTE,
+and
+simplified.
+2013-02-26
+10:24
++0000
+fd2f1476c795
+Graham
+Klyne
+Further
+editorial
+changes
+suggestred
+by
+Stian's
+comments
+28,29,30,33;
+quote
+anchor
+parameters
+in
+Link:
+header
+examples
+2013-02-21
+19:16
++0000
+2a38eacd1735
+Graham
+Klyne
+Section
+3,
+editorial
+changes
+and
+reorganization
+of
+text
+suggested
+by
+Stian's
+comments
+(15,16,17,18,19,20,21,22,23,24,25,26,27).
+Moved
+some
+more
+material
+from
+sect
+3
+to
+sect
+1.3,
+and
+trimmed.
+Removed
+duplicate
+material
+about
+authority
+guarantees
+from
+section
+2.
+Added
+URI/IRI
+discussion
+to
+concepts.
+Added
+HTTP
+examples.
+Included
+'#'
+in
+shorthand
+references
+to
+link
+relations.
+2013-02-21
+17:27
++0000
+6c7dc767652a
+Graham
+Klyne
+More
+trimming
+of
+material
+onprovenance
+interpretation
+2013-02-21
+15:57
++0000
+be8f6ec8a2d5
+Graham
+Klyne
+Section
+3,
+editorial
+changes
+and
+reorganization
+of
+text
+suggested
+by
+Stian's
+comments
+(10,11,12,13,14).
+provider
+abnd
+consumer
+definitions
+moved
+to
+1.1.
+Further
+discussion
+of
+provenance
+interpretation
+moved
+to
+section
+1.3.
+2013-02-21
+15:31
++0000
+7e2c896d5b3b
+Graham
+Klyne
+Section
+2,
+non-substantive
+editorial
+changes
+suggested
+by
+Stian's
+comments
+(8,9)
+2013-02-21
+15:22
++0000
+9afefa103a72
+Graham
+Klyne
+Non-substantive
+editorial
+changes
+suggested
+by
+Stian's
+comments
+(4,6,7)
+2013-02-21
+15:07
++0000
+27cf75d7a6f2
+Graham
+Klyne
+Changed
+'target-URI'
+to
+'entity-URI',
+and
+revised
+some
+associated
+text
+to
+describe
+provenance
+access
+with
+respect
+to
+entities.
+Stian's
+comment
+(2)
+2013-02-21
+14:06
++0000
+cc0ec03fed0e
+Graham
+Klyne
+Update
+Turtle
+reference
+to
+CR
+2013-02-21
+13:33
++0000
+2d42fb73e214
+Graham
+Klyne
+Add
+placeholder
+appendix
+for
+change
+log
+2013-02-07
+18:26
++0000
+ae85f08dcda4
+Graham
+Klyne
+Further
+editorial
+fixes
+suggested
+by
+Tim
+2013-02-07
+17:43
++0000
+266d233ce54c
+Graham
+Klyne
+Move
+text
+about
+isolating
+information
+from
+section
+3
+(locating)
+to
+1.3
+(interpreting).
+Tim's
+comment
+(13)
+2013-02-07
+17:29
++0000
+a53fb5b58d8f
+Graham
+Klyne
+Section
+2
+editorial
+rework
+including
+suggestions
+by
+Tim
+2013-02-07
+16:41
++0000
+cf11871bb9ba
+Graham
+Klyne
+Editorial
+fixes
+suggested
+by
+Tim,
+and
+replace
+'provenance
+description'
+with
+'provenance
+record',
+following
+PROV-DM
+2013-02-07
+15:53
++0000
+4d16b451fc1a
+Graham
+Klyne
+Editorial
+fixes
+suggested
+by
+Simon
+2013-02-07
+15:42
++0000
+9406759adad3
+Graham
+Klyne
+Editorial
+fixes
+suggested
+by
+Simon
+2013-02-07
+14:50
++0000
+d5e7a0c76495
+Graham
+Klyne
+Minor
+editorial
+fixes
+suggested
+by
+Ivan
+2013-02-07
+13:44
++0000
+d4cf95c11dcd
+Graham
+Klyne
+Minor
+editorial
+fixes
+suggested
+by
+Ivan
+2013-01-10
+15:43
++0100
+cb49c07522ff
+Paul
+Groth
+updated
+to
+fix
+minor
+editorial
+errors
+2013-01-04
+14:23
++0000
+47a1f3baf67a
+Graham
+Klyne
+Editorial
+tweaks
+2013-01-04
+13:26
++0000
+a374c48027b9
+Graham
+Klyne
+Separate
+prov:DirectQueryService
+(specifric
+mechanism)
+from
+prov:ProvenanceQueryService
+(generic)
+2013-01-04
+13:11
++0000
+7b4580bd6d52
+Graham
+Klyne
+Fix
+some
+section
+cross-references;
+rename
+'prov:hasProvenanceService'
+as
+'prov:hasQueryService'
+2013-01-04
+13:03
++0000
+f00efdbb4f6e
+Graham
+Klyne
+Reorganize
+provenance
+query
+service
+description
+to
+accommodate
+SPARQL
+(ISSUE
+601);
+'rename
+provenance
+service'
+as
+'provenance
+query
+service';
+rename
+'prov:ProvenanceService'
+as
+'prov:ProivenanceQueryService'
+2012-12-10
+22:40
++0000
+08deb1462a7c
+Graham
+Klyne
+Fix
+apostrophe
+2012-12-10
+19:03
++0000
+f0f315c6781c
+Graham
+Klyne
+Fold
+in
+Jun's
+editorial
+comments.
+Remove
+reference
+to
+POWDER
+2012-11-26
+14:43
++0000
+23f86dc89992
+Graham
+Klyne
+Change
+'provenance
+information'
+to
+'provenance
+description'
+(ISSUE
+601);
+extensive
+editorial
+changes
+should
+be
+reviewed
+2012-11-26
+12:07
++0000
+4bbf03ed4eff
+Graham
+Klyne
+Add
+note
+about
+service
+description
+and
+LDP
+consideration
+thereof
+2012-11-26
+11:49
++0000
+72ec0c88ede8
+Graham
+Klyne
+Add
+non-commital
+paragraph
+about
+accessing
+provenance
+bundles
+2012-11-26
+11:08
++0000
+b811ccb53b45
+Graham
+Klyne
+Update
+forward
+provenance
+(pingback)
+in
+response
+to
+comments;
+fix
+text
+around
+VoID
+example
+2012-11-20
+16:00
++0000
+839d503bd064
+Graham
+Klyne
+Added
+specification
+for
+pingback
+link
+header
+(ISSUE
+600)
+2012-11-20
+14:15
++0000
+0e668b4ce436
+Graham
+Klyne
+Tidy
+up
+some
+text
+2012-11-20
+14:03
++0000
+3cba6f76b797
+Graham
+Klyne
+Expanded
+discussion
+of
+provenance
+service
+discovery
+to
+include
+prov:hasProvenanceService
+2012-11-20
+12:22
++0000
+44586518f842
+Graham
+Klyne
+Remove
+speculative
+non-specification
+text
+to
+be
+covered
+in
+FAQ
+(ISSUES
+426,
+598)
+2012-11-20
+11:36
++0000
+2f1a8ca558a8
+Graham
+Klyne
+Added
+section
+with
+table
+of
+URIs
+and
+what
+they
+dereference
+to
+(ISSUE
+424)
+2012-11-20
+10:37
++0000
+d2acceb63c0b
+Graham
+Klyne
+Make
+treatment
+of
+direct
+retrieval
+and
+service
+for
+provenance
+access
+more
+equally
+visible
+(ISSUE
+422)
+2012-11-19
+18:53
++0000
+69d2ba847f40
+Graham
+Klyne
+Point
+out
+that
+provenance
+services
+can
+accept
+paraneters
+other
+than
+just
+'target'
+(ISSUE
+420)
+2012-11-19
+18:10
++0000
+6a283fe7b70c
+Graham
+Klyne
+Added
+definitions
+for
+accessung
+and
+locating
+(ISSUE
+417)
+2012-11-19
+13:23
++0000
+45683a007809
+Graham
+Klyne
+More
+CSS
+tweaking
+to
+override
+RewSopec.js
+colouring
+2012-11-19
+13:06
++0000
+390df423d8b3
+Graham
+Klyne
+Formatting
+and
+CSS
+colour
+tweaks
+for
+examples
+2012-11-19
+12:58
++0000
+7f6c1a541631
+Graham
+Klyne
+Added
+section
+on
+Link:
+headers
+and
+content
+negotiation
+(ISSUE
+416)
+2012-11-19
+12:17
++0000
+9c24773fd6c7
+Graham
+Klyne
+Revert
+to
+W3C
+-hosted
+ReSpec.js
+2012-11-19
+11:48
++0000
+10c290a46ee0
+Graham
+Klyne
+Added
+icon
+to
+distibguish
+external
+links
+(ISSUE
+400)
+2012-11-16
+16:29
++0000
+5f35560288e7
+Graham
+Klyne
+Updsate
+and
+cross-link
+table
+of
+prov:
+URIs
+defined
+2012-11-16
+16:01
++0000
+3144d9093733
+Graham
+Klyne
+Changed
+link
+relations
+to
+URIs;
+removed
+IANA
+considerations
+section
+2012-11-10
+19:03
++0000
+77c849e3d67d
+Graham
+Klyne
+Hyperlink
+concept
+definitions
+to
+themselves
+(per
+request
+from
+Tim
+2012-06-05)
+2012-11-10
+18:26
++0000
+aff3d2fcf8f5
+Graham
+Klyne
+Update
+security
+considerations
+with
+note
+about
+use
+of
+provenance
+as
+part
+of
+audit/enforcement
+mechanism
+2012-11-10
+18:07
++0000
+84864eeceffb
+Graham
+Klyne
+Update
+list
+of
+PROV
+documents,
+copied
+from
+PROV-DM
+2012-11-10
+02:08
++0000
+beb278a59b28
+Graham
+Klyne
+Revert
+JS
+import
+to
+W3C
+server
+2012-11-08
+22:36
++0000
+35ee2d7209ea
+Graham
+Klyne
+Adjust
+TODO
+notes
+2012-11-08
+22:27
++0000
+d269fcdfc9fd
+Graham
+Klyne
+Cut
+back
+on
+verbiage
+in
+sect
+3,4
+rbitrary
+data
+2012-11-08
+22:24
++0000
+aba651f6da5e
+Graham
+Klyne
+Adjust
+TODO
+notes
+2012-11-08
+22:20
++0000
+06627e013264
+Graham
+Klyne
+Revised
+section
+3
+descriptions
+in
+terms
+of
+prodcuers
+and
+consumers
+2012-11-08
+12:12
++0000
+098e7be8b4d5
+Graham
+Klyne
+Updated
+security
+considerations
+to
+mention
+audit
+2012-11-06
+17:04
++0000
+96247e20c8b4
+Graham
+Klyne
+Add
+TODO
+for
+producer/consumer
+roles,
+add
+note
+about
+multiple
+links,
+add
+reference
+to
+RFC3986
+for
+%-escaping
+2012-11-06
+15:17
++0000
+4fbe51a47591
+Graham
+Klyne
+Update
+security
+considerations,
+note
+about
+non-RDF
+service
+desription,
+PROV-O
+link,
+acknowledgements
+2012-06-20
+14:27
+-0700
+d0af0446868d
+Paul
+Groth
+</del>
+<ins class="diff-chg">HTTP/1.1
+</ins></cite>
+<del class="diff-old">updated
+to
+reflect
+newly
+published
+version
+</del>
+</a>.
+<ins class="diff-chg">June
+1999.
+RFC
+2616.
+URL:
+</ins><a href="http://www.ietf.org/rfc/rfc2616.txt"><ins class="diff-chg">
+http://www.ietf.org/rfc/rfc2616.txt
+</ins></a>
+</dd>
+<del class="diff-old">D.
+References
+D.1
+Informative
+references
+</del>
+<dt id="bib-INFO-ACC">
+[INFO-ACC]
+</dt>
+<dd>
+Weitzner,
+Abelson,
+Berners-Lee,
+Feigenbaum,
+Hendler,
+and
+Sussman.
+<a href="http://dig.csail.mit.edu/2008/06/info-accountability-cacm-weitzner.pdf">
+<cite>
+Information
+Accountability
+</cite>
+</a>.
+Communications
+of
+the
+ACM,
+Jun.
+2008,
+82-87,
+<a href="http://doi.acm.org/10.1145/1349026.1349043">
+http://doi.acm.org/10.1145/1349026.1349043
+</a>,
+<a href="http://dig.csail.mit.edu/2008/06/info-accountability-cacm-weitzner.pdf">
+http://dig.csail.mit.edu/2008/06/info-accountability-cacm-weitzner.pdf
+</a>
+(alt)
+</dd>
+<dt id="bib-LINK-REL">
+[LINK-REL]
+</dt>
+<dd>
+M.
+Nottingham,
+<a href="http://www.ietf.org/rfc/rfc5988.txt">
+<cite>
+Web
+Linking
+</cite>
+</a>,
+October
+2010,
+Internet
+RFC
+5988.
+URL:
+<a href="http://www.ietf.org/rfc/rfc5988.txt">
+http://www.ietf.org/rfc/rfc5988.txt
+</a>
+</dd>
+<dt id="bib-PROV-CONSTRAINTS">
+[PROV-CONSTRAINTS]
+</dt>
+<dd>
+James
+Cheney;
+Paolo
+Missier;
+Luc
+Moreau;
+eds.
+<a href="http://www.w3.org/TR/2013/REC-prov-constraints-20130430/">
+<cite>
+Constraints
+of
+the
+PROV
+Data
+Model
+</cite>
+</a>.
+<del class="diff-old">12
+March
+</del>
+<ins class="diff-chg">30
+April
+</ins>
+2013,
+W3C
+<del class="diff-old">Proposed
+</del>
+Recommendation.
+URL:
+<del class="diff-old">http://www.w3.org/TR/2013/PR-prov-constraints-20130312/
+</del>
+<a href="http://www.w3.org/TR/2013/REC-prov-constraints-20130430/">
+<ins class="diff-chg">http://www.w3.org/TR/2013/REC-prov-constraints-20130430/
+</ins>
+</a>
+</dd>
+<dt id="bib-PROV-DC">
+[PROV-DC]
+</dt>
+<dd>
+Daniel
+Garijo;
+Kai
+Eckert;
+eds.
+<a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/">
+<cite>
+Dublin
+Core
+to
+PROV
+Mapping
+</cite>
+</a>.
+<del class="diff-old">12
+March
+</del>
+<ins class="diff-chg">30
+April
+</ins>
+2013,
+<del class="diff-old">Working
+Draft.
+</del>
+<ins class="diff-chg">W3C
+Note.
+</ins>
+URL:
+<del class="diff-old">http://www.w3.org/TR/2013/WD-prov-dc-20130312/
+</del>
+<a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/">
+<ins class="diff-chg">http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/
+</ins>
+</a>
+</dd>
+<dt id="bib-PROV-DICTIONARY">
+[PROV-DICTIONARY]
+</dt>
+<dd>
+Tom
+De
+Nies;
+Sam
+Coppens;
+eds.
+<a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/">
+<cite>
+PROV
+<ins class="diff-new">Dictionary:
+Modeling
+Provenance
+for
+</ins>
+Dictionary
+<ins class="diff-new">Data
+Structures
+</ins>
+</cite>
+</a>.
+<del class="diff-old">12
+March
+</del>
+<ins class="diff-chg">30
+April
+</ins>
+2013,
+<del class="diff-old">Working
+Draft.
+</del>
+<ins class="diff-chg">W3C
+Note.
+</ins>
+URL:
+<del class="diff-old">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/
+</del>
+<a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/">
+<ins class="diff-chg">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/
+</ins>
+</a>
+</dd>
+<dt id="bib-PROV-DM">
+[PROV-DM]
+</dt>
+<dd>
+Luc
+Moreau;
+Paolo
+Missier;
+eds.
+<a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/">
+<cite>
+PROV-DM:
+The
+PROV
+Data
+Model
+</cite>
+</a>.
+<del class="diff-old">12
+March
+</del>
+<ins class="diff-chg">30
+April
+</ins>
+2013,
+W3C
+<del class="diff-old">Proposed
+</del>
+Recommendation.
+URL:
+<del class="diff-old">http://www.w3.org/TR/2013/PR-prov-dm-20130312/
+</del>
+<a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/">
+<ins class="diff-chg">http://www.w3.org/TR/2013/REC-prov-dm-20130430/
+</ins>
+</a>
+</dd>
+<dt id="bib-PROV-LINKS">
+[PROV-LINKS]
+</dt>
+<dd>
+Luc
+Moreau;
+Timothy
+Lebo;
+eds.
+<a href="http://www.w3.org/TR/2013/NOTE-prov-links-20130430/">
+<cite>
+Linking
+Across
+Provenance
+Bundles
+</cite>
+</a>.
+<del class="diff-old">12
+March
+</del>
+<ins class="diff-chg">30
+April
+</ins>
+2013,
+<del class="diff-old">Working
+Draft.
+</del>
+<ins class="diff-chg">W3C
+Note.
+</ins>
+URL:
+<del class="diff-old">http://www.w3.org/TR/2013/WD-prov-links-20130312/
+</del>
+<a href="http://www.w3.org/TR/2013/NOTE-prov-links-20130430/">
+<ins class="diff-chg">http://www.w3.org/TR/2013/NOTE-prov-links-20130430/
+</ins>
+</a>
+</dd>
+<dt id="bib-PROV-N">
+[PROV-N]
+</dt>
+<dd>
+Luc
+Moreau;
+Paolo
+Missier;
+eds.
+<a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/">
+<cite>
+PROV-N:
+The
+Provenance
+Notation
+</cite>
+</a>.
+<del class="diff-old">12
+March
+</del>
+<ins class="diff-chg">30
+April
+</ins>
+2013,
+W3C
+<del class="diff-old">Proposed
+</del>
+Recommendation.
+URL:
+<del class="diff-old">http://www.w3.org/TR/2013/PR-prov-n-20130312/
+</del>
+<a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/">
+<ins class="diff-chg">http://www.w3.org/TR/2013/REC-prov-n-20130430/
+</ins>
+</a>
+</dd>
+<dt id="bib-PROV-O">
+[PROV-O]
+</dt>
+<dd>
+Timothy
+Lebo;
+Satya
+Sahoo;
+Deborah
+McGuinness;
+eds.
+<a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/">
+<cite>
+PROV-O:
+The
+PROV
+Ontology
+</cite>
+</a>.
+<del class="diff-old">12
+March
+</del>
+<ins class="diff-chg">30
+April
+</ins>
+2013,
+W3C
+<del class="diff-old">Proposed
+</del>
+Recommendation.
+URL:
+<del class="diff-old">http://www.w3.org/TR/2013/PR-prov-o-20130312/
+</del>
+<a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/">
+<ins class="diff-chg">http://www.w3.org/TR/2013/REC-prov-o-20130430/
+</ins>
+</a>
+</dd>
+<dt id="bib-PROV-OVERVIEW">
+[PROV-OVERVIEW]
+</dt>
+<dd>
+Paul
+Groth;
+Luc
+Moreau;
+eds.
+<a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/">
+<cite>
+PROV-OVERVIEW:
+An
+Overview
+of
+the
+PROV
+Family
+of
+Documents
+</cite>
+</a>.
+<del class="diff-old">12
+March
+</del>
+<ins class="diff-chg">30
+April
+</ins>
+2013,
+<del class="diff-old">Working
+Draft.
+</del>
+<ins class="diff-chg">W3C
+Note.
+</ins>
+URL:
+<del class="diff-old">http://www.w3.org/TR/2013/WD-prov-overview-20130312/
+</del>
+<a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/">
+<ins class="diff-chg">http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/
+</ins>
+</a>
+</dd>
+<dt id="bib-PROV-PRIMER">
+[PROV-PRIMER]
+</dt>
+<dd>
+Yolanda
+Gil;
+Simon
+Miles;
+eds.
+<a href="http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/">
+<cite>
+PROV
+Model
+Primer
+</cite>
+</a>.
+<del class="diff-old">12
+March
+</del>
+<ins class="diff-chg">30
+April
+</ins>
+2013,
+<del class="diff-old">Working
+Draft.
+</del>
+<ins class="diff-chg">W3C
+Note.
+</ins>
+URL:
+<del class="diff-old">http://www.w3.org/TR/2013/WD-prov-primer-20130312/
+</del>
+<a href="http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/">
+<ins class="diff-chg">http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/
+</ins>
+</a>
+</dd>
+<dt id="bib-PROV-SEM">
+[PROV-SEM]
+</dt>
+<dd>
+James
+Cheney;
+ed.
+<a href="http://www.w3.org/TR/2013/NOTE-prov-sem-20130430">
+<cite>
+Semantics
+of
+the
+PROV
+Data
+Model
+</cite>
+</a>.
+<del class="diff-old">12
+March
+</del>
+<ins class="diff-chg">30
+April
+</ins>
+2013,
+<del class="diff-old">Working
+Draft.
+</del>
+<ins class="diff-chg">W3C
+Note.
+</ins>
+URL:
+<del class="diff-old">http://www.w3.org/TR/2013/WD-prov-sem-20130312
+</del>
+<a href="http://www.w3.org/TR/2013/NOTE-prov-sem-20130430">
+<ins class="diff-chg">http://www.w3.org/TR/2013/NOTE-prov-sem-20130430
+</ins>
+</a>.
+</dd>
+<dt id="bib-PROV-XML">
+[PROV-XML]
+</dt>
+<dd>
+Hook
+Hua;
+Curt
+Tilmes;
+Stephan
+Zednik;
+eds.
+<a href="http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/">
+<cite>
+PROV-XML:
+The
+PROV
+XML
+Schema
+</cite>
+</a>.
+<del class="diff-old">12
+March
+</del>
+<ins class="diff-chg">30
+April
+</ins>
+2013,
+<del class="diff-old">Working
+Draft.
+</del>
+<ins class="diff-chg">W3C
+Note.
+</ins>
+URL:
+<del class="diff-old">http://www.w3.org/TR/2013/WD-prov-xml-20130312/
+</del>
+<a href="http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/">
+<ins class="diff-chg">http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/
+</ins>
+</a>
+</dd>
+<dt id="bib-RDF-CONCEPTS11">
+[RDF-CONCEPTS11]
+</dt>
+<dd>
+Richard
+Cyganiak,
+David
+Wood,
+eds.
+<a href="http://www.w3.org/TR/rdf11-concepts/">
+<cite>
+RDF
+1.1
+Concepts
+and
+Abstract
+Syntax
+</cite>
+</a>.
+Working
+Draft.
+URL:
+<a href="http://www.w3.org/TR/rdf11-concepts/">
+http://www.w3.org/TR/rdf11-concepts/
+</a>
+</dd>
+<dt id="bib-REST">
+[REST]
+</dt>
+<dd>
+R.
+Fielding.
+<a href="http://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm">
+<cite>
+Representational
+State
+Transfer
+(REST)
+</cite>
+</a>.
+2000,
+Ph.D.
+dissertation.
+URL:
+<a href="http://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm">
+http://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm
+</a>
+</dd>
+<dt id="bib-REST-APIs">
+[REST-APIs]
+</dt>
+<dd>
+R.
+Fielding.
+<a href="http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven">
+<cite>
+REST
+APIs
+must
+be
+hypertext
+driven
+</cite>
+</a>.
+October
+2008
+(blog
+post),
+URL:
+<a href="http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven">
+http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven
+</a>
+</dd>
+<dt id="bib-RFC2119">
+<ins class="diff-new">[RFC2119]
+</ins></dt><dd><ins class="diff-new">
+S.
+Bradner.
+</ins><a href="http://www.ietf.org/rfc/rfc2119.txt"><cite><ins class="diff-new">
+Key
+words
+for
+use
+in
+RFCs
+to
+Indicate
+Requirement
+Levels.
+</ins></cite></a><ins class="diff-new">
+March
+1997.
+Internet
+RFC
+2119.
+URL:
+</ins><a href="http://www.ietf.org/rfc/rfc2119.txt"><ins class="diff-new">
+http://www.ietf.org/rfc/rfc2119.txt
+</ins></a></dd>
+<dt id="bib-RFC2392">
+[RFC2392]
+</dt>
+<dd>
+E.
+Levinson.
+<a href="http://www.ietf.org/rfc/rfc2392.txt">
+<cite>
+Content-ID
+and
+Message-ID
+Uniform
+Resource
+Locators.
+</cite>
+</a>
+August
+1998.
+Internet
+RFC
+2392.
+URL:
+<a href="http://www.ietf.org/rfc/rfc2392.txt">
+http://www.ietf.org/rfc/rfc2392.txt
+</a>
+</dd>
+<dt id="bib-RFC3986">
+[RFC3986]
+</dt>
+<dd>
+T.
+Berners-Lee;
+R.
+Fielding;
+L.
+Masinter.
+<a href="http://www.ietf.org/rfc/rfc3986.txt">
+<cite>
+Uniform
+Resource
+Identifier
+(URI):
+Generic
+Syntax
+<ins class="diff-new">(RFC
+3986)
+</ins>
+</cite>
+</a>.
+January
+2005.
+<del class="diff-old">RFC
+3986.
+</del>
+<ins class="diff-chg">RFC.
+</ins>
+URL:
+<a href="http://www.ietf.org/rfc/rfc3986.txt">
+http://www.ietf.org/rfc/rfc3986.txt
+</a>
+</dd>
+<dt id="bib-RFC3987">
+[RFC3987]
+</dt>
+<dd>
+M.
+Dürst;
+M.
+Suignard.
+<a href="http://www.ietf.org/rfc/rfc3987.txt">
+<cite>
+Internationalized
+Resource
+Identifiers
+(IRIs)
+<ins class="diff-new">(RFC
+3987)
+</ins>
+</cite>
+</a>.
+January
+2005.
+<del class="diff-old">RFC
+3987.
+</del>
+<ins class="diff-chg">RFC.
+</ins>
+URL:
+<a href="http://www.ietf.org/rfc/rfc3987.txt">
+http://www.ietf.org/rfc/rfc3987.txt
+</a>
+</dd>
+<dt id="bib-SPARQL-HTTP">
+[SPARQL-HTTP]
+</dt>
+<dd>
+Chimezie
+Ogbuji.
+<a href="http://www.w3.org/TR/sparql11-http-rdf-update/">
+<cite>
+SPARQL
+1.1
+Graph
+Store
+HTTP
+Protocol
+</cite>
+</a>.
+<ins class="diff-new">21
+March
+2013,
+</ins>
+W3C
+<del class="diff-old">Candidate
+Recommendation
+8
+November
+2012,
+</del>
+<ins class="diff-chg">Recommendation.
+</ins>
+URL:
+<a href="http://www.w3.org/TR/sparql11-http-rdf-update/">
+http://www.w3.org/TR/sparql11-http-rdf-update/
+</a>
+</dd>
+<dt id="bib-SPARQL-SD">
+[SPARQL-SD]
+</dt>
+<dd>
+G.
+T.
+Williams.
+<a href="http://www.w3.org/TR/sparql11-service-description/">
+<cite>
+SPARQL
+1.1
+Service
+Description
+</cite>
+</a>.
+<del class="diff-old">2011,
+Work
+in
+progress.
+</del>
+<ins class="diff-chg">21
+March
+2013,
+W3C
+Recommendation.
+</ins>
+URL:
+<a href="http://www.w3.org/TR/sparql11-service-description/">
+http://www.w3.org/TR/sparql11-service-description/
+</a>
+</dd>
+<dt id="bib-TURTLE">
+[TURTLE]
+</dt>
+<dd>
+Eric
+Prud'hommeaux,
+Gavin
+Carothers.
+<a href="http://www.w3.org/TR/turtle/">
+<cite>
+Turtle:
+Terse
+RDF
+Triple
+Language
+</cite>
+</a>.
+19
+February
+2013.
+W3C
+Candidate
+Recommendation.
+URL:
+<a href="http://www.w3.org/TR/turtle/">
+http://www.w3.org/TR/turtle/
+</a>
+</dd>
+<dt id="bib-URI-template">
+[URI-template]
+</dt>
+<dd>
+J.
+Gregorio;
+R.
+Fielding;
+M.
+Hadley;
+M.
+Nottingham;
+D.
+Orchard.
+<a href="http://tools.ietf.org/html/rfc6570">
+<cite>
+URI
+Template
+</cite>
+</a>.
+March
+2012,
+Internet
+RFC
+6570.
+URL:
+<a href="http://tools.ietf.org/html/rfc6570/">
+<cite>
+http://tools.ietf.org/html/rfc6570
+</cite>
+</a>
+</dd>
+<dt id="bib-VoID">
+[VoID]
+</dt>
+<dd>
+Keith
+Alexander,
+Richard
+Cyganiak,
+Michael
+Hausenblas,
+Jun
+Zhao.
+<a href="http://www.w3.org/TR/void/">
+<cite>
+Describing
+Linked
+Datasets
+with
+the
+VoID
+Vocabulary
+</cite>
+</a>,
+W3C
+Interest
+Group
+Note
+03
+March
+2011,
+<a href="http://www.w3.org/TR/void/">
+http://www.w3.org/TR/void/
+</a>
+</dd>
+<dt id="bib-WEBARCH">
+[WEBARCH]
+</dt>
+<dd>
+Norman
+Walsh;
+Ian
+Jacobs.
+<a href="http://www.w3.org/TR/2004/REC-webarch-20041215/">
+<cite>
+Architecture
+of
+the
+World
+Wide
+Web,
+Volume
+One
+</cite>
+</a>.
+15
+December
+2004.
+W3C
+Recommendation.
+URL:
+<a href="http://www.w3.org/TR/2004/REC-webarch-20041215/">
+http://www.w3.org/TR/2004/REC-webarch-20041215/
+</a>
+</dd>
+</dl>
+</section>
+</section>
+</body>
+</html>
+
+
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/paq/releases/NOTE-prov-aq-20130430/images/README.txt Fri Apr 26 09:27:12 2013 +0100
@@ -0,0 +1,4 @@
+External link icon copied from Wikipedia http://bits.wikimedia.org/static-1.21wmf3/skins/vector/images/external-link-ltr-icon.png
+
+Re-used with assumed permission per http://wikimediafoundation.org/wiki/Terms_of_use
+
Binary file paq/releases/NOTE-prov-aq-20130430/images/external-link-ltr-icon.png has changed
--- a/primer/NOTE-prov-primer-20130430/Overview.html Fri Apr 26 09:26:16 2013 +0100
+++ b/primer/NOTE-prov-primer-20130430/Overview.html Fri Apr 26 09:27:12 2013 +0100
@@ -1,2251 +1,2247 @@
-<!DOCTYPE html>
-<html lang="en" dir="ltr">
-<head>
- <title>PROV Model Primer</title>
- <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
- <link rel="http://www.w3.org/ns/prov#has_provenance" href="http://www.w3.org/2011/prov/provenance/prov-primer">
- <!--
- === NOTA BENE ===
- For the three scripts below, if your spec resides on dev.w3 you can check them
- out in the same tree and use relative links so that they'll work offline,
- -->
- <!-- PM -->
- <style type="text/css">
- .note { font-size:small; margin-left:50px }
- </style>
-
- <script src="toggles.js" type="text/javascript"></script>
-
-
-
-
-
- <style>/*****************************************************************
- * ReSpec 3 CSS
- * Robin Berjon - http://berjon.com/
- *****************************************************************/
-
-/* --- INLINES --- */
-em.rfc2119 {
- text-transform: lowercase;
- font-variant: small-caps;
- font-style: normal;
- color: #900;
-}
-
-h1 acronym, h2 acronym, h3 acronym, h4 acronym, h5 acronym, h6 acronym, a acronym,
-h1 abbr, h2 abbr, h3 abbr, h4 abbr, h5 abbr, h6 abbr, a abbr {
- border: none;
-}
-
-dfn {
- font-weight: bold;
-}
-
-a.internalDFN {
- color: inherit;
- border-bottom: 1px solid #99c;
- text-decoration: none;
-}
-
-a.externalDFN {
- color: inherit;
- border-bottom: 1px dotted #ccc;
- text-decoration: none;
-}
-
-a.bibref {
- text-decoration: none;
-}
-
-cite .bibref {
- font-style: normal;
-}
-
-code {
- color: #ff4500;
-}
-
-
-/* --- --- */
-ol.algorithm { counter-reset:numsection; list-style-type: none; }
-ol.algorithm li { margin: 0.5em 0; }
-ol.algorithm li:before { font-weight: bold; counter-increment: numsection; content: counters(numsection, ".") ") "; }
-
-/* --- TOC --- */
-.toc a, .tof a {
- text-decoration: none;
-}
-
-a .secno, a .figno {
- color: #000;
-}
-
-ul.tof, ol.tof {
- list-style: none outside none;
-}
-
-.caption {
- margin-top: 0.5em;
- font-style: italic;
-}
-
-/* --- TABLE --- */
-table.simple {
- border-spacing: 0;
- border-collapse: collapse;
- border-bottom: 3px solid #005a9c;
-}
-
-.simple th {
- background: #005a9c;
- color: #fff;
- padding: 3px 5px;
- text-align: left;
-}
-
-.simple th[scope="row"] {
- background: inherit;
- color: inherit;
- border-top: 1px solid #ddd;
-}
-
-.simple td {
- padding: 3px 10px;
- border-top: 1px solid #ddd;
-}
-
-.simple tr:nth-child(even) {
- background: #f0f6ff;
-}
-
-/* --- DL --- */
-.section dd > p:first-child {
- margin-top: 0;
-}
-
-.section dd > p:last-child {
- margin-bottom: 0;
-}
-
-.section dd {
- margin-bottom: 1em;
-}
-
-.section dl.attrs dd, .section dl.eldef dd {
- margin-bottom: 0;
-}
-</style><link rel="stylesheet" href="http://www.w3.org/StyleSheets/TR/W3C-WG-NOTE"><!--[if lt IE 9]><script src='http://www.w3.org/2008/site/js/html5shiv.js'></script><![endif]--></head>
- <body><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">PROV Model Primer</h1>
-
- <h2 id="w3c-working-group-note-30-april-2013"><abbr title="World Wide Web Consortium">W3C</abbr> Working Group Note 30 April 2013</h2>
- <dl>
-
- <dt>This version:</dt>
- <dd><a href="http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/">http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/</a></dd>
- <dt>Latest published version:</dt>
- <dd><a href="http://www.w3.org/TR/prov-primer/">http://www.w3.org/TR/prov-primer/</a></dd>
-
-
-
-
- <dt>Previous version:</dt>
- <dd><a href="http://www.w3.org/TR/2013/WD-prov-primer-20130312/">http://www.w3.org/TR/2013/WD-prov-primer-20130312/</a></dd>
-
-
- <dt>Editors:</dt>
- <dd><a href="http://www.isi.edu/~gil/">Yolanda Gil</a>, Information Sciences Institute, University of Southern California, US</dd>
-<dd><a href="http://www.inf.kcl.ac.uk/staff/simonm/">Simon Miles</a>, King's College London, UK</dd>
-
-
- <dt>Contributors:</dt>
- <dd><span><a href="http://semanticweb.org/wiki/Khalid_Belhajjame">Khalid Belhajjame</a></span>, University of Manchester</dd>
-<dd><span>Helena Deus</span>, Digital Enterprise Research Institute (DERI), NUI Galway</dd>
-<dd><span><a href="http://www.oeg-upm.net/index.php/en/phdstudents/28-dgarijo">Daniel Garijo</a></span>, Ontology Engineering Group, Universidad Politécnica de Madrid, Spain</dd>
-<dd><span>Graham Klyne</span>, University of Oxford</dd>
-<dd><span><a href="http://www.ncl.ac.uk/computing/people/profile/Paolo.Missier">Paolo Missier</a></span>, Newcastle University</dd>
-<dd><span><a href="http://soiland-reyes.com/stian/">Stian Soiland-Reyes</a></span>, University of Manchester</dd>
-<dd><span><a href="http://tw.rpi.edu/web/person/StephanZednik">Stephan Zednik</a></span>, Rensselaer Polytechnic Institute</dd>
-
-
- </dl>
-
-
-
-
-
- <p class="copyright">
- <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> ©
- 2013
-
- <a href="http://www.w3.org/"><abbr title="World Wide Web Consortium">W3C</abbr></a><sup>®</sup>
- (<a href="http://www.csail.mit.edu/"><abbr title="Massachusetts Institute of Technology">MIT</abbr></a>,
- <a href="http://www.ercim.eu/"><abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr></a>,
- <a href="http://www.keio.ac.jp/">Keio</a>, <a href="http://ev.buaa.edu.cn/">Beihang</a>), All Rights Reserved.
- <abbr title="World Wide Web Consortium">W3C</abbr> <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>,
- <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and
- <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.
- </p>
-
-
- <hr>
-</div>
- <section id="abstract" class="introductory"><h2>Abstract</h2>
- <p>
- This document provides an intuitive introduction and guide to the
- PROV Data Model for provenance interchange on the web. PROV defines a core data model for
- provenance for building representations of the entities, people and
- processes involved in producing a piece of data or thing in the world.
- This primer explains the fundamental PROV concepts and provides examples
- of its use. The primer is intended as a starting point for those wishing
- to create or use PROV data.
- </p>
- <p>
- The <a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/">PROV Document Overview</a> describes the overall state of PROV, and should be read before other PROV documents.
- </p>
-
- <!-- p>
- This is a document for internal discussion, which will ultimately
- evolve in the first Public Working Draft of the Primer.</p -->
- </section><section id="sotd" class="introductory"><h2>Status of This Document</h2>
-
-
-
- <p>
- <em>This section describes the status of this document at the time of its publication. Other
- documents may supersede this document. A list of current <abbr title="World Wide Web Consortium">W3C</abbr> publications and the latest revision
- of this technical report can be found in the <a href="http://www.w3.org/TR/"><abbr title="World Wide Web Consortium">W3C</abbr> technical reports
- index</a> at http://www.w3.org/TR/.</em>
- </p>
-
- <h4 id="prov-family-of-documents">PROV Family of Documents</h4>
- This document is part of the PROV family of documents, a set of documents defining various aspects that are necessary to achieve the vision of inter-operable
- interchange of provenance information in heterogeneous environments such as the Web. These documents are listed below. Please consult the [<cite><a class="bibref" href="#bib-PROV-OVERVIEW">PROV-OVERVIEW</a></cite>] for a guide to reading these documents.
- <ul>
- <li> <a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/">PROV-OVERVIEW</a> (Note), an overview of the PROV family of documents [<cite><a class="bibref" href="#bib-PROV-OVERVIEW">PROV-OVERVIEW</a></cite>];</li>
- <li> <a href="http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/">PROV-PRIMER</a> (Note), a primer for the PROV data model (this document);</li>
- <li> <a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/">PROV-O</a> (Recommendation), the PROV ontology, an OWL2 ontology allowing the mapping of the PROV data model to RDF [<cite><a class="bibref" href="#bib-PROV-O">PROV-O</a></cite>];</li>
- <li> <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/">PROV-DM</a> (Recommendation), the PROV data model for provenance [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>];</li>
- <li> <a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/">PROV-N</a> (Recommendation), a notation for provenance aimed at human consumption [<cite><a class="bibref" href="#bib-PROV-N">PROV-N</a></cite>];</li>
- <li> <a href="http://www.w3.org/TR/2013/REC-prov-constraints-20130430/">PROV-CONSTRAINTS</a> (Recommendation), a set of constraints applying to the PROV data model [<cite><a class="bibref" href="#bib-PROV-CONSTRAINTS">PROV-CONSTRAINTS</a></cite>];</li>
- <li> <a href="http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/">PROV-XML</a> (Note), an XML schema for the PROV data model [<cite><a class="bibref" href="#bib-PROV-XML">PROV-XML</a></cite>];</li>
- <li> <a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/">PROV-AQ</a> (Note), mechanisms for accessing and querying provenance [<cite><a class="bibref" href="#bib-PROV-AQ">PROV-AQ</a></cite>]; </li>
- <li> <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/">PROV-DICTIONARY</a> (Note) introduces a specific type of collection, consisting of key-entity pairs [<cite><a class="bibref" href="#bib-PROV-DICTIONARY">PROV-DICTIONARY</a></cite>];</li>
- <li> <a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/">PROV-DC</a> (Note) provides a mapping between PROV-O and Dublin Core Terms [<cite><a class="bibref" href="#bib-PROV-DC">PROV-DC</a></cite>];</li>
- <li> <a href="http://www.w3.org/TR/2013/NOTE-prov-sem-20130430/">PROV-SEM</a> (Note), a declarative specification in terms of first-order logic of the PROV data model [<cite><a class="bibref" href="#bib-PROV-SEM">PROV-SEM</a></cite>];</li>
- <li> <a href="http://www.w3.org/TR/2013/NOTE-prov-links-20130430/">PROV-LINKS</a> (Note) introduces a mechanism to link across bundles [<cite><a class="bibref" href="#bib-PROV-LINKS">PROV-LINKS</a></cite>].</li>
- </ul>
-
- <h4 id="implementations-encouraged">Implementations Encouraged</h4>
- <p>
- The Provenance Working Group encourages implementation of the material defined in this document.
- Although work on this document by the Provenance Working Group is complete,
- errors may be recorded in the <a href="http://www.w3.org/2011/prov/errata.html">errata</a> or and these may be addressed in future revisions.
- </p>
-
- <h4 id="please-send-comments">Please Send Comments</h4>
-
-
- <p>
- This document was published by the <a href="http://www.w3.org/2011/prov/">Provenance Working Group</a> as a Working Group Note.
-
-
- If you wish to make comments regarding this document, please send them to
- <a href="mailto:public-prov-comments@w3.org">public-prov-comments@w3.org</a>
- (<a href="mailto:public-prov-comments-request@w3.org?subject=subscribe">subscribe</a>,
- <a href="http://lists.w3.org/Archives/Public/public-prov-comments/">archives</a>).
-
-
-
-
- All comments are welcome.
-
-
- </p><p>
- Publication as a Working Group Note does not imply endorsement by the <abbr title="World Wide Web Consortium">W3C</abbr> Membership.
- This is a draft document and may be updated, replaced or obsoleted by other documents at
- any time. It is inappropriate to cite this document as other than work in progress.
- </p>
-
-
- <p>
-
- This document was produced by a group operating under the
- <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 <abbr title="World Wide Web Consortium">W3C</abbr> Patent Policy</a>.
-
-
-
-
- <abbr title="World Wide Web Consortium">W3C</abbr> maintains a <a href="http://www.w3.org/2004/01/pp-impl/46974/status" rel="disclosure">public list of any patent disclosures</a>
-
- made in connection with the deliverables of the group; that page also includes instructions for
- disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains
- <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential Claim(s)</a> must disclose the
- information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section
- 6 of the <abbr title="World Wide Web Consortium">W3C</abbr> Patent Policy</a>.
-
-
- </p>
-
-
-
-
-</section><section id="toc"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a href="#introduction" class="tocxref"><span class="secno">1. </span>Introduction</a></li><li class="tocline"><a href="#intuitive-overview-of-prov" class="tocxref"><span class="secno">2. </span>Intuitive overview of PROV</a><ul class="toc"><li class="tocline"><a href="#entities" class="tocxref"><span class="secno">2.1 </span>Entities</a></li><li class="tocline"><a href="#activities" class="tocxref"><span class="secno">2.2 </span>Activities</a></li><li class="tocline"><a href="#usage-and-generation" class="tocxref"><span class="secno">2.3 </span>Usage and Generation</a></li><li class="tocline"><a href="#agents-and-responsibility" class="tocxref"><span class="secno">2.4 </span>Agents and Responsibility</a></li><li class="tocline"><a href="#roles" class="tocxref"><span class="secno">2.5 </span>Roles</a></li><li class="tocline"><a href="#derivation-and-revision" class="tocxref"><span class="secno">2.6 </span>Derivation and Revision</a></li><li class="tocline"><a href="#plans" class="tocxref"><span class="secno">2.7 </span>Plans</a></li><li class="tocline"><a href="#time" class="tocxref"><span class="secno">2.8 </span>Time</a></li><li class="tocline"><a href="#alternate-entities-and-specialization" class="tocxref"><span class="secno">2.9 </span>Alternate Entities and Specialization</a></li></ul></li><li class="tocline"><a href="#examples-of-key-concepts-in-prov" class="tocxref"><span class="secno">3. </span>Examples of Key Concepts in PROV</a><ul class="toc"><li class="tocline"><a href="#entities-1" class="tocxref"><span class="secno">3.1 </span>Entities</a></li><li class="tocline"><a href="#activities-1" class="tocxref"><span class="secno">3.2 </span>Activities</a></li><li class="tocline"><a href="#usage-and-generation-1" class="tocxref"><span class="secno">3.3 </span>Usage and Generation</a></li><li class="tocline"><a href="#agents-and-responsibility-1" class="tocxref"><span class="secno">3.4 </span>Agents and Responsibility</a></li><li class="tocline"><a href="#roles-1" class="tocxref"><span class="secno">3.5 </span>Roles</a></li><li class="tocline"><a href="#derivation-and-revision-1" class="tocxref"><span class="secno">3.6 </span>Derivation and Revision</a></li><li class="tocline"><a href="#plans-1" class="tocxref"><span class="secno">3.7 </span>Plans</a></li><li class="tocline"><a href="#time-1" class="tocxref"><span class="secno">3.8 </span>Time</a></li><li class="tocline"><a href="#alternate-entities-and-specialization-1" class="tocxref"><span class="secno">3.9 </span>Alternate Entities and Specialization</a></li><li class="tocline"><a href="#the-complete-example" class="tocxref"><span class="secno">3.10 </span>The Complete Example</a></li></ul></li><li class="tocline"><a href="#summary" class="tocxref"><span class="secno">4. </span>Summary</a></li><li class="tocline"><a href="#acknowledgements" class="tocxref"><span class="secno">A. </span>Acknowledgements</a></li><li class="tocline"><a href="#changes-since-fourth-public-working-draft" class="tocxref"><span class="secno">B. </span>Changes Since Fourth Public Working Draft</a></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">C. </span>References</a><ul class="toc"><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">C.1 </span>Informative references</a></li></ul></li></ul></section>
-
-
-
- <section id="introduction">
- <!--OddPage--><h2><span class="secno">1. </span>Introduction</h2>
- <p>
- This primer document provides an accessible introduction to the PROV
- data model for provenance interchange on the Web.
- The <i>provenance</i> of digital objects represents their origins. PROV is a
- specification to express provenance records,
- which contain <i>descriptions</i> of the entities
- and activities involved in producing and delivering or otherwise influencing a
- given object.
- Provenance can be used for many purposes, such as
- understanding how data was collected so it can be meaningfully used, determining
- ownership and rights over an object, making judgements about information to
- determine whether to trust it, verifying that the process and steps used to obtain a
- result complies with given requirements, and reproducing how something was generated.
- </p>
-
- <p>
- As a specification for provenance, PROV accommodates all those different uses
- of provenance. Different people may have different perspectives on provenance,
- and as a result different types of information might be captured in provenance records.
- </p><ul>
- <li>
- One perspective might focus on <i>agent-centered provenance</i>, that is, what people or organizations
- were involved in generating or manipulating the information in question. For example,
- in the provenance of a picture in a news article we might capture the photographer who
- took it, the person that edited it, and the newspaper that published it.
- </li>
- <li>
- A second perspective
- might focus on <i>object-centered provenance</i>, by tracing the origins of portions of a
- document to other documents. An example is having a web page that was assembled from content
- from a news article, quotes of interviews with experts, and a chart that plots data from a
- government agency.
- </li>
- <li>A third perspective one might take is on <i>process-centered provenance</i>,
- capturing the actions and steps taken to generate the information in question. For example, a
- chart may have been generated by invoking a service to retrieve data from a database, then
- extracting certain statistics from the data using some statistics package, and finally
- processing these results with a graphing tool.
- </li>
- </ul>
- <p></p>
-
- <p>
- Provenance records are metadata. There are other kinds of metadata that are
- not provenance. For example, the size of an image is metadata of
- that image but it is not provenance.
- For general background on provenance, a
- comprehensive overview of requirements, use cases, prior research, and proposed
- vocabularies for provenance are available from the
- Final Report of the <abbr title="World Wide Web Consortium">W3C</abbr> Provenance Incubator Group [<cite><a class="bibref" href="#bib-PROVENANCE-XG">PROVENANCE-XG</a></cite>].
- That document contains three general scenarios
- that may help identify the provenance aspects of planned applications and
- help plan the design of a provenance system.
- </p>
-
- <p>
- This primer document aims to ease the adoption of the PROV specifications by providing:
- </p>
- <ul>
- <li>A high-level explanation of how PROV models provenance, in Section 2. A detailed description of
- all the concepts and relations in the PROV Data Model is provided in [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>].</li>
- <li>A simple self-contained example that illustrates how to produce and use PROV assertions, in
- Section 3.
- The example includes snippets in RDF using the PROV ontology [<cite><a class="bibref" href="#bib-PROV-O">PROV-O</a></cite>], in a
- notation designed for human consumption [<cite><a class="bibref" href="#bib-PROV-N">PROV-N</a></cite>], and in PROV's XML format [<cite><a class="bibref" href="#bib-PROV-XML">PROV-XML</a></cite>].
- The example shows how
- to combine PROV with other popular vocabularies such as FOAF [<cite><a class="bibref" href="#bib-FOAF">FOAF</a></cite>] and Dublin Core [<cite><a class="bibref" href="#bib-DCTERMS">DCTERMS</a></cite>].</li>
- </ul>
-
- <p>The document ends with a summary of major capabilities and features of PROV.</p>
-
- </section>
-
- <section id="intuitive-overview-of-prov">
- <!--OddPage--><h2><span class="secno">2. </span>Intuitive overview of PROV</h2>
-
- <p>
- This section provides an explanation of the main concepts in PROV.
- As with the rest of this document, it should be treated as a starting point for
- understanding the model. The PROV data model document [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>]
- provides precise definitions and constraints [<cite><a class="bibref" href="#bib-PROV-CONSTRAINTS">PROV-CONSTRAINTS</a></cite>] to be followed.
- </p>
- <p>
- The following diagram provides a high level overview of the structure of PROV records,
- limited to some key PROV concepts discussed in this document.
- Note that because PROV is meant to describe how things were created or delivered,
- PROV relations are named so they can be used in assertions about the past.
- </p>
-
- <div style="text-align: center;">
- <img src="images/key-concepts.png" alt="PROV key concepts overview">
- </div>
-
- <section id="entities">
- <h3><span class="secno">2.1 </span>Entities</h3>
-
- <p>
- In PROV, physical, digital, conceptual, or other kinds of thing are called
- <i>entities</i>.
- Examples of such entities are a web page, a chart, and a spellchecker.
- Provenance records can describe the provenance of entities, and
- an entity’s provenance may refer to many other entities. For example, a document D is
- an entity whose provenance refers to other entities such as a chart inserted into D,
- and the dataset that was used to create that chart.
- Entities may be described as having different attributes and
- be described from different perspectives. For example,
- document D as stored in my file system, the second version of document D,
- and D as an evolving document,
- are three distinct entities for which we may describe provenance.
- </p>
- </section>
-
- <section id="activities">
- <h3><span class="secno">2.2 </span>Activities</h3>
-
- <p>
- <i>Activities</i> are how entities come into
- existence and how their attributes change to become new entities,
- often making use of previously existing entities to achieve this.
- They are
- dynamic aspects of the world, such as actions, processes, etc.
- For example, if the second version of document D was generated
- by a translation from the first version of the document in another language,
- then this translation is an activity.
- </p>
- </section>
-
- <section id="usage-and-generation">
- <h3><span class="secno">2.3 </span>Usage and Generation</h3>
- <p>
- Activities <i>generate</i> new entities.
- For example, writing a document brings the document into existence, while
- revising the document brings a new version into existence.
- Activities also make <i>use</i> of entities. For example, revising a document
- to fix spelling mistakes uses the original version of the document as well
- as a list of corrections.
- Generation does not always occur at the end of an activity, and an activity may generate entities
- part-way through.
- Likewise, usage does not always occur at the beginning of an activity.
- </p>
- </section>
-
- <section id="agents-and-responsibility">
- <h3><span class="secno">2.4 </span>Agents and Responsibility</h3>
- <p>
- An <i>agent</i> takes a role in an activity such
- that the agent can be assigned some degree of responsibility for the activity taking
- place.
- An agent can be a person, a piece of software, an inanimate object, an organization, or
- other entities that may be ascribed responsibility.
- When an agent has some responsibility for an activity, PROV says the agent was
- <i>associated</i> with the activity, where several agents may be associated with
- an activity and vice-versa.
- Consider a chart displaying some statistics
- regarding crime rates over time in a linear regression. To represent the
- provenance of that chart, we could state that the person who created the
- chart was an agent involved in its creation, and that the software used to
- create the chart was also an agent involved in that activity.
- An agent may be <i>acting on behalf</i> of others, e.g. an employee on behalf of their
- organization, and we can express such chains of responsibility in the provenance.
- </p>
- <p>
- We can also describe that an entity is <i>attributed</i> to an agent to express
- the agent's responsibility for that entity, possibly along with other agents.
- This description can be understood as a shorthand
- for saying that the agent was responsible for the activity which generated
- the entity.
- </p>
- <p>
- One may want to describe the provenance of an agent. For example, an organization
- responsible for the creation of a report may evolve over time as the report is written as
- some members leave and others join. To make provenance assertions about an agent in PROV,
- the agent must be declared explicitly both as an agent and as an entity.
- </p>
-
- </section>
-
- <section id="roles">
- <h3><span class="secno">2.5 </span>Roles</h3>
- <p>
- A <i>role</i> is a description of the function or the part that an entity
- played in an activity. Roles specify
- the relationship between an entity and an activity, i.e. how
- the activity used or generated the entity. Roles also specify how agents are
- involved in an activity, qualifying their participation in the activity or
- specifying for what aspect of it each agent was responsible.
- For example, an agent may play the role of "editor" in an activity that uses
- one entity in the role of "document to be edited" and another in the role of
- "addition to be made to the document", to generate a further entity in the role of "edited document".
- Roles are application specific, so PROV does not define any particular roles.
- </p>
- </section>
-
- <section id="derivation-and-revision">
- <h3><span class="secno">2.6 </span>Derivation and Revision</h3>
- <p>
- When one entity's existence, content, characteristics and so on are
- at least partly due to another entity, then we say that the former was
- <i>derived</i> from the latter. For example, one document may contain
- material copied from another,
- and a chart was derived from the data that it illustrates.
- </p>
- <p>
- PROV allows some common, specialized kinds of derivation to be described.
- For example, a given entity, such as a document, may go through multiple <i>revisions</i>
- over time. Between revisions,
- one or more attributes of the entity may change.
- In PROV, the result of each revision is a new entity.
- PROV allows one to relate those entities by making a description that
- one was a revision of another.
- Another kind of derivation is to say that one entity, a quotation, <i>was quoted from</i>
- another entity, commonly a document.
- </p>
- </section>
-
- <section id="plans">
- <h3><span class="secno">2.7 </span>Plans</h3>
- <p>
- Activities may follow pre-defined procedures, such as recipes, tutorials, instructions, or workflows.
- PROV refers to these, in general, as <i>plans</i>, and allows the description that a plan was followed, by agents,
- in executing an activity.
- </p>
- </section>
-
- <section id="time">
- <h3><span class="secno">2.8 </span>Time</h3>
- <p>
- Time is often a critical aspect of provenance.
- PROV allows the timing of significant events to be described, including
- when an entity was generated or used, or when an activity started
- and finished. For example, the model can be used to describe facts such as when a new
- version of a document was created (generation time), or when a document was
- edited (start and end of the editing activity).
- </p>
- </section>
-
- <section id="alternate-entities-and-specialization">
- <h3><span class="secno">2.9 </span>Alternate Entities and Specialization</h3>
- <p>
- There is often more than one way to describe something in a record of
- provenance. Each perspective will be referred to by a separately identified
- entity, and PROV provides a mechanism for linking the different descriptions of
- the same thing together through the mechanism of <i>specialization</i>. One
- entity is a specialization of another entity if it shares the same fixed attributes,
- with the possible addition of further fixed attributes. This concept is best
- illustrated through a few use cases.
- </p>
- <p>
- Entities can be mutable things. For example, a webpage is a single
- entity, W, despite being edited over time. Each version of the webpage is
- also an entity, W1, W2... To connect an individual version to the webpage
- in general, we say that the former is a specialization of the latter: W1 is a
- specialization of W, W2 is a specialization of W, and so on.
- </p>
- <p>
- Two individuals may create provenance referring to the same thing from different
- perspectives. For example, the author of an article may attribute that article
- to themselves using PROV while, independently, a reader might quote a fact from that
- article elsewhere and document this in PROV. If the author later changes the fact,
- then from the reader's perspective there are now two versions of the article, and
- the reader had quoted from the version before the change. From the author's perspective,
- there is a single article, attributed to the author. If the author, the reader, or a
- third party, were to connect the two PROV records, that party would say that the
- article as referred to by the reader is a specialization of the same article
- as referred to by the author.
- </p>
- <p>
- The above illustrates where we may want to connect entities by
- saying that they refer to the same thing, but at different levels of specialization.
- PROV also allows us to more generally draw a connection between two descriptions
- of the same thing, even if not at different levels of specialization, describing the
- entities as <i>alternates</i> of each other. For example,
- two versions of the webpage above, W1 and W2, are alternates of each other because
- they describe the same webpage.
- </p>
- <p>
- As another example, if a file is copied from one directory to another to create a backup,
- we may say that the copies are alternate versions of the same, location-independent, file.
- Specifically, we may say that the file in the first directory, entity F1, is an alternate of the
- file in the second directory, entity F2. Note that it is
- the context (location) rather than content of the file that differs between the entities
- in this case.
- </p>
- </section>
-
- </section>
-
- <section id="examples-of-key-concepts-in-prov">
- <!--OddPage--><h2><span class="secno">3. </span>Examples of Key Concepts in PROV</h2>
-
- <p>
- In the following sections, we show how PROV can be used to model
- provenance in a specific example scenario. Samples of PROV data are given.
- These samples use the namespace prefixes <b>prov</b>, denoting
- terms from the PROV ontology, and prefixes <b>exc</b>, <b>exn</b>, <b>exb</b>, <b>exg</b>,
- denoting terms specific to the example.
- We illustrate in these examples how PROV can be used in combination with other
- languages, such as FOAF [<cite><a class="bibref" href="#bib-FOAF">FOAF</a></cite>] and Dublin Core [<cite><a class="bibref" href="#bib-DCTERMS">DCTERMS</a></cite>] (with namespace prefix <b>foaf</b> and
- <b>dcterms</b> respectively).
- </p>
- <p>
- The scenario describes a blogger exploring the provenance of an online newspaper
- article, including a chart produced from a government agency dataset. The
- provenance data comes from different sources: the blogger, the newspaper,
- the chart generator company and the government agency. The samples of provenance from each source
- use a different namespace prefix for identifiers that source has
- created: <b>exb</b>, <b>exn</b>, <b>exc</b>, and <b>exg</b>
- respectively.
- </p>
- <p>
- The samples can be displayed in one or more of the following formats.
- </p>
- <ul>
- <li>[<cite><a class="bibref" href="#bib-PROV-O">PROV-O</a></cite>] RDF triples, expressed using the [<cite><a class="bibref" href="#bib-TURTLE">TURTLE</a></cite>] notation.</li>
- <li>[<cite><a class="bibref" href="#bib-PROV-N">PROV-N</a></cite>] expressions.</li>
- <li>[<cite><a class="bibref" href="#bib-PROV-XML">PROV-XML</a></cite>] fragments.</li>
- </ul>
- <p>
- Select the formats to display using the buttons below. Note that if all formats
- are hidden, the worked examples may not make sense!
- </p>
- <form action="#"><p>
- <input id="hide-turtle-examples" type="button" value="Hide Turtle Examples" onclick="
- set_display_by_class('pre', 'turtle example', 'none');
- set_display_by_class('div', 'turtle example', 'none');
- set_display_by_id('hide-turtle-examples', 'none');
- set_display_by_id('show-turtle-examples', '');">
- <input id="show-turtle-examples" type="button" value="Show Turtle Examples" style="display:none" onclick="
- set_display_by_class('pre', 'turtle example', '');
- set_display_by_class('div', 'turtle example', '');
- set_display_by_id('hide-turtle-examples', '');
- set_display_by_id('show-turtle-examples', 'none');">
- <input id="hide-provn-examples" type="button" value="Hide PROV-N Examples" onclick="
- set_display_by_class('pre', 'provn example', 'none');
- set_display_by_class('div', 'provn example', 'none');
- set_display_by_id('hide-provn-examples', 'none');
- set_display_by_id('show-provn-examples', '');">
- <input id="show-provn-examples" type="button" value="Show PROV-N Examples" style="display:none" onclick="
- set_display_by_class('pre', 'provn example', '');
- set_display_by_class('div', 'provn example', '');
- set_display_by_id('hide-provn-examples', '');
- set_display_by_id('show-provn-examples', 'none');">
- <input id="hide-provxml-examples" type="button" value="Hide XML Examples" onclick="
- set_display_by_class('pre', 'provxml example', 'none');
- set_display_by_class('div', 'provxml example', 'none');
- set_display_by_id('hide-provxml-examples', 'none');
- set_display_by_id('show-provxml-examples', '');">
- <input id="show-provxml-examples" type="button" value="Show XML Examples" style="display:none" onclick="
- set_display_by_class('pre', 'provxml example', '');
- set_display_by_class('div', 'provxml example', '');
- set_display_by_id('hide-provxml-examples', '');
- set_display_by_id('show-provxml-examples', 'none');">
- </p>
- </form>
-
-
- <section id="entities-1">
- <h3><span class="secno">3.1 </span>Entities</h3>
-
- <p>
- An online newspaper publishes an article with a chart about crime statistics
- based on data (GovData) provided by a government portal.
- The article includes a chart based on the data, with data values composed (aggregated) by
- geographical regions.
- </p>
- <p>
- A blogger, Betty, looking at the article, spots what she thinks to be an error in the chart.
- Betty retrieves a record of the provenance of the article, describing how it was created.
- </p>
- <p>Betty finds the following descriptions of entities in the provenance.</p>
- <div class="turtle example">
- <div class="exampleheader">
- <span class="exampleheader"><b>Turtle Example</b>
- <a onclick="
- set_display_by_class('pre', 'turtle example', 'none');
- set_display_by_class('div', 'turtle example', 'none');
- set_display_by_id('hide-turtle-examples', 'none');
- set_display_by_id('show-turtle-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> exn:article a prov:Entity ;
- dcterms:title "Crime rises in cities" .
- exg:dataset1 a prov:Entity .
- exc:regionList a prov:Entity .
- exc:composition1 a prov:Entity .
- exc:chart1 a prov:Entity .
- </pre>
- </div>
- <div class="provn example">
- <div class="exampleheader">
- <span class="exampleheader"><b>PROV-N Example</b>
- <a onclick="
- set_display_by_class('pre', 'provn example', 'none');
- set_display_by_class('div', 'provn example', 'none');
- set_display_by_id('hide-provn-examples', 'none');
- set_display_by_id('show-provn-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> entity(exn:article, [dcterms:title="Crime rises in cities"])
- entity(exg:dataset1)
- entity(exc:regionList)
- entity(exc:composition1)
- entity(exc:chart1)
- </pre>
- </div>
- <div class="provxml example">
- <div class="exampleheader">
- <span class="exampleheader"><b>XML Example</b>
- <a onclick="
- set_display_by_class('pre', 'provxml example', 'none');
- set_display_by_class('div', 'provxml example', 'none');
- set_display_by_id('hide-provxml-examples', 'none');
- set_display_by_id('show-provxml-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> <prov:document>
- ...
- <prov:entity prov:id="exn:article">
- <dct:title>Crime rises in cities</dct:title>
- </prov:entity>
- <prov:entity prov:id="exg:dataset1"/>
- <prov:entity prov:id="exc:regionList1"/>
- <prov:entity prov:id="exc:composition1"/>
- <prov:entity prov:id="exc:chart1"/>
- </prov:document>
- </pre>
- </div>
- <p>
- These statements, in order, refer to the article
- (<code>exn:article</code>),
- an original data set (<code>exg:dataset1</code>),
- a list of regions (<code>exc:regionList</code>),
- data aggregated by region (<code>exc:composition1</code>),
- and a chart (<code>exc:chart1</code>), and state that each is an entity.
- Any entity may have attributes, such as the title
- of the article, expressed using <code>dcterms:title</code> above.
- </p>
- <p>
- Notice the different namespace prefixes used: for the article it corresponds to the
- newspaper that published it (<code>exn</code>), and
- for the dataset it is the government namespace (<code>exg</code>).
- The <code>dcterms:title</code> namespace is taken from the Dublin Core
- vocabulary.
- </p>
- <p>
- PROV data is commonly visualized for human consumption using <a href="http://www.w3.org/2011/prov/wiki/Diagrams">particular conventions</a>,
- which we will introduce over the following sections. To start with, entities
- are denoted using ovals, as shown below.
- </p>
- <img src="images/entities.png" alt="Visualization of the example entities">
- </section>
-
- <section id="activities-1">
- <h3><span class="secno">3.2 </span>Activities</h3>
-
- <p>
- Further, the provenance describes that there was
- an activity (<code>exc:compile1</code>) denoting the compilation of the
- chart from the data set.
- </p>
- <div class="turtle example">
- <div class="exampleheader">
- <span class="exampleheader"><b>Turtle Example</b>
- <a onclick="
- set_display_by_class('pre', 'turtle example', 'none');
- set_display_by_class('div', 'turtle example', 'none');
- set_display_by_id('hide-turtle-examples', 'none');
- set_display_by_id('show-turtle-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> exc:compile1 a prov:Activity .
- </pre>
- </div>
- <div class="provn example">
- <div class="exampleheader">
- <span class="exampleheader"><b>PROV-N Example</b>
- <a onclick="
- set_display_by_class('pre', 'provn example', 'none');
- set_display_by_class('div', 'provn example', 'none');
- set_display_by_id('hide-provn-examples', 'none');
- set_display_by_id('show-provn-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> activity(exc:compile1)
- </pre>
- </div>
- <div class="provxml example">
- <div class="exampleheader">
- <span class="exampleheader"><b>XML Example</b>
- <a onclick="
- set_display_by_class('pre', 'provxml example', 'none');
- set_display_by_class('div', 'provxml example', 'none');
- set_display_by_id('hide-provxml-examples', 'none');
- set_display_by_id('show-provxml-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> <prov:document>
- ...
- <prov:activity prov:id="exc:compile1"/>
- </prov:document>
- </pre>
- </div>
- <p>
- The provenance also includes reference to the more specific steps involved in this compilation,
- which are first composing the data by region (<code>exc:compose1</code>) and then generating the
- chart graphic (<code>exc:illustrate1</code>).
- </p>
- <div class="turtle example">
- <div class="exampleheader">
- <span class="exampleheader"><b>Turtle Example</b>
- <a onclick="
- set_display_by_class('pre', 'turtle example', 'none');
- set_display_by_class('div', 'turtle example', 'none');
- set_display_by_id('hide-turtle-examples', 'none');
- set_display_by_id('show-turtle-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> exc:compose1 a prov:Activity .
- exc:illustrate1 a prov:Activity .
- </pre>
- </div>
- <div class="provn example">
- <div class="exampleheader">
- <span class="exampleheader"><b>PROV-N Example</b>
- <a onclick="
- set_display_by_class('pre', 'provn example', 'none');
- set_display_by_class('div', 'provn example', 'none');
- set_display_by_id('hide-provn-examples', 'none');
- set_display_by_id('show-provn-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> activity(exc:compose1)
- activity(exc:illustrate1)
- </pre>
- </div>
- <div class="provxml example">
- <div class="exampleheader">
- <span class="exampleheader"><b>XML Example</b>
- <a onclick="
- set_display_by_class('pre', 'provxml example', 'none');
- set_display_by_class('div', 'provxml example', 'none');
- set_display_by_id('hide-provxml-examples', 'none');
- set_display_by_id('show-provxml-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> <prov:document>
- ...
- <prov:activity prov:id="exc:compose1"/>
- <prov:activity prov:id="exc:illustrate1"/>
- </prov:document>
- </pre>
- </div>
- <p>
- In visualizations of the PROV data, activities are depicted as rectangles, as below.
- </p>
- <img src="images/activities.png" alt="Visualization of the example activities">
- </section>
-
- <section id="usage-and-generation-1">
- <h3><span class="secno">3.3 </span>Usage and Generation</h3>
-
- <p>
- Concluding the basic description of what occurred, the provenance
- describes the key relations among the above
- entities and activities, i.e. the usage of an entity by an activity,
- or the generation of an entity by an activity.
- </p>
- <p>
- For example, the descriptions below state that the composition activity
- (<code>exc:compose1</code>) used the original data set, that it used the list of
- regions, and that the composed data was generated by this activity.
- </p>
- <div class="turtle example">
- <div class="exampleheader">
- <span class="exampleheader"><b>Turtle Example</b>
- <a onclick="
- set_display_by_class('pre', 'turtle example', 'none');
- set_display_by_class('div', 'turtle example', 'none');
- set_display_by_id('hide-turtle-examples', 'none');
- set_display_by_id('show-turtle-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> exc:compose1 prov:used exg:dataset1 ;
- prov:used exc:regionList1 .
- exc:composition1 prov:wasGeneratedBy exc:compose1 .
- </pre>
- </div>
- <div class="provn example">
- <div class="exampleheader">
- <span class="exampleheader"><b>PROV-N Example</b>
- <a onclick="
- set_display_by_class('pre', 'provn example', 'none');
- set_display_by_class('div', 'provn example', 'none');
- set_display_by_id('hide-provn-examples', 'none');
- set_display_by_id('show-provn-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> used(exc:compose1, exg:dataset1, -)
- used(exc:compose1, exc:regionList1, -)
- wasGeneratedBy(exc:composition1, exc:compose1, -)
- </pre>
- <p>Note that the - argument in the examples above denote unspecified optional
- information. See the [<cite><a class="bibref" href="#bib-PROV-N">PROV-N</a></cite>] specification for the details of what arguments
- may be expressed in each PROV-N statement.
- </p>
- </div>
- <div class="provxml example">
- <div class="exampleheader">
- <span class="exampleheader"><b>XML Example</b>
- <a onclick="
- set_display_by_class('pre', 'provxml example', 'none');
- set_display_by_class('div', 'provxml example', 'none');
- set_display_by_id('hide-provxml-examples', 'none');
- set_display_by_id('show-provxml-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> <prov:document>
- ...
- <prov:used>
- <prov:activity prov:ref="exc:compose1"/>
- <prov:entity prov:ref="exg:dataset1"/>
- </prov:used>
- <prov:used>
- <prov:activity prov:ref="exc:compose1"/>
- <prov:entity prov:ref="exc:regionList1"/>
- </prov:used>
- <prov:wasGeneratedBy>
- <prov:entity prov:ref="exc:composition1"/>
- <prov:activity prov:ref="exc:compose1"/>
- </prov:wasGeneratedBy>
- </prov:document>
- </pre>
- </div>
- <p>
- Similarly, the chart graphic creation activity (<code>exc:illustrate1</code>)
- used the composed data, and the chart was generated by this activity.
- </p>
- <div class="turtle example">
- <div class="exampleheader">
- <span class="exampleheader"><b>Turtle Example</b>
- <a onclick="
- set_display_by_class('pre', 'turtle example', 'none');
- set_display_by_class('div', 'turtle example', 'none');
- set_display_by_id('hide-turtle-examples', 'none');
- set_display_by_id('show-turtle-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> exc:illustrate1 prov:used exc:composition1 .
- exc:chart1 prov:wasGeneratedBy exc:illustrate1 .
- </pre>
- </div>
- <div class="provn example">
- <div class="exampleheader">
- <span class="exampleheader"><b>PROV-N Example</b>
- <a onclick="
- set_display_by_class('pre', 'provn example', 'none');
- set_display_by_class('div', 'provn example', 'none');
- set_display_by_id('hide-provn-examples', 'none');
- set_display_by_id('show-provn-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> used(exc:illustrate1, exc:composition1, -)
- wasGeneratedBy(exc:chart1, exc:illustrate1, -)
- </pre>
- </div>
- <div class="provxml example">
- <div class="exampleheader">
- <span class="exampleheader"><b>XML Example</b>
- <a onclick="
- set_display_by_class('pre', 'provxml example', 'none');
- set_display_by_class('div', 'provxml example', 'none');
- set_display_by_id('hide-provxml-examples', 'none');
- set_display_by_id('show-provxml-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> <prov:document>
- ...
- <prov:used>
- <prov:activity prov:ref="exc:illustrate1"/>
- <prov:entity prov:ref="exc:composition1"/>
- </prov:used>
- <prov:wasGeneratedBy>
- <prov:entity prov:ref="exc:chart1"/>
- <prov:activity prov:ref="exc:illustrate1"/>
- </prov:wasGeneratedBy>
- </prov:document>
- </pre>
- </div>
- <p>
- In visualizing the PROV data, usage and generation are connections between
- entities and activities. The arrows point from the future to the past.
- </p>
- <img src="images/use-generate.png" alt="Connection of the entities and activities by use and generation links">
- </section>
-
- <section id="agents-and-responsibility-1">
- <h3><span class="secno">3.4 </span>Agents and Responsibility</h3>
-
- <p>
- Digging deeper, Betty wants to know who compiled the chart.
- Betty sees that Derek was involved in both the composition and
- chart creation activities:
- </p>
- <div class="turtle example">
- <div class="exampleheader">
- <span class="exampleheader"><b>Turtle Example</b>
- <a onclick="
- set_display_by_class('pre', 'turtle example', 'none');
- set_display_by_class('div', 'turtle example', 'none');
- set_display_by_id('hide-turtle-examples', 'none');
- set_display_by_id('show-turtle-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> exc:compose1 prov:wasAssociatedWith exc:derek .
- exc:illustrate1 prov:wasAssociatedWith exc:derek .
- </pre>
- </div>
- <div class="provn example">
- <div class="exampleheader">
- <span class="exampleheader"><b>PROV-N Example</b>
- <a onclick="
- set_display_by_class('pre', 'provn example', 'none');
- set_display_by_class('div', 'provn example', 'none');
- set_display_by_id('hide-provn-examples', 'none');
- set_display_by_id('show-provn-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> wasAssociatedWith(exc:compose1, exc:derek, -)
- wasAssociatedWith(exc:illustrate1, exc:derek, -)
- </pre>
- </div>
- <div class="provxml example">
- <div class="exampleheader">
- <span class="exampleheader"><b>XML Example</b>
- <a onclick="
- set_display_by_class('pre', 'provxml example', 'none');
- set_display_by_class('div', 'provxml example', 'none');
- set_display_by_id('hide-provxml-examples', 'none');
- set_display_by_id('show-provxml-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> <prov:document>
- ...
- <prov:wasAssociatedWith>
- <prov:activity prov:ref="exc:compose1"/>
- <prov:agent prov:ref="exc:derek"/>
- </prov:wasAssociatedWith>
- <prov:wasAssociatedWith>
- <prov:activity prov:ref="exc:illustrate1"/>
- <prov:agent prov:ref="exc:derek"/>
- </prov:wasAssociatedWith>
- </prov:document>
- </pre>
- </div>
- <p>
- The record for Derek provides the
- following description that
- Derek is an agent, specifically a person, followed by non-PROV information
- giving attributes of Derek.
- </p>
- <div class="turtle example">
- <div class="exampleheader">
- <span class="exampleheader"><b>Turtle Example</b>
- <a onclick="
- set_display_by_class('pre', 'turtle example', 'none');
- set_display_by_class('div', 'turtle example', 'none');
- set_display_by_id('hide-turtle-examples', 'none');
- set_display_by_id('show-turtle-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> exc:derek a prov:Agent ;
- a prov:Person ;
- foaf:givenName "Derek"^^xsd:string ;
- foaf:mbox <mailto:derek@example.org> .
- </pre>
- </div>
- <div class="provn example">
- <div class="exampleheader">
- <span class="exampleheader"><b>PROV-N Example</b>
- <a onclick="
- set_display_by_class('pre', 'provn example', 'none');
- set_display_by_class('div', 'provn example', 'none');
- set_display_by_id('hide-provn-examples', 'none');
- set_display_by_id('show-provn-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> agent(exc:derek,
- [prov:type='prov:Person', foaf:givenName="Derek",
- foaf:mbox="<mailto:derek@example.org>"])
- </pre>
- </div>
- <div class="provxml example">
- <div class="exampleheader">
- <span class="exampleheader"><b>XML Example</b>
- <a onclick="
- set_display_by_class('pre', 'provxml example', 'none');
- set_display_by_class('div', 'provxml example', 'none');
- set_display_by_id('hide-provxml-examples', 'none');
- set_display_by_id('show-provxml-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> <prov:document>
- ...
- <prov:agent prov:id="exc:derek">
- <prov:type>prov:Person</prov:type>
- <foaf:givenName>Derek</foaf:givenName>
- <foaf:mbox>mailto:derek@example.org</foaf:mbox>
- </prov:agent>
- </prov:document>
- </pre>
- </div>
- <p>
- Derek works as part of an organization, Chart Generators Inc, and so the provenance
- declares that he acts on their behalf. Note that the organization is itself
- an agent. The namespace prefix used by the organization is <code>exc</code>.
- </p>
- <div class="turtle example">
- <div class="exampleheader">
- <span class="exampleheader"><b>Turtle Example</b>
- <a onclick="
- set_display_by_class('pre', 'turtle example', 'none');
- set_display_by_class('div', 'turtle example', 'none');
- set_display_by_id('hide-turtle-examples', 'none');
- set_display_by_id('show-turtle-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> exc:derek prov:actedOnBehalfOf exc:chartgen .
- exc:chartgen a prov:Agent ;
- a prov:Organization ;
- foaf:name "Chart Generators Inc" .
- </pre>
- </div>
- <div class="provn example">
- <div class="exampleheader">
- <span class="exampleheader"><b>PROV-N Example</b>
- <a onclick="
- set_display_by_class('pre', 'provn example', 'none');
- set_display_by_class('div', 'provn example', 'none');
- set_display_by_id('hide-provn-examples', 'none');
- set_display_by_id('show-provn-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> agent(exc:chartgen,
- [prov:type='prov:Organization',
- foaf:name="Chart Generators Inc"])
- actedOnBehalfOf(exc:derek, exc:chartgen)
- </pre>
- </div>
- <div class="provxml example">
- <div class="exampleheader">
- <span class="exampleheader"><b>XML Example</b>
- <a onclick="
- set_display_by_class('pre', 'provxml example', 'none');
- set_display_by_class('div', 'provxml example', 'none');
- set_display_by_id('hide-provxml-examples', 'none');
- set_display_by_id('show-provxml-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> <prov:document>
- ...
- <prov:agent prov:id="exc:chartgen">
- <prov:type>prov:Organization</prov:type>
- <foaf:name>Chart Generators Inc</foaf:name>
- </prov:agent>
- <prov:actedOnBehalfOf>
- <prov:delegate prov:ref="exc:derek"/>
- <prov:responsible prov:ref="exc:chartgen"/>
- </prov:actedOnBehalfOf>
- </prov:document>
- </pre>
- </div>
- <p>
- It would also be possible to express the more specific statement that Derek
- worked on the organization's behalf for a particular activity, rather than
- in general, and so may have acted on behalf of other organizations for other
- activities. See the PROV specifications for details on how to express
- activity-specific delegation.
- </p>
- <p>
- Finally, there is an explicit statement in the provenance that the chart was
- attributed to Derek.
- </p>
- <div class="turtle example">
- <div class="exampleheader">
- <span class="exampleheader"><b>Turtle Example</b>
- <a onclick="
- set_display_by_class('pre', 'turtle example', 'none');
- set_display_by_class('div', 'turtle example', 'none');
- set_display_by_id('hide-turtle-examples', 'none');
- set_display_by_id('show-turtle-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> exc:chart1 prov:wasAttributedTo exc:derek .
- </pre>
- </div>
- <div class="provn example">
- <div class="exampleheader">
- <span class="exampleheader"><b>PROV-N Example</b>
- <a onclick="
- set_display_by_class('pre', 'provn example', 'none');
- set_display_by_class('div', 'provn example', 'none');
- set_display_by_id('hide-provn-examples', 'none');
- set_display_by_id('show-provn-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> wasAttributedTo(exc:chart1, exc:derek)
- </pre>
- </div>
- <div class="provxml example">
- <div class="exampleheader">
- <span class="exampleheader"><b>XML Example</b>
- <a onclick="
- set_display_by_class('pre', 'provxml example', 'none');
- set_display_by_class('div', 'provxml example', 'none');
- set_display_by_id('hide-provxml-examples', 'none');
- set_display_by_id('show-provxml-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> <prov:document>
- ...
- <prov:wasAttributedTo>
- <prov:entity prov:ref="exc:chart1"/>
- <prov:agent prov:ref="exc:derek"/>
- </prov:wasAttributedTo>
- </prov:document>
- </pre>
- </div>
-
- <p>
- We can extend our graphical depiction to show the agents, association and attribution links.
- </p>
- <img src="images/agents.png" alt="Agents added to provenance graph and linked to entities and activities">
- </section>
-
- <section id="roles-1">
- <h3><span class="secno">3.5 </span>Roles</h3>
-
- <p>
- For Betty to understand where the error lies, she needs to have more detailed
- information on how entities have been used in and generated
- by activities. Betty has determined that <code>exc:compose1</code> used
- entities <code>exc:regionList1</code> and <code>exg:dataset1</code>, but she does not
- know what function these entities played in the processing. Betty
- also knows that <code>exc:derek</code> was associated with the activities, but she does
- not know if Derek was the analyst responsible for determining how the data
- should be composed.
- </p>
- <p>
- The above information is described as roles in the provenance. The composition
- activity involved entities in four roles: the data to be composed (<code>exc:dataToCompose</code>),
- the regions to aggregate by (<code>exc:regionsToAggregateBy</code>), the
- resulting composed data (<code>exc:composedData</code>), and the
- analyst doing the composition (<code>exc:analyst</code>).
- </p>
- <div class="turtle example">
- <div class="exampleheader">
- <span class="exampleheader"><b>Turtle Example</b>
- <a onclick="
- set_display_by_class('pre', 'turtle example', 'none');
- set_display_by_class('div', 'turtle example', 'none');
- set_display_by_id('hide-turtle-examples', 'none');
- set_display_by_id('show-turtle-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> exc:dataToCompose a prov:Role .
- exc:regionsToAggregateBy a prov:Role .
- exc:composedData a prov:Role .
- exc:analyst a prov:Role .
- </pre>
- <p>
- Examples in the sections above show descriptions of the simple facts that the
- composition activity used, generated and was enacted by entities/agents.
- For example, the usage of the data set by the compose activity is expressed
- as follows.
- </p>
- <div class="exampleheader">
- <span class="exampleheader"><b>Turtle Example</b>
- <a onclick="
- set_display_by_class('pre', 'turtle example', 'none');
- set_display_by_class('div', 'turtle example', 'none');
- set_display_by_id('hide-turtle-examples', 'none');
- set_display_by_id('show-turtle-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> exc:compose1 prov:used exg:dataset1 .
- </pre>
- <p>
- The
- provenance can contain more details of exactly how these entities and agents
- were involved in the activity.
- To express this, PROV-O refers to <i>qualified usage</i>, <i>qualified generation</i>, etc.,
- which are descriptions consisting of several statements about how usage, generation, etc. took place.
- For example, we may describe the plan followed by an agent in performing an activity, or
- the time at which an activity generated an entity, both illustrated later.
- Another example of qualified involvement is the role an entity played in an activity.
- The descriptions below state
- that the composition activity (<code>exc:compose1</code>) included the usage
- of the government data set (<code>exg:dataset1</code>) in the role of the data
- to be composed (<code>exc:dataToCompose</code>).
- </p>
- <div class="exampleheader">
- <span class="exampleheader"><b>Turtle Example</b>
- <a onclick="
- set_display_by_class('pre', 'turtle example', 'none');
- set_display_by_class('div', 'turtle example', 'none');
- set_display_by_id('hide-turtle-examples', 'none');
- set_display_by_id('show-turtle-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> exc:compose1 prov:qualifiedUsage [
- a prov:Usage ;
- prov:entity exg:dataset1 ;
- prov:hadRole exc:dataToCompose
- ] .
- </pre>
- </div>
- <div class="provn example">
- <p>
- In PROV-N, the role is expressed as one of the list of attributes in the used
- expression, with the attribute name <code>prov:role</code>.
- </p>
- <div class="exampleheader">
- <span class="exampleheader"><b>PROV-N Example</b>
- <a onclick="
- set_display_by_class('pre', 'provn example', 'none');
- set_display_by_class('div', 'provn example', 'none');
- set_display_by_id('hide-provn-examples', 'none');
- set_display_by_id('show-provn-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> used(exc:compose1, exg:dataset1, -, [prov:role='exc:dataToCompose'])
- </pre>
- </div>
- <div class="provxml example">
- <div class="exampleheader">
- <span class="exampleheader"><b>XML Example</b>
- <a onclick="
- set_display_by_class('pre', 'provxml example', 'none');
- set_display_by_class('div', 'provxml example', 'none');
- set_display_by_id('hide-provxml-examples', 'none');
- set_display_by_id('show-provxml-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> <prov:document>
- ...
- <prov:used>
- <prov:activity prov:ref="exc:compose1"/>
- <prov:entity prov:ref="exg:dataset1"/>
- <prov:role>exc:dataToCompose</prov:role>
- </prov:used>
- </prov:document>
- </pre>
- </div>
- <p>
- This can then be distinguished from the same activity's usage of the list of
- regions because the roles played are different.
- </p>
- <div class="turtle example">
- <div class="exampleheader">
- <span class="exampleheader"><b>Turtle Example</b>
- <a onclick="
- set_display_by_class('pre', 'turtle example', 'none');
- set_display_by_class('div', 'turtle example', 'none');
- set_display_by_id('hide-turtle-examples', 'none');
- set_display_by_id('show-turtle-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> exc:compose1 prov:qualifiedUsage [
- a prov:Usage ;
- prov:entity exc:regionList1 ;
- prov:hadRole exc:regionsToAggregateBy
- ] .
- </pre>
- </div>
- <div class="provn example">
- <div class="exampleheader">
- <span class="exampleheader"><b>PROV-N Example</b>
- <a onclick="
- set_display_by_class('pre', 'provn example', 'none');
- set_display_by_class('div', 'provn example', 'none');
- set_display_by_id('hide-provn-examples', 'none');
- set_display_by_id('show-provn-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> used(exc:compose1, exc:regionList1, -, [prov:role='exc:regionsToAggregateBy'])
- </pre>
- </div>
- <div class="provxml example">
- <div class="exampleheader">
- <span class="exampleheader"><b>XML Example</b>
- <a onclick="
- set_display_by_class('pre', 'provxml example', 'none');
- set_display_by_class('div', 'provxml example', 'none');
- set_display_by_id('hide-provxml-examples', 'none');
- set_display_by_id('show-provxml-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> <prov:document>
- ...
- <prov:used>
- <prov:activity prov:ref="exc:compose1"/>
- <prov:entity prov:ref="exc:regionList1"/>
- <prov:role>exc:regionsToAggregateBy</prov:role>
- </prov:used>
- </prov:document>
- </pre>
- </div>
- <p>
- Similarly, the provenance includes descriptions that the same activity was
- enacted in a particular way by Derek, so it indicates that he had the role of
- <code>exc:analyst</code>, and that the entity <code>exc:composition1</code> took the role of the composed
- data in what the activity generated:
- </p>
- <div class="turtle example">
- <div class="exampleheader">
- <span class="exampleheader"><b>Turtle Example</b>
- <a onclick="
- set_display_by_class('pre', 'turtle example', 'none');
- set_display_by_class('div', 'turtle example', 'none');
- set_display_by_id('hide-turtle-examples', 'none');
- set_display_by_id('show-turtle-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> exc:compose1 prov:qualifiedAssociation [
- a prov:Association ;
- prov:agent exc:derek ;
- prov:hadRole exc:analyst
- ] .
- exc:composition1 prov:qualifiedGeneration [
- a prov:Generation ;
- prov:activity exc:compose1 ;
- prov:hadRole exc:composedData
- ] .
- </pre>
- </div>
- <div class="provn example">
- <div class="exampleheader">
- <span class="exampleheader"><b>PROV-N Example</b>
- <a onclick="
- set_display_by_class('pre', 'provn example', 'none');
- set_display_by_class('div', 'provn example', 'none');
- set_display_by_id('hide-provn-examples', 'none');
- set_display_by_id('show-provn-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> wasAssociatedWith(exc:compose1, exc:derek, -, [prov:role='exc:analyst'])
- wasGeneratedBy(exc:composition1, exc:compose1, -, [prov:role='exc:composedData'])
- </pre>
- </div>
- <div class="provxml example">
- <div class="exampleheader">
- <span class="exampleheader"><b>XML Example</b>
- <a onclick="
- set_display_by_class('pre', 'provxml example', 'none');
- set_display_by_class('div', 'provxml example', 'none');
- set_display_by_id('hide-provxml-examples', 'none');
- set_display_by_id('show-provxml-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> <prov:document>
- ...
- <prov:wasAssociatedWith>
- <prov:activity prov:ref="exc:compose1"/>
- <prov:agent prov:ref="exc:derek"/>
- <prov:role>exc:analyst</prov:role>
- </prov:wasAssociatedWith>
- <prov:wasGeneratedBy>
- <prov:entity prov:ref="exc:composition1"/>
- <prov:activity prov:ref="exc:compose1"/>
- <prov:role>exc:composedData</prov:role>
- </prov:wasGeneratedBy>
- </prov:document>
- </pre>
- </div>
- <p>
- Depicting the above visually, we have the following.
- </p>
- <img src="images/roles.png" alt="Provenance graph annotated with roles played by entities and agents">
- </section>
-
- <section id="derivation-and-revision-1">
- <h3><span class="secno">3.6 </span>Derivation and Revision</h3>
-
- <p>
- After looking at the detail of the compilation activity, there appears
- to be nothing wrong, so Betty concludes the error is in the government dataset.
- She looks at the dataset <code>exg:dataset1</code>,
- and sees that it is missing data from one of the zipcodes in the area. She contacts
- the government agency, and a new version of GovData is created, declared to be the
- next revision of the data. The provenance of this new dataset,
- <code>exg:dataset2</code>, states that it is a revision of the
- old data set, <code>exg:dataset1</code>.
- </p>
- <div class="turtle example">
- <div class="exampleheader">
- <span class="exampleheader"><b>Turtle Example</b>
- <a onclick="
- set_display_by_class('pre', 'turtle example', 'none');
- set_display_by_class('div', 'turtle example', 'none');
- set_display_by_id('hide-turtle-examples', 'none');
- set_display_by_id('show-turtle-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> exg:dataset2 a prov:Entity ;
- prov:wasRevisionOf exg:dataset1 .
- </pre>
- </div>
- <div class="provn example">
- <div class="exampleheader">
- <span class="exampleheader"><b>PROV-N Example</b>
- <a onclick="
- set_display_by_class('pre', 'provn example', 'none');
- set_display_by_class('div', 'provn example', 'none');
- set_display_by_id('hide-provn-examples', 'none');
- set_display_by_id('show-provn-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> entity(exg:dataset2)
- wasDerivedFrom(exg:dataset2, exg:dataset1, [prov:type='prov:Revision'])
- </pre>
- </div>
- <div class="provxml example">
- <div class="exampleheader">
- <span class="exampleheader"><b>XML Example</b>
- <a onclick="
- set_display_by_class('pre', 'provxml example', 'none');
- set_display_by_class('div', 'provxml example', 'none');
- set_display_by_id('hide-provxml-examples', 'none');
- set_display_by_id('show-provxml-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> <prov:document>
- ...
- <entity prov:id="dataSet2"/>
- <prov:wasDerivedFrom>
- <prov:generatedEntity prov:ref="exg:dataset2"/>
- <prov:usedEntity prov:ref="exg:dataset1"/>
- <prov:type>prov:Revision</prov:type>
- </prov:wasDerivedFrom>
- </prov:document>
- </pre>
- </div>
- <p>
- Derek notices that there is a new dataset available and creates a new chart based on the revised data,
- using another compilation activity. Betty checks the article again at a
- later point, and wants to know if it is based on the old or new GovData.
- She sees a new description stating that the new chart is derived from the new dataset
- (the same relation could be expressed between the old chart and old dataset).
- </p>
- <div class="turtle example">
- <div class="exampleheader">
- <span class="exampleheader"><b>Turtle Example</b>
- <a onclick="
- set_display_by_class('pre', 'turtle example', 'none');
- set_display_by_class('div', 'turtle example', 'none');
- set_display_by_id('hide-turtle-examples', 'none');
- set_display_by_id('show-turtle-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> exc:chart2 a prov:Entity ;
- prov:wasDerivedFrom exg:dataset2 .
- </pre>
- </div>
- <div class="provn example">
- <div class="exampleheader">
- <span class="exampleheader"><b>PROV-N Example</b>
- <a onclick="
- set_display_by_class('pre', 'provn example', 'none');
- set_display_by_class('div', 'provn example', 'none');
- set_display_by_id('hide-provn-examples', 'none');
- set_display_by_id('show-provn-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> wasDerivedFrom(exc:chart2, exg:dataset2)
- </pre>
- </div>
- <div class="provxml example">
- <div class="exampleheader">
- <span class="exampleheader"><b>XML Example</b>
- <a onclick="
- set_display_by_class('pre', 'provxml example', 'none');
- set_display_by_class('div', 'provxml example', 'none');
- set_display_by_id('hide-provxml-examples', 'none');
- set_display_by_id('show-provxml-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> <prov:document>
- ...
- <prov:wasDerivedFrom>
- <prov:generatedEntity prov:ref="exc:chart2"/>
- <prov:usedEntity prov:ref="exg:dataset2"/>
- </prov:wasDerivedFrom>
- </prov:document>
- </pre>
- </div>
- <p>and that the new chart is a revision of the original one:
- </p>
- <div class="turtle example">
- <div class="exampleheader">
- <span class="exampleheader"><b>Turtle Example</b>
- <a onclick="
- set_display_by_class('pre', 'turtle example', 'none');
- set_display_by_class('div', 'turtle example', 'none');
- set_display_by_id('hide-turtle-examples', 'none');
- set_display_by_id('show-turtle-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> exc:chart2 a prov:Entity ;
- prov:wasRevisionOf exc:chart1 .
- </pre>
- </div>
- <div class="provn example">
- <div class="exampleheader">
- <span class="exampleheader"><b>PROV-N Example</b>
- <a onclick="
- set_display_by_class('pre', 'provn example', 'none');
- set_display_by_class('div', 'provn example', 'none');
- set_display_by_id('hide-provn-examples', 'none');
- set_display_by_id('show-provn-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> entity(exc:chart2)
- wasDerivedFrom(exc:chart2, exc:chart1, [prov:type='prov:Revision'])
- </pre>
- </div>
- <div class="provxml example">
- <div class="exampleheader">
- <span class="exampleheader"><b>XML Example</b>
- <a onclick="
- set_display_by_class('pre', 'provxml example', 'none');
- set_display_by_class('div', 'provxml example', 'none');
- set_display_by_id('hide-provxml-examples', 'none');
- set_display_by_id('show-provxml-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> <prov:document>
- ...
- <entity prov:id="chart2"/>
- <prov:wasDerivedFrom>
- <prov:generatedEntity prov:ref="exc:chart2"/>
- <prov:usedEntity prov:ref="exc:chart1"/>
- <prov:type>prov:Revision</prov:type>
- </prov:wasDerivedFrom>
- </prov:document>
- </pre>
- </div>
- <p>
- Derivation and revision are connections between entities, and so depicted
- with arrows in our visualization.
- </p>
- <img src="images/derivation.png" alt="Derivation and revision links between entities">
- </section>
-
- <section id="plans-1">
- <h3><span class="secno">3.7 </span>Plans</h3>
-
- <p>
- Betty then wishes to know whether the new data set correctly addresses
- the error that existed before. The provenance of the new dataset,
- <code>exg:dataset2</code>, describes not only who performed the corrections,
- Edith, but also what instructions she followed in doing so (in PROV terms, the plan).
- First, the correction activity (<code>exg:correct1</code>), the person who corrected
- it, Edith (<code>exg:edith</code>), and the correction instructions (<code>exg:instructions</code>)
- are described.
- </p><div class="turtle example">
- <div class="exampleheader">
- <span class="exampleheader"><b>Turtle Example</b>
- <a onclick="
- set_display_by_class('pre', 'turtle example', 'none');
- set_display_by_class('div', 'turtle example', 'none');
- set_display_by_id('hide-turtle-examples', 'none');
- set_display_by_id('show-turtle-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> exg:correct1 a prov:Activity .
- exg:edith a prov:Agent, prov:Person .
- exg:instructions a prov:Plan .
- </pre>
- </div>
- <div class="provn example">
- <div class="exampleheader">
- <span class="exampleheader"><b>PROV-N Example</b>
- <a onclick="
- set_display_by_class('pre', 'provn example', 'none');
- set_display_by_class('div', 'provn example', 'none');
- set_display_by_id('hide-provn-examples', 'none');
- set_display_by_id('show-provn-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> activity(exg:correct1)
- agent(exg:edith, [prov:type='prov:Person'])
- entity(exg:instructions)
- </pre>
- </div>
- <div class="provxml example">
- <div class="exampleheader">
- <span class="exampleheader"><b>XML Example</b>
- <a onclick="
- set_display_by_class('pre', 'provxml example', 'none');
- set_display_by_class('div', 'provxml example', 'none');
- set_display_by_id('hide-provxml-examples', 'none');
- set_display_by_id('show-provxml-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> <prov:document>
- ...
- <prov:activity prov:id="exg:correct1"/>
- <prov:agent prov:id="exg:edith">
- <prov:type>prov:Person</prov:type>
- </prov:agent>
- <prov:entity prov:id="exg:instructions">
- <prov:type>prov:Plan</prov:type>
- </prov:entity>
- </prov:document>
- </pre>
- </div>
- <div class="turtle example">
- <p>
- The connection between them is expressed in PROV-O using a qualified association giving details of
- how Edith was associated with the correction activity,
- including that she followed the above correction instructions.
- </p>
- <div class="exampleheader">
- <span class="exampleheader"><b>Turtle Example</b>
- <a onclick="
- set_display_by_class('pre', 'turtle example', 'none');
- set_display_by_class('div', 'turtle example', 'none');
- set_display_by_id('hide-turtle-examples', 'none');
- set_display_by_id('show-turtle-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> exg:correct1 prov:qualifiedAssociation [
- a Association ;
- prov:agent exg:edith ;
- prov:hadPlan exg:instructions
- ] .
- exg:dataset2 prov:wasGeneratedBy exg:correct1 .
- </pre>
- </div>
- <div class="provn example">
- <p>
- In PROV-N, the plan is an optional parameter to wasAssociatedWith descriptions.
- </p>
- <div class="exampleheader">
- <span class="exampleheader"><b>PROV-N Example</b>
- <a onclick="
- set_display_by_class('pre', 'provn example', 'none');
- set_display_by_class('div', 'provn example', 'none');
- set_display_by_id('hide-provn-examples', 'none');
- set_display_by_id('show-provn-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> wasAssociatedWith(exg:correct1, exg:edith, exg:instructions)
- wasGeneratedBy(exg:dataset2, exg:correct1, -)
- </pre>
- </div>
- <div class="provxml example">
- <p>
- In PROV-XML, the plan is an optional child of the wasAssociatedWith element.
- </p>
- <div class="exampleheader">
- <span class="exampleheader"><b>XML Example</b>
- <a onclick="
- set_display_by_class('pre', 'provxml example', 'none');
- set_display_by_class('div', 'provxml example', 'none');
- set_display_by_id('hide-provxml-examples', 'none');
- set_display_by_id('show-provxml-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> <prov:document>
- ...
- <prov:wasAssociatedWith>
- <prov:activity prov:ref="exg:correct1"/>
- <prov:agent prov:ref="exg:edith"/>
- <prov:plan prov:ref="exg:instructions"/>
- </prov:wasAssociatedWith>
- <prov:wasGeneratedBy>
- <prov:entity prov:ref="exg:dataset2"/>
- <prov:activity prov:ref="exg:correct1"/>
- </prov:wasGeneratedBy>
- </prov:document>
- </pre>
- </div>
- <p>
- Plans are additional information about the connection from an activity to
- an agent, and so, in our visualization, connect to the link between them.
- </p>
- <img src="images/plans.png" alt="Annotaion of example provenance graph with plan followed">
- </section>
-
- <section id="time-1">
- <h3><span class="secno">3.8 </span>Time</h3>
-
- <p>
- The government agency that produced GovData is concerned to know how long
- the incorrect chart was in circulation before the corrected chart was created.
- That is, they wish to compare the times at which the original and the corrected
- charts were generated. The snippet below shows that the second chart
- was generated roughly a month after the first.
- </p>
- <div class="turtle example">
- <div class="exampleheader">
- <span class="exampleheader"><b>Turtle Example</b>
- <a onclick="
- set_display_by_class('pre', 'turtle example', 'none');
- set_display_by_class('div', 'turtle example', 'none');
- set_display_by_id('hide-turtle-examples', 'none');
- set_display_by_id('show-turtle-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> exc:chart1 prov:generatedAtTime "2012-03-02T10:30:00"^^xsd:dateTime .
- exc:chart2 prov:generatedAtTime "2012-04-01T15:21:00"^^xsd:dateTime .
- </pre>
- </div>
- <div class="provn example">
- <div class="exampleheader">
- <span class="exampleheader"><b>PROV-N Example</b>
- <a onclick="
- set_display_by_class('pre', 'provn example', 'none');
- set_display_by_class('div', 'provn example', 'none');
- set_display_by_id('hide-provn-examples', 'none');
- set_display_by_id('show-provn-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> wasGeneratedBy(exc:chart1, exc:compile1, 2012-03-02T10:30:00)
- wasGeneratedBy(exc:chart2, exc:compile2, 2012-04-01T15:21:00)
- </pre>
- </div>
- <div class="provxml example">
- <div class="exampleheader">
- <span class="exampleheader"><b>XML Example</b>
- <a onclick="
- set_display_by_class('pre', 'provxml example', 'none');
- set_display_by_class('div', 'provxml example', 'none');
- set_display_by_id('hide-provxml-examples', 'none');
- set_display_by_id('show-provxml-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> <prov:document>
- ...
- <prov:wasGeneratedBy>
- <prov:entity prov:ref="exc:chart1"/>
- <prov:time>2012-03-02T10:30:00</prov:time>
- </prov:wasGeneratedBy>
- <prov:wasGeneratedBy>
- <prov:entity prov:ref="exc:chart2"/>
- <prov:time>2012-04-01T15:21:00</prov:time>
- </prov:wasGeneratedBy>
- </prov:document>
- </pre>
- </div>
-
- <p>
- To ensure their procedures are efficient, the agency also wishes to know how long the
- corrections took once the error was discovered. That is, they wish to know the
- start and end times of the correction activity (<code>exg:correct1</code>).
- These details are expressed as follows, showing that the corrections took a
- little over a day.
- </p>
- <div class="turtle example">
- <div class="exampleheader">
- <span class="exampleheader"><b>Turtle Example</b>
- <a onclick="
- set_display_by_class('pre', 'turtle example', 'none');
- set_display_by_class('div', 'turtle example', 'none');
- set_display_by_id('hide-turtle-examples', 'none');
- set_display_by_id('show-turtle-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> exg:correct1 prov:startedAtTime "2012-03-31T09:21:00"^^xsd:dateTime ;
- prov:endedAtTime "2012-04-01T15:21:00"^^xsd:dateTime .
- </pre>
- </div>
- <div class="provn example">
- <div class="exampleheader">
- <span class="exampleheader"><b>PROV-N Example</b>
- <a onclick="
- set_display_by_class('pre', 'provn example', 'none');
- set_display_by_class('div', 'provn example', 'none');
- set_display_by_id('hide-provn-examples', 'none');
- set_display_by_id('show-provn-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> activity(exg:correct1, 2012-03-31T09:21:00, 2012-04-01T15:21:00)
- </pre>
- </div>
- <div class="provxml example">
- <div class="exampleheader">
- <span class="exampleheader"><b>XML Example</b>
- <a onclick="
- set_display_by_class('pre', 'provxml example', 'none');
- set_display_by_class('div', 'provxml example', 'none');
- set_display_by_id('hide-provxml-examples', 'none');
- set_display_by_id('show-provxml-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> <prov:document>
- ...
- <prov:activity prov:id="exg:correct1">
- <prov:startTime>2012-03-31T09:21:00</prov:startTime>
- <prov:endTime>2012-04-01T15:21:00</prov:endTime>
- </prov:activity>
- </prov:document>
- </pre>
- </div>
- <p>
- Time is visualized as additional information regarding activities or the
- links between activities and entities or agents.
- </p>
- <img src="images/time.png" alt="Annotation of provenance graph with example timestamps">
- </section>
-
- <section id="alternate-entities-and-specialization-1">
- <h3><span class="secno">3.9 </span>Alternate Entities and Specialization</h3>
-
- <p>
- Before noticing anything wrong with the government data, Betty had already
- posted a blog entry about the article. The blog entry had its own published
- provenance. In particular, it contains some text copied from the article, and the
- provenance states that this text (<code>exb:quoteInBlogEntry-20130326</code>) is quoted
- from the article. Note the namespace prefix (<code>exb</code>) used for the blog.
- </p>
- <div class="turtle example">
- <div class="exampleheader">
- <span class="exampleheader"><b>Turtle Example</b>
- <a onclick="
- set_display_by_class('pre', 'turtle example', 'none');
- set_display_by_class('div', 'turtle example', 'none');
- set_display_by_id('hide-turtle-examples', 'none');
- set_display_by_id('show-turtle-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> exb:quoteInBlogEntry-20130326 a prov:Entity ;
- prov:value "Smaller cities have more crime than larger ones" ;
- prov:wasQuotedFrom exn:article .
- </pre>
- </div>
- <div class="provn example">
- <div class="exampleheader">
- <span class="exampleheader"><b>PROV-N Example</b>
- <a onclick="
- set_display_by_class('pre', 'provn example', 'none');
- set_display_by_class('div', 'provn example', 'none');
- set_display_by_id('hide-provn-examples', 'none');
- set_display_by_id('show-provn-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> entity(exb:quoteInBlogEntry-20130326, prov:value="Smaller cities have more crime than larger ones")
- wasDerivedFrom(exb:quoteInBlogEntry-20130326, exn:article, [prov:type='prov:Quotation'])
- </pre>
- </div>
- <div class="provxml example">
- <div class="exampleheader">
- <span class="exampleheader"><b>XML Example</b>
- <a onclick="
- set_display_by_class('pre', 'provxml example', 'none');
- set_display_by_class('div', 'provxml example', 'none');
- set_display_by_id('hide-provxml-examples', 'none');
- set_display_by_id('show-provxml-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> <prov:document>
- ...
- <prov:entity prov:id="exb:BlogEntry-20130326">
- <prov:value>Smaller cities have more crime than larger ones</prov:value>
- </prov:entity>
- <prov:wasDerivedFrom>
- <prov:generatedEntity prov:ref="exb:quoteInBlogEntry-20130326"/>
- <prov:usedEntity prov:ref="exn:article"/>
- <prov:type>prov:Quotation</prov:type>
- </prov:wasDerivedFrom>
- </prov:document>
- </pre>
- </div>
- <p>
- The newspaper, from past experience, anticipated that there could be revisions
- to the article, and so created identifiers for both the article in general
- (<code>exn:article</code>) as a URI that got redirected to the first version of the article (<code>exn:articleV1</code>),
- allowing both to be referred to as entities in provenance data.
- In the provenance records, the newspaper describes the connection between the two: that
- the first version of the article is a specialization of the article in general.
- </p>
- <div class="turtle example">
- <div class="exampleheader">
- <span class="exampleheader"><b>Turtle Example</b>
- <a onclick="
- set_display_by_class('pre', 'turtle example', 'none');
- set_display_by_class('div', 'turtle example', 'none');
- set_display_by_id('hide-turtle-examples', 'none');
- set_display_by_id('show-turtle-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> exn:articleV1 a prov:Entity ;
- prov:specializationOf exn:article .
- </pre>
- </div>
- <div class="provn example">
- <div class="exampleheader">
- <span class="exampleheader"><b>PROV-N Example</b>
- <a onclick="
- set_display_by_class('pre', 'provn example', 'none');
- set_display_by_class('div', 'provn example', 'none');
- set_display_by_id('hide-provn-examples', 'none');
- set_display_by_id('show-provn-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> entity(exn:articleV1)
- specializationOf(exn:articleV1, exn:article)
- </pre>
- </div>
- <div class="provxml example">
- <div class="exampleheader">
- <span class="exampleheader"><b>XML Example</b>
- <a onclick="
- set_display_by_class('pre', 'provxml example', 'none');
- set_display_by_class('div', 'provxml example', 'none');
- set_display_by_id('hide-provxml-examples', 'none');
- set_display_by_id('show-provxml-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> <prov:document>
- ...
- <prov:entity prov:id="exn:articleV1"/>
- <prov:specializationOf>
- <prov:specificEntity prov:ref="exn:articleV1"/>
- <prov:generalEntity prov:ref="exn:article"/>
- </prov:specializationOf>
- </prov:document>
- </pre>
- </div>
- <p>
- Later, after the data set is corrected and the new chart generated, a new version
- of the article is created, <code>exn:articleV2</code>, with its own URI where the article
- is redirected to. To ensure that those
- consulting the provenance of <code>exn:articleV2</code> understand that it
- is connected with the provenance of <code>exn:article</code> and <code>exn:articleV1</code>,
- the newspaper describes how these entities are related.
- </p>
- <div class="turtle example">
- <div class="exampleheader">
- <span class="exampleheader"><b>Turtle Example</b>
- <a onclick="
- set_display_by_class('pre', 'turtle example', 'none');
- set_display_by_class('div', 'turtle example', 'none');
- set_display_by_id('hide-turtle-examples', 'none');
- set_display_by_id('show-turtle-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> exn:articleV2 prov:specializationOf exn:article .
- exn:articleV2 prov:alternateOf exn:articleV1
- </pre>
- </div>
- <div class="provn example">
- <div class="exampleheader">
- <span class="exampleheader"><b>PROV-N Example</b>
- <a onclick="
- set_display_by_class('pre', 'provn example', 'none');
- set_display_by_class('div', 'provn example', 'none');
- set_display_by_id('hide-provn-examples', 'none');
- set_display_by_id('show-provn-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> specializationOf(exn:articleV2, exn:article)
- alternateOf(exn:articleV2, exn:articleV1)
- </pre>
- </div>
- <div class="provxml example">
- <div class="exampleheader">
- <span class="exampleheader"><b>XML Example</b>
- <a onclick="
- set_display_by_class('pre', 'provxml example', 'none');
- set_display_by_class('div', 'provxml example', 'none');
- set_display_by_id('hide-provxml-examples', 'none');
- set_display_by_id('show-provxml-examples', '');"><u><i>(hide all)</i></u></a>
- </span></div>
- <pre> <prov:document>
- ...
- <prov:specializationOf>
- <prov:specificEntity prov:ref="exn:articleV2"/>
- <prov:generalEntity prov:ref="exn:article"/>
- </prov:specializationOf>
- <prov:alternateOf>
- <prov:alternate1 prov:ref="exn:articleV1"/>
- <prov:alternate2 prov:ref="exn:articleV2"/>
- </prov:alternateOf>
- </prov:document>
- </pre>
- </div>
- <p>
- Note that above we could have also
- stated that <code>exn:articleV2</code> was a revision of <code>exn:articleV1</code>,
- as we did between <code>exc:chart2</code> and <code>exc:chart1</code>,
- which would describe more concretely how the alternate entities are related.
- Specialization and alternate relations connect entities, and so are visualized
- as links between them.
- </p>
- <img src="images/specialization.png" alt="Specialization and alternate links between entities">
- </section>
-
- <section id="the-complete-example">
- <h3><span class="secno">3.10 </span>The Complete Example</h3>
- <p>
- The full set of examples shown above are available in <a href="primer-turtle-examples.ttl">PROV-O Turtle format</a>
- or <a href="primer-provn-examples.provn">PROV-N format</a> or <a href="primer-prov-xml-examples.xml">PROV-XML format</a>.
- We visualize the whole example below.
- </p>
- <img src="images/everything.png" alt="Provenance graph for whole example">
- </section>
- </section>
- <section id="summary">
- <!--OddPage--><h2><span class="secno">4. </span>Summary</h2>
- <p>The examples in the previous section highlight the following important capabilities of PROV:
- </p>
- <ol>
- <li><b>Representing diverse entities involved in provenance</b>.
- The examples illustrate that provenance records can contain different
- kinds of information:
- <ul>
- <li>The newspaper took an object-centered view on their provenance statements,
- stating what objects were derived from others but not stating what processes
- were used or what entities were involved.</li>
- <li>Betty the blogger took a very agent-centered view on provenance.
- She chose to associate her blog post with herself, the government agency
- that published the data, and the newspaper that published the article.</li>
- <li>Derek took a process-centered perspective and combined it with object-centered
- and agent-centered provenance information. The processes followed to derive the
- charts from the government datasets were clearly. All intermediate and final
- documents were stated. His involvement in the various activities was clearly
- recorded, and the resulting documents were attributed to him.</li>
- </ul></li>
- <li><b>Stating partial or incomplete provenance</b>. The newspaper omitted
- information about their specific editorial processes in publishing articles.
- The chart generator said nothing about the software used, therefore omitting
- information about other agents involved in the processes.</li>
- <li><b>Integrating provenance-related information represented in other vocabularies</b>.
- The FOAF vocabulary was used for specifying details about Derek and his company.
- The Dublin Core vocabulary was used for specifying the article title. </li>
- <li><b>Combining distributed provenance records provided by different parties</b>.
- The provenance records described in this example came from a government source,
- a newspaper, a company, and a blogger. Using URIs and namespaces, a provenance
- record can draw from multiple sources on the Web.</li>
- <li><b>Describing the commonalities in the derivation of two entities</b>.
- The two versions of the charts were both derived through a similar compile activity.</li>
- <li><b>Relating versions of objects over time</b>.
- The second dataset was described as a revision of the first one.</li>
- <li><b>Stating the provenance of provenance assertions</b>.
- Betty could create a provenance record for her blog post, and
- then assert the provenance of that provenance record.</li>
- <li><b>Enabling alternative accounts for the provenance of an entity</b>.
- The blog post could have a provenance account from Betty as its author and another
- one from the newspaper that the blog quoted from.</li>
- <li><b>Supporting queries over provenance of different granularity</b>.
- The activity of composing the data from different regions was described
- in greater detail than the other steps to produce the chart.
- The provenance of the chart has much finer-grained detail than
- the provenance of the government dataset.</li>
- <li><b>Supporting reasoning and inference over provenance records</b>.
- The provenance assertions explicitly stated above can be used to infer
- additional assertions that are true according to the PROV model.
- For example, because Derek created the chart acting on behalf of Chart
- Generators, a PROV inference may be that the chart can be attributed to Chart Generators.</li>
- </ol>
- <p>The examples also illustrate how PROV enables many uses of provenance,
- such as checking for possible errors, tracking down parties responsible for
- fixing them, repeating processes to re-generate datasets, relating versions of
- documents over time, and inspecting sources and attribution.
- </p>
-
- <p>There are additional aspects of the PROV data model that we have not covered
- in this primer and that are important in many uses of provenance. These include
- the following.
- </p>
- <ol>
- <li><b>Provenance of provenance</b>:
- It is often useful to state the provenance of a provenance record.
- To enable this, PROV allows the grouping of provenance assertions as a <i>bundle</i>.
- A bundle is a type of entity, and therefore its provenance can be asserted in turn.
- For example, supposed that Betty wanted to express in the provenance of her blog
- entry that she personally checked her sources. She would want to state the
- provenance of her blog entry, and then state that she stands by that provenance.
- To do this, she would create a bundle that contains provenance assertions for
- her blog entry, and then she would state that she was the creator of that bundle. </li>
- <li><b>Collections of entities</b>:
- A <i>collection</i> in PROV is a type of entity that has other entities as members.
- For example, Derek could decide to create several types of charts using dataset2.
- He would describe all the charts as a collection, and then state the provenance of
- the collection to be a single step that generates all the charts. </li>
- </ol>
- <p>
- Please see the [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>] specification for details on these
- and other concepts.
- </p>
-</section>
-
-<section class="appendix" id="acknowledgements">
- <!--OddPage--><h2><span class="secno">A. </span>Acknowledgements</h2>
- <p>
- This document has been produced by the Provenance Working Group, and its contents reflect extensive discussion within the Working Group as a whole. The editors extend special thanks to Sandro Hawke (<abbr title="World Wide Web Consortium">W3C</abbr>/<abbr title="Massachusetts Institute of Technology">MIT</abbr>) and Ivan Herman (<abbr title="World Wide Web Consortium">W3C</abbr>/<abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr>), <abbr title="World Wide Web Consortium">W3C</abbr> contacts for the Provenance Working Group.
- </p>
- <p>
- The editors acknowledge valuable contributions from the following:
- Tom Baker,
- David Booth,
- Bob DuCharme,
- Robert Freimuth,
- Satrajit Ghosh,
- Ralph Hodgson,
- Renato Iannella,
- Jacek Kopecky,
- James Leigh,
- Chuck Morris,
- Jacco van Ossenbruggen,
- Alan Ruttenberg,
- Reza Samavi, and
- Antoine Zimmermann.
- </p>
- <p>
- Members of the Provenance Working Group at the time of publication of this document were:
-
- Ilkay Altintas (Invited expert),
- Reza B'Far (Oracle Corporation),
- Khalid Belhajjame (University of Manchester),
- James Cheney (University of Edinburgh, School of Informatics),
- Sam Coppens (iMinds - Ghent University),
- David Corsar (University of Aberdeen, Computing Science),
- Stephen Cresswell (The National Archives),
- Tom De Nies (iMinds - Ghent University),
- Helena Deus (DERI Galway at the National University of Ireland, Galway, Ireland),
- Simon Dobson (Invited expert),
- Martin Doerr (Foundation for Research and Technology - Hellas(FORTH)),
- Kai Eckert (Invited expert),
- Jean-Pierre EVAIN (European Broadcasting Union, EBU-UER),
- James Frew (Invited expert),
- Irini Fundulaki (Foundation for Research and Technology - Hellas(FORTH)),
- Daniel Garijo (Universidad Politécnica de Madrid),
- Yolanda Gil (Invited expert),
- Ryan Golden (Oracle Corporation),
- Paul Groth (Vrije Universiteit),
- Olaf Hartig (Invited expert),
- David Hau (National Cancer Institute, NCI),
- Sandro Hawke (<abbr title="World Wide Web Consortium">W3C</abbr>/<abbr title="Massachusetts Institute of Technology">MIT</abbr>),
- Jörn Hees (German Research Center for Artificial Intelligence (DFKI) Gmbh),
- Ivan Herman, (<abbr title="World Wide Web Consortium">W3C</abbr>/<abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr>),
- Ralph Hodgson (TopQuadrant),
- Hook Hua (Invited expert),
- Trung Dong Huynh (University of Southampton),
- Graham Klyne (University of Oxford),
- Michael Lang (Revelytix, Inc.),
- Timothy Lebo (Rensselaer Polytechnic Institute),
- James McCusker (Rensselaer Polytechnic Institute),
- Deborah McGuinness (Rensselaer Polytechnic Institute),
- Simon Miles (Invited expert),
- Paolo Missier (School of Computing Science, Newcastle university),
- Luc Moreau (University of Southampton),
- James Myers (Rensselaer Polytechnic Institute),
- Vinh Nguyen (Wright State University),
- Edoardo Pignotti (University of Aberdeen, Computing Science),
- Paulo da Silva Pinheiro (Rensselaer Polytechnic Institute),
- Carl Reed (Open Geospatial Consortium),
- Adam Retter (Invited Expert),
- Christine Runnegar (Invited expert),
- Satya Sahoo (Invited expert),
- David Schaengold (Revelytix, Inc.),
- Daniel Schutzer (FSTC, Financial Services Technology Consortium),
- Yogesh Simmhan (Invited expert),
- Stian Soiland-Reyes (University of Manchester),
- Eric Stephan (Pacific Northwest National Laboratory),
- Linda Stewart (The National Archives),
- Ed Summers (Library of Congress),
- Maria Theodoridou (Foundation for Research and Technology - Hellas(FORTH)),
- Ted Thibodeau (OpenLink Software Inc.),
- Curt Tilmes (National Aeronautics and Space Administration),
- Craig Trim (IBM Corporation),
- Stephan Zednik (Rensselaer Polytechnic Institute),
- Jun Zhao (University of Oxford),
- Yuting Zhao (University of Aberdeen, Computing Science).
-</p></section>
-
-<section class="appendix" id="changes-since-fourth-public-working-draft">
- <!--OddPage--><h2><span class="secno">B. </span>Changes Since Fourth Public Working Draft</h2>
- <ul>
- <li>Corrected XML example for activities</li>
- <li>Clarified usage of adoptedOnBehalfOf relation</li>
- <li>Clarified wasQuotedFrom example</li>
- <li>Adapted PROV-XML examples to clarify they are not RDF/XML</li>
- <li>Clarified varying sources of example provenance data with different namespace prefixes,
- and in division of complete example provenance graph</li>
- <li>Used instance-specific identifiers for entities, activities and agents</li>
- <li>Added section summarising some additional aspects of PROV not covered in depth</li>
- <li>Added summary section</li>
- <li>Added proper acknowledgements</li>
- <li>Clarified the introduction regarding what is in each section.</li>
- <li>Added references for FOAF, Dublin Core and newer PROV documents.</li>
- <li>Typos fixed and minor clarifications throughout</li>
- </ul>
-</section>
-
-
-<section id="references" class="appendix"><!--OddPage--><h2><span class="secno">C. </span>References</h2><section id="informative-references"><h3><span class="secno">C.1 </span>Informative references</h3><dl class="bibliography"><dt id="bib-DCTERMS">[DCTERMS]</dt><dd>Dublin Core Metadata Initiative. <a href="http://dublincore.org/documents/2012/06/14/dcmi-terms/"><cite>DCMI Metadata Terms</cite></a>. 14 June 2012. URL: <a href="http://dublincore.org/documents/2012/06/14/dcmi-terms/">http://dublincore.org/documents/2012/06/14/dcmi-terms/</a>
-</dd><dt id="bib-FOAF">[FOAF]</dt><dd>Dan Brickley, Libby Miller; eds. <a href="http://xmlns.com/foaf/spec/20100809.html"><cite>FOAF Vocabulary Specification 0.98</cite></a>. 9 August 2010. URL: <a href="http://xmlns.com/foaf/spec/20100809.html">http://xmlns.com/foaf/spec/20100809.html</a>
-</dd><dt id="bib-PROV-AQ">[PROV-AQ]</dt><dd>Graham Klyne; Paul Groth; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/"><cite>Provenance Access and Query</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/">http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/</a>
-</dd><dt id="bib-PROV-CONSTRAINTS">[PROV-CONSTRAINTS]</dt><dd>James Cheney; Paolo Missier; Luc Moreau; eds. <a href="http://www.w3.org/TR/2013/REC-prov-constraints-20130430/"><cite>Constraints of the PROV Data Model</cite></a>. 30 April 2013, W3C Recommendation. URL: <a href="http://www.w3.org/TR/2013/REC-prov-constraints-20130430/">http://www.w3.org/TR/2013/REC-prov-constraints-20130430/</a>
-</dd><dt id="bib-PROV-DC">[PROV-DC]</dt><dd>Daniel Garijo; Kai Eckert; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/"><cite>Dublin Core to PROV Mapping</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/">http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/</a>
-</dd><dt id="bib-PROV-DICTIONARY">[PROV-DICTIONARY]</dt><dd>Tom De Nies; Sam Coppens; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><cite>PROV Dictionary</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/</a>
-</dd><dt id="bib-PROV-DM">[PROV-DM]</dt><dd>Luc Moreau; Paolo Missier; eds. <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/"><cite>PROV-DM: The PROV Data Model</cite></a>. 30 April 2013, W3C Recommendation. URL: <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/">http://www.w3.org/TR/2013/REC-prov-dm-20130430/</a>
-</dd><dt id="bib-PROV-LINKS">[PROV-LINKS]</dt><dd>Luc Moreau; Timothy Lebo; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-links-20130430/"><cite>Linking Across Provenance Bundles</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-links-20130430/">http://www.w3.org/TR/2013/NOTE-prov-links-20130430/</a>
-</dd><dt id="bib-PROV-N">[PROV-N]</dt><dd>Luc Moreau; Paolo Missier; eds. <a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/"><cite>PROV-N: The Provenance Notation</cite></a>. 30 April 2013, W3C Recommendation. URL: <a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/">http://www.w3.org/TR/2013/REC-prov-n-20130430/</a>
-</dd><dt id="bib-PROV-O">[PROV-O]</dt><dd>Timothy Lebo; Satya Sahoo; Deborah McGuinness; eds. <a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/"><cite>PROV-O: The PROV Ontology</cite></a>. 30 April 2013, W3C Recommendation. URL: <a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/">http://www.w3.org/TR/2013/REC-prov-o-20130430/</a>
-</dd><dt id="bib-PROV-OVERVIEW">[PROV-OVERVIEW]</dt><dd>Paul Groth; Luc Moreau; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/"><cite>PROV-OVERVIEW: An Overview of the PROV Family of Documents</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/">http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/</a>
-</dd><dt id="bib-PROV-SEM">[PROV-SEM]</dt><dd>James Cheney; ed. <a href="http://www.w3.org/TR/2013/NOTE-prov-sem-20130430"><cite>Semantics of the PROV Data Model</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-sem-20130430">http://www.w3.org/TR/2013/NOTE-prov-sem-20130430</a>.
-</dd><dt id="bib-PROV-XML">[PROV-XML]</dt><dd>Hook Hua; Curt Tilmes; Stephan Zednik; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/"><cite>PROV-XML: The PROV XML Schema</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/">http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/</a>
-</dd><dt id="bib-PROVENANCE-XG">[PROVENANCE-XG]</dt><dd>Yolanda Gil, James Cheney, Paul Groth, Olaf Hartig, Simon Miles, Luc Moreau, Paulo Pinheiro da Silva. <a href="http://www.w3.org/2005/Incubator/prov/XGR-prov-20101214/"><cite>Provenance XG Final Report</cite></a>. 8 December 2010. URL: <a href="http://www.w3.org/2005/Incubator/prov/XGR-prov-20101214/">http://www.w3.org/2005/Incubator/prov/XGR-prov-20101214/</a>
-</dd><dt id="bib-TURTLE">[TURTLE]</dt><dd>Eric Prud'hommeaux, Gavin Carothers; eds. <a href="http://www.w3.org/TR/2011/WD-turtle-20110809/"><cite>Turtle: Terse RDF Triple Language</cite></a>. 9 August 2011. W3C Working Draft. URL: <a href="http://www.w3.org/TR/2011/WD-turtle-20110809/">http://www.w3.org/TR/2011/WD-turtle-20110809/</a>
+<!DOCTYPE html>
+<html lang="en" dir="ltr">
+<head>
+ <title>PROV Model Primer</title>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+ <link rel="http://www.w3.org/ns/prov#has_provenance" href="http://www.w3.org/2011/prov/provenance/prov-primer">
+ <!--
+ === NOTA BENE ===
+ For the three scripts below, if your spec resides on dev.w3 you can check them
+ out in the same tree and use relative links so that they'll work offline,
+ -->
+ <!-- PM -->
+ <style type="text/css">
+ .note { font-size:small; margin-left:50px }
+ </style>
+
+ <script src="toggles.js" type="text/javascript"></script>
+
+
+
+
+
+ <style>/*****************************************************************
+ * ReSpec 3 CSS
+ * Robin Berjon - http://berjon.com/
+ *****************************************************************/
+
+/* --- INLINES --- */
+em.rfc2119 {
+ text-transform: lowercase;
+ font-variant: small-caps;
+ font-style: normal;
+ color: #900;
+}
+
+h1 acronym, h2 acronym, h3 acronym, h4 acronym, h5 acronym, h6 acronym, a acronym,
+h1 abbr, h2 abbr, h3 abbr, h4 abbr, h5 abbr, h6 abbr, a abbr {
+ border: none;
+}
+
+dfn {
+ font-weight: bold;
+}
+
+a.internalDFN {
+ color: inherit;
+ border-bottom: 1px solid #99c;
+ text-decoration: none;
+}
+
+a.externalDFN {
+ color: inherit;
+ border-bottom: 1px dotted #ccc;
+ text-decoration: none;
+}
+
+a.bibref {
+ text-decoration: none;
+}
+
+cite .bibref {
+ font-style: normal;
+}
+
+code {
+ color: #ff4500;
+}
+
+/* --- TOC --- */
+.toc a, .tof a {
+ text-decoration: none;
+}
+
+a .secno, a .figno {
+ color: #000;
+}
+
+ul.tof, ol.tof {
+ list-style: none outside none;
+}
+
+.caption {
+ margin-top: 0.5em;
+ font-style: italic;
+}
+
+/* --- TABLE --- */
+table.simple {
+ border-spacing: 0;
+ border-collapse: collapse;
+ border-bottom: 3px solid #005a9c;
+}
+
+.simple th {
+ background: #005a9c;
+ color: #fff;
+ padding: 3px 5px;
+ text-align: left;
+}
+
+.simple th[scope="row"] {
+ background: inherit;
+ color: inherit;
+ border-top: 1px solid #ddd;
+}
+
+.simple td {
+ padding: 3px 10px;
+ border-top: 1px solid #ddd;
+}
+
+.simple tr:nth-child(even) {
+ background: #f0f6ff;
+}
+
+/* --- DL --- */
+.section dd > p:first-child {
+ margin-top: 0;
+}
+
+.section dd > p:last-child {
+ margin-bottom: 0;
+}
+
+.section dd {
+ margin-bottom: 1em;
+}
+
+.section dl.attrs dd, .section dl.eldef dd {
+ margin-bottom: 0;
+}
+</style><link rel="stylesheet" href="http://www.w3.org/StyleSheets/TR/W3C-WG-NOTE"><!--[if lt IE 9]><script src='http://www.w3.org/2008/site/js/html5shiv.js'></script><![endif]--><!--[if lt IE 9]><script src='http://www.w3.org/2008/site/js/html5shiv.js'></script><![endif]--></head>
+ <body><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">PROV Model Primer</h1>
+
+ <h2 id="w3c-working-group-note-30-april-2013"><abbr title="World Wide Web Consortium">W3C</abbr> Working Group Note 30 April 2013</h2>
+ <dl>
+
+ <dt>This version:</dt>
+ <dd><a href="http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/">http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/</a></dd>
+ <dt>Latest published version:</dt>
+ <dd><a href="http://www.w3.org/TR/prov-primer/">http://www.w3.org/TR/prov-primer/</a></dd>
+
+
+
+
+
+
+ <dt>Previous version:</dt>
+ <dd><a href="http://www.w3.org/TR/2013/WD-prov-primer-20130312/">http://www.w3.org/TR/2013/WD-prov-primer-20130312/</a></dd>
+
+
+ <dt>Editors:</dt>
+ <dd><a href="http://www.isi.edu/~gil/">Yolanda Gil</a>, Information Sciences Institute, University of Southern California, US</dd>
+<dd><a href="http://www.inf.kcl.ac.uk/staff/simonm/">Simon Miles</a>, King's College London, UK</dd>
+
+
+ <dt>Contributors:</dt>
+ <dd><span><a href="http://semanticweb.org/wiki/Khalid_Belhajjame">Khalid Belhajjame</a></span>, University of Manchester</dd>
+<dd><span>Helena Deus</span>, Digital Enterprise Research Institute (DERI), NUI Galway</dd>
+<dd><span><a href="http://www.oeg-upm.net/index.php/en/phdstudents/28-dgarijo">Daniel Garijo</a></span>, Ontology Engineering Group, Universidad Politécnica de Madrid, Spain</dd>
+<dd><span>Graham Klyne</span>, University of Oxford</dd>
+<dd><span><a href="http://www.ncl.ac.uk/computing/people/profile/Paolo.Missier">Paolo Missier</a></span>, Newcastle University</dd>
+<dd><span><a href="http://soiland-reyes.com/stian/">Stian Soiland-Reyes</a></span>, University of Manchester</dd>
+<dd><span><a href="http://tw.rpi.edu/web/person/StephanZednik">Stephan Zednik</a></span>, Rensselaer Polytechnic Institute</dd>
+
+
+ </dl>
+
+
+
+
+
+ <p class="copyright">
+ <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> ©
+ 2013
+
+ <a href="http://www.w3.org/"><abbr title="World Wide Web Consortium">W3C</abbr></a><sup>®</sup>
+ (<a href="http://www.csail.mit.edu/"><abbr title="Massachusetts Institute of Technology">MIT</abbr></a>,
+ <a href="http://www.ercim.eu/"><abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr></a>,
+ <a href="http://www.keio.ac.jp/">Keio</a>, <a href="http://ev.buaa.edu.cn/">Beihang</a>), All Rights Reserved.
+ <abbr title="World Wide Web Consortium">W3C</abbr> <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>,
+ <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and
+ <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.
+ </p>
+
+
+ <hr>
+</div>
+ <section id="abstract" class="introductory"><h2>Abstract</h2>
+ <p>
+ This document provides an intuitive introduction and guide to the
+ PROV Data Model for provenance interchange on the web. PROV defines a core data model for
+ provenance for building representations of the entities, people and
+ processes involved in producing a piece of data or thing in the world.
+ This primer explains the fundamental PROV concepts and provides examples
+ of its use. The primer is intended as a starting point for those wishing
+ to create or use PROV data.
+ </p>
+ <p>
+ The <a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/">PROV Document Overview</a> describes the overall state of PROV, and should be read before other PROV documents.
+ </p>
+
+ <!-- p>
+ This is a document for internal discussion, which will ultimately
+ evolve in the first Public Working Draft of the Primer.</p -->
+ </section><section id="sotd" class="introductory"><h2>Status of This Document</h2>
+
+
+
+ <p>
+ <em>This section describes the status of this document at the time of its publication. Other
+ documents may supersede this document. A list of current <abbr title="World Wide Web Consortium">W3C</abbr> publications and the latest revision
+ of this technical report can be found in the <a href="http://www.w3.org/TR/"><abbr title="World Wide Web Consortium">W3C</abbr> technical reports
+ index</a> at http://www.w3.org/TR/.</em>
+ </p>
+
+ <h4 id="prov-family-of-documents">PROV Family of Documents</h4>
+ This document is part of the PROV family of documents, a set of documents defining various aspects that are necessary to achieve the vision of inter-operable
+ interchange of provenance information in heterogeneous environments such as the Web. These documents are listed below. Please consult the [<cite><a class="bibref" href="#bib-PROV-OVERVIEW">PROV-OVERVIEW</a></cite>] for a guide to reading these documents.
+ <ul>
+ <li> <a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/">PROV-OVERVIEW</a> (Note), an overview of the PROV family of documents [<cite><a class="bibref" href="#bib-PROV-OVERVIEW">PROV-OVERVIEW</a></cite>];</li>
+ <li> <a href="http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/">PROV-PRIMER</a> (Note), a primer for the PROV data model (this document);</li>
+ <li> <a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/">PROV-O</a> (Recommendation), the PROV ontology, an OWL2 ontology allowing the mapping of the PROV data model to RDF [<cite><a class="bibref" href="#bib-PROV-O">PROV-O</a></cite>];</li>
+ <li> <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/">PROV-DM</a> (Recommendation), the PROV data model for provenance [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>];</li>
+ <li> <a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/">PROV-N</a> (Recommendation), a notation for provenance aimed at human consumption [<cite><a class="bibref" href="#bib-PROV-N">PROV-N</a></cite>];</li>
+ <li> <a href="http://www.w3.org/TR/2013/REC-prov-constraints-20130430/">PROV-CONSTRAINTS</a> (Recommendation), a set of constraints applying to the PROV data model [<cite><a class="bibref" href="#bib-PROV-CONSTRAINTS">PROV-CONSTRAINTS</a></cite>];</li>
+ <li> <a href="http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/">PROV-XML</a> (Note), an XML schema for the PROV data model [<cite><a class="bibref" href="#bib-PROV-XML">PROV-XML</a></cite>];</li>
+ <li> <a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/">PROV-AQ</a> (Note), mechanisms for accessing and querying provenance [<cite><a class="bibref" href="#bib-PROV-AQ">PROV-AQ</a></cite>]; </li>
+ <li> <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/">PROV-DICTIONARY</a> (Note) introduces a specific type of collection, consisting of key-entity pairs [<cite><a class="bibref" href="#bib-PROV-DICTIONARY">PROV-DICTIONARY</a></cite>];</li>
+ <li> <a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/">PROV-DC</a> (Note) provides a mapping between PROV-O and Dublin Core Terms [<cite><a class="bibref" href="#bib-PROV-DC">PROV-DC</a></cite>];</li>
+ <li> <a href="http://www.w3.org/TR/2013/NOTE-prov-sem-20130430/">PROV-SEM</a> (Note), a declarative specification in terms of first-order logic of the PROV data model [<cite><a class="bibref" href="#bib-PROV-SEM">PROV-SEM</a></cite>];</li>
+ <li> <a href="http://www.w3.org/TR/2013/NOTE-prov-links-20130430/">PROV-LINKS</a> (Note) introduces a mechanism to link across bundles [<cite><a class="bibref" href="#bib-PROV-LINKS">PROV-LINKS</a></cite>].</li>
+ </ul>
+
+ <h4 id="implementations-encouraged">Implementations Encouraged</h4>
+ <p>
+ The Provenance Working Group encourages implementation of the material defined in this document.
+ Although work on this document by the Provenance Working Group is complete,
+ errors may be recorded in the <a href="http://www.w3.org/2011/prov/errata.html">errata</a> or and these may be addressed in future revisions.
+ </p>
+
+ <h4 id="please-send-comments">Please Send Comments</h4>
+
+
+ <p>
+ This document was published by the <a href="http://www.w3.org/2011/prov/">Provenance Working Group</a> as a Working Group Note.
+
+
+ If you wish to make comments regarding this document, please send them to
+ <a href="mailto:public-prov-comments@w3.org">public-prov-comments@w3.org</a>
+ (<a href="mailto:public-prov-comments-request@w3.org?subject=subscribe">subscribe</a>,
+ <a href="http://lists.w3.org/Archives/Public/public-prov-comments/">archives</a>).
+
+
+
+
+ All comments are welcome.
+
+
+ </p><p>
+ Publication as a Working Group Note does not imply endorsement by the <abbr title="World Wide Web Consortium">W3C</abbr> Membership.
+ This is a draft document and may be updated, replaced or obsoleted by other documents at
+ any time. It is inappropriate to cite this document as other than work in progress.
+ </p>
+
+
+ <p>
+
+ This document was produced by a group operating under the
+ <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 <abbr title="World Wide Web Consortium">W3C</abbr> Patent Policy</a>.
+
+
+
+
+ <abbr title="World Wide Web Consortium">W3C</abbr> maintains a <a href="http://www.w3.org/2004/01/pp-impl/46974/status" rel="disclosure">public list of any patent disclosures</a>
+
+ made in connection with the deliverables of the group; that page also includes instructions for
+ disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains
+ <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential Claim(s)</a> must disclose the
+ information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section
+ 6 of the <abbr title="World Wide Web Consortium">W3C</abbr> Patent Policy</a>.
+
+
+ </p>
+
+
+
+
+</section><section id="toc"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a href="#introduction" class="tocxref"><span class="secno">1. </span>Introduction</a></li><li class="tocline"><a href="#intuitive-overview-of-prov" class="tocxref"><span class="secno">2. </span>Intuitive overview of PROV</a><ul class="toc"><li class="tocline"><a href="#entities" class="tocxref"><span class="secno">2.1 </span>Entities</a></li><li class="tocline"><a href="#activities" class="tocxref"><span class="secno">2.2 </span>Activities</a></li><li class="tocline"><a href="#usage-and-generation" class="tocxref"><span class="secno">2.3 </span>Usage and Generation</a></li><li class="tocline"><a href="#agents-and-responsibility" class="tocxref"><span class="secno">2.4 </span>Agents and Responsibility</a></li><li class="tocline"><a href="#roles" class="tocxref"><span class="secno">2.5 </span>Roles</a></li><li class="tocline"><a href="#derivation-and-revision" class="tocxref"><span class="secno">2.6 </span>Derivation and Revision</a></li><li class="tocline"><a href="#plans" class="tocxref"><span class="secno">2.7 </span>Plans</a></li><li class="tocline"><a href="#time" class="tocxref"><span class="secno">2.8 </span>Time</a></li><li class="tocline"><a href="#alternate-entities-and-specialization" class="tocxref"><span class="secno">2.9 </span>Alternate Entities and Specialization</a></li></ul></li><li class="tocline"><a href="#examples-of-key-concepts-in-prov" class="tocxref"><span class="secno">3. </span>Examples of Key Concepts in PROV</a><ul class="toc"><li class="tocline"><a href="#entities-1" class="tocxref"><span class="secno">3.1 </span>Entities</a></li><li class="tocline"><a href="#activities-1" class="tocxref"><span class="secno">3.2 </span>Activities</a></li><li class="tocline"><a href="#usage-and-generation-1" class="tocxref"><span class="secno">3.3 </span>Usage and Generation</a></li><li class="tocline"><a href="#agents-and-responsibility-1" class="tocxref"><span class="secno">3.4 </span>Agents and Responsibility</a></li><li class="tocline"><a href="#roles-1" class="tocxref"><span class="secno">3.5 </span>Roles</a></li><li class="tocline"><a href="#derivation-and-revision-1" class="tocxref"><span class="secno">3.6 </span>Derivation and Revision</a></li><li class="tocline"><a href="#plans-1" class="tocxref"><span class="secno">3.7 </span>Plans</a></li><li class="tocline"><a href="#time-1" class="tocxref"><span class="secno">3.8 </span>Time</a></li><li class="tocline"><a href="#alternate-entities-and-specialization-1" class="tocxref"><span class="secno">3.9 </span>Alternate Entities and Specialization</a></li><li class="tocline"><a href="#the-complete-example" class="tocxref"><span class="secno">3.10 </span>The Complete Example</a></li></ul></li><li class="tocline"><a href="#summary" class="tocxref"><span class="secno">4. </span>Summary</a></li><li class="tocline"><a href="#acknowledgements" class="tocxref"><span class="secno">A. </span>Acknowledgements</a></li><li class="tocline"><a href="#changes-since-fourth-public-working-draft" class="tocxref"><span class="secno">B. </span>Changes Since Fourth Public Working Draft</a></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">C. </span>References</a><ul class="toc"><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">C.1 </span>Informative references</a></li></ul></li></ul></section>
+
+
+
+ <section id="introduction">
+ <!--OddPage--><h2><span class="secno">1. </span>Introduction</h2>
+ <p>
+ This primer document provides an accessible introduction to the PROV
+ data model for provenance interchange on the Web.
+ The <i>provenance</i> of digital objects represents their origins. PROV is a
+ specification to express provenance records,
+ which contain <i>descriptions</i> of the entities
+ and activities involved in producing and delivering or otherwise influencing a
+ given object.
+ Provenance can be used for many purposes, such as
+ understanding how data was collected so it can be meaningfully used, determining
+ ownership and rights over an object, making judgements about information to
+ determine whether to trust it, verifying that the process and steps used to obtain a
+ result complies with given requirements, and reproducing how something was generated.
+ </p>
+
+ <p>
+ As a specification for provenance, PROV accommodates all those different uses
+ of provenance. Different people may have different perspectives on provenance,
+ and as a result different types of information might be captured in provenance records.
+ </p><ul>
+ <li>
+ One perspective might focus on <i>agent-centered provenance</i>, that is, what people or organizations
+ were involved in generating or manipulating the information in question. For example,
+ in the provenance of a picture in a news article we might capture the photographer who
+ took it, the person that edited it, and the newspaper that published it.
+ </li>
+ <li>
+ A second perspective
+ might focus on <i>object-centered provenance</i>, by tracing the origins of portions of a
+ document to other documents. An example is having a web page that was assembled from content
+ from a news article, quotes of interviews with experts, and a chart that plots data from a
+ government agency.
+ </li>
+ <li>A third perspective one might take is on <i>process-centered provenance</i>,
+ capturing the actions and steps taken to generate the information in question. For example, a
+ chart may have been generated by invoking a service to retrieve data from a database, then
+ extracting certain statistics from the data using some statistics package, and finally
+ processing these results with a graphing tool.
+ </li>
+ </ul>
+ <p></p>
+
+ <p>
+ Provenance records are metadata. There are other kinds of metadata that are
+ not provenance. For example, the size of an image is metadata of
+ that image but it is not provenance.
+ For general background on provenance, a
+ comprehensive overview of requirements, use cases, prior research, and proposed
+ vocabularies for provenance are available from the
+ Final Report of the <abbr title="World Wide Web Consortium">W3C</abbr> Provenance Incubator Group [<cite><a class="bibref" href="#bib-PROVENANCE-XG">PROVENANCE-XG</a></cite>].
+ That document contains three general scenarios
+ that may help identify the provenance aspects of planned applications and
+ help plan the design of a provenance system.
+ </p>
+
+ <p>
+ This primer document aims to ease the adoption of the PROV specifications by providing:
+ </p>
+ <ul>
+ <li>A high-level explanation of how PROV models provenance, in Section 2. A detailed description of
+ all the concepts and relations in the PROV Data Model is provided in [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>].</li>
+ <li>A simple self-contained example that illustrates how to produce and use PROV assertions, in
+ Section 3.
+ The example includes snippets in RDF using the PROV ontology [<cite><a class="bibref" href="#bib-PROV-O">PROV-O</a></cite>], in a
+ notation designed for human consumption [<cite><a class="bibref" href="#bib-PROV-N">PROV-N</a></cite>], and in PROV's XML format [<cite><a class="bibref" href="#bib-PROV-XML">PROV-XML</a></cite>].
+ The example shows how
+ to combine PROV with other popular vocabularies such as FOAF [<cite><a class="bibref" href="#bib-FOAF">FOAF</a></cite>] and Dublin Core [<cite><a class="bibref" href="#bib-DCTERMS">DCTERMS</a></cite>].</li>
+ </ul>
+
+ <p>The document ends with a summary of major capabilities and features of PROV.</p>
+
+ </section>
+
+ <section id="intuitive-overview-of-prov">
+ <!--OddPage--><h2><span class="secno">2. </span>Intuitive overview of PROV</h2>
+
+ <p>
+ This section provides an explanation of the main concepts in PROV.
+ As with the rest of this document, it should be treated as a starting point for
+ understanding the model. The PROV data model document [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>]
+ provides precise definitions and constraints [<cite><a class="bibref" href="#bib-PROV-CONSTRAINTS">PROV-CONSTRAINTS</a></cite>] to be followed.
+ </p>
+ <p>
+ The following diagram provides a high level overview of the structure of PROV records,
+ limited to some key PROV concepts discussed in this document.
+ Note that because PROV is meant to describe how things were created or delivered,
+ PROV relations are named so they can be used in assertions about the past.
+ </p>
+
+ <div style="text-align: center;">
+ <img src="images/key-concepts.png" alt="PROV key concepts overview">
+ </div>
+
+ <section id="entities">
+ <h3><span class="secno">2.1 </span>Entities</h3>
+
+ <p>
+ In PROV, physical, digital, conceptual, or other kinds of thing are called
+ <i>entities</i>.
+ Examples of such entities are a web page, a chart, and a spellchecker.
+ Provenance records can describe the provenance of entities, and
+ an entity’s provenance may refer to many other entities. For example, a document D is
+ an entity whose provenance refers to other entities such as a chart inserted into D,
+ and the dataset that was used to create that chart.
+ Entities may be described as having different attributes and
+ be described from different perspectives. For example,
+ document D as stored in my file system, the second version of document D,
+ and D as an evolving document,
+ are three distinct entities for which we may describe provenance.
+ </p>
+ </section>
+
+ <section id="activities">
+ <h3><span class="secno">2.2 </span>Activities</h3>
+
+ <p>
+ <i>Activities</i> are how entities come into
+ existence and how their attributes change to become new entities,
+ often making use of previously existing entities to achieve this.
+ They are
+ dynamic aspects of the world, such as actions, processes, etc.
+ For example, if the second version of document D was generated
+ by a translation from the first version of the document in another language,
+ then this translation is an activity.
+ </p>
+ </section>
+
+ <section id="usage-and-generation">
+ <h3><span class="secno">2.3 </span>Usage and Generation</h3>
+ <p>
+ Activities <i>generate</i> new entities.
+ For example, writing a document brings the document into existence, while
+ revising the document brings a new version into existence.
+ Activities also make <i>use</i> of entities. For example, revising a document
+ to fix spelling mistakes uses the original version of the document as well
+ as a list of corrections.
+ Generation does not always occur at the end of an activity, and an activity may generate entities
+ part-way through.
+ Likewise, usage does not always occur at the beginning of an activity.
+ </p>
+ </section>
+
+ <section id="agents-and-responsibility">
+ <h3><span class="secno">2.4 </span>Agents and Responsibility</h3>
+ <p>
+ An <i>agent</i> takes a role in an activity such
+ that the agent can be assigned some degree of responsibility for the activity taking
+ place.
+ An agent can be a person, a piece of software, an inanimate object, an organization, or
+ other entities that may be ascribed responsibility.
+ When an agent has some responsibility for an activity, PROV says the agent was
+ <i>associated</i> with the activity, where several agents may be associated with
+ an activity and vice-versa.
+ Consider a chart displaying some statistics
+ regarding crime rates over time in a linear regression. To represent the
+ provenance of that chart, we could state that the person who created the
+ chart was an agent involved in its creation, and that the software used to
+ create the chart was also an agent involved in that activity.
+ An agent may be <i>acting on behalf</i> of others, e.g. an employee on behalf of their
+ organization, and we can express such chains of responsibility in the provenance.
+ </p>
+ <p>
+ We can also describe that an entity is <i>attributed</i> to an agent to express
+ the agent's responsibility for that entity, possibly along with other agents.
+ This description can be understood as a shorthand
+ for saying that the agent was responsible for the activity which generated
+ the entity.
+ </p>
+ <p>
+ One may want to describe the provenance of an agent. For example, an organization
+ responsible for the creation of a report may evolve over time as the report is written as
+ some members leave and others join. To make provenance assertions about an agent in PROV,
+ the agent must be declared explicitly both as an agent and as an entity.
+ </p>
+
+ </section>
+
+ <section id="roles">
+ <h3><span class="secno">2.5 </span>Roles</h3>
+ <p>
+ A <i>role</i> is a description of the function or the part that an entity
+ played in an activity. Roles specify
+ the relationship between an entity and an activity, i.e. how
+ the activity used or generated the entity. Roles also specify how agents are
+ involved in an activity, qualifying their participation in the activity or
+ specifying for what aspect of it each agent was responsible.
+ For example, an agent may play the role of "editor" in an activity that uses
+ one entity in the role of "document to be edited" and another in the role of
+ "addition to be made to the document", to generate a further entity in the role of "edited document".
+ Roles are application specific, so PROV does not define any particular roles.
+ </p>
+ </section>
+
+ <section id="derivation-and-revision">
+ <h3><span class="secno">2.6 </span>Derivation and Revision</h3>
+ <p>
+ When one entity's existence, content, characteristics and so on are
+ at least partly due to another entity, then we say that the former was
+ <i>derived</i> from the latter. For example, one document may contain
+ material copied from another,
+ and a chart was derived from the data that it illustrates.
+ </p>
+ <p>
+ PROV allows some common, specialized kinds of derivation to be described.
+ For example, a given entity, such as a document, may go through multiple <i>revisions</i>
+ over time. Between revisions,
+ one or more attributes of the entity may change.
+ In PROV, the result of each revision is a new entity.
+ PROV allows one to relate those entities by making a description that
+ one was a revision of another.
+ Another kind of derivation is to say that one entity, a quotation, <i>was quoted from</i>
+ another entity, commonly a document.
+ </p>
+ </section>
+
+ <section id="plans">
+ <h3><span class="secno">2.7 </span>Plans</h3>
+ <p>
+ Activities may follow pre-defined procedures, such as recipes, tutorials, instructions, or workflows.
+ PROV refers to these, in general, as <i>plans</i>, and allows the description that a plan was followed, by agents,
+ in executing an activity.
+ </p>
+ </section>
+
+ <section id="time">
+ <h3><span class="secno">2.8 </span>Time</h3>
+ <p>
+ Time is often a critical aspect of provenance.
+ PROV allows the timing of significant events to be described, including
+ when an entity was generated or used, or when an activity started
+ and finished. For example, the model can be used to describe facts such as when a new
+ version of a document was created (generation time), or when a document was
+ edited (start and end of the editing activity).
+ </p>
+ </section>
+
+ <section id="alternate-entities-and-specialization">
+ <h3><span class="secno">2.9 </span>Alternate Entities and Specialization</h3>
+ <p>
+ There is often more than one way to describe something in a record of
+ provenance. Each perspective will be referred to by a separately identified
+ entity, and PROV provides a mechanism for linking the different descriptions of
+ the same thing together through the mechanism of <i>specialization</i>. One
+ entity is a specialization of another entity if it shares the same fixed attributes,
+ with the possible addition of further fixed attributes. This concept is best
+ illustrated through a few use cases.
+ </p>
+ <p>
+ Entities can be mutable things. For example, a webpage is a single
+ entity, W, despite being edited over time. Each version of the webpage is
+ also an entity, W1, W2... To connect an individual version to the webpage
+ in general, we say that the former is a specialization of the latter: W1 is a
+ specialization of W, W2 is a specialization of W, and so on.
+ </p>
+ <p>
+ Two individuals may create provenance referring to the same thing from different
+ perspectives. For example, the author of an article may attribute that article
+ to themselves using PROV while, independently, a reader might quote a fact from that
+ article elsewhere and document this in PROV. If the author later changes the fact,
+ then from the reader's perspective there are now two versions of the article, and
+ the reader had quoted from the version before the change. From the author's perspective,
+ there is a single article, attributed to the author. If the author, the reader, or a
+ third party, were to connect the two PROV records, that party would say that the
+ article as referred to by the reader is a specialization of the same article
+ as referred to by the author.
+ </p>
+ <p>
+ The above illustrates where we may want to connect entities by
+ saying that they refer to the same thing, but at different levels of specialization.
+ PROV also allows us to more generally draw a connection between two descriptions
+ of the same thing, even if not at different levels of specialization, describing the
+ entities as <i>alternates</i> of each other. For example,
+ two versions of the webpage above, W1 and W2, are alternates of each other because
+ they describe the same webpage.
+ </p>
+ <p>
+ As another example, if a file is copied from one directory to another to create a backup,
+ we may say that the copies are alternate versions of the same, location-independent, file.
+ Specifically, we may say that the file in the first directory, entity F1, is an alternate of the
+ file in the second directory, entity F2. Note that it is
+ the context (location) rather than content of the file that differs between the entities
+ in this case.
+ </p>
+ </section>
+
+ </section>
+
+ <section id="examples-of-key-concepts-in-prov">
+ <!--OddPage--><h2><span class="secno">3. </span>Examples of Key Concepts in PROV</h2>
+
+ <p>
+ In the following sections, we show how PROV can be used to model
+ provenance in a specific example scenario. Samples of PROV data are given.
+ These samples use the namespace prefixes <b>prov</b>, denoting
+ terms from the PROV ontology, and prefixes <b>exc</b>, <b>exn</b>, <b>exb</b>, <b>exg</b>,
+ denoting terms specific to the example.
+ We illustrate in these examples how PROV can be used in combination with other
+ languages, such as FOAF [<cite><a class="bibref" href="#bib-FOAF">FOAF</a></cite>] and Dublin Core [<cite><a class="bibref" href="#bib-DCTERMS">DCTERMS</a></cite>] (with namespace prefix <b>foaf</b> and
+ <b>dcterms</b> respectively).
+ </p>
+ <p>
+ The scenario describes a blogger exploring the provenance of an online newspaper
+ article, including a chart produced from a government agency dataset. The
+ provenance data comes from different sources: the blogger, the newspaper,
+ the chart generator company and the government agency. The samples of provenance from each source
+ use a different namespace prefix for identifiers that source has
+ created: <b>exb</b>, <b>exn</b>, <b>exc</b>, and <b>exg</b>
+ respectively.
+ </p>
+ <p>
+ The samples can be displayed in one or more of the following formats.
+ </p>
+ <ul>
+ <li>[<cite><a class="bibref" href="#bib-PROV-O">PROV-O</a></cite>] RDF triples, expressed using the [<cite><a class="bibref" href="#bib-TURTLE">TURTLE</a></cite>] notation.</li>
+ <li>[<cite><a class="bibref" href="#bib-PROV-N">PROV-N</a></cite>] expressions.</li>
+ <li>[<cite><a class="bibref" href="#bib-PROV-XML">PROV-XML</a></cite>] fragments.</li>
+ </ul>
+ <p>
+ Select the formats to display using the buttons below. Note that if all formats
+ are hidden, the worked examples may not make sense!
+ </p>
+ <form action="#"><p>
+ <input id="hide-turtle-examples" type="button" value="Hide Turtle Examples" onclick="
+ set_display_by_class('pre', 'turtle example', 'none');
+ set_display_by_class('div', 'turtle example', 'none');
+ set_display_by_id('hide-turtle-examples', 'none');
+ set_display_by_id('show-turtle-examples', '');">
+ <input id="show-turtle-examples" type="button" value="Show Turtle Examples" style="display:none" onclick="
+ set_display_by_class('pre', 'turtle example', '');
+ set_display_by_class('div', 'turtle example', '');
+ set_display_by_id('hide-turtle-examples', '');
+ set_display_by_id('show-turtle-examples', 'none');">
+ <input id="hide-provn-examples" type="button" value="Hide PROV-N Examples" onclick="
+ set_display_by_class('pre', 'provn example', 'none');
+ set_display_by_class('div', 'provn example', 'none');
+ set_display_by_id('hide-provn-examples', 'none');
+ set_display_by_id('show-provn-examples', '');">
+ <input id="show-provn-examples" type="button" value="Show PROV-N Examples" style="display:none" onclick="
+ set_display_by_class('pre', 'provn example', '');
+ set_display_by_class('div', 'provn example', '');
+ set_display_by_id('hide-provn-examples', '');
+ set_display_by_id('show-provn-examples', 'none');">
+ <input id="hide-provxml-examples" type="button" value="Hide XML Examples" onclick="
+ set_display_by_class('pre', 'provxml example', 'none');
+ set_display_by_class('div', 'provxml example', 'none');
+ set_display_by_id('hide-provxml-examples', 'none');
+ set_display_by_id('show-provxml-examples', '');">
+ <input id="show-provxml-examples" type="button" value="Show XML Examples" style="display:none" onclick="
+ set_display_by_class('pre', 'provxml example', '');
+ set_display_by_class('div', 'provxml example', '');
+ set_display_by_id('hide-provxml-examples', '');
+ set_display_by_id('show-provxml-examples', 'none');">
+ </p>
+ </form>
+
+
+ <section id="entities-1">
+ <h3><span class="secno">3.1 </span>Entities</h3>
+
+ <p>
+ An online newspaper publishes an article with a chart about crime statistics
+ based on data (GovData) provided by a government portal.
+ The article includes a chart based on the data, with data values composed (aggregated) by
+ geographical regions.
+ </p>
+ <p>
+ A blogger, Betty, looking at the article, spots what she thinks to be an error in the chart.
+ Betty retrieves a record of the provenance of the article, describing how it was created.
+ </p>
+ <p>Betty finds the following descriptions of entities in the provenance.</p>
+ <div class="turtle example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>Turtle Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'turtle example', 'none');
+ set_display_by_class('div', 'turtle example', 'none');
+ set_display_by_id('hide-turtle-examples', 'none');
+ set_display_by_id('show-turtle-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> exn:article a prov:Entity ;
+ dcterms:title "Crime rises in cities" .
+ exg:dataset1 a prov:Entity .
+ exc:regionList a prov:Entity .
+ exc:composition1 a prov:Entity .
+ exc:chart1 a prov:Entity .
+ </pre>
+ </div>
+ <div class="provn example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>PROV-N Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'provn example', 'none');
+ set_display_by_class('div', 'provn example', 'none');
+ set_display_by_id('hide-provn-examples', 'none');
+ set_display_by_id('show-provn-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> entity(exn:article, [dcterms:title="Crime rises in cities"])
+ entity(exg:dataset1)
+ entity(exc:regionList)
+ entity(exc:composition1)
+ entity(exc:chart1)
+ </pre>
+ </div>
+ <div class="provxml example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>XML Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'provxml example', 'none');
+ set_display_by_class('div', 'provxml example', 'none');
+ set_display_by_id('hide-provxml-examples', 'none');
+ set_display_by_id('show-provxml-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> <prov:document>
+ ...
+ <prov:entity prov:id="exn:article">
+ <dct:title>Crime rises in cities</dct:title>
+ </prov:entity>
+ <prov:entity prov:id="exg:dataset1"/>
+ <prov:entity prov:id="exc:regionList1"/>
+ <prov:entity prov:id="exc:composition1"/>
+ <prov:entity prov:id="exc:chart1"/>
+ </prov:document>
+ </pre>
+ </div>
+ <p>
+ These statements, in order, refer to the article
+ (<code>exn:article</code>),
+ an original data set (<code>exg:dataset1</code>),
+ a list of regions (<code>exc:regionList</code>),
+ data aggregated by region (<code>exc:composition1</code>),
+ and a chart (<code>exc:chart1</code>), and state that each is an entity.
+ Any entity may have attributes, such as the title
+ of the article, expressed using <code>dcterms:title</code> above.
+ </p>
+ <p>
+ Notice the different namespace prefixes used: for the article it corresponds to the
+ newspaper that published it (<code>exn</code>), and
+ for the dataset it is the government namespace (<code>exg</code>).
+ The <code>dcterms:title</code> namespace is taken from the Dublin Core
+ vocabulary.
+ </p>
+ <p>
+ PROV data is commonly visualized for human consumption using <a href="http://www.w3.org/2011/prov/wiki/Diagrams">particular conventions</a>,
+ which we will introduce over the following sections. To start with, entities
+ are denoted using ovals, as shown below.
+ </p>
+ <img src="images/entities.png" alt="Visualization of the example entities">
+ </section>
+
+ <section id="activities-1">
+ <h3><span class="secno">3.2 </span>Activities</h3>
+
+ <p>
+ Further, the provenance describes that there was
+ an activity (<code>exc:compile1</code>) denoting the compilation of the
+ chart from the data set.
+ </p>
+ <div class="turtle example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>Turtle Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'turtle example', 'none');
+ set_display_by_class('div', 'turtle example', 'none');
+ set_display_by_id('hide-turtle-examples', 'none');
+ set_display_by_id('show-turtle-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> exc:compile1 a prov:Activity .
+ </pre>
+ </div>
+ <div class="provn example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>PROV-N Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'provn example', 'none');
+ set_display_by_class('div', 'provn example', 'none');
+ set_display_by_id('hide-provn-examples', 'none');
+ set_display_by_id('show-provn-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> activity(exc:compile1)
+ </pre>
+ </div>
+ <div class="provxml example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>XML Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'provxml example', 'none');
+ set_display_by_class('div', 'provxml example', 'none');
+ set_display_by_id('hide-provxml-examples', 'none');
+ set_display_by_id('show-provxml-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> <prov:document>
+ ...
+ <prov:activity prov:id="exc:compile1"/>
+ </prov:document>
+ </pre>
+ </div>
+ <p>
+ The provenance also includes reference to the more specific steps involved in this compilation,
+ which are first composing the data by region (<code>exc:compose1</code>) and then generating the
+ chart graphic (<code>exc:illustrate1</code>).
+ </p>
+ <div class="turtle example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>Turtle Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'turtle example', 'none');
+ set_display_by_class('div', 'turtle example', 'none');
+ set_display_by_id('hide-turtle-examples', 'none');
+ set_display_by_id('show-turtle-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> exc:compose1 a prov:Activity .
+ exc:illustrate1 a prov:Activity .
+ </pre>
+ </div>
+ <div class="provn example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>PROV-N Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'provn example', 'none');
+ set_display_by_class('div', 'provn example', 'none');
+ set_display_by_id('hide-provn-examples', 'none');
+ set_display_by_id('show-provn-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> activity(exc:compose1)
+ activity(exc:illustrate1)
+ </pre>
+ </div>
+ <div class="provxml example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>XML Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'provxml example', 'none');
+ set_display_by_class('div', 'provxml example', 'none');
+ set_display_by_id('hide-provxml-examples', 'none');
+ set_display_by_id('show-provxml-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> <prov:document>
+ ...
+ <prov:activity prov:id="exc:compose1"/>
+ <prov:activity prov:id="exc:illustrate1"/>
+ </prov:document>
+ </pre>
+ </div>
+ <p>
+ In visualizations of the PROV data, activities are depicted as rectangles, as below.
+ </p>
+ <img src="images/activities.png" alt="Visualization of the example activities">
+ </section>
+
+ <section id="usage-and-generation-1">
+ <h3><span class="secno">3.3 </span>Usage and Generation</h3>
+
+ <p>
+ Concluding the basic description of what occurred, the provenance
+ describes the key relations among the above
+ entities and activities, i.e. the usage of an entity by an activity,
+ or the generation of an entity by an activity.
+ </p>
+ <p>
+ For example, the descriptions below state that the composition activity
+ (<code>exc:compose1</code>) used the original data set, that it used the list of
+ regions, and that the composed data was generated by this activity.
+ </p>
+ <div class="turtle example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>Turtle Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'turtle example', 'none');
+ set_display_by_class('div', 'turtle example', 'none');
+ set_display_by_id('hide-turtle-examples', 'none');
+ set_display_by_id('show-turtle-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> exc:compose1 prov:used exg:dataset1 ;
+ prov:used exc:regionList1 .
+ exc:composition1 prov:wasGeneratedBy exc:compose1 .
+ </pre>
+ </div>
+ <div class="provn example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>PROV-N Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'provn example', 'none');
+ set_display_by_class('div', 'provn example', 'none');
+ set_display_by_id('hide-provn-examples', 'none');
+ set_display_by_id('show-provn-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> used(exc:compose1, exg:dataset1, -)
+ used(exc:compose1, exc:regionList1, -)
+ wasGeneratedBy(exc:composition1, exc:compose1, -)
+ </pre>
+ <p>Note that the - argument in the examples above denote unspecified optional
+ information. See the [<cite><a class="bibref" href="#bib-PROV-N">PROV-N</a></cite>] specification for the details of what arguments
+ may be expressed in each PROV-N statement.
+ </p>
+ </div>
+ <div class="provxml example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>XML Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'provxml example', 'none');
+ set_display_by_class('div', 'provxml example', 'none');
+ set_display_by_id('hide-provxml-examples', 'none');
+ set_display_by_id('show-provxml-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> <prov:document>
+ ...
+ <prov:used>
+ <prov:activity prov:ref="exc:compose1"/>
+ <prov:entity prov:ref="exg:dataset1"/>
+ </prov:used>
+ <prov:used>
+ <prov:activity prov:ref="exc:compose1"/>
+ <prov:entity prov:ref="exc:regionList1"/>
+ </prov:used>
+ <prov:wasGeneratedBy>
+ <prov:entity prov:ref="exc:composition1"/>
+ <prov:activity prov:ref="exc:compose1"/>
+ </prov:wasGeneratedBy>
+ </prov:document>
+ </pre>
+ </div>
+ <p>
+ Similarly, the chart graphic creation activity (<code>exc:illustrate1</code>)
+ used the composed data, and the chart was generated by this activity.
+ </p>
+ <div class="turtle example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>Turtle Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'turtle example', 'none');
+ set_display_by_class('div', 'turtle example', 'none');
+ set_display_by_id('hide-turtle-examples', 'none');
+ set_display_by_id('show-turtle-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> exc:illustrate1 prov:used exc:composition1 .
+ exc:chart1 prov:wasGeneratedBy exc:illustrate1 .
+ </pre>
+ </div>
+ <div class="provn example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>PROV-N Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'provn example', 'none');
+ set_display_by_class('div', 'provn example', 'none');
+ set_display_by_id('hide-provn-examples', 'none');
+ set_display_by_id('show-provn-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> used(exc:illustrate1, exc:composition1, -)
+ wasGeneratedBy(exc:chart1, exc:illustrate1, -)
+ </pre>
+ </div>
+ <div class="provxml example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>XML Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'provxml example', 'none');
+ set_display_by_class('div', 'provxml example', 'none');
+ set_display_by_id('hide-provxml-examples', 'none');
+ set_display_by_id('show-provxml-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> <prov:document>
+ ...
+ <prov:used>
+ <prov:activity prov:ref="exc:illustrate1"/>
+ <prov:entity prov:ref="exc:composition1"/>
+ </prov:used>
+ <prov:wasGeneratedBy>
+ <prov:entity prov:ref="exc:chart1"/>
+ <prov:activity prov:ref="exc:illustrate1"/>
+ </prov:wasGeneratedBy>
+ </prov:document>
+ </pre>
+ </div>
+ <p>
+ In visualizing the PROV data, usage and generation are connections between
+ entities and activities. The arrows point from the future to the past.
+ </p>
+ <img src="images/use-generate.png" alt="Connection of the entities and activities by use and generation links">
+ </section>
+
+ <section id="agents-and-responsibility-1">
+ <h3><span class="secno">3.4 </span>Agents and Responsibility</h3>
+
+ <p>
+ Digging deeper, Betty wants to know who compiled the chart.
+ Betty sees that Derek was involved in both the composition and
+ chart creation activities:
+ </p>
+ <div class="turtle example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>Turtle Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'turtle example', 'none');
+ set_display_by_class('div', 'turtle example', 'none');
+ set_display_by_id('hide-turtle-examples', 'none');
+ set_display_by_id('show-turtle-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> exc:compose1 prov:wasAssociatedWith exc:derek .
+ exc:illustrate1 prov:wasAssociatedWith exc:derek .
+ </pre>
+ </div>
+ <div class="provn example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>PROV-N Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'provn example', 'none');
+ set_display_by_class('div', 'provn example', 'none');
+ set_display_by_id('hide-provn-examples', 'none');
+ set_display_by_id('show-provn-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> wasAssociatedWith(exc:compose1, exc:derek, -)
+ wasAssociatedWith(exc:illustrate1, exc:derek, -)
+ </pre>
+ </div>
+ <div class="provxml example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>XML Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'provxml example', 'none');
+ set_display_by_class('div', 'provxml example', 'none');
+ set_display_by_id('hide-provxml-examples', 'none');
+ set_display_by_id('show-provxml-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> <prov:document>
+ ...
+ <prov:wasAssociatedWith>
+ <prov:activity prov:ref="exc:compose1"/>
+ <prov:agent prov:ref="exc:derek"/>
+ </prov:wasAssociatedWith>
+ <prov:wasAssociatedWith>
+ <prov:activity prov:ref="exc:illustrate1"/>
+ <prov:agent prov:ref="exc:derek"/>
+ </prov:wasAssociatedWith>
+ </prov:document>
+ </pre>
+ </div>
+ <p>
+ The record for Derek provides the
+ following description that
+ Derek is an agent, specifically a person, followed by non-PROV information
+ giving attributes of Derek.
+ </p>
+ <div class="turtle example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>Turtle Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'turtle example', 'none');
+ set_display_by_class('div', 'turtle example', 'none');
+ set_display_by_id('hide-turtle-examples', 'none');
+ set_display_by_id('show-turtle-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> exc:derek a prov:Agent ;
+ a prov:Person ;
+ foaf:givenName "Derek"^^xsd:string ;
+ foaf:mbox <mailto:derek@example.org> .
+ </pre>
+ </div>
+ <div class="provn example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>PROV-N Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'provn example', 'none');
+ set_display_by_class('div', 'provn example', 'none');
+ set_display_by_id('hide-provn-examples', 'none');
+ set_display_by_id('show-provn-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> agent(exc:derek,
+ [prov:type='prov:Person', foaf:givenName="Derek",
+ foaf:mbox="<mailto:derek@example.org>"])
+ </pre>
+ </div>
+ <div class="provxml example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>XML Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'provxml example', 'none');
+ set_display_by_class('div', 'provxml example', 'none');
+ set_display_by_id('hide-provxml-examples', 'none');
+ set_display_by_id('show-provxml-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> <prov:document>
+ ...
+ <prov:agent prov:id="exc:derek">
+ <prov:type>prov:Person</prov:type>
+ <foaf:givenName>Derek</foaf:givenName>
+ <foaf:mbox>mailto:derek@example.org</foaf:mbox>
+ </prov:agent>
+ </prov:document>
+ </pre>
+ </div>
+ <p>
+ Derek works as part of an organization, Chart Generators Inc, and so the provenance
+ declares that he acts on their behalf. Note that the organization is itself
+ an agent. The namespace prefix used by the organization is <code>exc</code>.
+ </p>
+ <div class="turtle example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>Turtle Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'turtle example', 'none');
+ set_display_by_class('div', 'turtle example', 'none');
+ set_display_by_id('hide-turtle-examples', 'none');
+ set_display_by_id('show-turtle-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> exc:derek prov:actedOnBehalfOf exc:chartgen .
+ exc:chartgen a prov:Agent ;
+ a prov:Organization ;
+ foaf:name "Chart Generators Inc" .
+ </pre>
+ </div>
+ <div class="provn example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>PROV-N Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'provn example', 'none');
+ set_display_by_class('div', 'provn example', 'none');
+ set_display_by_id('hide-provn-examples', 'none');
+ set_display_by_id('show-provn-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> agent(exc:chartgen,
+ [prov:type='prov:Organization',
+ foaf:name="Chart Generators Inc"])
+ actedOnBehalfOf(exc:derek, exc:chartgen)
+ </pre>
+ </div>
+ <div class="provxml example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>XML Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'provxml example', 'none');
+ set_display_by_class('div', 'provxml example', 'none');
+ set_display_by_id('hide-provxml-examples', 'none');
+ set_display_by_id('show-provxml-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> <prov:document>
+ ...
+ <prov:agent prov:id="exc:chartgen">
+ <prov:type>prov:Organization</prov:type>
+ <foaf:name>Chart Generators Inc</foaf:name>
+ </prov:agent>
+ <prov:actedOnBehalfOf>
+ <prov:delegate prov:ref="exc:derek"/>
+ <prov:responsible prov:ref="exc:chartgen"/>
+ </prov:actedOnBehalfOf>
+ </prov:document>
+ </pre>
+ </div>
+ <p>
+ It would also be possible to express the more specific statement that Derek
+ worked on the organization's behalf for a particular activity, rather than
+ in general, and so may have acted on behalf of other organizations for other
+ activities. See the PROV specifications for details on how to express
+ activity-specific delegation.
+ </p>
+ <p>
+ Finally, there is an explicit statement in the provenance that the chart was
+ attributed to Derek.
+ </p>
+ <div class="turtle example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>Turtle Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'turtle example', 'none');
+ set_display_by_class('div', 'turtle example', 'none');
+ set_display_by_id('hide-turtle-examples', 'none');
+ set_display_by_id('show-turtle-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> exc:chart1 prov:wasAttributedTo exc:derek .
+ </pre>
+ </div>
+ <div class="provn example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>PROV-N Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'provn example', 'none');
+ set_display_by_class('div', 'provn example', 'none');
+ set_display_by_id('hide-provn-examples', 'none');
+ set_display_by_id('show-provn-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> wasAttributedTo(exc:chart1, exc:derek)
+ </pre>
+ </div>
+ <div class="provxml example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>XML Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'provxml example', 'none');
+ set_display_by_class('div', 'provxml example', 'none');
+ set_display_by_id('hide-provxml-examples', 'none');
+ set_display_by_id('show-provxml-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> <prov:document>
+ ...
+ <prov:wasAttributedTo>
+ <prov:entity prov:ref="exc:chart1"/>
+ <prov:agent prov:ref="exc:derek"/>
+ </prov:wasAttributedTo>
+ </prov:document>
+ </pre>
+ </div>
+
+ <p>
+ We can extend our graphical depiction to show the agents, association and attribution links.
+ </p>
+ <img src="images/agents.png" alt="Agents added to provenance graph and linked to entities and activities">
+ </section>
+
+ <section id="roles-1">
+ <h3><span class="secno">3.5 </span>Roles</h3>
+
+ <p>
+ For Betty to understand where the error lies, she needs to have more detailed
+ information on how entities have been used in and generated
+ by activities. Betty has determined that <code>exc:compose1</code> used
+ entities <code>exc:regionList1</code> and <code>exg:dataset1</code>, but she does not
+ know what function these entities played in the processing. Betty
+ also knows that <code>exc:derek</code> was associated with the activities, but she does
+ not know if Derek was the analyst responsible for determining how the data
+ should be composed.
+ </p>
+ <p>
+ The above information is described as roles in the provenance. The composition
+ activity involved entities in four roles: the data to be composed (<code>exc:dataToCompose</code>),
+ the regions to aggregate by (<code>exc:regionsToAggregateBy</code>), the
+ resulting composed data (<code>exc:composedData</code>), and the
+ analyst doing the composition (<code>exc:analyst</code>).
+ </p>
+ <div class="turtle example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>Turtle Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'turtle example', 'none');
+ set_display_by_class('div', 'turtle example', 'none');
+ set_display_by_id('hide-turtle-examples', 'none');
+ set_display_by_id('show-turtle-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> exc:dataToCompose a prov:Role .
+ exc:regionsToAggregateBy a prov:Role .
+ exc:composedData a prov:Role .
+ exc:analyst a prov:Role .
+ </pre>
+ <p>
+ Examples in the sections above show descriptions of the simple facts that the
+ composition activity used, generated and was enacted by entities/agents.
+ For example, the usage of the data set by the compose activity is expressed
+ as follows.
+ </p>
+ <div class="exampleheader">
+ <span class="exampleheader"><b>Turtle Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'turtle example', 'none');
+ set_display_by_class('div', 'turtle example', 'none');
+ set_display_by_id('hide-turtle-examples', 'none');
+ set_display_by_id('show-turtle-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> exc:compose1 prov:used exg:dataset1 .
+ </pre>
+ <p>
+ The
+ provenance can contain more details of exactly how these entities and agents
+ were involved in the activity.
+ To express this, PROV-O refers to <i>qualified usage</i>, <i>qualified generation</i>, etc.,
+ which are descriptions consisting of several statements about how usage, generation, etc. took place.
+ For example, we may describe the plan followed by an agent in performing an activity, or
+ the time at which an activity generated an entity, both illustrated later.
+ Another example of qualified involvement is the role an entity played in an activity.
+ The descriptions below state
+ that the composition activity (<code>exc:compose1</code>) included the usage
+ of the government data set (<code>exg:dataset1</code>) in the role of the data
+ to be composed (<code>exc:dataToCompose</code>).
+ </p>
+ <div class="exampleheader">
+ <span class="exampleheader"><b>Turtle Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'turtle example', 'none');
+ set_display_by_class('div', 'turtle example', 'none');
+ set_display_by_id('hide-turtle-examples', 'none');
+ set_display_by_id('show-turtle-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> exc:compose1 prov:qualifiedUsage [
+ a prov:Usage ;
+ prov:entity exg:dataset1 ;
+ prov:hadRole exc:dataToCompose
+ ] .
+ </pre>
+ </div>
+ <div class="provn example">
+ <p>
+ In PROV-N, the role is expressed as one of the list of attributes in the used
+ expression, with the attribute name <code>prov:role</code>.
+ </p>
+ <div class="exampleheader">
+ <span class="exampleheader"><b>PROV-N Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'provn example', 'none');
+ set_display_by_class('div', 'provn example', 'none');
+ set_display_by_id('hide-provn-examples', 'none');
+ set_display_by_id('show-provn-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> used(exc:compose1, exg:dataset1, -, [prov:role='exc:dataToCompose'])
+ </pre>
+ </div>
+ <div class="provxml example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>XML Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'provxml example', 'none');
+ set_display_by_class('div', 'provxml example', 'none');
+ set_display_by_id('hide-provxml-examples', 'none');
+ set_display_by_id('show-provxml-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> <prov:document>
+ ...
+ <prov:used>
+ <prov:activity prov:ref="exc:compose1"/>
+ <prov:entity prov:ref="exg:dataset1"/>
+ <prov:role>exc:dataToCompose</prov:role>
+ </prov:used>
+ </prov:document>
+ </pre>
+ </div>
+ <p>
+ This can then be distinguished from the same activity's usage of the list of
+ regions because the roles played are different.
+ </p>
+ <div class="turtle example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>Turtle Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'turtle example', 'none');
+ set_display_by_class('div', 'turtle example', 'none');
+ set_display_by_id('hide-turtle-examples', 'none');
+ set_display_by_id('show-turtle-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> exc:compose1 prov:qualifiedUsage [
+ a prov:Usage ;
+ prov:entity exc:regionList1 ;
+ prov:hadRole exc:regionsToAggregateBy
+ ] .
+ </pre>
+ </div>
+ <div class="provn example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>PROV-N Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'provn example', 'none');
+ set_display_by_class('div', 'provn example', 'none');
+ set_display_by_id('hide-provn-examples', 'none');
+ set_display_by_id('show-provn-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> used(exc:compose1, exc:regionList1, -, [prov:role='exc:regionsToAggregateBy'])
+ </pre>
+ </div>
+ <div class="provxml example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>XML Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'provxml example', 'none');
+ set_display_by_class('div', 'provxml example', 'none');
+ set_display_by_id('hide-provxml-examples', 'none');
+ set_display_by_id('show-provxml-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> <prov:document>
+ ...
+ <prov:used>
+ <prov:activity prov:ref="exc:compose1"/>
+ <prov:entity prov:ref="exc:regionList1"/>
+ <prov:role>exc:regionsToAggregateBy</prov:role>
+ </prov:used>
+ </prov:document>
+ </pre>
+ </div>
+ <p>
+ Similarly, the provenance includes descriptions that the same activity was
+ enacted in a particular way by Derek, so it indicates that he had the role of
+ <code>exc:analyst</code>, and that the entity <code>exc:composition1</code> took the role of the composed
+ data in what the activity generated:
+ </p>
+ <div class="turtle example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>Turtle Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'turtle example', 'none');
+ set_display_by_class('div', 'turtle example', 'none');
+ set_display_by_id('hide-turtle-examples', 'none');
+ set_display_by_id('show-turtle-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> exc:compose1 prov:qualifiedAssociation [
+ a prov:Association ;
+ prov:agent exc:derek ;
+ prov:hadRole exc:analyst
+ ] .
+ exc:composition1 prov:qualifiedGeneration [
+ a prov:Generation ;
+ prov:activity exc:compose1 ;
+ prov:hadRole exc:composedData
+ ] .
+ </pre>
+ </div>
+ <div class="provn example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>PROV-N Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'provn example', 'none');
+ set_display_by_class('div', 'provn example', 'none');
+ set_display_by_id('hide-provn-examples', 'none');
+ set_display_by_id('show-provn-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> wasAssociatedWith(exc:compose1, exc:derek, -, [prov:role='exc:analyst'])
+ wasGeneratedBy(exc:composition1, exc:compose1, -, [prov:role='exc:composedData'])
+ </pre>
+ </div>
+ <div class="provxml example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>XML Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'provxml example', 'none');
+ set_display_by_class('div', 'provxml example', 'none');
+ set_display_by_id('hide-provxml-examples', 'none');
+ set_display_by_id('show-provxml-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> <prov:document>
+ ...
+ <prov:wasAssociatedWith>
+ <prov:activity prov:ref="exc:compose1"/>
+ <prov:agent prov:ref="exc:derek"/>
+ <prov:role>exc:analyst</prov:role>
+ </prov:wasAssociatedWith>
+ <prov:wasGeneratedBy>
+ <prov:entity prov:ref="exc:composition1"/>
+ <prov:activity prov:ref="exc:compose1"/>
+ <prov:role>exc:composedData</prov:role>
+ </prov:wasGeneratedBy>
+ </prov:document>
+ </pre>
+ </div>
+ <p>
+ Depicting the above visually, we have the following.
+ </p>
+ <img src="images/roles.png" alt="Provenance graph annotated with roles played by entities and agents">
+ </section>
+
+ <section id="derivation-and-revision-1">
+ <h3><span class="secno">3.6 </span>Derivation and Revision</h3>
+
+ <p>
+ After looking at the detail of the compilation activity, there appears
+ to be nothing wrong, so Betty concludes the error is in the government dataset.
+ She looks at the dataset <code>exg:dataset1</code>,
+ and sees that it is missing data from one of the zipcodes in the area. She contacts
+ the government agency, and a new version of GovData is created, declared to be the
+ next revision of the data. The provenance of this new dataset,
+ <code>exg:dataset2</code>, states that it is a revision of the
+ old data set, <code>exg:dataset1</code>.
+ </p>
+ <div class="turtle example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>Turtle Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'turtle example', 'none');
+ set_display_by_class('div', 'turtle example', 'none');
+ set_display_by_id('hide-turtle-examples', 'none');
+ set_display_by_id('show-turtle-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> exg:dataset2 a prov:Entity ;
+ prov:wasRevisionOf exg:dataset1 .
+ </pre>
+ </div>
+ <div class="provn example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>PROV-N Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'provn example', 'none');
+ set_display_by_class('div', 'provn example', 'none');
+ set_display_by_id('hide-provn-examples', 'none');
+ set_display_by_id('show-provn-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> entity(exg:dataset2)
+ wasDerivedFrom(exg:dataset2, exg:dataset1, [prov:type='prov:Revision'])
+ </pre>
+ </div>
+ <div class="provxml example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>XML Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'provxml example', 'none');
+ set_display_by_class('div', 'provxml example', 'none');
+ set_display_by_id('hide-provxml-examples', 'none');
+ set_display_by_id('show-provxml-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> <prov:document>
+ ...
+ <entity prov:id="dataSet2"/>
+ <prov:wasDerivedFrom>
+ <prov:generatedEntity prov:ref="exg:dataset2"/>
+ <prov:usedEntity prov:ref="exg:dataset1"/>
+ <prov:type>prov:Revision</prov:type>
+ </prov:wasDerivedFrom>
+ </prov:document>
+ </pre>
+ </div>
+ <p>
+ Derek notices that there is a new dataset available and creates a new chart based on the revised data,
+ using another compilation activity. Betty checks the article again at a
+ later point, and wants to know if it is based on the old or new GovData.
+ She sees a new description stating that the new chart is derived from the new dataset
+ (the same relation could be expressed between the old chart and old dataset).
+ </p>
+ <div class="turtle example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>Turtle Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'turtle example', 'none');
+ set_display_by_class('div', 'turtle example', 'none');
+ set_display_by_id('hide-turtle-examples', 'none');
+ set_display_by_id('show-turtle-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> exc:chart2 a prov:Entity ;
+ prov:wasDerivedFrom exg:dataset2 .
+ </pre>
+ </div>
+ <div class="provn example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>PROV-N Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'provn example', 'none');
+ set_display_by_class('div', 'provn example', 'none');
+ set_display_by_id('hide-provn-examples', 'none');
+ set_display_by_id('show-provn-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> wasDerivedFrom(exc:chart2, exg:dataset2)
+ </pre>
+ </div>
+ <div class="provxml example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>XML Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'provxml example', 'none');
+ set_display_by_class('div', 'provxml example', 'none');
+ set_display_by_id('hide-provxml-examples', 'none');
+ set_display_by_id('show-provxml-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> <prov:document>
+ ...
+ <prov:wasDerivedFrom>
+ <prov:generatedEntity prov:ref="exc:chart2"/>
+ <prov:usedEntity prov:ref="exg:dataset2"/>
+ </prov:wasDerivedFrom>
+ </prov:document>
+ </pre>
+ </div>
+ <p>and that the new chart is a revision of the original one:
+ </p>
+ <div class="turtle example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>Turtle Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'turtle example', 'none');
+ set_display_by_class('div', 'turtle example', 'none');
+ set_display_by_id('hide-turtle-examples', 'none');
+ set_display_by_id('show-turtle-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> exc:chart2 a prov:Entity ;
+ prov:wasRevisionOf exc:chart1 .
+ </pre>
+ </div>
+ <div class="provn example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>PROV-N Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'provn example', 'none');
+ set_display_by_class('div', 'provn example', 'none');
+ set_display_by_id('hide-provn-examples', 'none');
+ set_display_by_id('show-provn-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> entity(exc:chart2)
+ wasDerivedFrom(exc:chart2, exc:chart1, [prov:type='prov:Revision'])
+ </pre>
+ </div>
+ <div class="provxml example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>XML Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'provxml example', 'none');
+ set_display_by_class('div', 'provxml example', 'none');
+ set_display_by_id('hide-provxml-examples', 'none');
+ set_display_by_id('show-provxml-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> <prov:document>
+ ...
+ <entity prov:id="chart2"/>
+ <prov:wasDerivedFrom>
+ <prov:generatedEntity prov:ref="exc:chart2"/>
+ <prov:usedEntity prov:ref="exc:chart1"/>
+ <prov:type>prov:Revision</prov:type>
+ </prov:wasDerivedFrom>
+ </prov:document>
+ </pre>
+ </div>
+ <p>
+ Derivation and revision are connections between entities, and so depicted
+ with arrows in our visualization.
+ </p>
+ <img src="images/derivation.png" alt="Derivation and revision links between entities">
+ </section>
+
+ <section id="plans-1">
+ <h3><span class="secno">3.7 </span>Plans</h3>
+
+ <p>
+ Betty then wishes to know whether the new data set correctly addresses
+ the error that existed before. The provenance of the new dataset,
+ <code>exg:dataset2</code>, describes not only who performed the corrections,
+ Edith, but also what instructions she followed in doing so (in PROV terms, the plan).
+ First, the correction activity (<code>exg:correct1</code>), the person who corrected
+ it, Edith (<code>exg:edith</code>), and the correction instructions (<code>exg:instructions</code>)
+ are described.
+ </p><div class="turtle example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>Turtle Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'turtle example', 'none');
+ set_display_by_class('div', 'turtle example', 'none');
+ set_display_by_id('hide-turtle-examples', 'none');
+ set_display_by_id('show-turtle-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> exg:correct1 a prov:Activity .
+ exg:edith a prov:Agent, prov:Person .
+ exg:instructions a prov:Plan .
+ </pre>
+ </div>
+ <div class="provn example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>PROV-N Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'provn example', 'none');
+ set_display_by_class('div', 'provn example', 'none');
+ set_display_by_id('hide-provn-examples', 'none');
+ set_display_by_id('show-provn-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> activity(exg:correct1)
+ agent(exg:edith, [prov:type='prov:Person'])
+ entity(exg:instructions)
+ </pre>
+ </div>
+ <div class="provxml example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>XML Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'provxml example', 'none');
+ set_display_by_class('div', 'provxml example', 'none');
+ set_display_by_id('hide-provxml-examples', 'none');
+ set_display_by_id('show-provxml-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> <prov:document>
+ ...
+ <prov:activity prov:id="exg:correct1"/>
+ <prov:agent prov:id="exg:edith">
+ <prov:type>prov:Person</prov:type>
+ </prov:agent>
+ <prov:entity prov:id="exg:instructions">
+ <prov:type>prov:Plan</prov:type>
+ </prov:entity>
+ </prov:document>
+ </pre>
+ </div>
+ <div class="turtle example">
+ <p>
+ The connection between them is expressed in PROV-O using a qualified association giving details of
+ how Edith was associated with the correction activity,
+ including that she followed the above correction instructions.
+ </p>
+ <div class="exampleheader">
+ <span class="exampleheader"><b>Turtle Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'turtle example', 'none');
+ set_display_by_class('div', 'turtle example', 'none');
+ set_display_by_id('hide-turtle-examples', 'none');
+ set_display_by_id('show-turtle-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> exg:correct1 prov:qualifiedAssociation [
+ a Association ;
+ prov:agent exg:edith ;
+ prov:hadPlan exg:instructions
+ ] .
+ exg:dataset2 prov:wasGeneratedBy exg:correct1 .
+ </pre>
+ </div>
+ <div class="provn example">
+ <p>
+ In PROV-N, the plan is an optional parameter to wasAssociatedWith descriptions.
+ </p>
+ <div class="exampleheader">
+ <span class="exampleheader"><b>PROV-N Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'provn example', 'none');
+ set_display_by_class('div', 'provn example', 'none');
+ set_display_by_id('hide-provn-examples', 'none');
+ set_display_by_id('show-provn-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> wasAssociatedWith(exg:correct1, exg:edith, exg:instructions)
+ wasGeneratedBy(exg:dataset2, exg:correct1, -)
+ </pre>
+ </div>
+ <div class="provxml example">
+ <p>
+ In PROV-XML, the plan is an optional child of the wasAssociatedWith element.
+ </p>
+ <div class="exampleheader">
+ <span class="exampleheader"><b>XML Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'provxml example', 'none');
+ set_display_by_class('div', 'provxml example', 'none');
+ set_display_by_id('hide-provxml-examples', 'none');
+ set_display_by_id('show-provxml-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> <prov:document>
+ ...
+ <prov:wasAssociatedWith>
+ <prov:activity prov:ref="exg:correct1"/>
+ <prov:agent prov:ref="exg:edith"/>
+ <prov:plan prov:ref="exg:instructions"/>
+ </prov:wasAssociatedWith>
+ <prov:wasGeneratedBy>
+ <prov:entity prov:ref="exg:dataset2"/>
+ <prov:activity prov:ref="exg:correct1"/>
+ </prov:wasGeneratedBy>
+ </prov:document>
+ </pre>
+ </div>
+ <p>
+ Plans are additional information about the connection from an activity to
+ an agent, and so, in our visualization, connect to the link between them.
+ </p>
+ <img src="images/plans.png" alt="Annotaion of example provenance graph with plan followed">
+ </section>
+
+ <section id="time-1">
+ <h3><span class="secno">3.8 </span>Time</h3>
+
+ <p>
+ The government agency that produced GovData is concerned to know how long
+ the incorrect chart was in circulation before the corrected chart was created.
+ That is, they wish to compare the times at which the original and the corrected
+ charts were generated. The snippet below shows that the second chart
+ was generated roughly a month after the first.
+ </p>
+ <div class="turtle example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>Turtle Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'turtle example', 'none');
+ set_display_by_class('div', 'turtle example', 'none');
+ set_display_by_id('hide-turtle-examples', 'none');
+ set_display_by_id('show-turtle-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> exc:chart1 prov:generatedAtTime "2012-03-02T10:30:00"^^xsd:dateTime .
+ exc:chart2 prov:generatedAtTime "2012-04-01T15:21:00"^^xsd:dateTime .
+ </pre>
+ </div>
+ <div class="provn example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>PROV-N Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'provn example', 'none');
+ set_display_by_class('div', 'provn example', 'none');
+ set_display_by_id('hide-provn-examples', 'none');
+ set_display_by_id('show-provn-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> wasGeneratedBy(exc:chart1, exc:compile1, 2012-03-02T10:30:00)
+ wasGeneratedBy(exc:chart2, exc:compile2, 2012-04-01T15:21:00)
+ </pre>
+ </div>
+ <div class="provxml example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>XML Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'provxml example', 'none');
+ set_display_by_class('div', 'provxml example', 'none');
+ set_display_by_id('hide-provxml-examples', 'none');
+ set_display_by_id('show-provxml-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> <prov:document>
+ ...
+ <prov:wasGeneratedBy>
+ <prov:entity prov:ref="exc:chart1"/>
+ <prov:time>2012-03-02T10:30:00</prov:time>
+ </prov:wasGeneratedBy>
+ <prov:wasGeneratedBy>
+ <prov:entity prov:ref="exc:chart2"/>
+ <prov:time>2012-04-01T15:21:00</prov:time>
+ </prov:wasGeneratedBy>
+ </prov:document>
+ </pre>
+ </div>
+
+ <p>
+ To ensure their procedures are efficient, the agency also wishes to know how long the
+ corrections took once the error was discovered. That is, they wish to know the
+ start and end times of the correction activity (<code>exg:correct1</code>).
+ These details are expressed as follows, showing that the corrections took a
+ little over a day.
+ </p>
+ <div class="turtle example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>Turtle Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'turtle example', 'none');
+ set_display_by_class('div', 'turtle example', 'none');
+ set_display_by_id('hide-turtle-examples', 'none');
+ set_display_by_id('show-turtle-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> exg:correct1 prov:startedAtTime "2012-03-31T09:21:00"^^xsd:dateTime ;
+ prov:endedAtTime "2012-04-01T15:21:00"^^xsd:dateTime .
+ </pre>
+ </div>
+ <div class="provn example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>PROV-N Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'provn example', 'none');
+ set_display_by_class('div', 'provn example', 'none');
+ set_display_by_id('hide-provn-examples', 'none');
+ set_display_by_id('show-provn-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> activity(exg:correct1, 2012-03-31T09:21:00, 2012-04-01T15:21:00)
+ </pre>
+ </div>
+ <div class="provxml example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>XML Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'provxml example', 'none');
+ set_display_by_class('div', 'provxml example', 'none');
+ set_display_by_id('hide-provxml-examples', 'none');
+ set_display_by_id('show-provxml-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> <prov:document>
+ ...
+ <prov:activity prov:id="exg:correct1">
+ <prov:startTime>2012-03-31T09:21:00</prov:startTime>
+ <prov:endTime>2012-04-01T15:21:00</prov:endTime>
+ </prov:activity>
+ </prov:document>
+ </pre>
+ </div>
+ <p>
+ Time is visualized as additional information regarding activities or the
+ links between activities and entities or agents.
+ </p>
+ <img src="images/time.png" alt="Annotation of provenance graph with example timestamps">
+ </section>
+
+ <section id="alternate-entities-and-specialization-1">
+ <h3><span class="secno">3.9 </span>Alternate Entities and Specialization</h3>
+
+ <p>
+ Before noticing anything wrong with the government data, Betty had already
+ posted a blog entry about the article. The blog entry had its own published
+ provenance. In particular, it contains some text copied from the article, and the
+ provenance states that this text (<code>exb:quoteInBlogEntry-20130326</code>) is quoted
+ from the article. Note the namespace prefix (<code>exb</code>) used for the blog.
+ </p>
+ <div class="turtle example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>Turtle Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'turtle example', 'none');
+ set_display_by_class('div', 'turtle example', 'none');
+ set_display_by_id('hide-turtle-examples', 'none');
+ set_display_by_id('show-turtle-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> exb:quoteInBlogEntry-20130326 a prov:Entity ;
+ prov:value "Smaller cities have more crime than larger ones" ;
+ prov:wasQuotedFrom exn:article .
+ </pre>
+ </div>
+ <div class="provn example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>PROV-N Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'provn example', 'none');
+ set_display_by_class('div', 'provn example', 'none');
+ set_display_by_id('hide-provn-examples', 'none');
+ set_display_by_id('show-provn-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> entity(exb:quoteInBlogEntry-20130326, prov:value="Smaller cities have more crime than larger ones")
+ wasDerivedFrom(exb:quoteInBlogEntry-20130326, exn:article, [prov:type='prov:Quotation'])
+ </pre>
+ </div>
+ <div class="provxml example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>XML Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'provxml example', 'none');
+ set_display_by_class('div', 'provxml example', 'none');
+ set_display_by_id('hide-provxml-examples', 'none');
+ set_display_by_id('show-provxml-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> <prov:document>
+ ...
+ <prov:entity prov:id="exb:BlogEntry-20130326">
+ <prov:value>Smaller cities have more crime than larger ones</prov:value>
+ </prov:entity>
+ <prov:wasDerivedFrom>
+ <prov:generatedEntity prov:ref="exb:quoteInBlogEntry-20130326"/>
+ <prov:usedEntity prov:ref="exn:article"/>
+ <prov:type>prov:Quotation</prov:type>
+ </prov:wasDerivedFrom>
+ </prov:document>
+ </pre>
+ </div>
+ <p>
+ The newspaper, from past experience, anticipated that there could be revisions
+ to the article, and so created identifiers for both the article in general
+ (<code>exn:article</code>) as a URI that got redirected to the first version of the article (<code>exn:articleV1</code>),
+ allowing both to be referred to as entities in provenance data.
+ In the provenance records, the newspaper describes the connection between the two: that
+ the first version of the article is a specialization of the article in general.
+ </p>
+ <div class="turtle example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>Turtle Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'turtle example', 'none');
+ set_display_by_class('div', 'turtle example', 'none');
+ set_display_by_id('hide-turtle-examples', 'none');
+ set_display_by_id('show-turtle-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> exn:articleV1 a prov:Entity ;
+ prov:specializationOf exn:article .
+ </pre>
+ </div>
+ <div class="provn example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>PROV-N Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'provn example', 'none');
+ set_display_by_class('div', 'provn example', 'none');
+ set_display_by_id('hide-provn-examples', 'none');
+ set_display_by_id('show-provn-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> entity(exn:articleV1)
+ specializationOf(exn:articleV1, exn:article)
+ </pre>
+ </div>
+ <div class="provxml example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>XML Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'provxml example', 'none');
+ set_display_by_class('div', 'provxml example', 'none');
+ set_display_by_id('hide-provxml-examples', 'none');
+ set_display_by_id('show-provxml-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> <prov:document>
+ ...
+ <prov:entity prov:id="exn:articleV1"/>
+ <prov:specializationOf>
+ <prov:specificEntity prov:ref="exn:articleV1"/>
+ <prov:generalEntity prov:ref="exn:article"/>
+ </prov:specializationOf>
+ </prov:document>
+ </pre>
+ </div>
+ <p>
+ Later, after the data set is corrected and the new chart generated, a new version
+ of the article is created, <code>exn:articleV2</code>, with its own URI where the article
+ is redirected to. To ensure that those
+ consulting the provenance of <code>exn:articleV2</code> understand that it
+ is connected with the provenance of <code>exn:article</code> and <code>exn:articleV1</code>,
+ the newspaper describes how these entities are related.
+ </p>
+ <div class="turtle example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>Turtle Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'turtle example', 'none');
+ set_display_by_class('div', 'turtle example', 'none');
+ set_display_by_id('hide-turtle-examples', 'none');
+ set_display_by_id('show-turtle-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> exn:articleV2 prov:specializationOf exn:article .
+ exn:articleV2 prov:alternateOf exn:articleV1
+ </pre>
+ </div>
+ <div class="provn example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>PROV-N Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'provn example', 'none');
+ set_display_by_class('div', 'provn example', 'none');
+ set_display_by_id('hide-provn-examples', 'none');
+ set_display_by_id('show-provn-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> specializationOf(exn:articleV2, exn:article)
+ alternateOf(exn:articleV2, exn:articleV1)
+ </pre>
+ </div>
+ <div class="provxml example">
+ <div class="exampleheader">
+ <span class="exampleheader"><b>XML Example</b>
+ <a onclick="
+ set_display_by_class('pre', 'provxml example', 'none');
+ set_display_by_class('div', 'provxml example', 'none');
+ set_display_by_id('hide-provxml-examples', 'none');
+ set_display_by_id('show-provxml-examples', '');"><u><i>(hide all)</i></u></a>
+ </span></div>
+ <pre> <prov:document>
+ ...
+ <prov:specializationOf>
+ <prov:specificEntity prov:ref="exn:articleV2"/>
+ <prov:generalEntity prov:ref="exn:article"/>
+ </prov:specializationOf>
+ <prov:alternateOf>
+ <prov:alternate1 prov:ref="exn:articleV1"/>
+ <prov:alternate2 prov:ref="exn:articleV2"/>
+ </prov:alternateOf>
+ </prov:document>
+ </pre>
+ </div>
+ <p>
+ Note that above we could have also
+ stated that <code>exn:articleV2</code> was a revision of <code>exn:articleV1</code>,
+ as we did between <code>exc:chart2</code> and <code>exc:chart1</code>,
+ which would describe more concretely how the alternate entities are related.
+ Specialization and alternate relations connect entities, and so are visualized
+ as links between them.
+ </p>
+ <img src="images/specialization.png" alt="Specialization and alternate links between entities">
+ </section>
+
+ <section id="the-complete-example">
+ <h3><span class="secno">3.10 </span>The Complete Example</h3>
+ <p>
+ The full set of examples shown above are available in <a href="primer-turtle-examples.ttl">PROV-O Turtle format</a>
+ or <a href="primer-provn-examples.provn">PROV-N format</a> or <a href="primer-prov-xml-examples.xml">PROV-XML format</a>.
+ We visualize the whole example below.
+ </p>
+ <img src="images/everything.png" alt="Provenance graph for whole example">
+ </section>
+ </section>
+ <section id="summary">
+ <!--OddPage--><h2><span class="secno">4. </span>Summary</h2>
+ <p>The examples in the previous section highlight the following important capabilities of PROV:
+ </p>
+ <ol>
+ <li><b>Representing diverse entities involved in provenance</b>.
+ The examples illustrate that provenance records can contain different
+ kinds of information:
+ <ul>
+ <li>The newspaper took an object-centered view on their provenance statements,
+ stating what objects were derived from others but not stating what processes
+ were used or what entities were involved.</li>
+ <li>Betty the blogger took a very agent-centered view on provenance.
+ She chose to associate her blog post with herself, the government agency
+ that published the data, and the newspaper that published the article.</li>
+ <li>Derek took a process-centered perspective and combined it with object-centered
+ and agent-centered provenance information. The processes followed to derive the
+ charts from the government datasets were clearly. All intermediate and final
+ documents were stated. His involvement in the various activities was clearly
+ recorded, and the resulting documents were attributed to him.</li>
+ </ul></li>
+ <li><b>Stating partial or incomplete provenance</b>. The newspaper omitted
+ information about their specific editorial processes in publishing articles.
+ The chart generator said nothing about the software used, therefore omitting
+ information about other agents involved in the processes.</li>
+ <li><b>Integrating provenance-related information represented in other vocabularies</b>.
+ The FOAF vocabulary was used for specifying details about Derek and his company.
+ The Dublin Core vocabulary was used for specifying the article title. </li>
+ <li><b>Combining distributed provenance records provided by different parties</b>.
+ The provenance records described in this example came from a government source,
+ a newspaper, a company, and a blogger. Using URIs and namespaces, a provenance
+ record can draw from multiple sources on the Web.</li>
+ <li><b>Describing the commonalities in the derivation of two entities</b>.
+ The two versions of the charts were both derived through a similar compile activity.</li>
+ <li><b>Relating versions of objects over time</b>.
+ The second dataset was described as a revision of the first one.</li>
+ <li><b>Stating the provenance of provenance assertions</b>.
+ Betty could create a provenance record for her blog post, and
+ then assert the provenance of that provenance record.</li>
+ <li><b>Enabling alternative accounts for the provenance of an entity</b>.
+ The blog post could have a provenance account from Betty as its author and another
+ one from the newspaper that the blog quoted from.</li>
+ <li><b>Supporting queries over provenance of different granularity</b>.
+ The activity of composing the data from different regions was described
+ in greater detail than the other steps to produce the chart.
+ The provenance of the chart has much finer-grained detail than
+ the provenance of the government dataset.</li>
+ <li><b>Supporting reasoning and inference over provenance records</b>.
+ The provenance assertions explicitly stated above can be used to infer
+ additional assertions that are true according to the PROV model.
+ For example, because Derek created the chart acting on behalf of Chart
+ Generators, a PROV inference may be that the chart can be attributed to Chart Generators.</li>
+ </ol>
+ <p>The examples also illustrate how PROV enables many uses of provenance,
+ such as checking for possible errors, tracking down parties responsible for
+ fixing them, repeating processes to re-generate datasets, relating versions of
+ documents over time, and inspecting sources and attribution.
+ </p>
+
+ <p>There are additional aspects of the PROV data model that we have not covered
+ in this primer and that are important in many uses of provenance. These include
+ the following.
+ </p>
+ <ol>
+ <li><b>Provenance of provenance</b>:
+ It is often useful to state the provenance of a provenance record.
+ To enable this, PROV allows the grouping of provenance assertions as a <i>bundle</i>.
+ A bundle is a type of entity, and therefore its provenance can be asserted in turn.
+ For example, supposed that Betty wanted to express in the provenance of her blog
+ entry that she personally checked her sources. She would want to state the
+ provenance of her blog entry, and then state that she stands by that provenance.
+ To do this, she would create a bundle that contains provenance assertions for
+ her blog entry, and then she would state that she was the creator of that bundle. </li>
+ <li><b>Collections of entities</b>:
+ A <i>collection</i> in PROV is a type of entity that has other entities as members.
+ For example, Derek could decide to create several types of charts using dataset2.
+ He would describe all the charts as a collection, and then state the provenance of
+ the collection to be a single step that generates all the charts. </li>
+ </ol>
+ <p>
+ Please see the [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>] specification for details on these
+ and other concepts.
+ </p>
+</section>
+
+<section class="appendix" id="acknowledgements">
+ <!--OddPage--><h2><span class="secno">A. </span>Acknowledgements</h2>
+ <p>
+ This document has been produced by the Provenance Working Group, and its contents reflect extensive discussion within the Working Group as a whole. The editors extend special thanks to Sandro Hawke (<abbr title="World Wide Web Consortium">W3C</abbr>/<abbr title="Massachusetts Institute of Technology">MIT</abbr>) and Ivan Herman (<abbr title="World Wide Web Consortium">W3C</abbr>/<abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr>), <abbr title="World Wide Web Consortium">W3C</abbr> contacts for the Provenance Working Group.
+ </p>
+ <p>
+ The editors acknowledge valuable contributions from the following:
+ Tom Baker,
+ David Booth,
+ Bob DuCharme,
+ Robert Freimuth,
+ Satrajit Ghosh,
+ Ralph Hodgson,
+ Renato Iannella,
+ Jacek Kopecky,
+ James Leigh,
+ Chuck Morris,
+ Jacco van Ossenbruggen,
+ Alan Ruttenberg,
+ Reza Samavi, and
+ Antoine Zimmermann.
+ </p>
+ <p>
+ Members of the Provenance Working Group at the time of publication of this document were:
+
+ Ilkay Altintas (Invited expert),
+ Reza B'Far (Oracle Corporation),
+ Khalid Belhajjame (University of Manchester),
+ James Cheney (University of Edinburgh, School of Informatics),
+ Sam Coppens (iMinds - Ghent University),
+ David Corsar (University of Aberdeen, Computing Science),
+ Stephen Cresswell (The National Archives),
+ Tom De Nies (iMinds - Ghent University),
+ Helena Deus (DERI Galway at the National University of Ireland, Galway, Ireland),
+ Simon Dobson (Invited expert),
+ Martin Doerr (Foundation for Research and Technology - Hellas(FORTH)),
+ Kai Eckert (Invited expert),
+ Jean-Pierre EVAIN (European Broadcasting Union, EBU-UER),
+ James Frew (Invited expert),
+ Irini Fundulaki (Foundation for Research and Technology - Hellas(FORTH)),
+ Daniel Garijo (Universidad Politécnica de Madrid),
+ Yolanda Gil (Invited expert),
+ Ryan Golden (Oracle Corporation),
+ Paul Groth (Vrije Universiteit),
+ Olaf Hartig (Invited expert),
+ David Hau (National Cancer Institute, NCI),
+ Sandro Hawke (<abbr title="World Wide Web Consortium">W3C</abbr>/<abbr title="Massachusetts Institute of Technology">MIT</abbr>),
+ Jörn Hees (German Research Center for Artificial Intelligence (DFKI) Gmbh),
+ Ivan Herman, (<abbr title="World Wide Web Consortium">W3C</abbr>/<abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr>),
+ Ralph Hodgson (TopQuadrant),
+ Hook Hua (Invited expert),
+ Trung Dong Huynh (University of Southampton),
+ Graham Klyne (University of Oxford),
+ Michael Lang (Revelytix, Inc.),
+ Timothy Lebo (Rensselaer Polytechnic Institute),
+ James McCusker (Rensselaer Polytechnic Institute),
+ Deborah McGuinness (Rensselaer Polytechnic Institute),
+ Simon Miles (Invited expert),
+ Paolo Missier (School of Computing Science, Newcastle university),
+ Luc Moreau (University of Southampton),
+ James Myers (Rensselaer Polytechnic Institute),
+ Vinh Nguyen (Wright State University),
+ Edoardo Pignotti (University of Aberdeen, Computing Science),
+ Paulo da Silva Pinheiro (Rensselaer Polytechnic Institute),
+ Carl Reed (Open Geospatial Consortium),
+ Adam Retter (Invited Expert),
+ Christine Runnegar (Invited expert),
+ Satya Sahoo (Invited expert),
+ David Schaengold (Revelytix, Inc.),
+ Daniel Schutzer (FSTC, Financial Services Technology Consortium),
+ Yogesh Simmhan (Invited expert),
+ Stian Soiland-Reyes (University of Manchester),
+ Eric Stephan (Pacific Northwest National Laboratory),
+ Linda Stewart (The National Archives),
+ Ed Summers (Library of Congress),
+ Maria Theodoridou (Foundation for Research and Technology - Hellas(FORTH)),
+ Ted Thibodeau (OpenLink Software Inc.),
+ Curt Tilmes (National Aeronautics and Space Administration),
+ Craig Trim (IBM Corporation),
+ Stephan Zednik (Rensselaer Polytechnic Institute),
+ Jun Zhao (University of Oxford),
+ Yuting Zhao (University of Aberdeen, Computing Science).
+</p></section>
+
+<section class="appendix" id="changes-since-fourth-public-working-draft">
+ <!--OddPage--><h2><span class="secno">B. </span>Changes Since Fourth Public Working Draft</h2>
+ <ul>
+ <li>Corrected XML example for activities</li>
+ <li>Clarified usage of adoptedOnBehalfOf relation</li>
+ <li>Clarified wasQuotedFrom example</li>
+ <li>Adapted PROV-XML examples to clarify they are not RDF/XML</li>
+ <li>Clarified varying sources of example provenance data with different namespace prefixes,
+ and in division of complete example provenance graph</li>
+ <li>Used instance-specific identifiers for entities, activities and agents</li>
+ <li>Added section summarising some additional aspects of PROV not covered in depth</li>
+ <li>Added summary section</li>
+ <li>Added proper acknowledgements</li>
+ <li>Clarified the introduction regarding what is in each section.</li>
+ <li>Added references for FOAF, Dublin Core and newer PROV documents.</li>
+ <li>Typos fixed and minor clarifications throughout</li>
+ </ul>
+</section>
+
+
+<section id="references" class="appendix"><!--OddPage--><h2><span class="secno">C. </span>References</h2><section id="informative-references"><h3><span class="secno">C.1 </span>Informative references</h3><dl class="bibliography"><dt id="bib-DCTERMS">[DCTERMS]</dt><dd>Dublin Core Metadata Initiative. <a href="http://dublincore.org/documents/2012/06/14/dcmi-terms/"><cite>DCMI Metadata Terms</cite></a>. 14 June 2012. URL: <a href="http://dublincore.org/documents/2012/06/14/dcmi-terms/">http://dublincore.org/documents/2012/06/14/dcmi-terms/</a>
+</dd><dt id="bib-FOAF">[FOAF]</dt><dd>Dan Brickley, Libby Miller; eds. <a href="http://xmlns.com/foaf/spec/20100809.html"><cite>FOAF Vocabulary Specification 0.98</cite></a>. 9 August 2010. URL: <a href="http://xmlns.com/foaf/spec/20100809.html">http://xmlns.com/foaf/spec/20100809.html</a>
+</dd><dt id="bib-PROV-AQ">[PROV-AQ]</dt><dd>Graham Klyne; Paul Groth; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/"><cite>Provenance Access and Query</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/">http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/</a>
+</dd><dt id="bib-PROV-CONSTRAINTS">[PROV-CONSTRAINTS]</dt><dd>James Cheney; Paolo Missier; Luc Moreau; eds. <a href="http://www.w3.org/TR/2013/REC-prov-constraints-20130430/"><cite>Constraints of the PROV Data Model</cite></a>. 30 April 2013, W3C Recommendation. URL: <a href="http://www.w3.org/TR/2013/REC-prov-constraints-20130430/">http://www.w3.org/TR/2013/REC-prov-constraints-20130430/</a>
+</dd><dt id="bib-PROV-DC">[PROV-DC]</dt><dd>Daniel Garijo; Kai Eckert; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/"><cite>Dublin Core to PROV Mapping</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/">http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/</a>
+</dd><dt id="bib-PROV-DICTIONARY">[PROV-DICTIONARY]</dt><dd>Tom De Nies; Sam Coppens; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><cite>PROV Dictionary: Modeling Provenance for Dictionary Data Structures</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/</a>
+</dd><dt id="bib-PROV-DM">[PROV-DM]</dt><dd>Luc Moreau; Paolo Missier; eds. <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/"><cite>PROV-DM: The PROV Data Model</cite></a>. 30 April 2013, W3C Recommendation. URL: <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/">http://www.w3.org/TR/2013/REC-prov-dm-20130430/</a>
+</dd><dt id="bib-PROV-LINKS">[PROV-LINKS]</dt><dd>Luc Moreau; Timothy Lebo; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-links-20130430/"><cite>Linking Across Provenance Bundles</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-links-20130430/">http://www.w3.org/TR/2013/NOTE-prov-links-20130430/</a>
+</dd><dt id="bib-PROV-N">[PROV-N]</dt><dd>Luc Moreau; Paolo Missier; eds. <a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/"><cite>PROV-N: The Provenance Notation</cite></a>. 30 April 2013, W3C Recommendation. URL: <a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/">http://www.w3.org/TR/2013/REC-prov-n-20130430/</a>
+</dd><dt id="bib-PROV-O">[PROV-O]</dt><dd>Timothy Lebo; Satya Sahoo; Deborah McGuinness; eds. <a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/"><cite>PROV-O: The PROV Ontology</cite></a>. 30 April 2013, W3C Recommendation. URL: <a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/">http://www.w3.org/TR/2013/REC-prov-o-20130430/</a>
+</dd><dt id="bib-PROV-OVERVIEW">[PROV-OVERVIEW]</dt><dd>Paul Groth; Luc Moreau; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/"><cite>PROV-OVERVIEW: An Overview of the PROV Family of Documents</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/">http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/</a>
+</dd><dt id="bib-PROV-SEM">[PROV-SEM]</dt><dd>James Cheney; ed. <a href="http://www.w3.org/TR/2013/NOTE-prov-sem-20130430"><cite>Semantics of the PROV Data Model</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-sem-20130430">http://www.w3.org/TR/2013/NOTE-prov-sem-20130430</a>.
+</dd><dt id="bib-PROV-XML">[PROV-XML]</dt><dd>Hook Hua; Curt Tilmes; Stephan Zednik; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/"><cite>PROV-XML: The PROV XML Schema</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/">http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/</a>
+</dd><dt id="bib-PROVENANCE-XG">[PROVENANCE-XG]</dt><dd>Yolanda Gil, James Cheney, Paul Groth, Olaf Hartig, Simon Miles, Luc Moreau, Paulo Pinheiro da Silva. <a href="http://www.w3.org/2005/Incubator/prov/XGR-prov-20101214/"><cite>Provenance XG Final Report</cite></a>. 8 December 2010. URL: <a href="http://www.w3.org/2005/Incubator/prov/XGR-prov-20101214/">http://www.w3.org/2005/Incubator/prov/XGR-prov-20101214/</a>
+</dd><dt id="bib-TURTLE">[TURTLE]</dt><dd>Eric Prud'hommeaux, Gavin Carothers; eds. <a href="http://www.w3.org/TR/2011/WD-turtle-20110809/"><cite>Turtle: Terse RDF Triple Language</cite></a>. 9 August 2011. W3C Working Draft. URL: <a href="http://www.w3.org/TR/2011/WD-turtle-20110809/">http://www.w3.org/TR/2011/WD-turtle-20110809/</a>
</dd></dl></section></section></body></html>
\ No newline at end of file
Binary file primer/NOTE-prov-primer-20130430/images/activities.png has changed
Binary file primer/images/activities.png has changed
--- a/primer/images/activities.svg Fri Apr 26 09:26:16 2013 +0100
+++ b/primer/images/activities.svg Fri Apr 26 09:27:12 2013 +0100
@@ -22,7 +22,7 @@
inkscape:export-ydpi="90"><metadata
id="metadata8"><rdf:RDF><cc:Work
rdf:about=""><dc:format>image/svg+xml</dc:format><dc:type
- rdf:resource="http://purl.org/dc/dcmitype/StillImage" /><dc:title></dc:title></cc:Work></rdf:RDF></metadata><defs
+ rdf:resource="http://purl.org/dc/dcmitype/StillImage" /><dc:title /></cc:Work></rdf:RDF></metadata><defs
id="defs6"><linearGradient
id="linearGradient4511"><stop
style="stop-color:#d19d00;stop-opacity:1;"
@@ -167,17 +167,18 @@
id="text128"
style="font-size:12px;fill:#000000;stroke:none"
x="-110.70643"
- y="-28.007856"><tspan
+ y="-28.236326"><tspan
font-size="16"
font-weight="500"
x="-63.247353"
- y="-13.007839"
+ y="-13.236309"
textLength="54.242188"
id="tspan130"
style="font-size:9.60000038px;font-weight:500;font-family:Georgia">exc:illustrate1</tspan></text>
+
<rect
x="-128.63626"
y="-23.68034"
@@ -194,19 +195,20 @@
transform="matrix(0.99997296,-0.00735337,0,1,0,0)" /><text
id="text128-4"
style="font-size:12px;fill:#000000;stroke:none"
- x="-174.01192"
- y="-27.049191"
- transform="matrix(1,0.01849022,0,1,0,0)"><tspan
+ x="-173.76906"
+ y="-27.897995"
+ transform="matrix(1.0001671,0.00275063,0.0157373,0.9998762,0,0)"><tspan
font-size="16"
font-weight="500"
- x="-126.55266"
- y="-12.049174"
+ x="-126.30979"
+ y="-12.897979"
textLength="54.242188"
id="tspan130-0"
style="font-size:9.60000038px;font-weight:500;font-family:Georgia">exc:compose1</tspan></text>
+
<rect
x="-0.65411484"
y="-24.825537"
@@ -222,11 +224,11 @@
style="fill:none;stroke:#0000ff;stroke-width:0.30654785;stroke-linecap:round;stroke-linejoin:round" /><text
id="text128-8"
style="font-size:12px;fill:#000000;stroke:none"
- x="-42.601112"
+ x="-44.201111"
y="-28.471903"><tspan
font-size="16"
font-weight="500"
- x="4.8579555"
+ x="3.2579556"
y="-13.471887"
textLength="54.242188"
id="tspan130-8"
@@ -234,6 +236,7 @@
+
</g>
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/provenance/prov-implementations.ttl Fri Apr 26 09:27:12 2013 +0100
@@ -0,0 +1,37 @@
+@prefix foaf: <http://xmlns.com/foaf/0.1/> .
+@prefix prov: <http://www.w3.org/ns/prov#> .
+@prefix : <#> .
+
+<http://www.w3.org/TR/prov-implementations/> a prov:Entity.
+
+<http://www.w3.org/TR/2013/NOTE-prov-implementations-20130430/>
+ prov:wasRevisionOf <http://www.w3.org/TR/2013/WD-prov-implementations-20130312/>;
+ prov:specializationOf <http://www.w3.org/TR/prov-implementations/>;
+ prov:wasAttributedTo :TrungDongHuynh;
+ prov:wasAttributedTo :PaulGroth;
+ prov:wasAttributedTo :StephanZednik;
+ prov:wasAttributedTo <http://www.w3.org/2011/prov>
+.
+
+:TrungDongHuynh
+ prov:specializationOf <http://users.ecs.soton.ac.uk/tdh/foaf.rdf#me>;
+ a prov:Person;
+ foaf:name "Trung Dong Huynh";
+ foaf:account <http://www.w3.org/2011/prov/wiki/User:Thuynh>
+.
+:PaulGroth
+ prov:specializationOf <http://id.ecs.soton.ac.uk/person/10022>;
+ a prov:Person;
+ foaf:name "Paul Groth";
+ foaf:account <http://www.w3.org/2011/prov/wiki/User:Pgroth>
+.
+:StephanZednik
+ prov:specializationOf <http://tw.rpi.edu/instances/StephanZednik>;
+ a prov:Person;
+ foaf:name "Stephan Zednik";
+ foaf:account <http://www.w3.org/2011/prov/wiki/User:Szednik>;
+ prov:actedOnBehalfOf <http://dbpedia.org/resource/Rensselaer_Polytechnic_Institute>;
+.
+
+<http://www.w3.org/2011/prov> a prov:Organization .
+
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/provenance/prov-overview.ttl Fri Apr 26 09:27:12 2013 +0100
@@ -0,0 +1,6 @@
+
+@prefix prov: <http://www.w3.org/ns/prov#> .
+
+
+<http://www.w3.org/TR/prov-aq/> a prov:Entity.
+
--- a/reports/NOTE-prov-implementations-20130430/Overview.html Fri Apr 26 09:26:16 2013 +0100
+++ b/reports/NOTE-prov-implementations-20130430/Overview.html Fri Apr 26 09:27:12 2013 +0100
@@ -5,6 +5,7 @@
<meta name="description" content="W3C PROV Implementation Report">
<meta name="keywords" content="W3C,PROV,implementation,Provenance Working Group">
<meta name="author" content="Trung Dong Huynh, Paul Groth, Stephan Zednik">
+ <link rel="http://www.w3.org/ns/prov#has_provenance" href="http://www.w3.org/2011/prov/provenance/prov-implementations">
<title>PROV Implementation Report</title>
@@ -526,7 +527,7 @@
</tr>
<tr id="33">
<td>33</td>
- <th scope="row"><a href="http://www.pubflow.de/en/provenanceArchive">PubFlow Provenance Archive</a></th>
+ <th scope="row"><a href="http://www.pubflow.de/en/provenancearchive">PubFlow Provenance Archive</a></th>
<td>Application<br>Framework / API</td>
<td>PROV-O, PROV-XML</td>
</tr>
--- a/reports/prov-implementations.html Fri Apr 26 09:26:16 2013 +0100
+++ b/reports/prov-implementations.html Fri Apr 26 09:27:12 2013 +0100
@@ -6,6 +6,7 @@
<meta name="description" content="W3C PROV Implementation Report">
<meta name="keywords" content="W3C,PROV,implementation,Provenance Working Group">
<meta name="author" content="Trung Dong Huynh, Paul Groth, Stephan Zednik">
+ <link rel="http://www.w3.org/ns/prov#has_provenance" href="http://www.w3.org/2011/prov/provenance/prov-implementations">
<title>PROV Implementation Report</title>
<script src="https://www.w3.org/Tools/respec/respec-w3c-common" class="remove" async></script>
@@ -335,7 +336,7 @@
</tr>
<tr id="33">
<td>33</td>
- <th scope="row"><a href="http://www.pubflow.de/en/provenanceArchive">PubFlow Provenance Archive</a></th>
+ <th scope="row"><a href="http://www.pubflow.de/en/provenancearchive">PubFlow Provenance Archive</a></th>
<td>Application<br>Framework / API</td>
<td>PROV-O, PROV-XML</td>
</tr>
--- a/semantics/releases/NOTE-prov-sem-20130430/Overview.html Fri Apr 26 09:26:16 2013 +0100
+++ b/semantics/releases/NOTE-prov-sem-20130430/Overview.html Fri Apr 26 09:27:12 2013 +0100
@@ -4421,7 +4421,7 @@
<section id="references" class="appendix"><!--OddPage--><h2><span class="secno">B. </span>References</h2><section id="informative-references"><h3><span class="secno">B.1 </span>Informative references</h3><dl class="bibliography"><dt id="bib-PROV-AQ">[PROV-AQ]</dt><dd>Graham Klyne; Paul Groth; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/"><cite>Provenance Access and Query</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/">http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/</a>
</dd><dt id="bib-PROV-CONSTRAINTS">[PROV-CONSTRAINTS]</dt><dd>James Cheney; Paolo Missier; Luc Moreau; eds. <a href="http://www.w3.org/TR/2013/REC-prov-constraints-20130430/"><cite>Constraints of the PROV Data Model</cite></a>. 30 April 2013, W3C Recommendation. URL: <a href="http://www.w3.org/TR/2013/REC-prov-constraints-20130430/">http://www.w3.org/TR/2013/REC-prov-constraints-20130430/</a>
</dd><dt id="bib-PROV-DC">[PROV-DC]</dt><dd>Daniel Garijo; Kai Eckert; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/"><cite>Dublin Core to PROV Mapping</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/">http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/</a>
-</dd><dt id="bib-PROV-DICTIONARY">[PROV-DICTIONARY]</dt><dd>Tom De Nies; Sam Coppens; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><cite>PROV Dictionary</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/</a>
+</dd><dt id="bib-PROV-DICTIONARY">[PROV-DICTIONARY]</dt><dd>Tom De Nies; Sam Coppens; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><cite>PROV-Dictionary: Modeling Provenance for Dictionary Data Structures</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/</a>
</dd><dt id="bib-PROV-DM">[PROV-DM]</dt><dd>Luc Moreau; Paolo Missier; eds. <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/"><cite>PROV-DM: The PROV Data Model</cite></a>. 30 April 2013, W3C Recommendation. URL: <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/">http://www.w3.org/TR/2013/REC-prov-dm-20130430/</a>
</dd><dt id="bib-PROV-LINKS">[PROV-LINKS]</dt><dd>Luc Moreau; Timothy Lebo; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-links-20130430/"><cite>Linking Across Provenance Bundles</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-links-20130430/">http://www.w3.org/TR/2013/NOTE-prov-links-20130430/</a>
</dd><dt id="bib-PROV-N">[PROV-N]</dt><dd>Luc Moreau; Paolo Missier; eds. <a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/"><cite>PROV-N: The Provenance Notation</cite></a>. 30 April 2013, W3C Recommendation. URL: <a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/">http://www.w3.org/TR/2013/REC-prov-n-20130430/</a>
@@ -4429,4 +4429,4 @@
</dd><dt id="bib-PROV-OVERVIEW">[PROV-OVERVIEW]</dt><dd>Paul Groth; Luc Moreau; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/"><cite>PROV-OVERVIEW: An Overview of the PROV Family of Documents</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/">http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/</a>
</dd><dt id="bib-PROV-PRIMER">[PROV-PRIMER]</dt><dd>Yolanda Gil; Simon Miles; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/"><cite>PROV Model Primer</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/">http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/</a>
</dd><dt id="bib-PROV-XML">[PROV-XML]</dt><dd>Hook Hua; Curt Tilmes; Stephan Zednik; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/"><cite>PROV-XML: The PROV XML Schema</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/">http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/</a>
-</dd></dl></section></section></body></html>
\ No newline at end of file
+</dd></dl></section></section></body></html>
Binary file semantics/releases/NOTE-prov-sem-20130430/prov-sem.pdf has changed
--- a/xml/Overview.html Fri Apr 26 09:26:16 2013 +0100
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,3044 +0,0 @@
-<?xml version='1.0' encoding='UTF-8'?>
-<!DOCTYPE html PUBLIC '-//W3C//DTD XHTML 1.0 Transitional//EN' 'http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd'>
-<html dir="ltr" xmlns="http://www.w3.org/1999/xhtml">
-<head>
- <title>PROV-XML: The PROV XML Schema</title>
- <meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
- <style type="text/css">
-
- .note { font-size:small; margin-left:50px }
-
- table.thinborder {
- border-width: 1px;
- border-spacing: 0px;
- border-style: none;
- border-color: gray;
- border-collapse: collapse;
- }
-
- table.thinborder th {
- border-width: 1px;
- padding: 0px;
- border-style: solid;
- border-color: gray;
- }
-
- table.thinborder td {
- border-width: 1px;
- padding: 2px;
- border-style: solid;
- border-color: gray;
- }
-
- </style>
-
-
-
-
-
-
-
-
-
-
-
-
-
- <style>/*****************************************************************
- * ReSpec 3 CSS
- * Robin Berjon - http://berjon.com/
- *****************************************************************/
-
-/* --- INLINES --- */
-em.rfc2119 {
- text-transform: lowercase;
- font-variant: small-caps;
- font-style: normal;
- color: #900;
-}
-
-h1 acronym, h2 acronym, h3 acronym, h4 acronym, h5 acronym, h6 acronym, a acronym,
-h1 abbr, h2 abbr, h3 abbr, h4 abbr, h5 abbr, h6 abbr, a abbr {
- border: none;
-}
-
-dfn {
- font-weight: bold;
-}
-
-a.internalDFN {
- color: inherit;
- border-bottom: 1px solid #99c;
- text-decoration: none;
-}
-
-a.externalDFN {
- color: inherit;
- border-bottom: 1px dotted #ccc;
- text-decoration: none;
-}
-
-a.bibref {
- text-decoration: none;
-}
-
-cite .bibref {
- font-style: normal;
-}
-
-code {
- color: #ff4500;
-}
-
-
-/* --- --- */
-ol.algorithm { counter-reset:numsection; list-style-type: none; }
-ol.algorithm li { margin: 0.5em 0; }
-ol.algorithm li:before { font-weight: bold; counter-increment: numsection; content: counters(numsection, ".") ") "; }
-
-/* --- TOC --- */
-.toc a, .tof a {
- text-decoration: none;
-}
-
-a .secno, a .figno {
- color: #000;
-}
-
-ul.tof, ol.tof {
- list-style: none outside none;
-}
-
-.caption {
- margin-top: 0.5em;
- font-style: italic;
-}
-
-/* --- TABLE --- */
-table.simple {
- border-spacing: 0;
- border-collapse: collapse;
- border-bottom: 3px solid #005a9c;
-}
-
-.simple th {
- background: #005a9c;
- color: #fff;
- padding: 3px 5px;
- text-align: left;
-}
-
-.simple th[scope="row"] {
- background: inherit;
- color: inherit;
- border-top: 1px solid #ddd;
-}
-
-.simple td {
- padding: 3px 10px;
- border-top: 1px solid #ddd;
-}
-
-.simple tr:nth-child(even) {
- background: #f0f6ff;
-}
-
-/* --- DL --- */
-.section dd > p:first-child {
- margin-top: 0;
-}
-
-.section dd > p:last-child {
- margin-bottom: 0;
-}
-
-.section dd {
- margin-bottom: 1em;
-}
-
-.section dl.attrs dd, .section dl.eldef dd {
- margin-bottom: 0;
-}
-</style><style>/* --- EXAMPLES --- */
-div.example-title {
- min-width: 7.5em;
- color: #b9ab2d;
-}
-div.example-title span {
- text-transform: uppercase;
-}
-aside.example, div.example, div.illegal-example {
- padding: 0.5em;
- margin: 1em 0;
- position: relative;
- clear: both;
-}
-div.illegal-example { color: red }
-div.illegal-example p { color: black }
-aside.example, div.example {
- padding: .5em;
- border-left-width: .5em;
- border-left-style: solid;
- border-color: #e0cb52;
- background: #fcfaee;
-}
-
-aside.example div.example {
- border-left-width: .1em;
- border-color: #999;
- background: #fff;
-}
-aside.example div.example div.example-title {
- color: #999;
-}
-</style><link rel="stylesheet" href="http://www.w3.org/StyleSheets/TR/W3C-WD" />
-<!--[if lt IE 9]><script src='http://www.w3.org/2008/site/js/html5shiv.js'></script><![endif]-->
-</head>
- <body><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">PROV-XML: The PROV XML Schema</h1>
-
- <h2 id="w3c-working-draft-12-march-2013"><abbr title="World Wide Web Consortium">W3C</abbr> Working Draft 12 March 2013</h2>
- <dl>
-
- <dt>This version:</dt>
- <dd><a href="http://www.w3.org/TR/2013/WD-prov-xml-20130312/">http://www.w3.org/TR/2013/WD-prov-xml-20130312/</a></dd>
- <dt>Latest published version:</dt>
- <dd><a href="http://www.w3.org/TR/prov-xml/">http://www.w3.org/TR/prov-xml/</a></dd>
-
-
- <dt>Latest editor's draft:</dt>
- <dd><a href="http://dvcs.w3.org/hg/prov/raw-file/default/xml/prov-xml.html">http://dvcs.w3.org/hg/prov/raw-file/default/xml/prov-xml.html</a></dd>
-
-
-
-
-
- <dt>Previous version:</dt>
- <dd><a href="http://www.w3.org/TR/2012/WD-prov-xml-20121211/">http://www.w3.org/TR/2012/WD-prov-xml-20121211/</a> <a href="diff.html">(color-coded diff)</a></dd>
-
-
- <dt>Editors:</dt>
- <dd><span>(In alphabetical order)</span></dd>
-<dd><span>Hook Hua</span>, Invited Expert</dd>
-<dd><span>Curt Tilmes</span>, National Aeronautics and Space Administration</dd>
-<dd><a href="http://tw.rpi.edu/web/person/StephanZednik">Stephan Zednik</a>, Rensselaer Polytechnic Institute</dd>
-
-
- <dt>Author:</dt>
- <dd><a href="http://www.ecs.soton.ac.uk/~lavm/">Luc Moreau</a>, University of Southampton</dd>
-
-
- </dl>
-
-
-
-
-
- <p class="copyright">
- <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> ©
- 2012-2013
-
- <a href="http://www.w3.org/"><abbr title="World Wide Web Consortium">W3C</abbr></a><sup>®</sup>
- (<a href="http://www.csail.mit.edu/"><abbr title="Massachusetts Institute of Technology">MIT</abbr></a>,
- <a href="http://www.ercim.eu/"><abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr></a>,
- <a href="http://www.keio.ac.jp/">Keio</a>, <a href="http://ev.buaa.edu.cn/">Beihang</a>), All Rights Reserved.
- <abbr title="World Wide Web Consortium">W3C</abbr> <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>,
- <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and
- <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.
- </p>
-
-
- <hr />
-</div>
-
-<section id="abstract" class="introductory"><h2>Abstract</h2>
-<p>
-Provenance is information about entities, activities, and people involved in producing a piece of data or thing, which can be used to form assessments about its quality, reliability or trustworthiness. PROV-DM is the conceptual data model that forms a basis for the <abbr title="World Wide Web Consortium">W3C</abbr> provenance (PROV) family of specifications. It defines a concepts for expressing provenance information enabling interchange. This document introduces an XML schema for the PROV data model (PROV-DM), allowing instances of the PROV data model to be serialized in XML.
-</p>
-<p>The <a href="http://www.w3.org/TR/2012/WD-prov-overview-20130312/">PROV Document Overview</a> describes the overall state of PROV, and should be read before other PROV documents.</p>
-</section><section id="sotd" class="introductory"><h2>Status of This Document</h2>
-
-
-
- <p>
- <em>This section describes the status of this document at the time of its publication. Other
- documents may supersede this document. A list of current <abbr title="World Wide Web Consortium">W3C</abbr> publications and the latest revision
- of this technical report can be found in the <a href="http://www.w3.org/TR/"><abbr title="World Wide Web Consortium">W3C</abbr> technical reports
- index</a> at http://www.w3.org/TR/.</em>
- </p>
-
-<h4 id="prov-family-of-documents">PROV Family of Documents</h4>
-This document is part of the PROV family of documents, a set of documents defining various aspects that are necessary to achieve the vision of inter-operable
-interchange of provenance information in heterogeneous environments such as the Web. These documents are listed below. Please consult the [<cite><a class="bibref" href="#bib-PROV-OVERVIEW">PROV-OVERVIEW</a></cite>] for a guide to reading these documents.
-<ul>
-<li> <a href="http://www.w3.org/TR/2013/WD-prov-overview-20130312/">PROV-OVERVIEW</a> (To be published as Note), an overview of the PROV family of documents [<cite><a class="bibref" href="#bib-PROV-OVERVIEW">PROV-OVERVIEW</a></cite>];</li>
-<li> <a href="http://www.w3.org/TR/2013/WD-prov-primer-20130312/">PROV-PRIMER</a> (To be published as Note), a primer for the PROV data model [<cite><a class="bibref" href="#bib-PROV-PRIMER">PROV-PRIMER</a></cite>];</li>
-<li> <a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/">PROV-O</a> (Proposed Recommendation), the PROV ontology, an OWL2 ontology allowing the mapping of PROV to RDF [<cite><a class="bibref" href="#bib-PROV-O">PROV-O</a></cite>];</li>
-<li> <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/">PROV-DM</a> (Proposed Recommendation), the PROV data model for provenance [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>];</li>
-<li> <a href="http://www.w3.org/TR/2013/PR-prov-n-20130312/">PROV-N</a> (Proposed Recommendation), a notation for provenance aimed at human consumption [<cite><a class="bibref" href="#bib-PROV-N">PROV-N</a></cite>];</li>
-<li> <a href="http://www.w3.org/TR/2013/PR-prov-constraints-20130312/">PROV-CONSTRAINTS</a> (Proposed Recommendation), a set of constraints applying to the PROV data model [<cite><a class="bibref" href="#bib-PROV-CONSTRAINTS">PROV-CONSTRAINTS</a></cite>];</li>
-<li> <a href="http://www.w3.org/TR/2013/WD-prov-xml-20130312/">PROV-XML</a> (To be published as Note), an XML schema for the PROV data model (this document);</li>
-<li> <a href="http://www.w3.org/TR/2013/WD-prov-aq-20130312/">PROV-AQ</a> (To be published as Note), the mechanisms for accessing and querying provenance [<cite><a class="bibref" href="#bib-PROV-AQ">PROV-AQ</a></cite>]; </li>
-<li> <a href="http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/">PROV-DICTIONARY</a> (To be published as Note) introduces a specific type of collection, consisting of key-entity pairs [<cite><a class="bibref" href="#bib-PROV-DICTIONARY">PROV-DICTIONARY</a></cite>];</li>
-<li> <a href="http://www.w3.org/TR/2013/WD-prov-dc-20130312/">PROV-DC</a> (To be published as Note) provides a mapping between PROV and Dublic Core Terms [<cite><a class="bibref" href="#bib-PROV-DC">PROV-DC</a></cite>];</li>
-<li> <a href="http://www.w3.org/TR/2013/WD-prov-sem-20130312/">PROV-SEM</a> (To be published as Note), a declarative specification in terms of first-order logic of the PROV data model [<cite><a class="bibref" href="#bib-PROV-SEM">PROV-SEM</a></cite>];</li>
-<li> <a href="http://www.w3.org/TR/2013/WD-prov-links-20130312/">PROV-LINKS</a> (To be published as Note) introduces a mechanism to link across bundles [<cite><a class="bibref" href="#bib-PROV-LINKS">PROV-LINKS</a></cite>].</li>
-</ul>
-
- <p>
- This document was published by the <a href="http://www.w3.org/2011/prov/">Provenance Working Group</a> as a Working Draft.
-
-
- If you wish to make comments regarding this document, please send them to
- <a href="mailto:public-prov-comments@w3.org">public-prov-comments@w3.org</a>
- (<a href="mailto:public-prov-comments-request@w3.org?subject=subscribe">subscribe</a>,
- <a href="http://lists.w3.org/Archives/Public/public-prov-comments/">archives</a>).
-
-
-
-
- All comments are welcome.
-
-
- </p><p>
- Publication as a Working Draft does not imply endorsement by the <abbr title="World Wide Web Consortium">W3C</abbr> Membership.
- This is a draft document and may be updated, replaced or obsoleted by other documents at
- any time. It is inappropriate to cite this document as other than work in progress.
- </p>
-
-
- <p>
-
- This document was produced by a group operating under the
- <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 <abbr title="World Wide Web Consortium">W3C</abbr> Patent Policy</a>.
-
- The group does not expect this document to become a <abbr title="World Wide Web Consortium">W3C</abbr> Recommendation.
-
-
- <abbr title="World Wide Web Consortium">W3C</abbr> maintains a <a href="http://www.w3.org/2004/01/pp-impl/46974/status" rel="disclosure">public list of any patent disclosures</a>
-
- made in connection with the deliverables of the group; that page also includes instructions for
- disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains
- <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential Claim(s)</a> must disclose the
- information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section
- 6 of the <abbr title="World Wide Web Consortium">W3C</abbr> Patent Policy</a>.
-
-
- </p>
-
-
-
-
-</section><section id="toc"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a href="#introduction" class="tocxref"><span class="secno">1. </span>Introduction</a><ul class="toc"><li class="tocline"><a href="#prov-namespace" class="tocxref"><span class="secno">1.1 </span>PROV Namespace</a></li><li class="tocline"><a href="#conventions" class="tocxref"><span class="secno">1.2 </span>Conventions</a></li></ul></li><li class="tocline"><a href="#schema-design" class="tocxref"><span class="secno">2. </span>XML Schema Design</a><ul class="toc"><li class="tocline"><a href="#schema-modularization" class="tocxref"><span class="secno">2.1 </span>Schema Modularization</a></li><li class="tocline"><a href="#design-pattern" class="tocxref"><span class="secno">2.2 </span><i>Salami Slice</i> Design Pattern</a></li><li class="tocline"><a href="#elements-vs-attributes" class="tocxref"><span class="secno">2.3 </span>Elements vs. Attributes</a></li><li class="tocline"><a href="#type-conventions" class="tocxref"><span class="secno">2.4 </span>Type Conventions</a><ul class="toc"><li class="tocline"><a href="#type-conventions-attributes" class="tocxref"><span class="secno">2.4.1 </span>PROV Type Attribute</a></li><li class="tocline"><a href="#type-conventions-extension-types" class="tocxref"><span class="secno">2.4.2 </span>Extension Types</a></li><li class="tocline"><a href="#type-conventions-xsi-type" class="tocxref"><span class="secno">2.4.3 </span>XSI Type</a></li></ul></li><li class="tocline"><a href="#naming-conventions" class="tocxref"><span class="secno">2.5 </span>Naming Conventions</a></li></ul></li><li class="tocline"><a href="#schema-components" class="tocxref"><span class="secno">3. </span>PROV XML Schema</a><ul class="toc"><li class="tocline"><a href="#component1" class="tocxref"><span class="secno">3.1 </span>Component 1: Entities and Activities</a><ul class="toc"><li class="tocline"><a href="#term-Entity" class="tocxref"><span class="secno">3.1.1 </span>Entity</a></li><li class="tocline"><a href="#term-Activity" class="tocxref"><span class="secno">3.1.2 </span>Activity</a></li><li class="tocline"><a href="#term-Generation" class="tocxref"><span class="secno">3.1.3 </span>Generation</a></li><li class="tocline"><a href="#term-Usage" class="tocxref"><span class="secno">3.1.4 </span>Usage</a></li><li class="tocline"><a href="#term-Communication" class="tocxref"><span class="secno">3.1.5 </span>Communication</a></li><li class="tocline"><a href="#term-Start" class="tocxref"><span class="secno">3.1.6 </span>Start</a></li><li class="tocline"><a href="#term-End" class="tocxref"><span class="secno">3.1.7 </span>End</a></li><li class="tocline"><a href="#term-Invalidation" class="tocxref"><span class="secno">3.1.8 </span>Invalidation</a></li></ul></li><li class="tocline"><a href="#component2" class="tocxref"><span class="secno">3.2 </span>Component 2: Derivations</a><ul class="toc"><li class="tocline"><a href="#term-Derivation" class="tocxref"><span class="secno">3.2.1 </span>Derivation</a></li><li class="tocline"><a href="#term-Revision" class="tocxref"><span class="secno">3.2.2 </span>Revision</a></li><li class="tocline"><a href="#term-Quotation" class="tocxref"><span class="secno">3.2.3 </span>Quotation</a></li><li class="tocline"><a href="#term-Primary-Source" class="tocxref"><span class="secno">3.2.4 </span>Primary Source</a></li></ul></li><li class="tocline"><a href="#component3" class="tocxref"><span class="secno">3.3 </span>Component 3: Agents, Responsibility, and Influence</a><ul class="toc"><li class="tocline"><a href="#term-Agent" class="tocxref"><span class="secno">3.3.1 </span>Agent</a><ul class="toc"><li class="tocline"><a href="#term-Person" class="tocxref"><span class="secno">3.3.1.1 </span>Person</a></li><li class="tocline"><a href="#term-Organization" class="tocxref"><span class="secno">3.3.1.2 </span>Organization</a></li><li class="tocline"><a href="#term-SoftwareAgent" class="tocxref"><span class="secno">3.3.1.3 </span>Software Agent</a></li></ul></li><li class="tocline"><a href="#term-Attribution" class="tocxref"><span class="secno">3.3.2 </span>Attribution</a></li><li class="tocline"><a href="#term-Association" class="tocxref"><span class="secno">3.3.3 </span>Association</a><ul class="toc"><li class="tocline"><a href="#term-Plan" class="tocxref"><span class="secno">3.3.3.1 </span>Plan</a></li></ul></li><li class="tocline"><a href="#term-Delegation" class="tocxref"><span class="secno">3.3.4 </span>Delegation</a></li><li class="tocline"><a href="#term-Influence" class="tocxref"><span class="secno">3.3.5 </span>Influence</a></li></ul></li><li class="tocline"><a href="#component4" class="tocxref"><span class="secno">3.4 </span>Component 4: Bundles</a><ul class="toc"><li class="tocline"><a href="#term-Bundle" class="tocxref"><span class="secno">3.4.1 </span>Bundle</a></li><li class="tocline"><a href="#term-BundleConstructor" class="tocxref"><span class="secno">3.4.2 </span>Bundle Constructor</a></li></ul></li><li class="tocline"><a href="#component5" class="tocxref"><span class="secno">3.5 </span>Component 5: Alternate Entities</a><ul class="toc"><li class="tocline"><a href="#term-Specialization" class="tocxref"><span class="secno">3.5.1 </span>Specialization</a></li><li class="tocline"><a href="#term-Alternate" class="tocxref"><span class="secno">3.5.2 </span>Alternate</a></li></ul></li><li class="tocline"><a href="#component6" class="tocxref"><span class="secno">3.6 </span>Component 6: Collections</a><ul class="toc"><li class="tocline"><a href="#term-Collection" class="tocxref"><span class="secno">3.6.1 </span>Collection</a><ul class="toc"><li class="tocline"><a href="#term-EmptyCollection" class="tocxref"><span class="secno">3.6.1.1 </span>Empty Collection</a></li></ul></li><li class="tocline"><a href="#term-Membership" class="tocxref"><span class="secno">3.6.2 </span>Membership</a></li></ul></li><li class="tocline"><a href="#further-elements" class="tocxref"><span class="secno">3.7 </span>Further Elements of PROV</a><ul class="toc"><li class="tocline"><a href="#attribute-Identifier" class="tocxref"><span class="secno">3.7.1 </span>Identifier</a></li><li class="tocline"><a href="#attribute-Reference" class="tocxref"><span class="secno">3.7.2 </span>Reference</a></li><li class="tocline"><a href="#attributes" class="tocxref"><span class="secno">3.7.3 </span>Attributes</a><ul class="toc"><li class="tocline"><a href="#element-Label" class="tocxref"><span class="secno">3.7.3.1 </span>Label</a></li><li class="tocline"><a href="#element-Location" class="tocxref"><span class="secno">3.7.3.2 </span>Location</a></li><li class="tocline"><a href="#element-Role" class="tocxref"><span class="secno">3.7.3.3 </span>Role</a></li><li class="tocline"><a href="#element-Type" class="tocxref"><span class="secno">3.7.3.4 </span>Type</a></li><li class="tocline"><a href="#element-Value" class="tocxref"><span class="secno">3.7.3.5 </span>Value</a></li></ul></li><li class="tocline"><a href="#type-value" class="tocxref"><span class="secno">3.7.4 </span>Value</a></li></ul></li><li class="tocline"><a href="#structural-elements" class="tocxref"><span class="secno">3.8 </span>Structural Elements of PROV-XML</a><ul class="toc"><li class="tocline"><a href="#term-Document" class="tocxref"><span class="secno">3.8.1 </span>Document</a></li></ul></li></ul></li><li class="tocline"><a href="#media-type" class="tocxref"><span class="secno">4. </span>Media Type</a></li><li class="tocline"><a href="#prov-xml-schema" class="tocxref"><span class="secno">A. </span>XML Schema</a><ul class="toc"><li class="tocline"><a href="#prov-schema" class="tocxref"><span class="secno">A.1 </span>prov.xsd</a></li><li class="tocline"><a href="#prov-core-schema" class="tocxref"><span class="secno">A.2 </span>prov-core.xsd</a></li><li class="tocline"><a href="#extension-schemas" class="tocxref"><span class="secno">A.3 </span>Extension Schemas</a></li></ul></li><li class="tocline"><a href="#changelog" class="tocxref"><span class="secno">B. </span>Change Log</a><ul class="toc"><li class="tocline"><a href="#changelog-last" class="tocxref"><span class="secno">B.1 </span>Changes since last version</a></li></ul></li><li class="tocline"><a href="#acknowledgements" class="tocxref"><span class="secno">C. </span>Acknowledgements</a></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">D. </span>References</a><ul class="toc"><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">D.1 </span>Informative references</a></li></ul></li></ul></section>
-<!-- end abstract -->
-
-
-
-<!-- end sotd -->
-
-
-<section id="introduction">
-
-<!--OddPage-->
-<h2><span class="secno">1. </span>Introduction</h2>
-
-<p>
-For the purpose of this specification, <dfn id="dfn-provenance" class="internalDFN">provenance</dfn><sup><a class="internalDFN" href="#dfn-provenance"><span class="diamond"> â—Š</span></a></sup> is defined as a record that describes the people, institutions, entities, and activities involved in producing, influencing, or delivering a piece of data or a thing. In particular, the provenance of information is crucial in deciding whether information is to be trusted, how it should be integrated with other diverse information sources, and how to give credit to its originators when reusing it. In an open and inclusive environment such as the Web, where users find information that is often contradictory or questionable, provenance can help those users to make trust judgements.
-</p>
-
-<p>
-The PROV data model, PROV-DM, presents a generic data model for provenance that allows domain and application specific representations of provenance to be translated into such a data model and <em>interchanged</em> between systems. Thus, heterogeneous systems can export their native provenance into such a core data model, and applications that need to make sense of provenance can then import it,
-process it, and reason over it.</p>
-
-<p>
-The PROV data model distinguishes <em>core structures</em> from <em>extended structures</em>: core structures form the essence of provenance information, and are commonly found in various domain-specific vocabularies that deal with provenance or similar kinds of information [<cite><a class="bibref" href="#bib-Mappings">Mappings</a></cite>]. Extended structures enhance and refine core structures with more expressive capabilities to cater for more advanced uses of provenance. The PROV data model, comprising both core and extended structures, is a domain-agnostic model, but with clear extensibility points allowing further domain-specific and application-specific extensions to be defined.
-</p>
-
-<p>
-The PROV data model has a modular design and is structured according to six components covering various facets of provenance:</p>
-<ul>
-<li> component 1: entities and activities, and the time at which they were created, used, or ended;
-</li><li> component 2: derivations of entities from others;
-</li><li> component 3: agents bearing responsibility for entities that were generated and activities that happened;
-</li><li> component 4: bundles, a mechanism to support provenance of provenance;
-</li><li> component 5: properties to link entities that refer to a same thing;
-</li><li> component 6: collections forming a logical structure for its members.
-</li></ul>
-
-<p>
-This specification goal is to provide a succinct definition of the XML form of PROV-DM, thus, we refer the reader to the PROV-DM to provide overall justification and context to the definitions presented here.
-</p>
-
-<section id="prov-namespace">
-<h3><span class="secno">1.1 </span>PROV Namespace</h3>
-<p>The PROV namespace is <span class="name">http://www.w3.org/ns/prov#</span>.</p>
-<p> All the concepts, reserved names and attributes introduced in this specification belong to the PROV namespace.</p>
-</section>
-<!-- end prov-namespace -->
-
-
-<section id="conventions">
-<h3><span class="secno">1.2 </span>Conventions</h3>
-
-<p>The key words "<em class="rfc2119" title="MUST">MUST</em>", "<em class="rfc2119" title="MUST NOT">MUST NOT</em>", "<em class="rfc2119" title="REQUIRED">REQUIRED</em>", "<em class="rfc2119" title="SHALL">SHALL</em>", "<em class="rfc2119" title="SHALL
- NOT">SHALL
- NOT</em>", "<em class="rfc2119" title="SHOULD">SHOULD</em>", "<em class="rfc2119" title="SHOULD NOT">SHOULD NOT</em>", "<em class="rfc2119" title="RECOMMENDED">RECOMMENDED</em>", "<em class="rfc2119" title="MAY">MAY</em>", and
- "<em class="rfc2119" title="OPTIONAL">OPTIONAL</em>" in this document are to be interpreted as described in
- [<cite><a class="bibref" href="#bib-RFC2119">RFC2119</a></cite>].</p>
-</section>
-<!-- end conventions -->
-
-
-</section>
-<!-- end introduction -->
-
-
-<section id="schema-design">
-
-<!--OddPage-->
-<h2><span class="secno">2. </span>XML Schema Design</h2>
-
-<p>Several general design principles and patterns were used in the construction of the PROV XML Schema.</p>
-
-<section id="schema-modularization">
-<h3><span class="secno">2.1 </span>Schema Modularization</h3>
-<p>The PROV-XML schema have been modularized so that extension elements defined in Working Group Notes can be defined in separate schemas. Elements corresponding to terms defined in the PROV-DM are defined in the <b>prov-core.xsd</b> schema and elements corresponding to terms defined in notes are defined in extension schemas (e.g. <b>prov-dictionary.xsd</b>, <b>prov-links.xsd</b>). The default schema, <b>prov.xsd</b>, imports <b>prov-core.xsd</b> and all extension schemas developed by the Working Group. With this modeling all PROV elements, even those defined in Notes, are defined from the default schema. If the user wishes to leverage a schema that does not include extension elements the user can use schemaLocation to directly reference <b>prov-core.xsd</b>.</p>
-<p>The default schema - <b>prov.xsd</b></p>
-<pre><?xml version="1.0" encoding="utf-8"?>
-<xs:schema targetNamespace="http://www.w3.org/ns/prov#"
- xmlns:xs="http://www.w3.org/2001/XMLSchema"
- xmlns:prov="http://www.w3.org/ns/prov#"
- elementFormDefault="qualified"
- attributeFormDefault="unqualified">
-
- <xs:include schemaLocation="prov-core.xsd"/>
- <xs:include schemaLocation="extensions/prov-dictionary.xsd"/>
- <xs:include schemaLocation="extensions/prov-links.xsd"/>
-
-</xs:schema>
-</pre>
-<p>Extension schemas import the <b>prov-core.xsd</b> schema and make use of a substitution group on the <code>prov:internalElement</code> to add extension-defined elements to the list of valid PROV elements in a bundle or document.</p>
-<p>The <b>prov-links.xsd</b> extension schema.</p>
-<pre><?xml version="1.0" encoding="UTF-8"?>
-<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
- targetNamespace="http://www.w3.org/ns/prov#" xmlns:prov="http://www.w3.org/ns/prov#"
- elementFormDefault="qualified">
-
- <xs:include schemaLocation="../prov-core.xsd" />
-
- <xs:complexType name="Mention">
- <xs:sequence>
- <xs:element name="specificEntity" type="prov:IDRef" />
- <xs:element name="generalEntity" type="prov:IDRef" />
- <xs:element name="bundle" type="prov:IDRef" />
- </xs:sequence>
- </xs:complexType>
-
- <xs:element name="mentionOf" type="prov:Mention" substitutionGroup="prov:internalElement" />
-
-</xs:schema>
-</pre>
-<p>All schemas developed by the PROV WG utilize the PROV namespace.</p>
-</section>
-<!-- end schema-modularization -->
-
-
-<section id="design-pattern">
-<h3><span class="secno">2.2 </span><i>Salami Slice</i> Design Pattern</h3>
-<p>The general design pattern for the XML schema has been called <i>Salami Slice Design</i> (cite?). With this design, the individual components are each defined at the top level as separate elements with distinct types. This allows the types to be easily reusable for domain specific extensions.</p>
-<p>The <code>prov:document</code> element has been defined to act as a convenient root element for a PROV-XML document, but it's use as the root element is not required. The schema follows the Salami Slice pattern to ensure PROV XML elements can be integrated with mixed-schema XML documents which require a different document root.</p>
-</section>
-<!-- end design-pattern -->
-
-
-<section id="elements-vs-attributes">
-<h3><span class="secno">2.3 </span>Elements vs. Attributes</h3>
-
-<p>The general PROV-N syntax patterns for expressing provenance
-concepts are:
-</p>
-
-<pre class="codeexample">thing(id, elem1, elem2, ..., [attr1=val1, attr2=val2])
-concept(id; elem1, elem2, ... [attr1=val2, attr2=val2])
-</pre>
-
-<p>In both cases (required id or optional id), the PROV-N id is treated as an XML attribute (<code>prov:id</code>), the PROV-N "elements" are treated as XML elements, always with the same required order (position) as the PROV-DM/PROV-N description, and optional PROV-N "attributes", if allowed, always follow and are also represented by XML elements. As in PROV-N, the attributes can be specified multiple times, but unlike PROV-N the attributes have a fixed (alphabetical) order. The PROV-N "attribute" elements are always defined at the end of the encompassing sequence after all PROV-N "elements". Elements defined in namespaces other than the PROV namespace may be included in a element after all PROV elements.</p>
-
-<p>Wherever an "id" is referenced from a later concept, the id is
-referenced as a prov:ref attribute of the element within the concept.
-</p>
-
-<p>This transformation technique yields a general XML pattern:
-</p>
-
-<pre class="codeexample"><prov:thing prov:id="id">
- <prov:elem1 />
- <prov:elem2 />
- ...
- <ex:attr1>val1</ex:attr1>
- <ex:attr2>val2</ex:attr2>
- ...
-</prov:thing>
-</pre>
-<p>Most of the concepts described below follow this general pattern.</p>
-</section>
-<!-- end elements-vs-attributes -->
-
-
-<section id="type-conventions">
-<h3><span class="secno">2.4 </span>Type Conventions</h3>
-<section id="type-conventions-attributes">
-<h4><span class="secno">2.4.1 </span>PROV Type Attribute</h4>
-<p>The PROV-DM states that type information is described using a the prov:type PROV attribute with and may occur multiple times for a given entity, activity, agent, or relation.</p>
-<p>PROV-XML uses the element <code>prov:type</code> to represent the prov:type PROV attribute. This element can be use to represent both PROV and non-PROV type information. The following examples shows type information encoded using the <code>prov:type</code> element.</p>
-<div class="example"><div class="example-title"><span>Example 1</span>: type information using prov:type PROV attribute</div><pre class="example" ignore=""><prov:document
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xmlns:xsd="http://www.w3.org/2001/XMLSchema"
- xmlns:prov="http://www.w3.org/ns/prov#"
- xmlns:ex="http://example.com/ns/ex#"
- xmlns:tr="http://example.com/ns/tr#">
-
- <prov:entity prov:id="tr:WD-prov-dm-20111215">
- <prov:type xsi:type="xsd:QName">prov:Plan</prov:type>
- <prov:type xsi:type="xsd:QName">ex:Workflow</prov:type>
- </prov:entity>
-
-</prov:document></pre></div>
-<p>The <code>prov:type</code> element is the only mechanism to explicitly declare multiple types for an instance or declare types that are not derived from the default element type. The <code>prov:type</code> element can be used in conjunction with schema-defined PROV types (see examples 2-5).</p>
-</section>
-<!-- end type-conventions-attributes -->
-
-<section id="type-conventions-extension-types">
-<h4><span class="secno">2.4.2 </span>Extension Types</h4>
-<p>PROV-XML defines complexTypes to match the PROV defined type values. These types provide a more native XML representation of PROV types. The following example is considered equivalent to the previous example because the element <code>prov:plan</code> has type <code>prov:Plan</code>. All complexTypes representing a PROV type which is defined as a subclass of another PROV type are defined in PROV-XML as extensions of their parent PROV type's complexType. For example, <code>prov:Plan</code> is defined as an extension of the complexType <code>prov:Entity</code> and may be referenced by either <code>prov:plan</code> or <code>prov:entity</code>.</p>
-<div class="example"><div class="example-title"><span>Example 2</span>: type information using schema defined types</div><pre class="example" ignore=""><prov:document
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xmlns:xsd="http://www.w3.org/2001/XMLSchema"
- xmlns:prov="http://www.w3.org/ns/prov#"
- xmlns:ex="http://example.com/ns/ex#"
- xmlns:tr="http://example.com/ns/tr#">
-
- <prov:plan prov:id="tr:WD-prov-dm-20111215">
- <prov:type xsi:type="xsd:QName">ex:Workflow</prov:type>
- </prov:plan>
-
-</prov:document></pre></div>
-<p>When an extended type is used a PROV type attribute relation may be inferred for the current and any parent type of the declared type.</p>
-<p>Stating all type information using the PROV type attribute assists in interoperability with non-PROV-XML encoding of PROV.</p>
-<div class="example"><div class="example-title"><span>Example 3</span>: type information using schema defined types - type inferences</div><pre class="example" ignore=""><prov:document
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xmlns:xsd="http://www.w3.org/2001/XMLSchema"
- xmlns:prov="http://www.w3.org/ns/prov#"
- xmlns:ex="http://example.com/ns/ex#"
- xmlns:tr="http://example.com/ns/tr#">
-
- <prov:plan prov:id="tr:WD-prov-dm-20111215">
- <prov:type xsi:type="xsd:QName">ex:Workflow</prov:type>
- <b><prov:type>prov:Plan</prov:type> <!-- inferred --></b>
- <b><prov:type>prov:Entity</prov:type> <!-- inferred --></b>
- </prov:plan>
-
-</prov:document></pre></div>
-</section>
-<!-- end-type-conventions-extension-types -->
-
-<section id="type-conventions-xsi-type">
-<h4><span class="secno">2.4.3 </span>XSI Type</h4>
-<p>Because the <code>prov:Plan</code> complexType is defined as an extension of the complexType <code>prov:Entity</code>, the following example using <code>xsi:type</code> is valid and considered equivalent to the two previous examples. The attribute <code>xsi:type</code> tells an XML parser the complexType of the element. The value of <code>xsi:type</code> must be a complexType derived from the default element type.</p>
-<div class="example"><div class="example-title"><span>Example 4</span>: type information using xsi:type</div><pre class="example" ignore=""><prov:document
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xmlns:xsd="http://www.w3.org/2001/XMLSchema"
- xmlns:prov="http://www.w3.org/ns/prov#"
- xmlns:ex="http://example.com/ns/ex#"
- xmlns:tr="http://example.com/ns/tr#">
-
- <prov:entity prov:id="tr:WD-prov-dm-20111215" xsi:type="prov:Plan">
- <prov:type xsi:type="xsd:QName">ex:Workflow</prov:type>
- </prov:entity>
-
-</prov:document></pre></div>
-<p>A PROV type attribute relation may be inferred by the use of the <code>xsi:type</code> XML attribute.</p>
-<div class="example"><div class="example-title"><span>Example 5</span>: type information using xsi:type - type inferences</div><pre class="example" ignore=""><prov:document
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xmlns:xsd="http://www.w3.org/2001/XMLSchema"
- xmlns:prov="http://www.w3.org/ns/prov#"
- xmlns:ex="http://example.com/ns/ex#"
- xmlns:tr="http://example.com/ns/tr#">
-
- <prov:entity prov:id="tr:WD-prov-dm-20111215" xsi:type="prov:Plan">
- <prov:type xsi:type="xsd:QName">ex:Workflow</prov:type>
- <b><prov:type>prov:Plan</prov:type> <!-- inferred --></b>
- <b><prov:type>prov:Entity</prov:type> <!-- inferred --></b>
- </prov:entity>
-
-</prov:document></pre></div>
-</section>
-<!-- end type-conventions-xsi-type -->
-
-
-</section>
-
-<section id="naming-conventions">
-<h3><span class="secno">2.5 </span>Naming Conventions</h3>
-<p>Element names are aligned with [<cite><a class="bibref" href="#bib-PROV-N">PROV-N</a></cite>] record names (e.g. <code>prov:wasGeneratedBy</code>, <code>prov:actedOnBehalfOf</code>) and record parameter roles (e.g. <code>prov:delegate</code>, <code>prov:responsible</code> on a Delegation). Elements are named in camelCase which also conforms with [<cite><a class="bibref" href="#bib-PROV-N">PROV-N</a></cite>] naming conventions.</p>
-<p>ComplexType names are aligned with [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>] type names (e.g. <code>prov:Generation</code>, <code>prov:Delegation</code>). ComplexTypes are named in PascalCase which conforms to [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>] naming conventions and differentiates complexTypes from elements in the schema.</p>
-</section>
-<!-- end naming-conventions -->
-
-
-</section>
-<!-- end schema-design -->
-
-
-<section id="schema-components">
-
-<!--OddPage-->
-<h2><span class="secno">3. </span>PROV XML Schema</h2>
-
-<p>Provenance concepts, expressed as PROV-DM types and relations, are organized according to six components that are defined in this section.</p>
-
-<div id="prov-dm-components-ul">
-<ul>
-<li><b>Component 1: entities and activities.</b> The first component consists of entities, activities, and concepts linking them, such as generation, usage, start, end. The first component is the only one comprising time-related concepts. </li>
-<li><b>Component 2: derivations.</b> The second component is formed with derivations and derivation subtypes.</li>
-<li><b>Component 3: agents, responsibility, and influence.</b> The third component consists of agents and concepts ascribing responsibility to agents.</li>
-<li><b>Component 4: bundles.</b> The fourth component is concerned with bundles, a mechanism to support provenance of provenance.</li>
-<li><b>Component 5: alternate.</b> The fifth component consists of relations linking entities referring to the same thing. </li>
-<li><b>Component 6: collections.</b> The sixth component is about collections. </li>
-</ul>
-</div>
-
-<div style="text-align: center;">
-<span class="figure" id="fig-agents-responsibility"><span class="figure" id="fig-figure-1-prov-dm-components-informative" style="max-width: 95%; ">
-<img usemap="#componentMap" src="images/dm/components-dependencies.png" alt="PROV-DM Components" style="max-width: 90%; " />
-<map id="componentMap" name="componentMap">
-<area title="agents/responsibility" href="#component3" coords="0,0,67,268" alt="agents/responsibility" shape="rect" />
-<area title="agents/responsibility" href="#component3" coords="67,0,134,201" alt="agents/responsibility" shape="rect" />
-<area title="agents/responsibility" href="#component3" coords="134,0,201,67" alt="agents/responsibility" shape="rect" />
-<area title="derivations" href="#component2" coords="201,0,268,201" alt="derivations" shape="rect" />
-<area title="derivations" href="#component2" coords="134,67,201,201" alt="derivations" shape="rect" />
-<area title="alternate" href="#component5" coords="335,0,402,201" alt="alternate" shape="rect" />
-<area title="collections" href="#component6" coords="402,0,469,201" alt="collections" shape="rect" />
-<area title="activities/entities" href="#component1" coords="67,201,469,268" alt="activities/entities" shape="rect" />
-<area title="bundles" href="#component4" coords="268,0,402,201" alt="bundles" shape="rect" />
-</map>
-<br />
-<span class="figcaption" id="prov-dm-components">Figure 1<sup><a class="internalDFN" href="#prov-dm-components"><span class="diamond"> â—Š:</span></a></sup> PROV-DM Components (Informative)</span>
-</span><figcaption>Fig. <span class="figno">1</span> <span class="fig-title">agents/responsibility</span></figcaption></span>
-</div>
-
-<p><a href="#prov-schema-mapping">Table 1</a> is a mapping of PROV-DM types and relations in PROV-XML schema XML types and elements.</p>
-
-<div id="prov-schema-mapping-div" style="text-align: center;">
-<table class="thinborder" style="margin-left: auto; margin-right: auto;">
-<caption id="prov-schema-mapping"><span>Table 1<sup><a class="internalDFN" href="#prov-schema-mapping"><span class="diamond"> â—Š:</span></a></sup> </span><span>Table 1<sup><a class="internalDFN" href="#prov-schema-mapping"><span class="diamond"> â—Š:</span></a></sup> </span>PROV-DM Types and Relations to XML Schema Mapping</caption>
-<tbody><tr>
-<td><a><b>Type or Relation Name</b></a></td>
-<td><b>XML Schema ComplexType</b></td>
-<td><b>XML Schema Referencing Element</b></td>
-<td><b>Component</b></td></tr>
-<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
-
-<tr class="component1-color">
- <td><a class="essential internalDFN" href="#concept-entity">Entity</a></td>
- <td>prov:Entity</td>
- <td>prov:entity</td>
- <td rowspan="8"><a href="#component1">Component 1: Entities/Activities</a></td>
-</tr>
-<tr class="component1-color">
- <td><a class="essential internalDFN" href="#concept-activity">Activity</a></td>
- <td>prov:Activity</td>
- <td>prov:activity</td>
-</tr>
-<tr class="component1-color">
- <td><a class="essential internalDFN" href="#concept-generation">Generation</a></td>
- <td>prov:Generation</td>
- <td>prov:wasGeneratedBy</td>
-</tr>
-<tr class="component1-color">
- <td><a class="essential internalDFN" href="#concept-usage">Usage</a></td>
- <td>prov:Usage</td>
- <td>prov:used</td>
-</tr>
-<tr class="component1-color">
- <td><a class="essential internalDFN" href="#concept-communication">Communication</a></td>
- <td>prov:Communication</td>
- <td>prov:wasInformedBy</td>
-</tr>
-<tr class="component1-color">
- <td><a class="essential internalDFN" href="#concept-start">Start</a></td>
- <td>prov:Start</td>
- <td>prov:wasStartedBy</td>
-</tr>
-<tr class="component1-color">
- <td><a class="essential internalDFN" href="#concept-end">End</a></td>
- <td>prov:End</td>
- <td>prov:wasEndedBy</td>
-</tr>
-<tr class="component1-color">
- <td><a class="essential internalDFN" href="#concept-invalidation">Invalidation</a></td>
- <td>prov:Invalidation</td>
- <td>prov:wasInvalidatedBy</td>
-</tr>
-<tr>
- <td colspan="3" style="border-width: 0px; "></td>
-</tr>
-<tr class="component2-color">
- <td><a class="essential internalDFN" href="#concept-derivation">Derivation</a></td>
- <td>prov:Derivation</td>
- <td>prov:wasDerivedFrom</td>
- <td rowspan="4"><a href="#component2">Component 2: Derivations</a></td>
-</tr>
-<tr class="component2-color">
- <td><a class="essential internalDFN" href="#concept-revision">Revision</a></td>
- <td>prov:Revision</td>
- <td>prov:wasRevisionOf</td>
-</tr>
-<tr class="component2-color">
- <td><a class="essential internalDFN" href="#concept-quotation">Quotation</a></td>
- <td>prov:Quotation</td>
- <td>prov:wasQuotedFrom</td>
-</tr>
-<tr class="component2-color">
- <td><a class="essential internalDFN" href="#concept-primary-source">Primary Source</a></td>
- <td>prov:PrimarySource</td>
- <td>prov:hadPrimarySource</td>
-</tr>
-<tr>
- <td colspan="3" style="border-width: 0px; "></td>
-</tr>
-<tr class="component3-color" style="border-collapse: collapse; ">
- <td><a class="essential internalDFN" href="#concept-agent">Agent</a></td>
- <td>prov:Agent</td>
- <td>prov:agent</td>
- <td rowspan="9"><a href="#component3">Component 3: Agents, Responsibility, Influence</a></td>
-</tr>
-<tr class="component3-color">
- <td><a class="essential internalDFN" href="#concept-attribution">Attribution</a></td>
- <td>prov:Attribution</td>
- <td>prov:wasAttributedTo</td>
-</tr>
-<tr class="component3-color">
- <td><a class="essential internalDFN" href="#concept-association">Association</a></td>
- <td>prov:Association</td>
- <td>prov:wasAssociatedWith</td>
-</tr>
-<tr class="component3-color">
- <td><a class="essential internalDFN" href="#concept-delegation">Delegation</a></td>
- <td>prov:Delegation</td>
- <td>prov:actedOnBehalfOf</td>
-</tr>
-<tr class="component3-color">
- <td><a class="essential internalDFN" href="#concept-plan">Plan</a></td>
- <td>prov:Plan</td>
- <td>prov:plan</td>
-</tr>
-<tr class="component3-color">
- <td><a class="essential internalDFN" href="#concept-person">Person</a></td>
- <td>prov:Person</td>
- <td>prov:person</td>
-</tr>
-<tr class="component3-color">
- <td><a class="essential internalDFN" href="#concept-organization">Organization</a></td>
- <td>prov:Organization</td>
- <td>prov:organization</td>
-</tr>
-<tr class="component3-color">
- <td><a class="essential">Software Agent</a></td>
- <td>prov:SoftwareAgent</td>
- <td>prov:softwareAgent</td>
-</tr>
-<tr class="component3-color">
- <td><a class="essential internalDFN" href="#concept-influence">Influence</a></td>
- <td>prov:Influence</td>
- <td>prov:wasInfluencedBy</td>
-</tr>
-<tr>
- <td colspan="3" style="border-width: 0px; "></td>
-</tr>
-<tr class="component4-color">
- <td><a class="essential internalDFN" href="#concept-bundle">Bundle</a></td>
- <td>prov:Bundle</td>
- <td>prov:bundle</td>
- <td rowspan="2"><a href="#component5">Component 4: Bundles</a></td>
-</tr>
-<tr class="component4-color">
- <td><a class="essential">Bundle Constructor</a></td>
- <td>prov:BundleConstructor</td>
- <td>prov:bundleContent</td>
-</tr>
-<tr>
- <td colspan="3" style="border-width: 0px; "></td>
-</tr>
-<tr class="component5-color">
- <td><a class="essential internalDFN" href="#concept-alternate">Alternate</a></td>
- <td>prov:Alternate</td>
- <td>prov:alternateOf</td>
- <td rowspan="3"><a href="#component4">Component 5: Alternate</a></td>
-</tr>
-<tr class="component5-color">
- <td><a class="essential internalDFN" href="#concept-specialization">Specialization</a></td>
- <td>prov:Specialization</td>
- <td>prov:specializationOf</td>
-</tr>
-<tr>
- <td colspan="3" style="border-width: 0px; "></td>
-</tr>
-<tr class="component6-color">
- <td><a class="essential internalDFN" href="#concept-collection">Collection</a></td>
- <td>prov:Collection</td>
- <td>prov:collection</td>
- <td rowspan="3"><a href="#component6">Component 6: Collections</a></td>
-</tr>
-<tr class="component6-color">
- <td><a class="essential internalDFN" href="#concept-empty-collection">Empty Collection</a></td>
- <td>prov:EmptyCollection</td>
- <td>prov:emptyCollection</td>
-</tr>
-<tr class="component6-color">
- <td><a class="essential internalDFN" href="#concept-membership">Membership</a></td>
- <td>prov:Membership</td>
- <td>prov:hadMember</td>
-</tr>
-</tbody></table>
-</div>
-
-<p>In the rest of the section, each type is defined, in English initially, followed by its XML schema definition and some example.</p>
-
-<section id="component1">
-<h3><span class="secno">3.1 </span>Component 1: Entities and Activities</h3>
-
-<p>The first component of PROV-DM is concerned with <a title="entity">entities</a> and <a title="activity">activities</a>, and their inter-relations: <a href="#concept-usage" class="internalDFN">Usage</a>, <a href="#concept-generation" class="internalDFN">Generation</a>, <a href="#concept-start" class="internalDFN">Start</a>, <a href="#concept-end" class="internalDFN">End</a>, and <a href="#concept-communication" class="internalDFN">Communication</a>. </p>
-
-<section id="term-Entity">
-<h4><span class="secno">3.1.1 </span>Entity</h4>
-<span class="glossary-ref"> An <span class="dfn">entity</span> is a physical, digital, conceptual, or other kind of thing with some fixed aspects; entities may be real or imaginary. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Entity">
- <xs:sequence>
- <!-- prov attributes -->
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:location" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:value" minOccurs="0"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
-</xs:complexType>
-</pre>
-<p>The element <code>prov:entity</code> is used to reference a prov:Entity from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element" element="prov:entity" schematype="prov:Entity"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="entity" type="prov:Entity"/>
-</pre>
-<div class="example"><div class="example-title"><span>Example 6</span>: prov:entity</div><pre class="example"><prov:document
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xmlns:xsd="http://www.w3.org/2001/XMLSchema"
- xmlns:prov="http://www.w3.org/ns/prov#"
- xmlns:ex="http://example.com/ns/ex#"
- xmlns:tr="http://example.com/ns/tr#">
-
- <b><prov:entity prov:id="tr:WD-prov-dm-20111215">
- <prov:type xsi:type="xsd:QName">document</prov:type>
- <ex:version>2</ex:version>
- </prov:entity></b>
-
-</prov:document></pre></div>
-</section>
-<!-- end term-Entity -->
-
-
-<section id="term-Activity">
-<h4><span class="secno">3.1.2 </span>Activity</h4>
-<span class="glossary-ref"> An <span class="dfn">activity</span> is something that occurs over a period of time and acts upon or with entities; it may include consuming, processing, transforming, modifying, relocating, using, or generating entities. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Activity">
- <xs:sequence>
- <xs:element name="startTime" type="xs:dateTime" minOccurs="0"/>
- <xs:element name="endTime" type="xs:dateTime" minOccurs="0"/>
- <!-- prov attributes -->
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:location" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
-</xs:complexType>
-</pre>
-<p>The element <code>prov:activity</code> is used to reference a prov:Activity from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element" element="prov:activity" schematype="prov:Activity"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="activity" type="prov:Activity"/>
-</pre>
-<div class="example"><div class="example-title"><span>Example 7</span>: prov:activity</div><pre class="example"><prov:document
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xmlns:xsd="http://www.w3.org/2001/XMLSchema"
- xmlns:prov="http://www.w3.org/ns/prov#"
- xmlns:ex="http://example.com/ns/ex#">
-
- <b><prov:activity prov:id="a1">
- <prov:startTime>2011-11-16T16:05:00</prov:startTime>
- <prov:endTime>2011-11-16T16:06:00</prov:endTime>
- <prov:type xsi:type="xsd:QName">ex:edit</prov:type>
- <ex:host>server.example.org</ex:host>
- </prov:activity></b>
-
-</prov:document></pre></div>
-</section>
-<!-- end term-Activity -->
-
-
-<section id="term-Generation">
-<h4><span class="secno">3.1.3 </span>Generation</h4>
-<span class="glossary-ref"> <span class="dfn">Generation</span> is the completion of production of a new entity by an activity. This entity did not exist before generation and becomes available for usage after this generation. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Generation">
- <xs:sequence>
- <xs:element name="entity" type="prov:IDRef"/>
- <xs:element name="activity" type="prov:IDRef" minOccurs="0"/>
- <xs:element name="time" type="xs:dateTime" minOccurs="0"/>
- <!-- prov attributes -->
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:location" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:role" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
-</xs:complexType>
-</pre>
-<p>The element <code>prov:wasGeneratedBy</code> is used to reference a prov:Generation from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element" element="prov:wasGeneratedBy" schematype="prov:Generation"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasGeneratedBy" type="prov:Generation"/>
-</pre>
-<div class="example"><div class="example-title"><span>Example 8</span>: prov:wasGeneratedBy</div><pre class="example"><prov:document
- xmlns:prov="http://www.w3.org/ns/prov#"
- xmlns:ex="http://example.com/ns/ex#">
-
- <prov:entity prov:id="e1"/>
-
- <prov:activity prov:id="a1"/>
-
- <b><prov:wasGeneratedBy>
- <prov:entity prov:ref="e1"/>
- <prov:activity prov:ref="a1"/>
- <prov:time>2001-10-26T21:32:52</prov:time>
- <ex:port>p1</ex:port>
- </prov:wasGeneratedBy></b>
-
- <prov:entity prov:id="e2"/>
-
- <b><prov:wasGeneratedBy>
- <prov:entity prov:ref="e2"/>
- <prov:activity prov:ref="a1"/>
- <prov:time>2001-10-26T10:00:00</prov:time>
- <ex:port>p2</ex:port>
- </prov:wasGeneratedBy></b>
-
-</prov:document></pre></div>
-</section>
-<!-- end term-Generation -->
-
-
-<section id="term-Usage">
-<h4><span class="secno">3.1.4 </span>Usage</h4>
-<span class="glossary-ref"> <span class="dfn">Usage</span> is the beginning of utilizing an entity by an activity. Before usage, the activity had not begun to utilize this entity and could not have been affected by the entity. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Usage">
- <xs:sequence>
- <xs:element name="activity" type="prov:IDRef"/>
- <xs:element name="entity" type="prov:IDRef" minOccurs="0"/>
- <xs:element name="time" type="xs:dateTime" minOccurs="0"/>
- <!-- prov attributes -->
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:location" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:role" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
-<xs:attribute ref="prov:id"/>
-</xs:complexType>
-</pre>
-<p>The element <code>prov:used</code> is used to reference a prov:Usage from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element" element="prov:used" schematype="prov:Usage"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="used" type="prov:Usage"/>
-</pre>
-<div class="example"><div class="example-title"><span>Example 9</span>: prov:used</div><pre class="example"><prov:document
- xmlns:prov="http://www.w3.org/ns/prov#"
- xmlns:ex="http://example.com/ns/ex#">
-
- <prov:activity prov:id="a1"/>
-
- <prov:entity prov:id="e1"/>
-
- <prov:entity prov:id="e2"/>
-
- <b><prov:used>
- <prov:activity prov:ref="a1"/>
- <prov:entity prov:ref="e1"/>
- <prov:time≶2011-11-16T16:00:00</prov:time>
- <ex:parameter>p1</ex:parameter>
- </prov:used></b>
-
- <b><prov:used>
- <prov:activity prov:ref="a1"/>
- <prov:entity prov:ref="e2"/>
- <prov:time>2011-11-16T16:00:01</prov:time>
- <ex:parameter>p2</ex:parameter>
- </prov:used></b>
-
-</prov:document></pre></div>
-</section>
-<!-- end term-Usage -->
-
-
-<section id="term-Communication">
-<h4><span class="secno">3.1.5 </span>Communication</h4>
-<span class="glossary-ref"> <span class="dfn">Communication</span> is the exchange of some unspecified entity by two activities, one activity using some entity generated by the other. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Communication">
- <xs:sequence>
- <xs:element name="informed" type="prov:IDRef"/>
- <xs:element name="informant" type="prov:IDRef"/>
- <!-- prov attributes -->
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
-</xs:complexType>
-</pre>
-<p>The element <code>prov:wasInformedBy</code> is used to reference a prov:Communication from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element" element="prov:wasInformedBy" schematype="prov:Communication"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasInformedBy" type="prov:Communication"/>
-</pre>
-<div class="example"><div class="example-title"><span>Example 10</span>: prov:wasInformedBy</div><pre class="example"><prov:document
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xmlns:xsd="http://www.w3.org/2001/XMLSchema"
- xmlns:prov="http://www.w3.org/ns/prov#">
-
- <prov:activity prov:id="a1">
- <prov:type xsi:type="xsd:string">traffic regulations enforcing<prov:type>
- </prov:activity>
-
- <prov:activity prov:id="a2">
- <prov:type xsi:type="xsd:string">fine paying, check writing, and mailing</prov:type>
- </prov:activity>
-
- <b><prov:wasInformedBy>
- <prov:informed prov:ref="a2"/>
- <prov:informant prov:ref="a1"/>
- </prov:wasInformedBy></b>
-
-</prov:document></pre></div>
-</section>
-<!-- end term-Communication -->
-
-
-<section id="term-Start">
-<h4><span class="secno">3.1.6 </span>Start</h4>
-<span class="glossary-ref"> <span class="dfn">Start</span> is when an activity is deemed to have been started by an entity, known as <span class="dfn">trigger</span>. The activity did not exist before its start. Any usage, generation, or invalidation involving an activity follows the activity's start. A start may refer to a trigger entity that set off the activity, or to an activity, known as <span class="dfn">starter</span>, that generated the trigger. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Start">
- <xs:sequence>
- <xs:element name="activity" type="prov:IDRef"/>
- <xs:element name="trigger" type="prov:IDRef" minOccurs="0"/>
- <xs:element name="starter" type="prov:IDRef" minOccurs="0"/>
- <xs:element name="time" type="xs:dateTime" minOccurs="0"/>
- <!-- prov attributes -->
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:location" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:role" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
-</xs:complexType>
-</pre>
-<p>The element <code>prov:wasStartedBy</code> is used to reference a prov:Start from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element" element="prov:wasStartedBy" schematype="prov:Start"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasStartedBy" type="prov:Start"/>
-</pre>
-<div class="example"><div class="example-title"><span>Example 11</span>: prov:wasStartedBy</div><pre class="example"><prov:document
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xmlns:xsd="http://www.w3.org/2001/XMLSchema"
- xmlns:prov="http://www.w3.org/ns/prov#"
- xmlns:ex="http://example.com/ns/ex#">
-
- <prov:entity prov:id="e1">
- <prov:type xsi:type="xsd:string">email message</prov:type>
- </prov:entity>
-
- <prov:activity prov:id="a1">
- <prov:type xsi:type="xsd:QName">Discuss</prov:type>
- </prov:activity>
-
- <b><prov:wasStartedBy>
- <prov:activity prov:ref="a1"/>
- <prov:trigger prov:ref="e1"/>
- <prov:time>2011-11-16T16:05:00</prov:time>
- </prov:wasStartedBy></b>
-
- <prov:used>
- <prov:activity prov:ref="a1"/>
- <prov:entity prov:ref="e1"/>
- </prov:used>
-
- <prov:activity prov:id="a0">
- <prov:type xsi:type="xsd:QName">Write</prov:type>
- </prov:activity>
-
- <prov:wasGeneratedBy>
- <prov:entity prov:ref="e1"/>
- <prov:activity prov:ref="a0"/>
- </prov:wasGeneratedBy>
-
- <b><prov:wasStartedBy>
- <prov:activity prov:ref="a1"/>
- <prov:trigger prov:ref="e1"/>
- <prov:starter prov:ref="a0"/>
- <prov:time>2011-11-16T16:05:00</prov:time>
- </prov:wasStartedBy></b>
-
- <b><prov:wasStartedBy>
- <prov:activity prov:ref="a1"/>
- <prov:starter prov:ref="a0"/>
- <prov:time>2011-11-16T16:05:00</prov:time>
- </prov:wasStartedBy></b>
-
-</prov:document></pre></div>
-</section>
-<!-- end term-Start -->
-
-
-<section id="term-End">
-<h4><span class="secno">3.1.7 </span>End</h4>
-<span class="glossary-ref"> <span class="dfn">End</span> is when an activity is deemed to have been ended by an entity, known as <span class="dfn">trigger</span>. The activity no longer exists after its end. Any usage, generation, or invalidation involving an activity precedes the activity's end. An end may refer to a trigger entity that terminated the activity, or to an activity, known as <span class="dfn">ender</span> that generated the trigger. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="End">
- <xs:sequence>
- <xs:element name="activity" type="prov:IDRef"/>
- <xs:element name="trigger" type="prov:IDRef" minOccurs="0"/>
- <xs:element name="ender" type="prov:IDRef" minOccurs="0"/>
- <xs:element name="time" type="xs:dateTime" minOccurs="0"/>
- <!-- prov attributes -->
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:location" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:role" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
-</xs:complexType>
-</pre>
-<p>The element <code>prov:wasEndedBy</code> is used to reference a prov:End from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element" element="prov:wasEndedBy" schematype="prov:End"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasEndedBy" type="prov:End"/>
-</pre>
-<div class="example"><div class="example-title"><span>Example 12</span>: prov:wasEndedBy</div><pre class="example"><prov:document
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xmlns:xsd="http://www.w3.org/2001/XMLSchema"
- xmlns:prov="http://www.w3.org/ns/prov#"
- xmlns:ex="http://example.com/ns/ex#">
-
- <prov:entity prov:id="e1">
- <prov:type xsi:type="xsd:string">approval document</prov:type>
- </prov:entity>
-
- <prov:activity prov:id="a1">
- <prov:type xsi:type="xsd:QName">Editing</prov:type>
- </prov:activity>
-
- <b><prov:wasEndedBy>
- <prov:activity prov:ref="a1"/>
- <prov:trigger prov:ref="e1"/>
- </prov:wasEndedBy></b>
-
-</prov:document></pre></div>
-</section>
-<!-- end term-End -->
-
-
-<section id="term-Invalidation">
-<h4><span class="secno">3.1.8 </span>Invalidation</h4>
-<span class="glossary-ref"> <span class="dfn">Invalidation</span> is the start of the destruction, cessation, or expiry of an existing entity by an activity. The entity is no longer available for use (or further invalidation) after invalidation. Any generation or usage of an entity precedes its invalidation.</span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Invalidation">
- <xs:sequence>
- <xs:element name="entity" type="prov:IDRef"/>
- <xs:element name="activity" type="prov:IDRef" minOccurs="0"/>
- <xs:element name="time" type="xs:dateTime" minOccurs="0"/>
- <!-- prov attributes -->
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:location" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:role" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
-</xs:complexType>
-</pre>
-<p>The element <code>prov:wasInvalidatedBy</code> is used to reference a prov:Invalidation from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element" element="prov:wasInvalidatedBy" schematype="prov:Invalidation"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasInvalidatedBy" type="prov:Invalidation"/>
-</pre>
-<div class="example"><div class="example-title"><span>Example 13</span>: prov:wasInvalidatedBy</div><pre class="example"><prov:document
- xmlns:prov="http://www.w3.org/ns/prov#"
- xmlns:ex="http://example.com/ns/ex#"
- xmlns:bbc="http://www.bbc.co.uk/news/">
-
- <prov:entity prov:id="ex:The-Painter"/>
-
- <prov:agent prov:id="ex:Picasso"/>
-
- <prov:wasAttributedTo>
- <prov:entity prov:ref="ex:The-Painter" />
- <prov:agent prov:ref="ex:Picasso" />
- </prov:wasAttributedTo>
-
- <prov:activity prov:id="ex:crash"/>
-
- <b><prov:wasInvalidatedBy>
- <prov:entity prov:ref="ex:The-Painter"/>
- <prov:activity prov:ref="ex:crash"/>
- <prov:time>1998-09-03T01:31:00</prov:time>
- <ex:circumstances>plane accident</ex:circumstances>
- </prov:wasInvalidatedBy></b>
-
-</prov:document></pre></div>
-</section>
-<!-- end term-Invalidation -->
-
-
-</section>
-<!-- end component1 -->
-
-
-<section id="component2">
-<h3><span class="secno">3.2 </span>Component 2: Derivations</h3>
-
-<p>The second component of PROV-DM is concerned with: <a title="derivation">derivations</a> of <a title="entity">entities</a> from other entities and derivation subtypes WasRevisionOf (<a href="#concept-revision" class="internalDFN">Revision</a>), WasQuotedFrom (<a href="#concept-quotation" class="internalDFN">Quotation</a>), and HasPrimarySource (<a href="#concept-primary-source" class="internalDFN">Primary Source</a>).</p>
-
-<section id="term-Derivation">
-<h4><span class="secno">3.2.1 </span>Derivation</h4>
-<span class="glossary-ref"> A <span class="dfn">derivation</span> is a transformation of an entity into another, an update of an entity resulting in a new one, or the construction of a new entity based on a pre-existing entity.</span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Derivation">
- <xs:sequence>
- <xs:element name="generatedEntity" type="prov:IDRef"/>
- <xs:element name="usedEntity" type="prov:IDRef"/>
- <xs:element name="activity" type="prov:IDRef" minOccurs="0"/>
- <xs:element name="generation" type="prov:IDRef" minOccurs="0"/>
- <xs:element name="usage" type="prov:IDRef" minOccurs="0"/>
- <!-- prov attributes -->
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
-</xs:complexType>
-</pre>
-<p>The element <code>prov:wasDerivedFrom</code> is used to reference a prov:Derivation from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element" element="prov:wasDerivedFrom" schematype="prov:Derivation"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasDerivedFrom" type="prov:Derivation"/>
-</pre>
-<div class="example"><div class="example-title"><span>Example 14</span>: prov:wasDerivedFrom</div><pre class="example"><prov:document
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xmlns:xsd="http://www.w3.org/2001/XMLSchema"
- xmlns:prov="http://www.w3.org/ns/prov#">
-
- <prov:entity prov:id="e1"/>
-
- <prov:entity prov:id="e2"/>
-
- <b><prov:wasDerivedFrom>
- <prov:generatedEntity prov:ref="e2"/>
- <prov:usedEntity prov:ref="e1"/>
- </prov:wasDerivedFrom></b>
-
- <b><prov:wasDerivedFrom>
- <prov:generatedEntity prov:ref="e2"/>
- <prov:usedEntity prov:ref="e1"/>
- <prov:type xsi:type="xsd:string">physical transform</prov:type>
- </prov:wasDerivedFrom></b>
-
-</prov:document></pre></div>
-</section>
-<!-- end term-Derivation -->
-
-
-<section id="term-Revision">
-<h4><span class="secno">3.2.2 </span>Revision</h4>
-<span class="glossary-ref"> A <span class="dfn">revision</span> is a derivation for which the resulting entity is a revised version of some original. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Revision">
- <xs:complexContent>
- <xs:extension base="prov:Derivation">
- </xs:extension>
- </xs:complexContent>
-</xs:complexType>
-</pre>
-<p>The element <code>prov:wasRevisionOf</code> is used to reference a prov:Revision from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element" element="prov:wasRevisionOf" schematype="prov:Revision"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasRevisionOf" type="prov:Revision"/>
-</pre>
-<div class="example"><div class="example-title"><span>Example 15</span>: prov:wasRevisionOf</div><pre class="example"><prov:document
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xmlns:xsd="http://www.w3.org/2001/XMLSchema"
- xmlns:prov="http://www.w3.org/ns/prov#"
- xmlns:rec54="http://www.w3.org/2001/02pd/rec54#"
- xmlns:tr="http://example.com/ns/tr#">
-
- <prov:entity prov:id="tr:WD-prov-dm-20111215">
- <prov:type xsi:type="xsd:QName">rec54:WD</prov:type>
- </prov:entity>
-
- <prov:entity prov:id="tr:WD-prov-dm-20111018">
- <prov:type xsi:type="xsd:QName">rec54:WD</prov:type>
- </prov:entity>
-
- <b><prov:wasRevisionOf>
- <prov:generatedEntity prov:ref="tr:WD-prov-dm-20111215"/>
- <prov:usedEntity prov:ref="tr:WD-prov-dm-20111018"/>
- </prov:wasRevisionOf></b>
-
-</prov:document></pre></div>
-</section>
-<!-- end term-Revision -->
-
-
-<section id="term-Quotation">
-<h4><span class="secno">3.2.3 </span>Quotation</h4>
-<span class="glossary-ref"> A <span class="dfn">quotation</span> is the repeat of (some or all of) an entity, such as text or image, by someone who may or may not be its original author. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Quotation">
- <xs:complexContent>
- <xs:extension base="prov:Derivation">
- </xs:extension>
- </xs:complexContent>
-</xs:complexType>
-</pre>
-<p>The element <code>prov:wasQuotedFrom</code> is used to reference a prov:Quotation from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element" element="prov:wasQuotedFrom" schematype="prov:Quotation"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasQuotedFrom" type="prov:Quotation"/>
-</pre>
-<div class="example"><div class="example-title"><span>Example 16</span>: prov:wasQuotedFrom</div><pre class="example"><prov:document
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xmlns:xsd="http://www.w3.org/2001/XMLSchema"
- xmlns:prov="http://www.w3.org/ns/prov#"
- xmlns:wp="http://thinklinks.wordpress.com/2012/03/07/"
- xmlns:ex="http://example.com/ns/ex#"
- xmlns:dm="http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html#">
-
- <prov:entity prov:id="wp:thoughts-from-the-dagstuhl-principles-of-provenance-workshop"/>
-
- <prov:entity prov:id="dm:bl-dagstuhl"/>
-
- <prov:person prov:id="ex:Luc"/>
-
- <prov:person prov:id="ex:Paul"/>
-
- <b><prov:wasQuotedFrom>
- <prov:generatedEntity prov:ref="dm:gl-dagstuhl"/>
- <prov:usedEntity prov:ref="wp:thoughts-from-the-dagstuhl-principles-of-provenance-workshop"/>
- </prov:wasQuotedFrom></b>
-
- <prov:wasAttributedTo>
- <prov:entity prov:ref="dm:bl-dagstuhl"/>
- <prov:agent prov:ref="ex:Luc"/>
- </prov:wasAttributedTo>
-
- <prov:wasAttributedTo>
- <prov:entity prov:ref="wp:thoughts-from-the-dagstuhl-principles-of-provenance-workshop"/>
- <prov:agent prov:ref="ex:Paul"/>
- </prov:wasAttributedTo>
-
-</prov:document></pre></div>
-</section>
-<!-- end term-Quotation -->
-
-
-<section id="term-Primary-Source">
-<h4><span class="secno">3.2.4 </span>Primary Source</h4>
-<span class="glossary-ref"> A <span class="dfn">primary source</span> for a topic refers to something produced by some agent with direct experience and knowledge about the topic, at the time of the topic's study, without benefit from hindsight. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="PrimarySource">
- <xs:complexContent>
- <xs:extension base="prov:Derivation">
- </xs:extension>
- </xs:complexContent>
-</xs:complexType>
-</pre>
-<p>The element <code>prov:hadPrimarySource</code> is used to reference a prov:PrimarySource from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element" element="prov:hadPrimarySource" schematype="prov:PrimarySource"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="hadPrimarySource" type="prov:PrimarySource"/>
-</pre>
-<div class="example"><div class="example-title"><span>Example 17</span>: prov:hadPrimarySource</div><pre class="example"><prov:document
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xmlns:xsd="http://www.w3.org/2001/XMLSchema"
- xmlns:prov="http://www.w3.org/ns/prov#"
- xmlns:ex="http://example.com/ns/ex#">
-
- <prov:entity prov:id="ex:la-campagne-de-Russie-1812-1813">
- <prov:type xsi:type="xsd:QName">map</prov:type>
- </prov:entity>
-
- <prov:entity prov:id="ex:revue-d-Histoire-de-la-Pharmacie-t-XVIII">
- <prov:type xsi:type="xsd:QName">journal</prov:type>
- </prov:entity>
-
- <b><prov:hadPrimarySource>
- <prov:generatedEntity prov:ref="ex:la-campagne-de-Russie-1812-1813"/>
- <prov:usedEntity prov:ref="ex:revue-d-Histoire-de-la-Pharmacie-t-XVIII"/>
- </prov:hadPrimarySource></b>
-
-</prov:document></pre></div>
-</section>
-<!-- end term-Primary-Source -->
-
-
-</section>
-<!-- end component2 -->
-
-
-<section id="component3">
-<h3><span class="secno">3.3 </span>Component 3: Agents, Responsibility, and Influence</h3>
-
-<p>The third component of PROV-DM is concerned with <a title="agent">agents</a> and the relations WasAttributedTo
-(<a href="#concept-attribution" class="internalDFN">Attribution</a>), WasAssociatedWith (<a href="#concept-association" class="internalDFN">Association</a>), ActedOnBehalfOf (<a href="#concept-delegation" class="internalDFN">Delegation</a>), relating agents to entities, activities, and agents, respectively.</p>
-
-<section id="term-Agent">
-<h4><span class="secno">3.3.1 </span>Agent</h4>
-<span class="glossary-ref"> An <span class="dfn">agent</span> is something that bears some form of responsibility for an activity taking place, for the existence of an entity, or for another agent's activity. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Agent">
- <xs:sequence>
- <!-- prov attributes -->
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:location" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
-</xs:complexType>
-</pre>
-<p>The element <code>prov:agent</code> is used to reference a prov:Agent from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element" element="prov:agent" schematype="prov:Agent"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="agent" type="prov:Agent"/>
-</pre>
-<div class="example"><div class="example-title"><span>Example 18</span>: prov:agent</div><pre class="example"><prov:document
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xmlns:xsd="http://www.w3.org/2001/XMLSchema"
- xmlns:prov="http://www.w3.org/ns/prov#"
- xmlns:ex="http://example.com/ns/ex#">
-
- <b><prov:agent prov:id="e1">
- <prov:type xsi:type="xsd:QName">prov:Person</prov:type>
- <ex:name>Alice</ex:name>
- <ex:employee>1234</ex:employee>
- </prov:agent></b>
-
-</prov:document></pre></div>
-
-<section id="term-Person">
-<h5><span class="secno">3.3.1.1 </span>Person</h5>
-<span class="glossary-ref"> Agents of type <span class="dfn">Person</span> are people. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Person">
- <xs:complexContent>
- <xs:extension base="prov:Agent">
- </xs:extension>
- </xs:complexContent>
-</xs:complexType>
-</pre>
-<p>The element <code>prov:person</code> is used to reference a prov:Person from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element" element="prov:person" schematype="prov:Person"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="person" type="prov:Person"/>
-</pre>
-<div class="example"><div class="example-title"><span>Example 19</span>: prov:person</div><pre class="example"><prov:document
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xmlns:xsd="http://www.w3.org/2001/XMLSchema"
- xmlns:prov="http://www.w3.org/ns/prov#"
- xmlns:ex="http://example.com/ns/ex#">
-
- <b><prov:person prov:id="ex:Paolo" /></b>
-
-</prov:document></pre></div>
-</section>
-<!-- end term-Person -->
-
-
-<section id="term-Organization">
-<h5><span class="secno">3.3.1.2 </span>Organization</h5>
-<span class="glossary-ref"> Agents of type <span class="dfn">Organization</span> are social or legal institutions such as companies, societies, etc. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Organization">
- <xs:complexContent>
- <xs:extension base="prov:Agent">
- </xs:extension>
- </xs:complexContent>
-</xs:complexType>
-</pre>
-<p>The element <code>prov:organization</code> is used to reference a prov:Organization from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element" element="prov:organization" schematype="prov:Organization"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="organization" type="prov:Organization"/>
-</pre>
-<div class="example"><div class="example-title"><span>Example 20</span>: prov:organization</div><pre class="example"><prov:document
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xmlns:xsd="http://www.w3.org/2001/XMLSchema"
- xmlns:prov="http://www.w3.org/ns/prov#"
- xmlns:ex="http://example.com/ns/ex#">
-
- <b><prov:organization prov:id="w3:Consortium" /></b>
-
-</prov:document></pre></div>
-</section>
-<!-- end term-Organization -->
-
-
-<section id="term-SoftwareAgent">
-<h5><span class="secno">3.3.1.3 </span>Software Agent</h5>
-<span class="glossary-ref"> A <span class="dfn">SoftwareAgent</span> is running software. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="SoftwareAgent">
- <xs:complexContent>
- <xs:extension base="prov:Agent">
- </xs:extension>
- </xs:complexContent>
-</xs:complexType>
-</pre>
-<p>The element <code>prov:softwareAgent</code> is used to reference a prov:SoftwareAgent from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element" element="prov:softwareAgent" schematype="prov:SoftwareAgent"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="softwareAgent" type="prov:SoftwareAgent"/>
-</pre>
-<div class="example"><div class="example-title"><span>Example 21</span>: prov:softwareAgent</div><pre class="example"><prov:document
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xmlns:xsd="http://www.w3.org/2001/XMLSchema"
- xmlns:prov="http://www.w3.org/ns/prov#"
- xmlns:ex="http://example.com/ns/ex#">
-
- <b><prov:softwareAgent prov:id="ag" /></b>
-
-</prov:document></pre></div>
-</section>
-<!-- end term-SoftwareAgent -->
-
-
-</section>
-<!-- end term-Agent -->
-
-
-<section id="term-Attribution">
-<h4><span class="secno">3.3.2 </span>Attribution</h4>
-<span class="glossary-ref"> <span class="dfn">Attribution</span> is the ascribing of an entity to an agent. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Attribution">
- <xs:sequence>
- <xs:element name="entity" type="prov:IDRef"/>
- <xs:element name="agent" type="prov:IDRef"/>
- <!-- prov attributes -->
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
-</xs:complexType>
-</pre>
-<p>The element <code>prov:wasAttributedTo</code> is used to reference a prov:Attribution from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element" element="prov:wasAttributedTo" schematype="prov:Attribution"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasAttributedTo" type="prov:Attribution"/>
-</pre>
-<div class="example"><div class="example-title"><span>Example 22</span>: prov:wasAttributedTo</div><pre class="example"><prov:document
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xmlns:xsd="http://www.w3.org/2001/XMLSchema"
- xmlns:prov="http://www.w3.org/ns/prov#"
- xmlns:ex="http://example.com/ns/ex#"
- xmlns:tr="http://example.com/ns/tr#"
- xmlns:rec54="http://example.com/ns/rec54#">
-
- <prov:agent prov:id="ex:Paolo">
- <prov:typexsi:type="xsd:QName">prov:Person</prov:type>
- </prov:agent>
-
- <prov:agent prov:id="ex:Simon">
- <prov:type xsi:type="xsd:QName">prov:Person</prov:type>
- </prov:agent>
-
- <prov:entity prov:id="tr:WD-prov-dm-20111215">
- <prov:type xsi:type="xsd:QName">rec54:WD</prov:type>
- </prov:entity>
-
- <b><prov:wasAttributedTo>
- <prov:entity prov:ref="rec54:WD"/>
- <prov:agent prov:ref="ex:Paolo"/>
- <prov:type xsi:type="xsd:QName">editorship</prov:type>
- </prov:wasAttributedTo></b>
-
- <b><prov:wasAttributedTo>
- <prov:entity prov:ref="rec54:WD"/>
- <prov:agent prov:ref="ex:Simon"/>
- <prov:type xsi:type="xsd:QName">authorship</prov:type>
- </prov:wasAttributedTo></b>
-
-</prov:document></pre></div>
-</section>
-<!-- end term-Attribution -->
-
-
-<section id="term-Association">
-<h4><span class="secno">3.3.3 </span>Association</h4>
-<span class="glossary-ref"> An activity <span class="dfn">association</span> is an assignment of responsibility to an agent for an activity, indicating that the agent had a role in the activity. It further allows for a plan to be specified, which is the plan intended by the agent to achieve some goals in the context of this activity. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Association">
- <xs:sequence>
- <xs:element name="activity" type="prov:IDRef"/>
- <xs:element name="agent" type="prov:IDRef" minOccurs="0"/>
- <xs:element name="plan" type="prov:IDRef" minOccurs="0"/>
- <!-- prov attributes -->
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:role" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
-</xs:complexType>
-</pre>
-<p>The element <code>prov:wasAssociatedWith</code> is used to reference a prov:Association from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element" element="prov:wasAssociatedWith" schematype="prov:Association"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasAssociatedWith" type="prov:Association"/>
-</pre>
-<div class="example"><div class="example-title"><span>Example 23</span>: prov:wasAssociatedWith</div><pre class="example"><prov:document
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xmlns:xsd="http://www.w3.org/2001/XMLSchema"
- xmlns:prov="http://www.w3.org/ns/prov#"
- xmlns:ex="http://example.com/ns/ex#">
-
- <prov:activity prov:id="a">
- <prov:type xsi:type="xsd:string">workflow execution</prov:type>
- </prov:activity>
-
- <prov:agent prov:id="ag1">
- <prov:type xsi:type="xsd:QName">operator</prov:type>
- </prov:agent>
-
- <prov:agent prov:id="ag2">
- <prov:type xsi:type="xsd:QName">designator</prov:type>
- </prov:agent>
-
- <b><prov:wasAssociatedWith>
- <prov:activity prov:ref="a"/>
- <prov:agent prov:ref="ag1"/>
- <prov:role xsi:type="xsd:QName">loggedInUser</prov:role>
- <ex:how>webapp</ex:how>
- </prov:wasAssociatedWith></b>
-
- <b><prov:wasAssociatedWith>
- <prov:activity prov:ref="a"/>
- <prov:agent prov:ref="ag2"/>
- <prov:plan prov:ref="ex:wf"/>
- <prov:role xsi:type="xsd:QName">designer</prov:role>
- <ex:content>project1</ex:content>
- </prov:wasAssociatedWith></b>
-
- <prov:plan prov:id="ex:wf">
- <ex:label>Workflow 1</ex:label>
- <prov:location xsi:type="xsd:anyURI">http://example.org/workflow1.bpel</prov:location>
- </prov:plan>
-
-</prov:document></pre></div>
-
-<section id="term-Plan">
-<h5><span class="secno">3.3.3.1 </span>Plan</h5>
-<span class="glossary-ref"> A <span class="dfn">plan</span> is an entity that represents a set of actions or steps intended by one or more agents to achieve some goals. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Plan">
- <xs:complexContent>
- <xs:extension base="prov:Entity">
- </xs:extension>
- </xs:complexContent>
-</xs:complexType>
-</pre>
-<p>The element <code>prov:plan</code> is used to reference a prov:Plan from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element" element="prov:plan" schematype="prov:Plan"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="plan" type="prov:Plan"/>
-</pre>
-<div class="example"><div class="example-title"><span>Example 24</span>: prov:plan</div><pre class="example"><prov:document
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xmlns:xsd="http://www.w3.org/2001/XMLSchema"
- xmlns:prov="http://www.w3.org/ns/prov#"
- xmlns:ex="http://example.com/ns/ex#">
-
- <prov:activity prov:id="a">
- <prov:type xsi:type="xsd:string">workflow execution</prov:type>
- </prov:activity>
-
- <prov:agent prov:id="ag1">
- <prov:type xsi:type="xsd:QName">operator</prov:type>
- </prov:agent>
-
- <prov:agent prov:id="ag2">
- <prov:type xsi:type="xsd:QName">designator</prov:type>
- </prov:agent>
-
- <prov:wasAssociatedWith>
- <prov:activity prov:ref="a"/>
- <prov:agent prov:ref="ag1"/>
- <prov:role xsi:type="xsd:QName">loggedInUser</prov:role>
- <ex:how>webapp</ex:how>
- </prov:wasAssociatedWith>
-
- <prov:wasAssociatedWith>
- <prov:activity prov:ref="a"/>
- <prov:agent prov:ref="ag2"/>
- <prov:plan prov:ref="ex:wf"/>
- <prov:role xsi:type="xsd:QName">designer</prov:role>
- <ex:content>project1</ex:content>
- </prov:wasAssociatedWith>
-
- <b><prov:plan prov:id="ex:wf">
- <ex:label>Workflow 1</ex:label>
- <prov:location xsi:type="xsd:anyURI">http://example.org/workflow1.bpel</prov:location>
- </prov:plan></b>
-
-</prov:document></pre></div>
-</section>
-<!-- end term-Plan -->
-
-</section>
-<!-- end term-Association -->
-
-
-<section id="term-Delegation">
-<h4><span class="secno">3.3.4 </span>Delegation</h4>
-<span class="glossary-ref"> <span class="dfn">Delegation</span> is the assignment of authority and responsibility to an agent (by itself or by another agent) to carry out a specific activity as a delegate or representative, while the agent it acts on behalf of retains some responsibility for the outcome of the delegated work. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Delegation">
- <xs:sequence>
- <xs:element name="delegate" type="prov:IDRef"/>
- <xs:element name="responsible" type="prov:IDRef"/>
- <xs:element name="activity" type="prov:IDRef" minOccurs="0"/>
- <!-- prov attributes -->
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
-</xs:complexType>
-</pre>
-<p>The element <code>prov:actedOnBehalfOf</code> is used to reference a prov:Delegation from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element" element="prov:actedOnBehalfOf" schematype="prov:Delegation"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="actedOnBehalfOf" type="prov:Delegation"/>
-</pre>
-<div class="example"><div class="example-title"><span>Example 25</span>: prov:actedOnBehalfOf</div><pre class="example"><prov:document
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xmlns:xsd="http://www.w3.org/2001/XMLSchema"
- xmlns:prov="http://www.w3.org/ns/prov#">
-
- <prov:activity prov:id="a">
- <prov:type xsi:type="xsd:QName">workflow</prov:type>
- </prov:activity>
-
- <prov:agent prov:id="ag1">
- <prov:type xsi:type="xsd:QName">programmer</prov:type>
- </prov:agent>
-
- <prov:agent prov:id="ag2">
- <prov:type xsi:type="xsd:QName">researcher</prov:type>
- </prov:agent>
-
- <prov:agent prov:id="ag3">
- <prov:type xsi:type="xsd:QName">funder</prov:type>
- </prov:agent>
-
- <prov:wasAssociatedWith>
- <prov:activity prov:ref="a"/>
- <prov:agent prov:ref="ag1"/>
- <prov:role xsi:type="xsd:QName">loggedInUser</prov:role>
- </prov:wasAssociatedWith>
-
- <prov:wasAssociatedWith>
- <prov:activity prov:ref="a"/>
- <prov:agent prov:ref="ag2"/>
- </prov:wasAssociatedWith>
-
- <prov:wasAssociatedWith>
- <prov:activity prov:ref="a"/>
- <prov:agent prov:ref="ag3"/>
- </prov:wasAssociatedWith>
-
- <b><prov:actedOnBehalfOf>
- <prov:delegate prov:ref="ag1"/>
- <prov:responsible prov:ref="ag2"/>
- <prov:activity prov:ref="a"/>
- <prov:type xsi:type="xsd:QName">line-management</prov:type>
- </prov:actedOnBehalfOf></b>
-
- <b><prov:actedOnBehalfOf>
- <prov:delegate prov:ref="ag2"/>
- <prov:responsible prov:ref="ag3"/>
- <prov:activity prov:ref="a"/>
- <prov:type xsi:type="xsd:QName">contract</prov:type>
- </prov:actedOnBehalfOf></b>
-
-</prov:document></pre></div>
-</section>
-<!-- end term-Delegation -->
-
-
-<section id="term-Influence">
-<h4><span class="secno">3.3.5 </span>Influence</h4>
-<span class="glossary-ref"> <span class="dfn">Influence</span> is the capacity of an entity, activity, or agent to have an effect on the character, development, or behavior of another by means of usage, start, end, generation, invalidation, communication, derivation, attribution, association, or delegation. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Influence">
- <xs:sequence>
- <xs:element name="influencee" type="prov:IDRef"/>
- <xs:element name="influencer" type="prov:IDRef"/>
- <!-- prov attributes -->
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
-</xs:complexType>
-</pre>
-<p>The element <code>prov:wasInfluencedBy</code> is used to reference a prov:Influence from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element" element="prov:wasInfluencedBy" schematype="prov:Influence"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasInfluencedBy" type="prov:Influence"/>
-</pre>
-<div class="example"><div class="example-title"><span>Example 26</span>: prov:wasInfluencedBy</div><pre class="example" id="example_38"><prov:document
- xmlns:prov="http://www.w3.org/ns/prov#"
- xmlns:tr="http://example.com/ns/tr#"
- xmlns:w3="http://w3.org/">
-
- <prov:entity prov:id="tr:WD-prov-dm-20111215"/>
-
- <prov:agent prov:id="w3:Consortium"/>
-
- <b><prov:wasInfluencedBy>
- <prov:influencee prov:ref="tr:WD-prov-dm-20111215"/>
- <prov:influencer prov:ref="w3:Consortium"/>
- </prov:wasInfluencedBy></b>
-
-</prov:document></pre></div>
-</section>
-<!-- end term-Influence -->
-
-
-</section>
-<!-- end component3 -->
-
-
-<section id="component4">
-<h3><span class="secno">3.4 </span>Component 4: Bundles</h3>
-<p>The fourth component is concerned with bundles, a mechanism to support provenance of provenance.</p>
-<section id="term-Bundle">
-<h4><span class="secno">3.4.1 </span>Bundle</h4>
-<span class="glossary-ref"> A <span class="dfn">bundle</span> is a named set of provenance descriptions, and is itself an entity, so allowing provenance of provenance to be expressed. </span>
-<p>A <code>prov:Bundle</code> identifies a set of provenance descriptions, and is an extension of <code>prov:Entity</code>, so allowing provenance of provenance to be expressed by referencing the associated entity. The content of a bundle, i.e. its provenance records, can be represented by the <code>prov:BundleConstructor</code> complexType and can be specified with the <code>prov:bundleContent</code> element, its <code>prov:id</code> corresponds to the bundle entity.</p>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Bundle">
- <xs:complexContent>
- <xs:extension base="prov:Entity">
- </xs:extension>
- </xs:complexContent>
-</xs:complexType>
-</pre>
-<p>The element <code>prov:bundle</code> is used to reference a prov:Bundle from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element" element="prov:bundle" schematype="prov:Bundle"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="bundle" type="prov:Bundle"/>
-</pre>
-<div class="example"><div class="example-title"><span>Example 27</span>: prov:bundle</div><pre class="example"><prov:document
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xmlns:xsd="http://www.w3.org/2001/XMLSchema"
- xmlns:prov="http://www.w3.org/ns/prov#"
- xmlns:ex="http://example.com/ns/ex#"
- xmlns:bob="http://example.com/ns/bob#"
- xmlns:alice="http://example.com/ns/alice#"
- xmlns:agg="http://example.com/ns/agg#">
-
- <b><prov:bundle prov:id="ex:bundle1">
- <ex:version>1</ex:version>
- </prov:bundle></b>
-
- <prov:bundleContent prov:id="ex:bundle1">
- <prov:entity prov:id="ex:report1"/>
-
- <prov:entity prov:id="ex:report2">
- <prov:type xsi:type="xsd:QName">report</prov:type>
- <ex:version>2</ex:version>
- </prov:entity>
-
- <prov:wasGeneratedBy>
- <prov:entity prov:ref="ex:report2"/>
- <prov:time>2012-05-25T11:00:01</prov:time>
- </prov:wasGeneratedBy>
-
- <prov:wasDerivedFrom>
- <prov:generatedEntity prov:ref="ex:report2"/>
- <prov:usedEntity prov:ref="ex:report1"/>
- </prov:wasDerivedFrom>
- </prov:bundleContent>
-
-</prov:document></pre></div>
-</section>
-<!-- end term-Bundle -->
-
-
-<section id="term-BundleConstructor">
-<h4><span class="secno">3.4.2 </span>Bundle Constructor</h4>
-<p>The <code>prov:BundleConstructor</code> complexType is used to define a named set of provenance statements. The Bundle Constructor type supports the <code>prov:id</code> attribute.</p>
-<p>The bundle entity associated with a bundle constructor set must have the same <code>prov:id</code> as the bundle constructor set.</p>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="BundleConstructor">
- <xs:sequence maxOccurs="unbounded">
- <xs:group ref="prov:documentElements"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
-</xs:complexType>
-</pre>
-<p>The element <code>prov:bundleContent</code> is used to reference a set of nested provenance statements from within a prov:Document.</p>
-<p>Although <code>prov:bundleContent</code> can only be expressed at the <code>prov:document</code> level, the corresponding bundle entities may be specified at from either the <code>prov:document</code> or any <code>prov:bundleContent</code>, if at all.</p>
-<pre><xs:complexType name="Document">
- <xs:sequence maxOccurs="unbounded">
- <xs:group ref="prov:documentElements" minOccurs="0"/>
- <xs:element name="bundleContent" type="prov:BundleConstructor" minOccurs="0"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" />
- </xs:sequence>
-</xs:complexType>
-</pre>
-<div class="example"><div class="example-title"><span>Example 28</span>: prov:bundleContent</div><pre class="example"><prov:document
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xmlns:xsd="http://www.w3.org/2001/XMLSchema"
- xmlns:prov="http://www.w3.org/ns/prov#"
- xmlns:ex="http://example.com/ns/ex#"
- xmlns:bob="http://example.com/ns/bob#"
- xmlns:alice="http://example.com/ns/alice#"
- xmlns:agg="http://example.com/ns/agg#">
-
- <prov:bundle prov:id="ex:bundle1">
- <ex:version>1</ex:version>
- </prov:bundle>
-
- <b><prov:bundleContent prov:id="ex:bundle1">
- <prov:entity prov:id="ex:report1"/>
-
- <prov:entity prov:id="ex:report2">
- <prov:type xsi:type="xsd:QName">report</prov:type>
- <ex:version>2</ex:version>
- </prov:entity>
-
- <prov:wasGeneratedBy>
- <prov:entity prov:ref="ex:report2"/>
- <prov:time>2012-05-25T11:00:01</prov:time>
- </prov:wasGeneratedBy>
-
- <prov:wasDerivedFrom>
- <prov:generatedEntity prov:ref="ex:report2"/>
- <prov:usedEntity prov:ref="ex:report1"/>
- </prov:wasDerivedFrom>
- </prov:bundleContent></b>
-
-</prov:document></pre></div>
-</section>
-<!-- end term-BundleConstructor -->
-
-</section>
-<!-- end component4 -->
-
-
-<section id="component5">
-<h3><span class="secno">3.5 </span>Component 5: Alternate Entities</h3>
-<p>The fifth component of PROV-DM is concerned with
-relations SpecializationOf (<a>specialization</a>) and AlternateOf (<a>alternate</a>) between entities.</p>
-
-<section id="term-Specialization">
-<h4><span class="secno">3.5.1 </span>Specialization</h4>
-<span class="glossary-ref"> An entity that is a <span class="dfn">specialization</span> of another shares all aspects of the latter, and additionally presents more specific aspects of the same thing as the latter. In particular, the lifetime of the entity being specialized contains that of any specialization. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Specialization">
- <xs:sequence>
- <xs:element name="specificEntity" type="prov:IDRef"/>
- <xs:element name="generalEntity" type="prov:IDRef"/>
- </xs:sequence>
-</xs:complexType>
-</pre>
-<p>The element <code>prov:specializationOf</code> is used to reference a prov:Specialization from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element" element="prov:specializationOf" schematype="prov:Specialization"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="specializationOf" type="prov:Specialization"/>
-</pre>
-<div class="example"><div class="example-title"><span>Example 29</span>: prov:specializationOf</div><pre class="example"><prov:document
- xmlns:prov="http://www.w3.org/ns/prov#"
- xmlns:ex="http://example.com/ns/ex#"
- xmlns:bbc="http://www.bbc.co.uk/">
-
- <prov:entity prov:id="ex:bbcNews2012-03-23"/>
-
- <prov:entity prov:id="bbc:news"/>
-
- <b><prov:specializationOf>
- <prov:specificEntity prov:ref="ex:bbcNews2012-03-23"/>
- <prov:generalEntity prov:ref="bbc:news"/>
- </prov:specializationOf></b>
-
-</prov:document></pre></div>
-</section>
-<!-- end term-Specialization -->
-
-
-<section id="term-Alternate">
-<h4><span class="secno">3.5.2 </span>Alternate</h4>
-<span class="glossary-ref"> Two <span class="dfn">alternate</span> entities present aspects of the same thing. These aspects may be the same or different, and the alternate entities may or may not overlap in time. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Alternate">
- <xs:sequence>
- <xs:element name="alternate1" type="prov:IDRef"/>
- <xs:element name="alternate2" type="prov:IDRef"/>
- </xs:sequence>
-</xs:complexType>
-</pre>
-<p>The element <code>prov:alternateOf</code> is used to reference a prov:Alternate from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element" element="prov:alternateOf" schematype="prov:Alternate"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="alternateOf" type="prov:Alternate"/>
-</pre>
-<div class="example"><div class="example-title"><span>Example 30</span>: prov:alternateOf</div><pre class="example"><prov:document
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xmlns:xsd="http://www.w3.org/2001/XMLSchema"
- xmlns:prov="http://www.w3.org/ns/prov#"
- xmlns:bbc="http://www.bbc.co.uk/news"
- xmlns:bbcmobile="http://www.bbc.co.uk/news/mobile">
-
- <prov:entity prov:id="bbc:science-environment-17526723">
- <prov:type xsi:type="xsd:string">a news item for desktop</prov:type>
- </prov:entity>
-
- <prov:entity prov:id="bbcmobile:science-environment-17526723">
- <prov:type xsi:type="xsd:string">a news item for mobile devices</prov:type>
- </prov:entity>
-
- <b><prov:alternateOf>
- <prov:alternate1 prov:ref="bbcmobile:science-environment-17526723"/>
- <prov:alternate2 prov:ref="bbc:science-environment-17526723"/>
- </prov:alternateOf></b>
-
-</prov:document></pre></div>
-</section>
-<!-- end term-Alternate -->
-
-
-</section>
-<!-- end component5 -->
-
-
-
-<section id="component6">
-<h3><span class="secno">3.6 </span>Component 6: Collections</h3>
-<p>The sixth component of PROV-DM is concerned with the notion of collections.
-A collection is an entity that has some members. The members are themselves entities, and therefore their provenance can be expressed. Some applications need to be able to express the provenance of the collection itself: e.g. who maintains the collection (attribution), which members it contains as it evolves, and how it was assembled. The purpose of Component 6 is to define the types and relations that are useful to express the provenance of collections. </p>
-
-<section id="term-Collection">
-<h4><span class="secno">3.6.1 </span>Collection</h4>
-<span class="glossary-ref"> A <span class="dfn">collection</span> is an entity that provides a structure to some constituents that must themselves be entities. These constituents are said to be <span class="dfn">member</span> of the collections. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Collection">
- <xs:complexContent>
- <xs:extension base="prov:Entity">
- </xs:extension>
- </xs:complexContent>
-</xs:complexType>
-</pre>
-<p>The element <code>prov:collection</code> is used to reference a prov:Collection from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element" element="prov:collection" schematype="prov:Collection"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="collection" type="prov:Collection"/>
-</pre>
-<div class="example"><div class="example-title"><span>Example 31</span>: prov:collection</div><pre class="example"><prov:document
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xmlns:xsd="http://www.w3.org/2001/XMLSchema"
- xmlns:prov="http://www.w3.org/ns/prov#"
- xmlns:ex="http://example.com/ns/ex#">
-
- <b><prov:collection prov:id="c1" /></b>
-
-</prov:document></pre></div>
-
-<section id="term-EmptyCollection">
-<h5><span class="secno">3.6.1.1 </span>Empty Collection</h5>
-<span class="glossary-ref"> An <span class="dfn">empty collection</span> is a collection without members. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="EmptyCollection">
- <xs:complexContent>
- <xs:extension base="prov:Collection">
- </xs:extension>
- </xs:complexContent>
-</xs:complexType>
-</pre>
-<p>The element <code>prov:emptyCollection</code> is used to reference a prov:EmptyCollection from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element" element="prov:emptyCollection" schematype="prov:EmptyCollection"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="emptyCollection" type="prov:EmptyCollection"/>
-</pre>
-<div class="example"><div class="example-title"><span>Example 32</span>: prov:emptyCollection</div><pre class="example"><prov:document
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xmlns:xsd="http://www.w3.org/2001/XMLSchema"
- xmlns:prov="http://www.w3.org/ns/prov#"
- xmlns:bbc="http://www.bbc.co.uk/news"
- xmlns:bbcmobile="http://www.bbc.co.uk/news/mobile">
-
- <b><prov:emptyCollection prov:id="c0"/></b>
-
-</prov:document></pre></div>
-</section>
-<!-- end term-EmptyCollection -->
-
-</section>
-<!-- end term-Collection -->
-
-
-<section id="term-Membership">
-<h4><span class="secno">3.6.2 </span>Membership</h4>
-<span class="glossary-ref"> <span class="dfn">Membership</span> is the belonging of an entity to a collection. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Membership">
- <xs:sequence>
- <xs:element name="collection" type="prov:IDRef"/>
- <xs:element name="entity" type="prov:IDRef" maxOccurs="unbounded"/>
- </xs:sequence>
-</xs:complexType>
-</pre>
-<p>The element <code>prov:hadMember</code> is used to reference a prov:Membership from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element" element="prov:hadMember" schematype="prov:Membership"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="hadMember" type="prov:Membership"/>
-</pre>
-<div class="example"><div class="example-title"><span>Example 33</span>: prov:hadMember</div><pre class="example"><prov:document
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xmlns:xsd="http://www.w3.org/2001/XMLSchema"
- xmlns:prov="http://www.w3.org/ns/prov#">
-
- <prov:entity prov:id="e0"/>
- <prov:entity prov:id="e1"/>
- <prov:entity prov:id="e2"/>
-
- <prov:collection prov:id="c"/>
-
- <b><prov:hadMember>
- <prov:collection prov:ref="c"/>
- <prov:entity prov:ref="e0"/>
- <prov:entity prov:ref="e1"/>
- <prov:entity prov:ref="e2"/>
- </prov:hadMember></b>
-
-</prov:document></pre></div>
-</section>
-<!-- end term-Membership -->
-
-
-</section>
-<!-- end component6 -->
-
-
-<section id="further-elements">
-<h3><span class="secno">3.7 </span>Further Elements of PROV</h3>
-
-<p>This section introduces further elements of PROV.</p>
-
-<section id="attribute-Identifier">
-<h4><span class="secno">3.7.1 </span>Identifier</h4>
-<span class="glossary-ref"></span>
-<p>The identifier attribute is used to identify instances of PROV types or relations.</p>
-<pre class="schema-attribute" attribute="prov:id" schematype="xs:QName"><xs:attribute xmlns:xs="http://www.w3.org/2001/XMLSchema" name="id" type="xs:QName"/>
-</pre>
-<div class="example"><div class="example-title"><span>Example 34</span>: prov:id</div><pre class="example"><prov:document
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xmlns:xsd="http://www.w3.org/2001/XMLSchema"
- xmlns:prov="http://www.w3.org/ns/prov#"
- xmlns:ex="http://example.com/ns/ex#"
- xmlns:tr="http://example.com/ns/tr#">
-
- <prov:entity <b>prov:id="tr:WD-prov-dm-20111215"</b>>
- <prov:type xsi:type="xsd:Qname">document</prov:type>
- <ex:version>2</ex:version>
- </prov:entity>
-
-</prov:document></pre></div>
-</section>
-<!-- end attribute-Identifier -->
-
-
-<section id="attribute-Reference">
-<h4><span class="secno">3.7.2 </span>Reference</h4>
-<span class="glossary-ref"></span>
-<p>A reference-by-id to a PROV entity, activity, agent, or relation.</p>
-<pre class="schema-attribute" attribute="prov:ref" schematype="xs:QName"><xs:attribute ref="prov:ref" use="required" />
-</pre>
-<div class="example"><div class="example-title"><span>Example 35</span>: prov:ref</div><pre class="example"><prov:document
- xmlns:prov="http://www.w3.org/ns/prov#"
- xmlns:ex="http://example.com/ns/ex#">
-
- <prov:entity prov:id="e1"/>
-
- <prov:activity prov:id="a1"/>
-
- <prov:wasGeneratedBy>
- <prov:entity <b>prov:ref="e1"</b>/>
- <prov:activity <b>prov:ref="a1"</b>/>
- <prov:time>2001-10-26T21:32:52</prov:time>
- <ex:port>p1</ex:port>
- </prov:wasGeneratedBy>
-
-</prov:document></pre></div>
-</section>
-<!-- end attribute-Reference -->
-
-
-<section id="attributes">
-<h4><span class="secno">3.7.3 </span>Attributes</h4>
-<p>The PROV-DM defined PROV attributes are represented in XML as elements.</p>
-
-<section id="element-Label">
-<h5><span class="secno">3.7.3.1 </span>Label</h5>
-<span class="glossary-ref"> The attribute <span class="dfn"><span class="name">prov:label</span></span> provides a human-readable representation of an instance of a PROV-DM type or relation. </span>
-<p>The element <code>prov:label</code> is used to represent a PROV label attribute and has type prov:InternationalizedString.</p><p>Element definition in XML Schema:</p><pre class="prov-attribute" element="prov:label" provtype="label" schematype="prov:InternationalizedString"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="label" type="prov:InternationalizedString"/>
-</pre>
-<div class="example"><div class="example-title"><span>Example 36</span>: prov:label</div><pre class="example"><prov:document
- xmlns:prov="http://www.w3.org/ns/prov#"
- xmlns:ex="http://example.com/ns/ex#">
-
- <prov:entity prov:id="ex:e1">
- <b><prov:label>This is a human-readable label</prov:label></b>
- </prov:entity>
-
- <prov:entity prov:id="ex:car01">
- <b><prov:label xml:lang="fr">Voiture 01</prov:label>
- <prov:label xml:lang="en">Car 01</prov:label></b>
- </prov:entity>
-
-</prov:document></pre></div>
-</section>
-<!-- end element-Label -->
-
-
-<section id="element-Location">
-<h5><span class="secno">3.7.3.2 </span>Location</h5>
-<span class="glossary-ref"> A <span class="dfn">location</span> can be an identifiable geographic place (ISO 19112), but it can also be a non-geographic place such as a directory, row, or column. </span>
-<p>The element <code>prov:location</code> is used to represent a PROV location attribute and has type xs:anySimpleType.</p><p>Element definition in XML Schema:</p><pre class="prov-attribute" element="prov:location" provtype="location" schematype="xs:anySimpleType"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="location" type="xs:anySimpleType"/>
-</pre>
-<div class="example"><div class="example-title"><span>Example 37</span>: prov:location</div><pre class="example"><prov:document
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xmlns:xsd="http://www.w3.org/2001/XMLSchema"
- xmlns:prov="http://www.w3.org/ns/prov#"
- xmlns:ex="http://example.com/ns/ex#">
-
- <prov:entity prov:id="ex:MonaLisa">
- <prov:type xsi:type="xsd:QName">StillImage</prov:type>
- <b><prov:location xsi:type="xsd:string">Le Louvre, Paris</prov:location></b>
- </prov:entity>
-
- <prov:entity prov:id="ex:cell">
- <b><prov:location xsi:type="xsd:string">(5,5)</prov:location></b>
- <prov:value xsi:type="xsd:integer">10</prov:value>
- </prov:entity>
-
-</prov:document></pre></div>
-</section>
-<!-- end element-Location -->
-
-
-<section id="element-Role">
-<h5><span class="secno">3.7.3.3 </span>Role</h5>
-<span class="glossary-ref"> A <span class="dfn">role</span> is the function of an entity or agent with respect to an activity, in the context of a <a title="Usage" href="#concept-usage" class="internalDFN">usage</a>, <a title="Generation" href="#concept-generation" class="internalDFN">generation</a>, <a title="Invalidation" href="#concept-invalidation" class="internalDFN">invalidation</a>, <a title="Association" href="#concept-association" class="internalDFN">association</a>, <a title="Start" href="#concept-start" class="internalDFN">start</a>, and <a title="End" href="#concept-end" class="internalDFN">end</a>. </span>
-<p>The element <code>prov:role</code> is used to represent a PROV Role attribute and has type xs:anySimpleType.</p><p>Element definition in XML Schema:</p><pre class="prov-attribute" element="prov:role" provtype="Role" schematype="xs:anySimpleType"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="role" type="xs:anySimpleType"/>
-</pre>
-<div class="example"><div class="example-title"><span>Example 38</span>: prov:role</div><pre class="example"><prov:document
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xmlns:xsd="http://www.w3.org/2001/XMLSchema"
- xmlns:prov="http://www.w3.org/ns/prov#"
- xmlns:ex="http://example.com/ns/ex#">
-
- <prov:wasAssociatedWith>
- <prov:activity prov:ref="a"/>
- <prov:agent prov:ref="ag1"/>
- <b><prov:role xsi:type="xsd:QName">loggedInUser</prov:role></b>
- <ex:how>webapp</ex:how>
- </prov:wasAssociatedWith>
-
- <prov:wasAssociatedWith>
- <prov:activity prov:ref="a"/>
- <prov:agent prov:ref="ag2"/>
- <prov:plan prov:ref="ex:wf"/>
- <b><prov:role xsi:type="xsd:QName">designer</prov:role></b>
- <ex:content>project1</ex:content>
- </prov:wasAssociatedWith>
-
-</prov:document></pre></div>
-</section>
-<!-- end element-Role -->
-
-
-<section id="element-Type">
-<h5><span class="secno">3.7.3.4 </span>Type</h5>
-<span class="glossary-ref"> The attribute <span class="dfn"><span class="name">prov:type</span></span> provides further typing information for any construct with an optional set of attribute-value pairs. </span>
-<p>The element <code>prov:type</code> is used to represent a PROV Type attribute and has type xs:anySimpleType.</p><p>Element definition in XML Schema:</p><pre class="prov-attribute" element="prov:type" provtype="Type" schematype="xs:anySimpleType"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="type" type="xs:anySimpleType"/>
-</pre>
-<div class="example"><div class="example-title"><span>Example 39</span>: prov:type</div><pre class="example"><prov:document
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xmlns:xsd="http://www.w3.org/2001/XMLSchema"
- xmlns:prov="http://www.w3.org/ns/prov#"
- xmlns:ex="http://example.com/ns/ex#"
- xmlns:tr="http://example.com/ns/tr#">
-
- <prov:entity prov:id="tr:WD-prov-dm-20111215">
- <b><prov:type xsi:type="xsd:QName">document</prov:type></b>
- <ex:version>2</ex:version>
- </prov:entity>
-
- <prov:agent prov:id="e1">
- <b><prov:type xsi:type="xsd:QName">prov:Person</prov:type></b>
- <ex:name>Alice</ex:name>
- <ex:employee>1234</ex:employee>
- </prov:agent>
-
- <prov:activity prov:id="a1">
- <prov:startTime>2011-11-16T16:05:00</prov:startTime>
- <prov:endTime>2011-11-16T16:06:00</prov:endTime>
- <b><prov:type xsi:type="xsd:QName">ex:edit</prov:type></b>
- <ex:host>server.example.org</ex:host>
- </prov:activity>
-
-</prov:document></pre></div>
-</section>
-<!-- end element-Type -->
-
-
-<section id="element-Value">
-<h5><span class="secno">3.7.3.5 </span>Value</h5>
-<span class="glossary-ref"> The attribute <span class="dfn"><span class="name">prov:value</span></span> provides a value that is a direct representation of an entity as a PROV-DM <a title="value" href="#concept-value" class="internalDFN">Value</a>. </span>
-<p>The element <code>prov:value</code> is used to represent a PROV Value attribute and has type xs:anySimpleType.</p><p>Element definition in XML Schema:</p><pre class="prov-attribute" element="prov:value" provtype="Value" schematype="xs:anySimpleType"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="value" type="xs:anySimpleType"/>
-</pre>
-<div class="example"><div class="example-title"><span>Example 40</span>: prov:value</div><pre class="example"><prov:document
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xmlns:xsd="http://www.w3.org/2001/XMLSchema"
- xmlns:prov="http://www.w3.org/ns/prov#"
- xmlns:ex="http://example.com/ns/ex#">
-
- <prov:entity prov:id="ex:in">
- <b><prov:value xsi:type="xsd:string">abcd</prov:value></b>
- </prov:entity>
-
- <prov:entity prov:id="ex:out">
- <b><prov:value xsi:type="xsd:integer">4</prov:value></b>
- </prov:entity>
-
-</prov:document></pre></div>
-</section>
-<!-- end element-Value -->
-
-
-</section>
-<!-- end attributes -->
-
-
-<section id="type-value">
-<h4><span class="secno">3.7.4 </span>Value</h4>
-<span class="glossary-ref"> A <span class="dfn">value</span> is a constant such as a string, number, time, qualified name, IRI, and encoded binary data, whose interpretation is outside the scope of PROV. </span>
-<p>Relations defined by the PROV-DM to have type Value have type <code>xs:anySimpleType</code> in PROV-XML unless otherwise specified.</p>
-</section>
-<!-- end type-Value -->
-
-
-</section>
-<!-- end further-elements -->
-
-
-<section id="structural-elements">
-<h3><span class="secno">3.8 </span>Structural Elements of PROV-XML</h3>
-
-<section id="term-Document">
-<h4><span class="secno">3.8.1 </span>Document</h4>
-<p>The root element of all PROV-XML documents is <code>prov:document</code> which has type <code>prov:Document</code>.</p>
-<p>Similar to a <code>prov:BundleConstructor</code>, the <code>prov:Document</code> complexType is used to define a set of provenance statements.</p>
-<p>Unlike the <code>prov:BundleConstructor</code>, a <code>prov:Document</code>
-</p><ul>
-<li>may contain <code>prov:bundle</code> elements (but not other <code>prov:document</code> elements)</li>
-<li>does not support the prov:id attribute.</li>
-</ul>
-<p></p>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Document">
- <xs:sequence maxOccurs="unbounded">
- <xs:group ref="prov:documentElements" minOccurs="0"/>
- <xs:element name="bundleContent" type="prov:BundleConstructor" minOccurs="0"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" />
- </xs:sequence>
-</xs:complexType>
-</pre>
-
-<p>The element <code>prov:document</code> may only be used as the root element of a a PROV-XML document.</p>
-<p>The element <code>prov:document</code> is used to reference a prov:Document from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element" element="prov:document" schematype="prov:Document" ignore=""><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="document" type="prov:Document"/>
-</pre>
-<div class="example"><div class="example-title"><span>Example 41</span>: prov:document</div><pre class="example"><b><prov:document
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xmlns:xsd="http://www.w3.org/2001/XMLSchema"
- xmlns:prov="http://www.w3.org/ns/prov#"
- xmlns:ex="http://example.com/ns/ex#"></b>
-
- <!-- prov statements go here -->
-
-<b></prov:document></b></pre></div>
-</section>
-<!-- end term-Document-->
-
-
-</section>
-<!-- end structural-elements -->
-
-
-</section>
-<!-- end schema-components -->
-
-
-
-
-
-
-
-
-<!-- end sec. 5 -->
-
-
-
-<section id="media-type">
-
-<!--OddPage-->
-<h2><span class="secno">4. </span>Media Type</h2>
-
-<dl>
- <dt>Contact:</dt>
- <dd>Ivan Herman</dd>
- <dt>See also:</dt>
- <dd><a href="http://www.w3.org/2002/06/registering-mediatype">How to Register a Media Type for a <abbr title="World Wide Web Consortium">W3C</abbr> Specification</a></dd>
- <dd><a href="http://www.w3.org/2001/tag/2002/0129-mime">Internet Media Type registration, consistency of use</a><br />TAG Finding 3 June 2002 (Revised 4 September 2002)</dd>
-</dl>
-
-<p>The Internet Media Type / MIME type for PROV-XML is "<code style="color: black">application/provenance+xml</code>".</p>
-
-<p>It is recommended that PROV-XML files have the extension "<code style="color: black">.provx</code>" (all lowercase) on all platforms.</p>
-
-<p>It is recommended that PROV-XML files stored on Macintosh HFS file systems be given a file type of <code style="color: black">TEXT</code>.</p>
-
-<p>The information that follows has been
-<!--<a href="https://lists.w3.org/Archives/Member/w3c-archive/2012Nov/0317.html">-->
-submitted to the IESG
-<!--</a>-->
- for review, approval, and registration with IANA.</p>
-
-<dl>
- <dt>Type name:</dt>
- <dd>application</dd>
- <dt>Subtype name:</dt>
- <dd>provenance+xml</dd>
- <dt>Required parameters:</dt>
- <dd>none</dd>
- <dt>Optional parameters:</dt>
- <dd>Same as charset parameter of application/xml as specified in RFC3023 (Section 3.2).</dd>
- <dt>Encoding considerations:</dt>
- <dd>Same as encoding considerations of application/xml as specified in RFC 3023 (Section 3.2).</dd>
- <dt>Security considerations:</dt>
- <dd>PROV-XML is an XML language for describing the provenance of things; applications may evaluate given data to dereference URIs, invoking the security considerations of the scheme for that URI. Note in particular, the privacy issues in [<cite><a class="bibref" href="#bib-RFC3023">RFC3023</a></cite>] section 10 for HTTP URIs. Data obtained from an inaccurate or malicious data source may lead to inaccurate or misleading conclusions, as well as the dereferencing of unintended URIs. Care must be taken to align the trust in consulted resources with the sensitivity of the intended use of the data.</dd>
- <dd>PROV-XML can express data which is presented to the user, for example, by means of label attributes. Application rendering strings retrieved from untrusted PROV-N documents must ensure that malignant strings may not be used to mislead the reader. The security considerations in the media type registration for XML ([<cite><a class="bibref" href="#bib-RFC3023">RFC3023</a></cite>] section 10) provide additional guidance around the expression of arbitrary data and markup.</dd>
- <dd>PROV-XML is a language for describing the provenance of things, and therefore a PROV-XML document is metadata for other resources. Untrusted PROV-XML documents may mislead its consumers by indicating that a third-party resource has a reputable lineage, when it has not. Provenance of PROV-XML document should be sought. </dd>
- <dd>PROV-XML uses QNames mappable to IRIs as term identifiers. Applications interpreting data expressed in PROV-XML should address the security issues of
- <a class="norm" href="http://www.ietf.org/rfc/rfc3987.txt">Internationalized Resource Identifiers (IRIs)</a> [<cite><a class="bibref" href="#bib-RFC3987">RFC3987</a></cite>] Section 8, as well as
- <a class="norm" href="http://www.ietf.org/rfc/rfc3986.txt">Uniform Resource Identifier (URI): Generic Syntax</a> [<cite><a class="bibref" href="#bib-RFC3986">RFC3986</a></cite>] Section 7.</dd>
- <dd>Multiple IRIs may have the same appearance. Characters in different scripts may look similar (a Cyrillic "о" may appear similar to a Latin "o"). A character followed by combining characters may have the same visual representation as another character (LATIN SMALL LETTER E followed by COMBINING ACUTE ACCENT has the same visual representation as LATIN SMALL LETTER E WITH ACUTE). Any person or application that is writing or interpreting data in PROV-N must take care to use the IRI that matches the intended semantics, and avoid IRIs that make look similar. Further information about matching of similar characters can be found in <a class="inform" href="http://www.unicode.org/reports/tr36/">Unicode Security Considerations</a> [<cite><a class="bibref" href="#bib-UNISEC">UNISEC</a></cite>] and <a class="norm" href="http://www.ietf.org/rfc/rfc3987.txt">Internationalized Resource Identifiers (IRIs)</a> [<cite><a class="bibref" href="#bib-RFC3987">RFC3987</a></cite>] Section 8.</dd>
- <dt>Interoperability considerations:</dt>
- <dd>There are no known interoperability issues.</dd>
- <dt>Published specification:</dt>
- <dd>PROV-XML: The PROV XML Schema, Hua, Tilmes, Zednik (eds), Moreau <a href="http://www.w3.org/TR/prov-xml/">http://www.w3.org/TR/prov-xml/</a>, 2013.</dd>
- <dt>Applications which use this media type:</dt>
- <dd>It may be used by any application for publishing provenance information. This format is designed to be an XML form of provenance.</dd>
- <dt>Fragment identifier considerations:</dt>
- <dd>N/A</dd>
- <dt>Additional Information:</dt>
- <span style="text-indent:2em;">
- <dt>Magic number(s):</dt>
- <dd>PROV-XML documents are XML documents and thus may have initial strings similar to any XML document.</dd>
- <dt>File extension(s):</dt>
- <dd>.provx</dd>
- <dt>Macintosh file type code(s):</dt>
- <dd>"TEXT"</dd>
- </span>
- <dt>Person & email address to contact for further information:</dt>
- <dd>Ivan Herman, ivan@w3.org</dd>
- <dt>Intended usage:</dt>
- <dd>COMMON</dd>
- <dt>Restrictions on usage:</dt>
- <dd>none</dd>
- <dt>Author:</dt>
- <dd>The PROV-XML specification is the product of the World Wide Web Consortium's Provenance Working Group.</dd>
- <dt>Change controller:</dt>
- <dd>The <abbr title="World Wide Web Consortium">W3C</abbr>, and the <abbr title="World Wide Web Consortium">W3C</abbr> Provenance Working Group, have change control over this specification.</dd>
-</dl>
-
-</section>
-<!-- end media-type -->
-
-
-
-
-
-<section class="appendix" id="prov-xml-schema">
-
-<!--OddPage-->
-<h2><span class="secno">A. </span>XML Schema</h2>
-
-<section id="prov-schema">
-<h3><span class="secno">A.1 </span>prov.xsd</h3>
-<pre class="prov-schema"><?xml version="1.0" encoding="utf-8"?>
-<xs:schema targetNamespace="http://www.w3.org/ns/prov#"
- xmlns:xs="http://www.w3.org/2001/XMLSchema"
- xmlns:prov="http://www.w3.org/ns/prov#"
- elementFormDefault="qualified"
- attributeFormDefault="unqualified">
-
- <xs:include schemaLocation="prov-core.xsd"/>
- <xs:include schemaLocation="extensions/prov-dictionary.xsd"/>
- <xs:include schemaLocation="extensions/prov-links.xsd"/>
-
-</xs:schema>
-</pre>
-</section>
-<!-- end prov-schema -->
-
-
-<section id="prov-core-schema">
-<h3><span class="secno">A.2 </span>prov-core.xsd</h3>
-<pre class="prov-core-schema"><?xml version="1.0" encoding="utf-8"?>
-<xs:schema targetNamespace="http://www.w3.org/ns/prov#"
- xmlns:xs="http://www.w3.org/2001/XMLSchema"
- xmlns:prov="http://www.w3.org/ns/prov#"
- xmlns:cu="http://www.w3.org/1999/xhtml/datatypes/"
- xmlns:xml="http://www.w3.org/XML/1998/namespace"
- elementFormDefault="qualified"
- attributeFormDefault="unqualified">
-
-
-
- <xs:import namespace="http://www.w3.org/1999/xhtml/datatypes/" />
- <xs:import namespace="http://www.w3.org/XML/1998/namespace"
- schemaLocation="http://www.w3.org/2001/xml.xsd"/>
-
- <!-- Component 1 -->
-
- <xs:complexType name="Entity">
- <xs:sequence>
- <!-- prov attributes -->
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:location" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:value" minOccurs="0"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <xs:complexType name="Activity">
- <xs:sequence>
- <xs:element name="startTime" type="xs:dateTime" minOccurs="0"/>
- <xs:element name="endTime" type="xs:dateTime" minOccurs="0"/>
- <!-- prov attributes -->
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:location" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <xs:complexType name="Generation">
- <xs:sequence>
- <xs:element name="entity" type="prov:IDRef"/>
- <xs:element name="activity" type="prov:IDRef" minOccurs="0"/>
- <xs:element name="time" type="xs:dateTime" minOccurs="0"/>
- <!-- prov attributes -->
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:location" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:role" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <xs:complexType name="Usage">
- <xs:sequence>
- <xs:element name="activity" type="prov:IDRef"/>
- <xs:element name="entity" type="prov:IDRef" minOccurs="0"/>
- <xs:element name="time" type="xs:dateTime" minOccurs="0"/>
- <!-- prov attributes -->
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:location" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:role" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <xs:complexType name="Communication">
- <xs:sequence>
- <xs:element name="informed" type="prov:IDRef"/>
- <xs:element name="informant" type="prov:IDRef"/>
- <!-- prov attributes -->
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <xs:complexType name="Start">
- <xs:sequence>
- <xs:element name="activity" type="prov:IDRef"/>
- <xs:element name="trigger" type="prov:IDRef" minOccurs="0"/>
- <xs:element name="starter" type="prov:IDRef" minOccurs="0"/>
- <xs:element name="time" type="xs:dateTime" minOccurs="0"/>
- <!-- prov attributes -->
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:location" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:role" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <xs:complexType name="End">
- <xs:sequence>
- <xs:element name="activity" type="prov:IDRef"/>
- <xs:element name="trigger" type="prov:IDRef" minOccurs="0"/>
- <xs:element name="ender" type="prov:IDRef" minOccurs="0"/>
- <xs:element name="time" type="xs:dateTime" minOccurs="0"/>
- <!-- prov attributes -->
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:location" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:role" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <xs:complexType name="Invalidation">
- <xs:sequence>
- <xs:element name="entity" type="prov:IDRef"/>
- <xs:element name="activity" type="prov:IDRef" minOccurs="0"/>
- <xs:element name="time" type="xs:dateTime" minOccurs="0"/>
- <!-- prov attributes -->
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:location" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:role" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <!-- Component 2 -->
-
- <xs:complexType name="Derivation">
- <xs:sequence>
- <xs:element name="generatedEntity" type="prov:IDRef"/>
- <xs:element name="usedEntity" type="prov:IDRef"/>
- <xs:element name="activity" type="prov:IDRef" minOccurs="0"/>
- <xs:element name="generation" type="prov:IDRef" minOccurs="0"/>
- <xs:element name="usage" type="prov:IDRef" minOccurs="0"/>
- <!-- prov attributes -->
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <xs:complexType name="Revision">
- <xs:complexContent>
- <xs:extension base="prov:Derivation">
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
-
- <xs:complexType name="Quotation">
- <xs:complexContent>
- <xs:extension base="prov:Derivation">
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
-
- <xs:complexType name="PrimarySource">
- <xs:complexContent>
- <xs:extension base="prov:Derivation">
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
-
- <!-- Component 3 -->
-
- <xs:complexType name="Agent">
- <xs:sequence>
- <!-- prov attributes -->
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:location" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <xs:complexType name="Person">
- <xs:complexContent>
- <xs:extension base="prov:Agent">
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
-
- <xs:complexType name="Organization">
- <xs:complexContent>
- <xs:extension base="prov:Agent">
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
-
- <xs:complexType name="SoftwareAgent">
- <xs:complexContent>
- <xs:extension base="prov:Agent">
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
-
- <xs:complexType name="Attribution">
- <xs:sequence>
- <xs:element name="entity" type="prov:IDRef"/>
- <xs:element name="agent" type="prov:IDRef"/>
- <!-- prov attributes -->
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <xs:complexType name="Association">
- <xs:sequence>
- <xs:element name="activity" type="prov:IDRef"/>
- <xs:element name="agent" type="prov:IDRef" minOccurs="0"/>
- <xs:element name="plan" type="prov:IDRef" minOccurs="0"/>
- <!-- prov attributes -->
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:role" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <xs:complexType name="Delegation">
- <xs:sequence>
- <xs:element name="delegate" type="prov:IDRef"/>
- <xs:element name="responsible" type="prov:IDRef"/>
- <xs:element name="activity" type="prov:IDRef" minOccurs="0"/>
- <!-- prov attributes -->
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <xs:complexType name="Influence">
- <xs:sequence>
- <xs:element name="influencee" type="prov:IDRef"/>
- <xs:element name="influencer" type="prov:IDRef"/>
- <!-- prov attributes -->
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <!-- Component 4 -->
-
- <!-- Is there a way to have this still extend prov:Entity? -->
-
- <xs:complexType name="Bundle">
- <xs:complexContent>
- <xs:extension base="prov:Entity">
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
-
- <xs:complexType name="BundleConstructor">
- <xs:sequence maxOccurs="unbounded">
- <xs:group ref="prov:documentElements"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <!-- Component 5 -->
-
- <xs:complexType name="Specialization">
- <xs:sequence>
- <xs:element name="specificEntity" type="prov:IDRef"/>
- <xs:element name="generalEntity" type="prov:IDRef"/>
- </xs:sequence>
- </xs:complexType>
-
- <xs:complexType name="Alternate">
- <xs:sequence>
- <xs:element name="alternate1" type="prov:IDRef"/>
- <xs:element name="alternate2" type="prov:IDRef"/>
- </xs:sequence>
- </xs:complexType>
-
- <!-- Component 6 -->
-
- <xs:complexType name="Collection">
- <xs:complexContent>
- <xs:extension base="prov:Entity">
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
-
- <xs:complexType name="EmptyCollection">
- <xs:complexContent>
- <xs:extension base="prov:Collection">
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
-
- <xs:complexType name="Membership">
- <xs:sequence>
- <xs:element name="collection" type="prov:IDRef"/>
- <xs:element name="entity" type="prov:IDRef" maxOccurs="unbounded"/>
- </xs:sequence>
- </xs:complexType>
-
- <xs:complexType name="Plan">
- <xs:complexContent>
- <xs:extension base="prov:Entity">
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
-
- <xs:complexType name="InternationalizedString">
- <xs:simpleContent>
- <xs:extension base="xs:string">
- <xs:attribute ref="xml:lang" use="optional"/>
- </xs:extension>
- </xs:simpleContent>
- </xs:complexType>
-
-
- <!--
- Typed literals are encoded by means
- of xsi:type that represent the prov:datatype.
- -->
-
- <xs:element name="label" type="prov:InternationalizedString"/>
- <xs:element name="role" type="xs:anySimpleType"/>
- <xs:element name="type" type="xs:anySimpleType"/>
- <xs:element name="location" type="xs:anySimpleType"/>
- <xs:element name="value" type="xs:anySimpleType"/>
-
- <xs:attribute name="id" type="xs:QName"/>
- <xs:attribute name="ref" type="xs:QName"/>
-
- <xs:complexType name="IDRef">
- <xs:attribute ref="prov:ref" use="required" />
- </xs:complexType>
-
- <!--
- top-level definition of elements following the salami slice XSD design pattern
- to encourage integration within existing non-prov XML documents.
- -->
-
- <!-- Component 1 elements -->
-
- <xs:element name="entity" type="prov:Entity"/>
- <xs:element name="activity" type="prov:Activity"/>
- <xs:element name="wasGeneratedBy" type="prov:Generation"/>
- <xs:element name="used" type="prov:Usage"/>
- <xs:element name="wasInformedBy" type="prov:Communication"/>
- <xs:element name="wasStartedBy" type="prov:Start"/>
- <xs:element name="wasEndedBy" type="prov:End"/>
- <xs:element name="wasInvalidatedBy" type="prov:Invalidation"/>
-
- <!-- Component 2 elements -->
-
- <xs:element name="wasDerivedFrom" type="prov:Derivation"/>
- <xs:element name="wasRevisionOf" type="prov:Revision"/>
- <xs:element name="wasQuotedFrom" type="prov:Quotation"/>
- <xs:element name="hadPrimarySource" type="prov:PrimarySource"/>
-
- <!-- Component 3 elements -->
-
- <xs:element name="agent" type="prov:Agent"/>
- <xs:element name="person" type="prov:Person"/>
- <xs:element name="organization" type="prov:Organization"/>
- <xs:element name="softwareAgent" type="prov:SoftwareAgent"/>
- <xs:element name="wasAttributedTo" type="prov:Attribution"/>
- <xs:element name="wasAssociatedWith" type="prov:Association"/>
- <xs:element name="actedOnBehalfOf" type="prov:Delegation"/>
- <xs:element name="wasInfluencedBy" type="prov:Influence"/>
-
- <!-- Component 5 elements -->
-
- <xs:element name="bundle" type="prov:Bundle"/>
- <xs:element name="specializationOf" type="prov:Specialization"/>
- <xs:element name="alternateOf" type="prov:Alternate"/>
-
- <!-- Component 6 elements -->
-
- <xs:element name="hadMember" type="prov:Membership"/>
- <xs:element name="collection" type="prov:Collection"/>
- <xs:element name="emptyCollection" type="prov:EmptyCollection"/>
-
- <!-- Component 7 elements -->
-
- <xs:element name="plan" type="prov:Plan"/>
-
- <!-- document elements -->
-
- <xs:group name="documentElements">
- <xs:sequence>
- <xs:element ref="prov:entity" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:activity" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:wasGeneratedBy" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:used" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:wasInformedBy" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:wasStartedBy" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:wasEndedBy" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:wasInvalidatedBy" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:wasDerivedFrom" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:wasRevisionOf" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:wasQuotedFrom" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:hadPrimarySource" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:agent" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:person" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:organization" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:softwareAgent" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:wasAttributedTo" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:wasAssociatedWith" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:actedOnBehalfOf" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:wasInfluencedBy" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:bundle" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:specializationOf" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:alternateOf" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:collection" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:emptyCollection" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:hadMember" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:plan" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:internalElement" minOccurs="0" maxOccurs="unbounded" />
- </xs:sequence>
- </xs:group>
-
- <xs:element name="document" type="prov:Document" />
- <xs:complexType name="Document">
- <xs:sequence maxOccurs="unbounded">
- <xs:group ref="prov:documentElements" minOccurs="0"/>
- <xs:element name="bundleContent" type="prov:BundleConstructor" minOccurs="0"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" />
- </xs:sequence>
- </xs:complexType>
-
-
- <!-- abstract element used by extensions -->
-
- <xs:element name="internalElement" abstract="true" />
-
-</xs:schema>
-</pre>
-</section>
-<!-- end prov-core-schema -->
-
-
-<section id="extension-schemas">
-<h3><span class="secno">A.3 </span>Extension Schemas</h3>
-<p>Extension schemas are schemas in the PROV Namespace that define additional PROV elements not from the PROV-DM. Workgroup Notes provide extension schemas to define their Note-introduced PROV elements. Extension schemas must import (using <code>xs:include</code>) the <b>prov-core.xsd</b> schema and make use of a substitution group on the <code>prov:internalElement</code> to add extension defined elements to the list of valid PROV elements in a bundle or document.</p>
-<p>Here is an example from the <b>prov-links.xsd</b> extension schema.</p>
-<pre title="prov-links.xsd"><?xml version="1.0" encoding="UTF-8"?>
-<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
- targetNamespace="http://www.w3.org/ns/prov#" xmlns:prov="http://www.w3.org/ns/prov#"
- elementFormDefault="qualified">
-
- <xs:include schemaLocation="../prov-core.xsd" />
-
- <xs:complexType name="Mention">
- <xs:sequence>
- <xs:element name="specificEntity" type="prov:IDRef" />
- <xs:element name="generalEntity" type="prov:IDRef" />
- <xs:element name="bundle" type="prov:IDRef" />
- </xs:sequence>
- </xs:complexType>
-
- <xs:element name="mentionOf" type="prov:Mention" substitutionGroup="prov:internalElement" />
-
-</xs:schema>
-</pre>
-</section>
-<!-- end extension-schemas -->
-
-</section>
-<!-- end prov-xml-schema -->
-
-
-<section class="appendix" id="changelog">
-
-<!--OddPage-->
-<h2><span class="secno">B. </span>Change Log</h2>
-
-<section id="changelog-last">
-<h3><span class="secno">B.1 </span>Changes since last version</h3>
-<ul>
-<li>Added Change Log section</li>
-<li> Changed the status of this document section: added new documents to the PROV Family of Document, and removed the how to read section, referring instead to PROV-OVERVIEW.</li>
-<li>Changed all URLs to PROV documents.</li>
-<li>Removed Review notes.</li>
-<li>Updated table 1 with XML Schema Referencing Element column.</li>
-<li>Added Type Conventions and Schema Modularization sections to XML Schema Design section.</li>
-<li>Updated Bundle section to reflect changes in schema design.</li>
-<li>Updated inline schema and schema examples to reflect updates to schema design.</li>
-<li>Updated text that appears before schema snippets and examples in PROV XML Schema subsections.</li>
-<li>Added extension schema example to appendix.</li>
-<li>Removed Macintosh HFS file type paragraph from Media Type section.</li>
-<li>Made all references informative instead of normative since PROV-XML is a note.</li>
-</ul>
-</section>
-<!-- end changelog-last -->
-
-</section>
-<!-- end changelog -->
-
-
-<section class="appendix" id="acknowledgements">
-
-<!--OddPage-->
-<h2><span class="secno">C. </span>Acknowledgements</h2>
-
-This document has been produced by the PROV Working Group, and its
-contents reflect extensive discussion within the Working Group as a
-whole. The editors extend special thanks to Luc Moreau (University of
-Southampton), Paul Groth (Vrije Universiteit) and James Cheney
-(University of Edinburgh) for their thorough reviews.
-
-<p>
-Members of the PROV Working Group at the time of publication of this document were:
-
-Ilkay Altintas (Invited expert),
-Reza B'Far (Oracle Corporation),
-Khalid Belhajjame (University of Manchester),
-James Cheney (University of Edinburgh, School of Informatics),
-Sam Coppens (IBBT),
-David Corsar (University of Aberdeen, Computing Science),
-Stephen Cresswell (The National Archives),
-Tom De Nies (IBBT),
-Helena Deus (DERI Galway at the National University of Ireland, Galway, Ireland),
-Simon Dobson (Invited expert),
-Martin Doerr (Foundation for Research and Technology - Hellas(FORTH)),
-Kai Eckert (Invited expert),
-Jean-Pierre EVAIN (European Broadcasting Union, EBU-UER),
-James Frew (Invited expert),
-Irini Fundulaki (Foundation for Research and Technology - Hellas(FORTH)),
-Daniel Garijo (Universidad Politécnica de Madrid),
-Yolanda Gil (Invited expert),
-Ryan Golden (Oracle Corporation),
-Paul Groth (Vrije Universiteit),
-Olaf Hartig (Invited expert),
-David Hau (National Cancer Institute, NCI),
-Sandro Hawke (<abbr title="World Wide Web Consortium">W3C</abbr>/<abbr title="Massachusetts Institute of Technology">MIT</abbr>),
-Jörn Hees (German Research Center for Artificial Intelligence (DFKI) Gmbh),
-Ivan Herman, (<abbr title="World Wide Web Consortium">W3C</abbr>/<abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr>),
-Ralph Hodgson (TopQuadrant),
-Hook Hua (Invited expert),
-Trung Dong Huynh (University of Southampton),
-Graham Klyne (University of Oxford),
-Michael Lang (Revelytix, Inc.),
-Timothy Lebo (Rensselaer Polytechnic Institute),
-James McCusker (Rensselaer Polytechnic Institute),
-Deborah McGuinness (Rensselaer Polytechnic Institute),
-Simon Miles (Invited expert),
-Paolo Missier (School of Computing Science, Newcastle university),
-Luc Moreau (University of Southampton),
-James Myers (Rensselaer Polytechnic Institute),
-Vinh Nguyen (Wright State University),
-Edoardo Pignotti (University of Aberdeen, Computing Science),
-Paulo da Silva Pinheiro (Rensselaer Polytechnic Institute),
-Carl Reed (Open Geospatial Consortium),
-Adam Retter (Invited Expert),
-Christine Runnegar (Invited expert),
-Satya Sahoo (Invited expert),
-David Schaengold (Revelytix, Inc.),
-Daniel Schutzer (FSTC, Financial Services Technology Consortium),
-Yogesh Simmhan (Invited expert),
-Stian Soiland-Reyes (University of Manchester),
-Eric Stephan (Pacific Northwest National Laboratory),
-Linda Stewart (The National Archives),
-Ed Summers (Library of Congress),
-Maria Theodoridou (Foundation for Research and Technology - Hellas(FORTH)),
-Ted Thibodeau (OpenLink Software Inc.),
-Curt Tilmes (National Aeronautics and Space Administration),
-Craig Trim (IBM Corporation),
-Stephan Zednik (Rensselaer Polytechnic Institute),
-Jun Zhao (University of Oxford),
-Yuting Zhao (University of Aberdeen, Computing Science).
-</p>
-</section>
-<!-- end acknowledgements -->
-
-
-
-
-
-
-
-
-<section id="references" class="appendix">
-<!--OddPage-->
-<h2><span class="secno">D. </span>References</h2><section id="informative-references"><h3><span class="secno">D.1 </span>Informative references</h3><dl class="bibliography"><dt id="bib-Mappings">[Mappings]</dt><dd>Satya Sahoo and Paul Groth and Olaf Hartig and Simon Miles and Sam Coppens and James Myers and Yolanda Gil and Luc Moreau and Jun Zhao and Michael Panzer and Daniel Garijo <a href="http://www.w3.org/2005/Incubator/prov/wiki/Provenance_Vocabulary_Mappings"><cite>Provenance Vocabulary Mappings</cite></a>. August 2010 URL: <a href="http://www.w3.org/2005/Incubator/prov/wiki/Provenance_Vocabulary_Mappings">http://www.w3.org/2005/Incubator/prov/wiki/Provenance_Vocabulary_Mappings</a>
-</dd><dt id="bib-PROV-AQ">[PROV-AQ]</dt><dd>Graham Klyne; Paul Groth; eds. <a href="http://www.w3.org/TR/2013/WD-prov-aq-20130312/"><cite>Provenance Access and Query</cite></a>. 12 March 2013, Working Draft. URL: <a href="http://www.w3.org/TR/2013/WD-prov-aq-20130312/">http://www.w3.org/TR/2013/WD-prov-aq-20130312/</a>
-</dd><dt id="bib-PROV-CONSTRAINTS">[PROV-CONSTRAINTS]</dt><dd>James Cheney; Paolo Missier; Luc Moreau; eds. <a href="http://www.w3.org/TR/2013/PR-prov-constraints-20130312/"><cite>Constraints of the PROV Data Model</cite></a>. 12 March 2013, W3C Proposed Recommendation. URL: <a href="http://www.w3.org/TR/2013/PR-prov-constraints-20130312/">http://www.w3.org/TR/2013/PR-prov-constraints-20130312/</a>
-</dd><dt id="bib-PROV-DC">[PROV-DC]</dt><dd>Daniel Garijo; Kai Eckert; eds. <a href="http://www.w3.org/TR/2013/WD-prov-dc-20130312/"><cite>Dublin Core to PROV Mapping</cite></a>. 12 March 2013, Working Draft. URL: <a href="http://www.w3.org/TR/2013/WD-prov-dc-20130312/">http://www.w3.org/TR/2013/WD-prov-dc-20130312/</a>
-</dd><dt id="bib-PROV-DICTIONARY">[PROV-DICTIONARY]</dt><dd>Tom De Nies; Sam Coppens; eds. <a href="http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/"><cite>PROV Dictionary</cite></a>. 12 March 2013, Working Draft. URL: <a href="http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/</a>
-</dd><dt id="bib-PROV-DM">[PROV-DM]</dt><dd>Luc Moreau; Paolo Missier; eds. <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/"><cite>PROV-DM: The PROV Data Model</cite></a>. 12 March 2013, W3C Proposed Recommendation. URL: <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/">http://www.w3.org/TR/2013/PR-prov-dm-20130312/</a>
-</dd><dt id="bib-PROV-LINKS">[PROV-LINKS]</dt><dd>Luc Moreau; Timothy Lebo; eds. <a href="http://www.w3.org/TR/2013/WD-prov-links-20130312/"><cite>Linking Across Provenance Bundles</cite></a>. 12 March 2013, Working Draft. URL: <a href="http://www.w3.org/TR/2013/WD-prov-links-20130312/">http://www.w3.org/TR/2013/WD-prov-links-20130312/</a>
-</dd><dt id="bib-PROV-N">[PROV-N]</dt><dd>Luc Moreau; Paolo Missier; eds. <a href="http://www.w3.org/TR/2013/PR-prov-n-20130312/"><cite>PROV-N: The Provenance Notation</cite></a>. 12 March 2013, W3C Proposed Recommendation. URL: <a href="http://www.w3.org/TR/2013/PR-prov-n-20130312/">http://www.w3.org/TR/2013/PR-prov-n-20130312/</a>
-</dd><dt id="bib-PROV-O">[PROV-O]</dt><dd>Timothy Lebo; Satya Sahoo; Deborah McGuinness; eds. <a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/"><cite>PROV-O: The PROV Ontology</cite></a>. 12 March 2013, W3C Proposed Recommendation. URL: <a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/">http://www.w3.org/TR/2013/PR-prov-o-20130312/</a>
-</dd><dt id="bib-PROV-OVERVIEW">[PROV-OVERVIEW]</dt><dd>Paul Groth; Luc Moreau; eds. <a href="http://www.w3.org/TR/2013/WD-prov-overview-20130312/"><cite>PROV-OVERVIEW: An Overview of the PROV Family of Documents</cite></a>. 12 March 2013, Working Draft. URL: <a href="http://www.w3.org/TR/2013/WD-prov-overview-20130312/">http://www.w3.org/TR/2013/WD-prov-overview-20130312/</a>
-</dd><dt id="bib-PROV-PRIMER">[PROV-PRIMER]</dt><dd>Yolanda Gil; Simon Miles; eds. <a href="http://www.w3.org/TR/2013/WD-prov-primer-20130312/"><cite>PROV Model Primer</cite></a>. 12 March 2013, Working Draft. URL: <a href="http://www.w3.org/TR/2013/WD-prov-primer-20130312/">http://www.w3.org/TR/2013/WD-prov-primer-20130312/</a>
-</dd><dt id="bib-PROV-SEM">[PROV-SEM]</dt><dd>James Cheney; ed. <a href="http://www.w3.org/TR/2013/WD-prov-sem-20130312"><cite>Semantics of the PROV Data Model</cite></a>. 12 March 2013, Working Draft. URL: <a href="http://www.w3.org/TR/2013/WD-prov-sem-20130312">http://www.w3.org/TR/2013/WD-prov-sem-20130312</a>.
-</dd><dt id="bib-RFC2119">[RFC2119]</dt><dd>S. Bradner. <a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>Key words for use in RFCs to Indicate Requirement Levels.</cite></a> March 1997. Internet RFC 2119. URL: <a href="http://www.ietf.org/rfc/rfc2119.txt">http://www.ietf.org/rfc/rfc2119.txt</a>
-</dd><dt id="bib-RFC3023">[RFC3023]</dt><dd>M. Murata; S. St.Laurent; D. Kohn. <a href="http://www.ietf.org/rfc/rfc3023.txt"><cite>XML Media Types</cite></a>. January 2001. RFC 3023. URL: <a href="http://www.ietf.org/rfc/rfc3023.txt">http://www.ietf.org/rfc/rfc3023.txt</a>
-</dd><dt id="bib-RFC3986">[RFC3986]</dt><dd>T. Berners-Lee; R. Fielding; L. Masinter. <a href="http://www.ietf.org/rfc/rfc3986.txt"><cite>Uniform Resource Identifier (URI): Generic Syntax</cite></a>. January 2005. RFC 3986. URL: <a href="http://www.ietf.org/rfc/rfc3986.txt">http://www.ietf.org/rfc/rfc3986.txt</a>
-</dd><dt id="bib-RFC3987">[RFC3987]</dt><dd>M. Dürst; M. Suignard. <a href="http://www.ietf.org/rfc/rfc3987.txt"><cite>Internationalized Resource Identifiers (IRIs)</cite></a>. January 2005. RFC 3987. URL: <a href="http://www.ietf.org/rfc/rfc3987.txt">http://www.ietf.org/rfc/rfc3987.txt</a>
-</dd><dt id="bib-UNISEC">[UNISEC]</dt><dd> Mark Davis; Michel Suignard. <a href="http://www.unicode.org/reports/tr36/"><cite>Unicode Security Considerations<cite></cite></cite></a>. 4 August 2010. URL: <a href="http://www.unicode.org/reports/tr36/">http://www.unicode.org/reports/tr36/</a>
-</dd></dl></section></section></body></html>
\ No newline at end of file
--- a/xml/examples/custom-example.xml Fri Apr 26 09:26:16 2013 +0100
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,36 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<prov:document xmlns:xml="http://www.w3.org/XML/1998/namespace"
- xmlns:prov="http://www.w3.org/ns/prov#" xmlns:custom="http://www.example.org/custom"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:schemaLocation="
- http://www.w3.org/ns/prov#
- ../schema/prov.xsd
- http://www.example.org/custom
- custom.xsd">
- <prov:person prov:id="fred">
- </prov:person>
-
- <custom:custom>
- <custom:title>Not in substitution group</custom:title>
- </custom:custom>
-
- <custom:usingProv>
- <custom:title>In substitution group</custom:title>
- <prov:wasDerivedFrom>
- <prov:generatedEntity prov:ref="e2"/>
- <prov:usedEntity prov:ref="e1"/>
- </prov:wasDerivedFrom>
- <prov:activity prov:id="a1">
- </prov:activity>
- </custom:usingProv>
-
- <prov:wasAttributedTo>
- <prov:entity prov:ref="e1"></prov:entity>
- <prov:agent prov:ref="ag1" />
- <custom:customAttribute>
- <custom:title>Fails unless custom:title is present</custom:title>
- </custom:customAttribute>
- </prov:wasAttributedTo>
-
-
-</prov:document>
--- a/xml/examples/custom.xsd Fri Apr 26 09:26:16 2013 +0100
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,25 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
- targetNamespace="http://www.example.org/custom" xmlns:tns="http://www.example.org/custom"
- elementFormDefault="qualified" xmlns:prov="http://www.w3.org/ns/prov#">
- <xsd:import schemaLocation="../schema/prov.xsd" namespace="http://www.w3.org/ns/prov#"></xsd:import>
-
- <xsd:element name="usingProvInside">
- <xsd:complexType>
- <xsd:sequence>
- <xsd:element name="title" />
- <xsd:element ref="prov:wasDerivedFrom" />
- <xsd:element ref="prov:activity" />
- </xsd:sequence>
- </xsd:complexType>
- </xsd:element>
-
- <xsd:element name="customAttribute">
- <xsd:complexType>
- <xsd:sequence>
- <xsd:element name="title" />
- </xsd:sequence>
- </xsd:complexType>
- </xsd:element>
-
-</xsd:schema>
\ No newline at end of file
--- a/xml/examples/pc1-full.xml Fri Apr 26 09:26:16 2013 +0100
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,756 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
-<prov:container xmlns:prov="http://www.w3.org/ns/prov-xml#" xmlns:prim="http://openprovenance.org/primitives#" xmlns:pc1="http://www.ipaw.info/pc1/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
- <prov:records>
- <prov:activity prov:id="pc1:00000p1">
- <prov:label>align_warp 1</prov:label>
- <prov:type xsi:type="xsd:QName">prim:align_warp</prov:type>
- <prov:type xsi:type="xsd:QName">prim:align_warp</prov:type>
- <prov:type xsi:type="xsd:int">10</prov:type>
- <prov:type xsi:type="xsd:int">-10</prov:type>
- <prov:type xsi:type="xsd:double">-10.55</prov:type>
- <prov:type xsi:type="xsd:string">abc</prov:type>
- <prov:type xsi:type="xsd:boolean">true</prov:type>
- <prov:type xsi:type="xsd:anyURI">http://www.example.com/hi</prov:type>
- </prov:activity>
- <prov:activity prov:id="pc1:p2">
- <prov:label>align_warp 2</prov:label>
- <prov:type xsi:type="xsd:QName">prim:align_warp</prov:type>
- </prov:activity>
- <prov:activity prov:id="pc1:p3">
- <prov:label>align_warp 3</prov:label>
- <prov:type xsi:type="xsd:QName">prim:align_warp</prov:type>
- </prov:activity>
- <prov:activity prov:id="pc1:p4">
- <prov:label>align_warp 4</prov:label>
- <prov:type xsi:type="xsd:QName">prim:align_warp</prov:type>
- </prov:activity>
- <prov:activity prov:id="pc1:p5">
- <prov:label>Reslice 1</prov:label>
- <prov:type xsi:type="xsd:anyURI">http://openprovenance.org/primitives#reslice</prov:type>
- </prov:activity>
- <prov:activity prov:id="pc1:p6">
- <prov:label>Reslice 2</prov:label>
- <prov:type xsi:type="xsd:anyURI">http://openprovenance.org/primitives#reslice</prov:type>
- </prov:activity>
- <prov:activity prov:id="pc1:p7">
- <prov:label>Reslice 3</prov:label>
- <prov:type xsi:type="xsd:anyURI">http://openprovenance.org/primitives#reslice</prov:type>
- </prov:activity>
- <prov:activity prov:id="pc1:p8">
- <prov:label>Reslice 4</prov:label>
- <prov:type xsi:type="xsd:anyURI">http://openprovenance.org/primitives#reslice</prov:type>
- </prov:activity>
- <prov:activity prov:id="pc1:p9">
- <prov:label>Softmean</prov:label>
- <prov:type xsi:type="xsd:anyURI">http://openprovenance.org/primitives#softmean</prov:type>
- </prov:activity>
- <prov:activity prov:id="pc1:p10">
- <prov:label>Slicer 1</prov:label>
- <prov:type xsi:type="xsd:anyURI">http://openprovenance.org/primitives#slicer</prov:type>
- </prov:activity>
- <prov:activity prov:id="pc1:p11">
- <prov:label>Slicer 2</prov:label>
- <prov:type xsi:type="xsd:anyURI">http://openprovenance.org/primitives#slicer</prov:type>
- </prov:activity>
- <prov:activity prov:id="pc1:p12">
- <prov:label>Slicer 3</prov:label>
- <prov:type xsi:type="xsd:anyURI">http://openprovenance.org/primitives#slicer</prov:type>
- </prov:activity>
- <prov:activity prov:id="pc1:p13">
- <prov:label>Convert 1</prov:label>
- <prov:type xsi:type="xsd:anyURI">http://openprovenance.org/primitives#convert</prov:type>
- </prov:activity>
- <prov:activity prov:id="pc1:p14">
- <prov:label>Convert 2</prov:label>
- <prov:type xsi:type="xsd:anyURI">http://openprovenance.org/primitives#convert</prov:type>
- </prov:activity>
- <prov:activity prov:id="pc1:p15">
- <prov:label>Convert 3</prov:label>
- <prov:type xsi:type="xsd:anyURI">http://openprovenance.org/primitives#convert</prov:type>
- </prov:activity>
- <prov:entity prov:id="pc1:a1">
- <prov:label>Reference Image</prov:label>
- <prov:type xsi:type="xsd:anyURI">http://openprovenance.org/primitives#File</prov:type>
- <pc1:url>http://www.ipaw.info/challenge/reference.img</pc1:url>
- </prov:entity>
- <prov:entity prov:id="pc1:a2">
- <prov:label>Reference Header</prov:label>
- <prov:type xsi:type="xsd:anyURI">http://openprovenance.org/primitives#File</prov:type>
- <pc1:url>http://www.ipaw.info/challenge/reference.hdr</pc1:url>
- </prov:entity>
- <prov:entity prov:id="pc1:a5">
- <prov:label>Anatomy I2</prov:label>
- <prov:type xsi:type="xsd:anyURI">http://openprovenance.org/primitives#File</prov:type>
- <pc1:url>http://www.ipaw.info/challenge/anatomy2.img</pc1:url>
- </prov:entity>
- <prov:entity prov:id="pc1:a6">
- <prov:label>Anatomy H2</prov:label>
- <prov:type xsi:type="xsd:anyURI">http://openprovenance.org/primitives#File</prov:type>
- <pc1:url>http://www.ipaw.info/challenge/anatomy2.hdr</pc1:url>
- </prov:entity>
- <prov:entity prov:id="pc1:a3">
- <prov:label>Anatomy I1</prov:label>
- <prov:type xsi:type="xsd:anyURI">http://openprovenance.org/primitives#File</prov:type>
- <pc1:url>http://www.ipaw.info/challenge/anatomy1.img</pc1:url>
- </prov:entity>
- <prov:entity prov:id="pc1:a4">
- <prov:label>Anatomy H1</prov:label>
- <prov:type xsi:type="xsd:anyURI">http://openprovenance.org/primitives#File</prov:type>
- <pc1:url>http://www.ipaw.info/challenge/anatomy1.hdr</pc1:url>
- </prov:entity>
- <prov:entity prov:id="pc1:a7">
- <prov:label>Anatomy I3</prov:label>
- <prov:type xsi:type="xsd:anyURI">http://openprovenance.org/primitives#File</prov:type>
- <pc1:url>http://www.ipaw.info/challenge/anatomy3.img</pc1:url>
- </prov:entity>
- <prov:entity prov:id="pc1:a8">
- <prov:label>Anatomy H3</prov:label>
- <prov:type xsi:type="xsd:anyURI">http://openprovenance.org/primitives#File</prov:type>
- <pc1:url>http://www.ipaw.info/challenge/anatomy3.hdr</pc1:url>
- </prov:entity>
- <prov:entity prov:id="pc1:a9">
- <prov:label>Anatomy I4</prov:label>
- <prov:type xsi:type="xsd:anyURI">http://openprovenance.org/primitives#File</prov:type>
- <pc1:url>http://www.ipaw.info/challenge/anatomy4.img</pc1:url>
- </prov:entity>
- <prov:entity prov:id="pc1:a10">
- <prov:label>Anatomy H4</prov:label>
- <prov:type xsi:type="xsd:anyURI">http://openprovenance.org/primitives#File</prov:type>
- <pc1:url>http://www.ipaw.info/challenge/anatomy4.hdr</pc1:url>
- </prov:entity>
- <prov:entity prov:id="pc1:a11">
- <prov:label>Warp Params1</prov:label>
- <prov:type xsi:type="xsd:anyURI">http://openprovenance.org/primitives#File</prov:type>
- <pc1:url>http://www.ipaw.info/challenge/warp1.warp</pc1:url>
- </prov:entity>
- <prov:entity prov:id="pc1:a12">
- <prov:label>Warp Params2</prov:label>
- <prov:type xsi:type="xsd:anyURI">http://openprovenance.org/primitives#File</prov:type>
- <pc1:url>http://www.ipaw.info/challenge/warp2.warp</pc1:url>
- </prov:entity>
- <prov:entity prov:id="pc1:a13">
- <prov:label>Warp Params3</prov:label>
- <prov:type xsi:type="xsd:anyURI">http://openprovenance.org/primitives#File</prov:type>
- <pc1:url>http://www.ipaw.info/challenge/warp3.warp</pc1:url>
- </prov:entity>
- <prov:entity prov:id="pc1:a14">
- <prov:label>Warp Params4</prov:label>
- <prov:type xsi:type="xsd:anyURI">http://openprovenance.org/primitives#File</prov:type>
- <pc1:url>http://www.ipaw.info/challenge/warp4.warp</pc1:url>
- </prov:entity>
- <prov:entity prov:id="pc1:a15">
- <prov:label>Resliced I1</prov:label>
- <prov:type xsi:type="xsd:anyURI">http://openprovenance.org/primitives#File</prov:type>
- <pc1:url>http://www.ipaw.info/challenge/resliced1.img</pc1:url>
- </prov:entity>
- <prov:entity prov:id="pc1:a16">
- <prov:label>Resliced H1</prov:label>
- <prov:type xsi:type="xsd:anyURI">http://openprovenance.org/primitives#File</prov:type>
- <pc1:url>http://www.ipaw.info/challenge/resliced1.hdr</pc1:url>
- </prov:entity>
- <prov:entity prov:id="pc1:a17">
- <prov:label>Resliced I2</prov:label>
- <prov:type xsi:type="xsd:anyURI">http://openprovenance.org/primitives#File</prov:type>
- <pc1:url>http://www.ipaw.info/challenge/resliced2.img</pc1:url>
- </prov:entity>
- <prov:entity prov:id="pc1:a18">
- <prov:label>Resliced H2</prov:label>
- <prov:type xsi:type="xsd:anyURI">http://openprovenance.org/primitives#File</prov:type>
- <pc1:url>http://www.ipaw.info/challenge/resliced2.hdr</pc1:url>
- </prov:entity>
- <prov:entity prov:id="pc1:a19">
- <prov:label>Resliced I3</prov:label>
- <prov:type xsi:type="xsd:anyURI">http://openprovenance.org/primitives#File</prov:type>
- <pc1:url>http://www.ipaw.info/challenge/resliced3.img</pc1:url>
- </prov:entity>
- <prov:entity prov:id="pc1:a20">
- <prov:label>Resliced H3</prov:label>
- <prov:type xsi:type="xsd:anyURI">http://openprovenance.org/primitives#File</prov:type>
- <pc1:url>http://www.ipaw.info/challenge/resliced3.hdr</pc1:url>
- </prov:entity>
- <prov:entity prov:id="pc1:a21">
- <prov:label>Resliced I4</prov:label>
- <prov:type xsi:type="xsd:anyURI">http://openprovenance.org/primitives#File</prov:type>
- <pc1:url>http://www.ipaw.info/challenge/resliced4.img</pc1:url>
- </prov:entity>
- <prov:entity prov:id="pc1:a22">
- <prov:label>Resliced H4</prov:label>
- <prov:type xsi:type="xsd:anyURI">http://openprovenance.org/primitives#File</prov:type>
- <pc1:url>http://www.ipaw.info/challenge/resliced4.hdr</pc1:url>
- </prov:entity>
- <prov:entity prov:id="pc1:a23">
- <prov:label>Atlas Image</prov:label>
- <prov:type xsi:type="xsd:anyURI">http://openprovenance.org/primitives#File</prov:type>
- <pc1:url>http://www.ipaw.info/challenge/atlas.img</pc1:url>
- </prov:entity>
- <prov:entity prov:id="pc1:a24">
- <prov:label>Atlas Header</prov:label>
- <prov:type xsi:type="xsd:anyURI">http://openprovenance.org/primitives#File</prov:type>
- <pc1:url>http://www.ipaw.info/challenge/atlas.hdr</pc1:url>
- </prov:entity>
- <prov:entity prov:id="pc1:a25">
- <prov:label>Atlas X Slice</prov:label>
- <prov:type xsi:type="xsd:anyURI">http://openprovenance.org/primitives#File</prov:type>
- <pc1:url>http://www.ipaw.info/challenge/atlas-x.pgm</pc1:url>
- </prov:entity>
- <prov:entity prov:id="pc1:a25p">
- <prov:label>slicer param 1</prov:label>
- <prov:type xsi:type="xsd:string">http://openprovenance.org/primitives#String</prov:type>
- <pc1:value>-x .5</pc1:value>
- </prov:entity>
- <prov:entity prov:id="pc1:a26">
- <prov:label>Atlas Y Slice</prov:label>
- <prov:type xsi:type="xsd:anyURI">http://openprovenance.org/primitives#File</prov:type>
- <pc1:url>http://www.ipaw.info/challenge/atlas-y.pgm</pc1:url>
- </prov:entity>
- <prov:entity prov:id="pc1:a26p">
- <prov:label>slicer param 2</prov:label>
- <prov:type xsi:type="xsd:string">http://openprovenance.org/primitives#String</prov:type>
- <pc1:value>-y .5</pc1:value>
- </prov:entity>
- <prov:entity prov:id="pc1:a27">
- <prov:label>Atlas Z Slice</prov:label>
- <prov:type xsi:type="xsd:anyURI">http://openprovenance.org/primitives#File</prov:type>
- <pc1:url>http://www.ipaw.info/challenge/atlas-z.pgm</pc1:url>
- </prov:entity>
- <prov:entity prov:id="pc1:a27p">
- <prov:label>slicer param 3</prov:label>
- <prov:type xsi:type="xsd:string">http://openprovenance.org/primitives#String</prov:type>
- <pc1:value>-z .5</pc1:value>
- </prov:entity>
- <prov:entity prov:id="pc1:a28">
- <prov:label>Atlas X Graphic</prov:label>
- <prov:type xsi:type="xsd:anyURI">http://openprovenance.org/primitives#File</prov:type>
- <pc1:url>http://www.ipaw.info/challenge/atlas-x.gif</pc1:url>
- </prov:entity>
- <prov:entity prov:id="pc1:a29">
- <prov:label>Atlas Y Graphic</prov:label>
- <prov:type xsi:type="xsd:anyURI">http://openprovenance.org/primitives#File</prov:type>
- <pc1:url>http://www.ipaw.info/challenge/atlas-y.gif</pc1:url>
- </prov:entity>
- <prov:entity prov:id="pc1:a30">
- <prov:label>Atlas Z Graphic</prov:label>
- <prov:type xsi:type="xsd:anyURI">http://openprovenance.org/primitives#File</prov:type>
- <pc1:url>http://www.ipaw.info/challenge/atlas-z.gif</pc1:url>
- </prov:entity>
- <prov:agent prov:id="pc1:ag1">
- <prov:label>John Doe</prov:label>
- </prov:agent>
- <prov:note prov:id="pc1:n1">
- <pc1:color>red</pc1:color>
- </prov:note>
- <prov:dependencies>
- <prov:used>
- <prov:activity prov:ref="pc1:00000p1"/>
- <prov:entity prov:ref="pc1:a3"/>
- <prov:role xsi:type="xsd:string">img</prov:role>
- </prov:used>
- <prov:used>
- <prov:activity prov:ref="pc1:00000p1"/>
- <prov:entity prov:ref="pc1:a4"/>
- <prov:role xsi:type="xsd:string">hdr</prov:role>
- </prov:used>
- <prov:used prov:id="pc1:u3">
- <prov:activity prov:ref="pc1:00000p1"/>
- <prov:entity prov:ref="pc1:a1"/>
- <prov:role xsi:type="xsd:string">imgRef</prov:role>
- </prov:used>
- <prov:used>
- <prov:activity prov:ref="pc1:00000p1"/>
- <prov:entity prov:ref="pc1:a2"/>
- <prov:role xsi:type="xsd:string">hdrRef</prov:role>
- </prov:used>
- <prov:used>
- <prov:activity prov:ref="pc1:p2"/>
- <prov:entity prov:ref="pc1:a5"/>
- <prov:role xsi:type="xsd:string">img</prov:role>
- </prov:used>
- <prov:used>
- <prov:activity prov:ref="pc1:p2"/>
- <prov:entity prov:ref="pc1:a6"/>
- <prov:role xsi:type="xsd:string">hdr</prov:role>
- </prov:used>
- <prov:used>
- <prov:activity prov:ref="pc1:p2"/>
- <prov:entity prov:ref="pc1:a1"/>
- <prov:role xsi:type="xsd:string">imgRef</prov:role>
- </prov:used>
- <prov:used>
- <prov:activity prov:ref="pc1:p2"/>
- <prov:entity prov:ref="pc1:a2"/>
- <prov:role xsi:type="xsd:string">hdrRef</prov:role>
- </prov:used>
- <prov:used>
- <prov:activity prov:ref="pc1:p3"/>
- <prov:entity prov:ref="pc1:a7"/>
- <prov:role xsi:type="xsd:string">img</prov:role>
- </prov:used>
- <prov:used>
- <prov:activity prov:ref="pc1:p3"/>
- <prov:entity prov:ref="pc1:a8"/>
- <prov:role xsi:type="xsd:string">hdr</prov:role>
- </prov:used>
- <prov:used>
- <prov:activity prov:ref="pc1:p3"/>
- <prov:entity prov:ref="pc1:a1"/>
- <prov:role xsi:type="xsd:string">imgRef</prov:role>
- </prov:used>
- <prov:used>
- <prov:activity prov:ref="pc1:p3"/>
- <prov:entity prov:ref="pc1:a2"/>
- <prov:role xsi:type="xsd:string">hdrRef</prov:role>
- </prov:used>
- <prov:used>
- <prov:activity prov:ref="pc1:p4"/>
- <prov:entity prov:ref="pc1:a9"/>
- <prov:role xsi:type="xsd:string">img</prov:role>
- </prov:used>
- <prov:used>
- <prov:activity prov:ref="pc1:p4"/>
- <prov:entity prov:ref="pc1:a10"/>
- <prov:role xsi:type="xsd:string">hdr</prov:role>
- </prov:used>
- <prov:used>
- <prov:activity prov:ref="pc1:p4"/>
- <prov:entity prov:ref="pc1:a1"/>
- <prov:role xsi:type="xsd:string">imgRef</prov:role>
- </prov:used>
- <prov:used>
- <prov:activity prov:ref="pc1:p4"/>
- <prov:entity prov:ref="pc1:a2"/>
- <prov:role xsi:type="xsd:string">hdrRef</prov:role>
- </prov:used>
- <prov:used>
- <prov:activity prov:ref="pc1:p5"/>
- <prov:entity prov:ref="pc1:a11"/>
- <prov:role xsi:type="xsd:string">in</prov:role>
- </prov:used>
- <prov:used>
- <prov:activity prov:ref="pc1:p6"/>
- <prov:entity prov:ref="pc1:a12"/>
- <prov:role xsi:type="xsd:string">in</prov:role>
- </prov:used>
- <prov:used>
- <prov:activity prov:ref="pc1:p7"/>
- <prov:entity prov:ref="pc1:a13"/>
- <prov:role xsi:type="xsd:string">in</prov:role>
- </prov:used>
- <prov:used>
- <prov:activity prov:ref="pc1:p8"/>
- <prov:entity prov:ref="pc1:a14"/>
- <prov:role xsi:type="xsd:string">in</prov:role>
- </prov:used>
- <prov:used>
- <prov:activity prov:ref="pc1:p9"/>
- <prov:entity prov:ref="pc1:a15"/>
- <prov:role xsi:type="xsd:string">i1</prov:role>
- </prov:used>
- <prov:used>
- <prov:activity prov:ref="pc1:p9"/>
- <prov:entity prov:ref="pc1:a16"/>
- <prov:role xsi:type="xsd:string">h1</prov:role>
- </prov:used>
- <prov:used>
- <prov:activity prov:ref="pc1:p9"/>
- <prov:entity prov:ref="pc1:a17"/>
- <prov:role xsi:type="xsd:string">i2</prov:role>
- </prov:used>
- <prov:used>
- <prov:activity prov:ref="pc1:p9"/>
- <prov:entity prov:ref="pc1:a18"/>
- <prov:role xsi:type="xsd:string">h2</prov:role>
- </prov:used>
- <prov:used>
- <prov:activity prov:ref="pc1:p9"/>
- <prov:entity prov:ref="pc1:a19"/>
- <prov:role xsi:type="xsd:string">i3</prov:role>
- </prov:used>
- <prov:used>
- <prov:activity prov:ref="pc1:p9"/>
- <prov:entity prov:ref="pc1:a20"/>
- <prov:role xsi:type="xsd:string">h3</prov:role>
- </prov:used>
- <prov:used>
- <prov:activity prov:ref="pc1:p9"/>
- <prov:entity prov:ref="pc1:a21"/>
- <prov:role xsi:type="xsd:string">i4</prov:role>
- </prov:used>
- <prov:used>
- <prov:activity prov:ref="pc1:p9"/>
- <prov:entity prov:ref="pc1:a22"/>
- <prov:role xsi:type="xsd:string">h4</prov:role>
- </prov:used>
- <prov:used>
- <prov:activity prov:ref="pc1:p10"/>
- <prov:entity prov:ref="pc1:a23"/>
- <prov:role xsi:type="xsd:string">img</prov:role>
- </prov:used>
- <prov:used>
- <prov:activity prov:ref="pc1:p10"/>
- <prov:entity prov:ref="pc1:a24"/>
- <prov:role xsi:type="xsd:string">hdr</prov:role>
- </prov:used>
- <prov:used>
- <prov:activity prov:ref="pc1:p11"/>
- <prov:entity prov:ref="pc1:a23"/>
- <prov:role xsi:type="xsd:string">img</prov:role>
- </prov:used>
- <prov:used>
- <prov:activity prov:ref="pc1:p11"/>
- <prov:entity prov:ref="pc1:a24"/>
- <prov:role xsi:type="xsd:string">hdr</prov:role>
- </prov:used>
- <prov:used>
- <prov:activity prov:ref="pc1:p12"/>
- <prov:entity prov:ref="pc1:a23"/>
- <prov:role xsi:type="xsd:string">img</prov:role>
- </prov:used>
- <prov:used>
- <prov:activity prov:ref="pc1:p12"/>
- <prov:entity prov:ref="pc1:a24"/>
- <prov:role xsi:type="xsd:string">hdr</prov:role>
- </prov:used>
- <prov:used>
- <prov:activity prov:ref="pc1:p10"/>
- <prov:entity prov:ref="pc1:a25p"/>
- <prov:role xsi:type="xsd:string">param</prov:role>
- </prov:used>
- <prov:used>
- <prov:activity prov:ref="pc1:p11"/>
- <prov:entity prov:ref="pc1:a26p"/>
- <prov:role xsi:type="xsd:string">param</prov:role>
- </prov:used>
- <prov:used>
- <prov:activity prov:ref="pc1:p12"/>
- <prov:entity prov:ref="pc1:a27p"/>
- <prov:role xsi:type="xsd:string">param</prov:role>
- </prov:used>
- <prov:used>
- <prov:activity prov:ref="pc1:p13"/>
- <prov:entity prov:ref="pc1:a25"/>
- <prov:role xsi:type="xsd:string">in</prov:role>
- </prov:used>
- <prov:used>
- <prov:activity prov:ref="pc1:p14"/>
- <prov:entity prov:ref="pc1:a26"/>
- <prov:role xsi:type="xsd:string">in</prov:role>
- </prov:used>
- <prov:used>
- <prov:activity prov:ref="pc1:p15"/>
- <prov:entity prov:ref="pc1:a27"/>
- <prov:role xsi:type="xsd:string">in</prov:role>
- </prov:used>
- <prov:wasGeneratedBy prov:id="pc1:wgb1">
- <prov:entity prov:ref="pc1:a11"/>
- <prov:activity prov:ref="pc1:00000p1"/>
- <prov:role xsi:type="xsd:string">out</prov:role>
- </prov:wasGeneratedBy>
- <prov:wasGeneratedBy>
- <prov:entity prov:ref="pc1:a12"/>
- <prov:activity prov:ref="pc1:p2"/>
- <prov:role xsi:type="xsd:string">out</prov:role>
- </prov:wasGeneratedBy>
- <prov:wasGeneratedBy>
- <prov:entity prov:ref="pc1:a13"/>
- <prov:activity prov:ref="pc1:p3"/>
- <prov:role xsi:type="xsd:string">out</prov:role>
- </prov:wasGeneratedBy>
- <prov:wasGeneratedBy>
- <prov:entity prov:ref="pc1:a14"/>
- <prov:activity prov:ref="pc1:p4"/>
- <prov:role xsi:type="xsd:string">out</prov:role>
- </prov:wasGeneratedBy>
- <prov:wasGeneratedBy>
- <prov:entity prov:ref="pc1:a15"/>
- <prov:activity prov:ref="pc1:p5"/>
- <prov:role xsi:type="xsd:string">img</prov:role>
- </prov:wasGeneratedBy>
- <prov:wasGeneratedBy>
- <prov:entity prov:ref="pc1:a16"/>
- <prov:activity prov:ref="pc1:p5"/>
- <prov:role xsi:type="xsd:string">hdr</prov:role>
- </prov:wasGeneratedBy>
- <prov:wasGeneratedBy>
- <prov:entity prov:ref="pc1:a17"/>
- <prov:activity prov:ref="pc1:p6"/>
- <prov:role xsi:type="xsd:string">img</prov:role>
- </prov:wasGeneratedBy>
- <prov:wasGeneratedBy>
- <prov:entity prov:ref="pc1:a18"/>
- <prov:activity prov:ref="pc1:p6"/>
- <prov:role xsi:type="xsd:string">hdr</prov:role>
- </prov:wasGeneratedBy>
- <prov:wasGeneratedBy>
- <prov:entity prov:ref="pc1:a19"/>
- <prov:activity prov:ref="pc1:p7"/>
- <prov:role xsi:type="xsd:string">img</prov:role>
- </prov:wasGeneratedBy>
- <prov:wasGeneratedBy>
- <prov:entity prov:ref="pc1:a20"/>
- <prov:activity prov:ref="pc1:p7"/>
- <prov:role xsi:type="xsd:string">hdr</prov:role>
- </prov:wasGeneratedBy>
- <prov:wasGeneratedBy>
- <prov:entity prov:ref="pc1:a21"/>
- <prov:activity prov:ref="pc1:p8"/>
- <prov:role xsi:type="xsd:string">img</prov:role>
- </prov:wasGeneratedBy>
- <prov:wasGeneratedBy>
- <prov:entity prov:ref="pc1:a22"/>
- <prov:activity prov:ref="pc1:p8"/>
- <prov:role xsi:type="xsd:string">hdr</prov:role>
- </prov:wasGeneratedBy>
- <prov:wasGeneratedBy>
- <prov:entity prov:ref="pc1:a23"/>
- <prov:activity prov:ref="pc1:p9"/>
- <prov:role xsi:type="xsd:string">img</prov:role>
- </prov:wasGeneratedBy>
- <prov:wasGeneratedBy>
- <prov:entity prov:ref="pc1:a24"/>
- <prov:activity prov:ref="pc1:p9"/>
- <prov:role xsi:type="xsd:string">hdr</prov:role>
- </prov:wasGeneratedBy>
- <prov:wasGeneratedBy>
- <prov:entity prov:ref="pc1:a25"/>
- <prov:activity prov:ref="pc1:p10"/>
- <prov:role xsi:type="xsd:string">out</prov:role>
- </prov:wasGeneratedBy>
- <prov:wasGeneratedBy>
- <prov:entity prov:ref="pc1:a26"/>
- <prov:activity prov:ref="pc1:p11"/>
- <prov:role xsi:type="xsd:string">out</prov:role>
- </prov:wasGeneratedBy>
- <prov:wasGeneratedBy>
- <prov:entity prov:ref="pc1:a27"/>
- <prov:activity prov:ref="pc1:p12"/>
- <prov:role xsi:type="xsd:string">out</prov:role>
- </prov:wasGeneratedBy>
- <prov:wasGeneratedBy>
- <prov:time>2012-01-31T22:15:54.067Z</prov:time>
- <prov:entity prov:ref="pc1:a28"/>
- <prov:activity prov:ref="pc1:p13"/>
- <prov:role xsi:type="xsd:string">out</prov:role>
- </prov:wasGeneratedBy>
- <prov:wasGeneratedBy>
- <prov:time>2012-01-31T22:15:54.097Z</prov:time>
- <prov:entity prov:ref="pc1:a29"/>
- <prov:activity prov:ref="pc1:p14"/>
- <prov:role xsi:type="xsd:string">out</prov:role>
- </prov:wasGeneratedBy>
- <prov:wasGeneratedBy>
- <prov:time>2012-01-31T22:15:54.097Z</prov:time>
- <prov:entity prov:ref="pc1:a30"/>
- <prov:activity prov:ref="pc1:p15"/>
- <prov:role xsi:type="xsd:string">out</prov:role>
- </prov:wasGeneratedBy>
- <prov:wasDerivedFrom>
- <prov:generation prov:ref="pc1:wgb1"/>
- <prov:usage prov:ref="pc1:u3"/>
- <prov:activity prov:ref="pc1:00000p1"/>
- <prov:effect prov:ref="pc1:a11"/>
- <prov:cause prov:ref="pc1:a1"/>
- </prov:wasDerivedFrom>
- <prov:wasDerivedFrom>
- <prov:effect prov:ref="pc1:a11"/>
- <prov:cause prov:ref="pc1:a2"/>
- </prov:wasDerivedFrom>
- <prov:wasDerivedFrom>
- <prov:effect prov:ref="pc1:a11"/>
- <prov:cause prov:ref="pc1:a3"/>
- </prov:wasDerivedFrom>
- <prov:wasDerivedFrom>
- <prov:effect prov:ref="pc1:a11"/>
- <prov:cause prov:ref="pc1:a4"/>
- </prov:wasDerivedFrom>
- <prov:wasDerivedFrom>
- <prov:effect prov:ref="pc1:a12"/>
- <prov:cause prov:ref="pc1:a1"/>
- </prov:wasDerivedFrom>
- <prov:wasDerivedFrom>
- <prov:effect prov:ref="pc1:a12"/>
- <prov:cause prov:ref="pc1:a2"/>
- </prov:wasDerivedFrom>
- <prov:wasDerivedFrom>
- <prov:effect prov:ref="pc1:a12"/>
- <prov:cause prov:ref="pc1:a5"/>
- </prov:wasDerivedFrom>
- <prov:wasDerivedFrom>
- <prov:effect prov:ref="pc1:a12"/>
- <prov:cause prov:ref="pc1:a6"/>
- </prov:wasDerivedFrom>
- <prov:wasDerivedFrom>
- <prov:effect prov:ref="pc1:a13"/>
- <prov:cause prov:ref="pc1:a1"/>
- </prov:wasDerivedFrom>
- <prov:wasDerivedFrom>
- <prov:effect prov:ref="pc1:a13"/>
- <prov:cause prov:ref="pc1:a2"/>
- </prov:wasDerivedFrom>
- <prov:wasDerivedFrom>
- <prov:effect prov:ref="pc1:a13"/>
- <prov:cause prov:ref="pc1:a7"/>
- </prov:wasDerivedFrom>
- <prov:wasDerivedFrom>
- <prov:effect prov:ref="pc1:a13"/>
- <prov:cause prov:ref="pc1:a8"/>
- </prov:wasDerivedFrom>
- <prov:wasDerivedFrom>
- <prov:effect prov:ref="pc1:a14"/>
- <prov:cause prov:ref="pc1:a1"/>
- </prov:wasDerivedFrom>
- <prov:wasDerivedFrom>
- <prov:effect prov:ref="pc1:a14"/>
- <prov:cause prov:ref="pc1:a2"/>
- </prov:wasDerivedFrom>
- <prov:wasDerivedFrom>
- <prov:effect prov:ref="pc1:a14"/>
- <prov:cause prov:ref="pc1:a9"/>
- </prov:wasDerivedFrom>
- <prov:wasDerivedFrom>
- <prov:effect prov:ref="pc1:a14"/>
- <prov:cause prov:ref="pc1:a10"/>
- </prov:wasDerivedFrom>
- <prov:wasDerivedFrom>
- <prov:effect prov:ref="pc1:a15"/>
- <prov:cause prov:ref="pc1:a11"/>
- </prov:wasDerivedFrom>
- <prov:wasDerivedFrom>
- <prov:effect prov:ref="pc1:a16"/>
- <prov:cause prov:ref="pc1:a11"/>
- </prov:wasDerivedFrom>
- <prov:wasDerivedFrom>
- <prov:effect prov:ref="pc1:a17"/>
- <prov:cause prov:ref="pc1:a12"/>
- </prov:wasDerivedFrom>
- <prov:wasDerivedFrom>
- <prov:effect prov:ref="pc1:a18"/>
- <prov:cause prov:ref="pc1:a12"/>
- </prov:wasDerivedFrom>
- <prov:wasDerivedFrom>
- <prov:effect prov:ref="pc1:a19"/>
- <prov:cause prov:ref="pc1:a13"/>
- </prov:wasDerivedFrom>
- <prov:wasDerivedFrom>
- <prov:effect prov:ref="pc1:a20"/>
- <prov:cause prov:ref="pc1:a13"/>
- </prov:wasDerivedFrom>
- <prov:wasDerivedFrom>
- <prov:effect prov:ref="pc1:a21"/>
- <prov:cause prov:ref="pc1:a14"/>
- </prov:wasDerivedFrom>
- <prov:wasDerivedFrom>
- <prov:effect prov:ref="pc1:a22"/>
- <prov:cause prov:ref="pc1:a14"/>
- </prov:wasDerivedFrom>
- <prov:wasDerivedFrom>
- <prov:effect prov:ref="pc1:a23"/>
- <prov:cause prov:ref="pc1:a15"/>
- </prov:wasDerivedFrom>
- <prov:wasDerivedFrom>
- <prov:effect prov:ref="pc1:a23"/>
- <prov:cause prov:ref="pc1:a16"/>
- </prov:wasDerivedFrom>
- <prov:wasDerivedFrom>
- <prov:effect prov:ref="pc1:a23"/>
- <prov:cause prov:ref="pc1:a17"/>
- </prov:wasDerivedFrom>
- <prov:wasDerivedFrom>
- <prov:effect prov:ref="pc1:a23"/>
- <prov:cause prov:ref="pc1:a18"/>
- </prov:wasDerivedFrom>
- <prov:wasDerivedFrom>
- <prov:effect prov:ref="pc1:a23"/>
- <prov:cause prov:ref="pc1:a19"/>
- </prov:wasDerivedFrom>
- <prov:wasDerivedFrom>
- <prov:effect prov:ref="pc1:a23"/>
- <prov:cause prov:ref="pc1:a20"/>
- </prov:wasDerivedFrom>
- <prov:wasDerivedFrom>
- <prov:effect prov:ref="pc1:a23"/>
- <prov:cause prov:ref="pc1:a21"/>
- </prov:wasDerivedFrom>
- <prov:wasDerivedFrom>
- <prov:effect prov:ref="pc1:a23"/>
- <prov:cause prov:ref="pc1:a22"/>
- </prov:wasDerivedFrom>
- <prov:wasDerivedFrom>
- <prov:effect prov:ref="pc1:a24"/>
- <prov:cause prov:ref="pc1:a15"/>
- </prov:wasDerivedFrom>
- <prov:wasDerivedFrom>
- <prov:effect prov:ref="pc1:a24"/>
- <prov:cause prov:ref="pc1:a16"/>
- </prov:wasDerivedFrom>
- <prov:wasDerivedFrom>
- <prov:effect prov:ref="pc1:a24"/>
- <prov:cause prov:ref="pc1:a17"/>
- </prov:wasDerivedFrom>
- <prov:wasDerivedFrom>
- <prov:effect prov:ref="pc1:a24"/>
- <prov:cause prov:ref="pc1:a18"/>
- </prov:wasDerivedFrom>
- <prov:wasDerivedFrom>
- <prov:effect prov:ref="pc1:a24"/>
- <prov:cause prov:ref="pc1:a19"/>
- </prov:wasDerivedFrom>
- <prov:wasDerivedFrom>
- <prov:effect prov:ref="pc1:a24"/>
- <prov:cause prov:ref="pc1:a20"/>
- </prov:wasDerivedFrom>
- <prov:wasDerivedFrom>
- <prov:effect prov:ref="pc1:a24"/>
- <prov:cause prov:ref="pc1:a21"/>
- </prov:wasDerivedFrom>
- <prov:wasDerivedFrom>
- <prov:effect prov:ref="pc1:a24"/>
- <prov:cause prov:ref="pc1:a22"/>
- </prov:wasDerivedFrom>
- <prov:wasDerivedFrom>
- <prov:effect prov:ref="pc1:a25"/>
- <prov:cause prov:ref="pc1:a23"/>
- </prov:wasDerivedFrom>
- <prov:wasDerivedFrom>
- <prov:effect prov:ref="pc1:a25"/>
- <prov:cause prov:ref="pc1:a24"/>
- </prov:wasDerivedFrom>
- <prov:wasDerivedFrom>
- <prov:effect prov:ref="pc1:a26"/>
- <prov:cause prov:ref="pc1:a23"/>
- </prov:wasDerivedFrom>
- <prov:wasDerivedFrom>
- <prov:effect prov:ref="pc1:a26"/>
- <prov:cause prov:ref="pc1:a24"/>
- </prov:wasDerivedFrom>
- <prov:wasDerivedFrom>
- <prov:effect prov:ref="pc1:a27"/>
- <prov:cause prov:ref="pc1:a23"/>
- </prov:wasDerivedFrom>
- <prov:wasDerivedFrom>
- <prov:effect prov:ref="pc1:a27"/>
- <prov:cause prov:ref="pc1:a24"/>
- </prov:wasDerivedFrom>
- <prov:wasDerivedFrom>
- <prov:effect prov:ref="pc1:a28"/>
- <prov:cause prov:ref="pc1:a25"/>
- </prov:wasDerivedFrom>
- <prov:wasDerivedFrom>
- <prov:effect prov:ref="pc1:a29"/>
- <prov:cause prov:ref="pc1:a26"/>
- </prov:wasDerivedFrom>
- <prov:wasDerivedFrom>
- <prov:effect prov:ref="pc1:a30"/>
- <prov:cause prov:ref="pc1:a27"/>
- </prov:wasDerivedFrom>
- <prov:wasControlledBy>
- <prov:effect prov:ref="pc1:00000p1"/>
- <prov:cause prov:ref="pc1:ag1"/>
- <prov:role xsi:type="xsd:string">user</prov:role>
- </prov:wasControlledBy>
- <prov:hasAnnotation>
- <prov:thing prov:ref="pc1:a1"/>
- <prov:note prov:ref="pc1:n1"/>
- </prov:hasAnnotation>
- </prov:dependencies>
- </prov:records>
-</prov:container>
--- a/xml/examples/prov-all.xml Fri Apr 26 09:26:16 2013 +0100
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,43 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-
-<prov:document xmlns:xml="http://www.w3.org/XML/1998/namespace"
- xmlns:prov="http://www.w3.org/ns/prov#" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xmlns:foaf="http://xmlns.com/foaf/0.1/"
- xsi:schemaLocation="http://www.w3.org/ns/prov#
- ../schema/prov.xsd ">
-<!--
-A documenting that is mixing the various extensions included by prov.xsd
- -->
-
- <!--
- <prov:label>Not allowed here as there is no xs:element for prov:label </prov:label>
- -->
-
- <prov:entity prov:id="empty">
- <prov:label>Hello</prov:label>
- <prov:type>prov:EmptyCollection</prov:type>
- </prov:entity>
- <prov:person>
- <prov:type>foaf:Person</prov:type>
- <!--
- foaf:name is allowed because of processContent=lax in xsd:any
- -->
- <foaf:name>Stian Soiland-Reyes</foaf:name>
- <!-- But prov:activity is not allowed as it's in the prov: namespace
- <prov:activity></prov:activity>
- -->
- </prov:person>
-
- <prov:emptyDictionary prov:id="empty" />
-
- <prov:bundle>
- <prov:label>a label</prov:label>
- </prov:bundle>
-
- <prov:mentionOf>
- <prov:specificEntity prov:ref="a" />
- <prov:generalEntity prov:ref="b" />
- <prov:bundle prov:ref="c" />
- </prov:mentionOf>
-
-</prov:document>
\ No newline at end of file
--- a/xml/examples/with-extensions.xml Fri Apr 26 09:26:16 2013 +0100
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,115 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!--
-
-This is an example showing a mixture of PROV-XML and other XML schemas which
-have been made without any special PROV-XML provisioning. These can be used
-wherever there is a <xsd:any> in the PROV-XML schemas.
-
--
-Stian Soiland-Reyes
-2013-02-14
-
-
- -->
-<prov:document
- xmlns:xml="http://www.w3.org/XML/1998/namespace"
- xmlns:prov="http://www.w3.org/ns/prov#"
- xmlns:dcterms="http://purl.org/dc/terms/"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xmlns:mathml="http://www.w3.org/1998/Math/MathML"
- xmlns:xhtml="http://www.w3.org/1999/xhtml"
- xmlns:foaf="http://xmlns.com/foaf/0.1/"
-
- xsi:schemaLocation="http://www.w3.org/ns/prov#
- ../schema/prov.xsd
- http://www.w3.org/1999/xhtml
- http://www.w3.org/2002/08/xhtml/xhtml1-strict.xsd
- http://www.w3.org/1998/Math/MathML
- http://www.w3.org/Math/XMLSchema/mathml3/mathml3.xsd
- http://purl.org/dc/terms/
- http://dublincore.org/schemas/xmls/qdc/2008/02/11/dcterms.xsd">
-
-
- <prov:entity prov:id="someBook">
- <dcterms:title>A title</dcterms:title>
- <!-- Should perhaps not be valid as we have a schema for dcterms namespace,
- but unknown elements are allowed by processContent="lax" -->
- <dcterms:madeup>Expected 'No declaration for element dcterms:madeup'</dcterms:madeup>
- </prov:entity>
-
- <prov:person prov:id="fred">
- <!-- Valid even without a schema because of processContent="lax" -->
- <foaf:name>Fred</foaf:name>
-
- <xhtml:p>
- A <xhtml:strong>nice</xhtml:strong> person
- </xhtml:p>
- <!--
- <prov:location>prov: not allowed AFTER xs:any inside
- prov:entity and friends</prov:location>
- -->
-
- <!-- elements in schema will have to validate, though:
- <xhtml:p><xhtml:p>Can't nest paragraphs!</p></xhtml:p></xhtml:p>
- -->
- </prov:person>
-
- <!-- An <xs:any> element from a non-PROV schema -->
- <mathml:annotation-xml prov:id="formula"
- xmlns="http://www.w3.org/1998/Math/MathML">
- <mrow>
- <msup>
- <mfenced>
- <mrow>
- <mi>a</mi>
- <mo>+</mo>
- <mi>b</mi>
- </mrow>
- </mfenced>
- <mn>2</mn>
- </msup>
- </mrow>
-
- <!-- arbitrary nesting allowed back to prov because
- of xs:any in MathML. Note that this prov:wasAttributedTo
- should NOT be picked up by a PROV-XML-only parser, at least
- not as a part of the <prov:document>
- -->
- <prov:wasAttributedTo>
- <prov:entity prov:ref="formula"></prov:entity>
- <prov:agent prov:ref="fred"/>
- <dcterms:description>We have to play along with the PROV-XSD
- schema if we reuse a prov:element inside, so the above
- two elements are required.
- </dcterms:description>
- </prov:wasAttributedTo>
- </mathml:annotation-xml>
-
- <!-- prov:elements also allowed AFTER extensions -->
-
- <prov:bundleContent prov:id="bundle1">
- <!-- Mix and match -->
- <mathml:mi>a</mathml:mi>
- <prov:activity prov:id="bunddleEntity" />
- <!-- A nested bundle -->
- <prov:bundle prov:id="bundle2" />
- <mathml:mo></mathml:mo>
- </prov:bundleContent>
-
- <!-- The prov:bundle entity
- -->
- <prov:bundle prov:id="bundle1">
- <prov:label>A bundle</prov:label>
- <mathml:mi>a</mathml:mi>
- </prov:bundle>
-
- <!-- Content of nested bundle must be under <prov:document> -->
- <prov:bundleContent prov:id="bundle2">
- <!-- Mix and match -->
- <mathml:mi>a</mathml:mi>
- <prov:activity prov:id="bunddleEntity" />
- <mathml:mo></mathml:mo>
- </prov:bundleContent>
-
-
-</prov:document>
--- a/xml/experimental/extensions/all.xsd Fri Apr 26 09:26:16 2013 +0100
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,8 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
- targetNamespace="http://www.w3.org/ns/prov#" xmlns:prov="http://www.w3.org/ns/prov#"
- elementFormDefault="qualified">
- <xsd:include schemaLocation="prov.xsd" />
- <xsd:include schemaLocation="links.xsd" />
- <xsd:include schemaLocation="dictionary.xsd" />
-</xsd:schema>
\ No newline at end of file
--- a/xml/experimental/extensions/allExample.xml Fri Apr 26 09:26:16 2013 +0100
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,35 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<prov:container prov:id="QName" xmlns:prov="http://www.w3.org/ns/prov#"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:schemaLocation="http://www.w3.org/ns/prov# all.xsd ">
- <prov:records prov:id="QName">
- <prov:entity prov:id="member">
- <prov:label>The member</prov:label>
- </prov:entity>
- <prov:entity prov:id="general">
- <prov:label>General entity</prov:label>
- </prov:entity>
- <prov:entity prov:id="specific">
- <prov:label>Specific entity</prov:label>
- </prov:entity>
- <prov:dependencies>
- <prov:wasGeneratedBy>
- <prov:time>2001-12-31T12:00:00</prov:time>
- <prov:entity prov:ref="dictionary" />
- </prov:wasGeneratedBy>
- <prov:hasMember>
- <prov:collection prov:ref="dictionary" />
- <prov:member prov:ref="member" />
- <prov:key>key</prov:key>
- </prov:hasMember>
- <prov:mentionOf>
- <prov:specificEntity prov:ref="specific" />
- <prov:generalEntity prov:ref="general" />
- <prov:bundle prov:ref="bundle" />
- </prov:mentionOf>
- </prov:dependencies>
- <prov:dictionary prov:id="dictionary">
- <prov:label>The dictionary</prov:label>
- </prov:dictionary>
- </prov:records>
-</prov:container>
--- a/xml/experimental/extensions/dictionary.xsd Fri Apr 26 09:26:16 2013 +0100
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,24 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
- targetNamespace="http://www.w3.org/ns/prov#" xmlns:prov="http://www.w3.org/ns/prov#"
- elementFormDefault="qualified">
- <xsd:include schemaLocation="prov.xsd" />
-
- <!--
- Note: This is only an *example* of how dictionary membership could be expressed
- as an extension of prov.xsd
- -->
-
- <xsd:complexType name="Membership">
- <xsd:sequence>
- <xsd:element name="collection" type="prov:EntityRef" />
- <xsd:element name="member" type="prov:EntityRef" />
- <xsd:element name="key" type="xsd:string" minOccurs="0"/>
- </xsd:sequence>
- </xsd:complexType>
-
- <xsd:element name="dictionary" type="prov:Entity" substitutionGroup="prov:extraRecord" />
- <xsd:element name="hasMember" type="prov:Membership" substitutionGroup="prov:extraDependency" />
-
-
-</xsd:schema>
\ No newline at end of file
--- a/xml/experimental/extensions/dictionaryExample.xml Fri Apr 26 09:26:16 2013 +0100
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,20 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<prov:container prov:id="QName" xmlns:prov="http://www.w3.org/ns/prov#"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:schemaLocation="http://www.w3.org/ns/prov# dictionary.xsd ">
- <prov:records prov:id="QName">
- <prov:entity prov:id="member">
- <prov:label>The member</prov:label>
- </prov:entity>
- <prov:dependencies>
- <prov:hasMember>
- <prov:collection prov:ref="dictionary" />
- <prov:member prov:ref="member" />
- <prov:key>key</prov:key>
- </prov:hasMember>
- </prov:dependencies>
- <prov:dictionary prov:id="dictionary">
- <prov:label>The dictionary</prov:label>
- </prov:dictionary>
- </prov:records>
-</prov:container>
--- a/xml/experimental/extensions/links.xsd Fri Apr 26 09:26:16 2013 +0100
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,24 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
- targetNamespace="http://www.w3.org/ns/prov#" xmlns:prov="http://www.w3.org/ns/prov#"
- elementFormDefault="qualified">
- <xsd:include schemaLocation="prov.xsd" />
-
-<!--
- Note: This is only an *example* of how mentionOf could be expressed
- as an extension of prov.xsd
- -->
-
- <xsd:complexType name="Mention">
- <xsd:sequence>
- <xsd:element name="specificEntity" type="prov:EntityRef" />
- <xsd:element name="generalEntity" type="prov:EntityRef" />
- <xsd:element name="bundle" type="prov:EntityRef" />
- </xsd:sequence>
- </xsd:complexType>
-
- <xsd:element name="mentionOf" type="prov:Mention" substitutionGroup="prov:extraDependency" />
-
-
-
-</xsd:schema>
\ No newline at end of file
--- a/xml/experimental/extensions/linksExample.xml Fri Apr 26 09:26:16 2013 +0100
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,21 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-
-<prov:container prov:id="QName" xmlns:prov="http://www.w3.org/ns/prov#"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:schemaLocation="http://www.w3.org/ns/prov# links.xsd ">
- <prov:records prov:id="QName">
- <prov:entity prov:id="specific">
- <prov:label>Specific entity</prov:label>
- </prov:entity>
- <prov:entity prov:id="general">
- <prov:label>General entity</prov:label>
- </prov:entity>
- <prov:dependencies>
- <prov:mentionOf>
- <prov:specificEntity prov:ref="specific" />
- <prov:generalEntity prov:ref="general" />
- <prov:bundle prov:ref="bundle" />
- </prov:mentionOf>
- </prov:dependencies>
- </prov:records>
-</prov:container>
--- a/xml/experimental/extensions/prov.xsd Fri Apr 26 09:26:16 2013 +0100
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,386 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-
-<!-- work in progress.
-
- In this schema, all ids are encoded as QNames.
-
- Instead, a more permissive definition should be used such as CURIEs.
-
- Note that typical implementations won't recognize CURIEs :-(
-
- -->
-
-
-<xs:schema targetNamespace="http://www.w3.org/ns/prov#"
- xmlns:xs="http://www.w3.org/2001/XMLSchema"
- xmlns:prov="http://www.w3.org/ns/prov#"
- xmlns:cu="http://www.w3.org/1999/xhtml/datatypes/"
- elementFormDefault="qualified"
- attributeFormDefault="unqualified">
-
-
-
-<!-- CURIEs <xs:import namespace="http://www.w3.org/1999/xhtml/datatypes/" /> -->
-
-
- <!-- Component 1 -->
-
- <xs:element name="entity" type="prov:Entity"/>
- <xs:complexType name="Entity">
- <xs:sequence>
- <xs:element ref="prov:label" minOccurs="0"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
-
- <xs:any namespace="##other" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <xs:element name="activity" type="prov:Activity"/>
- <xs:complexType name="Activity">
- <xs:sequence>
- <xs:element name="startTime" type="xs:dateTime" minOccurs="0"/>
- <xs:element name="endTime" type="xs:dateTime" minOccurs="0"/>
- <xs:element ref="prov:label" minOccurs="0"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
-
- <xs:any namespace="##other" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
-
- <xs:complexType name="Used">
- <xs:sequence>
- <xs:element name="time" type="xs:dateTime" minOccurs="0"/>
- <xs:element name="activity" type="prov:ActivityRef"/>
- <xs:element name="entity" type="prov:EntityRef"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
-
- <xs:element ref="prov:role" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <xs:complexType name="WasGeneratedBy">
- <xs:sequence>
- <xs:element name="time" type="xs:dateTime" minOccurs="0"/>
- <xs:element name="entity" type="prov:EntityRef"/>
- <xs:element name="activity" type="prov:ActivityRef" minOccurs="0"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:role" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <xs:complexType name="WasStartedBy">
- <xs:sequence>
- <xs:element name="time" type="xs:dateTime" minOccurs="0"/>
- <xs:element name="activity" type="prov:ActivityRef"/>
- <xs:element name="trigger" type="prov:EntityRef" minOccurs="0"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:role" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <xs:complexType name="WasEndedBy">
- <xs:sequence>
- <xs:element name="time" type="xs:dateTime" minOccurs="0"/>
- <xs:element name="activity" type="prov:ActivityRef"/>
- <xs:element name="trigger" type="prov:EntityRef" minOccurs="0"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:role" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <xs:complexType name="WasInformedBy">
- <xs:sequence>
- <xs:element name="time" type="xs:dateTime" minOccurs="0"/>
- <xs:element name="effect" type="prov:ActivityRef"/>
- <xs:element name="cause" type="prov:ActivityRef"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:role" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <xs:complexType name="WasStartedByActivity">
- <xs:sequence>
- <xs:element name="started" type="prov:ActivityRef"/>
- <xs:element name="starter" type="prov:ActivityRef"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:role" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
-
- <!-- Component 2 -->
-
- <xs:element name="agent" type="prov:Agent"/>
- <xs:complexType name="Agent">
- <xs:sequence>
- <xs:element ref="prov:label" minOccurs="0"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <xs:complexType name="WasAssociatedWith">
- <xs:sequence>
- <xs:element name="activity" type="prov:ActivityRef"/>
- <xs:element name="agent" type="prov:AgentRef"/>
- <xs:element name="plan" type="prov:EntityRef" minOccurs="0"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:role" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
-
- <xs:complexType name="WasAttributedTo">
- <xs:sequence>
- <xs:element name="entity" type="prov:EntityRef"/>
- <xs:element name="agent" type="prov:AgentRef"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:role" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <xs:complexType name="ActedOnBehalfOf">
- <xs:sequence>
- <xs:element name="subordinate" type="prov:AgentRef"/>
- <xs:element name="responsible" type="prov:AgentRef"/>
- <xs:element name="activity" type="prov:ActivityRef"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:role" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
-
- <!-- Component 3 -->
-
-
- <xs:complexType name="WasDerivedFrom">
- <xs:sequence>
- <xs:element name="generation" type="prov:DependencyRef" minOccurs="0"/>
- <xs:element name="usage" type="prov:DependencyRef" minOccurs="0"/>
- <xs:element name="activity" type="prov:ActivityRef" minOccurs="0"/>
- <xs:element name="generatedEntity" type="prov:EntityRef"/>
- <xs:element name="usedEntity" type="prov:EntityRef"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:role" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <xs:complexType name="WasRevisionOf">
- <xs:sequence>
- <xs:element name="newer" type="prov:EntityRef"/>
- <xs:element name="older" type="prov:EntityRef"/>
- <xs:element name="responsibility" type="prov:AgentRef" minOccurs="0"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <xs:complexType name="WasQuotedFrom">
- <xs:sequence>
- <xs:element name="quote" type="prov:EntityRef"/>
- <xs:element name="original" type="prov:EntityRef"/>
- <xs:element name="quoterAgent" type="prov:AgentRef" minOccurs="0"/>
- <xs:element name="quotedAgent" type="prov:AgentRef" minOccurs="0"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <xs:complexType name="HadOriginalSource">
- <xs:sequence>
- <xs:element name="derived" type="prov:EntityRef"/>
- <xs:element name="source" type="prov:EntityRef"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <xs:complexType name="TracedTo">
- <xs:sequence>
- <xs:element name="entity" type="prov:EntityRef"/>
- <xs:element name="ancestor" type="prov:EntityRef"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <!-- Component 4 -->
-
- <xs:complexType name="AlternateOf">
- <xs:sequence>
- <xs:element name="entity2" type="prov:EntityRef"/>
- <xs:element name="entity1" type="prov:EntityRef"/>
- </xs:sequence>
- </xs:complexType>
-
- <xs:complexType name="SpecializationOf">
- <xs:sequence>
- <xs:element name="specializedEntity" type="prov:EntityRef"/>
- <xs:element name="generalEntity" type="prov:EntityRef"/>
- </xs:sequence>
- </xs:complexType>
-
- <!-- Component 5 -->
-
-
- <!-- Component 6 -->
-
- <xs:element name="note" type="prov:Note"/>
- <xs:complexType name="Note">
- <xs:sequence>
- <xs:any namespace="##other" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <xs:complexType name="HasAnnotation">
- <xs:sequence>
- <xs:element name="thing" type="prov:NoteRef" minOccurs="1"/> <!-- note, just a ref to anything, really -->
- <xs:element name="note" type="prov:NoteRef" minOccurs="1"/>
- <xs:any namespace="##other" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <!--
- Typed literals are encoded by means
- of xsi:type that represent the prov:datatype.
-
- -->
-
- <xs:element name="label" type="xs:string"/>
- <xs:element name="role" type="xs:anySimpleType"/>
- <xs:element name="type" type="xs:anySimpleType"/>
-
- <xs:attribute name="id" type="xs:QName"/>
- <xs:attribute name="ref" type="xs:QName"/>
-
- <xs:complexType name="ActivityRef">
- <xs:attribute ref="prov:ref"/>
- </xs:complexType>
- <xs:complexType name="EntityRef">
- <xs:attribute ref="prov:ref"/>
- </xs:complexType>
- <xs:complexType name="AgentRef">
- <xs:attribute ref="prov:ref"/>
- </xs:complexType>
-
- <xs:complexType name="DependencyRef">
- <xs:attribute ref="prov:ref"/>
- </xs:complexType>
-
- <xs:complexType name="NoteRef">
- <xs:attribute ref="prov:ref"/>
- </xs:complexType>
-
- <xs:complexType name="Dependencies">
- <xs:sequence>
- <xs:choice minOccurs="0" maxOccurs="unbounded">
-
- <xs:element name="used" type="prov:Used"/>
- <xs:element name="wasGeneratedBy" type="prov:WasGeneratedBy"/>
- <xs:element name="wasStartedBy" type="prov:WasStartedBy"/>
- <xs:element name="wasEndedBy" type="prov:WasEndedBy"/>
- <xs:element name="wasInformedBy" type="prov:WasInformedBy"/>
- <xs:element name="wasStartedByActivity" type="prov:WasStartedByActivity"/>
-
- <xs:element name="wasAttributedTo" type="prov:WasAttributedTo"/>
- <xs:element name="wasAssociatedWith" type="prov:WasAssociatedWith"/>
- <xs:element name="actedOnBehalfOf" type="prov:ActedOnBehalfOf"/>
-
- <xs:element name="wasDerivedFrom" type="prov:WasDerivedFrom"/>
- <xs:element name="wasRevisionOf" type="prov:WasRevisionOf"/>
- <xs:element name="wasQuotedFrom" type="prov:WasQuotedFrom"/>
- <xs:element name="hadOriginalSource" type="prov:HadOriginalSource"/>
- <xs:element name="tracedTo" type="prov:TracedTo"/>
-
- <xs:element name="alternateOf" type="prov:AlternateOf"/>
- <xs:element name="specializationOf" type="prov:SpecializationOf"/>
-
- <xs:element name="hasAnnotation" type="prov:HasAnnotation"/>
- </xs:choice>
- <xs:element ref="prov:extraDependency" minOccurs="0" maxOccurs="unbounded" />
-
- </xs:sequence>
- </xs:complexType>
-
- <xs:element name="extraDependency" abstract="true" />
- <xs:element name="extraRecord" abstract="true" />
-
- <!-- BUNDLES -->
-
- <xs:element name="account" type="prov:Account"/>
- <xs:complexType name="Account">
- <xs:sequence>
- <xs:element name="asserter" type="prov:AgentRef" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:records" minOccurs="1" maxOccurs="1"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <xs:element name="container" type="prov:Container">
- <xs:annotation>
- <xs:documentation>A set of assertions about the provenance of things</xs:documentation>
- </xs:annotation>
- </xs:element>
-
- <!-- a wrapper element for all records, used in Container or Account -->
- <xs:element name="records" type="prov:Records"/>
- <xs:complexType name="Records">
- <xs:sequence>
- <xs:element ref="prov:account" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:activity" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:entity" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:agent" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:note" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element name="dependencies" type="prov:Dependencies" minOccurs="0"/>
- <xs:element ref="prov:extraRecord" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <xs:complexType name="Container">
- <xs:sequence>
- <xs:element ref="prov:records" minOccurs="1" maxOccurs="1"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- <!-- tentative, this could allow us to annotate containers ... -->
- </xs:complexType>
-
-
-
-
-
-
-
-
-
-</xs:schema>
--- a/xml/experimental/extensions/provExample.xml Fri Apr 26 09:26:16 2013 +0100
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,29 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<prov:container prov:id="QName" xmlns:prov="http://www.w3.org/ns/prov#" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.w3.org/ns/prov# prov.xsd ">
- <prov:records>
- <prov:activity prov:id="QName">
- <prov:startTime>2001-12-31T12:00:00</prov:startTime>
- <prov:endTime>2001-12-31T12:00:00</prov:endTime>
- <prov:label>prov:label</prov:label>
- <prov:type>prov:type</prov:type>
- </prov:activity>
- <prov:entity prov:id="QName">
- <prov:label>prov:label</prov:label>
- <prov:type>prov:type</prov:type>
- </prov:entity>
- <prov:agent prov:id="QName">
- <prov:label>prov:label</prov:label>
- <prov:type>prov:type</prov:type>
- </prov:agent>
- <prov:note prov:id="QName"/>
- <prov:dependencies>
- <prov:used prov:id="QName">
- <prov:time>2001-12-31T12:00:00</prov:time>
- <prov:activity prov:ref="QName"/>
- <prov:entity prov:ref="QName"/>
- <prov:type>prov:type</prov:type>
- <prov:role>prov:role</prov:role>
- </prov:used>
- </prov:dependencies>
- </prov:records>
-</prov:container>
--- a/xml/extra.css Fri Apr 26 09:26:16 2013 +0100
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,370 +0,0 @@
-
-/* --- 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[id]::before {
- content: "Inference: " attr(id);
- width: 380px; /* How can we compute the length of "Constraint: " attr(id) */
-}
-
-
-.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;
-}
-
-.syntax {
- padding: 1em;
- margin: 1em 0em 0em;
- border: 1px solid #f00;
- background: #fff;
-}
-
-.syntax[id]::before {
- content: "Syntax: " attr(id);
- width: 380px; /* How can we compute the length of "Constraint: " attr(id) */
-}
-
-
-.syntax::before {
- content: "Syntax";
- 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;
-}
-
-
-
-.interpretation {
- padding: 1em;
- margin: 1em 0em 0em;
- border: 1px solid #00f;
- background: #fff;
-}
-
-.interpretation[id]::before {
- content: "Interpretation: " attr(id);
- width: 380px; /* How can we compute the length of "Interpretation: " attr(id) */
-}
-
-
-.interpretation::before {
- content: "Interpretation";
- display: block;
- width: 150px;
- margin: -1.5em 0 0.5em 0;
- font-weight: bold;
- border: 1px solid #00f;
- background: #fff;
- padding: 3px 1em;
-}
-
-
-.deprecatedconstraint {
- padding: 1em;
- margin: 1em 0em 0em;
- border: 1px solid #00f;
- background: #fff;
-}
-
-.deprecatedconstraint[id]::before {
- content: "Deprecated: " attr(id);
- width: 380px; /* How can we compute the length of "Deprecatedconstraint: " attr(id) */
-}
-
-
-.deprecatedconstraint::before {
- content: "Deprecated";
- display: block;
- width: 150px;
- margin: -1.5em 0 0.5em 0;
- font-weight: bold;
- border: 1px solid #00f;
- background: #fff;
- padding: 3px 1em;
-}
-
-.glossary-ref {
- font-style: italic;
-}
-
-.dfn {
- font-weight: bold;
-}
-
-
-.attribute {
- font-style: italic;
-}
-
-
-.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;
-}
-.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;
-}
-
-.anexample:before {
- content: "Example:";
- font-family: sans-serif;
- font-size: 1.6ex;
- font-weight: bold;
-}
-.anexample {
- margin-top: 1ex;
- margin-bottom: 1ex;
- padding-left: 1ex;
- padding-right: 1ex;
- padding-top: 1ex;
- padding-bottom: 0.6ex;
- border: 1px dashed #2f6fab;
- background-color: #f9f9f9;
-}
-.anexample table {
- background-color: #f9f9f9;
-}
-
-.pnExpression {
- font-weight: normal;
- font-size:120%;
- font-family: monospace;
-}
-
-
-div[class="grammar"] span[class="name"]:before {
- content: "'";
-}
-
-div[class="grammar"] span[class="name"]:after {
- content: "'";
-}
-
-
-div[class="grammar"] span[class="optional"]:before {
- font-weight: normal;
- font-size:130%;
- font-family: monospace;
- content: "(";
-}
-
-div[class="grammar"] span[class="optional"]:after {
- font-weight: normal;
- font-size:130%;
- font-family: monospace;
- content: ")?";
-}
-
-
-div[class="grammar"] span[class="plus"]:before {
- font-weight: normal;
- font-size:130%;
- font-family: monospace;
- content: "(";
-}
-
-div[class="grammar"] span[class="plus"]:after {
- font-weight: normal;
- font-size:130%;
- font-family: monospace;
- content: ")+";
-}
-
-
-div[class="grammar"] span[class="star"]:before {
- font-weight: normal;
- font-size:130%;
- font-family: monospace;
- content: "(";
-}
-
-div[class="grammar"] span[class="star"]:after {
- font-weight: normal;
- font-size:130%;
- font-family: monospace;
- content: ")*";
-}
-
-div[class="grammar"] span[class="group"]:before {
- font-weight: normal;
- font-size:130%;
- font-family: monospace;
- content: "(";
-}
-
-div[class="grammar"] span[class="group"]:after {
- font-weight: normal;
- font-size:130%;
- font-family: monospace;
- content: ")";
-}
-
-table {
- background-color: #f9f9f9;
-}
-
-.component1-color {
- background-color: rgba(255,42,42,0.2);
-}
-
-.component2-color {
- background-color: rgba(0,68,170,0.2);
-}
-
-.component3-color {
- background-color: rgba(0,170,0,0.2);
-}
-.component4-color {
- background-color: rgba(204,255,0,0.2);
-}
-
-.component5-color {
- background-color: rgba(11,40,40,0.2);
-}
-
-.component6-color {
- background-color: rgba(244,105,14,0.2);
-}
-
-.interpretation-forward::before {
- content: "Interpretation: ";
- font-weight: bold;
-}
-
-.structural-forward::before {
- content: "Structural constraint: ";
- font-weight: bold;
-}
--- a/xml/prov-xml.html Fri Apr 26 09:26:16 2013 +0100
+++ b/xml/prov-xml.html Fri Apr 26 09:27:12 2013 +0100
@@ -68,6 +68,8 @@
$(function() {
$("pre.schema-type").before("<p>ComplexType definition (denoting a similarly named prov-\"type\") in XML Schema:</p>");
+
+ $("span.glossary-ref").before("<p>From [[PROV-DM]]:</p>").wrap("<blockquote />").wrap("<i/>");
$("pre.schema-element").each(function(index) {
@@ -544,7 +546,7 @@
<area title="bundles" href="#component4" coords="268,0,402,201" alt="bundles" shape="rect"/>
</map>
<br>
-<figcaption id="prov-dm-components"><!-- Figure 1<sup><a class="internalDFN" href="#prov-dm-components"><span class="diamond"> â—Š:</span></a></sup>--> PROV-DM Components (Informative)</figcaption>
+<figcaption id="prov-dm-components">PROV-DM Components (Informative, from PROV-DM Fig. 4)</figcaption>
<figure>
</div>
--- a/xml/releases/NOTE-prov-xml-20130430/Overview.html Fri Apr 26 09:26:16 2013 +0100
+++ b/xml/releases/NOTE-prov-xml-20130430/Overview.html Fri Apr 26 09:27:12 2013 +0100
@@ -89,12 +89,6 @@
color: #ff4500;
}
-
-/* --- --- */
-ol.algorithm { counter-reset:numsection; list-style-type: none; }
-ol.algorithm li { margin: 0.5em 0; }
-ol.algorithm li:before { font-weight: bold; counter-increment: numsection; content: counters(numsection, ".") ") "; }
-
/* --- TOC --- */
.toc a, .tof a {
text-decoration: none;
@@ -197,7 +191,7 @@
color: #b9ab2d;
}
div.issue-title { color: #e05252; }
-div.note-title { color: #52e052; }
+div.note-title { color: #2b2; }
div.issue-title span, div.note-title span {
text-transform: uppercase;
}
@@ -212,7 +206,7 @@
border-left-style: solid;
}
div.issue, div.note {
- padding: 0.5em;
+ padding: 1em 1.2em 0.5em;
margin: 1em 0;
position: relative;
clear: both;
@@ -229,11 +223,11 @@
}
-</style><link rel="stylesheet" href="http://www.w3.org/StyleSheets/TR/W3C-WG-NOTE"><!--[if lt IE 9]><script src='http://www.w3.org/2008/site/js/html5shiv.js'></script><![endif]--></head>
+</style><link rel="stylesheet" href="//www.w3.org/StyleSheets/TR/W3C-WG-NOTE"><!--[if lt IE 9]><script src='https://www.w3.org/2008/site/js/html5shiv.js'></script><![endif]--></head>
<body><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>
+ <a href="http://www.w3.org/"><img width="72" height="48" src="https://www.w3.org/Icons/w3c_home" alt="W3C"></a>
</p>
<h1 class="title" id="title">PROV-XML: The PROV XML Schema</h1>
@@ -247,9 +241,6 @@
<dd><a href="http://www.w3.org/TR/prov-xml/">http://www.w3.org/TR/prov-xml/</a></dd>
- <dt>Latest editor's draft:</dt>
- <dd><a href="http://dvcs.w3.org/hg/prov/raw-file/default/xml/prov-xml.html">http://dvcs.w3.org/hg/prov/raw-file/default/xml/prov-xml.html</a></dd>
-
@@ -321,7 +312,7 @@
<li> <a href="http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/">PROV-XML</a> (Note), an XML schema for the PROV data model (this document);</li>
<li> <a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/">PROV-AQ</a> (Note), mechanisms for accessing and querying provenance [<cite><a class="bibref" href="#bib-PROV-AQ">PROV-AQ</a></cite>]; </li>
<li> <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/">PROV-DICTIONARY</a> (Note) introduces a specific type of collection, consisting of key-entity pairs [<cite><a class="bibref" href="#bib-PROV-DICTIONARY">PROV-DICTIONARY</a></cite>];</li>
-<li> <a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/">PROV-DC</a> (Note) provides a mapping between PROV-O and Dublic Core Terms [<cite><a class="bibref" href="#bib-PROV-DC">PROV-DC</a></cite>];</li>
+<li> <a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/">PROV-DC</a> (Note) provides a mapping between PROV-O and Dublin Core Terms [<cite><a class="bibref" href="#bib-PROV-DC">PROV-DC</a></cite>];</li>
<li> <a href="http://www.w3.org/TR/2013/NOTE-prov-sem-20130430/">PROV-SEM</a> (Note), a declarative specification in terms of first-order logic of the PROV data model [<cite><a class="bibref" href="#bib-PROV-SEM">PROV-SEM</a></cite>];</li>
<li> <a href="http://www.w3.org/TR/2013/NOTE-prov-links-20130430/">PROV-LINKS</a> (Note) introduces a mechanism to link across bundles [<cite><a class="bibref" href="#bib-PROV-LINKS">PROV-LINKS</a></cite>].</li>
</ul>
@@ -380,7 +371,7 @@
-</section><section id="toc"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a href="#introduction" class="tocxref"><span class="secno">1. </span>Introduction</a><ul class="toc"><li class="tocline"><a href="#prov-namespace" class="tocxref"><span class="secno">1.1 </span>PROV Namespace</a></li><li class="tocline"><a href="#conventions" class="tocxref"><span class="secno">1.2 </span>Conventions</a></li></ul></li><li class="tocline"><a href="#schema-design" class="tocxref"><span class="secno">2. </span>XML Schema Design</a><ul class="toc"><li class="tocline"><a href="#schema-modularization" class="tocxref"><span class="secno">2.1 </span>Schema Modularization</a></li><li class="tocline"><a href="#design-pattern" class="tocxref"><span class="secno">2.2 </span><i>Salami Slice</i> Design Pattern</a></li><li class="tocline"><a href="#elements-vs-attributes" class="tocxref"><span class="secno">2.3 </span>Elements vs. Attributes</a></li><li class="tocline"><a href="#type-conventions" class="tocxref"><span class="secno">2.4 </span>Type Conventions</a><ul class="toc"><li class="tocline"><a href="#type-conventions-attributes" class="tocxref"><span class="secno">2.4.1 </span>PROV Type Attribute</a></li><li class="tocline"><a href="#type-conventions-extension-types" class="tocxref"><span class="secno">2.4.2 </span>Extension Types</a></li><li class="tocline"><a href="#type-conventions-xsi-type" class="tocxref"><span class="secno">2.4.3 </span>XSI Type</a></li></ul></li><li class="tocline"><a href="#naming-conventions" class="tocxref"><span class="secno">2.5 </span>Naming Conventions</a></li></ul></li><li class="tocline"><a href="#schema-components" class="tocxref"><span class="secno">3. </span>PROV XML Schema</a><ul class="toc"><li class="tocline"><a href="#component1" class="tocxref"><span class="secno">3.1 </span>Component 1: Entities and Activities</a><ul class="toc"><li class="tocline"><a href="#term-Entity" class="tocxref"><span class="secno">3.1.1 </span>Entity</a></li><li class="tocline"><a href="#term-Activity" class="tocxref"><span class="secno">3.1.2 </span>Activity</a></li><li class="tocline"><a href="#term-Generation" class="tocxref"><span class="secno">3.1.3 </span>Generation</a></li><li class="tocline"><a href="#term-Usage" class="tocxref"><span class="secno">3.1.4 </span>Usage</a></li><li class="tocline"><a href="#term-Communication" class="tocxref"><span class="secno">3.1.5 </span>Communication</a></li><li class="tocline"><a href="#term-Start" class="tocxref"><span class="secno">3.1.6 </span>Start</a></li><li class="tocline"><a href="#term-End" class="tocxref"><span class="secno">3.1.7 </span>End</a></li><li class="tocline"><a href="#term-Invalidation" class="tocxref"><span class="secno">3.1.8 </span>Invalidation</a></li></ul></li><li class="tocline"><a href="#component2" class="tocxref"><span class="secno">3.2 </span>Component 2: Derivations</a><ul class="toc"><li class="tocline"><a href="#term-Derivation" class="tocxref"><span class="secno">3.2.1 </span>Derivation</a></li><li class="tocline"><a href="#term-Revision" class="tocxref"><span class="secno">3.2.2 </span>Revision</a></li><li class="tocline"><a href="#term-Quotation" class="tocxref"><span class="secno">3.2.3 </span>Quotation</a></li><li class="tocline"><a href="#term-PrimarySource" class="tocxref"><span class="secno">3.2.4 </span>Primary Source</a></li></ul></li><li class="tocline"><a href="#component3" class="tocxref"><span class="secno">3.3 </span>Component 3: Agents, Responsibility, and Influence</a><ul class="toc"><li class="tocline"><a href="#term-Agent" class="tocxref"><span class="secno">3.3.1 </span>Agent</a><ul class="toc"><li class="tocline"><a href="#term-Person" class="tocxref"><span class="secno">3.3.1.1 </span>Person</a></li><li class="tocline"><a href="#term-Organization" class="tocxref"><span class="secno">3.3.1.2 </span>Organization</a></li><li class="tocline"><a href="#term-SoftwareAgent" class="tocxref"><span class="secno">3.3.1.3 </span>Software Agent</a></li></ul></li><li class="tocline"><a href="#term-Attribution" class="tocxref"><span class="secno">3.3.2 </span>Attribution</a></li><li class="tocline"><a href="#term-Association" class="tocxref"><span class="secno">3.3.3 </span>Association</a><ul class="toc"><li class="tocline"><a href="#term-Plan" class="tocxref"><span class="secno">3.3.3.1 </span>Plan</a></li></ul></li><li class="tocline"><a href="#term-Delegation" class="tocxref"><span class="secno">3.3.4 </span>Delegation</a></li><li class="tocline"><a href="#term-Influence" class="tocxref"><span class="secno">3.3.5 </span>Influence</a></li></ul></li><li class="tocline"><a href="#component4" class="tocxref"><span class="secno">3.4 </span>Component 4: Bundles</a><ul class="toc"><li class="tocline"><a href="#term-Bundle" class="tocxref"><span class="secno">3.4.1 </span>Bundle</a></li><li class="tocline"><a href="#term-BundleConstructor" class="tocxref"><span class="secno">3.4.2 </span>Bundle Constructor</a></li></ul></li><li class="tocline"><a href="#component5" class="tocxref"><span class="secno">3.5 </span>Component 5: Alternate Entities</a><ul class="toc"><li class="tocline"><a href="#term-Specialization" class="tocxref"><span class="secno">3.5.1 </span>Specialization</a></li><li class="tocline"><a href="#term-Alternate" class="tocxref"><span class="secno">3.5.2 </span>Alternate</a></li></ul></li><li class="tocline"><a href="#component6" class="tocxref"><span class="secno">3.6 </span>Component 6: Collections</a><ul class="toc"><li class="tocline"><a href="#term-Collection" class="tocxref"><span class="secno">3.6.1 </span>Collection</a><ul class="toc"><li class="tocline"><a href="#term-EmptyCollection" class="tocxref"><span class="secno">3.6.1.1 </span>Empty Collection</a></li></ul></li><li class="tocline"><a href="#term-Membership" class="tocxref"><span class="secno">3.6.2 </span>Membership</a></li></ul></li><li class="tocline"><a href="#further-elements" class="tocxref"><span class="secno">3.7 </span>Further Elements of PROV</a><ul class="toc"><li class="tocline"><a href="#attribute-Identifier" class="tocxref"><span class="secno">3.7.1 </span>Identifier</a></li><li class="tocline"><a href="#attribute-Reference" class="tocxref"><span class="secno">3.7.2 </span>Reference</a></li><li class="tocline"><a href="#attributes" class="tocxref"><span class="secno">3.7.3 </span>Attributes</a><ul class="toc"><li class="tocline"><a href="#element-Label" class="tocxref"><span class="secno">3.7.3.1 </span>Label</a></li><li class="tocline"><a href="#element-Location" class="tocxref"><span class="secno">3.7.3.2 </span>Location</a></li><li class="tocline"><a href="#element-Role" class="tocxref"><span class="secno">3.7.3.3 </span>Role</a></li><li class="tocline"><a href="#element-Type" class="tocxref"><span class="secno">3.7.3.4 </span>Type</a></li><li class="tocline"><a href="#element-Value" class="tocxref"><span class="secno">3.7.3.5 </span>Value</a></li></ul></li><li class="tocline"><a href="#type-value" class="tocxref"><span class="secno">3.7.4 </span>Value</a></li></ul></li><li class="tocline"><a href="#structural-elements" class="tocxref"><span class="secno">3.8 </span>Structural Elements of PROV-XML</a><ul class="toc"><li class="tocline"><a href="#term-Document" class="tocxref"><span class="secno">3.8.1 </span>Document</a></li><li class="tocline"><a href="#term-Other" class="tocxref"><span class="secno">3.8.2 </span>Other</a></li></ul></li></ul></li><li class="tocline"><a href="#media-type" class="tocxref"><span class="secno">4. </span>Media Type</a></li><li class="tocline"><a href="#prov-xml-schema" class="tocxref"><span class="secno">A. </span>XML Schema</a><ul class="toc"><li class="tocline"><a href="#prov-schema" class="tocxref"><span class="secno">A.1 </span>prov.xsd</a></li><li class="tocline"><a href="#prov-core-schema" class="tocxref"><span class="secno">A.2 </span>prov-core.xsd</a></li><li class="tocline"><a href="#extension-schemas" class="tocxref"><span class="secno">A.3 </span>Extension Schemas</a></li></ul></li><li class="tocline"><a href="#changelog" class="tocxref"><span class="secno">B. </span>Change Log</a><ul class="toc"><li class="tocline"><a href="#change-log-since-wd-working-draft-12-march-2013" class="tocxref"><span class="secno">B.1 </span>Change Log Since WD Working Draft 12 March 2013</a></li><li class="tocline"><a href="#change-log-since-first-public-working-draft" class="tocxref"><span class="secno">B.2 </span>Change Log Since First Public Working Draft</a></li></ul></li><li class="tocline"><a href="#acknowledgements" class="tocxref"><span class="secno">C. </span>Acknowledgements</a></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">D. </span>References</a><ul class="toc"><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">D.1 </span>Informative references</a></li></ul></li></ul></section> <!-- end abstract -->
+</section><section id="toc"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a href="#introduction" class="tocxref"><span class="secno">1. </span>Introduction</a><ul class="toc"><li class="tocline"><a href="#prov-namespace" class="tocxref"><span class="secno">1.1 </span>PROV Namespace</a></li><li class="tocline"><a href="#conventions" class="tocxref"><span class="secno">1.2 </span>Conventions</a></li></ul></li><li class="tocline"><a href="#schema-design" class="tocxref"><span class="secno">2. </span>XML Schema Design</a><ul class="toc"><li class="tocline"><a href="#schema-modularization" class="tocxref"><span class="secno">2.1 </span>Schema Modularization</a></li><li class="tocline"><a href="#design-pattern" class="tocxref"><span class="secno">2.2 </span><i>Salami Slice</i> Design Pattern</a></li><li class="tocline"><a href="#elements-vs-attributes" class="tocxref"><span class="secno">2.3 </span>Elements vs. Attributes</a></li><li class="tocline"><a href="#type-conventions" class="tocxref"><span class="secno">2.4 </span>Type Conventions</a><ul class="toc"><li class="tocline"><a href="#type-conventions-attributes" class="tocxref"><span class="secno">2.4.1 </span>PROV Type Attribute</a></li><li class="tocline"><a href="#type-conventions-extension-types" class="tocxref"><span class="secno">2.4.2 </span>Extension Types</a></li><li class="tocline"><a href="#type-conventions-xsi-type" class="tocxref"><span class="secno">2.4.3 </span>XSI Type</a></li></ul></li><li class="tocline"><a href="#identifier-conventions" class="tocxref"><span class="secno">2.5 </span>Identifier Conventions</a></li><li class="tocline"><a href="#naming-conventions" class="tocxref"><span class="secno">2.6 </span>Naming Conventions</a></li></ul></li><li class="tocline"><a href="#schema-components" class="tocxref"><span class="secno">3. </span>PROV XML Schema</a><ul class="toc"><li class="tocline"><a href="#component1" class="tocxref"><span class="secno">3.1 </span>Component 1: Entities and Activities</a><ul class="toc"><li class="tocline"><a href="#term-Entity" class="tocxref"><span class="secno">3.1.1 </span>Entity</a></li><li class="tocline"><a href="#term-Activity" class="tocxref"><span class="secno">3.1.2 </span>Activity</a></li><li class="tocline"><a href="#term-Generation" class="tocxref"><span class="secno">3.1.3 </span>Generation</a></li><li class="tocline"><a href="#term-Usage" class="tocxref"><span class="secno">3.1.4 </span>Usage</a></li><li class="tocline"><a href="#term-Communication" class="tocxref"><span class="secno">3.1.5 </span>Communication</a></li><li class="tocline"><a href="#term-Start" class="tocxref"><span class="secno">3.1.6 </span>Start</a></li><li class="tocline"><a href="#term-End" class="tocxref"><span class="secno">3.1.7 </span>End</a></li><li class="tocline"><a href="#term-Invalidation" class="tocxref"><span class="secno">3.1.8 </span>Invalidation</a></li></ul></li><li class="tocline"><a href="#component2" class="tocxref"><span class="secno">3.2 </span>Component 2: Derivations</a><ul class="toc"><li class="tocline"><a href="#term-Derivation" class="tocxref"><span class="secno">3.2.1 </span>Derivation</a></li><li class="tocline"><a href="#term-Revision" class="tocxref"><span class="secno">3.2.2 </span>Revision</a></li><li class="tocline"><a href="#term-Quotation" class="tocxref"><span class="secno">3.2.3 </span>Quotation</a></li><li class="tocline"><a href="#term-PrimarySource" class="tocxref"><span class="secno">3.2.4 </span>Primary Source</a></li></ul></li><li class="tocline"><a href="#component3" class="tocxref"><span class="secno">3.3 </span>Component 3: Agents, Responsibility, and Influence</a><ul class="toc"><li class="tocline"><a href="#term-Agent" class="tocxref"><span class="secno">3.3.1 </span>Agent</a><ul class="toc"><li class="tocline"><a href="#term-Person" class="tocxref"><span class="secno">3.3.1.1 </span>Person</a></li><li class="tocline"><a href="#term-Organization" class="tocxref"><span class="secno">3.3.1.2 </span>Organization</a></li><li class="tocline"><a href="#term-SoftwareAgent" class="tocxref"><span class="secno">3.3.1.3 </span>Software Agent</a></li></ul></li><li class="tocline"><a href="#term-Attribution" class="tocxref"><span class="secno">3.3.2 </span>Attribution</a></li><li class="tocline"><a href="#term-Association" class="tocxref"><span class="secno">3.3.3 </span>Association</a><ul class="toc"><li class="tocline"><a href="#term-Plan" class="tocxref"><span class="secno">3.3.3.1 </span>Plan</a></li></ul></li><li class="tocline"><a href="#term-Delegation" class="tocxref"><span class="secno">3.3.4 </span>Delegation</a></li><li class="tocline"><a href="#term-Influence" class="tocxref"><span class="secno">3.3.5 </span>Influence</a></li></ul></li><li class="tocline"><a href="#component4" class="tocxref"><span class="secno">3.4 </span>Component 4: Bundles</a><ul class="toc"><li class="tocline"><a href="#term-Bundle" class="tocxref"><span class="secno">3.4.1 </span>Bundle</a></li><li class="tocline"><a href="#term-BundleConstructor" class="tocxref"><span class="secno">3.4.2 </span>Bundle Constructor</a></li></ul></li><li class="tocline"><a href="#component5" class="tocxref"><span class="secno">3.5 </span>Component 5: Alternate Entities</a><ul class="toc"><li class="tocline"><a href="#term-Specialization" class="tocxref"><span class="secno">3.5.1 </span>Specialization</a></li><li class="tocline"><a href="#term-Alternate" class="tocxref"><span class="secno">3.5.2 </span>Alternate</a></li></ul></li><li class="tocline"><a href="#component6" class="tocxref"><span class="secno">3.6 </span>Component 6: Collections</a><ul class="toc"><li class="tocline"><a href="#term-Collection" class="tocxref"><span class="secno">3.6.1 </span>Collection</a><ul class="toc"><li class="tocline"><a href="#term-EmptyCollection" class="tocxref"><span class="secno">3.6.1.1 </span>Empty Collection</a></li></ul></li><li class="tocline"><a href="#term-Membership" class="tocxref"><span class="secno">3.6.2 </span>Membership</a></li></ul></li><li class="tocline"><a href="#further-elements" class="tocxref"><span class="secno">3.7 </span>Further Elements of PROV</a><ul class="toc"><li class="tocline"><a href="#attribute-Identifier" class="tocxref"><span class="secno">3.7.1 </span>Identifier</a></li><li class="tocline"><a href="#attribute-Reference" class="tocxref"><span class="secno">3.7.2 </span>Reference</a></li><li class="tocline"><a href="#attributes" class="tocxref"><span class="secno">3.7.3 </span>Attributes</a><ul class="toc"><li class="tocline"><a href="#element-Label" class="tocxref"><span class="secno">3.7.3.1 </span>Label</a></li><li class="tocline"><a href="#element-Location" class="tocxref"><span class="secno">3.7.3.2 </span>Location</a></li><li class="tocline"><a href="#element-Role" class="tocxref"><span class="secno">3.7.3.3 </span>Role</a></li><li class="tocline"><a href="#element-Type" class="tocxref"><span class="secno">3.7.3.4 </span>Type</a></li><li class="tocline"><a href="#element-Value" class="tocxref"><span class="secno">3.7.3.5 </span>Value</a></li></ul></li><li class="tocline"><a href="#type-value" class="tocxref"><span class="secno">3.7.4 </span>Value</a></li></ul></li><li class="tocline"><a href="#structural-elements" class="tocxref"><span class="secno">3.8 </span>Structural Elements of PROV-XML</a><ul class="toc"><li class="tocline"><a href="#term-Document" class="tocxref"><span class="secno">3.8.1 </span>Document</a></li><li class="tocline"><a href="#term-Other" class="tocxref"><span class="secno">3.8.2 </span>Other</a></li></ul></li></ul></li><li class="tocline"><a href="#media-type" class="tocxref"><span class="secno">4. </span>Media Type</a></li><li class="tocline"><a href="#prov-xml-schema" class="tocxref"><span class="secno">A. </span>XML Schema</a><ul class="toc"><li class="tocline"><a href="#prov-schema" class="tocxref"><span class="secno">A.1 </span>Main Schema</a></li><li class="tocline"><a href="#prov-core-schema" class="tocxref"><span class="secno">A.2 </span>Core Schema</a></li><li class="tocline"><a href="#extension-schemas" class="tocxref"><span class="secno">A.3 </span>Extension Schemas</a></li></ul></li><li class="tocline"><a href="#changelog" class="tocxref"><span class="secno">B. </span>Change Log</a><ul class="toc"><li class="tocline"><a href="#change-log-since-wd-working-draft-12-march-2013" class="tocxref"><span class="secno">B.1 </span>Change Log Since WD Working Draft 12 March 2013</a></li><li class="tocline"><a href="#change-log-since-first-public-working-draft" class="tocxref"><span class="secno">B.2 </span>Change Log Since First Public Working Draft</a></li></ul></li><li class="tocline"><a href="#acknowledgements" class="tocxref"><span class="secno">C. </span>Acknowledgements</a></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">D. </span>References</a><ul class="toc"><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">D.1 </span>Informative references</a></li></ul></li></ul></section> <!-- end abstract -->
<!-- end sotd -->
@@ -411,13 +402,14 @@
</li></ul>
<p>
-This specification goal is to provide a succinct definition of the XML form of PROV-DM, thus, we refer the reader to the PROV-DM to provide overall justification and context to the definitions presented here.
+<i>This specification's goal is to provide a succinct definition of the XML form of PROV-DM</i>, thus, we refer the reader to the PROV-DM to provide overall justification and context to the definitions presented here.
</p>
<section id="prov-namespace">
<h3><span class="secno">1.1 </span>PROV Namespace</h3>
<p>The PROV namespace is <span class="name">http://www.w3.org/ns/prov#</span>.</p>
-<p> All the concepts, reserved names and attributes introduced in this specification belong to the PROV namespace.</p>
+<p>All the concepts, reserved names and attributes introduced in this specification belong to the PROV namespace.</p>
+<p>The prefix <b>prov</b> is used when referring to the PROV namespace.</p>
</section> <!-- end prov-namespace -->
<section id="conventions">
@@ -439,42 +431,42 @@
<section id="schema-modularization">
<h3><span class="secno">2.1 </span>Schema Modularization</h3>
-<p>The PROV-XML schema have been modularized so that extension elements defined in Working Group Notes can be defined in separate schemas. Elements corresponding to terms defined in the PROV-DM are defined in the <b>prov-core.xsd</b> schema and elements corresponding to terms defined in notes are defined in extension schemas (e.g. <b>prov-dictionary.xsd</b>, <b>prov-links.xsd</b>). The default schema, <b>prov.xsd</b>, imports <b>prov-core.xsd</b> and all extension schemas developed by the Working Group. With this modeling all PROV elements, even those defined in Notes, are defined from the default schema. If the user wishes to leverage a schema that does not include extension elements the user can use schemaLocation to directly reference <b>prov-core.xsd</b>.</p>
-<p>The default schema - <b>prov.xsd</b></p>
+<p>The PROV-XML schema have been modularized so that xml-elements denoting terms defined in Working Group Notes are defined in separate extension schemas. All xml-elements denoting terms defined in the PROV-DM are defined in the <b><a href="http://www.w3.org/ns/prov-core.xsd">http://www.w3.org/ns/prov-core.xsd</a></b> schema and xml-elements denoting terms defined in PROV Working Group Notes are defined in extension schemas (e.g. <b><a href="http://www.w3.org/ns/prov-dictionary.xsd">http://www.w3.org/ns/prov-dictionary.xsd</a></b>, <b><a href="http://www.w3.org/ns/prov-links.xsd">http://www.w3.org/ns/prov-links.xsd</a></b>). The default schema, <b><a href="http://www.w3.org/ns/prov.xsd">http://www.w3.org/ns/prov.xsd</a></b>, imports <b><a href="http://www.w3.org/ns/prov-core.xsd">http://www.w3.org/ns/prov-core.xsd</a></b> and all extension schemas. With this modeling all PROV xml-elements, even those denoting terms defined in Notes, are declared from the default schema. If the user wishes to leverage a schema that does not include xml-elements corresponding to terms from the PROV Notes the user can use schemaLocation to directly reference the core schema.</p>
+<p>The default schema - <b><a href="http://www.w3.org/ns/prov.xsd">http://www.w3.org/ns/prov.xsd</a></b></p>
<pre><?xml version="1.0" encoding="utf-8"?>
<xs:schema targetNamespace="http://www.w3.org/ns/prov#"
- xmlns:xs="http://www.w3.org/2001/XMLSchema"
- xmlns:prov="http://www.w3.org/ns/prov#"
- elementFormDefault="qualified"
- attributeFormDefault="unqualified">
-
- <xs:include schemaLocation="prov-core.xsd"/>
- <xs:include schemaLocation="prov-dictionary.xsd"/>
- <xs:include schemaLocation="prov-links.xsd"/>
+ xmlns:xs="http://www.w3.org/2001/XMLSchema"
+ xmlns:prov="http://www.w3.org/ns/prov#"
+ elementFormDefault="qualified"
+ attributeFormDefault="unqualified">
+
+ <xs:include schemaLocation="prov-core.xsd"/>
+ <xs:include schemaLocation="prov-dictionary.xsd"/>
+ <xs:include schemaLocation="prov-links.xsd"/>
</xs:schema>
</pre>
-<p>Extension schemas import the <b>prov-core.xsd</b> schema and make use of a substitution group on the <code>prov:internalElement</code> to add extension-defined elements to the list of valid PROV elements in a bundle or document.</p>
-<div class="note"><div class="note-title"><span>Note</span></div><div class="">
-<p>This schema design leveraging substitutionGroups on an abstract element may result in sub-optimal binding classes being generated by OXM frameworks such as JAXB, JiBX, etc. See the PROV FAQ entry at <a href="http://www.w3.org/2001/sw/wiki/PROV-FAQ#How_should_I_generate_JAXB_classes_from_the_PROV-XML_schemas.3F">How should I generate JAXB classes from the PROV-XML schemas?</a> for a JAXB-specific discussion on using OXM technologies with the PROV schemas.</p>
+<p>Extension schemas import the <b><a href="http://www.w3.org/ns/prov-core.xsd">http://www.w3.org/ns/prov-core.xsd</a></b> schema and make use of a substitution group on the <code>prov:internalElement</code> to add extension-defined xml-elements to the list of valid PROV xml-elements in a bundle or document.</p>
+<div class="note"><div class="note-title" role="heading" aria-level="4"><span>Note</span></div><div class="">
+<p>This schema design leveraging substitutionGroups on an abstract xml-element may result in sub-optimal binding classes being generated by Object-to-XML frameworks such as JAXB, JiBX, etc. See the PROV FAQ entry at <a href="http://www.w3.org/2001/sw/wiki/PROV-FAQ#How_should_I_generate_JAXB_classes_from_the_PROV-XML_schemas.3F">How should I generate JAXB classes from the PROV-XML schemas?</a> for a JAXB-specific discussion on using OXM technologies with the PROV schemas.</p>
</div></div> <!-- end note -->
-<p>The <b>prov-links.xsd</b> extension schema.</p>
+<p>The <b><a href="http://www.w3.org/ns/prov-links.xsd">http://www.w3.org/ns/prov-links.xsd</a></b> extension schema.</p>
<pre><?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
- targetNamespace="http://www.w3.org/ns/prov#" xmlns:prov="http://www.w3.org/ns/prov#"
- elementFormDefault="qualified">
-
- <xs:include schemaLocation="prov-core.xsd" />
+ targetNamespace="http://www.w3.org/ns/prov#" xmlns:prov="http://www.w3.org/ns/prov#"
+ elementFormDefault="qualified">
- <xs:complexType name="Mention">
- <xs:sequence>
- <xs:element name="specificEntity" type="prov:IDRef" />
- <xs:element name="generalEntity" type="prov:IDRef" />
- <xs:element name="bundle" type="prov:IDRef" />
- </xs:sequence>
- </xs:complexType>
+ <xs:include schemaLocation="prov-core.xsd" />
- <xs:element name="mentionOf" type="prov:Mention" substitutionGroup="prov:internalElement" />
+ <xs:complexType name="Mention">
+ <xs:sequence>
+ <xs:element name="specificEntity" type="prov:IDRef" />
+ <xs:element name="generalEntity" type="prov:IDRef" />
+ <xs:element name="bundle" type="prov:IDRef" />
+ </xs:sequence>
+ </xs:complexType>
+
+ <xs:element name="mentionOf" type="prov:Mention" substitutionGroup="prov:internalElement" />
</xs:schema>
</pre>
@@ -484,13 +476,15 @@
<section id="design-pattern">
<h3><span class="secno">2.2 </span><i>Salami Slice</i> Design Pattern</h3>
-<p>The general design pattern for the XML schema has been called <i>Salami Slice Design</i>. With this design, the individual components are each defined at the top level as separate elements with distinct types. This allows the types to be easily reusable for domain specific extensions.</p>
-<p>The <code>prov:document</code> element has been defined to act as a convenient root element for a PROV-XML document, but it's use as the root element is not required. The schema follows the Salami Slice pattern to ensure PROV XML elements can be integrated with mixed-schema XML documents which require a different document root.</p>
+<p>The general design pattern for the XML schema has been called <i>Salami Slice Design</i>. With this design, the individual components are each defined at the top level as separate xml-elements with distinct xml-types. This allows the xml-types to be easily reusable for domain specific extensions.</p>
+<p>The <code>prov:document</code> xml-element has been defined to act as a convenient root xml-element for a PROV-XML document, but it's use as the root xml-element is not required. The schema follows the Salami Slice pattern to ensure PROV XML xml-elements can be integrated with mixed-schema XML documents which require a different document root.</p>
</section> <!-- end design-pattern -->
<section id="elements-vs-attributes">
<h3><span class="secno">2.3 </span>Elements vs. Attributes</h3>
+<p>The PROV Notation (PROV-N) is a serialization of the PROV Data Model described in [<cite><a class="bibref" href="#bib-PROV-N">PROV-N</a></cite>]. Examples in the [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>] document are encoded using PROV-N. Because of the heavy use of PROV-N syntax in [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>], the PROV-XML editors feel it is important to present a comparison of the PROV-N and PROV-XML syntaxes and justifications behind the select syntax decisions in PROV-XML.</p>
+
<p>The general PROV-N syntax patterns for expressing provenance
concepts are:
</p>
@@ -499,7 +493,7 @@
concept(id; elem1, elem2, ... [attr1=val2, attr2=val2])
</pre>
-<p>In both cases (required id or optional id), the PROV-N id is treated as an XML attribute (<code>prov:id</code>), the PROV-N "elements" are treated as XML elements, always with the same required order (position) as the PROV-DM/PROV-N description, and optional PROV-N "attributes", if allowed, always follow and are also represented by XML elements. As in PROV-N, the attributes can be specified multiple times, but unlike PROV-N the attributes have a fixed (alphabetical) order. The PROV-N "attribute" elements are always defined at the end of the encompassing sequence after all PROV-N "elements". Elements defined in namespaces other than the PROV namespace may be included in a element after all PROV elements.</p>
+<p>In PROV-XML the PROV identifier is treated as an xml-attribute (<code>prov:id</code>), the prov-"elements" are treated as xml-elements, always with the same required order (position) as the PROV-DM/PROV-N description followed by optional prov-"attributes" which are also represented by xml-elements. As in PROV-N, the prov-"attributes" can be specified multiple times, but unlike PROV-N the prov-"attributes" have a fixed (alphabetical) order. The prov-"attribute" xml-elements are always defined at the end of the encompassing sequence after all prov-"element" xml-elements. XML Elements defined in namespaces other than the PROV namespace may be included after the prov-"attribute" xml-elements.</p>
<p>Wherever an "id" is referenced from a later concept, the id is
referenced as a prov:ref attribute of the element within the concept.
@@ -524,8 +518,8 @@
<h3><span class="secno">2.4 </span>Type Conventions</h3>
<section id="type-conventions-attributes">
<h4><span class="secno">2.4.1 </span>PROV Type Attribute</h4>
-<p>The PROV-DM states type information is described using the prov:type PROV attribute and may occur multiple times for a given entity, activity, agent, or relation.</p>
-<p>PROV-XML uses the element <code>prov:type</code> to represent the prov:type PROV attribute. This element can be use to represent both PROV and non-PROV type information. The following examples shows type information encoded using the <code>prov:type</code> element.</p>
+<p>The PROV-DM states type information is described using the prov:type prov-"attribute" and may occur multiple times for a given entity, activity, agent, or relation.</p>
+<p>PROV-XML uses the xml-element <code>prov:type</code> to represent the prov:type prov-"attribute". This xml-element can be use to represent both PROV and non-PROV type information. The following examples shows type information encoded using the <code>prov:type</code> xml-element.</p>
<div class="example"><div class="example-title"><span>Example 1</span>: type information using prov:type PROV attribute</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
@@ -539,11 +533,11 @@
</prov:entity>
</prov:document></pre></div>
-<p>The <code>prov:type</code> element can be used in conjunction with schema-defined PROV types (see examples 2-5).</p>
+<p>The <code>prov:type</code> xml-element can be used in conjunction with schema-defined PROV types (see examples 2-5).</p>
</section> <!-- end type-conventions-attributes -->
<section id="type-conventions-extension-types">
<h4><span class="secno">2.4.2 </span>Extension Types</h4>
-<p>PROV-XML defines complexTypes to match the PROV defined type values. These types provide a more native XML representation of PROV types. The following example is considered equivalent to the previous example because the element <code>prov:plan</code> has type <code>prov:Plan</code>. All complexTypes representing a PROV type which is defined as a subclass of another PROV type are defined in PROV-XML as extensions of their parent PROV type's complexType. For example, <code>prov:Plan</code> is defined as an extension of the complexType <code>prov:Entity</code> and may be referenced by either <code>prov:plan</code> or <code>prov:entity</code>.</p>
+<p>PROV-XML defines complexTypes to match the PROV defined type values (prov-type). These xml-types provide a more native XML representation of prov-"types". The following example is considered equivalent to the previous example because the xml-element <code>prov:plan</code> has <code>xs:type=prov:Plan</code>. All complexTypes representing a prov-"type" which is defined as a subclass of another prov-"type" are defined in PROV-XML as extensions of their parent prov-"type's" complexType. For example, <code>prov:Plan</code> is defined as an extension of the complexType <code>prov:Entity</code> and may be referenced by either <code>prov:plan</code> or <code>prov:entity</code> xml-elements.</p>
<div class="example"><div class="example-title"><span>Example 2</span>: type information using schema defined types</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
@@ -556,8 +550,8 @@
</prov:plan>
</prov:document></pre></div>
-<p>When an extended type is used a PROV type attribute relation may be inferred for the current and any parent type of the declared type.</p>
-<p>Stating all type information using the PROV type attribute assists in interoperability with non-PROV-XML encoding of PROV.</p>
+<p>When an extension xml-type is used a prov-"type" may be inferred.</p>
+<p>Explicit type declarations made using the <code>prov:type</code> xml-element may be easier for some encoding transformation tools (such as XSLT) to process, therefore use of the <code>prov:type</code> xml-element is highly encouraged even in cases where prov-"type" information is determinable from schema defined ComplexTypes.</p>
<div class="example"><div class="example-title"><span>Example 3</span>: type information using schema defined types - type inferences</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
@@ -575,7 +569,7 @@
</section><!-- end-type-conventions-extension-types -->
<section id="type-conventions-xsi-type">
<h4><span class="secno">2.4.3 </span>XSI Type</h4>
-<p>Because the <code>prov:Plan</code> complexType is defined as an extension of the complexType <code>prov:Entity</code>, the following example using <code>xsi:type</code> is valid and considered equivalent to the two previous examples. The attribute <code>xsi:type</code> tells an XML parser the complexType of the element. The value of <code>xsi:type</code> must be a complexType derived from the default element type in a schema with known location (referenced through <code>xsi:schemaLocation</code>).</p>
+<p>Because the <code>prov:Plan</code> complexType is defined as an extension of the complexType <code>prov:Entity</code>, the following example using <code>xsi:type</code> is valid and considered equivalent to the two previous examples. The xml-attribute <code>xsi:type</code> tells an XML parser the complexType of the xml-element. The value of <code>xsi:type</code> must be a complexType derived from the default xml-element xml-type in a schema with known location (referenced through <code>xsi:schemaLocation</code>).</p>
<div class="example"><div class="example-title"><span>Example 4</span>: type information using xsi:type</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
@@ -588,7 +582,7 @@
</prov:entity>
</prov:document></pre></div>
-<p>A PROV type attribute relation may be inferred by the use of the <code>xsi:type</code> XML attribute.</p>
+<p>A prov-"type" xml-element may be inferred by the use of the <code>xsi:type</code> xml-attribute.</p>
<div class="example"><div class="example-title"><span>Example 5</span>: type information using xsi:type - type inferences</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
@@ -604,13 +598,28 @@
</prov:document></pre></div>
</section> <!-- end type-conventions-xsi-type -->
+</section> <!-- end type-conventions -->
+
+<section id="identifier-conventions">
+<h3><span class="secno">2.5 </span>Identifier Conventions</h3>
+<p>[<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>] defines a PROV Identifier as a qualified name with the following definition:</p>
+<p>From [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>]:</p><blockquote><i><span class="glossary-ref"> A <span class="dfn">qualified name</span> is a name subject to namespace interpretation. It consists of a namespace, denoted by an optional prefix, and a local name. </span></i></blockquote>
+<p>[<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>] also mandates that all qualified names be mappable to a URI by concatenating the namespace URI with a local name.</p>
+
+<p>PROV-XML uses the <code>prov:id</code> xml-attribute to denote a PROV Identifier and the <code>prov:ref</code> xml-attribute to denote a reference-by-id to an instance of a prov-"type" or prov-"relation" which has a matching PROV Identifier. The value of <code>prov:ref</code> must be a valid PROV Identifier, but there is no requirement that for every <code>prov:ref</code> a corresponding <code>prov:id</code> must be known to exist.</p>
+
+<p>PROV-XML defines the type of both the <code>prov:id</code> and <code>prov:ref</code> xml-attributes to be <code>xsd:QName</code> as that is the XSD datatype that most closely matches the qualified name definition by [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>]. Care should be taken when generating PROV identifier values in PROV-XML such that there is a known mapping to a URI.</p>
+
+<div class="note"><div class="note-title" role="heading" aria-level="4"><span>Note</span></div><div class="">
+<p>The xsd:QName datatype is more restrictive than the QualifiedName defined in [<cite><a class="bibref" href="#bib-PROV-N">PROV-N</a></cite>] (e.g. PROV-N allows local names to start with numbers), therefore valid identifier values in [<cite><a class="bibref" href="#bib-PROV-N">PROV-N</a></cite>] serializations have to potential to not be valid identifier values in PROV-XML. It is recommended to enhance interoperability that provenance users strive to always use identifier schemes that map to valid xsd:QNames and URIs.</p>
+</div></div>
</section>
<section id="naming-conventions">
-<h3><span class="secno">2.5 </span>Naming Conventions</h3>
-<p>Element names are aligned with [<cite><a class="bibref" href="#bib-PROV-N">PROV-N</a></cite>] record names (e.g. <code>prov:wasGeneratedBy</code>, <code>prov:actedOnBehalfOf</code>) and record parameter roles (e.g. <code>prov:delegate</code>, <code>prov:responsible</code> on a Delegation). Elements are named in camelCase which also conforms with [<cite><a class="bibref" href="#bib-PROV-N">PROV-N</a></cite>] naming conventions.</p>
-<p>ComplexType names are aligned with [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>] type names (e.g. <code>prov:Generation</code>, <code>prov:Delegation</code>). ComplexTypes are named in PascalCase which conforms to [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>] naming conventions and differentiates complexTypes from elements in the schema.</p>
+<h3><span class="secno">2.6 </span>Naming Conventions</h3>
+<p>XML element names are aligned with [<cite><a class="bibref" href="#bib-PROV-N">PROV-N</a></cite>] record names (e.g. <code>prov:wasGeneratedBy</code>, <code>prov:actedOnBehalfOf</code>) and record parameter roles (e.g. <code>prov:delegate</code>, <code>prov:responsible</code> on a Delegation). XML Elements are named in camelCase which also conforms with [<cite><a class="bibref" href="#bib-PROV-N">PROV-N</a></cite>] naming conventions.</p>
+<p>ComplexType names are aligned with [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>] prov-"type" names (e.g. <code>prov:Generation</code>, <code>prov:Delegation</code>). ComplexTypes are named in PascalCase which conforms to [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>] naming conventions and differentiates complexTypes from xml-elements in the schema.</p>
</section> <!-- end naming-conventions -->
</section> <!-- end schema-design -->
@@ -618,7 +627,7 @@
<section id="schema-components">
<!--OddPage--><h2><span class="secno">3. </span>PROV XML Schema</h2>
-<p>Provenance concepts, expressed as PROV-DM types and relations, are organized according to six components that are defined in this section.</p>
+<p>Provenance concepts, expressed as prov-"types" and prov-"relations", are organized according to six components that are defined in this section.</p>
<div id="prov-dm-components-ul">
<ul>
@@ -646,181 +655,181 @@
<area title="bundles" href="#component4" coords="268,0,402,201" alt="bundles" shape="rect">
</map>
<br>
-<span class="figcaption" id="prov-dm-components">Figure 1<sup><a class="internalDFN" href="#prov-dm-components"><span class="diamond"> â—Š:</span></a></sup> <!-- Figure 1<sup><a class="internalDFN" href="#prov-dm-components"><span class="diamond"> â—Š:</span></a></sup>--> PROV-DM Components (Informative)</span>
+<span class="figcaption" id="prov-dm-components">Figure 1<sup><a class="internalDFN" href="#prov-dm-components"><span class="diamond"> â—Š:</span></a></sup> PROV-DM Components (Informative, from PROV-DM Fig. 4)</span>
<span class="figure" id="fig-generatedID">
</span></span></div>
-<p><a href="#prov-schema-mapping">Table 1</a> is a mapping of PROV-DM types and relations in PROV-XML schema XML types and elements.</p>
+<p><a href="#prov-schema-mapping">Table 1</a> is a mapping of PROV-DM prov-"types" and prov-"relations" in PROV-XML schema XML complexTypes and xml-elements.</p>
<div id="prov-schema-mapping-div" style="text-align: center;">
<table class="thinborder" style="margin-left: auto; margin-right: auto;">
-<caption id="prov-schema-mapping"><span>Table 1<sup><a class="internalDFN" href="#prov-schema-mapping"><span class="diamond"> â—Š:</span></a></sup> </span><!--<span>Table 1<sup><a class="internalDFN" href="#prov-schema-mapping"><span class="diamond"> â—Š:</span></a></sup> </span>-->PROV-DM Types and Relations to XML Schema Mapping</caption>
+<caption id="prov-schema-mapping"><span>Table 1<sup><a class="internalDFN" href="#prov-schema-mapping"><span class="diamond"> â—Š:</span></a></sup> </span>PROV-DM Types and Relations to XML Schema Mapping</caption>
<tbody><tr>
-<td><a><b>Type or Relation Name</b></a></td>
+<td><a><b>PROV-DM Term / Concept</b></a></td>
<td><b>XML Schema ComplexType</b></td>
-<td><b>XML Schema Referencing Element</b></td>
+<td><b>XML Schema XML Element</b></td>
<td><b>Component</b></td></tr>
<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
<tr class="component1-color">
- <td><a href="#term-Entity">Entity</a></td>
- <td>prov:Entity</td>
+ <td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-entity">Entity</a></td>
+ <td><a href="#term-Entity">prov:Entity</a></td>
<td>prov:entity</td>
<td rowspan="8"><a href="#component1">Component 1: Entities/Activities</a></td>
</tr>
<tr class="component1-color">
- <td><a href="#term-Activity">Activity</a></td>
- <td>prov:Activity</td>
+ <td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-Activity">Activity</a></td>
+ <td><a href="#term-Activity">prov:Activity</a></td>
<td>prov:activity</td>
</tr>
<tr class="component1-color">
- <td><a href="#term-Generation">Generation</a></td>
- <td>prov:Generation</td>
+ <td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-Generation">Generation</a></td>
+ <td><a href="#term-Generation">prov:Generation</a></td>
<td>prov:wasGeneratedBy</td>
</tr>
<tr class="component1-color">
- <td><a href="#term-Usage">Usage</a></td>
- <td>prov:Usage</td>
+ <td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-Usage">Usage</a></td>
+ <td><a href="#term-Usage">prov:Usage</a></td>
<td>prov:used</td>
</tr>
<tr class="component1-color">
- <td><a href="#term-Communication">Communication</a></td>
- <td>prov:Communication</td>
+ <td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-Communication">Communication</a></td>
+ <td><a href="#term-Communication">prov:Communication</a></td>
<td>prov:wasInformedBy</td>
</tr>
<tr class="component1-color">
- <td><a href="#term-Start">Start</a></td>
- <td>prov:Start</td>
+ <td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-Start">Start</a></td>
+ <td><a href="#term-Start">prov:Start</a></td>
<td>prov:wasStartedBy</td>
</tr>
<tr class="component1-color">
- <td><a href="#term-End">End</a></td>
- <td>prov:End</td>
+ <td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-End">End</a></td>
+ <td><a href="#term-End">prov:End</a></td>
<td>prov:wasEndedBy</td>
</tr>
<tr class="component1-color">
- <td><a href="#term-Invalidation">Invalidation</a></td>
- <td>prov:Invalidation</td>
+ <td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-Invalidation">Invalidation</a></td>
+ <td><a href="#term-Invalidation">prov:Invalidation</a></td>
<td>prov:wasInvalidatedBy</td>
</tr>
<tr>
<td colspan="3" style="border-width: 0px; "></td>
</tr>
<tr class="component2-color">
- <td><a href="#term-Derivation">Derivation</a></td>
- <td>prov:Derivation</td>
+ <td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-Derivation">Derivation</a></td>
+ <td><a href="#term-Derivation">prov:Derivation</a></td>
<td>prov:wasDerivedFrom</td>
<td rowspan="4"><a href="#component2">Component 2: Derivations</a></td>
</tr>
<tr class="component2-color">
- <td><a href="#term-Revision">Revision</a></td>
- <td>prov:Revision</td>
+ <td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-revision">Revision</a></td>
+ <td><a href="#term-Revision">prov:Revision</a></td>
<td>prov:wasRevisionOf</td>
</tr>
<tr class="component2-color">
- <td><a href="#term-Quotation">Quotation</a></td>
- <td>prov:Quotation</td>
+ <td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-quotation">Quotation</a></td>
+ <td><a href="#term-Quotation">prov:Quotation</a></td>
<td>prov:wasQuotedFrom</td>
</tr>
<tr class="component2-color">
- <td><a href="#term-PrimarySource">Primary Source</a></td>
- <td>prov:PrimarySource</td>
+ <td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-primary-source">Primary Source</a></td>
+ <td><a href="#term-PrimarySource">prov:PrimarySource</a></td>
<td>prov:hadPrimarySource</td>
</tr>
<tr>
<td colspan="3" style="border-width: 0px; "></td>
</tr>
<tr class="component3-color" style="border-collapse: collapse; ">
- <td><a href="#term-Agent">Agent</a></td>
- <td>prov:Agent</td>
+ <td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-agent">Agent</a></td>
+ <td><a href="#term-Agent">prov:Agent</a></td>
<td>prov:agent</td>
<td rowspan="9"><a href="#component3">Component 3: Agents, Responsibility, Influence</a></td>
</tr>
<tr class="component3-color">
- <td><a href="#term-Attribution">Attribution</a></td>
- <td>prov:Attribution</td>
+ <td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-attribution">Attribution</a></td>
+ <td><a href="#term-Attribution">prov:Attribution</a></td>
<td>prov:wasAttributedTo</td>
</tr>
<tr class="component3-color">
- <td><a href="#term-Association">Association</a></td>
- <td>prov:Association</td>
+ <td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-Association">Association</a></td>
+ <td><a href="#term-Association">prov:Association</a></td>
<td>prov:wasAssociatedWith</td>
</tr>
<tr class="component3-color">
- <td><a href="#term-Delegation">Delegation</a></td>
- <td>prov:Delegation</td>
+ <td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-delegation">Delegation</a></td>
+ <td><a href="#term-Delegation">prov:Delegation</a></td>
<td>prov:actedOnBehalfOf</td>
</tr>
<tr class="component3-color">
- <td><a href="#term-Plan">Plan</a></td>
- <td>prov:Plan</td>
+ <td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#concept-plan">Plan</a></td>
+ <td><a href="#term-Plan">prov:Plan</a></td>
<td>prov:plan</td>
</tr>
<tr class="component3-color">
- <td><a href="#term-Person">Person</a></td>
- <td>prov:Person</td>
+ <td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#concept-person">Person</a></td>
+ <td><a href="#term-Person">prov:Person</a></td>
<td>prov:person</td>
</tr>
<tr class="component3-color">
- <td><a href="#term-Organization">Organization</a></td>
- <td>prov:Organization</td>
+ <td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#concept-organization">Organization</a></td>
+ <td><a href="#term-Organization">prov:Organization</a></td>
<td>prov:organization</td>
</tr>
<tr class="component3-color">
- <td><a href="#term-SoftwareAgent">Software Agent</a></td>
- <td>prov:SoftwareAgent</td>
+ <td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#concept-software-agent">Software Agent</a></td>
+ <td><a href="#term-SoftwareAgent">prov:SoftwareAgent</a></td>
<td>prov:softwareAgent</td>
</tr>
<tr class="component3-color">
- <td><a href="#term-Influence">Influence</a></td>
- <td>prov:Influence</td>
+ <td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-influence">Influence</a></td>
+ <td><a href="#term-Influence">prov:Influence</a></td>
<td>prov:wasInfluencedBy</td>
</tr>
<tr>
<td colspan="3" style="border-width: 0px; "></td>
</tr>
<tr class="component4-color">
- <td><a href="#term-Bundle">Bundle</a></td>
- <td>prov:Bundle</td>
+ <td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-bundle-entity">Bundle</a></td>
+ <td><a href="#term-Bundle">prov:Bundle</a></td>
<td>prov:bundle</td>
<td rowspan="2"><a href="#component4">Component 4: Bundles</a></td>
</tr>
<tr class="component4-color">
- <td><a href="#term-BundleConstructor">Bundle Constructor</a></td>
- <td>prov:BundleConstructor</td>
+ <td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-bundle">Bundle Constructor</a></td>
+ <td><a href="#term-BundleConstructor">prov:BundleConstructor</a></td>
<td>prov:bundleContent</td>
</tr>
<tr>
<td colspan="3" style="border-width: 0px; "></td>
</tr>
<tr class="component5-color">
- <td><a href="#term-Alternate">Alternate</a></td>
- <td>prov:Alternate</td>
+ <td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-alternate">Alternate</a></td>
+ <td><a href="#term-Alternate">prov:Alternate</a></td>
<td>prov:alternateOf</td>
<td rowspan="3"><a href="#component5">Component 5: Alternate</a></td>
</tr>
<tr class="component5-color">
- <td><a href="#term-Specialization">Specialization</a></td>
- <td>prov:Specialization</td>
+ <td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-specialization">Specialization</a></td>
+ <td><a href="#term-Specialization">prov:Specialization</a></td>
<td>prov:specializationOf</td>
</tr>
<tr>
<td colspan="3" style="border-width: 0px; "></td>
</tr>
<tr class="component6-color">
- <td><a href="#term-Collection">Collection</a></td>
- <td>prov:Collection</td>
+ <td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-collection">Collection</a></td>
+ <td><a href="#term-Collection">prov:Collection</a></td>
<td>prov:collection</td>
<td rowspan="3"><a href="#component6">Component 6: Collections</a></td>
</tr>
<tr class="component6-color">
- <td><a href="#term-EmptyCollection">Empty Collection</a></td>
- <td>prov:EmptyCollection</td>
+ <td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#concept-empty-collection">Empty Collection</a></td>
+ <td><a href="#term-EmptyCollection">prov:EmptyCollection</a></td>
<td>prov:emptyCollection</td>
</tr>
<tr class="component6-color">
- <td><a href="#term-Membership">Membership</a></td>
- <td>prov:Membership</td>
+ <td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-membership">Membership</a></td>
+ <td><a href="#term-Membership">prov:Membership</a></td>
<td>prov:hadMember</td>
</tr>
</tbody></table>
@@ -835,8 +844,8 @@
<section id="term-Entity">
<h4><span class="secno">3.1.1 </span>Entity</h4>
-<span class="glossary-ref"> An <span class="dfn">entity</span> is a physical, digital, conceptual, or other kind of thing with some fixed aspects; entities may be real or imaginary. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Entity">
+<p>From [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>]:</p><blockquote><i><span class="glossary-ref"> An <span class="dfn">entity</span> is a physical, digital, conceptual, or other kind of thing with some fixed aspects; entities may be real or imaginary. </span></i></blockquote>
+<p>ComplexType definition (denoting a similarly named prov-"type") in XML Schema:</p><pre class="schema-type"><xs:complexType name="Entity">
<xs:sequence>
<!-- prov attributes -->
<xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
@@ -848,7 +857,7 @@
<xs:attribute ref="prov:id"/>
</xs:complexType>
</pre>
-<p>The element <code>prov:entity</code> is used to reference a prov:Entity from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="entity" type="prov:Entity"/>
+<p>The xml-element <code>prov:entity</code> is used to denote a prov:Entity prov-"type" from within a prov:Document or prov:BundleConstructor.</p><p>XML Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="entity" type="prov:Entity"/>
</pre>
<div class="example"><div class="example-title"><span>Example 6</span>: prov:entity</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -867,8 +876,8 @@
<section id="term-Activity">
<h4><span class="secno">3.1.2 </span>Activity</h4>
-<span class="glossary-ref"> An <span class="dfn">activity</span> is something that occurs over a period of time and acts upon or with entities; it may include consuming, processing, transforming, modifying, relocating, using, or generating entities. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Activity">
+<p>From [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>]:</p><blockquote><i><span class="glossary-ref"> An <span class="dfn">activity</span> is something that occurs over a period of time and acts upon or with entities; it may include consuming, processing, transforming, modifying, relocating, using, or generating entities. </span></i></blockquote>
+<p>ComplexType definition (denoting a similarly named prov-"type") in XML Schema:</p><pre class="schema-type"><xs:complexType name="Activity">
<xs:sequence>
<xs:element name="startTime" type="xs:dateTime" minOccurs="0"/>
<xs:element name="endTime" type="xs:dateTime" minOccurs="0"/>
@@ -881,7 +890,7 @@
<xs:attribute ref="prov:id"/>
</xs:complexType>
</pre>
-<p>The element <code>prov:activity</code> is used to reference a prov:Activity from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="activity" type="prov:Activity"/>
+<p>The xml-element <code>prov:activity</code> is used to denote a prov:Activity prov-"type" from within a prov:Document or prov:BundleConstructor.</p><p>XML Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="activity" type="prov:Activity"/>
</pre>
<div class="example"><div class="example-title"><span>Example 7</span>: prov:activity</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -889,7 +898,7 @@
xmlns:prov="http://www.w3.org/ns/prov#"
xmlns:ex="http://example.com/ns/ex#">
- <b><prov:activity prov:id="a1">
+ <b><prov:activity prov:id="ex:a1">
<prov:startTime>2011-11-16T16:05:00</prov:startTime>
<prov:endTime>2011-11-16T16:06:00</prov:endTime>
<prov:type xsi:type="xsd:QName">ex:edit</prov:type>
@@ -901,8 +910,8 @@
<section id="term-Generation">
<h4><span class="secno">3.1.3 </span>Generation</h4>
-<span class="glossary-ref"> <span class="dfn">Generation</span> is the completion of production of a new entity by an activity. This entity did not exist before generation and becomes available for usage after this generation. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Generation">
+<p>From [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>]:</p><blockquote><i><span class="glossary-ref"> <span class="dfn">Generation</span> is the completion of production of a new entity by an activity. This entity did not exist before generation and becomes available for usage after this generation. </span></i></blockquote>
+<p>ComplexType definition (denoting a similarly named prov-"type") in XML Schema:</p><pre class="schema-type"><xs:complexType name="Generation">
<xs:sequence>
<xs:element name="entity" type="prov:IDRef"/>
<xs:element name="activity" type="prov:IDRef" minOccurs="0"/>
@@ -917,28 +926,28 @@
<xs:attribute ref="prov:id"/>
</xs:complexType>
</pre>
-<p>The element <code>prov:wasGeneratedBy</code> is used to reference a prov:Generation from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasGeneratedBy" type="prov:Generation"/>
+<p>The xml-element <code>prov:wasGeneratedBy</code> is used to denote a prov:Generation prov-"type" from within a prov:Document or prov:BundleConstructor.</p><p>XML Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasGeneratedBy" type="prov:Generation"/>
</pre>
<div class="example"><div class="example-title"><span>Example 8</span>: prov:wasGeneratedBy</div><pre class="example"><prov:document
xmlns:prov="http://www.w3.org/ns/prov#"
xmlns:ex="http://example.com/ns/ex#">
- <prov:entity prov:id="e1"/>
+ <prov:entity prov:id="ex:e1"/>
- <prov:activity prov:id="a1"/>
+ <prov:activity prov:id="ex:a1"/>
<b><prov:wasGeneratedBy>
- <prov:entity prov:ref="e1"/>
- <prov:activity prov:ref="a1"/>
+ <prov:entity prov:ref="ex:e1"/>
+ <prov:activity prov:ref="ex:a1"/>
<prov:time>2001-10-26T21:32:52</prov:time>
<ex:port>p1</ex:port>
</prov:wasGeneratedBy></b>
- <prov:entity prov:id="e2"/>
+ <prov:entity prov:id="ex:e2"/>
<b><prov:wasGeneratedBy>
- <prov:entity prov:ref="e2"/>
- <prov:activity prov:ref="a1"/>
+ <prov:entity prov:ref="ex:e2"/>
+ <prov:activity prov:ref="ex:a1"/>
<prov:time>2001-10-26T10:00:00</prov:time>
<ex:port>p2</ex:port>
</prov:wasGeneratedBy></b>
@@ -948,8 +957,8 @@
<section id="term-Usage">
<h4><span class="secno">3.1.4 </span>Usage</h4>
-<span class="glossary-ref"> <span class="dfn">Usage</span> is the beginning of utilizing an entity by an activity. Before usage, the activity had not begun to utilize this entity and could not have been affected by the entity. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Usage">
+<p>From [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>]:</p><blockquote><i><span class="glossary-ref"> <span class="dfn">Usage</span> is the beginning of utilizing an entity by an activity. Before usage, the activity had not begun to utilize this entity and could not have been affected by the entity. </span></i></blockquote>
+<p>ComplexType definition (denoting a similarly named prov-"type") in XML Schema:</p><pre class="schema-type"><xs:complexType name="Usage">
<xs:sequence>
<xs:element name="activity" type="prov:IDRef"/>
<xs:element name="entity" type="prov:IDRef" minOccurs="0"/>
@@ -964,28 +973,28 @@
<xs:attribute ref="prov:id"/>
</xs:complexType>
</pre>
-<p>The element <code>prov:used</code> is used to reference a prov:Usage from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="used" type="prov:Usage"/>
+<p>The xml-element <code>prov:used</code> is used to denote a prov:Usage prov-"type" from within a prov:Document or prov:BundleConstructor.</p><p>XML Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="used" type="prov:Usage"/>
</pre>
<div class="example"><div class="example-title"><span>Example 9</span>: prov:used</div><pre class="example"><prov:document
xmlns:prov="http://www.w3.org/ns/prov#"
xmlns:ex="http://example.com/ns/ex#">
- <prov:activity prov:id="a1"/>
+ <prov:activity prov:id="ex:a1"/>
- <prov:entity prov:id="e1"/>
+ <prov:entity prov:id="ex:e1"/>
- <prov:entity prov:id="e2"/>
+ <prov:entity prov:id="ex:e2"/>
<b><prov:used>
- <prov:activity prov:ref="a1"/>
- <prov:entity prov:ref="e1"/>
+ <prov:activity prov:ref="ex:a1"/>
+ <prov:entity prov:ref="ex:e1"/>
<prov:time≶2011-11-16T16:00:00</prov:time>
<ex:parameter>p1</ex:parameter>
</prov:used></b>
<b><prov:used>
- <prov:activity prov:ref="a1"/>
- <prov:entity prov:ref="e2"/>
+ <prov:activity prov:ref="ex:a1"/>
+ <prov:entity prov:ref="ex:e2"/>
<prov:time>2011-11-16T16:00:01</prov:time>
<ex:parameter>p2</ex:parameter>
</prov:used></b>
@@ -995,8 +1004,8 @@
<section id="term-Communication">
<h4><span class="secno">3.1.5 </span>Communication</h4>
-<span class="glossary-ref"> <span class="dfn">Communication</span> is the exchange of some unspecified entity by two activities, one activity using some entity generated by the other. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Communication">
+<p>From [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>]:</p><blockquote><i><span class="glossary-ref"> <span class="dfn">Communication</span> is the exchange of some unspecified entity by two activities, one activity using some entity generated by the other. </span></i></blockquote>
+<p>ComplexType definition (denoting a similarly named prov-"type") in XML Schema:</p><pre class="schema-type"><xs:complexType name="Communication">
<xs:sequence>
<xs:element name="informed" type="prov:IDRef"/>
<xs:element name="informant" type="prov:IDRef"/>
@@ -1008,24 +1017,25 @@
<xs:attribute ref="prov:id"/>
</xs:complexType>
</pre>
-<p>The element <code>prov:wasInformedBy</code> is used to reference a prov:Communication from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasInformedBy" type="prov:Communication"/>
+<p>The xml-element <code>prov:wasInformedBy</code> is used to denote a prov:Communication prov-"type" from within a prov:Document or prov:BundleConstructor.</p><p>XML Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasInformedBy" type="prov:Communication"/>
</pre>
<div class="example"><div class="example-title"><span>Example 10</span>: prov:wasInformedBy</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
- xmlns:prov="http://www.w3.org/ns/prov#">
+ xmlns:prov="http://www.w3.org/ns/prov#"
+ xmlns:ex="http://example.com/ns/ex#">
- <prov:activity prov:id="a1">
+ <prov:activity prov:id="ex:a1">
<prov:type xsi:type="xsd:string">traffic regulations enforcing<prov:type>
</prov:activity>
- <prov:activity prov:id="a2">
+ <prov:activity prov:id="ex:a2">
<prov:type xsi:type="xsd:string">fine paying, check writing, and mailing</prov:type>
</prov:activity>
<b><prov:wasInformedBy>
- <prov:informed prov:ref="a2"/>
- <prov:informant prov:ref="a1"/>
+ <prov:informed prov:ref="ex:a2"/>
+ <prov:informant prov:ref="ex:a1"/>
</prov:wasInformedBy></b>
</prov:document></pre></div>
@@ -1033,8 +1043,8 @@
<section id="term-Start">
<h4><span class="secno">3.1.6 </span>Start</h4>
-<span class="glossary-ref"> <span class="dfn">Start</span> is when an activity is deemed to have been started by an entity, known as <span class="dfn">trigger</span>. The activity did not exist before its start. Any usage, generation, or invalidation involving an activity follows the activity's start. A start may refer to a trigger entity that set off the activity, or to an activity, known as <span class="dfn">starter</span>, that generated the trigger. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Start">
+<p>From [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>]:</p><blockquote><i><span class="glossary-ref"> <span class="dfn">Start</span> is when an activity is deemed to have been started by an entity, known as <span class="dfn">trigger</span>. The activity did not exist before its start. Any usage, generation, or invalidation involving an activity follows the activity's start. A start may refer to a trigger entity that set off the activity, or to an activity, known as <span class="dfn">starter</span>, that generated the trigger. </span></i></blockquote>
+<p>ComplexType definition (denoting a similarly named prov-"type") in XML Schema:</p><pre class="schema-type"><xs:complexType name="Start">
<xs:sequence>
<xs:element name="activity" type="prov:IDRef"/>
<xs:element name="trigger" type="prov:IDRef" minOccurs="0"/>
@@ -1050,7 +1060,7 @@
<xs:attribute ref="prov:id"/>
</xs:complexType>
</pre>
-<p>The element <code>prov:wasStartedBy</code> is used to reference a prov:Start from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasStartedBy" type="prov:Start"/>
+<p>The xml-element <code>prov:wasStartedBy</code> is used to denote a prov:Start prov-"type" from within a prov:Document or prov:BundleConstructor.</p><p>XML Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasStartedBy" type="prov:Start"/>
</pre>
<div class="example"><div class="example-title"><span>Example 11</span>: prov:wasStartedBy</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -1058,44 +1068,44 @@
xmlns:prov="http://www.w3.org/ns/prov#"
xmlns:ex="http://example.com/ns/ex#">
- <prov:entity prov:id="e1">
+ <prov:entity prov:id="ex:e1">
<prov:type xsi:type="xsd:string">email message</prov:type>
</prov:entity>
- <prov:activity prov:id="a1">
+ <prov:activity prov:id="ex:a1">
<prov:type xsi:type="xsd:QName">Discuss</prov:type>
</prov:activity>
<b><prov:wasStartedBy>
- <prov:activity prov:ref="a1"/>
- <prov:trigger prov:ref="e1"/>
+ <prov:activity prov:ref="ex:a1"/>
+ <prov:trigger prov:ref="ex:e1"/>
<prov:time>2011-11-16T16:05:00</prov:time>
</prov:wasStartedBy></b>
<prov:used>
- <prov:activity prov:ref="a1"/>
- <prov:entity prov:ref="e1"/>
+ <prov:activity prov:ref="ex:a1"/>
+ <prov:entity prov:ref="ex:e1"/>
</prov:used>
- <prov:activity prov:id="a0">
+ <prov:activity prov:id="ex:a0">
<prov:type xsi:type="xsd:QName">Write</prov:type>
</prov:activity>
<prov:wasGeneratedBy>
- <prov:entity prov:ref="e1"/>
- <prov:activity prov:ref="a0"/>
+ <prov:entity prov:ref="ex:e1"/>
+ <prov:activity prov:ref="ex:a0"/>
</prov:wasGeneratedBy>
<b><prov:wasStartedBy>
- <prov:activity prov:ref="a1"/>
- <prov:trigger prov:ref="e1"/>
- <prov:starter prov:ref="a0"/>
+ <prov:activity prov:ref="ex:a1"/>
+ <prov:trigger prov:ref="ex:e1"/>
+ <prov:starter prov:ref="ex:a0"/>
<prov:time>2011-11-16T16:05:00</prov:time>
</prov:wasStartedBy></b>
<b><prov:wasStartedBy>
- <prov:activity prov:ref="a1"/>
- <prov:starter prov:ref="a0"/>
+ <prov:activity prov:ref="ex:a1"/>
+ <prov:starter prov:ref="ex:a0"/>
<prov:time>2011-11-16T16:05:00</prov:time>
</prov:wasStartedBy></b>
@@ -1104,8 +1114,8 @@
<section id="term-End">
<h4><span class="secno">3.1.7 </span>End</h4>
-<span class="glossary-ref"> <span class="dfn">End</span> is when an activity is deemed to have been ended by an entity, known as <span class="dfn">trigger</span>. The activity no longer exists after its end. Any usage, generation, or invalidation involving an activity precedes the activity's end. An end may refer to a trigger entity that terminated the activity, or to an activity, known as <span class="dfn">ender</span> that generated the trigger. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="End">
+<p>From [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>]:</p><blockquote><i><span class="glossary-ref"> <span class="dfn">End</span> is when an activity is deemed to have been ended by an entity, known as <span class="dfn">trigger</span>. The activity no longer exists after its end. Any usage, generation, or invalidation involving an activity precedes the activity's end. An end may refer to a trigger entity that terminated the activity, or to an activity, known as <span class="dfn">ender</span> that generated the trigger. </span></i></blockquote>
+<p>ComplexType definition (denoting a similarly named prov-"type") in XML Schema:</p><pre class="schema-type"><xs:complexType name="End">
<xs:sequence>
<xs:element name="activity" type="prov:IDRef"/>
<xs:element name="trigger" type="prov:IDRef" minOccurs="0"/>
@@ -1121,7 +1131,7 @@
<xs:attribute ref="prov:id"/>
</xs:complexType>
</pre>
-<p>The element <code>prov:wasEndedBy</code> is used to reference a prov:End from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasEndedBy" type="prov:End"/>
+<p>The xml-element <code>prov:wasEndedBy</code> is used to denote a prov:End prov-"type" from within a prov:Document or prov:BundleConstructor.</p><p>XML Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasEndedBy" type="prov:End"/>
</pre>
<div class="example"><div class="example-title"><span>Example 12</span>: prov:wasEndedBy</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -1129,17 +1139,17 @@
xmlns:prov="http://www.w3.org/ns/prov#"
xmlns:ex="http://example.com/ns/ex#">
- <prov:entity prov:id="e1">
+ <prov:entity prov:id="ex:e1">
<prov:type xsi:type="xsd:string">approval document</prov:type>
</prov:entity>
- <prov:activity prov:id="a1">
+ <prov:activity prov:id="ex:a1">
<prov:type xsi:type="xsd:QName">Editing</prov:type>
</prov:activity>
<b><prov:wasEndedBy>
- <prov:activity prov:ref="a1"/>
- <prov:trigger prov:ref="e1"/>
+ <prov:activity prov:ref="ex:a1"/>
+ <prov:trigger prov:ref="ex:e1"/>
</prov:wasEndedBy></b>
</prov:document></pre></div>
@@ -1147,8 +1157,8 @@
<section id="term-Invalidation">
<h4><span class="secno">3.1.8 </span>Invalidation</h4>
-<span class="glossary-ref"> <span class="dfn">Invalidation</span> is the start of the destruction, cessation, or expiry of an existing entity by an activity. The entity is no longer available for use (or further invalidation) after invalidation. Any generation or usage of an entity precedes its invalidation.</span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Invalidation">
+<p>From [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>]:</p><blockquote><i><span class="glossary-ref"> <span class="dfn">Invalidation</span> is the start of the destruction, cessation, or expiry of an existing entity by an activity. The entity is no longer available for use (or further invalidation) after invalidation. Any generation or usage of an entity precedes its invalidation.</span></i></blockquote>
+<p>ComplexType definition (denoting a similarly named prov-"type") in XML Schema:</p><pre class="schema-type"><xs:complexType name="Invalidation">
<xs:sequence>
<xs:element name="entity" type="prov:IDRef"/>
<xs:element name="activity" type="prov:IDRef" minOccurs="0"/>
@@ -1163,7 +1173,7 @@
<xs:attribute ref="prov:id"/>
</xs:complexType>
</pre>
-<p>The element <code>prov:wasInvalidatedBy</code> is used to reference a prov:Invalidation from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasInvalidatedBy" type="prov:Invalidation"/>
+<p>The xml-element <code>prov:wasInvalidatedBy</code> is used to denote a prov:Invalidation prov-"type" from within a prov:Document or prov:BundleConstructor.</p><p>XML Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasInvalidatedBy" type="prov:Invalidation"/>
</pre>
<div class="example"><div class="example-title"><span>Example 13</span>: prov:wasInvalidatedBy</div><pre class="example"><prov:document
xmlns:prov="http://www.w3.org/ns/prov#"
@@ -1196,12 +1206,12 @@
<section id="component2">
<h3><span class="secno">3.2 </span>Component 2: Derivations</h3>
-<p>The second component of PROV-DM is concerned with: <a title="derivation" href="#term-Derivation">derivations</a> of <a title="entity">entities</a> from other entities and derivation subtypes WasRevisionOf (<a href="#term-Revision">Revision</a>), WasQuotedFrom (<a href="#term-Quotation">Quotation</a>), and HasPrimarySource (<a href="#term-PrimarySource">Primary Source</a>).</p>
+<p>The second component of PROV-DM is concerned with: <a title="derivation" href="#term-Derivation">derivations</a> of <a title="entity">entities</a> from other entities and derivation subtypes<a href="#term-Revision">Revision</a>, <a href="#term-Quotation">Quotation</a>, and <a href="#term-PrimarySource">Primary Source</a>.</p>
<section id="term-Derivation">
<h4><span class="secno">3.2.1 </span>Derivation</h4>
-<span class="glossary-ref"> A <span class="dfn">derivation</span> is a transformation of an entity into another, an update of an entity resulting in a new one, or the construction of a new entity based on a pre-existing entity.</span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Derivation">
+<p>From [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>]:</p><blockquote><i><span class="glossary-ref"> A <span class="dfn">derivation</span> is a transformation of an entity into another, an update of an entity resulting in a new one, or the construction of a new entity based on a pre-existing entity.</span></i></blockquote>
+<p>ComplexType definition (denoting a similarly named prov-"type") in XML Schema:</p><pre class="schema-type"><xs:complexType name="Derivation">
<xs:sequence>
<xs:element name="generatedEntity" type="prov:IDRef"/>
<xs:element name="usedEntity" type="prov:IDRef"/>
@@ -1216,25 +1226,26 @@
<xs:attribute ref="prov:id"/>
</xs:complexType>
</pre>
-<p>The element <code>prov:wasDerivedFrom</code> is used to reference a prov:Derivation from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasDerivedFrom" type="prov:Derivation"/>
+<p>The xml-element <code>prov:wasDerivedFrom</code> is used to denote a prov:Derivation prov-"type" from within a prov:Document or prov:BundleConstructor.</p><p>XML Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasDerivedFrom" type="prov:Derivation"/>
</pre>
<div class="example"><div class="example-title"><span>Example 14</span>: prov:wasDerivedFrom</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
- xmlns:prov="http://www.w3.org/ns/prov#">
+ xmlns:prov="http://www.w3.org/ns/prov#"
+ xmlns:ex="http://example.com/ns/ex#">
- <prov:entity prov:id="e1"/>
+ <prov:entity prov:id="ex:e1"/>
- <prov:entity prov:id="e2"/>
+ <prov:entity prov:id="ex:e2"/>
<b><prov:wasDerivedFrom>
- <prov:generatedEntity prov:ref="e2"/>
- <prov:usedEntity prov:ref="e1"/>
+ <prov:generatedEntity prov:ref="ex:e2"/>
+ <prov:usedEntity prov:ref="ex:e1"/>
</prov:wasDerivedFrom></b>
<b><prov:wasDerivedFrom>
- <prov:generatedEntity prov:ref="e2"/>
- <prov:usedEntity prov:ref="e1"/>
+ <prov:generatedEntity prov:ref="ex:e2"/>
+ <prov:usedEntity prov:ref="ex:e1"/>
<prov:type xsi:type="xsd:string">physical transform</prov:type>
</prov:wasDerivedFrom></b>
@@ -1243,15 +1254,15 @@
<section id="term-Revision">
<h4><span class="secno">3.2.2 </span>Revision</h4>
-<span class="glossary-ref"> A <span class="dfn">revision</span> is a derivation for which the resulting entity is a revised version of some original. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Revision">
+<p>From [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>]:</p><blockquote><i><span class="glossary-ref"> A <span class="dfn">revision</span> is a derivation for which the resulting entity is a revised version of some original. </span></i></blockquote>
+<p>ComplexType definition (denoting a similarly named prov-"type") in XML Schema:</p><pre class="schema-type"><xs:complexType name="Revision">
<xs:complexContent>
<xs:extension base="prov:Derivation">
</xs:extension>
</xs:complexContent>
</xs:complexType>
</pre>
-<p>The element <code>prov:wasRevisionOf</code> is used to reference a prov:Revision from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasRevisionOf" type="prov:Revision"/>
+<p>The xml-element <code>prov:wasRevisionOf</code> is used to denote a prov:Revision prov-"type" from within a prov:Document or prov:BundleConstructor.</p><p>XML Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasRevisionOf" type="prov:Revision"/>
</pre>
<div class="example"><div class="example-title"><span>Example 15</span>: prov:wasRevisionOf</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -1278,15 +1289,15 @@
<section id="term-Quotation">
<h4><span class="secno">3.2.3 </span>Quotation</h4>
-<span class="glossary-ref"> A <span class="dfn">quotation</span> is the repeat of (some or all of) an entity, such as text or image, by someone who may or may not be its original author. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Quotation">
+<p>From [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>]:</p><blockquote><i><span class="glossary-ref"> A <span class="dfn">quotation</span> is the repeat of (some or all of) an entity, such as text or image, by someone who may or may not be its original author. </span></i></blockquote>
+<p>ComplexType definition (denoting a similarly named prov-"type") in XML Schema:</p><pre class="schema-type"><xs:complexType name="Quotation">
<xs:complexContent>
<xs:extension base="prov:Derivation">
</xs:extension>
</xs:complexContent>
</xs:complexType>
</pre>
-<p>The element <code>prov:wasQuotedFrom</code> is used to reference a prov:Quotation from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasQuotedFrom" type="prov:Quotation"/>
+<p>The xml-element <code>prov:wasQuotedFrom</code> is used to denote a prov:Quotation prov-"type" from within a prov:Document or prov:BundleConstructor.</p><p>XML Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasQuotedFrom" type="prov:Quotation"/>
</pre>
<div class="example"><div class="example-title"><span>Example 16</span>: prov:wasQuotedFrom</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -1324,15 +1335,15 @@
<section id="term-PrimarySource">
<h4><span class="secno">3.2.4 </span>Primary Source</h4>
-<span class="glossary-ref"> A <span class="dfn">primary source</span> for a topic refers to something produced by some agent with direct experience and knowledge about the topic, at the time of the topic's study, without benefit from hindsight. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="PrimarySource">
+<p>From [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>]:</p><blockquote><i><span class="glossary-ref"> A <span class="dfn">primary source</span> for a topic refers to something produced by some agent with direct experience and knowledge about the topic, at the time of the topic's study, without benefit from hindsight. </span></i></blockquote>
+<p>ComplexType definition (denoting a similarly named prov-"type") in XML Schema:</p><pre class="schema-type"><xs:complexType name="PrimarySource">
<xs:complexContent>
<xs:extension base="prov:Derivation">
</xs:extension>
</xs:complexContent>
</xs:complexType>
</pre>
-<p>The element <code>prov:hadPrimarySource</code> is used to reference a prov:PrimarySource from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="hadPrimarySource" type="prov:PrimarySource"/>
+<p>The xml-element <code>prov:hadPrimarySource</code> is used to denote a prov:PrimarySource prov-"type" from within a prov:Document or prov:BundleConstructor.</p><p>XML Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="hadPrimarySource" type="prov:PrimarySource"/>
</pre>
<div class="example"><div class="example-title"><span>Example 17</span>: prov:hadPrimarySource</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -1361,13 +1372,12 @@
<section id="component3">
<h3><span class="secno">3.3 </span>Component 3: Agents, Responsibility, and Influence</h3>
-<p>The third component of PROV-DM is concerned with <a title="agent">agents</a> and the relations WasAttributedTo
-(<a href="#term-Attribution">Attribution</a>), WasAssociatedWith (<a href="#term-Association">Association</a>), ActedOnBehalfOf (<a href="#term-Delegation">Delegation</a>), relating agents to entities, activities, and agents, respectively.</p>
+<p>The third component of PROV-DM is concerned with <a title="agent">agents</a> and the relations <a href="#term-Attribution">Attribution</a>, <a href="#term-Association">Association</a>, and <a href="#term-Delegation">Delegation</a>, relating agents to entities, activities, and agents, respectively.</p>
<section id="term-Agent">
<h4><span class="secno">3.3.1 </span>Agent</h4>
-<span class="glossary-ref"> An <span class="dfn">agent</span> is something that bears some form of responsibility for an activity taking place, for the existence of an entity, or for another agent's activity. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Agent">
+<p>From [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>]:</p><blockquote><i><span class="glossary-ref"> An <span class="dfn">agent</span> is something that bears some form of responsibility for an activity taking place, for the existence of an entity, or for another agent's activity. </span></i></blockquote>
+<p>ComplexType definition (denoting a similarly named prov-"type") in XML Schema:</p><pre class="schema-type"><xs:complexType name="Agent">
<xs:sequence>
<!-- prov attributes -->
<xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
@@ -1378,7 +1388,7 @@
<xs:attribute ref="prov:id"/>
</xs:complexType>
</pre>
-<p>The element <code>prov:agent</code> is used to reference a prov:Agent from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="agent" type="prov:Agent"/>
+<p>The xml-element <code>prov:agent</code> is used to denote a prov:Agent prov-"type" from within a prov:Document or prov:BundleConstructor.</p><p>XML Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="agent" type="prov:Agent"/>
</pre>
<div class="example"><div class="example-title"><span>Example 18</span>: prov:agent</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -1386,7 +1396,7 @@
xmlns:prov="http://www.w3.org/ns/prov#"
xmlns:ex="http://example.com/ns/ex#">
- <b><prov:agent prov:id="e1">
+ <b><prov:agent prov:id="ex:e1">
<prov:type xsi:type="xsd:QName">prov:Person</prov:type>
<ex:name>Alice</ex:name>
<ex:employee>1234</ex:employee>
@@ -1396,15 +1406,15 @@
<section id="term-Person">
<h5><span class="secno">3.3.1.1 </span>Person</h5>
-<span class="glossary-ref"> Agents of type <span class="dfn">Person</span> are people. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Person">
+<p>From [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>]:</p><blockquote><i><span class="glossary-ref"> <span class="dfn">Person</span> agents are people. </span></i></blockquote>
+<p>ComplexType definition (denoting a similarly named prov-"type") in XML Schema:</p><pre class="schema-type"><xs:complexType name="Person">
<xs:complexContent>
<xs:extension base="prov:Agent">
</xs:extension>
</xs:complexContent>
</xs:complexType>
</pre>
-<p>The element <code>prov:person</code> is used to reference a prov:Person from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="person" type="prov:Person"/>
+<p>The xml-element <code>prov:person</code> is used to denote a prov:Person prov-"type" from within a prov:Document or prov:BundleConstructor.</p><p>XML Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="person" type="prov:Person"/>
</pre>
<div class="example"><div class="example-title"><span>Example 19</span>: prov:person</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -1419,21 +1429,21 @@
<section id="term-Organization">
<h5><span class="secno">3.3.1.2 </span>Organization</h5>
-<span class="glossary-ref"> Agents of type <span class="dfn">Organization</span> are social or legal institutions such as companies, societies, etc. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Organization">
+<p>From [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>]:</p><blockquote><i><span class="glossary-ref"> An <span class="dfn">organization</span> is a social or legal institution such as a company, society, etc. </span></i></blockquote>
+<p>ComplexType definition (denoting a similarly named prov-"type") in XML Schema:</p><pre class="schema-type"><xs:complexType name="Organization">
<xs:complexContent>
<xs:extension base="prov:Agent">
</xs:extension>
</xs:complexContent>
</xs:complexType>
</pre>
-<p>The element <code>prov:organization</code> is used to reference a prov:Organization from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="organization" type="prov:Organization"/>
+<p>The xml-element <code>prov:organization</code> is used to denote a prov:Organization prov-"type" from within a prov:Document or prov:BundleConstructor.</p><p>XML Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="organization" type="prov:Organization"/>
</pre>
<div class="example"><div class="example-title"><span>Example 20</span>: prov:organization</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:prov="http://www.w3.org/ns/prov#"
- xmlns:ex="http://example.com/ns/ex#">
+ xmlns:w3="http://w3.org/">
<b><prov:organization prov:id="w3:Consortium" /></b>
@@ -1442,15 +1452,15 @@
<section id="term-SoftwareAgent">
<h5><span class="secno">3.3.1.3 </span>Software Agent</h5>
-<span class="glossary-ref"> A <span class="dfn">SoftwareAgent</span> is running software. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="SoftwareAgent">
+<p>From [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>]:</p><blockquote><i><span class="glossary-ref"> A <span class="dfn">software agent</span> is running software. </span></i></blockquote>
+<p>ComplexType definition (denoting a similarly named prov-"type") in XML Schema:</p><pre class="schema-type"><xs:complexType name="SoftwareAgent">
<xs:complexContent>
<xs:extension base="prov:Agent">
</xs:extension>
</xs:complexContent>
</xs:complexType>
</pre>
-<p>The element <code>prov:softwareAgent</code> is used to reference a prov:SoftwareAgent from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="softwareAgent" type="prov:SoftwareAgent"/>
+<p>The xml-element <code>prov:softwareAgent</code> is used to denote a prov:SoftwareAgent prov-"type" from within a prov:Document or prov:BundleConstructor.</p><p>XML Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="softwareAgent" type="prov:SoftwareAgent"/>
</pre>
<div class="example"><div class="example-title"><span>Example 21</span>: prov:softwareAgent</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -1458,7 +1468,7 @@
xmlns:prov="http://www.w3.org/ns/prov#"
xmlns:ex="http://example.com/ns/ex#">
- <b><prov:softwareAgent prov:id="ag" /></b>
+ <b><prov:softwareAgent prov:id="ex:ag" /></b>
</prov:document></pre></div>
</section> <!-- end term-SoftwareAgent -->
@@ -1467,8 +1477,8 @@
<section id="term-Attribution">
<h4><span class="secno">3.3.2 </span>Attribution</h4>
-<span class="glossary-ref"> <span class="dfn">Attribution</span> is the ascribing of an entity to an agent. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Attribution">
+<p>From [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>]:</p><blockquote><i><span class="glossary-ref"> <span class="dfn">Attribution</span> is the ascribing of an entity to an agent. </span></i></blockquote>
+<p>ComplexType definition (denoting a similarly named prov-"type") in XML Schema:</p><pre class="schema-type"><xs:complexType name="Attribution">
<xs:sequence>
<xs:element name="entity" type="prov:IDRef"/>
<xs:element name="agent" type="prov:IDRef"/>
@@ -1480,7 +1490,7 @@
<xs:attribute ref="prov:id"/>
</xs:complexType>
</pre>
-<p>The element <code>prov:wasAttributedTo</code> is used to reference a prov:Attribution from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasAttributedTo" type="prov:Attribution"/>
+<p>The xml-element <code>prov:wasAttributedTo</code> is used to denote a prov:Attribution prov-"type" from within a prov:Document or prov:BundleConstructor.</p><p>XML Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasAttributedTo" type="prov:Attribution"/>
</pre>
<div class="example"><div class="example-title"><span>Example 22</span>: prov:wasAttributedTo</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -1503,13 +1513,13 @@
</prov:entity>
<b><prov:wasAttributedTo>
- <prov:entity prov:ref="rec54:WD"/>
+ <prov:entity prov:ref="tr:WD-prov-dm-20111215"/>
<prov:agent prov:ref="ex:Paolo"/>
<prov:type xsi:type="xsd:QName">editorship</prov:type>
</prov:wasAttributedTo></b>
<b><prov:wasAttributedTo>
- <prov:entity prov:ref="rec54:WD"/>
+ <prov:entity prov:ref="tr:WD-prov-dm-20111215"/>
<prov:agent prov:ref="ex:Simon"/>
<prov:type xsi:type="xsd:QName">authorship</prov:type>
</prov:wasAttributedTo></b>
@@ -1519,8 +1529,8 @@
<section id="term-Association">
<h4><span class="secno">3.3.3 </span>Association</h4>
-<span class="glossary-ref"> An activity <span class="dfn">association</span> is an assignment of responsibility to an agent for an activity, indicating that the agent had a role in the activity. It further allows for a plan to be specified, which is the plan intended by the agent to achieve some goals in the context of this activity. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Association">
+<p>From [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>]:</p><blockquote><i><span class="glossary-ref"> An activity <span class="dfn">association</span> is an assignment of responsibility to an agent for an activity, indicating that the agent had a role in the activity. It further allows for a plan to be specified, which is the plan intended by the agent to achieve some goals in the context of this activity. </span></i></blockquote>
+<p>ComplexType definition (denoting a similarly named prov-"type") in XML Schema:</p><pre class="schema-type"><xs:complexType name="Association">
<xs:sequence>
<xs:element name="activity" type="prov:IDRef"/>
<xs:element name="agent" type="prov:IDRef" minOccurs="0"/>
@@ -1534,7 +1544,7 @@
<xs:attribute ref="prov:id"/>
</xs:complexType>
</pre>
-<p>The element <code>prov:wasAssociatedWith</code> is used to reference a prov:Association from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasAssociatedWith" type="prov:Association"/>
+<p>The xml-element <code>prov:wasAssociatedWith</code> is used to denote a prov:Association prov-"type" from within a prov:Document or prov:BundleConstructor.</p><p>XML Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasAssociatedWith" type="prov:Association"/>
</pre>
<div class="example"><div class="example-title"><span>Example 23</span>: prov:wasAssociatedWith</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -1542,28 +1552,28 @@
xmlns:prov="http://www.w3.org/ns/prov#"
xmlns:ex="http://example.com/ns/ex#">
- <prov:activity prov:id="a">
+ <prov:activity prov:id="ex:a">
<prov:type xsi:type="xsd:string">workflow execution</prov:type>
</prov:activity>
- <prov:agent prov:id="ag1">
+ <prov:agent prov:id="ex:ag1">
<prov:type xsi:type="xsd:QName">operator</prov:type>
</prov:agent>
- <prov:agent prov:id="ag2">
+ <prov:agent prov:id="ex:ag2">
<prov:type xsi:type="xsd:QName">designator</prov:type>
</prov:agent>
<b><prov:wasAssociatedWith>
- <prov:activity prov:ref="a"/>
- <prov:agent prov:ref="ag1"/>
+ <prov:activity prov:ref="ex:a"/>
+ <prov:agent prov:ref="ex:ag1"/>
<prov:role xsi:type="xsd:QName">loggedInUser</prov:role>
<ex:how>webapp</ex:how>
</prov:wasAssociatedWith></b>
<b><prov:wasAssociatedWith>
- <prov:activity prov:ref="a"/>
- <prov:agent prov:ref="ag2"/>
+ <prov:activity prov:ref="ex:a"/>
+ <prov:agent prov:ref="ex:ag2"/>
<prov:plan prov:ref="ex:wf"/>
<prov:role xsi:type="xsd:QName">designer</prov:role>
<ex:content>project1</ex:content>
@@ -1578,15 +1588,15 @@
<section id="term-Plan">
<h5><span class="secno">3.3.3.1 </span>Plan</h5>
-<span class="glossary-ref"> A <span class="dfn">plan</span> is an entity that represents a set of actions or steps intended by one or more agents to achieve some goals. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Plan">
+<p>From [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>]:</p><blockquote><i><span class="glossary-ref"> A <span class="dfn">plan</span> is an entity that represents a set of actions or steps intended by one or more agents to achieve some goals. </span></i></blockquote>
+<p>ComplexType definition (denoting a similarly named prov-"type") in XML Schema:</p><pre class="schema-type"><xs:complexType name="Plan">
<xs:complexContent>
<xs:extension base="prov:Entity">
</xs:extension>
</xs:complexContent>
</xs:complexType>
</pre>
-<p>The element <code>prov:plan</code> is used to reference a prov:Plan from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="plan" type="prov:Plan"/>
+<p>The xml-element <code>prov:plan</code> is used to denote a prov:Plan prov-"type" from within a prov:Document or prov:BundleConstructor.</p><p>XML Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="plan" type="prov:Plan"/>
</pre>
<div class="example"><div class="example-title"><span>Example 24</span>: prov:plan</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -1594,28 +1604,28 @@
xmlns:prov="http://www.w3.org/ns/prov#"
xmlns:ex="http://example.com/ns/ex#">
- <prov:activity prov:id="a">
+ <prov:activity prov:id="ex:a">
<prov:type xsi:type="xsd:string">workflow execution</prov:type>
</prov:activity>
- <prov:agent prov:id="ag1">
+ <prov:agent prov:id="ex:ag1">
<prov:type xsi:type="xsd:QName">operator</prov:type>
</prov:agent>
- <prov:agent prov:id="ag2">
+ <prov:agent prov:id="ex:ag2">
<prov:type xsi:type="xsd:QName">designator</prov:type>
</prov:agent>
<prov:wasAssociatedWith>
- <prov:activity prov:ref="a"/>
- <prov:agent prov:ref="ag1"/>
+ <prov:activity prov:ref="ex:a"/>
+ <prov:agent prov:ref="ex:ag1"/>
<prov:role xsi:type="xsd:QName">loggedInUser</prov:role>
<ex:how>webapp</ex:how>
</prov:wasAssociatedWith>
<prov:wasAssociatedWith>
- <prov:activity prov:ref="a"/>
- <prov:agent prov:ref="ag2"/>
+ <prov:activity prov:ref="ex:a"/>
+ <prov:agent prov:ref="ex:ag2"/>
<prov:plan prov:ref="ex:wf"/>
<prov:role xsi:type="xsd:QName">designer</prov:role>
<ex:content>project1</ex:content>
@@ -1632,8 +1642,8 @@
<section id="term-Delegation">
<h4><span class="secno">3.3.4 </span>Delegation</h4>
-<span class="glossary-ref"> <span class="dfn">Delegation</span> is the assignment of authority and responsibility to an agent (by itself or by another agent) to carry out a specific activity as a delegate or representative, while the agent it acts on behalf of retains some responsibility for the outcome of the delegated work. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Delegation">
+<p>From [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>]:</p><blockquote><i><span class="glossary-ref"> <span class="dfn">Delegation</span> is the assignment of authority and responsibility to an agent (by itself or by another agent) to carry out a specific activity as a delegate or representative, while the agent it acts on behalf of retains some responsibility for the outcome of the delegated work. </span></i></blockquote>
+<p>ComplexType definition (denoting a similarly named prov-"type") in XML Schema:</p><pre class="schema-type"><xs:complexType name="Delegation">
<xs:sequence>
<xs:element name="delegate" type="prov:IDRef"/>
<xs:element name="responsible" type="prov:IDRef"/>
@@ -1646,56 +1656,57 @@
<xs:attribute ref="prov:id"/>
</xs:complexType>
</pre>
-<p>The element <code>prov:actedOnBehalfOf</code> is used to reference a prov:Delegation from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="actedOnBehalfOf" type="prov:Delegation"/>
+<p>The xml-element <code>prov:actedOnBehalfOf</code> is used to denote a prov:Delegation prov-"type" from within a prov:Document or prov:BundleConstructor.</p><p>XML Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="actedOnBehalfOf" type="prov:Delegation"/>
</pre>
<div class="example"><div class="example-title"><span>Example 25</span>: prov:actedOnBehalfOf</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
- xmlns:prov="http://www.w3.org/ns/prov#">
+ xmlns:prov="http://www.w3.org/ns/prov#"
+ xmlns:ex="http://example.com/ns/ex#">
- <prov:activity prov:id="a">
+ <prov:activity prov:id="ex:a">
<prov:type xsi:type="xsd:QName">workflow</prov:type>
</prov:activity>
- <prov:agent prov:id="ag1">
+ <prov:agent prov:id="ex:ag1">
<prov:type xsi:type="xsd:QName">programmer</prov:type>
</prov:agent>
- <prov:agent prov:id="ag2">
+ <prov:agent prov:id="ex:ag2">
<prov:type xsi:type="xsd:QName">researcher</prov:type>
</prov:agent>
- <prov:agent prov:id="ag3">
+ <prov:agent prov:id="ex:ag3">
<prov:type xsi:type="xsd:QName">funder</prov:type>
</prov:agent>
<prov:wasAssociatedWith>
- <prov:activity prov:ref="a"/>
- <prov:agent prov:ref="ag1"/>
+ <prov:activity prov:ref="ex:a"/>
+ <prov:agent prov:ref="ex:ag1"/>
<prov:role xsi:type="xsd:QName">loggedInUser</prov:role>
</prov:wasAssociatedWith>
<prov:wasAssociatedWith>
- <prov:activity prov:ref="a"/>
- <prov:agent prov:ref="ag2"/>
+ <prov:activity prov:ref="ex:a"/>
+ <prov:agent prov:ref="ex:ag2"/>
</prov:wasAssociatedWith>
<prov:wasAssociatedWith>
- <prov:activity prov:ref="a"/>
- <prov:agent prov:ref="ag3"/>
+ <prov:activity prov:ref="ex:a"/>
+ <prov:agent prov:ref="ex:ag3"/>
</prov:wasAssociatedWith>
<b><prov:actedOnBehalfOf>
- <prov:delegate prov:ref="ag1"/>
- <prov:responsible prov:ref="ag2"/>
- <prov:activity prov:ref="a"/>
+ <prov:delegate prov:ref="ex:ag1"/>
+ <prov:responsible prov:ref="ex:ag2"/>
+ <prov:activity prov:ref="ex:a"/>
<prov:type xsi:type="xsd:QName">line-management</prov:type>
</prov:actedOnBehalfOf></b>
<b><prov:actedOnBehalfOf>
- <prov:delegate prov:ref="ag2"/>
- <prov:responsible prov:ref="ag3"/>
- <prov:activity prov:ref="a"/>
+ <prov:delegate prov:ref="ex:ag2"/>
+ <prov:responsible prov:ref="ex:ag3"/>
+ <prov:activity prov:ref="ex:a"/>
<prov:type xsi:type="xsd:QName">contract</prov:type>
</prov:actedOnBehalfOf></b>
@@ -1704,8 +1715,8 @@
<section id="term-Influence">
<h4><span class="secno">3.3.5 </span>Influence</h4>
-<span class="glossary-ref"> <span class="dfn">Influence</span> is the capacity of an entity, activity, or agent to have an effect on the character, development, or behavior of another by means of usage, start, end, generation, invalidation, communication, derivation, attribution, association, or delegation. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Influence">
+<p>From [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>]:</p><blockquote><i><span class="glossary-ref"> <span class="dfn">Influence</span> is the capacity of an entity, activity, or agent to have an effect on the character, development, or behavior of another by means of usage, start, end, generation, invalidation, communication, derivation, attribution, association, or delegation. </span></i></blockquote>
+<p>ComplexType definition (denoting a similarly named prov-"type") in XML Schema:</p><pre class="schema-type"><xs:complexType name="Influence">
<xs:sequence>
<xs:element name="influencee" type="prov:IDRef"/>
<xs:element name="influencer" type="prov:IDRef"/>
@@ -1717,7 +1728,7 @@
<xs:attribute ref="prov:id"/>
</xs:complexType>
</pre>
-<p>The element <code>prov:wasInfluencedBy</code> is used to reference a prov:Influence from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasInfluencedBy" type="prov:Influence"/>
+<p>The xml-element <code>prov:wasInfluencedBy</code> is used to denote a prov:Influence prov-"type" from within a prov:Document or prov:BundleConstructor.</p><p>XML Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasInfluencedBy" type="prov:Influence"/>
</pre>
<div class="example"><div class="example-title"><span>Example 26</span>: prov:wasInfluencedBy</div><pre class="example" id="example_38"><prov:document
xmlns:prov="http://www.w3.org/ns/prov#"
@@ -1743,16 +1754,16 @@
<p>The fourth component is concerned with bundles, a mechanism to support provenance of provenance.</p>
<section id="term-Bundle">
<h4><span class="secno">3.4.1 </span>Bundle</h4>
-<span class="glossary-ref"> A <span class="dfn">bundle</span> is a named set of provenance descriptions, and is itself an entity, so allowing provenance of provenance to be expressed. </span>
-<p>A <code>prov:Bundle</code> identifies a set of provenance descriptions, and is an extension of <code>prov:Entity</code>, so allowing provenance of provenance to be expressed by referencing the associated entity. The content of a bundle, i.e. its provenance records, can be represented by the <code>prov:BundleConstructor</code> complexType and can be specified with the <code>prov:bundleContent</code> element, its <code>prov:id</code> corresponds to the bundle entity.</p>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Bundle">
+<p>From [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>]:</p><blockquote><i><span class="glossary-ref"> A <span class="dfn">bundle</span> is a named set of provenance descriptions, and is itself an entity, so allowing provenance of provenance to be expressed. </span></i></blockquote>
+<p>A <code>prov:Bundle</code> identifies a set of provenance descriptions, and is an extension of <code>prov:Entity</code>, so allowing provenance of provenance to be expressed by referencing the associated entity. The content of a bundle, i.e. its provenance records, can be represented by the <code>prov:BundleConstructor</code> ComplexType and is denoted with the <code>prov:bundleContent</code> xml-element, its <code>prov:id</code> corresponds to the bundle entity.</p>
+<p>ComplexType definition (denoting a similarly named prov-"type") in XML Schema:</p><pre class="schema-type"><xs:complexType name="Bundle">
<xs:complexContent>
<xs:extension base="prov:Entity">
</xs:extension>
</xs:complexContent>
</xs:complexType>
</pre>
-<p>The element <code>prov:bundle</code> is used to reference a prov:Bundle from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="bundle" type="prov:Bundle"/>
+<p>The xml-element <code>prov:bundle</code> is used to denote a prov:Bundle prov-"type" from within a prov:Document or prov:BundleConstructor.</p><p>XML Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="bundle" type="prov:Bundle"/>
</pre>
<div class="example"><div class="example-title"><span>Example 27</span>: prov:bundle</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -1791,22 +1802,22 @@
<section id="term-BundleConstructor">
<h4><span class="secno">3.4.2 </span>Bundle Constructor</h4>
-<p>The <code>prov:BundleConstructor</code> complexType is used to define a named set of provenance statements. The Bundle Constructor type supports the <code>prov:id</code> attribute.</p>
+<p>The <code>prov:BundleConstructor</code> ComplexType is used to define a named set of provenance statements. The Bundle Constructor supports the <code>prov:id</code> xml-attribute.</p>
<p>The bundle entity associated with a bundle constructor set must have the same <code>prov:id</code> as the bundle constructor set.</p>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="BundleConstructor">
- <xs:sequence maxOccurs="unbounded">
+<p>ComplexType definition (denoting a similarly named prov-"type") in XML Schema:</p><pre class="schema-type"><xs:complexType name="BundleConstructor">
+ <xs:choice minOccurs="0" maxOccurs="unbounded">
<-- references to standard non-PROV attribute PROV elements -->
- </xs:sequence>
+ </xs:choice>
<xs:attribute ref="prov:id"/>
</xs:complexType>
</pre>
-<p>The element <code>prov:bundleContent</code> is used to reference a set of nested provenance statements from within a prov:Document.</p>
-<p>Although <code>prov:bundleContent</code> can only be expressed at the <code>prov:document</code> level, the corresponding bundle entities may be specified at from either the <code>prov:document</code> or any <code>prov:bundleContent</code>, if at all.</p>
+<p>The xml-element <code>prov:bundleContent</code> is used to denote a set of nested provenance statements from within a prov:Document.</p>
+<p>Although <code>prov:bundleContent</code> can only be expressed at the <code>prov:document</code> level, the corresponding bundle entities may be specified from either the <code>prov:document</code> or any <code>prov:bundleContent</code>.</p>
<pre><xs:complexType name="Document">
- <xs:sequence maxOccurs="unbounded">
+ <xs:choice minOccurs="0" maxOccurs="unbounded">
<!-- references to standard non-PROV attribute PROV elements -->
<xs:element name="bundleContent" type="prov:BundleConstructor" minOccurs="0"/>
- </xs:sequence>
+ </xs:choice>
</xs:complexType>
</pre>
<div class="example"><div class="example-title"><span>Example 28</span>: prov:bundleContent</div><pre class="example"><prov:document
@@ -1847,20 +1858,20 @@
<section id="component5">
<h3><span class="secno">3.5 </span>Component 5: Alternate Entities</h3>
-<p>The fifth component of PROV-DM is concerned with
-relations SpecializationOf (<a href="#term-Specialization">Specialization</a>) and AlternateOf (<a href="#term-Alternate">Alternate</a>) between entities.</p>
+<p>The fifth component of PROV-DM is concerned with the
+relations <a href="#term-Specialization">Specialization</a> and <a href="#term-Alternate">Alternate</a>, relating entities to entities.</p>
<section id="term-Specialization">
<h4><span class="secno">3.5.1 </span>Specialization</h4>
-<span class="glossary-ref"> An entity that is a <span class="dfn">specialization</span> of another shares all aspects of the latter, and additionally presents more specific aspects of the same thing as the latter. In particular, the lifetime of the entity being specialized contains that of any specialization. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Specialization">
+<p>From [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>]:</p><blockquote><i><span class="glossary-ref"> An entity that is a <span class="dfn">specialization</span> of another shares all aspects of the latter, and additionally presents more specific aspects of the same thing as the latter. In particular, the lifetime of the entity being specialized contains that of any specialization. </span></i></blockquote>
+<p>ComplexType definition (denoting a similarly named prov-"type") in XML Schema:</p><pre class="schema-type"><xs:complexType name="Specialization">
<xs:sequence>
<xs:element name="specificEntity" type="prov:IDRef"/>
<xs:element name="generalEntity" type="prov:IDRef"/>
</xs:sequence>
</xs:complexType>
</pre>
-<p>The element <code>prov:specializationOf</code> is used to reference a prov:Specialization from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="specializationOf" type="prov:Specialization"/>
+<p>The xml-element <code>prov:specializationOf</code> is used to denote a prov:Specialization prov-"type" from within a prov:Document or prov:BundleConstructor.</p><p>XML Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="specializationOf" type="prov:Specialization"/>
</pre>
<div class="example"><div class="example-title"><span>Example 29</span>: prov:specializationOf</div><pre class="example"><prov:document
xmlns:prov="http://www.w3.org/ns/prov#"
@@ -1881,15 +1892,15 @@
<section id="term-Alternate">
<h4><span class="secno">3.5.2 </span>Alternate</h4>
-<span class="glossary-ref"> Two <span class="dfn">alternate</span> entities present aspects of the same thing. These aspects may be the same or different, and the alternate entities may or may not overlap in time. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Alternate">
+<p>From [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>]:</p><blockquote><i><span class="glossary-ref"> Two <span class="dfn">alternate</span> entities present aspects of the same thing. These aspects may be the same or different, and the alternate entities may or may not overlap in time. </span></i></blockquote>
+<p>ComplexType definition (denoting a similarly named prov-"type") in XML Schema:</p><pre class="schema-type"><xs:complexType name="Alternate">
<xs:sequence>
<xs:element name="alternate1" type="prov:IDRef"/>
<xs:element name="alternate2" type="prov:IDRef"/>
</xs:sequence>
</xs:complexType>
</pre>
-<p>The element <code>prov:alternateOf</code> is used to reference a prov:Alternate from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="alternateOf" type="prov:Alternate"/>
+<p>The xml-element <code>prov:alternateOf</code> is used to denote a prov:Alternate prov-"type" from within a prov:Document or prov:BundleConstructor.</p><p>XML Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="alternateOf" type="prov:Alternate"/>
</pre>
<div class="example"><div class="example-title"><span>Example 30</span>: prov:alternateOf</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -1924,15 +1935,15 @@
<section id="term-Collection">
<h4><span class="secno">3.6.1 </span>Collection</h4>
-<span class="glossary-ref"> A <span class="dfn">collection</span> is an entity that provides a structure to some constituents that must themselves be entities. These constituents are said to be <span class="dfn">member</span> of the collections. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Collection">
+<p>From [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>]:</p><blockquote><i><span class="glossary-ref"> A <span class="dfn">collection</span> is an entity that provides a structure to some constituents that must themselves be entities. These constituents are said to be <span class="dfn">member</span> of the collections. </span></i></blockquote>
+<p>ComplexType definition (denoting a similarly named prov-"type") in XML Schema:</p><pre class="schema-type"><xs:complexType name="Collection">
<xs:complexContent>
<xs:extension base="prov:Entity">
</xs:extension>
</xs:complexContent>
</xs:complexType>
</pre>
-<p>The element <code>prov:collection</code> is used to reference a prov:Collection from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="collection" type="prov:Collection"/>
+<p>The xml-element <code>prov:collection</code> is used to denote a prov:Collection prov-"type" from within a prov:Document or prov:BundleConstructor.</p><p>XML Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="collection" type="prov:Collection"/>
</pre>
<div class="example"><div class="example-title"><span>Example 31</span>: prov:collection</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -1940,21 +1951,21 @@
xmlns:prov="http://www.w3.org/ns/prov#"
xmlns:ex="http://example.com/ns/ex#">
- <b><prov:collection prov:id="c1" /></b>
+ <b><prov:collection prov:id="ex:c1" /></b>
</prov:document></pre></div>
<section id="term-EmptyCollection">
<h5><span class="secno">3.6.1.1 </span>Empty Collection</h5>
-<span class="glossary-ref"> An <span class="dfn">empty collection</span> is a collection without members. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="EmptyCollection">
+<p>From [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>]:</p><blockquote><i><span class="glossary-ref"> An <span class="dfn">empty collection</span> is a collection without members. </span></i></blockquote>
+<p>ComplexType definition (denoting a similarly named prov-"type") in XML Schema:</p><pre class="schema-type"><xs:complexType name="EmptyCollection">
<xs:complexContent>
<xs:extension base="prov:Collection">
</xs:extension>
</xs:complexContent>
</xs:complexType>
</pre>
-<p>The element <code>prov:emptyCollection</code> is used to reference a prov:EmptyCollection from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="emptyCollection" type="prov:EmptyCollection"/>
+<p>The xml-element <code>prov:emptyCollection</code> is used to denote a prov:EmptyCollection prov-"type" from within a prov:Document or prov:BundleConstructor.</p><p>XML Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="emptyCollection" type="prov:EmptyCollection"/>
</pre>
<div class="example"><div class="example-title"><span>Example 32</span>: prov:emptyCollection</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -1963,7 +1974,7 @@
xmlns:bbc="http://www.bbc.co.uk/news"
xmlns:bbcmobile="http://www.bbc.co.uk/news/mobile">
- <b><prov:emptyCollection prov:id="c0"/></b>
+ <b><prov:emptyCollection prov:id="ex:c0"/></b>
</prov:document></pre></div>
</section> <!-- end term-EmptyCollection -->
@@ -1971,32 +1982,33 @@
<section id="term-Membership">
<h4><span class="secno">3.6.2 </span>Membership</h4>
-<span class="glossary-ref"> <span class="dfn">Membership</span> is the belonging of an entity to a collection. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Membership">
+<p>From [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>]:</p><blockquote><i><span class="glossary-ref"> <span class="dfn">Membership</span> is the belonging of an entity to a collection. </span></i></blockquote>
+<p>ComplexType definition (denoting a similarly named prov-"type") in XML Schema:</p><pre class="schema-type"><xs:complexType name="Membership">
<xs:sequence>
<xs:element name="collection" type="prov:IDRef"/>
<xs:element name="entity" type="prov:IDRef" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</pre>
-<p>The element <code>prov:hadMember</code> is used to reference a prov:Membership from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="hadMember" type="prov:Membership"/>
+<p>The xml-element <code>prov:hadMember</code> is used to denote a prov:Membership prov-"type" from within a prov:Document or prov:BundleConstructor.</p><p>XML Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="hadMember" type="prov:Membership"/>
</pre>
<div class="example"><div class="example-title"><span>Example 33</span>: prov:hadMember</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
- xmlns:prov="http://www.w3.org/ns/prov#">
+ xmlns:prov="http://www.w3.org/ns/prov#"
+ xmlns:ex="http://example.com/ns/ex#">
- <prov:entity prov:id="e0"/>
- <prov:entity prov:id="e1"/>
- <prov:entity prov:id="e2"/>
+ <prov:entity prov:id="ex:e0"/>
+ <prov:entity prov:id="ex:e1"/>
+ <prov:entity prov:id="ex:e2"/>
- <prov:collection prov:id="c"/>
+ <prov:collection prov:id="ex:c"/>
<b><prov:hadMember>
- <prov:collection prov:ref="c"/>
- <prov:entity prov:ref="e0"/>
- <prov:entity prov:ref="e1"/>
- <prov:entity prov:ref="e2"/>
+ <prov:collection prov:ref="ex:c"/>
+ <prov:entity prov:ref="ex:e0"/>
+ <prov:entity prov:ref="ex:e1"/>
+ <prov:entity prov:ref="ex:e2"/>
</prov:hadMember></b>
</prov:document></pre></div>
@@ -2011,8 +2023,8 @@
<section id="attribute-Identifier">
<h4><span class="secno">3.7.1 </span>Identifier</h4>
-<span class="glossary-ref"></span>
-<p>The identifier attribute is used to identify instances of PROV types or relations.</p>
+<p>From [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>]:</p><blockquote><i><span class="glossary-ref"></span></i></blockquote>
+<p>The xml-attribute used to identify an instances of a prov-"type" or prov-"relation".</p>
<pre class="schema-attribute"><xs:attribute xmlns:xs="http://www.w3.org/2001/XMLSchema" name="id" type="xs:QName"/>
</pre>
<div class="example"><div class="example-title"><span>Example 34</span>: prov:id</div><pre class="example"><prov:document
@@ -2032,21 +2044,21 @@
<section id="attribute-Reference">
<h4><span class="secno">3.7.2 </span>Reference</h4>
-<span class="glossary-ref"></span>
-<p>A reference-by-id to a PROV entity, activity, agent, or relation.</p>
+<p>From [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>]:</p><blockquote><i><span class="glossary-ref"></span></i></blockquote>
+<p>A xml-attribute that denotes a reference-by-id to an instance of a prov-"type" or prov-"relation".</p>
<pre class="schema-attribute"><xs:attribute ref="prov:ref" use="required" />
</pre>
<div class="example"><div class="example-title"><span>Example 35</span>: prov:ref</div><pre class="example"><prov:document
xmlns:prov="http://www.w3.org/ns/prov#"
xmlns:ex="http://example.com/ns/ex#">
- <prov:entity prov:id="e1"/>
+ <prov:entity prov:id="ex:e1"/>
- <prov:activity prov:id="a1"/>
+ <prov:activity prov:id="ex:a1"/>
<prov:wasGeneratedBy>
- <prov:entity <b>prov:ref="e1"</b>/>
- <prov:activity <b>prov:ref="a1"</b>/>
+ <prov:entity <b>prov:ref="ex:e1"</b>/>
+ <prov:activity <b>prov:ref="ex:a1"</b>/>
<prov:time>2001-10-26T21:32:52</prov:time>
<ex:port>p1</ex:port>
</prov:wasGeneratedBy>
@@ -2056,12 +2068,12 @@
<section id="attributes">
<h4><span class="secno">3.7.3 </span>Attributes</h4>
-<p>The PROV-DM defined PROV attributes are represented in XML as elements.</p>
+<p>The PROV-DM defined prov-"attributes" are represented in XML as xml-elements.</p>
<section id="element-Label">
<h5><span class="secno">3.7.3.1 </span>Label</h5>
-<span class="glossary-ref"> The attribute <span class="dfn"><span class="name">prov:label</span></span> provides a human-readable representation of an instance of a PROV-DM type or relation. </span>
-<p>The element <code>prov:label</code> is used to represent a PROV label attribute and has type prov:InternationalizedString.</p><p>Element definition in XML Schema:</p><pre class="prov-attribute"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="label" type="prov:InternationalizedString"/>
+<p>From [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>]:</p><blockquote><i><span class="glossary-ref"> The attribute <span class="dfn"><span class="name">prov:label</span></span> provides a human-readable representation of an instance of a PROV-DM type or relation. </span></i></blockquote>
+<p>The xml-element <code>prov:label</code> is used to denote a label prov-"attribute" and has prov-"type" prov:InternationalizedString.</p><p>XML Element definition in XML Schema:</p><pre class="prov-attribute"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="label" type="prov:InternationalizedString"/>
</pre>
<div class="example"><div class="example-title"><span>Example 36</span>: prov:label</div><pre class="example"><prov:document
xmlns:prov="http://www.w3.org/ns/prov#"
@@ -2081,8 +2093,8 @@
<section id="element-Location">
<h5><span class="secno">3.7.3.2 </span>Location</h5>
-<span class="glossary-ref"> A <span class="dfn">location</span> can be an identifiable geographic place (ISO 19112), but it can also be a non-geographic place such as a directory, row, or column. </span>
-<p>The element <code>prov:location</code> is used to represent a PROV location attribute and has type xs:anySimpleType.</p><p>Element definition in XML Schema:</p><pre class="prov-attribute"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="location" type="xs:anySimpleType"/>
+<p>From [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>]:</p><blockquote><i><span class="glossary-ref"> A <span class="dfn">location</span> can be an identifiable geographic place (ISO 19112), but it can also be a non-geographic place such as a directory, row, or column. </span></i></blockquote>
+<p>The xml-element <code>prov:location</code> is used to denote a location prov-"attribute" and has prov-"type" xs:anySimpleType.</p><p>XML Element definition in XML Schema:</p><pre class="prov-attribute"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="location" type="xs:anySimpleType"/>
</pre>
<div class="example"><div class="example-title"><span>Example 37</span>: prov:location</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -2105,8 +2117,8 @@
<section id="element-Role">
<h5><span class="secno">3.7.3.3 </span>Role</h5>
-<span class="glossary-ref"> A <span class="dfn">role</span> is the function of an entity or agent with respect to an activity, in the context of a <a title="Usage">usage</a>, <a title="Generation">generation</a>, <a title="Invalidation">invalidation</a>, <a title="Association">association</a>, <a title="Start">start</a>, and <a title="End">end</a>. </span>
-<p>The element <code>prov:role</code> is used to represent a PROV Role attribute and has type xs:anySimpleType.</p><p>Element definition in XML Schema:</p><pre class="prov-attribute"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="role" type="xs:anySimpleType"/>
+<p>From [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>]:</p><blockquote><i><span class="glossary-ref"> A <span class="dfn">role</span> is the function of an entity or agent with respect to an activity, in the context of a <a title="Usage">usage</a>, <a title="Generation">generation</a>, <a title="Invalidation">invalidation</a>, <a title="Association">association</a>, <a title="Start">start</a>, and <a title="End">end</a>. </span></i></blockquote>
+<p>The xml-element <code>prov:role</code> is used to denote a Role prov-"attribute" and has prov-"type" xs:anySimpleType.</p><p>XML Element definition in XML Schema:</p><pre class="prov-attribute"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="role" type="xs:anySimpleType"/>
</pre>
<div class="example"><div class="example-title"><span>Example 38</span>: prov:role</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -2115,15 +2127,15 @@
xmlns:ex="http://example.com/ns/ex#">
<prov:wasAssociatedWith>
- <prov:activity prov:ref="a"/>
- <prov:agent prov:ref="ag1"/>
+ <prov:activity prov:ref="ex:a"/>
+ <prov:agent prov:ref="ex:ag1"/>
<b><prov:role xsi:type="xsd:QName">loggedInUser</prov:role></b>
<ex:how>webapp</ex:how>
</prov:wasAssociatedWith>
<prov:wasAssociatedWith>
- <prov:activity prov:ref="a"/>
- <prov:agent prov:ref="ag2"/>
+ <prov:activity prov:ref="ex:a"/>
+ <prov:agent prov:ref="ex:ag2"/>
<prov:plan prov:ref="ex:wf"/>
<b><prov:role xsi:type="xsd:QName">designer</prov:role></b>
<ex:content>project1</ex:content>
@@ -2134,8 +2146,8 @@
<section id="element-Type">
<h5><span class="secno">3.7.3.4 </span>Type</h5>
-<span class="glossary-ref"> The attribute <span class="dfn"><span class="name">prov:type</span></span> provides further typing information for any construct with an optional set of attribute-value pairs. </span>
-<p>The element <code>prov:type</code> is used to represent a PROV Type attribute and has type xs:anySimpleType.</p><p>Element definition in XML Schema:</p><pre class="prov-attribute"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="type" type="xs:anySimpleType"/>
+<p>From [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>]:</p><blockquote><i><span class="glossary-ref"> The attribute <span class="dfn"><span class="name">prov:type</span></span> provides further typing information for any construct with an optional set of attribute-value pairs. </span></i></blockquote>
+<p>The xml-element <code>prov:type</code> is used to denote a Type prov-"attribute" and has prov-"type" xs:anySimpleType.</p><p>XML Element definition in XML Schema:</p><pre class="prov-attribute"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="type" type="xs:anySimpleType"/>
</pre>
<div class="example"><div class="example-title"><span>Example 39</span>: prov:type</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -2149,13 +2161,13 @@
<ex:version>2</ex:version>
</prov:entity>
- <prov:agent prov:id="e1">
+ <prov:agent prov:id="ex:e1">
<b><prov:type xsi:type="xsd:QName">prov:Person</prov:type></b>
<ex:name>Alice</ex:name>
<ex:employee>1234</ex:employee>
</prov:agent>
- <prov:activity prov:id="a1">
+ <prov:activity prov:id="ex:a1">
<prov:startTime>2011-11-16T16:05:00</prov:startTime>
<prov:endTime>2011-11-16T16:06:00</prov:endTime>
<b><prov:type xsi:type="xsd:QName">ex:edit</prov:type></b>
@@ -2167,8 +2179,8 @@
<section id="element-Value">
<h5><span class="secno">3.7.3.5 </span>Value</h5>
-<span class="glossary-ref"> The attribute <span class="dfn"><span class="name">prov:value</span></span> provides a value that is a direct representation of an entity as a PROV-DM <a title="value">Value</a>. </span>
-<p>The element <code>prov:value</code> is used to represent a PROV Value attribute and has type xs:anySimpleType.</p><p>Element definition in XML Schema:</p><pre class="prov-attribute"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="value" type="xs:anySimpleType"/>
+<p>From [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>]:</p><blockquote><i><span class="glossary-ref"> The attribute <span class="dfn"><span class="name">prov:value</span></span> provides a value that is a direct representation of an entity as a PROV-DM <a title="value">Value</a>. </span></i></blockquote>
+<p>The xml-element <code>prov:value</code> is used to denote a Value prov-"attribute" and has prov-"type" xs:anySimpleType.</p><p>XML Element definition in XML Schema:</p><pre class="prov-attribute"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="value" type="xs:anySimpleType"/>
</pre>
<div class="example"><div class="example-title"><span>Example 40</span>: prov:value</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -2191,8 +2203,8 @@
<section id="type-value">
<h4><span class="secno">3.7.4 </span>Value</h4>
-<span class="glossary-ref"> A <span class="dfn">value</span> is a constant such as a string, number, time, qualified name, IRI, and encoded binary data, whose interpretation is outside the scope of PROV. </span>
-<p>Relations defined by the PROV-DM to have type Value have type <code>xs:anySimpleType</code> in PROV-XML unless otherwise specified.</p>
+<p>From [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>]:</p><blockquote><i><span class="glossary-ref"> A <span class="dfn">value</span> is a constant such as a string, number, time, qualified name, IRI, and encoded binary data, whose interpretation is outside the scope of PROV. </span></i></blockquote>
+<p>Relations defined by the PROV-DM to have prov-"type" Value have type <code>xs:anySimpleType</code> in PROV-XML unless otherwise specified.</p>
</section> <!-- end type-Value -->
</section> <!-- end further-elements -->
@@ -2202,23 +2214,23 @@
<section id="term-Document">
<h4><span class="secno">3.8.1 </span>Document</h4>
-<p>The root element of all PROV-XML documents is <code>prov:document</code> which has type <code>prov:Document</code>.</p>
+<p>The root xml-element of all PROV-XML documents is <code>prov:document</code> which has xml-type <code>prov:Document</code>.</p>
<p>Similar to a <code>prov:BundleConstructor</code>, the <code>prov:Document</code> complexType is used to define a set of provenance statements.</p>
<p>Unlike the <code>prov:BundleConstructor</code>, a <code>prov:Document</code>
</p><ul>
-<li>may contain <code>prov:bundle</code> elements (but not other <code>prov:document</code> elements)</li>
-<li>does not support the prov:id attribute.</li>
+<li>may contain <code>prov:bundle</code> xml-elements (but not other <code>prov:document</code> xml-elements)</li>
+<li>does not support the prov:id xml-attribute.</li>
</ul>
<p></p>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Document">
- <xs:sequence maxOccurs="unbounded">
+<p>ComplexType definition (denoting a similarly named prov-"type") in XML Schema:</p><pre class="schema-type"><xs:complexType name="Document">
+ <xs:choice minOccurs="0" maxOccurs="unbounded">
<!-- references to standard non-PROV attribute PROV elements -->
<xs:element name="bundleContent" type="prov:BundleConstructor" minOccurs="0"/>
- </xs:sequence>
+ </xs:choice>
</xs:complexType>
</pre>
-<p>The element <code>prov:document</code> may only be used as the root element of a a PROV-XML document.</p>
+<p>The xml-element <code>prov:document</code> may only be used as the root xml-element of a a PROV-XML document.</p>
<pre><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="document" type="prov:Document"/>
</pre>
<div class="example"><div class="example-title"><span>Example 41</span>: prov:document</div><pre class="example"><b><prov:document
@@ -2234,14 +2246,14 @@
<section id="term-Other">
<h4><span class="secno">3.8.2 </span>Other</h4>
-<p>The <code>prov:other</code> element provides a place to include non-PROV XML elements inside a <code>prov:document</code> or <code>prov:bundleContent</code>.</p>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Other">
+<p>The <code>prov:other</code> xml-element provides a place to include non-PROV xml-elements inside a <code>prov:document</code> or <code>prov:bundleContent</code>.</p>
+<p>ComplexType definition (denoting a similarly named prov-"type") in XML Schema:</p><pre class="schema-type"><xs:complexType name="Other">
<xs:sequence>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</pre>
-<p>The element <code>prov:other</code> may be used in a <code>prov:document</code> or a <code>prov:bundleContent</code> but may not be used inside a relation, entity, or activity element.</p>
+<p>The xml-element <code>prov:other</code> may be used in a <code>prov:document</code> or a <code>prov:bundleContent</code> but may not be used inside a prov-"relation", entity, or activity xml-element.</p>
<pre><xs:element name="other" type="prov:Other"/>
</pre>
<div class="example"><div class="example-title"><span>Example 42</span>: prov:other</div><pre class="example"><prov:document
@@ -2349,535 +2361,26 @@
<!--OddPage--><h2><span class="secno">A. </span>XML Schema</h2>
<section id="prov-schema">
-<h3><span class="secno">A.1 </span>prov.xsd</h3>
-<pre class="prov-schema"><?xml version="1.0" encoding="utf-8"?>
-<xs:schema targetNamespace="http://www.w3.org/ns/prov#"
- xmlns:xs="http://www.w3.org/2001/XMLSchema"
- xmlns:prov="http://www.w3.org/ns/prov#"
- elementFormDefault="qualified"
- attributeFormDefault="unqualified">
-
- <xs:include schemaLocation="prov-core.xsd"/>
- <xs:include schemaLocation="prov-dictionary.xsd"/>
- <xs:include schemaLocation="prov-links.xsd"/>
-
-</xs:schema>
-</pre>
+<h3><span class="secno">A.1 </span>Main Schema</h3>
+<p>The main PROV schema is an aggregation of the PROV core schema and all PROV-defined extension schemas.</p>
+<p>The main PROV schema is available at <a href="http://www.w3.org/ns/prov.xsd">http://www.w3.org/ns/prov.xsd</a></p>
</section> <!-- end prov-schema -->
<section id="prov-core-schema">
-<h3><span class="secno">A.2 </span>prov-core.xsd</h3>
-<pre class="prov-core-schema"><?xml version="1.0" encoding="utf-8"?>
-
-<!--
- In PROV-DM, all ids are qualified names, specified as prov:QualifiedName in PROV-N.
- In this schema, all ids are instead defined as xsd:QNames.
- -->
-
-
-<xs:schema targetNamespace="http://www.w3.org/ns/prov#"
- xmlns:xs="http://www.w3.org/2001/XMLSchema"
- xmlns:prov="http://www.w3.org/ns/prov#"
- xmlns:cu="http://www.w3.org/1999/xhtml/datatypes/"
- xmlns:xml="http://www.w3.org/XML/1998/namespace"
- elementFormDefault="qualified"
- attributeFormDefault="unqualified">
-
-
-
- <xs:import namespace="http://www.w3.org/1999/xhtml/datatypes/" />
- <xs:import namespace="http://www.w3.org/XML/1998/namespace"
- schemaLocation="http://www.w3.org/2001/xml.xsd"/>
-
- <!-- Component 1 -->
-
- <xs:complexType name="Entity">
- <xs:sequence>
- <!-- prov attributes -->
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:location" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:value" minOccurs="0"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <xs:complexType name="Activity">
- <xs:sequence>
- <xs:element name="startTime" type="xs:dateTime" minOccurs="0"/>
- <xs:element name="endTime" type="xs:dateTime" minOccurs="0"/>
- <!-- prov attributes -->
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:location" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <xs:complexType name="Generation">
- <xs:sequence>
- <xs:element name="entity" type="prov:IDRef"/>
- <xs:element name="activity" type="prov:IDRef" minOccurs="0"/>
- <xs:element name="time" type="xs:dateTime" minOccurs="0"/>
- <!-- prov attributes -->
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:location" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:role" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <xs:complexType name="Usage">
- <xs:sequence>
- <xs:element name="activity" type="prov:IDRef"/>
- <xs:element name="entity" type="prov:IDRef" minOccurs="0"/>
- <xs:element name="time" type="xs:dateTime" minOccurs="0"/>
- <!-- prov attributes -->
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:location" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:role" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <xs:complexType name="Communication">
- <xs:sequence>
- <xs:element name="informed" type="prov:IDRef"/>
- <xs:element name="informant" type="prov:IDRef"/>
- <!-- prov attributes -->
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <xs:complexType name="Start">
- <xs:sequence>
- <xs:element name="activity" type="prov:IDRef"/>
- <xs:element name="trigger" type="prov:IDRef" minOccurs="0"/>
- <xs:element name="starter" type="prov:IDRef" minOccurs="0"/>
- <xs:element name="time" type="xs:dateTime" minOccurs="0"/>
- <!-- prov attributes -->
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:location" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:role" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <xs:complexType name="End">
- <xs:sequence>
- <xs:element name="activity" type="prov:IDRef"/>
- <xs:element name="trigger" type="prov:IDRef" minOccurs="0"/>
- <xs:element name="ender" type="prov:IDRef" minOccurs="0"/>
- <xs:element name="time" type="xs:dateTime" minOccurs="0"/>
- <!-- prov attributes -->
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:location" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:role" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <xs:complexType name="Invalidation">
- <xs:sequence>
- <xs:element name="entity" type="prov:IDRef"/>
- <xs:element name="activity" type="prov:IDRef" minOccurs="0"/>
- <xs:element name="time" type="xs:dateTime" minOccurs="0"/>
- <!-- prov attributes -->
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:location" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:role" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <!-- Component 2 -->
-
- <xs:complexType name="Derivation">
- <xs:sequence>
- <xs:element name="generatedEntity" type="prov:IDRef"/>
- <xs:element name="usedEntity" type="prov:IDRef"/>
- <xs:element name="activity" type="prov:IDRef" minOccurs="0"/>
- <xs:element name="generation" type="prov:IDRef" minOccurs="0"/>
- <xs:element name="usage" type="prov:IDRef" minOccurs="0"/>
- <!-- prov attributes -->
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <xs:complexType name="Revision">
- <xs:complexContent>
- <xs:extension base="prov:Derivation">
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
-
- <xs:complexType name="Quotation">
- <xs:complexContent>
- <xs:extension base="prov:Derivation">
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
-
- <xs:complexType name="PrimarySource">
- <xs:complexContent>
- <xs:extension base="prov:Derivation">
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
-
- <!-- Component 3 -->
-
- <xs:complexType name="Agent">
- <xs:sequence>
- <!-- prov attributes -->
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:location" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <xs:complexType name="Person">
- <xs:complexContent>
- <xs:extension base="prov:Agent">
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
-
- <xs:complexType name="Organization">
- <xs:complexContent>
- <xs:extension base="prov:Agent">
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
-
- <xs:complexType name="SoftwareAgent">
- <xs:complexContent>
- <xs:extension base="prov:Agent">
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
-
- <xs:complexType name="Attribution">
- <xs:sequence>
- <xs:element name="entity" type="prov:IDRef"/>
- <xs:element name="agent" type="prov:IDRef"/>
- <!-- prov attributes -->
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <xs:complexType name="Association">
- <xs:sequence>
- <xs:element name="activity" type="prov:IDRef"/>
- <xs:element name="agent" type="prov:IDRef" minOccurs="0"/>
- <xs:element name="plan" type="prov:IDRef" minOccurs="0"/>
- <!-- prov attributes -->
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:role" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <xs:complexType name="Delegation">
- <xs:sequence>
- <xs:element name="delegate" type="prov:IDRef"/>
- <xs:element name="responsible" type="prov:IDRef"/>
- <xs:element name="activity" type="prov:IDRef" minOccurs="0"/>
- <!-- prov attributes -->
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <xs:complexType name="Influence">
- <xs:sequence>
- <xs:element name="influencee" type="prov:IDRef"/>
- <xs:element name="influencer" type="prov:IDRef"/>
- <!-- prov attributes -->
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <!-- Component 4 -->
-
- <xs:complexType name="Bundle">
- <xs:complexContent>
- <xs:extension base="prov:Entity">
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
-
- <!-- bundle container and allowable PROV elements -->
-
- <xs:complexType name="BundleConstructor">
- <xs:sequence maxOccurs="unbounded">
- <xs:element ref="prov:entity" minOccurs="0"/>
- <xs:element ref="prov:activity" minOccurs="0"/>
- <xs:element ref="prov:wasGeneratedBy" minOccurs="0"/>
- <xs:element ref="prov:used" minOccurs="0"/>
- <xs:element ref="prov:wasInformedBy" minOccurs="0"/>
- <xs:element ref="prov:wasStartedBy" minOccurs="0"/>
- <xs:element ref="prov:wasEndedBy" minOccurs="0"/>
- <xs:element ref="prov:wasInvalidatedBy" minOccurs="0"/>
- <xs:element ref="prov:wasDerivedFrom" minOccurs="0"/>
- <xs:element ref="prov:wasRevisionOf" minOccurs="0"/>
- <xs:element ref="prov:wasQuotedFrom" minOccurs="0"/>
- <xs:element ref="prov:hadPrimarySource" minOccurs="0"/>
- <xs:element ref="prov:agent" minOccurs="0"/>
- <xs:element ref="prov:person" minOccurs="0"/>
- <xs:element ref="prov:organization" minOccurs="0"/>
- <xs:element ref="prov:softwareAgent" minOccurs="0"/>
- <xs:element ref="prov:wasAttributedTo" minOccurs="0"/>
- <xs:element ref="prov:wasAssociatedWith" minOccurs="0"/>
- <xs:element ref="prov:actedOnBehalfOf" minOccurs="0"/>
- <xs:element ref="prov:wasInfluencedBy" minOccurs="0"/>
- <xs:element ref="prov:bundle" minOccurs="0"/>
- <xs:element ref="prov:specializationOf" minOccurs="0"/>
- <xs:element ref="prov:alternateOf" minOccurs="0"/>
- <xs:element ref="prov:collection" minOccurs="0"/>
- <xs:element ref="prov:emptyCollection" minOccurs="0"/>
- <xs:element ref="prov:hadMember" minOccurs="0"/>
- <xs:element ref="prov:plan" minOccurs="0"/>
- <xs:element ref="prov:other" minOccurs="0"/>
- <xs:element ref="prov:internalElement" minOccurs="0"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <!-- Component 5 -->
-
- <xs:complexType name="Specialization">
- <xs:sequence>
- <xs:element name="specificEntity" type="prov:IDRef"/>
- <xs:element name="generalEntity" type="prov:IDRef"/>
- </xs:sequence>
- </xs:complexType>
-
- <xs:complexType name="Alternate">
- <xs:sequence>
- <xs:element name="alternate1" type="prov:IDRef"/>
- <xs:element name="alternate2" type="prov:IDRef"/>
- </xs:sequence>
- </xs:complexType>
-
- <!-- Component 6 -->
-
- <xs:complexType name="Collection">
- <xs:complexContent>
- <xs:extension base="prov:Entity">
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
-
- <xs:complexType name="EmptyCollection">
- <xs:complexContent>
- <xs:extension base="prov:Collection">
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
-
- <xs:complexType name="Membership">
- <xs:sequence>
- <xs:element name="collection" type="prov:IDRef"/>
- <xs:element name="entity" type="prov:IDRef" maxOccurs="unbounded"/>
- </xs:sequence>
- </xs:complexType>
-
- <xs:complexType name="Plan">
- <xs:complexContent>
- <xs:extension base="prov:Entity">
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
-
- <xs:complexType name="InternationalizedString">
- <xs:simpleContent>
- <xs:extension base="xs:string">
- <xs:attribute ref="xml:lang" use="optional"/>
- </xs:extension>
- </xs:simpleContent>
- </xs:complexType>
-
-
- <!--
- Typed literals are encoded by means
- of xsi:type that represent the prov:datatype.
- -->
-
- <xs:element name="label" type="prov:InternationalizedString"/>
- <xs:element name="role" type="xs:anySimpleType"/>
- <xs:element name="type" type="xs:anySimpleType"/>
- <xs:element name="location" type="xs:anySimpleType"/>
- <xs:element name="value" type="xs:anySimpleType"/>
-
- <xs:attribute name="id" type="xs:QName"/>
- <xs:attribute name="ref" type="xs:QName"/>
-
- <xs:complexType name="IDRef">
- <xs:attribute ref="prov:ref" use="required" />
- </xs:complexType>
-
- <!--
- top-level definition of elements following the salami slice XSD design pattern
- to encourage integration within existing non-prov XML documents.
- -->
-
- <!-- Component 1 elements -->
-
- <xs:element name="entity" type="prov:Entity"/>
- <xs:element name="activity" type="prov:Activity"/>
- <xs:element name="wasGeneratedBy" type="prov:Generation"/>
- <xs:element name="used" type="prov:Usage"/>
- <xs:element name="wasInformedBy" type="prov:Communication"/>
- <xs:element name="wasStartedBy" type="prov:Start"/>
- <xs:element name="wasEndedBy" type="prov:End"/>
- <xs:element name="wasInvalidatedBy" type="prov:Invalidation"/>
-
- <!-- Component 2 elements -->
-
- <xs:element name="wasDerivedFrom" type="prov:Derivation"/>
- <xs:element name="wasRevisionOf" type="prov:Revision"/>
- <xs:element name="wasQuotedFrom" type="prov:Quotation"/>
- <xs:element name="hadPrimarySource" type="prov:PrimarySource"/>
-
- <!-- Component 3 elements -->
-
- <xs:element name="agent" type="prov:Agent"/>
- <xs:element name="person" type="prov:Person"/>
- <xs:element name="organization" type="prov:Organization"/>
- <xs:element name="softwareAgent" type="prov:SoftwareAgent"/>
- <xs:element name="wasAttributedTo" type="prov:Attribution"/>
- <xs:element name="wasAssociatedWith" type="prov:Association"/>
- <xs:element name="actedOnBehalfOf" type="prov:Delegation"/>
- <xs:element name="wasInfluencedBy" type="prov:Influence"/>
-
- <!-- Component 5 elements -->
-
- <xs:element name="bundle" type="prov:Bundle"/>
- <xs:element name="specializationOf" type="prov:Specialization"/>
- <xs:element name="alternateOf" type="prov:Alternate"/>
-
- <!-- Component 6 elements -->
-
- <xs:element name="hadMember" type="prov:Membership"/>
- <xs:element name="collection" type="prov:Collection"/>
- <xs:element name="emptyCollection" type="prov:EmptyCollection"/>
-
- <!-- Component 7 elements -->
-
- <xs:element name="plan" type="prov:Plan"/>
-
- <!-- document container and allowable PROV elements -->
-
- <xs:element name="document" type="prov:Document" />
-
- <xs:complexType name="Document">
- <xs:sequence maxOccurs="unbounded">
- <xs:element ref="prov:entity" minOccurs="0"/>
- <xs:element ref="prov:activity" minOccurs="0"/>
- <xs:element ref="prov:wasGeneratedBy" minOccurs="0"/>
- <xs:element ref="prov:used" minOccurs="0"/>
- <xs:element ref="prov:wasInformedBy" minOccurs="0"/>
- <xs:element ref="prov:wasStartedBy" minOccurs="0"/>
- <xs:element ref="prov:wasEndedBy" minOccurs="0"/>
- <xs:element ref="prov:wasInvalidatedBy" minOccurs="0"/>
- <xs:element ref="prov:wasDerivedFrom" minOccurs="0"/>
- <xs:element ref="prov:wasRevisionOf" minOccurs="0"/>
- <xs:element ref="prov:wasQuotedFrom" minOccurs="0"/>
- <xs:element ref="prov:hadPrimarySource" minOccurs="0"/>
- <xs:element ref="prov:agent" minOccurs="0"/>
- <xs:element ref="prov:person" minOccurs="0"/>
- <xs:element ref="prov:organization" minOccurs="0"/>
- <xs:element ref="prov:softwareAgent" minOccurs="0"/>
- <xs:element ref="prov:wasAttributedTo" minOccurs="0"/>
- <xs:element ref="prov:wasAssociatedWith" minOccurs="0"/>
- <xs:element ref="prov:actedOnBehalfOf" minOccurs="0"/>
- <xs:element ref="prov:wasInfluencedBy" minOccurs="0"/>
- <xs:element ref="prov:bundle" minOccurs="0"/>
- <xs:element ref="prov:specializationOf" minOccurs="0"/>
- <xs:element ref="prov:alternateOf" minOccurs="0"/>
- <xs:element ref="prov:collection" minOccurs="0"/>
- <xs:element ref="prov:emptyCollection" minOccurs="0"/>
- <xs:element ref="prov:hadMember" minOccurs="0"/>
- <xs:element ref="prov:plan" minOccurs="0"/>
- <xs:element ref="prov:other" minOccurs="0"/>
- <xs:element ref="prov:internalElement" minOccurs="0"/>
- <xs:element name="bundleContent" type="prov:BundleConstructor" minOccurs="0"/>
- </xs:sequence>
- </xs:complexType>
-
- <!-- abstract element used by PROV extensions -->
-
- <xs:element name="internalElement" abstract="true" />
-
- <!-- 'others' element used to contain non-PROV elements -->
-
- <xs:element name="other" type="prov:Other"/>
-
- <xs:complexType name="Other">
- <xs:sequence>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- </xs:complexType>
-
-</xs:schema>
-
-</pre>
+<h3><span class="secno">A.2 </span>Core Schema</h3>
+<p>The PROV core schema defines an XML representation of the PROV data model defined by the PROV-DM. Extensions to PROV, defined in WG Notes, are defined in separate extension schemas.</p>
+<p>The PROV core schema is available at <a href="http://www.w3.org/ns/prov-core.xsd">http://www.w3.org/ns/prov-core.xsd</a></p>
</section> <!-- end prov-core-schema -->
<section id="extension-schemas">
<h3><span class="secno">A.3 </span>Extension Schemas</h3>
<p>Extension schemas are schemas in the PROV Namespace that define additional PROV elements not from the PROV-DM. Workgroup Notes provide extension schemas to define their Note-introduced PROV elements. Extension schemas must import (using <code>xs:include</code>) the <b>prov-core.xsd</b> schema and make use of a substitution group on the <code>prov:internalElement</code> to add extension defined elements to the list of valid PROV elements in a bundle or document.</p>
-<p>Here is an example from the <b>prov-links.xsd</b> extension schema.</p>
-<pre title="prov-links.xsd"><?xml version="1.0" encoding="UTF-8"?>
-<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
- targetNamespace="http://www.w3.org/ns/prov#" xmlns:prov="http://www.w3.org/ns/prov#"
- elementFormDefault="qualified">
-
- <xs:include schemaLocation="prov-core.xsd" />
-
- <xs:complexType name="Mention">
- <xs:sequence>
- <xs:element name="specificEntity" type="prov:IDRef" />
- <xs:element name="generalEntity" type="prov:IDRef" />
- <xs:element name="bundle" type="prov:IDRef" />
- </xs:sequence>
- </xs:complexType>
-
- <xs:element name="mentionOf" type="prov:Mention" substitutionGroup="prov:internalElement" />
-
-</xs:schema>
-</pre>
+<!-- TODO link to http://www.w3.org/ns/prov-dictionary.xsd, http://www.w3.org/ns/prov.xsd-links-->
+<p>The PROV-defined extension schemas are available at</p>
+<ul>
+<li>PROV-Dictionary: <a href="http://www.w3.org/ns/prov-dictionary.xsd">http://www.w3.org/ns/prov-dictionary.xsd</a></li>
+<li>PROV-Links: <a href="http://www.w3.org/ns/prov-links.xsd">http://www.w3.org/ns/prov-links.xsd</a></li>
+</ul>
</section> <!-- end extension-schemas -->
</section> <!-- end prov-xml-schema -->
@@ -2887,10 +2390,16 @@
<section id="change-log-since-wd-working-draft-12-march-2013">
<h3><span class="secno">B.1 </span>Change Log Since WD Working Draft 12 March 2013</h3>
<ul>
-<li>Updated inline schema</li>
-<li>Updated BundleConstructor and Document sections to reflect changes to schema</li>
-<li>Added Other section for prov:other element and type</li>
-<li>Updated the Status of this Document section</li>
+<li>Updated Component section descriptive text</li>
+<li>Added links to schemas in Schema Modularization section</li>
+<li>Fixed typo in Status of this Document section</li>
+<li>Added Identifier Conventions section</li>
+<li>Updated naming conventions to clarify distinction between PROV elements, attributes, and types and XML elements, attributes, and types.</li>
+<li>Added links to PROV-DM term/concepts in Table 1.</li>
+<li>Removed inline schema, added links to published schemas.</li>
+<li>Updated BundleConstructor and Document sections to reflect changes to schema.</li>
+<li>Added Other section for prov:other element and type.</li>
+<li>Updated the Status of this Document section.</li>
<li>Added a note about potential OXM issues to Schema Modularization section, referenced FAQ entry on subject.</li>
</ul>
</section>
@@ -2929,10 +2438,10 @@
Reza B'Far (Oracle Corporation),
Khalid Belhajjame (University of Manchester),
James Cheney (University of Edinburgh, School of Informatics),
-Sam Coppens (IBBT),
+Sam Coppens (iMinds - Ghent University),
David Corsar (University of Aberdeen, Computing Science),
Stephen Cresswell (The National Archives),
-Tom De Nies (IBBT),
+Tom De Nies (iMinds - Ghent University),
Helena Deus (DERI Galway at the National University of Ireland, Galway, Ireland),
Simon Dobson (Invited expert),
Martin Doerr (Foundation for Research and Technology - Hellas(FORTH)),
@@ -2995,7 +2504,7 @@
</dd><dt id="bib-PROV-AQ">[PROV-AQ]</dt><dd>Graham Klyne; Paul Groth; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/"><cite>Provenance Access and Query</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/">http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/</a>
</dd><dt id="bib-PROV-CONSTRAINTS">[PROV-CONSTRAINTS]</dt><dd>James Cheney; Paolo Missier; Luc Moreau; eds. <a href="http://www.w3.org/TR/2013/REC-prov-constraints-20130430/"><cite>Constraints of the PROV Data Model</cite></a>. 30 April 2013, W3C Recommendation. URL: <a href="http://www.w3.org/TR/2013/REC-prov-constraints-20130430/">http://www.w3.org/TR/2013/REC-prov-constraints-20130430/</a>
</dd><dt id="bib-PROV-DC">[PROV-DC]</dt><dd>Daniel Garijo; Kai Eckert; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/"><cite>Dublin Core to PROV Mapping</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/">http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/</a>
-</dd><dt id="bib-PROV-DICTIONARY">[PROV-DICTIONARY]</dt><dd>Tom De Nies; Sam Coppens; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><cite>PROV Dictionary</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/</a>
+</dd><dt id="bib-PROV-DICTIONARY">[PROV-DICTIONARY]</dt><dd>Tom De Nies; Sam Coppens; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><cite>PROV-Dictionary: Modeling Provenance for Dictionary Data Structures</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/</a>
</dd><dt id="bib-PROV-DM">[PROV-DM]</dt><dd>Luc Moreau; Paolo Missier; eds. <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/"><cite>PROV-DM: The PROV Data Model</cite></a>. 30 April 2013, W3C Recommendation. URL: <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/">http://www.w3.org/TR/2013/REC-prov-dm-20130430/</a>
</dd><dt id="bib-PROV-LINKS">[PROV-LINKS]</dt><dd>Luc Moreau; Timothy Lebo; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-links-20130430/"><cite>Linking Across Provenance Bundles</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-links-20130430/">http://www.w3.org/TR/2013/NOTE-prov-links-20130430/</a>
</dd><dt id="bib-PROV-N">[PROV-N]</dt><dd>Luc Moreau; Paolo Missier; eds. <a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/"><cite>PROV-N: The Provenance Notation</cite></a>. 30 April 2013, W3C Recommendation. URL: <a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/">http://www.w3.org/TR/2013/REC-prov-n-20130430/</a>
@@ -3008,4 +2517,4 @@
</dd><dt id="bib-RFC3986">[RFC3986]</dt><dd>T. Berners-Lee; R. Fielding; L. Masinter. <a href="http://www.ietf.org/rfc/rfc3986.txt"><cite>Uniform Resource Identifier (URI): Generic Syntax (RFC 3986)</cite></a>. January 2005. RFC. URL: <a href="http://www.ietf.org/rfc/rfc3986.txt">http://www.ietf.org/rfc/rfc3986.txt</a>
</dd><dt id="bib-RFC3987">[RFC3987]</dt><dd>M. Dürst; M. Suignard. <a href="http://www.ietf.org/rfc/rfc3987.txt"><cite>Internationalized Resource Identifiers (IRIs) (RFC 3987)</cite></a>. January 2005. RFC. URL: <a href="http://www.ietf.org/rfc/rfc3987.txt">http://www.ietf.org/rfc/rfc3987.txt</a>
</dd><dt id="bib-UNISEC">[UNISEC]</dt><dd> Mark Davis; Michel Suignard. <a href="http://www.unicode.org/reports/tr36/"><cite>Unicode Security Considerations<cite></cite></cite></a>. 4 August 2010. URL: <a href="http://www.unicode.org/reports/tr36/">http://www.unicode.org/reports/tr36/</a>
-</dd></dl></section></section></body></html>
\ No newline at end of file
+</dd></dl></section></section></body></html>
--- a/xml/releases/NOTE-prov-xml-20130430/diff.html Fri Apr 26 09:26:16 2013 +0100
+++ b/xml/releases/NOTE-prov-xml-20130430/diff.html Fri Apr 26 09:27:12 2013 +0100
@@ -94,13 +94,13 @@
code {
color: #ff4500;
-}
+}<span class="delete">
/* --- --- */
ol.algorithm { counter-reset:numsection; list-style-type: none; }
ol.algorithm li { margin: 0.5em 0; }
-ol.algorithm li:before { font-weight: bold; counter-increment: numsection; content: counters(numsection, ".") ") "; }
+ol.algorithm li:before { font-weight: bold; counter-increment: numsection; content: counters(numsection, ".") ") "; }</span>
/* --- TOC --- */
.toc a, .tof a {
@@ -204,7 +204,7 @@
color: #b9ab2d;
}
div.issue-title { color: #e05252; }
-div.note-title { color: #52e052; }
+div.note-title { color: #2b2; }
div.issue-title span, div.note-title span {
text-transform: uppercase;
}
@@ -219,7 +219,7 @@
border-left-style: solid;
}
div.issue, div.note {
- padding: 0.5em;
+ padding: 1em 1.2em 0.5em;
margin: 1em 0;
position: relative;
clear: both;
@@ -236,11 +236,11 @@
}
-</span></style><link rel="stylesheet" href="http://www.w3.org/StyleSheets/TR/W3C-WG-NOTE"></head>
+</span></style><link rel="stylesheet" href="//www.w3.org/StyleSheets/TR/W3C-WG-NOTE"></head>
<body><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>
+ <a href="http://www.w3.org/"><img width="72" height="48" src="https://www.w3.org/Icons/w3c_home" alt="W3C"></a>
</p>
<h1 class="title" id="title">PROV-XML: The PROV XML Schema</h1>
@@ -248,23 +248,10 @@
<h2 id="w3c-working-group-note-30-april-2013"><abbr title="World Wide Web Consortium">W3C</abbr> Working <span class="delete">Draft 12 March</span><span class="insert">Group Note 30 April</span> 2013</h2>
<dl>
- <dt>This<span class="insert"> version:</span></dt>
- <dd><a href="http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/</span></a></dd>
- <dt><span class="insert">Latest published version:</span></dt>
- <dd><a href="http://www.w3.org/TR/prov-xml/"><span class="insert">http://www.w3.org/TR/prov-xml/</span></a></dd>
-
-
- <dt><span class="insert">Latest editor's draft:</span></dt>
- <dd><a href="http://dvcs.w3.org/hg/prov/raw-file/default/xml/prov-xml.html"><span class="insert">http://dvcs.w3.org/hg/prov/raw-file/default/xml/prov-xml.html</span></a></dd>
-
-
-
-
-
- <dt><span class="insert">Previous</span> version:</dt>
- <dd><a href="http://www.w3.org/TR/2013/WD-prov-xml-20130312/">http://www.w3.org/TR/2013/WD-prov-xml-20130312/
- <span class="delete">Latest published version:</span>
- <span class="delete">http://www.w3.org/TR/prov-xml/</span>
+ <dt>This version:</dt>
+ <dd><span class="delete">http://www.w3.org/TR/2013/WD-prov-xml-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/</span></a></dd>
+ <dt>Latest published version:</dt>
+ <dd><a href="http://www.w3.org/TR/prov-xml/">http://www.w3.org/TR/prov-xml/</a></dd>
<span class="delete">Latest editor's draft:</span>
@@ -274,8 +261,15 @@
- <span class="delete">Previous version:</span>
- <span class="delete">http://www.w3.org/TR/2012/WD-prov-xml-20121211/</span></a> <a href="diff.html">(color-coded diff)</a></dd>
+
+
+
+
+
+
+
+ <dt>Previous version:</dt>
+ <dd><span class="delete">http://www.w3.org/TR/2012/WD-prov-xml-20121211/</span><a href="http://www.w3.org/TR/2013/WD-prov-xml-20130312/"><span class="insert">http://www.w3.org/TR/2013/WD-prov-xml-20130312/</span></a> <a href="diff.html">(color-coded diff)</a></dd>
<dt>Editors:</dt>
@@ -341,7 +335,7 @@
<li> <a href="http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/">PROV-XML</a> <span class="delete">(To be published as Note),</span><span class="insert">(Note),</span> an XML schema for the PROV data model (this document);</li>
<li> <a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/">PROV-AQ</a> <span class="delete">(To be published as Note), the</span><span class="insert">(Note),</span> mechanisms for accessing and querying provenance [<cite><a class="bibref" href="#bib-PROV-AQ">PROV-AQ</a></cite>]; </li>
<li> <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/">PROV-DICTIONARY</a> <span class="delete">(To be published as Note)</span><span class="insert">(Note)</span> introduces a specific type of collection, consisting of key-entity pairs [<cite><a class="bibref" href="#bib-PROV-DICTIONARY">PROV-DICTIONARY</a></cite>];</li>
-<li> <a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/">PROV-DC</a> <span class="delete">(To be published as Note)</span><span class="insert">(Note)</span> provides a mapping between <span class="delete">PROV</span><span class="insert">PROV-O</span> and Dublic Core Terms [<cite><a class="bibref" href="#bib-PROV-DC">PROV-DC</a></cite>];</li>
+<li> <a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/">PROV-DC</a> <span class="delete">(To be published as Note)</span><span class="insert">(Note)</span> provides a mapping between <span class="delete">PROV</span><span class="insert">PROV-O</span> and <span class="delete">Dublic</span><span class="insert">Dublin</span> Core Terms [<cite><a class="bibref" href="#bib-PROV-DC">PROV-DC</a></cite>];</li>
<li> <a href="http://www.w3.org/TR/2013/NOTE-prov-sem-20130430/">PROV-SEM</a> <span class="delete">(To be published as Note),</span><span class="insert">(Note),</span> a declarative specification in terms of first-order logic of the PROV data model [<cite><a class="bibref" href="#bib-PROV-SEM">PROV-SEM</a></cite>];</li>
<li> <a href="http://www.w3.org/TR/2013/NOTE-prov-links-20130430/">PROV-LINKS</a> <span class="delete">(To be published as Note)</span><span class="insert">(Note)</span> introduces a mechanism to link across bundles [<cite><a class="bibref" href="#bib-PROV-LINKS">PROV-LINKS</a></cite>].</li>
</ul>
@@ -407,7 +401,7 @@
-</section><section id="toc"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a href="#introduction" class="tocxref"><span class="secno">1. </span>Introduction</a><ul class="toc"><li class="tocline"><a href="#prov-namespace" class="tocxref"><span class="secno">1.1 </span>PROV Namespace</a></li><li class="tocline"><a href="#conventions" class="tocxref"><span class="secno">1.2 </span>Conventions</a></li></ul></li><li class="tocline"><a href="#schema-design" class="tocxref"><span class="secno">2. </span>XML Schema Design</a><ul class="toc"><li class="tocline"><a href="#schema-modularization" class="tocxref"><span class="secno">2.1 </span>Schema Modularization</a></li><li class="tocline"><a href="#design-pattern" class="tocxref"><span class="secno">2.2 </span><i>Salami Slice</i> Design Pattern</a></li><li class="tocline"><a href="#elements-vs-attributes" class="tocxref"><span class="secno">2.3 </span>Elements vs. Attributes</a></li><li class="tocline"><a href="#type-conventions" class="tocxref"><span class="secno">2.4 </span>Type Conventions</a><ul class="toc"><li class="tocline"><a href="#type-conventions-attributes" class="tocxref"><span class="secno">2.4.1 </span>PROV Type Attribute</a></li><li class="tocline"><a href="#type-conventions-extension-types" class="tocxref"><span class="secno">2.4.2 </span>Extension Types</a></li><li class="tocline"><a href="#type-conventions-xsi-type" class="tocxref"><span class="secno">2.4.3 </span>XSI Type</a></li></ul></li><li class="tocline"><a href="#naming-conventions" class="tocxref"><span class="secno">2.5 </span>Naming Conventions</a></li></ul></li><li class="tocline"><a href="#schema-components" class="tocxref"><span class="secno">3. </span>PROV XML Schema</a><ul class="toc"><li class="tocline"><a href="#component1" class="tocxref"><span class="secno">3.1 </span>Component 1: Entities and Activities</a><ul class="toc"><li class="tocline"><a href="#term-Entity" class="tocxref"><span class="secno">3.1.1 </span>Entity</a></li><li class="tocline"><a href="#term-Activity" class="tocxref"><span class="secno">3.1.2 </span>Activity</a></li><li class="tocline"><a href="#term-Generation" class="tocxref"><span class="secno">3.1.3 </span>Generation</a></li><li class="tocline"><a href="#term-Usage" class="tocxref"><span class="secno">3.1.4 </span>Usage</a></li><li class="tocline"><a href="#term-Communication" class="tocxref"><span class="secno">3.1.5 </span>Communication</a></li><li class="tocline"><a href="#term-Start" class="tocxref"><span class="secno">3.1.6 </span>Start</a></li><li class="tocline"><a href="#term-End" class="tocxref"><span class="secno">3.1.7 </span>End</a></li><li class="tocline"><a href="#term-Invalidation" class="tocxref"><span class="secno">3.1.8 </span>Invalidation</a></li></ul></li><li class="tocline"><a href="#component2" class="tocxref"><span class="secno">3.2 </span>Component 2: Derivations</a><ul class="toc"><li class="tocline"><a href="#term-Derivation" class="tocxref"><span class="secno">3.2.1 </span>Derivation</a></li><li class="tocline"><a href="#term-Revision" class="tocxref"><span class="secno">3.2.2 </span>Revision</a></li><li class="tocline"><a href="#term-Quotation" class="tocxref"><span class="secno">3.2.3 </span>Quotation</a></li><li class="tocline"><a href="#term-PrimarySource" class="tocxref"><span class="secno">3.2.4 </span>Primary Source</a></li></ul></li><li class="tocline"><a href="#component3" class="tocxref"><span class="secno">3.3 </span>Component 3: Agents, Responsibility, and Influence</a><ul class="toc"><li class="tocline"><a href="#term-Agent" class="tocxref"><span class="secno">3.3.1 </span>Agent</a><ul class="toc"><li class="tocline"><a href="#term-Person" class="tocxref"><span class="secno">3.3.1.1 </span>Person</a></li><li class="tocline"><a href="#term-Organization" class="tocxref"><span class="secno">3.3.1.2 </span>Organization</a></li><li class="tocline"><a href="#term-SoftwareAgent" class="tocxref"><span class="secno">3.3.1.3 </span>Software Agent</a></li></ul></li><li class="tocline"><a href="#term-Attribution" class="tocxref"><span class="secno">3.3.2 </span>Attribution</a></li><li class="tocline"><a href="#term-Association" class="tocxref"><span class="secno">3.3.3 </span>Association</a><ul class="toc"><li class="tocline"><a href="#term-Plan" class="tocxref"><span class="secno">3.3.3.1 </span>Plan</a></li></ul></li><li class="tocline"><a href="#term-Delegation" class="tocxref"><span class="secno">3.3.4 </span>Delegation</a></li><li class="tocline"><a href="#term-Influence" class="tocxref"><span class="secno">3.3.5 </span>Influence</a></li></ul></li><li class="tocline"><a href="#component4" class="tocxref"><span class="secno">3.4 </span>Component 4: Bundles</a><ul class="toc"><li class="tocline"><a href="#term-Bundle" class="tocxref"><span class="secno">3.4.1 </span>Bundle</a></li><li class="tocline"><a href="#term-BundleConstructor" class="tocxref"><span class="secno">3.4.2 </span>Bundle Constructor</a></li></ul></li><li class="tocline"><a href="#component5" class="tocxref"><span class="secno">3.5 </span>Component 5: Alternate Entities</a><ul class="toc"><li class="tocline"><a href="#term-Specialization" class="tocxref"><span class="secno">3.5.1 </span>Specialization</a></li><li class="tocline"><a href="#term-Alternate" class="tocxref"><span class="secno">3.5.2 </span>Alternate</a></li></ul></li><li class="tocline"><a href="#component6" class="tocxref"><span class="secno">3.6 </span>Component 6: Collections</a><ul class="toc"><li class="tocline"><a href="#term-Collection" class="tocxref"><span class="secno">3.6.1 </span>Collection</a><ul class="toc"><li class="tocline"><a href="#term-EmptyCollection" class="tocxref"><span class="secno">3.6.1.1 </span>Empty Collection</a></li></ul></li><li class="tocline"><a href="#term-Membership" class="tocxref"><span class="secno">3.6.2 </span>Membership</a></li></ul></li><li class="tocline"><a href="#further-elements" class="tocxref"><span class="secno">3.7 </span>Further Elements of PROV</a><ul class="toc"><li class="tocline"><a href="#attribute-Identifier" class="tocxref"><span class="secno">3.7.1 </span>Identifier</a></li><li class="tocline"><a href="#attribute-Reference" class="tocxref"><span class="secno">3.7.2 </span>Reference</a></li><li class="tocline"><a href="#attributes" class="tocxref"><span class="secno">3.7.3 </span>Attributes</a><ul class="toc"><li class="tocline"><a href="#element-Label" class="tocxref"><span class="secno">3.7.3.1 </span>Label</a></li><li class="tocline"><a href="#element-Location" class="tocxref"><span class="secno">3.7.3.2 </span>Location</a></li><li class="tocline"><a href="#element-Role" class="tocxref"><span class="secno">3.7.3.3 </span>Role</a></li><li class="tocline"><a href="#element-Type" class="tocxref"><span class="secno">3.7.3.4 </span>Type</a></li><li class="tocline"><a href="#element-Value" class="tocxref"><span class="secno">3.7.3.5 </span>Value</a></li></ul></li><li class="tocline"><a href="#type-value" class="tocxref"><span class="secno">3.7.4 </span>Value</a></li></ul></li><li class="tocline"><a href="#structural-elements" class="tocxref"><span class="secno">3.8 </span>Structural Elements of PROV-XML</a><ul class="toc"><li class="tocline"><a href="#term-Document" class="tocxref"><span class="secno">3.8.1 </span>Document</a></li><li class="tocline"><a href="#term-Other" class="tocxref"><span class="secno"><span class="insert">3.8.2 </span></span><span class="insert">Other</span></a></li></ul></li></ul></li><li class="tocline"><a href="#media-type" class="tocxref"><span class="secno">4. </span>Media Type</a></li><li class="tocline"><a href="#prov-xml-schema" class="tocxref"><span class="secno">A. </span>XML Schema</a><ul class="toc"><li class="tocline"><a href="#prov-schema" class="tocxref"><span class="secno">A.1 </span>prov.xsd</a></li><li class="tocline"><a href="#prov-core-schema" class="tocxref"><span class="secno">A.2 </span>prov-core.xsd</a></li><li class="tocline"><a href="#extension-schemas" class="tocxref"><span class="secno">A.3 </span>Extension Schemas</a></li></ul></li><li class="tocline"><a href="#changelog" class="tocxref"><span class="secno">B. </span>Change Log</a><ul class="toc"><li class="tocline"><a href="#change-log-since-wd-working-draft-12-march-2013" class="tocxref"><span class="secno">B.1 </span><span class="delete">Changes since last version</span><span class="insert">Change Log Since WD Working Draft 12 March 2013</span></a></li><li class="tocline"><a href="#change-log-since-first-public-working-draft" class="tocxref"><span class="secno"><span class="insert">B.2 </span></span><span class="insert">Change Log Since First Public Working Draft</span></a></li></ul></li><li class="tocline"><a href="#acknowledgements" class="tocxref"><span class="secno">C. </span>Acknowledgements</a></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">D. </span>References</a><ul class="toc"><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">D.1 </span>Informative references</a></li></ul></li></ul></section>
+</section><section id="toc"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a href="#introduction" class="tocxref"><span class="secno">1. </span>Introduction</a><ul class="toc"><li class="tocline"><a href="#prov-namespace" class="tocxref"><span class="secno">1.1 </span>PROV Namespace</a></li><li class="tocline"><a href="#conventions" class="tocxref"><span class="secno">1.2 </span>Conventions</a></li></ul></li><li class="tocline"><a href="#schema-design" class="tocxref"><span class="secno">2. </span>XML Schema Design</a><ul class="toc"><li class="tocline"><a href="#schema-modularization" class="tocxref"><span class="secno">2.1 </span>Schema Modularization</a></li><li class="tocline"><a href="#design-pattern" class="tocxref"><span class="secno">2.2 </span><i>Salami Slice</i> Design Pattern</a></li><li class="tocline"><a href="#elements-vs-attributes" class="tocxref"><span class="secno">2.3 </span>Elements vs. Attributes</a></li><li class="tocline"><a href="#type-conventions" class="tocxref"><span class="secno">2.4 </span>Type Conventions</a><ul class="toc"><li class="tocline"><a href="#type-conventions-attributes" class="tocxref"><span class="secno">2.4.1 </span>PROV Type Attribute</a></li><li class="tocline"><a href="#type-conventions-extension-types" class="tocxref"><span class="secno">2.4.2 </span>Extension Types</a></li><li class="tocline"><a href="#type-conventions-xsi-type" class="tocxref"><span class="secno">2.4.3 </span>XSI Type</a></li></ul></li><li class="tocline"><a href="#identifier-conventions" class="tocxref"><span class="secno"><span class="insert">2.5 </span></span><span class="insert">Identifier Conventions</span></a></li><li class="tocline"><a href="#naming-conventions" class="tocxref"><span class="secno"><span class="delete">2.5</span><span class="insert">2.6</span> </span>Naming Conventions</a></li></ul></li><li class="tocline"><a href="#schema-components" class="tocxref"><span class="secno">3. </span>PROV XML Schema</a><ul class="toc"><li class="tocline"><a href="#component1" class="tocxref"><span class="secno">3.1 </span>Component 1: Entities and Activities</a><ul class="toc"><li class="tocline"><a href="#term-Entity" class="tocxref"><span class="secno">3.1.1 </span>Entity</a></li><li class="tocline"><a href="#term-Activity" class="tocxref"><span class="secno">3.1.2 </span>Activity</a></li><li class="tocline"><a href="#term-Generation" class="tocxref"><span class="secno">3.1.3 </span>Generation</a></li><li class="tocline"><a href="#term-Usage" class="tocxref"><span class="secno">3.1.4 </span>Usage</a></li><li class="tocline"><a href="#term-Communication" class="tocxref"><span class="secno">3.1.5 </span>Communication</a></li><li class="tocline"><a href="#term-Start" class="tocxref"><span class="secno">3.1.6 </span>Start</a></li><li class="tocline"><a href="#term-End" class="tocxref"><span class="secno">3.1.7 </span>End</a></li><li class="tocline"><a href="#term-Invalidation" class="tocxref"><span class="secno">3.1.8 </span>Invalidation</a></li></ul></li><li class="tocline"><a href="#component2" class="tocxref"><span class="secno">3.2 </span>Component 2: Derivations</a><ul class="toc"><li class="tocline"><a href="#term-Derivation" class="tocxref"><span class="secno">3.2.1 </span>Derivation</a></li><li class="tocline"><a href="#term-Revision" class="tocxref"><span class="secno">3.2.2 </span>Revision</a></li><li class="tocline"><a href="#term-Quotation" class="tocxref"><span class="secno">3.2.3 </span>Quotation</a></li><li class="tocline"><a href="#term-PrimarySource" class="tocxref"><span class="secno">3.2.4 </span>Primary Source</a></li></ul></li><li class="tocline"><a href="#component3" class="tocxref"><span class="secno">3.3 </span>Component 3: Agents, Responsibility, and Influence</a><ul class="toc"><li class="tocline"><a href="#term-Agent" class="tocxref"><span class="secno">3.3.1 </span>Agent</a><ul class="toc"><li class="tocline"><a href="#term-Person" class="tocxref"><span class="secno">3.3.1.1 </span>Person</a></li><li class="tocline"><a href="#term-Organization" class="tocxref"><span class="secno">3.3.1.2 </span>Organization</a></li><li class="tocline"><a href="#term-SoftwareAgent" class="tocxref"><span class="secno">3.3.1.3 </span>Software Agent</a></li></ul></li><li class="tocline"><a href="#term-Attribution" class="tocxref"><span class="secno">3.3.2 </span>Attribution</a></li><li class="tocline"><a href="#term-Association" class="tocxref"><span class="secno">3.3.3 </span>Association</a><ul class="toc"><li class="tocline"><a href="#term-Plan" class="tocxref"><span class="secno">3.3.3.1 </span>Plan</a></li></ul></li><li class="tocline"><a href="#term-Delegation" class="tocxref"><span class="secno">3.3.4 </span>Delegation</a></li><li class="tocline"><a href="#term-Influence" class="tocxref"><span class="secno">3.3.5 </span>Influence</a></li></ul></li><li class="tocline"><a href="#component4" class="tocxref"><span class="secno">3.4 </span>Component 4: Bundles</a><ul class="toc"><li class="tocline"><a href="#term-Bundle" class="tocxref"><span class="secno">3.4.1 </span>Bundle</a></li><li class="tocline"><a href="#term-BundleConstructor" class="tocxref"><span class="secno">3.4.2 </span>Bundle Constructor</a></li></ul></li><li class="tocline"><a href="#component5" class="tocxref"><span class="secno">3.5 </span>Component 5: Alternate Entities</a><ul class="toc"><li class="tocline"><a href="#term-Specialization" class="tocxref"><span class="secno">3.5.1 </span>Specialization</a></li><li class="tocline"><a href="#term-Alternate" class="tocxref"><span class="secno">3.5.2 </span>Alternate</a></li></ul></li><li class="tocline"><a href="#component6" class="tocxref"><span class="secno">3.6 </span>Component 6: Collections</a><ul class="toc"><li class="tocline"><a href="#term-Collection" class="tocxref"><span class="secno">3.6.1 </span>Collection</a><ul class="toc"><li class="tocline"><a href="#term-EmptyCollection" class="tocxref"><span class="secno">3.6.1.1 </span>Empty Collection</a></li></ul></li><li class="tocline"><a href="#term-Membership" class="tocxref"><span class="secno">3.6.2 </span>Membership</a></li></ul></li><li class="tocline"><a href="#further-elements" class="tocxref"><span class="secno">3.7 </span>Further Elements of PROV</a><ul class="toc"><li class="tocline"><a href="#attribute-Identifier" class="tocxref"><span class="secno">3.7.1 </span>Identifier</a></li><li class="tocline"><a href="#attribute-Reference" class="tocxref"><span class="secno">3.7.2 </span>Reference</a></li><li class="tocline"><a href="#attributes" class="tocxref"><span class="secno">3.7.3 </span>Attributes</a><ul class="toc"><li class="tocline"><a href="#element-Label" class="tocxref"><span class="secno">3.7.3.1 </span>Label</a></li><li class="tocline"><a href="#element-Location" class="tocxref"><span class="secno">3.7.3.2 </span>Location</a></li><li class="tocline"><a href="#element-Role" class="tocxref"><span class="secno">3.7.3.3 </span>Role</a></li><li class="tocline"><a href="#element-Type" class="tocxref"><span class="secno">3.7.3.4 </span>Type</a></li><li class="tocline"><a href="#element-Value" class="tocxref"><span class="secno">3.7.3.5 </span>Value</a></li></ul></li><li class="tocline"><a href="#type-value" class="tocxref"><span class="secno">3.7.4 </span>Value</a></li></ul></li><li class="tocline"><a href="#structural-elements" class="tocxref"><span class="secno">3.8 </span>Structural Elements of PROV-XML</a><ul class="toc"><li class="tocline"><a href="#term-Document" class="tocxref"><span class="secno">3.8.1 </span>Document</a></li><li class="tocline"><a href="#term-Other" class="tocxref"><span class="secno"><span class="insert">3.8.2 </span></span><span class="insert">Other</span></a></li></ul></li></ul></li><li class="tocline"><a href="#media-type" class="tocxref"><span class="secno">4. </span>Media Type</a></li><li class="tocline"><a href="#prov-xml-schema" class="tocxref"><span class="secno">A. </span>XML Schema</a><ul class="toc"><li class="tocline"><a href="#prov-schema" class="tocxref"><span class="secno">A.1 </span><span class="delete">prov.xsd</span><span class="insert">Main Schema</span></a></li><li class="tocline"><a href="#prov-core-schema" class="tocxref"><span class="secno">A.2 </span><span class="delete">prov-core.xsd</span><span class="insert">Core Schema</span></a></li><li class="tocline"><a href="#extension-schemas" class="tocxref"><span class="secno">A.3 </span>Extension Schemas</a></li></ul></li><li class="tocline"><a href="#changelog" class="tocxref"><span class="secno">B. </span>Change Log</a><ul class="toc"><li class="tocline"><a href="#change-log-since-wd-working-draft-12-march-2013" class="tocxref"><span class="secno">B.1 </span><span class="delete">Changes since last version</span><span class="insert">Change Log Since WD Working Draft 12 March 2013</span></a></li><li class="tocline"><a href="#change-log-since-first-public-working-draft" class="tocxref"><span class="secno"><span class="insert">B.2 </span></span><span class="insert">Change Log Since First Public Working Draft</span></a></li></ul></li><li class="tocline"><a href="#acknowledgements" class="tocxref"><span class="secno">C. </span>Acknowledgements</a></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">D. </span>References</a><ul class="toc"><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">D.1 </span>Informative references</a></li></ul></li></ul></section>
@@ -438,13 +432,14 @@
</li></ul>
<p>
-This specification goal is to provide a succinct definition of the XML form of PROV-DM, thus, we refer the reader to the PROV-DM to provide overall justification and context to the definitions presented here.
+<i>This <span class="delete">specification</span><span class="insert">specification's</span> goal is to provide a succinct definition of the XML form of <span class="delete">PROV-DM,</span><span class="insert">PROV-DM</span></i><span class="insert">,</span> thus, we refer the reader to the PROV-DM to provide overall justification and context to the definitions presented here.
</p>
<section id="prov-namespace">
<h3><span class="secno">1.1 </span>PROV Namespace</h3>
<p>The PROV namespace is <span class="name">http://www.w3.org/ns/prov#</span>.</p>
-<p> All the concepts, reserved names and attributes introduced in this specification belong to the PROV namespace.</p>
+<p> All the concepts, reserved names and attributes introduced in this specification belong<span class="insert"> to the PROV namespace.</span></p>
+<p><span class="insert">The prefix </span><b><span class="insert">prov</span></b><span class="insert"> is used when referring</span> to the PROV namespace.</p>
</section>
<section id="conventions">
@@ -466,42 +461,64 @@
<section id="schema-modularization">
<h3><span class="secno">2.1 </span>Schema Modularization</h3>
-<p>The PROV-XML schema have been modularized so that extension elements defined in Working Group Notes can be defined in separate schemas. Elements corresponding to terms defined in the PROV-DM are defined in the <b>prov-core.xsd</b> schema and elements corresponding to terms defined in notes are defined in extension schemas (e.g. <b>prov-dictionary.xsd</b>, <b>prov-links.xsd</b>). The default schema, <b>prov.xsd</b>, imports <b>prov-core.xsd</b> and all extension schemas developed by the Working Group. With this modeling all PROV elements, even those defined in Notes, are defined from the default schema. If the user wishes to leverage a schema that does not include extension elements the user can use schemaLocation to directly reference <b>prov-core.xsd</b>.</p>
-<p>The default schema - <b>prov.xsd</b></p>
+<p>The PROV-XML schema have been modularized so that <span class="insert">xml-elements denoting terms defined in Working Group Notes are defined in separate </span>extension<span class="delete"> elements defined in Working Group Notes can be defined in separate</span> schemas. <span class="delete">Elements corresponding to</span><span class="insert">All xml-elements denoting</span> terms defined in the PROV-DM are defined in the <b><span class="delete">prov-core.xsd</span><a href="http://www.w3.org/ns/prov-core.xsd"><span class="insert">http://www.w3.org/ns/prov-core.xsd</span></a></b> schema and <span class="delete">elements corresponding to</span><span class="insert">xml-elements denoting</span> terms defined in <span class="delete">notes</span><span class="insert">PROV Working Group Notes</span> are defined in extension schemas (e.g. <b><span class="delete">prov-dictionary.xsd</span><a href="http://www.w3.org/ns/prov-dictionary.xsd"><span class="insert">http://www.w3.org/ns/prov-dictionary.xsd</span></a></b>, <b><span class="delete">prov-links.xsd</span><a href="http://www.w3.org/ns/prov-links.xsd"><span class="insert">http://www.w3.org/ns/prov-links.xsd</span></a></b>). The default schema, <b><span class="delete">prov.xsd</span><a href="http://www.w3.org/ns/prov.xsd"><span class="insert">http://www.w3.org/ns/prov.xsd</span></a></b>, imports <b><span class="delete">prov-core.xsd</span><a href="http://www.w3.org/ns/prov-core.xsd"><span class="insert">http://www.w3.org/ns/prov-core.xsd</span></a></b> and all extension <span class="delete">schemas developed by the Working Group.</span><span class="insert">schemas.</span> With this modeling all PROV <span class="delete">elements,</span><span class="insert">xml-elements,</span> even those <span class="insert">denoting terms </span>defined in Notes, are <span class="delete">defined</span><span class="insert">declared</span> from the default schema. If the user wishes to leverage a schema that does not include <span class="delete">extension elements</span><span class="insert">xml-elements corresponding to terms from the PROV Notes</span> the user can use schemaLocation to directly reference <span class="delete">prov-core.xsd</span><span class="delete">.</span><span class="insert">the core schema.</span></p>
+<p>The default schema - <b><span class="delete">prov.xsd</span><a href="http://www.w3.org/ns/prov.xsd"><span class="insert">http://www.w3.org/ns/prov.xsd</span></a></b></p>
<pre><?xml version="1.0" encoding="utf-8"?>
<xs:schema targetNamespace="http://www.w3.org/ns/prov#"
- xmlns:xs="http://www.w3.org/2001/XMLSchema"
- xmlns:prov="http://www.w3.org/ns/prov#"
- elementFormDefault="qualified"
- attributeFormDefault="unqualified">
-
- <xs:include schemaLocation="prov-core.xsd"/>
- <xs:include schemaLocation="prov-dictionary.xsd"/>
- <xs:include schemaLocation="prov-links.xsd"/>
+
+ xmlns:xs="http://www.w3.org/2001/XMLSchema"
+
+ xmlns:prov="http://www.w3.org/ns/prov#"
+
+ elementFormDefault="qualified"
+
+ attributeFormDefault="unqualified">
+
+
+
+ <xs:include schemaLocation="prov-core.xsd"/>
+
+ <xs:include schemaLocation="prov-dictionary.xsd"/>
+
+ <xs:include schemaLocation="prov-links.xsd"/>
</xs:schema>
</pre>
-<p>Extension schemas import the <b>prov-core.xsd</b> schema and make use of a substitution group on the <code>prov:internalElement</code> to add extension-defined elements to the list of valid PROV elements in a bundle or document.</p>
-<div class="note"><div class="note-title"><span><span class="insert">Note</span></span></div><div class="">
-<p><span class="insert">This schema design leveraging substitutionGroups on an abstract element may result in sub-optimal binding classes being generated by OXM frameworks such as JAXB, JiBX, etc. See the PROV FAQ entry at </span><a href="http://www.w3.org/2001/sw/wiki/PROV-FAQ#How_should_I_generate_JAXB_classes_from_the_PROV-XML_schemas.3F"><span class="insert">How should I generate JAXB classes from the PROV-XML schemas?</span></a><span class="insert"> for a JAXB-specific discussion on using OXM technologies with the PROV schemas.</span></p>
+<p>Extension schemas import the <b><span class="delete">prov-core.xsd</span><a href="http://www.w3.org/ns/prov-core.xsd"><span class="insert">http://www.w3.org/ns/prov-core.xsd</span></a></b> schema and make use of a substitution group on the <code>prov:internalElement</code> to add extension-defined <span class="delete">elements</span><span class="insert">xml-elements</span> to the list of valid PROV <span class="delete">elements</span><span class="insert">xml-elements</span> in a bundle or document.</p>
+<div class="note"><div class="note-title" role="heading" aria-level="4"><span><span class="insert">Note</span></span></div><div class="">
+<p><span class="insert">This schema design leveraging substitutionGroups on an abstract xml-element may result in sub-optimal binding classes being generated by Object-to-XML frameworks such as JAXB, JiBX, etc. See the PROV FAQ entry at </span><a href="http://www.w3.org/2001/sw/wiki/PROV-FAQ#How_should_I_generate_JAXB_classes_from_the_PROV-XML_schemas.3F"><span class="insert">How should I generate JAXB classes from the PROV-XML schemas?</span></a><span class="insert"> for a JAXB-specific discussion on using OXM technologies with the PROV schemas.</span></p>
</div></div>
-<p>The <b>prov-links.xsd</b> extension schema.</p>
+<p>The <b><span class="delete">prov-links.xsd</span><a href="http://www.w3.org/ns/prov-links.xsd"><span class="insert">http://www.w3.org/ns/prov-links.xsd</span></a></b> extension schema.</p>
<pre><?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
- targetNamespace="http://www.w3.org/ns/prov#" xmlns:prov="http://www.w3.org/ns/prov#"
- elementFormDefault="qualified">
-
- <xs:include schemaLocation="prov-core.xsd" />
- <xs:complexType name="Mention">
- <xs:sequence>
- <xs:element name="specificEntity" type="prov:IDRef" />
- <xs:element name="generalEntity" type="prov:IDRef" />
- <xs:element name="bundle" type="prov:IDRef" />
- </xs:sequence>
- </xs:complexType>
+ targetNamespace="http://www.w3.org/ns/prov#" xmlns:prov="http://www.w3.org/ns/prov#"
- <xs:element name="mentionOf" type="prov:Mention" substitutionGroup="prov:internalElement" />
+ elementFormDefault="qualified">
+
+
+
+ <xs:include schemaLocation="prov-core.xsd" />
+
+
+
+ <xs:complexType name="Mention">
+
+ <xs:sequence>
+
+ <xs:element name="specificEntity" type="prov:IDRef" />
+
+ <xs:element name="generalEntity" type="prov:IDRef" />
+
+ <xs:element name="bundle" type="prov:IDRef" />
+
+ </xs:sequence>
+
+ </xs:complexType>
+
+
+
+ <xs:element name="mentionOf" type="prov:Mention" substitutionGroup="prov:internalElement" />
</xs:schema>
</pre>
@@ -512,14 +529,16 @@
<section id="design-pattern">
<h3><span class="secno">2.2 </span><i>Salami Slice</i> Design Pattern</h3>
-<p>The general design pattern for the XML schema has been called <i>Salami Slice Design</i>. With this design, the individual components are each defined at the top level as separate elements with distinct types. This allows the types to be easily reusable for domain specific extensions.</p>
-<p>The <code>prov:document</code> element has been defined to act as a convenient root element for a PROV-XML document, but it's use as the root element is not required. The schema follows the Salami Slice pattern to ensure PROV XML elements can be integrated with mixed-schema XML documents which require a different document root.</p>
+<p>The general design pattern for the XML schema has been called <i>Salami Slice Design</i>. With this design, the individual components are each defined at the top level as separate <span class="delete">elements</span><span class="insert">xml-elements</span> with distinct <span class="delete">types.</span><span class="insert">xml-types.</span> This allows the <span class="delete">types</span><span class="insert">xml-types</span> to be easily reusable for domain specific extensions.</p>
+<p>The <code>prov:document</code> <span class="delete">element</span><span class="insert">xml-element</span> has been defined to act as a convenient root <span class="delete">element</span><span class="insert">xml-element</span> for a PROV-XML document, but it's use as the root <span class="delete">element</span><span class="insert">xml-element</span> is not required. The schema follows the Salami Slice pattern to ensure PROV XML <span class="delete">elements</span><span class="insert">xml-elements</span> can be integrated with mixed-schema XML documents which require a different document root.</p>
</section>
<section id="elements-vs-attributes">
<h3><span class="secno">2.3 </span>Elements vs. Attributes</h3>
-<p>The general PROV-N syntax patterns for expressing provenance
+<p>The <span class="insert">PROV Notation (PROV-N) is a serialization of the PROV Data Model described in [</span><cite><a class="bibref" href="#bib-PROV-N"><span class="insert">PROV-N</span></a></cite><span class="insert">]. Examples in the [</span><cite><a class="bibref" href="#bib-PROV-DM"><span class="insert">PROV-DM</span></a></cite><span class="insert">] document are encoded using PROV-N. Because of the heavy use of PROV-N syntax in [</span><cite><a class="bibref" href="#bib-PROV-DM"><span class="insert">PROV-DM</span></a></cite><span class="insert">], the PROV-XML editors feel it is important to present a comparison of the PROV-N and PROV-XML syntaxes and justifications behind the select syntax decisions in PROV-XML.</span></p>
+
+<p><span class="insert">The </span>general PROV-N syntax patterns for expressing provenance
concepts are:
</p>
@@ -527,7 +546,7 @@
concept(id; elem1, elem2, ... [attr1=val2, attr2=val2])
</pre>
-<p>In both cases (required id or optional id), the PROV-N id is treated as an XML attribute (<code>prov:id</code>), the PROV-N "elements" are treated as XML elements, always with the same required order (position) as the PROV-DM/PROV-N description, and optional PROV-N "attributes", if allowed, always follow and are also represented by XML elements. As in PROV-N, the attributes can be specified multiple times, but unlike PROV-N the attributes have a fixed (alphabetical) order. The PROV-N "attribute" elements are always defined at the end of the encompassing sequence after all PROV-N "elements". Elements defined in namespaces other than the PROV namespace may be included in a element after all PROV elements.</p>
+<p>In <span class="delete">both cases (required id or optional id), the PROV-N id</span><span class="insert">PROV-XML the PROV identifier</span> is treated as an <span class="delete">XML attribute</span><span class="insert">xml-attribute</span> (<code>prov:id</code>), the <span class="delete">PROV-N "elements"</span><span class="insert">prov-"elements"</span> are treated as <span class="delete">XML elements,</span><span class="insert">xml-elements,</span> always with the same required order (position) as the PROV-DM/PROV-N <span class="delete">description, and</span><span class="insert">description followed by</span> optional <span class="delete">PROV-N "attributes", if allowed, always follow and</span><span class="insert">prov-"attributes" which</span> are also represented by <span class="delete">XML elements.</span><span class="insert">xml-elements.</span> As in PROV-N, the <span class="delete">attributes</span><span class="insert">prov-"attributes"</span> can be specified multiple times, but unlike PROV-N the <span class="delete">attributes</span><span class="insert">prov-"attributes"</span> have a fixed (alphabetical) order. The <span class="delete">PROV-N "attribute" elements</span><span class="insert">prov-"attribute" xml-elements</span> are always defined at the end of the encompassing sequence after all <span class="delete">PROV-N "elements".</span><span class="insert">prov-"element" xml-elements.</span> <span class="insert">XML </span>Elements defined in namespaces other than the PROV namespace may be included <span class="delete">in a element </span>after <span class="delete">all PROV elements.</span><span class="insert">the prov-"attribute" xml-elements.</span></p>
<p>Wherever an "id" is referenced from a later concept, the id is
referenced as a prov:ref attribute of the element within the concept.
@@ -552,8 +571,8 @@
<h3><span class="secno">2.4 </span>Type Conventions</h3>
<section id="type-conventions-attributes">
<h4><span class="secno">2.4.1 </span>PROV Type Attribute</h4>
-<p>The PROV-DM states type information is described using the prov:type PROV attribute and may occur multiple times for a given entity, activity, agent, or relation.</p>
-<p>PROV-XML uses the element <code>prov:type</code> to represent the prov:type PROV attribute. This element can be use to represent both PROV and non-PROV type information. The following examples shows type information encoded using the <code>prov:type</code> element.</p>
+<p>The PROV-DM states type information is described using the prov:type <span class="delete">PROV attribute</span><span class="insert">prov-"attribute"</span> and may occur multiple times for a given entity, activity, agent, or relation.</p>
+<p>PROV-XML uses the <span class="delete">element</span><span class="insert">xml-element</span> <code>prov:type</code> to represent the prov:type <span class="delete">PROV attribute.</span><span class="insert">prov-"attribute".</span> This <span class="delete">element</span><span class="insert">xml-element</span> can be use to represent both PROV and non-PROV type information. The following examples shows type information encoded using the <code>prov:type</code> <span class="delete">element.</span><span class="insert">xml-element.</span></p>
<div class="example"><div class="example-title"><span>Example 1</span>: type information using prov:type PROV attribute</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
@@ -567,11 +586,11 @@
</prov:entity>
</prov:document></pre></div>
-<p>The <code>prov:type</code> element can be used in conjunction with schema-defined PROV types (see examples 2-5).</p>
+<p>The <code>prov:type</code> <span class="delete">element</span><span class="insert">xml-element</span> can be used in conjunction with schema-defined PROV types (see examples 2-5).</p>
</section>
<section id="type-conventions-extension-types">
<h4><span class="secno">2.4.2 </span>Extension Types</h4>
-<p>PROV-XML defines complexTypes to match the PROV defined type values. These types provide a more native XML representation of PROV types. The following example is considered equivalent to the previous example because the element <code>prov:plan</code> has type <code>prov:Plan</code>. All complexTypes representing a PROV type which is defined as a subclass of another PROV type are defined in PROV-XML as extensions of their parent PROV type's complexType. For example, <code>prov:Plan</code> is defined as an extension of the complexType <code>prov:Entity</code> and may be referenced by either <code>prov:plan</code> or <code>prov:entity</code>.</p>
+<p>PROV-XML defines complexTypes to match the PROV defined type <span class="delete">values.</span><span class="insert">values (prov-type).</span> These <span class="delete">types</span><span class="insert">xml-types</span> provide a more native XML representation of <span class="delete">PROV types.</span><span class="insert">prov-"types".</span> The following example is considered equivalent to the previous example because the <span class="delete">element</span><span class="insert">xml-element</span> <code>prov:plan</code> has <span class="delete">type </span><code><span class="delete">prov:Plan</span><span class="insert">xs:type=prov:Plan</span></code>. All complexTypes representing a <span class="delete">PROV type</span><span class="insert">prov-"type"</span> which is defined as a subclass of another <span class="delete">PROV type</span><span class="insert">prov-"type"</span> are defined in PROV-XML as extensions of their parent <span class="delete">PROV type's</span><span class="insert">prov-"type's"</span> complexType. For example, <code>prov:Plan</code> is defined as an extension of the complexType <code>prov:Entity</code> and may be referenced by either <code>prov:plan</code> or <code>prov:entity</code><span class="delete">.</span><span class="insert"> xml-elements.</span></p>
<div class="example"><div class="example-title"><span>Example 2</span>: type information using schema defined types</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
@@ -584,8 +603,10 @@
</prov:plan>
</prov:document></pre></div>
-<p>When an extended type is used a PROV type attribute relation may be inferred for the current and any parent type of the declared type.</p>
-<p>Stating all type information using the PROV type attribute assists in interoperability with non-PROV-XML encoding of PROV.</p>
+<p>When an <span class="delete">extended</span><span class="insert">extension xml-type is used a prov-"type" may be inferred.</span></p>
+<p><span class="insert">Explicit</span> type <span class="insert">declarations made using the </span><code><span class="insert">prov:type</span></code><span class="insert"> xml-element may be easier for some encoding transformation tools (such as XSLT) to process, therefore use of the </span><code><span class="insert">prov:type</span></code><span class="insert"> xml-element </span>is <span class="delete">used a PROV type attribute relation may be inferred for the current and any parent type of the declared type.</span><span class="insert">highly encouraged even in cases where prov-"type" information is determinable from schema defined ComplexTypes.</span></p>
+<span class="delete">Stating all type information using the PROV type attribute assists in interoperability with non-PROV-XML encoding of PROV.</span>
+
<div class="example"><div class="example-title"><span>Example 3</span>: type information using schema defined types - type inferences</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
@@ -603,7 +624,7 @@
</section>
<section id="type-conventions-xsi-type">
<h4><span class="secno">2.4.3 </span>XSI Type</h4>
-<p>Because the <code>prov:Plan</code> complexType is defined as an extension of the complexType <code>prov:Entity</code>, the following example using <code>xsi:type</code> is valid and considered equivalent to the two previous examples. The attribute <code>xsi:type</code> tells an XML parser the complexType of the element. The value of <code>xsi:type</code> must be a complexType derived from the default element type in a schema with known location (referenced through <code>xsi:schemaLocation</code>).</p>
+<p>Because the <code>prov:Plan</code> complexType is defined as an extension of the complexType <code>prov:Entity</code>, the following example using <code>xsi:type</code> is valid and considered equivalent to the two previous examples. The <span class="delete">attribute</span><span class="insert">xml-attribute</span> <code>xsi:type</code> tells an XML parser the complexType of the <span class="delete">element.</span><span class="insert">xml-element.</span> The value of <code>xsi:type</code> must be a complexType derived from the default <span class="delete">element type</span><span class="insert">xml-element xml-type</span> in a schema with known location (referenced through <code>xsi:schemaLocation</code>).</p>
<div class="example"><div class="example-title"><span>Example 4</span>: type information using xsi:type</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
@@ -616,7 +637,7 @@
</prov:entity>
</prov:document></pre></div>
-<p>A PROV type attribute relation may be inferred by the use of the <code>xsi:type</code> XML attribute.</p>
+<p>A <span class="delete">PROV type attribute relation</span><span class="insert">prov-"type" xml-element</span> may be inferred by the use of the <code>xsi:type</code> <span class="delete">XML attribute.</span><span class="insert">xml-attribute.</span></p>
<div class="example"><div class="example-title"><span>Example 5</span>: type information using xsi:type - type inferences</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
@@ -632,13 +653,30 @@
</prov:document></pre></div>
</section>
+</section>
+
+
+
+<section id="identifier-conventions">
+<h3><span class="secno">2.5 </span><span class="delete">Naming</span><span class="insert">Identifier</span> Conventions</h3>
+<p><span class="delete">Element</span><span class="insert">[</span><cite><a class="bibref" href="#bib-PROV-DM"><span class="insert">PROV-DM</span></a></cite><span class="insert">] defines a PROV Identifier as a qualified name with the following definition:</span></p>
+<p><span class="insert">From [</span><cite><a class="bibref" href="#bib-PROV-DM"><span class="insert">PROV-DM</span></a></cite><span class="insert">]:</span></p><blockquote><i><span class="glossary-ref"><span class="insert"> A </span><span class="dfn"><span class="insert">qualified name</span></span><span class="insert"> is a name subject to namespace interpretation. It consists of a namespace, denoted by an optional prefix, and a local name. </span></span></i></blockquote>
+<p><span class="insert">[</span><cite><a class="bibref" href="#bib-PROV-DM"><span class="insert">PROV-DM</span></a></cite><span class="insert">] also mandates that all qualified</span> names <span class="delete">are aligned</span><span class="insert">be mappable to a URI by concatenating the namespace URI</span> with<span class="insert"> a local name.</span></p>
+
+<p><span class="insert">PROV-XML uses the </span><code><span class="insert">prov:id</span></code><span class="insert"> xml-attribute to denote a PROV Identifier and the </span><code><span class="insert">prov:ref</span></code><span class="insert"> xml-attribute to denote a reference-by-id to an instance of a prov-"type" or prov-"relation" which has a matching PROV Identifier. The value of </span><code><span class="insert">prov:ref</span></code><span class="insert"> must be a valid PROV Identifier, but there is no requirement that for every </span><code><span class="insert">prov:ref</span></code><span class="insert"> a corresponding </span><code><span class="insert">prov:id</span></code><span class="insert"> must be known to exist.</span></p>
+
+<p><span class="insert">PROV-XML defines the type of both the </span><code><span class="insert">prov:id</span></code><span class="insert"> and </span><code><span class="insert">prov:ref</span></code><span class="insert"> xml-attributes to be </span><code><span class="insert">xsd:QName</span></code><span class="insert"> as that is the XSD datatype that most closely matches the qualified name definition by [</span><cite><a class="bibref" href="#bib-PROV-DM"><span class="insert">PROV-DM</span></a></cite><span class="insert">]. Care should be taken when generating PROV identifier values in PROV-XML such that there is a known mapping to a URI.</span></p>
+
+<div class="note"><div class="note-title" role="heading" aria-level="4"><span><span class="insert">Note</span></span></div><div class="">
+<p><span class="insert">The xsd:QName datatype is more restrictive than the QualifiedName defined in</span> [<cite><a class="bibref" href="#bib-PROV-N">PROV-N</a></cite>] <span class="insert">(e.g. PROV-N allows local names to start with numbers), therefore valid identifier values in [</span><cite><a class="bibref" href="#bib-PROV-N"><span class="insert">PROV-N</span></a></cite><span class="insert">] serializations have to potential to not be valid identifier values in PROV-XML. It is recommended to enhance interoperability that provenance users strive to always use identifier schemes that map to valid xsd:QNames and URIs.</span></p>
+</div></div>
</section>
<section id="naming-conventions">
-<h3><span class="secno">2.5 </span>Naming Conventions</h3>
-<p>Element names are aligned with [<cite><a class="bibref" href="#bib-PROV-N">PROV-N</a></cite>] record names (e.g. <code>prov:wasGeneratedBy</code>, <code>prov:actedOnBehalfOf</code>) and record parameter roles (e.g. <code>prov:delegate</code>, <code>prov:responsible</code> on a Delegation). Elements are named in camelCase which also conforms with [<cite><a class="bibref" href="#bib-PROV-N">PROV-N</a></cite>] naming conventions.</p>
-<p>ComplexType names are aligned with [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>] type names (e.g. <code>prov:Generation</code>, <code>prov:Delegation</code>). ComplexTypes are named in PascalCase which conforms to [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>] naming conventions and differentiates complexTypes from elements in the schema.</p>
+<h3><span class="secno"><span class="insert">2.6 </span></span><span class="insert">Naming Conventions</span></h3>
+<p><span class="insert">XML element names are aligned with [</span><cite><a class="bibref" href="#bib-PROV-N"><span class="insert">PROV-N</span></a></cite><span class="insert">] </span>record names (e.g. <code>prov:wasGeneratedBy</code>, <code>prov:actedOnBehalfOf</code>) and record parameter roles (e.g. <code>prov:delegate</code>, <code>prov:responsible</code> on a Delegation). <span class="insert">XML </span>Elements are named in camelCase which also conforms with [<cite><a class="bibref" href="#bib-PROV-N">PROV-N</a></cite>] naming conventions.</p>
+<p>ComplexType names are aligned with [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>] <span class="delete">type</span><span class="insert">prov-"type"</span> names (e.g. <code>prov:Generation</code>, <code>prov:Delegation</code>). ComplexTypes are named in PascalCase which conforms to [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>] naming conventions and differentiates complexTypes from <span class="delete">elements</span><span class="insert">xml-elements</span> in the schema.</p>
</section>
</section>
@@ -646,7 +684,7 @@
<section id="schema-components">
<h2><span class="secno">3. </span>PROV XML Schema</h2>
-<p>Provenance concepts, expressed as PROV-DM types and relations, are organized according to six components that are defined in this section.</p>
+<p>Provenance concepts, expressed as <span class="delete">PROV-DM types</span><span class="insert">prov-"types"</span> and <span class="delete">relations,</span><span class="insert">prov-"relations",</span> are organized according to six components that are defined in this section.</p>
<div id="prov-dm-components-ul">
<ul>
@@ -674,181 +712,181 @@
<area title="bundles" href="#component4" coords="268,0,402,201" alt="bundles" shape="rect">
</map>
<br>
-<span class="figcaption" id="prov-dm-components">Figure 1<sup><a class="internalDFN" href="#prov-dm-components"><span class="diamond"> â—Š:</span></a></sup> PROV-DM Components (Informative)</span>
+<span class="figcaption" id="prov-dm-components">Figure 1<sup><a class="internalDFN" href="#prov-dm-components"><span class="diamond"> â—Š:</span></a></sup> PROV-DM Components <span class="delete">(Informative)</span><span class="insert">(Informative, from PROV-DM Fig. 4)</span></span>
<span class="figure" id="fig-generatedID">
</span></span></div>
-<p><a href="#prov-schema-mapping">Table 1</a> is a mapping of PROV-DM types and relations in PROV-XML schema XML types and elements.</p>
+<p><a href="#prov-schema-mapping">Table 1</a> is a mapping of PROV-DM <span class="delete">types</span><span class="insert">prov-"types"</span> and <span class="delete">relations</span><span class="insert">prov-"relations"</span> in PROV-XML schema XML <span class="delete">types</span><span class="insert">complexTypes</span> and <span class="delete">elements.</span><span class="insert">xml-elements.</span></p>
<div id="prov-schema-mapping-div" style="text-align: center;">
<table class="thinborder" style="margin-left: auto; margin-right: auto;">
<caption id="prov-schema-mapping"><span>Table 1<sup><a class="internalDFN" href="#prov-schema-mapping"><span class="diamond"> â—Š:</span></a></sup> </span>PROV-DM Types and Relations to XML Schema Mapping</caption>
<tbody><tr>
-<td><a><b>Type or Relation Name</b></a></td>
+<td><a><b><span class="delete">Type or Relation Name</span><span class="insert">PROV-DM Term / Concept</span></b></a></td>
<td><b>XML Schema ComplexType</b></td>
-<td><b>XML Schema Referencing Element</b></td>
+<td><b>XML Schema <span class="delete">Referencing</span><span class="insert">XML</span> Element</b></td>
<td><b>Component</b></td></tr>
<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
<tr class="component1-color">
- <td><a href="#term-Entity">Entity</a></td>
- <td>prov:Entity</td>
+ <td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-entity">Entity</a></td>
+ <td><a href="#term-Entity">prov:Entity</a></td>
<td>prov:entity</td>
<td rowspan="8"><a href="#component1">Component 1: Entities/Activities</a></td>
</tr>
<tr class="component1-color">
- <td><a href="#term-Activity">Activity</a></td>
- <td>prov:Activity</td>
+ <td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-Activity">Activity</a></td>
+ <td><a href="#term-Activity">prov:Activity</a></td>
<td>prov:activity</td>
</tr>
<tr class="component1-color">
- <td><a href="#term-Generation">Generation</a></td>
- <td>prov:Generation</td>
+ <td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-Generation">Generation</a></td>
+ <td><a href="#term-Generation">prov:Generation</a></td>
<td>prov:wasGeneratedBy</td>
</tr>
<tr class="component1-color">
- <td><a href="#term-Usage">Usage</a></td>
- <td>prov:Usage</td>
+ <td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-Usage">Usage</a></td>
+ <td><a href="#term-Usage">prov:Usage</a></td>
<td>prov:used</td>
</tr>
<tr class="component1-color">
- <td><a href="#term-Communication">Communication</a></td>
- <td>prov:Communication</td>
+ <td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-Communication">Communication</a></td>
+ <td><a href="#term-Communication">prov:Communication</a></td>
<td>prov:wasInformedBy</td>
</tr>
<tr class="component1-color">
- <td><a href="#term-Start">Start</a></td>
- <td>prov:Start</td>
+ <td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-Start">Start</a></td>
+ <td><a href="#term-Start">prov:Start</a></td>
<td>prov:wasStartedBy</td>
</tr>
<tr class="component1-color">
- <td><a href="#term-End">End</a></td>
- <td>prov:End</td>
+ <td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-End">End</a></td>
+ <td><a href="#term-End">prov:End</a></td>
<td>prov:wasEndedBy</td>
</tr>
<tr class="component1-color">
- <td><a href="#term-Invalidation">Invalidation</a></td>
- <td>prov:Invalidation</td>
+ <td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-Invalidation">Invalidation</a></td>
+ <td><a href="#term-Invalidation">prov:Invalidation</a></td>
<td>prov:wasInvalidatedBy</td>
</tr>
<tr>
<td colspan="3" style="border-width: 0px; "></td>
</tr>
<tr class="component2-color">
- <td><a href="#term-Derivation">Derivation</a></td>
- <td>prov:Derivation</td>
+ <td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-Derivation">Derivation</a></td>
+ <td><a href="#term-Derivation">prov:Derivation</a></td>
<td>prov:wasDerivedFrom</td>
<td rowspan="4"><a href="#component2">Component 2: Derivations</a></td>
</tr>
<tr class="component2-color">
- <td><a href="#term-Revision">Revision</a></td>
- <td>prov:Revision</td>
+ <td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-revision">Revision</a></td>
+ <td><a href="#term-Revision">prov:Revision</a></td>
<td>prov:wasRevisionOf</td>
</tr>
<tr class="component2-color">
- <td><a href="#term-Quotation">Quotation</a></td>
- <td>prov:Quotation</td>
+ <td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-quotation">Quotation</a></td>
+ <td><a href="#term-Quotation">prov:Quotation</a></td>
<td>prov:wasQuotedFrom</td>
</tr>
<tr class="component2-color">
- <td><a href="#term-PrimarySource">Primary Source</a></td>
- <td>prov:PrimarySource</td>
+ <td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-primary-source">Primary Source</a></td>
+ <td><a href="#term-PrimarySource">prov:PrimarySource</a></td>
<td>prov:hadPrimarySource</td>
</tr>
<tr>
<td colspan="3" style="border-width: 0px; "></td>
</tr>
<tr class="component3-color" style="border-collapse: collapse; ">
- <td><a href="#term-Agent">Agent</a></td>
- <td>prov:Agent</td>
+ <td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-agent">Agent</a></td>
+ <td><a href="#term-Agent">prov:Agent</a></td>
<td>prov:agent</td>
<td rowspan="9"><a href="#component3">Component 3: Agents, Responsibility, Influence</a></td>
</tr>
<tr class="component3-color">
- <td><a href="#term-Attribution">Attribution</a></td>
- <td>prov:Attribution</td>
+ <td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-attribution">Attribution</a></td>
+ <td><a href="#term-Attribution">prov:Attribution</a></td>
<td>prov:wasAttributedTo</td>
</tr>
<tr class="component3-color">
- <td><a href="#term-Association">Association</a></td>
- <td>prov:Association</td>
+ <td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-Association">Association</a></td>
+ <td><a href="#term-Association">prov:Association</a></td>
<td>prov:wasAssociatedWith</td>
</tr>
<tr class="component3-color">
- <td><a href="#term-Delegation">Delegation</a></td>
- <td>prov:Delegation</td>
+ <td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-delegation">Delegation</a></td>
+ <td><a href="#term-Delegation">prov:Delegation</a></td>
<td>prov:actedOnBehalfOf</td>
</tr>
<tr class="component3-color">
- <td><a href="#term-Plan">Plan</a></td>
- <td>prov:Plan</td>
+ <td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#concept-plan">Plan</a></td>
+ <td><a href="#term-Plan">prov:Plan</a></td>
<td>prov:plan</td>
</tr>
<tr class="component3-color">
- <td><a href="#term-Person">Person</a></td>
- <td>prov:Person</td>
+ <td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#concept-person">Person</a></td>
+ <td><a href="#term-Person">prov:Person</a></td>
<td>prov:person</td>
</tr>
<tr class="component3-color">
- <td><a href="#term-Organization">Organization</a></td>
- <td>prov:Organization</td>
+ <td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#concept-organization">Organization</a></td>
+ <td><a href="#term-Organization">prov:Organization</a></td>
<td>prov:organization</td>
</tr>
<tr class="component3-color">
- <td><a href="#term-SoftwareAgent">Software Agent</a></td>
- <td>prov:SoftwareAgent</td>
+ <td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#concept-software-agent">Software Agent</a></td>
+ <td><a href="#term-SoftwareAgent">prov:SoftwareAgent</a></td>
<td>prov:softwareAgent</td>
</tr>
<tr class="component3-color">
- <td><a href="#term-Influence">Influence</a></td>
- <td>prov:Influence</td>
+ <td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-influence">Influence</a></td>
+ <td><a href="#term-Influence">prov:Influence</a></td>
<td>prov:wasInfluencedBy</td>
</tr>
<tr>
<td colspan="3" style="border-width: 0px; "></td>
</tr>
<tr class="component4-color">
- <td><a href="#term-Bundle">Bundle</a></td>
- <td>prov:Bundle</td>
+ <td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-bundle-entity">Bundle</a></td>
+ <td><a href="#term-Bundle">prov:Bundle</a></td>
<td>prov:bundle</td>
<td rowspan="2"><a href="#component4">Component 4: Bundles</a></td>
</tr>
<tr class="component4-color">
- <td><a href="#term-BundleConstructor">Bundle Constructor</a></td>
- <td>prov:BundleConstructor</td>
+ <td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-bundle">Bundle Constructor</a></td>
+ <td><a href="#term-BundleConstructor">prov:BundleConstructor</a></td>
<td>prov:bundleContent</td>
</tr>
<tr>
<td colspan="3" style="border-width: 0px; "></td>
</tr>
<tr class="component5-color">
- <td><a href="#term-Alternate">Alternate</a></td>
- <td>prov:Alternate</td>
+ <td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-alternate">Alternate</a></td>
+ <td><a href="#term-Alternate">prov:Alternate</a></td>
<td>prov:alternateOf</td>
<td rowspan="3"><a href="#component5">Component 5: Alternate</a></td>
</tr>
<tr class="component5-color">
- <td><a href="#term-Specialization">Specialization</a></td>
- <td>prov:Specialization</td>
+ <td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-specialization">Specialization</a></td>
+ <td><a href="#term-Specialization">prov:Specialization</a></td>
<td>prov:specializationOf</td>
</tr>
<tr>
<td colspan="3" style="border-width: 0px; "></td>
</tr>
<tr class="component6-color">
- <td><a href="#term-Collection">Collection</a></td>
- <td>prov:Collection</td>
+ <td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-collection">Collection</a></td>
+ <td><a href="#term-Collection">prov:Collection</a></td>
<td>prov:collection</td>
<td rowspan="3"><a href="#component6">Component 6: Collections</a></td>
</tr>
<tr class="component6-color">
- <td><a href="#term-EmptyCollection">Empty Collection</a></td>
- <td>prov:EmptyCollection</td>
+ <td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#concept-empty-collection">Empty Collection</a></td>
+ <td><a href="#term-EmptyCollection">prov:EmptyCollection</a></td>
<td>prov:emptyCollection</td>
</tr>
<tr class="component6-color">
- <td><a href="#term-Membership">Membership</a></td>
- <td>prov:Membership</td>
+ <td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-membership">Membership</a></td>
+ <td><a href="#term-Membership">prov:Membership</a></td>
<td>prov:hadMember</td>
</tr>
</tbody></table>
@@ -863,8 +901,8 @@
<section id="term-Entity">
<h4><span class="secno">3.1.1 </span>Entity</h4>
-<span class="glossary-ref"> An <span class="dfn">entity</span> is a physical, digital, conceptual, or other kind of thing with some fixed aspects; entities may be real or imaginary. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Entity">
+<p><span class="insert">From [</span><cite><a class="bibref" href="#bib-PROV-DM"><span class="insert">PROV-DM</span></a></cite><span class="insert">]:</span></p><blockquote><i><span class="glossary-ref"> An <span class="dfn">entity</span> is a physical, digital, conceptual, or other kind of thing with some fixed aspects; entities may be real or imaginary. </span></i></blockquote>
+<p><span class="delete">Type</span><span class="insert">ComplexType</span> definition<span class="insert"> (denoting a similarly named prov-"type")</span> in XML Schema:</p><pre class="schema-type"><xs:complexType name="Entity">
<xs:sequence>
<!-- prov attributes -->
<xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
@@ -876,7 +914,7 @@
<xs:attribute ref="prov:id"/>
</xs:complexType>
</pre>
-<p>The element <code>prov:entity</code> is used to reference a prov:Entity from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="entity" type="prov:Entity"/>
+<p>The <span class="delete">element</span><span class="insert">xml-element</span> <code>prov:entity</code> is used to <span class="delete">reference</span><span class="insert">denote</span> a prov:Entity<span class="insert"> prov-"type"</span> from within a prov:Document or prov:BundleConstructor.</p><p><span class="insert">XML </span>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="entity" type="prov:Entity"/>
</pre>
<div class="example"><div class="example-title"><span>Example 6</span>: prov:entity</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -895,8 +933,8 @@
<section id="term-Activity">
<h4><span class="secno">3.1.2 </span>Activity</h4>
-<span class="glossary-ref"> An <span class="dfn">activity</span> is something that occurs over a period of time and acts upon or with entities; it may include consuming, processing, transforming, modifying, relocating, using, or generating entities. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Activity">
+<p><span class="insert">From [</span><cite><a class="bibref" href="#bib-PROV-DM"><span class="insert">PROV-DM</span></a></cite><span class="insert">]:</span></p><blockquote><i><span class="glossary-ref"> An <span class="dfn">activity</span> is something that occurs over a period of time and acts upon or with entities; it may include consuming, processing, transforming, modifying, relocating, using, or generating entities. </span></i></blockquote>
+<p><span class="delete">Type</span><span class="insert">ComplexType</span> definition<span class="insert"> (denoting a similarly named prov-"type")</span> in XML Schema:</p><pre class="schema-type"><xs:complexType name="Activity">
<xs:sequence>
<xs:element name="startTime" type="xs:dateTime" minOccurs="0"/>
<xs:element name="endTime" type="xs:dateTime" minOccurs="0"/>
@@ -909,7 +947,7 @@
<xs:attribute ref="prov:id"/>
</xs:complexType>
</pre>
-<p>The element <code>prov:activity</code> is used to reference a prov:Activity from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="activity" type="prov:Activity"/>
+<p>The <span class="delete">element</span><span class="insert">xml-element</span> <code>prov:activity</code> is used to <span class="delete">reference</span><span class="insert">denote</span> a prov:Activity<span class="insert"> prov-"type"</span> from within a prov:Document or prov:BundleConstructor.</p><p><span class="insert">XML </span>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="activity" type="prov:Activity"/>
</pre>
<div class="example"><div class="example-title"><span>Example 7</span>: prov:activity</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -917,7 +955,7 @@
xmlns:prov="http://www.w3.org/ns/prov#"
xmlns:ex="http://example.com/ns/ex#">
- <b><prov:activity prov:id="a1">
+ <b><prov:activity <span class="delete">prov:id="a1"></span><span class="insert">prov:id="ex:a1"></span>
<prov:startTime>2011-11-16T16:05:00</prov:startTime>
<prov:endTime>2011-11-16T16:06:00</prov:endTime>
<prov:type xsi:type="xsd:QName">ex:edit</prov:type>
@@ -929,8 +967,8 @@
<section id="term-Generation">
<h4><span class="secno">3.1.3 </span>Generation</h4>
-<span class="glossary-ref"> <span class="dfn">Generation</span> is the completion of production of a new entity by an activity. This entity did not exist before generation and becomes available for usage after this generation. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Generation">
+<p><span class="insert">From [</span><cite><a class="bibref" href="#bib-PROV-DM"><span class="insert">PROV-DM</span></a></cite><span class="insert">]:</span></p><blockquote><i><span class="glossary-ref"> <span class="dfn">Generation</span> is the completion of production of a new entity by an activity. This entity did not exist before generation and becomes available for usage after this generation. </span></i></blockquote>
+<p><span class="delete">Type</span><span class="insert">ComplexType</span> definition<span class="insert"> (denoting a similarly named prov-"type")</span> in XML Schema:</p><pre class="schema-type"><xs:complexType name="Generation">
<xs:sequence>
<xs:element name="entity" type="prov:IDRef"/>
<xs:element name="activity" type="prov:IDRef" minOccurs="0"/>
@@ -945,28 +983,28 @@
<xs:attribute ref="prov:id"/>
</xs:complexType>
</pre>
-<p>The element <code>prov:wasGeneratedBy</code> is used to reference a prov:Generation from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasGeneratedBy" type="prov:Generation"/>
+<p>The <span class="delete">element</span><span class="insert">xml-element</span> <code>prov:wasGeneratedBy</code> is used to <span class="delete">reference</span><span class="insert">denote</span> a prov:Generation<span class="insert"> prov-"type"</span> from within a prov:Document or prov:BundleConstructor.</p><p><span class="insert">XML </span>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasGeneratedBy" type="prov:Generation"/>
</pre>
<div class="example"><div class="example-title"><span>Example 8</span>: prov:wasGeneratedBy</div><pre class="example"><prov:document
xmlns:prov="http://www.w3.org/ns/prov#"
xmlns:ex="http://example.com/ns/ex#">
- <prov:entity prov:id="e1"/>
-
- <prov:activity prov:id="a1"/>
+ <prov:entity <span class="delete">prov:id="e1"/></span><span class="insert">prov:id="ex:e1"/></span>
+
+ <prov:activity <span class="delete">prov:id="a1"/></span><span class="insert">prov:id="ex:a1"/></span>
<b><prov:wasGeneratedBy>
- <prov:entity prov:ref="e1"/>
- <prov:activity prov:ref="a1"/>
+ <prov:entity <span class="delete">prov:ref="e1"/></span><span class="insert">prov:ref="ex:e1"/></span>
+ <prov:activity <span class="delete">prov:ref="a1"/></span><span class="insert">prov:ref="ex:a1"/></span>
<prov:time>2001-10-26T21:32:52</prov:time>
<ex:port>p1</ex:port>
</prov:wasGeneratedBy></b>
- <prov:entity prov:id="e2"/>
+ <prov:entity <span class="delete">prov:id="e2"/></span><span class="insert">prov:id="ex:e2"/></span>
<b><prov:wasGeneratedBy>
- <prov:entity prov:ref="e2"/>
- <prov:activity prov:ref="a1"/>
+ <prov:entity <span class="delete">prov:ref="e2"/></span><span class="insert">prov:ref="ex:e2"/></span>
+ <prov:activity <span class="delete">prov:ref="a1"/></span><span class="insert">prov:ref="ex:a1"/></span>
<prov:time>2001-10-26T10:00:00</prov:time>
<ex:port>p2</ex:port>
</prov:wasGeneratedBy></b>
@@ -976,8 +1014,8 @@
<section id="term-Usage">
<h4><span class="secno">3.1.4 </span>Usage</h4>
-<span class="glossary-ref"> <span class="dfn">Usage</span> is the beginning of utilizing an entity by an activity. Before usage, the activity had not begun to utilize this entity and could not have been affected by the entity. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Usage">
+<p><span class="insert">From [</span><cite><a class="bibref" href="#bib-PROV-DM"><span class="insert">PROV-DM</span></a></cite><span class="insert">]:</span></p><blockquote><i><span class="glossary-ref"> <span class="dfn">Usage</span> is the beginning of utilizing an entity by an activity. Before usage, the activity had not begun to utilize this entity and could not have been affected by the entity. </span></i></blockquote>
+<p><span class="delete">Type</span><span class="insert">ComplexType</span> definition<span class="insert"> (denoting a similarly named prov-"type")</span> in XML Schema:</p><pre class="schema-type"><xs:complexType name="Usage">
<xs:sequence>
<xs:element name="activity" type="prov:IDRef"/>
<xs:element name="entity" type="prov:IDRef" minOccurs="0"/>
@@ -992,28 +1030,28 @@
<xs:attribute ref="prov:id"/>
</xs:complexType>
</pre>
-<p>The element <code>prov:used</code> is used to reference a prov:Usage from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="used" type="prov:Usage"/>
+<p>The <span class="delete">element</span><span class="insert">xml-element</span> <code>prov:used</code> is used to <span class="delete">reference</span><span class="insert">denote</span> a prov:Usage<span class="insert"> prov-"type"</span> from within a prov:Document or prov:BundleConstructor.</p><p><span class="insert">XML </span>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="used" type="prov:Usage"/>
</pre>
<div class="example"><div class="example-title"><span>Example 9</span>: prov:used</div><pre class="example"><prov:document
xmlns:prov="http://www.w3.org/ns/prov#"
xmlns:ex="http://example.com/ns/ex#">
- <prov:activity prov:id="a1"/>
-
- <prov:entity prov:id="e1"/>
-
- <prov:entity prov:id="e2"/>
+ <prov:activity <span class="delete">prov:id="a1"/></span><span class="insert">prov:id="ex:a1"/></span>
+
+ <prov:entity <span class="delete">prov:id="e1"/></span><span class="insert">prov:id="ex:e1"/></span>
+
+ <prov:entity <span class="delete">prov:id="e2"/></span><span class="insert">prov:id="ex:e2"/></span>
<b><prov:used>
- <prov:activity prov:ref="a1"/>
- <prov:entity prov:ref="e1"/>
+ <prov:activity <span class="delete">prov:ref="a1"/></span><span class="insert">prov:ref="ex:a1"/></span>
+ <prov:entity <span class="delete">prov:ref="e1"/></span><span class="insert">prov:ref="ex:e1"/></span>
<prov:time≶2011-11-16T16:00:00</prov:time>
<ex:parameter>p1</ex:parameter>
</prov:used></b>
<b><prov:used>
- <prov:activity prov:ref="a1"/>
- <prov:entity prov:ref="e2"/>
+ <prov:activity <span class="delete">prov:ref="a1"/></span><span class="insert">prov:ref="ex:a1"/></span>
+ <prov:entity <span class="delete">prov:ref="e2"/></span><span class="insert">prov:ref="ex:e2"/></span>
<prov:time>2011-11-16T16:00:01</prov:time>
<ex:parameter>p2</ex:parameter>
</prov:used></b>
@@ -1023,8 +1061,8 @@
<section id="term-Communication">
<h4><span class="secno">3.1.5 </span>Communication</h4>
-<span class="glossary-ref"> <span class="dfn">Communication</span> is the exchange of some unspecified entity by two activities, one activity using some entity generated by the other. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Communication">
+<p><span class="insert">From [</span><cite><a class="bibref" href="#bib-PROV-DM"><span class="insert">PROV-DM</span></a></cite><span class="insert">]:</span></p><blockquote><i><span class="glossary-ref"> <span class="dfn">Communication</span> is the exchange of some unspecified entity by two activities, one activity using some entity generated by the other. </span></i></blockquote>
+<p><span class="delete">Type</span><span class="insert">ComplexType</span> definition<span class="insert"> (denoting a similarly named prov-"type")</span> in XML Schema:</p><pre class="schema-type"><xs:complexType name="Communication">
<xs:sequence>
<xs:element name="informed" type="prov:IDRef"/>
<xs:element name="informant" type="prov:IDRef"/>
@@ -1036,24 +1074,25 @@
<xs:attribute ref="prov:id"/>
</xs:complexType>
</pre>
-<p>The element <code>prov:wasInformedBy</code> is used to reference a prov:Communication from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasInformedBy" type="prov:Communication"/>
+<p>The <span class="delete">element</span><span class="insert">xml-element</span> <code>prov:wasInformedBy</code> is used to <span class="delete">reference</span><span class="insert">denote</span> a prov:Communication<span class="insert"> prov-"type"</span> from within a prov:Document or prov:BundleConstructor.</p><p><span class="insert">XML </span>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasInformedBy" type="prov:Communication"/>
</pre>
<div class="example"><div class="example-title"><span>Example 10</span>: prov:wasInformedBy</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
- xmlns:prov="http://www.w3.org/ns/prov#">
-
- <prov:activity prov:id="a1">
+ <span class="delete">xmlns:prov="http://www.w3.org/ns/prov#"></span><span class="insert">xmlns:prov="http://www.w3.org/ns/prov#"
+ xmlns:ex="http://example.com/ns/ex#"></span>
+
+ <prov:activity <span class="delete">prov:id="a1"></span><span class="insert">prov:id="ex:a1"></span>
<prov:type xsi:type="xsd:string">traffic regulations enforcing<prov:type>
</prov:activity>
- <prov:activity prov:id="a2">
+ <prov:activity <span class="delete">prov:id="a2"></span><span class="insert">prov:id="ex:a2"></span>
<prov:type xsi:type="xsd:string">fine paying, check writing, and mailing</prov:type>
</prov:activity>
<b><prov:wasInformedBy>
- <prov:informed prov:ref="a2"/>
- <prov:informant prov:ref="a1"/>
+ <prov:informed <span class="delete">prov:ref="a2"/></span><span class="insert">prov:ref="ex:a2"/></span>
+ <prov:informant <span class="delete">prov:ref="a1"/></span><span class="insert">prov:ref="ex:a1"/></span>
</prov:wasInformedBy></b>
</prov:document></pre></div>
@@ -1061,8 +1100,8 @@
<section id="term-Start">
<h4><span class="secno">3.1.6 </span>Start</h4>
-<span class="glossary-ref"> <span class="dfn">Start</span> is when an activity is deemed to have been started by an entity, known as <span class="dfn">trigger</span>. The activity did not exist before its start. Any usage, generation, or invalidation involving an activity follows the activity's start. A start may refer to a trigger entity that set off the activity, or to an activity, known as <span class="dfn">starter</span>, that generated the trigger. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Start">
+<p><span class="insert">From [</span><cite><a class="bibref" href="#bib-PROV-DM"><span class="insert">PROV-DM</span></a></cite><span class="insert">]:</span></p><blockquote><i><span class="glossary-ref"> <span class="dfn">Start</span> is when an activity is deemed to have been started by an entity, known as <span class="dfn">trigger</span>. The activity did not exist before its start. Any usage, generation, or invalidation involving an activity follows the activity's start. A start may refer to a trigger entity that set off the activity, or to an activity, known as <span class="dfn">starter</span>, that generated the trigger. </span></i></blockquote>
+<p><span class="delete">Type</span><span class="insert">ComplexType</span> definition<span class="insert"> (denoting a similarly named prov-"type")</span> in XML Schema:</p><pre class="schema-type"><xs:complexType name="Start">
<xs:sequence>
<xs:element name="activity" type="prov:IDRef"/>
<xs:element name="trigger" type="prov:IDRef" minOccurs="0"/>
@@ -1078,7 +1117,7 @@
<xs:attribute ref="prov:id"/>
</xs:complexType>
</pre>
-<p>The element <code>prov:wasStartedBy</code> is used to reference a prov:Start from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasStartedBy" type="prov:Start"/>
+<p>The <span class="delete">element</span><span class="insert">xml-element</span> <code>prov:wasStartedBy</code> is used to <span class="delete">reference</span><span class="insert">denote</span> a prov:Start<span class="insert"> prov-"type"</span> from within a prov:Document or prov:BundleConstructor.</p><p><span class="insert">XML </span>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasStartedBy" type="prov:Start"/>
</pre>
<div class="example"><div class="example-title"><span>Example 11</span>: prov:wasStartedBy</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -1086,44 +1125,44 @@
xmlns:prov="http://www.w3.org/ns/prov#"
xmlns:ex="http://example.com/ns/ex#">
- <prov:entity prov:id="e1">
+ <prov:entity <span class="delete">prov:id="e1"></span><span class="insert">prov:id="ex:e1"></span>
<prov:type xsi:type="xsd:string">email message</prov:type>
</prov:entity>
- <prov:activity prov:id="a1">
+ <prov:activity <span class="delete">prov:id="a1"></span><span class="insert">prov:id="ex:a1"></span>
<prov:type xsi:type="xsd:QName">Discuss</prov:type>
</prov:activity>
<b><prov:wasStartedBy>
- <prov:activity prov:ref="a1"/>
- <prov:trigger prov:ref="e1"/>
+ <prov:activity <span class="delete">prov:ref="a1"/></span><span class="insert">prov:ref="ex:a1"/></span>
+ <prov:trigger <span class="delete">prov:ref="e1"/></span><span class="insert">prov:ref="ex:e1"/></span>
<prov:time>2011-11-16T16:05:00</prov:time>
</prov:wasStartedBy></b>
<prov:used>
- <prov:activity prov:ref="a1"/>
- <prov:entity prov:ref="e1"/>
+ <prov:activity <span class="delete">prov:ref="a1"/></span><span class="insert">prov:ref="ex:a1"/></span>
+ <prov:entity <span class="delete">prov:ref="e1"/></span><span class="insert">prov:ref="ex:e1"/></span>
</prov:used>
- <prov:activity prov:id="a0">
+ <prov:activity <span class="delete">prov:id="a0"></span><span class="insert">prov:id="ex:a0"></span>
<prov:type xsi:type="xsd:QName">Write</prov:type>
</prov:activity>
<prov:wasGeneratedBy>
- <prov:entity prov:ref="e1"/>
- <prov:activity prov:ref="a0"/>
+ <prov:entity <span class="delete">prov:ref="e1"/></span><span class="insert">prov:ref="ex:e1"/></span>
+ <prov:activity <span class="delete">prov:ref="a0"/></span><span class="insert">prov:ref="ex:a0"/></span>
</prov:wasGeneratedBy>
<b><prov:wasStartedBy>
- <prov:activity prov:ref="a1"/>
- <prov:trigger prov:ref="e1"/>
- <prov:starter prov:ref="a0"/>
+ <prov:activity <span class="delete">prov:ref="a1"/></span><span class="insert">prov:ref="ex:a1"/></span>
+ <prov:trigger <span class="delete">prov:ref="e1"/></span><span class="insert">prov:ref="ex:e1"/></span>
+ <prov:starter <span class="delete">prov:ref="a0"/></span><span class="insert">prov:ref="ex:a0"/></span>
<prov:time>2011-11-16T16:05:00</prov:time>
</prov:wasStartedBy></b>
<b><prov:wasStartedBy>
- <prov:activity prov:ref="a1"/>
- <prov:starter prov:ref="a0"/>
+ <prov:activity <span class="delete">prov:ref="a1"/></span><span class="insert">prov:ref="ex:a1"/></span>
+ <prov:starter <span class="delete">prov:ref="a0"/></span><span class="insert">prov:ref="ex:a0"/></span>
<prov:time>2011-11-16T16:05:00</prov:time>
</prov:wasStartedBy></b>
@@ -1132,8 +1171,8 @@
<section id="term-End">
<h4><span class="secno">3.1.7 </span>End</h4>
-<span class="glossary-ref"> <span class="dfn">End</span> is when an activity is deemed to have been ended by an entity, known as <span class="dfn">trigger</span>. The activity no longer exists after its end. Any usage, generation, or invalidation involving an activity precedes the activity's end. An end may refer to a trigger entity that terminated the activity, or to an activity, known as <span class="dfn">ender</span> that generated the trigger. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="End">
+<p><span class="insert">From [</span><cite><a class="bibref" href="#bib-PROV-DM"><span class="insert">PROV-DM</span></a></cite><span class="insert">]:</span></p><blockquote><i><span class="glossary-ref"> <span class="dfn">End</span> is when an activity is deemed to have been ended by an entity, known as <span class="dfn">trigger</span>. The activity no longer exists after its end. Any usage, generation, or invalidation involving an activity precedes the activity's end. An end may refer to a trigger entity that terminated the activity, or to an activity, known as <span class="dfn">ender</span> that generated the trigger. </span></i></blockquote>
+<p><span class="delete">Type</span><span class="insert">ComplexType</span> definition<span class="insert"> (denoting a similarly named prov-"type")</span> in XML Schema:</p><pre class="schema-type"><xs:complexType name="End">
<xs:sequence>
<xs:element name="activity" type="prov:IDRef"/>
<xs:element name="trigger" type="prov:IDRef" minOccurs="0"/>
@@ -1149,7 +1188,7 @@
<xs:attribute ref="prov:id"/>
</xs:complexType>
</pre>
-<p>The element <code>prov:wasEndedBy</code> is used to reference a prov:End from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasEndedBy" type="prov:End"/>
+<p>The <span class="delete">element</span><span class="insert">xml-element</span> <code>prov:wasEndedBy</code> is used to <span class="delete">reference</span><span class="insert">denote</span> a prov:End<span class="insert"> prov-"type"</span> from within a prov:Document or prov:BundleConstructor.</p><p><span class="insert">XML </span>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasEndedBy" type="prov:End"/>
</pre>
<div class="example"><div class="example-title"><span>Example 12</span>: prov:wasEndedBy</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -1157,17 +1196,17 @@
xmlns:prov="http://www.w3.org/ns/prov#"
xmlns:ex="http://example.com/ns/ex#">
- <prov:entity prov:id="e1">
+ <prov:entity <span class="delete">prov:id="e1"></span><span class="insert">prov:id="ex:e1"></span>
<prov:type xsi:type="xsd:string">approval document</prov:type>
</prov:entity>
- <prov:activity prov:id="a1">
+ <prov:activity <span class="delete">prov:id="a1"></span><span class="insert">prov:id="ex:a1"></span>
<prov:type xsi:type="xsd:QName">Editing</prov:type>
</prov:activity>
<b><prov:wasEndedBy>
- <prov:activity prov:ref="a1"/>
- <prov:trigger prov:ref="e1"/>
+ <prov:activity <span class="delete">prov:ref="a1"/></span><span class="insert">prov:ref="ex:a1"/></span>
+ <prov:trigger <span class="delete">prov:ref="e1"/></span><span class="insert">prov:ref="ex:e1"/></span>
</prov:wasEndedBy></b>
</prov:document></pre></div>
@@ -1175,8 +1214,8 @@
<section id="term-Invalidation">
<h4><span class="secno">3.1.8 </span>Invalidation</h4>
-<span class="glossary-ref"> <span class="dfn">Invalidation</span> is the start of the destruction, cessation, or expiry of an existing entity by an activity. The entity is no longer available for use (or further invalidation) after invalidation. Any generation or usage of an entity precedes its invalidation.</span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Invalidation">
+<p><span class="insert">From [</span><cite><a class="bibref" href="#bib-PROV-DM"><span class="insert">PROV-DM</span></a></cite><span class="insert">]:</span></p><blockquote><i><span class="glossary-ref"> <span class="dfn">Invalidation</span> is the start of the destruction, cessation, or expiry of an existing entity by an activity. The entity is no longer available for use (or further invalidation) after invalidation. Any generation or usage of an entity precedes its invalidation.</span></i></blockquote>
+<p><span class="delete">Type</span><span class="insert">ComplexType</span> definition<span class="insert"> (denoting a similarly named prov-"type")</span> in XML Schema:</p><pre class="schema-type"><xs:complexType name="Invalidation">
<xs:sequence>
<xs:element name="entity" type="prov:IDRef"/>
<xs:element name="activity" type="prov:IDRef" minOccurs="0"/>
@@ -1191,7 +1230,7 @@
<xs:attribute ref="prov:id"/>
</xs:complexType>
</pre>
-<p>The element <code>prov:wasInvalidatedBy</code> is used to reference a prov:Invalidation from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasInvalidatedBy" type="prov:Invalidation"/>
+<p>The <span class="delete">element</span><span class="insert">xml-element</span> <code>prov:wasInvalidatedBy</code> is used to <span class="delete">reference</span><span class="insert">denote</span> a prov:Invalidation<span class="insert"> prov-"type"</span> from within a prov:Document or prov:BundleConstructor.</p><p><span class="insert">XML </span>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasInvalidatedBy" type="prov:Invalidation"/>
</pre>
<div class="example"><div class="example-title"><span>Example 13</span>: prov:wasInvalidatedBy</div><pre class="example"><prov:document
xmlns:prov="http://www.w3.org/ns/prov#"
@@ -1224,12 +1263,12 @@
<section id="component2">
<h3><span class="secno">3.2 </span>Component 2: Derivations</h3>
-<p>The second component of PROV-DM is concerned with: <a title="derivation" href="#term-Derivation">derivations</a> of <a title="entity">entities</a> from other entities and derivation subtypes WasRevisionOf (<a href="#term-Revision">Revision</a>), WasQuotedFrom (<a href="#term-Quotation">Quotation</a>), and HasPrimarySource (<a href="#term-PrimarySource">Primary Source</a>).</p>
+<p>The second component of PROV-DM is concerned with: <a title="derivation" href="#term-Derivation">derivations</a> of <a title="entity">entities</a> from other entities and derivation subtypes<span class="delete"> WasRevisionOf (</span><a href="#term-Revision">Revision</a><span class="delete">), WasQuotedFrom (</span><span class="insert">, </span><a href="#term-Quotation">Quotation</a><span class="delete">),</span><span class="insert">,</span> and <span class="delete">HasPrimarySource (</span><a href="#term-PrimarySource">Primary Source</a><span class="delete">).</span><span class="insert">.</span></p>
<section id="term-Derivation">
<h4><span class="secno">3.2.1 </span>Derivation</h4>
-<span class="glossary-ref"> A <span class="dfn">derivation</span> is a transformation of an entity into another, an update of an entity resulting in a new one, or the construction of a new entity based on a pre-existing entity.</span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Derivation">
+<p><span class="insert">From [</span><cite><a class="bibref" href="#bib-PROV-DM"><span class="insert">PROV-DM</span></a></cite><span class="insert">]:</span></p><blockquote><i><span class="glossary-ref"> A <span class="dfn">derivation</span> is a transformation of an entity into another, an update of an entity resulting in a new one, or the construction of a new entity based on a pre-existing entity.</span></i></blockquote>
+<p><span class="delete">Type</span><span class="insert">ComplexType</span> definition<span class="insert"> (denoting a similarly named prov-"type")</span> in XML Schema:</p><pre class="schema-type"><xs:complexType name="Derivation">
<xs:sequence>
<xs:element name="generatedEntity" type="prov:IDRef"/>
<xs:element name="usedEntity" type="prov:IDRef"/>
@@ -1244,25 +1283,26 @@
<xs:attribute ref="prov:id"/>
</xs:complexType>
</pre>
-<p>The element <code>prov:wasDerivedFrom</code> is used to reference a prov:Derivation from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasDerivedFrom" type="prov:Derivation"/>
+<p>The <span class="delete">element</span><span class="insert">xml-element</span> <code>prov:wasDerivedFrom</code> is used to <span class="delete">reference</span><span class="insert">denote</span> a prov:Derivation<span class="insert"> prov-"type"</span> from within a prov:Document or prov:BundleConstructor.</p><p><span class="insert">XML </span>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasDerivedFrom" type="prov:Derivation"/>
</pre>
<div class="example"><div class="example-title"><span>Example 14</span>: prov:wasDerivedFrom</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
- xmlns:prov="http://www.w3.org/ns/prov#">
-
- <prov:entity prov:id="e1"/>
-
- <prov:entity prov:id="e2"/>
+ <span class="delete">xmlns:prov="http://www.w3.org/ns/prov#"></span><span class="insert">xmlns:prov="http://www.w3.org/ns/prov#"
+ xmlns:ex="http://example.com/ns/ex#"></span>
+
+ <prov:entity <span class="delete">prov:id="e1"/></span><span class="insert">prov:id="ex:e1"/></span>
+
+ <prov:entity <span class="delete">prov:id="e2"/></span><span class="insert">prov:id="ex:e2"/></span>
<b><prov:wasDerivedFrom>
- <prov:generatedEntity prov:ref="e2"/>
- <prov:usedEntity prov:ref="e1"/>
+ <prov:generatedEntity <span class="delete">prov:ref="e2"/></span><span class="insert">prov:ref="ex:e2"/></span>
+ <prov:usedEntity <span class="delete">prov:ref="e1"/></span><span class="insert">prov:ref="ex:e1"/></span>
</prov:wasDerivedFrom></b>
<b><prov:wasDerivedFrom>
- <prov:generatedEntity prov:ref="e2"/>
- <prov:usedEntity prov:ref="e1"/>
+ <prov:generatedEntity <span class="delete">prov:ref="e2"/></span><span class="insert">prov:ref="ex:e2"/></span>
+ <prov:usedEntity <span class="delete">prov:ref="e1"/></span><span class="insert">prov:ref="ex:e1"/></span>
<prov:type xsi:type="xsd:string">physical transform</prov:type>
</prov:wasDerivedFrom></b>
@@ -1271,15 +1311,15 @@
<section id="term-Revision">
<h4><span class="secno">3.2.2 </span>Revision</h4>
-<span class="glossary-ref"> A <span class="dfn">revision</span> is a derivation for which the resulting entity is a revised version of some original. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Revision">
+<p><span class="insert">From [</span><cite><a class="bibref" href="#bib-PROV-DM"><span class="insert">PROV-DM</span></a></cite><span class="insert">]:</span></p><blockquote><i><span class="glossary-ref"> A <span class="dfn">revision</span> is a derivation for which the resulting entity is a revised version of some original. </span></i></blockquote>
+<p><span class="delete">Type</span><span class="insert">ComplexType</span> definition<span class="insert"> (denoting a similarly named prov-"type")</span> in XML Schema:</p><pre class="schema-type"><xs:complexType name="Revision">
<xs:complexContent>
<xs:extension base="prov:Derivation">
</xs:extension>
</xs:complexContent>
</xs:complexType>
</pre>
-<p>The element <code>prov:wasRevisionOf</code> is used to reference a prov:Revision from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasRevisionOf" type="prov:Revision"/>
+<p>The <span class="delete">element</span><span class="insert">xml-element</span> <code>prov:wasRevisionOf</code> is used to <span class="delete">reference</span><span class="insert">denote</span> a prov:Revision<span class="insert"> prov-"type"</span> from within a prov:Document or prov:BundleConstructor.</p><p><span class="insert">XML </span>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasRevisionOf" type="prov:Revision"/>
</pre>
<div class="example"><div class="example-title"><span>Example 15</span>: prov:wasRevisionOf</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -1306,15 +1346,15 @@
<section id="term-Quotation">
<h4><span class="secno">3.2.3 </span>Quotation</h4>
-<span class="glossary-ref"> A <span class="dfn">quotation</span> is the repeat of (some or all of) an entity, such as text or image, by someone who may or may not be its original author. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Quotation">
+<p><span class="insert">From [</span><cite><a class="bibref" href="#bib-PROV-DM"><span class="insert">PROV-DM</span></a></cite><span class="insert">]:</span></p><blockquote><i><span class="glossary-ref"> A <span class="dfn">quotation</span> is the repeat of (some or all of) an entity, such as text or image, by someone who may or may not be its original author. </span></i></blockquote>
+<p><span class="delete">Type</span><span class="insert">ComplexType</span> definition<span class="insert"> (denoting a similarly named prov-"type")</span> in XML Schema:</p><pre class="schema-type"><xs:complexType name="Quotation">
<xs:complexContent>
<xs:extension base="prov:Derivation">
</xs:extension>
</xs:complexContent>
</xs:complexType>
</pre>
-<p>The element <code>prov:wasQuotedFrom</code> is used to reference a prov:Quotation from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasQuotedFrom" type="prov:Quotation"/>
+<p>The <span class="delete">element</span><span class="insert">xml-element</span> <code>prov:wasQuotedFrom</code> is used to <span class="delete">reference</span><span class="insert">denote</span> a prov:Quotation<span class="insert"> prov-"type"</span> from within a prov:Document or prov:BundleConstructor.</p><p><span class="insert">XML </span>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasQuotedFrom" type="prov:Quotation"/>
</pre>
<div class="example"><div class="example-title"><span>Example 16</span>: prov:wasQuotedFrom</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -1352,15 +1392,15 @@
<section id="term-PrimarySource">
<h4><span class="secno">3.2.4 </span>Primary Source</h4>
-<span class="glossary-ref"> A <span class="dfn">primary source</span> for a topic refers to something produced by some agent with direct experience and knowledge about the topic, at the time of the topic's study, without benefit from hindsight. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="PrimarySource">
+<p><span class="insert">From [</span><cite><a class="bibref" href="#bib-PROV-DM"><span class="insert">PROV-DM</span></a></cite><span class="insert">]:</span></p><blockquote><i><span class="glossary-ref"> A <span class="dfn">primary source</span> for a topic refers to something produced by some agent with direct experience and knowledge about the topic, at the time of the topic's study, without benefit from hindsight. </span></i></blockquote>
+<p><span class="delete">Type</span><span class="insert">ComplexType</span> definition<span class="insert"> (denoting a similarly named prov-"type")</span> in XML Schema:</p><pre class="schema-type"><xs:complexType name="PrimarySource">
<xs:complexContent>
<xs:extension base="prov:Derivation">
</xs:extension>
</xs:complexContent>
</xs:complexType>
</pre>
-<p>The element <code>prov:hadPrimarySource</code> is used to reference a prov:PrimarySource from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="hadPrimarySource" type="prov:PrimarySource"/>
+<p>The <span class="delete">element</span><span class="insert">xml-element</span> <code>prov:hadPrimarySource</code> is used to <span class="delete">reference</span><span class="insert">denote</span> a prov:PrimarySource<span class="insert"> prov-"type"</span> from within a prov:Document or prov:BundleConstructor.</p><p><span class="insert">XML </span>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="hadPrimarySource" type="prov:PrimarySource"/>
</pre>
<div class="example"><div class="example-title"><span>Example 17</span>: prov:hadPrimarySource</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -1389,13 +1429,13 @@
<section id="component3">
<h3><span class="secno">3.3 </span>Component 3: Agents, Responsibility, and Influence</h3>
-<p>The third component of PROV-DM is concerned with <a title="agent">agents</a> and the relations WasAttributedTo
-(<a href="#term-Attribution">Attribution</a>), WasAssociatedWith (<a href="#term-Association">Association</a>), ActedOnBehalfOf (<a href="#term-Delegation">Delegation</a>), relating agents to entities, activities, and agents, respectively.</p>
+<p>The third component of PROV-DM is concerned with <a title="agent">agents</a> and the relations <span class="delete">WasAttributedTo
+(</span><a href="#term-Attribution">Attribution</a><span class="delete">), WasAssociatedWith (</span><span class="insert">, </span><a href="#term-Association">Association</a><span class="delete">), ActedOnBehalfOf (</span><span class="insert">, and </span><a href="#term-Delegation">Delegation</a><span class="delete">),</span><span class="insert">,</span> relating agents to entities, activities, and agents, respectively.</p>
<section id="term-Agent">
<h4><span class="secno">3.3.1 </span>Agent</h4>
-<span class="glossary-ref"> An <span class="dfn">agent</span> is something that bears some form of responsibility for an activity taking place, for the existence of an entity, or for another agent's activity. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Agent">
+<p><span class="insert">From [</span><cite><a class="bibref" href="#bib-PROV-DM"><span class="insert">PROV-DM</span></a></cite><span class="insert">]:</span></p><blockquote><i><span class="glossary-ref"> An <span class="dfn">agent</span> is something that bears some form of responsibility for an activity taking place, for the existence of an entity, or for another agent's activity. </span></i></blockquote>
+<p><span class="delete">Type</span><span class="insert">ComplexType</span> definition<span class="insert"> (denoting a similarly named prov-"type")</span> in XML Schema:</p><pre class="schema-type"><xs:complexType name="Agent">
<xs:sequence>
<!-- prov attributes -->
<xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
@@ -1406,7 +1446,7 @@
<xs:attribute ref="prov:id"/>
</xs:complexType>
</pre>
-<p>The element <code>prov:agent</code> is used to reference a prov:Agent from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="agent" type="prov:Agent"/>
+<p>The <span class="delete">element</span><span class="insert">xml-element</span> <code>prov:agent</code> is used to <span class="delete">reference</span><span class="insert">denote</span> a prov:Agent<span class="insert"> prov-"type"</span> from within a prov:Document or prov:BundleConstructor.</p><p><span class="insert">XML </span>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="agent" type="prov:Agent"/>
</pre>
<div class="example"><div class="example-title"><span>Example 18</span>: prov:agent</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -1414,7 +1454,7 @@
xmlns:prov="http://www.w3.org/ns/prov#"
xmlns:ex="http://example.com/ns/ex#">
- <b><prov:agent prov:id="e1">
+ <b><prov:agent <span class="delete">prov:id="e1"></span><span class="insert">prov:id="ex:e1"></span>
<prov:type xsi:type="xsd:QName">prov:Person</prov:type>
<ex:name>Alice</ex:name>
<ex:employee>1234</ex:employee>
@@ -1424,15 +1464,15 @@
<section id="term-Person">
<h5><span class="secno">3.3.1.1 </span>Person</h5>
-<span class="glossary-ref"> Agents of type <span class="dfn">Person</span> are people. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Person">
+<p><span class="insert">From [</span><cite><a class="bibref" href="#bib-PROV-DM"><span class="insert">PROV-DM</span></a></cite><span class="insert">]:</span></p><blockquote><i><span class="glossary-ref"> <span class="delete">Agents of type </span><span class="dfn">Person</span><span class="insert"> agents</span> are people. </span></i></blockquote>
+<p><span class="delete">Type</span><span class="insert">ComplexType</span> definition<span class="insert"> (denoting a similarly named prov-"type")</span> in XML Schema:</p><pre class="schema-type"><xs:complexType name="Person">
<xs:complexContent>
<xs:extension base="prov:Agent">
</xs:extension>
</xs:complexContent>
</xs:complexType>
</pre>
-<p>The element <code>prov:person</code> is used to reference a prov:Person from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="person" type="prov:Person"/>
+<p>The <span class="delete">element</span><span class="insert">xml-element</span> <code>prov:person</code> is used to <span class="delete">reference</span><span class="insert">denote</span> a prov:Person<span class="insert"> prov-"type"</span> from within a prov:Document or prov:BundleConstructor.</p><p><span class="insert">XML </span>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="person" type="prov:Person"/>
</pre>
<div class="example"><div class="example-title"><span>Example 19</span>: prov:person</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -1447,21 +1487,21 @@
<section id="term-Organization">
<h5><span class="secno">3.3.1.2 </span>Organization</h5>
-<span class="glossary-ref"> Agents of type <span class="dfn">Organization</span> are social or legal institutions such as companies, societies, etc. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Organization">
+<p><span class="insert">From [</span><cite><a class="bibref" href="#bib-PROV-DM"><span class="insert">PROV-DM</span></a></cite><span class="insert">]:</span></p><blockquote><i><span class="glossary-ref"> <span class="delete">Agents of type</span><span class="insert">An</span> <span class="dfn"><span class="delete">Organization</span><span class="delete"> are</span><span class="insert">organization</span></span><span class="insert"> is a</span> social or legal <span class="delete">institutions</span><span class="insert">institution</span> such as <span class="delete">companies, societies,</span><span class="insert">a company, society,</span> etc. </span></i></blockquote>
+<p><span class="delete">Type</span><span class="insert">ComplexType</span> definition<span class="insert"> (denoting a similarly named prov-"type")</span> in XML Schema:</p><pre class="schema-type"><xs:complexType name="Organization">
<xs:complexContent>
<xs:extension base="prov:Agent">
</xs:extension>
</xs:complexContent>
</xs:complexType>
</pre>
-<p>The element <code>prov:organization</code> is used to reference a prov:Organization from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="organization" type="prov:Organization"/>
+<p>The <span class="delete">element</span><span class="insert">xml-element</span> <code>prov:organization</code> is used to <span class="delete">reference</span><span class="insert">denote</span> a prov:Organization<span class="insert"> prov-"type"</span> from within a prov:Document or prov:BundleConstructor.</p><p><span class="insert">XML </span>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="organization" type="prov:Organization"/>
</pre>
<div class="example"><div class="example-title"><span>Example 20</span>: prov:organization</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:prov="http://www.w3.org/ns/prov#"
- xmlns:ex="http://example.com/ns/ex#">
+ <span class="delete">xmlns:ex="http://example.com/ns/ex#"></span><span class="insert">xmlns:w3="http://w3.org/"></span>
<b><prov:organization prov:id="w3:Consortium" /></b>
@@ -1470,15 +1510,15 @@
<section id="term-SoftwareAgent">
<h5><span class="secno">3.3.1.3 </span>Software Agent</h5>
-<span class="glossary-ref"> A <span class="dfn">SoftwareAgent</span> is running software. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="SoftwareAgent">
+<p><span class="insert">From [</span><cite><a class="bibref" href="#bib-PROV-DM"><span class="insert">PROV-DM</span></a></cite><span class="insert">]:</span></p><blockquote><i><span class="glossary-ref"> A <span class="dfn"><span class="delete">SoftwareAgent</span><span class="insert">software agent</span></span> is running software. </span></i></blockquote>
+<p><span class="delete">Type</span><span class="insert">ComplexType</span> definition<span class="insert"> (denoting a similarly named prov-"type")</span> in XML Schema:</p><pre class="schema-type"><xs:complexType name="SoftwareAgent">
<xs:complexContent>
<xs:extension base="prov:Agent">
</xs:extension>
</xs:complexContent>
</xs:complexType>
</pre>
-<p>The element <code>prov:softwareAgent</code> is used to reference a prov:SoftwareAgent from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="softwareAgent" type="prov:SoftwareAgent"/>
+<p>The <span class="delete">element</span><span class="insert">xml-element</span> <code>prov:softwareAgent</code> is used to <span class="delete">reference</span><span class="insert">denote</span> a prov:SoftwareAgent<span class="insert"> prov-"type"</span> from within a prov:Document or prov:BundleConstructor.</p><p><span class="insert">XML </span>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="softwareAgent" type="prov:SoftwareAgent"/>
</pre>
<div class="example"><div class="example-title"><span>Example 21</span>: prov:softwareAgent</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -1486,7 +1526,7 @@
xmlns:prov="http://www.w3.org/ns/prov#"
xmlns:ex="http://example.com/ns/ex#">
- <b><prov:softwareAgent prov:id="ag" /></b>
+ <b><prov:softwareAgent <span class="delete">prov:id="ag"</span><span class="insert">prov:id="ex:ag"</span> /></b>
</prov:document></pre></div>
</section>
@@ -1495,8 +1535,8 @@
<section id="term-Attribution">
<h4><span class="secno">3.3.2 </span>Attribution</h4>
-<span class="glossary-ref"> <span class="dfn">Attribution</span> is the ascribing of an entity to an agent. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Attribution">
+<p><span class="insert">From [</span><cite><a class="bibref" href="#bib-PROV-DM"><span class="insert">PROV-DM</span></a></cite><span class="insert">]:</span></p><blockquote><i><span class="glossary-ref"> <span class="dfn">Attribution</span> is the ascribing of an entity to an agent. </span></i></blockquote>
+<p><span class="delete">Type</span><span class="insert">ComplexType</span> definition<span class="insert"> (denoting a similarly named prov-"type")</span> in XML Schema:</p><pre class="schema-type"><xs:complexType name="Attribution">
<xs:sequence>
<xs:element name="entity" type="prov:IDRef"/>
<xs:element name="agent" type="prov:IDRef"/>
@@ -1508,7 +1548,7 @@
<xs:attribute ref="prov:id"/>
</xs:complexType>
</pre>
-<p>The element <code>prov:wasAttributedTo</code> is used to reference a prov:Attribution from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasAttributedTo" type="prov:Attribution"/>
+<p>The <span class="delete">element</span><span class="insert">xml-element</span> <code>prov:wasAttributedTo</code> is used to <span class="delete">reference</span><span class="insert">denote</span> a prov:Attribution<span class="insert"> prov-"type"</span> from within a prov:Document or prov:BundleConstructor.</p><p><span class="insert">XML </span>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasAttributedTo" type="prov:Attribution"/>
</pre>
<div class="example"><div class="example-title"><span>Example 22</span>: prov:wasAttributedTo</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -1531,13 +1571,13 @@
</prov:entity>
<b><prov:wasAttributedTo>
- <prov:entity prov:ref="rec54:WD"/>
+ <prov:entity <span class="delete">prov:ref="rec54:WD"/></span><span class="insert">prov:ref="tr:WD-prov-dm-20111215"/></span>
<prov:agent prov:ref="ex:Paolo"/>
<prov:type xsi:type="xsd:QName">editorship</prov:type>
</prov:wasAttributedTo></b>
<b><prov:wasAttributedTo>
- <prov:entity prov:ref="rec54:WD"/>
+ <prov:entity <span class="delete">prov:ref="rec54:WD"/></span><span class="insert">prov:ref="tr:WD-prov-dm-20111215"/></span>
<prov:agent prov:ref="ex:Simon"/>
<prov:type xsi:type="xsd:QName">authorship</prov:type>
</prov:wasAttributedTo></b>
@@ -1547,8 +1587,8 @@
<section id="term-Association">
<h4><span class="secno">3.3.3 </span>Association</h4>
-<span class="glossary-ref"> An activity <span class="dfn">association</span> is an assignment of responsibility to an agent for an activity, indicating that the agent had a role in the activity. It further allows for a plan to be specified, which is the plan intended by the agent to achieve some goals in the context of this activity. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Association">
+<p><span class="insert">From [</span><cite><a class="bibref" href="#bib-PROV-DM"><span class="insert">PROV-DM</span></a></cite><span class="insert">]:</span></p><blockquote><i><span class="glossary-ref"> An activity <span class="dfn">association</span> is an assignment of responsibility to an agent for an activity, indicating that the agent had a role in the activity. It further allows for a plan to be specified, which is the plan intended by the agent to achieve some goals in the context of this activity. </span></i></blockquote>
+<p><span class="delete">Type</span><span class="insert">ComplexType</span> definition<span class="insert"> (denoting a similarly named prov-"type")</span> in XML Schema:</p><pre class="schema-type"><xs:complexType name="Association">
<xs:sequence>
<xs:element name="activity" type="prov:IDRef"/>
<xs:element name="agent" type="prov:IDRef" minOccurs="0"/>
@@ -1562,7 +1602,7 @@
<xs:attribute ref="prov:id"/>
</xs:complexType>
</pre>
-<p>The element <code>prov:wasAssociatedWith</code> is used to reference a prov:Association from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasAssociatedWith" type="prov:Association"/>
+<p>The <span class="delete">element</span><span class="insert">xml-element</span> <code>prov:wasAssociatedWith</code> is used to <span class="delete">reference</span><span class="insert">denote</span> a prov:Association<span class="insert"> prov-"type"</span> from within a prov:Document or prov:BundleConstructor.</p><p><span class="insert">XML </span>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasAssociatedWith" type="prov:Association"/>
</pre>
<div class="example"><div class="example-title"><span>Example 23</span>: prov:wasAssociatedWith</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -1570,28 +1610,28 @@
xmlns:prov="http://www.w3.org/ns/prov#"
xmlns:ex="http://example.com/ns/ex#">
- <prov:activity prov:id="a">
+ <prov:activity <span class="delete">prov:id="a"></span><span class="insert">prov:id="ex:a"></span>
<prov:type xsi:type="xsd:string">workflow execution</prov:type>
</prov:activity>
- <prov:agent prov:id="ag1">
+ <prov:agent <span class="delete">prov:id="ag1"></span><span class="insert">prov:id="ex:ag1"></span>
<prov:type xsi:type="xsd:QName">operator</prov:type>
</prov:agent>
- <prov:agent prov:id="ag2">
+ <prov:agent <span class="delete">prov:id="ag2"></span><span class="insert">prov:id="ex:ag2"></span>
<prov:type xsi:type="xsd:QName">designator</prov:type>
</prov:agent>
<b><prov:wasAssociatedWith>
- <prov:activity prov:ref="a"/>
- <prov:agent prov:ref="ag1"/>
+ <prov:activity <span class="delete">prov:ref="a"/></span><span class="insert">prov:ref="ex:a"/></span>
+ <prov:agent <span class="delete">prov:ref="ag1"/></span><span class="insert">prov:ref="ex:ag1"/></span>
<prov:role xsi:type="xsd:QName">loggedInUser</prov:role>
<ex:how>webapp</ex:how>
</prov:wasAssociatedWith></b>
<b><prov:wasAssociatedWith>
- <prov:activity prov:ref="a"/>
- <prov:agent prov:ref="ag2"/>
+ <prov:activity <span class="delete">prov:ref="a"/></span><span class="insert">prov:ref="ex:a"/></span>
+ <prov:agent <span class="delete">prov:ref="ag2"/></span><span class="insert">prov:ref="ex:ag2"/></span>
<prov:plan prov:ref="ex:wf"/>
<prov:role xsi:type="xsd:QName">designer</prov:role>
<ex:content>project1</ex:content>
@@ -1606,15 +1646,15 @@
<section id="term-Plan">
<h5><span class="secno">3.3.3.1 </span>Plan</h5>
-<span class="glossary-ref"> A <span class="dfn">plan</span> is an entity that represents a set of actions or steps intended by one or more agents to achieve some goals. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Plan">
+<p><span class="insert">From [</span><cite><a class="bibref" href="#bib-PROV-DM"><span class="insert">PROV-DM</span></a></cite><span class="insert">]:</span></p><blockquote><i><span class="glossary-ref"> A <span class="dfn">plan</span> is an entity that represents a set of actions or steps intended by one or more agents to achieve some goals. </span></i></blockquote>
+<p><span class="delete">Type</span><span class="insert">ComplexType</span> definition<span class="insert"> (denoting a similarly named prov-"type")</span> in XML Schema:</p><pre class="schema-type"><xs:complexType name="Plan">
<xs:complexContent>
<xs:extension base="prov:Entity">
</xs:extension>
</xs:complexContent>
</xs:complexType>
</pre>
-<p>The element <code>prov:plan</code> is used to reference a prov:Plan from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="plan" type="prov:Plan"/>
+<p>The <span class="delete">element</span><span class="insert">xml-element</span> <code>prov:plan</code> is used to <span class="delete">reference</span><span class="insert">denote</span> a prov:Plan<span class="insert"> prov-"type"</span> from within a prov:Document or prov:BundleConstructor.</p><p><span class="insert">XML </span>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="plan" type="prov:Plan"/>
</pre>
<div class="example"><div class="example-title"><span>Example 24</span>: prov:plan</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -1622,28 +1662,28 @@
xmlns:prov="http://www.w3.org/ns/prov#"
xmlns:ex="http://example.com/ns/ex#">
- <prov:activity prov:id="a">
+ <prov:activity <span class="delete">prov:id="a"></span><span class="insert">prov:id="ex:a"></span>
<prov:type xsi:type="xsd:string">workflow execution</prov:type>
</prov:activity>
- <prov:agent prov:id="ag1">
+ <prov:agent <span class="delete">prov:id="ag1"></span><span class="insert">prov:id="ex:ag1"></span>
<prov:type xsi:type="xsd:QName">operator</prov:type>
</prov:agent>
- <prov:agent prov:id="ag2">
+ <prov:agent <span class="delete">prov:id="ag2"></span><span class="insert">prov:id="ex:ag2"></span>
<prov:type xsi:type="xsd:QName">designator</prov:type>
</prov:agent>
<prov:wasAssociatedWith>
- <prov:activity prov:ref="a"/>
- <prov:agent prov:ref="ag1"/>
+ <prov:activity <span class="delete">prov:ref="a"/></span><span class="insert">prov:ref="ex:a"/></span>
+ <prov:agent <span class="delete">prov:ref="ag1"/></span><span class="insert">prov:ref="ex:ag1"/></span>
<prov:role xsi:type="xsd:QName">loggedInUser</prov:role>
<ex:how>webapp</ex:how>
</prov:wasAssociatedWith>
<prov:wasAssociatedWith>
- <prov:activity prov:ref="a"/>
- <prov:agent prov:ref="ag2"/>
+ <prov:activity <span class="delete">prov:ref="a"/></span><span class="insert">prov:ref="ex:a"/></span>
+ <prov:agent <span class="delete">prov:ref="ag2"/></span><span class="insert">prov:ref="ex:ag2"/></span>
<prov:plan prov:ref="ex:wf"/>
<prov:role xsi:type="xsd:QName">designer</prov:role>
<ex:content>project1</ex:content>
@@ -1660,8 +1700,8 @@
<section id="term-Delegation">
<h4><span class="secno">3.3.4 </span>Delegation</h4>
-<span class="glossary-ref"> <span class="dfn">Delegation</span> is the assignment of authority and responsibility to an agent (by itself or by another agent) to carry out a specific activity as a delegate or representative, while the agent it acts on behalf of retains some responsibility for the outcome of the delegated work. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Delegation">
+<p><span class="insert">From [</span><cite><a class="bibref" href="#bib-PROV-DM"><span class="insert">PROV-DM</span></a></cite><span class="insert">]:</span></p><blockquote><i><span class="glossary-ref"> <span class="dfn">Delegation</span> is the assignment of authority and responsibility to an agent (by itself or by another agent) to carry out a specific activity as a delegate or representative, while the agent it acts on behalf of retains some responsibility for the outcome of the delegated work. </span></i></blockquote>
+<p><span class="delete">Type</span><span class="insert">ComplexType</span> definition<span class="insert"> (denoting a similarly named prov-"type")</span> in XML Schema:</p><pre class="schema-type"><xs:complexType name="Delegation">
<xs:sequence>
<xs:element name="delegate" type="prov:IDRef"/>
<xs:element name="responsible" type="prov:IDRef"/>
@@ -1674,56 +1714,57 @@
<xs:attribute ref="prov:id"/>
</xs:complexType>
</pre>
-<p>The element <code>prov:actedOnBehalfOf</code> is used to reference a prov:Delegation from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="actedOnBehalfOf" type="prov:Delegation"/>
+<p>The <span class="delete">element</span><span class="insert">xml-element</span> <code>prov:actedOnBehalfOf</code> is used to <span class="delete">reference</span><span class="insert">denote</span> a prov:Delegation<span class="insert"> prov-"type"</span> from within a prov:Document or prov:BundleConstructor.</p><p><span class="insert">XML </span>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="actedOnBehalfOf" type="prov:Delegation"/>
</pre>
<div class="example"><div class="example-title"><span>Example 25</span>: prov:actedOnBehalfOf</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
- xmlns:prov="http://www.w3.org/ns/prov#">
-
- <prov:activity prov:id="a">
+ <span class="delete">xmlns:prov="http://www.w3.org/ns/prov#"></span><span class="insert">xmlns:prov="http://www.w3.org/ns/prov#"
+ xmlns:ex="http://example.com/ns/ex#"></span>
+
+ <prov:activity <span class="delete">prov:id="a"></span><span class="insert">prov:id="ex:a"></span>
<prov:type xsi:type="xsd:QName">workflow</prov:type>
</prov:activity>
- <prov:agent prov:id="ag1">
+ <prov:agent <span class="delete">prov:id="ag1"></span><span class="insert">prov:id="ex:ag1"></span>
<prov:type xsi:type="xsd:QName">programmer</prov:type>
</prov:agent>
- <prov:agent prov:id="ag2">
+ <prov:agent <span class="delete">prov:id="ag2"></span><span class="insert">prov:id="ex:ag2"></span>
<prov:type xsi:type="xsd:QName">researcher</prov:type>
</prov:agent>
- <prov:agent prov:id="ag3">
+ <prov:agent <span class="delete">prov:id="ag3"></span><span class="insert">prov:id="ex:ag3"></span>
<prov:type xsi:type="xsd:QName">funder</prov:type>
</prov:agent>
<prov:wasAssociatedWith>
- <prov:activity prov:ref="a"/>
- <prov:agent prov:ref="ag1"/>
+ <prov:activity <span class="delete">prov:ref="a"/></span><span class="insert">prov:ref="ex:a"/></span>
+ <prov:agent <span class="delete">prov:ref="ag1"/></span><span class="insert">prov:ref="ex:ag1"/></span>
<prov:role xsi:type="xsd:QName">loggedInUser</prov:role>
</prov:wasAssociatedWith>
<prov:wasAssociatedWith>
- <prov:activity prov:ref="a"/>
- <prov:agent prov:ref="ag2"/>
+ <prov:activity <span class="delete">prov:ref="a"/></span><span class="insert">prov:ref="ex:a"/></span>
+ <prov:agent <span class="delete">prov:ref="ag2"/></span><span class="insert">prov:ref="ex:ag2"/></span>
</prov:wasAssociatedWith>
<prov:wasAssociatedWith>
- <prov:activity prov:ref="a"/>
- <prov:agent prov:ref="ag3"/>
+ <prov:activity <span class="delete">prov:ref="a"/></span><span class="insert">prov:ref="ex:a"/></span>
+ <prov:agent <span class="delete">prov:ref="ag3"/></span><span class="insert">prov:ref="ex:ag3"/></span>
</prov:wasAssociatedWith>
<b><prov:actedOnBehalfOf>
- <prov:delegate prov:ref="ag1"/>
- <prov:responsible prov:ref="ag2"/>
- <prov:activity prov:ref="a"/>
+ <prov:delegate <span class="delete">prov:ref="ag1"/></span><span class="insert">prov:ref="ex:ag1"/></span>
+ <prov:responsible <span class="delete">prov:ref="ag2"/></span><span class="insert">prov:ref="ex:ag2"/></span>
+ <prov:activity <span class="delete">prov:ref="a"/></span><span class="insert">prov:ref="ex:a"/></span>
<prov:type xsi:type="xsd:QName">line-management</prov:type>
</prov:actedOnBehalfOf></b>
<b><prov:actedOnBehalfOf>
- <prov:delegate prov:ref="ag2"/>
- <prov:responsible prov:ref="ag3"/>
- <prov:activity prov:ref="a"/>
+ <prov:delegate <span class="delete">prov:ref="ag2"/></span><span class="insert">prov:ref="ex:ag2"/></span>
+ <prov:responsible <span class="delete">prov:ref="ag3"/></span><span class="insert">prov:ref="ex:ag3"/></span>
+ <prov:activity <span class="delete">prov:ref="a"/></span><span class="insert">prov:ref="ex:a"/></span>
<prov:type xsi:type="xsd:QName">contract</prov:type>
</prov:actedOnBehalfOf></b>
@@ -1732,8 +1773,8 @@
<section id="term-Influence">
<h4><span class="secno">3.3.5 </span>Influence</h4>
-<span class="glossary-ref"> <span class="dfn">Influence</span> is the capacity of an entity, activity, or agent to have an effect on the character, development, or behavior of another by means of usage, start, end, generation, invalidation, communication, derivation, attribution, association, or delegation. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Influence">
+<p><span class="insert">From [</span><cite><a class="bibref" href="#bib-PROV-DM"><span class="insert">PROV-DM</span></a></cite><span class="insert">]:</span></p><blockquote><i><span class="glossary-ref"> <span class="dfn">Influence</span> is the capacity of an entity, activity, or agent to have an effect on the character, development, or behavior of another by means of usage, start, end, generation, invalidation, communication, derivation, attribution, association, or delegation. </span></i></blockquote>
+<p><span class="delete">Type</span><span class="insert">ComplexType</span> definition<span class="insert"> (denoting a similarly named prov-"type")</span> in XML Schema:</p><pre class="schema-type"><xs:complexType name="Influence">
<xs:sequence>
<xs:element name="influencee" type="prov:IDRef"/>
<xs:element name="influencer" type="prov:IDRef"/>
@@ -1745,7 +1786,7 @@
<xs:attribute ref="prov:id"/>
</xs:complexType>
</pre>
-<p>The element <code>prov:wasInfluencedBy</code> is used to reference a prov:Influence from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasInfluencedBy" type="prov:Influence"/>
+<p>The <span class="delete">element</span><span class="insert">xml-element</span> <code>prov:wasInfluencedBy</code> is used to <span class="delete">reference</span><span class="insert">denote</span> a prov:Influence<span class="insert"> prov-"type"</span> from within a prov:Document or prov:BundleConstructor.</p><p><span class="insert">XML </span>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasInfluencedBy" type="prov:Influence"/>
</pre>
<div class="example"><div class="example-title"><span>Example 26</span>: prov:wasInfluencedBy</div><pre class="example" id="example_38"><prov:document
xmlns:prov="http://www.w3.org/ns/prov#"
@@ -1771,16 +1812,16 @@
<p>The fourth component is concerned with bundles, a mechanism to support provenance of provenance.</p>
<section id="term-Bundle">
<h4><span class="secno">3.4.1 </span>Bundle</h4>
-<span class="glossary-ref"> A <span class="dfn">bundle</span> is a named set of provenance descriptions, and is itself an entity, so allowing provenance of provenance to be expressed. </span>
-<p>A <code>prov:Bundle</code> identifies a set of provenance descriptions, and is an extension of <code>prov:Entity</code>, so allowing provenance of provenance to be expressed by referencing the associated entity. The content of a bundle, i.e. its provenance records, can be represented by the <code>prov:BundleConstructor</code> complexType and can be specified with the <code>prov:bundleContent</code> element, its <code>prov:id</code> corresponds to the bundle entity.</p>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Bundle">
+<p><span class="insert">From [</span><cite><a class="bibref" href="#bib-PROV-DM"><span class="insert">PROV-DM</span></a></cite><span class="insert">]:</span></p><blockquote><i><span class="glossary-ref"> A <span class="dfn">bundle</span> is a named set of provenance descriptions, and is itself an entity, so allowing provenance of provenance to be expressed. </span></i></blockquote>
+<p>A <code>prov:Bundle</code> identifies a set of provenance descriptions, and is an extension of <code>prov:Entity</code>, so allowing provenance of provenance to be expressed by referencing the associated entity. The content of a bundle, i.e. its provenance records, can be represented by the <code>prov:BundleConstructor</code> <span class="delete">complexType</span><span class="insert">ComplexType</span> and <span class="delete">can be specified</span><span class="insert">is denoted</span> with the <code>prov:bundleContent</code> <span class="delete">element,</span><span class="insert">xml-element,</span> its <code>prov:id</code> corresponds to the bundle entity.</p>
+<p><span class="delete">Type</span><span class="insert">ComplexType</span> definition<span class="insert"> (denoting a similarly named prov-"type")</span> in XML Schema:</p><pre class="schema-type"><xs:complexType name="Bundle">
<xs:complexContent>
<xs:extension base="prov:Entity">
</xs:extension>
</xs:complexContent>
</xs:complexType>
</pre>
-<p>The element <code>prov:bundle</code> is used to reference a prov:Bundle from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="bundle" type="prov:Bundle"/>
+<p>The <span class="delete">element</span><span class="insert">xml-element</span> <code>prov:bundle</code> is used to <span class="delete">reference</span><span class="insert">denote</span> a prov:Bundle<span class="insert"> prov-"type"</span> from within a prov:Document or prov:BundleConstructor.</p><p><span class="insert">XML </span>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="bundle" type="prov:Bundle"/>
</pre>
<div class="example"><div class="example-title"><span>Example 27</span>: prov:bundle</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -1819,25 +1860,25 @@
<section id="term-BundleConstructor">
<h4><span class="secno">3.4.2 </span>Bundle Constructor</h4>
-<p>The <code>prov:BundleConstructor</code> complexType is used to define a named set of provenance statements. The Bundle Constructor type supports the <code>prov:id</code> attribute.</p>
+<p>The <code>prov:BundleConstructor</code> <span class="delete">complexType</span><span class="insert">ComplexType</span> is used to define a named set of provenance statements. The Bundle Constructor <span class="delete">type </span>supports the <code>prov:id</code> <span class="delete">attribute.</span><span class="insert">xml-attribute.</span></p>
<p>The bundle entity associated with a bundle constructor set must have the same <code>prov:id</code> as the bundle constructor set.</p>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="BundleConstructor">
- <xs:sequence maxOccurs="unbounded">
+<p><span class="delete">Type</span><span class="insert">ComplexType</span> definition<span class="insert"> (denoting a similarly named prov-"type")</span> in XML Schema:</p><pre class="schema-type"><xs:complexType name="BundleConstructor">
+ <span class="delete"><xs:sequence</span><span class="insert"><xs:choice minOccurs="0"</span> maxOccurs="unbounded">
<span class="delete"><xs:group ref="prov:documentElements"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0"/></span><span class="insert"><-- references to standard non-PROV attribute PROV elements --></span>
- </xs:sequence>
+ <span class="delete"></xs:sequence></span><span class="insert"></xs:choice></span>
<xs:attribute ref="prov:id"/>
</xs:complexType>
</pre>
-<p>The element <code>prov:bundleContent</code> is used to reference a set of nested provenance statements from within a prov:Document.</p>
-<p>Although <code>prov:bundleContent</code> can only be expressed at the <code>prov:document</code> level, the corresponding bundle entities may be specified at from either the <code>prov:document</code> or any <code>prov:bundleContent</code>, if at all.</p>
+<p>The <span class="delete">element</span><span class="insert">xml-element</span> <code>prov:bundleContent</code> is used to <span class="delete">reference</span><span class="insert">denote</span> a set of nested provenance statements from within a prov:Document.</p>
+<p>Although <code>prov:bundleContent</code> can only be expressed at the <code>prov:document</code> level, the corresponding bundle entities may be specified <span class="delete">at </span>from either the <code>prov:document</code> or any <code>prov:bundleContent</code><span class="delete">, if at all.</span><span class="insert">.</span></p>
<pre><xs:complexType name="Document">
- <xs:sequence maxOccurs="unbounded">
+ <span class="delete"><xs:sequence</span><span class="insert"><xs:choice minOccurs="0"</span> maxOccurs="unbounded">
<span class="delete"><xs:group ref="prov:documentElements"</span><span class="insert"><!-- references to standard non-PROV attribute PROV elements -->
<xs:element name="bundleContent" type="prov:BundleConstructor"</span> minOccurs="0"/><span class="delete">
<xs:element name="bundleContent" type="prov:BundleConstructor" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" /></span>
- </xs:sequence>
+ <span class="delete"></xs:sequence></span><span class="insert"></xs:choice></span>
</xs:complexType>
</pre>
<div class="example"><div class="example-title"><span>Example 28</span>: prov:bundleContent</div><pre class="example"><prov:document
@@ -1878,20 +1919,20 @@
<section id="component5">
<h3><span class="secno">3.5 </span>Component 5: Alternate Entities</h3>
-<p>The fifth component of PROV-DM is concerned with
-relations SpecializationOf (<a href="#term-Specialization">Specialization</a>) and AlternateOf (<a href="#term-Alternate">Alternate</a>) between entities.</p>
+<p>The fifth component of PROV-DM is concerned with<span class="insert"> the</span>
+relations <span class="delete">SpecializationOf (</span><a href="#term-Specialization">Specialization</a><span class="delete">)</span> and <span class="delete">AlternateOf (</span><a href="#term-Alternate">Alternate</a><span class="delete">) between</span><span class="insert">, relating entities to</span> entities.</p>
<section id="term-Specialization">
<h4><span class="secno">3.5.1 </span>Specialization</h4>
-<span class="glossary-ref"> An entity that is a <span class="dfn">specialization</span> of another shares all aspects of the latter, and additionally presents more specific aspects of the same thing as the latter. In particular, the lifetime of the entity being specialized contains that of any specialization. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Specialization">
+<p><span class="insert">From [</span><cite><a class="bibref" href="#bib-PROV-DM"><span class="insert">PROV-DM</span></a></cite><span class="insert">]:</span></p><blockquote><i><span class="glossary-ref"> An entity that is a <span class="dfn">specialization</span> of another shares all aspects of the latter, and additionally presents more specific aspects of the same thing as the latter. In particular, the lifetime of the entity being specialized contains that of any specialization. </span></i></blockquote>
+<p><span class="delete">Type</span><span class="insert">ComplexType</span> definition<span class="insert"> (denoting a similarly named prov-"type")</span> in XML Schema:</p><pre class="schema-type"><xs:complexType name="Specialization">
<xs:sequence>
<xs:element name="specificEntity" type="prov:IDRef"/>
<xs:element name="generalEntity" type="prov:IDRef"/>
</xs:sequence>
</xs:complexType>
</pre>
-<p>The element <code>prov:specializationOf</code> is used to reference a prov:Specialization from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="specializationOf" type="prov:Specialization"/>
+<p>The <span class="delete">element</span><span class="insert">xml-element</span> <code>prov:specializationOf</code> is used to <span class="delete">reference</span><span class="insert">denote</span> a prov:Specialization<span class="insert"> prov-"type"</span> from within a prov:Document or prov:BundleConstructor.</p><p><span class="insert">XML </span>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="specializationOf" type="prov:Specialization"/>
</pre>
<div class="example"><div class="example-title"><span>Example 29</span>: prov:specializationOf</div><pre class="example"><prov:document
xmlns:prov="http://www.w3.org/ns/prov#"
@@ -1912,15 +1953,15 @@
<section id="term-Alternate">
<h4><span class="secno">3.5.2 </span>Alternate</h4>
-<span class="glossary-ref"> Two <span class="dfn">alternate</span> entities present aspects of the same thing. These aspects may be the same or different, and the alternate entities may or may not overlap in time. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Alternate">
+<p><span class="insert">From [</span><cite><a class="bibref" href="#bib-PROV-DM"><span class="insert">PROV-DM</span></a></cite><span class="insert">]:</span></p><blockquote><i><span class="glossary-ref"> Two <span class="dfn">alternate</span> entities present aspects of the same thing. These aspects may be the same or different, and the alternate entities may or may not overlap in time. </span></i></blockquote>
+<p><span class="delete">Type</span><span class="insert">ComplexType</span> definition<span class="insert"> (denoting a similarly named prov-"type")</span> in XML Schema:</p><pre class="schema-type"><xs:complexType name="Alternate">
<xs:sequence>
<xs:element name="alternate1" type="prov:IDRef"/>
<xs:element name="alternate2" type="prov:IDRef"/>
</xs:sequence>
</xs:complexType>
</pre>
-<p>The element <code>prov:alternateOf</code> is used to reference a prov:Alternate from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="alternateOf" type="prov:Alternate"/>
+<p>The <span class="delete">element</span><span class="insert">xml-element</span> <code>prov:alternateOf</code> is used to <span class="delete">reference</span><span class="insert">denote</span> a prov:Alternate<span class="insert"> prov-"type"</span> from within a prov:Document or prov:BundleConstructor.</p><p><span class="insert">XML </span>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="alternateOf" type="prov:Alternate"/>
</pre>
<div class="example"><div class="example-title"><span>Example 30</span>: prov:alternateOf</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -1955,15 +1996,15 @@
<section id="term-Collection">
<h4><span class="secno">3.6.1 </span>Collection</h4>
-<span class="glossary-ref"> A <span class="dfn">collection</span> is an entity that provides a structure to some constituents that must themselves be entities. These constituents are said to be <span class="dfn">member</span> of the collections. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Collection">
+<p><span class="insert">From [</span><cite><a class="bibref" href="#bib-PROV-DM"><span class="insert">PROV-DM</span></a></cite><span class="insert">]:</span></p><blockquote><i><span class="glossary-ref"> A <span class="dfn">collection</span> is an entity that provides a structure to some constituents that must themselves be entities. These constituents are said to be <span class="dfn">member</span> of the collections. </span></i></blockquote>
+<p><span class="delete">Type</span><span class="insert">ComplexType</span> definition<span class="insert"> (denoting a similarly named prov-"type")</span> in XML Schema:</p><pre class="schema-type"><xs:complexType name="Collection">
<xs:complexContent>
<xs:extension base="prov:Entity">
</xs:extension>
</xs:complexContent>
</xs:complexType>
</pre>
-<p>The element <code>prov:collection</code> is used to reference a prov:Collection from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="collection" type="prov:Collection"/>
+<p>The <span class="delete">element</span><span class="insert">xml-element</span> <code>prov:collection</code> is used to <span class="delete">reference</span><span class="insert">denote</span> a prov:Collection<span class="insert"> prov-"type"</span> from within a prov:Document or prov:BundleConstructor.</p><p><span class="insert">XML </span>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="collection" type="prov:Collection"/>
</pre>
<div class="example"><div class="example-title"><span>Example 31</span>: prov:collection</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -1971,21 +2012,21 @@
xmlns:prov="http://www.w3.org/ns/prov#"
xmlns:ex="http://example.com/ns/ex#">
- <b><prov:collection prov:id="c1" /></b>
+ <b><prov:collection <span class="delete">prov:id="c1"</span><span class="insert">prov:id="ex:c1"</span> /></b>
</prov:document></pre></div>
<section id="term-EmptyCollection">
<h5><span class="secno">3.6.1.1 </span>Empty Collection</h5>
-<span class="glossary-ref"> An <span class="dfn">empty collection</span> is a collection without members. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="EmptyCollection">
+<p><span class="insert">From [</span><cite><a class="bibref" href="#bib-PROV-DM"><span class="insert">PROV-DM</span></a></cite><span class="insert">]:</span></p><blockquote><i><span class="glossary-ref"> An <span class="dfn">empty collection</span> is a collection without members. </span></i></blockquote>
+<p><span class="delete">Type</span><span class="insert">ComplexType</span> definition<span class="insert"> (denoting a similarly named prov-"type")</span> in XML Schema:</p><pre class="schema-type"><xs:complexType name="EmptyCollection">
<xs:complexContent>
<xs:extension base="prov:Collection">
</xs:extension>
</xs:complexContent>
</xs:complexType>
</pre>
-<p>The element <code>prov:emptyCollection</code> is used to reference a prov:EmptyCollection from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="emptyCollection" type="prov:EmptyCollection"/>
+<p>The <span class="delete">element</span><span class="insert">xml-element</span> <code>prov:emptyCollection</code> is used to <span class="delete">reference</span><span class="insert">denote</span> a prov:EmptyCollection<span class="insert"> prov-"type"</span> from within a prov:Document or prov:BundleConstructor.</p><p><span class="insert">XML </span>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="emptyCollection" type="prov:EmptyCollection"/>
</pre>
<div class="example"><div class="example-title"><span>Example 32</span>: prov:emptyCollection</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -1994,7 +2035,7 @@
xmlns:bbc="http://www.bbc.co.uk/news"
xmlns:bbcmobile="http://www.bbc.co.uk/news/mobile">
- <b><prov:emptyCollection prov:id="c0"/></b>
+ <b><prov:emptyCollection <span class="delete">prov:id="c0"/></span><span class="insert">prov:id="ex:c0"/></span></b>
</prov:document></pre></div>
</section>
@@ -2002,32 +2043,33 @@
<section id="term-Membership">
<h4><span class="secno">3.6.2 </span>Membership</h4>
-<span class="glossary-ref"> <span class="dfn">Membership</span> is the belonging of an entity to a collection. </span>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Membership">
+<p><span class="insert">From [</span><cite><a class="bibref" href="#bib-PROV-DM"><span class="insert">PROV-DM</span></a></cite><span class="insert">]:</span></p><blockquote><i><span class="glossary-ref"> <span class="dfn">Membership</span> is the belonging of an entity to a collection. </span></i></blockquote>
+<p><span class="delete">Type</span><span class="insert">ComplexType</span> definition<span class="insert"> (denoting a similarly named prov-"type")</span> in XML Schema:</p><pre class="schema-type"><xs:complexType name="Membership">
<xs:sequence>
<xs:element name="collection" type="prov:IDRef"/>
<xs:element name="entity" type="prov:IDRef" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</pre>
-<p>The element <code>prov:hadMember</code> is used to reference a prov:Membership from within a prov:Document or prov:BundleConstructor.</p><p>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="hadMember" type="prov:Membership"/>
+<p>The <span class="delete">element</span><span class="insert">xml-element</span> <code>prov:hadMember</code> is used to <span class="delete">reference</span><span class="insert">denote</span> a prov:Membership<span class="insert"> prov-"type"</span> from within a prov:Document or prov:BundleConstructor.</p><p><span class="insert">XML </span>Element definition in XML Schema:</p><pre class="schema-element"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="hadMember" type="prov:Membership"/>
</pre>
<div class="example"><div class="example-title"><span>Example 33</span>: prov:hadMember</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
- xmlns:prov="http://www.w3.org/ns/prov#">
-
- <prov:entity prov:id="e0"/>
- <prov:entity prov:id="e1"/>
- <prov:entity prov:id="e2"/>
-
- <prov:collection prov:id="c"/>
+ <span class="delete">xmlns:prov="http://www.w3.org/ns/prov#"></span><span class="insert">xmlns:prov="http://www.w3.org/ns/prov#"
+ xmlns:ex="http://example.com/ns/ex#"></span>
+
+ <prov:entity <span class="delete">prov:id="e0"/></span><span class="insert">prov:id="ex:e0"/></span>
+ <prov:entity <span class="delete">prov:id="e1"/></span><span class="insert">prov:id="ex:e1"/></span>
+ <prov:entity <span class="delete">prov:id="e2"/></span><span class="insert">prov:id="ex:e2"/></span>
+
+ <prov:collection <span class="delete">prov:id="c"/></span><span class="insert">prov:id="ex:c"/></span>
<b><prov:hadMember>
- <prov:collection prov:ref="c"/>
- <prov:entity prov:ref="e0"/>
- <prov:entity prov:ref="e1"/>
- <prov:entity prov:ref="e2"/>
+ <prov:collection <span class="delete">prov:ref="c"/></span><span class="insert">prov:ref="ex:c"/></span>
+ <prov:entity <span class="delete">prov:ref="e0"/></span><span class="insert">prov:ref="ex:e0"/></span>
+ <prov:entity <span class="delete">prov:ref="e1"/></span><span class="insert">prov:ref="ex:e1"/></span>
+ <prov:entity <span class="delete">prov:ref="e2"/></span><span class="insert">prov:ref="ex:e2"/></span>
</prov:hadMember></b>
</prov:document></pre></div>
@@ -2042,8 +2084,8 @@
<section id="attribute-Identifier">
<h4><span class="secno">3.7.1 </span>Identifier</h4>
-<span class="glossary-ref"></span>
-<p>The identifier attribute is used to identify instances of PROV types or relations.</p>
+<p><span class="insert">From [</span><cite><a class="bibref" href="#bib-PROV-DM"><span class="insert">PROV-DM</span></a></cite><span class="insert">]:</span></p><blockquote><i><span class="glossary-ref"></span></i></blockquote>
+<p>The <span class="delete">identifier attribute is</span><span class="insert">xml-attribute</span> used to identify <span class="insert">an </span>instances of <span class="delete">PROV types</span><span class="insert">a prov-"type"</span> or <span class="delete">relations.</span><span class="insert">prov-"relation".</span></p>
<pre class="schema-attribute"><xs:attribute xmlns:xs="http://www.w3.org/2001/XMLSchema" name="id" type="xs:QName"/>
</pre>
<div class="example"><div class="example-title"><span>Example 34</span>: prov:id</div><pre class="example"><prov:document
@@ -2063,21 +2105,21 @@
<section id="attribute-Reference">
<h4><span class="secno">3.7.2 </span>Reference</h4>
-<span class="glossary-ref"></span>
-<p>A reference-by-id to a PROV entity, activity, agent, or relation.</p>
+<p><span class="insert">From [</span><cite><a class="bibref" href="#bib-PROV-DM"><span class="insert">PROV-DM</span></a></cite><span class="insert">]:</span></p><blockquote><i><span class="glossary-ref"></span></i></blockquote>
+<p>A <span class="insert">xml-attribute that denotes a </span>reference-by-id to <span class="insert">an instance of </span>a <span class="delete">PROV entity, activity, agent,</span><span class="insert">prov-"type"</span> or <span class="delete">relation.</span><span class="insert">prov-"relation".</span></p>
<pre class="schema-attribute"><xs:attribute ref="prov:ref" use="required" />
</pre>
<div class="example"><div class="example-title"><span>Example 35</span>: prov:ref</div><pre class="example"><prov:document
xmlns:prov="http://www.w3.org/ns/prov#"
xmlns:ex="http://example.com/ns/ex#">
- <prov:entity prov:id="e1"/>
-
- <prov:activity prov:id="a1"/>
+ <prov:entity <span class="delete">prov:id="e1"/></span><span class="insert">prov:id="ex:e1"/></span>
+
+ <prov:activity <span class="delete">prov:id="a1"/></span><span class="insert">prov:id="ex:a1"/></span>
<prov:wasGeneratedBy>
- <prov:entity <b>prov:ref="e1"</b>/>
- <prov:activity <b>prov:ref="a1"</b>/>
+ <prov:entity <b><span class="delete">prov:ref="e1"</span><span class="insert">prov:ref="ex:e1"</span></b>/>
+ <prov:activity <b><span class="delete">prov:ref="a1"</span><span class="insert">prov:ref="ex:a1"</span></b>/>
<prov:time>2001-10-26T21:32:52</prov:time>
<ex:port>p1</ex:port>
</prov:wasGeneratedBy>
@@ -2087,12 +2129,12 @@
<section id="attributes">
<h4><span class="secno">3.7.3 </span>Attributes</h4>
-<p>The PROV-DM defined PROV attributes are represented in XML as elements.</p>
+<p>The PROV-DM defined <span class="delete">PROV attributes</span><span class="insert">prov-"attributes"</span> are represented in XML as <span class="delete">elements.</span><span class="insert">xml-elements.</span></p>
<section id="element-Label">
<h5><span class="secno">3.7.3.1 </span>Label</h5>
-<span class="glossary-ref"> The attribute <span class="dfn"><span class="name">prov:label</span></span> provides a human-readable representation of an instance of a PROV-DM type or relation. </span>
-<p>The element <code>prov:label</code> is used to represent a PROV label attribute and has type prov:InternationalizedString.</p><p>Element definition in XML Schema:</p><pre class="prov-attribute"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="label" type="prov:InternationalizedString"/>
+<p><span class="insert">From [</span><cite><a class="bibref" href="#bib-PROV-DM"><span class="insert">PROV-DM</span></a></cite><span class="insert">]:</span></p><blockquote><i><span class="glossary-ref"> The attribute <span class="dfn"><span class="name">prov:label</span></span> provides a human-readable representation of an instance of a PROV-DM type or relation. </span></i></blockquote>
+<p>The <span class="delete">element</span><span class="insert">xml-element</span> <code>prov:label</code> is used to <span class="delete">represent</span><span class="insert">denote</span> a <span class="delete">PROV </span>label <span class="delete">attribute</span><span class="insert">prov-"attribute"</span> and has <span class="delete">type</span><span class="insert">prov-"type"</span> prov:InternationalizedString.</p><p><span class="insert">XML </span>Element definition in XML Schema:</p><pre class="prov-attribute"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="label" type="prov:InternationalizedString"/>
</pre>
<div class="example"><div class="example-title"><span>Example 36</span>: prov:label</div><pre class="example"><prov:document
xmlns:prov="http://www.w3.org/ns/prov#"
@@ -2112,8 +2154,8 @@
<section id="element-Location">
<h5><span class="secno">3.7.3.2 </span>Location</h5>
-<span class="glossary-ref"> A <span class="dfn">location</span> can be an identifiable geographic place (ISO 19112), but it can also be a non-geographic place such as a directory, row, or column. </span>
-<p>The element <code>prov:location</code> is used to represent a PROV location attribute and has type xs:anySimpleType.</p><p>Element definition in XML Schema:</p><pre class="prov-attribute"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="location" type="xs:anySimpleType"/>
+<p><span class="insert">From [</span><cite><a class="bibref" href="#bib-PROV-DM"><span class="insert">PROV-DM</span></a></cite><span class="insert">]:</span></p><blockquote><i><span class="glossary-ref"> A <span class="dfn">location</span> can be an identifiable geographic place (ISO 19112), but it can also be a non-geographic place such as a directory, row, or column. </span></i></blockquote>
+<p>The <span class="delete">element</span><span class="insert">xml-element</span> <code>prov:location</code> is used to <span class="delete">represent</span><span class="insert">denote</span> a <span class="delete">PROV </span>location <span class="delete">attribute</span><span class="insert">prov-"attribute"</span> and has <span class="delete">type</span><span class="insert">prov-"type"</span> xs:anySimpleType.</p><p><span class="insert">XML </span>Element definition in XML Schema:</p><pre class="prov-attribute"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="location" type="xs:anySimpleType"/>
</pre>
<div class="example"><div class="example-title"><span>Example 37</span>: prov:location</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -2136,8 +2178,8 @@
<section id="element-Role">
<h5><span class="secno">3.7.3.3 </span>Role</h5>
-<span class="glossary-ref"> A <span class="dfn">role</span> is the function of an entity or agent with respect to an activity, in the context of a <a title="Usage">usage</a>, <a title="Generation">generation</a>, <a title="Invalidation">invalidation</a>, <a title="Association">association</a>, <a title="Start">start</a>, and <a title="End">end</a>. </span>
-<p>The element <code>prov:role</code> is used to represent a PROV Role attribute and has type xs:anySimpleType.</p><p>Element definition in XML Schema:</p><pre class="prov-attribute"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="role" type="xs:anySimpleType"/>
+<p><span class="insert">From [</span><cite><a class="bibref" href="#bib-PROV-DM"><span class="insert">PROV-DM</span></a></cite><span class="insert">]:</span></p><blockquote><i><span class="glossary-ref"> A <span class="dfn">role</span> is the function of an entity or agent with respect to an activity, in the context of a <a title="Usage">usage</a>, <a title="Generation">generation</a>, <a title="Invalidation">invalidation</a>, <a title="Association">association</a>, <a title="Start">start</a>, and <a title="End">end</a>. </span></i></blockquote>
+<p>The <span class="delete">element</span><span class="insert">xml-element</span> <code>prov:role</code> is used to <span class="delete">represent</span><span class="insert">denote</span> a <span class="delete">PROV </span>Role <span class="delete">attribute</span><span class="insert">prov-"attribute"</span> and has <span class="delete">type</span><span class="insert">prov-"type"</span> xs:anySimpleType.</p><p><span class="insert">XML </span>Element definition in XML Schema:</p><pre class="prov-attribute"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="role" type="xs:anySimpleType"/>
</pre>
<div class="example"><div class="example-title"><span>Example 38</span>: prov:role</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -2146,15 +2188,15 @@
xmlns:ex="http://example.com/ns/ex#">
<prov:wasAssociatedWith>
- <prov:activity prov:ref="a"/>
- <prov:agent prov:ref="ag1"/>
+ <prov:activity <span class="delete">prov:ref="a"/></span><span class="insert">prov:ref="ex:a"/></span>
+ <prov:agent <span class="delete">prov:ref="ag1"/></span><span class="insert">prov:ref="ex:ag1"/></span>
<b><prov:role xsi:type="xsd:QName">loggedInUser</prov:role></b>
<ex:how>webapp</ex:how>
</prov:wasAssociatedWith>
<prov:wasAssociatedWith>
- <prov:activity prov:ref="a"/>
- <prov:agent prov:ref="ag2"/>
+ <prov:activity <span class="delete">prov:ref="a"/></span><span class="insert">prov:ref="ex:a"/></span>
+ <prov:agent <span class="delete">prov:ref="ag2"/></span><span class="insert">prov:ref="ex:ag2"/></span>
<prov:plan prov:ref="ex:wf"/>
<b><prov:role xsi:type="xsd:QName">designer</prov:role></b>
<ex:content>project1</ex:content>
@@ -2165,8 +2207,8 @@
<section id="element-Type">
<h5><span class="secno">3.7.3.4 </span>Type</h5>
-<span class="glossary-ref"> The attribute <span class="dfn"><span class="name">prov:type</span></span> provides further typing information for any construct with an optional set of attribute-value pairs. </span>
-<p>The element <code>prov:type</code> is used to represent a PROV Type attribute and has type xs:anySimpleType.</p><p>Element definition in XML Schema:</p><pre class="prov-attribute"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="type" type="xs:anySimpleType"/>
+<p><span class="insert">From [</span><cite><a class="bibref" href="#bib-PROV-DM"><span class="insert">PROV-DM</span></a></cite><span class="insert">]:</span></p><blockquote><i><span class="glossary-ref"> The attribute <span class="dfn"><span class="name">prov:type</span></span> provides further typing information for any construct with an optional set of attribute-value pairs. </span></i></blockquote>
+<p>The <span class="delete">element</span><span class="insert">xml-element</span> <code>prov:type</code> is used to <span class="delete">represent</span><span class="insert">denote</span> a <span class="delete">PROV </span>Type <span class="delete">attribute</span><span class="insert">prov-"attribute"</span> and has <span class="delete">type</span><span class="insert">prov-"type"</span> xs:anySimpleType.</p><p><span class="insert">XML </span>Element definition in XML Schema:</p><pre class="prov-attribute"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="type" type="xs:anySimpleType"/>
</pre>
<div class="example"><div class="example-title"><span>Example 39</span>: prov:type</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -2180,13 +2222,13 @@
<ex:version>2</ex:version>
</prov:entity>
- <prov:agent prov:id="e1">
+ <prov:agent <span class="delete">prov:id="e1"></span><span class="insert">prov:id="ex:e1"></span>
<b><prov:type xsi:type="xsd:QName">prov:Person</prov:type></b>
<ex:name>Alice</ex:name>
<ex:employee>1234</ex:employee>
</prov:agent>
- <prov:activity prov:id="a1">
+ <prov:activity <span class="delete">prov:id="a1"></span><span class="insert">prov:id="ex:a1"></span>
<prov:startTime>2011-11-16T16:05:00</prov:startTime>
<prov:endTime>2011-11-16T16:06:00</prov:endTime>
<b><prov:type xsi:type="xsd:QName">ex:edit</prov:type></b>
@@ -2198,8 +2240,8 @@
<section id="element-Value">
<h5><span class="secno">3.7.3.5 </span>Value</h5>
-<span class="glossary-ref"> The attribute <span class="dfn"><span class="name">prov:value</span></span> provides a value that is a direct representation of an entity as a PROV-DM <a title="value">Value</a>. </span>
-<p>The element <code>prov:value</code> is used to represent a PROV Value attribute and has type xs:anySimpleType.</p><p>Element definition in XML Schema:</p><pre class="prov-attribute"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="value" type="xs:anySimpleType"/>
+<p><span class="insert">From [</span><cite><a class="bibref" href="#bib-PROV-DM"><span class="insert">PROV-DM</span></a></cite><span class="insert">]:</span></p><blockquote><i><span class="glossary-ref"> The attribute <span class="dfn"><span class="name">prov:value</span></span> provides a value that is a direct representation of an entity as a PROV-DM <a title="value">Value</a>. </span></i></blockquote>
+<p>The <span class="delete">element</span><span class="insert">xml-element</span> <code>prov:value</code> is used to <span class="delete">represent</span><span class="insert">denote</span> a <span class="delete">PROV </span>Value <span class="delete">attribute</span><span class="insert">prov-"attribute"</span> and has <span class="delete">type</span><span class="insert">prov-"type"</span> xs:anySimpleType.</p><p><span class="insert">XML </span>Element definition in XML Schema:</p><pre class="prov-attribute"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="value" type="xs:anySimpleType"/>
</pre>
<div class="example"><div class="example-title"><span>Example 40</span>: prov:value</div><pre class="example"><prov:document
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -2222,8 +2264,8 @@
<section id="type-value">
<h4><span class="secno">3.7.4 </span>Value</h4>
-<span class="glossary-ref"> A <span class="dfn">value</span> is a constant such as a string, number, time, qualified name, IRI, and encoded binary data, whose interpretation is outside the scope of PROV. </span>
-<p>Relations defined by the PROV-DM to have type Value have type <code>xs:anySimpleType</code> in PROV-XML unless otherwise specified.</p>
+<p><span class="insert">From [</span><cite><a class="bibref" href="#bib-PROV-DM"><span class="insert">PROV-DM</span></a></cite><span class="insert">]:</span></p><blockquote><i><span class="glossary-ref"> A <span class="dfn">value</span> is a constant such as a string, number, time, qualified name, IRI, and encoded binary data, whose interpretation is outside the scope of PROV. </span></i></blockquote>
+<p>Relations defined by the PROV-DM to have <span class="delete">type</span><span class="insert">prov-"type"</span> Value have type <code>xs:anySimpleType</code> in PROV-XML unless otherwise specified.</p>
</section>
</section>
@@ -2233,25 +2275,25 @@
<section id="term-Document">
<h4><span class="secno">3.8.1 </span>Document</h4>
-<p>The root element of all PROV-XML documents is <code>prov:document</code> which has type <code>prov:Document</code>.</p>
+<p>The root <span class="delete">element</span><span class="insert">xml-element</span> of all PROV-XML documents is <code>prov:document</code> which has <span class="delete">type</span><span class="insert">xml-type</span> <code>prov:Document</code>.</p>
<p>Similar to a <code>prov:BundleConstructor</code>, the <code>prov:Document</code> complexType is used to define a set of provenance statements.</p>
<p>Unlike the <code>prov:BundleConstructor</code>, a <code>prov:Document</code>
</p><ul>
-<li>may contain <code>prov:bundle</code> elements (but not other <code>prov:document</code> elements)</li>
-<li>does not support the prov:id attribute.</li>
+<li>may contain <code>prov:bundle</code> <span class="delete">elements</span><span class="insert">xml-elements</span> (but not other <code>prov:document</code> <span class="delete">elements)</span><span class="insert">xml-elements)</span></li>
+<li>does not support the prov:id <span class="delete">attribute.</span><span class="insert">xml-attribute.</span></li>
</ul>
<p></p>
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType name="Document">
- <xs:sequence maxOccurs="unbounded">
+<p><span class="delete">Type</span><span class="insert">ComplexType</span> definition<span class="insert"> (denoting a similarly named prov-"type")</span> in XML Schema:</p><pre class="schema-type"><xs:complexType name="Document">
+ <span class="delete"><xs:sequence</span><span class="insert"><xs:choice minOccurs="0"</span> maxOccurs="unbounded">
<span class="delete"><xs:group ref="prov:documentElements"</span><span class="insert"><!-- references to standard non-PROV attribute PROV elements -->
<xs:element name="bundleContent" type="prov:BundleConstructor"</span> minOccurs="0"/><span class="delete">
<xs:element name="bundleContent" type="prov:BundleConstructor" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" /></span>
- </xs:sequence>
+ <span class="delete"></xs:sequence></span><span class="insert"></xs:choice></span>
</xs:complexType>
</pre>
-<p>The element <code>prov:document</code> may only be used as the root element of a a PROV-XML document.</p>
+<p>The <span class="delete">element</span><span class="insert">xml-element</span> <code>prov:document</code> may only be used as the root <span class="delete">element</span><span class="insert">xml-element</span> of a a PROV-XML document.</p>
<span class="delete">The element </span><span class="delete">prov:document</span><span class="delete"> is used to reference a prov:Document from within a prov:Document or prov:BundleConstructor.</span><span class="delete">Element definition in XML Schema:</span><pre><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="document" type="prov:Document"/>
</pre>
<div class="example"><div class="example-title"><span>Example 41</span>: prov:document</div><pre class="example"><b><prov:document
@@ -2267,14 +2309,14 @@
<section id="term-Other">
<h4><span class="secno"><span class="insert">3.8.2 </span></span><span class="insert">Other</span></h4>
-<p><span class="insert">The </span><code><span class="insert">prov:other</span></code><span class="insert"> element provides a place to include non-PROV XML elements inside a </span><code><span class="insert">prov:document</span></code><span class="insert"> or </span><code><span class="insert">prov:bundleContent</span></code><span class="insert">.</span></p>
-<p><span class="insert">Type definition in XML Schema:</span></p><pre class="schema-type"><span class="insert"><xs:complexType name="Other">
+<p><span class="insert">The </span><code><span class="insert">prov:other</span></code><span class="insert"> xml-element provides a place to include non-PROV xml-elements inside a </span><code><span class="insert">prov:document</span></code><span class="insert"> or </span><code><span class="insert">prov:bundleContent</span></code><span class="insert">.</span></p>
+<p><span class="insert">ComplexType definition (denoting a similarly named prov-"type") in XML Schema:</span></p><pre class="schema-type"><span class="insert"><xs:complexType name="Other">
<xs:sequence>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</span></pre>
-<p><span class="insert">The element </span><code><span class="insert">prov:other</span></code><span class="insert"> may be used in a </span><code><span class="insert">prov:document</span></code><span class="insert"> or a </span><code><span class="insert">prov:bundleContent</span></code><span class="insert"> but may not be used inside a relation, entity, or activity element.</span></p>
+<p><span class="insert">The xml-element </span><code><span class="insert">prov:other</span></code><span class="insert"> may be used in a </span><code><span class="insert">prov:document</span></code><span class="insert"> or a </span><code><span class="insert">prov:bundleContent</span></code><span class="insert"> but may not be used inside a prov-"relation", entity, or activity xml-element.</span></p>
<pre><span class="insert"><xs:element name="other" type="prov:Other"/>
</span></pre>
<div class="example"><div class="example-title"><span><span class="insert">Example 42</span></span><span class="insert">: prov:other</span></div><pre class="example"><span class="insert"><prov:document
@@ -2382,38 +2424,27 @@
<h2><span class="secno">A. </span>XML Schema</h2>
<section id="prov-schema">
-<h3><span class="secno">A.1 </span>prov.xsd</h3>
-<pre class="prov-schema"><?xml version="1.0" encoding="utf-8"?>
+<h3><span class="secno">A.1 </span><span class="delete">prov.xsd</span><span class="insert">Main Schema</span></h3>
+<span class="delete"><?xml version="1.0" encoding="utf-8"?>
<xs:schema targetNamespace="http://www.w3.org/ns/prov#"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:prov="http://www.w3.org/ns/prov#"
elementFormDefault="qualified"
attributeFormDefault="unqualified">
-
-
- <xs:include schemaLocation="prov-core.xsd"/>
-
- <xs:include schemaLocation="prov-dictionary.xsd"/>
-
- <xs:include schemaLocation="prov-links.xsd"/>
+ <xs:include schemaLocation="prov-core.xsd"/>
+ <xs:include schemaLocation="prov-dictionary.xsd"/>
+ <xs:include schemaLocation="prov-links.xsd"/>
</xs:schema>
-</pre>
+</span><p><span class="insert">The main PROV schema is an aggregation of the PROV core schema and all PROV-defined extension schemas.</span></p>
+<p><span class="insert">The main PROV schema is available at </span><a href="http://www.w3.org/ns/prov.xsd"><span class="insert">http://www.w3.org/ns/prov.xsd</span></a></p>
</section>
<section id="prov-core-schema">
-<h3><span class="secno">A.2 </span>prov-core.xsd</h3>
-<pre class="prov-core-schema"><?xml version="1.0" encoding="utf-8"?>
-<span class="insert">
-
-<!--
- In PROV-DM, all ids are qualified names, specified as prov:QualifiedName in PROV-N.
- In this schema, all ids are instead defined as xsd:QNames.
- -->
-
-
-</span><xs:schema targetNamespace="http://www.w3.org/ns/prov#"
+<h3><span class="secno">A.2 </span><span class="delete">prov-core.xsd</span><span class="insert">Core Schema</span></h3>
+<span class="delete"><?xml version="1.0" encoding="utf-8"?>
+<xs:schema targetNamespace="http://www.w3.org/ns/prov#"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:prov="http://www.w3.org/ns/prov#"
xmlns:cu="http://www.w3.org/1999/xhtml/datatypes/"
@@ -2431,180 +2462,114 @@
<xs:complexType name="Entity">
<xs:sequence>
-
- <!-- prov attributes -->
-
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
-
- <xs:element ref="prov:location" minOccurs="0" maxOccurs="unbounded"/>
-
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
-
- <xs:element ref="prov:value" minOccurs="0"/>
-
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
+ <!-- prov attributes -->
+ <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element ref="prov:location" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element ref="prov:value" minOccurs="0"/>
+ <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute ref="prov:id"/>
</xs:complexType>
<xs:complexType name="Activity">
<xs:sequence>
-
- <xs:element name="startTime" type="xs:dateTime" minOccurs="0"/>
-
- <xs:element name="endTime" type="xs:dateTime" minOccurs="0"/>
-
- <!-- prov attributes -->
-
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
-
- <xs:element ref="prov:location" minOccurs="0" maxOccurs="unbounded"/>
-
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
-
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element name="startTime" type="xs:dateTime" minOccurs="0"/>
+ <xs:element name="endTime" type="xs:dateTime" minOccurs="0"/>
+ <!-- prov attributes -->
+ <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element ref="prov:location" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute ref="prov:id"/>
</xs:complexType>
<xs:complexType name="Generation">
<xs:sequence>
-
- <xs:element name="entity" type="prov:IDRef"/>
-
- <xs:element name="activity" type="prov:IDRef" minOccurs="0"/>
-
- <xs:element name="time" type="xs:dateTime" minOccurs="0"/>
-
- <!-- prov attributes -->
-
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
-
- <xs:element ref="prov:location" minOccurs="0" maxOccurs="unbounded"/>
-
- <xs:element ref="prov:role" minOccurs="0" maxOccurs="unbounded"/>
-
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
-
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element name="entity" type="prov:IDRef"/>
+ <xs:element name="activity" type="prov:IDRef" minOccurs="0"/>
+ <xs:element name="time" type="xs:dateTime" minOccurs="0"/>
+ <!-- prov attributes -->
+ <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element ref="prov:location" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element ref="prov:role" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute ref="prov:id"/>
</xs:complexType>
<xs:complexType name="Usage">
<xs:sequence>
-
- <xs:element name="activity" type="prov:IDRef"/>
-
- <xs:element name="entity" type="prov:IDRef" minOccurs="0"/>
-
- <xs:element name="time" type="xs:dateTime" minOccurs="0"/>
-
- <!-- prov attributes -->
-
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
-
- <xs:element ref="prov:location" minOccurs="0" maxOccurs="unbounded"/>
-
- <xs:element ref="prov:role" minOccurs="0" maxOccurs="unbounded"/>
-
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
-
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element name="activity" type="prov:IDRef"/>
+ <xs:element name="entity" type="prov:IDRef" minOccurs="0"/>
+ <xs:element name="time" type="xs:dateTime" minOccurs="0"/>
+ <!-- prov attributes -->
+ <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element ref="prov:location" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element ref="prov:role" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute ref="prov:id"/>
</xs:complexType>
<xs:complexType name="Communication">
<xs:sequence>
-
- <xs:element name="informed" type="prov:IDRef"/>
-
- <xs:element name="informant" type="prov:IDRef"/>
-
- <!-- prov attributes -->
-
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
-
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
-
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element name="informed" type="prov:IDRef"/>
+ <xs:element name="informant" type="prov:IDRef"/>
+ <!-- prov attributes -->
+ <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute ref="prov:id"/>
</xs:complexType>
<xs:complexType name="Start">
<xs:sequence>
-
- <xs:element name="activity" type="prov:IDRef"/>
-
- <xs:element name="trigger" type="prov:IDRef" minOccurs="0"/>
-
- <xs:element name="starter" type="prov:IDRef" minOccurs="0"/>
-
- <xs:element name="time" type="xs:dateTime" minOccurs="0"/>
-
- <!-- prov attributes -->
-
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
-
- <xs:element ref="prov:location" minOccurs="0" maxOccurs="unbounded"/>
-
- <xs:element ref="prov:role" minOccurs="0" maxOccurs="unbounded"/>
-
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
-
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element name="activity" type="prov:IDRef"/>
+ <xs:element name="trigger" type="prov:IDRef" minOccurs="0"/>
+ <xs:element name="starter" type="prov:IDRef" minOccurs="0"/>
+ <xs:element name="time" type="xs:dateTime" minOccurs="0"/>
+ <!-- prov attributes -->
+ <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element ref="prov:location" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element ref="prov:role" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute ref="prov:id"/>
</xs:complexType>
<xs:complexType name="End">
<xs:sequence>
-
- <xs:element name="activity" type="prov:IDRef"/>
-
- <xs:element name="trigger" type="prov:IDRef" minOccurs="0"/>
-
- <xs:element name="ender" type="prov:IDRef" minOccurs="0"/>
-
- <xs:element name="time" type="xs:dateTime" minOccurs="0"/>
-
- <!-- prov attributes -->
-
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
-
- <xs:element ref="prov:location" minOccurs="0" maxOccurs="unbounded"/>
-
- <xs:element ref="prov:role" minOccurs="0" maxOccurs="unbounded"/>
-
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
-
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element name="activity" type="prov:IDRef"/>
+ <xs:element name="trigger" type="prov:IDRef"</span><p><span class="insert">The PROV core schema defines an XML representation of the PROV data model defined by the PROV-DM.</span> <span class="delete">minOccurs="0"/>
+ <xs:element name="ender" type="prov:IDRef" minOccurs="0"/>
+ <xs:element name="time" type="xs:dateTime" minOccurs="0"/>
+ <!-- prov attributes -->
+ <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element ref="prov:location" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element ref="prov:role" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute ref="prov:id"/>
</xs:complexType>
<xs:complexType name="Invalidation">
<xs:sequence>
-
- <xs:element name="entity" type="prov:IDRef"/>
-
- <xs:element name="activity" type="prov:IDRef" minOccurs="0"/>
-
- <xs:element name="time" type="xs:dateTime" minOccurs="0"/>
-
- <!-- prov attributes -->
-
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
-
- <xs:element ref="prov:location" minOccurs="0" maxOccurs="unbounded"/>
-
- <xs:element ref="prov:role" minOccurs="0" maxOccurs="unbounded"/>
-
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
-
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element name="entity" type="prov:IDRef"/>
+ <xs:element name="activity" type="prov:IDRef" minOccurs="0"/>
+ <xs:element name="time" type="xs:dateTime" minOccurs="0"/>
+ <!-- prov attributes -->
+ <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element ref="prov:location" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element ref="prov:role" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute ref="prov:id"/>
</xs:complexType>
@@ -2613,24 +2578,15 @@
<xs:complexType name="Derivation">
<xs:sequence>
-
- <xs:element name="generatedEntity" type="prov:IDRef"/>
-
- <xs:element name="usedEntity" type="prov:IDRef"/>
-
- <xs:element name="activity" type="prov:IDRef" minOccurs="0"/>
-
- <xs:element name="generation" type="prov:IDRef" minOccurs="0"/>
-
- <xs:element name="usage" type="prov:IDRef" minOccurs="0"/>
-
- <!-- prov attributes -->
-
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
-
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
-
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element name="generatedEntity" type="prov:IDRef"/>
+ <xs:element name="usedEntity" type="prov:IDRef"/>
+ <xs:element name="activity" type="prov:IDRef" minOccurs="0"/>
+ <xs:element name="generation" type="prov:IDRef" minOccurs="0"/>
+ <xs:element name="usage" type="prov:IDRef" minOccurs="0"/>
+ <!-- prov attributes -->
+ <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute ref="prov:id"/>
</xs:complexType>
@@ -2660,16 +2616,11 @@
<xs:complexType name="Agent">
<xs:sequence>
-
- <!-- prov attributes -->
-
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
-
- <xs:element ref="prov:location" minOccurs="0" maxOccurs="unbounded"/>
-
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
-
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
+ <!-- prov attributes -->
+ <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element ref="prov:location" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute ref="prov:id"/>
</xs:complexType>
@@ -2697,131 +2648,70 @@
<xs:complexType name="Attribution">
<xs:sequence>
-
- <xs:element name="entity" type="prov:IDRef"/>
-
- <xs:element name="agent" type="prov:IDRef"/>
-
- <!-- prov attributes -->
-
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
-
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
-
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element name="entity" type="prov:IDRef"/>
+ <xs:element name="agent" type="prov:IDRef"/>
+ <!-- prov attributes -->
+ <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute ref="prov:id"/>
</xs:complexType>
<xs:complexType name="Association">
<xs:sequence>
-
- <xs:element name="activity" type="prov:IDRef"/>
-
- <xs:element name="agent" type="prov:IDRef" minOccurs="0"/>
-
- <xs:element name="plan" type="prov:IDRef" minOccurs="0"/>
-
- <!-- prov attributes -->
-
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
-
- <xs:element ref="prov:role" minOccurs="0" maxOccurs="unbounded"/>
-
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
-
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element name="activity" type="prov:IDRef"/>
+ <xs:element name="agent" type="prov:IDRef" minOccurs="0"/>
+ <xs:element name="plan" type="prov:IDRef" minOccurs="0"/>
+ <!-- prov attributes -->
+ <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element ref="prov:role" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute ref="prov:id"/>
</xs:complexType>
<xs:complexType name="Delegation">
<xs:sequence>
-
- <xs:element name="delegate" type="prov:IDRef"/>
-
- <xs:element name="responsible" type="prov:IDRef"/>
-
- <xs:element name="activity" type="prov:IDRef" minOccurs="0"/>
-
- <!-- prov attributes -->
-
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
-
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
-
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element name="delegate" type="prov:IDRef"/>
+ <xs:element name="responsible" type="prov:IDRef"/>
+ <xs:element name="activity" type="prov:IDRef" minOccurs="0"/>
+ <!-- prov attributes -->
+ <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute ref="prov:id"/>
</xs:complexType>
<xs:complexType name="Influence">
<xs:sequence>
-
- <xs:element name="influencee" type="prov:IDRef"/>
-
- <xs:element name="influencer" type="prov:IDRef"/>
-
- <!-- prov attributes -->
-
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
-
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
-
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element name="influencee" type="prov:IDRef"/>
+ <xs:element name="influencer" type="prov:IDRef"/>
+ <!-- prov attributes -->
+ <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
+ <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute ref="prov:id"/>
</xs:complexType>
<!-- Component 4 -->
- <span class="insert"><xs:complexType name="Bundle">
- <xs:complexContent>
- <xs:extension base="prov:Entity">
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
-
- </span><!-- <span class="delete">Is there a way to have this still extend prov:Entity?</span><span class="insert">bundle container and allowable PROV elements</span> -->
-
- <xs:complexType <span class="delete">name="Bundle">
+ <!-- Is there a way</span><span class="insert">Extensions</span> to <span class="delete">have this still extend prov:Entity? -->
+
+ <xs:complexType name="Bundle">
<xs:complexContent>
<xs:extension base="prov:Entity">
</xs:extension>
</xs:complexContent>
</xs:complexType>
- <xs:complexType </span>name="BundleConstructor">
+ <xs:complexType name="BundleConstructor">
<xs:sequence maxOccurs="unbounded">
- <span class="delete"><xs:group ref="prov:documentElements"/></span><span class="insert"><xs:element ref="prov:entity" minOccurs="0"/></span>
- <span class="delete"><xs:any namespace="##other" processContents="lax"</span><span class="insert"><xs:element ref="prov:activity" minOccurs="0"/>
- <xs:element ref="prov:wasGeneratedBy" minOccurs="0"/>
- <xs:element ref="prov:used" minOccurs="0"/>
- <xs:element ref="prov:wasInformedBy" minOccurs="0"/>
- <xs:element ref="prov:wasStartedBy" minOccurs="0"/>
- <xs:element ref="prov:wasEndedBy" minOccurs="0"/>
- <xs:element ref="prov:wasInvalidatedBy" minOccurs="0"/>
- <xs:element ref="prov:wasDerivedFrom" minOccurs="0"/>
- <xs:element ref="prov:wasRevisionOf" minOccurs="0"/>
- <xs:element ref="prov:wasQuotedFrom" minOccurs="0"/>
- <xs:element ref="prov:hadPrimarySource" minOccurs="0"/>
- <xs:element ref="prov:agent" minOccurs="0"/>
- <xs:element ref="prov:person" minOccurs="0"/>
- <xs:element ref="prov:organization" minOccurs="0"/>
- <xs:element ref="prov:softwareAgent" minOccurs="0"/>
- <xs:element ref="prov:wasAttributedTo" minOccurs="0"/>
- <xs:element ref="prov:wasAssociatedWith" minOccurs="0"/>
- <xs:element ref="prov:actedOnBehalfOf" minOccurs="0"/>
- <xs:element ref="prov:wasInfluencedBy" minOccurs="0"/>
- <xs:element ref="prov:bundle" minOccurs="0"/>
- <xs:element ref="prov:specializationOf" minOccurs="0"/>
- <xs:element ref="prov:alternateOf" minOccurs="0"/>
- <xs:element ref="prov:collection" minOccurs="0"/>
- <xs:element ref="prov:emptyCollection" minOccurs="0"/>
- <xs:element ref="prov:hadMember" minOccurs="0"/>
- <xs:element ref="prov:plan" minOccurs="0"/>
- <xs:element ref="prov:other" minOccurs="0"/>
- <xs:element ref="prov:internalElement"</span> minOccurs="0"/>
+ <xs:group ref="prov:documentElements"/>
+ <xs:any namespace="##other" processContents="lax" minOccurs="0"/>
</xs:sequence>
<xs:attribute ref="prov:id"/>
</xs:complexType>
@@ -2882,7 +2772,7 @@
<!--
- Typed literals are encoded by means
+ Typed literals</span><span class="insert">PROV, defined in WG Notes,</span> are <span class="delete">encoded by means
of xsi:type that represent the prov:datatype.
-->
@@ -2949,9 +2839,9 @@
<xs:element name="plan" type="prov:Plan"/>
- <!-- document <span class="insert">container and allowable PROV </span>elements -->
-
- <span class="delete"><xs:group name="documentElements">
+ <!-- document elements -->
+
+ <xs:group name="documentElements">
<xs:sequence>
<xs:element ref="prov:entity" minOccurs="0" maxOccurs="unbounded"/>
<xs:element ref="prov:activity" minOccurs="0" maxOccurs="unbounded"/>
@@ -2980,104 +2870,57 @@
<xs:element ref="prov:emptyCollection" minOccurs="0" maxOccurs="unbounded"/>
<xs:element ref="prov:hadMember" minOccurs="0" maxOccurs="unbounded"/>
<xs:element ref="prov:plan" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:internalElement" minOccurs="0" maxOccurs="unbounded"</span><span class="insert"><xs:element name="document" type="prov:Document"</span> /><span class="delete">
+ <xs:element ref="prov:internalElement" minOccurs="0" maxOccurs="unbounded" />
</xs:sequence>
- </xs:group></span>
-
- <span class="delete"><xs:element name="document" type="prov:Document" />
- </span><xs:complexType name="Document">
+ </xs:group>
+
+ <xs:element name="document" type="prov:Document" />
+ <xs:complexType name="Document">
<xs:sequence maxOccurs="unbounded">
- <span class="delete"><xs:group ref="prov:documentElements"</span><span class="insert"><xs:element ref="prov:entity"</span> minOccurs="0"/>
- <xs:element <span class="delete">name="bundleContent" type="prov:BundleConstructor"</span><span class="insert">ref="prov:activity"</span> minOccurs="0"/>
- <span class="delete"><xs:any namespace="##other" processContents="lax" minOccurs="0" /></span><span class="insert"><xs:element ref="prov:wasGeneratedBy" minOccurs="0"/>
- <xs:element ref="prov:used" minOccurs="0"/>
- <xs:element ref="prov:wasInformedBy" minOccurs="0"/>
- <xs:element ref="prov:wasStartedBy" minOccurs="0"/>
- <xs:element ref="prov:wasEndedBy" minOccurs="0"/>
- <xs:element ref="prov:wasInvalidatedBy" minOccurs="0"/>
- <xs:element ref="prov:wasDerivedFrom" minOccurs="0"/>
- <xs:element ref="prov:wasRevisionOf" minOccurs="0"/>
- <xs:element ref="prov:wasQuotedFrom" minOccurs="0"/>
- <xs:element ref="prov:hadPrimarySource" minOccurs="0"/>
- <xs:element ref="prov:agent" minOccurs="0"/>
- <xs:element ref="prov:person" minOccurs="0"/>
- <xs:element ref="prov:organization" minOccurs="0"/>
- <xs:element ref="prov:softwareAgent" minOccurs="0"/>
- <xs:element ref="prov:wasAttributedTo" minOccurs="0"/>
- <xs:element ref="prov:wasAssociatedWith" minOccurs="0"/>
- <xs:element ref="prov:actedOnBehalfOf" minOccurs="0"/>
- <xs:element ref="prov:wasInfluencedBy" minOccurs="0"/>
- <xs:element ref="prov:bundle" minOccurs="0"/>
- <xs:element ref="prov:specializationOf" minOccurs="0"/>
- <xs:element ref="prov:alternateOf" minOccurs="0"/>
- <xs:element ref="prov:collection" minOccurs="0"/>
- <xs:element ref="prov:emptyCollection" minOccurs="0"/>
- <xs:element ref="prov:hadMember" minOccurs="0"/>
- <xs:element ref="prov:plan" minOccurs="0"/>
- <xs:element ref="prov:other" minOccurs="0"/>
- <xs:element ref="prov:internalElement" minOccurs="0"/>
- <xs:element name="bundleContent" type="prov:BundleConstructor" minOccurs="0"/></span>
+ <xs:group ref="prov:documentElements" minOccurs="0"/>
+ <xs:element name="bundleContent" type="prov:BundleConstructor" minOccurs="0"/>
+ <xs:any namespace="##other" processContents="lax" minOccurs="0" />
</xs:sequence>
</xs:complexType>
-
-
- <!-- abstract element used by<span class="insert"> PROV</span> extensions -->
-
- <xs:element name="internalElement" abstract="true" /><span class="insert">
-
- <!-- 'others' element used to contain non-PROV elements -->
-
- <xs:element name="other" type="prov:Other"/>
-
- <xs:complexType name="Other">
- <xs:sequence>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- </xs:complexType></span>
+ <!-- abstract element used by extensions -->
+
+ <xs:element name="internalElement" abstract="true" />
</xs:schema>
-
-
-</pre>
+</span><span class="insert">defined in separate extension schemas.</span></p>
+<p><span class="insert">The PROV core schema is available at </span><a href="http://www.w3.org/ns/prov-core.xsd"><span class="insert">http://www.w3.org/ns/prov-core.xsd</span></a></p>
</section>
<section id="extension-schemas">
<h3><span class="secno">A.3 </span>Extension Schemas</h3>
<p>Extension schemas are schemas in the PROV Namespace that define additional PROV elements not from the PROV-DM. Workgroup Notes provide extension schemas to define their Note-introduced PROV elements. Extension schemas must import (using <code>xs:include</code>) the <b>prov-core.xsd</b> schema and make use of a substitution group on the <code>prov:internalElement</code> to add extension defined elements to the list of valid PROV elements in a bundle or document.</p>
-<p>Here is an example from the <b>prov-links.xsd</b> extension schema.</p>
-<pre title="prov-links.xsd"><?xml version="1.0" encoding="UTF-8"?>
+
+
+<p><span class="delete">Here is an example from the </span><span class="delete">prov-links.xsd</span><span class="insert">The PROV-defined</span> extension <span class="delete">schema.</span><span class="insert">schemas are available at</span></p>
+<span class="delete"><?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://www.w3.org/ns/prov#" xmlns:prov="http://www.w3.org/ns/prov#"
elementFormDefault="qualified">
-
-
- <xs:include schemaLocation="prov-core.xsd" />
-
-
+ <xs:include schemaLocation="prov-core.xsd" />
- <xs:complexType name="Mention">
-
- <xs:sequence>
-
- <xs:element name="specificEntity" type="prov:IDRef" />
-
- <xs:element name="generalEntity" type="prov:IDRef" />
-
- <xs:element name="bundle" type="prov:IDRef" />
-
- </xs:sequence>
+ <xs:complexType name="Mention">
+ <xs:sequence>
+ <xs:element name="specificEntity" type="prov:IDRef" />
+ <xs:element name="generalEntity" type="prov:IDRef" />
+ <xs:element name="bundle" type="prov:IDRef" />
+ </xs:sequence>
+ </xs:complexType>
- </xs:complexType>
-
-
-
- <xs:element name="mentionOf" type="prov:Mention" substitutionGroup="prov:internalElement" />
+ <xs:element name="mentionOf" type="prov:Mention" substitutionGroup="prov:internalElement" />
</xs:schema>
-</pre>
+</span><ul>
+<li><span class="insert">PROV-Dictionary: </span><a href="http://www.w3.org/ns/prov-dictionary.xsd"><span class="insert">http://www.w3.org/ns/prov-dictionary.xsd</span></a></li>
+<li><span class="insert">PROV-Links: </span><a href="http://www.w3.org/ns/prov-links.xsd"><span class="insert">http://www.w3.org/ns/prov-links.xsd</span></a></li>
+</ul>
</section>
</section>
@@ -3087,11 +2930,17 @@
<section id="change-log-since-wd-working-draft-12-march-2013">
<h3><span class="secno">B.1 </span><span class="delete">Changes since last version</span><span class="insert">Change Log Since WD Working Draft 12 March 2013</span></h3>
<ul>
-<li><span class="insert">Updated inline schema</span></li>
-<li><span class="insert">Updated BundleConstructor and Document sections to reflect changes to schema</span></li>
-<li>Added <span class="delete">Change Log</span><span class="insert">Other section for prov:other element and type</span></li>
-<li><span class="insert">Updated the Status of this Document</span> section</li>
-<li> <span class="insert">Added a note about potential OXM issues to Schema Modularization section, referenced FAQ entry on subject.</span></li>
+<li><span class="insert">Updated Component section descriptive text</span></li>
+<li>Added <span class="delete">Change Log</span><span class="insert">links to schemas in Schema Modularization</span> section</li>
+<li> <span class="insert">Fixed typo in Status of this Document section</span></li>
+<li><span class="insert">Added Identifier Conventions section</span></li>
+<li><span class="insert">Updated naming conventions to clarify distinction between PROV elements, attributes, and types and XML elements, attributes, and types.</span></li>
+<li><span class="insert">Added links to PROV-DM term/concepts in Table 1.</span></li>
+<li><span class="insert">Removed inline schema, added links to published schemas.</span></li>
+<li><span class="insert">Updated BundleConstructor and Document sections to reflect changes to schema.</span></li>
+<li><span class="insert">Added Other section for prov:other element and type.</span></li>
+<li><span class="insert">Updated the Status of this Document section.</span></li>
+<li><span class="insert">Added a note about potential OXM issues to Schema Modularization section, referenced FAQ entry on subject.</span></li>
</ul>
</section>
<section id="change-log-since-first-public-working-draft">
@@ -3130,10 +2979,10 @@
Reza B'Far (Oracle Corporation),
Khalid Belhajjame (University of Manchester),
James Cheney (University of Edinburgh, School of Informatics),
-Sam Coppens (IBBT),
+Sam Coppens <span class="delete">(IBBT),</span><span class="insert">(iMinds - Ghent University),</span>
David Corsar (University of Aberdeen, Computing Science),
Stephen Cresswell (The National Archives),
-Tom De Nies (IBBT),
+Tom De Nies <span class="delete">(IBBT),</span><span class="insert">(iMinds - Ghent University),</span>
Helena Deus (DERI Galway at the National University of Ireland, Galway, Ireland),
Simon Dobson (Invited expert),
Martin Doerr (Foundation for Research and Technology - Hellas(FORTH)),
@@ -3196,7 +3045,7 @@
</dd><dt id="bib-PROV-AQ">[PROV-AQ]</dt><dd>Graham Klyne; Paul Groth; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/"><cite>Provenance Access and Query</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-aq-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/</span></a>
</dd><dt id="bib-PROV-CONSTRAINTS">[PROV-CONSTRAINTS]</dt><dd>James Cheney; Paolo Missier; Luc Moreau; eds. <a href="http://www.w3.org/TR/2013/REC-prov-constraints-20130430/"><cite>Constraints of the PROV Data Model</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, W3C <span class="delete">Proposed </span>Recommendation. URL: <span class="delete">http://www.w3.org/TR/2013/PR-prov-constraints-20130312/</span><a href="http://www.w3.org/TR/2013/REC-prov-constraints-20130430/"><span class="insert">http://www.w3.org/TR/2013/REC-prov-constraints-20130430/</span></a>
</dd><dt id="bib-PROV-DC">[PROV-DC]</dt><dd>Daniel Garijo; Kai Eckert; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/"><cite>Dublin Core to PROV Mapping</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-dc-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/</span></a>
-</dd><dt id="bib-PROV-DICTIONARY">[PROV-DICTIONARY]</dt><dd>Tom De Nies; Sam Coppens; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><cite>PROV Dictionary</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/</span></a>
+</dd><dt id="bib-PROV-DICTIONARY">[PROV-DICTIONARY]</dt><dd>Tom De Nies; Sam Coppens; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><cite><span class="delete">PROV</span><span class="insert">PROV-Dictionary: Modeling Provenance for</span> Dictionary<span class="insert"> Data Structures</span></cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/</span></a>
</dd><dt id="bib-PROV-DM">[PROV-DM]</dt><dd>Luc Moreau; Paolo Missier; eds. <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/"><cite>PROV-DM: The PROV Data Model</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, W3C <span class="delete">Proposed </span>Recommendation. URL: <span class="delete">http://www.w3.org/TR/2013/PR-prov-dm-20130312/</span><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/"><span class="insert">http://www.w3.org/TR/2013/REC-prov-dm-20130430/</span></a>
</dd><dt id="bib-PROV-LINKS">[PROV-LINKS]</dt><dd>Luc Moreau; Timothy Lebo; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-links-20130430/"><cite>Linking Across Provenance Bundles</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-links-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-links-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-links-20130430/</span></a>
</dd><dt id="bib-PROV-N">[PROV-N]</dt><dd>Luc Moreau; Paolo Missier; eds. <a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/"><cite>PROV-N: The Provenance Notation</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, W3C <span class="delete">Proposed </span>Recommendation. URL: <span class="delete">http://www.w3.org/TR/2013/PR-prov-n-20130312/</span><a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/"><span class="insert">http://www.w3.org/TR/2013/REC-prov-n-20130430/</span></a>
@@ -3210,3 +3059,4 @@
</dd><dt id="bib-RFC3987">[RFC3987]</dt><dd>M. Dürst; M. Suignard. <a href="http://www.ietf.org/rfc/rfc3987.txt"><cite>Internationalized Resource Identifiers (IRIs)<span class="insert"> (RFC 3987)</span></cite></a>. January 2005. <span class="delete">RFC 3987.</span><span class="insert">RFC.</span> URL: <a href="http://www.ietf.org/rfc/rfc3987.txt">http://www.ietf.org/rfc/rfc3987.txt</a>
</dd><dt id="bib-UNISEC">[UNISEC]</dt><dd> Mark Davis; Michel Suignard. <a href="http://www.unicode.org/reports/tr36/"><cite>Unicode Security Considerations<cite></cite></cite></a>. 4 August 2010. URL: <a href="http://www.unicode.org/reports/tr36/">http://www.unicode.org/reports/tr36/</a>
</dd></dl></section></section></body></html>
+
--- a/xml/releases/NOTE-prov-xml-20130430/schema/prov-core.xsd Fri Apr 26 09:26:16 2013 +0100
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,484 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-
-<!--
- In PROV-DM, all ids are qualified names, specified as prov:QualifiedName in PROV-N.
- In this schema, all ids are instead defined as xsd:QNames.
- -->
-
-
-<xs:schema targetNamespace="http://www.w3.org/ns/prov#"
- xmlns:xs="http://www.w3.org/2001/XMLSchema"
- xmlns:prov="http://www.w3.org/ns/prov#"
- xmlns:cu="http://www.w3.org/1999/xhtml/datatypes/"
- xmlns:xml="http://www.w3.org/XML/1998/namespace"
- elementFormDefault="qualified"
- attributeFormDefault="unqualified">
-
-
-
- <xs:import namespace="http://www.w3.org/1999/xhtml/datatypes/" />
- <xs:import namespace="http://www.w3.org/XML/1998/namespace"
- schemaLocation="http://www.w3.org/2001/xml.xsd"/>
-
- <!-- Component 1 -->
-
- <xs:complexType name="Entity">
- <xs:sequence>
- <!-- prov attributes -->
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:location" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:value" minOccurs="0"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <xs:complexType name="Activity">
- <xs:sequence>
- <xs:element name="startTime" type="xs:dateTime" minOccurs="0"/>
- <xs:element name="endTime" type="xs:dateTime" minOccurs="0"/>
- <!-- prov attributes -->
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:location" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <xs:complexType name="Generation">
- <xs:sequence>
- <xs:element name="entity" type="prov:IDRef"/>
- <xs:element name="activity" type="prov:IDRef" minOccurs="0"/>
- <xs:element name="time" type="xs:dateTime" minOccurs="0"/>
- <!-- prov attributes -->
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:location" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:role" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <xs:complexType name="Usage">
- <xs:sequence>
- <xs:element name="activity" type="prov:IDRef"/>
- <xs:element name="entity" type="prov:IDRef" minOccurs="0"/>
- <xs:element name="time" type="xs:dateTime" minOccurs="0"/>
- <!-- prov attributes -->
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:location" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:role" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <xs:complexType name="Communication">
- <xs:sequence>
- <xs:element name="informed" type="prov:IDRef"/>
- <xs:element name="informant" type="prov:IDRef"/>
- <!-- prov attributes -->
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <xs:complexType name="Start">
- <xs:sequence>
- <xs:element name="activity" type="prov:IDRef"/>
- <xs:element name="trigger" type="prov:IDRef" minOccurs="0"/>
- <xs:element name="starter" type="prov:IDRef" minOccurs="0"/>
- <xs:element name="time" type="xs:dateTime" minOccurs="0"/>
- <!-- prov attributes -->
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:location" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:role" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <xs:complexType name="End">
- <xs:sequence>
- <xs:element name="activity" type="prov:IDRef"/>
- <xs:element name="trigger" type="prov:IDRef" minOccurs="0"/>
- <xs:element name="ender" type="prov:IDRef" minOccurs="0"/>
- <xs:element name="time" type="xs:dateTime" minOccurs="0"/>
- <!-- prov attributes -->
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:location" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:role" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <xs:complexType name="Invalidation">
- <xs:sequence>
- <xs:element name="entity" type="prov:IDRef"/>
- <xs:element name="activity" type="prov:IDRef" minOccurs="0"/>
- <xs:element name="time" type="xs:dateTime" minOccurs="0"/>
- <!-- prov attributes -->
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:location" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:role" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <!-- Component 2 -->
-
- <xs:complexType name="Derivation">
- <xs:sequence>
- <xs:element name="generatedEntity" type="prov:IDRef"/>
- <xs:element name="usedEntity" type="prov:IDRef"/>
- <xs:element name="activity" type="prov:IDRef" minOccurs="0"/>
- <xs:element name="generation" type="prov:IDRef" minOccurs="0"/>
- <xs:element name="usage" type="prov:IDRef" minOccurs="0"/>
- <!-- prov attributes -->
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <xs:complexType name="Revision">
- <xs:complexContent>
- <xs:extension base="prov:Derivation">
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
-
- <xs:complexType name="Quotation">
- <xs:complexContent>
- <xs:extension base="prov:Derivation">
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
-
- <xs:complexType name="PrimarySource">
- <xs:complexContent>
- <xs:extension base="prov:Derivation">
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
-
- <!-- Component 3 -->
-
- <xs:complexType name="Agent">
- <xs:sequence>
- <!-- prov attributes -->
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:location" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <xs:complexType name="Person">
- <xs:complexContent>
- <xs:extension base="prov:Agent">
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
-
- <xs:complexType name="Organization">
- <xs:complexContent>
- <xs:extension base="prov:Agent">
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
-
- <xs:complexType name="SoftwareAgent">
- <xs:complexContent>
- <xs:extension base="prov:Agent">
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
-
- <xs:complexType name="Attribution">
- <xs:sequence>
- <xs:element name="entity" type="prov:IDRef"/>
- <xs:element name="agent" type="prov:IDRef"/>
- <!-- prov attributes -->
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <xs:complexType name="Association">
- <xs:sequence>
- <xs:element name="activity" type="prov:IDRef"/>
- <xs:element name="agent" type="prov:IDRef" minOccurs="0"/>
- <xs:element name="plan" type="prov:IDRef" minOccurs="0"/>
- <!-- prov attributes -->
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:role" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <xs:complexType name="Delegation">
- <xs:sequence>
- <xs:element name="delegate" type="prov:IDRef"/>
- <xs:element name="responsible" type="prov:IDRef"/>
- <xs:element name="activity" type="prov:IDRef" minOccurs="0"/>
- <!-- prov attributes -->
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <xs:complexType name="Influence">
- <xs:sequence>
- <xs:element name="influencee" type="prov:IDRef"/>
- <xs:element name="influencer" type="prov:IDRef"/>
- <!-- prov attributes -->
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <!-- Component 4 -->
-
- <xs:complexType name="Bundle">
- <xs:complexContent>
- <xs:extension base="prov:Entity">
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
-
- <!-- bundle container and allowable PROV elements -->
-
- <xs:complexType name="BundleConstructor">
- <xs:sequence maxOccurs="unbounded">
- <xs:element ref="prov:entity" minOccurs="0"/>
- <xs:element ref="prov:activity" minOccurs="0"/>
- <xs:element ref="prov:wasGeneratedBy" minOccurs="0"/>
- <xs:element ref="prov:used" minOccurs="0"/>
- <xs:element ref="prov:wasInformedBy" minOccurs="0"/>
- <xs:element ref="prov:wasStartedBy" minOccurs="0"/>
- <xs:element ref="prov:wasEndedBy" minOccurs="0"/>
- <xs:element ref="prov:wasInvalidatedBy" minOccurs="0"/>
- <xs:element ref="prov:wasDerivedFrom" minOccurs="0"/>
- <xs:element ref="prov:wasRevisionOf" minOccurs="0"/>
- <xs:element ref="prov:wasQuotedFrom" minOccurs="0"/>
- <xs:element ref="prov:hadPrimarySource" minOccurs="0"/>
- <xs:element ref="prov:agent" minOccurs="0"/>
- <xs:element ref="prov:person" minOccurs="0"/>
- <xs:element ref="prov:organization" minOccurs="0"/>
- <xs:element ref="prov:softwareAgent" minOccurs="0"/>
- <xs:element ref="prov:wasAttributedTo" minOccurs="0"/>
- <xs:element ref="prov:wasAssociatedWith" minOccurs="0"/>
- <xs:element ref="prov:actedOnBehalfOf" minOccurs="0"/>
- <xs:element ref="prov:wasInfluencedBy" minOccurs="0"/>
- <xs:element ref="prov:bundle" minOccurs="0"/>
- <xs:element ref="prov:specializationOf" minOccurs="0"/>
- <xs:element ref="prov:alternateOf" minOccurs="0"/>
- <xs:element ref="prov:collection" minOccurs="0"/>
- <xs:element ref="prov:emptyCollection" minOccurs="0"/>
- <xs:element ref="prov:hadMember" minOccurs="0"/>
- <xs:element ref="prov:plan" minOccurs="0"/>
- <xs:element ref="prov:other" minOccurs="0"/>
- <xs:element ref="prov:internalElement" minOccurs="0"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <!-- Component 5 -->
-
- <xs:complexType name="Specialization">
- <xs:sequence>
- <xs:element name="specificEntity" type="prov:IDRef"/>
- <xs:element name="generalEntity" type="prov:IDRef"/>
- </xs:sequence>
- </xs:complexType>
-
- <xs:complexType name="Alternate">
- <xs:sequence>
- <xs:element name="alternate1" type="prov:IDRef"/>
- <xs:element name="alternate2" type="prov:IDRef"/>
- </xs:sequence>
- </xs:complexType>
-
- <!-- Component 6 -->
-
- <xs:complexType name="Collection">
- <xs:complexContent>
- <xs:extension base="prov:Entity">
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
-
- <xs:complexType name="EmptyCollection">
- <xs:complexContent>
- <xs:extension base="prov:Collection">
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
-
- <xs:complexType name="Membership">
- <xs:sequence>
- <xs:element name="collection" type="prov:IDRef"/>
- <xs:element name="entity" type="prov:IDRef" maxOccurs="unbounded"/>
- </xs:sequence>
- </xs:complexType>
-
- <xs:complexType name="Plan">
- <xs:complexContent>
- <xs:extension base="prov:Entity">
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
-
- <xs:complexType name="InternationalizedString">
- <xs:simpleContent>
- <xs:extension base="xs:string">
- <xs:attribute ref="xml:lang" use="optional"/>
- </xs:extension>
- </xs:simpleContent>
- </xs:complexType>
-
-
- <!--
- Typed literals are encoded by means
- of xsi:type that represent the prov:datatype.
- -->
-
- <xs:element name="label" type="prov:InternationalizedString"/>
- <xs:element name="role" type="xs:anySimpleType"/>
- <xs:element name="type" type="xs:anySimpleType"/>
- <xs:element name="location" type="xs:anySimpleType"/>
- <xs:element name="value" type="xs:anySimpleType"/>
-
- <xs:attribute name="id" type="xs:QName"/>
- <xs:attribute name="ref" type="xs:QName"/>
-
- <xs:complexType name="IDRef">
- <xs:attribute ref="prov:ref" use="required" />
- </xs:complexType>
-
- <!--
- top-level definition of elements following the salami slice XSD design pattern
- to encourage integration within existing non-prov XML documents.
- -->
-
- <!-- Component 1 elements -->
-
- <xs:element name="entity" type="prov:Entity"/>
- <xs:element name="activity" type="prov:Activity"/>
- <xs:element name="wasGeneratedBy" type="prov:Generation"/>
- <xs:element name="used" type="prov:Usage"/>
- <xs:element name="wasInformedBy" type="prov:Communication"/>
- <xs:element name="wasStartedBy" type="prov:Start"/>
- <xs:element name="wasEndedBy" type="prov:End"/>
- <xs:element name="wasInvalidatedBy" type="prov:Invalidation"/>
-
- <!-- Component 2 elements -->
-
- <xs:element name="wasDerivedFrom" type="prov:Derivation"/>
- <xs:element name="wasRevisionOf" type="prov:Revision"/>
- <xs:element name="wasQuotedFrom" type="prov:Quotation"/>
- <xs:element name="hadPrimarySource" type="prov:PrimarySource"/>
-
- <!-- Component 3 elements -->
-
- <xs:element name="agent" type="prov:Agent"/>
- <xs:element name="person" type="prov:Person"/>
- <xs:element name="organization" type="prov:Organization"/>
- <xs:element name="softwareAgent" type="prov:SoftwareAgent"/>
- <xs:element name="wasAttributedTo" type="prov:Attribution"/>
- <xs:element name="wasAssociatedWith" type="prov:Association"/>
- <xs:element name="actedOnBehalfOf" type="prov:Delegation"/>
- <xs:element name="wasInfluencedBy" type="prov:Influence"/>
-
- <!-- Component 5 elements -->
-
- <xs:element name="bundle" type="prov:Bundle"/>
- <xs:element name="specializationOf" type="prov:Specialization"/>
- <xs:element name="alternateOf" type="prov:Alternate"/>
-
- <!-- Component 6 elements -->
-
- <xs:element name="hadMember" type="prov:Membership"/>
- <xs:element name="collection" type="prov:Collection"/>
- <xs:element name="emptyCollection" type="prov:EmptyCollection"/>
-
- <!-- Component 7 elements -->
-
- <xs:element name="plan" type="prov:Plan"/>
-
- <!-- document container and allowable PROV elements -->
-
- <xs:element name="document" type="prov:Document" />
-
- <xs:complexType name="Document">
- <xs:sequence maxOccurs="unbounded">
- <xs:element ref="prov:entity" minOccurs="0"/>
- <xs:element ref="prov:activity" minOccurs="0"/>
- <xs:element ref="prov:wasGeneratedBy" minOccurs="0"/>
- <xs:element ref="prov:used" minOccurs="0"/>
- <xs:element ref="prov:wasInformedBy" minOccurs="0"/>
- <xs:element ref="prov:wasStartedBy" minOccurs="0"/>
- <xs:element ref="prov:wasEndedBy" minOccurs="0"/>
- <xs:element ref="prov:wasInvalidatedBy" minOccurs="0"/>
- <xs:element ref="prov:wasDerivedFrom" minOccurs="0"/>
- <xs:element ref="prov:wasRevisionOf" minOccurs="0"/>
- <xs:element ref="prov:wasQuotedFrom" minOccurs="0"/>
- <xs:element ref="prov:hadPrimarySource" minOccurs="0"/>
- <xs:element ref="prov:agent" minOccurs="0"/>
- <xs:element ref="prov:person" minOccurs="0"/>
- <xs:element ref="prov:organization" minOccurs="0"/>
- <xs:element ref="prov:softwareAgent" minOccurs="0"/>
- <xs:element ref="prov:wasAttributedTo" minOccurs="0"/>
- <xs:element ref="prov:wasAssociatedWith" minOccurs="0"/>
- <xs:element ref="prov:actedOnBehalfOf" minOccurs="0"/>
- <xs:element ref="prov:wasInfluencedBy" minOccurs="0"/>
- <xs:element ref="prov:bundle" minOccurs="0"/>
- <xs:element ref="prov:specializationOf" minOccurs="0"/>
- <xs:element ref="prov:alternateOf" minOccurs="0"/>
- <xs:element ref="prov:collection" minOccurs="0"/>
- <xs:element ref="prov:emptyCollection" minOccurs="0"/>
- <xs:element ref="prov:hadMember" minOccurs="0"/>
- <xs:element ref="prov:plan" minOccurs="0"/>
- <xs:element ref="prov:other" minOccurs="0"/>
- <xs:element ref="prov:internalElement" minOccurs="0"/>
- <xs:element name="bundleContent" type="prov:BundleConstructor" minOccurs="0"/>
- </xs:sequence>
- </xs:complexType>
-
- <!-- abstract element used by PROV extensions -->
-
- <xs:element name="internalElement" abstract="true" />
-
- <!-- 'others' element used to contain non-PROV elements -->
-
- <xs:element name="other" type="prov:Other"/>
-
- <xs:complexType name="Other">
- <xs:sequence>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- </xs:complexType>
-
-</xs:schema>
--- a/xml/releases/NOTE-prov-xml-20130430/schema/prov-dictionary.xsd Fri Apr 26 09:26:16 2013 +0100
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,81 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
- targetNamespace="http://www.w3.org/ns/prov#" xmlns:prov="http://www.w3.org/ns/prov#"
- elementFormDefault="qualified">
-
- <xs:include schemaLocation="prov-core.xsd" />
-
- <!-- Dictionary -->
- <xs:complexType name="Dictionary">
- <xs:complexContent>
- <xs:extension base="prov:Collection">
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
-
- <xs:element name="dictionary" type="prov:Dictionary" substitutionGroup="prov:internalElement" />
-
- <!-- Empty Dictionary -->
- <xs:complexType name="EmptyDictionary">
- <xs:complexContent>
- <xs:extension base="prov:Dictionary">
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
-
- <xs:element name="emptyDictionary" type="prov:EmptyDictionary" substitutionGroup="prov:internalElement" />
-
- <!-- Key-Entity Pair -->
- <xs:complexType name="KeyEntityPair">
- <xs:sequence>
- <xs:element name="entity" type="prov:IDRef" />
- <xs:element name="key" type="xs:anySimpleType" />
- </xs:sequence>
- </xs:complexType>
-
- <!-- do we need to have this use the substitutionGroup? -->
- <xs:element name="keyEntityPair" type="prov:KeyEntityPair" substitutionGroup="prov:internalElement"/>
-
- <!-- Dictionary Membership -->
- <xs:complexType name="DictionaryMembership">
- <xs:sequence>
- <xs:element name="dictionary" type="prov:IDRef"/>
- <xs:element name="keyEntityPair" type="prov:KeyEntityPair" maxOccurs="unbounded"/>
- </xs:sequence>
- </xs:complexType>
-
- <xs:element name="hadDictionaryMember" type="prov:DictionaryMembership" substitutionGroup="prov:internalElement"/>
-
- <!-- Insertion -->
- <xs:complexType name="Insertion">
- <xs:sequence>
- <xs:element name="newDictionary" type="prov:IDRef"/>
- <xs:element name="oldDictionary" type="prov:IDRef"/>
- <xs:element name="keyEntityPair" type="prov:KeyEntityPair" maxOccurs="unbounded"/>
- <!-- prov attributes -->
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <xs:element name="derivedByInsertionFrom" type="prov:Insertion" substitutionGroup="prov:internalElement"/>
-
- <!-- Removal -->
- <xs:complexType name="Removal">
- <xs:sequence>
- <xs:element name="newDictionary" type="prov:IDRef"/>
- <xs:element name="oldDictionary" type="prov:IDRef"/>
- <xs:element name="key" type="xs:anySimpleType" maxOccurs="unbounded" />
- <!-- prov attributes -->
- <xs:element ref="prov:label" minOccurs="0" maxOccurs="unbounded"/>
- <xs:element ref="prov:type" minOccurs="0" maxOccurs="unbounded"/>
- <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
- </xs:sequence>
- <xs:attribute ref="prov:id"/>
- </xs:complexType>
-
- <xs:element name="derivedByRemovalFrom" type="prov:Removal" substitutionGroup="prov:internalElement"/>
-
-</xs:schema>
--- a/xml/releases/NOTE-prov-xml-20130430/schema/prov-links.xsd Fri Apr 26 09:26:16 2013 +0100
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,18 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
- targetNamespace="http://www.w3.org/ns/prov#" xmlns:prov="http://www.w3.org/ns/prov#"
- elementFormDefault="qualified">
-
- <xs:include schemaLocation="prov-core.xsd" />
-
- <xs:complexType name="Mention">
- <xs:sequence>
- <xs:element name="specificEntity" type="prov:IDRef" />
- <xs:element name="generalEntity" type="prov:IDRef" />
- <xs:element name="bundle" type="prov:IDRef" />
- </xs:sequence>
- </xs:complexType>
-
- <xs:element name="mentionOf" type="prov:Mention" substitutionGroup="prov:internalElement" />
-
-</xs:schema>
\ No newline at end of file
--- a/xml/releases/NOTE-prov-xml-20130430/schema/prov.xsd Fri Apr 26 09:26:16 2013 +0100
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,12 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<xs:schema targetNamespace="http://www.w3.org/ns/prov#"
- xmlns:xs="http://www.w3.org/2001/XMLSchema"
- xmlns:prov="http://www.w3.org/ns/prov#"
- elementFormDefault="qualified"
- attributeFormDefault="unqualified">
-
- <xs:include schemaLocation="prov-core.xsd"/>
- <xs:include schemaLocation="prov-dictionary.xsd"/>
- <xs:include schemaLocation="prov-links.xsd"/>
-
-</xs:schema>