--- a/xml/prov-xml.html Thu Nov 08 14:11:54 2012 -0700
+++ b/xml/prov-xml.html Thu Nov 08 16:13:12 2012 -0700
@@ -49,87 +49,8 @@
<script src="../model/glossary.js" class="remove"></script>
-<!--
- <script class="remove">
-function insertSchema(doc, content) {
-// return '<code class="language-xml"> ' + doc._esc(content) + '</code>';
- return doc._esc(content);
-}
-
-function htmlEncode(value){
- return $('<div/>').text(value).html();
-}
-
-function insertSchemaDefinition(doc, content, name) {
-
- var xml=$.parseXML(content);
- var segment = $(xml).find('complexType[name~="' + name + '"]')[0];
-
- return doc._esc((new XMLSerializer()).serializeToString(segment));
-}
-
-function insertSchemaEntity(doc, content) { return insertSchemaDefinition(doc,content,'Entity'); }
-function insertSchemaActivity(doc, content) { return insertSchemaDefinition(doc,content,'Activity'); }
-function insertSchemaWasGeneratedBy(doc, content) { return insertSchemaDefinition(doc,content,'WasGeneratedBy'); }
-function insertSchemaUsed(doc, content) { return insertSchemaDefinition(doc,content,'Used'); }
-function insertSchemaWasStartedBy(doc, content) { return insertSchemaDefinition(doc,content,'WasStartedBy'); }
-function insertSchemaWasEndedBy(doc, content) { return insertSchemaDefinition(doc,content,'WasEndedBy'); }
-function insertSchemaWasInformedBy(doc, content) { return insertSchemaDefinition(doc,content,'WasInformedBy'); }
-function insertSchemaWasStartedByActivity(doc, content) { return insertSchemaDefinition(doc,content,'WasStartedByActivity'); }
-
-function insertSchemaAgent(doc, content) { return insertSchemaDefinition(doc,content,'Agent'); }
-function insertSchemaWasAttributedTo(doc, content) { return insertSchemaDefinition(doc,content,'WasAttributedTo'); }
-function insertSchemaWasAssociatedWith(doc, content) { return insertSchemaDefinition(doc,content,'WasAssociatedWith'); }
-function insertSchemaActedOnBehalfOf(doc, content) { return insertSchemaDefinition(doc,content,'ActedOnBehalfOf'); }
-
-
-function insertSchemaWasDerivedFrom(doc, content) { return insertSchemaDefinition(doc,content,'WasDerivedFrom'); }
-function insertSchemaWasRevisionOf(doc, content) { return insertSchemaDefinition(doc,content,'WasRevisionOf'); }
-function insertSchemaWasQuotedFrom(doc, content) { return insertSchemaDefinition(doc,content,'WasQuotedFrom'); }
-function insertSchemaHadOriginalSource(doc, content) { return insertSchemaDefinition(doc,content,'HadOriginalSource'); }
-function insertSchemaTracedTo(doc, content) { return insertSchemaDefinition(doc,content,'TracedTo'); }
-
-function insertSchemaSpecializationOf(doc, content) { return insertSchemaDefinition(doc,content,'SpecializationOf'); }
-function insertSchemaAlternateOf(doc, content) { return insertSchemaDefinition(doc,content,'AlternateOf'); }
-
-function insertSchemaNote(doc, content) { return insertSchemaDefinition(doc,content,'Note'); }
-function insertSchemaHasAnnotation(doc, content) { return insertSchemaDefinition(doc,content,'HasAnnotation'); }
-
-function insertSchemaDefinitionOriginal(doc, content) {
- // perform transformations to make it render and prettier
-
- // NB - this is hardcoded to entity at present. The respec js doesn't appear
- // to pass in the element that it's working with - just the entire doc,
- // and the respec object.
-
- var xml=$.parseXML(content);
- var segment = $(xml).find('complexType[name~="Entity"]')[0];
- return doc._esc((new XMLSerializer()).serializeToString(segment));
-}
- function updateGlossaryRefs() {
- $('.glossary-ref').each(function(index) {
- var ref=$(this).attr('data-ref');
- var span=$(this).attr('data-withspan')
- $(this).removeAttr('data-withspan');
- $(this).removeAttr('data-ref');
-
- $('#'+ref+'.glossary').contents().clone().appendTo($(this));
- $(this).attr('prov:hadOriginalSource',glossary_hg);
- if (span) {
- $(this).children('dfn').replaceWith(function(){return $('<span>').addClass('dfn').append($(this).contents())});
- }
- });
- }
- $(document).ready(function(){
- // if glossary is in a string:
- $('#glossary_div').html(glossary_string)
- updateGlossaryRefs();
- });
-
- </script>
- -->
-
<!-- This is a test to see if the respec data-oninclude is working -->
+ <!--
<script>
function insertSchemaComplexType(doc, content, name) {
var xml = $.parseXML(content);
@@ -209,6 +130,7 @@
function insertSchema_value(doc, content) { return insertSchemaElement(doc, content, "value"); }
</script>
+ -->
<script>
$(function() {
@@ -243,65 +165,75 @@
berjon.biblio[k] = extraReferences[k];
};
var extraReferences = {
+
"CLOCK":
"Lamport, L. "+
"<a href=\"http://research.microsoft.com/users/lamport/pubs/time-clocks.pdf\"><cite>Time, clocks, and the ordering of events in a distributed system</cite></a>."+
"Communications of the ACM 21 (7): 558–565. 1978. "+
"URL: <a href=\"http://research.microsoft.com/users/lamport/pubs/time-clocks.pdf\">http://research.microsoft.com/users/lamport/pubs/time-clocks.pdf</a> " +
"DOI: doi:10.1145/359545.359563.",
+
"CSP":
"Hoare, C. A. R. "+
"<a href=\"http://www.usingcsp.com/cspbook.pdf\"><cite>Communicating Sequential Processes</cite></a>."+
"Prentice-Hall. 1985"+
"URL: <a href=\"http://www.usingcsp.com/cspbook.pdf\">http://www.usingcsp.com/cspbook.pdf</a>",
+
"Logic":
"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>",
+
"PROV-SEM":
"James Cheney "+
"<a href=\"http://www.w3.org/2011/prov/wiki/FormalSemanticsStrawman\"><cite>Formal Semantics Strawman</cite></a>. "+
"2011, Work in progress. "+
"URL: <a href=\"http://www.w3.org/2011/prov/wiki/FormalSemanticsStrawman\">http://www.w3.org/2011/prov/wiki/FormalSemanticsStrawman</a>",
-
+
"PROV-PRIMER":
"Yolanda Gil and Simon Miles (eds.) Khalid Belhajjame, Helena Deus, Daniel Garijo, Graham Klyne, Paolo Missier, Stian Soiland-Reyes, and Stephan Zednik "+
"<a href=\"http://www.w3.org/TR/prov-primer/\"><cite>Prov Model Primer</cite></a>. "+
- "2011, Working Draft. "+
+ "2012, Working Draft. "+
"URL: <a href=\"http://www.w3.org/TR/prov-primer/\">http://www.w3.org/TR/prov-primer/</a>",
"PROV-O":
- "Satya Sahoo and Deborah McGuinness (eds.) Khalid Belhajjame, James Cheney, Daniel Garijo, Timothy Lebo, Stian Soiland-Reyes, and Stephan Zednik "+
+ "Timothy Lebo, Satya Sahoo and Deborah McGuinness (eds.) Khalid Belhajjame, James Cheney, David Corsar, Daniel Garijo, Stian Soiland-Reyes, and Stephan Zednik "+
"<a href=\"http://www.w3.org/TR/prov-o/\"><cite>Provenance Formal Model</cite></a>. "+
- "2011, Working Draft. "+
+ "2012, Working Draft. "+
"URL: <a href=\"http://www.w3.org/TR/prov-o/\">http://www.w3.org/TR/prov-o/</a>",
"PROV-DM":
"Luc Moreau and Paolo Missier (eds.) ... "+
"<a href=\"http://www.w3.org/TR/prov-dm/\"><cite>PART 1: PROV-DM ...</cite></a>. "+
- "2011, Working Draft. "+
+ "2012, Working Draft. "+
"URL: <a href=\"http://www.w3.org/TR/prov-dm/\">http://www.w3.org/TR/prov-dm/</a>",
- "PROV-DM-CONSTRAINTS":
- "Luc Moreau and Paolo Missier (eds.) ... "+
- "<a href=\"http://www.w3.org/TR/prov-dm-constraints/\"><cite>PROV-DM Constraints</cite></a>. "+
- "2011, Working Draft. "+
- "URL: <a href=\"http://www.w3.org/TR/prov-dm-constraints/\">http://www.w3.org/TR/prov-dm-constraints/</a>",
+ "PROV-CONSTRAINTS":
+ "James Cheney, Paolo Missier, and Luc Moreau (eds.) "+
+ "<a href=\"http://www.w3.org/TR/prov-constraints/\"><cite>Constraints of the PROV Data Model</cite></a>. "+
+ "2012, Working Draft. "+
+ "URL: <a href=\"http://www.w3.org/TR/prov-constraints/\">http://www.w3.org/TR/prov-constraints/</a>",
"PROV-N":
- "Luc Moreau and Paolo Missier (eds.) ... "+
- "<a href=\"http://www.w3.org/TR/prov-n/\"><cite>PROV-N ....</cite></a>. "+
- "2011, Working Draft. "+
+ "Luc Moreau and Paolo Missier (eds.) James Cheney, Stian Soiland-Reyes "+
+ "<a href=\"http://www.w3.org/TR/prov-n/\"><cite>PROV-N: The Provenance Notation</cite></a>. "+
+ "2012, Working Draft. "+
"URL: <a href=\"http://www.w3.org/TR/prov-n/\">http://www.w3.org/TR/prov-n/</a>",
-
+
"PROV-AQ":
"Graham Klyne and Paul Groth (eds.) Luc Moreau, Olaf Hartig, Yogesh Simmhan, James Meyers, Timothy Lebo, Khalid Belhajjame, and Simon Miles "+
"<a href=\"http://www.w3.org/TR/prov-aq/\"><cite>Provenance Access and Query</cite></a>. "+
- "2011, Working Draft. "+
+ "2012, Working Draft. "+
"URL: <a href=\"http://www.w3.org/TR/prov-aq/\">http://www.w3.org/TR/prov-aq/</a>",
+
+ "Mappings":
+ "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>",
};
var respecConfig = {
// specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
@@ -355,9 +287,11 @@
// This is optional, uncomment if you have authors as well as editors.
// only "name" is required. Same format as editors.
- // authors: [
- // { },
- // ],
+ authors: [
+ { name: "Luc Moreau",
+ url: "http://www.ecs.soton.ac.uk/~lavm/",
+ company: "University of Southampton" },
+ ],
// name of the WG
wg: "Provenance Working Group",
@@ -386,49 +320,32 @@
<section id="abstract">
<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 W3C
-provenance (PROV) family of specifications.
-PROV-DM distinguishes core structures, forming the essence of provenance information, from
-extended structures catering for more specific uses of provenance.
-PROV-DM is organized in six components, respectively dealing with:
-(1) entities and activities, and the time at which they were created, used, or ended;
-(2) derivations of entities from entities;
-(3) agents bearing responsibility for entities that were generated and activities that happened;
-(4) a notion of bundle, a mechanism to support provenance of provenance;
-(5) properties to link entities that refer to the same thing; and,
-(6) collections forming a logical structure for its members.
+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 W3C 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>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>
</section> <!-- end abstract -->
<section id="sotd">
+
<h4>PROV Family of Specifications</h4>
-This document is part of the PROV family of specifications, a set of specifications aiming to define the various aspects that are necessary to achieve the vision of inter-operable
-interchange of provenance information in heterogeneous environments such as the Web. The specifications are as follows.
+This document is part of the PROV family of specifications, a set of specifications defining various aspects that are necessary to achieve the vision of inter-operable
+interchange of provenance information in heterogeneous environments such as the Web. The specifications are:
<ul>
-<li> PROV-DM, the PROV data model for provenance,</li>
-<li> PROV-DM-CONSTRAINTS, a set of constraints applying to the PROV data model,</li>
-<li> PROV-N, a notation for provenance aimed at human consumption,</li>
-<li> PROV-O, the PROV ontology, an OWL-RL ontology allowing the mapping of PROV to RDF;</li>
-<li> PROV-AQ, the mechanisms for accessing and querying provenance; </li>
-<li> PROV-PRIMER, a primer for the PROV data model,</li>
-<li> PROV-SEM, a formal semantics for the PROV data model.</li>
-<li> PROV-XML, an XML schema for the PROV data model (this document).</li>
+<li> <a href="http://www.w3.org/TR/prov-dm/">PROV-DM</a>, the PROV data model for provenance [[PROV-DM]];</li>
+<li> <a href="http://www.w3.org/TR/prov-constraints/">PROV-CONSTRAINTS</a>, a set of constraints applying to the PROV data model [[PROV-CONSTRAINTS]];</li>
+<li> <a href="http://www.w3.org/TR/prov-n/">PROV-N</a>, a notation for provenance aimed at human consumption [[PROV-N]];</li>
+<li> <a href="http://www.w3.org/TR/prov-o/">PROV-O</a>, the PROV ontology, an OWL2 ontology allowing the mapping of PROV to RDF [[PROV-O]];</li>
+<li> <a href="http://www.w3.org/TR/prov-aq/">PROV-AQ</a>, the mechanisms for accessing and querying provenance [[PROV-AQ]]; </li>
+<li> <a href="http://www.w3.org/TR/prov-primer/">PROV-PRIMER</a>, a primer for the PROV data model [[PROV-PRIMER]].</li>
+<li> <a href="http://www.w3.org/TR/prov-xml/">PROV-XML</a>, an XML schema for the PROV data model (this document).</li>
</ul>
<h4>How to read the PROV Family of Specifications</h4>
<ul>
-<li>The primer is the entry point to PROV offering a pedagogical presentation of the provenance model.</li>
-<li>The Linked Data and Semantic Web community should focus on PROV-O defining PROV classes and properties specified in an OWL-RL ontology. For further details, PROV-DM and PROV-DM-CONSTRAINTS specify the constraints applicable to the data model, and its interpretation. PROV-SEM provides a mathematical semantics.</li>
-<li>The XML community should focus on PROV-XML defining an XML schema for PROV-DM. Further details can also be found in PROV-DM, PROV-DM-CONSTRAINTS, and PROV-SEM.</li>
-<li>Developers seeking to retrieve or publish provenance should focus of PROV-AQ.</li>
+<li>The primer is the entry point to PROV offering an introduction to the provenance model.</li>
+<li>The Linked Data and Semantic Web community should focus on PROV-O defining PROV classes and properties specified in an OWL2 ontology. For further details, PROV-DM and PROV-CONSTRAINTS specify the constraints applicable to the data model, and its interpretation. </li>
+<li>The XML community should focus on PROV-XML (this document) defining an XML schema for PROV-DM. Further details can also be found in PROV-DM, PROV-DM-CONSTRAINTS, and PROV-SEM.</li>
+<li>Developers seeking to retrieve or publish provenance should focus on PROV-AQ.</li>
<li>Readers seeking to implement other PROV serializations
-should focus on PROV-DM and PROV-DM-CONSTRAINTS. PROV-O, PROV-N, PROV-XML offer examples of mapping to RDF, text, and XML, respectively.</li>
+should focus on PROV-DM and PROV-CONSTRAINTS. PROV-O, PROV-N, and PROV-XML offer examples of mapping to RDF, text, and XML, respectively.</li>
</ul>
</section> <!-- end sotd -->
@@ -436,50 +353,37 @@
<h2>Introduction</h2>
<p>
-For the purpose of this specification, <dfn>provenance</dfn> 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.
+For the purpose of this specification, <dfn>provenance</dfn> 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>A set of specifications, referred to as the PROV family of specifications, define the various aspects
-that are necessary to achieve this vision in an interoperable
-way:</p>
-<ul>
-<li>A data model for provenance, which is presented in three documents:
+<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 [[Mappings]]. 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> PROV-DM (part I): the provenance data model itself, expressed in natural language (this document);
-<li> PROV-DM-CONSTRAINTS (part II): constraints underpinning the data model [[PROV-DM-CONSTRAINTS]];
-<li> PROV-N (part III): a notation to express instances of that data model for human consumption [[PROV-N]];
-</ul>
-</li>
-<li>PROV-O: the PROV ontology, an OWL-RL ontology allowing the mapping of PROV to RDF [[PROV-O]];</li>
-<li>PROV-AQ: the mechanisms for accessing and querying provenance [[PROV-AQ]];</li>
-<li>PROV-PRIMER: a primer for the PROV approach [[PROV-PRIMER]];</li>
-<li>PROV-SEM: semantics of the PROV-DM data model [[PROV-SEM]];</li>
-<li>PROV-XML: an XML schema for the PROV data model.</li>
+<li> component 1: entities and activities, and the time at which they were created, used, or ended;
+<li> component 2: derivations of entities from others;
+<li> component 3: agents bearing responsibility for entities that were generated and activities that happened;
+<li> component 4: bundles, a mechanism to support provenance of provenance;
+<li> component 5: properties to link entities that refer to a same thing;
+<li> component 6: collections forming a logical structure for its members.
</ul>
<p>
- PROV-DM is a domain-agnostic model, but with clear extensibility points allowing further domain-specific and
-application-specific extensions to be defined.
-The PROV data model is structured according to six components covering various aspects of provenance:</p>
-<ol>
-<li> component 1: entities and activities, and the time at which they were created, used, or ended;
-<li> component 2: agents bearing responsibility for entities that were generated and actities that happened;
-<li> component 3: derivations between entities;
-<li> component 4: properties to link entities that refer to a same thing;
-<li> component 5: collections of entities, whose provenance can itself be tracked;
-<li> component 6: a simple annotation mechanism.
-</ol>
+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="structure-of-this-document">
<h3>Structure of this Document</h3>
+<p><a href="#schema-components">Section 2</a> provides an overview of the PROV XML Schema elements and types</p>
+<p><a href="#prov-xml-schema">Appendix A</a> contains the full PROV-XML Schema</p>
</section> <!-- end structure-of-this-document -->
<section id="prov-namespace">
@@ -724,12 +628,14 @@
</pre>
<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>document</prov:type>
+ <prov:type xsi:type="xsd:QName">document</prov:type>
<ex:version>2</ex:version>
</prov:entity></b>
@@ -760,13 +666,15 @@
</pre>
<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>ex:edit</prov:type>
+ <prov:type xsi:type="xsd:QName">ex:edit</prov:type>
<ex:host>server.example.org</ex:host>
</prov:activity></b>
@@ -899,14 +807,17 @@
<xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasInformedBy" type="prov:Communication"/>
</pre>
<pre class="example">
-<prov:document xmlns:prov="http://www.w3.org/ns/prov#">
+<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>traffic regulations enforcing<prov:type>
+ <prov:type xsi:type="xsd:string">traffic regulations enforcing<prov:type>
</prov:activity>
<prov:activity prov:id="a2">
- <prov:type>fine paying, check writing, and mailing</prov:type>
+ <prov:type xsi:type="xsd:string">fine paying, check writing, and mailing</prov:type>
</prov:activity>
<b><prov:wasInformedBy>
@@ -944,15 +855,17 @@
</pre>
<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>email message</prov:type>
+ <prov:type xsi:type="xsd:string">email message</prov:type>
</prov:entity>
<prov:activity prov:id="a1">
- <prov:type>Discuss</prov:type>
+ <prov:type xsi:type="xsd:QName">Discuss</prov:type>
</prov:activity>
<b><prov:wasStartedBy>
@@ -967,7 +880,7 @@
</prov:used>
<prov:activity prov:id="a0">
- <prov:type>Write</prov:type>
+ <prov:type xsi:type="xsd:QName">Write</prov:type>
</prov:activity>
<prov:wasGeneratedBy>
@@ -1018,15 +931,17 @@
</pre>
<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>approval document</prov:type>
+ <prov:type xsi:type="xsd:string">approval document</prov:type>
</prov:entity>
<prov:activity prov:id="a1">
- <prov:type>Editing</prov:type>
+ <prov:type xsi:type="xsd:QName">Editing</prov:type>
</prov:activity>
<b><prov:wasEndedBy>
@@ -1120,7 +1035,10 @@
<xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasDerivedFrom" type="prov:Derivation"/>
</pre>
<pre class="example">
-<prov:document xmlns:prov="http://www.w3.org/ns/prov#">
+<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"/>
@@ -1134,7 +1052,7 @@
<b><prov:wasDerivedFrom>
<prov:generatedEntity prov:ref="e2"/>
<prov:usedEntity prov:ref="e1"/>
- <prov:type>physical transform</prov:type>
+ <prov:type xsi:type="xsd:string">physical transform</prov:type>
</prov:wasDerivedFrom></b>
</prov:document>
@@ -1147,22 +1065,24 @@
<p>To specialize a Derivation relationship as a Revision relationship, include a <code>prov:type</code> with the value "prov:Revision".</p>
<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>rec54:WD</prov:type>
+ <prov:type xsi:type="xsd:QName">rec54:WD</prov:type>
</prov:entity>
<prov:entity prov:id="tr:WD-prov-dm-20111018">
- <prov:type>rec54:WD</prov:type>
+ <prov:type xsi:type="xsd:QName">rec54:WD</prov:type>
</prov:entity>
<prov:wasDerivedFrom>
<prov:generatedEntity prov:ref="tr:WD-prov-dm-20111215"/>
<prov:usedEntity prov:ref="tr:WD-prov-dm-20111018"/>
- <b><prov:type>prov:Revision</prov:type></b>
+ <b><prov:type xsi:type="xsd:QName">prov:Revision</prov:type></b>
</prov:wasDerivedFrom>
</prov:document>
@@ -1175,6 +1095,8 @@
<p>To specialize a Derivation relationship as a Quotation relationship, include a <code>prov:type</code> with the value "prov:Quotation".</p>
<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#"
@@ -1191,7 +1113,7 @@
<prov:wasDerivedFrom>
<prov:generatedEntity prov:ref="dm:gl-dagstuhl"/>
<prov:usedEntity prov:ref="wp:thoughts-from-the-dagstuhl-principles-of-provenance-workshop"/>
- <b><prov:type>prov:Quotation</prov:type></b>
+ <b><prov:type xsi:type="xsd:QName">prov:Quotation</prov:type></b>
</prov:wasDerivedFrom>
<prov:wasAttributedTo>
@@ -1214,21 +1136,23 @@
<p>To specialize a Derivation relationship as a Primary Source relationship, include a <code>prov:type</code> with the value "prov:PrimarySource".</p>
<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>map</prov:type>
+ <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>journal</prov:type>
+ <prov:type xsi:type="xsd:QName">journal</prov:type>
</prov:entity>
<prov:wasDerivedFrom>
<prov:generatedEntity prov:ref="ex:la-campagne-de-Russie-1812-1813"/>
<prov:usedEntity prov:ref="ex:revue-d-Histoire-de-la-Pharmacie-t-XVIII"/>
- <b><prov:type>prov:PrimarySource</prov:type></b>
+ <b><prov:type xsi:type="xsd:QName">prov:PrimarySource</prov:type></b>
</prov:wasDerivedFrom>
</prov:document>
@@ -1240,7 +1164,7 @@
<section id="component3">
<h3>Component 3: Agents, Responsibility, and Influence</h3>
-<p>The second component of PROV-DM, depicted in <a href="#figure-component3">Figure 7</a>, is concerned with <a title="agent">agents</a> and the relations WasAttributedTo
+<p>The third component of PROV-DM, depicted in <a href="#figure-component3">Figure 7</a>, is concerned with <a title="agent">agents</a> and the relations WasAttributedTo
(<a>Attribution</a>), WasAssociatedWith (<a>Association</a>), ActedOnBehalfOf (<a>Delegation</a>), relating agents to entities, activities, and agents, respectively.</p>
<section id="term-Agent">
@@ -1264,11 +1188,13 @@
</pre>
<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>prov:Person</prov:type>
+ <prov:type xsi:type="xsd:QName">prov:Person</prov:type>
<ex:name>Alice</ex:name>
<ex:employee>1234</ex:employee>
</prov:agent></b>
@@ -1299,33 +1225,35 @@
</pre>
<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:type>prov:Person</prov:type>
+ <prov:typexsi:type="xsd:QName">prov:Person</prov:type>
</prov:agent>
<prov:agent prov:id="ex:Simon">
- <prov:type>prov:Person</prov:type>
+ <prov:type xsi:type="xsd:QName">prov:Person</prov:type>
</prov:agent>
<prov:entity prov:id="tr:WD-prov-dm-20111215">
- <prov:type>rec54:WD</prov:type>
+ <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>editorship</prov:type>
+ <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>authorship</prov:type>
+ <prov:type xsi:type="xsd:QName">authorship</prov:type>
</prov:wasAttributedTo></b>
</prov:document>
@@ -1356,26 +1284,27 @@
</pre>
<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:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:ex="http://example.com/ns/ex#">
<prov:activity prov:id="a">
- <prov:type>workflow execution</prov:type>
+ <prov:type xsi:type="xsd:string">workflow execution</prov:type>
</prov:activity>
<prov:agent prov:id="ag1">
- <prov:type>operator</prov:type>
+ <prov:type xsi:type="xsd:QName">operator</prov:type>
</prov:agent>
<prov:agent prov:id="ag2">
- <prov:type>designator</prov:type>
+ <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>loggedInUser</prov:role>
+ <prov:role xsi:type="xsd:QName">loggedInUser</prov:role>
<ex:how>webapp</ex:how>
</prov:wasAssociatedWith></b>
@@ -1383,14 +1312,14 @@
<prov:activity prov:ref="a"/>
<prov:agent prov:ref="ag2"/>
<prov:plan prov:ref="ex:wf"/>
- <prov:role>designer</prov:role>
+ <prov:role xsi:type="xsd:QName">designer</prov:role>
<ex:content>project1</ex:content>
</prov:wasAssociatedWith></b>
<prov:entity prov:id="ex:wf">
- <prov:type>prov:Plan</prov:type>
+ <prov:type xsi:type="xsd:QName">prov:Plan</prov:type>
<ex:label>Workflow 1</ex:label>
- <prov:location>http://example.org/workflow1.bpel</prov:location>
+ <prov:location xsi:type="xsd:anyURI">http://example.org/workflow1.bpel</prov:location>
</prov:entity>
</prov:document>
@@ -1419,34 +1348,37 @@
<xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="actedOnBehalfOf" type="prov:Delegation"/>
</pre>
<pre class="example">
-<prov:document xmlns:prov="http://www.w3.org/ns/prov#">
+<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>workflow</prov:type>
+ <prov:type xsi:type="xsd:QName">workflow</prov:type>
</prov:activity>
<prov:agent prov:id="ag1">
- <prov:type>programmer</prov:type>
+ <prov:type xsi:type="xsd:QName">programmer</prov:type>
</prov:agent>
<prov:agent prov:id="ag2">
- <prov:type>researcher</prov:type>
+ <prov:type xsi:type="xsd:QName">researcher</prov:type>
</prov:agent>
<prov:agent prov:id="ag3">
- <prov:type>funder</prov:type>
+ <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>loggedInUser</prov:role>
+ <prov:role xsi:type="xsd:QName">loggedInUser</prov:role>
</prov:wasAssociatedWith>
<prov:wasAssociatedWith>
<prov:activity prov:ref="a"/>
<prov:agent prov:ref="ag2"/>
- </prov:wasAssociatedWithv
+ </prov:wasAssociatedWith>
<prov:wasAssociatedWith>
<prov:activity prov:ref="a"/>
@@ -1457,14 +1389,14 @@
<prov:delegate prov:ref="ag1"/>
<prov:responsible prov:ref="ag2"/>
<prov:activity prov:ref="a"/>
- <prov:type>line-management</prov:type>
+ <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>contract</prov:type>
+ <prov:type xsi:type="xsd:QName">contract</prov:type>
</prov:actedOnBehalfOf></b>
</prov:document>
@@ -1569,16 +1501,18 @@
</pre>
<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>a news item for desktop</prov:type>
+ <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>a news item for mobile devices</prov:type>
+ <prov:type xsi:type="xsd:string">a news item for mobile devices</prov:type>
</prov:entity>
<b><prov:alternateOf>
@@ -1607,6 +1541,8 @@
</pre>
<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:perf="http://example.com/ns/perf#"
@@ -1621,7 +1557,7 @@
<prov:wasAssociatedWith>
<prov:activity prov:ref="ex:a1" />
<prov:agent prov:ref="ex:Bob" />
- <prov:role>controller</prov:role>
+ <prov:role xsi:type="xsd:QName">controller</prov:role>
</prov:wasAssociatedWith>
</prov:bundle>
@@ -1634,7 +1570,7 @@
<prov:wasAssociatedWith>
<prov:activity prov:ref="ex:a2" />
<prov:agent prov:ref="ex:Bob" />
- <prov:role>controller</prov:role>
+ <prov:role xsi:type="xsd:QName">controller</prov:role>
</prov:wasAssociatedWith>
</prov:bundle>
@@ -1679,17 +1615,19 @@
<p>An EmptyCollection is asserted with the <code>prov:type</code> "prov:EmptyCollection" and denotes a Collection with no members.</p>
<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#">
<!-- c0 is an empty collection -->
<b><prov:entity prov:id="c0">
- <prov:type>prov:EmptyCollection</prov:type>
+ <prov:type xsi:type="xsd:QName">prov:EmptyCollection</prov:type>
</prov:entity></b>
<!-- c1 is a collection, with unknown content -->
<b><prov:entity prov:id="c1">
- <prov:type>prov:Collection</prov:type>
+ <prov:type xsi:type="xsd:QName">prov:Collection</prov:type>
</prov:entity></b>
</prov:document>
@@ -1712,6 +1650,8 @@
</pre>
<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"/>
@@ -1719,7 +1659,7 @@
<prov:entity prov:id="e2"/>
<prov:entity prov:id="c">
- <prov:type>prov:Collection</prov:type>
+ <prov:type xsi:type="xsd:QName">prov:Collection</prov:type>
</prov:entity>
<b><prov:hadMember>
@@ -1746,11 +1686,13 @@
<p>The identifier attribute is used to identify instances of PROV types or relations.</p>
<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 <b>prov:id="tr:WD-prov-dm-20111215"</b>>
- <prov:type>document</prov:type>
+ <prov:type xsi:type="xsd:Qname">document</prov:type>
<ex:version>2</ex:version>
</prov:entity>
@@ -1790,17 +1732,19 @@
</pre>
<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>StillImage</prov:type>
- <b><prov:location>Le Louvre, Paris</prov:location></b>
+ <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>(5,5)</prov:location></b>
- <prov:value>10</prov:value>
+ <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>
@@ -1815,14 +1759,15 @@
</pre>
<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:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:ex="http://example.com/ns/ex#">
<prov:wasAssociatedWith>
<prov:activity prov:ref="a"/>
<prov:agent prov:ref="ag1"/>
- <b><prov:role>loggedInUser</prov:role></b>
+ <b><prov:role xsi:type="xsd:QName">loggedInUser</prov:role></b>
<ex:how>webapp</ex:how>
</prov:wasAssociatedWith>
@@ -1830,7 +1775,7 @@
<prov:activity prov:ref="a"/>
<prov:agent prov:ref="ag2"/>
<prov:plan prov:ref="ex:wf"/>
- <b><prov:role>designer</prov:role></b>
+ <b><prov:role xsi:type="xsd:QName">designer</prov:role></b>
<ex:content>project1</ex:content>
</prov:wasAssociatedWith>
@@ -1846,17 +1791,19 @@
</pre>
<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>document</prov:type></b>
+ <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>prov:Person</prov:type></b>
+ <b><prov:type xsi:type="xsd:QName">prov:Person</prov:type></b>
<ex:name>Alice</ex:name>
<ex:employee>1234</ex:employee>
</prov:agent>
@@ -1864,7 +1811,7 @@
<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>ex:edit</prov:type></b>
+ <b><prov:type xsi:type="xsd:QName">ex:edit</prov:type></b>
<ex:host>server.example.org</ex:host>
</prov:activity>
@@ -1880,15 +1827,17 @@
</pre>
<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>abcd</prov:value></b>
+ <b><prov:value xsi:type="xsd:string">abcd</prov:value></b>
</prov:entity>
<prov:entity prov:id="ex:out">
- <b><prov:value>4</prov:value></b>
+ <b><prov:value xsi:type="xsd:integer">4</prov:value></b>
</prov:entity>
</prov:document>
@@ -1940,7 +1889,7 @@
<!-- Should this be folded or hid in some way until the user asks to see it? -->
-<section class="appendix">
+<section class="appendix" id="prov-xml-schema">
<h2>Full XML Schema</h2>
<pre class="full-schema">
<?xml version="1.0" encoding="utf-8"?>