--- a/model/prov-dm.html Thu Apr 18 18:03:41 2013 +0200
+++ b/model/prov-dm.html Thu Apr 18 18:05:22 2013 +0200
@@ -1,20 +1,19 @@
-<!DOCTYPE html
->
-
-<html><head>
+<!DOCTYPE html>
+<html lang="en" dir="ltr">
+<head>
<title>PROV-DM: The PROV Data Model</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-dm"/>
-
-<script src="https://www.w3.org/Tools/respec/respec-w3c-common" class="remove" async></script>
-
-<script src="https://ajax.googleapis.com/ajax/libs/jquery/1.7.1/jquery.min.js" class="remove"></script>
-
-<script src="prov-magic.js" class="remove"></script>
-
-<script src="glossary.js" class="remove"></script>
-
-<script src="provbib.js" class="remove"></script>
+<link rel="http://www.w3.org/ns/prov#has_provenance" href="http://www.w3.org/2011/prov/provenance/prov-dm">
+
+
+
+
+
+
+
+
+
+
<!-- javascript for button to hide examples -->
<script type="text/javascript">
@@ -72,174 +71,9 @@
}
</script>
-<script class="remove">
-$(document).ready(function(){
-// if glossary is in a string:
- $('#glossary_div').html(glossary_string)
- updateGlossaryRefs();
- updateFigCaptions();
- updateCaptions();
- updateExamples();
- updateExamplesRefs();
-
-
- if (typeof String.prototype.startsWith != 'function') {
- String.prototype.startsWith = function (str) {
- return this.indexOf(str) == 0;
- };
- }
- if (typeof String.prototype.contains != 'function') {
- String.prototype.contains = function (str) {
- return this.indexOf(str) >= 0;
- };
- }
- });
-</script>
-
-<script class="remove">
- var addExtraReferences = function() {
- for (var k in extraReferences)
- berjon.biblio[k] = extraReferences[k];
- };
- var extraReferences = {
-
- "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>",
-
- "UML":
- "Object Management Group "+
- "<a href=\"http://www.omg.org/spec/UML/2.0/Superstructure/PDF/\"><cite>Unified Modeling Language: Superstructure</cite></a>. "+
- "version 2.0, 2005 "+
- "URL: <a href=\"http://www.omg.org/spec/UML/2.0/Superstructure/PDF/\">http://www.omg.org/spec/UML/2.0/Superstructure/PDF/</a>",
-
- "RDF-CONCEPTS11":
- "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>",
-
- "Mappings":
- "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>",
-
-
-
- };
- var respecConfig = {
- // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
- specStatus: "REC",
-
- // the specification's short name, as in http://www.w3.org/TR/short-name/
- shortName: "prov-dm",
-
- // if your specification has a subtitle that goes below the main
- // formal title, define it here
- //subtitle : "Editor's draft since CR release",
+
- // if you wish the publication date to be other than today, set this
- publishDate: "2013-04-30",
-
- // if the specification's copyright date is a range of years, specify
- // the start date here:
- copyrightStart: "2011",
-
- errata: "http://www.w3.org/2011/prov/errata.html",
-
- // if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
- // and its maturity status
- //previousPublishDate: "2012-12-11",
- previousPublishDate: "2013-03-12",
- previousMaturity: "PR",
-
-
- // if there a publicly available Editor's Draft, this is the link
-// edDraftURI: "http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html",
-
- implementationReportURI: "http://www.w3.org/TR/2013/NOTE-prov-implementations-20130430/",
-
-// testSuiteURI: "http://dvcs.w3.org/hg/prov/raw-file/default/testcases/process.html",
-
-
- // if this is a LCWD, uncomment and set the end of its review period
- prEnd: "2013-04-09",
- crEnd: "2013-01-31",
- lcEnd: "2012-09-18",
-
- // if you want to have extra CSS, append them to this list
- // it is recommended that the respec.css stylesheet be kept
- //extraCSS: ["http://dev.w3.org/2009/dap/ReSpec.js/css/respec.css"],
-
- // editors, add as many as you like
- // only "name" is required
- editors: [
- { name: "Luc Moreau", url: "http://www.ecs.soton.ac.uk/~lavm/",
- company: "University of Southampton" },
- { name: "Paolo Missier", url: "http://www.cs.ncl.ac.uk/people/Paolo.Missier",
- company: "Newcastle University" },
- ],
-
- // authors, add as many as you like.
- // This is optional, uncomment if you have authors as well as editors.
- // only "name" is required. Same format as editors.
-
- authors: [
- { name: "Khalid Belhajjame", url: "http://semanticweb.org/wiki/Khalid_Belhajjame",
- company: "University of Manchester" },
- { name: "Reza B'Far",
- company: "Oracle Corporation" },
- { name: "James Cheney", url: "http://homepages.inf.ed.ac.uk/jcheney/",
- company: "University of Edinburgh" },
- { name: "Sam Coppens",
- company: "iMinds - Ghent University"},
- { name: "Stephen Cresswell",
- company: "legislation.gov.uk"},
- { name: "Yolanda Gil",
- company: "Invited Expert", url:"http://www.isi.edu/~gil/"},
- { name: "Paul Groth", url: "http://www.few.vu.nl/~pgroth/",
- company: "VU University of Amsterdam" },
- { name: "Graham Klyne",
- company: "University of Oxford" },
- { name: "Timothy Lebo", url: "http://tw.rpi.edu/instances/TimLebo",
- company: "Rensselaer Polytechnic Institute" },
- { name: "Jim McCusker", url: "http://tw.rpi.edu/web/person/JamesMcCusker",
- company: "Rensselaer Polytechnic Institute" },
- { name: "Simon Miles",
- company: "Invited Expert", url:"http://www.inf.kcl.ac.uk/staff/simonm/" },
- { name: "James Myers", url:"http://www.rpi.edu/research/ccni/",
- company: "Rensselaer Polytechnic Institute"},
- { name: "Satya Sahoo", url:"http://cci.case.edu/cci/index.php/Satya_Sahoo",
- company: "Case Western Reserve University" },
- { name: "Curt Tilmes",
- company: "National Aeronautics and Space Administration" },
- ],
-
- // name of the WG
- wg: "Provenance Working Group",
-
- // URI of the public WG page
- wgURI: "http://www.w3.org/2011/prov/",
-
- // name (with the @w3c.org) of the public mailing to which comments are due
- wgPublicList: "public-prov-comments",
-
- // URI of the patent status for this WG, for Rec-track documents
- // !!!! IMPORTANT !!!!
- // This is important for Rec-track documents, do not copy a patent URI from a random
- // document unless you know what you're doing. If in doubt ask your friendly neighbourhood
- // Team Contact.
- wgPatentURI: "http://www.w3.org/2004/01/pp-impl/46974/status",
-
- // Add extraReferences to bibliography database
- preProcess: [addExtraReferences, addProvReferences],
-
- postProcess: [updateSectionRefs, updateDfn, updateFigures, checkLinksToW3CReports, setContributors, setColoredDiffs, checkFragments],
- };
-</script>
<style type="text/css">
.note { font-size:small; margin-left:50px }
@@ -818,15 +652,210 @@
</style>
- </head>
- <body prefix="prov: http://www.w3.org/ns/prov#">
-
- <section id="abstract" class="introductory">
+ <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-REC"><!--[if lt IE 9]><script src='http://www.w3.org/2008/site/js/html5shiv.js'></script><![endif]--></head>
+ <body prefix="prov: http://www.w3.org/ns/prov#"><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-DM: The PROV Data Model</h1>
+
+ <h2 id="w3c-recommendation-30-april-2013"><abbr title="World Wide Web Consortium">W3C</abbr> Recommendation 30 April 2013</h2>
+ <dl>
+
+ <dt>This version:</dt>
+ <dd><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>Latest published version:</dt>
+ <dd><a href="http://www.w3.org/TR/prov-dm/">http://www.w3.org/TR/prov-dm/</a></dd>
+
+
+
+
+ <dt>Implementation report:</dt>
+ <dd><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>Previous version:</dt>
+ <dd><a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/">http://www.w3.org/TR/2013/PR-prov-dm-20130312/</a> <a href="diff.html">(color-coded diff)</a></dd>
+
+
+ <dt>Editors:</dt>
+ <dd><a href="http://www.ecs.soton.ac.uk/~lavm/">Luc Moreau</a>, University of Southampton</dd>
+<dd><a href="http://www.cs.ncl.ac.uk/people/Paolo.Missier">Paolo Missier</a>, Newcastle University</dd>
+
+
+ <dt>Contributors:</dt>
+ <dd><a href="http://semanticweb.org/wiki/Khalid_Belhajjame">Khalid Belhajjame</a>, University of Manchester</dd>
+<dd><span>Reza B'Far</span>, Oracle Corporation</dd>
+<dd><a href="http://homepages.inf.ed.ac.uk/jcheney/">James Cheney</a>, University of Edinburgh</dd>
+<dd><span>Sam Coppens</span>, iMinds - Ghent University</dd>
+<dd><span>Stephen Cresswell</span>, legislation.gov.uk</dd>
+<dd><a href="http://www.isi.edu/~gil/">Yolanda Gil</a>, Invited Expert</dd>
+<dd><a href="http://www.few.vu.nl/~pgroth/">Paul Groth</a>, VU University of Amsterdam</dd>
+<dd><span>Graham Klyne</span>, University of Oxford</dd>
+<dd><a href="http://tw.rpi.edu/instances/TimLebo">Timothy Lebo</a>, Rensselaer Polytechnic Institute</dd>
+<dd><a href="http://tw.rpi.edu/web/person/JamesMcCusker">Jim McCusker</a>, Rensselaer Polytechnic Institute</dd>
+<dd><a href="http://www.inf.kcl.ac.uk/staff/simonm/">Simon Miles</a>, Invited Expert</dd>
+<dd><a href="http://www.rpi.edu/research/ccni/">James Myers</a>, Rensselaer Polytechnic Institute</dd>
+<dd><a href="http://cci.case.edu/cci/index.php/Satya_Sahoo">Satya Sahoo</a>, Case Western Reserve University</dd>
+<dd><span>Curt Tilmes</span>, National Aeronautics and Space Administration</dd>
+
+
+ </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.
+ </p>
+
+
+
+ <p>
+ The English version of this specification is the only normative version. Non-normative
+ <a href="http://www.w3.org/Consortium/Translation/">translations</a> may also be available.
+ </p>
+
+
+
+ <p class="copyright">
+ <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> ©
+ 2011-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 W3C
+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.
PROV-DM distinguishes core structures, forming the essence of provenance information, from
extended structures catering for more specific uses of provenance.
@@ -853,44 +882,94 @@
<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">
-<h4>PROV Family of Documents</h4>
+ </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 [[PROV-OVERVIEW]] for a guide to reading these documents.
+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 [[PROV-OVERVIEW]];</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 [[PROV-PRIMER]];</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 [[!PROV-O]];</li>
+<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 (this document);</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 [[!PROV-N]];</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 [[!PROV-CONSTRAINTS]];</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 [[PROV-XML]];</li>
-<li> <a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/">PROV-AQ</a> (Note), mechanisms for accessing and querying provenance [[PROV-AQ]]; </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 [[PROV-DICTIONARY]];</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 [[PROV-DC]];</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 [[PROV-SEM]];</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 [[PROV-LINKS]].</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>Endorsed By W3C</h4>
-
-<p>This document has been reviewed by W3C Members, by software developers, and by other W3C groups and interested parties, and is endorsed by the Director as a W3C Recommendation. It is a stable document and may be used as reference material or cited from another document. W3C's role in making the Recommendation is to draw attention to the specification and to promote its widespread deployment. This enhances the functionality and interoperability of the Web.</p>
-
-<h4>Please Send Comments</h4>
-</section>
+<h4 id="endorsed-by-w3c">Endorsed By <abbr title="World Wide Web Consortium">W3C</abbr></h4>
+
+<p>This document has been reviewed by <abbr title="World Wide Web Consortium">W3C</abbr> Members, by software developers, and by other <abbr title="World Wide Web Consortium">W3C</abbr> groups and interested parties, and is endorsed by the Director as a <abbr title="World Wide Web Consortium">W3C</abbr> Recommendation. It is a stable document and may be used as reference material or cited from another document. <abbr title="World Wide Web Consortium">W3C</abbr>'s role in making the Recommendation is to draw attention to the specification and to promote its widespread deployment. This enhances the functionality and interoperability of the Web.</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 Recommendation.
+
+
+ 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>
+
+ 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<br>
+</a><ul class="toc"><li class="tocline"><a href="#compliance-with-this-document" class="tocxref"><span class="secno">1.1 </span>Compliance with this Document</a></li><li class="tocline"><a href="#structure-of-this-document" class="tocxref"><span class="secno">1.2 </span>Structure of this Document</a></li><li class="tocline"><a href="#conventions" class="tocxref"><span class="secno">1.3 </span>Notational Conventions</a></li><li class="tocline"><a href="#namespaces" class="tocxref"><span class="secno">1.4 </span>Namespaces</a></li></ul></li><li class="tocline"><a href="#section-prov-overview" class="tocxref"><span class="secno">2. </span>PROV Overview</a><ul class="toc"><li class="tocline"><a href="#core-structures" class="tocxref"><span class="secno">2.1 </span>PROV Core Structures</a><ul class="toc"><li class="tocline"><a href="#section-entity-activity" class="tocxref"><span class="secno">2.1.1 </span>Entity and Activity</a></li><li class="tocline"><a href="#section-derivation" class="tocxref"><span class="secno">2.1.2 </span>Derivation</a></li><li class="tocline"><a href="#section-agents-attribution-association-delegation" class="tocxref"><span class="secno">2.1.3 </span>Agents and Responsibility</a></li></ul></li><li class="tocline"><a href="#section-extended-structures" class="tocxref"><span class="secno">2.2 </span>PROV Extended Structures</a><ul class="toc"><li class="tocline"><a href="#section-prov-extended-mechanisms" class="tocxref"><span class="secno">2.2.1 </span>Mechanisms to Define Extended Structures</a><ul class="toc"><li class="tocline"><a href="#section-prov-extended-approach-subtyping" class="tocxref"><span class="secno">2.2.1.1 </span>Subtyping</a></li><li class="tocline"><a href="#section-prov-extended-approach-expanded-relation" class="tocxref"><span class="secno">2.2.1.2 </span>Expanded Relations</a></li><li class="tocline"><a href="#section-prov-extended-approach-optional-identification" class="tocxref"><span class="secno">2.2.1.3 </span>Optional Identification</a></li><li class="tocline"><a href="#section-prov-extended-approach-further-relations" class="tocxref"><span class="secno">2.2.1.4 </span>Further Relations</a></li></ul></li><li class="tocline"><a href="#section-provenance-of-provnance" class="tocxref"><span class="secno">2.2.2 </span>Provenance of Provenance</a></li><li class="tocline"><a href="#section-collections" class="tocxref"><span class="secno">2.2.3 </span>Collections</a></li></ul></li><li class="tocline"><a href="#section-overview-components" class="tocxref"><span class="secno">2.3 </span>Modular Organization</a></li></ul></li><li class="tocline"><a href="#prov-notation" class="tocxref"><span class="secno">3. </span>The Provenance Notation</a></li><li class="tocline"><a href="#prov-dm-example" class="tocxref"><span class="secno">4. </span>Illustration of PROV-DM by an Example</a><ul class="toc"><li class="tocline"><a href="#section-example-one" class="tocxref"><span class="secno">4.1 </span>Example: The Authors View</a></li><li class="tocline"><a href="#section-example-two" class="tocxref"><span class="secno">4.2 </span>Example: The Process View</a></li><li class="tocline"><a href="#section-example-c" class="tocxref"><span class="secno">4.3 </span>Example: Attribution of Provenance</a></li></ul></li><li class="tocline"><a href="#data-model-components" class="tocxref"><span class="secno">5. </span>PROV-DM Types and Relations</a><ul class="toc"><li class="tocline"><a href="#component1" class="tocxref"><span class="secno">5.1 </span>Component 1: Entities and Activities</a><ul class="toc"><li class="tocline"><a href="#term-entity" class="tocxref"><span class="secno">5.1.1 </span>Entity</a></li><li class="tocline"><a href="#term-Activity" class="tocxref"><span class="secno">5.1.2 </span>Activity</a></li><li class="tocline"><a href="#term-Generation" class="tocxref"><span class="secno">5.1.3 </span>Generation</a></li><li class="tocline"><a href="#term-Usage" class="tocxref"><span class="secno">5.1.4 </span>Usage</a></li><li class="tocline"><a href="#term-Communication" class="tocxref"><span class="secno">5.1.5 </span>Communication</a></li><li class="tocline"><a href="#term-Start" class="tocxref"><span class="secno">5.1.6 </span>Start</a></li><li class="tocline"><a href="#term-End" class="tocxref"><span class="secno">5.1.7 </span>End</a></li><li class="tocline"><a href="#term-Invalidation" class="tocxref"><span class="secno">5.1.8 </span>Invalidation</a></li></ul></li><li class="tocline"><a href="#component2" class="tocxref"><span class="secno">5.2 </span>Component 2: Derivations</a><ul class="toc"><li class="tocline"><a href="#term-Derivation" class="tocxref"><span class="secno">5.2.1 </span>Derivation</a></li><li class="tocline"><a href="#term-revision" class="tocxref"><span class="secno">5.2.2 </span>Revision</a></li><li class="tocline"><a href="#term-quotation" class="tocxref"><span class="secno">5.2.3 </span>Quotation</a></li><li class="tocline"><a href="#term-primary-source" class="tocxref"><span class="secno">5.2.4 </span>Primary Source</a></li></ul></li><li class="tocline"><a href="#component3" class="tocxref"><span class="secno">5.3 </span>Component 3: Agents, Responsibility, and Influence</a><ul class="toc"><li class="tocline"><a href="#term-agent" class="tocxref"><span class="secno">5.3.1 </span>Agent</a></li><li class="tocline"><a href="#term-attribution" class="tocxref"><span class="secno">5.3.2 </span>Attribution</a></li><li class="tocline"><a href="#term-Association" class="tocxref"><span class="secno">5.3.3 </span>Association</a></li><li class="tocline"><a href="#term-delegation" class="tocxref"><span class="secno">5.3.4 </span>Delegation</a></li><li class="tocline"><a href="#term-influence" class="tocxref"><span class="secno">5.3.5 </span>Influence</a></li></ul></li><li class="tocline"><a href="#component4" class="tocxref"><span class="secno">5.4 </span>Component 4: Bundles</a><ul class="toc"><li class="tocline"><a href="#term-bundle" class="tocxref"><span class="secno">5.4.1 </span>Bundle constructor</a></li><li class="tocline"><a href="#term-bundle-entity" class="tocxref"><span class="secno">5.4.2 </span>Bundle Type</a></li></ul></li><li class="tocline"><a href="#component5" class="tocxref"><span class="secno">5.5 </span>Component 5: Alternate Entities</a><ul class="toc"><li class="tocline"><a href="#term-specialization" class="tocxref"><span class="secno">5.5.1 </span>Specialization</a></li><li class="tocline"><a href="#term-alternate" class="tocxref"><span class="secno">5.5.2 </span>Alternate</a></li></ul></li><li class="tocline"><a href="#component6" class="tocxref"><span class="secno">5.6 </span>Component 6: Collections</a><ul class="toc"><li class="tocline"><a href="#term-collection" class="tocxref"><span class="secno">5.6.1 </span>Collection</a></li><li class="tocline"><a href="#term-membership" class="tocxref"><span class="secno">5.6.2 </span>Membership</a></li></ul></li><li class="tocline"><a href="#second-class-elements" class="tocxref"><span class="secno">5.7 </span>Further Elements of PROV-DM</a><ul class="toc"><li class="tocline"><a href="#term-identifier" class="tocxref"><span class="secno">5.7.1 </span>Identifier</a></li><li class="tocline"><a href="#term-attribute" class="tocxref"><span class="secno">5.7.2 </span>Attribute</a><ul class="toc"><li class="tocline"><a href="#term-attribute-label" class="tocxref"><span class="secno">5.7.2.1 </span>prov:label</a></li><li class="tocline"><a href="#term-attribute-location" class="tocxref"><span class="secno">5.7.2.2 </span>prov:location</a></li><li class="tocline"><a href="#term-attribute-role" class="tocxref"><span class="secno">5.7.2.3 </span>prov:role</a></li><li class="tocline"><a href="#term-attribute-type" class="tocxref"><span class="secno">5.7.2.4 </span>prov:type</a></li><li class="tocline"><a href="#term-attribute-value" class="tocxref"><span class="secno">5.7.2.5 </span>prov:value</a></li></ul></li><li class="tocline"><a href="#term-value" class="tocxref"><span class="secno">5.7.3 </span>Value</a></li><li class="tocline"><a href="#term-NamespaceDeclaration" class="tocxref"><span class="secno">5.7.4 </span>Namespace Declaration</a></li><li class="tocline"><a href="#term-qualified-name" class="tocxref"><span class="secno">5.7.5 </span>Qualified Name</a></li></ul></li></ul></li><li class="tocline"><a href="#extensibility-section" class="tocxref"><span class="secno">6. </span>PROV-DM Extensibility Points</a></li><li class="tocline"><a href="#valid-provenance" class="tocxref"><span class="secno">7. </span>Creating Valid Provenance</a></li><li class="tocline"><a href="#cross-references-to-prov-o-and-prov-n" class="tocxref"><span class="secno">A. </span>Cross-References to PROV-O and PROV-N</a></li><li class="tocline"><a href="#change-log" class="tocxref"><span class="secno">B. </span>Change Log</a><ul class="toc"><li class="tocline"><a href="#changes-since-proposed-recommendation" class="tocxref"><span class="secno">B.1 </span>Changes since Proposed Recommendation</a></li><li class="tocline"><a href="#changes-since-candidate-recommendation" class="tocxref"><span class="secno">B.2 </span>Changes since Candidate Recommendation</a></li><li class="tocline"><a href="#changes-since-last-call" class="tocxref"><span class="secno">B.3 </span>Changes since Last Call</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="#normative-references" class="tocxref"><span class="secno">D.1 </span>Normative references</a></li><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">D.2 </span>Informative references</a></li></ul></li></ul></section>
+
+
<section id="introduction">
- <h2>Introduction<br>
+ <!--OddPage--><h2><span class="secno">1. </span>Introduction<br>
</h2>
<p>
-For the purpose of this specification, <dfn>provenance</dfn> is defined as a record that describes the people,
+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
@@ -914,7 +993,7 @@
<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]].
+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.
@@ -927,12 +1006,12 @@
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> 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 the same thing;
-<li> component 6: collections forming a logical structure for its members.
-</ul>
+</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 the same thing;
+</li><li> component 6: collections forming a logical structure for its members.
+</li></ul>
<p>This specification presents the concepts of the PROV data model, and
@@ -941,7 +1020,7 @@
<p>However, if something about which provenance is expressed is subject to change, then it is challenging to express its provenance precisely (e.g. the data from which a daily weather report is derived changes from day to day).
This is addressed in a companion
- specification [[!PROV-CONSTRAINTS]] by proposing formal constraints on
+ specification [<cite><a class="bibref" href="#bib-PROV-CONSTRAINTS">PROV-CONSTRAINTS</a></cite>] by proposing formal constraints on
the way that provenance is related to the things it
describes (such as the use of attributes, temporal information and
specialization of entities), and additional conclusions that are valid
@@ -949,25 +1028,25 @@
</p>
<section id="compliance-with-this-document">
-<h3>Compliance with this Document</h3>
+<h3><span class="secno">1.1 </span>Compliance with this Document</h3>
<p>For the purpose of compliance, the normative sections of this document
are
-<a class="section-ref" href="#compliance-with-this-document"><span>TBD</span></a>,
-<a class="section-ref" href="#conventions"><span>TBD</span></a>,
-<a class="section-ref" href="#data-model-components"><span>TBD</span></a>, and
+<a class="section-ref" href="#compliance-with-this-document"><span>Section 1.1</span></a>,
+<a class="section-ref" href="#conventions"><span>Section 1.3</span></a>,
+<a class="section-ref" href="#data-model-components"><span>Section 5.</span></a>, and
<a href="#cross-references-to-prov-o-and-prov-n">Appendix A</a>.
-<ul>
+</p><ul>
<li> Information in tables is normative if it appears in a normative section. </li>
<li> All figures (including UML diagrams) are informative. </li>
<li> Text in boxes labeled "Example" is informative.
-</ul>
+</li></ul>
</section>
<section class="informative" id="structure-of-this-document">
-<h3>Structure of this Document</h3>
+<h3><span class="secno">1.2 </span>Structure of this Document</h3><p><em>This section is non-normative.</em></p>
<p><a href="#section-prov-overview">Section 2</a> provides an overview of the PROV data model, distinguishing a core set of types and relations, commonly found in provenance, from extended structures catering for more specific uses. It also introduces a modular organization of the data model in components. </p>
@@ -984,44 +1063,45 @@
<p><a href="#extensibility-section">Section 6</a> summarizes PROV-DM extensibility points.</p>
-<p><a href="#valid-provenance">Section 7</a> introduces the idea that constraints can be applied to the PROV data model to validate provenance; these are covered in the companion specification [[!PROV-CONSTRAINTS]].</p>
+<p><a href="#valid-provenance">Section 7</a> introduces the idea that constraints can be applied to the PROV data model to validate provenance; these are covered in the companion specification [<cite><a class="bibref" href="#bib-PROV-CONSTRAINTS">PROV-CONSTRAINTS</a></cite>].</p>
</section>
<section id="conventions">
-<h3>Notational Conventions</h3>
-
-
-
-<p>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
- NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
- "OPTIONAL" in this document are to be interpreted as described in
- [[!RFC2119]].</p>
+<h3><span class="secno">1.3 </span>Notational 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>
<p>
Examples throughout this document use the PROV-N Provenance
- Notation, briefly introduced in <a href="#prov-notation">Section 3</a> and specified fully in a separate document [[!PROV-N]].</p>
+ Notation, briefly introduced in <a href="#prov-notation">Section 3</a> and specified fully in a separate document [<cite><a class="bibref" href="#bib-PROV-N">PROV-N</a></cite>].</p>
</section>
<section class="informative" id="namespaces">
-<h3>Namespaces</h3>
+<h3><span class="secno">1.4 </span>Namespaces</h3><p><em>This section is non-normative.</em></p>
<p>
The following namespaces prefixes are used throughout this document.
-<div style="text-align: left;">
-<table class="thinborder" style="margin-left: auto; margin-right: auto;">
-<caption id="namespace-table">Prefix and Namespaces used in this specification</caption> <!-- Table 1-->
-<tr><td><b>prefix</b></td><td><b>namespace IRI</b></td> <td><b>definition</b></td></tr>
-<tr><td>prov</td><td>http://www.w3.org/ns/prov#</td><td>The PROV namespace (see <a class="section-ref" href="#term-NamespaceDeclaration"><span>TBD</span></a>)</td></tr>
-<tr><td>xsd</td><td>http://www.w3.org/2000/10/XMLSchema#</td><td>XML Schema Namespace [[!XMLSCHEMA11-2]]</td></tr>
-<tr><td>rdf</td><td>http://www.w3.org/1999/02/22-rdf-syntax-ns#</td><td>The RDF namespace [[!RDF-CONCEPTS]]</td></tr>
-<tr><td>(others)</td><td>(various)</td><td>All other namespace prefixes are used in examples only. <br/> In particular, IRIs starting with "http://example.com" represent<br/> some application-dependent IRI [[!RFC3987]]</td></tr>
-</table>
+</p><div style="text-align: left;">
+<table class="thinborder" style="margin-left: auto; margin-right: auto;">
+<caption id="namespace-table"><span>Table 1<sup><a class="internalDFN" href="#namespace-table"><span class="diamond"> ◊:</span></a></sup> </span>Prefix and Namespaces used in this specification</caption> <!-- Table 1-->
+<tbody><tr><td><b>prefix</b></td><td><b>namespace IRI</b></td> <td><b>definition</b></td></tr>
+<tr><td>prov</td><td>http://www.w3.org/ns/prov#</td><td>The PROV namespace (see <a class="section-ref" href="#term-NamespaceDeclaration"><span>Section 5.7.4</span></a>)</td></tr>
+<tr><td>xsd</td><td>http://www.w3.org/2000/10/XMLSchema#</td><td>XML Schema Namespace [<cite><a class="bibref" href="#bib-XMLSCHEMA11-2">XMLSCHEMA11-2</a></cite>]</td></tr>
+<tr><td>rdf</td><td>http://www.w3.org/1999/02/22-rdf-syntax-ns#</td><td>The RDF namespace [<cite><a class="bibref" href="#bib-RDF-CONCEPTS">RDF-CONCEPTS</a></cite>]</td></tr>
+<tr><td>(others)</td><td>(various)</td><td>All other namespace prefixes are used in examples only. <br> In particular, IRIs starting with "http://example.com" represent<br> some application-dependent IRI [<cite><a class="bibref" href="#bib-RFC3987">RFC3987</a></cite>]</td></tr>
+</tbody></table>
</div>
@@ -1031,16 +1111,16 @@
-<section class="informative" id='section-prov-overview'>
-<h1>PROV Overview</h1>
+<section class="informative" id="section-prov-overview">
+<!--OddPage--><h2><span class="secno">2. </span>PROV Overview</h2><p><em>This section is non-normative.</em></p>
<p>This section introduces provenance concepts with informal explanations and illustrative
examples. PROV distinguishes <em>core structures</em>, forming the essence of provenance, from <em>extended structures</em> catering for more specific uses of provenance. Core and extended structures are respectively presented in <a href="#core-structures">Section 2.1</a> and <a href="#section-extended-structures">Section 2.2</a>. Furthermore, the PROV data model is organized according to components, which form thematic groupings of concepts (see <a href="#section-overview-components">Section 2.3</a>). A <em>provenance description</em> is an instance of a provenance structure, whether core or extended, described below.
</p>
-<section id='core-structures'>
-<h1>PROV Core Structures</h1>
+<section id="core-structures">
+<h3><span class="secno">2.1 </span>PROV Core Structures</h3><p><em>This section is non-normative.</em></p>
<p>At its core, provenance describes the use and production of
<em>entities</em> by <em>activities</em>, which may be
@@ -1048,14 +1128,14 @@
various ways by <em>agents</em>. These core types and their relationships
are illustrated
by
-the UML diagram of <a href="#prov-core-structures-top">Figure 1</a>.</p>
+the UML diagram of <a href="#prov-core-structures-top" class="fig-ref">Figure 1</a>.</p>
<div style="text-align: center; ">
- <figure style="max-width: 70%; " id="prov-core-structures-top">
-<img src="uml/essentials.png" alt="PROV Core Structures" style="max-width: 70%; " /><br>
-<figcaption id="prov-core-structures">PROV Core Structures (Informative)</figcaption>
- </figure>
+ <span class="figure" id="prov-core-structures-top" style="max-width: 70%; ">
+<img src="uml/essentials.png" alt="PROV Core Structures" style="max-width: 70%; "><br>
+<span class="figcaption" id="prov-core-structures">Figure 1<sup><a class="internalDFN" href="#prov-core-structures"><span class="diamond"> ◊:</span></a></sup> PROV Core Structures (Informative)</span>
+ </span>
</div>
<p>The concepts found in the core of PROV are introduced in the rest of this section.
@@ -1070,22 +1150,22 @@
<div style="text-align: left;">
-<table class="thinborder" style="margin-left: auto; margin-right: auto;">
-<caption id="overview-types-and-relations">Mapping of PROV core concepts to types and relations</caption> <!-- Table 2 -->
-<tr><td><b>PROV Concepts</b></td><td><b>PROV-DM types or relations</b></td><td><b>Name</b></td><td><b>Overview</b></td></tr>
-<tr>
-<td><a>Entity</a></td><td rowspan="3" style="text-align: center;">PROV-DM Types</td><td><a title="dfn-Entity">Entity</a></td><td style="text-align: center;"><a class="section-ref" href="#section-entity-activity"><span>TBD</span></a></td></tr>
-<tr><td><a>Activity</a></td><td><a title="dfn-Activity">Activity</a></td><td style="text-align: center;"><a class="section-ref" href="#section-entity-activity"><span>TBD</span></a></td></tr>
-<tr><td><a>Agent</a></td><td><a title="dfn-agent">Agent</a></td><td style="text-align: center;"><a class="section-ref" href="#section-agents-attribution-association-delegation"><span>TBD</span></a></td></tr>
+<table class="thinborder" style="margin-left: auto; margin-right: auto;">
+<caption id="overview-types-and-relations"><span>Table 2<sup><a class="internalDFN" href="#overview-types-and-relations"><span class="diamond"> ◊:</span></a></sup> </span>Mapping of PROV core concepts to types and relations</caption> <!-- Table 2 -->
+<tbody><tr><td><b>PROV Concepts</b></td><td><b>PROV-DM types or relations</b></td><td><b>Name</b></td><td><b>Overview</b></td></tr>
<tr>
-<td><a>Generation</a></td><td rowspan="7" style="text-align: center;">PROV-DM Relations</td><td><a title="wasGeneratedBy">WasGeneratedBy</a></td><td style="text-align: center;"><a class="section-ref" href="#section-entity-activity"><span>TBD</span></a></td></tr>
-<tr><td><a>Usage</a></td><td><a title="used">Used</a></td><td style="text-align: center;"><a class="section-ref" href="#section-entity-activity"><span>TBD</span></a></td></tr>
-<tr><td><a>Communication</a></td><td><a title="wasInformedBy">WasInformedBy</a></td><td style="text-align: center;"><a class="section-ref" href="#section-entity-activity"><span>TBD</span></a></td></tr>
-<tr><td><a>Derivation</a></td><td><a title="wasDerivedFrom">WasDerivedFrom</a></td><td style="text-align: center;"><a class="section-ref" href="#section-derivation"><span>TBD</span></a></td></tr>
-<tr><td><a>Attribution</a></td><td><a title="wasAttributedTo">WasAttributedTo</a></td><td style="text-align: center;"><a class="section-ref" href="#section-agents-attribution-association-delegation"><span>TBD</span></a></td></tr>
-<tr><td><a>Association</a></td><td><a title="wasAssociatedWith">WasAssociatedWith</a></td><td style="text-align: center;"><a class="section-ref" href="#section-agents-attribution-association-delegation"><span>TBD</span></a></td></tr>
-<tr><td><a>Delegation</a></td><td><a title="actedOnBehalfOf">ActedOnBehalfOf</a></td><td style="text-align: center;"><a class="section-ref" href="#section-agents-attribution-association-delegation"><span>TBD</span></a></td></tr>
-</table>
+<td><a href="#concept-entity" class="internalDFN">Entity</a></td><td rowspan="3" style="text-align: center;">PROV-DM Types</td><td><a title="dfn-Entity" href="#dfn-entity" class="internalDFN">Entity</a></td><td style="text-align: center;"><a class="section-ref" href="#section-entity-activity"><span>Section 2.1.1</span></a></td></tr>
+<tr><td><a href="#concept-activity" class="internalDFN">Activity</a></td><td><a title="dfn-Activity" href="#dfn-activity" class="internalDFN">Activity</a></td><td style="text-align: center;"><a class="section-ref" href="#section-entity-activity"><span>Section 2.1.1</span></a></td></tr>
+<tr><td><a href="#concept-agent" class="internalDFN">Agent</a></td><td><a title="dfn-agent" href="#dfn-agent" class="internalDFN">Agent</a></td><td style="text-align: center;"><a class="section-ref" href="#section-agents-attribution-association-delegation"><span>Section 2.1.3</span></a></td></tr>
+<tr>
+<td><a href="#concept-generation" class="internalDFN">Generation</a></td><td rowspan="7" style="text-align: center;">PROV-DM Relations</td><td><a title="wasGeneratedBy" href="#dfn-wasgeneratedby" class="internalDFN">WasGeneratedBy</a></td><td style="text-align: center;"><a class="section-ref" href="#section-entity-activity"><span>Section 2.1.1</span></a></td></tr>
+<tr><td><a href="#concept-usage" class="internalDFN">Usage</a></td><td><a title="used" href="#dfn-used" class="internalDFN">Used</a></td><td style="text-align: center;"><a class="section-ref" href="#section-entity-activity"><span>Section 2.1.1</span></a></td></tr>
+<tr><td><a href="#concept-communication" class="internalDFN">Communication</a></td><td><a title="wasInformedBy" href="#dfn-wasinformedby" class="internalDFN">WasInformedBy</a></td><td style="text-align: center;"><a class="section-ref" href="#section-entity-activity"><span>Section 2.1.1</span></a></td></tr>
+<tr><td><a href="#concept-derivation" class="internalDFN">Derivation</a></td><td><a title="wasDerivedFrom" href="#dfn-wasderivedfrom" class="internalDFN">WasDerivedFrom</a></td><td style="text-align: center;"><a class="section-ref" href="#section-derivation"><span>Section 2.1.2</span></a></td></tr>
+<tr><td><a href="#concept-attribution" class="internalDFN">Attribution</a></td><td><a title="wasAttributedTo" href="#dfn-wasattributedto" class="internalDFN">WasAttributedTo</a></td><td style="text-align: center;"><a class="section-ref" href="#section-agents-attribution-association-delegation"><span>Section 2.1.3</span></a></td></tr>
+<tr><td><a href="#concept-association" class="internalDFN">Association</a></td><td><a title="wasAssociatedWith" href="#dfn-wasassociatedwith" class="internalDFN">WasAssociatedWith</a></td><td style="text-align: center;"><a class="section-ref" href="#section-agents-attribution-association-delegation"><span>Section 2.1.3</span></a></td></tr>
+<tr><td><a href="#concept-delegation" class="internalDFN">Delegation</a></td><td><a title="actedOnBehalfOf" href="#dfn-actedonbehalfof" class="internalDFN">ActedOnBehalfOf</a></td><td style="text-align: center;"><a class="section-ref" href="#section-agents-attribution-association-delegation"><span>Section 2.1.3</span></a></td></tr>
+</tbody></table>
</div>
@@ -1096,10 +1176,8 @@
<form action="#"><p>
-<input id="hide-examples" onclick="set_display_by_class('div','anexample conceptexample','none'); set_display_by_id('hide-examples','none'); set_display_by_id('show-examples','');" type="button"
-value="Hide Concept Examples" />
-<input id="show-examples" onclick="set_display_by_class('div','anexample conceptexample',''); set_display_by_id('hide-examples',''); set_display_by_id('show-examples','none');" style="display: none"
-type="button" value="Show Concept Examples" />
+<input id="hide-examples" onclick="set_display_by_class('div','anexample conceptexample','none'); set_display_by_id('hide-examples','none'); set_display_by_id('show-examples','');" type="button" value="Hide Concept Examples">
+<input id="show-examples" onclick="set_display_by_class('div','anexample conceptexample',''); set_display_by_id('hide-examples',''); set_display_by_id('show-examples','none');" style="display: none" type="button" value="Show Concept Examples">
</p>
</form>
@@ -1107,8 +1185,8 @@
- <section id='section-entity-activity'>
-<h2>Entity and Activity</h2>
+ <section id="section-entity-activity">
+<h4><span class="secno">2.1.1 </span>Entity and Activity</h4><p><em>This section is non-normative.</em></p>
<p>In PROV, things we want to describe the provenance of are called <em>entities</em> and have some fixed aspects. The term "things" encompasses a broad diversity of notions, including digital objects such as a file or web page,
@@ -1116,19 +1194,19 @@
</p>
<p>
-<span class="glossary-ref" data-ref="glossary-entity" data-withspan="true">
-</span> [<a href="#term-entity">Detailed specification</a>]</p>
-
-
-
-<div class="anexample conceptexample" id="entity-example">
+<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> [<a href="#term-entity">Detailed specification</a>]</p>
+
+
+
+<div class="anexample conceptexample" id="entity-example"><div class="anexampleTitle">Example 1<sup><a class="internalDFN" href="#entity-example"><span class="diamond"> ◊</span></a></sup></div>
<p>An entity may be the document at IRI <a href="http://www.bbc.co.uk/news/science-environment-17526723">http://www.bbc.co.uk/news/science-environment-17526723</a>, a file in a file system, a car, or an idea.</p>
</div>
<p>
-<span class="glossary-ref" data-ref="glossary-activity" data-withspan="true"></span> [<a href="#term-Activity">Detailed specification</a>]
+<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> [<a href="#term-Activity">Detailed specification</a>]
Just as entities cover a broad range of notions,
activities can cover a broad range of
notions:
@@ -1140,7 +1218,7 @@
-<div class="anexample conceptexample" id="activity-example">
+<div class="anexample conceptexample" id="activity-example"><div class="anexampleTitle">Example 2<sup><a class="internalDFN" href="#activity-example"><span class="diamond"> ◊</span></a></sup></div>
<p>An activity may be the publishing of a document on the Web, sending a twitter message, extracting metadata embedded in a file, driving a car from Boston to Cambridge, assembling a data set based on a set of measurements, performing a statistical analysis over a data set, sorting news items according to some criteria, running a SPARQL query over a triple store, or editing a file.</p>
</div>
@@ -1148,34 +1226,34 @@
The term 'generation' refers to the completion of the act of producing; likewise, the term 'usage' refers to the beginning of the act of utilizing entities. Thus, we define the following concepts of generation and usage. </p>
<p>
-<span class="glossary-ref" data-ref="glossary-generation" data-withspan="true">
-</span> [<a href="#term-Generation">Detailed specification</a>]</p>
+<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> [<a href="#term-Generation">Detailed specification</a>]</p>
<p>
-<span class="glossary-ref" data-ref="glossary-usage" data-withspan="true">
-</span> [<a href="#term-Usage">Detailed specification</a>]</p>
-
-
-
-
-<div class="anexample conceptexample" id="generation-example">
+<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> [<a href="#term-Usage">Detailed specification</a>]</p>
+
+
+
+
+<div class="anexample conceptexample" id="generation-example"><div class="anexampleTitle">Example 3<sup><a class="internalDFN" href="#generation-example"><span class="diamond"> ◊</span></a></sup></div>
<p>Examples of generation are the completed creation of a file by a
program, the completed creation of a linked data set, and the completed
publication of a new version of a document.
-</div>
-
-
-
-
-
-<div class="anexample conceptexample" id="usage-example">
+</p></div>
+
+
+
+
+
+<div class="anexample conceptexample" id="usage-example"><div class="anexampleTitle">Example 4<sup><a class="internalDFN" href="#usage-example"><span class="diamond"> ◊</span></a></sup></div>
<p>Usage examples include a procedure beginning to consume an argument, a service starting to read a value on a port, a program beginning to read a configuration
file, or the point at which an ingredient, such as eggs, is being added in a baking activity. Usage may entirely consume an entity (e.g. eggs are no longer available after being added to
the mix); in contrast, the same entity may be used multiple times, possibly by different activities (e.g. a file on a file system can be read indefinitely).
-</div>
-
-
-<div class="anexample conceptexample" id="driving-a-car">
+</p></div>
+
+
+<div class="anexample conceptexample" id="driving-a-car"><div class="anexampleTitle">Example 5<sup><a class="internalDFN" href="#driving-a-car"><span class="diamond"> ◊</span></a></sup></div>
<p>
Let us consider the activity of driving a car from Boston to Cambridge.
One might reasonably ask what entities are used and generated by this activity.
@@ -1202,25 +1280,25 @@
<p>The generation of an entity by an activity and its subsequent usage by another activity is termed communication.</p>
<p>
-<span class="glossary-ref" data-ref="glossary-communication" data-withspan="true">
-</span> [<a href="#term-Communication">Detailed specification</a>]</p>
-
-
-
-
-
-<div class="anexample conceptexample" id="communication-example">
+<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> [<a href="#term-Communication">Detailed specification</a>]</p>
+
+
+
+
+
+<div class="anexample conceptexample" id="communication-example"><div class="anexampleTitle">Example 6<sup><a class="internalDFN" href="#communication-example"><span class="diamond"> ◊</span></a></sup></div>
<p>
The activity of writing a celebrity article was informed by (a
communication instance) the activity of intercepting voicemails.
-</div>
+</p></div>
</section>
<section id="section-derivation">
-<h2>Derivation</h2>
+<h4><span class="secno">2.1.2 </span>Derivation</h4>
@@ -1228,14 +1306,14 @@
</p>
<p>
-<span class="glossary-ref" data-ref="glossary-derivation" data-withspan="true"></span>
+<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>
[<a href="#term-Derivation">Detailed specification</a>]</p>
-<div class="anexample conceptexample" id="derivation-example">
+<div class="anexample conceptexample" id="derivation-example"><div class="anexampleTitle">Example 7<sup><a class="internalDFN" href="#derivation-example"><span class="diamond"> ◊</span></a></sup></div>
<p>Examples of derivation include the transformation of a relational table into a
linked data set, the transformation of a canvas into a painting, the transportation of a work of art from London to New York, and a physical transformation such as the melting of ice into water.</p>
</div>
@@ -1269,7 +1347,7 @@
<section id="section-agents-attribution-association-delegation">
-<h2>Agents and Responsibility</h2>
+<h4><span class="secno">2.1.3 </span>Agents and Responsibility</h4>
<p>For many purposes, a key consideration
for deciding whether something is reliable and/or trustworthy is
@@ -1282,15 +1360,15 @@
program.</p>
<p>
-<span class="glossary-ref" data-ref="glossary-agent" data-withspan="true">
-</span> [<a href="#term-agent">Detailed specification</a>]
+<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> [<a href="#term-agent">Detailed specification</a>]
An agent may be a particular type of entity or activity. This means that the model can be
used to express provenance of the agents themselves.
</p>
-<div class="anexample conceptexample" id="agent-example">
+<div class="anexample conceptexample" id="agent-example"><div class="anexampleTitle">Example 8<sup><a class="internalDFN" href="#agent-example"><span class="diamond"> ◊</span></a></sup></div>
<p>
Software for checking the use of grammar in a document may be defined as an agent of a document preparation activity; one can also describe its provenance, including for instance the vendor and the version history.
A site selling books on the Web, the services involved in the processing of orders, and the companies hosting them are also agents.
@@ -1302,10 +1380,10 @@
<p>Agents can be related to entities, activities, and other agents.</p>
-<p><span class="glossary-ref" data-ref="glossary-attribution" data-withspan="true"></span>
+<p><span class="glossary-ref"> <span class="dfn">Attribution</span> is the ascribing of an entity to an agent. </span>
[<a href="#term-attribution">Detailed specification</a>]</p>
-<div class="anexample conceptexample" id="attribution-example">
+<div class="anexample conceptexample" id="attribution-example"><div class="anexampleTitle">Example 9<sup><a class="internalDFN" href="#attribution-example"><span class="diamond"> ◊</span></a></sup></div>
<p>A blog post can be attributed to an author, a mobile phone to its manufacturer.</p>
</div>
@@ -1314,13 +1392,13 @@
<p>
-<span class="glossary-ref" data-ref="glossary-core-association" data-withspan="true"></span>
+<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. </span>
[<a href="#term-Association">Detailed specification</a>]</p>
-<div class="anexample conceptexample" id="association-example">
+<div class="anexample conceptexample" id="association-example"><div class="anexampleTitle">Example 10<sup><a class="internalDFN" href="#association-example"><span class="diamond"> ◊</span></a></sup></div>
<p>Examples of association between an activity and an agent are:
-<ul>
+</p><ul>
<li>creation of a web page under the guidance of a designer;</li>
<li>various forms of participation in a panel discussion, including audience member, panelist, or panel chair;</li>
<li>a public event, sponsored by a company, and hosted by a museum;</li>
@@ -1330,15 +1408,15 @@
<p>
-<span class="glossary-ref" data-ref="glossary-delegation" data-withspan="true">
-</span>
+<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>
[<a href="#term-delegation">Detailed specification</a>]
The nature of this relation is intended to be broad, including contractual relation, but also altruistic initiative by the representative agent. </p>
-<div class="anexample conceptexample" id="delegation-example">
+<div class="anexample conceptexample" id="delegation-example"><div class="anexampleTitle">Example 11<sup><a class="internalDFN" href="#delegation-example"><span class="diamond"> ◊</span></a></sup></div>
<p>A student publishing a web page describing an academic
department could result in both the student and the department being
agents associated with the activity. It may not matter which actual
@@ -1352,7 +1430,7 @@
</section>
<section id="section-extended-structures">
-<h2>PROV Extended Structures</h2>
+<h3><span class="secno">2.2 </span>PROV Extended Structures</h3>
<p>While the core of PROV focuses on essential provenance structures commonly found in provenance descriptions, extended structures
are designed to support more advanced uses of provenance.
@@ -1362,7 +1440,7 @@
<section id="section-prov-extended-mechanisms">
-<h2>Mechanisms to Define Extended Structures</h2>
+<h4><span class="secno">2.2.1 </span>Mechanisms to Define Extended Structures</h4>
<p>Extended structures are defined by a variety of mechanisms
outlined in this section: subtyping, expanded relations, optional
@@ -1370,25 +1448,25 @@
<section id="section-prov-extended-approach-subtyping">
-<h2>Subtyping</h2>
+<h5><span class="secno">2.2.1.1 </span>Subtyping</h5><p><em>This section is non-normative.</em></p>
<p>Subtyping can be applied to core types. For example, a software agent is special kind of agent, defined as follows.</p>
-<span class="glossary-ref" data-ref="glossary-software-agent" data-withspan="true">
-</span>
+<span class="glossary-ref">
+ A <span class="dfn">software agent</span> is running software. </span>
<p>Subtyping can also be applied to core relations. For example, a revision is a special kind of derivation, defined as follows.</p>
-<p><span class="glossary-ref" data-ref="glossary-revision" data-withspan="true"></span></p>
+<p><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>
</section>
<section id="section-prov-extended-approach-expanded-relation">
-<h2>Expanded Relations</h2>
-
-<p><a class="section-ref" href="#core-structures"><span>TBD</span></a> shows that seven concepts are mapped to binary relations in the core of PROV. However, some advanced uses of these concepts cannot be captured by a binary relation, but require relations to be expanded to n-ary relations.</p>
+<h5><span class="secno">2.2.1.2 </span>Expanded Relations</h5>
+
+<p><a class="section-ref" href="#core-structures"><span>Section 2.1</span></a> shows that seven concepts are mapped to binary relations in the core of PROV. However, some advanced uses of these concepts cannot be captured by a binary relation, but require relations to be expanded to n-ary relations.</p>
<p>Indeed, binary relations are actually shorthands that can be 'opened up' by applications and filled in with further application details. For example, derivation is a very high level relationship between two entities: an application may decide to 'open up' that relationship in an expanded relation that describes how an entity was derived from another by virtue of listing the generation, usage, and activity involved in the derivation relationship. Applications are free to decide which level of granularity they want describe, and PROV gives them the way to do that.</p>
@@ -1396,21 +1474,21 @@
<p>To illustrate expanded relations, we revisit the concept of
association, introduced
-in <a class="section-ref" href="#section-agents-attribution-association-delegation"><span>TBD</span></a> (full definition of the expanded association can be found
-in <a class="section-ref" href="#term-Association"><span>TBD</span></a>). Agents may rely on <em>plans</em>, i.e. sets of actions or steps, to achieve their
+in <a class="section-ref" href="#section-agents-attribution-association-delegation"><span>Section 2.1.3</span></a> (full definition of the expanded association can be found
+in <a class="section-ref" href="#term-Association"><span>Section 5.3.3</span></a>). Agents may rely on <em>plans</em>, i.e. sets of actions or steps, to achieve their
goals in the context of an activity.
Hence, an expanded form of
association relation allows for a plan to be specified. Plan is defined by subtyping and
full association by an expanded relation, as follows. </p>
<p>
-<span class="glossary-ref" data-ref="glossary-plan" data-withspan="true">
-</span>
+<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>
<p>
-<span class="glossary-ref" data-ref="glossary-association" data-withspan="true"></span>
+<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>
<p>There exist no
@@ -1422,16 +1500,16 @@
manage expectation failures, or to provide explanations.</p>
-<div class="anexample conceptexample" id="association-example2">
+<div class="anexample conceptexample" id="association-example2"><div class="anexampleTitle">Example 12<sup><a class="internalDFN" href="#association-example2"><span class="diamond"> ◊</span></a></sup></div>
<p>An example of association between an activity and an agent involving a plan is:
an XSLT transform (an activity) launched by a user (an agent) based on an XSL style sheet (a plan).
-</div>
+</p></div>
</section>
<section id="section-prov-extended-approach-optional-identification">
-<h2>Optional Identification</h2>
+<h5><span class="secno">2.2.1.3 </span>Optional Identification</h5>
<p>Some concepts exhibit both a core use, expressed as
binary relation, and an extended use, expressed as n-ary relation. In
@@ -1443,9 +1521,9 @@
more elements. This optional identifier can then be used to refer to
an instance as part of other concepts.</p>
-<div class="anexample conceptexample" id="identifier-example">
+<div class="anexample conceptexample" id="identifier-example"><div class="anexampleTitle">Example 13<sup><a class="internalDFN" href="#identifier-example"><span class="diamond"> ◊</span></a></sup></div>
<p>A service may read a same configuration file on two different occasions. Each usage can be identifed by its own identifier, allowing them to be distinguished.
-</div>
+</p></div>
</section>
@@ -1453,9 +1531,9 @@
<section id="section-prov-extended-approach-further-relations">
-<h2>Further Relations</h2>
-
-<p>Finally, PROV supports further relations that are not subtypes or expanded versions of existing relations (such as <a title="Specialization">specialization</a>, <a title="Alternate">alternate</a>).</p>
+<h5><span class="secno">2.2.1.4 </span>Further Relations</h5>
+
+<p>Finally, PROV supports further relations that are not subtypes or expanded versions of existing relations (such as <a title="Specialization" href="#concept-specialization" class="internalDFN">specialization</a>, <a title="Alternate" href="#concept-alternate" class="internalDFN">alternate</a>).</p>
</section>
@@ -1464,16 +1542,16 @@
<section id="section-provenance-of-provnance">
-<h2>Provenance of Provenance</h2>
+<h4><span class="secno">2.2.2 </span>Provenance of Provenance</h4>
<p>
-<span class="glossary-ref" data-ref="glossary-bundle" data-withspan="true">
-</span>
-
-<p>
+<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><p>
For users to decide whether they can place their trust in
something, they may want to analyze its provenance, but also determine
the agent its provenance is attributed to, and when it was
@@ -1483,7 +1561,7 @@
expressed.
</p>
-<div class="anexample conceptexample" id="bundle-example">
+<div class="anexample conceptexample" id="bundle-example"><div class="anexampleTitle">Example 14<sup><a class="internalDFN" href="#bundle-example"><span class="diamond"> ◊</span></a></sup></div>
<p>
In a decision making situation, decision makers may be presented with the same piece of knowledge, issued by multiple sources. In order to validate this piece of knowledge, decision makers can consider its provenance, but also the provenance of its provenance, which may help determine whether it can be trusted.
</p>
@@ -1491,16 +1569,16 @@
</section>
<section id="section-collections">
-<h2>Collections</h2>
+<h4><span class="secno">2.2.3 </span>Collections</h4>
<p>
-<span class="glossary-ref" data-ref="glossary-collection" data-withspan="true"></span> Many different types of collections exist, such as <em>sets</em>, <em>dictionaries</em>, or <em>lists</em>.
+<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> Many different types of collections exist, such as <em>sets</em>, <em>dictionaries</em>, or <em>lists</em>.
Using Collections, one can express the provenance of the collection itself in addition to that of the members. </p>
-<div class="anexample conceptexample" id="collection-example">
+<div class="anexample conceptexample" id="collection-example"><div class="anexampleTitle">Example 15<sup><a class="internalDFN" href="#collection-example"><span class="diamond"> ◊</span></a></sup></div>
<p>
An example of collection is an archive of documents. Each document has its own provenance, but the archive itself also has some provenance: who maintained it, which documents it contained at which point in time, how it was assembled, etc.
-</div>
+</p></div>
</section>
@@ -1512,7 +1590,7 @@
</section>
<section id="section-overview-components">
-<h2>Modular Organization</h2>
+<h3><span class="secno">2.3 </span>Modular Organization</h3>
<p>Besides the separation between core and extended structures, PROV-DM
is further organized according to components, grouping concepts in a
@@ -1520,18 +1598,18 @@
<p> <a href="#components-overview">Table 3</a> enumerates the six components, five of which have already been implicitly overviewed in this section. All components contain extended structures, whereas only the first three contain core structures.
-<div id="components-overview-div" style="text-align: center;">
-<table class="thinborder" style="margin-left: auto; margin-right: auto;">
-<caption id="components-overview">Components Overview</caption> <!-- Table 3: -->
-<tr><td style="border-width: 0px; "></td><td>Component</td><td>Core <br>Structures</td><td>Overview</td><td>Specification</td><td>Description</td></tr>
+</p><div id="components-overview-div" style="text-align: center;">
+<table class="thinborder" style="margin-left: auto; margin-right: auto;">
+<caption id="components-overview"><span>Table 3<sup><a class="internalDFN" href="#components-overview"><span class="diamond"> ◊:</span></a></sup> </span>Components Overview</caption> <!-- Table 3: -->
+<tbody><tr><td style="border-width: 0px; "></td><td>Component</td><td>Core <br>Structures</td><td>Overview</td><td>Specification</td><td>Description</td></tr>
<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
-<tr><td style=" padding: 8px;">1</td><td style="text-align: left;">Entities and Activities</td><td>✔</td><td><a href="#section-entity-activity">2.1.1</a></td><td><a href="#component1">5.1</a></td><td style="text-align: left;">about entities and activities, and their interrelations</td></tr>
-<tr><td>2</td><td style="text-align: left;">Derivation</td><td>✔</td><td><a href="#section-derivation">2.1.2</a></td><td><a href="#component2">5.2</a></td><td style="text-align: left;">about derivation and its subtypes</td></tr>
-<tr><td>3</td><td style="text-align: left;">Agent and Responsibility</td><td>✔</td><td><a href="#section-agents-attribution-association-delegation">2.1.3</a></td><td><a href="#component3">5.3</a></td><td style="text-align: left;">about agents and concepts ascribing responsibility to them</td></tr>
+<tr><td style=" padding: 8px;">1</td><td style="text-align: left;">Entities and Activities</td><td>✔</td><td><a href="#section-entity-activity">2.1.1</a></td><td><a href="#component1">5.1</a></td><td style="text-align: left;">about entities and activities, and their interrelations</td></tr>
+<tr><td>2</td><td style="text-align: left;">Derivation</td><td>✔</td><td><a href="#section-derivation">2.1.2</a></td><td><a href="#component2">5.2</a></td><td style="text-align: left;">about derivation and its subtypes</td></tr>
+<tr><td>3</td><td style="text-align: left;">Agent and Responsibility</td><td>✔</td><td><a href="#section-agents-attribution-association-delegation">2.1.3</a></td><td><a href="#component3">5.3</a></td><td style="text-align: left;">about agents and concepts ascribing responsibility to them</td></tr>
<tr><td>4</td><td style="text-align: left;">Bundles</td><td></td><td><a href="#section-provenance-of-provnance">2.2.2</a></td><td><a href="#component4">5.4</a></td><td style="text-align: left;">about bundles, a mechanism to support provenance of provenance</td></tr>
-<tr><td>5</td><td style="text-align: left;">Alternate</td><td></td><td>—</td><td><a href="#component5">5.5</a></td><td style="text-align: left;">about relations linking entities referring the same thing</td></tr>
+<tr><td>5</td><td style="text-align: left;">Alternate</td><td></td><td>—</td><td><a href="#component5">5.5</a></td><td style="text-align: left;">about relations linking entities referring to the same thing</td></tr>
<tr><td>6</td><td style="text-align: left;">Collections</td><td></td><td><a href="#section-collections">2.2.3</a></td><td><a href="#component6">5.6</a></td><td style="text-align: left;">about collections</td></tr>
-</table>
+</tbody></table>
</div>
</section>
@@ -1539,12 +1617,12 @@
</section>
-<section class="informative" id="prov-notation">
-<h2>The Provenance Notation</h2>
+<section class="informative" id="prov-notation">
+<!--OddPage--><h2><span class="secno">3. </span>The Provenance Notation</h2><p><em>This section is non-normative.</em></p>
<p>To illustrate the application of PROV concepts to a concrete example (see <a href="#prov-dm-example">Section 4</a>) and to provide examples of concepts (see <a href="#data-model-components">Section 5</a>),
-we introduce PROV-N, a notation for writing instances of the PROV data model. For full details and for a normative reference, the reader is referred to the companion specification [[!PROV-N]].
+we introduce PROV-N, a notation for writing instances of the PROV data model. For full details and for a normative reference, the reader is referred to the companion specification [<cite><a class="bibref" href="#bib-PROV-N">PROV-N</a></cite>].
PROV-N is a notation aimed at human consumption, with the following characteristics:</p>
<ul>
<li>PROV-N expressions adopt a <em>functional notation</em> consisting
@@ -1568,25 +1646,21 @@
</li>
</ul>
-<div class="anexample" id="anexample-prov-n">
+<div class="anexample" id="anexample-prov-n"><div class="anexampleTitle">Example 16<sup><a class="internalDFN" href="#anexample-prov-n"><span class="diamond"> ◊</span></a></sup></div>
<p>
An activity with identifier <span class="name">a1</span> and an attribute <span class="name">type</span> with value <span class="name">createFile</span>.
-<pre class="codeexample" >
-activity(a1, [ prov:type="createFile" ])
+</p><pre class="codeexample">activity(a1, [ prov:type="createFile" ])
</pre>
Two entities with identifiers <span class="name">e1</span> and <span class="name">e2</span>.
-<pre class="codeexample" >
-entity(e1)
+<pre class="codeexample">entity(e1)
entity(e2)
</pre>
The activity <span class="name">a1</span> used <span class="name">e1</span>, and <span class="name">e2</span> was generated by <span class="name">a1</span>.
-<pre class="codeexample" >
-used(a1, e1)
+<pre class="codeexample">used(a1, e1)
wasGeneratedBy(e2, a1)
</pre>
The same descriptions, but with an explicit identifier <span class="name">u1</span> for the usage, and the syntactic marker '<span class="name">-</span>' to mark the absence of identifier in the generation. Both are followed by '<span class="name">;</span>'.
-<pre class="codeexample" >
-used(u1; a1, e1)
+<pre class="codeexample">used(u1; a1, e1)
wasGeneratedBy(-; e2, a1)
</pre>
</div>
@@ -1597,7 +1671,7 @@
<section class="informative" id="prov-dm-example">
-<h2>Illustration of PROV-DM by an Example</h2>
+<!--OddPage--><h2><span class="secno">4. </span>Illustration of PROV-DM by an Example</h2><p><em>This section is non-normative.</em></p>
<p><a href="#section-prov-overview">Section 2</a> has introduced some provenance concepts, and how they are expressed as types or relations in the PROV data model. The purpose of this section is to put these concepts into practice in order to express the provenance of some document published on the Web.
With this realistic example, PROV concepts are composed together, and a graphical illustration shows a provenance description forming a directed graph, rooted at the entity we want to explain the provenance of, and pointing to the entities, activities, and agents it depended on. This example also shows that, sometimes, multiple provenance descriptions about the same entity can co-exist, which then justifies the need for provenance of provenance.</p>
@@ -1605,14 +1679,14 @@
<p>In this example, we consider one of the many documents published by the World Wide Web Consortium, and describe its provenance.
Specifically, we consider the document identified by
-<a href="http://www.w3.org/TR/2011/WD-prov-dm-20111215">http://www.w3.org/TR/2011/WD-prov-dm-20111215</a>. Its provenance can be expressed from several perspectives: first, provenance can take the authors' viewpoint; second, it can be concerned with the W3C process. Then, attribution of these two provenance descriptions is provided.</p>
+<a href="http://www.w3.org/TR/2011/WD-prov-dm-20111215">http://www.w3.org/TR/2011/WD-prov-dm-20111215</a>. Its provenance can be expressed from several perspectives: first, provenance can take the authors' viewpoint; second, it can be concerned with the <abbr title="World Wide Web Consortium">W3C</abbr> process. Then, attribution of these two provenance descriptions is provided.</p>
<section id="section-example-one">
-<h3>Example: The Authors View</h3>
-
-
-<p style="font-style:italic; " ><b>Description:</b> A document
+<h3><span class="secno">4.1 </span>Example: The Authors View</h3><p><em>This section is non-normative.</em></p>
+
+
+<p style="font-style:italic; "><b>Description:</b> A document
is edited by some editor, using contributions from various
contributors.
</p>
@@ -1625,47 +1699,42 @@
-<p>We paraphrase some PROV descriptions, express them with the PROV-N notation, and depict them with a graphical illustration (see <a href="#prov-a-document1-top">Figure 2</a>).
+<p>We paraphrase some PROV descriptions, express them with the PROV-N notation, and depict them with a graphical illustration (see <a href="#prov-a-document1-top" class="fig-ref">Figure 2</a>).
Full details of the provenance record can be found <a href="examples/w3c-publication1.provn">here</a>.</p>
<div style="text-align: center; ">
- <figure id="prov-a-document1-top">
- <img src="images/dm/w3c-publication1.png" alt="Provenance of a Document (1)" style="max-width: 98%; "/><br>
-<figcaption id="prov-a-document1">Provenance of a Document (part 1) (Informative)</figcaption> <!-- Figure 2 -->
- </figure>
+ <span class="figure" id="prov-a-document1-top">
+ <img src="images/dm/w3c-publication1.png" alt="Provenance of a Document (1)" style="max-width: 98%; "><br>
+<span class="figcaption" id="prov-a-document1">Figure 2<sup><a class="internalDFN" href="#prov-a-document1"><span class="diamond"> ◊:</span></a></sup> Provenance of a Document (part 1) (Informative)</span> <!-- Figure 2 -->
+ </span>
</div>
<ul>
<li>There was a document <span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111215">tr:WD-prov-dm-20111215</a></span>, which from the author's perspective was a document in its second version.
-<pre>
-entity(tr:WD-prov-dm-20111215, [ prov:type="document", ex:version="2" ])
+<pre>entity(tr:WD-prov-dm-20111215, [ prov:type="document", ex:version="2" ])
</pre>
</li>
<li>There was an editing activity.
-<pre>
-activity(ex:edit1, [ prov:type="edit" ])
+<pre>activity(ex:edit1, [ prov:type="editing" ])
</pre>
</li>
-<li>The document was generated by the editing activity: this was a <a title="Generation">Generation</a>. Its time is not specified, hence, the marker '-'.
-<pre>
-wasGeneratedBy(tr:WD-prov-dm-20111215, ex:edit1, -)
+<li>The document was generated by the editing activity: this was a <a title="Generation" href="#concept-generation" class="internalDFN">Generation</a>. Its time is not specified, hence, the marker '-'.
+<pre>wasGeneratedBy(tr:WD-prov-dm-20111215, ex:edit1, -)
</pre>
</li>
<li>There were some agents.
-<pre>
-agent(ex:Paolo, [ prov:type='prov:Person' ])
+<pre>agent(ex:Paolo, [ prov:type='prov:Person' ])
agent(ex:Simon, [ prov:type='prov:Person' ])
</pre>
</li>
<li>Agents were assigned various responsibilities in the editing activity: contributor and editor. The plan the agent relied upon is not specified, hence, the marker '-'.
-<pre>
-wasAssociatedWith(ex:edit1, ex:Paolo, -, [ prov:role="editor" ])
+<pre>wasAssociatedWith(ex:edit1, ex:Paolo, -, [ prov:role="editor" ])
wasAssociatedWith(ex:edit1, ex:Simon, -, [ prov:role="contributor" ])
</pre>
</li>
@@ -1673,7 +1742,7 @@
<p>
Provenance descriptions can be <em>illustrated</em> graphically. The illustration is not intended to represent all the details of the model, but it is intended to show the essence of a set of
-provenance descriptions [[PROV-LAYOUT]]. Therefore, it should not be seen as an alternate notation for expressing provenance.</p>
+provenance descriptions [<cite><a class="bibref" href="#bib-PROV-LAYOUT">PROV-LAYOUT</a></cite>]. Therefore, it should not be seen as an alternate notation for expressing provenance.</p>
<p>The graphical illustration takes the form of a graph. Entities, activities and agents are represented as nodes, with oval, rectangular, and pentagonal shapes, respectively. Usage,
Generation, Derivation, and Association are represented as directed edges.</p>
@@ -1686,21 +1755,21 @@
</section>
<section id="section-example-two">
-<h3>Example: The Process View</h3>
-
-
-<p style="font-style:italic; " ><b>Description:</b> The World Wide Web
+<h3><span class="secno">4.2 </span>Example: The Process View</h3>
+
+
+<p style="font-style:italic; "><b>Description:</b> The World Wide Web
Consortium publishes documents according to its publication
policy. Working drafts are published regularly to reflect the work
accomplished by working groups. Every publication of a working draft
must be preceded by a "publication request" to the Webmaster. The
very first version of a document must also be preceded by a
-"transition request" to be approved by the W3C director. All working
+"transition request" to be approved by the <abbr title="World Wide Web Consortium">W3C</abbr> director. All working
drafts are made available at a unique IRI. In this scenario, we consider two successive versions of a given document, the policy according to which they were published, and the associated requests.
</p>
<p>
-We describe the kind of provenance record that the <a href="http://www.w3.org/Consortium">WWW Consortium</a> could keep for auditors to check that due processes are followed. All entities involved in this example are Web resources, with well-defined IRIs (some of which refer to archived email messages, available to W3C Members).</p>
+We describe the kind of provenance record that the <a href="http://www.w3.org/Consortium">WWW Consortium</a> could keep for auditors to check that due processes are followed. All entities involved in this example are Web resources, with well-defined IRIs (some of which refer to archived email messages, available to <abbr title="World Wide Web Consortium">W3C</abbr> Members).</p>
<ul>
<li> Two versions of a document were involved: <span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111215">tr:WD-prov-dm-20111215</a></span> (second working draft) and <span class="name"><span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018">tr:WD-prov-dm-20111018</a></span></span> (first working draft);</li>
@@ -1717,53 +1786,47 @@
</ul>
<p>
-We now paraphrase some PROV descriptions, and express them with the PROV-N notation, and depict them with a graphical illustration (see <a href="#prov-a-document2-top">Figure 3</a>). Full details of the provenance record can be found <a href="examples/w3c-publication2.provn">here</a>.
-
-<div style="text-align: center;">
- <figure id="prov-a-document2-top">
- <img src="images/dm/w3c-publication2.png" alt="Provenance of a Document (2)" style="max-width: 90%; "/><br>
-<figcaption id="prov-a-document2">Provenance of a Document (part 2) (Informative)</figcaption> <!-- figure 3 -->
- </figure>
+We now paraphrase some PROV descriptions, and express them with the PROV-N notation, and depict them with a graphical illustration (see <a href="#prov-a-document2-top" class="fig-ref">Figure 3</a>). Full details of the provenance record can be found <a href="examples/w3c-publication2.provn">here</a>.
+
+</p><div style="text-align: center;">
+ <span class="figure" id="prov-a-document2-top">
+ <img src="images/dm/w3c-publication2.png" alt="Provenance of a Document (2)" style="max-width: 90%; "><br>
+<span class="figcaption" id="prov-a-document2">Figure 3<sup><a class="internalDFN" href="#prov-a-document2"><span class="diamond"> ◊:</span></a></sup> Provenance of a Document (part 2) (Informative)</span> <!-- figure 3 -->
+ </span>
</div>
<ul>
<li>There was a document, a working draft (<a href="http://www.w3.org/2001/02pd/rec54#WD">rec54:WD</a>), which is an entity so that we can describe its provenance. Similar descriptions exist for all entities.
-<pre>
-entity(tr:WD-prov-dm-20111215, [ prov:type='rec54:WD' ])
+<pre>entity(tr:WD-prov-dm-20111215, [ prov:type='rec54:WD' ])
</pre>
</li>
<li>There was a publication activity.
-<pre>
-activity(ex:act2, [ prov:type="publish" ])
-</pre>
-</li>
-
-<li>The document was generated by the publication activity: this was a <a title="Generation">Generation</a>. Its time is not specified, hence, the marker '-'.
-<pre>
-wasGeneratedBy(tr:WD-prov-dm-20111215, ex:act2, -)
-</pre>
-</li>
-
-
-<li>The second draft of the document was derived from the first draft: this was a <a title="Derivation">Derivation</a>.
-<pre>
-wasDerivedFrom(tr:WD-prov-dm-20111215, tr:WD-prov-dm-20111018)
+<pre>activity(ex:act2, [ prov:type="publish" ])
</pre>
</li>
-<li>The activity required a publication request: this was a <a>Usage</a>. Its time is not specified, hence, the marker '-'.
-<pre>
-used(ex:act2, email:2011Dec/0111, -)
+<li>The document was generated by the publication activity: this was a <a title="Generation" href="#concept-generation" class="internalDFN">Generation</a>. Its time is not specified, hence, the marker '-'.
+<pre>wasGeneratedBy(tr:WD-prov-dm-20111215, ex:act2, -)
</pre>
</li>
-<li>The activity was associated with the Consortium agent, and proceeded according to its publication policy: this is an <a title="Association">Association</a>.
-<pre>
-wasAssociatedWith(ex:act2, w3:Consortium, process:rec-advance)
+
+<li>The second draft of the document was derived from the first draft: this was a <a title="Derivation" href="#concept-derivation" class="internalDFN">Derivation</a>.
+<pre>wasDerivedFrom(tr:WD-prov-dm-20111215, tr:WD-prov-dm-20111018)
</pre>
-This relation is illustrated in <a href="#prov-a-document2-top">Figure 3</a> with a multi-edge labelled <span class="name">wasAssociatedWith</span> pointing to an agent and entity (representing a plan).
+</li>
+
+<li>The activity required a publication request: this was a <a href="#concept-usage" class="internalDFN">Usage</a>. Its time is not specified, hence, the marker '-'.
+<pre>used(ex:act2, email:2011Dec/0111, -)
+</pre>
+</li>
+
+<li>The activity was associated with the Consortium agent, and proceeded according to its publication policy: this is an <a title="Association" href="#concept-association" class="internalDFN">Association</a>.
+<pre>wasAssociatedWith(ex:act2, w3:Consortium, process:rec-advance)
+</pre>
+This relation is illustrated in <a href="#prov-a-document2-top" class="fig-ref">Figure 3</a> with a multi-edge labelled <span class="name">wasAssociatedWith</span> pointing to an agent and entity (representing a plan).
</li>
</ul>
@@ -1774,22 +1837,21 @@
-<p> This simple example has shown a variety of PROV concepts, such as Entity, Agent, Activity, Usage, Generation, Derivation, and Association. In this example, it happens that all entities were already Web resources, with readily available IRIs, which we used. We note that some of the resources are public, whereas others have restricted access: provenance statements only make use of their identifiers. If identifiers do not pre-exist, e.g. for activities, then they can be generated, for instance <span class="name">ex:act2</span>, occurring in the namespace identified by prefix <span class="name">ex</span>. We note that the IRI scheme developed by W3C is particularly suited for expressing provenance of these documents, since each IRI denotes a specific version of a document. It then becomes easy to relate the various versions with PROV relations. We note that an Association is a ternary relation (represented by a multi-edge labeled wasAssociatedWith) from an activity to an agent and a plan.</p>
+<p> This simple example has shown a variety of PROV concepts, such as Entity, Agent, Activity, Usage, Generation, Derivation, and Association. In this example, it happens that all entities were already Web resources, with readily available IRIs, which we used. We note that some of the resources are public, whereas others have restricted access: provenance statements only make use of their identifiers. If identifiers do not pre-exist, e.g. for activities, then they can be generated, for instance <span class="name">ex:act2</span>, occurring in the namespace identified by prefix <span class="name">ex</span>. We note that the IRI scheme developed by <abbr title="World Wide Web Consortium">W3C</abbr> is particularly suited for expressing provenance of these documents, since each IRI denotes a specific version of a document. It then becomes easy to relate the various versions with PROV relations. We note that an Association is a ternary relation (represented by a multi-edge labeled wasAssociatedWith) from an activity to an agent and a plan.</p>
</section>
<section id="section-example-c">
-<h3>Example: Attribution of Provenance</h3>
+<h3><span class="secno">4.3 </span>Example: Attribution of Provenance</h3>
<p>The two previous sections offer two different perspectives on the provenance of a document. PROV allows for multiple sources to provide the provenance of a subject. For users to decide whether they can place their trust in the document, they may want to analyze its provenance, but also determine who the provenance is attributed to, and when it was
generated, etc. In other words, we need to be able to express the provenance of provenance.</p>
<p>PROV-DM offers a construct to name a bundle of provenance descriptions (full details: <a href="examples/w3c-publication1.provn">ex:author-view</a>). </p>
-<pre class="codeexample">
-bundle ex:author-view
+<pre class="codeexample">bundle ex:author-view
agent(ex:Paolo, [ prov:type='prov:Person' ])
agent(ex:Simon, [ prov:type='prov:Person' ])
@@ -1801,8 +1863,7 @@
</pre>
Likewise, the process view can be expressed as a separate named bundle (full details: <a href="examples/w3c-publication2.provn">ex:process-view</a>).
-<pre class="codeexample">
-bundle ex:process-view
+<pre class="codeexample">bundle ex:process-view
agent(w3:Consortium, [ prov:type='prov:Organization' ])
@@ -1813,8 +1874,7 @@
<p>To express their respective provenance, these bundles must be seen as entities, and all PROV constructs are now available to express their provenance. In the example below, <span class="name">ex:author-view</span> is attributed to the agent <span class="name">ex:Simon</span>, whereas <span class="name">ex:process-view</span> to <span class="name">w3:Consortium</span>.
-<pre class="codeexample">
-entity(ex:author-view, [ prov:type='prov:Bundle' ])
+</p><pre class="codeexample">entity(ex:author-view, [ prov:type='prov:Bundle' ])
wasAttributedTo(ex:author-view, ex:Simon)
entity(ex:process-view, [ prov:type='prov:Bundle' ])
@@ -1828,7 +1888,7 @@
<section id="data-model-components">
-<h2>PROV-DM Types and Relations</h2>
+<!--OddPage--><h2><span class="secno">5. </span>PROV-DM Types and Relations</h2>
<p>Provenance concepts, expressed as PROV-DM types and relations, are organized according to six components that are defined in this section.
The components and their dependencies are illustrated in <a href="#prov-dm-components">Figure 4</a>. A component that relies on concepts defined in another is displayed above it in the figure. So, for example, component 5 (alternate) depends on concepts defined in component 4 (bundles), itself dependent on concepts defined in component 1 (entity and activity).
@@ -1848,50 +1908,48 @@
<div style="text-align: center;">
-<figure style="max-width: 95%; ">
-<img usemap="#componentMap" src="images/dm/components-dependencies.png" alt="PROV-DM Components" style="max-width: 90%; " />
+<span class="figure" id="fig-figure-4-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="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="268,0,335,67" alt="alternate" 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"/>
+<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>
-<figcaption id="prov-dm-components">PROV-DM Components (Informative)</figcaption> <!-- Figure 4 -->
-</figure>
+<span class="figcaption" id="prov-dm-components">Figure 4<sup><a class="internalDFN" href="#prov-dm-components"><span class="diamond"> ◊:</span></a></sup> PROV-DM Components (Informative)</span> <!-- Figure 4 -->
+</span>
</div>
<p>
-While not all PROV-DM relations are binary, they all involve two primary elements. Hence, <a href="#relations-at-a-glance">Table 4</a> indexes all relations (except <a title="wasInfluencedBy">wasInfluencedBy</a>) according to their two primary elements (referred to as subject and object). The table adopts the same color scheme as <a href="#prov-dm-components">Figure 4</a>, allowing components to be readily identified.
+While not all PROV-DM relations are binary, they all involve two primary elements. Hence, <a href="#relations-at-a-glance">Table 4</a> indexes all relations (except <a title="wasInfluencedBy" href="#dfn-wasinfluencedby" class="internalDFN">wasInfluencedBy</a>) according to their two primary elements (referred to as subject and object). The table adopts the same color scheme as <a href="#prov-dm-components">Figure 4</a>, allowing components to be readily identified.
Relation names appearing in bold correspond to the core structures introduced
in <a href="#core-structures">Section 2.1</a>.</p>
<div id="relations-at-a-glance-div" style="text-align: center;">
-<table class="thinborder" style="margin-left: auto; margin-right: auto;">
-<caption id="relations-at-a-glance">PROV-DM Relations At a Glance</caption> <!-- Table 4 -->
-<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td colspan="6">Object</td></tr>
+<table class="thinborder" style="margin-left: auto; margin-right: auto;">
+<caption id="relations-at-a-glance"><span>Table 4<sup><a class="internalDFN" href="#relations-at-a-glance"><span class="diamond"> ◊:</span></a></sup> </span>PROV-DM Relations At a Glance</caption> <!-- Table 4 -->
+<tbody><tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td colspan="6">Object</td></tr>
<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td colspan="2">Entity</td><td colspan="2">Activity</td><td colspan="2">Agent</td></tr>
-<tr><td rowspan="3">Subject</td><td>Entity</td><td colspan="2"><div class="component2-color"><a class="essential" title="wasDerivedFrom">WasDerivedFrom</a><br><a>Revision</a><br><a>Quotation</a><br><a title="Primary Source">PrimarySource</a></div><div class="component5-color"><a title="alternateOf">AlternateOf</a><br><a title="specializationOf">SpecializationOf</a></div><div class="component6-color"><a title="hadMember">HadMember</a></div></td><td class="component1-color"><a class="essential"
-title="wasGeneratedBy">WasGeneratedBy</a><br><a
-title="wasInvalidatedBy">WasInvalidatedBy</a></td><td class="component1-color" style="font-style: italic; "><a title="role">R</a><br><a title="time">T</a><br><a title="location">L</a><br></td><td class="component3-color" colspan="2"><a class="essential" title="wasAttributedTo">WasAttributedTo</a></td></tr>
-<tr><td>Activity</td><td class="component1-color"><a class="essential" title="used">Used</a><br><a title="wasStartedBy">WasStartedBy</a><br><a title="wasEndedBy">WasEndedBy</a></td><td class="component1-color" style="font-style: italic; "><a title="role">R</a><br><a title="time">T</a><br><a title="location">L</a><br></td><td colspan="2" class="component1-color"><a class="essential" title="wasInformedBy">WasInformedBy</a></td><td class="component3-color"><a class="essential" title="wasAssociatedWith">WasAssociatedWith</a></td><td class="component3-color" style="font-style: italic; "><a title="role">R</a><br></td></tr>
-<tr><td>Agent</td><td colspan="2">—</td><td colspan="2">—</td><td class="component3-color" colspan="2"><a class="essential" title="actedOnBehalfOf">ActedOnBehalfOf</a></td></tr>
-</table>
+<tr><td rowspan="3">Subject</td><td>Entity</td><td colspan="2"><div class="component2-color"><a class="essential internalDFN" title="wasDerivedFrom" href="#dfn-wasderivedfrom">WasDerivedFrom</a><br><a href="#concept-revision" class="internalDFN">Revision</a><br><a href="#concept-quotation" class="internalDFN">Quotation</a><br><a title="Primary Source" href="#concept-primary-source" class="internalDFN">PrimarySource</a></div><div class="component5-color"><a title="alternateOf" href="#dfn-alternateof" class="internalDFN">AlternateOf</a><br><a title="specializationOf" href="#dfn-specializationof" class="internalDFN">SpecializationOf</a></div><div class="component6-color"><a title="hadMember" href="#dfn-hadmember" class="internalDFN">HadMember</a></div></td><td class="component1-color"><a class="essential internalDFN" title="wasGeneratedBy" href="#dfn-wasgeneratedby">WasGeneratedBy</a><br><a title="wasInvalidatedBy" href="#dfn-wasinvalidatedby" class="internalDFN">WasInvalidatedBy</a></td><td class="component1-color" style="font-style: italic; "><a title="role" href="#concept-role" class="internalDFN">R</a><br><a title="time" href="#dfn-time" class="internalDFN">T</a><br><a title="location" href="#concept-location" class="internalDFN">L</a><br></td><td class="component3-color" colspan="2"><a class="essential internalDFN" title="wasAttributedTo" href="#dfn-wasattributedto">WasAttributedTo</a></td></tr>
+<tr><td>Activity</td><td class="component1-color"><a class="essential internalDFN" title="used" href="#dfn-used">Used</a><br><a title="wasStartedBy" href="#dfn-wasstartedby" class="internalDFN">WasStartedBy</a><br><a title="wasEndedBy" href="#dfn-wasendedby" class="internalDFN">WasEndedBy</a></td><td class="component1-color" style="font-style: italic; "><a title="role" href="#concept-role" class="internalDFN">R</a><br><a title="time" href="#dfn-time" class="internalDFN">T</a><br><a title="location" href="#concept-location" class="internalDFN">L</a><br></td><td colspan="2" class="component1-color"><a class="essential internalDFN" title="wasInformedBy" href="#dfn-wasinformedby">WasInformedBy</a></td><td class="component3-color"><a class="essential internalDFN" title="wasAssociatedWith" href="#dfn-wasassociatedwith">WasAssociatedWith</a></td><td class="component3-color" style="font-style: italic; "><a title="role" href="#concept-role" class="internalDFN">R</a><br></td></tr>
+<tr><td>Agent</td><td colspan="2">—</td><td colspan="2">—</td><td class="component3-color" colspan="2"><a class="essential internalDFN" title="actedOnBehalfOf" href="#dfn-actedonbehalfof">ActedOnBehalfOf</a></td></tr>
+</tbody></table>
</div>
<p>The letters 'R' and 'L' appearing in the right-hand side of some cells of <a href="#relations-at-a-glance">Table 4</a> indicate that attributes
-<a title="role">prov:role</a> (<a class="section-ref" href="#term-attribute-role"><span>TBD</span></a>)
+<a title="role" href="#concept-role" class="internalDFN">prov:role</a> (<a class="section-ref" href="#term-attribute-role"><span>Section 5.7.2.3</span></a>)
and
-<a title="location">prov:location</a> (<a class="section-ref" href="#term-attribute-location"><span>TBD</span></a>)
+<a title="location" href="#concept-location" class="internalDFN">prov:location</a> (<a class="section-ref" href="#term-attribute-location"><span>Section 5.7.2.2</span></a>)
are permitted for these relations.
-The letter 'T' indicates an OPTIONAL <a title="time">time</a> is also permitted.
+The letter 'T' indicates an <em class="rfc2119" title="OPTIONAL">OPTIONAL</em> <a title="time" href="#dfn-time" class="internalDFN">time</a> is also permitted.
</p>
@@ -1901,14 +1959,14 @@
<div id="secondary-elements-relations-at-a-glance-div" style="text-align: center;">
-<table class="thinborder" style="margin-left: auto; margin-right: auto;">
-<caption id="secondary-elements-relations-at-a-glance">Secondary optional elements in PROV-DM Relations</caption> <!-- Table 4 -->
-<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td colspan="3">Secondary Object</td></tr>
-<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td>Entity</td><td>Activity</td><td >Agent</td></tr>
-<tr><td rowspan="3">Subject</td><td>Entity</td><td>—</td><td class="component2-color"><a title="wasDerivedFrom">WasDerivedFrom</a> (<a href="#derivation.activity">activity</a>)</td><td>—</td></tr>
-<tr><td>Activity</td><td class="component3-color"><a title="wasAssociatedWith">WasAssociatedWith</a> (<a href="#association.plan">plan</a>)</td><td class="component1-color"><a title="wasStartedBy">WasStartedBy</a> (<a href="#start.starter">starter</a>)<br><a title="wasEndedBy">WasEndedBy</a> (<a href="#end.ender">ender</a>)</td><td>—</td></tr>
-<tr><td>Agent</td><td>—</td><td class="component3-color"><a title="actedOnBehalfOf">ActedOnBehalfOf</a> (<a href="#delegation.activity">activity</a>)</td><td>—</td></tr>
-</table>
+<table class="thinborder" style="margin-left: auto; margin-right: auto;">
+<caption id="secondary-elements-relations-at-a-glance"><span>Table 5<sup><a class="internalDFN" href="#secondary-elements-relations-at-a-glance"><span class="diamond"> ◊:</span></a></sup> </span>Secondary optional elements in PROV-DM Relations</caption> <!-- Table 4 -->
+<tbody><tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td colspan="3">Secondary Object</td></tr>
+<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td>Entity</td><td>Activity</td><td>Agent</td></tr>
+<tr><td rowspan="3">Subject</td><td>Entity</td><td>—</td><td class="component2-color"><a title="wasDerivedFrom" href="#dfn-wasderivedfrom" class="internalDFN">WasDerivedFrom</a> (<a href="#derivation.activity">activity</a>)</td><td>—</td></tr>
+<tr><td>Activity</td><td class="component3-color"><a title="wasAssociatedWith" href="#dfn-wasassociatedwith" class="internalDFN">WasAssociatedWith</a> (<a href="#association.plan">plan</a>)</td><td class="component1-color"><a title="wasStartedBy" href="#dfn-wasstartedby" class="internalDFN">WasStartedBy</a> (<a href="#start.starter">starter</a>)<br><a title="wasEndedBy" href="#dfn-wasendedby" class="internalDFN">WasEndedBy</a> (<a href="#end.ender">ender</a>)</td><td>—</td></tr>
+<tr><td>Agent</td><td>—</td><td class="component3-color"><a title="actedOnBehalfOf" href="#dfn-actedonbehalfof" class="internalDFN">ActedOnBehalfOf</a> (<a href="#delegation.activity">activity</a>)</td><td>—</td></tr>
+</tbody></table>
</div>
@@ -1916,54 +1974,54 @@
<div id="prov-dm-types-and-relations-fig" style="text-align: left;">
-<table class="thinborder" style="margin-left: auto; margin-right: auto;">
-<caption id="prov-dm-types-and-relations">PROV-DM Types and Relations</caption> <!-- Table 6-->
-<tr><td><b>Type or Relation Name</b></td><td><b>Representation in the PROV-N notation</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 class="essential"><a>Entity</a></td><td><a title="dfn-Entity" class="essential">entity(id, [ attr1=val1, ...])</a></td><td rowspan="8"><a href="#component1">Component 1: Entities/Activities</a></td></tr>
-<tr class="component1-color"><td class="essential"><a>Activity</a></td><td><a title="dfn-Activity" class="essential">activity(id, st, et, [ attr1=val1, ...])</a></td></tr>
-<tr class="component1-color"><td class="essential"><a>Generation</a></td><td><a title="wasGeneratedBy"><span class="essential">wasGeneratedBy(</span>id;<span class="essential">e,a</span>,t,attrs<span class="essential">)</span></a></td></tr>
-<tr class="component1-color"><td class="essential"><a>Usage</a></td><td><a title="used"><span class="essential">used(</span>id;<span class="essential">a,e</span>,t,attrs<span class="essential">)</span></a></td></tr>
-<tr class="component1-color"><td class="essential"><a>Communication</a></td><td><a title="wasInformedBy"><span class="essential">wasInformedBy(</span>id;<span class="essential">a2,a1</span>,attrs<span class="essential">)</span></a></td></tr>
-<tr class="component1-color"><td><a>Start</a></td><td><a title="wasStartedBy">wasStartedBy(id;a2,e,a1,t,attrs)</a></td></tr>
-<tr class="component1-color"><td><a>End</a></td><td><a title="wasEndedBy">wasEndedBy(id;a2,e,a1,t,attrs)</a></td></tr>
-<tr class="component1-color"><td><a>Invalidation</a></td><td><a title="wasInvalidatedBy">wasInvalidatedBy(id;e,a,t,attrs)</a></td></tr>
+<table class="thinborder" style="margin-left: auto; margin-right: auto;">
+<caption id="prov-dm-types-and-relations"><span>Table 6<sup><a class="internalDFN" href="#prov-dm-types-and-relations"><span class="diamond"> ◊:</span></a></sup> </span>PROV-DM Types and Relations</caption> <!-- Table 6-->
+<tbody><tr><td><b>Type or Relation Name</b></td><td><b>Representation in the PROV-N notation</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="component2-color"><td class="essential"><a>Derivation</a></td><td><a title="wasDerivedFrom"><span class="essential">wasDerivedFrom(</span>id; <span class="essential">e2, e1</span>, a, g2, u1, attrs<span class="essential">)</span></a></td><td rowspan="4"><a href="#component2">Component 2: Derivations</a></td></tr>
-<tr class="component2-color"><td class="provType"><a>Revision</a></td><td><a title="dfn-prov:revision">... prov:type='prov:Revision' ...</a></td></tr>
-<tr class="component2-color"><td class="provType"><a>Quotation</a></td><td><a title="dfn-prov:quotation">... prov:type='prov:Quotation' ...</a></td></tr>
-<tr class="component2-color"><td class="provType"><a>Primary Source</a></td><td><a title="dfn-prov:primary-source">... prov:type='prov:PrimarySource' ...</a></td></tr>
+<tr class="component1-color"><td class="essential"><a href="#concept-entity" class="internalDFN">Entity</a></td><td><a title="dfn-Entity" class="essential internalDFN" href="#dfn-entity">entity(id, [ attr1=val1, ...])</a></td><td rowspan="8"><a href="#component1">Component 1: Entities/Activities</a></td></tr>
+<tr class="component1-color"><td class="essential"><a href="#concept-activity" class="internalDFN">Activity</a></td><td><a title="dfn-Activity" class="essential internalDFN" href="#dfn-activity">activity(id, st, et, [ attr1=val1, ...])</a></td></tr>
+<tr class="component1-color"><td class="essential"><a href="#concept-generation" class="internalDFN">Generation</a></td><td><a title="wasGeneratedBy" href="#dfn-wasgeneratedby" class="internalDFN"><span class="essential">wasGeneratedBy(</span>id;<span class="essential">e,a</span>,t,attrs<span class="essential">)</span></a></td></tr>
+<tr class="component1-color"><td class="essential"><a href="#concept-usage" class="internalDFN">Usage</a></td><td><a title="used" href="#dfn-used" class="internalDFN"><span class="essential">used(</span>id;<span class="essential">a,e</span>,t,attrs<span class="essential">)</span></a></td></tr>
+<tr class="component1-color"><td class="essential"><a href="#concept-communication" class="internalDFN">Communication</a></td><td><a title="wasInformedBy" href="#dfn-wasinformedby" class="internalDFN"><span class="essential">wasInformedBy(</span>id;<span class="essential">a2,a1</span>,attrs<span class="essential">)</span></a></td></tr>
+<tr class="component1-color"><td><a href="#concept-start" class="internalDFN">Start</a></td><td><a title="wasStartedBy" href="#dfn-wasstartedby" class="internalDFN">wasStartedBy(id;a2,e,a1,t,attrs)</a></td></tr>
+<tr class="component1-color"><td><a href="#concept-end" class="internalDFN">End</a></td><td><a title="wasEndedBy" href="#dfn-wasendedby" class="internalDFN">wasEndedBy(id;a2,e,a1,t,attrs)</a></td></tr>
+<tr class="component1-color"><td><a href="#concept-invalidation" class="internalDFN">Invalidation</a></td><td><a title="wasInvalidatedBy" href="#dfn-wasinvalidatedby" class="internalDFN">wasInvalidatedBy(id;e,a,t,attrs)</a></td></tr>
<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
-<tr class="component3-color" style="border-collapse: collapse; "><td class="essential"><a>Agent</a></td><td><a title="dfn-agent" class="essential">agent(id, [ attr1=val1, ...])</a></td><td rowspan="9"><a href="#component3">Component 3: Agents, Responsibility, Influence</a></td></tr>
-<tr class="component3-color"><td class="essential"><a>Attribution</a></td><td><a title="wasAttributedTo"><span class="essential">wasAttributedTo(</span>id;<span class="essential">e,ag</span>,attr<span class="essential">)</span></a></td></tr>
-<tr class="component3-color"><td class="essential"><a>Association</a></td><td><a title="wasAssociatedWith"><span class="essential">wasAssociatedWith(</span>id;<span class="essential">a,ag</span>,pl,attrs<span class="essential">)</span></a></td></tr>
-<tr class="component3-color"><td class="essential"><a>Delegation</a></td><td><a title="actedOnBehalfOf"><span class="essential">actedOnBehalfOf(</span>id;<span class="essential">ag2,ag1</span>,a,attrs<span class="essential">)</span></a></td></tr>
-<tr class="component3-color"><td class="provType"><a>Plan</a></td><td><a title="dfn-prov:plan">... prov:type='prov:Plan' ...</a></td></tr>
-<tr class="component3-color"><td class="provType"><a>Person</a></td><td><a title="dfn-prov:person">... prov:type='prov:Person' ...</a></td></tr>
-<tr class="component3-color"><td class="provType"><a>Organization</a></td><td><a title="dfn-prov:organization">... prov:type='prov:Organization' ...</a></td></tr>
-<tr class="component3-color"><td class="provType"><a title="dfn-prov:softwareAgent">SoftwareAgent</a></td><td><a title="software-agent">... prov:type='prov:SoftwareAgent' ...</a></td></tr>
-<tr class="component3-color"><td><a>Influence</a></td><td><a title="wasInfluencedBy">wasInfluencedBy(id;e2,e1,attrs)</a></td></tr>
+
+<tr class="component2-color"><td class="essential"><a href="#concept-derivation" class="internalDFN">Derivation</a></td><td><a title="wasDerivedFrom" href="#dfn-wasderivedfrom" class="internalDFN"><span class="essential">wasDerivedFrom(</span>id; <span class="essential">e2, e1</span>, a, g2, u1, attrs<span class="essential">)</span></a></td><td rowspan="4"><a href="#component2">Component 2: Derivations</a></td></tr>
+<tr class="component2-color"><td class="provType"><a href="#concept-revision" class="internalDFN">Revision</a></td><td><a title="dfn-prov:revision" href="#dfn-prov:revision" class="internalDFN">... prov:type='prov:Revision' ...</a></td></tr>
+<tr class="component2-color"><td class="provType"><a href="#concept-quotation" class="internalDFN">Quotation</a></td><td><a title="dfn-prov:quotation" href="#dfn-prov:quotation" class="internalDFN">... prov:type='prov:Quotation' ...</a></td></tr>
+<tr class="component2-color"><td class="provType"><a href="#concept-primary-source" class="internalDFN">Primary Source</a></td><td><a title="dfn-prov:primary-source" href="#dfn-prov:primary-source" class="internalDFN">... prov:type='prov:PrimarySource' ...</a></td></tr>
<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
-
-
-<tr class="component4-color"><td><a title="Bundle">Bundle constructor</a></td><td><a title="dfn-bundle">bundle id description_1 ... description_n endBundle</a></td><td rowspan="2"><a href="#component4">Component 4: Bundles</a></td></tr>
-<tr class="component4-color"><td class="provType"><a title="Bundle Type">Bundle type</a></td><td><a title="dfn-prov:bundle">... prov:type='prov:Bundle' ...</a></td></tr>
+<tr class="component3-color" style="border-collapse: collapse; "><td class="essential"><a href="#concept-agent" class="internalDFN">Agent</a></td><td><a title="dfn-agent" class="essential internalDFN" href="#dfn-agent">agent(id, [ attr1=val1, ...])</a></td><td rowspan="9"><a href="#component3">Component 3: Agents, Responsibility, Influence</a></td></tr>
+<tr class="component3-color"><td class="essential"><a href="#concept-attribution" class="internalDFN">Attribution</a></td><td><a title="wasAttributedTo" href="#dfn-wasattributedto" class="internalDFN"><span class="essential">wasAttributedTo(</span>id;<span class="essential">e,ag</span>,attr<span class="essential">)</span></a></td></tr>
+<tr class="component3-color"><td class="essential"><a href="#concept-association" class="internalDFN">Association</a></td><td><a title="wasAssociatedWith" href="#dfn-wasassociatedwith" class="internalDFN"><span class="essential">wasAssociatedWith(</span>id;<span class="essential">a,ag</span>,pl,attrs<span class="essential">)</span></a></td></tr>
+<tr class="component3-color"><td class="essential"><a href="#concept-delegation" class="internalDFN">Delegation</a></td><td><a title="actedOnBehalfOf" href="#dfn-actedonbehalfof" class="internalDFN"><span class="essential">actedOnBehalfOf(</span>id;<span class="essential">ag2,ag1</span>,a,attrs<span class="essential">)</span></a></td></tr>
+<tr class="component3-color"><td class="provType"><a href="#concept-plan" class="internalDFN">Plan</a></td><td><a title="dfn-prov:plan" href="#dfn-prov:plan" class="internalDFN">... prov:type='prov:Plan' ...</a></td></tr>
+<tr class="component3-color"><td class="provType"><a href="#concept-person" class="internalDFN">Person</a></td><td><a title="dfn-prov:person" href="#dfn-prov:person" class="internalDFN">... prov:type='prov:Person' ...</a></td></tr>
+<tr class="component3-color"><td class="provType"><a>Organization</a></td><td><a title="dfn-prov:organization" href="#dfn-prov:organization" class="internalDFN">... prov:type='prov:Organization' ...</a></td></tr>
+<tr class="component3-color"><td class="provType"><a title="dfn-prov:softwareAgent" href="#dfn-prov:softwareAgent" class="internalDFN">SoftwareAgent</a></td><td><a title="software-agent" href="#concept-software-agent" class="internalDFN">... prov:type='prov:SoftwareAgent' ...</a></td></tr>
+<tr class="component3-color"><td><a href="#concept-influence" class="internalDFN">Influence</a></td><td><a title="wasInfluencedBy" href="#dfn-wasinfluencedby" class="internalDFN">wasInfluencedBy(id;e2,e1,attrs)</a></td></tr>
+<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
+
+
+
+<tr class="component4-color"><td><a title="Bundle" href="#concept-bundle" class="internalDFN">Bundle constructor</a></td><td><a title="dfn-bundle" href="#dfn-bundle-constructor" class="internalDFN">bundle id description_1 ... description_n endBundle</a></td><td rowspan="2"><a href="#component4">Component 4: Bundles</a></td></tr>
+<tr class="component4-color"><td class="provType"><a title="Bundle Type" href="#dfn-bundle-type" class="internalDFN">Bundle type</a></td><td><a title="dfn-prov:bundle" href="#dfn-prov:bundle" class="internalDFN">... prov:type='prov:Bundle' ...</a></td></tr>
<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
-<tr class="component5-color"><td><a>Alternate</a></td><td><a title="alternateOf">alternateOf(alt1, alt2)</a></td><td rowspan="2"><a href="#component5">Component 5: Alternate</a></td></tr>
-<tr class="component5-color"><td><a title="Specialization">Specialization</a></td><td><a title="specializationOf">specializationOf(infra, supra)</a></td></tr>
+<tr class="component5-color"><td><a href="#concept-alternate" class="internalDFN">Alternate</a></td><td><a title="alternateOf" href="#dfn-alternateof" class="internalDFN">alternateOf(alt1, alt2)</a></td><td rowspan="2"><a href="#component5">Component 5: Alternate</a></td></tr>
+<tr class="component5-color"><td><a title="Specialization" href="#concept-specialization" class="internalDFN">Specialization</a></td><td><a title="specializationOf" href="#dfn-specializationof" class="internalDFN">specializationOf(infra, supra)</a></td></tr>
<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
-<tr class="component6-color"><td class="provType"><a>Collection</a></td><td><a title="dfn-prov:collection">... prov:type='prov:Collection' ...</a></td><td rowspan="3"><a href="#component6">Component 6: Collections</a></td></tr>
-<tr class="component6-color"><td class="provType"><a title="Empty Collection">EmptyCollection</a></td><td><a title="dfn-prov:emptyCollection">... prov:type='prov:EmptyCollection' ...</a></td></tr>
-<tr class="component6-color"><td><a>Membership</a></td><td><a title="hadMember">hadMember(c,e)</a></td></tr>
-</table>
+<tr class="component6-color"><td class="provType"><a href="#concept-collection" class="internalDFN">Collection</a></td><td><a title="dfn-prov:collection" href="#dfn-prov:collection" class="internalDFN">... prov:type='prov:Collection' ...</a></td><td rowspan="3"><a href="#component6">Component 6: Collections</a></td></tr>
+<tr class="component6-color"><td class="provType"><a title="Empty Collection" href="#concept-empty-collection" class="internalDFN">EmptyCollection</a></td><td><a title="dfn-prov:emptyCollection" href="#dfn-prov:emptyCollection" class="internalDFN">... prov:type='prov:EmptyCollection' ...</a></td></tr>
+<tr class="component6-color"><td><a href="#concept-membership" class="internalDFN">Membership</a></td><td><a title="hadMember" href="#dfn-hadmember" class="internalDFN">hadMember(c,e)</a></td></tr>
+</tbody></table>
</div>
<p>
@@ -1973,17 +2031,17 @@
<section id="component1">
-<h3>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 interrelations: Used (<a>Usage</a>), WasGeneratedBy (<a>Generation</a>), WasStartedBy (<a>Start</a>), WasEndedBy (<a>End</a>), WasInvalidatedBy (<a>Invalidation</a>), and WasInformedBy (<a>Communication</a>). <a href="#figure-component1">Figure 5</a> uses UML to depict the first component.
-Core structures are displayed in the yellow area, consisting of two classes (<a>Entity</a>, <a>Activity</a>) and three binary associations between them: Used (<a>Usage</a>), WasGeneratedBy (<a>Generation</a>), and WasInformedBy (<a>Communication</a>). The rest of the figure displays extended structures, including UML association classes (see [[UML]], section 7.3.4, p. 42), represented in gray, to express expanded n-ary relations for Used (<a>Usage</a>), WasGeneratedBy (<a>Generation</a>), WasInvalidatedBy (<a>Invalidation</a>), WasStartedBy (<a>Start</a>), WasEndedBy (<a>End</a>). The figure also makes explicit associations with <em>time</em> for these concepts (time being marked with the primitive stereotype). When not specified, cardinality is assumed to be 0..*.
+<h3><span class="secno">5.1 </span>Component 1: Entities and Activities</h3>
+
+<p>The first component of PROV-DM is concerned with <a title="Entity" href="#concept-entity" class="internalDFN">entities</a> and <a title="Activity" href="#concept-activity" class="internalDFN">activities</a>, and their interrelations: Used (<a href="#concept-usage" class="internalDFN">Usage</a>), WasGeneratedBy (<a href="#concept-generation" class="internalDFN">Generation</a>), WasStartedBy (<a href="#concept-start" class="internalDFN">Start</a>), WasEndedBy (<a href="#concept-end" class="internalDFN">End</a>), WasInvalidatedBy (<a href="#concept-invalidation" class="internalDFN">Invalidation</a>), and WasInformedBy (<a href="#concept-communication" class="internalDFN">Communication</a>). <a href="#figure-component1">Figure 5</a> uses UML to depict the first component.
+Core structures are displayed in the yellow area, consisting of two classes (<a href="#concept-entity" class="internalDFN">Entity</a>, <a href="#concept-activity" class="internalDFN">Activity</a>) and three binary associations between them: Used (<a href="#concept-usage" class="internalDFN">Usage</a>), WasGeneratedBy (<a href="#concept-generation" class="internalDFN">Generation</a>), and WasInformedBy (<a href="#concept-communication" class="internalDFN">Communication</a>). The rest of the figure displays extended structures, including UML association classes (see [<cite><a class="bibref" href="#bib-UML">UML</a></cite>], section 7.3.4, p. 42), represented in gray, to express expanded n-ary relations for Used (<a href="#concept-usage" class="internalDFN">Usage</a>), WasGeneratedBy (<a href="#concept-generation" class="internalDFN">Generation</a>), WasInvalidatedBy (<a href="#concept-invalidation" class="internalDFN">Invalidation</a>), WasStartedBy (<a href="#concept-start" class="internalDFN">Start</a>), WasEndedBy (<a href="#concept-end" class="internalDFN">End</a>). The figure also makes explicit associations with <em>time</em> for these concepts (time being marked with the primitive stereotype). When not specified, cardinality is assumed to be 0..*.
</p>
<div style="text-align: center;">
-<figure style="max-width: 95%; ">
-<img src="uml/component1.png" alt="entities and activities"/><br>
-<figcaption id="figure-component1">Entities and Activities Component Overview (Informative)</figcaption> <!-- Figure 5 -->
-</figure>
+<span class="figure" id="fig-figure-5-entities-and-activities-component-overview-informative" style="max-width: 95%; ">
+<img src="uml/component1.png" alt="entities and activities"><br>
+<span class="figcaption" id="figure-component1">Figure 5<sup><a class="internalDFN" href="#figure-component1"><span class="diamond"> ◊:</span></a></sup> Entities and Activities Component Overview (Informative)</span> <!-- Figure 5 -->
+</span>
</div>
@@ -1992,26 +2050,24 @@
<section id="term-entity">
-<h4>Entity</h4>
-
-
-<div class="glossary-ref" data-ref="glossary-entity"></div>
-
-
-<p><div class="attributes" id="attributes-entity">An <dfn title="dfn-Entity" id="dfn-entity">entity</dfn><span class="withPn">, written <span class="pnExpression" id="pn-entity">entity(id, [attr1=val1, ...])</span> in PROV-N, </span> has:
+<h4><span class="secno">5.1.1 </span>Entity</h4>
+
+
+<div class="glossary-ref"> An <dfn id="concept-entity" title="Entity" class="internalDFN">entity</dfn><sup><a class="internalDFN" href="#concept-entity"><span class="diamond"> ◊</span></a></sup> is a physical, digital, conceptual, or other kind of thing with some fixed aspects; entities may be real or imaginary. </div>
+
+
+<p></p><div class="attributes" id="attributes-entity">An <dfn title="dfn-Entity" id="dfn-entity" class="internalDFN">entity</dfn><sup><a class="internalDFN" href="#dfn-entity"><span class="diamond"> ◊</span></a></sup><span class="withPn">, written <span class="pnExpression" id="pn-entity">entity(id, [attr1=val1, ...])</span> in PROV-N, </span> has:
<ul>
-<li><span class='attribute' id="entity.id">id</span>: an identifier for an entity; </li>
-<li><span class='attribute' id="entity.attributes">attributes</span>: an OPTIONAL set of attribute-value pairs ((<span class="name">attr1</span>, <span class="name">val1</span>), ...) representing additional information about the fixed aspects of this entity.</li>
+<li><span class="attribute" id="entity.id">id</span>: an identifier for an entity; </li>
+<li><span class="attribute" id="entity.attributes">attributes</span>: an <em class="rfc2119" title="OPTIONAL">OPTIONAL</em> set of attribute-value pairs ((<span class="name">attr1</span>, <span class="name">val1</span>), ...) representing additional information about the fixed aspects of this entity.</li>
</ul></div>
-<div class="anexample" id="anexample-entity">
+<div class="anexample" id="anexample-entity"><div class="anexampleTitle">Example 17<sup><a class="internalDFN" href="#anexample-entity"><span class="diamond"> ◊</span></a></sup></div>
<p>
The following expression</p>
-<pre class="codeexample">
-entity(tr:WD-prov-dm-20111215, [ prov:type="document", ex:version="2" ])
+<pre class="codeexample">entity(tr:WD-prov-dm-20111215, [ prov:type="document", ex:version="2" ])
</pre>
-states the existence of an entity, denoted by identifier <span class="name">tr:WD-prov-dm-20111215</span>, with type <span class="name">document</span> and version number <span class="name">2</span>. The attribute <span class="name">ex:version</span> is application specific, whereas the attribute <span
-class="name">type</span> (see <a href="#term-attribute-type">Section 5.7.4.4</a>) is reserved in the <a title="prov-namespace">PROV namespace</a>.
+states the existence of an entity, denoted by identifier <span class="name">tr:WD-prov-dm-20111215</span>, with type <span class="name">document</span> and version number <span class="name">2</span>. The attribute <span class="name">ex:version</span> is application specific, whereas the attribute <span class="name">type</span> (see <a href="#term-attribute-type">Section 5.7.4.4</a>) is reserved in the <a title="prov-namespace" href="#dfn-prov-namespace" class="internalDFN">PROV namespace</a>.
</div>
@@ -2021,28 +2077,25 @@
<section id="term-Activity">
-<h3>Activity</h3>
-
-<div class="glossary-ref" data-ref="glossary-activity"></div>
-
-<p><div class="attributes" id="attributes-activity"> An <dfn title="dfn-Activity" id="dfn-activity">activity</dfn><span class="withPn">, written <span class="pnExpression" id="pn-activity">activity(id, st, et, [attr1=val1, ...])</span> in PROV-N,</span> has:
+<h4><span class="secno">5.1.2 </span>Activity</h4>
+
+<div class="glossary-ref"> An <dfn id="concept-activity" title="Activity" class="internalDFN">activity</dfn><sup><a class="internalDFN" href="#concept-activity"><span class="diamond"> ◊</span></a></sup> 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. </div>
+
+<p></p><div class="attributes" id="attributes-activity"> An <dfn title="dfn-Activity" id="dfn-activity" class="internalDFN">activity</dfn><sup><a class="internalDFN" href="#dfn-activity"><span class="diamond"> ◊</span></a></sup><span class="withPn">, written <span class="pnExpression" id="pn-activity">activity(id, st, et, [attr1=val1, ...])</span> in PROV-N,</span> has:
<ul>
-<li><span class='attribute' id="activity.id">id</span>: an identifier for an activity;</li>
-<li><span class='attribute' id="activity.startTime">startTime</span>: an OPTIONAL time (<span class="name">st</span>) for the start of the activity;</li>
-<li><span class='attribute' id="activity.endTime">endTime</span>: an OPTIONAL time (<span class="name">et</span>) for the end of the activity;</li>
-<li><span class='attribute' id="activity.attributes">attributes</span>: an OPTIONAL set of attribute-value pairs ((<span class="name">attr1</span>, <span class="name">val1</span>), ...) representing additional information about this activity.</li>
+<li><span class="attribute" id="activity.id">id</span>: an identifier for an activity;</li>
+<li><span class="attribute" id="activity.startTime">startTime</span>: an <em class="rfc2119" title="OPTIONAL">OPTIONAL</em> time (<span class="name">st</span>) for the start of the activity;</li>
+<li><span class="attribute" id="activity.endTime">endTime</span>: an <em class="rfc2119" title="OPTIONAL">OPTIONAL</em> time (<span class="name">et</span>) for the end of the activity;</li>
+<li><span class="attribute" id="activity.attributes">attributes</span>: an <em class="rfc2119" title="OPTIONAL">OPTIONAL</em> set of attribute-value pairs ((<span class="name">attr1</span>, <span class="name">val1</span>), ...) representing additional information about this activity.</li>
</ul></div>
-<div class="anexample" id="anexample-activity">
+<div class="anexample" id="anexample-activity"><div class="anexampleTitle">Example 18<sup><a class="internalDFN" href="#anexample-activity"><span class="diamond"> ◊</span></a></sup></div>
<p>
The following expression</p>
-<pre class="codeexample">
-activity(a1, 2011-11-16T16:05:00, 2011-11-16T16:06:00,
+<pre class="codeexample">activity(a1, 2011-11-16T16:05:00, 2011-11-16T16:06:00,
[ ex:host="server.example.org", prov:type='ex:edit' ])
</pre>
-<p>states the existence of an activity with identifier <span class="name">a1</span>, start time <span class="name">2011-11-16T16:05:00</span>, and end time <span
-class="name">2011-11-16T16:06:00</span>, running on host <span class="name">server.example.org</span>, and of type <span class="name">edit</span>. The attribute <span class="name">host</span> is application specific (declared in some namespace with prefix <span class="name">ex</span>). The attribute <span
-class="name">type</span> is a reserved attribute of PROV-DM, allowing for sub-typing to be expressed (see <a class="section-ref" href="#term-attribute-type"><span>TBD</span></a>).</p>
+<p>states the existence of an activity with identifier <span class="name">a1</span>, start time <span class="name">2011-11-16T16:05:00</span>, and end time <span class="name">2011-11-16T16:06:00</span>, running on host <span class="name">server.example.org</span>, and of type <span class="name">edit</span>. The attribute <span class="name">host</span> is application specific (declared in some namespace with prefix <span class="name">ex</span>). The attribute <span class="name">type</span> is a reserved attribute of PROV-DM, allowing for sub-typing to be expressed (see <a class="section-ref" href="#term-attribute-type"><span>Section 5.7.2.4</span></a>).</p>
</div>
@@ -2050,7 +2103,7 @@
<p>Further considerations:</p>
<ul>
<li>An activity is not an entity. This distinction is similar to the distinction between
-'continuant' and 'occurrent' in logic [[Logic]].
+'continuant' and 'occurrent' in logic [<cite><a class="bibref" href="#bib-Logic">Logic</a></cite>].
</li>
</ul>
@@ -2058,50 +2111,47 @@
</section>
<section id="term-Generation">
-<h4>Generation</h4>
-
-<div class="glossary-ref" data-ref="glossary-generation"></div>
+<h4><span class="secno">5.1.3 </span>Generation</h4>
+
+<div class="glossary-ref"> <dfn id="concept-generation" class="internalDFN">Generation</dfn><sup><a class="internalDFN" href="#concept-generation"><span class="diamond"> ◊</span></a></sup> 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. </div>
<p>Given that a generation is the completion of production of an entity,
it is instantaneous.</p>
<p>
-<div class="attributes" id="attributes-generation"><dfn title="wasGeneratedBy">Generation</dfn><span class="withPn">, written <span class="pnExpression">wasGeneratedBy(id; e, a, t, attrs)</span> in PROV-N,</span> has:
+</p><div class="attributes" id="attributes-generation"><dfn title="wasGeneratedBy" id="dfn-wasgeneratedby" class="internalDFN">Generation</dfn><sup><a class="internalDFN" href="#dfn-wasgeneratedby"><span class="diamond"> ◊</span></a></sup><span class="withPn">, written <span class="pnExpression">wasGeneratedBy(id; e, a, t, attrs)</span> in PROV-N,</span> has:
<ul>
-<li><span class='attribute' id="generation.id">id</span>: an OPTIONAL identifier for a generation;</li>
-<li><span class='attribute' id="generation.entity">entity</span>: an identifier (<span class="name">e</span>) for a created entity; </li>
-<li><span class='attribute' id="generation.activity">activity</span>: an OPTIONAL identifier (<span class="name">a</span>) for the activity that creates the entity;</li>
-
-<li><span class='attribute' id="generation.time">time</span>: an OPTIONAL "generation time" (<span class="name">t</span>), the time at which the entity was completely created;</li>
-
-<li><span class='attribute' id="generation.attributes">attributes</span>: an OPTIONAL set (<span class="name">attrs</span>) of attribute-value pairs representing additional information about this generation.</li>
+<li><span class="attribute" id="generation.id">id</span>: an <em class="rfc2119" title="OPTIONAL">OPTIONAL</em> identifier for a generation;</li>
+<li><span class="attribute" id="generation.entity">entity</span>: an identifier (<span class="name">e</span>) for a created entity; </li>
+<li><span class="attribute" id="generation.activity">activity</span>: an <em class="rfc2119" title="OPTIONAL">OPTIONAL</em> identifier (<span class="name">a</span>) for the activity that creates the entity;</li>
+
+<li><span class="attribute" id="generation.time">time</span>: an <em class="rfc2119" title="OPTIONAL">OPTIONAL</em> "generation time" (<span class="name">t</span>), the time at which the entity was completely created;</li>
+
+<li><span class="attribute" id="generation.attributes">attributes</span>: an <em class="rfc2119" title="OPTIONAL">OPTIONAL</em> set (<span class="name">attrs</span>) of attribute-value pairs representing additional information about this generation.</li>
</ul></div>
-<p>While each of <a href="#generation.id"><span class='attribute'>id</span></a>, <a href="#generation.activity"><span class='attribute'>activity</span></a>, <a href="#generation.time"><span class='attribute'>time</span></a>, and <a href="#generation.attributes"><span class='attribute'>attributes</span></a> is OPTIONAL, at least one of them MUST be present.</p>
-
-
-
-
-
-<div class='anexample' id="anexample-generation1">
+<p>While each of <a href="#generation.id"><span class="attribute">id</span></a>, <a href="#generation.activity"><span class="attribute">activity</span></a>, <a href="#generation.time"><span class="attribute">time</span></a>, and <a href="#generation.attributes"><span class="attribute">attributes</span></a> is <em class="rfc2119" title="OPTIONAL">OPTIONAL</em>, at least one of them <em class="rfc2119" title="MUST">MUST</em> be present.</p>
+
+
+
+
+
+<div class="anexample" id="anexample-generation1"><div class="anexampleTitle">Example 19<sup><a class="internalDFN" href="#anexample-generation1"><span class="diamond"> ◊</span></a></sup></div>
<p>
The following expressions</p>
-<pre class="codeexample">
- wasGeneratedBy(e1, a1, 2001-10-26T21:32:52, [ ex:port="p1" ])
+<pre class="codeexample"> wasGeneratedBy(e1, a1, 2001-10-26T21:32:52, [ ex:port="p1" ])
wasGeneratedBy(e2, a1, 2001-10-26T10:00:00, [ ex:port="p2" ])
</pre>
-<p>state the existence of two generations (with respective times <span class="name">2001-10-26T21:32:52</span> and <span
-class="name">2001-10-26T10:00:00</span>), at which new entities, identified by <span class="name">e1</span> and <span class="name">e2</span>, were created by an
+<p>state the existence of two generations (with respective times <span class="name">2001-10-26T21:32:52</span> and <span class="name">2001-10-26T10:00:00</span>), at which new entities, identified by <span class="name">e1</span> and <span class="name">e2</span>, were created by an
activity, identified by <span class="name">a1</span>.
The first one was available on port <span class="name">p1</span>, whereas the other was available on port <span class="name">p2</span>. The semantics of <span class="name">port</span> are application specific.
</p>
</div>
-<div class='anexample' id="anexample-generation2">
+<div class="anexample" id="anexample-generation2"><div class="anexampleTitle">Example 20<sup><a class="internalDFN" href="#anexample-generation2"><span class="diamond"> ◊</span></a></sup></div>
<p>
In some cases, we may want to record the time at which an entity was generated without having to specify the activity that generated it. To support this requirement, the activity element in generation is optional. Hence, the following expression indicates the time at which an entity is generated, without naming the activity that did it.</p>
-<pre class="codeexample">
- wasGeneratedBy(e, -, 2001-10-26T21:32:52)
+<pre class="codeexample"> wasGeneratedBy(e, -, 2001-10-26T21:32:52)
</pre>
</div>
@@ -2110,40 +2160,37 @@
<section id="term-Usage">
-<h3>Usage</h3>
-
-<p><span class="glossary-ref" data-ref="glossary-usage"></span> (Note: This definition is formulated for a given usage; it is permitted for an activity to have used a same entity multiple times.)</p>
+<h4><span class="secno">5.1.4 </span>Usage</h4>
+
+<p><span class="glossary-ref"> <dfn id="concept-usage" class="internalDFN">Usage</dfn><sup><a class="internalDFN" href="#concept-usage"><span class="diamond"> ◊</span></a></sup> 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> (Note: This definition is formulated for a given usage; it is permitted for an activity to have used a same entity multiple times.)</p>
<p>Given that a usage is the beginning of utilizing an entity, it is
instantaneous.</p>
-<p><div class="attributes" id="attributes-usage"><dfn title="used">Usage</dfn><span class="withPn">, written <span class="pnExpression">used(id; a, e, t, attrs)</span> in PROV-N,</span> has:
+<p></p><div class="attributes" id="attributes-usage"><dfn title="used" id="dfn-used" class="internalDFN">Usage</dfn><sup><a class="internalDFN" href="#dfn-used"><span class="diamond"> ◊</span></a></sup><span class="withPn">, written <span class="pnExpression">used(id; a, e, t, attrs)</span> in PROV-N,</span> has:
<ul>
-<li><span class='attribute' id="usage.id">id</span>: an OPTIONAL identifier for a usage;</li>
-<li><span class='attribute' id="usage.activity">activity</span>: an identifier (<span class="name">a</span>) for the activity that used an entity;</li>
-<li><span class='attribute' id="usage.entity">entity</span>: an OPTIONAL identifier (<span class="name">e</span>) for the entity being used;</li>
-<li><span class='attribute' id="usage.time">time</span>: an OPTIONAL "usage time" (<span class="name">t</span>), the time at which the entity started to be used;</li>
-<li><span class='attribute' id="usage.attributes">attributes</span>: an OPTIONAL set (<span class="name">attrs</span>) of attribute-value pairs representing additional information about this usage.</li>
+<li><span class="attribute" id="usage.id">id</span>: an <em class="rfc2119" title="OPTIONAL">OPTIONAL</em> identifier for a usage;</li>
+<li><span class="attribute" id="usage.activity">activity</span>: an identifier (<span class="name">a</span>) for the activity that used an entity;</li>
+<li><span class="attribute" id="usage.entity">entity</span>: an <em class="rfc2119" title="OPTIONAL">OPTIONAL</em> identifier (<span class="name">e</span>) for the entity being used;</li>
+<li><span class="attribute" id="usage.time">time</span>: an <em class="rfc2119" title="OPTIONAL">OPTIONAL</em> "usage time" (<span class="name">t</span>), the time at which the entity started to be used;</li>
+<li><span class="attribute" id="usage.attributes">attributes</span>: an <em class="rfc2119" title="OPTIONAL">OPTIONAL</em> set (<span class="name">attrs</span>) of attribute-value pairs representing additional information about this usage.</li>
</ul></div>
-<p>While each of <a href="#usage.id"><span class='attribute'>id</span></a>, <a href="#usage.entity"><span class='attribute'>entity</span></a>, <a href="#usage.time"><span class='attribute'>time</span></a>, and <a href="#usage.attributes"><span class='attribute'>attributes</span></a> is OPTIONAL, at least one of them MUST be present.</p>
+<p>While each of <a href="#usage.id"><span class="attribute">id</span></a>, <a href="#usage.entity"><span class="attribute">entity</span></a>, <a href="#usage.time"><span class="attribute">time</span></a>, and <a href="#usage.attributes"><span class="attribute">attributes</span></a> is <em class="rfc2119" title="OPTIONAL">OPTIONAL</em>, at least one of them <em class="rfc2119" title="MUST">MUST</em> be present.</p>
<p>
-A reference to a given entity MAY appear in multiple usages that share
+A reference to a given entity <em class="rfc2119" title="MAY">MAY</em> appear in multiple usages that share
a given activity identifier.
</p>
-<div class='anexample' id="anexample-usage">
+<div class="anexample" id="anexample-usage"><div class="anexampleTitle">Example 21<sup><a class="internalDFN" href="#anexample-usage"><span class="diamond"> ◊</span></a></sup></div>
<p>The following usages</p>
-<pre class="codeexample">
- used(a1, e1, 2011-11-16T16:00:00, [ ex:parameter="p1" ])
+<pre class="codeexample"> used(a1, e1, 2011-11-16T16:00:00, [ ex:parameter="p1" ])
used(a1, e2, 2011-11-16T16:00:01, [ ex:parameter="p2" ])
</pre>
-<p>state that the activity identified by <span class="name">a1</span> used two entities identified by <span
-class="name">e1</span> and <span class="name">e2</span>, at times <span class="name">2011-11-16T16:00:00</span> and <span class="name">2011-11-16T16:00:01</span>, respectively; the first
-one was found as the value of parameter <span class="name">p1</span>, whereas the second was found as value of parameter <span class="name">p2</span>. The semantics of <span
-class="name">parameter</span> is application specific.</p>
+<p>state that the activity identified by <span class="name">a1</span> used two entities identified by <span class="name">e1</span> and <span class="name">e2</span>, at times <span class="name">2011-11-16T16:00:00</span> and <span class="name">2011-11-16T16:00:01</span>, respectively; the first
+one was found as the value of parameter <span class="name">p1</span>, whereas the second was found as value of parameter <span class="name">p2</span>. The semantics of <span class="name">parameter</span> is application specific.</p>
</div>
@@ -2154,9 +2201,9 @@
</section>
<section id="term-Communication">
-<h3>Communication</h3>
-
-<div class="glossary-ref" data-ref="glossary-communication"></div>
+<h4><span class="secno">5.1.5 </span>Communication</h4>
+
+<div class="glossary-ref"> <dfn id="concept-communication" class="internalDFN">Communication</dfn><sup><a class="internalDFN" href="#concept-communication"><span class="diamond"> ◊</span></a></sup> is the exchange of some unspecified entity by two activities, one activity using some entity generated by the other. </div>
<p>A communication implies that activity <span class="name">a2</span> is dependent on another <span class="name">a1</span>, by way of some unspecified entity that is generated by <span class="name">a1</span> and used by <span class="name">a2</span>.</p>
@@ -2164,24 +2211,23 @@
-<p><div class="attributes" id="attributes-wasInformedBy">
-A <dfn title="wasInformedBy">communication</dfn><span class="withPn">, written as
+<p></p><div class="attributes" id="attributes-wasInformedBy">
+A <dfn title="wasInformedBy" id="dfn-wasinformedby" class="internalDFN">communication</dfn><sup><a class="internalDFN" href="#dfn-wasinformedby"><span class="diamond"> ◊</span></a></sup><span class="withPn">, written as
<span class="pnExpression">wasInformedBy(id; a2, a1, attrs)</span> in PROV-N,</span> has:
<ul>
-<li><span class='attribute' id="communication.id">id</span>: an OPTIONAL identifier identifying the relation;</li>
-<li><span class='attribute' id="communication.informed">informed</span>: the identifier (<span class="name">a2</span>) of the informed activity;
-<li><span class='attribute' id="communication.informant">informant</span>: the identifier (<span class="name">a1</span>) of the informant activity;
-<li><span class='attribute' id="communication.attributes">attributes</span>: an OPTIONAL set (<span class="name">attrs</span>) of attribute-value pairs representing additional information about this communication.</li>
+<li><span class="attribute" id="communication.id">id</span>: an <em class="rfc2119" title="OPTIONAL">OPTIONAL</em> identifier identifying the relation;</li>
+<li><span class="attribute" id="communication.informed">informed</span>: the identifier (<span class="name">a2</span>) of the informed activity;
+</li><li><span class="attribute" id="communication.informant">informant</span>: the identifier (<span class="name">a1</span>) of the informant activity;
+</li><li><span class="attribute" id="communication.attributes">attributes</span>: an <em class="rfc2119" title="OPTIONAL">OPTIONAL</em> set (<span class="name">attrs</span>) of attribute-value pairs representing additional information about this communication.</li>
</ul>
</div>
-<div class="anexample" id="anexample-communication">
+<div class="anexample" id="anexample-communication"><div class="anexampleTitle">Example 22<sup><a class="internalDFN" href="#anexample-communication"><span class="diamond"> ◊</span></a></sup></div>
<p>
Consider two activities <span class="name">a1</span> and <span class="name">a2</span>, the former performed by a government agency, and the latter by a driver caught speeding.
-<pre class="codeexample">
-activity(a1, [ prov:type="traffic regulations enforcing" ])
+</p><pre class="codeexample">activity(a1, [ prov:type="traffic regulations enforcing" ])
activity(a2, [ prov:type="fine paying" ])
wasInformedBy(a2, a1)
</pre>
@@ -2190,57 +2236,52 @@
</section>
<section id="term-Start">
-<h4>Start</h4>
-
-<div class="glossary-ref" data-ref="glossary-start"></div>
+<h4><span class="secno">5.1.6 </span>Start</h4>
+
+<div class="glossary-ref"> <dfn id="concept-start" class="internalDFN">Start</dfn><sup><a class="internalDFN" href="#concept-start"><span class="diamond"> ◊</span></a></sup> is when an activity is deemed to have been started by an entity, known as <dfn id="concept-start-trigger" title="start trigger" class="internalDFN">trigger</dfn><sup><a class="internalDFN" href="#concept-start-trigger"><span class="diamond"> ◊</span></a></sup>. 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 <dfn id="concept-start-starter" class="internalDFN">starter</dfn><sup><a class="internalDFN" href="#concept-start-starter"><span class="diamond"> ◊</span></a></sup>, that generated the trigger. </div>
<p>Given that a start is when an activity is deemed to have started, it
is instantaneous.</p>
-<p><div class="attributes" id="attributes-start">An activity <dfn title="wasStartedBy">start</dfn><span class="withPn">, written <span class="pnExpression">wasStartedBy(id; a2, e, a1, t, attrs)</span> in PROV-N,</span> has:
+<p></p><div class="attributes" id="attributes-start">An activity <dfn title="wasStartedBy" id="dfn-wasstartedby" class="internalDFN">start</dfn><sup><a class="internalDFN" href="#dfn-wasstartedby"><span class="diamond"> ◊</span></a></sup><span class="withPn">, written <span class="pnExpression">wasStartedBy(id; a2, e, a1, t, attrs)</span> in PROV-N,</span> has:
<ul>
-<li><span class='attribute' id="start.id">id</span>: an OPTIONAL identifier for the activity start;</li>
-<li><span class='attribute' id="start.activity">activity</span>: an identifier (<span class="name">a2</span>) for the started activity;</li>
-<li><span class='attribute' id="start.trigger">trigger</span>: an OPTIONAL identifier (<span class="name">e</span>) for the entity triggering the activity;</li>
-<li><span class='attribute' id="start.starter">starter</span>: an OPTIONAL identifier (<span class="name">a1</span>) for the activity that generated the (possibly unspecified) entity (<span class="name">e</span>);</li>
-<li><span class='attribute' id="start.time">time</span>: the OPTIONAL time (<span class="name">t</span>) at which the activity was started; </li>
-<li><span class='attribute' id="start.attributes">attributes</span>: an OPTIONAL set (<span class="name">attrs</span>) of attribute-value pairs representing additional information about this activity start.
-</ul>
+<li><span class="attribute" id="start.id">id</span>: an <em class="rfc2119" title="OPTIONAL">OPTIONAL</em> identifier for the activity start;</li>
+<li><span class="attribute" id="start.activity">activity</span>: an identifier (<span class="name">a2</span>) for the started activity;</li>
+<li><span class="attribute" id="start.trigger">trigger</span>: an <em class="rfc2119" title="OPTIONAL">OPTIONAL</em> identifier (<span class="name">e</span>) for the entity triggering the activity;</li>
+<li><span class="attribute" id="start.starter">starter</span>: an <em class="rfc2119" title="OPTIONAL">OPTIONAL</em> identifier (<span class="name">a1</span>) for the activity that generated the (possibly unspecified) entity (<span class="name">e</span>);</li>
+<li><span class="attribute" id="start.time">time</span>: the <em class="rfc2119" title="OPTIONAL">OPTIONAL</em> time (<span class="name">t</span>) at which the activity was started; </li>
+<li><span class="attribute" id="start.attributes">attributes</span>: an <em class="rfc2119" title="OPTIONAL">OPTIONAL</em> set (<span class="name">attrs</span>) of attribute-value pairs representing additional information about this activity start.
+</li></ul>
</div>
-<p>While each of <a href="#start.id"><span class='attribute'>id</span></a>, <a href="#start.trigger"><span class='attribute'>trigger</span></a>, <a href="#start.starter"><span class='attribute'>starter</span></a>, <a href="#start.time"><span class='attribute'>time</span></a>, and <a href="#start.attributes"><span class='attribute'>attributes</span></a> is OPTIONAL, at least one of them MUST be present.</p>
-
-
-<div class="anexample" id="anexample-start1">
+<p>While each of <a href="#start.id"><span class="attribute">id</span></a>, <a href="#start.trigger"><span class="attribute">trigger</span></a>, <a href="#start.starter"><span class="attribute">starter</span></a>, <a href="#start.time"><span class="attribute">time</span></a>, and <a href="#start.attributes"><span class="attribute">attributes</span></a> is <em class="rfc2119" title="OPTIONAL">OPTIONAL</em>, at least one of them <em class="rfc2119" title="MUST">MUST</em> be present.</p>
+
+
+<div class="anexample" id="anexample-start1"><div class="anexampleTitle">Example 23<sup><a class="internalDFN" href="#anexample-start1"><span class="diamond"> ◊</span></a></sup></div>
<p>
The following example contains the description of an activity <span class="name">a1</span> (a discussion), which was started at a specific time, and was triggered by an email message <span class="name">e1</span>.</p>
-<pre class="codeexample">
-entity(e1, [ prov:type="email message"] )
+<pre class="codeexample">entity(e1, [ prov:type="email message"] )
activity(a1, [ prov:type="Discuss" ])
wasStartedBy(a1, e1, -, 2011-11-16T16:05:00)
</pre>
Furthermore, if the message is also an input to the activity, this can be described as follows:
-<pre class="codeexample">
-used(a1, e1, -)
+<pre class="codeexample">used(a1, e1, -)
</pre>
<p>Alternatively, one can also describe the activity that generated the email message.</p>
-<pre class="codeexample">
-activity(a0, [ prov:type="Write" ])
+<pre class="codeexample">activity(a0, [ prov:type="Write" ])
wasGeneratedBy(e1, a0)
wasStartedBy(a1, e1, a0, 2011-11-16T16:05:00)
</pre>
<p>If <span class="name">e1</span> is not known, it would also be valid to write:
-<pre class="codeexample">
-wasStartedBy(a1, -, a0, 2011-11-16T16:05:00)
+</p><pre class="codeexample">wasStartedBy(a1, -, a0, 2011-11-16T16:05:00)
</pre>
</div>
-<div class="anexample" id="anexample-start2">
+<div class="anexample" id="anexample-start2"><div class="anexampleTitle">Example 24<sup><a class="internalDFN" href="#anexample-start2"><span class="diamond"> ◊</span></a></sup></div>
<p>
In the following example, a race is started by a bang, and responsibility for this trigger is attributed to an agent
<span class="name">ex:Bob</span>.
-<pre class="codeexample">
-activity(ex:foot_race)
+</p><pre class="codeexample">activity(ex:foot_race)
entity(ex:bang)
wasStartedBy(ex:foot_race, ex:bang, -, 2012-03-09T08:05:08-05:00)
agent(ex:Bob)
@@ -2248,7 +2289,7 @@
</pre>
</div>
-<div class="anexample" id="anexample-start3">
+<div class="anexample" id="anexample-start3"><div class="anexampleTitle">Example 25<sup><a class="internalDFN" href="#anexample-start3"><span class="diamond"> ◊</span></a></sup></div>
<p>
In this example, filling the fuel tank was started as a consequence of
observing low fuel. The trigger entity is unspecified, it could
@@ -2256,8 +2297,7 @@
indicator needle position, or the engine not running properly.
-<pre class="codeexample" id="anexample-start4">
-activity(ex:filling-fuel)
+</p><pre class="codeexample" id="anexample-start4">activity(ex:filling-fuel)
activity(ex:observing-low-fuel)
agent(ex:driver, [ prov:type='prov:Person' )
@@ -2273,32 +2313,31 @@
</section>
<section id="term-End">
-<h4>End</h4>
-
-<div class="glossary-ref" data-ref="glossary-end"></div>
+<h4><span class="secno">5.1.7 </span>End</h4>
+
+<div class="glossary-ref"> <dfn id="concept-end" class="internalDFN">End</dfn><sup><a class="internalDFN" href="#concept-end"><span class="diamond"> ◊</span></a></sup> is when an activity is deemed to have been ended by an entity, known as <dfn id="concept-end-trigger" title="end trigger" class="internalDFN">trigger</dfn><sup><a class="internalDFN" href="#concept-end-trigger"><span class="diamond"> ◊</span></a></sup>. 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 <dfn id="concept-end-ender" class="internalDFN">ender</dfn><sup><a class="internalDFN" href="#concept-end-ender"><span class="diamond"> ◊</span></a></sup> that generated the trigger. </div>
<p>Given that an end is when an activity is deemed to have ended, it is
instantaneous.</p>
-<p><div class="attributes" id="attributes-end">An activity <dfn title="wasEndedBy">end</dfn><span class="withAsn">, written <span class="pnExpression">wasEndedBy(id; a2, e, a1, t, attrs)</span> in PROV-N,</span> has:
+<p></p><div class="attributes" id="attributes-end">An activity <dfn title="wasEndedBy" id="dfn-wasendedby" class="internalDFN">end</dfn><sup><a class="internalDFN" href="#dfn-wasendedby"><span class="diamond"> ◊</span></a></sup><span class="withAsn">, written <span class="pnExpression">wasEndedBy(id; a2, e, a1, t, attrs)</span> in PROV-N,</span> has:
<ul>
-<li><span class='attribute' id="end.id">id</span>: an OPTIONAL identifier for the activity end;</li>
-<li><span class='attribute' id="end.activity">activity</span>: an identifier (<span class="name">a2</span>) for the ended activity;
-<li><span class='attribute' id="end.trigger">trigger</span>: an OPTIONAL identifier (<span class="name">e</span>) for the entity triggering the activity ending;
-<li><span class='attribute' id="end.ender">ender</span>: an OPTIONAL identifier (<span class="name">a1</span>) for the activity that generated the (possibly unspecified) entity (<span class="name">e</span>);</li>
-<li><span class='attribute' id="end.time">time</span>: the OPTIONAL time (<span class="name">t</span>) at which the activity was ended; </li>
-<li><span class='attribute' id="end.attributes">attributes</span>: an OPTIONAL set (<span class="name">attrs</span>) of attribute-value pairs representing additional information about this activity end.
-</ul>
+<li><span class="attribute" id="end.id">id</span>: an <em class="rfc2119" title="OPTIONAL">OPTIONAL</em> identifier for the activity end;</li>
+<li><span class="attribute" id="end.activity">activity</span>: an identifier (<span class="name">a2</span>) for the ended activity;
+</li><li><span class="attribute" id="end.trigger">trigger</span>: an <em class="rfc2119" title="OPTIONAL">OPTIONAL</em> identifier (<span class="name">e</span>) for the entity triggering the activity ending;
+</li><li><span class="attribute" id="end.ender">ender</span>: an <em class="rfc2119" title="OPTIONAL">OPTIONAL</em> identifier (<span class="name">a1</span>) for the activity that generated the (possibly unspecified) entity (<span class="name">e</span>);</li>
+<li><span class="attribute" id="end.time">time</span>: the <em class="rfc2119" title="OPTIONAL">OPTIONAL</em> time (<span class="name">t</span>) at which the activity was ended; </li>
+<li><span class="attribute" id="end.attributes">attributes</span>: an <em class="rfc2119" title="OPTIONAL">OPTIONAL</em> set (<span class="name">attrs</span>) of attribute-value pairs representing additional information about this activity end.
+</li></ul>
</div>
-<p>While each of <a href="#end.id"><span class='attribute'>id</span></a>, <a href="#end.trigger"><span class='attribute'>trigger</span></a>, <a href="#end.ender"><span class='attribute'>ender</span></a>, <a href="#end.time"><span class='attribute'>time</span></a>, and <a href="#end.attributes"><span class='attribute'>attributes</span></a> is OPTIONAL, at least one of them MUST be present.</p>
-
-
-<div class="anexample" id="anexample-end">
+<p>While each of <a href="#end.id"><span class="attribute">id</span></a>, <a href="#end.trigger"><span class="attribute">trigger</span></a>, <a href="#end.ender"><span class="attribute">ender</span></a>, <a href="#end.time"><span class="attribute">time</span></a>, and <a href="#end.attributes"><span class="attribute">attributes</span></a> is <em class="rfc2119" title="OPTIONAL">OPTIONAL</em>, at least one of them <em class="rfc2119" title="MUST">MUST</em> be present.</p>
+
+
+<div class="anexample" id="anexample-end"><div class="anexampleTitle">Example 26<sup><a class="internalDFN" href="#anexample-end"><span class="diamond"> ◊</span></a></sup></div>
<p>
The following example is a description of an activity <span class="name">a1</span> (editing) that was ended following an approval document <span class="name">e1</span>.</p>
-<pre class="codeexample">
-entity(e1, [ prov:type="approval document" ])
+<pre class="codeexample">entity(e1, [ prov:type="approval document" ])
activity(a1, [ prov:type="Editing" ])
wasEndedBy(a1, e1, -, -)
</pre>
@@ -2306,10 +2345,10 @@
</section>
<section id="term-Invalidation">
-<h4>Invalidation</h4>
-
-
-<div class="glossary-ref" data-ref="glossary-invalidation"></div>
+<h4><span class="secno">5.1.8 </span>Invalidation</h4>
+
+
+<div class="glossary-ref"> <dfn id="concept-invalidation" class="internalDFN">Invalidation</dfn><sup><a class="internalDFN" href="#concept-invalidation"><span class="diamond"> ◊</span></a></sup> 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.</div>
<p>Given that an invalidation is the start of destruction, cessation, or
expiry, it is instantaneous.</p>
@@ -2319,11 +2358,11 @@
An entity's lifetime can end for different reasons:</p>
<ul>
<li> an entity was destroyed: e.g. a painting was destroyed by fire; a Web page is taken out of a site;
-<li> an entity was consumed: e.g. Bob ate all his soup, Alice ran out of gas when driving to work;
-<li> an entity expires: e.g. a "buy one beer, get one free" offer is valid during happy hour (7-8pm);
-<li> an entity is time limited: e.g. the BBC news site on April 3rd, 2012;
-<li> an entity attribute is changing: e.g. the traffic light changed from green to red.
-</ul>
+</li><li> an entity was consumed: e.g. Bob ate all his soup, Alice ran out of gas when driving to work;
+</li><li> an entity expires: e.g. a "buy one beer, get one free" offer is valid during happy hour (7-8pm);
+</li><li> an entity is time limited: e.g. the BBC news site on April 3rd, 2012;
+</li><li> an entity attribute is changing: e.g. the traffic light changed from green to red.
+</li></ul>
<p>In the first two cases, the entity has physically disappeared after its termination: there is no more soup, or painting. In the third case, there may be an "offer voucher" that still exists, but it is no longer valid; likewise, on April 4th, the BBC news site still exists but it is not the same entity as BBC news Web site on April 3rd; or the
green traffic light (an entity with a fixed aspect green light) became the
red traffic light (another entity with a fixed aspect red light).
@@ -2332,26 +2371,25 @@
<p>
-<div class="attributes" id="attributes-invalidation"><dfn title="wasInvalidatedBy">Invalidation</dfn><span class="withPn">, written <span class="pnExpression">wasInvalidatedBy(id; e, a, t, attrs)</span> in PROV-N,</span> has:
+</p><div class="attributes" id="attributes-invalidation"><dfn title="wasInvalidatedBy" id="dfn-wasinvalidatedby" class="internalDFN">Invalidation</dfn><sup><a class="internalDFN" href="#dfn-wasinvalidatedby"><span class="diamond"> ◊</span></a></sup><span class="withPn">, written <span class="pnExpression">wasInvalidatedBy(id; e, a, t, attrs)</span> in PROV-N,</span> has:
<ul>
-<li><span class='attribute' id="invalidation.id">id</span>: an OPTIONAL identifier for a invalidation;</li>
-<li><span class='attribute' id="invalidation.entity">entity</span>: an identifier for the invalidated entity; </li>
-<li><span class='attribute' id="invalidation.activity">activity</span>: an OPTIONAL identifier for the activity that invalidated the entity;</li>
-
-<li><span class='attribute' id="invalidation.time">time</span>: an OPTIONAL "invalidation time", the time at which the entity began to be invalidated;</li>
-
-<li><span class='attribute' id="invalidation.attributes">attributes</span>: an OPTIONAL set of attribute-value pairs representing additional information about this invalidation.</li>
+<li><span class="attribute" id="invalidation.id">id</span>: an <em class="rfc2119" title="OPTIONAL">OPTIONAL</em> identifier for a invalidation;</li>
+<li><span class="attribute" id="invalidation.entity">entity</span>: an identifier for the invalidated entity; </li>
+<li><span class="attribute" id="invalidation.activity">activity</span>: an <em class="rfc2119" title="OPTIONAL">OPTIONAL</em> identifier for the activity that invalidated the entity;</li>
+
+<li><span class="attribute" id="invalidation.time">time</span>: an <em class="rfc2119" title="OPTIONAL">OPTIONAL</em> "invalidation time", the time at which the entity began to be invalidated;</li>
+
+<li><span class="attribute" id="invalidation.attributes">attributes</span>: an <em class="rfc2119" title="OPTIONAL">OPTIONAL</em> set of attribute-value pairs representing additional information about this invalidation.</li>
</ul></div>
-<p>While each of <a href="#invalidation.id"><span class='attribute'>id</span></a>, <a href="#invalidation.activity"><span class='attribute'>activity</span></a>, <a href="#invalidation.time"><span class='attribute'>time</span></a>, and <a href="#invalidation.attributes"><span class='attribute'>attributes</span></a> is OPTIONAL, at least one of them MUST be present.</p>
-
-
-
-<div class="anexample" id="anexample-invalidation1">
+<p>While each of <a href="#invalidation.id"><span class="attribute">id</span></a>, <a href="#invalidation.activity"><span class="attribute">activity</span></a>, <a href="#invalidation.time"><span class="attribute">time</span></a>, and <a href="#invalidation.attributes"><span class="attribute">attributes</span></a> is <em class="rfc2119" title="OPTIONAL">OPTIONAL</em>, at least one of them <em class="rfc2119" title="MUST">MUST</em> be present.</p>
+
+
+
+<div class="anexample" id="anexample-invalidation1"><div class="anexampleTitle">Example 27<sup><a class="internalDFN" href="#anexample-invalidation1"><span class="diamond"> ◊</span></a></sup></div>
<p>
<em>The Painter</em>, a Picasso painting, is known to have been destroyed in a <a href="http://en.wikipedia.org/wiki/Lost_artworks#20th_century">plane accident</a>.
-<pre class="codeexample">
-entity(ex:The-Painter)
+</p><pre class="codeexample">entity(ex:The-Painter)
agent(ex:Picasso)
wasAttributedTo(ex:The-Painter, ex:Picasso)
activity(ex:crash)
@@ -2359,38 +2397,35 @@
</pre>
</div>
-<div class="anexample" id="anexample-invalidation2">
+<div class="anexample" id="anexample-invalidation2"><div class="anexampleTitle">Example 28<sup><a class="internalDFN" href="#anexample-invalidation2"><span class="diamond"> ◊</span></a></sup></div>
<p>
The BBC news home page on 2012-04-03 <span class="name">ex:bbcNews2012-04-03</span>
contained a reference to a given news item
<a href="http://www.bbc.co.uk/news/uk-17595024">bbc:news/uk-17595024</a>,
but the BBC news home page on the next day did not.
-<pre class="codeexample">
-entity(ex:bbcNews2012-04-03)
+</p><pre class="codeexample">entity(ex:bbcNews2012-04-03)
hadMember(ex:bbcNews2012-04-03, bbc:news/uk-17595024)
wasGeneratedBy (ex:bbcNews2012-04-03, -, 2012-04-03T00:00:01)
wasInvalidatedBy(ex:bbcNews2012-04-03, -, 2012-04-03T23:59:59)
</pre>
We refer to example
-<a href="#anexample-specialization" class="anexample-ref"><span>Example REF</span></a>
- for further descriptions of the BBC Web site, and to <a href="#term-membership">Section 5.6.2</a> for a description of the relation <a title="hadMember">hadMember</a>.
+<a href="#anexample-specialization" class="anexample-ref"><span>Example 43</span></a>
+ for further descriptions of the BBC Web site, and to <a href="#term-membership">Section 5.6.2</a> for a description of the relation <a title="hadMember" href="#dfn-hadmember" class="internalDFN">hadMember</a>.
</div>
-<div class="anexample" id="anexample-invalidation3">
+<div class="anexample" id="anexample-invalidation3"><div class="anexampleTitle">Example 29<sup><a class="internalDFN" href="#anexample-invalidation3"><span class="diamond"> ◊</span></a></sup></div>
<p>
In this example, the "buy one beer, get one free" offer expired at the end of the happy hour.</p>
-<pre class="codeexample">
-entity(buy_one_beer_get_one_free_offer_during_happy_hour)
+<pre class="codeexample">entity(buy_one_beer_get_one_free_offer_during_happy_hour)
wasAttributedTo(buy_one_beer_get_one_free_offer_during_happy_hour, proprietor)
wasInvalidatedBy(buy_one_beer_get_one_free_offer_during_happy_hour,
-,2012-03-10T18:00:00)
</pre>
<p>In contrast, in the following descriptions, Bob redeemed the offer 45 minutes before it expired, and got two beers.
</p>
-<pre class="codeexample">
-entity(buy_one_beer_get_one_free_offer_during_happy_hour)
+<pre class="codeexample">entity(buy_one_beer_get_one_free_offer_during_happy_hour)
wasAttributedTo(buy_one_beer_get_one_free_offer_during_happy_hour, proprietor)
activity(redeemOffer)
entity(twoBeers)
@@ -2418,35 +2453,35 @@
<section id="component2">
-<h3>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>Revision</a>), WasQuotedFrom (<a>Quotation</a>), and HasPrimarySource (<a>Primary Source</a>).
+<h3><span class="secno">5.2 </span>Component 2: Derivations</h3>
+
+
+
+<p>The second component of PROV-DM is concerned with: <a title="Derivation" href="#concept-derivation" class="internalDFN">derivations</a> of <a title="Entity" href="#concept-entity" class="internalDFN">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>).
<a href="#figure-component2">Figure 6</a> depicts the third component
with PROV core structures in the yellow area, including two classes
-(<a>Entity</a>, <a>Activity</a>) and binary association WasDerivedFrom
-(<a>Derivation</a>). PROV extended structures are found outside this
+(<a href="#concept-entity" class="internalDFN">Entity</a>, <a href="#concept-activity" class="internalDFN">Activity</a>) and binary association WasDerivedFrom
+(<a href="#concept-derivation" class="internalDFN">Derivation</a>). PROV extended structures are found outside this
area. UML association classes express expanded n-ary relations.
The subclasses are marked by the UML stereotype "prov:type" to indicate that the corresponding types are valid values for the attribute <a href="#term-attribute-type">prov:type</a>.
</p>
<div style="text-align: center;">
-<figure style="max-width: 95%; ">
-<img src="uml/component2.png" alt="derivation"/><br>
-<figcaption id="figure-component2">Derivation Component Overview (Informative)</figcaption> <!-- Figure 6 -->
-</figure>
+<span class="figure" id="fig-figure-6-derivation-component-overview-informative" style="max-width: 95%; ">
+<img src="uml/component2.png" alt="derivation"><br>
+<span class="figcaption" id="figure-component2">Figure 6<sup><a class="internalDFN" href="#figure-component2"><span class="diamond"> ◊:</span></a></sup> Derivation Component Overview (Informative)</span> <!-- Figure 6 -->
+</span>
</div>
<section id="term-Derivation">
-<h4>Derivation</h4>
-
-
-
-
-
-<div class="glossary-ref" data-ref="glossary-derivation"></div>
+<h4><span class="secno">5.2.1 </span>Derivation</h4>
+
+
+
+
+
+<div class="glossary-ref"> A <dfn id="concept-derivation" title="Derivation" class="internalDFN">derivation</dfn><sup><a class="internalDFN" href="#concept-derivation"><span class="diamond"> ◊</span></a></sup> 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.</div>
@@ -2456,24 +2491,23 @@
A derivation can be described at various levels of precision. In its simplest form, derivation relates two entities. Optionally, attributes can be added to represent further information about the derivation. If the derivation is the result of a single known activity, then this activity can also be optionally expressed. To provide a completely accurate description of the derivation, the generation and usage of the generated and used entities, respectively, can be provided, so as to make the derivation path, through usage, activity, and generation, explicit. Optional information such as activity, generation, and usage can be linked to derivations to aid analysis of provenance and to facilitate provenance-based reproducibility. </p>
-<p><div class="attributes" id="attributes-derivation">A <dfn title="wasDerivedFrom">derivation</dfn><span class="withPn">, written <span class="pnExpression" id="pn-wasDerivedFrom">wasDerivedFrom(id; e2, e1, a, g2, u1, attrs)</span> in PROV-N,</span> has:
+<p></p><div class="attributes" id="attributes-derivation">A <dfn title="wasDerivedFrom" id="dfn-wasderivedfrom" class="internalDFN">derivation</dfn><sup><a class="internalDFN" href="#dfn-wasderivedfrom"><span class="diamond"> ◊</span></a></sup><span class="withPn">, written <span class="pnExpression" id="pn-wasDerivedFrom">wasDerivedFrom(id; e2, e1, a, g2, u1, attrs)</span> in PROV-N,</span> has:
<ul>
-<li><span class='attribute' id="derivation.id">id</span>: an OPTIONAL identifier for a derivation;</li>
-<li><span class='attribute' id="derivation.generatedEntity">generatedEntity</span>: the identifier (<span class="name">e2</span>) of the entity generated by the derivation;</li>
-<li><span class='attribute' id="derivation.usedEntity">usedEntity</span>: the identifier (<span class="name">e1</span>) of the entity used by the derivation;</li>
-<li><span class='attribute' id="derivation.activity">activity</span>: an OPTIONAL identifier (<span class="name">a</span>) for the activity using and generating the above entities;</li>
-<li><span class='attribute' id="derivation.generation">generation</span>: an OPTIONAL identifier (<span class="name">g2</span>) for the generation involving the generated entity (<span class="name">e2</span>) and activity (<span class="name">a</span>);</li>
-<li><span class='attribute' id="derivation.usage">usage</span>: an OPTIONAL identifier (<span class="name">u1</span>) for the usage involving the used entity (<span class="name">e1</span>) and activity (<span class="name">a</span>);</li>
-<li><span class='attribute' id="derivation.attributes">attributes</span>: an OPTIONAL set (<span class="name">attrs</span>) of attribute-value pairs representing additional information about this derivation.</li>
+<li><span class="attribute" id="derivation.id">id</span>: an <em class="rfc2119" title="OPTIONAL">OPTIONAL</em> identifier for a derivation;</li>
+<li><span class="attribute" id="derivation.generatedEntity">generatedEntity</span>: the identifier (<span class="name">e2</span>) of the entity generated by the derivation;</li>
+<li><span class="attribute" id="derivation.usedEntity">usedEntity</span>: the identifier (<span class="name">e1</span>) of the entity used by the derivation;</li>
+<li><span class="attribute" id="derivation.activity">activity</span>: an <em class="rfc2119" title="OPTIONAL">OPTIONAL</em> identifier (<span class="name">a</span>) for the activity using and generating the above entities;</li>
+<li><span class="attribute" id="derivation.generation">generation</span>: an <em class="rfc2119" title="OPTIONAL">OPTIONAL</em> identifier (<span class="name">g2</span>) for the generation involving the generated entity (<span class="name">e2</span>) and activity (<span class="name">a</span>);</li>
+<li><span class="attribute" id="derivation.usage">usage</span>: an <em class="rfc2119" title="OPTIONAL">OPTIONAL</em> identifier (<span class="name">u1</span>) for the usage involving the used entity (<span class="name">e1</span>) and activity (<span class="name">a</span>);</li>
+<li><span class="attribute" id="derivation.attributes">attributes</span>: an <em class="rfc2119" title="OPTIONAL">OPTIONAL</em> set (<span class="name">attrs</span>) of attribute-value pairs representing additional information about this derivation.</li>
</ul>
</div>
-<div class="anexample" id="anexample-derivation">
+<div class="anexample" id="anexample-derivation"><div class="anexampleTitle">Example 30<sup><a class="internalDFN" href="#anexample-derivation"><span class="diamond"> ◊</span></a></sup></div>
<p>The following descriptions are about derivations between <span class="name">e2</span> and <span class="name">e1</span>, but no information is provided as to the identity of the activity (and usage and generation) underpinning the derivation. In the second line, a type attribute is also provided.</p>
-<pre class="codeexample">
-wasDerivedFrom(e2, e1)
+<pre class="codeexample">wasDerivedFrom(e2, e1)
wasDerivedFrom(e2, e1, [ prov:type="physical transform" ])
</pre>
<p>The following description expresses that activity <span class="name">a</span>,
@@ -2481,8 +2515,7 @@
derived the
entity <span class="name">e2</span> and generated it according to generation
<span class="name">g2</span>. It is followed by descriptions for generation <span class="name">g2</span> and usage <span class="name">u1</span>.</p>
-<pre class="codeexample">
-wasDerivedFrom(e2, e1, a, g2, u1)
+<pre class="codeexample">wasDerivedFrom(e2, e1, a, g2, u1)
wasGeneratedBy(g2; e2, a, -)
used(u1; a, e1, -)
</pre>
@@ -2495,30 +2528,29 @@
</section>
<section id="term-revision">
-<h3>Revision</h3>
-
-<p><span class="glossary-ref" data-ref="glossary-revision"></span></p>
+<h4><span class="secno">5.2.2 </span>Revision</h4>
+
+<p><span class="glossary-ref"> A <dfn id="concept-revision" title="Revision" class="internalDFN">revision</dfn><sup><a class="internalDFN" href="#concept-revision"><span class="diamond"> ◊</span></a></sup> is a derivation for which the resulting entity is a revised version of some original. </span></p>
<p>
The implication here is that
the resulting entity contains substantial content from the
original.
-A <dfn>revision</dfn> relation is a kind of <a title="Derivation">derivation</a> relation from a revised entity to a preceding entity.
+A <dfn id="dfn-revision" class="internalDFN">revision</dfn><sup><a class="internalDFN" href="#dfn-revision"><span class="diamond"> ◊</span></a></sup> relation is a kind of <a title="Derivation" href="#concept-derivation" class="internalDFN">derivation</a> relation from a revised entity to a preceding entity.
The type of a revision relation is denoted by:
-<dfn title="dfn-prov:revision" id="dfn-prov:revision"><span class="name">prov:Revision</span></dfn>.
+<dfn title="dfn-prov:revision" id="dfn-prov:revision" class="internalDFN"><span class="name">prov:Revision</span></dfn><sup><a class="internalDFN" href="#dfn-prov:revision"><span class="diamond"> ◊</span></a></sup>.
PROV defines no revision-specific attributes.
</p>
-<div class="anexample" id="anexample-revision">
+<div class="anexample" id="anexample-revision"><div class="anexampleTitle">Example 31<sup><a class="internalDFN" href="#anexample-revision"><span class="diamond"> ◊</span></a></sup></div>
<p>
Revisiting the example of <a href="#section-example-two">Section 4.2</a>,
we can now state that the report
<span class="name">tr:WD-prov-dm-20111215</span> was a revision of
the report <span class="name">tr:WD-prov-dm-20111018</span>.
-<pre class="codeexample">
-entity(tr:WD-prov-dm-20111215, [ prov:type='rec54:WD' ])
+</p><pre class="codeexample">entity(tr:WD-prov-dm-20111215, [ prov:type='rec54:WD' ])
entity(tr:WD-prov-dm-20111018, [ prov:type='rec54:WD' ])
wasDerivedFrom(tr:WD-prov-dm-20111215,
tr:WD-prov-dm-20111018,
@@ -2531,31 +2563,30 @@
</section> <!-- end revision -->
<section id="term-quotation">
-<h3>Quotation</h3>
+<h4><span class="secno">5.2.3 </span>Quotation</h4>
<p>
-<span class="glossary-ref" data-ref="glossary-quotation"></span>
+<span class="glossary-ref"> A <dfn id="concept-quotation" title="Quotation" class="internalDFN">quotation</dfn><sup><a class="internalDFN" href="#concept-quotation"><span class="diamond"> ◊</span></a></sup> 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>
-<p>A <dfn>quotation</dfn> relation
- is a kind of <a title="Derivation">derivation</a> relation, for which an entity was derived from a preceding entity by copying, or "quoting", some or all of it.
+<p>A <dfn id="dfn-quotation" class="internalDFN">quotation</dfn><sup><a class="internalDFN" href="#dfn-quotation"><span class="diamond"> ◊</span></a></sup> relation
+ is a kind of <a title="Derivation" href="#concept-derivation" class="internalDFN">derivation</a> relation, for which an entity was derived from a preceding entity by copying, or "quoting", some or all of it.
The type of a quotation relation is denoted by:
-<dfn title="dfn-prov:quotation" id="dfn-prov:quotation"><span class="name">prov:Quotation</span></dfn>.
+<dfn title="dfn-prov:quotation" id="dfn-prov:quotation" class="internalDFN"><span class="name">prov:Quotation</span></dfn><sup><a class="internalDFN" href="#dfn-prov:quotation"><span class="diamond"> ◊</span></a></sup>.
PROV defines no quotation-specific attributes.
</p>
-<div class="anexample" id="anexample-quotation">
+<div class="anexample" id="anexample-quotation"><div class="anexampleTitle">Example 32<sup><a class="internalDFN" href="#anexample-quotation"><span class="diamond"> ◊</span></a></sup></div>
<p>
The following paragraph is a quote from one of <a href="http://thinklinks.wordpress.com/2012/03/07/thoughts-from-the-dagstuhl-principles-of-provenance-workshop/">the author's blogs</a>.
-<blockquote id="bl-dagstuhl"><em>
+</p><blockquote id="bl-dagstuhl"><em>
"During the workshop, it became clear to me that the consensus based models (which are often graphical in nature) can not only be formalized but also be directly connected to these database focused formalizations. I just needed to get over the differences in syntax. This could imply that we could have nice way to trace provenance across systems and through databases and be able to understand the mathematical properties of this interconnection."</em>
</blockquote>
<p>If <a href="http://thinklinks.wordpress.com/2012/03/07/thoughts-from-the-dagstuhl-principles-of-provenance-workshop/"><span class="name">wp:thoughts-from-the-dagstuhl-principles-of-provenance-workshop/</span></a> denotes the original blog by agent <span class="name">ex:Paul</span>, and
<a href="#bl-dagstuhl"><span class="name">dm:bl-dagstuhl</span></a> denotes the above paragraph, then the following descriptions express that the above paragraph was copied by agent <span class="name">ex:Luc</span> from a part of the blog, attributed to the agent <span class="name">ex:Paul</span>.</p>
-<pre class="codeexample">
-entity(wp:thoughts-from-the-dagstuhl-principles-of-provenance-workshop/)
+<pre class="codeexample">entity(wp:thoughts-from-the-dagstuhl-principles-of-provenance-workshop/)
entity(dm:bl-dagstuhl)
agent(ex:Luc)
agent(ex:Paul)
@@ -2573,10 +2604,10 @@
<section id="term-primary-source">
-<h3>Primary Source</h3>
+<h4><span class="secno">5.2.4 </span>Primary Source</h4>
<p>
-<span class="glossary-ref" data-ref="glossary-primary-source"></span>
+<span class="glossary-ref"> A <dfn id="concept-primary-source" title="Primary Source" class="internalDFN">primary source</dfn><sup><a class="internalDFN" href="#concept-primary-source"><span class="diamond"> ◊</span></a></sup> 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>
<p>Because of the directness
@@ -2587,21 +2618,21 @@
from which they were derived, so that their reliability can be
investigated.</p>
-<p>It is also important to note that a given entity might be a primary source for one entity but not another. It the reason why Primary Source is defined as a relation as opposed to a subtype of Entity.</p>
-
-<p>A <dfn>primary source</dfn> relation is a kind of a <a title="Derivation">derivation</a> relation from
+<p>It is also important to note that a given entity might be a primary source for one entity but not another. It is the reason why Primary Source is defined as a relation as opposed to a subtype of Entity.</p>
+
+<p>A <dfn id="dfn-primary-source" class="internalDFN">primary source</dfn><sup><a class="internalDFN" href="#dfn-primary-source"><span class="diamond"> ◊</span></a></sup> relation is a kind of a <a title="Derivation" href="#concept-derivation" class="internalDFN">derivation</a> relation from
secondary materials to their primary sources. It is recognized that
the determination of primary sources can be up to interpretation, and
should be done according to conventions accepted within the
application's domain.
The type of a primary source relation is denoted by:
-<dfn title="dfn-prov:primary-source" id="dfn-prov:primary-source"><span class="name">prov:PrimarySource</span></dfn>.
+<dfn title="dfn-prov:primary-source" id="dfn-prov:primary-source" class="internalDFN"><span class="name">prov:PrimarySource</span></dfn><sup><a class="internalDFN" href="#dfn-prov:primary-source"><span class="diamond"> ◊</span></a></sup>.
PROV defines no attributes specific to primary source.
</p>
-<div class="anexample" id="anexample-primary-source1">
+<div class="anexample" id="anexample-primary-source1"><div class="anexampleTitle">Example 33<sup><a class="internalDFN" href="#anexample-primary-source1"><span class="diamond"> ◊</span></a></sup></div>
<p>
Let us consider Charles Joseph Minard's flow map of Napoleon's March in
1812, which was published in 1869. Although the map is not a primary source,
@@ -2609,8 +2640,7 @@
to Napoleon's army during the Russian campaign. This primary source relation
can be encoded as follows.</p>
-<pre class="codeexample">
-entity(ex:la-campagne-de-Russie-1812-1813, [ prov:type="map" ])
+<pre class="codeexample">entity(ex:la-campagne-de-Russie-1812-1813, [ prov:type="map" ])
entity(ex:revue-d-Histoire-de-la-Pharmacie-t-XVIII, [ prov:type="journal" ])
wasDerivedFrom(ex:la-campagne-de-Russie-1812-1813,
ex:revue-d-Histoire-de-la-Pharmacie-t-XVIII,
@@ -2626,44 +2656,44 @@
</section>
<section id="component3">
-<h3>Component 3: Agents, Responsibility, and Influence</h3>
-
-<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.
- Core structures are displayed in the yellow area and include three classes and three binary associations. Outside the yellow area, extended structures comprise UML association classes to express expanded n-ary relations, and subclasses <a>Plan</a>, <a>Person</a>, <a title="software-agent">SofwareAgent</a>, and <a>Organization</a>. The subclasses are marked by the UML stereotype "prov:type" to indicate that that these are valid values for the attribute <a href="#term-attribute-type">prov:type</a>.
+<h3><span class="secno">5.3 </span>Component 3: Agents, Responsibility, and Influence</h3>
+
+<p>The third component of PROV-DM, depicted in <a href="#figure-component3">Figure 7</a>, is concerned with <a title="Agent" href="#concept-agent" class="internalDFN">agents</a> and the relations WasAttributedTo
+(<a href="#concept-attribution" class="internalDFN">Attribution</a>), WasAssociatedWith (<a href="#concept-association" class="internalDFN">Association</a>), and ActedOnBehalfOf (<a href="#concept-delegation" class="internalDFN">Delegation</a>), relating agents to entities, activities, and agents, respectively.
+ Core structures are displayed in the yellow area and include three classes and three binary associations. Outside the yellow area, extended structures comprise UML association classes to express expanded n-ary relations, and subclasses <a href="#concept-plan" class="internalDFN">Plan</a>, <a href="#concept-person" class="internalDFN">Person</a>, <a title="software-agent" href="#concept-software-agent" class="internalDFN">SoftwareAgent</a>, and <a title="software-organization" href="#concept-organization" class="internalDFN">Organization</a>. The subclasses are marked by the UML stereotype "prov:type" to indicate that that these are valid values for the attribute <a href="#term-attribute-type">prov:type</a>.
</p>
<div style="text-align: center;">
-<figure style="max-width: 95%; ">
-<img src="uml/component3.png" alt="agents and responsibilities"/><br>
-<figcaption id="figure-component3">Agents and Responsibility Overview (Informative)</figcaption> <!-- Figure 7 -->
-</figure>
+<span class="figure" id="fig-figure-7-agents-and-responsibility-overview-informative" style="max-width: 95%; ">
+<img src="uml/component3.png" alt="agents and responsibilities"><br>
+<span class="figcaption" id="figure-component3">Figure 7<sup><a class="internalDFN" href="#figure-component3"><span class="diamond"> ◊:</span></a></sup> Agents and Responsibility Overview (Informative)</span> <!-- Figure 7 -->
+</span>
</div>
-<p>Component 3 further defines a general notion of <a title="Influence">influence</a>, a relation implied by all relations defined so far. <a href="#figure-component3b">Figure 8</a> displays one new association class, generalizing previously introduced associations.</p>
+<p>Component 3 further defines a general notion of <a title="Influence" href="#concept-influence" class="internalDFN">influence</a>, a relation implied by all relations defined so far. <a href="#figure-component3b">Figure 8</a> displays one new association class, generalizing previously introduced associations.</p>
<div style="text-align: center;">
-<figure style="max-width: 95%; ">
-<img src="uml/Component3b.png" alt="Influence Overview"/><br>
-<figcaption id="figure-component3b">Influence Overview (Informative)</figcaption> <!-- Figure 8 -->
-</figure>
+<span class="figure" id="fig-figure-8-influence-overview-informative" style="max-width: 95%; ">
+<img src="uml/Component3b.png" alt="Influence Overview"><br>
+<span class="figcaption" id="figure-component3b">Figure 8<sup><a class="internalDFN" href="#figure-component3b"><span class="diamond"> ◊:</span></a></sup> Influence Overview (Informative)</span> <!-- Figure 8 -->
+</span>
</div>
<section id="term-agent">
-<h3>Agent</h3>
-
-<div class="glossary-ref" data-ref="glossary-agent"></div>
+<h4><span class="secno">5.3.1 </span>Agent</h4>
+
+<div class="glossary-ref"> An <dfn id="concept-agent" title="Agent" class="internalDFN">agent</dfn><sup><a class="internalDFN" href="#concept-agent"><span class="diamond"> ◊</span></a></sup> 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. </div>
<p>An agent may be a particular type of entity or activity. This means that the model can be
used to express provenance of the agents themselves. </p>
-<p><div class="attributes" id="attributes-agent">An <dfn title="dfn-agent" id="dfn-agent">agent</dfn><span class="withPn">, written <span class="pnExpression" id="pn-agent">agent(id, [attr1=val1, ...])</span> in PROV-N,</span> has:
+<p></p><div class="attributes" id="attributes-agent">An <dfn title="dfn-agent" id="dfn-agent" class="internalDFN">agent</dfn><sup><a class="internalDFN" href="#dfn-agent"><span class="diamond"> ◊</span></a></sup><span class="withPn">, written <span class="pnExpression" id="pn-agent">agent(id, [attr1=val1, ...])</span> in PROV-N,</span> has:
<ul>
-<li><span class='attribute' id="agent.id">id</span>: an identifier for an agent;</li>
-<li><span class='attribute' id="agent.attributes">attributes</span>: a set of attribute-value pairs ((<span class="name">attr1</span>, <span class="name">val1</span>), ...) representing additional information about this agent.
+<li><span class="attribute" id="agent.id">id</span>: an identifier for an agent;</li>
+<li><span class="attribute" id="agent.attributes">attributes</span>: a set of attribute-value pairs ((<span class="name">attr1</span>, <span class="name">val1</span>), ...) representing additional information about this agent.
</li>
</ul></div>
@@ -2675,19 +2705,19 @@
<ul>
<li><span class="name">SoftwareAgent</span>
-<p><span class="glossary-ref" data-ref="glossary-software-agent"></span> The type of a software agent is denoted by <dfn title="dfn-prov:softwareAgent" id="dfn-prov:softwareAgent"><span class="name">prov:SoftwareAgent</span></dfn>.</p>
-
-<p></li>
+<p><span class="glossary-ref"> A <dfn id="concept-software-agent" title="software-agent" class="internalDFN">software agent</dfn><sup><a class="internalDFN" href="#concept-software-agent"><span class="diamond"> ◊</span></a></sup> is running software. </span> The type of a software agent is denoted by <dfn title="dfn-prov:softwareAgent" id="dfn-prov:softwareAgent" class="internalDFN"><span class="name">prov:SoftwareAgent</span></dfn><sup><a class="internalDFN" href="#dfn-prov:softwareAgent"><span class="diamond"> ◊</span></a></sup>.</p>
+
+<p></p></li>
<li><span class="name">Organization</span>
-<p><span class="glossary-ref" data-ref="glossary-organization"></span> The type of an organization agent is denoted by <dfn title="dfn-prov:organization" id="dfn-prov:organization"><span class="name">prov:Organization</span></dfn>.</p>
-
-<p></li>
+<p><span class="glossary-ref"> An <dfn id="concept-organization" class="internalDFN">organization</dfn><sup><a class="internalDFN" href="#concept-organization"><span class="diamond"> ◊</span></a></sup> is a social or legal institution such as a company, society, etc. </span> The type of an organization agent is denoted by <dfn title="dfn-prov:organization" id="dfn-prov:organization" class="internalDFN"><span class="name">prov:Organization</span></dfn><sup><a class="internalDFN" href="#dfn-prov:organization"><span class="diamond"> ◊</span></a></sup>.</p>
+
+<p></p></li>
<li><span class="name">Person</span>
-<p><span class="glossary-ref" data-ref="glossary-person"></span> The type of a person agent is denoted by <dfn title="dfn-prov:person" id="dfn-prov:person"><span class="name">prov:Person</span></dfn>.</p>
+<p><span class="glossary-ref"> <dfn id="concept-person" title="Person" class="internalDFN">Person</dfn><sup><a class="internalDFN" href="#concept-person"><span class="diamond"> ◊</span></a></sup> agents are people. </span> The type of a person agent is denoted by <dfn title="dfn-prov:person" id="dfn-prov:person" class="internalDFN"><span class="name">prov:Person</span></dfn><sup><a class="internalDFN" href="#dfn-prov:person"><span class="diamond"> ◊</span></a></sup>.</p>
</li>
</ul>
<p>PROV defines no attributes specific to SoftwareAgent, Organization, and Person.</p>
@@ -2695,10 +2725,9 @@
-<div class="anexample">
+<div class="anexample" id="example_34"><div class="anexampleTitle">Example 34<sup><a class="internalDFN" href="#example_34"><span class="diamond"> ◊</span></a></sup></div>
<p>The following expression is about an agent identified by <span class="name">e1</span>, which is a person, named Alice, with employee number 1234.</p>
-<pre class="codeexample">
-agent(e1, [ex:employee="1234", ex:name="Alice", prov:type='prov:Person' ])
+<pre class="codeexample">agent(e1, [ex:employee="1234", ex:name="Alice", prov:type='prov:Person' ])
</pre>
<p>It is optional to specify the type of an agent. When present, it is expressed using the <span class="name">prov:type</span> attribute.</p>
</div>
@@ -2706,28 +2735,27 @@
</section>
<section id="term-attribution">
-<h3>Attribution</h3>
-
-<div class="glossary-ref" data-ref="glossary-attribution"></div>
+<h4><span class="secno">5.3.2 </span>Attribution</h4>
+
+<div class="glossary-ref"> <dfn id="concept-attribution" class="internalDFN">Attribution</dfn><sup><a class="internalDFN" href="#concept-attribution"><span class="diamond"> ◊</span></a></sup> is the ascribing of an entity to an agent. </div>
<p>When an entity <span class="name">e</span> is attributed to agent <span class="name">ag</span>, entity <span class="name">e</span> was generated by some unspecified activity that in turn was associated to agent <span class="name">ag</span>. Thus, this relation is useful when the activity is not known, or irrelevant.</p>
-<p><div class="attributes" id="attributes-attribution">An <dfn title="wasAttributedTo">attribution</dfn> relation<span class="withPn">, written <span class="pnExpression">wasAttributedTo(id; e, ag, attrs)</span> in PROV-N,</span> has:
+<p></p><div class="attributes" id="attributes-attribution">An <dfn title="wasAttributedTo" id="dfn-wasattributedto" class="internalDFN">attribution</dfn><sup><a class="internalDFN" href="#dfn-wasattributedto"><span class="diamond"> ◊</span></a></sup> relation<span class="withPn">, written <span class="pnExpression">wasAttributedTo(id; e, ag, attrs)</span> in PROV-N,</span> has:
<ul>
-<li><span class='attribute' id="attribution.id">id</span>: an OPTIONAL identifier for the relation;</li>
-<li><span class='attribute' id="attribution.entity">entity</span>: an entity identifier (<span class="name">e</span>);</li>
-<li><span class='attribute' id="attribution.agent">agent</span>: the identifier (<span class="name">ag</span>) of the agent whom the entity is ascribed to, and therefore bears some responsibility for its existence;</li>
-<li><span class='attribute' id="attribution.attributes">attributes</span>: an OPTIONAL set (<span class="name">attrs</span>) of attribute-value pairs representing additional information about this attribution.</li>
+<li><span class="attribute" id="attribution.id">id</span>: an <em class="rfc2119" title="OPTIONAL">OPTIONAL</em> identifier for the relation;</li>
+<li><span class="attribute" id="attribution.entity">entity</span>: an entity identifier (<span class="name">e</span>);</li>
+<li><span class="attribute" id="attribution.agent">agent</span>: the identifier (<span class="name">ag</span>) of the agent whom the entity is ascribed to, and therefore bears some responsibility for its existence;</li>
+<li><span class="attribute" id="attribution.attributes">attributes</span>: an <em class="rfc2119" title="OPTIONAL">OPTIONAL</em> set (<span class="name">attrs</span>) of attribute-value pairs representing additional information about this attribution.</li>
</ul>
</div>
-<div class="anexample" id="anexample-attribution">
+<div class="anexample" id="anexample-attribution"><div class="anexampleTitle">Example 35<sup><a class="internalDFN" href="#anexample-attribution"><span class="diamond"> ◊</span></a></sup></div>
<p>
Revisiting the example of
-<a class="section-ref" href="#section-example-one"><span>TBD</span></a>,
+<a class="section-ref" href="#section-example-one"><span>Section 4.1</span></a>,
we can ascribe <span class="name">tr:WD-prov-dm-20111215</span> to some agents without an explicit activity.
-<pre class="codeexample">
-agent(ex:Paolo, [ prov:type='prov:Person' ])
+</p><pre class="codeexample">agent(ex:Paolo, [ prov:type='prov:Person' ])
agent(ex:Simon, [ prov:type='prov:Person' ])
entity(tr:WD-prov-dm-20111215, [ prov:type='rec54:WD' ])
wasAttributedTo(tr:WD-prov-dm-20111215, ex:Paolo, [ prov:type="editorship" ])
@@ -2739,27 +2767,27 @@
<section id="term-Association">
-<h4>Association</h4>
-
-<div class="glossary-ref" data-ref="glossary-association"></div>
-
-
-
-<p><div class="attributes" id="attributes-activity-association">An <dfn title="wasAssociatedWith">association</dfn><span class="withPn">, written <span class="pnExpression">wasAssociatedWith(id; a, ag, pl, attrs)</span> in PROV-N,</span> has:
+<h4><span class="secno">5.3.3 </span>Association</h4>
+
+<div class="glossary-ref"> An activity <dfn id="concept-association" title="Association" class="internalDFN">association</dfn><sup><a class="internalDFN" href="#concept-association"><span class="diamond"> ◊</span></a></sup> 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. </div>
+
+
+
+<p></p><div class="attributes" id="attributes-activity-association">An <dfn title="wasAssociatedWith" id="dfn-wasassociatedwith" class="internalDFN">association</dfn><sup><a class="internalDFN" href="#dfn-wasassociatedwith"><span class="diamond"> ◊</span></a></sup><span class="withPn">, written <span class="pnExpression">wasAssociatedWith(id; a, ag, pl, attrs)</span> in PROV-N,</span> has:
<ul>
-<li><span class='attribute' id="association.id">id</span>: an OPTIONAL identifier for the association between an activity and an agent;</li>
-<li><span class='attribute' id="association.activity">activity</span>: an identifier (<span class="name">a</span>) for the activity;</li>
-<li><span class='attribute' id="association.agent">agent</span>: an OPTIONAL identifier (<span class="name">ag</span>) for the agent associated with the activity;</li>
-<li><span class='attribute' id="association.plan">plan</span>: an OPTIONAL identifier (<span class="name">pl</span>) for the plan the agent relied on in the context of this activity;
-<li><span class='attribute' id="association.attributes">attributes</span>: an OPTIONAL set (<span class="name">attrs</span>) of attribute-value pairs representing additional information about this association of this activity with this agent.</li>
+<li><span class="attribute" id="association.id">id</span>: an <em class="rfc2119" title="OPTIONAL">OPTIONAL</em> identifier for the association between an activity and an agent;</li>
+<li><span class="attribute" id="association.activity">activity</span>: an identifier (<span class="name">a</span>) for the activity;</li>
+<li><span class="attribute" id="association.agent">agent</span>: an <em class="rfc2119" title="OPTIONAL">OPTIONAL</em> identifier (<span class="name">ag</span>) for the agent associated with the activity;</li>
+<li><span class="attribute" id="association.plan">plan</span>: an <em class="rfc2119" title="OPTIONAL">OPTIONAL</em> identifier (<span class="name">pl</span>) for the plan the agent relied on in the context of this activity;
+</li><li><span class="attribute" id="association.attributes">attributes</span>: an <em class="rfc2119" title="OPTIONAL">OPTIONAL</em> set (<span class="name">attrs</span>) of attribute-value pairs representing additional information about this association of this activity with this agent.</li>
</ul></div>
<p></p>
-<p>While each of <a href="#association.id"><span class='attribute'>id</span></a>, <a href="#association.agent"><span class='attribute'>agent</span></a>, <a href="#association.plan"><span class='attribute'>plan</span></a>, and <a href="#association.attributes"><span class='attribute'>attributes</span></a> is OPTIONAL, at least one of them MUST be present.</p>
-
-<p><span class="glossary-ref" data-ref="glossary-plan"></span> The type of a Plan entity is denoted by <dfn title="dfn-prov:plan" id="dfn-prov:plan"><span class="name">prov:Plan</span></dfn>.</p>
+<p>While each of <a href="#association.id"><span class="attribute">id</span></a>, <a href="#association.agent"><span class="attribute">agent</span></a>, <a href="#association.plan"><span class="attribute">plan</span></a>, and <a href="#association.attributes"><span class="attribute">attributes</span></a> is <em class="rfc2119" title="OPTIONAL">OPTIONAL</em>, at least one of them <em class="rfc2119" title="MUST">MUST</em> be present.</p>
+
+<p><span class="glossary-ref"> A <dfn id="concept-plan" title="Plan" class="internalDFN">plan</dfn><sup><a class="internalDFN" href="#concept-plan"><span class="diamond"> ◊</span></a></sup> is an entity that represents a set of actions or steps intended by one or more agents to achieve some goals. </span> The type of a Plan entity is denoted by <dfn title="dfn-prov:plan" id="dfn-prov:plan" class="internalDFN"><span class="name">prov:Plan</span></dfn><sup><a class="internalDFN" href="#dfn-prov:plan"><span class="diamond"> ◊</span></a></sup>.</p>
@@ -2768,10 +2796,9 @@
<p>PROV defines no plan-specific attributes.</p>
-<div class="anexample" id="anexample-wasAssociatedWith">
-<p>In the following example, a designer agent and an operator agent are associated with an activity. The designer's goals are achieved by a workflow <span class="name">ex:wf</span>, described as an entity of type <span class="name"><a title="dfn-prov:plan">plan</a></span>. </p>
-<pre class="codeexample">
-activity(ex:a, [ prov:type="workflow execution" ])
+<div class="anexample" id="anexample-wasAssociatedWith"><div class="anexampleTitle">Example 36<sup><a class="internalDFN" href="#anexample-wasAssociatedWith"><span class="diamond"> ◊</span></a></sup></div>
+<p>In the following example, a designer agent and an operator agent are associated with an activity. The designer's goals are achieved by a workflow <span class="name">ex:wf</span>, described as an entity of type <span class="name"><a title="dfn-prov:plan" href="#dfn-prov:plan" class="internalDFN">plan</a></span>. </p>
+<pre class="codeexample">activity(ex:a, [ prov:type="workflow execution" ])
agent(ex:ag1, [ prov:type="operator" ])
agent(ex:ag2, [ prov:type="designer" ])
wasAssociatedWith(ex:a, ex:ag1, -, [ prov:role="loggedInUser", ex:how="webapp" ])
@@ -2784,10 +2811,9 @@
for instance.
</div>
-<div class="anexample" id="anexample-wasAssociatedWith-2">
+<div class="anexample" id="anexample-wasAssociatedWith-2"><div class="anexampleTitle">Example 37<sup><a class="internalDFN" href="#anexample-wasAssociatedWith-2"><span class="diamond"> ◊</span></a></sup></div>
<p>In some cases, one wants to indicate a plan was followed, without having to specify which agent was involved.</p>
-<pre class="codeexample">
-activity(ex:a, [ prov:type="workflow execution" ])
+<pre class="codeexample">activity(ex:a, [ prov:type="workflow execution" ])
wasAssociatedWith(ex:a, -, ex:wf)
entity(ex:wf, [ prov:type='prov:Plan',
ex:label="Workflow 1",
@@ -2803,9 +2829,9 @@
<section id="term-delegation">
-<h4>Delegation</h4>
-
-<div class="glossary-ref" data-ref="glossary-delegation"></div>
+<h4><span class="secno">5.3.4 </span>Delegation</h4>
+
+<div class="glossary-ref"> <dfn id="concept-delegation" class="internalDFN">Delegation</dfn><sup><a class="internalDFN" href="#concept-delegation"><span class="diamond"> ◊</span></a></sup> 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. </div>
<p>For example, a
student acted on behalf of his or her supervisor, who acted on behalf of the
@@ -2816,24 +2842,23 @@
<p>
-<div class="attributes" id="attributes-delegation">
-A <dfn title="actedOnBehalfOf">delegation</dfn> link<span class="withPn">, written <span class="pnExpression">actedOnBehalfOf(id; ag2, ag1, a, attrs)</span> in PROV-N,</span> has:
+</p><div class="attributes" id="attributes-delegation">
+A <dfn title="actedOnBehalfOf" id="dfn-actedonbehalfof" class="internalDFN">delegation</dfn><sup><a class="internalDFN" href="#dfn-actedonbehalfof"><span class="diamond"> ◊</span></a></sup> link<span class="withPn">, written <span class="pnExpression">actedOnBehalfOf(id; ag2, ag1, a, attrs)</span> in PROV-N,</span> has:
<ul>
-<li><span class='attribute' id="delegation.id">id</span>: an OPTIONAL identifier for the delegation link between delegate and responsible;</li>
-<li><span class='attribute' id="delegation.delegate">delegate</span>: an identifier (<span class="name">ag2</span>) for the agent associated with an activity, acting on behalf of the responsible
+<li><span class="attribute" id="delegation.id">id</span>: an <em class="rfc2119" title="OPTIONAL">OPTIONAL</em> identifier for the delegation link between delegate and responsible;</li>
+<li><span class="attribute" id="delegation.delegate">delegate</span>: an identifier (<span class="name">ag2</span>) for the agent associated with an activity, acting on behalf of the responsible
agent;</li>
-<li><span class='attribute' id="delegation.responsible">responsible</span>: an identifier (<span class="name">ag1</span>) for the agent, on behalf of which the delegate agent acted;</li>
-<li><span class='attribute' id="delegation.activity">activity</span>: an OPTIONAL identifier (<span class="name">a</span>) of an activity for which the delegation link holds;</li>
-<li><span class='attribute' id="delegation.attributes">attributes</span>: an OPTIONAL set (<span class="name">attrs</span>) of attribute-value pairs representing additional information about this delegation link.</li>
+<li><span class="attribute" id="delegation.responsible">responsible</span>: an identifier (<span class="name">ag1</span>) for the agent, on behalf of which the delegate agent acted;</li>
+<li><span class="attribute" id="delegation.activity">activity</span>: an <em class="rfc2119" title="OPTIONAL">OPTIONAL</em> identifier (<span class="name">a</span>) of an activity for which the delegation link holds;</li>
+<li><span class="attribute" id="delegation.attributes">attributes</span>: an <em class="rfc2119" title="OPTIONAL">OPTIONAL</em> set (<span class="name">attrs</span>) of attribute-value pairs representing additional information about this delegation link.</li>
</ul></div>
-<div class="anexample">
+<div class="anexample" id="example_38"><div class="anexampleTitle">Example 38<sup><a class="internalDFN" href="#example_38"><span class="diamond"> ◊</span></a></sup></div>
<p>The following fragment describes three agents: a programmer, a researcher, and a funder. The programmer and researcher are associated with a workflow activity. The programmer acts on behalf
of the researcher (line-management) encoding the commands specified by the researcher; the researcher acts on behalf of the funder, who has a contractual agreement with the researcher. The terms
'line-management' and 'contract' used in this example are domain specific.</p>
-<pre class="codeexample">
-activity(a,[ prov:type="workflow" ])
+<pre class="codeexample">activity(a,[ prov:type="workflow" ])
agent(ag1, [ prov:type="programmer" ])
agent(ag2, [ prov:type="researcher" ])
agent(ag3, [ prov:type="funder" ])
@@ -2857,10 +2882,10 @@
</section>
<section id="term-influence">
-<h3>Influence</h3>
+<h4><span class="secno">5.3.5 </span>Influence</h4>
<p>
-<span class="glossary-ref" data-ref="glossary-influence"></span>
+<span class="glossary-ref"> <dfn id="concept-influence" class="internalDFN">Influence</dfn><sup><a class="internalDFN" href="#concept-influence"><span class="diamond"> ◊</span></a></sup> 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>
@@ -2869,62 +2894,60 @@
<p>
-<div class="attributes" id="attributes-influence">
-An <dfn title="wasInfluencedBy">Influence</dfn> relation<span class="withPn">, written <span class="pnExpression">wasInfluencedBy(id; o2, o1, attrs)</span> in PROV-N,</span> has:
+</p><div class="attributes" id="attributes-influence">
+An <dfn title="wasInfluencedBy" id="dfn-wasinfluencedby" class="internalDFN">Influence</dfn><sup><a class="internalDFN" href="#dfn-wasinfluencedby"><span class="diamond"> ◊</span></a></sup> relation<span class="withPn">, written <span class="pnExpression">wasInfluencedBy(id; o2, o1, attrs)</span> in PROV-N,</span> has:
<ul>
-<li><span class='attribute' id="influence.id">id</span>: an OPTIONAL identifier identifying the relation;</li>
-<li><span class='attribute' id="influence.influencee">influencee</span>: an identifier (<span class="name">o2</span>) for an entity, activity, or agent;
-<li><span class='attribute' id="influence.influencer">influencer</span>: an identifier (<span class="name">o1</span>) for an ancestor entity, activity, or agent that the former depends on;
-<li><span class='attribute' id="influence.attributes">attributes</span>: an OPTIONAL set (<span class="name">attrs</span>) of attribute-value pairs representing additional information about this relation.</li>
+<li><span class="attribute" id="influence.id">id</span>: an <em class="rfc2119" title="OPTIONAL">OPTIONAL</em> identifier identifying the relation;</li>
+<li><span class="attribute" id="influence.influencee">influencee</span>: an identifier (<span class="name">o2</span>) for an entity, activity, or agent;
+</li><li><span class="attribute" id="influence.influencer">influencer</span>: an identifier (<span class="name">o1</span>) for an ancestor entity, activity, or agent that the former depends on;
+</li><li><span class="attribute" id="influence.attributes">attributes</span>: an <em class="rfc2119" title="OPTIONAL">OPTIONAL</em> set (<span class="name">attrs</span>) of attribute-value pairs representing additional information about this relation.</li>
</ul></div>
<p>
-A <a>Usage</a>, <a title="Start">start</a>, <a title="End">end</a>, <a title="Generation">generation</a>, <a title="Invalidation">invalidation</a>, <a title="Communication">communication</a>, <a title="Derivation">derivation</a>, <a title="Attribution">attribution</a>, <a title="Association">association</a>, and <a title="Delegation">delegation</a> is also an <a title="Influence">influence</a>. It is RECOMMENDED to adopt these more specific relations when writing provenance descriptions. It is anticipated that the <a>Influence</a> relation may be useful to express queries over provenance information.
+A <a href="#concept-usage" class="internalDFN">usage</a>, <a title="Start" href="#concept-start" class="internalDFN">start</a>, <a title="End" href="#concept-end" class="internalDFN">end</a>, <a title="Generation" href="#concept-generation" class="internalDFN">generation</a>, <a title="Invalidation" href="#concept-invalidation" class="internalDFN">invalidation</a>, <a title="Communication" href="#concept-communication" class="internalDFN">communication</a>, <a title="Derivation" href="#concept-derivation" class="internalDFN">derivation</a>, <a title="Attribution" href="#concept-attribution" class="internalDFN">attribution</a>, <a title="Association" href="#concept-association" class="internalDFN">association</a>, and <a title="Delegation" href="#concept-delegation" class="internalDFN">delegation</a> is also an <a title="Influence" href="#concept-influence" class="internalDFN">influence</a>. It is <em class="rfc2119" title="RECOMMENDED">RECOMMENDED</em> to adopt these more specific relations when writing provenance descriptions. It is anticipated that the <a href="#concept-influence" class="internalDFN">Influence</a> relation may be useful to express queries over provenance information.
</p>
<div id="mapping-relations-to-influence-table_text" style="text-align: left;">
The following table establishes the correspondence between
-the attributes <a class='attribute' href="#influence.influencee">influencee</a> and <a class='attribute' href="#influence.influencer">influencer</a>, and attributes of
-<a>Usage</a>, <a>Start</a>, <a>End</a>, <a>Generation</a>, <a>Invalidation</a>, <a>Communication</a>, <a>Derivation</a>, <a>Attribution</a>, <a>Association</a>, and <a>Delegation</a>.
-
-<table class="thinborder" style="margin-left: auto; margin-right: auto;">
-<caption id="mapping-relations-to-influence-table">Mapping Relations to Influence</caption> <!-- Table 7-->
-<tr><td><b>Relation Name</b></td><td><b><a class='attribute' href="#influence.influencee">influencee</a></b></td><td><b><a class='attribute' href="#influence.influencer">influencer</a></b></td></tr>
+the attributes <a class="attribute" href="#influence.influencee">influencee</a> and <a class="attribute" href="#influence.influencer">influencer</a>, and attributes of
+<a href="#concept-usage" class="internalDFN">Usage</a>, <a href="#concept-start" class="internalDFN">Start</a>, <a href="#concept-end" class="internalDFN">End</a>, <a href="#concept-generation" class="internalDFN">Generation</a>, <a href="#concept-invalidation" class="internalDFN">Invalidation</a>, <a href="#concept-communication" class="internalDFN">Communication</a>, <a href="#concept-derivation" class="internalDFN">Derivation</a>, <a href="#concept-attribution" class="internalDFN">Attribution</a>, <a href="#concept-association" class="internalDFN">Association</a>, and <a href="#concept-delegation" class="internalDFN">Delegation</a>.
+
+<table class="thinborder" style="margin-left: auto; margin-right: auto;">
+<caption id="mapping-relations-to-influence-table"><span>Table 7<sup><a class="internalDFN" href="#mapping-relations-to-influence-table"><span class="diamond"> ◊:</span></a></sup> </span>Mapping Relations to Influence</caption> <!-- Table 7-->
+<tbody><tr><td><b>Relation Name</b></td><td><b><a class="attribute" href="#influence.influencee">influencee</a></b></td><td><b><a class="attribute" href="#influence.influencer">influencer</a></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>Generation</a></td><td><a class='attribute' href="#generation.entity">entity</a></td><td><a class='attribute' href="#generation.activity">activity</a></td></tr>
-<tr class="component1-color"><td><a>Usage</a></td><td><a class='attribute' href="#usage.activity">activity</a></td><td><a class='attribute' href="#usage.entity">entity</a></td></tr>
-<tr class="component1-color"><td><a>Communication</a></td><td><a class='attribute' href="#communication.informed">informed</a></td><td><a class='attribute' href="#communication.informant">informant</a></td></tr>
-<tr class="component1-color"><td><a>Start</a></td><td><a class='attribute' href="#start.activity">activity</a></td><td><a class='attribute' href="#start.trigger">trigger</a></td></tr>
-<tr class="component1-color"><td><a>End</a></td><td><a class='attribute' href="#end.activity">activity</a></td><td><a class='attribute' href="#end.trigger">trigger</a></td></tr>
-<tr class="component1-color"><td><a>Invalidation</a></td><td><a class='attribute' href="#invalidation.entity">entity</a></td><td><a class='attribute' href="#invalidation.activity">activity</a></td></tr>
+<tr class="component1-color"><td><a href="#concept-generation" class="internalDFN">Generation</a></td><td><a class="attribute" href="#generation.entity">entity</a></td><td><a class="attribute" href="#generation.activity">activity</a></td></tr>
+<tr class="component1-color"><td><a href="#concept-usage" class="internalDFN">Usage</a></td><td><a class="attribute" href="#usage.activity">activity</a></td><td><a class="attribute" href="#usage.entity">entity</a></td></tr>
+<tr class="component1-color"><td><a href="#concept-communication" class="internalDFN">Communication</a></td><td><a class="attribute" href="#communication.informed">informed</a></td><td><a class="attribute" href="#communication.informant">informant</a></td></tr>
+<tr class="component1-color"><td><a href="#concept-start" class="internalDFN">Start</a></td><td><a class="attribute" href="#start.activity">activity</a></td><td><a class="attribute" href="#start.trigger">trigger</a></td></tr>
+<tr class="component1-color"><td><a href="#concept-end" class="internalDFN">End</a></td><td><a class="attribute" href="#end.activity">activity</a></td><td><a class="attribute" href="#end.trigger">trigger</a></td></tr>
+<tr class="component1-color"><td><a href="#concept-invalidation" class="internalDFN">Invalidation</a></td><td><a class="attribute" href="#invalidation.entity">entity</a></td><td><a class="attribute" href="#invalidation.activity">activity</a></td></tr>
<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
-<tr class="component2-color"><td><a>Derivation</a></td><td><a class='attribute' href="#derivation.generatedEntity">generatedEntity</a></td><td><a class='attribute' href="#derivation.usedEntity">usedEntity</a></td></tr>
+<tr class="component2-color"><td><a href="#concept-derivation" class="internalDFN">Derivation</a></td><td><a class="attribute" href="#derivation.generatedEntity">generatedEntity</a></td><td><a class="attribute" href="#derivation.usedEntity">usedEntity</a></td></tr>
<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
-<tr class="component3-color"><td><a>Attribution</a></td><td><a class='attribute' href="#attribution.entity">entity</a></td><td><a class='attribute' href="#attribution.agent">agent</a></td></tr>
-<tr class="component3-color"><td><a>Association</a></td><td><a class='attribute' href="#association.activity">activity</a></td><td><a class='attribute' href="#association.agent">agent</a></td></tr>
-<tr class="component3-color"><td><a>Delegation</a></td><td><a class='attribute' href="#delegation.delegate">delegate</a></td><td><a class='attribute' href="#delegation.responsible">responsible</a></td></tr>
-</table>
+<tr class="component3-color"><td><a href="#concept-attribution" class="internalDFN">Attribution</a></td><td><a class="attribute" href="#attribution.entity">entity</a></td><td><a class="attribute" href="#attribution.agent">agent</a></td></tr>
+<tr class="component3-color"><td><a href="#concept-association" class="internalDFN">Association</a></td><td><a class="attribute" href="#association.activity">activity</a></td><td><a class="attribute" href="#association.agent">agent</a></td></tr>
+<tr class="component3-color"><td><a href="#concept-delegation" class="internalDFN">Delegation</a></td><td><a class="attribute" href="#delegation.delegate">delegate</a></td><td><a class="attribute" href="#delegation.responsible">responsible</a></td></tr>
+</tbody></table>
</div>
-<div class="anexample" id="influence-example">
-<p>We refer to the example of <a class="section-ref" href="#section-example-two"><span>TBD</span></a>, and specifically to <a href="#prov-a-document2-top">Figure 3</a>.
+<div class="anexample" id="influence-example"><div class="anexampleTitle">Example 39<sup><a class="internalDFN" href="#influence-example"><span class="diamond"> ◊</span></a></sup></div>
+<p>We refer to the example of <a class="section-ref" href="#section-example-two"><span>Section 4.2</span></a>, and specifically to <a href="#prov-a-document2-top" class="fig-ref">Figure 3</a>.
We could have expressed that the influence of
<span class="name">w3:Consortium</span>
on <span class="name">tr:WD-prov-dm-20111215</span>.
-<pre class="codeexample">
- wasInfluencedBy(tr:WD-prov-dm-20111215, w3:Consortium)
+</p><pre class="codeexample"> wasInfluencedBy(tr:WD-prov-dm-20111215, w3:Consortium)
</pre>
Instead, it is recommended to express the more specific description:
-<pre class="codeexample">
- wasAttributedTo(tr:WD-prov-dm-20111215, w3:Consortium)
+<pre class="codeexample"> wasAttributedTo(tr:WD-prov-dm-20111215, w3:Consortium)
</pre>
</div>
@@ -2939,42 +2962,42 @@
<section id="component4">
-<h3>Component 4: Bundles</h3>
+<h3><span class="secno">5.4 </span>Component 4: Bundles</h3>
<p>The fourth component of PROV-DM is concerned with bundles, a mechanism to support provenance of provenance.
-<a href="#figure-component4">Figure 9</a> depicts a UML class diagram for the fourth component. It comprises a <a>Bundle</a> class defined as a subclass of <a>Entity</a>.
+<a href="#figure-component4">Figure 9</a> depicts a UML class diagram for the fourth component. It comprises a <a href="#concept-bundle" class="internalDFN">Bundle</a> class defined as a subclass of <a href="#concept-entity" class="internalDFN">Entity</a>.
</p>
<div style="text-align: center;">
-<figure style="max-width: 95%; ">
-
-<img src="uml/component4.png" alt="bundles"/><br>
-<figcaption id="figure-component4">Bundle Component Overview (Informative)</figcaption>
-</figure>
+<span class="figure" id="fig-figure-9-bundle-component-overview-informative" style="max-width: 95%; ">
+
+<img src="uml/component4.png" alt="bundles"><br>
+<span class="figcaption" id="figure-component4">Figure 9<sup><a class="internalDFN" href="#figure-component4"><span class="diamond"> ◊:</span></a></sup> Bundle Component Overview (Informative)</span>
+</span>
</div>
<section id="term-bundle">
-<h3>Bundle constructor</h3>
+<h4><span class="secno">5.4.1 </span>Bundle constructor</h4>
<p>
-<span class="glossary-ref" data-ref="glossary-bundle" >
-</span>
+<span class="glossary-ref">
+ A <dfn id="concept-bundle" title="Bundle" class="internalDFN">bundle</dfn><sup><a class="internalDFN" href="#concept-bundle"><span class="diamond"> ◊</span></a></sup> is a named set of provenance descriptions, and is itself an entity, so allowing provenance of provenance to be expressed. </span>
</p>
<p>
-<div class="attributes" id="attributes-bundle">
- A <dfn title="dfn-bundle" id="dfn-bundle-constructor">bundle constructor</dfn> allows the content and the name of a bundle to be specified; it is written <span class="pnExpression">bundle id description_1 ... description_n endBundle</span> and consists of:
+</p><div class="attributes" id="attributes-bundle">
+ A <dfn title="dfn-bundle" id="dfn-bundle-constructor" class="internalDFN">bundle constructor</dfn><sup><a class="internalDFN" href="#dfn-bundle-constructor"><span class="diamond"> ◊</span></a></sup> allows the content and the name of a bundle to be specified; it is written <span class="pnExpression">bundle id description_1 ... description_n endBundle</span> and consists of:
<ul>
-<li><span class='attribute' id="bundle.constructor.id">id</span>: an identifier for the bundle;</li>
-<li><span class='attribute' id="bundle.constructor.descriptions">descriptions</span>: a set of provenance descriptions <span class="name">
+<li><span class="attribute" id="bundle.constructor.id">id</span>: an identifier for the bundle;</li>
+<li><span class="attribute" id="bundle.constructor.descriptions">descriptions</span>: a set of provenance descriptions <span class="name">
description_1</span>, ..., <span class="name">description_n</span>.</li>
</ul>
<p>A bundle's identifier <span class="name">id</span> identifies a unique set of descriptions.</p>
@@ -2989,31 +3012,31 @@
<section id="term-bundle-entity">
-<h3>Bundle Type</h3>
+<h4><span class="secno">5.4.2 </span>Bundle Type</h4>
<p>A bundle is a named set of descriptions, but it is also an entity so that its provenance can be described. </p>
-<p>PROV defines the following <dfn title="Bundle Type" id="dfn-bundle-type">type for bundles</dfn>:</p>
+<p>PROV defines the following <dfn title="Bundle Type" id="dfn-bundle-type" class="internalDFN">type for bundles</dfn><sup><a class="internalDFN" href="#dfn-bundle-type"><span class="diamond"> ◊</span></a></sup>:</p>
<ul>
-<li><dfn title="dfn-prov:bundle" id="dfn-prov:bundle"><span class="name">prov:Bundle</span></dfn> is the type that denotes Bundle entities.
-</ul>
+<li><dfn title="dfn-prov:bundle" id="dfn-prov:bundle" class="internalDFN"><span class="name">prov:Bundle</span></dfn><sup><a class="internalDFN" href="#dfn-prov:bundle"><span class="diamond"> ◊</span></a></sup> is the type that denotes Bundle entities.
+</li></ul>
<p>PROV defines no bundle-specific attributes.</p>
<p>
A bundle description is of the form <span class="pnExpression">entity(id, [ prov:type='prov:Bundle', attr1=val1, ...] )</span>
-where <span class='name'>id</span> is an identifier denoting a bundle,
+where <span class="name">id</span> is an identifier denoting a bundle,
a type <span>prov:Bundle</span> and
-an OPTIONAL set of attribute-value pairs ((<span class="name">attr1</span>, <span class="name">val1</span>), ...) representing additional information about this bundle.
+an <em class="rfc2119" title="OPTIONAL">OPTIONAL</em> set of attribute-value pairs ((<span class="name">attr1</span>, <span class="name">val1</span>), ...) representing additional information about this bundle.
</p>
<p>The provenance of provenance can then be described using PROV constructs, as illustrated by
-<a href="#anexample-provenance-of-provenance" class="anexample-ref"><span>Example REF</span></a>
+<a href="#anexample-provenance-of-provenance" class="anexample-ref"><span>Example 40</span></a>
and
-<a href="#anexample-provenance-aggregation" class="anexample-ref"><span>Example REF</span></a>.</p>
-
-<div class="anexample" id="anexample-provenance-of-provenance">
+<a href="#anexample-provenance-aggregation" class="anexample-ref"><span>Example 41</span></a>.</p>
+
+<div class="anexample" id="anexample-provenance-of-provenance"><div class="anexampleTitle">Example 40<sup><a class="internalDFN" href="#anexample-provenance-of-provenance"><span class="diamond"> ◊</span></a></sup></div>
<p>Let us consider two entities <span class="name">ex:report1</span> and <span class="name">ex:report2</span>.</p>
<pre class="codeexample">
entity(ex:report1, [ prov:type="report", ex:version=1 ])
@@ -3060,7 +3083,7 @@
</pre>
</div>
-<div class="anexample" id="anexample-provenance-aggregation">
+<div class="anexample" id="anexample-provenance-aggregation"><div class="anexampleTitle">Example 41<sup><a class="internalDFN" href="#anexample-provenance-aggregation"><span class="diamond"> ◊</span></a></sup></div>
<p>A provenance aggregator could merge two bundles, resulting in a novel bundle, whose provenance is described as follows.</p>
<pre class="codeexample">
bundle agg:bundle3
@@ -3079,7 +3102,7 @@
wasDerivedFrom(agg:bundle3, alice:bundle2)
</pre>
<p>The new bundle is given a new identifier <span class="name">agg:bundle3</span> and is attributed to the <span class="name">ex:aggregator01</span> agent.
-</div>
+</p></div>
</section>
@@ -3089,26 +3112,26 @@
<section id="component5">
-<h3>Component 5: Alternate Entities</h3>
+<h3><span class="secno">5.5 </span>Component 5: Alternate Entities</h3>
<p>The fifth component of PROV-DM is concerned with
-relations SpecializationOf (<a title="Specialization">Specialization</a>) and AlternateOf (<a>Alternate</a>) between entities.
+relations SpecializationOf (<a title="Specialization" href="#concept-specialization" class="internalDFN">Specialization</a>) and AlternateOf (<a href="#concept-alternate" class="internalDFN">Alternate</a>) between entities.
<a href="#figure-component5">Figure 10</a> depicts
the fifth component with a single class and two binary associations.
</p>
<div style="text-align: center;">
-<figure style="max-width: 95%; ">
-<img src="uml/component5.png" alt="alternates"/><br>
-<figcaption id="figure-component5">Alternates Component Overview (Informative)</figcaption>
-</figure>
+<span class="figure" id="fig-figure-10-alternates-component-overview-informative" style="max-width: 95%; ">
+<img src="uml/component5.png" alt="alternates"><br>
+<span class="figcaption" id="figure-component5">Figure 10<sup><a class="internalDFN" href="#figure-component5"><span class="diamond"> ◊:</span></a></sup> Alternates Component Overview (Informative)</span>
+</span>
</div>
<p>Two provenance descriptions about the same thing may emphasize differents aspects of that thing.</p>
-<div class="anexample" id="entity-example1">
+<div class="anexample" id="entity-example1"><div class="anexampleTitle">Example 42<sup><a class="internalDFN" href="#entity-example1"><span class="diamond"> ◊</span></a></sup></div>
<p>User Alice writes an article. In its provenance, she wishes to refer to the precise version of the article with a date-specific IRI, as she might edit the article later. Alternatively, user Bob refers to the article in general, independently of its variants over time.</p>
</div>
<p>
@@ -3118,10 +3141,10 @@
<section id="term-specialization">
-<h4>Specialization</h4>
-
-
-<span class="glossary-ref" data-ref="glossary-specialization"></span>
+<h4><span class="secno">5.5.1 </span>Specialization</h4>
+
+
+<span class="glossary-ref"> An entity that is a <dfn id="concept-specialization" title="Specialization" class="internalDFN">specialization</dfn><sup><a class="internalDFN" href="#concept-specialization"><span class="diamond"> ◊</span></a></sup> 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>
@@ -3131,12 +3154,12 @@
<p>
-<div class="attributes" id="attributes-specialization">A <dfn title="specializationOf">specialization</dfn> relation<span class="withPn">, written <span class="pnExpression">specializationOf(infra, supra)</span> in PROV-N,</span> has:
+</p><div class="attributes" id="attributes-specialization">A <dfn title="specializationOf" id="dfn-specializationof" class="internalDFN">specialization</dfn><sup><a class="internalDFN" href="#dfn-specializationof"><span class="diamond"> ◊</span></a></sup> relation<span class="withPn">, written <span class="pnExpression">specializationOf(infra, supra)</span> in PROV-N,</span> has:
<ul>
-<li><span class='attribute' id="specialization.specificEntity">specificEntity</span>: an identifier (<span class="name">infra</span>)
+<li><span class="attribute" id="specialization.specificEntity">specificEntity</span>: an identifier (<span class="name">infra</span>)
of the entity that is a specialization of the general entity (<span class="name">supra</span>);</li>
-<li><span class='attribute' id="specialization.generalEntity">generalEntity</span>: an identifier (<span class="name">supra</span>) of the entity that is being specialized.</li>
+<li><span class="attribute" id="specialization.generalEntity">generalEntity</span>: an identifier (<span class="name">supra</span>) of the entity that is being specialized.</li>
</ul>
</div>
@@ -3144,13 +3167,12 @@
-<div class="anexample" id="anexample-specialization">
+<div class="anexample" id="anexample-specialization"><div class="anexampleTitle">Example 43<sup><a class="internalDFN" href="#anexample-specialization"><span class="diamond"> ◊</span></a></sup></div>
<p>
The BBC news home page on 2012-03-23 <span class="name">ex:bbcNews2012-03-23</span>
is a specialization of the BBC news page in general
<a href="http://www.bbc.co.uk/news/">bbc:news/</a>. This can be expressed as follows.
-<pre class="codeexample">
-specializationOf(ex:bbcNews2012-03-23, bbc:news/)
+</p><pre class="codeexample">specializationOf(ex:bbcNews2012-03-23, bbc:news/)
</pre>
We have created a new qualified name, <span class="name">ex:bbcNews2012-03-23</span>, in the namespace <span class="name">ex</span>, to identify the specific page carrying this day's news, which would otherwise be the generic <span class="name">bbc:news/</span> page.
</div>
@@ -3165,41 +3187,40 @@
<section id="term-alternate">
-<h4>Alternate</h4>
-
-
-<span class="glossary-ref" data-ref="glossary-alternate"></span>
-
-
-
-<p><div class="attributes" id="attributes-alternate">An <dfn title="alternateOf">alternate</dfn> relation<span class="withPn">, written <span class="pnExpression">alternateOf(e1, e2)</span> in PROV-N,</span> has:
+<h4><span class="secno">5.5.2 </span>Alternate</h4>
+
+
+<span class="glossary-ref"> Two <dfn id="concept-alternate" title="Alternate" class="internalDFN">alternate</dfn><sup><a class="internalDFN" href="#concept-alternate"><span class="diamond"> ◊</span></a></sup> 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></p><div class="attributes" id="attributes-alternate">An <dfn title="alternateOf" id="dfn-alternateof" class="internalDFN">alternate</dfn><sup><a class="internalDFN" href="#dfn-alternateof"><span class="diamond"> ◊</span></a></sup> relation<span class="withPn">, written <span class="pnExpression">alternateOf(e1, e2)</span> in PROV-N,</span> has:
<ul>
-<li><span class='attribute' id="alternate.alternate1">alternate1</span>: an identifier (<span class="name">e1</span>) of the first of the two entities;</li>
-<li><span class='attribute' id="alternate.alternate2">alternate2</span>: an identifier (<span class="name">e2</span>) of the second of the two entities.</li>
+<li><span class="attribute" id="alternate.alternate1">alternate1</span>: an identifier (<span class="name">e1</span>) of the first of the two entities;</li>
+<li><span class="attribute" id="alternate.alternate2">alternate2</span>: an identifier (<span class="name">e2</span>) of the second of the two entities.</li>
</ul>
</div>
<p>An alternate is not, as defined here, also an influence, and therefore does not have an id and attributes.</p>
<p>
-Note that <a title="alternateOf">alternateOf</a> is a necessarily very general
+Note that <a title="alternateOf" href="#dfn-alternateof" class="internalDFN">alternateOf</a> is a necessarily very general
relationship that, in reasoning, only states that the two
alternate entities respectively fix some aspects of some common thing
(possibly evolving over time), and so there is some relevant
connection between the provenance of the alternates. In a
-specific application context, <a title="alternateOf">alternateOf</a>, or a subtype of it,
+specific application context, <a title="alternateOf" href="#dfn-alternateof" class="internalDFN">alternateOf</a>, or a subtype of it,
could allow more inferences.
</p>
-<div class="anexample" id="anexample-alternate">
+<div class="anexample" id="anexample-alternate"><div class="anexampleTitle">Example 44<sup><a class="internalDFN" href="#anexample-alternate"><span class="diamond"> ◊</span></a></sup></div>
<p>
A given news item on the BBC News site
<a href="http://www.bbc.co.uk/news/science-environment-17526723">bbc:news/science-environment-17526723</a> for desktop
is an alternate of a
<a href="http://www.bbc.co.uk/news/mobile/science-environment-17526723">bbc:news/mobile/science-environment-17526723</a> for mobile devices.</p>
-<pre class="codeexample">
-entity(bbc:news/science-environment-17526723,
+<pre class="codeexample">entity(bbc:news/science-environment-17526723,
[ prov:type="a news item for desktop"])
entity(bbc:news/mobile/science-environment-17526723,
[ prov:type="a news item for mobile devices"])
@@ -3209,15 +3230,14 @@
</div>
-<div class="anexample" id="anexample-alternate2">
+<div class="anexample" id="anexample-alternate2"><div class="anexampleTitle">Example 45<sup><a class="internalDFN" href="#anexample-alternate2"><span class="diamond"> ◊</span></a></sup></div>
<p>
Considering again the two versions of the technical report <span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111215">tr:WD-prov-dm-20111215</a></span> (second working draft) and <span class="name"><span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018">tr:WD-prov-dm-20111018</a></span></span> (first working draft). They are alternates of each other.
-<pre class="codeexample">
-entity(tr:WD-prov-dm-20111018)
+</p><pre class="codeexample">entity(tr:WD-prov-dm-20111018)
entity(tr:WD-prov-dm-20111215)
alternateOf(tr:WD-prov-dm-20111018, tr:WD-prov-dm-20111215)
</pre>
-<p>They are both specialization of the page <a href="http://www.w3.org/TR/prov-dm/">http://www.w3.org/TR/prov-dm/</a>.</p>
+<p>They are both specializations of the page <a href="http://www.w3.org/TR/prov-dm/">http://www.w3.org/TR/prov-dm/</a>.</p>
</div>
</section>
@@ -3226,44 +3246,43 @@
<section id="component6">
-<h3>Component 6: Collections</h3>
+<h3><span class="secno">5.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>
<p><a href="#figure-component6">Figure 11</a> depicts
-the sixth component with two new classes (Collection, Empty Collection) and one association HadMember (<a>Membership</a>).
+the sixth component with two new classes (Collection, Empty Collection) and one association HadMember (<a href="#concept-membership" class="internalDFN">Membership</a>).
</p>
<div style="text-align: center;">
-<figure style="max-width: 95%; ">
-<img src="uml/component6.png" alt="collection"/><br>
-<figcaption id="figure-component6">Collections Component Overview (Informative)</figcaption>
-</figure>
+<span class="figure" id="fig-figure-11-collections-component-overview-informative" style="max-width: 95%; ">
+<img src="uml/component6.png" alt="collection"><br>
+<span class="figcaption" id="figure-component6">Figure 11<sup><a class="internalDFN" href="#figure-component6"><span class="diamond"> ◊:</span></a></sup> Collections Component Overview (Informative)</span>
+</span>
</div>
<section id="term-collection">
-<h3>Collection</h3>
-
-<span class="glossary-ref" data-ref="glossary-collection"></span>
-
-<span class="glossary-ref" data-ref="glossary-empty-collection"></span>
+<h4><span class="secno">5.6.1 </span>Collection</h4>
+
+<span class="glossary-ref"> A <dfn id="concept-collection" title="Collection" class="internalDFN">collection</dfn><sup><a class="internalDFN" href="#concept-collection"><span class="diamond"> ◊</span></a></sup> is an entity that provides a structure to some constituents that must themselves be entities. These constituents are said to be <dfn id="dfn-member" class="internalDFN">member</dfn><sup><a class="internalDFN" href="#dfn-member"><span class="diamond"> ◊</span></a></sup> of the collections. </span>
+
+<span class="glossary-ref"> An <dfn id="concept-empty-collection" title="Empty Collection" class="internalDFN">empty collection</dfn><sup><a class="internalDFN" href="#concept-empty-collection"><span class="diamond"> ◊</span></a></sup> is a collection without members. </span>
<p>PROV-DM defines the following types related to collections:</p>
<ul>
- <li><dfn title="dfn-prov:collection" id="dfn-prov:collection"><span class="name">prov:Collection</span></dfn> denotes an entity of type Collection, i.e. an entity that can participate in relations amongst collections;
-
- <li><dfn title="dfn-prov:emptyCollection" id="dfn-prov:emptyCollection"><span class="name">prov:EmptyCollection</span></dfn> denotes an empty collection.
-</ul>
+ <li><dfn title="dfn-prov:collection" id="dfn-prov:collection" class="internalDFN"><span class="name">prov:Collection</span></dfn><sup><a class="internalDFN" href="#dfn-prov:collection"><span class="diamond"> ◊</span></a></sup> denotes an entity of type Collection, i.e. an entity that can participate in relations amongst collections;
+
+ </li><li><dfn title="dfn-prov:emptyCollection" id="dfn-prov:emptyCollection" class="internalDFN"><span class="name">prov:EmptyCollection</span></dfn><sup><a class="internalDFN" href="#dfn-prov:emptyCollection"><span class="diamond"> ◊</span></a></sup> denotes an empty collection.
+</li></ul>
<p>PROV defines no collection-specific attributes.</p>
-<div class="anexample">
-<pre class="codeexample">
-entity(c0, [ prov:type='prov:EmptyCollection' ]) // c0 is an empty collection
+<div class="anexample" id="example_46"><div class="anexampleTitle">Example 46<sup><a class="internalDFN" href="#example_46"><span class="diamond"> ◊</span></a></sup></div>
+<pre class="codeexample">entity(c0, [ prov:type='prov:EmptyCollection' ]) // c0 is an empty collection
entity(c1, [ prov:type='prov:Collection' ]) // c1 is a collection, with unknown content
</pre>
</div>
@@ -3272,19 +3291,19 @@
</section>
<section id="term-membership">
-<h3>Membership</h3>
-
-<p>A <strong>membership</strong> relation is defined the members of a Collection to be stated. </p>
-
-<span class="glossary-ref" data-ref="glossary-membership"></span>
+<h4><span class="secno">5.6.2 </span>Membership</h4>
+
+<p>A <strong>membership</strong> relation is defined for stating the members of a Collection. </p>
+
+<span class="glossary-ref"> <dfn id="concept-membership" class="internalDFN">Membership</dfn><sup><a class="internalDFN" href="#concept-membership"><span class="diamond"> ◊</span></a></sup> is the belonging of an entity to a collection. </span>
<p>
-<div class="attributes" id="attributes-hadMember">
- A <dfn title="hadMember">membership</dfn> relation, written <span class="pnExpression">hadMember(c, e)</span>, has:
+</p><div class="attributes" id="attributes-hadMember">
+ A <dfn title="hadMember" id="dfn-hadmember" class="internalDFN">membership</dfn><sup><a class="internalDFN" href="#dfn-hadmember"><span class="diamond"> ◊</span></a></sup> relation, written <span class="pnExpression">hadMember(c, e)</span>, has:
<ul>
-<li><span class='attribute' id="membership.collection">collection</span>: an identifier (<span class="name">c</span>) for the collection whose member is asserted; </li>
-<li><span class='attribute' id="membership.entity">entity</span>: the identifier <span class="name">e</span> of an entity that is member of the collection.</li>
+<li><span class="attribute" id="membership.collection">collection</span>: an identifier (<span class="name">c</span>) for the collection whose member is asserted; </li>
+<li><span class="attribute" id="membership.entity">entity</span>: the identifier <span class="name">e</span> of an entity that is member of the collection.</li>
</ul>
</div>
@@ -3292,10 +3311,9 @@
<p>Membership is not, as defined here, also an influence, and therefore does not have an id and attributes.</p>
-<div class="anexample" >
+<div class="anexample" id="example_47"><div class="anexampleTitle">Example 47<sup><a class="internalDFN" href="#example_47"><span class="diamond"> ◊</span></a></sup></div>
<p>In this example, <span class="name">c</span> is a collection known to have <span class="name">e0</span>, <span class="name">e1</span>, and <span class="name">e2</span> as members, and may have other members.</p>
-<pre class="codeexample">
-entity(e0)
+<pre class="codeexample">entity(e0)
entity(e1)
entity(e2)
@@ -3318,8 +3336,8 @@
-<section id="second-class-elements">
-<h3>Further Elements of PROV-DM</h3>
+<section id="second-class-elements">
+<h3><span class="secno">5.7 </span>Further Elements of PROV-DM</h3>
This section introduces further elements of PROV-DM.
@@ -3327,39 +3345,39 @@
<section id="term-identifier">
-<h4>Identifier</h4>
+<h4><span class="secno">5.7.1 </span>Identifier</h4>
<p>
-An <dfn id="dfn-identifier">identifier</dfn> is a <a>qualified
+An <dfn id="dfn-identifier" class="internalDFN">identifier</dfn><sup><a class="internalDFN" href="#dfn-identifier"><span class="diamond"> ◊</span></a></sup> is a <a href="#concept-qualifiedName" class="internalDFN">qualified
name</a>.
</p>
-<p><a>Entity</a>, <a>Activity</a>, and <a>Agent</a> have a mandatory identifier. Two entities (resp. activities, agents) are equal if they have the same identifier.</p>
-
-<p><a>Generation</a>, <a>Usage</a>, <a>Communication</a>, <a>Start</a>, <a>End</a>, <a>Invalidation</a>, <a>Derivation</a>, <a>Attribution</a>, <a>Association</a>, <a>Delegation</a>, <a>Influence</a> have an optional identifier. Two generations (resp. usages, communications, etc.) are equal if they have the same identifier.
-
-</section>
+<p><a href="#concept-entity" class="internalDFN">Entity</a>, <a href="#concept-activity" class="internalDFN">Activity</a>, and <a href="#concept-agent" class="internalDFN">Agent</a> have a mandatory identifier. Two entities (resp. activities, agents) are equal if they have the same identifier.</p>
+
+<p><a href="#concept-generation" class="internalDFN">Generation</a>, <a href="#concept-usage" class="internalDFN">Usage</a>, <a href="#concept-communication" class="internalDFN">Communication</a>, <a href="#concept-start" class="internalDFN">Start</a>, <a href="#concept-end" class="internalDFN">End</a>, <a href="#concept-invalidation" class="internalDFN">Invalidation</a>, <a href="#concept-derivation" class="internalDFN">Derivation</a>, <a href="#concept-attribution" class="internalDFN">Attribution</a>, <a href="#concept-association" class="internalDFN">Association</a>, <a href="#concept-delegation" class="internalDFN">Delegation</a>, <a href="#concept-influence" class="internalDFN">Influence</a> have an optional identifier. Two generations (resp. usages, communications, etc.) are equal if they have the same identifier.
+
+</p></section>
<section id="term-attribute">
-<h4>Attribute</h4>
-
-<p>An <dfn title="dfn-attribute" id="dfn-attribute">attribute</dfn> is a <a>qualified name</a>.
-
-
-<p>The PROV data model introduces a pre-defined set of attributes in the <a title="prov-namespace">PROV namespace</a>, which we define below.
+<h4><span class="secno">5.7.2 </span>Attribute</h4>
+
+<p>An <dfn title="dfn-attribute" id="dfn-attribute" class="internalDFN">attribute</dfn><sup><a class="internalDFN" href="#dfn-attribute"><span class="diamond"> ◊</span></a></sup> is a <a href="#concept-qualifiedName" class="internalDFN">qualified name</a>.
+
+
+</p><p>The PROV data model introduces a pre-defined set of attributes in the <a title="prov-namespace" href="#dfn-prov-namespace" class="internalDFN">PROV namespace</a>, which we define below.
This specification does not provide any interpretation for any attribute declared in any other namespace.</p>
<div id="attributes-at-a-glance-divz" style="text-align: left;">
-<table class="thinborder" style="margin-left: auto; margin-right: auto;">
-<caption id="attributes-at-a-glance">PROV-DM Attributes At a Glance</caption> <!-- Table 8 -->
-<tr><td><b>Attribute</b></td><td><b>Allowed In</b></td><td><b>value</b></td><td><b>Section</b></td></tr>
-<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "><td style="border-width: 0px; "></td></tr>
-<tr><td><a title="label">prov:label</a></td><td><em>any construct</em></td><td>A <a title="value">Value</a> of type <a class="section-ref" href="http://www.w3.org/TR/xmlschema11-2/#string">xsd:string</a></td><td><a class="section-ref" href="#term-attribute-label"><span>TBD</span></a> </td></tr>
-<tr><td><a title="location">prov:location</a></td><td><a>Entity</a>, <a>Activity</a>, <a>Agent</a>, <a>Usage</a>, <a>Generation</a>, <a>Invalidation</a>, <a>Start</a>, and <a>End</a></td><td>A <a title="value">Value</a></td><td><a class="section-ref" href="#term-attribute-location"><span>TBD</span></a> </td></tr>
-<tr><td><a title="role">prov:role</a></td><td><a>Usage</a>, <a>Generation</a>, <a>Invalidation</a>, <a>Association</a>, <a>Start</a>, and <a>End</a></td><td>A <a title="value">Value</a></td><td><a class="section-ref" href="#term-attribute-role"><span>TBD</span></a> </td></tr>
-<tr><td><a title="type">prov:type</a></td><td><em>any construct</em></td><td>A <a title="value">Value</a></td><td><a class="section-ref" href="#term-attribute-type"><span>TBD</span></a> </td></tr>
-<tr><td><a title="value-attribute">prov:value</a></td><td><a>Entity</a></td><td>A <a title="value">Value</a></td><td><a class="section-ref" href="#term-attribute-value"><span>TBD</span></a> </td></tr>
-</table>
+<table class="thinborder" style="margin-left: auto; margin-right: auto;">
+<caption id="attributes-at-a-glance"><span>Table 8<sup><a class="internalDFN" href="#attributes-at-a-glance"><span class="diamond"> ◊:</span></a></sup> </span>PROV-DM Attributes At a Glance</caption> <!-- Table 8 -->
+<tbody><tr><td><b>Attribute</b></td><td><b>Allowed In</b></td><td><b>value</b></td><td><b>Section</b></td></tr>
+<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
+<tr><td><a title="label" href="#concept-label" class="internalDFN">prov:label</a></td><td><em>any construct</em></td><td>A <a title="value" href="#concept-value" class="internalDFN">Value</a> of type <a class="section-ref" href="http://www.w3.org/TR/xmlschema11-2/#string">xsd:string</a></td><td><a class="section-ref" href="#term-attribute-label"><span>Section 5.7.2.1</span></a> </td></tr>
+<tr><td><a title="location" href="#concept-location" class="internalDFN">prov:location</a></td><td><a href="#concept-entity" class="internalDFN">Entity</a>, <a href="#concept-activity" class="internalDFN">Activity</a>, <a href="#concept-agent" class="internalDFN">Agent</a>, <a href="#concept-usage" class="internalDFN">Usage</a>, <a href="#concept-generation" class="internalDFN">Generation</a>, <a href="#concept-invalidation" class="internalDFN">Invalidation</a>, <a href="#concept-start" class="internalDFN">Start</a>, and <a href="#concept-end" class="internalDFN">End</a></td><td>A <a title="value" href="#concept-value" class="internalDFN">Value</a></td><td><a class="section-ref" href="#term-attribute-location"><span>Section 5.7.2.2</span></a> </td></tr>
+<tr><td><a title="role" href="#concept-role" class="internalDFN">prov:role</a></td><td><a href="#concept-usage" class="internalDFN">Usage</a>, <a href="#concept-generation" class="internalDFN">Generation</a>, <a href="#concept-invalidation" class="internalDFN">Invalidation</a>, <a href="#concept-association" class="internalDFN">Association</a>, <a href="#concept-start" class="internalDFN">Start</a>, and <a href="#concept-end" class="internalDFN">End</a></td><td>A <a title="value" href="#concept-value" class="internalDFN">Value</a></td><td><a class="section-ref" href="#term-attribute-role"><span>Section 5.7.2.3</span></a> </td></tr>
+<tr><td><a title="type" href="#concept-type" class="internalDFN">prov:type</a></td><td><em>any construct</em></td><td>A <a title="value" href="#concept-value" class="internalDFN">Value</a></td><td><a class="section-ref" href="#term-attribute-type"><span>Section 5.7.2.4</span></a> </td></tr>
+<tr><td><a title="value-attribute" href="#concept-value-attribute" class="internalDFN">prov:value</a></td><td><a href="#concept-entity" class="internalDFN">Entity</a></td><td>A <a title="value" href="#concept-value" class="internalDFN">Value</a></td><td><a class="section-ref" href="#term-attribute-value"><span>Section 5.7.2.5</span></a> </td></tr>
+</tbody></table>
</div>
@@ -3367,49 +3385,45 @@
<section id="term-attribute-label">
-<h4>prov:label</h4>
+<h5><span class="secno">5.7.2.1 </span>prov:label</h5>
<p>
-<span class="glossary-ref" data-ref="glossary-label"></span>
-The value associated with the attribute <span class="name">prov:label</span> MUST be a string.</p>
-
-<div class="anexample">
+<span class="glossary-ref"> The attribute <dfn id="concept-label" title="label" class="internalDFN"><span class="name">prov:label</span></dfn><sup><a class="internalDFN" href="#concept-label"><span class="diamond"> ◊</span></a></sup> provides a human-readable representation of an instance of a PROV-DM type or relation. </span>
+The value associated with the attribute <span class="name">prov:label</span> <em class="rfc2119" title="MUST">MUST</em> be a string.</p>
+
+<div class="anexample" id="example_48"><div class="anexampleTitle">Example 48<sup><a class="internalDFN" href="#example_48"><span class="diamond"> ◊</span></a></sup></div>
<p>The following entity is provided with a label attribute.</p>
-<pre class="codeexample">
- entity(ex:e1, [ prov:label="This is a human-readable label" ])
+<pre class="codeexample"> entity(ex:e1, [ prov:label="This is a human-readable label" ])
</pre>
<p>The following entity has two label attributes, in French and English.</p>
-<pre class="codeexample">
- entity(ex:car01, [ prov:label="Voiture 01"@fr, prov:label="Car 01"@en ])
+<pre class="codeexample"> entity(ex:car01, [ prov:label="Voiture 01"@fr, prov:label="Car 01"@en ])
</pre>
</div>
</section>
<section id="term-attribute-location">
-<h4>prov:location</h4>
-
-<p><span class="glossary-ref" data-ref="glossary-location"></span>
+<h5><span class="secno">5.7.2.2 </span>prov:location</h5>
+
+<p><span class="glossary-ref"> A <dfn id="concept-location" title="location" class="internalDFN">location</dfn><sup><a class="internalDFN" href="#concept-location"><span class="diamond"> ◊</span></a></sup> 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>
As such, there are numerous ways in which location can be expressed, such as by a coordinate,
address, landmark, and so forth. This document does not specify how to concretely express locations, but instead provide a mechanism to introduce locations, by means of a reserved attribute. </p>
<p>
-The attribute <span class="name">prov:location</span> is an OPTIONAL attribute of <a>Entity</a>, <a>Activity</a>, <a>Agent</a>, <a>Usage</a>, <a>Generation</a>, <a>Invalidation</a>, <a>Start</a>, and <a>End</a>. The value associated with the attribute <span class="name">prov:location</span> MUST be a PROV-DM <a title="value">Value</a>, expected to denote a location.
+The attribute <span class="name">prov:location</span> is an <em class="rfc2119" title="OPTIONAL">OPTIONAL</em> attribute of <a href="#concept-entity" class="internalDFN">Entity</a>, <a href="#concept-activity" class="internalDFN">Activity</a>, <a href="#concept-agent" class="internalDFN">Agent</a>, <a href="#concept-usage" class="internalDFN">Usage</a>, <a href="#concept-generation" class="internalDFN">Generation</a>, <a href="#concept-invalidation" class="internalDFN">Invalidation</a>, <a href="#concept-start" class="internalDFN">Start</a>, and <a href="#concept-end" class="internalDFN">End</a>. The value associated with the attribute <span class="name">prov:location</span> <em class="rfc2119" title="MUST">MUST</em> be a PROV-DM <a title="value" href="#concept-value" class="internalDFN">Value</a>, expected to denote a location.
</p>
<p>While the attribute <span class="name">prov:location</span> is allowed for several PROV concepts, it may not make sense to use it in some cases. For example, an activity that describes the relocation of an entity will have start and end locations, as well as every place in between those points.</p>
-<div class="anexample" id="example-location">
+<div class="anexample" id="example-location"><div class="anexampleTitle">Example 49<sup><a class="internalDFN" href="#example-location"><span class="diamond"> ◊</span></a></sup></div>
<p>The following expression describes entity Mona Lisa, a painting, with a location attribute. </p>
-<pre class="codeexample">
- entity(ex:MonaLisa, [ prov:location="Le Louvre, Paris", prov:type="StillImage" ])
+<pre class="codeexample"> entity(ex:MonaLisa, [ prov:location="Le Louvre, Paris", prov:type="StillImage" ])
</pre>
<p>The following expression describes a cell, at coordinates (5,5), with value 10. </p>
-<pre class="codeexample">
- entity(ex:cell, [ prov:location="(5,5)", prov:value="10" %% xsd:integer ])
+<pre class="codeexample"> entity(ex:cell, [ prov:location="(5,5)", prov:value="10" %% xsd:integer ])
</pre>
</div>
</section>
@@ -3417,41 +3431,38 @@
<section id="term-attribute-role">
-<h4>prov:role</h4>
-
-
-<p><span class="glossary-ref" data-ref="glossary-role"></span></p>
+<h5><span class="secno">5.7.2.3 </span>prov:role</h5>
+
+
+<p><span class="glossary-ref"> A <dfn id="concept-role" class="internalDFN">role</dfn><sup><a class="internalDFN" href="#concept-role"><span class="diamond"> ◊</span></a></sup> 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>
<p>
-The attribute <span class="name">prov:role</span> is allowed to occur multiple times in a list of attribute-value pairs. The value associated with a <span class="name">prov:role</span> attribute MUST be a PROV-DM <a title="value">Value</a>.</p>
-
-<div class="anexample" id="anexample-role">
+The attribute <span class="name">prov:role</span> is allowed to occur multiple times in a list of attribute-value pairs. The value associated with a <span class="name">prov:role</span> attribute <em class="rfc2119" title="MUST">MUST</em> be a PROV-DM <a title="value" href="#concept-value" class="internalDFN">Value</a>.</p>
+
+<div class="anexample" id="anexample-role"><div class="anexampleTitle">Example 50<sup><a class="internalDFN" href="#anexample-role"><span class="diamond"> ◊</span></a></sup></div>
<p>The following activity is associated with an agent acting as the operator. </p>
-<pre class="codeexample">
- wasAssociatedWith(a, ag, [ prov:role="operator" ])
+<pre class="codeexample"> wasAssociatedWith(a, ag, [ prov:role="operator" ])
</pre>
<p>In the following expression, the activity <span class="name">ex:div01</span> used entity <span class="name">ex:cell</span> in the role of divisor.</p>
-<pre class="codeexample">
-used(ex:div01, ex:cell, [ prov:role="divisor" ])
+<pre class="codeexample">used(ex:div01, ex:cell, [ prov:role="divisor" ])
</pre>
</div>
</section>
<section id="term-attribute-type">
-<h4>prov:type</h4>
-
-<p><span class="glossary-ref" data-ref="glossary-type"></span></p>
+<h5><span class="secno">5.7.2.4 </span>prov:type</h5>
+
+<p><span class="glossary-ref"> The attribute <dfn id="concept-type" title="type" class="internalDFN"><span class="name">prov:type</span></dfn><sup><a class="internalDFN" href="#concept-type"><span class="diamond"> ◊</span></a></sup> provides further typing information for any construct with an optional set of attribute-value pairs. </span></p>
<p>
PROV-DM liberally
defines a type as a category of things having common characteristics. PROV-DM is agnostic about the representation of types, and only states that
-the value associated with a <span class="name">prov:type</span> attribute MUST be a PROV-DM <a title="value">Value</a>. The attribute <span class="name">prov:type</span>
+the value associated with a <span class="name">prov:type</span> attribute <em class="rfc2119" title="MUST">MUST</em> be a PROV-DM <a title="value" href="#concept-value" class="internalDFN">Value</a>. The attribute <span class="name">prov:type</span>
is allowed to occur multiple times.</p>
-<div class="anexample">
+<div class="anexample" id="example_51"><div class="anexampleTitle">Example 51<sup><a class="internalDFN" href="#example_51"><span class="diamond"> ◊</span></a></sup></div>
<p>The following describes an agent of type software agent.</p>
-<pre class="codeexample">
- agent(ag, [ prov:type='prov:SoftwareAgent' ])
+<pre class="codeexample"> agent(ag, [ prov:type='prov:SoftwareAgent' ])
</pre>
</div>
@@ -3459,39 +3470,38 @@
<table class="thinborder" style="margin-left: auto; margin-right: auto;">
-<caption id="prov-dm-predefined-types">PROV-DM Predefined Types</caption> <!-- Table 9 -->
-<tr><td><b>Type</b></td><td><b>Specification</b></td><td><b>Core concept</b></td></tr>
+<caption id="prov-dm-predefined-types"><span>Table 9<sup><a class="internalDFN" href="#prov-dm-predefined-types"><span class="diamond"> ◊:</span></a></sup> </span>PROV-DM Predefined Types</caption> <!-- Table 9 -->
+<tbody><tr><td><b>Type</b></td><td><b>Specification</b></td><td><b>Core concept</b></td></tr>
<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
-<tr><td><a title="dfn-prov:bundle"><span class="name">prov:Bundle</span></a></td><td><a class="section-ref" href="#term-bundle"><span>TBD</span></a></td><td><a>Entity</a></td></tr>
-<tr><td><a title="dfn-prov:collection"><span class="name">prov:Collection</span></a></td><td><a class="section-ref" href="#term-collection"><span>TBD</span></a></td><td><a>Entity</a></td></tr>
-<tr><td><a title="dfn-prov:emptyCollection"><span class="name">prov:EmptyCollection</span></a></td><td><a class="section-ref" href="#term-collection"><span>TBD</span></a></td><td><a>Entity</a></td></tr>
-<tr><td><a title="dfn-prov:organization"><span class="name">prov:Organization</span></a></td><td><a class="section-ref" href="#term-agent"><span>TBD</span></a></td><td><a>Agent</a></td></tr>
-<tr><td><a title="dfn-prov:person"><span class="name">prov:Person</span></a></td><td><a class="section-ref" href="#term-agent"><span>TBD</span></a></td><td><a>Agent</a></td></tr>
-<tr><td><a title="dfn-prov:plan"><span class="name">prov:Plan</span></a></td><td><a class="section-ref" href="#term-Association"><span>TBD</span></a></td><td><a>Entity</a></td></tr>
-<tr><td><a title="dfn-prov:primary-source"><span class="name">prov:PrimarySource</span></a></td><td><a class="section-ref" href="#term-primary-source"><span>TBD</span></a></td><td><a>Derivation</a></td></tr>
-<tr><td><a title="dfn-prov:quotation"><span class="name">prov:Quotation</span></a></td><td><a class="section-ref" href="#term-quotation"><span>TBD</span></a></td><td><a>Derivation</a></td></tr>
-<tr><td><a title="dfn-prov:revision"><span class="name">prov:Revision</span></a></td><td><a class="section-ref" href="#term-revision"><span>TBD</span></a></td><td><a>Derivation</a></td></tr>
-<tr><td><a title="dfn-prov:softwareAgent"><span class="name">prov:SoftwareAgent</span></a></td><td><a class="section-ref" href="#term-agent"><span>TBD</span></a></td><td><a>Agent</a></td></tr>
-</table>
+<tr><td><a title="dfn-prov:bundle" href="#dfn-prov:bundle" class="internalDFN"><span class="name">prov:Bundle</span></a></td><td><a class="section-ref" href="#term-bundle"><span>Section 5.4.1</span></a></td><td><a href="#concept-entity" class="internalDFN">Entity</a></td></tr>
+<tr><td><a title="dfn-prov:collection" href="#dfn-prov:collection" class="internalDFN"><span class="name">prov:Collection</span></a></td><td><a class="section-ref" href="#term-collection"><span>Section 5.6.1</span></a></td><td><a href="#concept-entity" class="internalDFN">Entity</a></td></tr>
+<tr><td><a title="dfn-prov:emptyCollection" href="#dfn-prov:emptyCollection" class="internalDFN"><span class="name">prov:EmptyCollection</span></a></td><td><a class="section-ref" href="#term-collection"><span>Section 5.6.1</span></a></td><td><a href="#concept-entity" class="internalDFN">Entity</a></td></tr>
+<tr><td><a title="dfn-prov:organization" href="#dfn-prov:organization" class="internalDFN"><span class="name">prov:Organization</span></a></td><td><a class="section-ref" href="#term-agent"><span>Section 5.3.1</span></a></td><td><a href="#concept-agent" class="internalDFN">Agent</a></td></tr>
+<tr><td><a title="dfn-prov:person" href="#dfn-prov:person" class="internalDFN"><span class="name">prov:Person</span></a></td><td><a class="section-ref" href="#term-agent"><span>Section 5.3.1</span></a></td><td><a href="#concept-agent" class="internalDFN">Agent</a></td></tr>
+<tr><td><a title="dfn-prov:plan" href="#dfn-prov:plan" class="internalDFN"><span class="name">prov:Plan</span></a></td><td><a class="section-ref" href="#term-Association"><span>Section 5.3.3</span></a></td><td><a href="#concept-entity" class="internalDFN">Entity</a></td></tr>
+<tr><td><a title="dfn-prov:primary-source" href="#dfn-prov:primary-source" class="internalDFN"><span class="name">prov:PrimarySource</span></a></td><td><a class="section-ref" href="#term-primary-source"><span>Section 5.2.4</span></a></td><td><a href="#concept-derivation" class="internalDFN">Derivation</a></td></tr>
+<tr><td><a title="dfn-prov:quotation" href="#dfn-prov:quotation" class="internalDFN"><span class="name">prov:Quotation</span></a></td><td><a class="section-ref" href="#term-quotation"><span>Section 5.2.3</span></a></td><td><a href="#concept-derivation" class="internalDFN">Derivation</a></td></tr>
+<tr><td><a title="dfn-prov:revision" href="#dfn-prov:revision" class="internalDFN"><span class="name">prov:Revision</span></a></td><td><a class="section-ref" href="#term-revision"><span>Section 5.2.2</span></a></td><td><a href="#concept-derivation" class="internalDFN">Derivation</a></td></tr>
+<tr><td><a title="dfn-prov:softwareAgent" href="#dfn-prov:softwareAgent" class="internalDFN"><span class="name">prov:SoftwareAgent</span></a></td><td><a class="section-ref" href="#term-agent"><span>Section 5.3.1</span></a></td><td><a href="#concept-agent" class="internalDFN">Agent</a></td></tr>
+</tbody></table>
</section>
<section id="term-attribute-value">
-<h4>prov:value</h4>
-
-<p><span class="glossary-ref" data-ref="glossary-value-attribute"></span></p>
-
-
-
-<p>The attribute <span class="name">prov:value</span> is an OPTIONAL attribute of entity. The value associated with the attribute <span class="name">prov:value</span> MUST be a PROV-DM <a title="value">Value</a>. The attribute <span class="name">prov:value</span> MAY occur at most once in a set of attribute-value pairs.</p>
-
-<div class="anexample" id="anexample-value1">
+<h5><span class="secno">5.7.2.5 </span>prov:value</h5>
+
+<p><span class="glossary-ref"> The attribute <dfn id="concept-value-attribute" title="value-attribute" class="internalDFN"><span class="name">prov:value</span></dfn><sup><a class="internalDFN" href="#concept-value-attribute"><span class="diamond"> ◊</span></a></sup> 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>
+
+
+
+<p>The attribute <span class="name">prov:value</span> is an <em class="rfc2119" title="OPTIONAL">OPTIONAL</em> attribute of entity. The value associated with the attribute <span class="name">prov:value</span> <em class="rfc2119" title="MUST">MUST</em> be a PROV-DM <a title="value" href="#concept-value" class="internalDFN">Value</a>. The attribute <span class="name">prov:value</span> <em class="rfc2119" title="MAY">MAY</em> occur at most once in a set of attribute-value pairs.</p>
+
+<div class="anexample" id="anexample-value1"><div class="anexampleTitle">Example 52<sup><a class="internalDFN" href="#anexample-value1"><span class="diamond"> ◊</span></a></sup></div>
<p>The following example illustrates the provenance of the number <span class="name">4</span> obtained by an activity that computed the length of an input string <span class="name">"abcd"</span>.
The input and the output are expressed as entities <span class="name">ex:in</span> and <span class="name">ex:out</span>, respectively. They each have a <span class="name">prov:value</span> attribute associated with the corresponding value.
</p>
-<pre class="codeexample">
-entity(ex:in, [ prov:value="abcd" ])
+<pre class="codeexample">entity(ex:in, [ prov:value="abcd" ])
entity(ex:out, [ prov:value=4 ])
activity(ex:len, [ prov:type="string-length" ])
used(ex:len, ex:in)
@@ -3501,18 +3511,17 @@
</div>
<p>
-Two different entities MAY have the same value for the attribute
+Two different entities <em class="rfc2119" title="MAY">MAY</em> have the same value for the attribute
prov:value. For instance,
when two entities, with the same prov:value, are generated by two
different activities, as illustrated
by the following example.</p>
-<div class="anexample" id="anexample-value2">
-<p><a href="#anexample-value1" class="anexample-ref"><span>Example REF</span></a> illustrates an entity with a given value
+<div class="anexample" id="anexample-value2"><div class="anexampleTitle">Example 53<sup><a class="internalDFN" href="#anexample-value2"><span class="diamond"> ◊</span></a></sup></div>
+<p><a href="#anexample-value1" class="anexample-ref"><span>Example 52</span></a> illustrates an entity with a given value
<span class="name">4</span>. This examples shows that another entity with the same value may be computed differently (by an addition).
</p>
-<pre class="codeexample">
-entity(ex:in1, [ prov:value=3 ])
+<pre class="codeexample">entity(ex:in1, [ prov:value=3 ])
entity(ex:in2, [ prov:value=1 ])
entity(ex:out2, [ prov:value=4 ]) // ex:out2 also has value 4
activity(ex:add1, [ prov:type="addition" ])
@@ -3530,15 +3539,15 @@
</section>
<section id="term-value">
-<h4>Value</h4>
-
-<p><span class="glossary-ref" data-ref="glossary-value"></span> Values can occur in attribute-value pairs. </p>
+<h4><span class="secno">5.7.3 </span>Value</h4>
+
+<p><span class="glossary-ref"> A <dfn id="concept-value" title="value" class="internalDFN">value</dfn><sup><a class="internalDFN" href="#concept-value"><span class="diamond"> ◊</span></a></sup> 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> Values can occur in attribute-value pairs. </p>
<p>Each kind of such values is called a <em>datatype</em>.
- Use of the following data types is RECOMMENDED. </p>
+ Use of the following data types is <em class="rfc2119" title="RECOMMENDED">RECOMMENDED</em>. </p>
<ul>
-<li> The RDF-compatible [[!RDF-CONCEPTS]] types, including those taken from
-the set of XML Schema Datatypes [[!XMLSCHEMA11-2]];</li>
+<li> The RDF-compatible [<cite><a class="bibref" href="#bib-RDF-CONCEPTS">RDF-CONCEPTS</a></cite>] types, including those taken from
+the set of XML Schema Datatypes [<cite><a class="bibref" href="#bib-XMLSCHEMA11-2">XMLSCHEMA11-2</a></cite>];</li>
<li> Qualified names introduced in this specification.</li>
</ul>
<p>
@@ -3547,36 +3556,35 @@
-<p id="conformance-to-rdf-datatypes"><b>Conformance to RDF Datatypes</b> As of the publication of this document, RDF 1.1 Concepts and Abstract Syntax [[RDF-CONCEPTS11]] is not yet a W3C Recommendation (see <a href="http://www.w3.org/TR/rdf11-concepts/">http://www.w3.org/TR/rdf11-concepts/</a> for the latest version).
-Both the Provenance Working Group and the RDF Working Group are confident that there will be only minor changes before it becomes a W3C Recommendation. In order to take advantage of the anticipated corrections and new features sooner, while also providing stability in case the specification does not advance as expected, conformance to PROV as it relates to RDF Datatypes is defined as follows:</p>
+<p id="conformance-to-rdf-datatypes"><b>Conformance to RDF Datatypes</b> As of the publication of this document, RDF 1.1 Concepts and Abstract Syntax [<cite><a class="bibref" href="#bib-RDF-CONCEPTS11">RDF-CONCEPTS11</a></cite>] is not yet a <abbr title="World Wide Web Consortium">W3C</abbr> Recommendation (see <a href="http://www.w3.org/TR/rdf11-concepts/">http://www.w3.org/TR/rdf11-concepts/</a> for the latest version).
+Both the Provenance Working Group and the RDF Working Group are confident that there will be only minor changes before it becomes a <abbr title="World Wide Web Consortium">W3C</abbr> Recommendation. In order to take advantage of the anticipated corrections and new features sooner, while also providing stability in case the specification does not advance as expected, conformance to PROV as it relates to RDF Datatypes is defined as follows:</p>
<ul>
-<li>If RDF 1.1 Concepts and Abstract Syntax becomes a W3C Recommendation, all references in PROV to
+<li>If RDF 1.1 Concepts and Abstract Syntax becomes a <abbr title="World Wide Web Consortium">W3C</abbr> Recommendation, all references in PROV to
RDF Concepts and Abstract Syntax will be normative references to the 1.1 Recommendation.
-<li>Until that time, references in PROV to RDF Concepts and Abstract Syntax features operate as follows:
+</li><li>Until that time, references in PROV to RDF Concepts and Abstract Syntax features operate as follows:
<ul>
-<li> If RDF 1.0 defines the features, then the reference is normative to the 1.0 definition [[!RDF-CONCEPTS]];</li>
+<li> If RDF 1.0 defines the features, then the reference is normative to the 1.0 definition [<cite><a class="bibref" href="#bib-RDF-CONCEPTS">RDF-CONCEPTS</a></cite>];</li>
<li>otherwise, the feature is optional in PROV and the reference is informative only.</li>
</ul>
-</ul>
-<p>This "change in normative reference" is effective as of the publication of RDF 1.1 as a W3C Recommendation. However, W3C expects to publish a new edition of PROV once RDF 1.1 becomes a Recommendation to update the reference explicitly.</p>
-
-
-
-
-
-
-<div class="anexample" id="anexample-value">
+</li></ul>
+<p>This "change in normative reference" is effective as of the publication of RDF 1.1 as a <abbr title="World Wide Web Consortium">W3C</abbr> Recommendation. However, <abbr title="World Wide Web Consortium">W3C</abbr> expects to publish a new edition of PROV once RDF 1.1 becomes a Recommendation to update the reference explicitly.</p>
+
+
+
+
+
+
+<div class="anexample" id="anexample-value"><div class="anexampleTitle">Example 54<sup><a class="internalDFN" href="#anexample-value"><span class="diamond"> ◊</span></a></sup></div>
<p>
The following examples respectively are the string "abc", the integer number 1, and the IRI "http://example.org/foo".
-<pre class="codeexample">
- "abc"
+</p><pre class="codeexample"> "abc"
"1" %% xsd:integer
"http://example.org/foo" %% xsd:anyURI
</pre>
<p>The following example shows a value of type <span class="name">prov:QUALIFIED_NAME</span> (see
-<span class="name"><a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/#prod-QUALIFIED_NAME">prov:QUALIFIED_NAME</a></span> [[!PROV-N]]).
-The prefix <span class="name">ex</span> must be bound to a <a>namespace</a> declared in a <a>namespace declaration</a>.</p>
+<span class="name"><a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/#prod-QUALIFIED_NAME">prov:QUALIFIED_NAME</a></span> [<cite><a class="bibref" href="#bib-PROV-N">PROV-N</a></cite>]).
+The prefix <span class="name">ex</span> must be bound to a <a href="#dfn-namespace" class="internalDFN">namespace</a> declared in a <a href="#dfn-namespaceDeclaration" class="internalDFN">namespace declaration</a>.</p>
<pre class="codeexample">
"ex:value" %% prov:QUALIFIED_NAME
</pre>
@@ -3586,13 +3594,13 @@
</pre>
</div>
-<p>We note that PROV <dfn title="time">time instants</dfn> are defined according to xsd:dateTime [[!XMLSCHEMA11-2]].</p>
-
-
-<div class="anexample" id="anexample-time">
+<p>We note that PROV <dfn title="time" id="dfn-time" class="internalDFN">time instants</dfn><sup><a class="internalDFN" href="#dfn-time"><span class="diamond"> ◊</span></a></sup> are defined according to xsd:dateTime [<cite><a class="bibref" href="#bib-XMLSCHEMA11-2">XMLSCHEMA11-2</a></cite>].</p>
+
+
+<div class="anexample" id="anexample-time"><div class="anexampleTitle">Example 55<sup><a class="internalDFN" href="#anexample-time"><span class="diamond"> ◊</span></a></sup></div>
<p>
In the following example, the generation time of entity <span class="name">e1</span> is expressed according to
-<a href="http://www.w3.org/TR/xmlschema11-2/#dateTime">xsd:dateTime</a> [[!XMLSCHEMA11-2]].</p>
+<a href="http://www.w3.org/TR/xmlschema11-2/#dateTime">xsd:dateTime</a> [<cite><a class="bibref" href="#bib-XMLSCHEMA11-2">XMLSCHEMA11-2</a></cite>].</p>
<pre class="codeexample">
wasGeneratedBy(e1,a1, 2001-10-26T21:32:52)
</pre>
@@ -3601,33 +3609,33 @@
</section>
<section id="term-NamespaceDeclaration">
-<h3>Namespace Declaration</h3>
-
-<p>A <dfn id="dfn-namespace">namespace</dfn> is identified by an IRI [[!RFC3987]]. In PROV-DM, attributes, identifiers, and values with <a title="qualified name">qualified names</a> as data type can be placed in a namespace using the mechanisms described in this specification. </p>
-
-
-<p>A <dfn id="dfn-namespaceDeclaration">namespace declaration</dfn> consists of a binding between a prefix and a namespace. Every qualified name with this prefix in the scope of this
+<h4><span class="secno">5.7.4 </span>Namespace Declaration</h4>
+
+<p>A <dfn id="dfn-namespace" class="internalDFN">namespace</dfn><sup><a class="internalDFN" href="#dfn-namespace"><span class="diamond"> ◊</span></a></sup> is identified by an IRI [<cite><a class="bibref" href="#bib-RFC3987">RFC3987</a></cite>]. In PROV-DM, attributes, identifiers, and values with <a title="qualified name" href="#concept-qualifiedName" class="internalDFN">qualified names</a> as data type can be placed in a namespace using the mechanisms described in this specification. </p>
+
+
+<p>A <dfn id="dfn-namespaceDeclaration" class="internalDFN">namespace declaration</dfn><sup><a class="internalDFN" href="#dfn-namespaceDeclaration"><span class="diamond"> ◊</span></a></sup> consists of a binding between a prefix and a namespace. Every qualified name with this prefix in the scope of this
declaration refers to this namespace. </p>
-<p>A <dfn id="dfn-defaultNamespaceDeclaration">default namespace declaration</dfn> consists of a namespace. Every un-prefixed qualified name
+<p>A <dfn id="dfn-defaultNamespaceDeclaration" class="internalDFN">default namespace declaration</dfn><sup><a class="internalDFN" href="#dfn-defaultNamespaceDeclaration"><span class="diamond"> ◊</span></a></sup> consists of a namespace. Every un-prefixed qualified name
refers to default namespace declaration.</p>
-<p>The <dfn title="prov-namespace">PROV namespace</dfn> is identified by the IRI <a href="http://www.w3.org/ns/prov#">http://www.w3.org/ns/prov#</a>.</p>
+<p>The <dfn title="prov-namespace" id="dfn-prov-namespace" class="internalDFN">PROV namespace</dfn><sup><a class="internalDFN" href="#dfn-prov-namespace"><span class="diamond"> ◊</span></a></sup> is identified by the IRI <a href="http://www.w3.org/ns/prov#">http://www.w3.org/ns/prov#</a>.</p>
</section>
<section id="term-qualified-name">
-<h4>Qualified Name</h4>
-
-
-<span class="glossary-ref" data-ref="glossary-qualifiedName"></span>
+<h4><span class="secno">5.7.5 </span>Qualified Name</h4>
+
+
+<span class="glossary-ref"> A <dfn id="concept-qualifiedName" class="internalDFN">qualified name</dfn><sup><a class="internalDFN" href="#concept-qualifiedName"><span class="diamond"> ◊</span></a></sup> is a name subject to namespace interpretation. It consists of a namespace, denoted by an optional prefix, and a local name. </span>
<p>PROV-DM stipulates that a qualified name can be mapped into an IRI
by concatenating the IRI associated with the prefix and the local part.</p>
-<p>A qualified name's prefix is OPTIONAL. If a prefix occurs in a
- qualified name, it refers to a <a>namespace</a> declared in a namespace declaration. In the absence of prefix, the qualified name
- refers to the <a title="default namespace declaration">default namespace</a>.</p>
+<p>A qualified name's prefix is <em class="rfc2119" title="OPTIONAL">OPTIONAL</em>. If a prefix occurs in a
+ qualified name, it refers to a <a href="#dfn-namespace" class="internalDFN">namespace</a> declared in a namespace declaration. In the absence of prefix, the qualified name
+ refers to the <a title="default namespace declaration" href="#dfn-defaultNamespaceDeclaration" class="internalDFN">default namespace</a>.</p>
</section>
@@ -3641,32 +3649,31 @@
<!-- end sec. 5 -->
<section id="extensibility-section">
-<h2>PROV-DM Extensibility Points</h2>
+<!--OddPage--><h2><span class="secno">6. </span>PROV-DM Extensibility Points</h2>
<p>The PROV data model provides extensibility points that allow designers to specialize it for specific applications or domains. We summarize these extensibility points here. </p>
-<p>The <a title="prov-namespace">PROV namespace</a> declares a set of reserved attributes catering for extensibility: <a href="#term-attribute-type"><span class="name">prov:type</span></a>, <a href="#term-attribute-role"><span class="name">prov:role</span></a>, <a href="#term-attribute-location"><span
-class="name">prov:location</span></a>.</p>
+<p>The <a title="prov-namespace" href="#dfn-prov-namespace" class="internalDFN">PROV namespace</a> declares a set of reserved attributes catering for extensibility: <a href="#term-attribute-type"><span class="name">prov:type</span></a>, <a href="#term-attribute-role"><span class="name">prov:role</span></a>, <a href="#term-attribute-location"><span class="name">prov:location</span></a>.</p>
<ul>
<li>Sub-types and sub-relations can be expressed by means of the reserved attribute
<a href="#term-attribute-type"><span class="name">prov:type</span></a>.
-<div class="anexample" id="anexample-sub-relation">
+<div class="anexample" id="anexample-sub-relation"><div class="anexampleTitle">Example 56<sup><a class="internalDFN" href="#anexample-sub-relation"><span class="diamond"> ◊</span></a></sup></div>
<p>
In the following example, <span class="name">e2</span> is a translation of <span class="name">e1</span>,
expressed as a sub-type of derivation.
-<pre class="codeexample">
+</p><pre class="codeexample">
wasDerivedFrom(e2,e1, [prov:type='ex:Translation' ])
</pre>
</div>
-<div class="anexample" id="anexample-sub-type">
+<div class="anexample" id="anexample-sub-type"><div class="anexampleTitle">Example 57<sup><a class="internalDFN" href="#anexample-sub-type"><span class="diamond"> ◊</span></a></sup></div>
<p>
In the following example, <span class="name">e</span> is described as a Car, a type of entity.
-<pre class="codeexample">
+</p><pre class="codeexample">
entity(e, [prov:type='ex:Car' ])
</pre>
</div>
@@ -3679,10 +3686,10 @@
<li>Application and domain specific roles can be expressed by means of the reserved attribute
<a href="#term-attribute-role"><span class="name">prov:role</span></a>.
-<div class="anexample" id="anexample-usage-with-role">
+<div class="anexample" id="anexample-usage-with-role"><div class="anexampleTitle">Example 58<sup><a class="internalDFN" href="#anexample-usage-with-role"><span class="diamond"> ◊</span></a></sup></div>
<p>
In the following example, two computers <span class="name">ex:laptop4</span> and <span class="name">ex:desktop9</span> are used in different roles in a work activity.
-<pre class="codeexample">
+</p><pre class="codeexample">
activity(ex:work)
entity(ex:laptop4)
entity(ex:desktop9)
@@ -3702,7 +3709,7 @@
</ul>
<p>The PROV data model is designed to be application and technology independent, but implementers are welcome and encouraged to specialize PROV-DM to specific domains and applications. To ensure interoperability, specializations of
-the PROV data model that exploit the extensibility points summarized in this section must preserve the semantics specified in this document and in [[!PROV-CONSTRAINTS]]. </p>
+the PROV data model that exploit the extensibility points summarized in this section must preserve the semantics specified in this document and in [<cite><a class="bibref" href="#bib-PROV-CONSTRAINTS">PROV-CONSTRAINTS</a></cite>]. </p>
@@ -3711,7 +3718,7 @@
<section id="valid-provenance">
-<h4>Creating Valid Provenance</h4>
+<!--OddPage--><h2><span class="secno">7. </span>Creating Valid Provenance</h2>
<p>This specification defines PROV-DM, a data model that allows
descriptions of the people, institutions, entities, and activities,
@@ -3721,8 +3728,8 @@
express that an entity was used before it was generated, or that the
activity that generated an entity started after the entity
generation. A set of constraints have been defined for PROV and
-can be found in a companion specification [[!PROV-CONSTRAINTS]].
-They SHOULD be used by developers to compose provenance descriptions that are valid, and
+can be found in a companion specification [<cite><a class="bibref" href="#bib-PROV-CONSTRAINTS">PROV-CONSTRAINTS</a></cite>].
+They <em class="rfc2119" title="SHOULD">SHOULD</em> be used by developers to compose provenance descriptions that are valid, and
by implementers of reasoning engines aiming to check whether provenance descriptions have problems. </p>
@@ -3730,74 +3737,70 @@
<p> The example of <a href="#prov-dm-example">section 3</a> contains identifiers such as <span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111215">tr:WD-prov-dm-20111215</a></span>, which denotes a specific version of a technical report. On the other hand, an IRI such as <a href="http://www.w3.org/TR/prov-dm/">http://www.w3.org/TR/prov-dm/</a> denotes the latest version of a document. One needs to ensure that provenance descriptions for the latter resource remain valid as the resource state changes. </p>
-<p>To this end, PROV allows asserters to describe "<em>partial states</em>" of entities by means of attributes and associated values. Some further constraints apply to the use of these attributes, since the values associated with them are expected to remain unchanged for some period of time. The constraints associated to attributes allow provenance descriptions to be refined, they can also be found in the companion specification [[!PROV-CONSTRAINTS]].</p>
+<p>To this end, PROV allows asserters to describe "<em>partial states</em>" of entities by means of attributes and associated values. Some further constraints apply to the use of these attributes, since the values associated with them are expected to remain unchanged for some period of time. The constraints associated to attributes allow provenance descriptions to be refined, they can also be found in the companion specification [<cite><a class="bibref" href="#bib-PROV-CONSTRAINTS">PROV-CONSTRAINTS</a></cite>].</p>
</section>
-<div id="glossary_div" class="remove">
-<!-- glossary loaded from glossary.js will be hooked up here,
- class remove, will remove this element from the final output.
--->
-</div>
-
-<section class="appendix">
-<h2>Cross-References to PROV-O and PROV-N</h2>
+
+
+<section class="appendix" id="cross-references-to-prov-o-and-prov-n">
+<!--OddPage--><h2><span class="secno">A. </span>Cross-References to PROV-O and PROV-N</h2>
<p>PROV-DM is a conceptual data model which can be serialized in various ways.
-The following table contains the PROV-O classes and properties, as described in [[!PROV-O]], and PROV-N productions, as described in [[!PROV-N]] that correspond to PROV-DM concepts.</p>
+The following table contains the PROV-O classes and properties, as described in [<cite><a class="bibref" href="#bib-PROV-O">PROV-O</a></cite>], and PROV-N productions, as described in [<cite><a class="bibref" href="#bib-PROV-N">PROV-N</a></cite>] that correspond to PROV-DM concepts.</p>
<div id="prov-dm-to-prov-o-and-prov-n-fig" style="text-align: left;">
-<table class="thinborder" style="margin-left: auto; margin-right: auto;">
-<caption id="prov-dm-to-prov-o-and-prov-n">Cross-References to PROV-O and PROV-N</caption> <!-- Table 10-->
-<tr><td><b>PROV-DM</b></td><td><b>PROV-O</b></td><td><b>PROV-N</b></td><td><b>Component</b></td></tr>
+<table class="thinborder" style="margin-left: auto; margin-right: auto;">
+<caption id="prov-dm-to-prov-o-and-prov-n"><span>Table 10<sup><a class="internalDFN" href="#prov-dm-to-prov-o-and-prov-n"><span class="diamond"> ◊:</span></a></sup> </span>Cross-References to PROV-O and PROV-N</caption> <!-- Table 10-->
+<tbody><tr><td><b>PROV-DM</b></td><td><b>PROV-O</b></td><td><b>PROV-N</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><td style="border-width: 0px; "></td></tr>
<tr class="component1-color">
-<td><a title="Entity">Entity</a></td>
+<td><a title="Entity" href="#concept-entity" class="internalDFN">Entity</a></td>
<td><a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/#Entity">Entity</a></td>
<td><code><a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/#prod-entityExpression">entityExpression</a></code>
</td><td rowspan="8"><a href="#component1">Component 1:<br> Entities/Activities</a></td></tr>
<tr class="component1-color">
-<td><a title="Activity">Activity</a></td>
+<td><a title="Activity" href="#concept-activity" class="internalDFN">Activity</a></td>
<td><a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/#Entity">Activity</a></td>
<td><code><a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/#prod-activityExpression">activityExpression</a></code></td>
</tr>
<tr class="component1-color">
-<td><a title="Generation">Generation</a></td>
+<td><a title="Generation" href="#concept-generation" class="internalDFN">Generation</a></td>
<td><a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/#wasGeneratedBy">wasGeneratedBy</a>, <a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/#Generation">Generation</a></td>
<td><code><a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/#prod-generationExpression">generationExpression</a></code></td>
</tr>
<tr class="component1-color">
-<td><a title="Usage">Usage</a></td>
+<td><a title="Usage" href="#concept-usage" class="internalDFN">Usage</a></td>
<td><a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/#used">used</a>, <a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/#Usage">Usage</a></td>
<td><code><a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/#prod-usageExpression">usageExpression</a></code></td>
</tr>
<tr class="component1-color">
-<td><a title="Communication">Communication</a></td>
+<td><a title="Communication" href="#concept-communication" class="internalDFN">Communication</a></td>
<td><a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/#wasInformedBy">wasInformedBy</a>, <a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/#Communication">Communication</a></td>
<td><code><a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/#prod-communicationExpression">communicationExpression</a></code></td>
</tr>
<tr class="component1-color">
-<td><a title="Start">Start</a></td>
+<td><a title="Start" href="#concept-start" class="internalDFN">Start</a></td>
<td><a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/#wasStartedBy">wasStartedBy</a>, <a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/#Start">Start</a></td>
<td><code><a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/#prod-startExpression">startExpression</a></code></td>
</tr>
<tr class="component1-color">
-<td><a title="End">End</a></td>
+<td><a title="End" href="#concept-end" class="internalDFN">End</a></td>
<td><a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/#wasEndedBy">wasEndedBy</a>, <a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/#End">End</a></td>
<td><code><a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/#prod-endExpression">endExpression</a></code></td>
</tr>
<tr class="component1-color">
-<td><a title="Invalidation">Invalidation</a></td>
+<td><a title="Invalidation" href="#concept-invalidation" class="internalDFN">Invalidation</a></td>
<td><a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/#wasInvalidatedBy">wasInvalidatedBy</a>, <a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/#Invalidation">Invalidation</a></td>
<td><code><a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/#prod-invalidationExpression">invalidationExpression</a></code></td>
</tr>
@@ -3807,25 +3810,25 @@
<tr class="component2-color">
-<td><a title="Derivation">Derivation</a></td>
+<td><a title="Derivation" href="#concept-derivation" class="internalDFN">Derivation</a></td>
<td><a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/#wasDerivedFrom">wasDerivedFrom</a>, <a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/#Derivation">Derivation</a></td>
<td><code><a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/#prod-derivationExpression">derivationExpression</a></code></td>
-<td rowspan="4"><a href="#component2">Component 2:<br> Derivations</a></td>
+<td rowspan="4"><a href="#component2">Component 2:<br> Derivations</a></td>
</tr>
<tr class="component2-color">
-<td class="provType"><a title="Revision">Revision</a></td>
+<td class="provType"><a title="Revision" href="#concept-revision" class="internalDFN">Revision</a></td>
<td><a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/#wasRevisionOf">wasRevisionOf</a>, <a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/#Revision">Revision</a></td>
<td>type <code><a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/#provn-type-Revision">Revision</a></code></td>
</tr>
<tr class="component2-color">
-<td class="provType"><a title="Quotation">Quotation</a></td>
+<td class="provType"><a title="Quotation" href="#concept-quotation" class="internalDFN">Quotation</a></td>
<td><a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/#wasQuotedFrom">wasQuotedFrom</a>, <a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/#Quotation">Quotation</a></td>
<td>type <code><a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/#provn-type-Quotation">Quotation</a></code></td>
</tr>
-<tr class="component2-color"><td class="provType"><a title="Primary Source">Primary Source</a></td>
+<tr class="component2-color"><td class="provType"><a title="Primary Source" href="#concept-primary-source" class="internalDFN">Primary Source</a></td>
<td><a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/#hadPrimarySource">hadPrimarySource</a>, <a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/#PrimarySource">PrimarySource</a></td>
<td>type <code><a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/#provn-type-Primary-Source">PrimarySource</a></code></td>
</tr>
@@ -3835,38 +3838,38 @@
<tr class="component3-color" style="border-collapse: collapse; ">
-<td><a title="Agent">Agent</a></td>
+<td><a title="Agent" href="#concept-agent" class="internalDFN">Agent</a></td>
<td><a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/#Agent">Agent</a></td>
<td><code><a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/#prod-agentExpression">agentExpression</a></code></td>
-<td rowspan="9"><a href="#component3">Component 3: <br>Agents, Responsibility, <br>Influence</a></td>
+<td rowspan="9"><a href="#component3">Component 3: <br>Agents, Responsibility, <br>Influence</a></td>
</tr>
<tr class="component3-color">
-<td><a title="Attribution">Attribution</a></td>
+<td><a title="Attribution" href="#concept-attribution" class="internalDFN">Attribution</a></td>
<td><a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/#wasAttributedTo">wasAttributedTo</a>, <a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/#Attribution">Attribution</a></td>
<td><code><a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/#prod-attributionExpression">attributionExpression</a></code></td>
</tr>
<tr class="component3-color">
-<td><a title="Association">Association</a></td>
+<td><a title="Association" href="#concept-association" class="internalDFN">Association</a></td>
<td><a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/#wasAssociatedWith">wasAssociatedWith</a>, <a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/#Association">Association</a></td>
<td><code><a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/#prod-associationExpression">associationExpression</a></code></td>
</tr>
<tr class="component3-color">
-<td><a title="Delegation">Delegation</a></td>
+<td><a title="Delegation" href="#concept-delegation" class="internalDFN">Delegation</a></td>
<td><a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/#actedOnBehalfOf">actedOnBehalfOf</a>, <a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/#Delegation">Delegation</a></td>
<td><code><a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/#prod-delegationExpression">delegationExpression</a></code></td>
</tr>
<tr class="component3-color">
-<td><a title="Plan">Plan</a></td>
+<td><a title="Plan" href="#concept-plan" class="internalDFN">Plan</a></td>
<td><a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/#Plan">Plan</a></td>
<td>type <code><a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/#provn-type-Plan">Plan</a></code></td>
</tr>
<tr class="component3-color">
-<td><a title="Person">Person</a></td>
+<td><a title="Person" href="#concept-person" class="internalDFN">Person</a></td>
<td><a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/#Person">Person</a></td>
<td>type <code><a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/#provn-type-Person">Person</a></code></td>
</tr>
@@ -3878,13 +3881,13 @@
</tr>
<tr class="component3-color">
-<td><a title="software-agent">SoftwareAgent</a></td>
+<td><a title="software-agent" href="#concept-software-agent" class="internalDFN">SoftwareAgent</a></td>
<td><a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/#SoftwareAgent">SoftwareAgent</a></td>
<td>type <code><a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/#provn-type-SoftwareAgent">SoftwareAgent</a></code></td>
</tr>
<tr class="component3-color">
-<td><a title="Influence">Influence</a></td>
+<td><a title="Influence" href="#concept-influence" class="internalDFN">Influence</a></td>
<td><a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/#wasInfluencedBy">wasInfluencedBy</a>, <a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/#Influence">Influence</a></td>
<td><code><a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/#prod-influenceExpression">influenceExpression</a></code></td>
</tr>
@@ -3895,13 +3898,13 @@
<tr class="component4-color">
-<td><a title="Bundle">Bundle constructor</a></td>
+<td><a title="Bundle" href="#concept-bundle" class="internalDFN">Bundle constructor</a></td>
<td> <a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/#description-bundle">bundle description</a> </td>
<td><code><a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/#prod-bundle">bundle</a></code></td>
-<td rowspan="2"><a href="#component5">Component 4: <br> Bundles</a></td>
+<td rowspan="2"><a href="#component4">Component 4: <br> Bundles</a></td>
</tr>
-<tr class="component4-color"><td class="provType"><a title="Bundle Type">Bundle type</a></td>
+<tr class="component4-color"><td class="provType"><a title="Bundle Type" href="#dfn-bundle-type" class="internalDFN">Bundle type</a></td>
<td><a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/#Bundle">Bundle</a></td>
<td>type <code><a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/#provn-type-Bundle">Bundle</a></code></td>
</tr>
@@ -3910,14 +3913,14 @@
</tr>
<tr class="component5-color">
-<td><a title="Alternate">Alternate</a></td>
+<td><a title="Alternate" href="#concept-alternate" class="internalDFN">Alternate</a></td>
<td><a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/#alternateOf">alternateOf</a></td>
<td><code><a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/#prod-alternateExpression">alternateExpression</a></code></td>
-<td rowspan="2"><a href="#component4">Component 5: <br> Alternate</a></td>
+<td rowspan="2"><a href="#component5">Component 5: <br> Alternate</a></td>
</tr>
<tr class="component5-color">
-<td><a title="Specialization">Specialization</a></td>
+<td><a title="Specialization" href="#concept-specialization" class="internalDFN">Specialization</a></td>
<td><a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/#specializationOf">specializationOf</a></td>
<td><code><a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/#prod-specializationExpression">specializationExpression</a></code></td>
</tr>
@@ -3926,101 +3929,102 @@
</tr>
<tr class="component6-color">
-<td><a title="Collection">Collection</a></td>
+<td><a title="Collection" href="#concept-collection" class="internalDFN">Collection</a></td>
<td><a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/#Collection">Collection</a></td>
<td>type <code><a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/#provn-type-Collection">Collection</a></code></td>
-<td rowspan="3"><a href="#component6">Component 6: <br> Collections</a></td>
+<td rowspan="3"><a href="#component6">Component 6: <br> Collections</a></td>
</tr>
<tr class="component6-color">
-<td><a title="Empty Collection">EmptyCollection</a></td>
+<td><a title="Empty Collection" href="#concept-empty-collection" class="internalDFN">EmptyCollection</a></td>
<td><a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/#EmptyCollection">EmptyCollection</a></td>
<td>type <code><a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/#provn-type-EmptyCollection">EmptyCollection</a></code></td>
</tr>
<tr class="component6-color">
-<td><a title="Membership">Membership</a></td>
+<td><a title="Membership" href="#concept-membership" class="internalDFN">Membership</a></td>
<td><a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/#hadMember">hadMember</a></td>
<td><code><a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/#prod-membershipExpression">membershipExpression</a></code></td>
</tr>
-</table>
+</tbody></table>
</div>
</section>
-<section class="appendix">
- <h2>Change Log</h2>
-
-<section>
- <h2>Changes since Proposed Recommendation</h2>
+<section class="appendix" id="change-log">
+ <!--OddPage--><h2><span class="secno">B. </span>Change Log</h2>
+
+<section id="changes-since-proposed-recommendation">
+ <h3><span class="secno">B.1 </span>Changes since Proposed Recommendation</h3>
<ul>
<li> Changed the status of this document section.
-<li> Changed all URLs to PROV documents.
-<li> <a href="http://www.w3.org/2011/prov/track/issues/653">ISSUE-653</a>: Fixed typo in example to ensure compatibility with prov-n grammar.
-<li> Fixed capitalization in definition of software agent, organization, and person.
+</li><li> Changed all URLs to PROV documents.
+</li><li> <a href="http://www.w3.org/2011/prov/track/issues/653">ISSUE-653</a>: Fixed typo in example to ensure compatibility with prov-n grammar.
+</li><li> Fixed capitalization in definition of software agent, organization, and person.
+</li>
</ul>
</section>
-<section>
- <h2>Changes since Candidate Recommendation</h2>
+<section id="changes-since-candidate-recommendation">
+ <h3><span class="secno">B.2 </span>Changes since Candidate Recommendation</h3>
<ul>
<li> Checked all internal fragments resolved.
-<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> Changed all URLs to PROV documents.
-<li> Fixed links to internal anchors, following change in respec.js
-<li> Added anchors for prov:Bundle, prov:Collection, prov:Emptycollection, prov:Plan, prov:Person, prov:SoftwareAgent, prov:Organization, to facilitate systematic cross-referencing.
-<li> Likewise, added anchor for Bundle Type.
-<li> Table 9: fixed section number where plan is defined.
-<li> Added html link to provenance.
-</ul>
+</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> Fixed links to internal anchors, following change in respec.js
+</li><li> Added anchors for prov:Bundle, prov:Collection, prov:Emptycollection, prov:Plan, prov:Person, prov:SoftwareAgent, prov:Organization, to facilitate systematic cross-referencing.
+</li><li> Likewise, added anchor for Bundle Type.
+</li><li> Table 9: fixed section number where plan is defined.
+</li><li> Added html link to provenance.
+</li></ul>
</section>
-<section>
- <h2>Changes since Last Call</h2>
+<section id="changes-since-last-call">
+ <h3><span class="secno">B.3 </span>Changes since Last Call</h3>
<p> Please see the <a href="http://www.w3.org/2011/prov/wiki/ResponsesToPublicComments">Responses to Public Comments on the Last Call Working Draft</a> for more details about the justification of these changes.</p>
<ul>
<li> <a href="http://www.w3.org/2011/prov/track/issues/506">ISSUE-506</a>: Updated role from author to contributor, in line with text.
-<li> <a href="http://www.w3.org/2011/prov/track/issues/492">ISSUE-492</a>: Fixed typos in <a href="#anexample-invalidation3" class="anexample-ref"><span>Example REF</span></a>.
-<li> <a href="http://www.w3.org/2011/prov/track/issues/508">ISSUE-508</a>: Clarified the bold names and parameters in text preceding <a href="#prov-dm-types-and-relations-fig">Table 5</a>.
-<li> <a href="http://www.w3.org/2011/prov/track/issues/501">ISSUE-501</a>: Put the example about driving a car to Boston in a box.
-<li> <a href="http://www.w3.org/2011/prov/track/issues/450">ISSUE-450</a>, <a href="http://www.w3.org/2011/prov/track/issues/514">ISSUE-514</a>: added table with secondary objects in relations.
-<li> <a href="http://www.w3.org/2011/prov/track/issues/512">ISSUE-512</a>: simplied type of activity a2 to "fine paying"
-<li> <a href="http://www.w3.org/2011/prov/track/issues/509">ISSUE-509</a>: modified the introductory text to UML figures, so that they refer to relation names (e.g. WasStartedBy) as visualized in figures
-<li> <a href="http://www.w3.org/2011/prov/track/issues/515">ISSUE-515</a>: fixed typo
-<li> <a href="http://www.w3.org/2011/prov/track/issues/531">ISSUE-531</a>: added sentence on the use of prov:location attribute.
-
-<li> <a href="http://www.w3.org/2011/prov/track/issues/519">ISSUE-519</a>, <a href="http://www.w3.org/2011/prov/track/issues/523">ISSUE-523</a>, <a href="http://www.w3.org/2011/prov/track/issues/524">ISSUE-524</a>, <a href="http://www.w3.org/2011/prov/track/issues/529">ISSUE-529</a>: changed UML diagram of figure 8 by removing explicit inheritance from influence for usage, start, end, generation, invalidation, communication, derivation, attribution, association, and delegation. Instead, introduced correspondance table 7. Furthermore, in response to these issues, it was made clear that PROV defines no attribute specific to subtypes such as SoftwareAgent, ..., Plan, Revision, Bundle, Collection.
-<li> <a href="http://www.w3.org/2011/prov/track/issues/495">ISSUE-495</a>: made explicit which section, figure, table was informative or normative.
-<li> <a href="http://www.w3.org/2011/prov/track/issues/521">ISSUE-521</a>: now states that "an agent relied on a plan" instead of "an agent adopted a plan".
-<li> <a href="http://www.w3.org/2011/prov/track/issues/499">ISSUE-499</a>: Made explicit that generation/usage/invalidation/start/end are implicit.
-<li> <a href="http://www.w3.org/2011/prov/track/issues/449">ISSUE-449</a>: Clarified definition of prov:value attribute and added an example.
-<li> <a href="http://www.w3.org/2011/prov/track/issues/495">ISSUE-495</a>: added paragraph about 'relations opening up'. Clarified the role of '-' in example. Fixed dates in biblio. Fixed space issue in prov-n examples
-<li> <a href="http://www.w3.org/2011/prov/track/issues/516">ISSUE-516</a>: Stating that there moust be some underpinning activity or activities for a derivation, instead of just activities.
-<li> <a href="http://www.w3.org/2011/prov/track/issues/525">ISSUE-525</a>: Made it explicit that Membership, Alternate, Specialization are not Influence
-<li> Copied the sentence " An agent may be a particular type of entity or activity. This means that the model can be
+</li><li> <a href="http://www.w3.org/2011/prov/track/issues/492">ISSUE-492</a>: Fixed typos in <a href="#anexample-invalidation3" class="anexample-ref"><span>Example 29</span></a>.
+</li><li> <a href="http://www.w3.org/2011/prov/track/issues/508">ISSUE-508</a>: Clarified the bold names and parameters in text preceding <a href="#prov-dm-types-and-relations-fig">Table 5</a>.
+</li><li> <a href="http://www.w3.org/2011/prov/track/issues/501">ISSUE-501</a>: Put the example about driving a car to Boston in a box.
+</li><li> <a href="http://www.w3.org/2011/prov/track/issues/450">ISSUE-450</a>, <a href="http://www.w3.org/2011/prov/track/issues/514">ISSUE-514</a>: added table with secondary objects in relations.
+</li><li> <a href="http://www.w3.org/2011/prov/track/issues/512">ISSUE-512</a>: simplied type of activity a2 to "fine paying"
+</li><li> <a href="http://www.w3.org/2011/prov/track/issues/509">ISSUE-509</a>: modified the introductory text to UML figures, so that they refer to relation names (e.g. WasStartedBy) as visualized in figures
+</li><li> <a href="http://www.w3.org/2011/prov/track/issues/515">ISSUE-515</a>: fixed typo
+</li><li> <a href="http://www.w3.org/2011/prov/track/issues/531">ISSUE-531</a>: added sentence on the use of prov:location attribute.
+
+</li><li> <a href="http://www.w3.org/2011/prov/track/issues/519">ISSUE-519</a>, <a href="http://www.w3.org/2011/prov/track/issues/523">ISSUE-523</a>, <a href="http://www.w3.org/2011/prov/track/issues/524">ISSUE-524</a>, <a href="http://www.w3.org/2011/prov/track/issues/529">ISSUE-529</a>: changed UML diagram of figure 8 by removing explicit inheritance from influence for usage, start, end, generation, invalidation, communication, derivation, attribution, association, and delegation. Instead, introduced correspondance table 7. Furthermore, in response to these issues, it was made clear that PROV defines no attribute specific to subtypes such as SoftwareAgent, ..., Plan, Revision, Bundle, Collection.
+</li><li> <a href="http://www.w3.org/2011/prov/track/issues/495">ISSUE-495</a>: made explicit which section, figure, table was informative or normative.
+</li><li> <a href="http://www.w3.org/2011/prov/track/issues/521">ISSUE-521</a>: now states that "an agent relied on a plan" instead of "an agent adopted a plan".
+</li><li> <a href="http://www.w3.org/2011/prov/track/issues/499">ISSUE-499</a>: Made explicit that generation/usage/invalidation/start/end are implicit.
+</li><li> <a href="http://www.w3.org/2011/prov/track/issues/449">ISSUE-449</a>: Clarified definition of prov:value attribute and added an example.
+</li><li> <a href="http://www.w3.org/2011/prov/track/issues/495">ISSUE-495</a>: added paragraph about 'relations opening up'. Clarified the role of '-' in example. Fixed dates in biblio. Fixed space issue in prov-n examples
+</li><li> <a href="http://www.w3.org/2011/prov/track/issues/516">ISSUE-516</a>: Stating that there moust be some underpinning activity or activities for a derivation, instead of just activities.
+</li><li> <a href="http://www.w3.org/2011/prov/track/issues/525">ISSUE-525</a>: Made it explicit that Membership, Alternate, Specialization are not Influence
+</li><li> Copied the sentence " An agent may be a particular type of entity or activity. This means that the model can be
used to express provenance of the agents themselves. " from the informative section into the normative section.
-<li> <a href="http://www.w3.org/2011/prov/track/issues/504">ISSUE-504</a>: Updated definition of collection.
-<li> <a href="http://www.w3.org/2011/prov/track/issues/503">ISSUE-503</a>: Rephrased the introduction of expanded association in section 2.2.1.2 Expanded Relations.
-<li> <a href="http://www.w3.org/2011/prov/track/issues/514">ISSUE-514</a>: added links to the attributes listed in the secondary element table. Also removed PrimarySource, Quotation, Revision.
-<li> <a href="http://www.w3.org/2011/prov/track/issues/502">ISSUE-502</a>: Added sentence in section 2.1.2 explaining that the focus
+</li><li> <a href="http://www.w3.org/2011/prov/track/issues/504">ISSUE-504</a>: Updated definition of collection.
+</li><li> <a href="http://www.w3.org/2011/prov/track/issues/503">ISSUE-503</a>: Rephrased the introduction of expanded association in section 2.2.1.2 Expanded Relations.
+</li><li> <a href="http://www.w3.org/2011/prov/track/issues/514">ISSUE-514</a>: added links to the attributes listed in the secondary element table. Also removed PrimarySource, Quotation, Revision.
+</li><li> <a href="http://www.w3.org/2011/prov/track/issues/502">ISSUE-502</a>: Added sentence in section 2.1.2 explaining that the focus
of derivation is on connecting a generated entity to a used entity.
-<li> <a href="http://www.w3.org/2011/prov/track/issues/526">ISSUE-526</a>: Added sentence clarifying sentence in section 5.5.2.
-<li> <a href="http://www.w3.org/2011/prov/track/issues/462">ISSUE-462</a>: Added clarification regarding entity attributes (with respect to fixed aspects) and role of identifier with respect to equality.
-<li> <a href="http://www.w3.org/2011/prov/track/issues/518">ISSUE-518</a>: Added clarifying sentence of primary source.
-<li> <a href="http://www.w3.org/2011/prov/track/issues/552">ISSUE-552</a>: Clarifying phrasing around a quotation/revision/primary-source relation is a particular case of a derivation relation ...; updated definitions for start and end.
-<li> Rephrased original entity to preceding entity.
-<li> Moved feature at risk, Mention, to note document (prov-mention).
-</ul>
+</li><li> <a href="http://www.w3.org/2011/prov/track/issues/526">ISSUE-526</a>: Added sentence clarifying sentence in section 5.5.2.
+</li><li> <a href="http://www.w3.org/2011/prov/track/issues/462">ISSUE-462</a>: Added clarification regarding entity attributes (with respect to fixed aspects) and role of identifier with respect to equality.
+</li><li> <a href="http://www.w3.org/2011/prov/track/issues/518">ISSUE-518</a>: Added clarifying sentence of primary source.
+</li><li> <a href="http://www.w3.org/2011/prov/track/issues/552">ISSUE-552</a>: Clarifying phrasing around a quotation/revision/primary-source relation is a particular case of a derivation relation ...; updated definitions for start and end.
+</li><li> Rephrased original entity to preceding entity.
+</li><li> Moved feature at risk, Mention, to note document (prov-mention).
+</li></ul>
</section>
</section>
-<section class="appendix">
- <h2>Acknowledgements</h2>
+<section class="appendix" id="acknowledgements">
+ <!--OddPage--><h2><span class="secno">C. </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 (W3C/MIT) and Ivan Herman (W3C/ERCIM), W3C contacts for the Provenance Working Group.
+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>
@@ -4063,9 +4067,9 @@
Paul Groth (Vrije Universiteit),
Olaf Hartig (Invited expert),
David Hau (National Cancer Institute, NCI),
-Sandro Hawke (W3C/MIT),
+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, (W3C/ERCIM),
+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),
@@ -4103,5 +4107,26 @@
</section>
- </body>
-</html>
+
+
+<section id="references" class="appendix"><!--OddPage--><h2><span class="secno">D. </span>References</h2><section id="normative-references"><h3><span class="secno">D.1 </span>Normative references</h3><dl class="bibliography"><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-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-RDF-CONCEPTS">[RDF-CONCEPTS]</dt><dd>Graham Klyne; Jeremy J. Carroll. <a href="http://www.w3.org/TR/2004/REC-rdf-concepts-20040210"><cite>Resource Description Framework (RDF): Concepts and Abstract Syntax</cite></a>. 10 February 2004. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2004/REC-rdf-concepts-20040210">http://www.w3.org/TR/2004/REC-rdf-concepts-20040210</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-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-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">D.2 </span>Informative references</h3><dl class="bibliography"><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-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-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>
+</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-UML">[UML]</dt><dd>Object Management Group <a href="http://www.omg.org/spec/UML/2.0/Superstructure/PDF/"><cite>Unified Modeling Language: Superstructure</cite></a>. version 2.0, 2005 URL: <a href="http://www.omg.org/spec/UML/2.0/Superstructure/PDF/">http://www.omg.org/spec/UML/2.0/Superstructure/PDF/</a>
+</dd></dl></section></section></body></html>
--- a/model/prov-n.html Thu Apr 18 18:03:41 2013 +0200
+++ b/model/prov-n.html Thu Apr 18 18:05:22 2013 +0200
@@ -1,10 +1,9 @@
- <!DOCTYPE html>
-
-<html>
+<!DOCTYPE html>
+<html lang="en" dir="ltr">
<head>
<title>PROV-N: The Provenance Notation</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-n"/>
+<link rel="http://www.w3.org/ns/prov#has_provenance" href="http://www.w3.org/2011/prov/provenance/prov-n">
<style type="text/css">
.note { font-size:small; margin-left:50px }
@@ -29,163 +28,22 @@
}
</style>
- <script src="grammar/ll.js" class="remove"></script>
-
- <script src="https://www.w3.org/Tools/respec/respec-w3c-common" class="remove" async></script>
-
- <script src="https://www.w3.org/2007/OWL/toggles.js" class="remove"></script>
-
- <script src="https://ajax.googleapis.com/ajax/libs/jquery/1.7.1/jquery.min.js" class="remove"></script>
-
- <script src="prov-magic.js" class="remove"></script>
-
- <script src="provbib.js" class="remove"></script>
-
-
- <script class="remove">
-function setColoredDiffs () {
- setColoredDiffsForFile('diff-n.html');
-}
-
- $(document).ready(function(){
- // if grammar is in a string:
- $('#grammar_div').html(grammar_string);
- console.log( "updating grammar entries");
- updateGrammarRefs();
- updateExamplesWithLinks();
- updateExamplesRefs();
-
- if (typeof String.prototype.startsWith != 'function') {
- String.prototype.startsWith = function (str) {
- return this.indexOf(str) == 0;
- };
- }
- if (typeof String.prototype.contains != 'function') {
- String.prototype.contains = function (str) {
- return this.indexOf(str) >= 0;
- };
- }
-
- });
-
- </script>
-
- <script class="remove">
- var addExtraReferences = function() {
- for (var k in extraReferences)
- berjon.biblio[k] = extraReferences[k];
- };
- var extraReferences = {
- "PROV-RDF":
- "James Cheney "+
- "<a href=\"http://www.w3.org/2011/prov/wiki/ProvRDF\"><cite>PROV-RDF Mapping </cite></a>"+
- "2012, Working in Progress. "+
- "URL: <a href=\"http://www.w3.org/2011/prov/wiki/ProvRDF\">http://www.w3.org/2011/prov/wiki/ProvRDF</a>",
-
-
- "UNICODE" :
- "The Unicode Consortium. "+
- " <a href=\"http://www.unicode.org/unicode/standard/versions/enumeratedversions.html\"><cite>The Unicode Standard.</cite></a> " +
- " Defined by: The Unicode Standard, Version 6.2.0, (Mountain View, CA: The Unicode Consortium, 2012. ISBN 978-1-936213-07-8) , as updated from time to time by the publication of new versions URL: <a href=\"http://www.unicode.org/unicode/standard/versions/enumeratedversions.html\">http://www.unicode.org/unicode/standard/versions/enumeratedversions.html</a> ",
- "UNISEC":
- " Mark Davis; Michel Suignard. " +
- "<a href=\"http://www.unicode.org/reports/tr36/\"><cite>Unicode Security Considerations<cite></a>. " +
- " 4 August 2010. " +
- "URL: <a href=\"http://www.unicode.org/reports/tr36/\">http://www.unicode.org/reports/tr36/</a>",
- };
-
- var respecConfig = {
- // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
- specStatus: "REC",
-
- // the specification's short name, as in http://www.w3.org/TR/short-name/
- shortName: "prov-n",
-
- // if your specification has a subtitle that goes below the main
- // formal title, define it here
- // subtitle : "About-to-be-frozen WD4 (for internal release)",
- //subtitle : "<a href=\"diff-n.html\">Diffs</a> since LC Release ",
- //subtitle: "Editor's draft since CR release",
-
-
-
- // if you wish the publication date to be other than today, set this
- publishDate: "2013-04-30",
-
- // if the specification's copyright date is a range of years, specify
- // the start date here:
- copyrightStart: "2012",
-
- errata: "http://www.w3.org/2011/prov/errata.html",
-
-
- // if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
- // and its maturity status
- //previousPublishDate: "2012-12-11",
- previousPublishDate: "2013-03-12",
- previousMaturity: "PR",
-
-
- // if there a publicly available Editor's Draft, this is the link
- //edDraftURI: "http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-n.html",
-
- implementationReportURI: "http://www.w3.org/TR/2013/NOTE-prov-implementations-20130430/",
-
-
- // if this is a LCWD, uncomment and set the end of its review period
- prEnd: "2013-04-09",
- crEnd: "2013-01-31",
- lcEnd: "2012-09-18",
-
-
- // if you want to have extra CSS, append them to this list
- // it is recommended that the respec.css stylesheet be kept
- //extraCSS: ["http://dev.w3.org/2009/dap/ReSpec.js/css/respec.css"],
- //noReSpecCSS="true",
-
- // editors, add as many as you like
- // only "name" is required
- editors: [
- { name: "Luc Moreau", url: "http://www.ecs.soton.ac.uk/~lavm/",
- company: "University of Southampton" },
- { name: "Paolo Missier", url: "http://www.cs.ncl.ac.uk/people/Paolo.Missier",
- company: "Newcastle University" },
- ],
-
- // authors, add as many as you like.
- // This is optional, uncomment if you have authors as well as editors.
- // only "name" is required. Same format as editors.
-
- authors: [
- { name: "James Cheney", url: "http://homepages.inf.ed.ac.uk/jcheney/",
- company: "University of Edinburgh" },
-
- { name: "Stian Soiland-Reyes", url: "http://soiland-reyes.com/stian/",
- company: "University of Manchester" }
- ],
-
-
- // name of the WG
- wg: "Provenance Working Group",
-
- // URI of the public WG page
- wgURI: "http://www.w3.org/2011/prov/",
-
- // name (with the @w3c.org) of the public mailing to which comments are due
- wgPublicList: "public-prov-comments",
-
- // URI of the patent status for this WG, for Rec-track documents
- // !!!! IMPORTANT !!!!
- // This is important for Rec-track documents, do not copy a patent URI from a random
- // document unless you know what you're doing. If in doubt ask your friendly neighbourhood
- // Team Contact.
- wgPatentURI: "http://www.w3.org/2004/01/pp-impl/46974/status",
-
- // Add extraReferences to bibliography database
- preProcess: [addExtraReferences, addProvReferences],
- postProcess: [checkLinksToW3CReports, setContributors, setColoredDiffs, checkFragments],
- };
- </script>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
<style type="text/css">
/*****************************************************************
@@ -789,16 +647,199 @@
</style>
- </head>
-
- <body>
- <section id="abstract">
+ <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-REC"><!--[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-N: The Provenance Notation</h1>
+
+ <h2 id="w3c-recommendation-30-april-2013"><abbr title="World Wide Web Consortium">W3C</abbr> Recommendation 30 April 2013</h2>
+ <dl>
+
+ <dt>This version:</dt>
+ <dd><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>Latest published version:</dt>
+ <dd><a href="http://www.w3.org/TR/prov-n/">http://www.w3.org/TR/prov-n/</a></dd>
+
+
+
+
+ <dt>Implementation report:</dt>
+ <dd><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>Previous version:</dt>
+ <dd><a href="http://www.w3.org/TR/2013/PR-prov-n-20130312/">http://www.w3.org/TR/2013/PR-prov-n-20130312/</a> <a href="diff-n.html">(color-coded diff)</a></dd>
+
+
+ <dt>Editors:</dt>
+ <dd><a href="http://www.ecs.soton.ac.uk/~lavm/">Luc Moreau</a>, University of Southampton</dd>
+<dd><a href="http://www.cs.ncl.ac.uk/people/Paolo.Missier">Paolo Missier</a>, Newcastle University</dd>
+
+
+ <dt>Contributors:</dt>
+ <dd><a href="http://homepages.inf.ed.ac.uk/jcheney/">James Cheney</a>, University of Edinburgh</dd>
+<dd><a href="http://soiland-reyes.com/stian/">Stian Soiland-Reyes</a>, University of Manchester</dd>
+
+
+ </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.
+ </p>
+
+
+
+ <p>
+ The English version of this specification is the only normative version. Non-normative
+ <a href="http://www.w3.org/Consortium/Translation/">translations</a> may also be available.
+ </p>
+
+
+
+ <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 W3C
+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.
PROV-DM distinguishes core structures, forming the essence of provenance information, from
extended structures catering for more specific uses of provenance.
@@ -817,50 +858,99 @@
</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>
- </section>
-
-<section id="sotd">
-<h4>PROV Family of Documents</h4>
+ </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 [[PROV-OVERVIEW]] for a guide to reading these documents.
+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 [[PROV-OVERVIEW]];</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 [[PROV-PRIMER]];</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 [[!PROV-O]];</li>
-<li> <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/">PROV-DM</a> (Recommendation), the PROV data model for provenance [[!PROV-DM]];</li>
+<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 (this document);</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 [[!PROV-CONSTRAINTS]];</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 [[PROV-XML]];</li>
-<li> <a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/">PROV-AQ</a> (Note), mechanisms for accessing and querying provenance [[PROV-AQ]]; </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 [[PROV-DICTIONARY]];</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 [[PROV-DC]];</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 [[PROV-SEM]];</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 [[PROV-LINKS]].</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>Endorsed By W3C</h4>
-
-<p>This document has been reviewed by W3C Members, by software developers, and by other W3C groups and interested parties, and is endorsed by the Director as a W3C Recommendation. It is a stable document and may be used as reference material or cited from another document. W3C's role in making the Recommendation is to draw attention to the specification and to promote its widespread deployment. This enhances the functionality and interoperability of the Web.</p>
-
-<h4>Please Send Comments</h4>
-</section>
+<h4 id="endorsed-by-w3c">Endorsed By <abbr title="World Wide Web Consortium">W3C</abbr></h4>
+
+<p>This document has been reviewed by <abbr title="World Wide Web Consortium">W3C</abbr> Members, by software developers, and by other <abbr title="World Wide Web Consortium">W3C</abbr> groups and interested parties, and is endorsed by the Director as a <abbr title="World Wide Web Consortium">W3C</abbr> Recommendation. It is a stable document and may be used as reference material or cited from another document. <abbr title="World Wide Web Consortium">W3C</abbr>'s role in making the Recommendation is to draw attention to the specification and to promote its widespread deployment. This enhances the functionality and interoperability of the Web.</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 Recommendation.
+
+
+ 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>
+
+ 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="#purpose" class="tocxref"><span class="secno">1.1 </span>Purpose of this Document and Target Audience</a></li><li class="tocline"><a href="#compliance-with-this-document" class="tocxref"><span class="secno">1.2 </span>Compliance with this Document</a></li><li class="tocline"><a href="#structure-of-this-document" class="tocxref"><span class="secno">1.3 </span>Structure of this Document</a></li><li class="tocline"><a href="#notational-conventions" class="tocxref"><span class="secno">1.4 </span>Notational Conventions</a></li></ul></li><li class="tocline"><a href="#general-conventions" class="tocxref"><span class="secno">2. </span>General grammar considerations</a><ul class="toc"><li class="tocline"><a href="#functional-syntax" class="tocxref"><span class="secno">2.1 </span>Functional-style Syntax</a></li><li class="tocline"><a href="#grammar-notation" class="tocxref"><span class="secno">2.2 </span>EBNF Grammar</a></li><li class="tocline"><a href="#main-productions" class="tocxref"><span class="secno">2.3 </span>Main Productions</a></li><li class="tocline"><a href="#prov-n-optionals" class="tocxref"><span class="secno">2.4 </span>Optional terms in expressions</a></li><li class="tocline"><a href="#prov-n-standard-terms" class="tocxref"><span class="secno">2.5 </span>Identifiers and attributes</a></li><li class="tocline"><a href="#comments" class="tocxref"><span class="secno">2.6 </span>Comments</a></li></ul></li><li class="tocline"><a href="#prov-n-expressions" class="tocxref"><span class="secno">3. </span>PROV-N Productions per Component</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="#expression-Entity" class="tocxref"><span class="secno">3.1.1 </span>Entity</a></li><li class="tocline"><a href="#expression-Activity" class="tocxref"><span class="secno">3.1.2 </span>Activity</a></li><li class="tocline"><a href="#expression-Generation" class="tocxref"><span class="secno">3.1.3 </span>Generation</a></li><li class="tocline"><a href="#expression-Usage" class="tocxref"><span class="secno">3.1.4 </span>Usage</a></li><li class="tocline"><a href="#expression-wasInformedBy" class="tocxref"><span class="secno">3.1.5 </span>Communication</a></li><li class="tocline"><a href="#expression-Start" class="tocxref"><span class="secno">3.1.6 </span>Start</a></li><li class="tocline"><a href="#expression-End" class="tocxref"><span class="secno">3.1.7 </span>End</a></li><li class="tocline"><a href="#expression-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="#Derivation-Relation" class="tocxref"><span class="secno">3.2.1 </span>Derivation</a></li><li class="tocline"><a href="#expression-Revision" class="tocxref"><span class="secno">3.2.2 </span>Revision</a></li><li class="tocline"><a href="#expression-quotation" class="tocxref"><span class="secno">3.2.3 </span>Quotation</a></li><li class="tocline"><a href="#expression-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="#expression-Agent" class="tocxref"><span class="secno">3.3.1 </span>Agent</a></li><li class="tocline"><a href="#expression-attribution" class="tocxref"><span class="secno">3.3.2 </span>Attribution</a></li><li class="tocline"><a href="#expression-Association" class="tocxref"><span class="secno">3.3.3 </span>Association</a></li><li class="tocline"><a href="#expression-delegation" class="tocxref"><span class="secno">3.3.4 </span>Delegation</a></li><li class="tocline"><a href="#expression-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="#expression-bundle-constructor" class="tocxref"><span class="secno">3.4.1 </span>Bundle Constructor</a></li><li class="tocline"><a href="#expression-bundle-type" class="tocxref"><span class="secno">3.4.2 </span>Bundle Type</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="#expression-alternate" class="tocxref"><span class="secno">3.5.1 </span>Alternate</a></li><li class="tocline"><a href="#expression-specialization" class="tocxref"><span class="secno">3.5.2 </span>Specialization</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="#expression-collection" class="tocxref"><span class="secno">3.6.1 </span>Collection</a></li><li class="tocline"><a href="#expression-collection-membership" class="tocxref"><span class="secno">3.6.2 </span>Membership</a></li></ul></li><li class="tocline"><a href="#subexpressions" class="tocxref"><span class="secno">3.7 </span>Further Expressions</a><ul class="toc"><li class="tocline"><a href="#expression-identifier" class="tocxref"><span class="secno">3.7.1 </span>Identifier</a></li><li class="tocline"><a href="#expression-attribute" class="tocxref"><span class="secno">3.7.2 </span>Attribute</a></li><li class="tocline"><a href="#expression-literal" class="tocxref"><span class="secno">3.7.3 </span>Literal</a><ul class="toc"><li class="tocline"><a href="#expression-types" class="tocxref"><span class="secno">3.7.3.1 </span>Reserved Type Values</a></li><li class="tocline"><a href="#expression-Time" class="tocxref"><span class="secno">3.7.3.2 </span>Time Values</a></li></ul></li><li class="tocline"><a href="#expression-NamespaceDeclaration" class="tocxref"><span class="secno">3.7.4 </span>Namespace Declaration</a></li><li class="tocline"><a href="#semantic-rules-summary" class="tocxref"><span class="secno">3.7.5 </span>Summary of additional semantic rules</a></li></ul></li></ul></li><li class="tocline"><a href="#document" class="tocxref"><span class="secno">4. </span>Document</a></li><li class="tocline"><a href="#extensibility" class="tocxref"><span class="secno">5. </span>Extensibility</a></li><li class="tocline"><a href="#media-type" class="tocxref"><span class="secno">6. </span>Media Type</a></li><li class="tocline"><a href="#change-log" class="tocxref"><span class="secno">A. </span>Change Log</a><ul class="toc"><li class="tocline"><a href="#changes-since-proposed-recommendation" class="tocxref"><span class="secno">A.1 </span>Changes since Proposed Recommendation</a></li><li class="tocline"><a href="#changes-since-candidate-recommendation" class="tocxref"><span class="secno">A.2 </span>Changes since Candidate Recommendation</a></li><li class="tocline"><a href="#changes-since-last-call" class="tocxref"><span class="secno">A.3 </span>Changes since last call</a></li></ul></li><li class="tocline"><a href="#acknowledgements" class="tocxref"><span class="secno">B. </span>Acknowledgements</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="#normative-references" class="tocxref"><span class="secno">C.1 </span>Normative references</a></li><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">C.2 </span>Informative references</a></li></ul></li></ul></section>
+
+
<section id="introduction">
-<h2>Introduction</h2>
+<!--OddPage--><h2><span class="secno">1. </span>Introduction</h2>
<p> Provenance is a record that describes the people,
institutions, entities, and activities, involved in producing,
influencing, or delivering a piece of data or a thing in the world. Two
companion specifications respectively define PROV-DM, a data model for
-provenance, allowing provenance descriptions to be expressed [[!PROV-DM]] and a set of constraints that provenance descriptions are expected to satisfy [[!PROV-CONSTRAINTS]].
+provenance, allowing provenance descriptions to be expressed [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>] and a set of constraints that provenance descriptions are expected to satisfy [<cite><a class="bibref" href="#bib-PROV-CONSTRAINTS">PROV-CONSTRAINTS</a></cite>].
</p>
<section id="purpose">
-<h2>Purpose of this Document and Target Audience</h2>
+<h3><span class="secno">1.1 </span>Purpose of this Document and Target Audience</h3>
A key goal of PROV is the specification of a machine-processable data model for provenance. However, communicating provenance between humans is also important when teaching, illustrating, formalizing, and discussing provenance-related issues.
@@ -870,51 +960,51 @@
<ul>
<li>Technology independence. PROV-N provides a simple syntax that can be mapped to several technologies.
-<li>Human readability. PROV-N follows a functional syntax style that is meant to be easily human-readable so it can be used in illustrative examples, such as those presented in the PROV documents suite
-
-<li>Formality. PROV-N is defined through a formal grammar amenable to be used with parser generators.
-
- </ul>
+</li><li>Human readability. PROV-N follows a functional syntax style that is meant to be easily human-readable so it can be used in illustrative examples, such as those presented in the PROV documents suite.
+
+</li><li>Formality. PROV-N is defined through a formal grammar amenable to be used with parser generators.
+
+ </li></ul>
PROV-N has several known uses:
<ul>
-<li> It is the notation used in the examples found in [[PROV-DM]], as well as in the definition of PROV constraints [[PROV-CONSTRAINTS]]; </li>
-<li> It is a source language for the encoding of PROV data model instances into a variety of target languages, including amongst others RDF [[PROV-RDF]] and XML [[PROV-XML]]; </li>
-<li> It provides the basis for a formal semantics of the PROV data model [[PROV-SEM]], in which an interpretation is given to each element of the PROV-N language.
-</ul>
+<li> It is the notation used in the examples found in [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>], as well as in the definition of PROV constraints [<cite><a class="bibref" href="#bib-PROV-CONSTRAINTS">PROV-CONSTRAINTS</a></cite>]; </li>
+<li> It is a source language for the encoding of PROV data model instances into a variety of target languages, including amongst others RDF [<cite><a class="bibref" href="#bib-PROV-RDF">PROV-RDF</a></cite>] and XML [<cite><a class="bibref" href="#bib-PROV-XML">PROV-XML</a></cite>]; </li>
+<li> It provides the basis for a formal semantics of the PROV data model [<cite><a class="bibref" href="#bib-PROV-SEM">PROV-SEM</a></cite>], in which an interpretation is given to each element of the PROV-N language.
+</li></ul>
<p>This document introduces the PROV-N grammar along with examples of its usage.</p>
<p>Its target audience is twofold:
-<ul>
+</p><ul>
<li>Developers of provenance management applications, as well as implementors of new PROV data model encodings, and thus in particular of PROV-N parsers. These readers may be interested in the entire structure of the grammar, starting from the top level nonterminal
<code><a class="grammarRef" href="#prod-document">document</a></code>.</li>
-<li>Readers of the [[PROV-DM]] and of [[PROV-CONSTRAINTS]] documents, who are interested in the details of the formal language underpinning the notation used in the examples and in the definition of the constraints. Those readers may find the <code><a class="grammarRef" href="#prod-expression">expression</a></code> nonterminal a useful entry point into the grammar.</li>
+<li>Readers of the [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>] and of [<cite><a class="bibref" href="#bib-PROV-CONSTRAINTS">PROV-CONSTRAINTS</a></cite>] documents, who are interested in the details of the formal language underpinning the notation used in the examples and in the definition of the constraints. Those readers may find the <code><a class="grammarRef" href="#prod-expression">expression</a></code> nonterminal a useful entry point into the grammar.</li>
</ul>
</section>
<section id="compliance-with-this-document">
-<h3>Compliance with this Document</h3>
+<h3><span class="secno">1.2 </span>Compliance with this Document</h3>
<p>For the purpose of compliance, all sections of this document are normative, except
<a href="#change-log">Appendix A</a>,
<a href="#acknowledgements">Appendix B</a>, and
<a href="#informative-references">Appendix C.2</a>.
-<ul>
+</p><ul>
<li> Information in tables is normative. </li>
<li> Text in boxes labeled "Example" is informative.
-<li> Productions (displayed in boxes) are normative, as opposed to the separate <a href="grammar.txt">file</a> grouping all productions for convenience of programmers, which is informative.
-</ul>
+</li><li> Productions (displayed in boxes) are normative, as opposed to the separate <a href="grammar.txt">file</a> grouping all productions for convenience of programmers, which is informative.
+</li></ul>
</section>
<section id="structure-of-this-document">
-<h3>Structure of this Document</h3>
+<h3><span class="secno">1.3 </span>Structure of this Document</h3>
<p>This document is structured as follows.
-<p><a href="#general-conventions">Section 2</a> provides general consideration about the PROV-N grammar.</p>
+</p><p><a href="#general-conventions">Section 2</a> provides general consideration about the PROV-N grammar.</p>
<p><a href="#prov-n-expressions">Section 3</a> presents the grammar of all expressions of the language grouped according to the PROV data model components.</p>
@@ -929,13 +1019,14 @@
<section id="notational-conventions">
- <h3>Notational Conventions</h3>
-
-
-<p>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
- NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
- "OPTIONAL" in this document are to be interpreted as described in
- [[!RFC2119]].</p>
+ <h3><span class="secno">1.4 </span>Notational 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>
@@ -943,14 +1034,14 @@
<p>
The following namespaces prefixes are used throughout this document.
-<div style="text-align: left;">
+</p><div style="text-align: left;">
<table border="1" style="margin-left: auto; margin-right: auto;">
<caption id="namespace-table">Table 1: Prefix and Namespaces used in this specification</caption>
-<tr><td><b>prefix</b></td><td><b>namespace uri</b></td> <td><b>definition</b></td></tr>
+<tbody><tr><td><b>prefix</b></td><td><b>namespace uri</b></td> <td><b>definition</b></td></tr>
<tr><td>prov</td><td>http://www.w3.org/ns/prov#</td><td>The PROV namespace (see Section <a href="#expression-NamespaceDeclaration">3.7.4</a>)</td></tr>
-<tr><td>xsd</td><td>http://www.w3.org/2000/10/XMLSchema#</td><td>XML Schema Namespace [[!XMLSCHEMA11-2]]</td></tr>
-<tr><td>(others)</td><td>(various)</td><td>All other namespace prefixes are used in examples only. <br/> In particular, URIs starting with "http://example.com" represent<br/> some application-dependent URI [[!RFC3986]]</td></tr>
-</table>
+<tr><td>xsd</td><td>http://www.w3.org/2000/10/XMLSchema#</td><td>XML Schema Namespace [<cite><a class="bibref" href="#bib-XMLSCHEMA11-2">XMLSCHEMA11-2</a></cite>]</td></tr>
+<tr><td>(others)</td><td>(various)</td><td>All other namespace prefixes are used in examples only. <br> In particular, URIs starting with "http://example.com" represent<br> some application-dependent URI [<cite><a class="bibref" href="#bib-RFC3986">RFC3986</a></cite>]</td></tr>
+</tbody></table>
</div>
</section>
@@ -958,59 +1049,54 @@
</section>
<section id="general-conventions">
-<h3>General grammar considerations</h3>
+<!--OddPage--><h2><span class="secno">2. </span>General grammar considerations</h2>
<p>For convenience, all productions presented in this document have been grouped in a
separate <a href="grammar.txt">file</a>.</p>
<section id="functional-syntax">
-<h3>Functional-style Syntax</h3>
+<h3><span class="secno">2.1 </span>Functional-style Syntax</h3>
<p> PROV-N adopts a functional-style syntax consisting of a predicate name and an ordered list of terms.</p>
<p>
All PROV data model types have an identifier. Furthermore, some expressions also admit additional elements that further characterize it. </p>
-<div class="anexample">
+<div class="anexample" id="example_1"><div class="anexampleTitle"><a class="internalDFN" href="#example_1">Example 1</a></div>
<p>The following expression should be read as "entity <span class="name">e1</span>".
-<pre class="codeexample" >
-entity(e1)
+</p><pre class="codeexample">entity(e1)
</pre>
</div>
-<div class="anexample">
+<div class="anexample" id="example_2"><div class="anexampleTitle"><a class="internalDFN" href="#example_2">Example 2</a></div>
<p>The following expression should be read as "activity <span class="name">a2</span>, which occurred
between <code>2011-11-16T16:00:00</code> and <code>2011-11-16T16:00:01</code>".
-<pre class="codeexample" >
-entity(e1)
+</p><pre class="codeexample">entity(e1)
activity(a2, 2011-11-16T16:00:00, 2011-11-16T16:00:01)
</pre>
</div>
<p>
All PROV data model relations involve two primary elements, the <em>subject</em> and the <em>object</em>, in this order. Furthermore, some expressions also admit additional elements that further characterize it.
-<div class="anexample">
+</p><div class="anexample" id="example_3"><div class="anexampleTitle"><a class="internalDFN" href="#example_3">Example 3</a></div>
<p>The following expression should be read as "<span class="name">e2</span> was derived from <span class="name">e1</span>". Here <span class="name">e2</span> is the subject, and <span class="name">e1</span> is the object.
-<pre class="codeexample" >
-wasDerivedFrom(e2, e1)
+</p><pre class="codeexample">wasDerivedFrom(e2, e1)
</pre>
</div>
-<div class="anexample">
+<div class="anexample" id="example_4"><div class="anexampleTitle"><a class="internalDFN" href="#example_4">Example 4</a></div>
<p>The following expression expands the above derivation relation by providing
additional elements the optional activity <span class="name">a</span>, the generation <span class="name">g2</span>, and the usage <span class="name">u1</span>:
-<pre class="codeexample" >
-wasDerivedFrom(e2, e1, a, g2, u1)
+</p><pre class="codeexample">wasDerivedFrom(e2, e1, a, g2, u1)
</pre>
</div>
</section>
<section id="grammar-notation">
-<h3>EBNF Grammar</h3>
+<h3><span class="secno">2.2 </span>EBNF Grammar</h3>
<p>The grammar is specified using a subset of the Extended Backus-Naur
Form (EBNF) notation, as defined in Extensible Markup Language (XML) 1.1
-[[!XML11]] section <a
-href="http://www.w3.org/TR/2006/REC-xml11-20060816/#sec-notation">6
+[<cite><a class="bibref" href="#bib-XML11">XML11</a></cite>] section <a href="http://www.w3.org/TR/2006/REC-xml11-20060816/#sec-notation">6
Notation</a>.
</p>
@@ -1020,20 +1106,20 @@
<p>
- EBNF specifies a series of production rules (<dfn>production</dfn>).
+ EBNF specifies a series of production rules (<dfn id="dfn-production">production</dfn>).
A production rule in the grammar defines a symbol
- <code class="grammarRef">expr</code> (<dfn>nonterminal symbol</dfn>)
+ <code class="grammarRef">expr</code> (<dfn id="dfn-nonterminal-symbol">nonterminal symbol</dfn>)
using the following form:</p>
-<div class='grammar'>
+<div class="grammar">
<code class="grammarRef">expr</code> ::= <em>term</em>
</div>
<p>Symbols are written with an initial capital letter if they are the start symbol of a regular language, otherwise with an initial lowercase letter.
A production rule in the grammar defines a symbol
- <code class="grammarRef"><TERMINAL></code> (<dfn>terminal symbol</dfn>)
+ <code class="grammarRef"><TERMINAL></code> (<dfn id="dfn-terminal-symbol">terminal symbol</dfn>)
using the following form:</p>
-<div class='grammar'>
+<div class="grammar">
<code class="grammarRef"><TERMINAL></code> ::= <em>term</em>
</div>
@@ -1043,7 +1129,7 @@
<p>Within the term on the right-hand side of a rule, the following
<em>term</em>s are used to match strings of one or more characters:
-<ul>
+</p><ul>
<li>
<code class="grammarRef">expr</code>: matches production for nonterminal symbol <code class="grammarRef">expr</code>
</li>
@@ -1077,12 +1163,12 @@
</ul>
-<p>Where suitable, the PROV-N grammar reuses production and terminal names of the SPARQL grammar [[!RDF-SPARQL-QUERY]].</p>
+<p>Where suitable, the PROV-N grammar reuses production and terminal names of the SPARQL grammar [<cite><a class="bibref" href="#bib-RDF-SPARQL-QUERY">RDF-SPARQL-QUERY</a></cite>].</p>
</section>
<section id="main-productions">
-<h3>Main Productions</h3>
+<h3><span class="secno">2.3 </span>Main Productions</h3>
<p>Two productions are entry points to the grammar.</p>
@@ -1092,8 +1178,8 @@
-<table class="grammar">
-<tbody class="grammar-ref" data-ref="prod-expression"></tbody>
+</p><table class="grammar">
+<tbody class="prod"> <tr style="vertical-align: baseline; "> <td><a id="prod-expression" data-name="prod-expression"></a>[<span class="prodNo">2</span>] </td> <td><code class="production prod">expression</code></td> <td> ::= </td> <td><code class="content">( <span class="prod"><a class="grammarRef" href="#prod-entityExpression">entityExpression</a></span> | <span class="prod"><a class="grammarRef" href="#prod-activityExpression">activityExpression</a></span> | <span class="prod"><a class="grammarRef" href="#prod-generationExpression">generationExpression</a></span> | <span class="prod"><a class="grammarRef" href="#prod-usageExpression">usageExpression</a></span> | <span class="prod"><a class="grammarRef" href="#prod-startExpression">startExpression</a></span> | <span class="prod"><a class="grammarRef" href="#prod-endExpression">endExpression</a></span> | <span class="prod"><a class="grammarRef" href="#prod-invalidationExpression">invalidationExpression</a></span> | <span class="prod"><a class="grammarRef" href="#prod-communicationExpression">communicationExpression</a></span> | <span class="prod"><a class="grammarRef" href="#prod-agentExpression">agentExpression</a></span> | <span class="prod"><a class="grammarRef" href="#prod-associationExpression">associationExpression</a></span> | <span class="prod"><a class="grammarRef" href="#prod-attributionExpression">attributionExpression</a></span> | <span class="prod"><a class="grammarRef" href="#prod-delegationExpression">delegationExpression</a></span> | <span class="prod"><a class="grammarRef" href="#prod-derivationExpression">derivationExpression</a></span> | <span class="prod"><a class="grammarRef" href="#prod-influenceExpression">influenceExpression</a></span> | <span class="prod"><a class="grammarRef" href="#prod-alternateExpression">alternateExpression</a></span> | <span class="prod"><a class="grammarRef" href="#prod-specializationExpression">specializationExpression</a></span> | <span class="prod"><a class="grammarRef" href="#prod-membershipExpression">membershipExpression</a></span> | <span class="prod"><a class="grammarRef" href="#prod-extensibilityExpression">extensibilityExpression</a></span> )</code></td> </tr> </tbody>
</table>
@@ -1108,21 +1194,19 @@
<section id="prov-n-optionals">
-<h3>Optional terms in expressions</h3>
+<h3><span class="secno">2.4 </span>Optional terms in expressions</h3>
Some terms in an expression may be optional. For example:
-<div class="anexample">
-<pre class="codeexample" >
-wasDerivedFrom(e2, e1, a, g2, u1)
+<div class="anexample" id="example_5"><div class="anexampleTitle"><a class="internalDFN" href="#example_5">Example 5</a></div>
+<pre class="codeexample">wasDerivedFrom(e2, e1, a, g2, u1)
wasDerivedFrom(e2, e1)
</pre>
In a derivation expression, the activity, generation, and usage are optional terms. They are specified in the first derivation, but not in the second.
</div>
-<div class="anexample">
-<pre class="codeexample" >
-activity(a2, 2011-11-16T16:00:00, 2011-11-16T16:00:01)
+<div class="anexample" id="example_6"><div class="anexampleTitle"><a class="internalDFN" href="#example_6">Example 6</a></div>
+<pre class="codeexample">activity(a2, 2011-11-16T16:00:00, 2011-11-16T16:00:01)
activity(a1)
</pre>
The start and end times for an activity are optional. They are specified in the first expression, but not in the second.
@@ -1131,19 +1215,17 @@
<p>The general rule for optionals is that, if <em>none</em> of the optionals are used in the expression, then they are simply omitted, resulting in a simpler expression as in the examples above.</p>
However, it may be the case that only some of the optional terms are omitted. Because the position of the terms in the expression matters, an additional marker must be used to indicate that a particular term is not available. The symbol <span class="name">'-'</span> is used for this purpose.
-<div class="anexample">
+<div class="anexample" id="example_7"><div class="anexampleTitle"><a class="internalDFN" href="#example_7">Example 7</a></div>
<p>In the first expression below, all optionals are specified. However in the second and third, only one optional is specified, forcing the use of the marker for the missing terms.
-<pre class="codeexample" >
-wasDerivedFrom(e2, e1, a, g2, u1)
+</p><pre class="codeexample">wasDerivedFrom(e2, e1, a, g2, u1)
wasDerivedFrom(e2, e1, -, -, u1)
wasDerivedFrom(e2, e1, a, -, -)
</pre>
</div>
Note that the more succinct form is just shorthand for a complete expression with all the markers specified:
-<div class="anexample">
-<pre class="codeexample" >
-activity(a1)
+<div class="anexample" id="example_8"><div class="anexampleTitle"><a class="internalDFN" href="#example_8">Example 8</a></div>
+<pre class="codeexample">activity(a1)
activity(a1, -, -)
</pre>
</div>
@@ -1152,15 +1234,14 @@
</section>
<section id="prov-n-standard-terms">
-<h3>Identifiers and attributes</h3>
+<h3><span class="secno">2.5 </span>Identifiers and attributes</h3>
<p>Almost all expressions defined in the grammar include an identifier (see <a href="#expression-identifier">Section 3.7.1</a> for the full syntax of identifiers). Most expressions
-can also include a set of attribute-value pairs, delimited by square brackets. Identifiers are optional except for Entities, Activites, and Agents. Identifiers are always the first term in any expression. <em>Optional</em> identifiers MUST be separated using a semi-colon ';', but where the identifiers are required, a regular comma ',' MUST be used. This makes it possible to completely omit an optional identifier with no ambiguity arising. Also, if the set of attribute-value pairs is present, it is always the last term in any expression.</p>
-
-<div class="anexample">
+can also include a set of attribute-value pairs, delimited by square brackets. Identifiers are optional except for Entities, Activities, and Agents. Identifiers are always the first term in any expression. <em>Optional</em> identifiers <em class="rfc2119" title="MUST">MUST</em> be separated using a semi-colon ';', but where the identifiers are required, a regular comma ',' <em class="rfc2119" title="MUST">MUST</em> be used. This makes it possible to completely omit an optional identifier with no ambiguity arising. Also, if the set of attribute-value pairs is present, it is always the last term in any expression.</p>
+
+<div class="anexample" id="example_9"><div class="anexampleTitle"><a class="internalDFN" href="#example_9">Example 9</a></div>
<p>Derivation has an optional identifier. In the first expression, the identifier is not available, while it is explicit in the second. The third example shows that one can optionally indicate the missing identifier using the <span class="name">-</span> marker. This is equivalent to the first expression. </p>
-<pre class="codeexample" >
-wasDerivedFrom(e2, e1)
+<pre class="codeexample">wasDerivedFrom(e2, e1)
wasDerivedFrom(d; e2, e1)
wasDerivedFrom(-; e2, e1)
</pre>
@@ -1170,12 +1251,11 @@
<!-- Expressions with no attributes A distinction is made between expressions with no attributes, and expressions that include an empty list of attributes. -->
-<div class="anexample">
+<div class="anexample" id="example_10"><div class="anexampleTitle"><a class="internalDFN" href="#example_10">Example 10</a></div>
<p>The first and second activity expressions do not specify any attributes, and are equivalent.
<!-- does not have any attributes. The second has an empty list of attributes. -->
The third activity expression specifies two attributes.
-<pre class="codeexample" >
-activity(ex:a1)
+</p><pre class="codeexample">activity(ex:a1)
activity(ex:a1, [])
activity(ex:a1, [ex:param1="a", ex:param2="b"])
</pre>
@@ -1183,16 +1263,16 @@
</section>
-<section>
-<h3>Comments</h3>
+<section id="comments">
+<h3><span class="secno">2.6 </span>Comments</h3>
Comments in PROV-N take two forms:
<ul>
<li> '//' outside an <code class="content"><a class="grammarRef" href="http://www.w3.org/TR/rdf-sparql-query/#rIRI_REF">IRI_REF</a></code> or <code class="content"><a class="grammarRef" href="#prod-STRING_LITERAL">STRING_LITERAL</a></code>; such comments continue to the end of line (marked by characters U+000D or U+000A) or end of file if there is no end of line after the comment marker.
-<li> '/*' ... '*/', outside an <code class="content"><a class="grammarRef" href="http://www.w3.org/TR/rdf-sparql-query/#rIRI_REF">IRI_REF</a></code> or <code class="content"><a class="grammarRef" href="#prod-STRING_LITERAL">STRING_LITERAL</a></code>.
-</ul>
+</li><li> '/*' ... '*/', outside an <code class="content"><a class="grammarRef" href="http://www.w3.org/TR/rdf-sparql-query/#rIRI_REF">IRI_REF</a></code> or <code class="content"><a class="grammarRef" href="#prod-STRING_LITERAL">STRING_LITERAL</a></code>.
+</li></ul>
<p>Comments are treated as white space.</p>
</section>
@@ -1200,46 +1280,44 @@
</section>
<section id="prov-n-expressions">
-<h2>PROV-N Productions per Component</h2>
+<!--OddPage--><h2><span class="secno">3. </span>PROV-N Productions per Component</h2>
<p>This section introduces grammar productions for each expression, followed by small examples of expressions illustrating the grammar. Strings conforming to the grammar are valid expressions in the PROV-N language.</p>
<section id="component1">
-<h3>Component 1: Entities and Activities</h3>
+<h3><span class="secno">3.1 </span>Component 1: Entities and Activities</h3>
<section id="expression-Entity">
-<h4>Entity</h4>
+<h4><span class="secno">3.1.1 </span>Entity</h4>
<p>
-<table class="grammar">
-<tbody class="grammar-ref" data-ref="prod-entityExpression"></tbody>
-<tbody class="grammar-ref" data-ref="prod-optionalAttributeValuePairs"></tbody>
-<tbody class="grammar-ref" data-ref="prod-attributeValuePairs"></tbody>
-<tbody class="grammar-ref" data-ref="prod-attributeValuePair"></tbody>
+</p><table class="grammar">
+<tbody class="prod"> <tr style="vertical-align: baseline; "> <td><a id="prod-entityExpression" data-name="prod-entityExpression"></a>[<span class="prodNo">3</span>] </td> <td><code class="production prod">entityExpression</code></td> <td> ::= </td> <td><code class="content">"entity" "(" <span class="prod"><a class="grammarRef" href="#prod-identifier">identifier</a></span> <span class="prod"><a class="grammarRef" href="#prod-optionalAttributeValuePairs">optionalAttributeValuePairs</a></span> ")"</code></td> </tr> </tbody>
+<tbody class="prod"> <tr style="vertical-align: baseline; "> <td><a id="prod-optionalAttributeValuePairs" data-name="prod-optionalAttributeValuePairs"></a>[<span class="prodNo">4</span>] </td> <td><code class="production prod">optionalAttributeValuePairs</code></td> <td> ::= </td> <td><code class="content">( "," "[" <span class="prod"><a class="grammarRef" href="#prod-attributeValuePairs">attributeValuePairs</a></span> "]" )?</code></td> </tr> </tbody>
+<tbody class="prod"> <tr style="vertical-align: baseline; "> <td><a id="prod-attributeValuePairs" data-name="prod-attributeValuePairs"></a>[<span class="prodNo">5</span>] </td> <td><code class="production prod">attributeValuePairs</code></td> <td> ::= </td> <td><code class="content">( | <span class="prod"><a class="grammarRef" href="#prod-attributeValuePair">attributeValuePair</a></span> ( "," <span class="prod"><a class="grammarRef" href="#prod-attributeValuePair">attributeValuePair</a></span> )* )</code></td> </tr> </tbody>
+<tbody class="prod"> <tr style="vertical-align: baseline; "> <td><a id="prod-attributeValuePair" data-name="prod-attributeValuePair"></a>[<span class="prodNo">6</span>] </td> <td><code class="production prod">attributeValuePair</code></td> <td> ::= </td> <td><code class="content"><span class="prod"><a class="grammarRef" href="#prod-attribute">attribute</a></span> "=" <span class="prod"><a class="grammarRef" href="#prod-literal">literal</a></span></code></td> </tr> </tbody>
</table>
<p>The following table summarizes how each constituent of a PROV-DM Entity maps to a PROV-N syntax element.</p>
<div style="text-align: left; ">
<table class="thinborder" style="margin-left: auto; margin-right: auto;">
-<tr><td><b><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#dfn-entity">Entity</a></b></td><td><b>Non-Terminal</b></td></tr>
+<tbody><tr><td><b><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#dfn-entity">Entity</a></b></td><td><b>Non-Terminal</b></td></tr>
<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#entity.id"><span class='attribute' id="entity.id">id</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-identifier">identifier</a></code></td></tr>
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#entity.attributes"><span class='attribute' id="entity.attributes">attributes</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-optionalAttributeValuePairs">optionalAttributeValuePairs</a></code></td></tr>
-</table>
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#entity.id"><span class="attribute" id="entity.id">id</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-identifier">identifier</a></code></td></tr>
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#entity.attributes"><span class="attribute" id="entity.attributes">attributes</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-optionalAttributeValuePairs">optionalAttributeValuePairs</a></code></td></tr>
+</tbody></table>
</div>
-<div class="anexample">
-<pre class="codeexample">
-entity(tr:WD-prov-dm-20111215, [ prov:type="document" ])
+<div class="anexample" id="example_11"><div class="anexampleTitle"><a class="internalDFN" href="#example_11">Example 11</a></div>
+<pre class="codeexample">entity(tr:WD-prov-dm-20111215, [ prov:type="document" ])
</pre>
Here <span class="name">tr:WD-prov-dm-20111215</span> is the entity identifier, and <span class="name">[ prov:type="document" ]</span> groups the optional attributes, only one in this example, with their values.
- <pre class="codeexample">
-<!-- entity(tr:WD-prov-dm-20111215, [ prov:type="document", ex:version=2 ]) -->
+ <pre class="codeexample"><!-- entity(tr:WD-prov-dm-20111215, [ prov:type="document", ex:version=2 ]) -->
entity(tr:WD-prov-dm-20111215)
</pre>
Here, the optional attributes are absent.
@@ -1249,42 +1327,40 @@
</section>
<section id="expression-Activity">
-<h4>Activity</h4>
+<h4><span class="secno">3.1.2 </span>Activity</h4>
<table class="grammar">
-<tbody class="grammar-ref" data-ref="prod-activityExpression"></tbody>
-<tbody class="grammar-ref" data-ref="prod-timeOrMarker"></tbody>
+<tbody class="prod"> <tr style="vertical-align: baseline; "> <td><a id="prod-activityExpression" data-name="prod-activityExpression"></a>[<span class="prodNo">7</span>] </td> <td><code class="production prod">activityExpression</code></td> <td> ::= </td> <td><code class="content">"activity" "(" <span class="prod"><a class="grammarRef" href="#prod-identifier">identifier</a></span> ( "," <span class="prod"><a class="grammarRef" href="#prod-timeOrMarker">timeOrMarker</a></span> "," <span class="prod"><a class="grammarRef" href="#prod-timeOrMarker">timeOrMarker</a></span> )? <span class="prod"><a class="grammarRef" href="#prod-optionalAttributeValuePairs">optionalAttributeValuePairs</a></span> ")"</code></td> </tr> </tbody>
+<tbody class="prod"> <tr style="vertical-align: baseline; "> <td><a id="prod-timeOrMarker" data-name="prod-timeOrMarker"></a>[<span class="prodNo">8</span>] </td> <td><code class="production prod">timeOrMarker</code></td> <td> ::= </td> <td><code class="content">( <span class="prod"><a class="grammarRef" href="#prod-time">time</a></span> | "-" )</code></td> </tr> </tbody>
</table>
<p>The following table summarizes how each constituent of a PROV-DM Activity maps to a PROV-N syntax element.</p>
<div style="text-align: left; ">
<table class="thinborder" style="margin-left: auto; margin-right: auto;">
-<tr><td><b><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#dfn-activity">Activity</a></b></td><td><b>Non-Terminal</b></td></tr>
+<tbody><tr><td><b><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#dfn-activity">Activity</a></b></td><td><b>Non-Terminal</b></td></tr>
<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#activity.id"><span class='attribute' id="activity.id">id</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-identifier">identifier</a></code></td></tr>
-
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#activity.startTime"><span class='attribute' id="activity.startTime">startTime</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-timeOrMarker">timeOrMarker</a></code></td></tr>
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#activity.endTime"><span class='attribute' id="activity.endTime">endTime</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-timeOrMarker">timeOrMarker</a></code></td></tr>
-
-
-
-
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#activity.attributes"><span class='attribute' id="activity.attributes">attributes</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-optionalAttributeValuePairs">optionalAttributeValuePairs</a></code></td></tr>
-</table>
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#activity.id"><span class="attribute" id="activity.id">id</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-identifier">identifier</a></code></td></tr>
+
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#activity.startTime"><span class="attribute" id="activity.startTime">startTime</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-timeOrMarker">timeOrMarker</a></code></td></tr>
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#activity.endTime"><span class="attribute" id="activity.endTime">endTime</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-timeOrMarker">timeOrMarker</a></code></td></tr>
+
+
+
+
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#activity.attributes"><span class="attribute" id="activity.attributes">attributes</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-optionalAttributeValuePairs">optionalAttributeValuePairs</a></code></td></tr>
+</tbody></table>
</div>
-<div class="anexample">
-<pre class="codeexample">
-activity(ex:a10, 2011-11-16T16:00:00, 2011-11-16T16:00:01, [prov:type="createFile"])
+<div class="anexample" id="example_12"><div class="anexampleTitle"><a class="internalDFN" href="#example_12">Example 12</a></div>
+<pre class="codeexample">activity(ex:a10, 2011-11-16T16:00:00, 2011-11-16T16:00:01, [prov:type="createFile"])
</pre>
<p>Here <span class="name">ex:a10</span> is the activity identifier, <span class="name">2011-11-16T16:00:00</span> and <span class="name">2011-11-16T16:00:01</span> are the optional start and end times for the activity, and <span class="name">[prov:type="createFile"]</span> are optional attributes. </p>
The remaining examples show cases where some of the optionals are omitted.
-<pre class="codeexample">
-activity(ex:a10)
+<pre class="codeexample">activity(ex:a10)
activity(ex:a10, -, -)
activity(ex:a10, -, -, [prov:type="edit"])
activity(ex:a10, -, 2011-11-16T16:00:00)
@@ -1297,7 +1373,7 @@
</section>
<section id="expression-Generation">
-<h4>Generation</h4>
+<h4><span class="secno">3.1.3 </span>Generation</h4>
@@ -1306,39 +1382,37 @@
<table class="grammar">
-<tbody class="grammar-ref" data-ref="prod-generationExpression"></tbody>
-<tbody class="grammar-ref" data-ref="prod-optionalIdentifier"></tbody>
-<tbody class="grammar-ref" data-ref="prod-identifierOrMarker"></tbody>
+<tbody class="prod"> <tr style="vertical-align: baseline; "> <td><a id="prod-generationExpression" data-name="prod-generationExpression"></a>[<span class="prodNo">9</span>] </td> <td><code class="production prod">generationExpression</code></td> <td> ::= </td> <td><code class="content">"wasGeneratedBy" "(" <span class="prod"><a class="grammarRef" href="#prod-optionalIdentifier">optionalIdentifier</a></span> <span class="prod"><a class="grammarRef" href="#prod-eIdentifier">eIdentifier</a></span> ( "," <span class="prod"><a class="grammarRef" href="#prod-aIdentifierOrMarker">aIdentifierOrMarker</a></span> "," <span class="prod"><a class="grammarRef" href="#prod-timeOrMarker">timeOrMarker</a></span> )? <span class="prod"><a class="grammarRef" href="#prod-optionalAttributeValuePairs">optionalAttributeValuePairs</a></span> ")"</code></td> </tr> </tbody>
+<tbody class="prod"> <tr style="vertical-align: baseline; "> <td><a id="prod-optionalIdentifier" data-name="prod-optionalIdentifier"></a>[<span class="prodNo">10</span>] </td> <td><code class="production prod">optionalIdentifier</code></td> <td> ::= </td> <td><code class="content">( <span class="prod"><a class="grammarRef" href="#prod-identifierOrMarker">identifierOrMarker</a></span> ";" )?</code></td> </tr> </tbody>
+<tbody class="prod"> <tr style="vertical-align: baseline; "> <td><a id="prod-identifierOrMarker" data-name="prod-identifierOrMarker"></a>[<span class="prodNo">11</span>] </td> <td><code class="production prod">identifierOrMarker</code></td> <td> ::= </td> <td><code class="content">( <span class="prod"><a class="grammarRef" href="#prod-identifier">identifier</a></span> | "-" )</code></td> </tr> </tbody>
</table>
<p>The following table summarizes how each constituent of a PROV-DM Generation maps to a PROV-N syntax element.</p>
<div style="text-align: left; ">
<table class="thinborder" style="margin-left: auto; margin-right: auto;">
-<tr><td><b><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#dfn-wasgeneratedby">Generation</a></b></td><td><b>Non-Terminal</b></td></tr>
+<tbody><tr><td><b><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#dfn-wasgeneratedby">Generation</a></b></td><td><b>Non-Terminal</b></td></tr>
<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#generation.id"><span class='attribute' id="generation.id">id</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-optionalIdentifier">optionalIdentifier</a></code></td></tr>
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#generation.entity"><span class='attribute' id="generation.entity">entity</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-eIdentifier">eIdentifier</a></code></td></tr>
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#generation.activity"><span class='attribute' id="generation.activity">activity</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-aIdentifierOrMarker">aIdentifierOrMarker</a></code></td></tr>
-
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#generation.time"><span class='attribute' id="generation.time">time</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-timeOrMarker">timeOrMarker</a></code></td></tr>
-
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#generation.attributes"><span class='attribute' id="generation.attributes">attributes</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-optionalAttributeValuePairs">optionalAttributeValuePairs</a></code></td></tr>
-</table>
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#generation.id"><span class="attribute" id="generation.id">id</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-optionalIdentifier">optionalIdentifier</a></code></td></tr>
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#generation.entity"><span class="attribute" id="generation.entity">entity</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-eIdentifier">eIdentifier</a></code></td></tr>
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#generation.activity"><span class="attribute" id="generation.activity">activity</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-aIdentifierOrMarker">aIdentifierOrMarker</a></code></td></tr>
+
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#generation.time"><span class="attribute" id="generation.time">time</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-timeOrMarker">timeOrMarker</a></code></td></tr>
+
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#generation.attributes"><span class="attribute" id="generation.attributes">attributes</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-optionalAttributeValuePairs">optionalAttributeValuePairs</a></code></td></tr>
+</tbody></table>
</div>
-<div class="anexample">
-
-<pre class="codeexample">
-wasGeneratedBy(ex:g1; tr:WD-prov-dm-20111215, ex:edit1, 2011-11-16T16:00:00, [ex:fct="save"])
+<div class="anexample" id="example_13"><div class="anexampleTitle"><a class="internalDFN" href="#example_13">Example 13</a></div>
+
+<pre class="codeexample">wasGeneratedBy(ex:g1; tr:WD-prov-dm-20111215, ex:edit1, 2011-11-16T16:00:00, [ex:fct="save"])
</pre>
<p> Here <span class="name">ex:g1</span> is the optional generation identifier, <span class="name">tr:WD-prov-dm-20111215</span> is the identifier of the entity being generated,
<span class="name">ex:edit1</span> is the optional identifier of the generating activity, <span class="name">2011-11-16T16:00:00</span> is the optional generation time, and <span class="name"> [ex:fct="save"]</span> are optional attributes. </p>
The remaining examples show cases where some of the optionals are omitted.
-<pre class="codeexample">
-wasGeneratedBy(e2, a1, -)
+<pre class="codeexample">wasGeneratedBy(e2, a1, -)
wasGeneratedBy(e2, a1, 2011-11-16T16:00:00)
wasGeneratedBy(e2, a1, -, [ex:fct="save"])
wasGeneratedBy(e2, [ex:fct="save"])
@@ -1358,41 +1432,39 @@
</section>
<section id="expression-Usage">
-<h4>Usage</h4>
+<h4><span class="secno">3.1.4 </span>Usage</h4>
<table class="grammar">
-<tbody class="grammar-ref" data-ref="prod-usageExpression"></tbody>
+<tbody class="prod"> <tr style="vertical-align: baseline; "> <td><a id="prod-usageExpression" data-name="prod-usageExpression"></a>[<span class="prodNo">12</span>] </td> <td><code class="production prod">usageExpression</code></td> <td> ::= </td> <td><code class="content">"used" "(" <span class="prod"><a class="grammarRef" href="#prod-optionalIdentifier">optionalIdentifier</a></span> <span class="prod"><a class="grammarRef" href="#prod-aIdentifier">aIdentifier</a></span> ( "," <span class="prod"><a class="grammarRef" href="#prod-eIdentifierOrMarker">eIdentifierOrMarker</a></span> "," <span class="prod"><a class="grammarRef" href="#prod-timeOrMarker">timeOrMarker</a></span> )? <span class="prod"><a class="grammarRef" href="#prod-optionalAttributeValuePairs">optionalAttributeValuePairs</a></span> ")"</code></td> </tr> </tbody>
</table>
<p>The following table summarizes how each constituent of a PROV-DM Usage maps to a PROV-N syntax element.</p>
<div style="text-align: left; ">
<table class="thinborder" style="margin-left: auto; margin-right: auto;">
-<tr><td><b><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#dfn-used">Usage</a></b></td><td><b>Non-Terminal</b></td></tr>
+<tbody><tr><td><b><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#dfn-used">Usage</a></b></td><td><b>Non-Terminal</b></td></tr>
<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#usage.id"><span class='attribute' id="usage.id">id</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-optionalIdentifier">optionalIdentifier</a></code></td></tr>
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#usage.activity"><span class='attribute' id="usage.activity">activity</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-aIdentifier">aIdentifier</a></code></td></tr><tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#usage.entity"><span class='attribute' id="usage.entity">entity</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-eIdentifierOrMarker">eIdentifierOrMarker</a></code></td></tr>
-
-
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#usage.time"><span class='attribute' id="usage.time">time</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-timeOrMarker">timeOrMarker</a></code></td></tr>
-
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#usage.attributes"><span class='attribute' id="usage.attributes">attributes</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-optionalAttributeValuePairs">optionalAttributeValuePairs</a></code></td></tr>
-</table>
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#usage.id"><span class="attribute" id="usage.id">id</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-optionalIdentifier">optionalIdentifier</a></code></td></tr>
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#usage.activity"><span class="attribute" id="usage.activity">activity</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-aIdentifier">aIdentifier</a></code></td></tr><tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#usage.entity"><span class="attribute" id="usage.entity">entity</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-eIdentifierOrMarker">eIdentifierOrMarker</a></code></td></tr>
+
+
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#usage.time"><span class="attribute" id="usage.time">time</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-timeOrMarker">timeOrMarker</a></code></td></tr>
+
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#usage.attributes"><span class="attribute" id="usage.attributes">attributes</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-optionalAttributeValuePairs">optionalAttributeValuePairs</a></code></td></tr>
+</tbody></table>
</div>
-<div class="anexample">
+<div class="anexample" id="example_14"><div class="anexampleTitle"><a class="internalDFN" href="#example_14">Example 14</a></div>
-<pre class="codeexample">
-used(ex:u1; ex:act2, ar3:0111, 2011-11-16T16:00:00, [ex:fct="load"])
+<pre class="codeexample">used(ex:u1; ex:act2, ar3:0111, 2011-11-16T16:00:00, [ex:fct="load"])
</pre>
<p> Here <span class="name">ex:u1</span> is the optional usage identifier, <span class="name">ex:act2</span> is the identifier of the using activity,
<span class="name">ar3:0111</span> is the identifier of the entity being used,
<span class="name">2011-11-16T16:00:00</span> is the optional usage time, and <span class="name"> [ex:fct="load"]</span> are optional attributes.</p>
The remaining examples show cases where some of the optionals are omitted.
- <pre class="codeexample">
-used(ex:act2)
+ <pre class="codeexample">used(ex:act2)
used(ex:act2, ar3:0111, 2011-11-16T16:00:00)
used(a1,e1, -, [ex:fct="load"])
used(ex:u1; ex:act2, ar3:0111, -)
@@ -1406,11 +1478,11 @@
</section>
<section id="expression-wasInformedBy">
-<h4>Communication</h4>
+<h4><span class="secno">3.1.5 </span>Communication</h4>
<table class="grammar">
-<tbody class="grammar-ref" data-ref="prod-communicationExpression"></tbody>
+<tbody class="prod"> <tr style="vertical-align: baseline; "> <td><a id="prod-communicationExpression" data-name="prod-communicationExpression"></a>[<span class="prodNo">13</span>] </td> <td><code class="production prod">communicationExpression</code></td> <td> ::= </td> <td><code class="content">"wasInformedBy" "(" <span class="prod"><a class="grammarRef" href="#prod-optionalIdentifier">optionalIdentifier</a></span> <span class="prod"><a class="grammarRef" href="#prod-aIdentifier">aIdentifier</a></span> "," <span class="prod"><a class="grammarRef" href="#prod-aIdentifier">aIdentifier</a></span> <span class="prod"><a class="grammarRef" href="#prod-optionalAttributeValuePairs">optionalAttributeValuePairs</a></span> ")"</code></td> </tr> </tbody>
</table>
@@ -1418,31 +1490,29 @@
<p>The following table summarizes how each constituent of a PROV-DM Communication maps to a PROV-N syntax element.</p>
<div style="text-align: left; ">
<table class="thinborder" style="margin-left: auto; margin-right: auto;">
-<tr><td><b><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#dfn-wasinformedby">Communication</a></b></td><td><b>Non-Terminal</b></td></tr>
+<tbody><tr><td><b><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#dfn-wasinformedby">Communication</a></b></td><td><b>Non-Terminal</b></td></tr>
<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#communication.id"><span class='attribute' id="communication.id">id</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-optionalIdentifier">optionalIdentifier</a></code></td></tr>
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#communication.informed"><span class='attribute' id="communication.informed">informed</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-aIdentifier">aIdentifier</a></code></td></tr>
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#communication.informant"><span class='attribute' id="communication.informant">informant</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-aIdentifier">aIdentifier</a></code></td></tr>
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#communication.attributes"><span class='attribute' id="communication.attributes">attributes</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-optionalAttributeValuePairs">optionalAttributeValuePairs</a></code></td></tr>
-</table>
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#communication.id"><span class="attribute" id="communication.id">id</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-optionalIdentifier">optionalIdentifier</a></code></td></tr>
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#communication.informed"><span class="attribute" id="communication.informed">informed</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-aIdentifier">aIdentifier</a></code></td></tr>
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#communication.informant"><span class="attribute" id="communication.informant">informant</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-aIdentifier">aIdentifier</a></code></td></tr>
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#communication.attributes"><span class="attribute" id="communication.attributes">attributes</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-optionalAttributeValuePairs">optionalAttributeValuePairs</a></code></td></tr>
+</tbody></table>
</div>
-<div class="anexample">
-<pre class="codeexample">
-wasInformedBy(ex:inf1; ex:a1, ex:a2, [ex:param1="a", ex:param2="b"])
+<div class="anexample" id="example_15"><div class="anexampleTitle"><a class="internalDFN" href="#example_15">Example 15</a></div>
+<pre class="codeexample">wasInformedBy(ex:inf1; ex:a1, ex:a2, [ex:param1="a", ex:param2="b"])
</pre>
<p> Here <span class="name">ex:inf1</span> is the optional communication identifier, <span class="name">ex:a1</span> is the identifier of the informed activity,
<span class="name">ex:a2</span> is the identifier of the informant activity,
and <span class="name">[ex:param1="a", ex:param2="b"]</span> are optional attributes. </p>
The remaining examples show cases where some of the optionals are omitted.
-<pre class="codeexample">
-wasInformedBy(ex:a1, ex:a2)
+<pre class="codeexample">wasInformedBy(ex:a1, ex:a2)
wasInformedBy(ex:a1, ex:a2, [ex:param1="a", ex:param2="b"])
-wasInformedBy(i; ex:a1, ex:a2)
-wasInformedBy(i; ex:a1, ex:a2, [ex:param1="a", ex:param2="b"])
+wasInformedBy(ex:i; ex:a1, ex:a2)
+wasInformedBy(ex:i; ex:a1, ex:a2, [ex:param1="a", ex:param2="b"])
</pre>
</div>
</section>
@@ -1450,45 +1520,43 @@
<section id="expression-Start">
-<h4>Start</h4>
+<h4><span class="secno">3.1.6 </span>Start</h4>
<table class="grammar">
-<tbody class="grammar-ref" data-ref="prod-startExpression"></tbody>
+<tbody class="prod"> <tr style="vertical-align: baseline; "> <td><a id="prod-startExpression" data-name="prod-startExpression"></a>[<span class="prodNo">14</span>] </td> <td><code class="production prod">startExpression</code></td> <td> ::= </td> <td><code class="content">"wasStartedBy" "(" <span class="prod"><a class="grammarRef" href="#prod-optionalIdentifier">optionalIdentifier</a></span> <span class="prod"><a class="grammarRef" href="#prod-aIdentifier">aIdentifier</a></span> ( "," <span class="prod"><a class="grammarRef" href="#prod-eIdentifierOrMarker">eIdentifierOrMarker</a></span> "," <span class="prod"><a class="grammarRef" href="#prod-aIdentifierOrMarker">aIdentifierOrMarker</a></span> "," <span class="prod"><a class="grammarRef" href="#prod-timeOrMarker">timeOrMarker</a></span> )? <span class="prod"><a class="grammarRef" href="#prod-optionalAttributeValuePairs">optionalAttributeValuePairs</a></span> ")"</code></td> </tr> </tbody>
</table>
<p>The following table summarizes how each constituent of a PROV-DM Start maps to a PROV-N syntax element.</p>
<div style="text-align: left; ">
<table class="thinborder" style="margin-left: auto; margin-right: auto;">
-<tr><td><b><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#dfn-wasstartedby">Start</a></b></td><td><b>Non-Terminal</b></td></tr>
+<tbody><tr><td><b><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#dfn-wasstartedby">Start</a></b></td><td><b>Non-Terminal</b></td></tr>
<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#start.id"><span class='attribute' id="start.id">id</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-optionalIdentifier">optionalIdentifier</a></code></td></tr>
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#start.activity"><span class='attribute' id="start.activity">activity</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-aIdentifier">aIdentifier</a></code></td></tr>
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#start.trigger"><span class='attribute' id="start.trigger">trigger</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-eIdentifierOrMarker">eIdentifierOrMarker</a></code></td></tr>
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#start.starter"><span class='attribute' id="start.starter">starter</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-aIdentifierOrMarker">aIdentifierOrMarker</a></code></td></tr>
-
-
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#start.time"><span class='attribute' id="start.time">time</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-timeOrMarker">timeOrMarker</a></code></td></tr>
-
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#start.attributes"><span class='attribute' id="start.attributes">attributes</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-optionalAttributeValuePairs">optionalAttributeValuePairs</a></code></td></tr>
-</table>
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#start.id"><span class="attribute" id="start.id">id</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-optionalIdentifier">optionalIdentifier</a></code></td></tr>
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#start.activity"><span class="attribute" id="start.activity">activity</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-aIdentifier">aIdentifier</a></code></td></tr>
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#start.trigger"><span class="attribute" id="start.trigger">trigger</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-eIdentifierOrMarker">eIdentifierOrMarker</a></code></td></tr>
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#start.starter"><span class="attribute" id="start.starter">starter</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-aIdentifierOrMarker">aIdentifierOrMarker</a></code></td></tr>
+
+
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#start.time"><span class="attribute" id="start.time">time</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-timeOrMarker">timeOrMarker</a></code></td></tr>
+
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#start.attributes"><span class="attribute" id="start.attributes">attributes</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-optionalAttributeValuePairs">optionalAttributeValuePairs</a></code></td></tr>
+</tbody></table>
</div>
-<div class="anexample">
-
- <pre class="codeexample">
-wasStartedBy(start; ex:act2, ex:trigger, ex:act1, 2011-11-16T16:00:00, [ex:param="a"])
+<div class="anexample" id="example_16"><div class="anexampleTitle"><a class="internalDFN" href="#example_16">Example 16</a></div>
+
+ <pre class="codeexample">wasStartedBy(start; ex:act2, ex:trigger, ex:act1, 2011-11-16T16:00:00, [ex:param="a"])
</pre>
<p>Here <span class="name">start</span> is the optional start identifier, <span class="name">ex:act2</span> is the identifier of the started activity,
<span class="name">ex:trigger</span> is the optional identifier for the entity that triggered the activity start,
<span class="name">ex:act1</span> is the optional identifier for the activity that generated the (possibly unspecified) entity <span class="name">ex:trigger</span>,
- <span class="name">2011-11-16T16:00:00</span> is the optional start time, and <span class="name"> [ex:param="a"]</span> are optional attributes.</p>
+ <span class="name">2011-11-16T16:00:00</span> is the optional start time, and <span class="name"> [ex:param="a"]</span> is a list of optional attributes.</p>
The remaining examples show cases where some of the optionals are omitted.
- <pre class="codeexample">
-wasStartedBy(ex:act2, -, ex:act1, -)
+ <pre class="codeexample">wasStartedBy(ex:act2, -, ex:act1, -)
wasStartedBy(ex:act2, -, ex:act1, 2011-11-16T16:00:00)
wasStartedBy(ex:act2, -, -, 2011-11-16T16:00:00)
wasStartedBy(ex:act2, [ex:param="a"])
@@ -1503,46 +1571,44 @@
</section>
<section id="expression-End">
-<h4>End</h4>
+<h4><span class="secno">3.1.7 </span>End</h4>
<table class="grammar">
-<tbody class="grammar-ref" data-ref="prod-endExpression"></tbody>
+<tbody class="prod"> <tr style="vertical-align: baseline; "> <td><a id="prod-endExpression" data-name="prod-endExpression"></a>[<span class="prodNo">15</span>] </td> <td><code class="production prod">endExpression</code></td> <td> ::= </td> <td><code class="content">"wasEndedBy" "(" <span class="prod"><a class="grammarRef" href="#prod-optionalIdentifier">optionalIdentifier</a></span> <span class="prod"><a class="grammarRef" href="#prod-aIdentifier">aIdentifier</a></span> ( "," <span class="prod"><a class="grammarRef" href="#prod-eIdentifierOrMarker">eIdentifierOrMarker</a></span> "," <span class="prod"><a class="grammarRef" href="#prod-aIdentifierOrMarker">aIdentifierOrMarker</a></span> "," <span class="prod"><a class="grammarRef" href="#prod-timeOrMarker">timeOrMarker</a></span> )? <span class="prod"><a class="grammarRef" href="#prod-optionalAttributeValuePairs">optionalAttributeValuePairs</a></span> ")"</code></td> </tr> </tbody>
</table>
<p>The following table summarizes how each constituent of a PROV-DM End maps to a PROV-N syntax element.</p>
<div style="text-align: left; ">
<table class="thinborder" style="margin-left: auto; margin-right: auto;">
-<tr><td><b><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#dfn-wasendedby">End</a></b></td><td><b>Non-Terminal</b></td></tr>
+<tbody><tr><td><b><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#dfn-wasendedby">End</a></b></td><td><b>Non-Terminal</b></td></tr>
<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#end.id"><span class='attribute' id="end.id">id</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-optionalIdentifier">optionalIdentifier</a></code></td></tr>
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#end.activity"><span class='attribute' id="end.activity">activity</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-aIdentifier">aIdentifier</a></code></td></tr>
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#end.trigger"><span class='attribute' id="end.trigger">trigger</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-eIdentifierOrMarker">eIdentifierOrMarker</a></code></td></tr>
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#end.ender"><span class='attribute' id="end.ender">ender</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-aIdentifierOrMarker">aIdentifierOrMarker</a></code></td></tr>
-
-
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#end.time"><span class='attribute' id="end.time">time</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-timeOrMarker">timeOrMarker</a></code></td></tr>
-
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#end.attributes"><span class='attribute' id="end.attributes">attributes</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-optionalAttributeValuePairs">optionalAttributeValuePairs</a></code></td></tr>
-</table>
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#end.id"><span class="attribute" id="end.id">id</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-optionalIdentifier">optionalIdentifier</a></code></td></tr>
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#end.activity"><span class="attribute" id="end.activity">activity</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-aIdentifier">aIdentifier</a></code></td></tr>
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#end.trigger"><span class="attribute" id="end.trigger">trigger</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-eIdentifierOrMarker">eIdentifierOrMarker</a></code></td></tr>
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#end.ender"><span class="attribute" id="end.ender">ender</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-aIdentifierOrMarker">aIdentifierOrMarker</a></code></td></tr>
+
+
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#end.time"><span class="attribute" id="end.time">time</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-timeOrMarker">timeOrMarker</a></code></td></tr>
+
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#end.attributes"><span class="attribute" id="end.attributes">attributes</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-optionalAttributeValuePairs">optionalAttributeValuePairs</a></code></td></tr>
+</tbody></table>
</div>
-<div class="anexample">
-
- <pre class="codeexample">
-wasEndedBy(end; ex:act2, ex:trigger, ex:act3, 2011-11-16T16:00:00, [ex:param="a"])
+<div class="anexample" id="example_17"><div class="anexampleTitle"><a class="internalDFN" href="#example_17">Example 17</a></div>
+
+ <pre class="codeexample">wasEndedBy(end; ex:act2, ex:trigger, ex:act3, 2011-11-16T16:00:00, [ex:param="a"])
</pre>
<p> Here <span class="name">end</span> is the optional end identifier,
<span class="name">ex:act2</span> is the identifier of the ending activity,
<span class="name">ex:trigger</span> is the identifier of the entity that triggered the activity end,
<span class="name">ex:act3</span> is the optional identifier for the activity that generated the (possibly unspecified) entity <span class="name">ex:trigger</span>,
- <span class="name">2011-11-16T16:00:00</span> is the optional usage time, and <span class="name"> [ex:param="a"]</span> are optional attributes. </p>
+ <span class="name">2011-11-16T16:00:00</span> is the optional usage time, and <span class="name"> [ex:param="a"]</span> is a list of optional attributes. </p>
The remaining examples show cases where some of the optionals are omitted.
-<pre class="codeexample">
-wasEndedBy(ex:act2, ex:trigger, -, -)
+<pre class="codeexample">wasEndedBy(ex:act2, ex:trigger, -, -)
wasEndedBy(ex:act2, ex:trigger, -, 2011-11-16T16:00:00)
wasEndedBy(ex:act2, -, -, 2011-11-16T16:00:00)
wasEndedBy(ex:act2, -, -, 2011-11-16T16:00:00, [ex:param="a"])
@@ -1559,43 +1625,41 @@
<section id="expression-Invalidation">
-<h4>Invalidation</h4>
+<h4><span class="secno">3.1.8 </span>Invalidation</h4>
<table class="grammar">
-<tbody class="grammar-ref" data-ref="prod-invalidationExpression"></tbody>
+<tbody class="prod"> <tr style="vertical-align: baseline; "> <td><a id="prod-invalidationExpression" data-name="prod-invalidationExpression"></a>[<span class="prodNo">16</span>] </td> <td><code class="production prod">invalidationExpression</code></td> <td> ::= </td> <td><code class="content">"wasInvalidatedBy" "(" <span class="prod"><a class="grammarRef" href="#prod-optionalIdentifier">optionalIdentifier</a></span> <span class="prod"><a class="grammarRef" href="#prod-eIdentifier">eIdentifier</a></span> ( "," <span class="prod"><a class="grammarRef" href="#prod-aIdentifierOrMarker">aIdentifierOrMarker</a></span> "," <span class="prod"><a class="grammarRef" href="#prod-timeOrMarker">timeOrMarker</a></span> )? <span class="prod"><a class="grammarRef" href="#prod-optionalAttributeValuePairs">optionalAttributeValuePairs</a></span> ")"</code></td> </tr> </tbody>
</table>
<p>The following table summarizes how each constituent of a PROV-DM Invalidation maps to a PROV-N syntax element.</p>
<div style="text-align: left; ">
<table class="thinborder" style="margin-left: auto; margin-right: auto;">
-<tr><td><b><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#dfn-wasinvalidatedby">Invalidation</a></b></td><td><b>Non-Terminal</b></td></tr>
+<tbody><tr><td><b><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#dfn-wasinvalidatedby">Invalidation</a></b></td><td><b>Non-Terminal</b></td></tr>
<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#invalidation.id"><span class='attribute' id="invalidation.id">id</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-optionalIdentifier">optionalIdentifier</a></code></td></tr>
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#invalidation.entity"><span class='attribute' id="invalidation.entity">entity</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-eIdentifier">eIdentifier</a></code></td></tr>
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#invalidation.activity"><span class='attribute' id="invalidation.activity">activity</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-aIdentifierOrMarker">aIdentifierOrMarker</a></code></td></tr>
-
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#invalidation.time"><span class='attribute' id="invalidation.time">time</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-timeOrMarker">timeOrMarker</a></code></td></tr>
-
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#invalidation.attributes"><span class='attribute' id="invalidation.attributes">attributes</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-optionalAttributeValuePairs">optionalAttributeValuePairs</a></code></td></tr>
-</table>
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#invalidation.id"><span class="attribute" id="invalidation.id">id</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-optionalIdentifier">optionalIdentifier</a></code></td></tr>
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#invalidation.entity"><span class="attribute" id="invalidation.entity">entity</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-eIdentifier">eIdentifier</a></code></td></tr>
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#invalidation.activity"><span class="attribute" id="invalidation.activity">activity</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-aIdentifierOrMarker">aIdentifierOrMarker</a></code></td></tr>
+
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#invalidation.time"><span class="attribute" id="invalidation.time">time</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-timeOrMarker">timeOrMarker</a></code></td></tr>
+
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#invalidation.attributes"><span class="attribute" id="invalidation.attributes">attributes</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-optionalAttributeValuePairs">optionalAttributeValuePairs</a></code></td></tr>
+</tbody></table>
</div>
-<div class="anexample">
-
-<pre class="codeexample">
-wasInvalidatedBy(ex:inv; tr:WD-prov-dm-20111215, ex:edit1, 2011-11-16T16:00:00, [ex:fct="save"])
+<div class="anexample" id="example_18"><div class="anexampleTitle"><a class="internalDFN" href="#example_18">Example 18</a></div>
+
+<pre class="codeexample">wasInvalidatedBy(ex:inv; tr:WD-prov-dm-20111215, ex:edit1, 2011-11-16T16:00:00, [ex:fct="save"])
</pre>
<p> Here <span class="name">ex:inv</span> is the optional invalidation identifier, <span class="name">tr:WD-prov-dm-20111215</span> is the identifier of the entity being invalidated,
- <span class="name">ex:edit1</span> is the optional identifier of the invalidating activity, <span class="name">2011-11-16T16:00:00</span> is the optional invalidation time, and <span class="name"> [ex:fct="save"]</span> are optional attributes. </p>
+ <span class="name">ex:edit1</span> is the optional identifier of the invalidating activity, <span class="name">2011-11-16T16:00:00</span> is the optional invalidation time, and <span class="name"> [ex:fct="save"]</span> is a list of optional attributes. </p>
The remaining examples show cases where some of the optionals are omitted.
-<pre class="codeexample">
-wasInvalidatedBy(tr:WD-prov-dm-20111215, ex:edit1, -)
+<pre class="codeexample">wasInvalidatedBy(tr:WD-prov-dm-20111215, ex:edit1, -)
wasInvalidatedBy(tr:WD-prov-dm-20111215, ex:edit1, 2011-11-16T16:00:00)
wasInvalidatedBy(e2, a1, -, [ex:fct="save"])
wasInvalidatedBy(e2, -, -, [ex:fct="save"])
@@ -1616,46 +1680,45 @@
</section>
<section id="component2">
-<h3>Component 2: Derivations</h3>
+<h3><span class="secno">3.2 </span>Component 2: Derivations</h3>
<section id="Derivation-Relation">
-<h4>Derivation</h4>
+<h4><span class="secno">3.2.1 </span>Derivation</h4>
<table class="grammar">
-<tbody class="grammar-ref" data-ref="prod-derivationExpression"></tbody>
+<tbody class="prod"> <tr style="vertical-align: baseline; "> <td><a id="prod-derivationExpression" data-name="prod-derivationExpression"></a>[<span class="prodNo">17</span>] </td> <td><code class="production prod">derivationExpression</code></td> <td> ::= </td> <td><code class="content">"wasDerivedFrom" "(" <span class="prod"><a class="grammarRef" href="#prod-optionalIdentifier">optionalIdentifier</a></span> <span class="prod"><a class="grammarRef" href="#prod-eIdentifier">eIdentifier</a></span> "," <span class="prod"><a class="grammarRef" href="#prod-eIdentifier">eIdentifier</a></span> ( "," <span class="prod"><a class="grammarRef" href="#prod-aIdentifierOrMarker">aIdentifierOrMarker</a></span> "," <span class="prod"><a class="grammarRef" href="#prod-gIdentifierOrMarker">gIdentifierOrMarker</a></span> "," <span class="prod"><a class="grammarRef" href="#prod-uIdentifierOrMarker">uIdentifierOrMarker</a></span> )? <span class="prod"><a class="grammarRef" href="#prod-optionalAttributeValuePairs">optionalAttributeValuePairs</a></span> ")"</code></td> </tr> </tbody>
</table>
<p>The following table summarizes how each constituent of a PROV-DM Derivation maps to a PROV-N syntax element.</p>
<div style="text-align: left; ">
<table class="thinborder" style="margin-left: auto; margin-right: auto;">
-<tr><td><b><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#dfn-wasderivedfrom">Derivation</a></b></td><td><b>Non-Terminal</b></td></tr>
+<tbody><tr><td><b><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#dfn-wasderivedfrom">Derivation</a></b></td><td><b>Non-Terminal</b></td></tr>
<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#derivation.id"><span class='attribute' id="derivation.id">id</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-optionalIdentifier">optionalIdentifier</a></code></td></tr>
-
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#derivation.generatedEntity"><span class='attribute' id="derivation.generatedEntity">generatedEntity</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-eIdentifier">eIdentifier</a></code></td></tr>
-
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#derivation.usedEntity"><span class='attribute' id="derivation.usedEntity">usedEntity</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-eIdentifier">eIdentifier</a></code></td></tr>
-
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#derivation.activity"><span class='attribute' id="derivation.activity">activity</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-aIdentifierOrMarker">aIdentifierOrMarker</a></code></td></tr>
-
-
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#derivation.generation"><span class='attribute' id="derivation.generation">generation</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-gIdentifierOrMarker">gIdentifierOrMarker</a></code></td></tr>
-
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#derivation.usage"><span class='attribute' id="derivation.usage">usage</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-uIdentifierOrMarker">uIdentifierOrMarker</a></code></td></tr>
-
-
-
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#derivation.attributes"><span class='attribute' id="derivation.attributes">attributes</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-optionalAttributeValuePairs">optionalAttributeValuePairs</a></code></td></tr>
-</table>
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#derivation.id"><span class="attribute" id="derivation.id">id</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-optionalIdentifier">optionalIdentifier</a></code></td></tr>
+
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#derivation.generatedEntity"><span class="attribute" id="derivation.generatedEntity">generatedEntity</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-eIdentifier">eIdentifier</a></code></td></tr>
+
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#derivation.usedEntity"><span class="attribute" id="derivation.usedEntity">usedEntity</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-eIdentifier">eIdentifier</a></code></td></tr>
+
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#derivation.activity"><span class="attribute" id="derivation.activity">activity</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-aIdentifierOrMarker">aIdentifierOrMarker</a></code></td></tr>
+
+
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#derivation.generation"><span class="attribute" id="derivation.generation">generation</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-gIdentifierOrMarker">gIdentifierOrMarker</a></code></td></tr>
+
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#derivation.usage"><span class="attribute" id="derivation.usage">usage</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-uIdentifierOrMarker">uIdentifierOrMarker</a></code></td></tr>
+
+
+
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#derivation.attributes"><span class="attribute" id="derivation.attributes">attributes</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-optionalAttributeValuePairs">optionalAttributeValuePairs</a></code></td></tr>
+</tbody></table>
</div>
-<div class="anexample" id="anexample-derivation">
- <pre class="codeexample">
-wasDerivedFrom(d; e2, e1, a, g2, u1, [ex:comment="a righteous derivation"])
+<div class="anexample" id="anexample-derivation"><div class="anexampleTitle"><a class="internalDFN" href="#anexample-derivation">Example 19</a></div>
+ <pre class="codeexample">wasDerivedFrom(d; e2, e1, a, g2, u1, [ex:comment="a righteous derivation"])
</pre>
<p> Here
<span class="name">d</span> is the optional derivation identifier,
@@ -1664,12 +1727,11 @@
<span class="name">a</span> is the optional identifier of the activity which used/generated the entities,
<span class="name">g2</span> is the optional identifier of the generation,
<span class="name">u1</span> is the optional identifier of the usage,
- and <span class="name">[ex:comment="a righteous derivation"]</span> are optional attributes. </p>
+ and <span class="name">[ex:comment="a righteous derivation"]</span> is a list of optional attributes. </p>
The remaining examples show cases where some of the optionals are omitted.
-<pre class="codeexample">
-wasDerivedFrom(e2, e1)
+<pre class="codeexample">wasDerivedFrom(e2, e1)
wasDerivedFrom(e2, e1, a, g2, u1)
wasDerivedFrom(e2, e1, -, g2, u1)
wasDerivedFrom(e2, e1, a, -, u1)
@@ -1684,63 +1746,60 @@
</section>
<section id="expression-Revision">
-<h4>Revision</h4>
+<h4><span class="secno">3.2.2 </span>Revision</h4>
<p id="provn-type-Revision">
-PROV-N provides no dedicated syntax for Revision. Instead, a Revision MUST be expressed as a
+PROV-N provides no dedicated syntax for Revision. Instead, a Revision <em class="rfc2119" title="MUST">MUST</em> be expressed as a
<code class="content"><a class="grammarRef" href="#prod-derivationExpression">derivationExpression</a></code> with attribute <code>prov:type='prov:Revision'</code>.</p>
-<div class="anexample">
- <pre class="codeexample">
-wasDerivedFrom(d; e2, e1, a, g2, u1,
+<div class="anexample" id="example_20"><div class="anexampleTitle"><a class="internalDFN" href="#example_20">Example 20</a></div>
+ <pre class="codeexample">wasDerivedFrom(d; e2, e1, a, g2, u1,
[prov:type='prov:Revision',
ex:comment="a righteous derivation"])
</pre>
<p>Here, the derivation from
-<a href="#anexample-derivation" class="anexample-ref"><span>Example REF</span></a>
+<a href="#anexample-derivation" class="anexample-ref"><span>Example 19</span></a>
is extended with a <span class="name">prov:type</span> attribute and value <span class="name">prov:Revision</span>. The expression <code>'prov:Revision'</code> is <code class="content"><a class="grammarRef" href="#prod-convenienceNotation">convenienceNotation</a></code> to denote a <code class="content"><a class="grammarRef" href="#prod-QUALIFIED_NAME">QUALIFIED_NAME</a></code> literal (See <a href="#expression-literal">Section 3.7.3. Literal</a>).
-</div>
+</p></div>
</section> <!-- end revision -->
<section id="expression-quotation">
-<h4>Quotation</h4>
+<h4><span class="secno">3.2.3 </span>Quotation</h4>
<p id="provn-type-Quotation">
-PROV-N provides no dedicated syntax for Quotation. Instead, a Quotation MUST be expressed as a
+PROV-N provides no dedicated syntax for Quotation. Instead, a Quotation <em class="rfc2119" title="MUST">MUST</em> be expressed as a
<code class="content"><a class="grammarRef" href="#prod-derivationExpression">derivationExpression</a></code> with attribute <code>prov:type='prov:Quotation'</code>.</p>
-<div class="anexample">
- <pre class="codeexample">
-wasDerivedFrom(quoteId1; ex:blockQuote,ex:blog, ex:act1, ex:g, ex:u,
+<div class="anexample" id="example_21"><div class="anexampleTitle"><a class="internalDFN" href="#example_21">Example 21</a></div>
+ <pre class="codeexample">wasDerivedFrom(quoteId1; ex:blockQuote,ex:blog, ex:act1, ex:g, ex:u,
[ prov:type='prov:Quotation' ])
</pre>
<p>Here, the derivation is provided with a <span class="name">prov:type</span> attribute and value <span class="name">prov:Quotation</span>.
-</div>
+</p></div>
</section> <!-- end quotation -->
<section id="expression-primary-source">
-<h4>Primary Source</h4>
+<h4><span class="secno">3.2.4 </span>Primary Source</h4>
<p id="provn-type-Primary-Source">
-PROV-N provides no dedicated syntax for PrimarySource. Instead, a PrimarySource MUST be expressed as a
+PROV-N provides no dedicated syntax for PrimarySource. Instead, a PrimarySource <em class="rfc2119" title="MUST">MUST</em> be expressed as a
<code class="content"><a class="grammarRef" href="#prod-derivationExpression">derivationExpression</a></code> with attribute <code>prov:type='prov:Primary-Source'</code>.</p>
-<div class="anexample">
- <pre class="codeexample">
-wasDerivedFrom(sourceId1; ex:e1, ex:e2, ex:act, ex:g, ex:u,
+<div class="anexample" id="example_22"><div class="anexampleTitle"><a class="internalDFN" href="#example_22">Example 22</a></div>
+ <pre class="codeexample">wasDerivedFrom(sourceId1; ex:e1, ex:e2, ex:act, ex:g, ex:u,
[ prov:type='prov:PrimarySource' ])
</pre>
<p>Here, the derivation is provided with a <span class="name">prov:type</span> attribute and value <span class="name">prov:PrimarySource</span>.
@@ -1754,9 +1813,9 @@
<section id="component3">
-<h3>Component 3: Agents, Responsibility, and Influence</h3>
+<h3><span class="secno">3.3 </span>Component 3: Agents, Responsibility, and Influence</h3>
<section id="expression-Agent">
-<h4>Agent</h4>
+<h4><span class="secno">3.3.1 </span>Agent</h4>
<!--
<div class='grammar'>
@@ -1772,50 +1831,48 @@
<table class="grammar">
-<tbody class="grammar-ref" data-ref="prod-agentExpression"></tbody>
+<tbody class="prod"> <tr style="vertical-align: baseline; "> <td><a id="prod-agentExpression" data-name="prod-agentExpression"></a>[<span class="prodNo">18</span>] </td> <td><code class="production prod">agentExpression</code></td> <td> ::= </td> <td><code class="content">"agent" "(" <span class="prod"><a class="grammarRef" href="#prod-identifier">identifier</a></span> <span class="prod"><a class="grammarRef" href="#prod-optionalAttributeValuePairs">optionalAttributeValuePairs</a></span> ")"</code></td> </tr> </tbody>
</table>
<p>The following table summarizes how each constituent of a PROV-DM Agent maps to a PROV-N syntax element.</p>
<div style="text-align: left; ">
<table class="thinborder" style="margin-left: auto; margin-right: auto;">
-<tr><td><b><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#dfn-agent">Agent</a></b></td><td><b>Non-Terminal</b></td></tr>
+<tbody><tr><td><b><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#dfn-agent">Agent</a></b></td><td><b>Non-Terminal</b></td></tr>
<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#agent.id"><span class='attribute' id="agent.id">id</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-identifier">identifier</a></code></td></tr>
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#agent.attributes"><span class='attribute' id="agent.attributes">attributes</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-optionalAttributeValuePairs">optionalAttributeValuePairs</a></code></td></tr>
-</table>
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#agent.id"><span class="attribute" id="agent.id">id</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-identifier">identifier</a></code></td></tr>
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#agent.attributes"><span class="attribute" id="agent.attributes">attributes</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-optionalAttributeValuePairs">optionalAttributeValuePairs</a></code></td></tr>
+</tbody></table>
</div>
<p>
-PROV-N provides no dedicated syntax for Person, Organization, SoftwareAgent. Instead, a Person, an Organization, or a SoftwareAgent MUST be expressed as an
+PROV-N provides no dedicated syntax for Person, Organization, SoftwareAgent. Instead, a Person, an Organization, or a SoftwareAgent <em class="rfc2119" title="MUST">MUST</em> be expressed as an
<code class="content"><a class="grammarRef" href="#prod-agentExpression">agentExpression</a></code> with attribute
<span id="provn-type-Person"><code>prov:type='prov:Person'</code></span>,
<span id="provn-type-Organization"><code>prov:type='prov:Organization'</code></span>, or
<span id="provn-type-SoftwareAgent"><code>prov:type='prov:SoftwareAgent'</code></span>, respectively.</p>
-<div class="anexample">
-<pre class="codeexample">
-agent(ag4, [ prov:type='prov:Person', ex:name="David" ])
+<div class="anexample" id="example_23"><div class="anexampleTitle"><a class="internalDFN" href="#example_23">Example 23</a></div>
+<pre class="codeexample">agent(ag4, [ prov:type='prov:Person', ex:name="David" ])
</pre>
<p>Here <span class="name">ag</span> is the agent identifier, and
- <span class="name">[ prov:type='prov:Person', ex:name="David" ]</span> are optional attributes. </p>
+ <span class="name">[ prov:type='prov:Person', ex:name="David" ]</span> is a list of optional attributes. </p>
In the next example, the optional attributes are omitted.
-<pre class="codeexample">
-agent(ag4)
+<pre class="codeexample">agent(ag4)
</pre>
</div>
</section>
<section id="expression-attribution">
-<h4>Attribution</h4>
+<h4><span class="secno">3.3.2 </span>Attribution</h4>
<table class="grammar">
-<tbody class="grammar-ref" data-ref="prod-attributionExpression"></tbody>
+<tbody class="prod"> <tr style="vertical-align: baseline; "> <td><a id="prod-attributionExpression" data-name="prod-attributionExpression"></a>[<span class="prodNo">19</span>] </td> <td><code class="production prod">attributionExpression</code></td> <td> ::= </td> <td><code class="content">"wasAttributedTo" "(" <span class="prod"><a class="grammarRef" href="#prod-optionalIdentifier">optionalIdentifier</a></span> <span class="prod"><a class="grammarRef" href="#prod-eIdentifier">eIdentifier</a></span> "," <span class="prod"><a class="grammarRef" href="#prod-agIdentifier">agIdentifier</a></span> <span class="prod"><a class="grammarRef" href="#prod-optionalAttributeValuePairs">optionalAttributeValuePairs</a></span> ")"</code></td> </tr> </tbody>
</table>
@@ -1823,31 +1880,29 @@
<p>The following table summarizes how each constituent of a PROV-DM Attribution maps to a PROV-N syntax element.</p>
<div style="text-align: left; ">
<table class="thinborder" style="margin-left: auto; margin-right: auto;">
-<tr><td><b><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#dfn-wasattributedto">Attribution</a></b></td><td><b>Non-Terminal</b></td></tr>
+<tbody><tr><td><b><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#dfn-wasattributedto">Attribution</a></b></td><td><b>Non-Terminal</b></td></tr>
<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#attribution.id"><span class='attribute' id="attribution.id">id</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-optionalIdentifier">optionalIdentifier</a></code></td></tr>
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#attribution.entity"><span class='attribute' id="attribution.entity">entity</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-identifier">eIdentifier</a></code></td></tr>
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#attribution.agent"><span class='attribute' id="attribution.agent">agent</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-agIdentifier">agIdentifier</a></code></td></tr>
-
-
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#attribution.attributes"><span class='attribute' id="attribution.attributes">attributes</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-optionalAttributeValuePairs">optionalAttributeValuePairs</a></code></td></tr>
-</table>
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#attribution.id"><span class="attribute" id="attribution.id">id</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-optionalIdentifier">optionalIdentifier</a></code></td></tr>
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#attribution.entity"><span class="attribute" id="attribution.entity">entity</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-identifier">eIdentifier</a></code></td></tr>
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#attribution.agent"><span class="attribute" id="attribution.agent">agent</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-agIdentifier">agIdentifier</a></code></td></tr>
+
+
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#attribution.attributes"><span class="attribute" id="attribution.attributes">attributes</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-optionalAttributeValuePairs">optionalAttributeValuePairs</a></code></td></tr>
+</tbody></table>
</div>
-<div class="anexample">
-
-<pre class="codeexample">
-wasAttributedTo(attr; e, ag, [ex:license='cc:attributionURL' ])
+<div class="anexample" id="example_24"><div class="anexampleTitle"><a class="internalDFN" href="#example_24">Example 24</a></div>
+
+<pre class="codeexample">wasAttributedTo(attr; e, ag, [ex:license='cc:attributionURL' ])
</pre>
<p> Here <span class="name">attr</span> is the optional attribution identifier, <span class="name">e</span> is an entity identifier,
- <span class="name">ag</span> is the identifier of the agent to whom the entity is abscribed,
-and <span class="name">[ex:license='cc:attributionURL' ]</span> are optional attributes. </p>
+ <span class="name">ag</span> is the identifier of the agent to whom the entity is ascribed,
+and <span class="name">[ex:license='cc:attributionURL' ]</span> is a list of optional attributes. </p>
The remaining examples show cases where some of the optionals are omitted.
-<pre class="codeexample">
-wasAttributedTo(e, ag)
+<pre class="codeexample">wasAttributedTo(e, ag)
wasAttributedTo(e, ag, [ex:license='cc:attributionURL' ])
</pre>
</div>
@@ -1856,12 +1911,12 @@
<section id="expression-Association">
-<h4>Association</h4>
+<h4><span class="secno">3.3.3 </span>Association</h4>
<table class="grammar">
-<tbody class="grammar-ref" data-ref="prod-associationExpression"></tbody>
+<tbody class="prod"> <tr style="vertical-align: baseline; "> <td><a id="prod-associationExpression" data-name="prod-associationExpression"></a>[<span class="prodNo">20</span>] </td> <td><code class="production prod">associationExpression</code></td> <td> ::= </td> <td><code class="content">"wasAssociatedWith" "(" <span class="prod"><a class="grammarRef" href="#prod-optionalIdentifier">optionalIdentifier</a></span> <span class="prod"><a class="grammarRef" href="#prod-aIdentifier">aIdentifier</a></span> ( "," <span class="prod"><a class="grammarRef" href="#prod-agIdentifierOrMarker">agIdentifierOrMarker</a></span> "," <span class="prod"><a class="grammarRef" href="#prod-eIdentifierOrMarker">eIdentifierOrMarker</a></span> )? <span class="prod"><a class="grammarRef" href="#prod-optionalAttributeValuePairs">optionalAttributeValuePairs</a></span> ")"</code></td> </tr> </tbody>
</table>
@@ -1869,48 +1924,53 @@
<p>The following table summarizes how each constituent of a PROV-DM Association maps to a PROV-N syntax element.</p>
<div style="text-align: left; ">
<table class="thinborder" style="margin-left: auto; margin-right: auto;">
-<tr><td><b><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#dfn-wasassociatedwith">Association</a></b></td><td><b>Non-Terminal</b></td></tr>
+<tbody><tr><td><b><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#dfn-wasassociatedwith">Association</a></b></td><td><b>Non-Terminal</b></td></tr>
<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#association.id"><span class='attribute' id="association.id">id</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-optionalIdentifier">optionalIdentifier</a></code></td></tr>
-
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#association.activity"><span class='attribute' id="association.activity">activity</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-aIdentifier">aIdentifier</a></code></td></tr>
-
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#association.agent"><span class='attribute' id="association.agent">agent</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-agIdentifierOrMarker">agIdentifierOrMarker</a></code></td></tr>
-
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#association.plan"><span class='attribute' id="association.plan">plan</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-eIdentifierOrMarker">eIdentifierOrMarker</a></code></td></tr>
-
-
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#association.attributes"><span class='attribute' id="association.attributes">attributes</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-optionalAttributeValuePairs">optionalAttributeValuePairs</a></code></td></tr>
-</table>
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#association.id"><span class="attribute" id="association.id">id</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-optionalIdentifier">optionalIdentifier</a></code></td></tr>
+
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#association.activity"><span class="attribute" id="association.activity">activity</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-aIdentifier">aIdentifier</a></code></td></tr>
+
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#association.agent"><span class="attribute" id="association.agent">agent</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-agIdentifierOrMarker">agIdentifierOrMarker</a></code></td></tr>
+
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#association.plan"><span class="attribute" id="association.plan">plan</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-eIdentifierOrMarker">eIdentifierOrMarker</a></code></td></tr>
+
+
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#association.attributes"><span class="attribute" id="association.attributes">attributes</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-optionalAttributeValuePairs">optionalAttributeValuePairs</a></code></td></tr>
+</tbody></table>
</div>
<p id="provn-type-Plan">
-PROV-N provides no dedicated syntax for Plan. Instead, a Plan MUST be expressed as an
+PROV-N provides no dedicated syntax for Plan. Instead, a Plan <em class="rfc2119" title="MUST">MUST</em> be expressed as an
<code class="content"><a class="grammarRef" href="#prod-entityExpression">entityExpression</a></code> with attribute <code>prov:type='prov:Plan'</code>.</p>
-<div class="anexample">
-<pre class="codeexample">
-wasAssociatedWith(ex:assoc; ex:a1, ex:ag1, ex:e1, [ex:param1="a", ex:param2="b"])
+<div class="anexample" id="example_25"><div class="anexampleTitle"><a class="internalDFN" href="#example_25">Example 25</a></div>
+<p>The following expression illustrates a plan.
+</p><pre class="codeexample"> entity(ex:pl1, [ prov:type='prov:Plan' ])
+</pre>
+</div>
+
+
+<div class="anexample" id="example_26"><div class="anexampleTitle"><a class="internalDFN" href="#example_26">Example 26</a></div>
+<pre class="codeexample">wasAssociatedWith(ex:assoc; ex:a1, ex:ag1, ex:pl1, [ex:param1="a", ex:param2="b"])
</pre>
<p> Here <span class="name">ex:assoc</span> is the optional attribution identifier,
<span class="name">ex:a1</span> is an activity identifier,
<span class="name">ex:ag1</span> is the optional identifier of the agent associated to the activity,
- <span class="name">ex:e1</span> is the optional identifier of the plan used by the agent in the context of the activity,
- and <span class="name"> [ex:param1="a", ex:param2="b"]</span> are optional attributes. </p>
+ <span class="name">ex:pl1</span> is the optional identifier of the plan used by the agent in the context of the activity,
+ and <span class="name"> [ex:param1="a", ex:param2="b"]</span> is a list of optional attributes. </p>
The remaining examples show cases where some of the optionals are omitted.
-<pre class="codeexample">
-wasAssociatedWith(ex:a1, -, ex:e1)
+<pre class="codeexample">wasAssociatedWith(ex:a1, -, ex:pl1)
wasAssociatedWith(ex:a1, ex:ag1)
-wasAssociatedWith(ex:a1, ex:ag1, ex:e1)
-wasAssociatedWith(ex:a1, ex:ag1, ex:e1, [ex:param1="a", ex:param2="b"])
-wasAssociatedWith(a; ex:a1, -, ex:e1)
+wasAssociatedWith(ex:a1, ex:ag1, ex:pl1)
+wasAssociatedWith(ex:a1, ex:ag1, ex:pl1, [ex:param1="a", ex:param2="b"])
+wasAssociatedWith(a; ex:a1, -, ex:pl1)
</pre>
</div>
@@ -1918,13 +1978,6 @@
<p>Additional semantic rules (<a href="#semantic-rules-summary">Section 3.7.5</a>) apply to <code class="content"><a class="grammarRef" href="#prod-associationExpression">associationExpression</a></code>.</p>
-<div class="anexample">
-<p>The following expression illustrates a plan.
-<pre class="codeexample">
- entity(ex:pl1, [ prov:type='prov:Plan' ])
-</pre>
-</div>
-
<!--
<p><strong>Note:</strong>The production <code class="content"><a class="grammarRef" href="#prod-associationExpression">associationExpression</a></code> allows for expressions <span class="name">wasAssociatedWith(a, -, -)</span> and <span class="name">wasAssociatedWith(-; a, -, -)</span>. However, these expressions are not valid in PROV-N,
@@ -1934,52 +1987,50 @@
</section>
<section id="expression-delegation">
-<h4>Delegation</h4>
+<h4><span class="secno">3.3.4 </span>Delegation</h4>
<table class="grammar">
-<tbody class="grammar-ref" data-ref="prod-delegationExpression"></tbody>
+<tbody class="prod"> <tr style="vertical-align: baseline; "> <td><a id="prod-delegationExpression" data-name="prod-delegationExpression"></a>[<span class="prodNo">21</span>] </td> <td><code class="production prod">delegationExpression</code></td> <td> ::= </td> <td><code class="content">"actedOnBehalfOf" "(" <span class="prod"><a class="grammarRef" href="#prod-optionalIdentifier">optionalIdentifier</a></span> <span class="prod"><a class="grammarRef" href="#prod-agIdentifier">agIdentifier</a></span> "," <span class="prod"><a class="grammarRef" href="#prod-agIdentifier">agIdentifier</a></span> ( "," <span class="prod"><a class="grammarRef" href="#prod-aIdentifierOrMarker">aIdentifierOrMarker</a></span> )? <span class="prod"><a class="grammarRef" href="#prod-optionalAttributeValuePairs">optionalAttributeValuePairs</a></span> ")"</code></td> </tr> </tbody>
</table>
<p>The following table summarizes how each constituent of a PROV-DM Delegation maps to a PROV-N syntax element.</p>
<div style="text-align: left; ">
<table class="thinborder" style="margin-left: auto; margin-right: auto;">
-<tr><td><b><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#dfn-actedonbehalfof">Delegation</a></b></td><td><b>Non-Terminal</b></td></tr>
+<tbody><tr><td><b><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#dfn-actedonbehalfof">Delegation</a></b></td><td><b>Non-Terminal</b></td></tr>
<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#delegation.id"><span class='attribute' id="delegation.id">id</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-optionalIdentifier">optionalIdentifier</a></code></td></tr>
-
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#delegation.delegate"><span class='attribute' id="delegation.delegate">delegate</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-agIdentifier">agIdentifier</a></code></td></tr>
-
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#delegation.responsible"><span class='attribute' id="delegation.responsible">responsible</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-agIdentifier">agIdentifier</a></code></td></tr>
-
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#delegation.activity"><span class='attribute' id="delegation.activity">activity</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-aIdentifierOrMarker">aIdentifierOrMarker</a></code></td></tr>
-
-
-
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#delegation.attributes"><span class='attribute' id="delegation.attributes">attributes</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-optionalAttributeValuePairs">optionalAttributeValuePairs</a></code></td></tr>
-</table>
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#delegation.id"><span class="attribute" id="delegation.id">id</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-optionalIdentifier">optionalIdentifier</a></code></td></tr>
+
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#delegation.delegate"><span class="attribute" id="delegation.delegate">delegate</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-agIdentifier">agIdentifier</a></code></td></tr>
+
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#delegation.responsible"><span class="attribute" id="delegation.responsible">responsible</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-agIdentifier">agIdentifier</a></code></td></tr>
+
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#delegation.activity"><span class="attribute" id="delegation.activity">activity</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-aIdentifierOrMarker">aIdentifierOrMarker</a></code></td></tr>
+
+
+
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#delegation.attributes"><span class="attribute" id="delegation.attributes">attributes</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-optionalAttributeValuePairs">optionalAttributeValuePairs</a></code></td></tr>
+</tbody></table>
</div>
-<div class="anexample">
-
- <pre class="codeexample">
-actedOnBehalfOf(del1; ag2, ag1, a, [prov:type="contract"])
+<div class="anexample" id="example_27"><div class="anexampleTitle"><a class="internalDFN" href="#example_27">Example 27</a></div>
+
+ <pre class="codeexample">actedOnBehalfOf(del1; ag2, ag1, a, [prov:type="contract"])
</pre>
<p> Here <span class="name">del1</span> is the optional delegation identifier,
<span class="name">ag2</span> is the identifier for the delegate agent,
<span class="name">ag1</span> is the identifier of the responsible agent,
<span class="name">a</span> is the optional identifier of the activity for which the delegation link holds,
- and <span class="name">[prov:type="contract"]</span> are optional attributes. </p>
+ and <span class="name">[prov:type="contract"]</span> is a list of optional attributes. </p>
The remaining examples show cases where some of the optionals are omitted.
-<pre class="codeexample">
-actedOnBehalfOf(ag1, ag2)
+<pre class="codeexample">actedOnBehalfOf(ag1, ag2)
actedOnBehalfOf(ag1, ag2, a)
actedOnBehalfOf(ag1, ag2, -, [prov:type="delegation"])
actedOnBehalfOf(ag2, ag3, a, [prov:type="contract"])
@@ -1991,34 +2042,33 @@
</section>
<section id="expression-influence">
-<h4>Influence</h4>
+<h4><span class="secno">3.3.5 </span>Influence</h4>
<table class="grammar">
-<tbody class="grammar-ref" data-ref="prod-influenceExpression"></tbody>
+<tbody class="prod"> <tr style="vertical-align: baseline; "> <td><a id="prod-influenceExpression" data-name="prod-influenceExpression"></a>[<span class="prodNo">22</span>] </td> <td><code class="production prod">influenceExpression</code></td> <td> ::= </td> <td><code class="content">"wasInfluencedBy" "(" <span class="prod"><a class="grammarRef" href="#prod-optionalIdentifier">optionalIdentifier</a></span> <span class="prod"><a class="grammarRef" href="#prod-eIdentifier">eIdentifier</a></span> "," <span class="prod"><a class="grammarRef" href="#prod-eIdentifier">eIdentifier</a></span> <span class="prod"><a class="grammarRef" href="#prod-optionalAttributeValuePairs">optionalAttributeValuePairs</a></span> ")"</code></td> </tr> </tbody>
</table>
<p>The following table summarizes how each constituent of a PROV-DM Influence maps to a PROV-N syntax element.</p>
<div style="text-align: left; ">
<table class="thinborder" style="margin-left: auto; margin-right: auto;">
-<tr><td><b><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#dfn-wasinfluencedby">Influence</a></b></td><td><b>Non-Terminal</b></td></tr>
+<tbody><tr><td><b><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#dfn-wasinfluencedby">Influence</a></b></td><td><b>Non-Terminal</b></td></tr>
<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#influence.id"><span class='attribute' id="influence.id">id</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-optionalIdentifier">optionalIdentifier</a></code></td></tr>
-
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#influence.influencee"><span class='attribute' id="influence.influencee">influencee</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-eIdentifier">eIdentifier</a></code></td></tr>
-
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#influence.influencer"><span class='attribute' id="influence.influencer">influencer</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-eIdentifier">eIdentifier</a></code></td></tr>
-
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#influence.attributes"><span class='attribute' id="influence.attributes">attributes</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-optionalAttributeValuePairs">optionalAttributeValuePairs</a></code></td></tr>
-</table>
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#influence.id"><span class="attribute" id="influence.id">id</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-optionalIdentifier">optionalIdentifier</a></code></td></tr>
+
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#influence.influencee"><span class="attribute" id="influence.influencee">influencee</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-eIdentifier">eIdentifier</a></code></td></tr>
+
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#influence.influencer"><span class="attribute" id="influence.influencer">influencer</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-eIdentifier">eIdentifier</a></code></td></tr>
+
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#influence.attributes"><span class="attribute" id="influence.attributes">attributes</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-optionalAttributeValuePairs">optionalAttributeValuePairs</a></code></td></tr>
+</tbody></table>
</div>
-<div class="anexample">
- <pre class="codeexample">
-wasInfluencedBy(infl1;e2,e1,[ex:param="a"])
+<div class="anexample" id="example_28"><div class="anexampleTitle"><a class="internalDFN" href="#example_28">Example 28</a></div>
+ <pre class="codeexample">wasInfluencedBy(infl1;e2,e1,[ex:param="a"])
</pre>
<p> Here,
<span class="name">infl1</span> is the optional influence identifier,
@@ -2028,8 +2078,7 @@
The remaining examples show cases where some of the optionals are omitted.
- <pre class="codeexample">
-wasInfluencedBy(e2,e1)
+ <pre class="codeexample">wasInfluencedBy(e2,e1)
wasInfluencedBy(e2,e1,[ex:param="a"])
wasInfluencedBy(infl1; e2,e1)
</pre>
@@ -2040,40 +2089,39 @@
</section>
<section id="component4">
-<h3>Component 4: Bundles</h3>
+<h3><span class="secno">3.4 </span>Component 4: Bundles</h3>
<section id="expression-bundle-constructor">
-<h4>Bundle Constructor</h4>
+<h4><span class="secno">3.4.1 </span>Bundle Constructor</h4>
<table class="grammar">
-<tbody class="grammar-ref" data-ref="prod-bundle"></tbody>
+<tbody class="prod"> <tr style="vertical-align: baseline; "> <td><a id="prod-bundle" data-name="prod-bundle"></a>[<span class="prodNo">23</span>] </td> <td><code class="production prod">bundle</code></td> <td> ::= </td> <td><code class="content">"bundle" <span class="prod"><a class="grammarRef" href="#prod-identifier">identifier</a></span> (<span class="prod"><a class="grammarRef" href="#prod-namespaceDeclarations">namespaceDeclarations</a></span>)? (<span class="prod"><a class="grammarRef" href="#prod-expression">expression</a></span>)* "endBundle"</code></td> </tr> </tbody>
</table>
<p>Bundles cannot be nested. It is for this reason that a <code><a class="grammarRef" href="#prod-bundle">bundle</a></code> is not defined as an <code><a class="grammarRef" href="#prod-expression">expression</a></code>, to prevent the occurrence of a <code><a class="grammarRef" href="#prod-bundle">bundle</a></code> inside another <code><a class="grammarRef" href="#prod-bundle">bundle</a></code>.</p>
-<p>Each identifier occurring in a bundle, including the bundle identifier itself, MUST be interpreted with respect to the namespace declarations of that bundle, or if the identifier's prefix is not declared in the bundle, with respect to the namespace declarations in the document. </p>
+<p>Each identifier occurring in a bundle, including the bundle identifier itself, <em class="rfc2119" title="MUST">MUST</em> be interpreted with respect to the namespace declarations of that bundle, or if the identifier's prefix is not declared in the bundle, with respect to the namespace declarations in the document. </p>
<p>The following table summarizes how each constituent of a PROV-DM bundle maps to a PROV-N syntax element.</p>
<div style="text-align: left; ">
<table class="thinborder" style="margin-left: auto; margin-right: auto;">
-<tr><td><b><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#dfn-bundle-constructor">Bundle</a></b></td><td><b>Non-Terminal</b></td></tr>
+<tbody><tr><td><b><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#dfn-bundle-constructor">Bundle</a></b></td><td><b>Non-Terminal</b></td></tr>
<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#bundle.constructor.id"><span class='attribute' id="bundle.id">id</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-optionalIdentifier">optionalIdentifier</a></code></td></tr>
-
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#bundle.constructor.descriptions"><span class='attribute' id="bundle.descriptions">descriptions</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-expression">expression</a></code></td></tr>
-
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#dfn-namespaceDeclaration"><span class='attribute' id="namespaceDeclaration">namespaceDeclaration</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-namespaceDeclarations">namespaceDeclarations</a></code></td></tr>
-
-
-</table>
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#bundle.constructor.id"><span class="attribute" id="bundle.id">id</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-identifier">identifier</a></code></td></tr>
+
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#bundle.constructor.descriptions"><span class="attribute" id="bundle.descriptions">descriptions</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-expression">expression</a></code></td></tr>
+
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#dfn-namespaceDeclaration"><span class="attribute" id="namespaceDeclaration">namespaceDeclaration</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-namespaceDeclarations">namespaceDeclarations</a></code></td></tr>
+
+
+</tbody></table>
</div>
-<div class="anexample" id="anexample-bundle1">
- <pre class="codeexample">
-bundle ex:author-view
+<div class="anexample" id="anexample-bundle1"><div class="anexampleTitle"><a class="internalDFN" href="#anexample-bundle1">Example 29</a></div>
+ <pre class="codeexample">bundle ex:author-view
prefix ex <http://example.org/>
agent(ex:Paolo, [ prov:type='prov:Person' ])
agent(ex:Simon, [ prov:type='prov:Person' ])
@@ -2091,25 +2139,24 @@
</section>
<section id="expression-bundle-type">
-<h4>Bundle Type</h4>
+<h4><span class="secno">3.4.2 </span>Bundle Type</h4>
<p id="provn-type-Bundle">
-When described, a Bundle MUST be expressed as an <code class="content"><a class="grammarRef" href="#prod-entityExpression">entityExpression</a></code> with attribute <code>prov:type='prov:Bundle'</code>.</p>
-
-<div class="anexample">
+When described, a Bundle <em class="rfc2119" title="MUST">MUST</em> be expressed as an <code class="content"><a class="grammarRef" href="#prod-entityExpression">entityExpression</a></code> with attribute <code>prov:type='prov:Bundle'</code>.</p>
+
+<div class="anexample" id="example_30"><div class="anexampleTitle"><a class="internalDFN" href="#example_30">Example 30</a></div>
<p>The bundle of
-<a href="#anexample-bundle1" class="anexample-ref"><span>Example REF</span></a> can be referred to as an an entity, and its provenance described.</p>
-<pre class="codeexample">
- entity(ex:author-view, [ prov:type='prov:Bundle' ])
+<a href="#anexample-bundle1" class="anexample-ref"><span>Example 29</span></a> can be referred to as an entity, and its provenance described.</p>
+<pre class="codeexample"> entity(ex:author-view, [ prov:type='prov:Bundle' ])
</pre>
</div>
</section>
</section>
<section id="component5">
-<h3>Component 5: Alternate Entities</h3>
+<h3><span class="secno">3.5 </span>Component 5: Alternate Entities</h3>
<section id="expression-alternate">
-<h4>Alternate</h4>
+<h4><span class="secno">3.5.1 </span>Alternate</h4>
<!--
<div class='grammar'>
@@ -2125,7 +2172,7 @@
<table class="grammar">
-<tbody class="grammar-ref" data-ref="prod-alternateExpression"></tbody>
+<tbody class="prod"> <tr style="vertical-align: baseline; "> <td><a id="prod-alternateExpression" data-name="prod-alternateExpression"></a>[<span class="prodNo">24</span>] </td> <td><code class="production prod">alternateExpression</code></td> <td> ::= </td> <td><code class="content">"alternateOf" "(" <span class="prod"><a class="grammarRef" href="#prod-eIdentifier">eIdentifier</a></span> "," <span class="prod"><a class="grammarRef" href="#prod-eIdentifier">eIdentifier</a></span> ")"</code></td> </tr> </tbody>
</table>
@@ -2133,21 +2180,20 @@
<p>The following table summarizes how each constituent of a PROV-DM Alternate maps to a PROV-N syntax element.</p>
<div style="text-align: left; ">
<table class="thinborder" style="margin-left: auto; margin-right: auto;">
-<tr><td><b><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#dfn-alternateof">Alternate</a></b></td><td><b>Non-Terminal</b></td></tr>
+<tbody><tr><td><b><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#dfn-alternateof">Alternate</a></b></td><td><b>Non-Terminal</b></td></tr>
<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#alternate.alternate1"><span class='attribute' id="alternate.alternate1">alternate1</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-eIdentifier">eIdentifier</a></code></td></tr>
-
-
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#alternate.alternate2"><span class='attribute' id="alternate.alternate2">alternate2</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-eIdentifier">eIdentifier</a></code></td></tr>
-
-</table>
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#alternate.alternate1"><span class="attribute" id="alternate.alternate1">alternate1</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-eIdentifier">eIdentifier</a></code></td></tr>
+
+
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#alternate.alternate2"><span class="attribute" id="alternate.alternate2">alternate2</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-eIdentifier">eIdentifier</a></code></td></tr>
+
+</tbody></table>
</div>
-<div class="anexample">
-<pre class="codeexample">
-alternateOf(tr:WD-prov-dm-20111215,ex:alternate-20111215)
+<div class="anexample" id="example_31"><div class="anexampleTitle"><a class="internalDFN" href="#example_31">Example 31</a></div>
+<pre class="codeexample">alternateOf(tr:WD-prov-dm-20111215,ex:alternate-20111215)
</pre>
Here <span class="name">tr:WD-prov-dm-20111215</span> is alternate for <span class="name">ex:alternate-20111215</span>.
</div>
@@ -2155,34 +2201,33 @@
</section>
<section id="expression-specialization">
-<h4>Specialization</h4>
+<h4><span class="secno">3.5.2 </span>Specialization</h4>
<table class="grammar">
-<tbody class="grammar-ref" data-ref="prod-specializationExpression"></tbody>
+<tbody class="prod"> <tr style="vertical-align: baseline; "> <td><a id="prod-specializationExpression" data-name="prod-specializationExpression"></a>[<span class="prodNo">25</span>] </td> <td><code class="production prod">specializationExpression</code></td> <td> ::= </td> <td><code class="content">"specializationOf" "(" <span class="prod"><a class="grammarRef" href="#prod-eIdentifier">eIdentifier</a></span> "," <span class="prod"><a class="grammarRef" href="#prod-eIdentifier">eIdentifier</a></span> ")"</code></td> </tr> </tbody>
</table>
<p>The following table summarizes how each constituent of a PROV-DM Specialization maps to a PROV-N syntax element.</p>
<div style="text-align: left; ">
<table class="thinborder" style="margin-left: auto; margin-right: auto;">
-<tr><td><b><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#dfn-specializationof">Specialization</a></b></td><td><b>Non-Terminal</b></td></tr>
+<tbody><tr><td><b><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#dfn-specializationof">Specialization</a></b></td><td><b>Non-Terminal</b></td></tr>
<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#specialization.specificEntity"><span class='attribute' id="specialization.specificEntity">specificEntity</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-eIdentifier">eIdentifier</a></code></td></tr>
-
-
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#specialization.generalEntity"><span class='attribute' id="specialization.generalEntity">generalEntity</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-eIdentifier">eIdentifier</a></code></td></tr>
-
-</table>
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#specialization.specificEntity"><span class="attribute" id="specialization.specificEntity">specificEntity</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-eIdentifier">eIdentifier</a></code></td></tr>
+
+
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#specialization.generalEntity"><span class="attribute" id="specialization.generalEntity">generalEntity</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-eIdentifier">eIdentifier</a></code></td></tr>
+
+</tbody></table>
</div>
-<div class="anexample">
-<pre class="codeexample">
-specializationOf(tr:WD-prov-dm-20111215,tr:prov-dm)
+<div class="anexample" id="example_32"><div class="anexampleTitle"><a class="internalDFN" href="#example_32">Example 32</a></div>
+<pre class="codeexample">specializationOf(tr:WD-prov-dm-20111215,tr:prov-dm)
</pre>
Here <span class="name">tr:WD-prov-dm-20111215</span> is a specialization of <span class="name">tr:prov-dm</span>.
</div>
@@ -2200,25 +2245,24 @@
<section id="component6">
-<h3>Component 6: Collections</h3>
+<h3><span class="secno">3.6 </span>Component 6: Collections</h3>
<section id="expression-collection">
-<h3>Collection</h3>
+<h4><span class="secno">3.6.1 </span>Collection</h4>
<p>
-PROV-N provides no dedicated syntax for Collection and EmptyCollection. Instead, a Collection or an EmptyCollection MUST be expressed as an
+PROV-N provides no dedicated syntax for Collection and EmptyCollection. Instead, a Collection or an EmptyCollection <em class="rfc2119" title="MUST">MUST</em> be expressed as an
<code class="content"><a class="grammarRef" href="#prod-entityExpression">entityExpression</a></code> with attribute
-<span id="provn-type-Collection"><code>prov:type='prov:Collection'</code></span>, or
-<span id="provn-type-EmptyCollection"><code>prov:type='prov:EmptyCollection'</code></span>, respectively.</p>
-
-
-
-<div class="anexample">
+<span id="provn-type-Collection"><code>prov:type='prov:Collection'</code></span>, or
+<span id="provn-type-EmptyCollection"><code>prov:type='prov:EmptyCollection'</code></span>, respectively.</p>
+
+
+
+<div class="anexample" id="example_33"><div class="anexampleTitle"><a class="internalDFN" href="#example_33">Example 33</a></div>
<p>The following two expressions are about a collection and an empty collection, respectively.
-<pre class="codeexample">
- entity(ex:col1, [ prov:type='prov:Collection' ])
+</p><pre class="codeexample"> entity(ex:col1, [ prov:type='prov:Collection' ])
entity(ex:col2, [ prov:type='prov:EmptyCollection' ])
</pre>
</div>
@@ -2226,34 +2270,33 @@
<section id="expression-collection-membership">
-<h3>Membership</h3>
+<h4><span class="secno">3.6.2 </span>Membership</h4>
<table class="grammar">
-<tbody class="grammar-ref" data-ref="prod-membershipExpression"></tbody>
+<tbody class="prod"> <tr style="vertical-align: baseline; "> <td><a id="prod-membershipExpression" data-name="prod-membershipExpression"></a>[<span class="prodNo">26</span>] </td> <td><code class="production prod">membershipExpression</code></td> <td> ::= </td> <td><code class="content">"hadMember" "(" <span class="prod"><a class="grammarRef" href="#prod-cIdentifier">cIdentifier</a></span> "," <span class="prod"><a class="grammarRef" href="#prod-eIdentifier">eIdentifier</a></span> ")"</code></td> </tr> </tbody>
</table>
<p>The following table summarizes how each constituent of a PROV-DM Membership maps to a PROV-N syntax element.</p>
<div style="text-align: left; ">
<table class="thinborder" style="margin-left: auto; margin-right: auto;">
-<tr><td><b><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#dfn-hadmember">Membership</a></b></td><td><b>Non-Terminal</b></td></tr>
+<tbody><tr><td><b><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#dfn-hadmember">Membership</a></b></td><td><b>Non-Terminal</b></td></tr>
<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#membership.collection"><span class='attribute' id="membership.collection">collection</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-cIdentifier">cIdentifier</a></code></td></tr>
-
-<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#membership.entity"><span class='attribute' id="membership.entity">entity</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-eIdentifier">eIdentifier</a></code></td></tr>
-</table>
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#membership.collection"><span class="attribute" id="membership.collection">collection</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-cIdentifier">cIdentifier</a></code></td></tr>
+
+<tr><td><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#membership.entity"><span class="attribute" id="membership.entity">entity</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-eIdentifier">eIdentifier</a></code></td></tr>
+</tbody></table>
</div>
-<div class="anexample">
- <pre class="codeexample">
- hadMember(c, e1) // c contained e1
+<div class="anexample" id="example_34"><div class="anexampleTitle"><a class="internalDFN" href="#example_34">Example 34</a></div>
+ <pre class="codeexample"> hadMember(c, e1) // c contained e1
hadMember(c, e2) // c contained e2
</pre>
<p> Here
@@ -2264,7 +2307,7 @@
and <span class="name">[prov:label="A beautiful collection"]</span> is the optional set of attributes. </p>
-->
-</div>
+</p></div>
</section>
@@ -2274,31 +2317,31 @@
-<section id="subexpressions">
-<h3>Further Expressions</h3>
+<section id="subexpressions">
+<h3><span class="secno">3.7 </span>Further Expressions</h3>
This section defines further expressions of PROV-N.
<section id="expression-identifier">
-<h4>Identifier</h4>
+<h4><span class="secno">3.7.1 </span>Identifier</h4>
<p>Various kinds of identifiers are used in productions.</p>
<table class="grammar">
-<tbody class="grammar-ref" data-ref="prod-eIdentifier"></tbody>
-<tbody class="grammar-ref" data-ref="prod-aIdentifier"></tbody>
-<tbody class="grammar-ref" data-ref="prod-agIdentifier"></tbody>
-<tbody class="grammar-ref" data-ref="prod-gIdentifier"></tbody>
-<tbody class="grammar-ref" data-ref="prod-uIdentifier"></tbody>
-<tbody class="grammar-ref" data-ref="prod-cIdentifier"></tbody>
-
-<tbody class="grammar-ref" data-ref="prod-eIdentifierOrMarker"></tbody>
-<tbody class="grammar-ref" data-ref="prod-aIdentifierOrMarker"></tbody>
-<tbody class="grammar-ref" data-ref="prod-agIdentifierOrMarker"></tbody>
-<tbody class="grammar-ref" data-ref="prod-gIdentifierOrMarker"></tbody>
-<tbody class="grammar-ref" data-ref="prod-uIdentifierOrMarker"></tbody>
-<tbody class="grammar-ref" data-ref="prod-identifier"></tbody>
+<tbody class="prod"> <tr style="vertical-align: baseline; "> <td><a id="prod-eIdentifier" data-name="prod-eIdentifier"></a>[<span class="prodNo">27</span>] </td> <td><code class="production prod">eIdentifier</code></td> <td> ::= </td> <td><code class="content"><span class="prod"><a class="grammarRef" href="#prod-identifier">identifier</a></span></code></td> </tr> </tbody>
+<tbody class="prod"> <tr style="vertical-align: baseline; "> <td><a id="prod-aIdentifier" data-name="prod-aIdentifier"></a>[<span class="prodNo">28</span>] </td> <td><code class="production prod">aIdentifier</code></td> <td> ::= </td> <td><code class="content"><span class="prod"><a class="grammarRef" href="#prod-identifier">identifier</a></span></code></td> </tr> </tbody>
+<tbody class="prod"> <tr style="vertical-align: baseline; "> <td><a id="prod-agIdentifier" data-name="prod-agIdentifier"></a>[<span class="prodNo">29</span>] </td> <td><code class="production prod">agIdentifier</code></td> <td> ::= </td> <td><code class="content"><span class="prod"><a class="grammarRef" href="#prod-identifier">identifier</a></span></code></td> </tr> </tbody>
+<tbody class="prod"> <tr style="vertical-align: baseline; "> <td><a id="prod-gIdentifier" data-name="prod-gIdentifier"></a>[<span class="prodNo">30</span>] </td> <td><code class="production prod">gIdentifier</code></td> <td> ::= </td> <td><code class="content"><span class="prod"><a class="grammarRef" href="#prod-identifier">identifier</a></span></code></td> </tr> </tbody>
+<tbody class="prod"> <tr style="vertical-align: baseline; "> <td><a id="prod-uIdentifier" data-name="prod-uIdentifier"></a>[<span class="prodNo">31</span>] </td> <td><code class="production prod">uIdentifier</code></td> <td> ::= </td> <td><code class="content"><span class="prod"><a class="grammarRef" href="#prod-identifier">identifier</a></span></code></td> </tr> </tbody>
+<tbody class="prod"> <tr style="vertical-align: baseline; "> <td><a id="prod-cIdentifier" data-name="prod-cIdentifier"></a>[<span class="prodNo">32</span>] </td> <td><code class="production prod">cIdentifier</code></td> <td> ::= </td> <td><code class="content"><span class="prod"><a class="grammarRef" href="#prod-identifier">identifier</a></span></code></td> </tr> </tbody>
+
+<tbody class="prod"> <tr style="vertical-align: baseline; "> <td><a id="prod-eIdentifierOrMarker" data-name="prod-eIdentifierOrMarker"></a>[<span class="prodNo">33</span>] </td> <td><code class="production prod">eIdentifierOrMarker</code></td> <td> ::= </td> <td><code class="content">( <span class="prod"><a class="grammarRef" href="#prod-eIdentifier">eIdentifier</a></span> | "-" )</code></td> </tr> </tbody>
+<tbody class="prod"> <tr style="vertical-align: baseline; "> <td><a id="prod-aIdentifierOrMarker" data-name="prod-aIdentifierOrMarker"></a>[<span class="prodNo">34</span>] </td> <td><code class="production prod">aIdentifierOrMarker</code></td> <td> ::= </td> <td><code class="content">( <span class="prod"><a class="grammarRef" href="#prod-aIdentifier">aIdentifier</a></span> | "-" )</code></td> </tr> </tbody>
+<tbody class="prod"> <tr style="vertical-align: baseline; "> <td><a id="prod-agIdentifierOrMarker" data-name="prod-agIdentifierOrMarker"></a>[<span class="prodNo">35</span>] </td> <td><code class="production prod">agIdentifierOrMarker</code></td> <td> ::= </td> <td><code class="content">( <span class="prod"><a class="grammarRef" href="#prod-agIdentifier">agIdentifier</a></span> | "-" )</code></td> </tr> </tbody>
+<tbody class="prod"> <tr style="vertical-align: baseline; "> <td><a id="prod-gIdentifierOrMarker" data-name="prod-gIdentifierOrMarker"></a>[<span class="prodNo">36</span>] </td> <td><code class="production prod">gIdentifierOrMarker</code></td> <td> ::= </td> <td><code class="content">( <span class="prod"><a class="grammarRef" href="#prod-gIdentifier">gIdentifier</a></span> | "-" )</code></td> </tr> </tbody>
+<tbody class="prod"> <tr style="vertical-align: baseline; "> <td><a id="prod-uIdentifierOrMarker" data-name="prod-uIdentifierOrMarker"></a>[<span class="prodNo">37</span>] </td> <td><code class="production prod">uIdentifierOrMarker</code></td> <td> ::= </td> <td><code class="content">( <span class="prod"><a class="grammarRef" href="#prod-uIdentifier">uIdentifier</a></span> | "-" )</code></td> </tr> </tbody>
+<tbody class="prod"> <tr style="vertical-align: baseline; "> <td><a id="prod-identifier" data-name="prod-identifier"></a>[<span class="prodNo">38</span>] </td> <td><code class="production prod">identifier</code></td> <td> ::= </td> <td><code class="content"><span class="prod"><a class="grammarRef" href="#prod-QUALIFIED_NAME">QUALIFIED_NAME</a></span></code></td> </tr> </tbody>
</table>
@@ -2307,8 +2350,8 @@
The PROV data model stipulates that a qualified name can be mapped to an IRI
by concatenating the IRI associated with the prefix and the local part. This section provides the exact details of this procedure for qualified names defined by PROV-N. </p>
-<p>A qualified name's prefix is OPTIONAL. If a prefix occurs in a
- qualified name, the prefix MUST refer to a namespace declared in a namespace declaration. In the absence of prefix, the qualified name
+<p>A qualified name's prefix is <em class="rfc2119" title="OPTIONAL">OPTIONAL</em>. If a prefix occurs in a
+ qualified name, the prefix <em class="rfc2119" title="MUST">MUST</em> refer to a namespace declared in a namespace declaration. In the absence of prefix, the qualified name
belongs to the default namespace.</p>
<!--
@@ -2330,14 +2373,14 @@
-->
-<p>A PROV-N qualified name (production <code class="content"><a class="grammarRef" href="#prod-QUALIFIED_NAME">QUALIFIED_NAME</a></code>) has a more permissive syntax then XML's <code class="content"><a href="http://www.w3.org/TR/2009/REC-xml-names-20091208/#NT-QName">QName</a></code> [[!XML-NAMES]]
-and SPARQL <code class="content"><a href="http://www.w3.org/TR/2008/REC-rdf-sparql-query-20080115/#rPrefixedName">PrefixedName</a></code> [[!RDF-SPARQL-QUERY]].
-A <code class="content"><a class="grammarRef" href="#prod-QUALIFIED_NAME">QUALIFIED_NAME</a></code> consists of a prefix and a local part. Prefixes follow the production <code class="content"><a class="grammarRef" href="http://www.w3.org/TR/rdf-sparql-query/#rPN_PREFIX">PN_PREFIX</a></code> defined by SPARQL [[!RDF-SPARQL-QUERY]]. Local parts have to be conformant with <code class="content"><a class="grammarRef" href="#prod-PN_LOCAL">PN_LOCAL</a></code>, which extends the original SPARQL <code class="content"><a class="grammarRef" href="http://www.w3.org/TR/rdf-sparql-query/#rPN_LOCAL">PN_LOCAL</a></code> definition
+<p>A PROV-N qualified name (production <code class="content"><a class="grammarRef" href="#prod-QUALIFIED_NAME">QUALIFIED_NAME</a></code>) has a more permissive syntax than XML's <code class="content"><a href="http://www.w3.org/TR/2009/REC-xml-names-20091208/#NT-QName">QName</a></code> [<cite><a class="bibref" href="#bib-XML-NAMES">XML-NAMES</a></cite>]
+and SPARQL <code class="content"><a href="http://www.w3.org/TR/2008/REC-rdf-sparql-query-20080115/#rPrefixedName">PrefixedName</a></code> [<cite><a class="bibref" href="#bib-RDF-SPARQL-QUERY">RDF-SPARQL-QUERY</a></cite>].
+A <code class="content"><a class="grammarRef" href="#prod-QUALIFIED_NAME">QUALIFIED_NAME</a></code> consists of a prefix and a local part. Prefixes follow the production <code class="content"><a class="grammarRef" href="http://www.w3.org/TR/rdf-sparql-query/#rPN_PREFIX">PN_PREFIX</a></code> defined by SPARQL [<cite><a class="bibref" href="#bib-RDF-SPARQL-QUERY">RDF-SPARQL-QUERY</a></cite>]. Local parts have to be conformant with <code class="content"><a class="grammarRef" href="#prod-PN_LOCAL">PN_LOCAL</a></code>, which extends the original SPARQL <code class="content"><a class="grammarRef" href="http://www.w3.org/TR/rdf-sparql-query/#rPN_LOCAL">PN_LOCAL</a></code> definition
by allowing further characters (see <code class="content"><a class="grammarRef" href="#prod-PN_CHARS_OTHERS">PN_CHARS_OTHERS</a></code>):</p>
<ul>
<li> an extra set of characters commonly encountered in IRIs;
-<li> %-escaped characters (see <code class="content"><a class="grammarRef" href="#prod-PERCENT">PERCENT</a></code>) to be interpreted as per
- Section 3.1. Mapping of IRIs to URIs in [[!RFC3987]];</li>
+</li><li> %-escaped characters (see <code class="content"><a class="grammarRef" href="#prod-PERCENT">PERCENT</a></code>) to be interpreted as per
+ Section 3.1. Mapping of IRIs to URIs in [<cite><a class="bibref" href="#bib-RFC3987">RFC3987</a></cite>];</li>
<li> and \-escaped characters (see <code class="content"><a class="grammarRef" href="#prod-PN_CHARS_ESC">PN_CHARS_ESC</a></code>).</li>
</ul>
@@ -2359,25 +2402,24 @@
-<p>A PROV-N qualified name <code class="content"><a class="grammarRef" href="#prod-QUALIFIED_NAME">QUALIFIED_NAME</a></code> can be mapped to a valid IRI [[!RFC3987]] by concatenating the namespace denoted its local name <code class="content"><a class="grammarRef" href="http://www.w3.org/TR/rdf-sparql-query/#rPN_PREFIX">PN_PREFIX</a></code> to the local name <code class="content"><a class="grammarRef" href="#prod-PN_LOCAL">PN_LOCAL</a></code>, whose \-escaped characters have been unescaped by dropping the character '\' (backslash).</p>
+<p>A PROV-N qualified name <code class="content"><a class="grammarRef" href="#prod-QUALIFIED_NAME">QUALIFIED_NAME</a></code> can be mapped to a valid IRI [<cite><a class="bibref" href="#bib-RFC3987">RFC3987</a></cite>] by concatenating the namespace denoted its local name <code class="content"><a class="grammarRef" href="http://www.w3.org/TR/rdf-sparql-query/#rPN_PREFIX">PN_PREFIX</a></code> to the local name <code class="content"><a class="grammarRef" href="#prod-PN_LOCAL">PN_LOCAL</a></code>, whose \-escaped characters have been unescaped by dropping the character '\' (backslash).</p>
<table class="grammar">
-<tbody class="grammar-ref" data-ref="prod-QUALIFIED_NAME"></tbody>
-<tbody class="grammar-ref" data-ref="prod-PN_LOCAL"></tbody>
-<tbody class="grammar-ref" data-ref="prod-PN_CHARS_OTHERS"></tbody>
-<tbody class="grammar-ref" data-ref="prod-PN_CHARS_ESC"></tbody>
-<tbody class="grammar-ref" data-ref="prod-PERCENT"></tbody>
-<tbody class="grammar-ref" data-ref="prod-HEX"></tbody>
+<tbody class="term"> <tr style="vertical-align: baseline; "> <td><a id="prod-QUALIFIED_NAME" data-name="prod-QUALIFIED_NAME"></a>[<span class="prodNo">52</span>] </td> <td><<code class="production term">QUALIFIED_NAME</code>></td> <td> ::= </td> <td><code class="content">( <span class="prod"><a class="grammarRef" href="http://www.w3.org/TR/rdf-sparql-query/#rPN_PREFIX">PN_PREFIX</a></span> ":" )? <span class="prod"><a class="grammarRef" href="#prod-PN_LOCAL">PN_LOCAL</a></span><br> | <span class="prod"><a class="grammarRef" href="http://www.w3.org/TR/rdf-sparql-query/#rPN_PREFIX">PN_PREFIX</a></span> ":"</code></td> </tr> </tbody>
+<tbody class="term"> <tr style="vertical-align: baseline; "> <td><a id="prod-PN_LOCAL" data-name="prod-PN_LOCAL"></a>[<span class="prodNo">53</span>] </td> <td><<code class="production term">PN_LOCAL</code>></td> <td> ::= </td> <td><code class="content">( <span class="prod"><a class="grammarRef" href="http://www.w3.org/TR/rdf-sparql-query/#rPN_CHARS_U">PN_CHARS_U</a></span> | [0-9] | <span class="prod"><a class="grammarRef" href="#prod-PN_CHARS_OTHERS">PN_CHARS_OTHERS</a></span> ) ( ( <span class="prod"><a class="grammarRef" href="http://www.w3.org/TR/rdf-sparql-query/#rPN_CHARS">PN_CHARS</a></span> | "." | <span class="prod"><a class="grammarRef" href="#prod-PN_CHARS_OTHERS">PN_CHARS_OTHERS</a></span> )* ( <span class="prod"><a class="grammarRef" href="http://www.w3.org/TR/rdf-sparql-query/#rPN_CHARS">PN_CHARS</a></span> | <span class="prod"><a class="grammarRef" href="#prod-PN_CHARS_OTHERS">PN_CHARS_OTHERS</a></span> ) )?</code></td> </tr> </tbody>
+<tbody class="term"> <tr style="vertical-align: baseline; "> <td><a id="prod-PN_CHARS_OTHERS" data-name="prod-PN_CHARS_OTHERS"></a>[<span class="prodNo">54</span>] </td> <td><<code class="production term">PN_CHARS_OTHERS</code>></td> <td> ::= </td> <td><code class="content">"/"<br> | "@"<br> | "~"<br> | "&"<br> | "+"<br> | "*"<br> | "?"<br> | "#"<br> | "$"<br> | "!"<br> | <span class="prod"><a class="grammarRef" href="#prod-PERCENT">PERCENT</a></span><br> | <span class="prod"><a class="grammarRef" href="#prod-PN_CHARS_ESC">PN_CHARS_ESC</a></span></code></td> </tr> </tbody>
+<tbody class="term"> <tr style="vertical-align: baseline; "> <td><a id="prod-PN_CHARS_ESC" data-name="prod-PN_CHARS_ESC"></a>[<span class="prodNo">55</span>] </td> <td><<code class="production term">PN_CHARS_ESC</code>></td> <td> ::= </td> <td><code class="content">"\" ( "=" | "'" | "(" | ")" | "," | "-" | ":" | ";" | "[" | "]" | "." )</code></td> </tr> </tbody>
+<tbody class="term"> <tr style="vertical-align: baseline; "> <td><a id="prod-PERCENT" data-name="prod-PERCENT"></a>[<span class="prodNo">56</span>] </td> <td><<code class="production term">PERCENT</code>></td> <td> ::= </td> <td><code class="content">"%" <span class="prod"><a class="grammarRef" href="#prod-HEX">HEX</a></span> <span class="prod"><a class="grammarRef" href="#prod-HEX">HEX</a></span></code></td> </tr> </tbody>
+<tbody class="term"> <tr style="vertical-align: baseline; "> <td><a id="prod-HEX" data-name="prod-HEX"></a>[<span class="prodNo">57</span>] </td> <td><<code class="production term">HEX</code>></td> <td> ::= </td> <td><code class="content">[0-9]<br> | [A-F]<br> | [a-f]</code></td> </tr> </tbody>
</table>
-<div class="anexample" id="anexample-qualified-name">
+<div class="anexample" id="anexample-qualified-name"><div class="anexampleTitle"><a class="internalDFN" href="#anexample-qualified-name">Example 35</a></div>
<p>Examples of articles on the BBC Web site seen as entities.</p>
-<pre class="codeexample">
-document
+<pre class="codeexample">document
prefix bbc <http://www.bbc.co.uk/>
prefix bbcNews <http://www.bbc.co.uk/news/>
@@ -2392,10 +2434,9 @@
</div>
-<div class="anexample" id="anexample-qualified-name2">
+<div class="anexample" id="anexample-qualified-name2"><div class="anexampleTitle"><a class="internalDFN" href="#anexample-qualified-name2">Example 36</a></div>
<p>Examples of entities with declared and default namespace.</p>
-<pre class="codeexample">
-document
+<pre class="codeexample">document
default <http://example.org/2/>
prefix ex <http://example.org/1/>
@@ -2412,10 +2453,9 @@
</div>
-<div class="anexample" id="anexample-qualified-name3">
+<div class="anexample" id="anexample-qualified-name3"><div class="anexampleTitle"><a class="internalDFN" href="#anexample-qualified-name3">Example 37</a></div>
<p>Examples of \-escaped characters.</p>
-<pre class="codeexample">
-document
+<pre class="codeexample">document
prefix ex <http://example.org/>
default <http://example.org/default>
@@ -2441,7 +2481,7 @@
</section>
<section id="expression-attribute">
-<h4>Attribute</h4>
+<h4><span class="secno">3.7.2 </span>Attribute</h4>
<!--
<div class='grammar'>
@@ -2450,21 +2490,21 @@
-->
<table class="grammar">
-<tbody class="grammar-ref" data-ref="prod-attribute"></tbody>
+<tbody class="prod"> <tr style="vertical-align: baseline; "> <td><a id="prod-attribute" data-name="prod-attribute"></a>[<span class="prodNo">39</span>] </td> <td><code class="production prod">attribute</code></td> <td> ::= </td> <td><code class="content"><span class="prod"><a class="grammarRef" href="#prod-QUALIFIED_NAME">QUALIFIED_NAME</a></span></code></td> </tr> </tbody>
</table>
<p>The reserved attributes in the PROV namespace are the following.
-Their meaning is explained by [[PROV-DM]] (see <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-attribute">Section 5.7.2: Attribute</a>).
+Their meaning is explained by [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>] (see <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-attribute">Section 5.7.2: Attribute</a>).
</p>
<ol>
<li> <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-attribute-label"><span class="name">prov:label</span></a>
-<li> <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-attribute-location"><span class="name">prov:location</span></a>
-<li> <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-attribute-role"><span class="name">prov:role</span></a>
-<li> <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-attribute-type"><span class="name">prov:type</span></a>
-<li> <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-attribute-value"><span class="name">prov:value</span></a>
-</ol>
+</li><li> <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-attribute-location"><span class="name">prov:location</span></a>
+</li><li> <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-attribute-role"><span class="name">prov:role</span></a>
+</li><li> <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-attribute-type"><span class="name">prov:type</span></a>
+</li><li> <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-attribute-value"><span class="name">prov:value</span></a>
+</li></ol>
</section>
@@ -2474,7 +2514,7 @@
<section id="expression-literal">
-<h4>Literal</h4>
+<h4><span class="secno">3.7.3 </span>Literal</h4>
<!--
<div class='grammar'>
@@ -2490,20 +2530,20 @@
-->
<table class="grammar">
-<tbody class="grammar-ref" data-ref="prod-literal"></tbody>
-<tbody class="grammar-ref" data-ref="prod-typedLiteral"></tbody>
-<tbody class="grammar-ref" data-ref="prod-datatype"></tbody>
-<tbody class="grammar-ref" data-ref="prod-convenienceNotation"></tbody>
-<tbody class="grammar-ref" data-ref="prod-STRING_LITERAL"></tbody>
-<tbody class="grammar-ref" data-ref="prod-INT_LITERAL"></tbody>
-<tbody class="grammar-ref" data-ref="prod-DIGIT"></tbody>
-<tbody class="grammar-ref" data-ref="prod-QUALIFIED_NAME_LITERAL"></tbody>
+<tbody class="prod"> <tr style="vertical-align: baseline; "> <td><a id="prod-literal" data-name="prod-literal"></a>[<span class="prodNo">40</span>] </td> <td><code class="production prod">literal</code></td> <td> ::= </td> <td><code class="content"><span class="prod"><a class="grammarRef" href="#prod-typedLiteral">typedLiteral</a></span><br> | <span class="prod"><a class="grammarRef" href="#prod-convenienceNotation">convenienceNotation</a></span></code></td> </tr> </tbody>
+<tbody class="prod"> <tr style="vertical-align: baseline; "> <td><a id="prod-typedLiteral" data-name="prod-typedLiteral"></a>[<span class="prodNo">41</span>] </td> <td><code class="production prod">typedLiteral</code></td> <td> ::= </td> <td><code class="content"><span class="prod"><a class="grammarRef" href="#prod-STRING_LITERAL">STRING_LITERAL</a></span> "%%" <span class="prod"><a class="grammarRef" href="#prod-datatype">datatype</a></span></code></td> </tr> </tbody>
+<tbody class="prod"> <tr style="vertical-align: baseline; "> <td><a id="prod-datatype" data-name="prod-datatype"></a>[<span class="prodNo">42</span>] </td> <td><code class="production prod">datatype</code></td> <td> ::= </td> <td><code class="content"><span class="prod"><a class="grammarRef" href="#prod-QUALIFIED_NAME">QUALIFIED_NAME</a></span></code></td> </tr> </tbody>
+<tbody class="prod"> <tr style="vertical-align: baseline; "> <td><a id="prod-convenienceNotation" data-name="prod-convenienceNotation"></a>[<span class="prodNo">43</span>] </td> <td><code class="production prod">convenienceNotation</code></td> <td> ::= </td> <td><code class="content"><span class="prod"><a class="grammarRef" href="#prod-STRING_LITERAL">STRING_LITERAL</a></span> (<span class="prod"><a class="grammarRef" href="http://www.w3.org/TR/rdf-sparql-query/#rLANGTAG">LANGTAG</a></span>)?<br> | <span class="prod"><a class="grammarRef" href="#prod-INT_LITERAL">INT_LITERAL</a></span><br> | <span class="prod"><a class="grammarRef" href="#prod-QUALIFIED_NAME_LITERAL">QUALIFIED_NAME_LITERAL</a></span></code></td> </tr> </tbody>
+<tbody class="term"> <tr style="vertical-align: baseline; "> <td><a id="prod-STRING_LITERAL" data-name="prod-STRING_LITERAL"></a>[<span class="prodNo">58</span>] </td> <td><<code class="production term">STRING_LITERAL</code>></td> <td> ::= </td> <td><code class="content"><span class="prod"><a class="grammarRef" href="http://www.w3.org/TR/rdf-sparql-query/#rSTRING_LITERAL2">STRING_LITERAL2</a></span><br> | <span class="prod"><a class="grammarRef" href="http://www.w3.org/TR/rdf-sparql-query/#rSTRING_LITERAL_LONG2">STRING_LITERAL_LONG2</a></span></code></td> </tr> </tbody>
+<tbody class="term"> <tr style="vertical-align: baseline; "> <td><a id="prod-INT_LITERAL" data-name="prod-INT_LITERAL"></a>[<span class="prodNo">60</span>] </td> <td><<code class="production term">INT_LITERAL</code>></td> <td> ::= </td> <td><code class="content">("-")? (<span class="prod"><a class="grammarRef" href="#prod-DIGIT">DIGIT</a></span>)+</code></td> </tr> </tbody>
+<tbody class="term"> <tr style="vertical-align: baseline; "> <td><a id="prod-DIGIT" data-name="prod-DIGIT"></a>[<span class="prodNo">62</span>] </td> <td><<code class="production term">DIGIT</code>></td> <td> ::= </td> <td><code class="content">[0-9]</code></td> </tr> </tbody>
+<tbody class="term"> <tr style="vertical-align: baseline; "> <td><a id="prod-QUALIFIED_NAME_LITERAL" data-name="prod-QUALIFIED_NAME_LITERAL"></a>[<span class="prodNo">61</span>] </td> <td><<code class="production term">QUALIFIED_NAME_LITERAL</code>></td> <td> ::= </td> <td><code class="content">"'" <span class="prod"><a class="grammarRef" href="#prod-QUALIFIED_NAME">QUALIFIED_NAME</a></span> "'"</code></td> </tr> </tbody>
</table>
-<p>In production <code class="content"><a class="grammarRef" href="#prod-datatype">datatype</a></code>, the <code class="content"><a class="grammarRef" href="#prod-QUALIFIED_NAME">QUALIFIED_NAME</a></code> is used to denote a <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-value">PROV data type</a> [[PROV-DM]].
-
-
-<p>The non terminals
+<p>In production <code class="content"><a class="grammarRef" href="#prod-datatype">datatype</a></code>, the <code class="content"><a class="grammarRef" href="#prod-QUALIFIED_NAME">QUALIFIED_NAME</a></code> is used to denote a <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-value">PROV data type</a> [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>].
+
+
+</p><p>The non terminals
<code class="content"><a class="grammarRef" href="#prod-STRING_LITERAL">STRING_LITERAL</a></code>,
<code class="content"><a class="grammarRef" href="#prod-INT_LITERAL">INT_LITERAL</a></code>, and
<code class="content"><a class="grammarRef" href="#prod-QUALIFIED_NAME_LITERAL">QUALIFIED_NAME_LITERAL</a></code>
@@ -2524,44 +2564,39 @@
<code class="content"><a class="grammarRef" href="#prod-INT_LITERAL">INT_LITERAL</a></code>.
</p>
-<div class="anexample" id="anexample-convenience">
+<div class="anexample" id="anexample-convenience"><div class="anexampleTitle"><a class="internalDFN" href="#anexample-convenience">Example 38</a></div>
<p>
The following examples illustrate convenience notations.</p>
<p>The two following expressions are strings; if <code class="content"><a class="grammarRef" href="#prod-datatype">datatype</a></code> is not specified, it is <code>xsd:string</code>.</p>
-<pre class="codeexample">
- "abc" %% xsd:string
+<pre class="codeexample"> "abc" %% xsd:string
"abc"
</pre>
<p>The two following expressions are integers. For convenience, numbers, expressed as digits optionally preceded by a minus sign, can occur without quotes.</p>
-<pre class="codeexample">
- "1234" %% xsd:integer
+<pre class="codeexample"> "1234" %% xsd:integer
1234
"-1234" %% xsd:integer
-1234
</pre>
<p>The two following expressions are qualified names. Values of type qualified name can be conveniently expressed within single quotes.</p>
-<pre class="codeexample">
- "ex:value" %% prov:QUALIFIED_NAME
+<pre class="codeexample"> "ex:value" %% prov:QUALIFIED_NAME
'ex:value'
</pre>
</div>
-<div class="anexample" id="anexample-value">
+<div class="anexample" id="anexample-value"><div class="anexampleTitle"><a class="internalDFN" href="#anexample-value">Example 39</a></div>
<p>
The following examples respectively are the string "abc", the string (in French) "bonjour", the integer number 1, and the IRI "http://example.org/foo".</p>
-<pre class="codeexample">
- "abc"
+<pre class="codeexample"> "abc"
"bonjour"@fr
"1" %% xsd:integer
"http://example.org/foo" %% xsd:anyURI
</pre>
<p>The following examples respectively are the floating point number 1.01 and the boolean true.</p>
-<pre class="codeexample">
- "1.01" %% xsd:float
+<pre class="codeexample"> "1.01" %% xsd:float
"true" %% xsd:boolean
</pre>
</div>
@@ -2569,30 +2604,29 @@
<section id="expression-types">
-<h4>Reserved Type Values</h4>
+<h5><span class="secno">3.7.3.1 </span>Reserved Type Values</h5>
<p>The reserved type values in the PROV namespace are the following.
-Their meaning is defined [[PROV-DM]] (see <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-attribute-type">Section 5.7.2.4: prov:type</a>).
+Their meaning is defined [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>] (see <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-attribute-type">Section 5.7.2.4: prov:type</a>).
</p>
<ol>
<li> <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-bundle-entity"><span class="name">prov:Bundle</span></a>
-<li> <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#concept-collection"><span class="name">prov:Collection</span></a>
-<li> <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#concept-empty-collection"><span class="name">prov:EmptyCollection</span></a>
-<li> <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#concept-organization"><span class="name">prov:Organization</span></a>
-<li> <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#concept-person"><span class="name">prov:Person</span></a>
-<li> <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#concept-plan"><span class="name">prov:Plan</span></a>
-<li> <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#dfn-primary-source"><span class="name">prov:PrimarySource</span></a>
-<li> <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#dfn-quotation"><span class="name">prov:Quotation</span></a>
-<li> <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#dfn-revision"><span class="name">prov:Revision</span></a>
-<li> <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#concept-software-agent"><span class="name">prov:SoftwareAgent</span></a>
-</ol>
-
-<div class="anexample" id="anexample-types">
+</li><li> <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#concept-collection"><span class="name">prov:Collection</span></a>
+</li><li> <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#concept-empty-collection"><span class="name">prov:EmptyCollection</span></a>
+</li><li> <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#concept-organization"><span class="name">prov:Organization</span></a>
+</li><li> <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#concept-person"><span class="name">prov:Person</span></a>
+</li><li> <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#concept-plan"><span class="name">prov:Plan</span></a>
+</li><li> <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#dfn-primary-source"><span class="name">prov:PrimarySource</span></a>
+</li><li> <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#dfn-quotation"><span class="name">prov:Quotation</span></a>
+</li><li> <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#dfn-revision"><span class="name">prov:Revision</span></a>
+</li><li> <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#concept-software-agent"><span class="name">prov:SoftwareAgent</span></a>
+</li></ol>
+
+<div class="anexample" id="anexample-types"><div class="anexampleTitle"><a class="internalDFN" href="#anexample-types">Example 40</a></div>
<p>The agent <span class="name">ag</span> is a person (type: <span class="name">prov:Person</span>), whereas the entity
<span class="name">pl</span> is a plan (type: <span class="name">prov:Plan</span>).</p>
-<pre class="codeexample">
-agent(ag, [ prov:type='prov:Person' ])
+<pre class="codeexample">agent(ag, [ prov:type='prov:Person' ])
entity(pl, [ prov:type='prov:Plan' ])
</pre>
</div>
@@ -2601,20 +2635,19 @@
</section>
<section id="expression-Time">
-<h4>Time Values</h4>
-
-<p><dfn id="dfn-time">Time instants</dfn> are defined according to xsd:dateTime [[!XMLSCHEMA11-2]].</p>
+<h5><span class="secno">3.7.3.2 </span>Time Values</h5>
+
+<p><dfn id="dfn-time">Time instants</dfn> are defined according to xsd:dateTime [<cite><a class="bibref" href="#bib-XMLSCHEMA11-2">XMLSCHEMA11-2</a></cite>].</p>
<table class="grammar">
-<tbody class="grammar-ref" data-ref="prod-time"></tbody>
+<tbody class="prod"> <tr style="vertical-align: baseline; "> <td><a id="prod-time" data-name="prod-time"></a>[<span class="prodNo">44</span>] </td> <td><code class="production prod">time</code></td> <td> ::= </td> <td><code class="content"><span class="prod"><a class="grammarRef" href="http://www.w3.org/TR/xmlschema11-2/#nt-dateTimeRep">DATETIME</a></span></code></td> </tr> </tbody>
</table>
-<div class="anexample" id="anexample-time">
+<div class="anexample" id="anexample-time"><div class="anexampleTitle"><a class="internalDFN" href="#anexample-time">Example 41</a></div>
<p>The third argument in the following usage expression is a time instance, namely 4pm on 2011-11-16.</p>
-<pre class="codeexample">
-used(ex:act2, ar3:0111, 2011-11-16T16:00:00)
+<pre class="codeexample">used(ex:act2, ar3:0111, 2011-11-16T16:00:00)
</pre>
</div>
@@ -2631,15 +2664,15 @@
<section id="expression-NamespaceDeclaration">
-<h3>Namespace Declaration</h3>
+<h4><span class="secno">3.7.4 </span>Namespace Declaration</h4>
<table class="grammar">
-<tbody class="grammar-ref" data-ref="prod-namespaceDeclarations"></tbody>
-<tbody class="grammar-ref" data-ref="prod-namespaceDeclaration"></tbody>
-<tbody class="grammar-ref" data-ref="prod-defaultNamespaceDeclaration"></tbody>
-<tbody class="grammar-ref" data-ref="prod-namespace"></tbody>
+<tbody class="prod"> <tr style="vertical-align: baseline; "> <td><a id="prod-namespaceDeclarations" data-name="prod-namespaceDeclarations"></a>[<span class="prodNo">45</span>] </td> <td><code class="production prod">namespaceDeclarations</code></td> <td> ::= </td> <td><code class="content">( <span class="prod"><a class="grammarRef" href="#prod-defaultNamespaceDeclaration">defaultNamespaceDeclaration</a></span> | <span class="prod"><a class="grammarRef" href="#prod-namespaceDeclaration">namespaceDeclaration</a></span> ) (<span class="prod"><a class="grammarRef" href="#prod-namespaceDeclaration">namespaceDeclaration</a></span>)*</code></td> </tr> </tbody>
+<tbody class="prod"> <tr style="vertical-align: baseline; "> <td><a id="prod-namespaceDeclaration" data-name="prod-namespaceDeclaration"></a>[<span class="prodNo">46</span>] </td> <td><code class="production prod">namespaceDeclaration</code></td> <td> ::= </td> <td><code class="content">"prefix" <span class="prod"><a class="grammarRef" href="http://www.w3.org/TR/rdf-sparql-query/#rPN_PREFIX">PN_PREFIX</a></span> <span class="prod"><a class="grammarRef" href="#prod-namespace">namespace</a></span></code></td> </tr> </tbody>
+<tbody class="prod"> <tr style="vertical-align: baseline; "> <td><a id="prod-defaultNamespaceDeclaration" data-name="prod-defaultNamespaceDeclaration"></a>[<span class="prodNo">47</span>] </td> <td><code class="production prod">defaultNamespaceDeclaration</code></td> <td> ::= </td> <td><code class="content">"default" <span class="prod"><a class="grammarRef" href="http://www.w3.org/TR/rdf-sparql-query/#rIRI_REF">IRI_REF</a></span></code></td> </tr> </tbody>
+<tbody class="prod"> <tr style="vertical-align: baseline; "> <td><a id="prod-namespace" data-name="prod-namespace"></a>[<span class="prodNo">48</span>] </td> <td><code class="production prod">namespace</code></td> <td> ::= </td> <td><code class="content"><span class="prod"><a class="grammarRef" href="http://www.w3.org/TR/rdf-sparql-query/#rIRI_REF">IRI_REF</a></span></code></td> </tr> </tbody>
</table>
@@ -2652,18 +2685,17 @@
The scope of a prefix-namespace declaration directly occurring in a <code><a class="grammarRef" href="#prod-document">document</a></code> is the <code><a class="grammarRef" href="#prod-document">document</a></code> including the <code><a class="grammarRef" href="#prod-bundle">bundles</a></code> it contains but excluding those <code><a class="grammarRef" href="#prod-bundle">bundles</a></code> that re-declare this prefix.</li>
</ul>
-<p>A set of namespace declarations <code><a class="grammarRef" href="#prod-namespaceDeclarations">namespaceDeclarations</a></code> MUST NOT re-declare the same prefix.</p>
-
-<p>A set of namespace declarations <code><a class="grammarRef" href="#prod-namespaceDeclarations">namespaceDeclarations</a></code> occurring in a bundle MAY re-declare a prefix declared in a surrounding document.</p>
-
-<p>A namespace declaration <code><a class="grammarRef" href="#prod-namespaceDeclaration">namespaceDeclaration</a></code> MUST NOT declare prefixes <span class="name">prov</span> and <span class="name">xsd</span> (see <a href="#namespace-table">Table 1</a> for their IRI).</p>
-
-
-
-<div class="anexample" id="anexample-namespace">
+<p>A set of namespace declarations <code><a class="grammarRef" href="#prod-namespaceDeclarations">namespaceDeclarations</a></code> <em class="rfc2119" title="MUST NOT">MUST NOT</em> re-declare the same prefix.</p>
+
+<p>A set of namespace declarations <code><a class="grammarRef" href="#prod-namespaceDeclarations">namespaceDeclarations</a></code> occurring in a bundle <em class="rfc2119" title="MAY">MAY</em> re-declare a prefix declared in a surrounding document.</p>
+
+<p>A namespace declaration <code><a class="grammarRef" href="#prod-namespaceDeclaration">namespaceDeclaration</a></code> <em class="rfc2119" title="MUST NOT">MUST NOT</em> declare prefixes <span class="name">prov</span> and <span class="name">xsd</span> (see <a href="#namespace-table">Table 1</a> for their IRI).</p>
+
+
+
+<div class="anexample" id="anexample-namespace"><div class="anexampleTitle"><a class="internalDFN" href="#anexample-namespace">Example 42</a></div>
<p>The following example declares three namespaces, one default, and two with explicit prefixes <span class="name">ex1</span> and <span class="name">ex2</span>.</p>
-<pre class="codeexample">
-document
+<pre class="codeexample">document
default <http://example.org/0/>
prefix ex1 <http://example.org/1/>
prefix ex2 <http://example.org/2/>
@@ -2673,14 +2705,13 @@
</div>
-<div class="anexample" id="anexample-namespace-scope">
+<div class="anexample" id="anexample-namespace-scope"><div class="anexampleTitle"><a class="internalDFN" href="#anexample-namespace-scope">Example 43</a></div>
<p>In the following example, a document declares a default namespace and the occurrence of
<code>e001</code> directly occurring in the document refers to that namespace.
A nested bundle also declares a default namespace, but with a different IRI.
In that bundle, the occurrences of
<code>e001</code>, including the bundle name, refer to the latest default namespace.</p>
-<pre class="codeexample">
-document
+<pre class="codeexample">document
default <http://example.org/1/>
entity(e001) // IRI: http://example.org/1/e001
@@ -2693,13 +2724,12 @@
</div>
-<div class="anexample" id="anexample-namespace-scope2">
+<div class="anexample" id="anexample-namespace-scope2"><div class="anexampleTitle"><a class="internalDFN" href="#anexample-namespace-scope2">Example 44</a></div>
<p>In the following example, a document declares a namespace with prefix <code>ex</code> and the occurrence of
<code>ex:e001</code> directly occurring in the document refers to that namespace.
In a nested bundle, the occurrence of
<code>ex:e001</code> also refers to the same namespace.</p>
-<pre class="codeexample">
-document
+<pre class="codeexample">document
prefix ex <http://example.org/1/>
entity(ex:e001) // IRI: http://example.org/1/e001
@@ -2720,52 +2750,52 @@
<section id="semantic-rules-summary">
-<h3>Summary of additional semantic rules</h3>
-
-<p>Some of the grammar productions allow for expressions that are syntactically correct, and yet according to [[PROV-DM]] they are not acceptable, because additional semantic rules are defined for those expressions.
+<h4><span class="secno">3.7.5 </span>Summary of additional semantic rules</h4>
+
+<p>Some of the grammar productions allow for expressions that are syntactically correct, and yet according to [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>] they are not acceptable, because additional semantic rules are defined for those expressions.
The following table provides a summary of such expressions along with examples of syntactically correct but unacceptable forms, and the additional semantic rules.</p>
<div style="text-align: left;">
<table class="thinborder" style="margin-left: auto; margin-right: auto;">
<caption id="validity-rules-table">Table 2: Summary of additional semantic rules for grammar productions</caption>
-<tr><td><b>Production</b></td>
+<tbody><tr><td><b>Production</b></td>
<td><b>Examples of syntactically correct expressions</b></td>
<td><b>Additional semantic rule</b></td>
</tr>
<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
<tr><td><a class="grammarRef" href="#prod-generationExpression">Generation expression</a></td>
- <td><span class="name">wasGeneratedBy(e2, -, -)</span><br/><span class="name">wasGeneratedBy(-; e2, -, -)</span></td>
- <td>At least one of <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#generation.id"><span class='attribute'>id</span></a>, <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#generation.activity"><span class='attribute'>activity</span></a>, <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#generation.time"><span class='attribute'>time</span></a>, and <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#generation.attributes"><span class='attribute'>attributes</span></a> MUST be present.</td>
+ <td><span class="name">wasGeneratedBy(e2, -, -)</span><br><span class="name">wasGeneratedBy(-; e2, -, -)</span></td>
+ <td>At least one of <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#generation.id"><span class="attribute">id</span></a>, <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#generation.activity"><span class="attribute">activity</span></a>, <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#generation.time"><span class="attribute">time</span></a>, and <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#generation.attributes"><span class="attribute">attributes</span></a> <em class="rfc2119" title="MUST">MUST</em> be present.</td>
</tr>
<tr><td><a class="grammarRef" href="#prod-usageExpression">Usage expression</a></td>
-<td><span class="name">used(a2, -, -)</span><br/><span class="name">used(-; a2, -, -)</span></td>
-<td>At least one of <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#usage.id"><span class='attribute'>id</span></a>, <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#usage.entity"><span class='attribute'>entity</span></a>, <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#usage.time"><span class='attribute'>time</span></a>, and <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#usage.attributes"><span class='attribute'>attributes</span></a> MUST be present</td>
+<td><span class="name">used(a2, -, -)</span><br><span class="name">used(-; a2, -, -)</span></td>
+<td>At least one of <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#usage.id"><span class="attribute">id</span></a>, <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#usage.entity"><span class="attribute">entity</span></a>, <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#usage.time"><span class="attribute">time</span></a>, and <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#usage.attributes"><span class="attribute">attributes</span></a> <em class="rfc2119" title="MUST">MUST</em> be present</td>
</tr>
<tr>
<td><a class="grammarRef" href="#prod-startExpression">Start expression</a></td>
-<td> <span class="name">wasStartedBy(e2, -, -, -)</span><br/><span class="name">wasStartedBy(-; e2, -, -, -)</span></td>
-<td>At least one of <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#start.id"><span class='attribute'>id</span></a>, <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#start.trigger"><span class='attribute'>trigger</span></a>, <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#start.starter"><span class='attribute'>starter</span></a>, <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#start.time"><span class='attribute'>time</span></a>, and <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#start.attributes"><span class='attribute'>attributes</span></a> MUST be present</td>
+<td> <span class="name">wasStartedBy(e2, -, -, -)</span><br><span class="name">wasStartedBy(-; e2, -, -, -)</span></td>
+<td>At least one of <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#start.id"><span class="attribute">id</span></a>, <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#start.trigger"><span class="attribute">trigger</span></a>, <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#start.starter"><span class="attribute">starter</span></a>, <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#start.time"><span class="attribute">time</span></a>, and <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#start.attributes"><span class="attribute">attributes</span></a> <em class="rfc2119" title="MUST">MUST</em> be present</td>
</tr>
<tr>
<td><a class="grammarRef" href="#prod-endExpression">End expression</a></td>
-<td><span class="name">wasEndedBy(e2, -, -, -)</span><br/><span class="name">wasEndedBy(-; e2, -, -, -)</span></td>
-<td>At least one of <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#end.id"><span class='attribute'>id</span></a>, <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#end.trigger"><span class='attribute'>trigger</span></a>, <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#end.ender"><span class='attribute'>ender</span></a>, <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#end.time"><span class='attribute'>time</span></a>, and <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#end.attributes"><span class='attribute'>attributes</span></a> MUST be present</td>
+<td><span class="name">wasEndedBy(e2, -, -, -)</span><br><span class="name">wasEndedBy(-; e2, -, -, -)</span></td>
+<td>At least one of <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#end.id"><span class="attribute">id</span></a>, <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#end.trigger"><span class="attribute">trigger</span></a>, <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#end.ender"><span class="attribute">ender</span></a>, <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#end.time"><span class="attribute">time</span></a>, and <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#end.attributes"><span class="attribute">attributes</span></a> <em class="rfc2119" title="MUST">MUST</em> be present</td>
</tr>
<tr>
<td><a class="grammarRef" href="#prod-invalidationExpression">Invalidation expression</a></td>
-<td><span class="name">wasInvalidatedBy(e2, -, -)</span> <br/><span class="name">wasInvalidatedBy(-; e2, -, -)</span></td>
-<td>At least one of <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#invalidation.id"><span class='attribute'>id</span></a>, <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#invalidation.activity"><span class='attribute'>activity</span></a>, <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#invalidation.time"><span class='attribute'>time</span></a>, and <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#invalidation.attributes"><span class='attribute'>attributes</span></a> MUST be present</td>
+<td><span class="name">wasInvalidatedBy(e2, -, -)</span> <br><span class="name">wasInvalidatedBy(-; e2, -, -)</span></td>
+<td>At least one of <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#invalidation.id"><span class="attribute">id</span></a>, <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#invalidation.activity"><span class="attribute">activity</span></a>, <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#invalidation.time"><span class="attribute">time</span></a>, and <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#invalidation.attributes"><span class="attribute">attributes</span></a> <em class="rfc2119" title="MUST">MUST</em> be present</td>
</tr>
<tr>
<td><a class="grammarRef" href="#prod-associationExpression">Association expression</a></td>
-<td><span class="name">wasAssociatedWith(a, -, -)</span> <br/><span class="name">wasAssociatedWith(-; a, -, -)</span></td>
-<td>At least one of <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#association.id"><span class='attribute'>id</span></a>, <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#association.agent"><span class='attribute'>agent</span></a>, <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#association.plan"><span class='attribute'>plan</span></a>, and <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#association.attributes"><span class='attribute'>attributes</span></a> MUST be present</td>
+<td><span class="name">wasAssociatedWith(a, -, -)</span> <br><span class="name">wasAssociatedWith(-; a, -, -)</span></td>
+<td>At least one of <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#association.id"><span class="attribute">id</span></a>, <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#association.agent"><span class="attribute">agent</span></a>, <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#association.plan"><span class="attribute">plan</span></a>, and <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#association.attributes"><span class="attribute">attributes</span></a> <em class="rfc2119" title="MUST">MUST</em> be present</td>
</tr>
-</table>
+</tbody></table>
</div>
</section>
@@ -2779,26 +2809,25 @@
<section id="document">
-<h4>Document</h4>
-
-<p>A <dfn>document</dfn> is a house-keeping construct of PROV-N capable of packaging up PROV-N expressions and namespace declarations. A document forms a self-contained package of provenance descriptions for the purpose of <em>exchanging</em> them. A document may be used
- to package up PROV-N expressions in response to a request for the provenance of something ([[PROV-AQ]]).</p>
-
-<p> Given its status of house keeping construct for the purpose of exchanging provenance expressions, a document is not defined as a PROV-N expression (production <code class="content"><a class="grammarRef" href="#prod-expression">expression</a></code>).</p>
-
-
-
-
-
-<p>A document's text matches the <code class="content"><a class="grammarRef"
- href="#prod-document">document</a></code> production.</p>
+<!--OddPage--><h2><span class="secno">4. </span>Document</h2>
+
+<p>A <dfn id="dfn-document">document</dfn> is a house-keeping construct of PROV-N capable of packaging up PROV-N expressions and namespace declarations. A document forms a self-contained package of provenance descriptions for the purpose of <em>exchanging</em> them. A document may be used
+ to package up PROV-N expressions in response to a request for the provenance of something ([<cite><a class="bibref" href="#bib-PROV-AQ">PROV-AQ</a></cite>]).</p>
+
+<p> Given its status of house-keeping construct for the purpose of exchanging provenance expressions, a document is not defined as a PROV-N expression (production <code class="content"><a class="grammarRef" href="#prod-expression">expression</a></code>).</p>
+
+
+
+
+
+<p>A document's text matches the <code class="content"><a class="grammarRef" href="#prod-document">document</a></code> production.</p>
<table class="grammar">
-<tbody class="grammar-ref" data-ref="prod-document"></tbody>
+<tbody class="prod"> <tr style="vertical-align: baseline; "> <td><a id="prod-document" data-name="prod-document"></a>[<span class="prodNo">1</span>] </td> <td><code class="production prod">document</code></td> <td> ::= </td> <td><code class="content">"document" (<span class="prod"><a class="grammarRef" href="#prod-namespaceDeclarations">namespaceDeclarations</a></span>)? (<span class="prod"><a class="grammarRef" href="#prod-expression">expression</a></span>)* (<span class="prod"><a class="grammarRef" href="#prod-bundle">bundle</a></span>)* "endDocument"</code></td> </tr> </tbody>
</table>
<p>A document contains:
-<ul>
+</p><ul>
<li><em>namespaceDeclarations</em>: a set of namespace declarations <code><a class="grammarRef" href="#prod-namespaceDeclarations">namespaceDeclarations</a></code>, declaring namespaces and associated prefixes, which can be used in attributes and identifiers occurring inside <em>expressions</em> or <em>bundles</em>;</li>
<li><em>expressions</em>: a set of expressions, each matching <code><a class="grammarRef" href="#prod-expression">expression</a></code>;</li>
<li><em>bundles</em>: a set of expressions, each matching
@@ -2806,18 +2835,17 @@
</ul>
-<p>Thus, bundles MAY occur inside a document, but do not appear inside other bundles.
+<p>Thus, bundles <em class="rfc2119" title="MAY">MAY</em> occur inside a document, but do not appear inside other bundles.
</p>
-<div class="anexample">
+<div class="anexample" id="example_45"><div class="anexampleTitle"><a class="internalDFN" href="#example_45">Example 45</a></div>
<p>
The following document contains expressions related to the provenance of entity
<span class="name">e2</span>.
</p>
-<pre class="codeexample">
-document
+<pre class="codeexample">document
default <http://anotherexample.org/>
prefix ex <http://example.org/>
@@ -2830,7 +2858,7 @@
endDocument
</pre>
-<p>This container could for instance be returned as the result of a query to a provenance store for the provenance of entity <span class="name">e2</span> [[PROV-AQ]].
+<p>This container could, for instance, be returned as the result of a query to a provenance store for the provenance of entity <span class="name">e2</span> [<cite><a class="bibref" href="#bib-PROV-AQ">PROV-AQ</a></cite>].
</p>
</div>
@@ -2839,47 +2867,42 @@
</section>
<section id="extensibility">
-<h4>Extensibility</h4>
+<!--OddPage--><h2><span class="secno">5. </span>Extensibility</h2>
<p>The PROV data model is extensible by means of attributes <span class="name">prov:type</span> and <span class="name">prov:role</span> allowing subtyping of expressions. For some applications, novel syntax may also be convenient. Hence, the normative requirements are as follow.</p>
<ul>
-<li> PROV-N compliant parsers MUST be able to parse expressions matching the <code class="content"><a class="grammarRef"
- href="#prod-extensibilityExpression">extensibilityExpression</a></code> production defined below.
-<li> As PROV provides no definition for these expressions, PROV compliant implementations
- MAY ignore these expressions.</li>
-<li> Extensions to PROV and PROV-N MAY specify more specific productions and interpretations for these expressions, which applications MAY elect to follow. </li>
+<li> PROV-N compliant parsers <em class="rfc2119" title="MUST">MUST</em> be able to parse expressions matching the <code class="content"><a class="grammarRef" href="#prod-extensibilityExpression">extensibilityExpression</a></code> production defined below.
+</li><li> As PROV provides no definition for these expressions, PROV compliant implementations
+ <em class="rfc2119" title="MAY">MAY</em> ignore these expressions.</li>
+<li> Extensions to PROV and PROV-N <em class="rfc2119" title="MAY">MAY</em> specify more specific productions and interpretations for these expressions, which applications <em class="rfc2119" title="MAY">MAY</em> elect to follow. </li>
</ul>
<table class="grammar">
-<tbody class="grammar-ref" data-ref="prod-extensibilityExpression"></tbody>
-<tbody class="grammar-ref" data-ref="prod-extensibilityArgument"></tbody>
-<tbody class="grammar-ref" data-ref="prod-extensibilityTuple"></tbody>
+<tbody class="prod"> <tr style="vertical-align: baseline; "> <td><a id="prod-extensibilityExpression" data-name="prod-extensibilityExpression"></a>[<span class="prodNo">49</span>] </td> <td><code class="production prod">extensibilityExpression</code></td> <td> ::= </td> <td><code class="content"><span class="prod"><a class="grammarRef" href="#prod-QUALIFIED_NAME">QUALIFIED_NAME</a></span> "(" <span class="prod"><a class="grammarRef" href="#prod-optionalIdentifier">optionalIdentifier</a></span> <span class="prod"><a class="grammarRef" href="#prod-extensibilityArgument">extensibilityArgument</a></span> ( "," <span class="prod"><a class="grammarRef" href="#prod-extensibilityArgument">extensibilityArgument</a></span> )* <span class="prod"><a class="grammarRef" href="#prod-optionalAttributeValuePairs">optionalAttributeValuePairs</a></span> ")"</code></td> </tr> </tbody>
+<tbody class="prod"> <tr style="vertical-align: baseline; "> <td><a id="prod-extensibilityArgument" data-name="prod-extensibilityArgument"></a>[<span class="prodNo">50</span>] </td> <td><code class="production prod">extensibilityArgument</code></td> <td> ::= </td> <td><code class="content">( <span class="prod"><a class="grammarRef" href="#prod-identifierOrMarker">identifierOrMarker</a></span> | <span class="prod"><a class="grammarRef" href="#prod-literal">literal</a></span> | <span class="prod"><a class="grammarRef" href="#prod-time">time</a></span> | <span class="prod"><a class="grammarRef" href="#prod-extensibilityExpression">extensibilityExpression</a></span> | <span class="prod"><a class="grammarRef" href="#prod-extensibilityTuple">extensibilityTuple</a></span> )</code></td> </tr> </tbody>
+<tbody class="prod"> <tr style="vertical-align: baseline; "> <td><a id="prod-extensibilityTuple" data-name="prod-extensibilityTuple"></a>[<span class="prodNo">51</span>] </td> <td><code class="production prod">extensibilityTuple</code></td> <td> ::= </td> <td><code class="content">"{" <span class="prod"><a class="grammarRef" href="#prod-extensibilityArgument">extensibilityArgument</a></span> ( "," <span class="prod"><a class="grammarRef" href="#prod-extensibilityArgument">extensibilityArgument</a></span> )* "}"<br> | "(" <span class="prod"><a class="grammarRef" href="#prod-extensibilityArgument">extensibilityArgument</a></span> ( "," <span class="prod"><a class="grammarRef" href="#prod-extensibilityArgument">extensibilityArgument</a></span> )* ")"</code></td> </tr> </tbody>
</table>
<p>Expressions compatible with the
-<code class="content"><a class="grammarRef"
- href="#prod-extensibilityExpression">extensibilityExpression</a></code> production follow a general form of functional syntax, in which the predicate MUST be a
+<code class="content"><a class="grammarRef" href="#prod-extensibilityExpression">extensibilityExpression</a></code> production follow a general form of functional syntax, in which the predicate <em class="rfc2119" title="MUST">MUST</em> be a
<code class="content"><a class="grammarRef" href="#prod-QUALIFIED_NAME">qualifiedName</a></code>
with a non-empty <code class="content"><a class="grammarRef" href="http://www.w3.org/TR/rdf-sparql-query/#rPN_PREFIX">prefix</a></code>.</p>
-<div class="anexample">
+<div class="anexample" id="example_46"><div class="anexampleTitle"><a class="internalDFN" href="#example_46">Example 46</a></div>
<p>
<a href="#component6">Collections</a> are sets of entities, whose membership can be expressed using the <span class="name">hadMember</span> relation. The following example shows how one can express membership for <em>dictionaries</em>, an illustrative extension of Collections consisting of sets of key-entity pairs, where a key is a <code><a class="grammarRef" href="#prod-literal">literal</a></code>. The notation is a variation of that used for Collections membership, allowing multiple member elements to be declared, and in which the elements are pairs. The name of the relation is qualified with the extension-specific namespace <span class="name">http://example.org/dictionaries</span>.
</p>
-<pre class="codeexample">
- prefix dictExt <http://example.org/dictionaries#>
+<pre class="codeexample"> prefix dictExt <http://example.org/dictionaries#>
dictExt:hadMembers(mId; d, {("k1",e1), ("k2",e2), ("k3",e3)}, [])
</pre>
-Note that the generic <code class="content"><a class="grammarRef"
- href="#prod-extensibilityExpression">extensibilityExpression</a></code> production above allows for alternative notations to be used for expressing membership, if the designers of the extensions so desire. Here is an alternate syntax that is consistent with the productions:
-<pre class="codeexample">
- prefix dictExt <http://example.org/dictionaries#>
+Note that the generic <code class="content"><a class="grammarRef" href="#prod-extensibilityExpression">extensibilityExpression</a></code> production above allows for alternative notations to be used for expressing membership, if the designers of the extensions so desire. Here is an alternate syntax that is consistent with the productions:
+<pre class="codeexample"> prefix dictExt <http://example.org/dictionaries#>
dictExt:hadMembers(mid; d, dictExt:set(dictExt:pair("k1",e1),
dictExt:pair("k2",e2),
dictExt:pair("k3",e3)),
@@ -2895,8 +2918,8 @@
</section>
-<section id="media-type">
-<h3>Media Type</h3>
+<section id="media-type">
+<!--OddPage--><h2><span class="secno">6. </span>Media Type</h2>
<p>
The media type of PROV-N is <span class="name">text/provenance-notation</span>. The content encoding of PROV-N content is UTF-8.
@@ -2907,12 +2930,12 @@
<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 W3C 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>
+ <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-N is "text/provenance-notation".</p>
- <p>It is recommended that PROV-N files have the extension ".provn" (all lowercase) on all platforms.</p>
- <p>It is recommended that PROV-N files stored on Macintosh HFS file systems be given a file type of "TEXT".</p>
+ <p>The Internet Media Type / MIME Type for PROV-N is "text/provenance-notation".</p>
+ <p>It is recommended that PROV-N files have the extension ".provn" (all lowercase) on all platforms.</p>
+ <p>It is recommended that PROV-N files stored on Macintosh HFS file systems be given a file type of "TEXT".</p>
<p>The information that follows has been <a href="http://www.iana.org/assignments/media-types/text/provenance-notation">registered with IANA</a>.</p>
<dl>
<dt>Type name:</dt>
@@ -2920,23 +2943,23 @@
<dt>Subtype name:</dt>
<dd>provenance-notation</dd>
<dt>Required parameters:</dt>
- <dd><kbd>charset</kbd> — the value of <kbd>charset</kbd> MUST always be <kbd>UTF-8</kbd>.</dd>
+ <dd><kbd>charset</kbd> — the value of <kbd>charset</kbd> <em class="rfc2119" title="MUST">MUST</em> always be <kbd>UTF-8</kbd>.</dd>
<dt>Optional parameters:</dt>
<dd>None</dd>
<dt>Encoding considerations: 8bit</dt>
- <dd>The syntax of PROV-N is expressed over code points in Unicode [[!UNICODE]]. The encoding is always UTF-8 [[!UTF-8]].</dd>
+ <dd>The syntax of PROV-N is expressed over code points in Unicode [<cite><a class="bibref" href="#bib-UNICODE">UNICODE</a></cite>]. The encoding is always UTF-8 [<cite><a class="bibref" href="#bib-UTF-8">UTF-8</a></cite>].</dd>
<dd>Unicode code points may also be expressed using an \uXXXX (U+0 to U+FFFF) or \UXXXXXXXX syntax (for U+10000 onwards) where X is a hexadecimal digit [0-9A-F]</dd>
<dt>Security considerations:</dt>
- <dd>PROV-N is a general-purpose language for describing the provenance of things; applications may evaluate given data to infer more descriptions or to dereference URIs, invoking the security considerations of the scheme for that URI. Note in particular, the privacy issues in [[!RFC3023]] 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-N is a general-purpose language for describing the provenance of things; applications may evaluate given data to infer more descriptions or 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-N is used to express the provenance of arbitrary application data; security considerations will vary by domain of use. Security tools and protocols applicable to text (e.g. PGP encryption, MD5 sum validation, password-protected compression) may also be used on PROV-N documents. Security/privacy protocols must be imposed which reflect the sensitivity of the embedded information. </dd>
- <dd>PROV-N 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 ([[!RFC3023]] section 10) provide additional guidance around the expression of arbitrary data and markup.</dd>
+ <dd>PROV-N 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-N is a language for describing the provenance of things, and therefore a PROV-N document is metadata for other resources. Untrusted PROV-N documents may mislead its consumers by indicating that a third-party resource has a reputable lineage, when it has not. Provenance of PROV-N document should be sought. </dd>
<dd>PROV-N uses qualified names mappable to IRIs as term identifiers. Applications interpreting data expressed in PROV-N should address the security issues of
- <a class="norm" href="http://www.ietf.org/rfc/rfc3987.txt">Internationalized Resource Identifiers (IRIs)</a> [[!RFC3987]] Section 8, as well as
- <a class="norm" href="http://www.ietf.org/rfc/rfc3986.txt">Uniform Resource Identifier (URI): Generic Syntax</a> [[!RFC3986]] Section 7.</dd>
+ <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
+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).
@@ -2944,9 +2967,9 @@
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> [[UNISEC]] and
+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> [[!RFC3987]] Section 8.
+Identifiers (IRIs)</a> [<cite><a class="bibref" href="#bib-RFC3987">RFC3987</a></cite>] Section 8.
</dd>
<dd>PROV-N offers an extensibility mechanism, which in turn may introduce additional security considerations. For example, predicates in extensibility expressions use qualified names, mappable to IRIs, and appropriate security considerations for IRIs apply too.</dd>
@@ -2965,7 +2988,7 @@
<dt>Base URI:</dt>
<dd>There are no constructs in the PROV-N Syntax to change the Base IRI.</dd>
<dt>Macintosh file type code(s):</dt>
- <dd>"TEXT"</dd>
+ <dd>"TEXT"</dd>
<dt>Person & email address to contact for further information:</dt>
<dd>Ivan Herman, ivan@w3.org</dd>
<dt>Intended usage:</dt>
@@ -2973,74 +2996,66 @@
<dt>Restrictions on usage:</dt>
<dd>None</dd>
<dt>Author/Change controller:</dt>
- <dd>The PROV-N specification is the product of the World Wide Web Consortium's Provenance Working Group. The W3C has change control over this specification.</dd>
+ <dd>The PROV-N specification is the product of the World Wide Web Consortium's Provenance Working Group. The <abbr title="World Wide Web Consortium">W3C</abbr> has change control over this specification.</dd>
</dl>
</section>
-<div id="glossary_div" class="remove">
-<!-- glossary loaded from glossary.js will be hooked up here,
- class remove, will remove this element from the final output.
--->
-</div>
-
-
-<div id="grammar_div" class="remove" style="display:none; ">
-<!-- grammar loaded from glossary.js will be hooked up here,
- class remove, will remove this element from the final output.
--->
-</div>
-
-<section class="appendix informative">
- <h2>Change Log</h2>
-
-<section>
- <h2>Changes since Proposed Recommendation</h2>
+
+
+
+
+
+<section class="appendix informative" id="change-log">
+ <!--OddPage--><h2><span class="secno">A. </span>Change Log</h2><p><em>This section is non-normative.</em></p>
+
+<section id="changes-since-proposed-recommendation">
+ <h3><span class="secno">A.1 </span>Changes since Proposed Recommendation</h3><p><em>This section is non-normative.</em></p>
<ul>
<li> Changed the status of this document section.
-<li> Changed all URLs to PROV documents.
-<li> Updated URL to IANA registered text/provenance-notation mime type.
-</ul>
+</li><li> Changed all URLs to PROV documents.
+</li><li> Updated URL to IANA registered text/provenance-notation mime type.
+</li></ul>
</section>
-<section class="appendix informative">
- <h2>Changes since Candidate Recommendation</h2>
+<section class="appendix informative" id="changes-since-candidate-recommendation">
+ <h3><span class="secno">A.2 </span>Changes since Candidate Recommendation</h3><p><em>This section is non-normative.</em></p>
<ul>
<li> Checked that all fragments resolved.
-<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> Changed all URLs to PROV documents.
-<li> Clarified a sentence about the (non) nesting of bundles.
-<li> Added html link to provenance.
-<li> Updated security consideration for extensibility feature of PROV-N following IANA feedback.
-</ul>
+</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> Clarified a sentence about the (non) nesting of bundles.
+</li><li> Added html link to provenance.
+</li><li> Updated security consideration for extensibility feature of PROV-N following IANA feedback.
+</li></ul>
</section>
-<section class="appendix informative">
- <h2>Changes since last call</h2>
+<section class="appendix informative" id="changes-since-last-call">
+ <h3><span class="secno">A.3 </span>Changes since last call</h3><p><em>This section is non-normative.</em></p>
<p> Please see the <a href="http://www.w3.org/2011/prov/wiki/ResponsesToPublicComments">Responses to Public Comments on the Last Call Working Draft</a> for more details about the justification of these changes.</p>
<ul>
<li> <a href="http://www.w3.org/2011/prov/track/issues/543">ISSUE-543</a>: Uses key-entity pair terminology for example 43.
-<li> <a href="http://www.w3.org/2011/prov/track/issues/538">ISSUE-538</a>: Rephrasing of text in example 10.
-<li> <a href="http://www.w3.org/2011/prov/track/issues/547">ISSUE-547</a>: Aligned terminology and productions with prov-constraints document, renaming 'toplevel bundle' to 'document', and renaming 'named bundle' to 'bundle'.
-<li> <a href="http://www.w3.org/2011/prov/track/issues/496">ISSUE-496</a>: For each prov-n term, added a cross-reference to corresponding prov-dm term (see table following each production). Rephrased text related to scope of a namespace declaration. Added an informative file with all productions.
-<li> <a href="http://www.w3.org/2011/prov/track/issues/573">ISSUE-573</a>: Updated Media Type section.
-<li> <a href="http://www.w3.org/2011/prov/track/issues/589">ISSUE-589</a>: Updated scoping rule for prefix-namespace declaration. Also refrained from saying bundles are self-contained.
-<li> Moved feature at Risk mention into a separate note.
-<li> Editorial's pass pre-publication.
-</ul>
+</li><li> <a href="http://www.w3.org/2011/prov/track/issues/538">ISSUE-538</a>: Rephrasing of text in example 10.
+</li><li> <a href="http://www.w3.org/2011/prov/track/issues/547">ISSUE-547</a>: Aligned terminology and productions with prov-constraints document, renaming 'toplevel bundle' to 'document', and renaming 'named bundle' to 'bundle'.
+</li><li> <a href="http://www.w3.org/2011/prov/track/issues/496">ISSUE-496</a>: For each prov-n term, added a cross-reference to corresponding prov-dm term (see table following each production). Rephrased text related to scope of a namespace declaration. Added an informative file with all productions.
+</li><li> <a href="http://www.w3.org/2011/prov/track/issues/573">ISSUE-573</a>: Updated Media Type section.
+</li><li> <a href="http://www.w3.org/2011/prov/track/issues/589">ISSUE-589</a>: Updated scoping rule for prefix-namespace declaration. Also refrained from saying bundles are self-contained.
+</li><li> Moved feature at Risk mention into a separate note.
+</li><li> Editorial's pass pre-publication.
+</li></ul>
</section>
</section>
-<section class="appendix informative">
- <h2>Acknowledgements</h2>
+<section class="appendix informative" id="acknowledgements">
+ <!--OddPage--><h2><span class="secno">B. </span>Acknowledgements</h2><p><em>This section is non-normative.</em></p>
<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 (W3C/MIT) and Ivan Herman (W3C/ERCIM), W3C contacts for the Provenance Working Group.
+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>
@@ -3083,9 +3098,9 @@
Paul Groth (Vrije Universiteit),
Olaf Hartig (Invited expert),
David Hau (National Cancer Institute, NCI),
-Sandro Hawke (W3C/MIT),
+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, (W3C/ERCIM),
+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),
@@ -3124,4 +3139,28 @@
</section>
- </body></html>
+
+<section id="references" class="appendix"><!--OddPage--><h2><span class="secno">C. </span>References</h2><section id="normative-references"><h3><span class="secno">C.1 </span>Normative references</h3><dl class="bibliography"><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-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-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-RDF-SPARQL-QUERY">[RDF-SPARQL-QUERY]</dt><dd>Andy Seaborne; Eric Prud'hommeaux. <a href="http://www.w3.org/TR/2008/REC-rdf-sparql-query-20080115"><cite>SPARQL Query Language for RDF</cite></a>. 15 January 2008. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2008/REC-rdf-sparql-query-20080115">http://www.w3.org/TR/2008/REC-rdf-sparql-query-20080115</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 (RFC 3023)</cite></a>. January 2001. RFC. 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 (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-UNICODE">[UNICODE]</dt><dd>The Unicode Consortium. <a href="http://www.unicode.org/unicode/standard/versions/enumeratedversions.html"><cite>The Unicode Standard.</cite></a> Defined by: The Unicode Standard, Version 6.2.0, (Mountain View, CA: The Unicode Consortium, 2012. ISBN 978-1-936213-07-8) , as updated from time to time by the publication of new versions URL: <a href="http://www.unicode.org/unicode/standard/versions/enumeratedversions.html">http://www.unicode.org/unicode/standard/versions/enumeratedversions.html</a>
+</dd><dt id="bib-UTF-8">[UTF-8]</dt><dd>F. Yergeau. <a href="http://www.ietf.org/rfc/rfc3629.txt"><cite>UTF-8, a transformation format of ISO 10646</cite></a>. IETF RFC 3629. November 2003. URL: <a href="http://www.ietf.org/rfc/rfc3629.txt">http://www.ietf.org/rfc/rfc3629.txt</a>
+</dd><dt id="bib-XML-NAMES">[XML-NAMES]</dt><dd>Richard Tobin et al. <a href="http://www.w3.org/TR/2009/REC-xml-names-20091208/"><cite>Namespaces in XML 1.0 (Third Edition)</cite></a>. 8 December 2009. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2009/REC-xml-names-20091208/">http://www.w3.org/TR/2009/REC-xml-names-20091208/</a>
+</dd><dt id="bib-XML11">[XML11]</dt><dd>Eve Maler et al. <a href="http://www.w3.org/TR/2006/REC-xml11-20060816"><cite>Extensible Markup Language (XML) 1.1 (Second Edition)</cite></a>. 16 August 2006. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2006/REC-xml11-20060816">http://www.w3.org/TR/2006/REC-xml11-20060816</a>
+</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-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>
+</dd><dt id="bib-PROV-RDF">[PROV-RDF]</dt><dd>James Cheney <a href="http://www.w3.org/2011/prov/wiki/ProvRDF"><cite>PROV-RDF Mapping </cite></a>2012, Working in Progress. URL: <a href="http://www.w3.org/2011/prov/wiki/ProvRDF">http://www.w3.org/2011/prov/wiki/ProvRDF</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-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>