--- a/model/diff-c.html Mon Mar 25 15:24:00 2013 +0000
+++ b/model/diff-c.html Mon Mar 25 15:26:37 2013 +0000
@@ -1,5230 +0,0 @@
-<!DOCTYPE html>
-<html lang="en" dir="ltr">
-<head><style type="text/css"><!--
-
-.insert { background-color: #aaffaa }
-.delete { background-color: #ff8888; text-decoration: line-through }
-.tagInsert { background-color: #007700; color: #ffffff }
-.tagDelete { background-color: #770000; color: #ffffff }
-
---></style>
- <title>Constraints of 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-constraints">
-
-
-
- <style type="text/css">
- .note { font-size:small; margin-left:50px }
-
-
-/* --- EDITORIAL NOTES --- */
-.pending {
- padding: 1em;
- margin: 1em 0em 0em;
- border: 1px solid #f00;
- background: #BFEFFF;
-}
-
-.pending::before {
- content: "Pending Review";
- display: block;
- width: 150px;
- margin: -1.5em 0 0.5em 0;
- font-weight: bold;
- border: 1px solid #f00;
- background: #fff;
- padding: 3px 1em;
-}
-
-
-
-
-.resolved {
- padding: 1em;
- margin: 1em 0em 0em;
- border: 1px solid #f00;
- background: #9BCD9B;
-}
-
-.resolved::before {
- content: "Resolved";
- display: block;
- width: 150px;
- margin: -1.5em 0 0.5em 0;
- font-weight: bold;
- border: 1px solid #f00;
- background: #fff;
- padding: 3px 1em;
-}
-
-
-.inference {
- padding: 1em;
- margin: 1em 0em 0em;
- border: 1px solid #f00;
- background: #fff;
-}
-
-
-.inference-example {
- padding: 1em;
- margin: 1em 0em 0em;
- border: 1px solid #f00;
- background: #fff;
-}
-
-/* .inference[id]::before { */
-/* content: "Inference: " attr(id); */
-/* width: 380px; /\* How can we compute the length of "Constraint: " attr(id) *\/ */
-/* } */
-
-
-/* .inference::before { */
-/* content: "Inference"; */
-/* display: block; */
-/* width: 150px; */
-/* margin: -1.5em 0 0.5em 0; */
-/* font-weight: bold; */
-/* border: 1px solid #f00; */
-/* background: #fff; */
-/* padding: 3px 1em; */
-/* } */
-
-.syntax {
- padding: 1em;
- margin: 1em 0em 0em;
- border: 1px solid #f00;
- background: #fff;
-}
-
-.syntax[id]::before {
- content: "Syntax: " attr(id);
- width: 380px; /* How can we compute the length of "Constraint: " attr(id) */
-}
-
-
-.syntax::before {
- content: "Syntax";
- display: block;
- width: 150px;
- margin: -1.5em 0 0.5em 0;
- font-weight: bold;
- border: 1px solid #f00;
- background: #fff;
- padding: 3px 1em;
-}
-
-.unamedconstraint {
- padding: 1em;
- margin: 1em 0em 0em;
- border: 1px solid #00f;
- background: #fff;
-}
-
-
-.unamedconstraint::before {
- content: "Constraint";
- display: block;
- width: 150px;
- margin: -1.5em 0 0.5em 0;
- font-weight: bold;
- border: 1px solid #00f;
- background: #fff;
- padding: 3px 1em;
-}
-
-
-
-.constraint {
- padding: 1em;
- margin: 1em 0em 0em;
- border: 1px solid #00f;
- background: #fff;
-}
-
-.constraint-example {
- padding: 1em;
- margin: 1em 0em 0em;
- border: 1px solid #00f;
- background: #fff;
-}
-
-/* .constraint[id]::before { */
-/* content: "Constraint: " attr(id); */
-/* width: 380px; /\* How can we compute the length of "Constraint: " attr(id) *\/ */
-/* } */
-
-
-/* .constraint::before { */
-/* content: "Constraint"; */
-/* display: block; */
-/* width: 150px; */
-/* margin: -1.5em 0 0.5em 0; */
-/* font-weight: bold; */
-/* border: 1px solid #00f; */
-/* background: #fff; */
-/* padding: 3px 1em; */
-/* } */
-
-
-
-.interpretation {
- padding: 1em;
- margin: 1em 0em 0em;
- border: 1px solid #00f;
- background: #fff;
-}
-
-.interpretation[id]::before {
- content: "Interpretation: " attr(id);
- width: 380px; /* How can we compute the length of "Interpretation: " attr(id) */
-}
-
-
-.interpretation::before {
- content: "Interpretation";
- display: block;
- width: 150px;
- margin: -1.5em 0 0.5em 0;
- font-weight: bold;
- border: 1px solid #00f;
- background: #fff;
- padding: 3px 1em;
-}
-
-.definition {
- padding: 1em;
- margin: 1em 0em 0em;
- border: 1px solid #777;
- background: #fff;
-}
-
-.definition-example {
- padding: 1em;
- margin: 1em 0em 0em;
- border: 1px solid #777;
- background: #fff;
-}
-
-/* .definition[id]::before { */
-/* content: "Definition: " attr(id); */
-/* width: 380px; */
-/* } */
-
-
-/* .definition::before { */
-/* content: "Definition"; */
-/* display: block; */
-/* width: 150px; */
-/* margin: -1.5em 0 0.5em 0; */
-/* font-weight: bold; */
-/* border: 1px solid #000; */
-/* background: #fff; */
-/* padding: 3px 1em; */
-/* } */
-
-
-.deprecatedconstraint {
- padding: 1em;
- margin: 1em 0em 0em;
- border: 1px solid #00f;
- background: #fff;
-}
-
-.deprecatedconstraint[id]::before {
- content: "Deprecated: " attr(id);
- width: 380px; /* How can we compute the length of "Deprecatedconstraint: " attr(id) */
-}
-
-
-.deprecatedconstraint::before {
- content: "Deprecated";
- display: block;
- width: 150px;
- margin: -1.5em 0 0.5em 0;
- font-weight: bold;
- border: 1px solid #00f;
- background: #fff;
- padding: 3px 1em;
-}
-
-.glossary-ref {
- font-style: italic;
-}
-
-.dfn {
- font-weight: bold;
-}
-
-
-.attribute {
- font-style: italic;
-}
-
-
-.conditional {
- color: blue;
-}
-
-.grammar {
- margin-top: 1ex;
- margin-bottom: 1ex;
- padding-left: 1ex;
- padding-right: 1ex;
- padding-top: 1ex;
- padding-bottom: 0.6ex;
- border: 1px dashed #2f6fab;
- font-size: 95%;
-}
-.nonterminal {
- font-weight: bold;
- font-family: sans-serif;
- font-size: 95%;
-}
-
-.name {
- font-family: monospace;
-}
-
-.math {
- font-family: roman;
- font-style:italic;
-}
-
-
-.xmpl {
- padding: 1em;
- margin: 1em 0em 0em;
- border: 1px solid #f00;
- background: #fff;
-}
-
-.xmpl::before {
- content: "Example";
- display: block;
- width: 150px;
- margin: -1.5em 0 0.5em 0;
- font-weight: bold;
- border: 1px solid #f00;
- background: #fff;
- padding: 3px 1em;
-}
-
-/*
-.anexample[count]::before {
- content: "Example " attr(count) ;
- font-family: sans-serif;
- font-size: 1.6ex;
- font-weight: bold;
-}
-
-.anexample:before {
- content: "Example:";
- font-family: sans-serif;
- font-size: 1.6ex;
- font-weight: bold;
-}
-
-*/
-
-.anexample {
- margin-top: 1ex;
- margin-bottom: 1ex;
- padding-left: 1ex;
- padding-right: 1ex;
- padding-top: 1ex;
- padding-bottom: 0.6ex;
- border: 1px dashed #2f6fab;
- background-color: #f9f9f9;
-}
-.anexample table {
- background-color: #f9f9f9;
-}
-
-.conceptexample:before {
- content: "Example:";
- font-family: sans-serif;
- font-size: 1.6ex;
- font-weight: bold;
-}
-.conceptexample {
- margin-top: 1ex;
- margin-bottom: 1ex;
- padding-left: 1ex;
- padding-right: 1ex;
- padding-top: 1ex;
- padding-bottom: 0.6ex;
- border: 1px dashed #2f6fab;
- background-color: #f9f9f9;
-}
-
-.pnExpression {
- font-weight: normal;
- font-size:120%;
- font-family: monospace;
-}
-
-
-div[class="grammar"] span[class="name"]:before {
- content: "'";
-}
-
-div[class="grammar"] span[class="name"]:after {
- content: "'";
-}
-
-
-div[class="grammar"] span[class="optional"]:before {
- font-weight: normal;
- font-size:130%;
- font-family: monospace;
- content: "(";
-}
-
-div[class="grammar"] span[class="optional"]:after {
- font-weight: normal;
- font-size:130%;
- font-family: monospace;
- content: ")?";
-}
-
-
-div[class="grammar"] span[class="plus"]:before {
- font-weight: normal;
- font-size:130%;
- font-family: monospace;
- content: "(";
-}
-
-div[class="grammar"] span[class="plus"]:after {
- font-weight: normal;
- font-size:130%;
- font-family: monospace;
- content: ")+";
-}
-
-
-div[class="grammar"] span[class="star"]:before {
- font-weight: normal;
- font-size:130%;
- font-family: monospace;
- content: "(";
-}
-
-div[class="grammar"] span[class="star"]:after {
- font-weight: normal;
- font-size:130%;
- font-family: monospace;
- content: ")*";
-}
-
-div[class="grammar"] span[class="choice"]:before {
- font-weight: normal;
- font-size:130%;
- font-family: monospace;
- content: "(";
-}
-
-div[class="grammar"] span[class="choice"]:after {
- font-weight: normal;
- font-size:130%;
- font-family: monospace;
- content: ")";
-}
-
-div[class="grammar"] span[class="group"]:before {
- font-weight: normal;
- font-size:130%;
- font-family: monospace;
- content: "(";
-}
-
-div[class="grammar"] span[class="group"]:after {
- font-weight: normal;
- font-size:130%;
- font-family: monospace;
- content: ")";
-}
-
-table {
- background-color: #f9f9f9;
-}
-
-.component1-color {
- background-color: rgba(255,42,42,0.2);
-}
-
-.component2-color {
- background-color: rgba(0,68,170,0.2);
-}
-
-.component3-color {
- background-color: rgba(0,170,0,0.2);
-}
-.component4-color {
- background-color: rgba(204,255,0,0.2);
-}
-
-.component5-color {
- background-color: rgba(11,40,40,0.2);
-}
-
-.component6-color {
- background-color: rgba(244,105,14,0.2);
-}
-
-.interpretation-forward::before {
- content: "Interpretation: ";
- font-weight: bold;
-}
-
-.structural-forward::before {
- content: "Structural constraint: ";
- font-weight: bold;
-}
-
-
-code {
- color: black;
-}
-
-.ruleTitle {
- font-family: sans-serif;
- font-size: 1.6ex;
- font-weight: bold;
-}
-
-
-
-
-.remark {
- padding: 1em;
- margin: 1em 0em 0em;
- border: 1px dashed #000;
- background: #F0F0F0;
-}
-
-.remark::before {
- content: "Remark";
- display: block;
- width: 150px;
- margin: -1.5em 0 0.5em 0;
- font-weight: bold;
- border: 1px solid #000;
- background: #fff;
- padding: 3px 1em;
-}
-
-table.thinborder {
- border-width: 1px;
- border-spacing: 0px;
- border-style: none;
- border-color: gray;
- border-collapse: collapse;
-}
-table.thinborder th {
- border-width: 1px;
- padding: 0px;
- border-style: solid;
- border-color: gray;
-}
-table.thinborder td {
- border-width: 1px;
- padding: 2px;
- border-style: solid;
- border-color: gray;
-}
-
-
- </style>
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- <style>/*****************************************************************
- * ReSpec 3 CSS
- * Robin Berjon - http://berjon.com/
- *****************************************************************/
-
-/* --- INLINES --- */
-em.rfc2119 {
- text-transform: lowercase;
- font-variant: small-caps;
- font-style: normal;
- color: #900;
-}
-
-h1 acronym, h2 acronym, h3 acronym, h4 acronym, h5 acronym, h6 acronym, a acronym,
-h1 abbr, h2 abbr, h3 abbr, h4 abbr, h5 abbr, h6 abbr, a abbr {
- border: none;
-}
-
-dfn {
- font-weight: bold;
-}
-
-a.internalDFN {
- color: inherit;
- border-bottom: 1px solid #99c;
- text-decoration: none;
-}
-
-a.externalDFN {
- color: inherit;
- border-bottom: 1px dotted #ccc;
- text-decoration: none;
-}
-
-a.bibref {
- text-decoration: none;
-}
-
-cite .bibref {
- font-style: normal;
-}
-
-code {
- color: #ff4500;
-}
-
-
-/* --- --- */
-ol.algorithm { counter-reset:numsection; list-style-type: none; }
-ol.algorithm li { margin: 0.5em 0; }
-ol.algorithm li:before { font-weight: bold; counter-increment: numsection; content: counters(numsection, ".") ") "; }
-
-/* --- TOC --- */
-.toc a, .tof a {
- text-decoration: none;
-}
-
-a .secno, a .figno {
- color: #000;
-}
-
-ul.tof, ol.tof {
- list-style: none outside none;
-}
-
-.caption {
- margin-top: 0.5em;
- font-style: italic;
-}
-
-/* --- TABLE --- */
-table.simple {
- border-spacing: 0;
- border-collapse: collapse;
- border-bottom: 3px solid #005a9c;
-}
-
-.simple th {
- background: #005a9c;
- color: #fff;
- padding: 3px 5px;
- text-align: left;
-}
-
-.simple th[scope="row"] {
- background: inherit;
- color: inherit;
- border-top: 1px solid #ddd;
-}
-
-.simple td {
- padding: 3px 10px;
- border-top: 1px solid #ddd;
-}
-
-.simple tr:nth-child(even) {
- background: #f0f6ff;
-}
-
-/* --- DL --- */
-.section dd > p:first-child {
- margin-top: 0;
-}
-
-.section dd > p:last-child {
- margin-bottom: 0;
-}
-
-.section dd {
- margin-bottom: 1em;
-}
-
-.section dl.attrs dd, .section dl.eldef dd {
- margin-bottom: 0;
-}
-</style><link rel="stylesheet" href="http://www.w3.org/StyleSheets/TR/W3C-PR"></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">Constraints of the PROV Data Model</h1>
-
- <h2 id="w3c-proposed-recommendation-12-march-2013"><abbr title="World Wide Web Consortium">W3C</abbr> <span class="delete">Candidate</span><span class="insert">Proposed</span> Recommendation <span class="delete">11 December 2012</span><span class="insert">12 March 2013</span></h2>
- <dl>
-
- <dt>This<span class="insert"> version:</span></dt>
- <dd><a href="http://www.w3.org/TR/2013/PR-prov-constraints-20130312/"><span class="insert">http://www.w3.org/TR/2013/PR-prov-constraints-20130312/</span></a></dd>
- <dt><span class="insert">Latest published version:</span></dt>
- <dd><a href="http://www.w3.org/TR/prov-constraints/"><span class="insert">http://www.w3.org/TR/prov-constraints/</span></a></dd>
-
-
-
- <dt><span class="insert">Test suite:</span></dt>
- <dd><a href="http://dvcs.w3.org/hg/prov/raw-file/default/testcases/process.html"><span class="insert">http://dvcs.w3.org/hg/prov/raw-file/default/testcases/process.html</span></a></dd>
-
-
- <dt><span class="insert">Implementation report:</span></dt>
- <dd><a href="http://www.w3.org/TR/2013/WD-prov-implementations-20130312/"><span class="insert">http://www.w3.org/TR/2013/WD-prov-implementations-20130312/</span></a></dd>
-
-
-
- <dt><span class="insert">Previous</span> version:</dt>
- <dd><a href="http://www.w3.org/TR/2012/CR-prov-constraints-20121211/">http://www.w3.org/TR/2012/CR-prov-constraints-20121211/
- <span class="delete">Latest published version:</span>
- <span class="delete">http://www.w3.org/TR/prov-constraints/</span>
-
-
-
- <span class="delete">Test suite:</span>
- <span class="delete">http://dvcs.w3.org/hg/prov/raw-file/default/testcases/process.html</span>
-
-
- <span class="delete">Implementation report:</span>
- <span class="delete">http://dvcs.w3.org/hg/prov/raw-file/default/reports/prov-implementations.html</span>
-
-
-
- <span class="delete">Previous version:</span>
- <span class="delete">http://www.w3.org/TR/2012/WD-prov-constraints-20120911/</span></a> <a href="diff-c.html">(color-coded diff)</a></dd>
-
-
- <dt>Editors:</dt>
- <dd><a href="http://homepages.inf.ed.ac.uk/jcheney">James Cheney</a>, University of Edinburgh</dd>
-<dd><a href="http://www.cs.ncl.ac.uk/people/Paolo.Missier">Paolo Missier</a>, Newcastle University</dd>
-<dd><a href="http://www.ecs.soton.ac.uk/~lavm/">Luc Moreau</a>, University of Southampton</dd>
-
-
- <dt>Author:</dt>
- <dd><a href="http://users.ugent.be/~tdenies/">Tom De Nies</a>, <span class="delete">IBBT</span><span class="insert">iMinds</span> - Ghent University</dd>
-
-
- </dl>
-
-
-
-
-
- <p class="copyright">
- <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> ©
- <span class="delete">2012</span><span class="insert">2012-2013</span>
-
- <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><span class="insert">, </span><a href="http://ev.buaa.edu.cn/"><span class="insert">Beihang</span></a>), All Rights Reserved.
- <abbr title="World Wide Web Consortium">W3C</abbr> <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>,
- <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and
- <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.
- </p>
-
-
- <hr>
-</div>
-
- <section id="abstract" class="introductory"><h2>Abstract</h2>
-<p>
-Provenance is information about entities, activities, and people
-involved in producing a piece of data or thing, which can be used to
-form assessments about its quality, reliability or
-trustworthiness. PROV-DM is the conceptual data model that forms a
-basis for the <abbr title="World Wide Web Consortium">W3C</abbr> provenance (PROV) family of specifications.
-
-</p>
-
-
-<p> This document defines a subset of PROV instances called
-<i><a href="#dfn-valid" class="internalDFN">valid</a></i> PROV instances, by analogy with notions of
-validity for other Web standards.
-The intent of validation is <span class="insert">to </span>ensure that a PROV instance represents a
-consistent history of objects and their interactions that is safe to
-use for the purpose of logical reasoning and other kinds of analysis.
-Valid PROV instances satisfy
-certain <a title="definition" href="#dfn-definition" class="internalDFN">definitions</a>, <a title="inference" href="#inference" class="internalDFN">inferences</a>, and
-<a title="constraint">constraints</a>. These definitions, inferences, and constraints
-provide a measure of consistency checking for provenance and reasoning
-over provenance. They can also be used to <a title="normal
-form" href="#dfn-normal-form" class="internalDFN">normalize</a> PROV instances to forms that can easily be
-compared in order to determine whether two PROV instances are
-<a title="equivalence">equivalent</a>. Validity and equivalence are also defined for PROV
-bundles (that is, named instances) and documents (that is, a toplevel
-instance together with zero or more bundles).</p>
-<p>The <a href="http://www.w3.org/TR/2013/WD-prov-overview-20130312/">PROV Document Overview</a> describes the overall state of PROV, and should be read before other PROV documents.</p>
-</section><section id="sotd" class="introductory"><h2>Status of This Document</h2>
-
-
-
- <p>
- <em>This section describes the status of this document at the time of its publication. Other
- documents may supersede this document. A list of current <abbr title="World Wide Web Consortium">W3C</abbr> publications and the latest revision
- of this technical report can be found in the <a href="http://www.w3.org/TR/"><abbr title="World Wide Web Consortium">W3C</abbr> technical reports
- index</a> at http://www.w3.org/TR/.</em>
- </p>
-
-<h4 id="prov-family-of-documents">PROV Family of Documents</h4>
-This document is part of the PROV family of documents, a set of documents defining various aspects that are necessary to achieve the vision of inter-operable
-interchange of provenance information in heterogeneous environments such as the Web. These documents <span class="delete">are:
-</span>
- <span class="delete">PROV-OVERVIEW</span><span class="delete"> (To be published as Note), an overview of the PROV family of documents</span><span class="insert">are listed below. Please consult the</span> [<cite><a class="bibref" href="#bib-PROV-OVERVIEW">PROV-OVERVIEW</a></cite><span class="insert">] for a guide to reading these documents.
-</span><ul>
-<li> <a href="http://www.w3.org/TR/2013/WD-prov-overview-20130312/"><span class="insert">PROV-OVERVIEW</span></a><span class="insert"> (To be published as Note), an overview of the PROV family of documents [</span><cite><a class="bibref" href="#bib-PROV-OVERVIEW"><span class="insert">PROV-OVERVIEW</span></a></cite>];</li>
-<li> <a href="http://www.w3.org/TR/2013/WD-prov-primer-20130312/">PROV-PRIMER</a> (To be published as Note), a primer for the PROV data model [<cite><a class="bibref" href="#bib-PROV-PRIMER">PROV-PRIMER</a></cite>];</li>
-<li> <a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/">PROV-O</a> <span class="delete">(Candidate</span><span class="insert">(Proposed</span> Recommendation), the PROV ontology, an OWL2 ontology allowing the mapping of PROV to RDF [<cite><a class="bibref" href="#bib-PROV-O">PROV-O</a></cite>];</li>
-<li> <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/">PROV-DM</a> <span class="delete">(Candidate</span><span class="insert">(Proposed</span> Recommendation), the PROV data model for provenance [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>];</li>
-<li> <a href="http://www.w3.org/TR/2013/PR-prov-n-20130312/">PROV-N</a> <span class="delete">(Candidate</span><span class="insert">(Proposed</span> Recommendation), a notation for provenance aimed at human consumption [<cite><a class="bibref" href="#bib-PROV-N">PROV-N</a></cite>];</li>
-<li> <a href="http://www.w3.org/TR/2013/PR-prov-constraints-20130312/">PROV-CONSTRAINTS</a><span class="delete">
-(Candidate</span><span class="insert"> (Proposed</span> Recommendation), a set of constraints applying to the PROV data model
- (this document);</li>
-<li> <a href="http://www.w3.org/TR/2013/WD-prov-xml-20130312/"><span class="insert">PROV-XML</span></a><span class="insert"> (To be published as Note), an XML schema for the PROV data model [</span><cite><a class="bibref" href="#bib-PROV-XML"><span class="insert">PROV-XML</span></a></cite><span class="insert">];</span></li>
-<li> <a href="http://www.w3.org/TR/2013/WD-prov-aq-20130312/">PROV-AQ</a> (To be published as Note), the mechanisms for accessing and querying provenance [<cite><a class="bibref" href="#bib-PROV-AQ">PROV-AQ</a></cite>]; </li>
-<li> <span class="delete">PROV-XML</span><a href="http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/"><span class="insert">PROV-DICTIONARY</span></a> (To be published as <span class="delete">Note), an XML schema for the PROV data model</span><span class="insert">Note) introduces a specific type of collection, consisting of key-entity pairs</span> [<cite><span class="delete">PROV-XML</span><a class="bibref" href="#bib-PROV-DICTIONARY"><span class="insert">PROV-DICTIONARY</span></a></cite><span class="insert">];</span></li>
-<li> <a href="http://www.w3.org/TR/2013/WD-prov-dc-20130312/"><span class="insert">PROV-DC</span></a><span class="insert"> (To be published as Note) provides a mapping between PROV and Dublic Core Terms [</span><cite><a class="bibref" href="#bib-PROV-DC"><span class="insert">PROV-DC</span></a></cite><span class="insert">];</span></li>
-<li> <a href="http://www.w3.org/TR/2013/WD-prov-sem-20130312/"><span class="insert">PROV-SEM</span></a><span class="insert"> (To be published as Note), a declarative specification in terms of first-order logic of the PROV data model [</span><cite><a class="bibref" href="#bib-PROV-SEM"><span class="insert">PROV-SEM</span></a></cite><span class="insert">];</span></li>
-<li> <a href="http://www.w3.org/TR/2013/WD-prov-links-20130312/"><span class="insert">PROV-LINKS</span></a><span class="insert"> (To be published as Note) introduces a mechanism to link across bundles [</span><cite><a class="bibref" href="#bib-PROV-LINKS"><span class="insert">PROV-LINKS</span></a></cite>].</li>
-</ul>
-
-
-<span class="delete">How to read the PROV Family of Documents</span>
-
-<span class="delete">[</span><span class="delete">PROV-OVERVIEW</span><span class="delete">] overviews the PROV family of documents. </span>
-<span class="delete">The primer [</span><span class="delete">PROV-PRIMER</span><span class="delete">] is the entry point to PROV offering an introduction to the provenance model.</span>
-<span class="delete">The Linked Data and Semantic Web community should focus on [</span><span class="delete">PROV-O</span><span class="delete">] defining PROV classes and properties specified in an OWL2 ontology. For further details, [</span><span class="delete">PROV-DM</span><span class="delete">] and PROV-CONSTRAINTS specify the constraints applicable to the data model, and its interpretation. </span>
-<span class="delete">The XML community should focus on [</span><span class="delete">PROV-XML</span><span class="delete">] defining an XML schema for PROV. Further details can also be found in [</span><span class="delete">PROV-DM</span><span class="delete">] and PROV-CONSTRAINTS.</span>
-<span class="delete">Developers seeking to retrieve or publish provenance should focus on [</span><span class="delete">PROV-AQ</span><span class="delete">].</span>
-<span class="delete">Readers seeking to implement other PROV serializations
-should focus on [</span><span class="delete">PROV-DM</span><span class="delete">] and PROV-CONSTRAINTS. [</span><span class="delete">PROV-O</span><span class="delete">], [</span><span class="delete">PROV-N</span><span class="delete">], and [</span><span class="delete">PROV-XML</span><span class="delete">] offer examples of mapping to RDF, text, and XML, respectively.</span>
-
-<h4 id="w3c-members-please-review-by-09-april-2013"><abbr title="World Wide Web Consortium"><span class="insert">W3C</span></abbr><span class="insert"> Members </span>Please <span class="delete">Comment</span><span class="insert">Review</span> By <span class="delete">January 31,</span><span class="insert">09 April</span> 2013</h4>
-
-<p>The<span class="delete"> Provenance Working Group seeks to gather experience from </span><span class="delete">implementations</span><span class="delete"> in order to increase confidence in the specifications and meet specific </span><span class="delete">exit criteria</span><span class="delete">. This document will remain a Candidate Recommendation until at least 31 January 31, 2013. After that date, when and if the exit criteria are met, the group intends to request </span><span class="delete">Proposed Recommendation</span><span class="delete"> status.
-
-
- </span><span class="delete">
- This document was published by the </span><span class="delete">Provenance Working Group</span><span class="delete"> as a Candidate Recommendation.
-
- This document is intended to become a</span> <abbr title="World Wide Web Consortium">W3C</abbr> <span class="insert">Director seeks review and feedback from </span><abbr title="World Wide Web Consortium"><span class="insert">W3C</span></abbr><span class="insert"> Advisory Committee representatives by 09 April 2013. This will allow the Director to assess consensus and determine whether to issue this document as a </span><abbr title="World Wide Web Consortium"><span class="insert">W3C</span></abbr> Recommendation.<span class="delete">
-
- If you wish</span></p>
-
-<p><span class="insert">Others are encouraged by the Provenance Working Group</span> to <span class="delete">make comments regarding this document, please</span><span class="insert">continue to</span> send <span class="delete">them</span><span class="insert">reports of implementation experience, and other feedback,</span> 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>).
-
-
- <span class="insert"> Reports of any success or difficulty with the test cases are encouraged. Open discussion among developers is welcome at
-</span><a href="mailto:public-prov-comments@w3.org"><span class="insert">public-prov-comments@w3.org</span></a><span class="insert">
- (</span><a href="mailto:public-prov-comments-request@w3.org?subject=subscribe"><span class="insert">subscribe</span></a><span class="insert">,
- </span><a href="http://lists.w3.org/Archives/Public/public-prov-comments/"><span class="insert">archives</span></a><span class="insert">).</span></p>
-
- <p><span class="insert">
- This document was published by the </span><a href="http://www.w3.org/2011/prov/"><span class="insert">Provenance Working Group</span></a><span class="insert"> as a Proposed Recommendation.
-
- This document is intended to become a </span><abbr title="World Wide Web Consortium">W3C</abbr> <span class="delete">publishes a Candidate Recommendation </span><span class="insert">Recommendation.
-
-
-
-
-
-
- The </span><abbr title="World Wide Web Consortium"><span class="insert">W3C</span></abbr><span class="insert"> Membership and other interested parties are invited
- </span>to <span class="delete">indicate</span><span class="insert">review the document and send comments to
-
- </span><a href="mailto:public-prov-comments@w3.org"><span class="insert">public-prov-comments@w3.org</span></a><span class="insert">
- (</span><a href="mailto:public-prov-comments-request@w3.org?subject=subscribe"><span class="insert">subscribe</span></a><span class="insert">,
- </span><a href="http://lists.w3.org/Archives/Public/public-prov-comments/"><span class="insert">archives</span></a><span class="insert">)
- through 09 April 2013.
- Advisory Committee Representatives should consult their
- </span><a href="https://www.w3.org/2002/09/wbs/myQuestionnaires"><span class="insert">WBS questionnaires</span></a><span class="insert">.
- Note</span> that <span class="delete">the document is believed
- to be stable and to encourage implementation by the developer community. This
- Candidate Recommendation is</span><span class="insert">substantive technical comments were</span> expected <span class="delete">to advance to Proposed Recommendation no earlier than
- 31 January 2013.
-
- All feedback is welcome.</span><span class="insert">during the Last Call review period that ended 10 October 2012.</span>
- </p>
-
-
-
-
-
- <p>
- Publication as a <span class="delete">Candidate</span><span class="insert">Proposed</span> Recommendation does not imply endorsement by the <abbr title="World Wide Web Consortium">W3C</abbr> Membership.
- This is a draft document and may be updated, replaced or obsoleted by other documents at
- any time. It is inappropriate to cite this document as other than work in progress.
- </p>
-
-
- <p>
-
- This document was produced by a group operating under the
- <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 <abbr title="World Wide Web Consortium">W3C</abbr> Patent Policy</a>.
-
-
-
-
- <abbr title="World Wide Web Consortium">W3C</abbr> maintains a <a href="http://www.w3.org/2004/01/pp-impl/46974/status" rel="disclosure">public list of any patent disclosures</a>
-
- made in connection with the deliverables of the group; that page also includes instructions for
- disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains
- <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential Claim(s)</a> must disclose the
- information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section
- 6 of the <abbr title="World Wide Web Consortium">W3C</abbr> Patent Policy</a>.
-
-
- </p>
-
-
-
-
-</section><section id="toc"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a href="#introduction" class="tocxref"><span class="secno">1. </span>Introduction<br>
-</a><ul class="toc"><li class="tocline"><a href="#conventions" class="tocxref"><span class="secno">1.1 </span>Conventions</a></li><li class="tocline"><a href="#purpose" class="tocxref"><span class="secno">1.2 </span>Purpose of 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="#audience" class="tocxref"><span class="secno">1.4 </span> Audience </a></li></ul></li><li class="tocline"><a href="#rationale" class="tocxref"><span class="secno">2. </span>Rationale (Informative)</a><ul class="toc"><li class="tocline"><a href="#entities-activities-and-agents" class="tocxref"><span class="secno">2.1 </span>Entities, Activities and Agents</a></li><li class="tocline"><a href="#events" class="tocxref"><span class="secno">2.2 </span>Events</a></li><li class="tocline"><a href="#typing-section" class="tocxref"><span class="secno">2.3 </span>Types</a></li><li class="tocline"><a href="#overview" class="tocxref"><span class="secno">2.4 </span>Validation Process Overview</a></li><li class="tocline"><a href="#summary-of-inferences-and-constraints" class="tocxref"><span class="secno">2.5 </span>Summary of inferences and constraints</a></li></ul></li><li class="tocline"><a href="#compliance" class="tocxref"><span class="secno">3. </span>Compliance with this document</a></li><li class="tocline"><a href="#concepts" class="tocxref"><span class="secno">4. </span>Basic concepts</a></li><li class="tocline"><a href="#inferences" class="tocxref"><span class="secno">5. </span>Definitions and Inferences</a><ul class="toc"><li class="tocline"><a href="#optional-identifiers-and-attributes" class="tocxref"><span class="secno">5.1 </span>Optional Identifiers and Attributes</a></li><li class="tocline"><a href="#entities-and-activities" class="tocxref"><span class="secno">5.2 </span>Entities and Activities</a></li><li class="tocline"><a href="#derivations" class="tocxref"><span class="secno">5.3 </span>Derivations</a></li><li class="tocline"><a href="#agents" class="tocxref"><span class="secno">5.4 </span>Agents</a></li><li class="tocline"><a href="#alternate-and-specialized-entities" class="tocxref"><span class="secno">5.5 </span>Alternate and Specialized Entities</a></li></ul></li><li class="tocline"><a href="#constraints" class="tocxref"><span class="secno">6. </span>Constraints</a><ul class="toc"><li class="tocline"><a href="#uniqueness-constraints" class="tocxref"><span class="secno">6.1 </span>Uniqueness Constraints</a></li><li class="tocline"><a href="#event-ordering-constraints" class="tocxref"><span class="secno">6.2 </span>Event Ordering Constraints</a><ul class="toc"><li class="tocline"><a href="#activity-constraints" class="tocxref"><span class="secno">6.2.1 </span>Activity constraints</a></li><li class="tocline"><a href="#entity-constraints" class="tocxref"><span class="secno">6.2.2 </span> Entity constraints</a></li><li class="tocline"><a href="#agent-constraints" class="tocxref"><span class="secno">6.2.3 </span> Agent constraints</a></li></ul></li><li class="tocline"><a href="#type-constraints" class="tocxref"><span class="secno">6.3 </span>Type Constraints</a></li><li class="tocline"><a href="#impossibility-constraints" class="tocxref"><span class="secno">6.4 </span>Impossibility constraints</a></li></ul></li><li class="tocline"><a href="#normalization-validity-equivalence" class="tocxref"><span class="secno">7. </span>Normalization, Validity, and Equivalence</a><ul class="toc"><li class="tocline"><a href="#instances" class="tocxref"><span class="secno">7.1 </span>Instances</a></li><li class="tocline"><a href="#bundle-constraints" class="tocxref"><span class="secno">7.2 </span>Bundles and Documents</a></li></ul></li><li class="tocline"><a href="#glossary" class="tocxref"><span class="secno">8. </span>Glossary</a></li><li class="tocline"><a href="#termination" class="tocxref"><span class="secno">A. </span>Termination of normalization</a></li><li class="tocline"><a href="#change-log" class="tocxref"><span class="secno">B. </span><span class="insert">Change Log</span></a><ul class="toc"><li class="tocline"><a href="#changes-from-candidate-recommendation-to-this-version" class="tocxref"><span class="secno"><span class="insert">B.1 </span></span>Changes <span class="delete">since last</span><span class="insert">from Candidate Recommendation to this</span> version</a></li><li class="tocline"><a href="#changes-from-last-call-working-draft-to-candidate-recommendation" class="tocxref"><span class="secno"><span class="insert">B.2 </span></span><span class="insert">Changes from Last Call Working Draft to Candidate Recommendation</span></a></li></ul></li><li class="tocline"><a href="#acknowledgements" class="tocxref"><span class="secno">C. </span>Acknowledgements</a></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">D. </span>References</a><ul class="toc"><li class="tocline"><a href="#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><span class="secno">1. </span>Introduction<br>
-</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.
-This document complements
- the PROV-DM specification [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>] that defines a data model for
- provenance on the Web. This document defines a form of validation for provenance. </p>
-
-
-
- <section id="conventions">
-<h3><span class="secno">1.1 </span>Conventions</h3>
-
-
-
-<p>The key words "<span class="delete">must</span><em class="rfc2119" title="MUST"><span class="insert">MUST</span></em>", "<span class="delete">must not</span><em class="rfc2119" title="MUST NOT"><span class="insert">MUST NOT</span></em>", "<span class="delete">required</span><em class="rfc2119" title="REQUIRED"><span class="insert">REQUIRED</span></em>", "<span class="delete">shall</span><em class="rfc2119" title="SHALL"><span class="insert">SHALL</span></em>", "<span class="delete">shall</span><em class="rfc2119" title="SHALL
- NOT"><span class="insert">SHALL</span>
- <span class="delete">not</span><span class="insert">NOT</span></em>", "<span class="delete">should</span><em class="rfc2119" title="SHOULD"><span class="insert">SHOULD</span></em>", "<span class="delete">should not</span><em class="rfc2119" title="SHOULD NOT"><span class="insert">SHOULD NOT</span></em>", "<span class="delete">recommended</span><em class="rfc2119" title="RECOMMENDED"><span class="insert">RECOMMENDED</span></em>", "<span class="delete">may</span><em class="rfc2119" title="MAY"><span class="insert">MAY</span></em>", and
- "<span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></em>" in this document are to be interpreted as described in
- [<cite><a class="bibref" href="#bib-RFC2119">RFC2119</a></cite>].</p>
-
-<p>In this document, logical formulas contain variables written as
- lower-case identifiers. Some of these variables are written
- beginning with the underscore character <span class="name">_</span>, by convention, to indicate that they
- appear only once in the formula. Such variables are
- provided merely as an aid to the reader. </p>
-
-</section>
-
-
-<section id="purpose">
-
-<h3><span class="secno">1.2 </span>Purpose of this document</h3>
-
-<p>The PROV Data Model, PROV-DM, is a conceptual data model for provenance, which is
-realizable using different representations such as PROV-N and PROV-O.
-A <dfn id="dfn-prov-instance">PROV instance</dfn> is a set of PROV statements.
-A <dfn id="dfn-prov-document">PROV document<span class="delete"> is</span></dfn><span class="insert"> consists of</span> an <span class="insert">anonymous instance, called the </span><dfn id="dfn-toplevel-instance"><span class="insert">toplevel </span>instance</dfn><span class="insert">,</span>
-together with zero or more <span class="insert">named instances, called </span><dfn title="bundle" id="dfn-bundle">bundles<span class="delete">, or named instances.</span></dfn><span class="insert">.</span> For
-example, a PROV document could be a .provn document, the result
-of a query, a triple store containing PROV statements in RDF, etc.
-The
-PROV-DM specification [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>] imposes minimal requirements upon
-PROV instances. A <a href="#dfn-valid" class="internalDFN">valid</a> PROV instance corresponds to a
-consistent history of objects and interactions to which logical
-reasoning can be safely applied. PROV instances need not
-be <a href="#dfn-valid" class="internalDFN">valid</a>.
-The term <a href="#dfn-valid" class="internalDFN">valid</a> is chosen by analogy with
-notions of validity in other <abbr title="World Wide Web Consortium">W3C</abbr> specifications. This
-terminology differs from the usual meaning of "validity" in logic;
-our notion of validity of a PROV instance/document is closer to
-logical "consistency".
-</p>
-
-<p> This document specifies <em>definitions</em> of some
-provenance statements in terms of others, <em>inferences</em> over PROV instances
-that applications <span class="delete">may</span><em class="rfc2119" title="MAY"><span class="insert">MAY</span></em> employ, and also defines a class of
-<a href="#dfn-valid" class="internalDFN">valid</a> PROV instances by specifying <em>constraints</em> that
-<a href="#dfn-valid" class="internalDFN">valid</a> PROV instances must satisfy. There are four kinds of
-constraints: <em>uniqueness constraints</em>, <em>event ordering
-constraints</em>, <em>impossibility constraints</em>, and <em>type
-constraints</em>.
-Further discussion
-of the semantics of PROV statements, which justifies the definitions, inferences
-and constraints, and relates the procedural specification approach
-taken here to a declarative specification, can be found in the formal semantics [<cite><a class="bibref" href="#bib-PROV-SEM">PROV-SEM</a></cite>].
-</p>
-
-<p>We define validity and equivalence in terms of a
-concept called <a title="normal form" href="#dfn-normal-form" class="internalDFN">normalization</a>. Definitions, inferences,
-and uniqueness constraints can be applied to <a title="normal
-form" href="#dfn-normal-form" class="internalDFN">normalize</a> PROV instances, and event ordering, typing, and
-impossibility constraints can be checked on the normal form to determine
-<a title="valid" href="#dfn-valid" class="internalDFN">validity</a>. Equivalence of two PROV
-instances can be determined by comparing their normal forms. For PROV
-documents, validity and equivalence amount to checking the validity or
-pairwise equivalence of their respective instances.
-</p>
-<p>
-This specification defines
-validity and equivalence procedurally, via an algorithm based on
-<a title="normal form" href="#dfn-normal-form" class="internalDFN">normalization</a>. Applications <span class="delete">may</span><em class="rfc2119" title="MAY"><span class="insert">MAY</span></em> implement
-validity and equivalence checking using normalization, as outlined
-here. Applications <span class="delete">may</span><em class="rfc2119" title="MAY"><span class="insert">MAY</span></em> also implement validation and equivalence
-checking in
-any other way as long as the same instances or documents are considered valid or
-equivalent, respectively.
-</p>
-
-<p> Checking validity or equivalence are <span class="delete">recommended</span><em class="rfc2119" title="RECOMMENDED"><span class="insert">RECOMMENDED</span></em>, but not required, for
-applications compliant with PROV.
-Applications producing provenance <span class="delete">should</span><em class="rfc2119" title="SHOULD"><span class="insert">SHOULD</span></em> ensure that it is
-<a href="#dfn-valid" class="internalDFN">valid</a>, and similarly applications consuming provenance <span class="delete">may</span><em class="rfc2119" title="MAY"><span class="insert">MAY</span></em> reject provenance that is not <a href="#dfn-valid" class="internalDFN">valid</a>. Applications
-that are determining whether PROV instances or documents convey the same
-information <span class="delete">should</span><em class="rfc2119" title="SHOULD"><span class="insert">SHOULD</span></em> check equivalence as specified here. As a
-guideline, applications should
-treat equivalent instances or documents in the same way. This is a
-guideline only, because meaning of "in the same way" is
-application-specific. For example, applications that manipulate the syntax of
-PROV instances in particular representations, such as pretty-printing
-or digital signing, have good reasons to treat syntactically
-different, but equivalent, documents differently.
-</p>
-</section>
-<section id="structure-of-this-document">
-<h3><span class="secno">1.3 </span>Structure of this document</h3>
-
-<p><a href="#rationale">Section 2</a> gives a brief rationale
-for the definitions, inferences and constraints.
-</p>
-<p>
-<a href="#compliance">Section 3</a> summarizes the
-requirements for compliance with this document, which are specified in
-detail in the rest of the document. </p>
-<p>
-<a href="#concepts">Section 4</a> defines basic concepts used in the
-rest of the specification. </p>
-
-<p> <a href="#inferences">Section 5</a> presents definitions and inferences. Definitions allow replacing shorthand notation in [<cite><a class="bibref" href="#bib-PROV-N">PROV-N</a></cite>]
-with more explicit and complete statements; inferences allow adding
-new facts representing implicit knowledge about the structure of
-provenance. </p>
-
-<p><a href="#constraints">Section 6</a> presents four kinds of constraints,
-<em>uniqueness</em> constraints that prescribe that certain statements
-must be unique within <a title="PROV instance" href="#instance" class="internalDFN">PROV instances</a>,
-<em>event ordering</em> constraints that require that the records in a
-<a href="#instance" class="internalDFN">PROV instance</a> are consistent with a sensible ordering of events
-relating the activities, entities and agents involved,
-<em>impossibility</em> constraints that forbid certain patterns of
-statements in valid PROV instances, and <em>type</em> constraints that
-classify the types of identifiers in valid PROV instances.
-</p>
-
-<p><a href="#normalization-validity-equivalence">Section 7</a> defines the notions
-of <a title="valid" href="#dfn-valid" class="internalDFN">validity</a>, <a title="equivalent" href="#dfn-equivalent" class="internalDFN">equivalence</a> and <a title="normal form" href="#dfn-normal-form" class="internalDFN">normalization</a>.
-</p>
-
-
-
-</section>
-<section id="audience">
-<h3><span class="secno">1.4 </span> Audience </h3>
-
-<p> The audience for this document is the same as for [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>]: developers
-and users who wish to create, process, share or integrate provenance
-records on the (Semantic) Web. Not all PROV-compliant applications
-need to perform inferences or check validity when processing provenance.
-However, applications that create or transform provenance <span class="delete">should</span><em class="rfc2119" title="SHOULD"><span class="insert">SHOULD</span></em>
-attempt to produce valid provenance, to make it more useful to other
-applications by ruling out nonsensical or inconsistent information.
-</p>
-
-<p>This document assumes familiarity with [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>] and employs the
-[<cite><a class="bibref" href="#bib-PROV-N">PROV-N</a></cite>] notation.
-</p>
-
-</section>
-</section>
-
-<section id="rationale" class="informative">
-<h2><span class="secno">2. </span>Rationale (Informative)</h2><p><em>This section is non-normative.</em></p>
-<p> This section gives a high-level rationale that provides some
- further background for the constraints, but does not affect the
-technical content of the rest of the specification.</p>
-
-<section class="informative" id="entities-activities-and-agents">
-<h3><span class="secno">2.1 </span>Entities, Activities and Agents</h3><p><em>This section is non-normative.</em></p>
-<p>
-One of the central challenges in representing provenance information
-is how to deal with change. Real-world objects, information objects
-and Web resources change over time, and the characteristics that make
-them identifiable in a given situation are sometimes subject to change
-as well. PROV allows for things to be described
-in different ways, with different descriptions of their
-state.
-</p>
-
-<p>
-An entity is a thing one wants to provide provenance for
-and whose situation in the world is described by some fixed
-attributes. An entity has a <dfn id="dfn-lifetime">lifetime</dfn>,
-defined as the period
-between its <a title="entity generation event" href="#dfn-generation-event" class="internalDFN">generation event</a>
-and its <a title="entity invalidation event" href="#dfn-invalidation-event" class="internalDFN">invalidation event</a>.
-An entity's attributes are established when the entity is
-created and (partially) describe the entity's situation and state
-during the entirety of the entity's lifetime.</p>
-
-<p>
-A different entity (perhaps representing a different user or
-system perspective) may fix other aspects of the same thing, and its provenance
-may be different. Different entities that fix aspects of the same
-thing are called <em>alternates</em>, and the PROV relations of
-<span class="name">specializationOf</span> and <span class="name">alternateOf</span> can be used to link such entities.</p>
-
-<p>Besides entities, a variety of other PROV objects and relationships carry
-attributes, including activity, generation, usage, invalidation, start, end,
-communication, attribution, association, delegation, and
-derivation. Each object has an associated duration interval (which may
-be a single time point), and attribute-value pairs for a given object
-are expected to be descriptions that hold for the object's duration.
-</p>
-<p>
-However, the attributes of entities have special meaning because they
-are considered to be fixed aspects
-of underlying, changing things. This motivates constraints on
-<span class="name">alternateOf</span> and <span class="name">specializationOf</span> relating the attribute values of
-different entities.
-</p>
-
-<p>
-In order to describe the provenance of something during an interval
- over which relevant attributes of the thing are not fixed, a PROV
- instance would describe multiple entities, each with its own
- identifier, <a href="#dfn-lifetime" class="internalDFN">lifetime</a>, and fixed attributes, and express dependencies between
- the various entities using <i><a title="instantaneous event" href="#dfn-event" class="internalDFN">events</a></i>. For example, in order to
- describe the provenance of several versions of a document, involving
- attributes such as authorship that change over time, one can use
- different entities for the versions linked by appropriate
- generation, usage, revision, and invalidation events.
-</p>
-
-<p>There is no assumption that the set of attributes listed in an
-<span class="name">entity</span> statement is complete, nor
-that the attributes are independent or orthogonal of each
-other. Similarly, there is no assumption that the attributes of an
-entity uniquely identify it. Two different entities that present the
-same aspects of possibly different things can have the same
-attributes; this leads to potential ambiguity, which is mitigated through the
-use of identifiers.</p>
-
-<p>An <span class="delete">activity</span><span class="delete">'s</span><span class="insert">activity's</span> lifetime is delimited by its <a title="activity start
-event" href="#dfn-start-event" class="internalDFN">start</a> and its <a title="activity end event" href="#dfn-end-event" class="internalDFN">end</a>
-events. It occurs over
-an interval delimited by two <a title="instantaneous event" href="#dfn-event" class="internalDFN">instantaneous
-events</a>. However, an activity statement need not mention start or end time information, because they may not be known.
-An activity's attribute-value pairs are expected to describe the activity's situation during its lifetime.
-</p>
-
-
-
-<p>An activity is not an entity. Indeed, an entity exists in full at
-any point in its lifetime, persists during this interval, and
-preserves the characteristics provided. In
-contrast, an activity is something that occurs, happens, unfolds, or
-develops through time. This
-distinction is similar to the distinction between 'continuant' and
-'occurrent' in logic [<cite><a class="bibref" href="#bib-Logic">Logic</a></cite>].</p>
-
-
-</section>
-<section class="informative" id="events">
-<h3><span class="secno">2.2 </span>Events</h3><p><em>This section is non-normative.</em></p>
-
-<p> Although time is important for provenance, provenance can be used
-in many different contexts within individual systems and across the
-Web. Different systems may use different clocks which may not be
-precisely synchronized, so when provenance statements are combined by
-different systems, an application may not be able to align the times involved to a
-single global timeline. Hence, PROV is designed to minimize
-assumptions about time. Instead, PROV talks about (identified)
-events. </p>
-
-<p>The PROV data model is implicitly based on a notion of <dfn id="dfn-event">instantaneous event</dfn>s (or just <a title="instantaneous event" href="#dfn-event" class="internalDFN">event</a>s), that mark
-transitions in the world. Events include generation, usage, or
-invalidation of entities, as well as start or end of activities. This
-notion of event is not first-class in the data model, but it is useful
-for explaining its other concepts and its semantics [<cite><a class="bibref" href="#bib-PROV-SEM">PROV-SEM</a></cite>].
-Thus, events help justify <i>inferences</i> on provenance as well as
-<i>validity</i> constraints indicating when provenance is
- self-consistent.
-
-
-
-</p><p>Five kinds of <a title="instantaneous event" href="#dfn-event" class="internalDFN">instantaneous
-events</a> are used in PROV. The <strong>activity start</strong>
-and <strong>activity end</strong> events delimit the beginning and the
-end of activities, respectively. The
-<strong>entity generation</strong>, <strong>entity usage</strong>, and <strong>entity
-invalidation</strong> events apply to entities, and the generation and
-invalidation events delimit the <a href="#dfn-lifetime" class="internalDFN">lifetime</a> of an entity. More
-precisely:
-</p>
-
-<p>An <dfn id="dfn-start-event">activity start event</dfn> is the <a title="instantaneous event" href="#dfn-event" class="internalDFN">instantaneous event</a> that marks the instant an activity starts.</p>
-
-<p>An <dfn id="dfn-end-event">activity end event</dfn> is the <a title="instantaneous event" href="#dfn-event" class="internalDFN">instantaneous event</a> that marks the instant an activity ends.</p>
-
-<p>An <dfn id="dfn-generation-event">entity generation event</dfn> is the <a title="instantaneous event" href="#dfn-event" class="internalDFN">instantaneous event</a> that marks the final instant of an entity's creation timespan, after which
-it is available for use. The entity did not exist before this event.</p>
-
-
-<p>An <dfn id="dfn-usage-event">entity usage event</dfn> is the <a title="instantaneous event" href="#dfn-event" class="internalDFN">instantaneous event</a> that marks the first instant of
-an entity's consumption timespan by an activity. The described usage
-had not started before this instant, although the activity could
-potentially have used the same entity at a different time.</p>
-
-
-<p>An <dfn id="dfn-invalidation-event">entity invalidation event</dfn>
-is the <a title="instantaneous event" href="#dfn-event" class="internalDFN">instantaneous event</a> that
-marks the initial instant of the destruction, invalidation, or
-cessation of an entity, after which the entity is no longer available
-for use. The entity no longer exists after this event.</p>
-
-</section>
-
-<section id="typing-section" class="informative">
-<h3><span class="secno">2.3 </span>Types</h3><p><em>This section is non-normative.</em></p>
-
-<p> As set out in other specifications, the identifiers used in PROV
-documents have associated type information. An identifier can have
-more than one type, reflecting subtyping or allowed overlap between
-types, and so we define a set of types of each identifier, <span class="name">typeOf(id)</span>. Some types are, however,
-required not to overlap (for example, no identifier can describe both
-an entity and an activity).
-In addition, an identifier cannot be used to identify both an object
-(that is, an entity, activity or agent) and a property (that is, a
-named event such as usage, generation, or a relationship such as
-attribution.)
-This specification includes <a href="#type-constraints">disjointness and typing constraints</a> that
-check these requirements. Here, we
-summarize the type constraints in <a href="#typing-table">Table 1</a>.
-</p>
-
-<div id="typing-table-fig">
- <table id="typing-table" border="1" class="thinborder" style="margin-left: auto; margin-right: auto; border-color: black;">
-<caption id="typing-table-caption">Table 1: Summary of Typing Constraints</caption>
- <tbody><tr>
- <th>In relation...</th>
- <th>identifier</th>
- <th>has type(s)...</th>
- </tr>
-
-<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
-
- <tr style="text-align: center; ">
- <td class="name">entity(e,attrs)</td>
- <td class="name" style="text-align: center; ">e</td>
- <td class="name">'entity'</td>
- </tr>
- <tr style="text-align: center; ">
- <td class="name">activity(a,t1,t2,attrs)</td>
- <td class="name">a</td>
- <td class="name">'activity'</td>
- </tr>
- <tr style="text-align: center; ">
- <td class="name">agent(ag,attrs)</td>
- <td class="name">ag</td>
- <td class="name">'agent'</td>
- </tr>
- <tr style="text-align: center; ">
- <td rowspan="2" class="name">used(id; a,e,t,attrs)</td>
- <td class="name">e</td>
- <td class="name">'entity'</td>
- </tr>
- <tr style="text-align: center; ">
- <td class="name">a</td>
- <td class="name">'activity'</td>
- </tr>
- <tr style="text-align: center; ">
- <td rowspan="2" class="name">wasGeneratedBy(id; e,a,t,attrs)</td>
- <td class="name">e</td>
- <td class="name">'entity'</td>
- </tr>
- <tr style="text-align: center; ">
- <td class="name">a</td>
- <td class="name">'activity'</td>
- </tr>
- <tr style="text-align: center; ">
- <td rowspan="2" class="name">wasInformedBy(id; a2,a1,attrs)</td>
- <td class="name">a2</td>
- <td class="name">'activity'</td>
- </tr>
- <tr style="text-align: center; ">
- <td class="name">a1</td>
- <td class="name">'activity'</td>
- </tr>
- <tr style="text-align: center; ">
- <td rowspan="3" class="name">wasStartedBy(id; a2,e,a1,t,attrs)</td>
- <td class="name">a2</td>
- <td class="name">'activity'</td>
- </tr>
- <tr style="text-align: center; ">
- <td class="name">e</td>
- <td class="name">'entity'</td>
- </tr>
- <tr style="text-align: center; ">
- <td class="name">a1</td>
- <td class="name">'activity'</td>
- </tr>
- <tr style="text-align: center; ">
- <td rowspan="3" class="name">wasEndedBy(id; a2,e,a1,t,attrs)</td>
- <td class="name">a2</td>
- <td class="name">'activity'</td>
- </tr>
- <tr style="text-align: center; ">
- <td class="name">e</td>
- <td class="name">'entity'</td>
- </tr>
- <tr style="text-align: center; ">
- <td class="name">a1</td>
- <td class="name">'activity'</td>
- </tr>
- <tr style="text-align: center; ">
- <td rowspan="2" class="name">wasInvalidatedBy(id; e,a,t,attrs)</td>
- <td class="name">e</td>
- <td class="name">'entity'</td>
- </tr>
- <tr style="text-align: center; ">
- <td class="name">a</td>
- <td class="name">'activity'</td>
- </tr>
- <tr style="text-align: center; ">
- <td rowspan="3" class="name">wasDerivedFrom(id; e2,e1,a,g,u,attrs)</td>
- <td class="name">e2</td>
- <td class="name">'entity'</td>
- </tr>
- <tr style="text-align: center; ">
- <td class="name">e1</td>
- <td class="name">'entity'</td>
- </tr>
- <tr style="text-align: center; ">
- <td class="name">a</td>
- <td class="name">'activity'</td>
- </tr>
- <tr style="text-align: center; ">
- <td rowspan="2" class="name">wasAttributedTo(id; e,ag,attr)</td>
- <td class="name">e</td>
- <td class="name">'entity'</td>
- </tr>
- <tr style="text-align: center; ">
- <td class="name">ag</td>
- <td class="name">'agent'</td>
- </tr>
- <tr style="text-align: center; ">
- <td rowspan="3" class="name">wasAssociatedWith(id; a,ag,pl,attrs)</td>
- <td class="name">a</td>
- <td class="name">'activity'</td>
- </tr>
- <tr style="text-align: center; ">
- <td class="name">ag</td>
- <td class="name">'agent'</td>
- </tr>
- <tr style="text-align: center; ">
- <td class="name">pl</td>
- <td class="name">'entity'</td>
- </tr>
- <tr style="text-align: center; ">
- <td rowspan="3" class="name">actedOnBehalfOf(id; ag2,ag1,a,attrs)</td>
- <td class="name">ag2</td>
- <td class="name">'agent'</td>
- </tr>
- <tr style="text-align: center; ">
- <td class="name">ag1</td>
- <td class="name">'agent'</td>
- </tr>
- <tr style="text-align: center; ">
- <td class="name">a</td>
- <td class="name">'activity'</td>
- </tr>
- <tr style="text-align: center; ">
- <td rowspan="2" class="name">alternateOf(e1,e2)</td>
- <td class="name">e1</td>
- <td class="name">'entity'</td>
- </tr>
- <tr style="text-align: center; ">
- <td class="name">e2</td>
- <td class="name">'entity'</td>
- </tr>
- <tr style="text-align: center; ">
- <td rowspan="2" class="name">specializationOf(e1,e2)</td>
- <td class="name">e1</td>
- <td class="name">'entity'</td>
- </tr>
- <tr style="text-align: center; ">
- <td class="name">e2</td>
- <td class="name">'entity'</td>
- </tr>
-
- <tr style="text-align: center; ">
- <td rowspan="2" class="name">hadMember(c,e)</td>
- <td class="name">c</td>
- <td class="name">'entity'<br> 'prov:Collection'</td>
- </tr>
- <tr style="text-align: center; ">
- <td class="name">e</td>
- <td class="name">'entity'</td>
- </tr>
- <tr style="text-align: center; ">
- <td class="name">entity(c,[prov:type='prov:EmptyCollection,...])</td>
- <td class="name">c</td>
- <td class="name">'entity'<br> 'prov:Collection' <br> 'prov:EmptyCollection'</td>
- </tr>
- </tbody></table>
- </div>
-
-</section>
-<section id="overview" class="informative">
-<h3><span class="secno">2.4 </span>Validation Process Overview</h3><p><em>This section is non-normative.</em></p>
-
-
- <p>
- This section collects common concepts and operations that are used
- throughout the specification, and relates them to background
- terminology and ideas from logic [<cite><a class="bibref" href="#bib-Logic">Logic</a></cite>], constraint programming
- [<cite><a class="bibref" href="#bib-CHR">CHR</a></cite>], and database constraints [<cite><a class="bibref" href="#bib-DBCONSTRAINTS">DBCONSTRAINTS</a></cite>]. This section
- does not attempt to provide a complete introduction to these topics,
- but it is provided in order to aid readers familiar with one or more
- of these topics in understanding the specification, and to clarify
- some of the motivations for choices in the specification to all
- readers.
- </p>
-
- <p>As discussed below, the definitions, inferences and constraints
-can be viewed as pure logical assertions that could be checked in a
-variety of ways. The rest of this document specifies validity and
-equivalence procedurally, that is, in terms of a reference
-implementation based on normalization. Although both declarative and
-procedural specification techniques have advantages, a purely
-declarative specification offers much less guidance for
-implementers, while the procedural approach adopted here immediately demonstrates
-implementability and provides an adequate (polynomial-time) default implementation. In
-this section we relate the declarative meaning of formulas to their
-procedural meaning. [<cite><a class="bibref" href="#bib-PROV-SEM">PROV-SEM</a></cite>] will provide an alternative,
-declarative characterization of validity and equivalence which could
-be used as a starting point for other implementation strategies. </p>
-
-
-
- <h3 id="constants-variables-and-placeholders">Constants, Variables and Placeholders</h3>
- <p>
- PROV statements involve identifiers, literals,
- placeholders, and attribute lists. Identifiers are, according to PROV-N, expressed as <a href="http://www.w3.org/TR/2013/PR-prov-n-20130312/#prod-QUALIFIED_NAME">qualified names</a> which can be mapped to URIs [<cite><a class="bibref" href="#bib-RFC3987">RFC3987</a></cite>].
- However, in order to specify
- constraints over PROV instances, we also need <em>variables</em>
- that represent unknown identifiers, literals, or placeholders.
- These variables are similar to those in first-order
- logic [<cite><a class="bibref" href="#bib-Logic">Logic</a></cite>]. A variable is a symbol that can be replaced by
- other symbols, including either other variables or constant
- identifiers, literals, or placeholders. In a few special cases, we
- also use variables for unknown attribute lists.
- To help distinguish identifiers and variables, we also term the former 'constant identifiers' to highlight their non-variable nature.
- </p>
-
- <p>Several definitions and inferences conclude by saying that some
- objects exist such that some other formulas hold. Such an inference
- introduces fresh <a href="#dfn-existential-variable" class="internalDFN">existential variable</a>s into the instance. An
- existential variable denotes a fixed object that exists, but its
- exact identity is unknown. Existential variables can stand for
- unknown identifiers or literal values only; we do not allow
- existential variables that stand for unknown attribute lists. </p>
-
- <p>In particular, many
- occurrences of the placeholder symbol <span class="name">-</span> stand for unknown
- objects; these are handled by expanding them to existential
- variables. Some placeholders, however, indicate the absence of an
- object, rather than an unknown object. In other words, the
- placeholder is overloaded, with different meanings in different
- places.
- </p>
- <p>An expression is called a <em>term</em> if it is either a
- constant identifier, literal, placeholder, or variable. We write
- <span class="math">t</span> to denote an arbitrary term.
-</p>
-
-
- <h4 id="substitution-1">Substitution</h4><p><em>This section is non-normative.</em></p>
-<p>A <em>substitution</em> is a function that maps variables to terms. Concretely, since we only
- need to consider substitutions of finite sets of variables, we can
- write substitutions as <span class="math">[x<sub>1</sub> = t<sub>1</sub>,...,x<sub>n</sub>=t<sub>n</sub>]</span>. A substitution
- <span class="math">S = [x<sub>1</sub> = t<sub>1</sub>,...,x<sub>n</sub>=t<sub>n</sub>]</span>
- can be <em>applied</em> to a term by replacing occurrences of
-<span class="math">x_i</span> with <span class="math">t_i</span>.
-</p>
-
- <p>
- In addition, a substitution can be applied to an atomic formula
- (PROV statement) <span class="math">p(t<sub>1</sub>,...,t<sub>n</sub>)</span> by applying it to each term,
- that is, <span class="math">S(p(t<sub>1</sub>,...,t<sub>n</sub>)) = p(S(t<sub>1</sub>),...,S(t<sub>n</sub>))</span>. Likewise, a
- substitution <span class="math">S</span> can be applied to an instance <span class="math">I</span> by applying
- it to each atomic formula (PROV statement) in <span class="math">I</span>, that is, <span class="math">S(I)
- = {S(A) | A ∈ I}</span>.
-</p>
-
-
-
-
-
- <h4 id="formulas">Formulas</h4>
- <p>
- For the purpose of constraint checking, we view PROV statements
- (possibly involving existential variables) as
- <dfn id="formula">formulas</dfn>. An instance is analogous to a "theory" in
- logic, that is, a set of formulas all thought to describe the same
- situation. The set can also be thought of a single, large formula:
- the conjunction of all of the atomic formulas.
- </p>
-<p>The atomic constraints considered in this specification can be
- viewed as atomic formulas:</p>
-<ul>
- <li>Uniqueness constraints employ atomic equational formulas <span class="math">t =
- t'</span>.</li>
- <li>Ordering constraints employ atomic precedence relations that can
- be thought of as binary formulas <span class="math">precedes(t,t')</span> or <span class="math">strictly_precedes(t,t')</span>
- </li>
- <li>Typing constraints <span class="name">'type' ∈ typeOf(id)</span>
- can be represented as a atomic formulas <span class="name">typeOf(id,'type')</span>.
- </li>
- <li>Impossibility constraints employ the conclusion <span class="name">INVALID</span>,
- which is equivalent to the logical constant <span class="math">False</span>. </li>
- </ul>
- <p> Similarly, the definitions, inferences, and constraint rules in this
- specification can also be viewed as logical formulas, built up out
- of atomic formulas, logical connectives "and" (∧), "implies" (⇒),
- and quantifiers "for all" (∀) and "there exists" (∃). For more
- background on logical formulas, see a logic textbook such as [<cite><a class="bibref" href="#bib-Logic">Logic</a></cite>].</p>
-<ul>
- <li>
- A definition of the form <span class="name">A</span> <span class="conditional">IF AND ONLY IF</span> there
- exists <span class="name">y<sub>1</sub></span>...<span class="name">y<sub>m</sub></span> such that <span class="name">B<sub>1</sub></span> and ... and <span class="name">B<sub>k</sub></span>
- can be thought of as a formula <span class="math">∀ x<sub>1</sub>,....,x<sub>n</sub>. A ⇔ ∃ y<sub>1</sub>...y<sub>m</sub> . B<sub>1</sub> ∧ ... ∧ B<sub>k</sub></span>, where <span class="math">x<sub>1</sub></span>...<span class="math">x<sub>n</sub></span> are the
- free variables of the definition.
-</li>
-<li>An inference of the form <span class="conditional">IF</span> <span class="name">A<sub>1</sub></span> and ... and <span class="name">A<sub>p</sub></span> <span class="conditional">THEN</span> there
- exists <span class="name">y<sub>1</sub></span>...<span class="name">y<sub>m</sub></span> such that <span class="name">B<sub>1</sub></span> and ... and <span class="name">B<sub>k</sub></span> can
- be thought of as a formula <span class="math">∀ x<sub>1</sub>,....,x<sub>n</sub>. A<sub>1</sub> ∧ ... ∧ A<sub>p</sub> ⇒ ∃ y<sub>1</sub>...y<sub>m</sub> . B<sub>1</sub> ∧ ... ∧ B<sub>k</sub></span>, where <span class="math">x<sub>1</sub></span>...<span class="math">x<sub>n</sub></span> are the
- free variables of the inference.
-</li>
-<li>A uniqueness, ordering, or typing constraint of the form <span class="conditional">IF</span> <span class="name">A<sub>1</sub> ∧ ... ∧ A<sub>p</sub></span> <span class="conditional">THEN</span> <span class="name">C</span> can be viewed as a formula
- <span class="math">∀ x<sub>1</sub>...x<sub>n</sub>. A<sub>1</sub> ∧ ... ∧ A<sub>p</sub> ⇒ C</span>. </li>
-<li>A constraint of the form <span class="conditional">IF</span> <span class="name">A<sub>1</sub> ∧ ... ∧ A<sub>p</sub></span> <span class="conditional">THEN INVALID</span> can be viewed as a formula
- <span class="math">∀ x<sub>1</sub>...x<sub>n</sub>. A<sub>1</sub> ∧ ... ∧ A<sub>p</sub> ⇒ False</span>. </li>
- </ul>
-
-
- <h4 id="satisfying-definitions-inferences-and-constraints">Satisfying definitions, inferences, and constraints</h4>
- <p>
- In logic, a formula's meaning is defined by saying when it is
- <em>satisfied</em>. We can view
- definitions, inferences, and constraints as being satisfied or not
- satisfied in a PROV instance, augmented with information about the constraints.
- </p>
- <ol>
- <li>A logical equivalence as used in a definition is satisfied
- when the formula <span class="math">∀
- x<sub>1</sub>,....,x<sub>n</sub>. A ⇔ ∃
- y<sub>1</sub>...y<sub>m</sub> . B<sub>1</sub> ∧ ... ∧
- B<sub>k</sub></span> holds, that is, for any substitution of the
- variables <span class="math">x<sub>1</sub>,....,x<sub>n</sub></span>, formula <span class="math">A</span> and
- formula <span class="math">∃
- y<sub>1</sub>...y<sub>m</sub>. B<sub>1</sub> ∧ ... ∧
- B<sub>k</sub></span> are either both true or both false.
- </li>
- <li>A logical implication as used in an inference is
- satisfied with the formula <span class="math">∀
- x<sub>1</sub>,....,x<sub>n</sub>. A<sub>1</sub> ∧ ... ∧
- A<sub>p</sub> ⇒ ∃ y<sub>1</sub>...y<sub>m</sub> . B<sub>1</sub> ∧
- ... ∧ B<sub>k</sub></span> holds, that is, for any substitution of
- the variables <span class="math">x<sub>1</sub>,....,x<sub>n</sub></span>, if <span class="math">A<sub>1</sub> ∧ ... ∧
- A<sub>p</sub></span> is true, then
- for some further substitution of terms for variables <span class="math">
- y<sub>1</sub>...y<sub>m</sub></span>, formula <span class="math">B<sub>1</sub> ∧ ... ∧
- B<sub>k</sub></span> is also true.</li>
- <li>A uniqueness, ordering, or typing constraint is satisfied when
- its associated formula <span class="math">∀ x<sub>1</sub>...x<sub>n</sub>. A<sub>1</sub> ∧ ... ∧ A<sub>p</sub> ⇒ C</span> holds, that is, for any substitution of
- the variables <span class="math">x<sub>1</sub>,....,x<sub>n</sub></span>, if <span class="math">A<sub>1</sub> ∧ ... ∧
- A<sub>p</sub></span> is true, then <span class="math">C</span> is
- also true.</li>
- <li>An impossibility constraint is satisfied when the formula
- <span class="math">∀ x<sub>1</sub>...x<sub>n</sub>. A<sub>1</sub> ∧ ... ∧ A<sub>p</sub> ⇒
- False</span> holds. This is logically equivalent to <span class="math">∄
- x<sub>1</sub>...x<sub>n</sub>. A<sub>1</sub> ∧ ... ∧ A<sub>p</sub></span>, that is, there exists no
- substitution for <span class="math">x<sub>1</sub>...x<sub>n</sub></span> making <span class="math">A<sub>1</sub> ∧ ... ∧ A<sub>p</sub></span> true.
-</li></ol>
-
-<h4 id="unification-and-merging">Unification and Merging</h4>
-
- <p><em>Unification</em> is an operation that takes two terms and compares them to
- determine whether they can be made equal by substituting an
- existential variable with another term. If so, the result is such a
- substitution; otherwise, the result is failure. Unification is an
- essential concept in logic programming and automated reasoning,
-where terms can involve variables, constants and function symbols. In PROV,
- by comparison, unification only needs to deal with variables,
- constants and literals.
-</p>
-<p>
-Unifying two terms <span class="math">t,t'</span> results in either substitution <span class="math">S</span>
- such that <span class="math">S(t) = S(t')</span>, or failure indicating that there is no
- substitution that can be applied to both <span class="math">t</span> and <span class="math">t'</span> to make
- them equal. Unification is also used to define an operation on PROV
- statements called <em>merging</em>. Merging takes two statements
- that have equal identifiers, unifies their corresponding term
- arguments, and combines their attribute lists.
-</p>
-
-
-
- <h4 id="applying-definitions-inferences-and-constraints">Applying definitions, inferences, and constraints</h4>
-<p>Formulas can also be interpreted as having computational
- content. That is, if an instance does not satisfy a formula, we can
- often <em>apply</em> the formula to the instance to produce another
- instance that does satisfy the formula. Definitions, inferences,
- and uniqueness constraints can be applied to instances:
-</p>
- <ul>
- <li>
- A definition of the form <span class="math">∀
- x<sub>1</sub>,....,x<sub>n</sub>. A ⇔ ∃
- y<sub>1</sub>...y<sub>m</sub> . B<sub>1</sub> ∧ ... ∧
- B<sub>k</sub></span>
- can be applied by searching for any occurrences of <span class="math">A</span> in the instance and adding <span class="math"> B<sub>1</sub>, ..., B<sub>k</sub></span>, generating fresh existential
- variables <span class="math">y<sub>1</sub>,...,y<sub>m</sub></span>, and conversely, whenever there is an
- occurrence of <span class="math"> B<sub>1</sub>, ..., B<sub>k</sub></span>, adding
- <span class="math">A</span>.
- In our setting, the defined formulas <span class="math">A</span> are never used in other
- formulas, so it is sufficient to replace all occurrences of
- <span class="math">A</span> with their definitions. The formula <span class="math">A</span> is then redundant, and can be
- removed from the instance.
-</li>
-<li>An inference of the form <span class="math">∀
- x<sub>1</sub>,....,x<sub>n</sub>. A<sub>1</sub> ∧ ... ∧
- A<sub>p</sub> ⇒ ∃ y<sub>1</sub>...y<sub>m</sub> . B<sub>1</sub> ∧
- ... ∧ B<sub>k</sub></span> can be applied by searching for any occurrences of <span class="math"> A<sub>1</sub> ∧ ... ∧
- A<sub>p</sub></span> in the instance and, for each such match,
-for which the entire conclusion does not already hold (for some <span class="math">y<sub>1</sub>,...,y<sub>m</sub></span>),
-adding <span class="math">B<sub>1</sub> ∧
- ... ∧ B<sub>k</sub></span> to the instance, generating fresh existential
- variables <span class="math">y<sub>1</sub>,...,y<sub>m</sub></span>.
-</li>
-<li>A uniqueness constraint of the form <span class="math">∀
-x<sub>1</sub>...x<sub>n</sub>. A<sub>1</sub> ∧ ... ∧ A<sub>p</sub> ⇒ t
-= t'</span> can be
- applied by searching for an occurrence <span class="math">A<sub>1</sub> ∧ ... ∧ A<sub>p</sub></span> in the instance, and
- if one is found, unifying the terms <span class="math">t</span> and
-<span class="math">t'</span>. If successful, the resulting
-substitution is applied to the instance; otherwise, the application
-of the uniqueness constraint fails. </li>
-<li>A key constraint can similarly be applied by searching for
-different occurrences of a statement with the same identifier, unifying the
-corresponding parameters of the statements, and concatenating their
-attribute lists, to form a single statement. The substitutions obtained by unification are applied to
-the merged statement and the rest of the instance.
-</li>
- </ul>
-
- <p>As noted above, uniqueness or key constraint
- application can <em>fail</em>, if a required unification or merging step fails. Failure of constraint
- application means that there is no way to add information to the
- instance to satisfy the constraint, which in turn implies that the
- instance is <em>invalid</em>.
- </p>
- <p>
- The process of applying definitions, inferences, and constraints
- to a PROV instance until all of them are satisfied is similar to
- what is sometimes
- called <em>chasing</em> [<cite><a class="bibref" href="#bib-DBCONSTRAINTS">DBCONSTRAINTS</a></cite>] or <em>saturation</em>
- [<cite><a class="bibref" href="#bib-CHR">CHR</a></cite>]. We call this process <em>normalization</em>.
- </p>
- <p>
- Although this specification outlines one particular way of
- performing inferences and checking constraints, based on
- normalization, implementations can use any other equivalent
- algorithm. The logical formulas corresponding to the definitions,
- inferences, and constraints outlined above (and further elaborated
- in [<cite><a class="bibref" href="#bib-PROV-SEM">PROV-SEM</a></cite>]) provides an equivalent specification, and any
- implementation that correctly checks validity and equivalence (whether it performs normalization or not) complies
- with this specification.
- </p>
-
-
- <h4 id="termination-1">Termination</h4>
- <p>
- In general, applying sets of logical formulas of the above
- definition, inference, and constraint forms is not guaranteed to
- terminate. A simple example is the inference <span class="math">R(x,y) ⇒ ∃z. R(x,z)
- ∧R(z,y)</span>, which can be applied to <span class="math">{R(a,b)}</span> to generate an
- infinite sequence of larger and larger instances. To ensure that
- normalization, validity, and equivalence are decidable, we require
- that normalization terminates. There is a great deal of work on termination of the chase in
- databases, or of sets of constraint handling rules. The termination
- of the notion of normalization defined in this specification is
- guaranteed because the definitions, inferences and uniqueness/key
- constraints correspond to a <em>weakly acyclic</em> set of
- tuple-generating and equality-generating dependencies, in the
- terminology of [<cite><a class="bibref" href="#bib-DBCONSTRAINTS">DBCONSTRAINTS</a></cite>]. The termination of the remaining
- ordering, typing, and impossibility constraints is easy to show. <a href="#termination">Appendix
- A</a> gives a proof that the definitions, inferences, and uniqueness
- and key constraints are weakly acyclic and therefore terminating.
- </p>
- <p>
- There is an important subtlety that is essential to guarantee
- termination. This specification draws a distinction between knowing
- that an identifier has type <span class="name">'entity'</span>, <span class="name">'activity'</span>, or <span class="name">'agent'</span>, and having
- an explicit <span class="name">entity(id)</span>, <span class="name">activity(id)</span>, or <span class="name">agent(id)</span> statement in the instance.
- For example, focusing on entity statements, we can infer <span class="name">'entity' ∈ typeOf(id)</span> if <span class="name">entity(id)</span> holds in the instance. In contrast, if we only know
- that <span class="name">'entity' ∈ typeOf(id)</span>, this does not imply that <span class="name">entity(id)</span>
- holds.
- </p>
- <p>
- This distinction (for both entities and activities) is essential to
- ensure termination of the inferences, because we allow inferring
- that a declared <span class="name">entity(id,attrs)</span> has a generation
- and invalidation event, using
- <a class="rule-text" href="#entity-generation-invalidation-inference_text"><span>Inference 7 (entity-generation-invalidation-inference)</span></a>.
- Likewise, for activities, we allow inferring that a declared <span class="name">activity(id,t1,t2,attrs)</span> has a generation
- and invalidation event, using
- <a class="rule-text" href="#activity-start-end-inference_text"><span>Inference 8 (activity-start-end-inference)</span></a>. These
- inferences do not apply to identifiers whose types are known, but for
- which there is not an explicit entity or activity statement.
-If we strengthened the type
- inference constraints to add new entity or activity statements for
- the entities and activities involved in generating or starting other
- declared entities or activities, then we could keep generating new entities and
- activities in an unbounded chain into the past (as in the "chicken
- and egg" paradox). The
- design adopted here requires that instances explicitly declare the
- entities and activities that are relevant for validity checking, and only
- these can be inferred to have invalidation/generation and start/end events. This inference
- is not supported for identifiers
-that are indirectly referenced in other relations and therefore have
- type <span class="name">'entity'</span> or <span class="name">'activity'</span>.
- </p>
-
-
-<div style="text-align: center;">
-<span class="figure" id="fig-figure-1-overview-of-the-validation-process">
-<img src="images/constraints/prov-c.graffle.svg/overview.svg" alt="validation process overview">
-<br>
-<span class="figcaption" id="validation-process-overview">Figure 1<sup><a class="internalDFN" href="#validation-process-overview"><span class="diamond"> ◊:</span></a></sup> Overview of the Validation Process</span>
-</span>
-</div>
-
-
- <h4 id="checking-ordering-typing-and-impossibility-constraints">Checking ordering, typing, and impossibility constraints</h4>
- <p>
- The ordering, typing, and impossibility constraints are checked
- rather than applied. This means that they do not generate new
- formulas expressible in PROV, but they do generate basic constraints
- that might or might not be consistent with each other. Checking
- such constraints follows a saturation strategy similar to that for normalization:
- </p>
- <ol>
- <li><p>
- For ordering constraints, we check by generating all of the
- precedes and strictly-precedes relationships specified by the rules. These can be thought
- of as a directed graph whose nodes are terms, and whose edges are
- precedes or strictly-precedes relationships.
- An ordering constraint of the form <span class="math">∀
-x<sub>1</sub>...x<sub>n</sub>. A<sub>1</sub> ∧ ... ∧ A<sub>p</sub> ⇒
-precedes(t,t')</span> can be applied by searching for occurrences of
-<span class="math"> A<sub>1</sub> ∧ ... ∧ A<sub>p</sub></span> and for each such match
-adding the atomic formula <span class="math">precedes(t,t')</span> to
- the instance, and similarly for strictly-precedes constraints. After all such constraints have been checked, and the
- resulting edges added to the graph, the ordering constraints are
- violated if there is a cycle in the graph that includes a
- strictly-precedes edge, and satisfied otherwise.
- </p>
-</li>
-<li><p>For typing constraints, we check by constructing a function
- <span class="math">typeOf(id)</span> mapping identifiers to sets of possible types. We
- start with a function mapping each identifier to the empty set,
- reflecting no constraints on the identifiers' types. A typing
- constraint of the form <span class="math">∀
-x<sub>1</sub>...x<sub>n</sub>. A<sub>1</sub> ∧ ... ∧ A<sub>p</sub> ⇒ 'type' ∈ typeOf(id)
-</span> is checked by adjusting the
- function by adding <span class="name">'type'</span> to <span class="math">typeOf(id)</span> for each conclusion
- <span class="name">'type' ∈ typeOf(id)</span> of the rule. Typing constraints with
- multiple conclusions are handled analogously. Once all constraints
- have been checked in all possible ways, we check that the
- disjointness constraints hold of the resulting <span class="math">typeOf</span> function.
- (These are essentially impossibility constraints).
-</p>
- </li>
- <li><p>For impossibility constraints, we check by searching for the
- forbidden pattern that the impossibility constraint describes. Any
- match of this pattern leads to failure of the constraint checking process.
-An impossibility constraint of the form <span class="math">∀
-x<sub>1</sub>...x<sub>n</sub>. A<sub>1</sub> ∧ ... ∧ A<sub>p</sub> ⇒
-False</span> can be applied by searching for occurrences of
-<span class="math">A<sub>1</sub> ∧ ... ∧ A<sub>p</sub></span> in the instance, and if any
-such occurrence is found, signaling failure.</p>
- </li>
- </ol>
- <p>
- A normalized instance that passes all of the ordering, typing,
- and impossibility constraint checks
- is called <a href="#dfn-valid" class="internalDFN">valid</a>. Validity can be, but is not required to be,
- checked by normalizing and then checking constraints. Any other
- algorithm that provides equivalent behavior (that is, accepts the
- same valid instances and rejects the same invalid instances) is allowed.
- In particular, the checked constraints and the
- applied definitions, inferences and uniqueness constraints do not
- interfere with one another, so it is also possible to mix checking
- and application. This may be desirable in order to detect
- invalidity more quickly.
- </p>
-
-
-
- <h4 id="equivalence-and-isomorphism">Equivalence and Isomorphism</h4>
- <p> Given two normal forms, a natural question is whether they contain
- the same information, that is, whether they are equivalent (if so,
- then the original instances are also equivalent.) By analogy with
- logic, if we consider normalized PROV instances with existential
- variables to represent sets of possible situations, then two normal
- forms may describe the same situation but differ in inessential
- details such as the order of statements or of elements of
- attribute-value lists. To remedy this, we can easily consider
- instances to be equivalent up to reordering of attributes. However,
- instances can also be equivalent if they differ only in choice of
- names of existential variables. Because of this, the appropriate
- notion of equivalence of normal forms is <em>isomorphism</em>. Two
- instances <span class="math">I<sub>1</sub></span> and <span class="math">I<sub>2</sub></span> are <em>isomorphic</em> if there is an invertible
- substitution <span class="math">S</span> mapping existential variables to existential variables such that <span class="math">S(I<sub>1</sub>) = I<sub>2</sub></span>.
-
- </p>
-
-<p>Equivalence can be checked by normalizing instances, checking that
- both instances are valid, then
- testing whether the two normal forms are isomorphic. (It is
- technically possible for two invalid normal forms to be isomorphic,
- but to be considered equivalent, the two instances must also be
- valid.)
-As with validity, the algorithm suggested by this specification is
- just one of many possible ways to implement equivalence checking; it
- is not required that implementations compute normal forms
- explicitly, only that their determinations of equivalence match
- those obtained by the algorithm in this specification.
- </p>
-
-<p>Equivalence is only explicitly specified for
-valid instances (whose normal forms exist and are unique up to
-isomorphism). Implementations may test equivalences involving valid
-and invalid documents. This specification does not constrain the
-behavior of equivalence checking involving invalid instances, provided
-that:
-</p>
-<ul>
- <li>instance equivalence is <a href="#dfn-reflexive" class="internalDFN">reflexive</a>, <a href="#dfn-symmetric" class="internalDFN">symmetric</a> and
- <a href="#dfn-transitive" class="internalDFN">transitive</a> on all instances</li>
- <li> no valid instance is equivalent to an invalid instance.</li>
- </ul>
-<p>
-Because of the second constraint, equivalence is essentially the union
- of two equivalence relations on the disjoint sets of valid and
- invalid instances.
- There are two simple implementations of equivalence for invalid
- documents that are correct:</p>
- <ol>
- <li>each invalid instance is equivalent only to itself</li>
- <li>every pair of invalid instances are equivalent</li>
- </ol>
-
-<h4 id="from-instances-to-bundles-and-documents">From Instances to Bundles and Documents</h4>
-
-<p>PROV documents can contain multiple instances: a <a href="#dfn-toplevel-instance" class="internalDFN">toplevel
-instance</a>, and
-zero or more additional, named instances called <span class="delete">bundle</span><span class="delete">s.</span><a title="bundle" href="#dfn-bundle" class="internalDFN"><span class="insert">bundles</span></a><span class="insert">.</span> For the purpose
-of inference and constraint checking, these instances are treated independently. That is,
-a PROV document is valid provided that each instance in it is valid
-and the names of its bundles are distinct. In other words, there are
-no validity constraints that need to be checked across the different
-instances in a PROV document; the contents of one instance in a
-multi-instance PROV document cannot affect the validity of another instance.
-Similarly, a PROV document is
-equivalent to another if their toplevel instances are equivalent, they
-have the same number of bundles with the same names, and the instances
-of their corresponding bundles are equivalent.
-
-The scope of an existential variable in PROV is delimited at the instance
-<span class="delete">level, so</span><span class="insert">level. This means that occurrences of existential variables with the
- same name appearing in different statements within the same
- instance stand for a common, unknown term. However,</span> existential variables with the same name occurring in
-different instances do not necessarily denote the same term. This
-is a consequence of the fact that the instances of two equivalent
-documents only need to be pairwise isomorphic; this is a weaker
-property than requiring that there be a single isomorphism that works
-for all of the corresponding instances.
-</p>
-</section>
-
-<section class="informative" id="summary-of-inferences-and-constraints">
-<h3><span class="secno">2.5 </span>Summary of inferences and constraints</h3><p><em>This section is non-normative.</em></p>
-
-<p><a href="">Table 2</a> summarizes the inferences, and
-constraints specified in this document, broken down by component and
-type or relation involved.
-</p>
-
-
-
-<div id="prov-constraints-fig" style="text-align: left;">
-<table class="thinborder" style="margin-left: auto; margin-right: auto; border-color: black;">
-<caption id="prov-constraints">Table 2: Summary of inferences and constraints for PROV Types and Relations</caption>
-<tbody><tr><td><b>Type or Relation Name</b></td><td><b>
- Inferences and Constraints</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">Entity</td>
- <td><a class="rule-text" href="#entity-generation-invalidation-inference_text"><span>Inference 7 (entity-generation-invalidation-inference)</span></a><br>
- <a class="rule-text" href="#specialization-attributes-inference_text"><span>Inference 21 (specialization-attributes-inference)</span></a><br>
- <a class="rule-text" href="#key-object_text"><span>Constraint 22 (key-object)</span></a><br>
- <a class="rule-text" href="#impossible-object-property-overlap_text"><span>Constraint 54 (impossible-object-property-overlap)</span></a><br>
- <a class="rule-text" href="#entity-activity-disjoint_text"><span>Constraint 55 (entity-activity-disjoint)</span></a><br>
- </td>
- <td rowspan="8" style="text-align: center; "><a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#component1" title="Component 1: Entities/Activities">1</a></td>
-</tr>
-<tr class="component1-color">
- <td class="essential">Activity</td>
- <td><a class="rule-text" href="#activity-start-end-inference_text"><span>Inference 8 (activity-start-end-inference)</span></a><br>
- <a class="rule-text" href="#key-object_text"><span>Constraint 22 (key-object)</span></a><br>
- <a class="rule-text" href="#unique-startTime_text"><span>Constraint 28 (unique-startTime)</span></a><br>
- <a class="rule-text" href="#unique-endTime_text"><span>Constraint 29 (unique-endTime)</span></a><br>
- <a class="rule-text" href="#impossible-object-property-overlap_text"><span>Constraint 54 (impossible-object-property-overlap)</span></a><br>
- <a class="rule-text" href="#entity-activity-disjoint_text"><span>Constraint 55 (entity-activity-disjoint)</span></a><br>
- </td>
-</tr>
-<tr class="component1-color">
- <td class="essential">Generation</td>
- <td><a class="rule-text" href="#generation-use-communication-inference_text"><span>Inference 6 (generation-use-communication-inference)</span></a><br>
-
- <a class="rule-text" href="#influence-inference_text"><span>Inference 15 (influence-inference)</span></a><br>
- <a class="rule-text" href="#key-properties_text"><span>Constraint 23 (key-properties)</span></a><br>
- <a class="rule-text" href="#unique-generation_text"><span>Constraint 24 (unique-generation)</span></a><br>
- <a class="rule-text" href="#generation-within-activity_text"><span>Constraint 34 (generation-within-activity)</span></a><br>
- <a class="rule-text" href="#generation-precedes-invalidation_text"><span>Constraint 36 (generation-precedes-invalidation)</span></a><br>
- <a class="rule-text" href="#generation-precedes-usage_text"><span>Constraint 37 (generation-precedes-usage)</span></a><br>
- <a class="rule-text" href="#generation-generation-ordering_text"><span>Constraint 39 (generation-generation-ordering)</span></a><br>
- <a class="rule-text" href="#derivation-usage-generation-ordering_text"><span>Constraint 41 (derivation-usage-generation-ordering)</span></a><br>
- <a class="rule-text" href="#derivation-generation-generation-ordering_text"><span>Constraint 42 (derivation-generation-generation-ordering)</span></a><br>
- <a class="rule-text" href="#wasStartedBy-ordering_text"><span>Constraint 43 (wasStartedBy-ordering)</span></a><br>
- <a class="rule-text" href="#wasEndedBy-ordering_text"><span>Constraint 44 (wasEndedBy-ordering)</span></a><br>
- <a class="rule-text" href="#specialization-generation-ordering_text"><span>Constraint 45 (specialization-generation-ordering)</span></a><br>
- <a class="rule-text" href="#wasAssociatedWith-ordering_text"><span>Constraint 47 (wasAssociatedWith-ordering)</span></a><br>
- <a class="rule-text" href="#wasAttributedTo-ordering_text"><span>Constraint 48 (wasAttributedTo-ordering)</span></a><br>
- <a class="rule-text" href="#actedOnBehalfOf-ordering_text"><span>Constraint 49 (actedOnBehalfOf-ordering)</span></a><br>
- <a class="rule-text" href="#impossible-property-overlap_text"><span>Constraint 53 (impossible-property-overlap)</span></a><br>
- <a class="rule-text" href="#typing_text"><span>Constraint 50 (typing)</span></a><br>
- </td>
-</tr>
-<tr class="component1-color">
- <td class="essential">Usage</td>
- <td><a class="rule-text" href="#generation-use-communication-inference_text"><span>Inference 6 (generation-use-communication-inference)</span></a><br>
- <a class="rule-text" href="#influence-inference_text"><span>Inference 15 (influence-inference)</span></a><br>
- <a class="rule-text" href="#key-properties_text"><span>Constraint 23 (key-properties)</span></a><br>
- <a class="rule-text" href="#usage-within-activity_text"><span>Constraint 33 (usage-within-activity)</span></a><br>
- <a class="rule-text" href="#generation-precedes-usage_text"><span>Constraint 37 (generation-precedes-usage)</span></a><br>
- <a class="rule-text" href="#usage-precedes-invalidation_text"><span>Constraint 38 (usage-precedes-invalidation)</span></a><br>
- <a class="rule-text" href="#derivation-usage-generation-ordering_text"><span>Constraint 41 (derivation-usage-generation-ordering)</span></a><br>
- <a class="rule-text" href="#impossible-property-overlap_text"><span>Constraint 53 (impossible-property-overlap)</span></a><br>
- <a class="rule-text" href="#typing_text"><span>Constraint 50 (typing)</span></a><br>
- </td>
-</tr>
-<tr class="component1-color">
- <td class="essential">Communication</td>
- <td><a class="rule-text" href="#communication-generation-use-inference_text"><span>Inference 5 (communication-generation-use-inference)</span></a><br>
- <a class="rule-text" href="#influence-inference_text"><span>Inference 15 (influence-inference)</span></a><br>
- <a class="rule-text" href="#key-properties_text"><span>Constraint 23 (key-properties)</span></a><br>
- <a class="rule-text" href="#wasInformedBy-ordering_text"><span>Constraint 35 (wasInformedBy-ordering)</span></a><br>
- <a class="rule-text" href="#impossible-property-overlap_text"><span>Constraint 53 (impossible-property-overlap)</span></a><br>
- <a class="rule-text" href="#typing_text"><span>Constraint 50 (typing)</span></a><br>
- </td>
-</tr>
-<tr class="component1-color">
- <td class="essential">Start</td>
- <td><a class="rule-text" href="#wasStartedBy-inference_text"><span>Inference 9 (wasStartedBy-inference)</span></a><br>
- <a class="rule-text" href="#influence-inference_text"><span>Inference 15 (influence-inference)</span></a><br>
- <a class="rule-text" href="#key-properties_text"><span>Constraint 23 (key-properties)</span></a><br>
- <a class="rule-text" href="#unique-wasStartedBy_text"><span>Constraint 26 (unique-wasStartedBy)</span></a><br>
- <a class="rule-text" href="#unique-startTime_text"><span>Constraint 28 (unique-startTime)</span></a><br>
- <a class="rule-text" href="#start-precedes-end_text"><span>Constraint 30 (start-precedes-end)</span></a><br>
- <a class="rule-text" href="#usage-within-activity_text"><span>Constraint 33 (usage-within-activity)</span></a><br>
- <a class="rule-text" href="#generation-within-activity_text"><span>Constraint 34 (generation-within-activity)</span></a><br>
- <a class="rule-text" href="#wasInformedBy-ordering_text"><span>Constraint 35 (wasInformedBy-ordering)</span></a><br>
- <a class="rule-text" href="#start-start-ordering_text"><span>Constraint 31 (start-start-ordering)</span></a><br>
- <a class="rule-text" href="#wasStartedBy-ordering_text"><span>Constraint 43 (wasStartedBy-ordering)</span></a><br>
- <a class="rule-text" href="#wasAssociatedWith-ordering_text"><span>Constraint 47 (wasAssociatedWith-ordering)</span></a><br>
- <a class="rule-text" href="#impossible-property-overlap_text"><span>Constraint 53 (impossible-property-overlap)</span></a><br>
- <a class="rule-text" href="#typing_text"><span>Constraint 50 (typing)</span></a><br>
- </td>
-</tr>
-<tr class="component1-color">
- <td class="essential">End</td>
- <td><a class="rule-text" href="#wasEndedBy-inference_text"><span>Inference 10 (wasEndedBy-inference)</span></a><br>
- <a class="rule-text" href="#influence-inference_text"><span>Inference 15 (influence-inference)</span></a><br>
- <a class="rule-text" href="#key-properties_text"><span>Constraint 23 (key-properties)</span></a><br>
- <a class="rule-text" href="#unique-wasEndedBy_text"><span>Constraint 27 (unique-wasEndedBy)</span></a><br>
- <a class="rule-text" href="#unique-endTime_text"><span>Constraint 29 (unique-endTime)</span></a><br>
- <a class="rule-text" href="#start-precedes-end_text"><span>Constraint 30 (start-precedes-end)</span></a><br>
- <a class="rule-text" href="#usage-within-activity_text"><span>Constraint 33 (usage-within-activity)</span></a><br>
- <a class="rule-text" href="#generation-within-activity_text"><span>Constraint 34 (generation-within-activity)</span></a><br>
- <a class="rule-text" href="#wasInformedBy-ordering_text"><span>Constraint 35 (wasInformedBy-ordering)</span></a><br>
- <a class="rule-text" href="#end-end-ordering_text"><span>Constraint 32 (end-end-ordering)</span></a><br>
- <a class="rule-text" href="#wasEndedBy-ordering_text"><span>Constraint 44 (wasEndedBy-ordering)</span></a><br>
- <a class="rule-text" href="#wasAssociatedWith-ordering_text"><span>Constraint 47 (wasAssociatedWith-ordering)</span></a><br>
- <a class="rule-text" href="#impossible-property-overlap_text"><span>Constraint 53 (impossible-property-overlap)</span></a><br>
- <a class="rule-text" href="#typing_text"><span>Constraint 50 (typing)</span></a><br>
- </td>
-</tr>
-<tr class="component1-color">
- <td class="essential">Invalidation</td>
- <td><a class="rule-text" href="#influence-inference_text"><span>Inference 15 (influence-inference)</span></a><br>
- <a class="rule-text" href="#key-properties_text"><span>Constraint 23 (key-properties)</span></a><br>
- <a class="rule-text" href="#unique-invalidation_text"><span>Constraint 25 (unique-invalidation)</span></a><br>
- <a class="rule-text" href="#generation-precedes-invalidation_text"><span>Constraint 36 (generation-precedes-invalidation)</span></a><br>
- <a class="rule-text" href="#usage-precedes-invalidation_text"><span>Constraint 38 (usage-precedes-invalidation)</span></a><br>
- <a class="rule-text" href="#invalidation-invalidation-ordering_text"><span>Constraint 40 (invalidation-invalidation-ordering)</span></a><br>
- <a class="rule-text" href="#wasStartedBy-ordering_text"><span>Constraint 43 (wasStartedBy-ordering)</span></a><br>
- <a class="rule-text" href="#wasEndedBy-ordering_text"><span>Constraint 44 (wasEndedBy-ordering)</span></a><br>
- <a class="rule-text" href="#specialization-invalidation-ordering_text"><span>Constraint 46 (specialization-invalidation-ordering)</span></a><br>
- <a class="rule-text" href="#wasAssociatedWith-ordering_text"><span>Constraint 47 (wasAssociatedWith-ordering)</span></a><br>
- <a class="rule-text" href="#wasAttributedTo-ordering_text"><span>Constraint 48 (wasAttributedTo-ordering)</span></a><br>
- <a class="rule-text" href="#actedOnBehalfOf-ordering_text"><span>Constraint 49 (actedOnBehalfOf-ordering)</span></a><br>
- <a class="rule-text" href="#impossible-property-overlap_text"><span>Constraint 53 (impossible-property-overlap)</span></a><br>
- <a class="rule-text" href="#typing_text"><span>Constraint 50 (typing)</span></a><br>
- </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">Derivation</td>
- <td><a class="rule-text" href="#derivation-generation-use-inference_text"><span>Inference 11 (derivation-generation-use-inference)</span></a><br>
-
-
- <a class="rule-text" href="#influence-inference_text"><span>Inference 15 (influence-inference)</span></a><br>
- <a class="rule-text" href="#key-properties_text"><span>Constraint 23 (key-properties)</span></a><br>
- <a class="rule-text" href="#derivation-usage-generation-ordering_text"><span>Constraint 41 (derivation-usage-generation-ordering)</span></a><br>
- <a class="rule-text" href="#derivation-generation-generation-ordering_text"><span>Constraint 42 (derivation-generation-generation-ordering)</span></a><br>
- <a class="rule-text" href="#typing_text"><span>Constraint 50 (typing)</span></a><br>
- </td>
- <td rowspan="5" style="text-align: center; "><a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#component2" title="Component 2: Derivations">2</a></td>
-</tr>
-<tr class="component2-color">
- <td class="provType">Revision</td>
- <td><a class="rule-text" href="#revision-is-alternate-inference_text"><span>Inference 12 (revision-is-alternate-inference)</span></a><br></td>
-</tr>
-<tr class="component2-color">
- <td class="provType">Quotation</td>
- <td>No specific constraints</td>
-</tr>
-<tr class="component2-color">
- <td class="provType">Primary Source</td>
- <td>No specific constraints</td>
-</tr>
-<tr class="component2-color">
- <td class="essential">Influence</td>
- <td>No specific constraints</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">Agent</td>
- <td><a class="rule-text" href="#key-object_text"><span>Constraint 22 (key-object)</span></a><br>
- <a class="rule-text" href="#impossible-object-property-overlap_text"><span>Constraint 54 (impossible-object-property-overlap)</span></a><br>
- </td>
- <td rowspan="5" style="text-align: center; "><a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#component3" title="Component 3: Agents/Responsibility">3</a></td>
-</tr>
-<tr class="component3-color">
- <td class="essential">Attribution</td>
- <td><a class="rule-text" href="#attribution-inference_text"><span>Inference 13 (attribution-inference)</span></a><br>
- <a class="rule-text" href="#influence-inference_text"><span>Inference 15 (influence-inference)</span></a><br>
- <a class="rule-text" href="#key-properties_text"><span>Constraint 23 (key-properties)</span></a><br>
- <a class="rule-text" href="#wasAttributedTo-ordering_text"><span>Constraint 48 (wasAttributedTo-ordering)</span></a><br>
- <a class="rule-text" href="#impossible-property-overlap_text"><span>Constraint 53 (impossible-property-overlap)</span></a><br>
- <a class="rule-text" href="#typing_text"><span>Constraint 50 (typing)</span></a><br>
- </td>
-</tr>
-<tr class="component3-color">
- <td class="essential">Association</td>
- <td><a class="rule-text" href="#influence-inference_text"><span>Inference 15 (influence-inference)</span></a><br>
- <a class="rule-text" href="#key-properties_text"><span>Constraint 23 (key-properties)</span></a><br>
- <a class="rule-text" href="#wasAssociatedWith-ordering_text"><span>Constraint 47 (wasAssociatedWith-ordering)</span></a><br>
- <a class="rule-text" href="#impossible-property-overlap_text"><span>Constraint 53 (impossible-property-overlap)</span></a><br>
- <a class="rule-text" href="#typing_text"><span>Constraint 50 (typing)</span></a><br>
- </td>
-</tr>
-<tr class="component3-color">
- <td class="essential">Delegation</td>
- <td><a class="rule-text" href="#delegation-inference_text"><span>Inference 14 (delegation-inference)</span></a><br>
- <a class="rule-text" href="#influence-inference_text"><span>Inference 15 (influence-inference)</span></a><br>
- <a class="rule-text" href="#key-properties_text"><span>Constraint 23 (key-properties)</span></a><br>
- <a class="rule-text" href="#actedOnBehalfOf-ordering_text"><span>Constraint 49 (actedOnBehalfOf-ordering)</span></a><br>
- <a class="rule-text" href="#impossible-property-overlap_text"><span>Constraint 53 (impossible-property-overlap)</span></a><br>
- <a class="rule-text" href="#typing_text"><span>Constraint 50 (typing)</span></a><br>
- </td>
-</tr>
-<tr class="component3-color">
- <td class="essential">Influence</td>
- <td><a class="rule-text" href="#influence-inference_text"><span>Inference 15 (influence-inference)</span></a><br>
- <a class="rule-text" href="#key-properties_text"><span>Constraint 23 (key-properties)</span></a><br>
- </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="#dfn-bundle" class="internalDFN">Bundle constructor</a></td>
- <td>No specific constraints; see <a href="#bundle-constraints" class="sectionRef sec-ref">section 7.2 Bundles and Documents</a></td>
- <td rowspan="2" style="text-align: center; "><a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#component4" title="Component 4: Bundles">4</a></td>
-</tr>
-<tr class="component4-color">
- <td class="provType"><a title="bundle" href="#dfn-bundle" class="internalDFN">Bundle type</a></td>
- <td> No specific constraints; see <a href="#bundle-constraints" class="sectionRef sec-ref">section 7.2 Bundles and Documents</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>Alternate</td>
- <td><a class="rule-text" href="#alternate-reflexive_text"><span>Inference 16 (alternate-reflexive)</span></a><br>
- <a class="rule-text" href="#alternate-transitive_text"><span>Inference 17 (alternate-transitive)</span></a><br>
- <a class="rule-text" href="#alternate-symmetric_text"><span>Inference 18 (alternate-symmetric)</span></a><br>
- <a class="rule-text" href="#typing_text"><span>Constraint 50 (typing)</span></a><br>
- </td>
- <td rowspan="3" style="text-align: center; "><a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#component5" title="Component 5: Alternate Entities">5</a></td>
-</tr>
-<tr class="component5-color">
- <td>Specialization</td>
- <td><a class="rule-text" href="#specialization-transitive_text"><span>Inference 19 (specialization-transitive)</span></a><br>
- <a class="rule-text" href="#specialization-alternate-inference_text"><span>Inference 20 (specialization-alternate-inference)</span></a><br>
- <a class="rule-text" href="#specialization-attributes-inference_text"><span>Inference 21 (specialization-attributes-inference)</span></a><br>
- <a class="rule-text" href="#specialization-generation-ordering_text"><span>Constraint 45 (specialization-generation-ordering)</span></a><br>
- <a class="rule-text" href="#specialization-invalidation-ordering_text"><span>Constraint 46 (specialization-invalidation-ordering)</span></a><br>
- <a class="rule-text" href="#impossible-specialization-reflexive_text"><span>Constraint 52 (impossible-specialization-reflexive)</span></a><br>
- <a class="rule-text" href="#typing_text"><span>Constraint 50 (typing)</span></a><br>
- </td>
-</tr>
-
-<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
-
-<tr class="component6-color">
- <td>Collection</td>
- <td> No specific constraints </td>
- <td rowspan="2" style="text-align: center; "><a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#component6" title="Component 6: Collections">6</a></td>
-</tr>
-<tr class="component6-color">
- <td>Membership</td>
- <td> <a class="rule-text" href="#membership-empty-collection_text"><span>Constraint 56 (membership-empty-collection)</span></a><br>
- <a class="rule-text" href="#typing_text"><span>Constraint 50 (typing)</span></a><br>
- </td>
-</tr>
-</tbody></table>
-</div>
-
-
-</section>
-
-</section>
-
-<section id="compliance">
-<h2><span class="secno">3. </span>Compliance with this document</h2>
-
-<p>
- For the purpose of compliance, the normative sections of this document
- are <a href="#compliance" class="sectionRef sec-ref">section 3. Compliance with this document</a>,
-<a href="#concepts" class="sectionRef sec-ref">section 4. Basic concepts</a>,
-<a href="#inferences" class="sectionRef sec-ref">section 5. Definitions and Inferences</a>,
-<a href="#constraints" class="sectionRef sec-ref">section 6. Constraints</a>, and
-<a href="#normalization-validity-equivalence" class="sectionRef sec-ref">section 7. Normalization, Validity, and Equivalence</a>.
-
-
- To be compliant:
- </p><ol><li>When processing provenance, an
- application <span class="delete">may</span><em class="rfc2119" title="MAY"><span class="insert">MAY</span></em> apply the inferences and definitions in <a href="#inferences" class="sectionRef sec-ref">section 5. Definitions and Inferences</a>.</li>
- <li>If determining whether a PROV instance or document is <a href="#dfn-valid" class="internalDFN">valid</a>, an
- application <span class="delete">must</span><em class="rfc2119" title="MUST"><span class="insert">MUST</span></em> determine whether all of the
- constraints of <a href="#constraints" class="sectionRef sec-ref">section 6. Constraints</a> are
- satisfied on
- the <a href="#dfn-normal-form" class="internalDFN">normal form</a> of the instance or document. </li>
- <li> If producing provenance meant for other applications to
- use, the application <span class="delete">should</span><em class="rfc2119" title="SHOULD"><span class="insert">SHOULD</span></em> produce <a href="#dfn-valid" class="internalDFN">valid</a> provenance, as specified in <a href="#normalization-validity-equivalence" class="sectionRef sec-ref">section 7. Normalization, Validity, and Equivalence</a>. </li>
- <li>If determining whether two PROV instances or documents are
- <a href="#dfn-equivalent" class="internalDFN">equivalent</a>, an application <span class="delete">must</span><em class="rfc2119" title="MUST"><span class="insert">MUST</span></em> determine whether their
- normal forms are equal, as specified in <a href="#normalization-validity-equivalence" class="sectionRef sec-ref">section 7. Normalization, Validity, and Equivalence</a>.
- </li></ol>
-
- <p>This specification defines validity and equivalence procedurally
- via reduction to normal forms. If checking validity or equivalence, the
- results <span class="delete">must</span><em class="rfc2119" title="MUST"><span class="insert">MUST</span></em> be the same as would be obtained by computing normal
- forms as defined in this specification. Applications that explicitly compute
- normal forms, following the implementation strategy suggested by
- this specification, are by definition compliant. However,
- applications can also comply by checking validity and equivalence in any
- other way that yields the same answers without explicitly applying
- definitions, inferences, and constraints or constructing normal forms.</p>
-
- <p>
- All figures are for illustration purposes
- only. Information in tables is normative if it appears in a
- normative section; specifically, <a href="#expandable-parameters-fig">Table 3</a> is normative. Text in appendices and
-in boxes labeled "Remark" is informative. Where there is any apparent
- ambiguity between the descriptive text and the formal text in a
- "definition", "inference" or "constraint" box, the formal text takes
-priority.
- </p>
-
-
-
-</section>
-
- <section id="concepts">
- <h2><span class="secno">4. </span>Basic concepts</h2>
-
- <p>This section specifies the key concepts of terms, statements, instances, substitution,
- satisfaction, and unification, which have already been discussed in
- <a href="#rationale">Section 2</a>.
- </p>
-
- <p>Many PROV relation statements have an identifier, identifying a
- link between two or more related objects. Identifiers can sometimes
- be omitted in [<cite><a class="bibref" href="#bib-PROV-N">PROV-N</a></cite>] notation. For the purpose of inference and
- validity checking, we generate special identifiers called
- <dfn id="dfn-variables">variables</dfn> denoting the unknown values.
- Generally, identifiers occurring in constraints and inferences are
- variables. Variables that are generated during inferences and
- appear inside an instance are often called <dfn title="existential variable" id="dfn-existential-variable">existential
- variables</dfn>, because they are implicitly existentially quantified.
-</p>
-
-
-
-
-
- <p> A <dfn title="term" id="dfn-term">PROV term</dfn> is a constant identifier
- <span class="math">c</span>, a placeholder <span class="name">-</span>, a literal value,
- or an existential variable <span class="math">x</span>. An
- arbitrary PROV term is written <span class="math">t</span>.</p>
-
- <p> A <dfn id="statement">PROV statement</dfn> is an expression of
- the form <span class="math">p(t<sub>1</sub>,...,t<sub>n</sub>)</span> or <span class="math">p(id;t<sub>1</sub>,...,t<sub>n</sub>)</span> where
- <span class="math">id,t<sub>1</sub>,...,t<sub>n</sub></span> are
- PROV <a href="#dfn-term" class="internalDFN">term</a>s and <span class="math">p</span> is one of the
- basic PROV relations. An arbitrary PROV statement is written <span class="math">A</span>.</p>
-
-<p> A <dfn id="instance">PROV instance</dfn> is a set of PROV
- statements. Two instances are considered to be the same if they
- contain the same statements, without regard to order or repetition.
- An arbitrary PROV instance is written <span class="math">I</span>.
-</p>
-
- <p>A <dfn id="substitution">substitution</dfn> <span class="math">S</span> is a mapping <span class="math">
- [x<sub>1</sub>=t<sub>1</sub>,...,x<sub>n</sub>=t<sub>n</sub>]</span> associating existential variables
- with terms. A substitution is <em>applied</em> to a term, statement
- or instance by replacing all occurrences of each of the variables
- <span class="math">x<sub>i</sub></span> with the corresponding <span class="math">t<sub>i</sub></span>. Specifically, if <span class="math">S =
- [x<sub>1</sub>=t<sub>1</sub>,...,x<sub>n</sub>=t<sub>n</sub>]</span>
- then the application of <span class="math">S</span> to a term, statement or instance, written <span class="math">S(t)</span>, <span class="math">S(A)</span> and
- <span class="math">S(I)</span> respectively, is defined as follows:</p>
-<ul><li><span class="math">S(c) = c</span> if <span class="math">c</span> is a constant identifier.</li>
-<li><span class="math">S(x<sub>i</sub>) = t<sub>i</sub></span> if <span class="math">x<sub>i</sub></span> is one of the variables bound to a
- term <span class="math">t<sub>i</sub></span> in <span class="math">S</span>.</li>
-<li><span class="math">S(x) = x</span> if <span class="math">x</span> is a variable not bound in <span class="math">S</span>.</li>
-<li><span class="math">S(p(t<sub>1</sub>,...,t<sub>n</sub>)) = p(S(t<sub>1</sub>),...,S(t<sub>n</sub>))</span>.</li>
-<li><span class="math">S(p(id;t<sub>1</sub>,...,t<sub>n</sub>)) = p(S(id);S(t<sub>1</sub>),...,S(t<sub>n</sub>))</span>.</li>
-<li><span class="math">S(I) = { S(A) | A ∈ I } </span> if <span class="math">I</span> is an instance.</li>
-</ul>
-
- <p>Suppose <span class="math">A</span> is a statement and <span class="math">I</span> is an
- instance and <span class="math">S</span> a substitution. We say that <span class="math">A</span> is
- <dfn id="dfn-satisfied">satisfied</dfn> in <span class="math">I</span> by <span class="math">S</span> if <span class="math">S(A) ∈ I</span>. Likewise,
- we say that a set of statements <span class="math">{A<sub>1</sub>,...,A<sub>n</sub>}</span> is satisfied in
- <span class="math">I</span> if each <span class="math">A<sub>i</sub></span> is satisfied in <span class="math">I</span> by <span class="math">S</span>. Finally, we
- say that a set of statements is <dfn id="dfn-satisfiable">satisfiable</dfn>
- in <span class="math">I</span> if there is some substitution <span class="math">S</span> that satisfies the
- statements in <span class="math">I</span>.
-</p>
-
- <p> <dfn title="unification" id="dfn-unification">Unification</dfn> is an operation that can be applied
- to a pair of terms.
- The result of unification is either a <dfn id="dfn-unifier">unifier</dfn>, that is, a substitution <span class="math">S</span> such that <span class="math">S(t)
- = S(t')</span>, or failure, indicating
- that there is no <a href="#dfn-unifier" class="internalDFN">unifier</a>. Unification of pairs of terms is defined as follows.</p>
-
- <ul>
- <li> If <span class="math">t</span> and <span class="math">t'</span> are constant identifiers or literal values
- (including the placeholder <span class="name">-</span>), then
- there are two cases. If <span class="math">t = t'</span> then their <a href="#dfn-unifier" class="internalDFN">unifier</a> is the
- empty substitution, otherwise unification
-fails. </li>
- <li> If <span class="math">x</span> is an existential variable
- and
- <span class="math">t'</span> is any term (identifier, constant,
- placeholder <span class="name">-</span>, or
- existential variable), then their
- <a href="#dfn-unifier" class="internalDFN">unifier</a> is
- <span class="math">[x=t']</span>. In the special case where
- <span class="math">t'=x</span>, the <a href="#dfn-unifier" class="internalDFN">unifier</a> is the empty substitution.</li>
- <li> If <span class="math">t</span> is any term (identifier, constant,
- placeholder <span class="name">-</span>, or
- existential variable) and
- <span class="math">x'</span> is an existential variable, then their
- <a href="#dfn-unifier" class="internalDFN">unifier</a> is the same as the <a href="#dfn-unifier" class="internalDFN">unifier</a> of <span class="math">x</span>
- and <span class="math">t</span>.</li>
- </ul>
-
-
-
-<div class="remark">Unification is analogous to unification in
- logic programming and theorem proving, restricted to flat terms with
-constants and variables but no function symbols. No "occurs check" is needed because there are no
- function symbols.</div>
-
- <p>Two PROV instances <span class="math">I</span> and <span class="math">I'</span> are <dfn id="dfn-isomorphic">isomorphic</dfn> if
- there exists an invertible substitution <span class="math">S</span> that maps each
- variable of <span class="math">I</span> to a distinct variable of <span class="math">I'</span> and such that
- <span class="math">S(I) = I'</span>.</p>
-
-
-<div class="remark"><span class="insert">The scope of an existential variable is at the
- instance level. When we obtain information about an existential
- variable, for example through unification or merging during
- uniqueness constraint application, we substitute all other
- occurrences of that variable occurring in the same instance.
- Occurrences in other instances are not affected. </span></div>
-
-</section>
-<section id="inferences">
-<h2><span class="secno">5. </span>Definitions and Inferences</h2>
-<p>
-This section describes <a title="definition" href="#dfn-definition" class="internalDFN">definitions</a> and <a title="inference" href="#inference" class="internalDFN">inferences</a> that <span class="delete">may</span><em class="rfc2119" title="MAY"><span class="insert">MAY</span></em> be used on
- provenance data, and that preserve <a title="equivalent" href="#dfn-equivalent" class="internalDFN">equivalence</a> on <a href="#dfn-valid" class="internalDFN">valid</a>
-PROV instances (as detailed in <a href="#normalization-validity-equivalence" class="sectionRef sec-ref">section 7. Normalization, Validity, and Equivalence</a>).
-A <dfn id="dfn-definition">definition</dfn> is a rule that can be applied to
- PROV instances to replace defined statements with other statements. An <dfn id="inference">inference</dfn> is a rule that can be applied
- to PROV instances to add new PROV statements. A definition states that a
- provenance statement is equivalent to some other statements, whereas
- an inference only states one direction of an implication.
-</p>
-
-
-<p> Definitions have the following general form:</p>
-
-<div class="definition-example" id="definition-example"><div class="ruleTitle"><a class="internalDFN" href="#definition-example">Definition-example NNN (definition-example)</a></div>
-<p>
- <span class="name">defined_stmt</span> <span class="conditional">IF AND ONLY IF</span>
- there exists <span class="name">a<sub>1</sub></span>,..., <span class="name">a<sub>m</sub></span> such that <span class="name">defining_stmt<sub>1</sub></span> and ... and <span class="name">defining_stmt<sub>n</sub></span>.</p>
- </div>
-
- <p>
- A definition can be applied to a PROV instance, since its <span class="name">defined_stmt</span> is defined in
- terms of other statements. Applying a
- definition to an instance means that if an occurrence of a defined
- provenance statement <span class="name">defined_stmt</span>
- can be found in a PROV instance, then we can remove it and add all of the statements
-<span class="name">defining_stmt<sub>1</sub></span> ... <span class="name">defining_stmt<sub>n</sub></span> to the instance, possibly after generating fresh
- identifiers <span class="name">a<sub>1</sub></span>,...,<span class="name">a<sub>m</sub></span> for existential variables. In
- other words, it is safe to replace
- a defined statement with
- its definition.
-</p>
-
- <div class="remark">
- We use definitions primarily to expand the compact, concrete
- PROV-N syntax, including short forms and optional parameters, to the abstract syntax
- implicitly used in PROV-DM.
- </div>
-
- <p> Inferences have the following general form:</p>
-<div class="inference-example" id="inference-example"><div class="ruleTitle"><a class="internalDFN" href="#inference-example">Inference-example NNN (inference-example)</a></div>
-<p>
- <span class="conditional">IF</span> <span class="name">hyp<sub>1</sub></span> and ... and
-<span class="name">hyp<sub>k</sub></span> <span class="conditional">THEN</span>
- there exists <span class="name">a<sub>1</sub></span> and ... and <span class="name">a<sub>m</sub></span> such that <span class="name">concl<sub>1</sub></span> and ... and <span class="name">concl<sub>n</sub></span>.</p>
- </div>
-
-<p> Inferences can be applied to PROV instances. Applying an inference to an instance means that if all of the provenance statements matching
- <span class="name">hyp<sub>1</sub></span>... <span class="name">hyp<sub>k</sub></span>
- can be found in the instance, then we check whether the conclusion
- <span class="name">concl<sub>1</sub></span> ... <span class="name">concl<sub>n</sub></span> is <a href="#dfn-satisfied" class="internalDFN">satisfied</a> for some values
- of existential variables. If so, application of the inference has
- no effect on the instance. If not, then a copy the
- conclusion should be added to the instance, after
- generating fresh identifiers <span class="name">a<sub>1</sub></span>,...,<span class="name">a<sub>m</sub></span> for the existential variables. These fresh
- identifiers might later be found to be equal to known identifiers;
- they play a similar role in PROV constraints to existential
- variables in logic [<cite><a class="bibref" href="#bib-Logic">Logic</a></cite>] or database theory
- [<cite><a class="bibref" href="#bib-DBCONSTRAINTS">DBCONSTRAINTS</a></cite>].
-
- In general, omitted optional parameters to
- [<cite><a class="bibref" href="#bib-PROV-N">PROV-N</a></cite>] statements, or explicit <span class="name">-</span>
- markers, are placeholders for existentially quantified variables;
- that is, they denote unknown values. There are a few exceptions to
- this general rule, which are specified in <a class="rule-ref" href="#optional-placeholders"><span>Definition 4 (optional-placeholders)</span></a>.</p>
-
-<p> Definitions and inferences can be viewed as logical formulas;
- similar formalisms are often used in rule-based reasoning [<cite><a class="bibref" href="#bib-CHR">CHR</a></cite>]
- and in databases [<cite><a class="bibref" href="#bib-DBCONSTRAINTS">DBCONSTRAINTS</a></cite>]. In particular, the identifiers
- <span class="name">a<sub>1</sub></span> ... <span class="name">a<sub>n</sub></span>
- should be viewed as existentially quantified variables, meaning that
- through subsequent reasoning steps they may turn out to be equal to
- other identifiers that are already known, or to other existentially
- quantified variables.
-
- In contrast, distinct URIs or literal values in PROV
- are assumed to be distinct for the purpose of checking validity or
- inferences. This issue is discussed in more detail under <a href="#uniqueness-constraints">Uniqueness Constraints</a>.
- </p>
-
-<p>In a definition or inference, term symbols such as <span class="name">id</span>,
- <span class="name">start</span>, <span class="name">end</span>, <span class="name">e</span>,
- <span class="name">a</span>, <span class="name">attrs</span>,
- are assumed to be variables unless otherwise specified. These variables are scoped at
- the definition, inference, or constraint level, so the rule is equivalent to any one-for-one
- renaming of the variable names. When several rules are
- collected within a definition or inference
- as an ordered list, the scope of the variables in each rule is at the level of list elements, and so reuse of
- variable names in different rules does not affect the meaning.
-</p>
-<section id="optional-identifiers-and-attributes">
- <h3><span class="secno">5.1 </span>Optional Identifiers and Attributes</h3>
-
-
-
-<p>
-<a class="rule-ref" href="#optional-identifiers"><span>Definition 1 (optional-identifiers)</span></a>,
-<a class="rule-ref" href="#optional-attributes"><span>Definition 2 (optional-attributes)</span></a>, and
-<a class="rule-ref" href="#definition-short-forms"><span>Definition 3 (definition-short-forms)</span></a>,
- explain how to expand the compact forms of PROV-N notation into a
- normal form. <a class="rule-ref" href="#optional-placeholders"><span>Definition 4 (optional-placeholders)</span></a> indicates when
- other optional parameters can be replaced by <a title="existential variable" href="#dfn-existential-variable" class="internalDFN">existential
- variables</a>.
-</p>
-
- <div class="definition" id="optional-identifiers"><div class="ruleTitle"><a id="1"></a><a class="internalDFN" href="#optional-identifiers">Definition 1 (optional-identifiers)</a></div>
-<p>For each <span class="name">r</span> in {
-<span class="name">used</span>,
-<span class="name">wasGeneratedBy</span>,
-<span class="name">wasInvalidatedBy</span>,
-<span class="name">wasInfluencedBy</span>,
-<span class="name">wasStartedBy</span>,
-<span class="name">wasEndedBy</span>,
-<span class="name">wasInformedBy</span>,
-<span class="name">wasDerivedFrom</span>,
-<span class="name">wasAttributedTo</span>,
-<span class="name">wasAssociatedWith</span>,
-<span class="name">actedOnBehalfOf</span>}, the following
- definitional rules hold:</p>
- <ol> <li>
- <span class="name">r(a<sub>1</sub>,...,a<sub>n</sub>) </span> <span class="conditional">IF AND ONLY IF</span>
- there exists <span class="name">id</span> such that <span class="name">r(id; a<sub>1</sub>,...,a<sub>n</sub>)</span>.</li>
- <li> <span class="name">r(-; a<sub>1</sub>,...,a<sub>n</sub>) </span> <span class="conditional">IF AND ONLY IF</span>
- there exists <span class="name">id</span> such that <span class="name">r(id; a<sub>1</sub>,...,a<sub>n</sub>)</span>.</li>
- </ol>
- </div>
-
- <p>Likewise, many PROV-N statements allow for an optional attribute
- list. If it is omitted, this is the same as specifying an empty
- attribute list:</p>
- <div class="definition" id="optional-attributes"><div class="ruleTitle"><a id="2"></a><a class="internalDFN" href="#optional-attributes">Definition 2 (optional-attributes)</a></div>
-<ol>
- <li><span class="delete">
- For each</span>
-
-<p> <span class="delete">p</span><span class="delete"> in {</span><span class="delete">entity</span><span class="delete">, </span><span class="delete">activity</span><span class="delete">,
- </span><span class="delete">agent</span><span class="delete">}, if </span><span class="delete">a</span><span class="delete">n</span><span class="delete"> is not an attribute
- list parameter then the</span><span class="insert">The</span> following definitional <span class="delete">rule holds:
- </span><span class="delete">p(a</span><span class="delete">1</span><span class="delete">,...,a</span><span class="delete">n</span><span class="delete">)</span><span class="insert">rules hold:</span></p>
- <ul><li><span class="name"><span class="insert">entity(id)</span></span>
- <span class="conditional">IF AND ONLY IF</span> <span class="name"><span class="delete">p(a</span><span class="delete">1</span><span class="delete">,...,a</span><span class="delete">n</span><span class="delete">,[])</span><span class="insert">entity(id,[])</span></span>.
-
- </li>
- <li><span class="name"><span class="insert">activity(id)</span></span>
- <span class="conditional"><span class="insert">IF AND ONLY IF</span></span> <span class="name"><span class="insert">activity(id,[])</span></span><span class="insert">.
- </span></li>
- <li><span class="name"><span class="insert">activity(id,t1,t2)</span></span>
- <span class="conditional"><span class="insert">IF AND ONLY IF</span></span> <span class="name"><span class="insert">activity(id,t1,t2,[])</span></span><span class="insert">.
- </span></li>
- <li><span class="name"><span class="insert">agent(id)</span></span>
- <span class="conditional"><span class="insert">IF AND ONLY IF</span></span> <span class="name"><span class="insert">agent(id,[])</span></span><span class="insert">.
- </span></li>
- </ul>
- <br>
- </li>
- <li>
- For each <span class="name">r</span> in {
-<span class="name">used</span>,
-<span class="name">wasGeneratedBy</span>,
-<span class="name">wasInvalidated</span>,
-<span class="name">wasInfluencedBy</span>,
-<span class="name">wasStartedBy</span>,
-<span class="name">wasEndedBy</span>,
-<span class="name">wasInformedBy</span>,
-<span class="name">wasDerivedFrom</span>,
-<span class="name">wasAttributedTo</span>,
-<span class="name">wasAssociatedWith</span>,
-<span class="name">actedOnBehalfOf</span>}, if <span class="name">a<sub>n</sub></span> is not an
- attribute list parameter then the following definition holds:
-
- <p> <span class="name">r(id; a<sub>1</sub>,...,a<sub>n</sub>)</span>
- <span class="conditional">IF AND ONLY IF</span> <span class="name">r(id; a<sub>1</sub>,...,a<sub>n</sub>,[])</span>.</p></li></ol>
- </div>
-
-
- <div class="remark">
- <p>Definitions <a class="rule-ref" href="#optional-identifiers"><span>Definition 1 (optional-identifiers)</span></a> and <a class="rule-ref" href="#optional-attributes"><span>Definition 2 (optional-attributes)</span></a>.
-do not apply to <span class="name">alternateOf</span> and <span class="name">specializationOf</span>, which do not have identifiers and attributes.
-</p>
- </div>
-
-
- <p> Finally, many PROV
- statements have other optional arguments or short forms that can be
- used if none of the optional arguments is present. These are
- handled by specific rules listed below. </p>
-
-<div class="definition" id="definition-short-forms"><div class="ruleTitle"><a id="3"></a><a class="internalDFN" href="#definition-short-forms">Definition 3 (definition-short-forms)</a></div>
- <p>
-
- </p><ol>
- <li> <span class="name">activity(id,attrs)</span> <span class="conditional">IF AND ONLY IF</span> <span class="name">activity(id,-,-,attrs)</span>.
- </li>
- <li><span class="name">wasGeneratedBy(id; e,attrs)</span> <span class="conditional">IF AND ONLY IF</span> <span class="name">wasGeneratedBy(id; e,-,-,attrs)</span>.
- </li>
- <li><span class="name">used(id; a,attrs)</span> <span class="conditional">IF AND ONLY IF</span> <span class="name">used(id; a,-,-,attrs)</span>.
- </li>
- <li><span class="name">wasStartedBy(id; a,attrs)</span> <span class="conditional">IF AND ONLY IF</span> <span class="name">wasStartedBy(id; a,-,-,-,attrs)</span>.
- </li>
- <li><span class="name">wasEndedBy(id; a,attrs)</span> <span class="conditional">IF AND ONLY IF</span> <span class="name">wasEndedBy(id; a,-,-,-,attrs)</span>.
- </li>
- <li><span class="name">wasInvalidatedBy(id; e,attrs)</span> <span class="conditional">IF AND ONLY IF</span> <span class="name">wasInvalidatedBy(id; e,-,-,attrs)</span>.
- </li>
- <li><span class="name">wasDerivedFrom(id; e2,e1,attrs)</span> <span class="conditional">IF AND ONLY IF</span> <span class="name">wasDerivedFrom(id; e2,e1,-,-,-,attrs)</span>.
- </li>
- <li><span class="name">wasAssociatedWith(id; e,attrs)</span> <span class="conditional">IF AND ONLY IF</span> <span class="name">wasAssociatedWith(id; e,-,-,attrs)</span>.
- </li>
- <li><span class="name">actedOnBehalfOf(id; a2,a1,attrs)</span> <span class="conditional">IF AND ONLY IF</span> <span class="name">actedOnBehalfOf(id; a2,a1,-,attrs)</span>.
- </li>
- </ol>
- </div>
-
- <div class="remark">
-
-
- <p>
-There are no expansion rules for entity, agent, communication,
- attribution, influence, alternate, or specialization
- relations, because these
- have no optional parameters aside from the identifier and attributes,
- which are expanded by the rules in <a class="rule-ref" href="#optional-identifiers"><span>Definition 1 (optional-identifiers)</span></a> and <a class="rule-ref" href="#optional-attributes"><span>Definition 2 (optional-attributes)</span></a>. </p>
- </div>
-
-
-<p id="optional-placeholders_text">Finally, most optional parameters (written <span class="name">-</span>) are, for the purpose of this document,
- considered to be distinct, fresh existential variables. Optional parameters are defined in [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>] and in [<cite><a class="bibref" href="#bib-PROV-N">PROV-N</a></cite>] for each type of PROV statement.
- Thus,
- before proceeding to apply other definitions or inferences, most
- occurrences of <span class="name">-</span> are to be replaced
- by fresh existential variables, distinct from any others occurring in
- the instance.
- The only exceptions to this general rule, where <span class="name">-</span> are to be left
- in place, are the <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#derivation.activity">activity</a>, <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#derivation.generation">generation</a>, and <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#derivation.usage">usage</a> parameters in <span class="name">wasDerivedFrom</span> and
- the <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#association.plan">plan</a>
- parameter in <span class="name">wasAssociatedWith</span>. This is
- further explained in remarks below.
- </p>
-
- <p>The treatment of optional parameters is specified formally using
- the auxiliary concept of <dfn id="dfn-expandable-parameter">expandable parameter</dfn>. An
- expandable parameter is one that can be omitted using the
- placeholder <span class="name">-</span>, and if so, it is
- to be replaced by a fresh existential identifier.
- <a href="#expandable-parameters-fig">Table 3</a> defines the <a href="#dfn-expandable-parameter" class="internalDFN">expandable
- parameter</a>s of the properties of PROV, needed in <a class="rule-ref" href="#optional-placeholders"><span>Definition 4 (optional-placeholders)</span></a>. For emphasis, the four optional parameters
- that are not <a title="expandable parameter" href="#dfn-expandable-parameter" class="internalDFN">expandable</a> are
- also listed. Parameters that cannot have value <span class="name">-</span>, and identifiers that are
- expanded by <a class="rule-ref" href="#optional-identifiers"><span>Definition 1 (optional-identifiers)</span></a>, are not listed.</p>
- <div id="expandable-parameters-fig">
- <table id="expandable-parameters_table" border="1" class="thinborder" style="margin-left: auto; margin-right: auto; border-color: black;">
-<caption id="expandable-parameters">Table 3: Expandable and
- Non-Expandable Parameters</caption>
-<tbody><tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
- <tr>
- <th>Relation</th>
- <th>Expandable </th>
- <th>Non-expandable</th>
- </tr>
- <tr>
- <td class="name">used(id; a,e,t,attrs)</td>
- <td class="name">e,t</td>
- <td></td>
- </tr>
- <tr>
- <td class="name">wasGeneratedBy(id; e,a,t,attrs)</td>
- <td class="name">a,t</td>
- <td></td>
- </tr>
-
- <tr>
- <td class="name">wasStartedBy(id; a2,e,a1,t,attrs)</td>
- <td class="name">e,a1,t</td>
- <td></td>
- </tr>
- <tr>
- <td class="name">wasEndedBy(id; a2,e,a1,t,attrs)</td>
- <td class="name">e,a1,t</td>
- <td></td>
- </tr>
- <tr>
- <td class="name">wasInvalidatedBy(id; e,a,t,attrs)</td>
- <td class="name">a,t</td>
- <td></td>
- </tr>
- <tr>
- <td class="name">wasDerivedFrom(id; e2,e1,-,g,u,attrs)</td>
- <td class="name"></td>
- <td class="name">g,u</td>
- </tr> <tr>
- <td class="name">wasDerivedFrom(id; e2,e1,a,g,u,attrs)<br>(where <span class="name">a</span> is not placeholder <span class="name">-</span>)</td>
- <td class="name">g,u</td>
- <td class="name">a</td>
- </tr>
-
-
-
- <tr>
- <td class="name">wasAssociatedWith(id; a,ag,pl,attrs)</td>
- <td class="name">ag</td>
- <td class="name">pl</td>
- </tr>
- <tr>
- <td class="name">actedOnBehalfOf(id; ag2,ag1,a,attrs)</td>
- <td class="name">a</td>
- <td></td>
- </tr>
-
- </tbody></table>
- </div>
-
-<p> <a class="rule-ref" href="#optional-placeholders"><span>Definition 4 (optional-placeholders)</span></a> states how parameters are to be expanded,
- using the expandable parameters defined in <a href="#expandable-parameters-fig">Table 3</a>. The last two parts, 4 and 5,
- indicate how to handle expansion of parameters for
- <span class="name">wasDerivedFrom</span> expansion, which is only allowed for the
- generation and use parameters when the activity is specified.
- Essentially, the definitions state that parameters
-<span class="name">g,u</span> are expandable only if the activity is specified, i.e., if parameter <span class="name">a</span> is provided.
-
-The rationale for this is that when a is provided, then there have to be two events, namely <span class="name">u</span> and <span class="name">g</span>, which account for the usage of <span class="name">e1</span> and the generation of <span class="name">e2</span>, respectively, by <span class="name">a</span>. Conversely, if <span class="name">a</span> is not provided, then one cannot tell whether one or more activities are involved in the derivation, and the explicit introduction of such events, which correspond to a single activity, would therefore not be justified. </p>
-
-
-<p> A later constraint, <a class="rule-ref" href="#impossible-unspecified-derivation-generation-use"><span>Constraint 51 (impossible-unspecified-derivation-generation-use)</span></a>,
- forbids specifying generation and use parameters when the activity
- is unspecified.</p>
-
- <div class="definition" id="optional-placeholders"><div class="ruleTitle"><a id="4"></a><a class="internalDFN" href="#optional-placeholders">Definition 4 (optional-placeholders)</a></div>
- <ol><li>
- <span class="name">activity(id,-,t2,attrs)</span> <span class="conditional">IF AND ONLY
- IF</span> there exists <span class="name">t1</span> such that <span class="name">activity(id,t1,t2,attrs)</span>. Here, <span class="name">t2</span> <span class="delete">may</span><em class="rfc2119" title="MAY"><span class="insert">MAY</span></em> be a placeholder.
- </li>
-<li> <span class="name">activity(id,t1,-,attrs)</span> <span class="conditional">IF AND ONLY
- IF</span> there exists <span class="name">t2</span> such that <span class="name">activity(id,t1,t2,attrs)</span>. Here, <span class="name">t1</span> <span class="delete">may</span><em class="rfc2119" title="MAY"><span class="insert">MAY</span></em> be a placeholder.
-</li>
-
- <li>For each <span class="name">r</span> in {
-<span class="name">used</span>,
-<span class="name">wasGeneratedBy</span>,
-
-<span class="name">wasStartedBy</span>,
-<span class="name">wasEndedBy</span>,
-<span class="name">wasInvalidatedBy</span>,
-
-
-<span class="name">wasAssociatedWith</span>,
-<span class="name">actedOnBehalfOf</span>
-
- }, if the <span class="name">i</span>th parameter
- of <span class="name">r</span> is an <a href="#dfn-expandable-parameter" class="internalDFN">expandable parameter</a>
- of <span class="name">r</span>
- as specified in <a href="#expandable-parameters-fig">Table 3</a>
-then the following definition holds:
- <p> <span class="name">r(a<sub>0</sub>;...,a<sub>i-1</sub>, -, a<sub>i+1</sub>, ...,a<sub>n</sub>) </span> <span class="conditional">IF AND ONLY IF</span> there exists <span class="name">a'</span>
- such that <span class="name">r(a<sub>0</sub>;...,a<sub>i-1</sub>,a',a<sub>i+1</sub>,...,a<sub>n</sub>)</span>.
- </p></li>
- <li>If <span class="name">a</span> is not the placeholder <span class="name">-</span>, and <span class="name">u</span> is any term, then the following definition holds:
- <p> <span class="name">wasDerivedFrom(id; e2,e1,a,-,u,attrs)</span> <span class="conditional">IF AND ONLY IF</span> there exists <span class="name">g</span>
- such that <span class="name">wasDerivedFrom(id; e2,e1,a,g,u,attrs)</span>.</p></li>
- <li>If <span class="name">a</span> is not the placeholder <span class="name">-</span>, and <span class="name">g</span> is any term,
- then the following definition holds:
- <p> <span class="name">wasDerivedFrom(id; e2,e1,a,g,-,attrs)</span> <span class="conditional">IF AND ONLY IF</span> there exists <span class="name">u</span>
- such that <span class="name">wasDerivedFrom(id; e2,e1,a,g,u,attrs)</span>.</p></li></ol>
- </div>
-
- <div class="remark">
-<p>In an association of the form
- <span class="name">wasAssociatedWith(id; a,ag,-,attr)</span>, the
- absence of a plan means: either no plan exists, or a plan exists but
- it is not identified. Thus, it is not equivalent to <span class="name">wasAssociatedWith(id; a,ag,p,attr)</span> where a
- plan <span class="name">p</span> is given.</p>
-</div>
- <div class="remark">
-<p> A derivation <span class="name">wasDerivedFrom(id; e2,e1,a,gen,use,attrs)</span> that
- specifies an activity explicitly indicates that this activity achieved the derivation, with a usage <span class="name">use</span> of entity <span class="name">e1</span>, and a generation <span class="name">gen</span> of entity <span class="name">e2</span>.
- It differs from a derivation of the form
- <span class="name">wasDerivedFrom(id; e2,e1,-,-,-,attrs)</span> with
- missing activity, generation, and usage. In the latter form, it is not specified
- if one or more activities are involved in the derivation. </p>
-
- <p>Let us consider a system, in which a derivation is underpinned by multiple activities. Conceptually, one could also model such a system with a new activity that encompasses the two original activities and underpins the derivation. The inferences defined in this specification do not allow the latter <span class="delete">modelling</span><span class="insert">modeling</span> to be inferred from the former. Hence, the two <span class="delete">modellings</span><span class="insert">modeling</span> of the same system are regarded as different in the context of this specification.</p>
- </div>
-</section>
-
-<section id="entities-and-activities">
- <h3><span class="secno">5.2 </span>Entities and Activities</h3>
-
-
-
-
-<p id="communication-generation-use-inference_text">Communication between activities <a title="definition" href="#dfn-definition" class="internalDFN">implies</a> the existence of an underlying
-entity generated by one activity and used by the other, and vice versa.</p>
-
-<div class="inference" id="communication-generation-use-inference"><div class="ruleTitle"><a id="5"></a><a class="internalDFN" href="#communication-generation-use-inference">Inference 5 (communication-generation-use-inference)</a></div>
-<p>
-<span class="conditional">IF</span>
-<span class="name">wasInformedBy(_id; a2,a1,_attrs)</span>
-<span class="conditional">THEN</span>
- there exist <span class="name">e</span>, <span class="name">_gen</span>, <span class="name">_t1</span>, <span class="name">_use</span>, and <span class="name">_t2</span>,
-such that <span class="name">wasGeneratedBy(_gen; e,a1,_t1,[])</span> and <span class="name">used(_use; a2,e,_t2,[])</span> hold.</p>
-</div>
-
-
-<p id="generation-use-communication-inference_text">
-
- </p><div class="inference" id="generation-use-communication-inference"><div class="ruleTitle"><a id="6"></a><a class="internalDFN" href="#generation-use-communication-inference">Inference 6 (generation-use-communication-inference)</a></div>
-<p>
-<span class="conditional">IF</span> <span class="name">wasGeneratedBy(_gen; e,a1,_t1,_attrs1)</span>
- and <span class="name"><span class="delete">used(_id2;</span><span class="insert">used(_use;</span> a2,e,_t2,_attrs2)</span> hold
- <span class="conditional">THEN</span>
- there exists <span class="name">_id</span>
-such that <span class="name">wasInformedBy(_id; a2,a1,[])</span>
-</p></div>
-
-
- <div class="remark">
-<p>The relationship <span class="name">wasInformedBy</span> is not
-<a href="#dfn-transitive" class="internalDFN">transitive</a>. Indeed, consider the following statements.</p>
-<pre class="codeexample">wasInformedBy(a2,a1)
-wasInformedBy(a3,a2)
-</pre>
-<p> We cannot infer <span class="name">wasInformedBy(a3,a1)</span>
- from these statements alone. Indeed,
-from
-<span class="name">wasInformedBy(a2,a1)</span>, we know that there exists <span class="name">e1</span> such that <span class="name">e1</span> was generated by <span class="name">a1</span>
-and used by <span class="name">a2</span>. Likewise, from <span class="name">wasInformedBy(a3,a2)</span>, we know that there exists <span class="name">e2</span> such that <span class="name">e2</span> was generated by <span class="name">a2</span>
-and used by <span class="name">a3</span>. The following illustration
-shows a counterexample to transitivity. The
-horizontal axis represents the event line. We see that <span class="name">e1</span> was generated after <span class="name">e2</span> was used. Furthermore, the illustration also shows that
-<span class="name">a3</span> completes before <span class="name">a1</span> started. So in this example (with no other
- information) it is impossible for <span class="name">a3</span> to have used an entity generated by <span class="name">a1</span>. This is illustrated in <a href="#counterexample-wasInformedBy">Figure 2</a>.</p>
-
-<div style="text-align: center;">
-<span class="figure" id="fig-figure-2-counter-example-for-transitivity-of-wasinformedby">
-<img src="images/constraints/informedByNonTransitive.png" alt="non transitivity of wasInformedBy">
-<br>
-<span class="figcaption" id="counterexample-wasInformedBy">Figure 2<sup><a class="internalDFN" href="#counterexample-wasInformedBy"><span class="diamond"> ◊:</span></a></sup> Counter-example for transitivity of wasInformedBy</span>
-</span>
-</div>
-</div>
-
-
-
-<hr>
-
-
-
-<p id="entity-generation-invalidation-inference_text">
-From an entity statement, we can infer the existence of
-generation and invalidation events.
-</p>
-<div class="inference" id="entity-generation-invalidation-inference"><div class="ruleTitle"><a id="7"></a><a class="internalDFN" href="#entity-generation-invalidation-inference">Inference 7 (entity-generation-invalidation-inference)</a></div>
-<p>
-<span class="conditional">IF</span> <span class="name">entity(e,_attrs)</span> <span class="conditional">THEN</span> there exist
-<span class="name">_gen</span>, <span class="name">_a1</span>, <span class="name">_t1</span>,
-<span class="name">_inv</span>, <span class="name">_a2</span>, and <span class="name">_t2</span> such that
- <span class="name">wasGeneratedBy(_gen; e,_a1,_t1,[])</span> and <span class="name">wasInvalidatedBy(_inv; e,_a2,_t2,[])</span>.
-</p></div>
-
-
-<hr>
-
-
-<p id="activity-start-end-inference_text">
-From an activity statement, we can infer
-start and end events whose times match the start and end times of
-the activity, respectively.
-</p>
-<div class="inference" id="activity-start-end-inference"><div class="ruleTitle"><a id="8"></a><a class="internalDFN" href="#activity-start-end-inference">Inference 8 (activity-start-end-inference)</a></div>
-<p>
-<span class="conditional">IF</span> <span class="name">activity(a,t1,t2,_attrs)</span> <span class="conditional">THEN</span> there exist <span class="name">_start</span>, <span class="name">_e1</span>, <span class="name">_a1</span>, <span class="name">_end</span>, <span class="name">_a2</span>,
- and <span class="name">_e2</span> such that
- <span class="name">wasStartedBy(_start; a,_e1,_a1,t1,[])</span> and <span class="name">wasEndedBy(_end; a,_e2,_a2,t2,[])</span>.
-</p></div>
-
-
-<hr>
-
-
-<p id="wasStartedBy-inference_text">The start of an activity <span class="name">a</span> triggered by entity <span class="name">e1</span>
-implies that
-<span class="name">e1</span> was generated by the starting activity <span class="name">a1</span>.</p>
-
-<div class="inference" id="wasStartedBy-inference"><div class="ruleTitle"><a id="9"></a><a class="internalDFN" href="#wasStartedBy-inference">Inference 9 (wasStartedBy-inference)</a></div>
-<p><span class="conditional">IF</span>
- <span class="name">wasStartedBy(_id; <span class="delete">a,e1,a1,_t,_attrs)</span><span class="insert">_a,e1,a1,_t,_attrs)</span></span>,
-<span class="conditional">THEN</span> there exist <span class="name">_gen</span> and <span class="name">_t1</span>
-such that
- <span class="name">wasGeneratedBy(_gen; e1,a1,_t1,[])</span>.</p>
-</div>
-<p>
-
-</p><hr>
-
-<p id="wasEndedBy-inference_text">Likewise,
-the ending of activity <span class="name">a</span> by triggering entity <span class="name">e1</span> implies that
-<span class="name">e1</span> was generated by the ending activity <span class="name">a1</span>.
-</p>
-
-<div class="inference" id="wasEndedBy-inference"><div class="ruleTitle"><a id="10"></a><a class="internalDFN" href="#wasEndedBy-inference">Inference 10 (wasEndedBy-inference)</a></div>
-<p><span class="conditional">IF</span>
- <span class="name">wasEndedBy(_id; <span class="delete">a,e1,a1,_t,_attrs)</span><span class="insert">_a,e1,a1,_t,_attrs)</span></span>,
-<span class="conditional">THEN</span> there exist <span class="name">_gen</span> and <span class="name">_t1</span> such that
- <span class="name">wasGeneratedBy(_gen; e1,a1,_t1,[])</span>.</p>
-</div>
-
-
-
-
-</section>
-
- <section id="derivations">
-<h3><span class="secno">5.3 </span>Derivations</h3>
-
-
-<hr>
-<p id="derivation-generation-use-inference_text">Derivations with explicit
-activity, generation, and usage admit the following inference: </p>
-
-<div class="inference" id="derivation-generation-use-inference"><div class="ruleTitle"><a id="11"></a><a class="internalDFN" href="#derivation-generation-use-inference">Inference 11 (derivation-generation-use-inference)</a></div>
-<p> In this inference, none of <span class="name">a</span>, <span class="name">gen2</span> or <span class="name">use1</span> can be
- placeholders <span class="name">-</span>.
- </p><p>
-<span class="conditional">IF</span> <span class="name">wasDerivedFrom(_id; e2,e1,a,gen2,use1,_attrs)</span>,
- <span class="conditional">THEN</span> there exists <span class="name">_t1</span> and <span class="name">_t2</span> such that <span class="name">used(use1; a,e1,_t1,[])</span> and <span class="name">wasGeneratedBy(gen2; e2,a,_t2,[])</span>.
-</p>
-</div>
-<p>
-
-
-
-
-</p><hr>
-<p id="revision-is-alternate-inference_text">A revision admits the following inference, stating that the two entities
-linked by a revision are also alternates.</p>
-
-<div class="inference" id="revision-is-alternate-inference"><div class="ruleTitle"><a id="12"></a><a class="internalDFN" href="#revision-is-alternate-inference">Inference 12 (revision-is-alternate-inference)</a></div>
- <p>In this inference, any of <span class="name">_a</span>, <span class="name">_g</span> or <span class="name">_u</span> <span class="delete">may</span><em class="rfc2119" title="MAY"><span class="insert">MAY</span></em> be placeholders.</p>
-<p>
- <span class="conditional">IF</span> <span class="name">wasDerivedFrom(_id; e2,e1,_a,_g,_u,[prov:type='prov:Revision'])</span>, <span class="conditional">THEN</span> <span class="name">alternateOf(e2,e1)</span>.
-</p>
-
-</div>
-
-
-
-
-<div class="remark">
- There is no inference stating that <span class="name">wasDerivedFrom</span> is
- transitive.
- </div>
-</section>
-
-
-<section id="agents">
-<h3><span class="secno">5.4 </span>Agents</h3>
-
-<p id="attribution-inference_text"> Attribution is the ascribing of an entity to an agent. An
-entity can only be ascribed to an agent if the agent was associated with
-an activity that generated the entity. If the activity, generation
-and association events are not explicit in the instance, they can
-be inferred.</p>
-
-<div class="inference" id="attribution-inference"><div class="ruleTitle"><a id="13"></a><a class="internalDFN" href="#attribution-inference">Inference 13 (attribution-inference)</a></div>
-<p>
-<span class="conditional">IF</span>
-<span class="name">wasAttributedTo(_att; e,ag,_attrs)</span>
-
-<span class="conditional">THEN</span> there exist
- <span class="name">a</span>,
- <span class="name">_t</span>,
-<span class="name">_gen</span>,
-<span class="name">_assoc</span>,
- <span class="name">_pl</span>,
-such that
-<span class="name">wasGeneratedBy(_gen; e,a,_t,[])</span> and
-<span class="name">wasAssociatedWith(_assoc; a,ag,_pl,[])</span>.
-</p>
-</div>
-
-<div class="remark">
- In the above inference, <span class="name">_pl</span> is an
- existential variable, so it can be unified
-with a constant identifier, another existential variable, or a
- placeholder <span class="name">-</span>, as explained
- in the definition of <a href="#dfn-unification" class="internalDFN">unification</a>.
- </div>
-<hr>
-<p id="delegation-inference_text"> Delegation relates agents where one agent acts on behalf of
-another, in the context of some activity. The supervising agent
-delegates some responsibility for part of the activity to the
-subordinate agent, while retaining some responsibility for the overall
-activity. Both agents are associated with this activity.</p>
-
-
-<div class="inference" id="delegation-inference"><div class="ruleTitle"><a id="14"></a><a class="internalDFN" href="#delegation-inference">Inference 14 (delegation-inference)</a></div>
-<p>
-<span class="conditional">IF</span>
-<span class="name">actedOnBehalfOf(_id; ag1, ag2, a, _attrs)</span>
-<span class="conditional">THEN</span> there exist <span class="name">_id1</span>, <span class="name">_pl1</span>, <span class="name">_id2</span>, and <span class="name">_pl2</span> such that <span class="name">wasAssociatedWith(_id1; a, ag1, _pl1, [])</span>
- and <span class="name">wasAssociatedWith(_id2; a, ag2, _pl2,
- [])</span>.
-</p>
-</div>
-
-
-<div class="remark">
- The two associations between the agents and the activity
- may have different identifiers, different plans, and different
- attributes. In particular, the plans of the two agents need not be
- the same, and one, both, or neither can be the placeholder <span class="name">-</span>
- indicating that there is no plan, because the existential variables
- <span class="name">_pl1</span> and <span class="name">_pl2</span>
- can be replaced with constant identifiers, existential variables, or
- placeholders <span class="name">-</span> independently, as explained
- in the definition of <a href="#dfn-unification" class="internalDFN">unification</a>.
- </div>
-
-<hr>
-<p id="influence-inference_text">
-The <span class="name">wasInfluencedBy</span> relation is implied by other relations, including
-usage, start, end, generation, invalidation, communication,
-derivation, attribution, association, and delegation. To capture this
-explicitly, we allow the following inferences:
-</p>
-<div class="inference" id="influence-inference"><div class="ruleTitle"><a id="15"></a><a class="internalDFN" href="#influence-inference">Inference 15 (influence-inference)</a></div>
-<p>
- </p><ol>
- <li>
- <span class="conditional">IF</span> <span class="name">wasGeneratedBy(id; e,a,_t,attrs)</span> <span class="conditional">THEN</span> <span class="name">wasInfluencedBy(id; e, a, attrs)</span>.
- </li>
- <li>
- <span class="conditional">IF</span> <span class="name">used(id; a,e,_t,attrs)</span> <span class="conditional">THEN</span> <span class="name">wasInfluencedBy(id; a, e, attrs)</span>.
- </li>
- <li>
- <span class="conditional">IF</span> <span class="name">wasInformedBy(id; a2,a1,attrs)</span> <span class="conditional">THEN</span> <span class="name">wasInfluencedBy(id; a2, a1, attrs)</span>.
- </li>
- <li>
- <span class="conditional">IF</span> <span class="name">wasStartedBy(id; <span class="delete">a2,e,a1,_t,attrs)</span><span class="insert">a2,e,_a1,_t,attrs)</span></span> <span class="conditional">THEN</span> <span class="name">wasInfluencedBy(id; a2, e, attrs)</span>.
- </li>
- <li>
- <span class="conditional">IF</span> <span class="name">wasEndedBy(id; a2,e,_a1,_t,attrs)</span> <span class="conditional">THEN</span> <span class="name">wasInfluencedBy(id; a2, e, attrs)</span>.
- </li>
- <li>
- <span class="conditional">IF</span> <span class="name">wasInvalidatedBy(id; e,a,_t,attrs)</span> <span class="conditional">THEN</span> <span class="name">wasInfluencedBy(id; e, a, attrs)</span>.
- </li>
- <li>
- <span class="conditional">IF</span> <span class="name">wasDerivedFrom(id; e2, e1, <span class="delete">a, g, u,</span><span class="insert">_a, _g, _u,</span> attrs)</span> <span class="conditional">THEN</span> <span class="name">wasInfluencedBy(id; e2, e1, attrs)</span>. Here,
- <span class="name"><span class="delete">a</span><span class="insert">_a</span></span>, <span class="name"><span class="delete">g</span><span class="insert">_g</span></span>, <span class="name"><span class="delete">u</span> <span class="delete">may</span><span class="insert">_u</span></span> <em class="rfc2119" title="MAY"><span class="insert">MAY</span></em> be placeholders <span class="name">-</span>.
- </li>
-<li>
- <span class="conditional">IF</span> <span class="name">wasAttributedTo(id; e,ag,attrs)</span> <span class="conditional">THEN</span> <span class="name">wasInfluencedBy(id; e, ag, attrs)</span>.
- </li>
- <li>
- <span class="conditional">IF</span> <span class="name">wasAssociatedWith(id; a,ag,_pl,attrs)</span> <span class="conditional">THEN</span> <span class="name">wasInfluencedBy(id; a, ag, attrs)</span>. Here,
- <span class="name">_pl</span> <span class="delete">may</span><em class="rfc2119" title="MAY"><span class="insert">MAY</span></em> be a placeholder <span class="name">-</span>.
- </li>
- <li>
- <span class="conditional">IF</span> <span class="name">actedOnBehalfOf(id; ag2,ag1,_a,attrs)</span> <span class="conditional">THEN</span> <span class="name">wasInfluencedBy(id; ag2, ag1, attrs)</span>.
- </li>
-</ol>
-</div>
-
-<div class="remark">
- The inferences above permit the use of same identifier for an
- influence relationship and a more
- specific relationship.
-</div>
-
-</section>
-
-
-
- <section id="alternate-and-specialized-entities">
-<h3><span class="secno">5.5 </span>Alternate and Specialized Entities</h3>
-
-
-
-
-<hr>
- <p id="alternate-reflexive_text">The relation <span class="name">alternateOf</span> is an <a href="#dfn-equivalence-relation" class="internalDFN">equivalence relation</a> on
- entities: that is,
- it is <a href="#dfn-reflexive" class="internalDFN">reflexive</a>,
- <a href="#dfn-transitive" class="internalDFN">transitive</a> and <a href="#dfn-symmetric" class="internalDFN">symmetric</a>. As a consequence, the
- following inferences can be applied:</p>
-
-
-<div class="inference" id="alternate-reflexive"><div class="ruleTitle"><a id="16"></a><a class="internalDFN" href="#alternate-reflexive">Inference 16 (alternate-reflexive)</a></div>
-<p>
-<span class="conditional">IF</span> <span class="name">entity(e)</span> <span class="conditional">THEN</span>
-<span class="name">alternateOf(e,e)</span>.
-</p>
- </div>
-
-<p>
-
-</p><hr>
- <p id="alternate-transitive_text">
-
- </p><div class="inference" id="alternate-transitive"><div class="ruleTitle"><a id="17"></a><a class="internalDFN" href="#alternate-transitive">Inference 17 (alternate-transitive)</a></div>
-<p>
-<span class="conditional">IF</span> <span class="name">alternateOf(e1,e2)</span> and
- <span class="name">alternateOf(e2,e3)</span> <span class="conditional">THEN</span> <span class="name">alternateOf(e1,e3)</span>.</p>
- </div>
-
-<p>
-
-</p><hr>
- <p id="alternate-symmetric_text">
-
- </p><div class="inference" id="alternate-symmetric"><div class="ruleTitle"><a id="18"></a><a class="internalDFN" href="#alternate-symmetric">Inference 18 (alternate-symmetric)</a></div>
-<p>
-<span class="conditional">IF</span> <span class="name">alternateOf(e1,e2)</span> <span class="conditional">THEN</span> <span class="name">alternateOf(e2,e1)</span>.</p>
- </div>
-
-<p>
-
-
-</p><hr>
-<p id="specialization-transitive_text">
-Similarly, specialization is a
- <a href="#dfn-strict-partial-order" class="internalDFN">strict partial order</a>: it is <a href="#dfn-irreflexive" class="internalDFN">irreflexive</a> and
- <a href="#dfn-transitive" class="internalDFN">transitive</a>. Irreflexivity is handled later as <a class="rule-ref" href="#impossible-specialization-reflexive"><span>Constraint 52 (impossible-specialization-reflexive)</span></a>
- </p>
- <div class="inference" id="specialization-transitive"><div class="ruleTitle"><a id="19"></a><a class="internalDFN" href="#specialization-transitive">Inference 19 (specialization-transitive)</a></div>
-<p>
-
-<span class="conditional">IF</span> <span class="name">specializationOf(e1,e2)</span>
- and
- <span class="name">specializationOf(e2,e3)</span> <span class="conditional">THEN</span> <span class="name">specializationOf(e1,e3)</span>.</p>
- </div>
-
-<p>
-
-</p><hr>
-
- <p id="specialization-alternate-inference_text">If one entity specializes another, then they are also
- alternates:</p>
-
- <div class="inference" id="specialization-alternate-inference"><div class="ruleTitle"><a id="20"></a><a class="internalDFN" href="#specialization-alternate-inference">Inference 20 (specialization-alternate-inference)</a></div>
-<p>
-
-<span class="conditional">IF</span> <span class="name">specializationOf(e1,e2)</span> <span class="conditional">THEN</span> <span class="name">alternateOf(e1,e2)</span>.</p>
- </div>
-
-<hr>
-<p id="specialization-attributes-inference_text">
- If one entity specializes another then all attributes of the more
- general entity are also attributes of the more specific one.
- </p>
-<div class="inference" id="specialization-attributes-inference"><div class="ruleTitle"><a id="21"></a><a class="internalDFN" href="#specialization-attributes-inference">Inference 21 (specialization-attributes-inference)</a></div>
- <p>
-
-<span class="conditional">IF</span> <span class="name">entity(e1, attrs)</span> and <span class="name">specializationOf(e2,e1)</span>, <span class="conditional">THEN </span>
- <span class="name">entity(e2, attrs)</span>.</p>
- </div>
-
-
-
-
-</section>
-
-
-
-
-
-</section>
-
-
-
-<section id="constraints">
-<h2><span class="secno">6. </span>Constraints</h2>
-
-
-
-
-<p>
-This section defines a collection of constraints on PROV instances.
-There are three kinds of constraints:
- </p><ul><li><em>uniqueness constraints</em> that say that a <a href="#instance" class="internalDFN">PROV
- instance</a> can contain at most one statement of each kind with a
- given identifier. For
- example, if we describe the same generation event twice, then the
- two statements should have the same times;
- </li>
- <li> <em>event ordering constraints</em> that say that it
- should be possible to arrange the
- events (generation, usage, invalidation, start, end) described in a
- PROV instance into a <a href="#dfn-preorder" class="internalDFN">preorder</a> that corresponds to a sensible
- "history" (for example, an entity should not be generated after it
- is used); and
- </li>
- <li><em>impossibility constraints</em>, which forbid certain
- patterns of statements in <a href="#dfn-valid" class="internalDFN">valid</a> PROV instances.
- </li></ul>
-
- <p>As in a definition or inference, term symbols such as <span class="name">id</span>,
- <span class="name">start</span>, <span class="name">end</span>, <span class="name">e</span>,
- <span class="name">a</span>, <span class="name">attrs</span> in a constraint,
- are assumed to be variables unless otherwise specified. These variables are scoped at
- the constraint level, so the rule is equivalent to any one-for-one
- renaming of the variable names. When several rules are collected within a constraint
- as an ordered list, the scope of the variables in each rule is at the level of list elements, and so reuse of
- variable names in different rules does not affect the meaning.
-</p>
- <section id="uniqueness-constraints">
-
-
-
- <h3><span class="secno">6.1 </span>Uniqueness Constraints</h3>
-
-
-
- <p> In the absence of existential variables, uniqueness constraints
- could be checked directly by checking that no identifier appears
- more than once for a given statement. However, in the presence of
- existential variables, we need to be more careful to combine
- partial information that might be present in multiple compatible
- statements, due to inferences. Uniqueness constraints are
- enforced through <a href="#dfn-merging" class="internalDFN">merging</a> pairs of statements subject to
- equalities. For example, suppose we have two activity statements
- <span class="name">activity(a,2011-11-16T16:00:00,_t1,[a=1])</span> and <span class="name">activity(a,_t2,2011-11-16T18:00:00,[b=2])</span>, with existential variables <span class="name">_t1</span> and <span class="name">_t2</span>. The <dfn id="dfn-merge">merge</dfn> of
- these two statements (describing the same activity <span class="name">a</span>) is <span class="name">activity(a,2011-11-16T16:00:00,2011-11-16T18:00:00,[a=1,b=2])</span>. </p>
-
-
- <p>
-A typical uniqueness constraint is as follows:
- </p>
- <div class="constraint-example" id="uniqueness-example"><div class="ruleTitle"><a class="internalDFN" href="#uniqueness-example">Constraint-example NNN (uniqueness-example)</a></div>
-<p> <span class="conditional">IF</span> <span class="name">hyp<sub>1</sub></span> and ... and <span class="name">hyp<sub>n</sub></span> <span class="conditional">THEN</span> <span class="name">t<sub>1</sub></span> = <span class="name">u<sub>1</sub></span> and ... and <span class="name">t<sub>n</sub></span> = <span class="name">u<sub>n</sub></span>.</p>
- </div>
-
- <p> Such a constraint is enforced as follows:</p>
- <ol> <li>Suppose PROV instance <span class="math">I</span> contains all of the hypotheses
- <span class="name">hyp<sub>1</sub></span> and ... and <span class="name">hyp<sub>n</sub></span>.
- </li>
- <li>Attempt to unify all of the equated terms in the conclusion
- <span class="name">t<sub>1</sub></span> = <span class="name">u<sub>1</sub></span> and ... and <span class="name">t<sub>n</sub></span> = <span class="name">u<sub>n</sub></span>.
- </li>
- <li>If unification fails, then the constraint
- is unsatisfiable, so application of the constraint to <span class="math">I</span>
- fails. If this failure occurs during <a title="normal form" href="#dfn-normal-form" class="internalDFN">normalization</a> prior to
-validation, then <span class="math">I</span> is invalid, as explained in <a href="#normalization-validity-equivalence">Section 6</a>.
- </li>
- <li>If unification succeeds with a substitution <span class="math">S</span>, then
- <span class="math">S</span> is applied to the instance <span class="math">I</span>, yielding result <span class="math">S(I)</span>.</li>
- </ol>
-
-<p> <em><dfn id="dfn-key-constraints">Key constraints</dfn></em> are uniqueness constraints
- that specify that a particular key field of a relation uniquely
- determines the other parameters. Key constraints are written as follows:
- </p>
-
- <div class="constraint-example" id="key-example"><div class="ruleTitle"><a class="internalDFN" href="#key-example">Constraint-example NNN (key-example)</a></div>
- <p>The <span class="name">a<sub>k</sub></span> field is a <span class="conditional">KEY</span> for relation <span class="name">r(a<sub>0</sub>; a<sub>1</sub>,...,a<sub>n</sub>)</span>. </p></div>
-
- <p> Because of the presence of attributes, key constraints do not
- reduce directly to uniqueness constraints. Instead, we enforce key
- constraints using the following <dfn id="dfn-merging">merging</dfn> process. </p>
- <ol>
- <li> Suppose <span class="name">r(a<sub>0</sub>; a<sub>1</sub>,...a<sub>n</sub>,attrs1)</span> and <span class="name">r(b<sub>0</sub>; b<sub>1</sub>,...b<sub>n</sub>,attrs2)</span> hold in PROV instance <span class="math">I</span>, where the key fields <span class="name">a<sub>k</sub> = b<sub>k</sub></span> are equal.</li>
- <li> Attempt to unify all of the corresponding parameters <span class="name">a<sub>0</sub> = b<sub>0</sub> </span> and ... and <span class="name">a<sub>n</sub> = b<sub>n</sub></span>.
- </li>
- <li>If unification fails, then the constraint is unsatisfiable, so
- application of the key constraint to <span class="math">I</span> fails.
- </li>
- <li>If unification succeeds with substitution <span class="math">S</span>, then we remove <span class="name">r(a<sub>0</sub>; a<sub>1</sub>,...a<sub>n</sub>,attrs1)</span> and <span class="name">r(b<sub>0</sub>; b<sub>1</sub>,...b<sub>n</sub>,attrs2)</span> from <span class="math">I</span>, obtaining
- instance <span class="math">I'</span>, and return instance <span class="name">{r(S(a<sub>0</sub>); S(a<sub>1</sub>),...S(a<sub>n</sub>),attrs1 ∪
- attrs2)}</span> ∪ <span class="math">S(I')</span>.
- </li></ol>
-
-
-
-<p>Thus, if a PROV instance contains an apparent violation of a uniqueness
- constraint or key constraint, unification or merging can be used to determine
- whether the constraint can be satisfied by instantiating some existential
- variables with other terms. For key constraints, this is the same
- as merging pairs of statements whose keys are equal and whose
- corresponding arguments are compatible, because after
- unifying respective arguments and combining attribute lists, the two statements
- become equal and one can be omitted. </p>
-
-
-
-
-
-
-<p>
-</p><hr>
-
- <p id="key-object_text">The various identified objects of PROV <span class="delete">must</span><em class="rfc2119" title="MUST"><span class="insert">MUST</span></em> have
- unique statements describing them within a valid PROV instance.
- This is enforced through
- the following key constraints:
- </p>
- <div class="constraint" id="key-object"><div class="ruleTitle"><a id="22"></a><a class="internalDFN" href="#key-object">Constraint 22 (key-object)</a></div>
-<p></p><ol>
- <li>The identifier field <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#entity.id"><span class="name">id</span></a> is a <span class="conditional">KEY</span> for
- the <span class="name">entity(id,attrs)</span> statement.
- </li>
- <li>The identifier field <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#activity.id"><span class="name">id</span></a> is a <span class="conditional">KEY</span> for
- the <span class="name">activity(id,t1,t2,attrs)</span> statement.
- </li>
-<li>The identifier field <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#agent.id"><span class="name">id</span></a> is a <span class="conditional">KEY</span> for
- the <span class="name">agent(id,attrs)</span> statement.
- </li>
- </ol>
- </div>
-
- <hr>
- <p id="key-properties_text"> Likewise, the statements
-in a valid PROV instance must provide consistent information about
- each identified object or relationship. The following key
- constraints require that all of the information about each identified
- statement can be merged into a single, consistent statement:
- </p>
- <div class="constraint" id="key-properties"><div class="ruleTitle"><a id="23"></a><a class="internalDFN" href="#key-properties">Constraint 23 (key-properties)</a></div>
-<p></p><ol>
- <li>The identifier field <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#generation.id"><span class="name">id</span></a> is a <span class="conditional">KEY</span> for
- the <span class="name">wasGeneratedBy(id; e,a,t,attrs)</span> statement.
- </li>
- <li>The identifier field <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#usage.id"><span class="name">id</span></a> is a <span class="conditional">KEY</span> for
- the <span class="name">used(id; a,e,t,attrs)</span> statement.
- </li>
- <li>The identifier field <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#communication.id"><span class="name">id</span></a> is a <span class="conditional">KEY</span> for
- the <span class="name">wasInformedBy(id; a2,a1,attrs)</span> statement.
- </li>
- <li>The identifier field <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#start.id"><span class="name">id</span></a> is a <span class="conditional">KEY</span> for
- the <span class="name">wasStartedBy(id; a2,e,a1,t,attrs)</span> statement.
- </li>
- <li>The identifier field <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#end.id"><span class="name">id</span></a> is a <span class="conditional">KEY</span> for
- the <span class="name">wasEndedBy(id; a2,e,a1,t,attrs)</span> statement.
- </li>
- <li>The identifier field <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#invalidation.id"><span class="name">id</span></a> is a <span class="conditional">KEY</span> for
- the <span class="name">wasInvalidatedBy(id; e,a,t,attrs)</span> statement.
- </li>
- <li>The identifier field <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#derivation.id"><span class="name">id</span></a> is a <span class="conditional">KEY</span> for
- the <span class="name">wasDerivedFrom(id; e2, e1, a, g2, u1, attrs)</span> statement.
- </li>
- <li>The identifier field <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#attribution.id"><span class="name">id</span></a> is a <span class="conditional">KEY</span> for
- the <span class="name">wasAttributedTo(id; e,ag,attr)</span> statement.
- </li>
- <li>The identifier field <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#association.id"><span class="name">id</span></a> is a <span class="conditional">KEY</span> for
- the <span class="name">wasAssociatedWith(id; a,ag,pl,attrs)</span> statement.
- </li>
-
- <li>The identifier field <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#delegation.id"><span class="name">id</span></a> is a <span class="conditional">KEY</span> for
- the <span class="name">actedOnBehalfOf(id; ag2,ag1,a,attrs)</span> statement.
- </li>
- <li>The identifier field <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#influence.id"><span class="name">id</span></a> is a <span class="conditional">KEY</span> for
- the <span class="name">wasInfluencedBy(id; o2,o1,attrs)</span> statement.
- </li>
-</ol>
- </div>
-
-
-
-<hr>
-
-
-<div id="unique-generation_text">
-<p> Entities may have multiple generation or invalidation events
- (either or both may, however, be left implicit). An entity can be
- generated by more than one activity, with one generation event per
- each entity-activity pair. These events must be simultaneous, as required by <a class="rule-ref" href="#generation-generation-ordering"><span>Constraint 39 (generation-generation-ordering)</span></a>
- and <a class="rule-ref" href="#invalidation-invalidation-ordering"><span>Constraint 40 (invalidation-invalidation-ordering)</span></a>.
-
-</p>
-</div>
-
-
-<div class="constraint" id="unique-generation"><div class="ruleTitle"><a id="24"></a><a class="internalDFN" href="#unique-generation">Constraint 24 (unique-generation)</a></div>
-<p>
-<span class="conditional">IF</span> <span class="name">wasGeneratedBy(gen1; e,a,_t1,_attrs1)</span> and <span class="name">wasGeneratedBy(gen2; e,a,_t2,_attrs2)</span>,
-<span class="conditional">THEN</span> <span class="name">gen1</span> = <span class="name">gen2</span>.</p>
-</div>
-
-<p>
-
-</p><hr>
-<p id="unique-invalidation_text">
-
-</p><div class="constraint" id="unique-invalidation"><div class="ruleTitle"><a id="25"></a><a class="internalDFN" href="#unique-invalidation">Constraint 25 (unique-invalidation)</a></div>
-<p>
-<span class="conditional">IF</span> <span class="name">wasInvalidatedBy(inv1; e,a,_t1,_attrs1)</span> and <span class="name">wasInvalidatedBy(inv2; e,a,_t2,_attrs2)</span>,
-<span class="conditional">THEN</span> <span class="name">inv1</span> = <span class="name">inv2</span>.</p>
-</div>
-
-
-<div class="remark"> <p> It follows from the above uniqueness and key
- constraints that the generation and invalidation events linking an
- entity and activity are unique, if specified. However, because we
- apply the constraints by merging, it is possible for a valid PROV instance
-to contain multiple statements about the same generation or
- invalidation event, for example:</p>
- <pre>wasGeneratedBy(id1; e,a,-,[prov:location="Paris"])
-wasGeneratedBy(-; e,a,-,[color="Red"])
-</pre>
-<p> When the uniqueness and key constraints are applied, the instance is
- <a title="normal form" href="#dfn-normal-form" class="internalDFN">normalized</a> to the following form:</p>
- <pre>wasGeneratedBy(id1; e,a,_t,[prov:location="Paris",color="Red"])
-</pre>
-<p>
- where <span class="name">_t</span> is a new existential variable.
- </p>
-</div>
-
-
-<hr>
-<p id="unique-wasStartedBy_text">
-An activity may have more than one start and
-end event, each having a different activity (either or both may,
-however, be left implicit). However,
-the triggering entity linking any two activities in a start or end event is unique.
-That is, an activity may be started by
-several other activities, with shared or separate triggering
-entities. If an activity is started or ended by multiple events, they must all
-be simultaneous, as specified in <a class="rule-ref" href="#start-start-ordering"><span>Constraint 31 (start-start-ordering)</span></a>
-and <a class="rule-ref" href="#end-end-ordering"><span>Constraint 32 (end-end-ordering)</span></a>.
-</p>
-
-<div class="constraint" id="unique-wasStartedBy"><div class="ruleTitle"><a id="26"></a><a class="internalDFN" href="#unique-wasStartedBy">Constraint 26 (unique-wasStartedBy)</a></div>
-<p>
-<span class="conditional">IF</span> <span class="name">wasStartedBy(start1; a,_e1,a0,_t1,_attrs1)</span> and <span class="name">wasStartedBy(start2; a,_e2,a0,_t2,_attrs2)</span>, <span class="conditional">THEN</span> <span class="name">start1</span> = <span class="name">start2</span>.</p>
-</div>
-
-<p id="unique-wasEndedBy_text">
-
-</p><div class="constraint" id="unique-wasEndedBy"><div class="ruleTitle"><a id="27"></a><a class="internalDFN" href="#unique-wasEndedBy">Constraint 27 (unique-wasEndedBy)</a></div>
-<p>
-<span class="conditional">IF</span> <span class="name">wasEndedBy(end1; a,_e1,a0,_t1,_attrs1)</span> and <span class="name">wasEndedBy(end2; a,_e2,a0,_t2,_attrs2)</span>, <span class="conditional">THEN</span> <span class="name">end1</span> = <span class="name">end2</span>.</p>
-</div>
-
-
-<hr>
-
-
-
-
-
- <p id="unique-startTime_text">An <a href="#dfn-start-event" class="internalDFN">activity start event</a> is the <a title="instantaneous event" href="#dfn-event" class="internalDFN">instantaneous event</a> that marks the instant an activity starts. It allows for an optional time attribute. <span id="optional-start-time">Activities also allow for an optional start time attribute. If both are specified, they <span class="delete">must</span><em class="rfc2119" title="MUST"><span class="insert">MUST</span></em> be the same, as expressed by the following constraint.</span>
-</p>
-
-<div class="constraint" id="unique-startTime"><div class="ruleTitle"><a id="28"></a><a class="internalDFN" href="#unique-startTime">Constraint 28 (unique-startTime)</a></div>
-<p>
-<span class="conditional">IF</span> <span class="name">activity(a2,t1,_t2,_attrs)</span> and <span class="name">wasStartedBy(_start; a2,_e,_a1,t,_attrs)</span>, <span class="conditional">THEN</span> <span class="name">t1</span>=<span class="name">t</span>.</p>
-</div>
-
-<hr>
-
-<p id="unique-endTime_text">An <a href="#dfn-end-event" class="internalDFN">activity end event</a> is the <a title="instantaneous event" href="#dfn-event" class="internalDFN">instantaneous event</a> that marks the instant an activity ends. It allows for an optional time attribute. <span id="optional-end-time">Activities also allow for an optional end time attribute. If both are specified, they <span class="delete">must</span><em class="rfc2119" title="MUST"><span class="insert">MUST</span></em> be the same, as expressed by the following constraint.</span>
-</p>
-
-<div class="constraint" id="unique-endTime"><div class="ruleTitle"><a id="29"></a><a class="internalDFN" href="#unique-endTime">Constraint 29 (unique-endTime)</a></div>
-<p>
-<span class="conditional">IF</span> <span class="name">activity(a2,_t1,t2,_attrs)</span> and <span class="name">wasEndedBy(_end; a2,_e,_a1,t,_attrs1)</span>, <span class="conditional">THEN</span> <span class="name">t2</span> = <span class="name">t</span>.</p>
-</div>
-
-<p>
-
-
-</p><hr>
-
-
-
-
-
-
-</section>
-
-<section id="event-ordering-constraints">
-<h3><span class="secno">6.2 </span>Event Ordering Constraints</h3>
-
-
-<p>Given that provenance consists of a description of past entities
-and activities, <a href="#dfn-valid" class="internalDFN">valid</a> provenance instances <span class="delete">must</span><em class="rfc2119" title="MUST"><span class="insert">MUST</span></em>
-satisfy <em>ordering constraints</em> between instantaneous events, which are introduced in
-this section. For instance, an entity can only be used after it was
-generated; in other words, an entity's <a title="entity generation
-event" href="#dfn-generation-event" class="internalDFN">generation event</a> precedes any of this
-entity's <a title="entity usage event" href="#dfn-usage-event" class="internalDFN">usage events</a>. Should this
-ordering constraint be violated, the associated generation and
-usage would not be credible. The rest of this section defines
-the <dfn id="dfn-temporal-interpretation">temporal interpretation</dfn> of provenance instances as a
-set of instantaneous event ordering constraints. </p>
-
-
-<p>To allow for minimalistic clock assumptions, like Lamport
-[<cite><a class="bibref" href="#bib-CLOCK">CLOCK</a></cite>], PROV relies on a notion of relative ordering of <a title="instantaneous event" href="#dfn-event" class="internalDFN">instantaneous events</a>,
-without using physical clocks. This specification assumes that a <a href="#dfn-preorder" class="internalDFN">preorder</a> exists between <a title="instantaneous event" href="#dfn-event" class="internalDFN">instantaneous events</a>.
-</p>
-
-
-<p>Specifically, <dfn id="dfn-precedes">precedes</dfn> is a <a href="#dfn-preorder" class="internalDFN">preorder</a>
-between <a title="instantaneous event" href="#dfn-event" class="internalDFN">instantaneous events</a>. A
-constraint of the form
-<span class="name">e1</span> <a href="#dfn-precedes" class="internalDFN">precedes</a> <span class="name">e2</span> means that <span class="name">e1</span>
-happened at the same time as or before <span class="name">e2</span>.
-For symmetry, <dfn id="dfn-follows">follows</dfn> is defined as the
-inverse of <a title="precedes" href="#dfn-precedes" class="internalDFN">precedes</a>; that is, a constraint of
-the form
-<span class="name">e1</span> follows <span class="name">e2</span> means that <span class="name">e1</span> happened at the same time
-as or after <span class="name">e2</span>. Both relations are
-<a href="#dfn-preorder" class="internalDFN">preorder</a>s, meaning that they are <a href="#dfn-reflexive" class="internalDFN">reflexive</a> and
-<a href="#dfn-transitive" class="internalDFN">transitive</a>. Moreover, we sometimes consider <em>strict</em> forms of these
-orders: we say <span class="name">e1</span> <dfn id="dfn-strictly-precedes">strictly precedes</dfn> <span class="name">e2</span> to indicate that <span class="name">e1</span>
-happened before <span class="name">e2</span>, but not at the same time. This is a
-<a href="#dfn-transitive" class="internalDFN">transitive</a>, <a href="#dfn-irreflexive" class="internalDFN">irreflexive</a> relation. </p>
-
-
-<p>PROV also allows for time observations to be inserted in
-specific provenance statements, for each of the five kinds of <a title="instantaneous event" href="#dfn-event" class="internalDFN">instantaneous events</a> introduced in
-this specification. Times in provenance records arising from
-different sources might be with respect to different timelines
-(e.g. different time zones) leading to apparent inconsistencies. For
-the purpose of checking ordering constraints, the times associated
-with events are irrelevant; thus, there is no inference that time ordering
-implies event ordering, or vice versa. However, an application <span class="delete">may</span><em class="rfc2119" title="MAY"><span class="insert">MAY</span></em> flag time values
-that appear inconsistent with the event ordering as possible
-inconsistencies. When generating provenance, an application <span class="delete">should</span><em class="rfc2119" title="SHOULD"><span class="insert">SHOULD</span></em>
-use a consistent timeline for related PROV statements within an
-instance.</p>
-
-
-<p> A typical ordering constraint is as follows.</p>
-
- <div class="constraint-example" id="ordering-example"><div class="ruleTitle"><a class="internalDFN" href="#ordering-example">Constraint-example NNN (ordering-example)</a></div>
- <p><span class="conditional">IF</span> <span class="name">hyp<sub>1</sub></span> and ... and <span class="name">hyp<sub>n</sub></span> <span class="conditional">THEN</span> <span class="name">evt1</span> <a href="#dfn-precedes" class="internalDFN">precedes</a>/<a href="#dfn-strictly-precedes" class="internalDFN">strictly precedes</a> <span class="name">evt2</span>. </p></div>
- <p>
- The conclusion of an ordering constraint is either <a href="#dfn-precedes" class="internalDFN">precedes</a>
- or <a href="#dfn-strictly-precedes" class="internalDFN">strictly precedes</a>. One way to check
- ordering constraints is to
- generate all <a href="#dfn-precedes" class="internalDFN">precedes</a> and <a title="precedes" href="#dfn-precedes" class="internalDFN">strictly
- precedes</a>
- relationships arising from the ordering constraints to form a directed graph, with edges marked <a href="#dfn-precedes" class="internalDFN">precedes</a> or
- <a href="#dfn-strictly-precedes" class="internalDFN">strictly precedes</a>, and check that there is no cycle
- containing a <a href="#dfn-strictly-precedes" class="internalDFN">strictly precedes</a> edge.
- </p>
-
-
-
-
-
-<section id="activity-constraints">
-<h4><span class="secno">6.2.1 </span>Activity constraints</h4>
-
-<p>
-This section specifies ordering constraints from the perspective of
-the <a href="#dfn-lifetime" class="internalDFN">lifetime</a> of an activity. An activity starts, then during
-its lifetime can use, generate or invalidate entities, communicate
- with, start, or end
-other
-activities, or be associated with agents, and finally it ends. The following constraints amount to
-checking that all of the events associated with an activity take place
-within the activity's lifetime, and the start and end events mark the
-start and endpoints of its lifetime.
-</p>
-
-<p><a href="#ordering-activity" class="fig-ref">Figure 3</a> summarizes the ordering
- constraints on activities in a
-graphical manner. For this and subsequent figures, an event time line points to the
-right. Activities are represented by rectangles, whereas entities are
-represented by circles. Usage, generation and invalidation are
-represented by the corresponding edges between entities and
-activities. The five kinds of <a title="instantaneous event" href="#dfn-event" class="internalDFN">instantaneous events</a> are represented by vertical
-dotted lines (adjacent to the vertical sides of an activity's
-rectangle, or intersecting usage and generation edges). The ordering
-constraints are represented by triangles: an occurrence of a triangle between two <a title="instantaneous event" href="#dfn-event" class="internalDFN">instantaneous event</a> vertical dotted lines represents that the event denoted by the left
-line precedes the event denoted by the right line.</p>
-
-
-
- <div style="text-align: center;">
-
-<span class="figure" id="ordering-activity">
-<img src="images/constraints/ordering-activity.png" alt="constraints between events">
-<br>
-<span class="figcaption" id="ordering-activity-fig">Figure 3<sup><a class="internalDFN" href="#ordering-activity-fig"><span class="diamond"> ◊:</span></a></sup> Summary of <a title="instantaneous event" href="#dfn-event" class="internalDFN">instantaneous event</a> ordering constraints for activities</span>
-</span>
-</div>
-
-
-
-<hr>
-
-<p id="start-precedes-end_text">
-The existence of an activity implies that the <a href="#dfn-start-event" class="internalDFN">activity start
-event</a> always <a href="#dfn-precedes" class="internalDFN">precedes</a> the corresponding <a href="#dfn-end-event" class="internalDFN">activity end
-event</a>. This is illustrated by
-<a href="#ordering-activity" class="fig-ref">Figure 3</a>
-(a) and expressed by <a class="rule-ref" href="#start-precedes-end"><span>Constraint 30 (start-precedes-end)</span></a>.</p>
-
-<div class="constraint" id="start-precedes-end"><div class="ruleTitle"><a id="30"></a><a class="internalDFN" href="#start-precedes-end">Constraint 30 (start-precedes-end)</a></div>
-<p>
-<span class="conditional">IF</span>
-<span class="name">wasStartedBy(start; a,_e1,_a1,_t1,_attrs1)</span>
-and
-<span class="name">wasEndedBy(end; a,_e2,_a2,_t2,_attrs2)</span>
-<span class="conditional">THEN</span>
-<span class="name">start</span>
-<a title="precedes" href="#dfn-precedes" class="internalDFN">precedes</a>
-<span class="name">end</span>.
-</p>
-</div>
-<p>
-
-</p><hr>
-
-<p id="start-start-ordering_text">
-If an activity is started by more than one activity, the events must all
-be simultaneous. The following constraint requires that if there are two start
-events that start the same activity, then one <a href="#dfn-precedes" class="internalDFN">precedes</a> the
-other. Using this constraint in both directions means that each event
-<a href="#dfn-precedes" class="internalDFN">precedes</a> the other.
-</p>
-<div class="constraint" id="start-start-ordering"><div class="ruleTitle"><a id="31"></a><a class="internalDFN" href="#start-start-ordering">Constraint 31 (start-start-ordering)</a></div>
- <p>
- <span class="conditional">IF</span>
-<span class="name">wasStartedBy(start1; a,_e1,_a1,_t1,_attrs1)</span>
-and
-<span class="name">wasStartedBy(start2; a,_e2,_a2,_t2,_attrs2)</span>
-<span class="conditional">THEN</span>
-<span class="name">start1</span>
-<a title="precedes" href="#dfn-precedes" class="internalDFN">precedes</a>
-<span class="name">start2</span>.
- </p>
-</div>
-
-<hr>
-
-<p id="end-end-ordering_text">
-If an activity is ended by more than one activity, the events must all
-be simultaneous. The following constraint requires that if there are two end
-events that end the same activity, then one <a href="#dfn-precedes" class="internalDFN">precedes</a> the
-other. Using this constraint in both directions means that each event
-<a href="#dfn-precedes" class="internalDFN">precedes</a> the other, that is, they are simultaneous.
-</p>
-<div class="constraint" id="end-end-ordering"><div class="ruleTitle"><a id="32"></a><a class="internalDFN" href="#end-end-ordering">Constraint 32 (end-end-ordering)</a></div>
- <p>
- <span class="conditional">IF</span>
-<span class="name">wasEndedBy(end1; a,_e1,_a1,_t1,_attrs1)</span>
-and
-<span class="name">wasEndedBy(end2; a,_e2,_a2,_t2,_attrs2)</span>
-<span class="conditional">THEN</span>
-<span class="name">end1</span>
-<a title="precedes" href="#dfn-precedes" class="internalDFN">precedes</a>
-<span class="name">end2</span>.
- </p>
-</div>
-
-<hr>
-
-<p id="usage-within-activity_text">A usage implies ordering of <a title="instantaneous event" href="#dfn-event" class="internalDFN">events</a>, since the <a title="entity usage event" href="#dfn-usage-event" class="internalDFN">usage event</a> had to occur during the associated activity. This is
-illustrated by <a href="#ordering-activity" class="fig-ref">Figure 3</a> (b) and expressed by <a class="rule-ref" href="#usage-within-activity"><span>Constraint 33 (usage-within-activity)</span></a>.</p>
-
-<div class="constraint" id="usage-within-activity"><div class="ruleTitle"><a id="33"></a><a class="internalDFN" href="#usage-within-activity">Constraint 33 (usage-within-activity)</a></div>
-<ol>
- <li>
- <span class="conditional">IF</span>
-<span class="name">wasStartedBy(start; a,_e1,_a1,_t1,_attrs1)</span>
- and
-<span class="name">used(use; a,_e2,_t2,_attrs2)</span>
-<span class="conditional">THEN</span>
-<span class="name">start</span>
-<a title="precedes" href="#dfn-precedes" class="internalDFN">precedes</a>
-<span class="name">use</span>.
- </li>
- <li>
- <span class="conditional">IF</span>
-<span class="name">used(use; a,_e1,_t1,_attrs1)</span>
-and
-<span class="name">wasEndedBy(end; a,_e2,_a2,_t2,_attrs2)</span>
-<span class="conditional">THEN</span>
-<span class="name">use</span>
-<a title="precedes" href="#dfn-precedes" class="internalDFN">precedes</a>
-<span class="name">end</span>.
- </li>
- </ol>
-</div>
-
-<p>
-
-</p><hr>
-
-
-<p id="generation-within-activity_text">A generation implies ordering of <a title="instantaneous event" href="#dfn-event" class="internalDFN">events</a>, since the <a title="entity generation event" href="#dfn-generation-event" class="internalDFN">generation event</a> had to occur during the associated activity. This is
-illustrated by <a href="#ordering-activity" class="fig-ref">Figure 3</a> (c) and expressed by <a class="rule-ref" href="#generation-within-activity"><span>Constraint 34 (generation-within-activity)</span></a>.</p>
-
-<div class="constraint" id="generation-within-activity"><div class="ruleTitle"><a id="34"></a><a class="internalDFN" href="#generation-within-activity">Constraint 34 (generation-within-activity)</a></div>
- <ol>
- <li>
- <span class="conditional">IF</span>
-<span class="name">wasStartedBy(start; a,_e1,_a1,_t1,_attrs1)</span>
- and
-<span class="name">wasGeneratedBy(gen; _e2,a,_t2,_attrs2)</span>
-<span class="conditional">THEN</span>
-<span class="name">start</span>
-<a title="precedes" href="#dfn-precedes" class="internalDFN">precedes</a>
-<span class="name">gen</span>.
- </li>
- <li>
- <span class="conditional">IF</span>
-<span class="name">wasGeneratedBy(gen; _e,a,_t,_attrs)</span>
-and
-<span class="name">wasEndedBy(end; a,_e1,_a1,_t1,_attrs1)</span>
-<span class="conditional">THEN</span>
-<span class="name">gen</span>
-<a title="precedes" href="#dfn-precedes" class="internalDFN">precedes</a>
-<span class="name">end</span>.
- </li>
- </ol>
-</div>
-
-<p>
-
-</p><hr>
-<p id="wasInformedBy-ordering_text">
-Communication between two activities <span class="name">a1</span>
-and <span class="name">a2</span> also implies ordering
-of <a title="instantaneous event" href="#dfn-event" class="internalDFN">events</a>, since some entity must
-have been generated by the former and used by the latter, which
-implies that the start event of <span class="name">a1</span> cannot
-follow the end event of <span class="name">a2</span>. This is
-illustrated by
-<a href="#ordering-activity" class="fig-ref">Figure 3</a>
-(d) and expressed by <a class="rule-ref" href="#wasInformedBy-ordering"><span>Constraint 35 (wasInformedBy-ordering)</span></a>.</p>
-
-<div class="constraint" id="wasInformedBy-ordering"><div class="ruleTitle"><a id="35"></a><a class="internalDFN" href="#wasInformedBy-ordering">Constraint 35 (wasInformedBy-ordering)</a></div>
-<p>
- <span class="conditional">IF</span>
-<span class="name">wasInformedBy(_id; a2,a1,_attrs)</span>
-and
-<span class="name">wasStartedBy(start; a1,_e1,_a1',_t1,_attrs1)</span>
-and
-<span class="name">wasEndedBy(end; a2,_e2,_a2',_t2,_attrs2)</span>
-<span class="conditional">THEN</span>
-<span class="name">start</span>
-<a title="precedes" href="#dfn-precedes" class="internalDFN">precedes</a>
-<span class="name">end</span>.
-</p>
-</div>
-<p>
-
-
-
-</p></section>
-
-<section id="entity-constraints">
-<h4><span class="secno">6.2.2 </span> Entity constraints</h4>
-
-
-
-
-<p>
-As with activities, entities have lifetimes: they are generated, then
-can be used, other entities can be derived from them, and finally they
-can be invalidated. The constraints on these events are
-illustrated graphically in <a href="#ordering-entity" class="fig-ref">Figure 4</a> and
-<a href="#ordering-entity-trigger" class="fig-ref">Figure 5</a>.
-</p>
-
-
-
-<div style="text-align: center;">
-<span class="figure" id="ordering-entity">
-<img src="images/constraints/ordering-entity.png" alt="ordering constraints for entities">
-<br>
-<span class="figcaption" id="ordering-entity-fig">Figure 4<sup><a class="internalDFN" href="#ordering-entity-fig"><span class="diamond"> ◊:</span></a></sup> Summary of <a title="instantaneous event" href="#dfn-event" class="internalDFN">instantaneous event</a> ordering constraints for entities</span></span>
-</div>
-
-<p>
-
-</p><hr>
-
-<p id="generation-precedes-invalidation_text">
-Generation of an entity precedes its invalidation. (This
-follows from other constraints if the entity is used, but it is stated
-explicitly here to cover the case of an entity that is generated and
-invalidated without being used.)</p>
-
-<div class="constraint" id="generation-precedes-invalidation"><div class="ruleTitle"><a id="36"></a><a class="internalDFN" href="#generation-precedes-invalidation">Constraint 36 (generation-precedes-invalidation)</a></div>
-<p>
- <span class="conditional">IF</span>
-<span class="name">wasGeneratedBy(gen; e,_a1,_t1,_attrs1)</span>
-and
-<span class="name">wasInvalidatedBy(inv; e,_a2,_t2,_attrs2)</span>
-<span class="conditional">THEN</span>
-<span class="name">gen</span>
-<a title="precedes" href="#dfn-precedes" class="internalDFN">precedes</a>
-<span class="name">inv</span>.
-</p>
-</div>
-
-
-
-
-<hr>
-
-<p id="generation-precedes-usage_text">
-A usage and a generation for a given entity implies ordering of <a title="instantaneous event" href="#dfn-event" class="internalDFN">events</a>, since the <a title="entity generation
-event" href="#dfn-generation-event" class="internalDFN">generation event</a> had to precede the <a title="entity usage event" href="#dfn-usage-event" class="internalDFN">usage event</a>. This is
-illustrated by <a href="#ordering-entity" class="fig-ref">Figure 4</a>(a) and expressed by <a class="rule-ref" href="#generation-precedes-usage"><span>Constraint 37 (generation-precedes-usage)</span></a>.</p>
-
-<div class="constraint" id="generation-precedes-usage"><div class="ruleTitle"><a id="37"></a><a class="internalDFN" href="#generation-precedes-usage">Constraint 37 (generation-precedes-usage)</a></div>
-<p> <span class="conditional">IF</span>
-<span class="name">wasGeneratedBy(gen; e,_a1,_t1,_attrs1)</span>
-and
-<span class="name">used(use; _a2,e,_t2,_attrs2)</span>
-<span class="conditional">THEN</span>
-<span class="name">gen</span>
-<a title="precedes" href="#dfn-precedes" class="internalDFN">precedes</a>
-<span class="name">use</span>.
-</p>
-</div>
-
-
-<hr>
-
-<p id="usage-precedes-invalidation_text">All usages of an entity precede its invalidation, which is captured by <a class="rule-ref" href="#usage-precedes-invalidation"><span>Constraint 38 (usage-precedes-invalidation)</span></a> (without any explicit graphical representation).</p>
-
-<div class="constraint" id="usage-precedes-invalidation"><div class="ruleTitle"><a id="38"></a><a class="internalDFN" href="#usage-precedes-invalidation">Constraint 38 (usage-precedes-invalidation)</a></div>
-<p>
-<span class="conditional">IF</span>
-<span class="name">used(use; _a1,e,_t1,_attrs1)</span>
-and
-<span class="name">wasInvalidatedBy(inv; e,_a2,_t2,_attrs2)</span>
-<span class="conditional">THEN</span>
-<span class="name">use</span>
-<a title="precedes" href="#dfn-precedes" class="internalDFN">precedes</a>
-<span class="name">inv</span>.</p>
-</div>
-
-
-<hr>
-
-<p id="generation-generation-ordering_text">
-If an entity is generated by more than one activity, the events must all
-be simultaneous. The following constraint requires that if there are two generation
-events that generate the same entity, then one <a href="#dfn-precedes" class="internalDFN">precedes</a> the
-other. Using this constraint in both directions means that each event
-<a href="#dfn-precedes" class="internalDFN">precedes</a> the other.
-</p>
-<div class="constraint" id="generation-generation-ordering"><div class="ruleTitle"><a id="39"></a><a class="internalDFN" href="#generation-generation-ordering">Constraint 39 (generation-generation-ordering)</a></div>
- <p>
- <span class="conditional">IF</span>
-<span class="name">wasGeneratedBy(gen1; e,_a1,_t1,_attrs1)</span>
-and
-<span class="name">wasGeneratedBy(gen2; e,_a2,_t2,_attrs2)</span>
-<span class="conditional">THEN</span>
-<span class="name">gen1</span>
-<a title="precedes" href="#dfn-precedes" class="internalDFN">precedes</a>
-<span class="name">gen2</span>.
- </p>
-</div>
-
-<hr>
-
-<p id="invalidation-invalidation-ordering_text">
-If an entity is invalidated by more than one activity, the events must all
-be simultaneous. The following constraint requires that if there are two invalidation
-events that invalidate the same entity, then one <a href="#dfn-precedes" class="internalDFN">precedes</a> the
-other. Using this constraint in both directions means that each event
-<a href="#dfn-precedes" class="internalDFN">precedes</a> the other, that is, they are simultaneous.
-</p>
-<div class="constraint" id="invalidation-invalidation-ordering"><div class="ruleTitle"><a id="40"></a><a class="internalDFN" href="#invalidation-invalidation-ordering">Constraint 40 (invalidation-invalidation-ordering)</a></div>
- <p>
- <span class="conditional">IF</span>
-<span class="name">wasInvalidatedBy(inv1; e,_a1,_t1,_attrs1)</span>
-and
-<span class="name">wasInvalidatedBy(inv2; e,_a2,_t2,_attrs2)</span>
-<span class="conditional">THEN</span>
-<span class="name">inv1</span>
-<a title="precedes" href="#dfn-precedes" class="internalDFN">precedes</a>
-<span class="name">inv2</span>.
- </p>
-</div>
-
-
-
-<p id="derivation-usage-generation-ordering_text">If there is a
-derivation relationship linking <span class="name">e2</span> and <span class="name">e1</span>, then
-this means that the entity <span class="name">e1</span> had some influence on the entity <span class="name">e2</span>; for this to be possible, some event ordering must be satisfied.
-First, we consider derivations, where the activity and usage are known. In that case, the <a title="entity usage event" href="#dfn-usage-event" class="internalDFN">usage</a> of <span class="name">e1</span> has to precede the <a title="entity generation
-event" href="#dfn-generation-event" class="internalDFN">generation</a> of <span class="name">e2</span>.
-This is
-illustrated by <a href="#ordering-entity-fig">Figure 4</a> (b) and expressed by <a class="rule-ref" href="#derivation-usage-generation-ordering"><span>Constraint 41 (derivation-usage-generation-ordering)</span></a>.</p>
-
-
-<div class="constraint" id="derivation-usage-generation-ordering"><div class="ruleTitle"><a id="41"></a><a class="internalDFN" href="#derivation-usage-generation-ordering">Constraint 41 (derivation-usage-generation-ordering)</a></div>
- <p>
- In this constraint, <span class="name">_a</span>, <span class="name">gen2</span>, <span class="name">use1</span> <span class="delete">must not</span><em class="rfc2119" title="MUST NOT"><span class="insert">MUST NOT</span></em> be placeholders.</p>
-<p>
- <span class="conditional">IF</span>
-<span class="name">wasDerivedFrom(_d; _e2,_e1,_a,gen2,use1,_attrs)</span>
-<span class="conditional">THEN</span>
-<span class="name">use1</span>
-<a title="precedes" href="#dfn-precedes" class="internalDFN">precedes</a>
-<span class="name">gen2</span>.
-</p>
-</div>
-<p>
-</p><hr>
-
-<p id="derivation-generation-generation-ordering_text">
-When the activity, generation or usage is unknown, a similar constraint exists, except that the constraint refers to its
-generation event, as
-illustrated by <a href="#ordering-entity-fig">Figure 4</a> (c) and expressed by <a class="rule-ref" href="#derivation-generation-generation-ordering"><span>Constraint 42 (derivation-generation-generation-ordering)</span></a>.</p>
-
-<div class="constraint" id="derivation-generation-generation-ordering"><div class="ruleTitle"><a id="42"></a><a class="internalDFN" href="#derivation-generation-generation-ordering">Constraint 42 (derivation-generation-generation-ordering)</a></div>
- <p>
-In this constraint, any of <span class="name">_a</span>, <span class="name">_g</span>, <span class="name">_u</span> <span class="delete">may</span><em class="rfc2119" title="MAY"><span class="insert">MAY</span></em> be placeholders.</p>
-<p>
- <span class="conditional">IF</span>
-<span class="name">wasDerivedFrom(_d; e2,e1,_a,_g,_u,attrs)</span>
- and
-<span class="name">wasGeneratedBy(gen1; e1,_a1,_t1,_attrs1)</span>
- and
-<span class="name">wasGeneratedBy(gen2; e2,_a2,_t2,_attrs2)</span>
-<span class="conditional">THEN</span>
-<span class="name">gen1</span>
-<a href="#dfn-strictly-precedes" class="internalDFN">strictly precedes</a>
-<span class="name">gen2</span>.
-</p>
- </div>
-
-<div class="remark">
- <p>This constraint requires the derived
- entity to be generated strictly following the generation of the
- original entity. This follows from the [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>] definition of
- derivation: <em>A derivation 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</em>, thus
- the derived entity must be newer than the original entity.</p>
- <p>The event ordering is between generations of <span class="name">e1</span>
-and <span class="name">e2</span>, as opposed to derivation where usage is known,
-which implies ordering between the usage of <span class="name">e1</span> and
-generation of <span class="name">e2</span>. </p>
-</div>
-
-<hr>
-
-<p id="wasStartedBy-ordering_text">
-The entity that triggered the start of an activity must exist before the activity starts.
-This is
-illustrated by <a href="#ordering-entity-trigger" class="fig-ref">Figure 5</a>(a) and expressed by <a class="rule-ref" href="#wasStartedBy-ordering"><span>Constraint 43 (wasStartedBy-ordering)</span></a>.</p>
-
-
-<div class="constraint" id="wasStartedBy-ordering"><div class="ruleTitle"><a id="43"></a><a class="internalDFN" href="#wasStartedBy-ordering">Constraint 43 (wasStartedBy-ordering)</a></div>
- <ol>
- <li>
- <span class="conditional">IF</span>
-<span class="name">wasGeneratedBy(gen; e,_a1,_t1,_attrs1)</span>
-and
-<span class="name">wasStartedBy(start; _a,e,_a2,_t2,_attrs2)</span>
-<span class="conditional">THEN</span>
-<span class="name">gen</span>
-<a title="precedes" href="#dfn-precedes" class="internalDFN">precedes</a>
-<span class="name">start</span>.
- </li><li>
- <span class="conditional">IF</span>
-<span class="name">wasStartedBy(start; _a,e,_a1,_t1,_attrs1)</span>
-and
-<span class="name">wasInvalidatedBy(inv; e,_a2,_t2,_attrs2)</span>
-<span class="conditional">THEN</span>
-<span class="name">start</span>
-<a title="precedes" href="#dfn-precedes" class="internalDFN">precedes</a>
-<span class="name">inv</span>.
- </li>
- </ol>
-</div>
-
-<hr>
-
-<p id="wasEndedBy-ordering_text"> Similarly, the entity that triggered
-the end of an activity must exist before the activity ends, as
-illustrated by
-<a href="#ordering-entity-trigger" class="fig-ref">Figure 5</a>(b).</p>
-
-
-<div class="constraint" id="wasEndedBy-ordering"><div class="ruleTitle"><a id="44"></a><a class="internalDFN" href="#wasEndedBy-ordering">Constraint 44 (wasEndedBy-ordering)</a></div>
- <ol>
- <li>
- <span class="conditional">IF</span>
-<span class="name">wasGeneratedBy(gen; e,_a1,_t1,_attrs1)</span>
-and
- <span class="name">wasEndedBy(end; _a,e,_a2,_t2,_attrs2)</span>
-<span class="conditional">THEN</span>
-<span class="name">gen</span>
-<a title="precedes" href="#dfn-precedes" class="internalDFN">precedes</a>
-<span class="name">end</span>.
- </li><li>
- <span class="conditional">IF</span>
-<span class="name">wasEndedBy(end; _a,e,_a1,_t1,_attrs1)</span>
-and
-<span class="name">wasInvalidatedBy(inv; e,_a2,_t2,_attrs2)</span>
-<span class="conditional">THEN</span>
-<span class="name">end</span>
-<a title="precedes" href="#dfn-precedes" class="internalDFN">precedes</a>
-<span class="name">inv</span>.
- </li>
- </ol>
-</div>
-
-<div style="text-align: center; ">
-<span class="figure" id="ordering-entity-trigger">
-<img src="images/constraints/ordering-entity-trigger.png" alt="ordering constraints for trigger entities">
-<br>
-<span class="figcaption" id="ordering-entity-trigger-fig">Figure 5<sup><a class="internalDFN" href="#ordering-entity-trigger-fig"><span class="diamond"> ◊:</span></a></sup> Summary of <a title="instantaneous event" href="#dfn-event" class="internalDFN">instantaneous event</a> ordering constraints for trigger entities</span>
-</span>
-</div>
-
-<hr>
-<p id="specialization-generation-ordering_text">
-If an entity is a specialization of another, then the more
-specific entity must have been generated after the
-less specific entity was generated.
-</p>
-<div class="constraint" id="specialization-generation-ordering"><div class="ruleTitle"><a id="45"></a><a class="internalDFN" href="#specialization-generation-ordering">Constraint 45 (specialization-generation-ordering)</a></div>
- <p>
-<span class="conditional">IF</span> <span class="name">specializationOf(e2,e1)</span> and <span class="name">wasGeneratedBy(gen1; e1,_a1,_t1,_attrs1)</span> and
- <span class="name">wasGeneratedBy(gen2; e2,_a2,_t2,_attrs2)</span>
- <span class="conditional">THEN</span> <span class="name">gen1</span> <a href="#dfn-precedes" class="internalDFN">precedes</a> <span class="name">gen2</span>.
-</p></div>
-
-<p>
-
-</p><hr>
-<p id="specialization-invalidation-ordering_text">
-Similarly, if an entity is a specialization of another entity, and
-then
-the invalidation event of the more specific entity precedes that of
-the less specific entity.
-</p><div class="constraint" id="specialization-invalidation-ordering"><div class="ruleTitle"><a id="46"></a><a class="internalDFN" href="#specialization-invalidation-ordering">Constraint 46 (specialization-invalidation-ordering)</a></div>
- <p>
-<span class="conditional">IF</span> <span class="name">specializationOf(e1,e2)</span> and
- <span class="name">wasInvalidatedBy(inv1; e1,_a1,_t1,_attrs1)</span> and
- <span class="name">wasInvalidatedBy(inv2; e2,_a2,_t2,_attrs2)</span>
- <span class="conditional">THEN</span> <span class="name">inv1</span> <a href="#dfn-precedes" class="internalDFN">precedes</a> <span class="name">inv2</span>.
-</p>
- </div>
-
-</section>
-
-<section id="agent-constraints">
-<h4><span class="secno">6.2.3 </span> Agent constraints</h4>
-
-<p> Like entities and activities, agents have lifetimes that follow a
-familiar pattern. An agent that is also an entity can be generated
-and invalidated; an agent that is also an activity can be started or
-ended. During its lifetime, an agent can participate in interactions
-such as starting or ending other activities, association with an
-activity, attribution, or delegation.
-
-</p> <p>Further constraints associated with agents appear in <a href="#ordering-agents">Figure 6</a> and are discussed below.</p>
-
-<div style="text-align: center;">
-<span class="figure" id="ordering-agents-fig">
-<img src="images/constraints/ordering-agents.png" alt="ordering constraints for agents">
-<br>
-<span class="figcaption" id="ordering-agents">Figure 6<sup><a class="internalDFN" href="#ordering-agents"><span class="diamond"> ◊:</span></a></sup> Summary of <a title="instantaneous event" href="#dfn-event" class="internalDFN">instantaneous event</a> ordering
- constraints for agents</span>
-</span>
-</div>
-
-<hr>
-
-
-<p id="wasAssociatedWith-ordering_text">An activity that was
-associated with an agent must have some overlap with the agent. The
-agent <span class="delete">must</span><em class="rfc2119" title="MUST"><span class="insert">MUST</span></em> have been generated (or started), or <span class="delete">must</span><em class="rfc2119" title="MUST"><span class="insert">MUST</span></em> have become
-associated with the activity, after the activity start: so, the agent <span class="delete">must</span><em class="rfc2119" title="MUST"><span class="insert">MUST</span></em> exist before the activity end. Likewise, the agent may be destructed (or ended), or may terminate its association with the activity, before the activity end: hence, the agent invalidation (or end) is required to happen after the activity start.
-This is illustrated by <a href="#ordering-agents">Figure 6</a> (a) and expressed by <a class="rule-ref" href="#wasAssociatedWith-ordering"><span>Constraint 47 (wasAssociatedWith-ordering)</span></a>.</p>
-
-
-
-<div class="constraint" id="wasAssociatedWith-ordering"><div class="ruleTitle"><a id="47"></a><a class="internalDFN" href="#wasAssociatedWith-ordering">Constraint 47 (wasAssociatedWith-ordering)</a></div>
- <p>
-In the following inferences, <span class="name">_pl</span> <span class="delete">may</span><em class="rfc2119" title="MAY"><span class="insert">MAY</span></em> be
- a placeholder <span class="name">-</span>.
- </p><ol> <li>
- <span class="conditional">IF</span>
-<span class="name">wasAssociatedWith(_assoc; a,ag,_pl,_attrs)</span>
-and
-<span class="name">wasStartedBy(start1; a,_e1,_a1,_t1,_attrs1)</span>
-and
-<span class="name">wasInvalidatedBy(inv2; ag,_a2,_t2,_attrs2)</span>
-<span class="conditional">THEN</span>
-<span class="name">start1</span>
-<a title="precedes" href="#dfn-precedes" class="internalDFN">precedes</a>
-<span class="name">inv2</span>.
- </li><li>
- <span class="conditional">IF</span>
-<span class="name">wasAssociatedWith(_assoc; a,ag,_pl,_attrs)</span>
-and
-<span class="name">wasGeneratedBy(gen1; ag,_a1,_t1,_attrs1)</span>
-and
-<span class="name">wasEndedBy(end2; a,_e2,_a2,_t2,_attrs2)</span>
-<span class="conditional">THEN</span>
-<span class="name">gen1</span>
-<a title="precedes" href="#dfn-precedes" class="internalDFN">precedes</a>
-<span class="name">end2</span>.
- </li><li>
- <span class="conditional">IF</span>
-<span class="name">wasAssociatedWith(_assoc; a,ag,_pl,_attrs)</span>
-and
-<span class="name">wasStartedBy(start1; a,_e1,_a1,_t1,_attrs1)</span>
-and
-<span class="name">wasEndedBy(end2; ag,_e2,_a2,_t2,_attrs2)</span>
-<span class="conditional">THEN</span>
-<span class="name">start1</span>
-<a title="precedes" href="#dfn-precedes" class="internalDFN">precedes</a>
-<span class="name">end2</span>.
- </li><li>
- <span class="conditional">IF</span>
-<span class="name">wasAssociatedWith(_assoc; a,ag,_pl,_attrs)</span>
-and
-<span class="name">wasStartedBy(start1; ag,_e1,_a1,_t1,_attrs1)</span>
-and
-<span class="name">wasEndedBy(end2; a,_e2,_a2,_t2,_attrs2)</span>
-<span class="conditional">THEN</span>
-<span class="name">start1</span>
-<a title="precedes" href="#dfn-precedes" class="internalDFN">precedes</a>
-<span class="name">end2</span>.
- </li>
- </ol>
-</div>
-
-
-
-
-<div class="remark"> <p><span class="insert"> Case 3 of the above constraint says that the
-agent </span><span class="name"><span class="insert">ag</span></span><span class="insert">
-must have ended after the start of the activity </span><span class="name"><span class="insert">a</span></span><span class="insert">,
-ensuring some overlap between the two. Since </span><span class="name"><span class="insert">ag</span></span><span class="insert"> is the subject of a
-</span><span class="name"><span class="insert">wasEndedBy</span></span><span class="insert"> statement, it is an activity according to the </span><a href="#typing"><span class="insert">typing constraints</span></a><span class="insert">. Case 4 handles the symmetric
- case, ensuring that the start of an agent-activity precedes the
- start of an associated activity. </span></p> </div>
-
-<p>
-
-</p><hr>
-
-<p id="wasAttributedTo-ordering_text">An agent to which an entity was attributed, <span class="delete">must</span><em class="rfc2119" title="MUST"><span class="insert">MUST</span></em> exist before this entity was generated.
-This is
-illustrated by <a href="#ordering-agents">Figure 6</a> (b) and expressed by <a class="rule-ref" href="#wasAttributedTo-ordering"><span>Constraint 48 (wasAttributedTo-ordering)</span></a>.</p>
-
-
-
-
-<div class="constraint" id="wasAttributedTo-ordering"><div class="ruleTitle"><a id="48"></a><a class="internalDFN" href="#wasAttributedTo-ordering">Constraint 48 (wasAttributedTo-ordering)</a></div>
- <ol> <li>
- <span class="conditional">IF</span>
-<span class="name">wasAttributedTo(_at; e,ag,_attrs)</span>
-and
-<span class="name">wasGeneratedBy(gen1; ag,_a1,_t1,_attrs1)</span>
-and
-<span class="name">wasGeneratedBy(gen2; e,_a2,_t2,_attrs2)</span>
-<span class="conditional">THEN</span>
-<span class="name">gen1</span>
-<a title="precedes" href="#dfn-precedes" class="internalDFN">precedes</a>
-<span class="name">gen2</span>.
- </li><li>
- <span class="conditional">IF</span>
-<span class="name">wasAttributedTo(_at; e,ag,_attrs)</span>
-and
-<span class="name">wasStartedBy(start1; ag,_e1,_a1,_t1,_attrs1)</span>
-and
-<span class="name">wasGeneratedBy(gen2; e,_a2,_t2,_attrs2)</span>
-<span class="conditional">THEN</span>
-<span class="name">start1</span>
-<a title="precedes" href="#dfn-precedes" class="internalDFN">precedes</a>
-<span class="name">gen2</span>.
- </li>
- </ol>
-</div>
-
-<p>
-</p><hr>
-
-<p id="actedOnBehalfOf-ordering_text">For delegation, the responsible agent has to precede or have some overlap with the subordinate agent.</p>
-
-
-<div class="constraint" id="actedOnBehalfOf-ordering"><div class="ruleTitle"><a id="49"></a><a class="internalDFN" href="#actedOnBehalfOf-ordering">Constraint 49 (actedOnBehalfOf-ordering)</a></div>
- <ol> <li>
- <span class="conditional">IF</span>
-<span class="name">actedOnBehalfOf(_del; ag2,ag1,_a,_attrs)</span>
-and
-<span class="name">wasGeneratedBy(gen1; ag1,_a1,_t1,_attrs1)</span>
-and
-<span class="name">wasInvalidatedBy(inv2; ag2,_a2,_t2,_attrs2)</span>
-<span class="conditional">THEN</span>
-<span class="name">gen1</span>
-<a title="precedes" href="#dfn-precedes" class="internalDFN">precedes</a>
-<span class="name">inv2</span>.
- </li><li>
- <span class="conditional">IF</span>
-<span class="name">actedOnBehalfOf(_del; ag2,ag1,_a,_attrs)</span>
-and
-<span class="name">wasStartedBy(start1; ag1,_e1,_a1,_t1,_attrs1)</span>
-and
-<span class="name">wasEndedBy(end2; ag2,_e2,_a2,_t2,_attrs2)</span>
-<span class="conditional">THEN</span>
-<span class="name">start1</span>
-<a title="precedes" href="#dfn-precedes" class="internalDFN">precedes</a>
-<span class="name">end2</span>.
- </li>
- </ol>
-
-</div>
-
-</section>
-
-</section>
-
-
-
-<section id="type-constraints">
-<h3><span class="secno">6.3 </span>Type Constraints</h3>
-
-<p id="typing_text">The following rules assign types to identifiers
-based on their use within statements.
-The function <span class="name">typeOf</span> gives the set of types denoted by an identifier.
-That is, <span class="name">typeOf(e)</span> returns the set of types
-associated with identifier <span class="name">e</span>. The function
-<span class="name">typeOf</span> is not a PROV statement, but a
-construct used only during validation PROV, similar to <a href="#dfn-precedes" class="internalDFN">precedes</a>.
-</p>
-
-
-
-
-<p>
- For any identifier <span class="name">id</span>, <span class="name">typeOf(id)</span> is a subset of {<span class="name">'entity'</span>, <span class="name">'activity'</span>, <span class="name">'agent'</span>, <span class="name">'prov:Collection'</span>, <span class="name">'prov:EmptyCollection'</span>}.
-For identifiers that do not have a type, <span class="name">typeOf</span> gives the empty set.
- Identifiers can have more than one type, because of subtyping
- (e.g. <span class="name">'prov:EmptyCollection'</span> is a subtype of <span class="name">'prov:Collection'</span>) or because certain types are not
- disjoint (such as <span class="name">'agent'</span> and <span class="name">'entity'</span>). The set of types
- does not reflect all of the distinctions among objects, only those
- relevant for checking validity. In particular, a subtype such as <span class="name">'plan'</span> is omitted, and statements such as <span class="name">wasAssociatedWith</span> that have plan parameters only check that these parameters are entities.
-</p>
-
-<p>To check if a PROV instance satisfies type constraints, one obtains the types of identifiers by application of
-<a class="rule-ref" href="#typing"><span>Constraint 50 (typing)</span></a>
-and check that none of the impossibility constraints
-<a class="rule-ref" href="#entity-activity-disjoint"><span>Constraint 55 (entity-activity-disjoint)</span></a> and
-<a class="rule-ref" href="#membership-empty-collection"><span>Constraint 56 (membership-empty-collection)</span></a> are
- violated as a result.</p>
-
-
-<div class="constraint" id="typing"><div class="ruleTitle"><a id="50"></a><a class="internalDFN" href="#typing">Constraint 50 (typing)</a></div>
-
-
-<ol>
-<li>
-<span class="conditional">IF</span>
- <span class="name">entity(e,attrs)</span>
-<span class="conditional">THEN</span>
-<span class="name">'entity' ∈ typeOf(e)</span>.
-</li><li>
-<span class="conditional">IF</span>
- <span class="name">agent(ag,attrs)</span>
-<span class="conditional">THEN</span>
-<span class="name">'agent' ∈ typeOf(ag)</span>.
-</li><li>
-<span class="conditional">IF</span>
- <span class="name">activity(a,t1,t2,attrs)</span>
-<span class="conditional">THEN</span>
-<span class="name">'activity' ∈ typeOf(a)</span>.
-
-
-</li><li>
-
-<span class="conditional">IF</span>
- <span class="name">used(u; a,e,t,attrs)</span>
-<span class="conditional">THEN</span>
-<span class="name">'activity' ∈ typeOf(a)</span> AND
-<span class="name">'entity' ∈ typeOf(e)</span>.
-
-</li><li>
-<span class="conditional">IF</span>
- <span class="name">wasGeneratedBy(gen; e,a,t,attrs)</span>
-<span class="conditional">THEN</span>
-<span class="name">'entity' ∈ typeOf(e)</span> AND
-<span class="name">'activity' ∈ typeOf(a)</span>.
-
-</li><li>
-
-<span class="conditional">IF</span>
- <span class="name">wasInformedBy(id; a2,a1,attrs)</span>
-<span class="conditional">THEN</span>
-<span class="name">'activity' ∈ typeOf(a2)</span> AND
-<span class="name">'activity' ∈ typeOf(a1)</span>.
-
-</li><li>
-
-<span class="conditional">IF</span>
- <span class="name">wasStartedBy(id; a2,e,a1,t,attrs)</span>
-<span class="conditional">THEN</span>
-<span class="name">'activity' ∈ typeOf(a2)</span> AND
-<span class="name">'entity' ∈ typeOf(e)</span> AND
-<span class="name">'activity' ∈ typeOf(a1)</span>.
-
-
-
-</li><li>
-
-
-<span class="conditional">IF</span>
- <span class="name">wasEndedBy(id; a2,e,a1,t,attrs)</span>
-<span class="conditional">THEN</span>
-<span class="name">'activity' ∈ typeOf(a2)</span> AND
-<span class="name">'entity' ∈ typeOf(e)</span> AND
-<span class="name">'activity' ∈ typeOf(a1)</span>.
-
-
-
-</li><li>
-<span class="conditional">IF</span>
- <span class="name">wasInvalidatedBy(id; e,a,t,attrs)</span>
-<span class="conditional">THEN</span>
-<span class="name">'entity' ∈ typeOf(e)</span> AND
-<span class="name">'activity' ∈ typeOf(a)</span>.
-
-
-
-
-</li><li>
-<span class="conditional">IF</span>
- <span class="name">wasDerivedFrom(id; e2, e1, a, g2, u1, attrs)</span>
-<span class="conditional">THEN</span>
-<span class="name">'entity' ∈ typeOf(e2)</span> AND
-<span class="name">'entity' ∈ typeOf(e1)</span> AND
-<span class="name">'activity' ∈ typeOf(a)</span>.
- In this constraint, <span class="name">a</span>, <span class="name">g2</span>, and <span class="name">u1</span> <span class="delete">must not</span><em class="rfc2119" title="MUST NOT"><span class="insert">MUST NOT</span></em> be placeholders.
-
-</li><li>
-<span class="conditional">IF</span>
- <span class="name">wasDerivedFrom(id; e2, e1, -, -, -, attrs)</span>
-<span class="conditional">THEN</span>
-<span class="name">'entity' ∈ typeOf(e2)</span> AND
-<span class="name">'entity' ∈ typeOf(e1)</span>.
-
-</li><li>
-<span class="conditional">IF</span>
- <span class="name">wasAttributedTo(id; e,ag,attr)</span>
-<span class="conditional">THEN</span>
-<span class="name">'entity' ∈ typeOf(e)</span> AND
-<span class="name">'agent' ∈ typeOf(ag)</span>.
-
-
-</li><li>
-<span class="conditional">IF</span>
- <span class="name">wasAssociatedWith(id; a,ag,pl,attrs)</span>
-<span class="conditional">THEN</span>
-<span class="name">'activity' ∈ typeOf(a)</span> AND
-<span class="name">'agent' ∈ typeOf(ag)</span> AND
-<span class="name">'entity' ∈ typeOf(pl)</span>. In this
-constraint, <span class="name">pl</span> <span class="delete">must not</span><em class="rfc2119" title="MUST NOT"><span class="insert">MUST NOT</span></em> be a placeholder.
-
-</li><li>
-<span class="conditional">IF</span>
- <span class="name">wasAssociatedWith(id; a,ag,-,attrs)</span>
-<span class="conditional">THEN</span>
-<span class="name">'activity' ∈ typeOf(a)</span> AND
-<span class="name">'agent' ∈ typeOf(ag)</span>.
-
-
-
-
-</li><li>
-<span class="conditional">IF</span>
- <span class="name">actedOnBehalfOf(id; ag2,ag1,a,attrs)</span>
-<span class="conditional">THEN</span>
-<span class="name">'agent' ∈ typeOf(ag2)</span> AND
-<span class="name">'agent' ∈ typeOf(ag1)</span> AND
-<span class="name">'activity' ∈ typeOf(a)</span>.
-
-
-
-
-</li><li>
-<span class="conditional">IF</span>
- <span class="name">alternateOf(e2, e1)</span>
-<span class="conditional">THEN</span>
-<span class="name">'entity' ∈ typeOf(e2)</span> AND
-<span class="name">'entity' ∈ typeOf(e1)</span>.
-
-
-</li><li>
-<span class="conditional">IF</span>
- <span class="name">specializationOf(e2, e1)</span>
-<span class="conditional">THEN</span>
-<span class="name">'entity' ∈ typeOf(e2)</span> AND
-<span class="name">'entity' ∈ typeOf(e1)</span>.
-
-
-
-
-</li><li>
-
-<span class="conditional">IF</span>
- <span class="name">hadMember(c,e)</span>
-<span class="conditional">THEN</span>
-<span class="name">'prov:Collection' ∈ typeOf(c)</span> AND
-<span class="name">'entity' ∈ typeOf(c)</span> AND
-<span class="name">'entity' ∈ typeOf(e)</span>.
-
-
-</li><li>
-
-<span class="conditional">IF</span>
- <span class="name">entity(c,[prov:type='prov:EmptyCollection'])</span>
-<span class="conditional">THEN</span>
-<span class="name">'entity' ∈ typeOf(c)</span> AND
-<span class="name">'prov:Collection' ∈ typeOf(c)</span> AND
-<span class="name">'prov:EmptyCollection' ∈ typeOf(c)</span>.
-
-</li></ol>
-</div>
-
-</section>
-
-<section id="impossibility-constraints">
-<h3><span class="secno">6.4 </span>Impossibility constraints</h3>
-
-<p> Impossibility constraints require that certain patterns of
-statements never appear in <a href="#dfn-valid" class="internalDFN">valid</a> PROV instances. Impossibility
-constraints have the following general form:
-</p>
-
-<div class="constraint-example" id="impossible-example"><div class="ruleTitle"><a class="internalDFN" href="#impossible-example">Constraint-example NNN (impossible-example)</a></div>
- <p><span class="conditional">IF</span> <span class="name">hyp<sub>1</sub></span> and ... and <span class="name">hyp<sub>n</sub></span> <span class="conditional">THEN</span> <span class="conditional">INVALID</span>.</p>
- </div>
-
-<p> Checking an impossibility constraint on instance <span class="math">I</span> means checking whether there is
-any way of matching the pattern <span class="name">hyp<sub>1</sub></span>, ..., <span class="name">hyp<sub>n</sub></span>. If there
-is, then checking the constraint on <span class="math">I</span> fails (which implies that
-<span class="math">I</span> is invalid).
-
-
-</p><hr>
-
-<p id="impossible-unspecified-derivation-generation-use_text">
-A derivation with unspecified activity <span class="name">wasDerivedFrom(id;e1,e2,-,g,u,attrs)</span> represents a derivation that
- takes one or more steps, whose activity, generation and use events
- are unspecified. It is forbidden to specify a generation or use
- event without specifying the activity.</p>
-
- <div class="constraint" id="impossible-unspecified-derivation-generation-use"><div class="ruleTitle"><a id="51"></a><a class="internalDFN" href="#impossible-unspecified-derivation-generation-use">Constraint 51 (impossible-unspecified-derivation-generation-use)</a></div>
-<p> In the following rules, <span class="name">g</span> and <span class="name">u</span> <span class="delete">must not</span><em class="rfc2119" title="MUST NOT"><span class="insert">MUST NOT</span></em> be <span class="name">-</span>.</p>
- <ol>
- <li> <span class="conditional">IF</span>
- <span class="name">wasDerivedFrom(_id;_e2,_e1,-,g,-,attrs)</span>
- <span class="conditional">THEN</span> <span class="conditional">INVALID</span>.</li> <li> <span class="conditional">IF</span>
- <span class="name">wasDerivedFrom(_id;_e2,_e1,-,-,u,attrs)</span>
- <span class="conditional">THEN</span> <span class="conditional">INVALID</span>.</li>
- <li> <span class="conditional">IF</span>
- <span class="name">wasDerivedFrom(_id;_e2,_e1,-,g,u,attrs)</span>
- <span class="conditional">THEN</span> <span class="conditional">INVALID</span>.</li>
- </ol>
- </div>
-<hr>
-
-<p id="impossible-specialization-reflexive_text">As noted previously, specialization is a
- <a href="#dfn-strict-partial-order" class="internalDFN">strict partial order</a>: it is <a href="#dfn-irreflexive" class="internalDFN">irreflexive</a> and
- <a href="#dfn-transitive" class="internalDFN">transitive</a>.</p>
-
- <div class="constraint" id="impossible-specialization-reflexive"><div class="ruleTitle"><a id="52"></a><a class="internalDFN" href="#impossible-specialization-reflexive">Constraint 52 (impossible-specialization-reflexive)</a></div>
-
- <p> <span class="conditional">IF</span> <span class="name">specializationOf(e,e)</span> <span class="conditional">THEN</span> <span class="conditional">INVALID</span>.</p>
- </div>
-
-
-
-
-
- <hr>
-
-
- <p id="impossible-property-overlap_text"> Furthermore, identifiers
- of basic relationships are disjoint.
- </p>
- <div class="constraint" id="impossible-property-overlap"><div class="ruleTitle"><a id="53"></a><a class="internalDFN" href="#impossible-property-overlap">Constraint 53 (impossible-property-overlap)</a></div>
- <p>
-For each <span class="name">r</span> and <span class="name">s</span>
- in {
-<span class="name">used</span>,
-<span class="name">wasGeneratedBy</span>,
-<span class="name">wasInvalidatedBy</span>,
-<span class="name">wasStartedBy</span>,
-<span class="name">wasEndedBy</span>,
-<span class="name">wasInformedBy</span>,
-<span class="name">wasAttributedTo</span>,
-<span class="name">wasAssociatedWith</span>,
-<span class="name">actedOnBehalfOf</span>} such that <span class="name">r</span> and <span class="name">s</span>
- are different relation names, the
- following constraint holds:
-</p>
- <p>
- <span class="conditional">IF</span> <span class="name">r(id; a<sub>1</sub>,...,a<sub>m</sub>)</span> and <span class="name">s(id; b<sub>1</sub>,...,b<sub>n</sub>)</span> <span class="conditional">THEN INVALID</span>.
- </p>
- </div>
-
- <div class="remark">
- <p>Since <span class="name">wasInfluencedBy</span> is a superproperty of many other
- properties, it is excluded from the set of properties whose
- identifiers are required to be pairwise disjoint. The following
- example illustrates this observation:
- </p><pre>wasInfluencedBy(id;e2,e1)
-wasDerivedFrom(id;e2,e1)
-</pre>
-<p> This satisfies the disjointness constraint.
- </p>
- <p>There is, however, no
- constraint requiring that every influence relationship is
- accompanied by a more specific relationship having the same
- identifier. The following valid example illustrates this observation:
- </p><pre>wasInfluencedBy(id; e2,e1)
-</pre>
-<p> This is valid; there is no inferrable information about what kind
- of influence relates <span class="name">e2</span> and <span class="name">e1</span>, other than its identity.
- </p>
- </div>
-
- <p id="impossible-object-property-overlap_text"> Identifiers of entities,
- agents and activities cannot also be identifiers of properties.
- </p>
- <div class="constraint" id="impossible-object-property-overlap"><div class="ruleTitle"><a id="54"></a><a class="internalDFN" href="#impossible-object-property-overlap">Constraint 54 (impossible-object-property-overlap)</a></div>
- <p>
-For each <span class="name">p</span> in {<span class="name">entity</span>, <span class="name">activity</span>
- or <span class="name">agent</span>} and for each <span class="name">r</span> in {
-<span class="name">used</span>,
-<span class="name">wasGeneratedBy</span>,
-<span class="name">wasInvalidatedBy</span>,
-<span class="name">wasInfluencedBy</span>,
-<span class="name">wasStartedBy</span>,
-<span class="name">wasEndedBy</span>,
-<span class="name">wasInformedBy</span>,
-<span class="name">wasDerivedFrom</span>,
-<span class="name">wasAttributedTo</span>,
-<span class="name">wasAssociatedWith</span>,
-<span class="name">actedOnBehalfOf</span>}, the following
- impossibility constraint holds:</p>
-
-<p> <span class="conditional">IF</span> <span class="name">p(id,a<sub>1</sub>,...,a<sub>m</sub>)</span> and
- <span class="name">r(id; b<sub>1</sub>,...,b<sub>n</sub>)</span> <span class="conditional">THEN INVALID</span>.
- </p>
- </div>
-
-
-
-
- <hr>
- <p id="entity-activity-disjoint_text"> The set of entities and activities are disjoint, expressed by
- the following constraint:
- </p>
- <div class="constraint" id="entity-activity-disjoint"><div class="ruleTitle"><a id="55"></a><a class="internalDFN" href="#entity-activity-disjoint">Constraint 55 (entity-activity-disjoint)</a></div>
-
-
-<p>
- <span class="conditional">IF</span>
-<span class="name">'entity' ∈ typeOf(id)</span> AND
-<span class="name">'activity' ∈ typeOf(id)</span>
-<span class="conditional">THEN</span> <span class="conditional">INVALID</span>.</p>
- </div>
- <div class="remark">
- There is no disjointness between entities and agents. This is because one might want to make statements about the provenance of an agent, by making it an entity.
- For example, one can assert both <span class="name">entity(a1)</span> and <span class="name">agent(a1)</span> in a valid PROV instance.
- Similarly, there is no disjointness between activities and
- agents, and one can assert both <span class="name">activity(a1)</span> and <span class="name">agent(a1)</span> in a valid PROV instance.
- However, one should keep in mind that some specific types of agents may not be suitable as activities.
- For example, asserting statements such as <span class="name">agent(Bob, [type=prov:Person])</span> and <span class="name">activity(Bob)</span> is discouraged. In these cases, disjointness can be ensured by explicitly asserting the agent as both agent and entity, and applying <a class="rule-ref" href="#entity-activity-disjoint"><span>Constraint 55 (entity-activity-disjoint)</span></a>.
- </div>
-
-
- <hr>
- <p id="membership-empty-collection_text"> An empty collection cannot contain any member, expressed by
- the following constraint:
- </p>
- <div class="constraint" id="membership-empty-collection"><div class="ruleTitle"><a id="56"></a><a class="internalDFN" href="#membership-empty-collection">Constraint 56 (membership-empty-collection)</a></div>
-<p> <span class="conditional">IF</span>
- <span class="name"><span class="delete">hasMember(c,e)</span><span class="insert">hadMember(c,e)</span></span> and
-<span class="name">'prov:EmptyCollection' ∈ typeOf(c)</span>
-<span class="conditional">THEN</span> <span class="conditional">INVALID</span>.</p>
- </div>
-
-
-
-</section>
-
-
-</section>
-
- <section id="normalization-validity-equivalence">
-<h2><span class="secno">7. </span>Normalization, Validity, and Equivalence</h2>
-
-
- <p>We define the notions of <a title="normal form" href="#dfn-normal-form" class="internalDFN">normalization</a>, <a title="valid" href="#dfn-valid" class="internalDFN">validity</a> and
-<a title="equivalence">equivalence</a> of PROV documents and instances. We first define these concepts
-for PROV instances and then extend them to PROV documents.</p>
-
-<section id="instances">
- <h3><span class="secno">7.1 </span>Instances</h3>
-
-<div class="remark">
- Before normalization or validation, implementations should expand
- namespace prefixes and perform any appropriate reasoning about
- co-reference of identifiers, and rewrite the instance (by
- replacing co-referent identifiers with a single common identifier) to
- make this explicit, before doing validation, equivalence checking,
- or normalization.
- All of the following definitions assume that the application has
- already determined which URIs in the PROV instance are co-referent
- (e.g. <span class="name">owl:sameAs</span> as a result of OWL
- reasoning).
- </div>
-
-<p> We define the <dfn id="dfn-normal-form">normal form</dfn> of a PROV instance as the set
-of provenance statements resulting from applying all definitions,
- inferences, and uniqueness constraints, obtained as follows:</p>
-
-
-
- <ol>
- <li>
- Apply all definitions to <span class="math">I</span> by replacing each defined statement by its
- definition (possibly introducing fresh existential variables in
- the process), yielding an instance <span class="math">I<sub>1</sub></span>.
- </li>
- <li>
- Apply all inferences to <span class="math">I<sub>1</sub></span> by adding the conclusion of each inference
- whose hypotheses are satisfied and whose entire conclusion does not
- already hold (again, possibly introducing fresh existential
- variables), yielding an instance <span class="math">I<sub>2</sub></span>.
- </li>
- <li>
- Apply all uniqueness constraints to <span class="math">I<sub>2</sub></span> by unifying terms or merging statements
- and applying the resulting substitution to the instance, yielding
- an instance <span class="math">I<sub>3</sub></span>. If some uniqueness constraint cannot be
- applied, then normalization fails.
- </li>
- <li>If no definitions, inferences, or uniqueness constraints can be applied to instance <span class="math">I<sub>3</sub></span>, then <span class="math">I<sub>3</sub></span> is the
- normal form of <span class="math">I</span>.</li>
- <li>Otherwise, the normal form of <span class="math">I</span> is the same as the normal form
- of <span class="math">I<sub>3</sub></span> (that is, proceed by
- normalizing <span class="math">I<sub>3</sub></span> at step 1).
- </li></ol>
-
-<p>Because of the potential interaction among definitions, inferences, and
- constraints, the above algorithm is iterative. Nevertheless,
- all of our constraints fall into a class of <em>tuple-generating
- dependencies<span class="delete"> and </span></em><span class="insert"> and </span><em>equality-generating dependencies</em> that
- satisfy a termination condition called <em>weak acyclicity</em> that
- has been studied in the context of relational databases
- [<cite><a class="bibref" href="#bib-DBCONSTRAINTS">DBCONSTRAINTS</a></cite>]. Therefore, the above algorithm terminates, independently
- of the order in which inferences and constraints are applied.
- <a href="#termination">Appendix A</a> gives a proof that normalization terminates and produces
- a unique (up to isomorphism) normal form.
-</p>
-
- <p>
- A PROV instance is <dfn id="dfn-valid">valid</dfn>
-if its normal form exists and all of
- the validity constraints succeed on the normal form.
- The following algorithm can be used to test
- validity:</p>
-
-<ol>
- <li>Normalize the instance <span class="math">I</span>, obtaining
- normal form <span class="math">I'</span>. If
- normalization fails, then <span class="math">I</span> is not <a href="#dfn-valid" class="internalDFN">valid</a>.
- </li>
- <li>Apply all event ordering constraints to <span class="math">I'</span> to build a graph <span class="math">G</span> whose nodes
- are event identifiers and edges
- are labeled by "precedes"
- and "strictly precedes" relationships among events induced by the constraints.</li>
- <li> Determine whether there is a cycle in <span class="math">G</span> that contains a
- "strictly precedes" edge. If so, then <span class="math">I</span> is not <a href="#dfn-valid" class="internalDFN">valid</a>.
- </li>
- <li>Apply the type constraints <a href="#type-constraints">(section
- 5.3)</a> to determine whether there are any violations of
- disjointness. If so, then <span class="math">I</span> is not <a href="#dfn-valid" class="internalDFN">valid</a>.
- </li><li>
- Check that none of the impossibility constraints <a href="#impossibility-constraints">(section 5.4)</a> are
- violated. If any are violated, then <span class="math">I</span> is
- not <a href="#dfn-valid" class="internalDFN">valid</a>. Otherwise, <span class="math">I</span> is <a href="#dfn-valid" class="internalDFN">valid</a>.
- </li>
- </ol>
-
-<p>A normal form of a PROV instance does not exist when a uniqueness
- constraint fails due to unification or merging failure. </p>
-
-
-
-<p> Two <a href="#dfn-valid" class="internalDFN">valid</a> PROV instances are <dfn title="equivalent" id="dfn-equivalent">equivalent</dfn> if they
- have <a href="#dfn-isomorphic" class="internalDFN">isomorphic</a> normal forms. That is, after applying all possible inference
-rules, the two instances produce the same set of PROV statements,
-up to reordering of statements and attributes within attribute lists,
- and renaming of existential variables.
-</p>
- <p>Equivalence can also be checked over pairs of PROV instances that
- are not necessarily valid, subject to the following rules:
- </p><ul>
- <li>If both are valid, then equivalence is
- defined above.</li>
- <li>If both are invalid, then equivalence can be
- implemented in any way provided it is <a href="#dfn-reflexive" class="internalDFN">reflexive</a>, <a href="#dfn-symmetric" class="internalDFN">symmetric</a>, and <a href="#dfn-transitive" class="internalDFN">transitive</a>.
- </li>
- <li>If one instance is valid and the other is invalid, then the two
- instances are not equivalent.</li>
- </ul>
- <p>
-Equivalence has the following characteristics over valid instances: </p>
-
-<ul>
- <li>
- The order of provenance statements is irrelevant to the meaning of
- a PROV instance. That is, a
- PROV instance is equivalent to any other instance obtained by
-reordering its statements.
- </li>
- <li>The order of attribute-value pairs in attribute lists is
- irrelevant to the meaning of a PROV statement. That is, a PROV
- statement carrying attributes is equivalent to any other statement
- obtained by reordering attribute-value pairs and eliminating
- duplicate pairs.
- </li>
- <li>The particular choices of names of existential variables are irrelevant to the meaning
- of an instance; that is, the names can be renamed without changing
- the meaning, as long as different names are always replaced with
- different names. (Replacing two different names with equal names,
- however, can
- change the meaning, so does not preserve equivalence.)</li>
- <li>
- Applying inference rules, definitions, and uniqueness constraints preserves equivalence. That is, a <a href="#instance" class="internalDFN">PROV
- instance</a> is equivalent to the instance obtained by applying any
- inference rule or definition, or by <a title="unification" href="#dfn-unification" class="internalDFN">unifying</a> two terms or <a href="#dfn-merging" class="internalDFN">merging</a> two statements to
- enforce a uniqueness constraint.
- </li>
- <li>Equivalence is <a href="#dfn-reflexive" class="internalDFN">reflexive</a>, <a href="#dfn-symmetric" class="internalDFN">symmetric</a>, and
- <a href="#dfn-transitive" class="internalDFN">transitive</a>. (This is because a valid instance has a unique
- normal form up to isomorphism [<cite><a class="bibref" href="#bib-DBCONSTRAINTS">DBCONSTRAINTS</a></cite>]). </li>
-</ul>
-
-<p> An application that processes PROV data <span class="delete">should</span><em class="rfc2119" title="SHOULD"><span class="insert">SHOULD</span></em> handle
-equivalent instances in the same way. This guideline is necessarily
-imprecise because "in the same way" is application-specific.
-Common exceptions to this guideline
-include, for example, applications that pretty-print or digitally sign
-provenance, where the order and syntactic form of statements matters. </p>
-
-</section>
-
-<section id="bundle-constraints">
-<h3><span class="secno">7.2 </span>Bundles and Documents</h3>
-
-
-<p>The definitions, inferences, and constraints, and
-the resulting notions of normalization, validity and equivalence,
-work on a single PROV instance. In this
-section, we describe how to deal with general PROV
-documents, possibly including multiple named <a title="bundle" href="#dfn-bundle" class="internalDFN">bundles</a> as well as a
-<a href="#dfn-toplevel-instance" class="internalDFN">toplevel <span class="delete">instance.</span><span class="insert">instance</span></a><span class="insert">.</span> Briefly, each bundle is
-handled independently; there is no interaction between bundles from
-the perspective of applying definitions, inferences, or constraints,
-computing normal forms, or checking validity or equivalence.</p>
-
-<p> We model a general PROV document, containing <span class="name">n</span> named bundles
-<span class="name">b<sub>1</sub>...b<sub>n</sub></span>, as a tuple
-<span class="name">(I<sub>0</sub>,[b<sub>1</sub>=I<sub>1</sub>,...,b<sub>n</sub>=I<sub>n</sub>])</span>
-where <span class="name">I<sub>0</sub></span> is the toplevel
-instance, and for each <span class="name">i</span>, <span class="name">I<sub>i</sub></span> is the instance associated with
-bundle <span class="name">b<sub>i</sub></span>. This notation is shorthand for the
-following PROV-N syntax:</p>
-
-<div class="name">
-document<br>
- I<sub>0</sub><br>
- bundle b<sub>1</sub><br>
- I<sub>1</sub><br>
- endBundle<br>
- ...<br>
- bundle b<sub>n</sub><br>
- I<sub>n</sub><br>
- endBundle<br>
-endDocument
-</div>
-
-<p> The <a href="#dfn-normal-form" class="internalDFN">normal form</a> of a PROV document
-<span class="name">(I<sub>0</sub>,[b<sub>1</sub>=I<sub>1</sub>,...,[b<sub>n</sub>=I<sub>n</sub>])</span> is <span class="name">(I'<sub>0</sub>,[b<sub>1</sub>=I'<sub>1</sub>,...,b<sub>n</sub>=I'<sub>n</sub>])</span>
-where <span class="name">I'<sub>i</sub></span> is the normal
-form of <span class="name">I<sub>i</sub></span> for each <span class="name">i</span> between 0 and <span class="name">n</span>. </p>
-
-<p>A PROV document is <a href="#dfn-valid" class="internalDFN">valid</a> if each of the bundles <span class="name">I<sub>0</sub></span>,
-..., <span class="name">I<sub>n</sub></span> are valid and none of the bundle identifiers <span class="name">b<sub>i</sub></span> are repeated.</p>
-
-<p>Two (valid) PROV documents <span class="name">(I<sub>0</sub>,[b<sub>1</sub>=I<sub>1</sub>,...,b<sub>n</sub>=I<sub>n</sub>])</span> and
-<span class="name">(I'<sub>0</sub>,[b<sub>1</sub>'=I'<sub>1</sub>,...,b'<sub>m</sub>=I'<sub>m</sub>])</span> are <a href="#dfn-equivalent" class="internalDFN">equivalent</a> if <span class="name">I<sub>0</sub></span> is
-equivalent to <span class="name">I'<sub>0</sub></span> and <span class="name">n = m</span> and
-there exists a permutation <span class="name">P : {1..n} -> {1..n}</span> such that for each <span class="name">i</span>, <span class="name">b<sub>i</sub> =
-b'<sub>P(i)</sub></span> and <span class="name">I<sub>i</sub></span> is equivalent to <span class="name">I'<sub>P(i)</sub></span>.
-</p>
-
-</section>
-
-
-</section>
-
-
-
-
-
-
-
-
-
-
-
-<section class="glossary" id="glossary">
- <h2><span class="secno">8. </span>Glossary</h2>
-
- <ul>
- <li> <dfn id="dfn-antisymmetric">antisymmetric</dfn>: A relation <span class="math">R</span> over <span class="math">X</span> is <a href="#dfn-antisymmetric" class="internalDFN">antisymmetric</a> if
- for any elements <span class="math">x</span>, <span class="math">y</span> of <span class="math">X</span>, if <span class="math">x R y</span> and <span class="math">y R x</span> then <span class="math">x = y</span>.</li>
- <li> <dfn id="dfn-asymmetric">asymmetric</dfn>: A relation <span class="math">R</span> over <span class="math">X</span> is <a href="#dfn-asymmetric" class="internalDFN">asymmetric</a> if
- <span class="math">x R y</span> and <span class="math">y R x</span> do not hold for any elements <span class="math">x</span>, <span class="math">y</span> of <span class="math">X</span>.</li>
- <li><dfn id="dfn-equivalence-relation">equivalence relation</dfn>: An equivalence relation is a relation
- that is <a href="#dfn-reflexive" class="internalDFN">reflexive</a>, <a href="#dfn-symmetric" class="internalDFN">symmetric</a>, and
- <a href="#dfn-transitive" class="internalDFN">transitive</a>.</li>
- <li> <dfn id="dfn-irreflexive">irreflexive</dfn>: A relation <span class="math">R</span> over <span class="math">X</span> is <a href="#dfn-irreflexive" class="internalDFN">irreflexive</a> if
- for <span class="math">x R x</span> does not hold for any element <span class="math">x</span> of <span class="math">X</span>.</li>
- <li><dfn id="dfn-partial-order">partial order</dfn>: A partial order is a relation
- that is <a href="#dfn-reflexive" class="internalDFN">reflexive</a>, <a href="#dfn-antisymmetric" class="internalDFN">antisymmetric</a>, and <a href="#dfn-transitive" class="internalDFN">transitive</a>.</li>
- <li><dfn id="dfn-preorder">preorder</dfn>: A preorder is a relation that is
- <a href="#dfn-reflexive" class="internalDFN">reflexive</a> and <a href="#dfn-transitive" class="internalDFN">transitive</a>. (It is not necessarily antisymmetric,
- meaning there can be cycles of distinct elements <span class="math">x<sub>1</sub> R x<sub>2</sub> R ... R
- x<sub>n</sub> R x<sub>1</sub>.</span></li>
- <li> <dfn id="dfn-reflexive">reflexive</dfn>: A relation <span class="math">R</span> over <span class="math">X</span> is <a href="#dfn-reflexive" class="internalDFN">reflexive</a> if
- for any element <span class="math">x</span> of <span class="math">X</span>, we have <span class="math">x R x</span>.</li>
- <li><dfn id="dfn-strict-partial-order">strict partial order</dfn>: A strict partial order is a
- relation that is <a href="#dfn-irreflexive" class="internalDFN">irreflexive</a>, <a href="#dfn-asymmetric" class="internalDFN">asymmetric</a> and <a href="#dfn-transitive" class="internalDFN">transitive</a>.</li>
- <li><dfn id="dfn-strict-preorder">strict preorder</dfn>: A strict preorder is a relation
- that is <a href="#dfn-irreflexive" class="internalDFN">irreflexive</a> and <a href="#dfn-transitive" class="internalDFN">transitive</a>.</li>
- <li> <dfn id="dfn-symmetric">symmetric</dfn>: A relation <span class="math">R</span> over <span class="math">X</span> is <a href="#dfn-symmetric" class="internalDFN">symmetric</a> if
- for any elements <span class="math">x</span>, <span class="math">y</span> of <span class="math">X</span>, if <span class="math">x R y</span> then <span class="math">y R x</span>.</li>
- <li> <dfn id="dfn-transitive">transitive</dfn>: A relation <span class="math">R</span> over <span class="math">X</span> is <a href="#dfn-transitive" class="internalDFN">transitive</a> if
- for any elements <span class="math">x</span>, <span class="math">y</span>, <span class="math">z</span> of <span class="math">X</span>, if <span class="math">x R y</span> and <span class="math">y R z</span> then <span class="math">x R z</span>.</li>
-
-
- </ul>
- </section>
-
-
- <section class="appendix informative" id="termination">
- <h2><span class="secno">A. </span>Termination of normalization</h2><p><em>This section is non-normative.</em></p>
-
- <p>
- We will show that normalization terminates, that is, that
- applying definitions, inferences and uniqueness/key constraints
- eventually either fails (due to constraint violation) or
- terminates with a normal form.
- </p>
- <p>
- First, since the inferences and constraints never introduce new
- defined statements, for the purpose of termination we always expand
- the definitions first and then consider only normalization of
- instances in which there are no remaining defined statements.
- </p>
- <p>We will prove termination for the simple case where there are no
- attributes. For the general case, we will show that any
- nontermination arising from an instance that does involve
- attributes would also arise from one with no attributes.
- </p>
-
- <p><b>Termination for instances without attributes.</b> For
- these instances, uniqueness and key constraints can be
- As shown in [<cite><a class="bibref" href="#bib-DBCONSTRAINTS">DBCONSTRAINTS</a></cite>], termination of normalization can be
- shown by checking that the inference rules are <em>weakly
- acyclic</em>. In addition, weak acyclicity can be checked
- in a modular fashion for our system, because there are only a few possible
- cycles among statements. The following table summarizes seven
- <em>stages</em> of the inference rules; because there are no
- cycles among stages, it is sufficient to check weak acyclicity
- of each stage independently.
- </p>
-
- <table border="1">
- <tbody><tr>
- <th>Stage #</th>
- <th>Inference</th>
- <th>Hypotheses</th>
- <th>Conclusions</th>
- </tr>
- <tr>
- <td>1</td>
- <td>19, 20, 21</td>
- <td class="name">specializationOf</td>
- <td class="name">specializationOf, entity</td>
- </tr>
- <tr>
- <td>2</td>
- <td>7, 8, 13, 14</td>
- <td class="name">entity, activity, wasAttributedTo, actedOnBehalfOf</td>
- <td class="name">wasInvalidatedBy, wasStartedBy, wasEndedBy,
- wasAssociatedWith</td>
- </tr>
- <tr>
- <td>3</td>
- <td>9, 10</td>
- <td class="name">wasStartedBy, wasEndedBy</td>
- <td class="name">wasGeneratedBy</td>
- </tr>
- <tr>
- <td>4</td>
- <td>11, 12</td>
- <td class="name">wasDerivedFrom</td>
- <td class="name">wasGeneratedBy, used, alternateOf</td>
- </tr>
- <tr>
- <td>5</td>
- <td>16, 17, 18</td>
- <td class="name">alternateOf, entity</td>
- <td class="name">alternateOf</td>
- </tr>
- <tr>
- <td>6</td>
- <td>5, 6</td>
- <td class="name">wasInformedBy, generated, used</td>
- <td class="name">wasInformedBy, generated, used</td>
- </tr>
- <tr>
- <td>7</td>
- <td>15</td>
- <td>many</td>
- <td class="name">wasInfluencedBy</td>
- </tr>
-
- </tbody></table>
- <p>
- For each stage, we show that the stage is weakly acyclic.
- </p><ul><li>Stages 1 and 5 have no rules with existential quantifiers,
- so they are weakly acyclic.
- </li>
- <li>Stages 2, 3, 4, and 7 have no cycles among the formulas
- involved, so they are weakly acyclic.
- </li>
- <li>For stage 6, we check weak acyclicity using the algorithm
- in [<cite><a class="bibref" href="#bib-DBCONSTRAINTS">DBCONSTRAINTS</a></cite>], namely:
- <ul><li> Given a formula <span class="math">φ(x<sub>1</sub>,...,x<sub>n</sub>) ⇒
- ∃y<sub>1</sub>,...,y<sub>m</sub>. ψ(x<sub>1</sub>,...,x<sub>n</sub>,y<sub>1</sub>,...,y<sub>m</sub>)</span></li>
- <li>For every <span class="math">x</span> that occurs in <span class="math">ψ</span>, and for every
- occurrence of <span class="math">x</span> in <span class="math">φ</span> in position <span class="math">r.i</span>:
- <ol><li>For every occurrence of <span class="math">x</span> in position <span class="math">s.j</span>, add
- an edge from <span class="math">r.i</span> to <span class="math">s.j</span> (if it does
- not already exist). </li>
- <li>In addition, for every existentially quantified variable <span class="math">y</span>
- and for every occurrence of <span class="math">y</span> in <span class="math">ψ</span> in position
- <span class="math">t.k</span>, add a special edge from <span class="math">r.i</span> to <span class="math">t.k</span> (if it does
- not already exist).
- </li>
- </ol>
- </li>
- </ul>
- Weak
- acyclicity means that there is no cycle involving a special
- edge in the resulting graph. For the two inferences in stage 6,
- the following dependency graph witnesses weak
- acyclicity. The nodes <span class="name">wasGeneratedBy.i</span>,
- <span class="name">wasInformedBy.i</span>, and <span class="name">used.i</span> denote the <span class="math">i</span>th arguments
- of the corresponding predicates. The solid edges are ordinary
- edges, and the dashed edges are <em>special</em> edges.
- </li>
- </ul>
-
-
- <img src="images/constraints/weak-acyclic-6.svg" alt="Graph illustrating weak
- acyclicity of stage 6">
-
- <p><b>Termination for instances with attributes.</b>
- We can translate an instance with attributes to an alternative,
- purely relational language by introducing a relation
- <span class="name">attribute(id,a,v)</span> and replacing every statement of the form
- <span class="name">r(id;a1,...,a<sub>n</sub>,[(k<sub>1</sub>,v<sub>1</sub>),...,(k<sub>m</sub>,v<sub>m</sub>)])</span> with
- <span class="name">r(id;a1,...,a<sub>n</sub>),attribute(id,k<sub>1</sub>,v<sub>1</sub>),...,attribute(id,k<sub>m</sub>,v<sub>m</sub>)</span>,
- and similarly for <span class="name">entity</span>, <span class="name">activity</span> and <span class="name">agent</span>
- attributes. The inference rules can also be translated so as
- to work on these instances, and a similar argument to
- the above shows that inference is terminating on instances with
- explicit attributes. Any infinite
- sequence of normalization steps on the original instance would
- lead to an infinite sequence of translated normalization steps
- on instances with explicit attributes.
- </p>
-</section>
-
-
- <section class="appendix" id="change-log">
- <h2><span class="secno">B. </span><span class="insert">Change Log</span></h2>
-
-<section class="appendix" id="changes-from-candidate-recommendation-to-this-version">
- <h3><span class="secno"><span class="insert">B.1 </span></span>Changes <span class="delete">since last</span><span class="insert">from Candidate Recommendation to this</span> version</h3>
- <p> Please see the <a href="http://www.w3.org/2011/prov/wiki/ResponsesToPublicCommentsCR"><span class="insert">
- Responses to Public Comments on the Candidate Recommendation</span></a><span class="insert">
- for more details about the justification of these changes.</span></p>
-<ul>
- <li><span class="insert"> Reworded description of toplevel instance and
- bundles to provide a clearer restatement in one place (</span><a href="#purpose"><span class="insert">Sec. 1.2</span></a><span class="insert">)</span></li>
- <li><span class="insert">Fixed a number of broken links from definition references to definitions</span></li>
- <li><span class="insert">Updated the </span><a href="#sotd"><span class="insert">Status of This Document</span></a><span class="insert"> to describe proposed recommendation
- status and updated references to other PR-stage PROV documents</span></li>
- <li><span class="insert">Added clarification concerning constraint
- </span><a href="#wasAssociatedWith-ordering"><span class="insert">wasAssociatedWith-ordering</span></a><span class="insert"> (issue-615).</span></li>
- <li><span class="insert">Added underscores to some variables in inferences </span><a href="#wasStartedBy-inference"><span class="insert">9</span></a><span class="insert">, </span><a href="#wasEndedBy-inference"><span class="insert">10</span></a><span class="insert">,
- </span><a href="#influence-inference"><span class="insert">15</span></a><span class="insert"> (issue-611).</span></li>
- <li><span class="insert">Corrected a typo in the name </span><span class="name"><span class="insert">hadMember</span></span><span class="insert"> in </span><a href=""><span class="insert">constraint 56</span></a><span class="insert">
- (issue-611).
- </span></li>
- <li><span class="insert">Clarified that existential variables are scoped at the
- instance level, not statement level, thus it is correct to apply
- uniqueness constraints by substituting variables through an
- instance (issue-611). (Remark at the end of </span><a href="#concepts"><span class="insert">section
- 4. Basic concepts</span></a><span class="insert">, and clarified discussion in </span><a href="#overview"><span class="insert">Validation Process Overview</span></a><span class="insert">)</span></li>
- <li><span class="insert">Gave equivalent form of </span><a href="#optional-attributes"><span class="insert">Definition 2</span></a><span class="insert"> (issue-611).</span></li>
-</ul>
-</section>
-
- <section id="changes-from-last-call-working-draft-to-candidate-recommendation">
- <h3><span class="secno"><span class="insert">B.2 </span></span><span class="insert">Changes from Last Call Working Draft to Candidate Recommendation</span></h3>
- <p><span class="insert"> Please see the </span><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>Abstract: clarified that term "validity" is analogous to other
- notions of validity in Web standards. </li>
- <li>Added bullet point linking to PROV-SEM under "How to read the
- PROV family of specifications"</li>
- <li>Revised sec. 1.2 to clarify terminology (validity), emphasize
- that any implementation equivalent to the procedural specification
- is compliant, and clarify that treating "equivalent instances in the
- same way" is a guideline.</li>
- <li>Added paragraph to sec 2.4 to clarify the purpose of the section.</li>
- <li>Sec 2.4 Unification and Merging: changed "merging" to "unification" for terms</li>
- <li>Sec. 2.4 "Applying definitions, inferences and constraints":
- Updated merging to unification and added paragraph reinforcing that
- compliance is algorithm independent</li>
- <li>Sec. 2.4 "Checking ordering, typing and impossibility
- constraints": Avoided use of the term "satisfies".</li>
- <li>Sec. 2.4 "Equivalence and Isomorphism": Extended equivalence to
- be defined on all instances, valid or not. Removed analogy to RDF.</li>
- <li>Sec. 2.4 "From Instances to Bundles and Documents": Revised to
- avoid giving the impression that toplevel instances must be disjoint
- from bundles; removed reference to RDF.</li>
- <li>Sec. 3. Clarified and reinforced algorithm independence.</li>
- <li>Sec. 4. Added clarifying remark about role of definitions.</li>
- <li>Sec. 4. Avoided reference to RDF, minor clarifications to
- discussion of existential variables. </li>
- <li>Sec. 4.1. Spelling correction.</li>
- <li>Sec. 4.4. Merging -> unification</li>
- <li>Sec. 5. Merging -> unification terminology change. Added
- declarative definition of unification. Clarified
- procedural definition. Removed definition of merging of attribute
- lists. Updated descriptions of uniqueness and key constraint application.</li>
- <li>Constraint 23. Renamed e, a, ag to id.</li>
- <li>Sec. 5.2. Explicitly stated that strictly-precedes is irreflexive.</li>
- <li>Sec. 5.2. Spelling</li>
- <li>Sec. 5.2, just before constraint 51: updated text to accurately
- describe constraint.</li>
- <li>Sec. 6. Merging -> unification. Updated definition of validity
- to avoid referring to "satisfies". Explicitly defined isomorphism
- of instances. Broadened the definition of equivalence so that it is
- allowed to test arbitrary instances for equivalence. Reinforce the
- intention of the guideline that applications treat equivalent
- instances "in the same way".</li>
- <li>Dropped RDF as a normative reference.</li>
- <li>Made PROV-DM and PROV-N into normative references.</li>
- <li>Added "document" and "endDocument" to sec. 6.2.</li>
- <li>Added sentence of explanation of purpose to beginning.</li>
- <li>Moved "mention" to a separate note. </li>
- <li>Added <a href="#concepts">Section 4: Basic Concepts</a>.</li>
- <li>Miscellaneous final cleanup prior to CR staging.</li>
- <li><span class="insert"> Added html link to provenance.</span></li>
-</ul>
-
-</section>
-
-
-
-</section>
-
-
-<section class="appendix" id="acknowledgements">
- <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 Ivan Herman (<abbr title="World Wide Web Consortium">W3C</abbr>/<abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr>), Paul Groth, Tim Lebo, Simon Miles, Stian Soiland-Reyes, for their thorough reviews.
- </p>
-
-<p>
-The editors acknowledge valuable contributions from the following:
-Tom Baker,
-David Booth,
-Robert Freimuth,
-Satrajit Ghosh,
-Ralph Hodgson,
-Renato Iannella,
-Jacek Kopecky,
-James Leigh,
-Jacco van Ossenbruggen,
-<span class="insert">Héctor Pérez-Urbina,
-</span>Alan Ruttenberg,
-Reza Samavi,<span class="delete"> and
-</span><span class="insert">
-Evren Sirin,
-</span>Antoine Zimmermann.
-</p>
-
-<p>
-Members of the Provenance Working Group at the time of publication of this document were:
-
-Ilkay Altintas (Invited expert),
-Reza B'Far (Oracle Corporation),
-Khalid Belhajjame (University of Manchester),
-James Cheney (University of Edinburgh, School of Informatics),
-Sam Coppens <span class="delete">(IBBT),</span><span class="insert">(iMinds - Ghent University),</span>
-David Corsar (University of Aberdeen, Computing Science),
-Stephen Cresswell (The National Archives),
-Tom De Nies <span class="delete">(IBBT),</span><span class="insert">(iMinds - Ghent University),</span>
-Helena Deus (DERI Galway at the National University of Ireland, Galway, Ireland),
-Simon Dobson (Invited expert),
-Martin Doerr (Foundation for Research and Technology - Hellas(FORTH)),
-Kai Eckert (Invited expert),
-Jean-Pierre EVAIN (European Broadcasting Union, EBU-UER),
-James Frew (Invited expert),
-Irini Fundulaki (Foundation for Research and Technology - Hellas(FORTH)),
-Daniel Garijo (Universidad Politécnica de Madrid),
-Yolanda Gil (Invited expert),
-Ryan Golden (Oracle Corporation),
-Paul Groth (Vrije Universiteit),
-Olaf Hartig (Invited expert),
-David Hau (National Cancer Institute, NCI),
-Sandro Hawke (<abbr title="World Wide Web Consortium">W3C</abbr>/<abbr title="Massachusetts Institute of Technology">MIT</abbr>),
-Jörn Hees (German Research Center for Artificial Intelligence (DFKI) Gmbh),
-Ivan Herman, (<abbr title="World Wide Web Consortium">W3C</abbr>/<abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr>),
-Ralph Hodgson (TopQuadrant),
-Hook Hua (Invited expert),
-Trung Dong Huynh (University of Southampton),
-Graham Klyne (University of Oxford),
-Michael Lang (Revelytix, Inc.),
-Timothy Lebo (Rensselaer Polytechnic Institute),
-James McCusker (Rensselaer Polytechnic Institute),
-Deborah McGuinness (Rensselaer Polytechnic Institute),
-Simon Miles (Invited expert),
-Paolo Missier (School of Computing Science, Newcastle university),
-Luc Moreau (University of Southampton),
-James Myers (Rensselaer Polytechnic Institute),
-Vinh Nguyen (Wright State University),
-Edoardo Pignotti (University of Aberdeen, Computing Science),
-Paulo da Silva Pinheiro (Rensselaer Polytechnic Institute),
-Carl Reed (Open Geospatial Consortium),
-Adam Retter (Invited Expert),
-Christine Runnegar (Invited expert),
-Satya Sahoo (Invited expert),
-David Schaengold (Revelytix, Inc.),
-Daniel Schutzer (FSTC, Financial Services Technology Consortium),
-Yogesh Simmhan (Invited expert),
-Stian Soiland-Reyes (University of Manchester),
-Eric Stephan (Pacific Northwest National Laboratory),
-Linda Stewart (The National Archives),
-Ed Summers (Library of Congress),
-Maria Theodoridou (Foundation for Research and Technology - Hellas(FORTH)),
-Ted Thibodeau (OpenLink Software Inc.),
-Curt Tilmes (National Aeronautics and Space Administration),
-Craig Trim (IBM Corporation),
-Stephan Zednik (Rensselaer Polytechnic Institute),
-Jun Zhao (University of Oxford),
-Yuting Zhao (University of Aberdeen, Computing Science).
-</p>
- </section>
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-<section id="references" class="appendix"><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-DM">[PROV-DM]</dt><dd>Luc Moreau; Paolo Missier; eds. <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/"><cite>PROV-DM: The PROV Data Model</cite></a>. <span class="delete">11 December 2012,</span><span class="insert">12 March 2013,</span> W3C <span class="delete">Candidate</span><span class="insert">Proposed</span> Recommendation. URL: <span class="delete">http://www.w3.org/TR/2012/CR-prov-dm-20121211/</span><a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/"><span class="insert">http://www.w3.org/TR/2013/PR-prov-dm-20130312/</span></a>
-</dd><dt id="bib-PROV-N">[PROV-N]</dt><dd>Luc Moreau; Paolo Missier; eds. <a href="http://www.w3.org/TR/2013/PR-prov-n-20130312/"><cite>PROV-N: The Provenance Notation</cite></a>. <span class="delete">11 December 2012,</span><span class="insert">12 March 2013,</span> W3C <span class="delete">Candidate</span><span class="insert">Proposed</span> Recommendation. URL: <span class="delete">http://www.w3.org/TR/2012/CR-prov-n-20121211/</span><a href="http://www.w3.org/TR/2013/PR-prov-n-20130312/"><span class="insert">http://www.w3.org/TR/2013/PR-prov-n-20130312/</span></a>
-</dd><dt id="bib-PROV-O">[PROV-O]</dt><dd>Timothy Lebo; Satya Sahoo; Deborah McGuinness; eds. <a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/"><cite>PROV-O: The PROV Ontology</cite></a>. <span class="delete">11 December 2012,</span><span class="insert">12 March 2013,</span> W3C <span class="delete">Candidate</span><span class="insert">Proposed</span> Recommendation. URL: <span class="delete">http://www.w3.org/TR/2012/CR-prov-o-20121211/</span><a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/"><span class="insert">http://www.w3.org/TR/2013/PR-prov-o-20130312/</span></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 <span class="delete">(IRIs).</span><span class="insert">(IRIs)</span></cite></a><span class="insert">.</span> January 2005.<span class="delete"> Internet</span> RFC 3987. URL: <a href="http://www.ietf.org/rfc/rfc3987.txt">http://www.ietf.org/rfc/rfc3987.txt</a>
-
-</dd></dl></section><section id="informative-references"><h3><span class="secno">D.2 </span>Informative references</h3><dl class="bibliography"><dt id="bib-CHR">[CHR]</dt><dd>Thom Frühwirth. <a href="http://constraint-handling-rules.org/"><cite>Constraint Handling Rules</cite></a>. Cambridge University Press URL: <a href="http://constraint-handling-rules.org/">http://constraint-handling-rules.org/</a>
-</dd><dt id="bib-CLOCK">[CLOCK]</dt><dd>L. Lamport. <a href="http://research.microsoft.com/users/lamport/pubs/time-clocks.pdf"><cite>Time, clocks, and the ordering of events in a distributed system</cite></a>. Communications of the ACM 21 (7): 558–565. 1978. URL: <a href="http://research.microsoft.com/users/lamport/pubs/time-clocks.pdf">http://research.microsoft.com/users/lamport/pubs/time-clocks.pdf</a> DOI: doi:10.1145/359545.359563.
-</dd><dt id="bib-DBCONSTRAINTS">[DBCONSTRAINTS]</dt><dd> Ronald Fagin; Phokion G. Kolaitis; Renée J. Miller; Lucian Popa. <a href="http://dx.doi.org/10.1016/j.tcs.2004.10.033"><cite>Data exchange: Semantics and query answering</cite></a>. Theoretical computer science 336(1):89-124 Elsevier URL: <a href="http://dx.doi.org/10.1016/j.tcs.2004.10.033">http://dx.doi.org/10.1016/j.tcs.2004.10.033</a>
-</dd><dt id="bib-Logic">[Logic]</dt><dd>W. E. Johnson. <a href="http://www.ditext.com/johnson/intro-3.html"><cite>Logic: Part III</cite></a>.1924. URL: <a href="http://www.ditext.com/johnson/intro-3.html">http://www.ditext.com/johnson/intro-3.html</a>
-</dd><dt id="bib-PROV-AQ">[PROV-AQ]</dt><dd>Graham Klyne; Paul Groth; eds. <a href="http://www.w3.org/TR/2013/WD-prov-aq-20130312/"><cite>Provenance Access and Query</cite></a>. <span class="delete">19 June 2012,</span><span class="insert">12 March 2013,</span> Working Draft. URL: <span class="delete">http://www.w3.org/TR/2012/WD-prov-aq-20120619/</span><a href="http://www.w3.org/TR/2013/WD-prov-aq-20130312/"><span class="insert">http://www.w3.org/TR/2013/WD-prov-aq-20130312/</span></a>
-</dd><dt id="bib-PROV-DC"><span class="insert">[PROV-DC]</span></dt><dd><span class="insert">Daniel Garijo; Kai Eckert; eds. </span><a href="http://www.w3.org/TR/2013/WD-prov-dc-20130312/"><cite><span class="insert">Dublin Core to PROV Mapping</span></cite></a><span class="insert">. 12 March 2013, Working Draft. URL: </span><a href="http://www.w3.org/TR/2013/WD-prov-dc-20130312/"><span class="insert">http://www.w3.org/TR/2013/WD-prov-dc-20130312/</span></a>
-</dd><dt id="bib-PROV-DICTIONARY"><span class="insert">[PROV-DICTIONARY]</span></dt><dd><span class="insert">Tom De Nies; Sam Coppens; eds. </span><a href="http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/"><cite><span class="insert">PROV Dictionary</span></cite></a><span class="insert">. 12 March 2013, Working Draft. URL: </span><a href="http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/"><span class="insert">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/</span></a>
-</dd><dt id="bib-PROV-LINKS"><span class="insert">[PROV-LINKS]</span></dt><dd><span class="insert">Luc Moreau; Timothy Lebo; eds. </span><a href="http://www.w3.org/TR/2013/WD-prov-links-20130312/"><cite><span class="insert">Linking Across Provenance Bundles</span></cite></a><span class="insert">. 12 March 2013, Working Draft. URL: </span><a href="http://www.w3.org/TR/2013/WD-prov-links-20130312/"><span class="insert">http://www.w3.org/TR/2013/WD-prov-links-20130312/</span></a>
-</dd><dt id="bib-PROV-OVERVIEW">[PROV-OVERVIEW]</dt><dd>Paul Groth; Luc Moreau; eds. <a href="http://www.w3.org/TR/2013/WD-prov-overview-20130312/"><cite>PROV-OVERVIEW: An Overview of the PROV Family of Documents</cite></a>. <span class="delete">11 December 2012,</span><span class="insert">12 March 2013,</span> Working Draft. URL: <span class="delete">http://www.w3.org/TR/2012/WD-prov-overview-20121211/</span><a href="http://www.w3.org/TR/2013/WD-prov-overview-20130312/"><span class="insert">http://www.w3.org/TR/2013/WD-prov-overview-20130312/</span></a>
-</dd><dt id="bib-PROV-PRIMER">[PROV-PRIMER]</dt><dd>Yolanda Gil; Simon Miles; eds. <a href="http://www.w3.org/TR/2013/WD-prov-primer-20130312/"><cite>PROV Model Primer</cite></a>. <span class="delete">11 December 2012,</span><span class="insert">12 March 2013,</span> Working Draft. URL: <span class="delete">http://www.w3.org/TR/2012/WD-prov-primer-20121211/</span><a href="http://www.w3.org/TR/2013/WD-prov-primer-20130312/"><span class="insert">http://www.w3.org/TR/2013/WD-prov-primer-20130312/</span></a>
-</dd><dt id="bib-PROV-SEM">[PROV-SEM]</dt><dd>James Cheney; ed. <a href="http://www.w3.org/TR/2013/WD-prov-sem-20130312"><cite><span class="delete">Formal </span>Semantics of <span class="insert">the </span>PROV<span class="insert"> Data Model</span></cite></a>. <span class="delete">2011, Work in progress.</span><span class="insert">12 March 2013, Working Draft.</span> URL: <span class="delete">http://www.w3.org/2011/prov/wiki/FormalSemanticsED</span><a href="http://www.w3.org/TR/2013/WD-prov-sem-20130312"><span class="insert">http://www.w3.org/TR/2013/WD-prov-sem-20130312</span></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/WD-prov-xml-20130312/"><cite>PROV-XML: The PROV XML Schema</cite></a>. <span class="delete">11 December 2012,</span><span class="insert">12 March 2013,</span> Working Draft. URL: <span class="delete">http://www.w3.org/TR/2012/WD-prov-xml-20121211/</span><a href="http://www.w3.org/TR/2013/WD-prov-xml-20130312/"><span class="insert">http://www.w3.org/TR/2013/WD-prov-xml-20130312/</span></a>
-</dd></dl></section></section></body></html>
-
--- a/model/diff-n.html Mon Mar 25 15:24:00 2013 +0000
+++ b/model/diff-n.html Mon Mar 25 15:26:37 2013 +0000
@@ -1,21 +1,18 @@
-
-<!DOCTYPE html>
-<html lang="en" dir="ltr">
-<head><style type="text/css"><!--
+<style type="text/css"><!--
.insert { background-color: #aaffaa }
.delete { background-color: #ff8888; text-decoration: line-through }
.tagInsert { background-color: #007700; color: #ffffff }
.tagDelete { background-color: #770000; color: #ffffff }
---></style>
-<title>PROV-N: The Provenance Notation</title>
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+--></style>
-<link rel="http://www.w3.org/ns/prov#has_provenance" href="http://www.w3.org/2011/prov/provenance/prov-n">
-
-<style type="text/css">
+<span class="delete">PROV-N: The Provenance Notation</span>
+
+
+
+<span class="delete">
.note { font-size:small; margin-left:50px }
table.thinborder {
border-width: 1px;
@@ -36,27 +33,7 @@
border-style: solid;
border-color: gray;
}
-</style>
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+</span>
@@ -75,7 +52,7 @@
- <style type="text/css">
+ <span class="delete">
/*****************************************************************
* ReSpec CSS
* Robin Berjon (robin at berjon dot com)
@@ -225,8 +202,8 @@
margin: 1.5em 0.5em -1em 1em;
}
}
-</style>
-<style type="text/css">
+</span>
+<span class="delete">
/* --- EDITORIAL NOTES --- */
.pending {
padding: 1em;
@@ -676,8 +653,8 @@
}
-</style>
- <style>/*****************************************************************
+</span>
+ <span class="delete">/*****************************************************************
* ReSpec 3 CSS
* Robin Berjon - http://berjon.com/
*****************************************************************/
@@ -792,75 +769,75 @@
.section dl.attrs dd, .section dl.eldef dd {
margin-bottom: 0;
}
-</style><link rel="stylesheet" href="http://www.w3.org/StyleSheets/TR/W3C-PR"></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>
+</span>
+
+
+
- </p>
- <h1 class="title" id="title">PROV-N: The Provenance Notation</h1>
+
+
- <h2 id="w3c-proposed-recommendation-12-march-2013"><abbr title="World Wide Web Consortium">W3C</abbr> <span class="delete">Candidate</span><span class="insert">Proposed</span> Recommendation <span class="delete">11 December 2012</span><span class="insert">12 March 2013</span></h2>
- <dl>
+ <span class="delete">PROV-N: The Provenance Notation</span>
+
+ <span class="delete">W3C</span><span class="delete"> Proposed Recommendation 12 March 2013</span>
+
- <dt>This version:</dt>
- <dd><span class="delete">http://www.w3.org/TR/2012/CR-prov-n-20121211/</span><a href="http://www.w3.org/TR/2013/PR-prov-n-20130312/"><span class="insert">http://www.w3.org/TR/2013/PR-prov-n-20130312/</span></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>
+ <span class="delete">This version:</span>
+ <span class="delete">http://www.w3.org/TR/2013/PR-prov-n-20130312/</span>
+ <span class="delete">Latest published version:</span>
+ <span class="delete">http://www.w3.org/TR/prov-n/</span>
- <dt>Implementation report:</dt>
- <dd><span class="delete">http://dvcs.w3.org/hg/prov/raw-file/default/reports/prov-implementations.html</span><a href="http://www.w3.org/TR/2013/WD-prov-implementations-20130312/"><span class="insert">http://www.w3.org/TR/2013/WD-prov-implementations-20130312/</span></a></dd>
+ <span class="delete">Implementation report:</span>
+ <span class="delete">http://www.w3.org/TR/2013/WD-prov-implementations-20130312/</span>
- <dt>Previous version:</dt>
- <dd><span class="delete">http://www.w3.org/TR/2012/WD-prov-n-20120724/</span><a href="http://www.w3.org/TR/2012/CR-prov-n-20121211/"><span class="insert">http://www.w3.org/TR/2012/CR-prov-n-20121211/</span></a> <a href="diff-n.html">(color-coded diff)</a></dd>
+ <span class="delete">Previous version:</span>
+ <span class="delete">http://www.w3.org/TR/2012/CR-prov-n-20121211/</span> <span class="delete">(color-coded diff)</span>
- <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>
+ <span class="delete">Editors:</span>
+ <span class="delete">Luc Moreau</span><span class="delete">, University of Southampton</span>
+<span class="delete">Paolo Missier</span><span class="delete">, Newcastle University</span>
- <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>
+ <span class="delete">Contributors:</span>
+ <span class="delete">James Cheney</span><span class="delete">, University of Edinburgh</span>
+<span class="delete">Stian Soiland-Reyes</span><span class="delete">, University of Manchester</span>
- </dl>
+
- <p class="copyright">
- <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> ©
- <span class="delete">2012</span><span class="insert">2012-2013</span>
+
+ <span class="delete">Copyright</span><span class="delete"> ©
+ 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><span class="insert">, </span><a href="http://ev.buaa.edu.cn/"><span class="insert">Beihang</span></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>
+ </span><span class="delete">W3C</span><span class="delete">®</span><span class="delete">
+ (</span><span class="delete">MIT</span><span class="delete">,
+ </span><span class="delete">ERCIM</span><span class="delete">,
+ </span><span class="delete">Keio</span><span class="delete">, </span><span class="delete">Beihang</span><span class="delete">), All Rights Reserved.
+ </span><span class="delete">W3C</span> <span class="delete">liability</span><span class="delete">,
+ </span><span class="delete">trademark</span><span class="delete"> and
+ </span><span class="delete">document use</span><span class="delete"> rules apply.
+ </span>
- <hr>
-</div>
- <section id="abstract" class="introductory"><h2>Abstract</h2>
-
-<p>
+
+
+ <span class="delete">Abstract</span>
+
+<span class="delete">
Provenance is information about entities, activities, and people
involved in producing a piece of data or thing, which can be used
to form assessments about its quality, reliability or trustworthiness.
-PROV-DM is the conceptual data model that forms a basis for the <abbr title="World Wide Web Consortium">W3C</abbr>
+PROV-DM is the conceptual data model that forms a basis for the </span><span class="delete">W3C</span><span class="delete">
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.
@@ -871,141 +848,845 @@
(4) a notion of bundle, a mechanism to support provenance of provenance; and,
(5) properties to link entities that refer to the same thing;
(6) collections forming a logical structure for its members.
-</p>
-<p>To provide examples of the PROV data model, the PROV notation (PROV-N) is introduced: aimed at human consumption, PROV-N allows serializations of PROV
+</span>
+<span class="delete">To provide examples of the PROV data model, the PROV notation (PROV-N) is introduced: aimed at human consumption, PROV-N allows serializations of PROV
instances to be created in a compact manner. PROV-N facilitates the
mapping of the PROV data model to concrete syntax, and is used as the basis for a
formal semantics of PROV. The purpose of this document is to define the PROV-N notation.
-</p>
-
-<p>The <a href="http://www.w3.org/TR/2013/WD-prov-overview-20130312/">PROV Document Overview</a> describes the overall state of PROV, and should be read before other PROV documents.</p>
- </section><section id="sotd" class="introductory"><h2>Status of This Document</h2>
+</span>
+
+<span class="delete">The </span><span class="delete">PROV Document Overview</span><span class="delete"> describes the overall state of PROV, and should be read before other PROV documents.</span>
+ <span class="delete">Status of This Document</span>
- <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>
+ <span class="delete">This section describes the status of this document at the time of its publication. Other
+ documents may supersede this document. A list of current </span><span class="delete">W3C</span><span class="delete"> publications and the latest revision
+ of this technical report can be found in the </span><span class="delete">W3C</span><span class="delete"> technical reports
+ index</span><span class="delete"> at http://www.w3.org/TR/.</span>
+
+
+<span class="delete">PROV Family of Documents</span><span class="delete">
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 <span class="delete">are:
+interchange of provenance information in heterogeneous environments such as the Web. These documents are listed below. Please consult the [</span><span class="delete">PROV-OVERVIEW</span><span class="delete">] for a guide to reading these documents.
</span>
- <span class="delete">PROV-OVERVIEW</span><span class="delete"> (To be published as Note), an overview of the PROV family of documents</span><span class="insert">are listed below. Please consult the</span> [<cite><a class="bibref" href="#bib-PROV-OVERVIEW">PROV-OVERVIEW</a></cite><span class="insert">] for a guide to reading these documents.
-</span><ul>
-<li> <a href="http://www.w3.org/TR/2013/WD-prov-overview-20130312/"><span class="insert">PROV-OVERVIEW</span></a><span class="insert"> (To be published as Note), an overview of the PROV family of documents [</span><cite><a class="bibref" href="#bib-PROV-OVERVIEW"><span class="insert">PROV-OVERVIEW</span></a></cite>];</li>
-<li> <a href="http://www.w3.org/TR/2013/WD-prov-primer-20130312/">PROV-PRIMER</a> (To be published as Note), a primer for the PROV data model [<cite><a class="bibref" href="#bib-PROV-PRIMER">PROV-PRIMER</a></cite>];</li>
-<li> <a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/">PROV-O</a> <span class="delete">(Candidate</span><span class="insert">(Proposed</span> Recommendation), the PROV ontology, an OWL2 ontology allowing the mapping of PROV to RDF [<cite><a class="bibref" href="#bib-PROV-O">PROV-O</a></cite>];</li>
-<li> <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/">PROV-DM</a> <span class="delete">(Candidate</span><span class="insert">(Proposed</span> Recommendation), the PROV data model for provenance [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>];</li>
-<li> <a href="http://www.w3.org/TR/2013/PR-prov-n-20130312/">PROV-N</a> <span class="delete">(Candidate</span><span class="insert">(Proposed</span> Recommendation), a notation for provenance aimed at human consumption (this document);</li>
-<li> <a href="http://www.w3.org/TR/2013/PR-prov-constraints-20130312/">PROV-CONSTRAINTS</a> <span class="delete">(Candidate</span><span class="insert">(Proposed</span> Recommendation), a set of constraints applying to the PROV data model [<cite><a class="bibref" href="#bib-PROV-CONSTRAINTS">PROV-CONSTRAINTS</a></cite>];</li>
-<li> <a href="http://www.w3.org/TR/2013/WD-prov-xml-20130312/"><span class="insert">PROV-XML</span></a><span class="insert"> (To be published as Note), an XML schema for the PROV data model [</span><cite><a class="bibref" href="#bib-PROV-XML"><span class="insert">PROV-XML</span></a></cite><span class="insert">];</span></li>
-<li> <a href="http://www.w3.org/TR/2013/WD-prov-aq-20130312/">PROV-AQ</a> (To be published as Note), the mechanisms for accessing and querying provenance [<cite><a class="bibref" href="#bib-PROV-AQ">PROV-AQ</a></cite>]; </li>
-<li> <span class="delete">PROV-XML</span><a href="http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/"><span class="insert">PROV-DICTIONARY</span></a> (To be published as <span class="delete">Note), an XML schema for the PROV data model</span><span class="insert">Note) introduces a specific type of collection, consisting of key-entity pairs</span> [<cite><span class="delete">PROV-XML</span><a class="bibref" href="#bib-PROV-DICTIONARY"><span class="insert">PROV-DICTIONARY</span></a></cite><span class="insert">];</span></li>
-<li> <a href="http://www.w3.org/TR/2013/WD-prov-dc-20130312/"><span class="insert">PROV-DC</span></a><span class="insert"> (To be published as Note) provides a mapping between PROV and Dublic Core Terms [</span><cite><a class="bibref" href="#bib-PROV-DC"><span class="insert">PROV-DC</span></a></cite><span class="insert">];</span></li>
-<li> <a href="http://www.w3.org/TR/2013/WD-prov-sem-20130312/"><span class="insert">PROV-SEM</span></a><span class="insert"> (To be published as Note), a declarative specification in terms of first-order logic of the PROV data model [</span><cite><a class="bibref" href="#bib-PROV-SEM"><span class="insert">PROV-SEM</span></a></cite><span class="insert">];</span></li>
-<li> <a href="http://www.w3.org/TR/2013/WD-prov-links-20130312/"><span class="insert">PROV-LINKS</span></a><span class="insert"> (To be published as Note) introduces a mechanism to link across bundles [</span><cite><a class="bibref" href="#bib-PROV-LINKS"><span class="insert">PROV-LINKS</span></a></cite>].</li>
-</ul>
-
-<span class="delete">How to read the PROV Family of Documents</span>
-
-<span class="delete">[</span><span class="delete">PROV-OVERVIEW</span><span class="delete">] overviews the PROV family of documents. </span>
-<span class="delete">The primer [</span><span class="delete">PROV-PRIMER</span><span class="delete">] is the entry point to PROV offering an introduction to the provenance model.</span>
-<span class="delete">The Linked Data and Semantic Web community should focus on [</span><span class="delete">PROV-O</span><span class="delete">] defining PROV classes and properties specified in an OWL2 ontology. For further details, [</span><span class="delete">PROV-DM</span><span class="delete">] and [</span><span class="delete">PROV-CONSTRAINTS</span><span class="delete">] specify the constraints applicable to the data model, and its interpretation. </span>
-<span class="delete">The XML community should focus on [</span><span class="delete">PROV-XML</span><span class="delete">] defining an XML schema for PROV. Further details can also be found in [</span><span class="delete">PROV-DM</span><span class="delete">] and [</span><span class="delete">PROV-CONSTRAINTS</span><span class="delete">].</span>
-<span class="delete">Developers seeking to retrieve or publish provenance should focus on [</span><span class="delete">PROV-AQ</span><span class="delete">].</span>
-<span class="delete">Readers seeking to implement other PROV serializations
-should focus on [</span><span class="delete">PROV-DM</span><span class="delete">] and [</span><span class="delete">PROV-CONSTRAINTS</span><span class="delete">]. [</span><span class="delete">PROV-O</span><span class="delete">], PROV-N, and [</span><span class="delete">PROV-XML</span><span class="delete">] offer examples of mapping to RDF, text, and XML, respectively.</span>
-
-
-<h4 id="w3c-members-please-review-by-09-april-2013"><abbr title="World Wide Web Consortium"><span class="insert">W3C</span></abbr><span class="insert"> Members </span>Please <span class="delete">Comment</span><span class="insert">Review</span> By <span class="delete">January 31,</span><span class="insert">09 April</span> 2013</h4>
-
-<p>The<span class="delete"> Provenance Working Group seeks to gather experience from </span><span class="delete">implementations</span><span class="delete"> in order to increase confidence in the specifications and meet specific </span><span class="delete">exit criteria</span><span class="delete">. This document will remain a Candidate Recommendation until at least 31 January 31, 2013. After that date, when and if the exit criteria are met, the group intends to request </span><span class="delete">Proposed Recommendation</span><span class="delete"> status.
-
-
- </span><span class="delete">
- This document was published by the </span><span class="delete">Provenance Working Group</span><span class="delete"> as a Candidate Recommendation.
+ <span class="delete">PROV-OVERVIEW</span><span class="delete"> (To be published as Note), an overview of the PROV family of documents [</span><span class="delete">PROV-OVERVIEW</span><span class="delete">];</span>
+ <span class="delete">PROV-PRIMER</span><span class="delete"> (To be published as Note), a primer for the PROV data model [</span><span class="delete">PROV-PRIMER</span><span class="delete">];</span>
+ <span class="delete">PROV-O</span><span class="delete"> (Proposed Recommendation), the PROV ontology, an OWL2 ontology allowing the mapping of PROV to RDF [</span><span class="delete">PROV-O</span><span class="delete">];</span>
+ <span class="delete">PROV-DM</span><span class="delete"> (Proposed Recommendation), the PROV data model for provenance [</span><span class="delete">PROV-DM</span><span class="delete">];</span>
+ <span class="delete">PROV-N</span><span class="delete"> (Proposed Recommendation), a notation for provenance aimed at human consumption (this document);</span>
+ <span class="delete">PROV-CONSTRAINTS</span><span class="delete"> (Proposed Recommendation), a set of constraints applying to the PROV data model [</span><span class="delete">PROV-CONSTRAINTS</span><span class="delete">];</span>
+ <span class="delete">PROV-XML</span><span class="delete"> (To be published as Note), an XML schema for the PROV data model [</span><span class="delete">PROV-XML</span><span class="delete">];</span>
+ <span class="delete">PROV-AQ</span><span class="delete"> (To be published as Note), the mechanisms for accessing and querying provenance [</span><span class="delete">PROV-AQ</span><span class="delete">]; </span>
+ <span class="delete">PROV-DICTIONARY</span><span class="delete"> (To be published as Note) introduces a specific type of collection, consisting of key-entity pairs [</span><span class="delete">PROV-DICTIONARY</span><span class="delete">];</span>
+ <span class="delete">PROV-DC</span><span class="delete"> (To be published as Note) provides a mapping between PROV and Dublic Core Terms [</span><span class="delete">PROV-DC</span><span class="delete">];</span>
+ <span class="delete">PROV-SEM</span><span class="delete"> (To be published as Note), a declarative specification in terms of first-order logic of the PROV data model [</span><span class="delete">PROV-SEM</span><span class="delete">];</span>
+ <span class="delete">PROV-LINKS</span><span class="delete"> (To be published as Note) introduces a mechanism to link across bundles [</span><span class="delete">PROV-LINKS</span><span class="delete">].</span>
+
+
+<span class="delete">W3C</span><span class="delete"> Members Please Review By 09 April 2013</span>
+
+<span class="delete">The </span><span class="delete">W3C</span><span class="delete"> Director seeks review and feedback from </span><span class="delete">W3C</span><span class="delete"> Advisory Committee representatives by 09 April 2013. This will allow the Director to assess consensus and determine whether to issue this document as a </span><span class="delete">W3C</span><span class="delete"> Recommendation.</span>
+
+<span class="delete">Others are encouraged by the Provenance Working Group to continue to send reports of implementation experience, and other feedback, to
+</span><span class="delete">public-prov-comments@w3.org</span><span class="delete">
+ (</span><span class="delete">subscribe</span><span class="delete">,
+ </span><span class="delete">archives</span><span class="delete">). Open discussion among developers is also welcome at
+</span><span class="delete">public-prov-comments@w3.org</span><span class="delete">
+ (</span><span class="delete">subscribe</span><span class="delete">,
+ </span><span class="delete">archives</span><span class="delete">).</span>
+
+ <span class="delete">
+ This document was published by the </span><span class="delete">Provenance Working Group</span><span class="delete"> as a Proposed Recommendation.
- This document is intended to become a</span> <abbr title="World Wide Web Consortium">W3C</abbr> <span class="insert">Director seeks review and feedback from </span><abbr title="World Wide Web Consortium"><span class="insert">W3C</span></abbr><span class="insert"> Advisory Committee representatives by 09 April 2013. This will allow the Director to assess consensus and determine whether to issue this document as a </span><abbr title="World Wide Web Consortium"><span class="insert">W3C</span></abbr> Recommendation.<span class="delete">
-
- If you wish</span></p>
-
-<p><span class="insert">Others are encouraged by the Provenance Working Group</span> to <span class="delete">make comments regarding this document, please</span><span class="insert">continue to</span> send <span class="delete">them</span><span class="insert">reports of implementation experience, and other feedback,</span> 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>).
-
-
- <span class="insert"> Open discussion among developers is also welcome at
-</span><a href="mailto:public-prov-comments@w3.org"><span class="insert">public-prov-comments@w3.org</span></a><span class="insert">
- (</span><a href="mailto:public-prov-comments-request@w3.org?subject=subscribe"><span class="insert">subscribe</span></a><span class="insert">,
- </span><a href="http://lists.w3.org/Archives/Public/public-prov-comments/"><span class="insert">archives</span></a><span class="insert">).</span></p>
-
- <p><span class="insert">
- This document was published by the </span><a href="http://www.w3.org/2011/prov/"><span class="insert">Provenance Working Group</span></a><span class="insert"> as a Proposed Recommendation.
-
- This document is intended to become a </span><abbr title="World Wide Web Consortium">W3C</abbr> <span class="delete">publishes a Candidate Recommendation </span><span class="insert">Recommendation.
+ This document is intended to become a </span><span class="delete">W3C</span><span class="delete"> Recommendation.
- The </span><abbr title="World Wide Web Consortium"><span class="insert">W3C</span></abbr><span class="insert"> Membership and other interested parties are invited
- </span>to <span class="delete">indicate</span><span class="insert">review the document and send comments to
-
- </span><a href="mailto:public-prov-comments@w3.org"><span class="insert">public-prov-comments@w3.org</span></a><span class="insert">
- (</span><a href="mailto:public-prov-comments-request@w3.org?subject=subscribe"><span class="insert">subscribe</span></a><span class="insert">,
- </span><a href="http://lists.w3.org/Archives/Public/public-prov-comments/"><span class="insert">archives</span></a><span class="insert">)
+ The </span><span class="delete">W3C</span><span class="delete"> Membership and other interested parties are invited
+ to review the document and send comments to
+
+ </span><span class="delete">public-prov-comments@w3.org</span><span class="delete">
+ (</span><span class="delete">subscribe</span><span class="delete">,
+ </span><span class="delete">archives</span><span class="delete">)
through 09 April 2013.
Advisory Committee Representatives should consult their
- </span><a href="https://www.w3.org/2002/09/wbs/myQuestionnaires"><span class="insert">WBS questionnaires</span></a><span class="insert">.
- Note</span> that <span class="delete">the document is believed
- to be stable and to encourage implementation by the developer community. This
- Candidate Recommendation is</span><span class="insert">substantive technical comments were</span> expected <span class="delete">to advance to Proposed Recommendation no earlier than
- 31 January 2013.
-
- All feedback is welcome.</span><span class="insert">during the Last Call review period that ended 18 September 2012.</span>
- </p>
-
-
+ </span><span class="delete">WBS questionnaires</span><span class="delete">.
+ Note that substantive technical comments were expected during the Last Call review period that ended 18 September 2012.
+ </span>
- <p>
- Publication as a <span class="delete">Candidate</span><span class="insert">Proposed</span> Recommendation does not imply endorsement by the <abbr title="World Wide Web Consortium">W3C</abbr> Membership.
+ <span class="delete">
+ Publication as a Proposed Recommendation does not imply endorsement by the </span><span class="delete">W3C</span><span class="delete"> Membership.
This is a draft document and may be updated, replaced or obsoleted by other documents at
any time. It is inappropriate to cite this document as other than work in progress.
- </p>
+ </span>
- <p>
+ <span class="delete">
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>.
+ </span><span class="delete">5 February 2004 </span><span class="delete">W3C</span><span class="delete"> Patent Policy</span><span class="delete">.
- <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>
+ </span><span class="delete">W3C</span><span class="delete"> maintains a </span><span class="delete">public list of any patent disclosures</span><span class="delete">
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>.
+ </span><span class="delete">Essential Claim(s)</span><span class="delete"> must disclose the
+ information in accordance with </span><span class="delete">section
+ 6 of the </span><span class="delete">W3C</span><span class="delete"> Patent Policy</span><span class="delete">.
- </p>
+ </span>
-</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><span class="insert">Change Log</span></a><ul class="toc"><li class="tocline"><a href="#changes-since-candidate-recommendation" class="tocxref"><span class="secno"><span class="insert">A.1 </span></span>Changes since <span class="insert">Candidate Recommendation</span></a></li><li class="tocline"><a href="#changes-since-last-call" class="tocxref"><span class="secno"><span class="insert">A.2 </span></span><span class="insert">Changes since </span>last <span class="delete">version</span><span class="insert">call</span></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>
+<span class="delete">Table of Contents</span><span class="delete">1. </span><span class="delete">Introduction</span><span class="delete">1.1 </span><span class="delete">Purpose of this Document and Target Audience</span><span class="delete">1.2 </span><span class="delete">Compliance with this Document</span><span class="delete">1.3 </span><span class="delete">Structure of this Document</span><span class="delete">1.4 </span><span class="delete">Notational Conventions</span><span class="delete">2. </span><span class="delete">General grammar considerations</span><span class="delete">2.1 </span><span class="delete">Functional-style Syntax</span><span class="delete">2.2 </span><span class="delete">EBNF Grammar</span><span class="delete">2.3 </span><span class="delete">Main Productions</span><span class="delete">2.4 </span><span class="delete">Optional terms in expressions</span><span class="delete">2.5 </span><span class="delete">Identifiers and attributes</span><span class="delete">2.6 </span><span class="delete">Comments</span><span class="delete">3. </span><span class="delete">PROV-N Productions per Component</span><span class="delete">3.1 </span><span class="delete">Component 1: Entities and Activities</span><span class="delete">3.1.1 </span><span class="delete">Entity</span><span class="delete">3.1.2 </span><span class="delete">Activity</span><span class="delete">3.1.3 </span><span class="delete">Generation</span><span class="delete">3.1.4 </span><span class="delete">Usage</span><span class="delete">3.1.5 </span><span class="delete">Communication</span><span class="delete">3.1.6 </span><span class="delete">Start</span><span class="delete">3.1.7 </span><span class="delete">End</span><span class="delete">3.1.8 </span><span class="delete">Invalidation</span><span class="delete">3.2 </span><span class="delete">Component 2: Derivations</span><span class="delete">3.2.1 </span><span class="delete">Derivation</span><span class="delete">3.2.2 </span><span class="delete">Revision</span><span class="delete">3.2.3 </span><span class="delete">Quotation</span><span class="delete">3.2.4 </span><span class="delete">Primary Source</span><span class="delete">3.3 </span><span class="delete">Component 3: Agents, Responsibility, and Influence</span><span class="delete">3.3.1 </span><span class="delete">Agent</span><span class="delete">3.3.2 </span><span class="delete">Attribution</span><span class="delete">3.3.3 </span><span class="delete">Association</span><span class="delete">3.3.4 </span><span class="delete">Delegation</span><span class="delete">3.3.5 </span><span class="delete">Influence</span><span class="delete">3.4 </span><span class="delete">Component 4: Bundles</span><span class="delete">3.4.1 </span><span class="delete">Bundle Constructor</span><span class="delete">3.4.2 </span><span class="delete">Bundle Type</span><span class="delete">3.5 </span><span class="delete">Component 5: Alternate Entities</span><span class="delete">3.5.1 </span><span class="delete">Alternate</span><span class="delete">3.5.2 </span><span class="delete">Specialization</span><span class="delete">3.6 </span><span class="delete">Component 6: Collections</span><span class="delete">3.6.1 </span><span class="delete">Collection</span><span class="delete">3.6.2 </span><span class="delete">Membership</span><span class="delete">3.7 </span><span class="delete">Further Expressions</span><span class="delete">3.7.1 </span><span class="delete">Identifier</span><span class="delete">3.7.2 </span><span class="delete">Attribute</span><span class="delete">3.7.3 </span><span class="delete">Literal</span><span class="delete">3.7.3.1 </span><span class="delete">Reserved Type Values</span><span class="delete">3.7.3.2 </span><span class="delete">Time Values</span><span class="delete">3.7.4 </span><span class="delete">Namespace Declaration</span><span class="delete">3.7.5 </span><span class="delete">Summary of additional semantic rules</span><span class="delete">4. </span><span class="delete">Document</span><span class="delete">5. </span><span class="delete">Extensibility</span><span class="delete">6. </span><span class="delete">Media Type</span><span class="delete">A. </span><span class="delete">Change Log</span><span class="delete">A.1 </span><span class="delete">Changes since Candidate Recommendation</span><span class="delete">A.2 </span><span class="delete">Changes since last call</span><span class="delete">B. </span><span class="delete">Acknowledgements</span><span class="delete">C. </span><span class="delete">References</span><span class="delete">C.1 </span><span class="delete">Normative references</span><span class="delete">C.2 </span><span class="delete">Informative references</span>
+
+
+
+
+
+
+
+
+<span class="delete">1. </span><span class="delete">Introduction</span>
+
+<span class="delete"> 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 [</span><span class="delete">PROV-DM</span><span class="delete">] and a set of constraints that provenance descriptions are expected to satisfy [</span><span class="delete">PROV-CONSTRAINTS</span><span class="delete">].
+</span>
+
+
+<span class="delete">1.1 </span><span class="delete">Purpose of this Document and Target Audience</span><span class="delete">
+
+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.
+
+
+
+With these two requirements in mind, this document introduces PROV-N, the PROV notation, a syntax designed to write instances of the PROV data model according to the following design principles:
+</span>
+<span class="delete">Technology independence. PROV-N provides a simple syntax that can be mapped to several technologies.
+
+</span><span class="delete">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
+
+</span><span class="delete">Formality. PROV-N is defined through a formal grammar amenable to be used with parser generators.
+
+ </span><span class="delete">
+
+PROV-N has several known uses:
+</span>
+<span class="delete"> It is the notation used in the examples found in [</span><span class="delete">PROV-DM</span><span class="delete">], as well as in the definition of PROV constraints [</span><span class="delete">PROV-CONSTRAINTS</span><span class="delete">]; </span>
+<span class="delete"> It is a source language for the encoding of PROV data model instances into a variety of target languages, including amongst others RDF [</span><span class="delete">PROV-RDF</span><span class="delete">] and XML [</span><span class="delete">PROV-XML</span><span class="delete">]; </span>
+<span class="delete"> It provides the basis for a formal semantics of the PROV data model [</span><span class="delete">PROV-SEM</span><span class="delete">], in which an interpretation is given to each element of the PROV-N language.
+</span>
+
+<span class="delete">This document introduces the PROV-N grammar along with examples of its usage.</span>
+<span class="delete">Its target audience is twofold:
+</span>
+<span class="delete">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
+</span><span class="delete">document</span><span class="delete">.</span>
+<span class="delete">Readers of the [</span><span class="delete">PROV-DM</span><span class="delete">] and of [</span><span class="delete">PROV-CONSTRAINTS</span><span class="delete">] 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 </span><span class="delete">expression</span><span class="delete"> nonterminal a useful entry point into the grammar.</span>
+
+
+
+
+
+<span class="delete">1.2 </span><span class="delete">Compliance with this Document</span>
+
+
+<span class="delete">For the purpose of compliance, all sections of this document are normative, except
+</span><span class="delete">Appendix A</span><span class="delete">,
+</span><span class="delete">Appendix B</span><span class="delete">, and
+</span><span class="delete">Appendix C.2</span><span class="delete">.
+</span>
+<span class="delete"> Information in tables is normative. </span>
+<span class="delete"> Text in boxes labeled "Example" is informative.
+</span><span class="delete"> Productions (displayed in boxes) are normative, as opposed to the separate </span><span class="delete">file</span><span class="delete"> grouping all productions for convenience of programmers, which is informative.
+</span>
+
+
+
+
+<span class="delete">1.3 </span><span class="delete">Structure of this Document</span>
+
+<span class="delete">This document is structured as follows.
+
+</span><span class="delete">Section 2</span><span class="delete"> provides general consideration about the PROV-N grammar.</span>
+
+<span class="delete">Section 3</span><span class="delete"> presents the grammar of all expressions of the language grouped according to the PROV data model components.</span>
+
+<span class="delete">Section 4</span><span class="delete"> defines the grammar of document, a house-keeping construct of PROV-N capable of packaging up PROV-N expressions and namespace declarations.</span>
+
+<span class="delete">Section 5</span><span class="delete"> defines the extensibility mechanism for the PROV-N notation.</span>
+
+<span class="delete">Section 6</span><span class="delete"> defines media type for the PROV-N notation.</span>
+
+
+
+
+
+
+ <span class="delete">1.4 </span><span class="delete">Notational Conventions</span>
+
+
+<span class="delete">The key words "</span><span class="delete">MUST</span><span class="delete">", "</span><span class="delete">MUST NOT</span><span class="delete">", "</span><span class="delete">REQUIRED</span><span class="delete">", "</span><span class="delete">SHALL</span><span class="delete">", "</span><span class="delete">SHALL
+ NOT</span><span class="delete">", "</span><span class="delete">SHOULD</span><span class="delete">", "</span><span class="delete">SHOULD NOT</span><span class="delete">", "</span><span class="delete">RECOMMENDED</span><span class="delete">", "</span><span class="delete">MAY</span><span class="delete">", and
+ "</span><span class="delete">OPTIONAL</span><span class="delete">" in this document are to be interpreted as described in
+ [</span><span class="delete">RFC2119</span><span class="delete">].</span>
+
+
+
+
+<span class="delete">
+The following namespaces prefixes are used throughout this document.
+
+</span>
+
+<span class="delete">Table 1: Prefix and Namespaces used in this specification</span>
+<span class="delete">prefix</span><span class="delete">namespace uri</span> <span class="delete">definition</span>
+<span class="delete">prov</span><span class="delete">http://www.w3.org/ns/prov#</span><span class="delete">The PROV namespace (see Section </span><span class="delete">3.7.4</span><span class="delete">)</span>
+<span class="delete">xsd</span><span class="delete">http://www.w3.org/2000/10/XMLSchema#</span><span class="delete">XML Schema Namespace [</span><span class="delete">XMLSCHEMA11-2</span><span class="delete">]</span>
+<span class="delete">(others)</span><span class="delete">(various)</span><span class="delete">All other namespace prefixes are used in examples only. </span><span class="delete"> In particular, URIs starting with "http://example.com" represent</span><span class="delete"> some application-dependent URI [</span><span class="delete">RFC3986</span><span class="delete">]</span>
+
+
+
+
+
+
+
+
+<span class="delete">2. </span><span class="delete">General grammar considerations</span>
+
+<span class="delete">For convenience, all productions presented in this document have been grouped in a
+separate </span><span class="delete">file</span><span class="delete">.</span>
+
+
+<span class="delete">2.1 </span><span class="delete">Functional-style Syntax</span>
+
+<span class="delete"> PROV-N adopts a functional-style syntax consisting of a predicate name and an ordered list of terms.</span>
+
+<span class="delete">
+All PROV data model types have an identifier. Furthermore, some expressions also admit additional elements that further characterize it. </span>
+<span class="delete">Example 1</span>
+<span class="delete">The following expression should be read as "entity </span><span class="delete">e1</span><span class="delete">".
+</span><span class="delete">entity(e1)
+</span>
+
+<span class="delete">Example 2</span>
+<span class="delete">The following expression should be read as "activity </span><span class="delete">a2</span><span class="delete">, which occurred
+between </span><span class="delete">2011-11-16T16:00:00</span><span class="delete"> and </span><span class="delete">2011-11-16T16:00:01</span><span class="delete">".
+</span><span class="delete">entity(e1)
+activity(a2, 2011-11-16T16:00:00, 2011-11-16T16:00:01)
+</span>
+
+
+<span class="delete">
+All PROV data model relations involve two primary elements, the </span><span class="delete">subject</span><span class="delete"> and the </span><span class="delete">object</span><span class="delete">, in this order. Furthermore, some expressions also admit additional elements that further characterize it.
+</span><span class="delete">Example 3</span>
+<span class="delete">The following expression should be read as "</span><span class="delete">e2</span><span class="delete"> was derived from </span><span class="delete">e1</span><span class="delete">". Here </span><span class="delete">e2</span><span class="delete"> is the subject, and </span><span class="delete">e1</span><span class="delete"> is the object.
+</span><span class="delete">wasDerivedFrom(e2, e1)
+</span>
+
+
+<span class="delete">Example 4</span>
+<span class="delete">The following expression expands the above derivation relation by providing
+additional elements the optional activity </span><span class="delete">a</span><span class="delete">, the generation </span><span class="delete">g2</span><span class="delete">, and the usage </span><span class="delete">u1</span><span class="delete">:
+</span><span class="delete">wasDerivedFrom(e2, e1, a, g2, u1)
+</span>
+
+
+
+
+
+<span class="delete">2.2 </span><span class="delete">EBNF Grammar</span>
+
+<span class="delete">The grammar is specified using a subset of the Extended Backus-Naur
+Form (EBNF) notation, as defined in Extensible Markup Language (XML) 1.1
+[</span><span class="delete">XML11</span><span class="delete">] section </span><span class="delete">6
+Notation</span><span class="delete">.
+</span>
+
+<span class="delete">
+The text below provides an introduction to the EBNF notation used in
+this document.</span>
+
+
+<span class="delete">
+ EBNF specifies a series of production rules (</span><span class="delete">production</span><span class="delete">).
+A production rule in the grammar defines a symbol
+ </span><span class="delete">expr</span><span class="delete"> (</span><span class="delete">nonterminal symbol</span><span class="delete">)
+ using the following form:</span>
+
+
+
+ <span class="delete">expr</span><span class="delete"> ::= </span><span class="delete">term</span>
+
+<span class="delete">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
+ </span><span class="delete"><TERMINAL></span><span class="delete"> (</span><span class="delete">terminal symbol</span><span class="delete">)
+ using the following form:</span>
+
+ <span class="delete"><TERMINAL></span><span class="delete"> ::= </span><span class="delete">term</span>
+
+
+
+
+
+
+<span class="delete">Within the term on the right-hand side of a rule, the following
+</span><span class="delete">term</span><span class="delete">s are used to match strings of one or more characters:
+</span>
+
+ <span class="delete">expr</span><span class="delete">: matches production for nonterminal symbol </span><span class="delete">expr</span>
+
+
+
+
+ <span class="delete">TERMINAL</span><span class="delete">: matches production for terminal symbol </span><span class="delete">TERMINAL</span>
+
+
+
+ <span class="delete">"abc"</span><span class="delete">: matches the literal string inside the single quotes.
+</span>
+
+
+
+ <span class="delete">(term)?</span><span class="delete">: optional, matches </span><span class="delete">term</span><span class="delete"> or nothing.
+</span>
+
+
+ <span class="delete">(term)+</span><span class="delete">: matches one or more occurrences of </span><span class="delete">term</span><span class="delete">.
+</span>
+
+
+ <span class="delete">(term)*</span><span class="delete">: matches zero or more occurrences of </span><span class="delete">term</span><span class="delete">.
+</span>
+
+
+ <span class="delete">(term | term)</span><span class="delete">: matches one of the two </span><span class="delete">terms</span><span class="delete">.
+</span>
+
+
+
+
+<span class="delete">Where suitable, the PROV-N grammar reuses production and terminal names of the SPARQL grammar [</span><span class="delete">RDF-SPARQL-QUERY</span><span class="delete">].</span>
+
+
+
+
+<span class="delete">2.3 </span><span class="delete">Main Productions</span>
+
+<span class="delete">Two productions are entry points to the grammar.</span>
+
+<span class="delete">The production </span><span class="delete">expression</span><span class="delete">
+provides the structure for the </span><span class="delete">core expressions</span><span class="delete"> of PROV-N.
+
+
+
+
+</span>
+ <span class="delete">[</span><span class="delete">2</span><span class="delete">] </span> <span class="delete">expression</span> <span class="delete"> ::= </span> <span class="delete">( </span><span class="delete">entityExpression</span><span class="delete"> | </span><span class="delete">activityExpression</span><span class="delete"> | </span><span class="delete">generationExpression</span><span class="delete"> | </span><span class="delete">usageExpression</span><span class="delete"> | </span><span class="delete">startExpression</span><span class="delete"> | </span><span class="delete">endExpression</span><span class="delete"> | </span><span class="delete">invalidationExpression</span><span class="delete"> | </span><span class="delete">communicationExpression</span><span class="delete"> | </span><span class="delete">agentExpression</span><span class="delete"> | </span><span class="delete">associationExpression</span><span class="delete"> | </span><span class="delete">attributionExpression</span><span class="delete"> | </span><span class="delete">delegationExpression</span><span class="delete"> | </span><span class="delete">derivationExpression</span><span class="delete"> | </span><span class="delete">influenceExpression</span><span class="delete"> | </span><span class="delete">alternateExpression</span><span class="delete"> | </span><span class="delete">specializationExpression</span><span class="delete"> | </span><span class="delete">membershipExpression</span><span class="delete"> | </span><span class="delete">extensibilityExpression</span><span class="delete"> )</span>
+
+
+
+<span class="delete">Each of the symbols included in </span><span class="delete">expression</span><span class="delete"> above, i.e., </span><span class="delete">entityExpression</span><span class="delete">, </span><span class="delete">activityExpression</span><span class="delete"> etc., corresponds to one concept (e.g., Entity, Activity, etc.) of the PROV data model.</span>
+
+
+<span class="delete">Alternatively, the production rule </span><span class="delete">document</span><span class="delete">
+provides the overall structure of PROV-N descriptions. It is a wrapper for
+ a set of expressions, such that the text for an element matches the corresponding </span><span class="delete">expression</span><span class="delete"> production, and some namespace declarations.</span>
+
+
+
+
+
+<span class="delete">2.4 </span><span class="delete">Optional terms in expressions</span><span class="delete">
+
+Some terms in an expression may be optional. For example:
+
+</span><span class="delete">Example 5</span>
+<span class="delete">wasDerivedFrom(e2, e1, a, g2, u1)
+wasDerivedFrom(e2, e1)
+</span><span class="delete">
+In a derivation expression, the activity, generation, and usage are optional terms. They are specified in the first derivation, but not in the second.
+</span>
+
+<span class="delete">Example 6</span>
+<span class="delete">activity(a2, 2011-11-16T16:00:00, 2011-11-16T16:00:01)
+activity(a1)
+</span><span class="delete">
+The start and end times for an activity are optional. They are specified in the first expression, but not in the second.
+</span>
+
+<span class="delete">The general rule for optionals is that, if </span><span class="delete">none</span><span class="delete"> of the optionals are used in the expression, then they are simply omitted, resulting in a simpler expression as in the examples above.</span><span class="delete">
+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><span class="delete">'-'</span><span class="delete"> is used for this purpose.
+
+</span><span class="delete">Example 7</span>
+<span class="delete">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.
+
+</span><span class="delete">wasDerivedFrom(e2, e1, a, g2, u1)
+wasDerivedFrom(e2, e1, -, -, u1)
+wasDerivedFrom(e2, e1, a, -, -)
+</span>
+<span class="delete">
+Note that the more succinct form is just shorthand for a complete expression with all the markers specified:
+</span><span class="delete">Example 8</span>
+<span class="delete">activity(a1)
+activity(a1, -, -)
+</span>
+
+
+
+
+
+
+<span class="delete">2.5 </span><span class="delete">Identifiers and attributes</span>
+
+<span class="delete">Almost all expressions defined in the grammar include an identifier (see </span><span class="delete">Section 3.7.1</span><span class="delete"> 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. </span><span class="delete">Optional</span><span class="delete"> identifiers </span><span class="delete">MUST</span><span class="delete"> be separated using a semi-colon ';', but where the identifiers are required, a regular comma ',' </span><span class="delete">MUST</span><span class="delete"> 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.</span>
+
+<span class="delete">Example 9</span>
+<span class="delete">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><span class="delete">-</span><span class="delete"> marker. This is equivalent to the first expression. </span>
+<span class="delete">wasDerivedFrom(e2, e1)
+wasDerivedFrom(d; e2, e1)
+wasDerivedFrom(-; e2, e1)
+</span>
+<span class="delete">
+
+Lack of attributes can be equivalently expressed by omitting the list, or by using an empty list.
+
+
+
+</span><span class="delete">Example 10</span>
+<span class="delete">The first and second activity expressions do not specify any attributes, and are equivalent.
+
+The third activity expression specifies two attributes.
+</span><span class="delete">activity(ex:a1)
+activity(ex:a1, [])
+activity(ex:a1, [ex:param1="a", ex:param2="b"])
+</span>
+
+
+
+
+
+<span class="delete">2.6 </span><span class="delete">Comments</span><span class="delete">
+
+
+Comments in PROV-N take two forms:
+</span>
+<span class="delete"> '//' outside an </span><span class="delete">IRI_REF</span><span class="delete"> or </span><span class="delete">STRING_LITERAL</span><span class="delete">; 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.
+
+</span><span class="delete"> '/*' ... '*/', outside an </span><span class="delete">IRI_REF</span><span class="delete"> or </span><span class="delete">STRING_LITERAL</span><span class="delete">.
+</span>
+<span class="delete">Comments are treated as white space.</span>
+
+
+
+
+
+
+<span class="delete">3. </span><span class="delete">PROV-N Productions per Component</span>
+
+<span class="delete">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.</span>
+
+
+<span class="delete">3.1 </span><span class="delete">Component 1: Entities and Activities</span>
+
+
+<span class="delete">3.1.1 </span><span class="delete">Entity</span>
+
+
+
+
+
+ <span class="delete">[</span><span class="delete">3</span><span class="delete">] </span> <span class="delete">entityExpression</span> <span class="delete"> ::= </span> <span class="delete">"entity" "(" </span><span class="delete">identifier</span> <span class="delete">optionalAttributeValuePairs</span><span class="delete"> ")"</span>
+ <span class="delete">[</span><span class="delete">4</span><span class="delete">] </span> <span class="delete">optionalAttributeValuePairs</span> <span class="delete"> ::= </span> <span class="delete">( "," "[" </span><span class="delete">attributeValuePairs</span><span class="delete"> "]" )?</span>
+ <span class="delete">[</span><span class="delete">5</span><span class="delete">] </span> <span class="delete">attributeValuePairs</span> <span class="delete"> ::= </span> <span class="delete">( | </span><span class="delete">attributeValuePair</span><span class="delete"> ( "," </span><span class="delete">attributeValuePair</span><span class="delete"> )* )</span>
+ <span class="delete">[</span><span class="delete">6</span><span class="delete">] </span> <span class="delete">attributeValuePair</span> <span class="delete"> ::= </span> <span class="delete">attribute</span><span class="delete"> "=" </span><span class="delete">literal</span>
+
+
+
+<span class="delete">The following table summarizes how each constituent of a PROV-DM Entity maps to a PROV-N syntax element.</span>
+
+
+<span class="delete">Entity</span><span class="delete">Non-Terminal</span>
+
+<span class="delete">id</span><span class="delete">identifier</span>
+<span class="delete">attributes</span><span class="delete">optionalAttributeValuePairs</span>
+
+
+
+
+
+<span class="delete">Example 11</span>
+<span class="delete">entity(tr:WD-prov-dm-20111215, [ prov:type="document" ])
+</span><span class="delete">
+ Here </span><span class="delete">tr:WD-prov-dm-20111215</span><span class="delete"> is the entity identifier, and </span><span class="delete">[ prov:type="document" ]</span><span class="delete"> groups the optional attributes, only one in this example, with their values.
+ </span><span class="delete">
+entity(tr:WD-prov-dm-20111215)
+</span><span class="delete">
+Here, the optional attributes are absent.
+</span>
+
+
+
+
+
+<span class="delete">3.1.2 </span><span class="delete">Activity</span>
+
+
+
+
+ <span class="delete">[</span><span class="delete">7</span><span class="delete">] </span> <span class="delete">activityExpression</span> <span class="delete"> ::= </span> <span class="delete">"activity" "(" </span><span class="delete">identifier</span><span class="delete"> ( "," </span><span class="delete">timeOrMarker</span><span class="delete"> "," </span><span class="delete">timeOrMarker</span><span class="delete"> )? </span><span class="delete">optionalAttributeValuePairs</span><span class="delete"> ")"</span>
+ <span class="delete">[</span><span class="delete">8</span><span class="delete">] </span> <span class="delete">timeOrMarker</span> <span class="delete"> ::= </span> <span class="delete">( </span><span class="delete">time</span><span class="delete"> | "-" )</span>
+
+
+<span class="delete">The following table summarizes how each constituent of a PROV-DM Activity maps to a PROV-N syntax element.</span>
+
+
+<span class="delete">Activity</span><span class="delete">Non-Terminal</span>
+
+<span class="delete">id</span><span class="delete">identifier</span>
+
+<span class="delete">startTime</span><span class="delete">timeOrMarker</span>
+<span class="delete">endTime</span><span class="delete">timeOrMarker</span>
+
+
+
+
+<span class="delete">attributes</span><span class="delete">optionalAttributeValuePairs</span>
+
+
+
+
+
+<span class="delete">Example 12</span>
+<span class="delete">activity(ex:a10, 2011-11-16T16:00:00, 2011-11-16T16:00:01, [prov:type="createFile"])
+</span>
+<span class="delete">Here </span><span class="delete">ex:a10</span><span class="delete"> is the activity identifier, </span><span class="delete">2011-11-16T16:00:00</span><span class="delete"> and </span><span class="delete">2011-11-16T16:00:01</span><span class="delete"> are the optional start and end times for the activity, and </span><span class="delete">[prov:type="createFile"]</span><span class="delete"> are optional attributes. </span><span class="delete">
+The remaining examples show cases where some of the optionals are omitted.
+</span><span class="delete">activity(ex:a10)
+activity(ex:a10, -, -)
+activity(ex:a10, -, -, [prov:type="edit"])
+activity(ex:a10, -, 2011-11-16T16:00:00)
+activity(ex:a10, 2011-11-16T16:00:00, -)
+activity(ex:a10, 2011-11-16T16:00:00, -, [prov:type="createFile"])
+activity(ex:a10, [prov:type="edit"])
+</span>
+
+
+
+
+
+<span class="delete">3.1.3 </span><span class="delete">Generation</span>
+
+
+
+
+
+
+
+
+ <span class="delete">[</span><span class="delete">9</span><span class="delete">] </span> <span class="delete">generationExpression</span> <span class="delete"> ::= </span> <span class="delete">"wasGeneratedBy" "(" </span><span class="delete">optionalIdentifier</span> <span class="delete">eIdentifier</span><span class="delete"> ( "," </span><span class="delete">aIdentifierOrMarker</span><span class="delete"> "," </span><span class="delete">timeOrMarker</span><span class="delete"> )? </span><span class="delete">optionalAttributeValuePairs</span><span class="delete"> ")"</span>
+ <span class="delete">[</span><span class="delete">10</span><span class="delete">] </span> <span class="delete">optionalIdentifier</span> <span class="delete"> ::= </span> <span class="delete">( </span><span class="delete">identifierOrMarker</span><span class="delete"> ";" )?</span>
+ <span class="delete">[</span><span class="delete">11</span><span class="delete">] </span> <span class="delete">identifierOrMarker</span> <span class="delete"> ::= </span> <span class="delete">( </span><span class="delete">identifier</span><span class="delete"> | "-" )</span>
+
+
+
+<span class="delete">The following table summarizes how each constituent of a PROV-DM Generation maps to a PROV-N syntax element.</span>
+
+
+<span class="delete">Generation</span><span class="delete">Non-Terminal</span>
+
+<span class="delete">id</span><span class="delete">optionalIdentifier</span>
+<span class="delete">entity</span><span class="delete">eIdentifier</span>
+<span class="delete">activity</span><span class="delete">aIdentifierOrMarker</span>
+
+<span class="delete">time</span><span class="delete">timeOrMarker</span>
+
+<span class="delete">attributes</span><span class="delete">optionalAttributeValuePairs</span>
+
+
+
+
+<span class="delete">Example 13</span>
+
+<span class="delete">wasGeneratedBy(ex:g1; tr:WD-prov-dm-20111215, ex:edit1, 2011-11-16T16:00:00, [ex:fct="save"])
+</span>
+<span class="delete"> Here </span><span class="delete">ex:g1</span><span class="delete"> is the optional generation identifier, </span><span class="delete">tr:WD-prov-dm-20111215</span><span class="delete"> is the identifier of the entity being generated,
+ </span><span class="delete">ex:edit1</span><span class="delete"> is the optional identifier of the generating activity, </span><span class="delete">2011-11-16T16:00:00</span><span class="delete"> is the optional generation time, and </span><span class="delete"> [ex:fct="save"]</span><span class="delete"> are optional attributes. </span><span class="delete">
+The remaining examples show cases where some of the optionals are omitted.
+
+</span><span class="delete">wasGeneratedBy(e2, a1, -)
+wasGeneratedBy(e2, a1, 2011-11-16T16:00:00)
+wasGeneratedBy(e2, a1, -, [ex:fct="save"])
+wasGeneratedBy(e2, [ex:fct="save"])
+wasGeneratedBy(ex:g1; e)
+wasGeneratedBy(ex:g1; e, a, tr:WD-prov-dm-20111215)
+</span>
+
+
+<span class="delete">Additional semantic rules (</span><span class="delete">Section 3.7.5</span><span class="delete">) apply to </span><span class="delete">generationExpression</span><span class="delete">.</span>
+
+
+
+
+
+
+
+
+<span class="delete">3.1.4 </span><span class="delete">Usage</span>
+
+
+
+ <span class="delete">[</span><span class="delete">12</span><span class="delete">] </span> <span class="delete">usageExpression</span> <span class="delete"> ::= </span> <span class="delete">"used" "(" </span><span class="delete">optionalIdentifier</span> <span class="delete">aIdentifier</span><span class="delete"> ( "," </span><span class="delete">eIdentifierOrMarker</span><span class="delete"> "," </span><span class="delete">timeOrMarker</span><span class="delete"> )? </span><span class="delete">optionalAttributeValuePairs</span><span class="delete"> ")"</span>
+
+
+
+<span class="delete">The following table summarizes how each constituent of a PROV-DM Usage maps to a PROV-N syntax element.</span>
+
+
+<span class="delete">Usage</span><span class="delete">Non-Terminal</span>
+
+<span class="delete">id</span><span class="delete">optionalIdentifier</span>
+<span class="delete">activity</span><span class="delete">aIdentifier</span><span class="delete">entity</span><span class="delete">eIdentifierOrMarker</span>
+
+
+<span class="delete">time</span><span class="delete">timeOrMarker</span>
+
+<span class="delete">attributes</span><span class="delete">optionalAttributeValuePairs</span>
+
+
+
+<span class="delete">Example 14</span>
+
+<span class="delete">used(ex:u1; ex:act2, ar3:0111, 2011-11-16T16:00:00, [ex:fct="load"])
+ </span>
+<span class="delete"> Here </span><span class="delete">ex:u1</span><span class="delete"> is the optional usage identifier, </span><span class="delete">ex:act2</span><span class="delete"> is the identifier of the using activity,
+ </span><span class="delete">ar3:0111</span><span class="delete"> is the identifier of the entity being used,
+ </span><span class="delete">2011-11-16T16:00:00</span><span class="delete"> is the optional usage time, and </span><span class="delete"> [ex:fct="load"]</span><span class="delete"> are optional attributes.</span><span class="delete">
+The remaining examples show cases where some of the optionals are omitted.
+
+ </span><span class="delete">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, -)
+</span>
+
+
+<span class="delete">Additional semantic rules (</span><span class="delete">Section 3.7.5</span><span class="delete">) apply to </span><span class="delete">usageExpression</span><span class="delete">.</span>
+
+
+
+
+
+
+<span class="delete">3.1.5 </span><span class="delete">Communication</span>
+
+
+
+ <span class="delete">[</span><span class="delete">13</span><span class="delete">] </span> <span class="delete">communicationExpression</span> <span class="delete"> ::= </span> <span class="delete">"wasInformedBy" "(" </span><span class="delete">optionalIdentifier</span> <span class="delete">aIdentifier</span><span class="delete"> "," </span><span class="delete">aIdentifier</span> <span class="delete">optionalAttributeValuePairs</span><span class="delete"> ")"</span>
+
+
+
+
+<span class="delete">The following table summarizes how each constituent of a PROV-DM Communication maps to a PROV-N syntax element.</span>
+
+
+<span class="delete">Communication</span><span class="delete">Non-Terminal</span>
+
+<span class="delete">id</span><span class="delete">optionalIdentifier</span>
+<span class="delete">informed</span><span class="delete">aIdentifier</span>
+<span class="delete">informant</span><span class="delete">aIdentifier</span>
+<span class="delete">attributes</span><span class="delete">optionalAttributeValuePairs</span>
+
+
+
+
+
+<span class="delete">Example 15</span>
+<span class="delete">wasInformedBy(ex:inf1; ex:a1, ex:a2, [ex:param1="a", ex:param2="b"])
+</span>
+<span class="delete"> Here </span><span class="delete">ex:inf1</span><span class="delete"> is the optional communication identifier, </span><span class="delete">ex:a1</span><span class="delete"> is the identifier of the informed activity,
+ </span><span class="delete">ex:a2</span><span class="delete"> is the identifier of the informant activity,
+and </span><span class="delete">[ex:param1="a", ex:param2="b"]</span><span class="delete"> are optional attributes. </span><span class="delete">
+The remaining examples show cases where some of the optionals are omitted.
+
+</span><span class="delete">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"])
+</span>
+
+
+
+
+
+
+<span class="delete">3.1.6 </span><span class="delete">Start</span>
+
+
+
+ <span class="delete">[</span><span class="delete">14</span><span class="delete">] </span> <span class="delete">startExpression</span> <span class="delete"> ::= </span> <span class="delete">"wasStartedBy" "(" </span><span class="delete">optionalIdentifier</span> <span class="delete">aIdentifier</span><span class="delete"> ( "," </span><span class="delete">eIdentifierOrMarker</span><span class="delete"> "," </span><span class="delete">aIdentifierOrMarker</span><span class="delete"> "," </span><span class="delete">timeOrMarker</span><span class="delete"> )? </span><span class="delete">optionalAttributeValuePairs</span><span class="delete"> ")"</span>
+
+
+<span class="delete">The following table summarizes how each constituent of a PROV-DM Start maps to a PROV-N syntax element.</span>
+
+
+<span class="delete">Start</span><span class="delete">Non-Terminal</span>
+
+<span class="delete">id</span><span class="delete">optionalIdentifier</span>
+<span class="delete">activity</span><span class="delete">aIdentifier</span>
+<span class="delete">trigger</span><span class="delete">eIdentifierOrMarker</span>
+<span class="delete">starter</span><span class="delete">aIdentifierOrMarker</span>
+
+
+<span class="delete">time</span><span class="delete">timeOrMarker</span>
+
+<span class="delete">attributes</span><span class="delete">optionalAttributeValuePairs</span>
+
+
+
+
+
+<span class="delete">Example 16</span>
+
+ <span class="delete">wasStartedBy(start; ex:act2, ex:trigger, ex:act1, 2011-11-16T16:00:00, [ex:param="a"])
+ </span>
+ <span class="delete">Here </span><span class="delete">start</span><span class="delete"> is the optional start identifier, </span><span class="delete">ex:act2</span><span class="delete"> is the identifier of the started activity,
+ </span><span class="delete">ex:trigger</span><span class="delete"> is the optional identifier for the entity that triggered the activity start,
+ </span><span class="delete">ex:act1</span><span class="delete"> is the optional identifier for the activity that generated the (possibly unspecified) entity </span><span class="delete">ex:trigger</span><span class="delete">,
+ </span><span class="delete">2011-11-16T16:00:00</span><span class="delete"> is the optional start time, and </span><span class="delete"> [ex:param="a"]</span><span class="delete"> are optional attributes.</span><span class="delete">
+ The remaining examples show cases where some of the optionals are omitted.
+
+ </span><span class="delete">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"])
+wasStartedBy(start; ex:act2, e, ex:act1, 2011-11-16T16:00:00)
+</span>
+
+
+
+<span class="delete">Additional semantic rules (</span><span class="delete">Section 3.7.5</span><span class="delete">) apply to </span><span class="delete">startExpression</span><span class="delete">.</span>
+
+
+
+
+
+<span class="delete">3.1.7 </span><span class="delete">End</span>
+
+
+ <span class="delete">[</span><span class="delete">15</span><span class="delete">] </span> <span class="delete">endExpression</span> <span class="delete"> ::= </span> <span class="delete">"wasEndedBy" "(" </span><span class="delete">optionalIdentifier</span> <span class="delete">aIdentifier</span><span class="delete"> ( "," </span><span class="delete">eIdentifierOrMarker</span><span class="delete"> "," </span><span class="delete">aIdentifierOrMarker</span><span class="delete"> "," </span><span class="delete">timeOrMarker</span><span class="delete"> )? </span><span class="delete">optionalAttributeValuePairs</span><span class="delete"> ")"</span>
+
+
+
+<span class="delete">The following table summarizes how each constituent of a PROV-DM End maps to a PROV-N syntax element.</span>
+
+
+<span class="delete">End</span><span class="delete">Non-Terminal</span>
+
+<span class="delete">id</span><span class="delete">optionalIdentifier</span>
+<span class="delete">activity</span><span class="delete">aIdentifier</span>
+<span class="delete">trigger</span><span class="delete">eIdentifierOrMarker</span>
+<span class="delete">ender</span><span class="delete">aIdentifierOrMarker</span>
+
+
+<span class="delete">time</span><span class="delete">timeOrMarker</span>
+
+<span class="delete">attributes</span><span class="delete">optionalAttributeValuePairs</span>
+
+
+
+
+<span class="delete">Example 17</span>
+
+ <span class="delete">wasEndedBy(end; ex:act2, ex:trigger, ex:act3, 2011-11-16T16:00:00, [ex:param="a"])
+ </span>
+<span class="delete"> Here </span><span class="delete">end</span><span class="delete"> is the optional end identifier,
+</span><span class="delete">ex:act2</span><span class="delete"> is the identifier of the ending activity,
+ </span><span class="delete">ex:trigger</span><span class="delete"> is the identifier of the entity that triggered the activity end,
+ </span><span class="delete">ex:act3</span><span class="delete"> is the optional identifier for the activity that generated the (possibly unspecified) entity </span><span class="delete">ex:trigger</span><span class="delete">,
+ </span><span class="delete">2011-11-16T16:00:00</span><span class="delete"> is the optional usage time, and </span><span class="delete"> [ex:param="a"]</span><span class="delete"> are optional attributes. </span><span class="delete">
+The remaining examples show cases where some of the optionals are omitted.
+
+
+</span><span class="delete">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"])
+wasEndedBy(end; ex:act2)
+wasEndedBy(end; ex:act2, ex:trigger, -, 2011-11-16T16:00:00)
+</span>
+
+
+
+<span class="delete">Additional semantic rules (</span><span class="delete">Section 3.7.5</span><span class="delete">) apply to </span><span class="delete">endExpression</span><span class="delete">.</span>
+
+
+
+
+
+
+<span class="delete">3.1.8 </span><span class="delete">Invalidation</span>
+
+
+
+
+
+
+ <span class="delete">[</span><span class="delete">16</span><span class="delete">] </span> <span class="delete">invalidationExpression</span> <span class="delete"> ::= </span> <span class="delete">"wasInvalidatedBy" "(" </span><span class="delete">optionalIdentifier</span> <span class="delete">eIdentifier</span><span class="delete"> ( "," </span><span class="delete">aIdentifierOrMarker</span><span class="delete"> "," </span><span class="delete">timeOrMarker</span><span class="delete"> )? </span><span class="delete">optionalAttributeValuePairs</span><span class="delete"> ")"</span>
+
+
+
+<span class="delete">The following table summarizes how each constituent of a PROV-DM Invalidation maps to a PROV-N syntax element.</span>
+
+
+<span class="delete">Invalidation</span><span class="delete">Non-Terminal</span>
+
+<span class="delete">id</span><span class="delete">optionalIdentifier</span>
+<span class="delete">entity</span><span class="delete">eIdentifier</span>
+<span class="delete">activity</span><span class="delete">aIdentifierOrMarker</span>
+
+<span class="delete">time</span><span class="delete">timeOrMarker</span>
+
+<span class="delete">attributes</span><span class="delete">optionalAttributeValuePairs</span>
+
+
+
+<span class="delete">Example 18</span>
+
+<span class="delete">wasInvalidatedBy(ex:inv; tr:WD-prov-dm-20111215, ex:edit1, 2011-11-16T16:00:00, [ex:fct="save"])
+</span>
+<span class="delete"> Here </span><span class="delete">ex:inv</span><span class="delete"> is the optional invalidation identifier, </span><span class="delete">tr:WD-prov-dm-20111215</span><span class="delete"> is the identifier of the entity being invalidated,
+ </span><span class="delete">ex:edit1</span><span class="delete"> is the optional identifier of the invalidating activity, </span><span class="delete">2011-11-16T16:00:00</span><span class="delete"> is the optional invalidation time, and </span><span class="delete"> [ex:fct="save"]</span><span class="delete"> are optional attributes. </span><span class="delete">
+The remaining examples show cases where some of the optionals are omitted.
+
+</span><span class="delete">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"])
+wasInvalidatedBy(ex:inv; tr:WD-prov-dm-20111215, ex:edit1, -)
+wasInvalidatedBy(tr:WD-prov-dm-20111215, ex:edit1, -)
+</span>
+
+
+
+<span class="delete">Additional semantic rules (</span><span class="delete">Section 3.7.5</span><span class="delete">) apply to </span><span class="delete">invalidationExpression</span><span class="delete">.</span>
+
@@ -1015,815 +1696,58 @@
-
-
-
-
-
-
-
-<section id="introduction">
-<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 [<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">
-<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.
-
-
-
-With these two requirements in mind, this document introduces PROV-N, the PROV notation, a syntax designed to write instances of the PROV data model according to the following design principles:
-<ul>
-<li>Technology independence. PROV-N provides a simple syntax that can be mapped to several technologies.
-
-</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 [<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:
-</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 [<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><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>.
-</p><ul>
-<li> Information in tables is normative. </li>
-<li> Text in boxes labeled "Example" is informative.
-</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><span class="secno">1.3 </span>Structure of this Document</h3>
-
-<p>This document is structured as follows.
-
-</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>
-
-<p><a href="#document">Section 4</a> defines the grammar of document, a house-keeping construct of PROV-N capable of packaging up PROV-N expressions and namespace declarations.</p>
-
-<p><a href="#extensibility">Section 5</a> defines the extensibility mechanism for the PROV-N notation.</p>
-
-<p><a href="#media-type">Section 6</a> defines media type for the PROV-N notation.</p>
-
-
- </section>
-
-
-<section id="notational-conventions">
- <h3><span class="secno">1.4 </span>Notational Conventions</h3>
-
-
-
-
-
-
-<p>The key words "<span class="delete">must</span><em class="rfc2119" title="MUST"><span class="insert">MUST</span></em>", "<span class="delete">must not</span><em class="rfc2119" title="MUST NOT"><span class="insert">MUST NOT</span></em>", "<span class="delete">required</span><em class="rfc2119" title="REQUIRED"><span class="insert">REQUIRED</span></em>", "<span class="delete">shall</span><em class="rfc2119" title="SHALL"><span class="insert">SHALL</span></em>", "<span class="delete">shall</span><em class="rfc2119" title="SHALL
- NOT"><span class="insert">SHALL</span>
- <span class="delete">not</span><span class="insert">NOT</span></em>", "<span class="delete">should</span><em class="rfc2119" title="SHOULD"><span class="insert">SHOULD</span></em>", "<span class="delete">should not</span><em class="rfc2119" title="SHOULD NOT"><span class="insert">SHOULD NOT</span></em>", "<span class="delete">recommended</span><em class="rfc2119" title="RECOMMENDED"><span class="insert">RECOMMENDED</span></em>", "<span class="delete">may</span><em class="rfc2119" title="MAY"><span class="insert">MAY</span></em>", and
- "<span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></em>" in this document are to be interpreted as described in
- [<cite><a class="bibref" href="#bib-RFC2119">RFC2119</a></cite>].</p>
-
-
-
-
-<p>
-The following namespaces prefixes are used throughout this document.
-
-</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>
-<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 [<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>
-
-</section>
-
-<section id="general-conventions">
-<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><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" 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>".
-</p><pre class="codeexample">entity(e1)
-</pre>
- </div>
-<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>".
-</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.
-</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.
-</p><pre class="codeexample">wasDerivedFrom(e2, e1)
-</pre>
- </div>
-
-<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>:
-</p><pre class="codeexample">wasDerivedFrom(e2, e1, a, g2, u1)
-</pre>
-</div>
-
-</section>
-
-<section id="grammar-notation">
-<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
-[<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>
-
-<p>
-The text below provides an introduction to the EBNF notation used in
-this document.</p>
-
-
-<p>
- 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 id="dfn-nonterminal-symbol">nonterminal symbol</dfn>)
- using the following form:</p>
-
-
-<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 id="dfn-terminal-symbol">terminal symbol</dfn>)
- using the following form:</p>
-<div class="grammar">
- <code class="grammarRef"><TERMINAL></code> ::= <em>term</em>
-</div>
-
-
-
-
-
-<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:
-</p><ul>
-<li>
- <code class="grammarRef">expr</code>: matches production for nonterminal symbol <code class="grammarRef">expr</code>
-</li>
-
-
-<li>
- <code class="grammarRef">TERMINAL</code>: matches production for terminal symbol <code class="grammarRef">TERMINAL</code>
-</li>
-
-<li>
- <code class="grammarRef">"abc"</code>: matches the literal string inside the single quotes.
-</li>
-
-
-<li>
- <code class="grammarRef">(term)?</code>: optional, matches <em>term</em> or nothing.
-</li>
-
-<li>
- <code class="grammarRef">(term)+</code>: matches one or more occurrences of <em>term</em>.
-</li>
-
-<li>
- <code class="grammarRef">(term)*</code>: matches zero or more occurrences of <em>term</em>.
-</li>
-
-<li>
- <code class="grammarRef">(term | term)</code>: matches one of the two <em>terms</em>.
-</li>
-
-</ul>
-
-
-<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><span class="secno">2.3 </span>Main Productions</h3>
-
-<p>Two productions are entry points to the grammar.</p>
-
-<p>The production <code class="grammarRef"><a class="grammarRef" href="#prod-expression">expression</a></code>
-provides the structure for the <em>core expressions</em> of PROV-N.
-
-
-
-
-</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>
-
-
-<p>Each of the symbols included in <code>expression</code> above, i.e., <code><a class="grammarRef" href="#prod-entityExpression">entityExpression</a></code>, <code><a class="grammarRef" href="#prod-activityExpression">activityExpression</a></code> etc., corresponds to one concept (e.g., Entity, Activity, etc.) of the PROV data model.</p>
-
-
-<p>Alternatively, the production rule <code><a href="#prod-document"><span class="grammarRef">document</span></a></code>
-provides the overall structure of PROV-N descriptions. It is a wrapper for
- a set of expressions, such that the text for an element matches the corresponding <code><a class="grammarRef" href="#prod-expression">expression</a></code> production, and some namespace declarations.</p>
-
-</section>
-
-
-<section id="prov-n-optionals">
-<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" 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" 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.
-</div>
-
-<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" 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.
-
-</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" 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>
-
-
-</section>
-
-<section id="prov-n-standard-terms">
-<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 <span class="delete">must</span><em class="rfc2119" title="MUST"><span class="insert">MUST</span></em> be separated using a semi-colon ';', but where the identifiers are required, a regular comma ',' <span class="delete">must</span><em class="rfc2119" title="MUST"><span class="insert">MUST</span></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)
-wasDerivedFrom(d; e2, e1)
-wasDerivedFrom(-; e2, e1)
-</pre>
-</div>
-
-Lack of attributes can be equivalently expressed by omitting the list, or by using an empty list.
-
-
-
-<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.
-
-The third activity expression specifies two attributes.
-</p><pre class="codeexample">activity(ex:a1)
-activity(ex:a1, [])
-activity(ex:a1, [ex:param1="a", ex:param2="b"])
-</pre>
-</div>
-
-</section>
-
-<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><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>
-
-</section>
-
-<section id="prov-n-expressions">
-<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><span class="secno">3.1 </span>Component 1: Entities and Activities</h3>
-
-<section id="expression-Entity">
-<h4><span class="secno">3.1.1 </span>Entity</h4>
-
-
-<p>
-
-</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;">
-<tbody><tr><td><b><a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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" 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)
-</pre>
-Here, the optional attributes are absent.
-</div>
-
-
-
-</section>
-<section id="expression-Activity">
-<h4><span class="secno">3.1.2 </span>Activity</h4>
-
-
-<table class="grammar">
-
-<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;">
-<tbody><tr><td><b><a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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" 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)
-activity(ex:a10, -, -)
-activity(ex:a10, -, -, [prov:type="edit"])
-activity(ex:a10, -, 2011-11-16T16:00:00)
-activity(ex:a10, 2011-11-16T16:00:00, -)
-activity(ex:a10, 2011-11-16T16:00:00, -, [prov:type="createFile"])
-activity(ex:a10, [prov:type="edit"])
-</pre>
-</div>
-
-
-</section>
-<section id="expression-Generation">
-<h4><span class="secno">3.1.3 </span>Generation</h4>
-
-
-
-
-
-
-<table class="grammar">
-
-<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;">
-<tbody><tr><td><b><a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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" 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, -)
-wasGeneratedBy(e2, a1, 2011-11-16T16:00:00)
-wasGeneratedBy(e2, a1, -, [ex:fct="save"])
-wasGeneratedBy(e2, [ex:fct="save"])
-wasGeneratedBy(ex:g1; e)
-wasGeneratedBy(ex:g1; e, a, tr:WD-prov-dm-20111215)
-</pre>
-</div>
-
-<p>Additional semantic rules (<a href="#semantic-rules-summary">Section 3.7.5</a>) apply to <code class="content"><a class="grammarRef" href="#prod-generationExpression">generationExpression</a></code>.</p>
-
-
-
-
-
-</section>
-
-<section id="expression-Usage">
-<h4><span class="secno">3.1.4 </span>Usage</h4>
-
-<table class="grammar">
-
-<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;">
-<tbody><tr><td><b><a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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" 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>
-<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)
-used(ex:act2, ar3:0111, 2011-11-16T16:00:00)
-used(a1,e1, -, [ex:fct="load"])
-used(ex:u1; ex:act2, ar3:0111, -)
-</pre>
-</div>
-
-<p>Additional semantic rules (<a href="#semantic-rules-summary">Section 3.7.5</a>) apply to <code class="content"><a class="grammarRef" href="#prod-usageExpression">usageExpression</a></code>.</p>
-
-
-
-</section>
-
-<section id="expression-wasInformedBy">
-<h4><span class="secno">3.1.5 </span>Communication</h4>
-
-<table class="grammar">
-
-<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>
-
-
-<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;">
-<tbody><tr><td><b><a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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" 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)
-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"])
-</pre>
-</div>
-</section>
-
-
-
-<section id="expression-Start">
-<h4><span class="secno">3.1.6 </span>Start</h4>
-
-
-<table class="grammar">
-<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;">
-<tbody><tr><td><b><a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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" 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>
- The remaining examples show cases where some of the optionals are omitted.
-
- <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"])
-wasStartedBy(start; ex:act2, e, ex:act1, 2011-11-16T16:00:00)
-</pre>
-</div>
-
-
-<p>Additional semantic rules (<a href="#semantic-rules-summary">Section 3.7.5</a>) apply to <code class="content"><a class="grammarRef" href="#prod-startExpression">startExpression</a></code>.</p>
-
-
-</section>
-
-<section id="expression-End">
-<h4><span class="secno">3.1.7 </span>End</h4>
-
-<table class="grammar">
-<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;">
-<tbody><tr><td><b><a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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" 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="delete">3.2 </span><span class="delete">Component 2: Derivations</span>
+
+<span class="delete">3.2.1 </span><span class="delete">Derivation</span>
+
+
+ <span class="delete">[</span><span class="delete">17</span><span class="delete">] </span> <span class="delete">derivationExpression</span> <span class="delete"> ::= </span> <span class="delete">"wasDerivedFrom" "(" </span><span class="delete">optionalIdentifier</span> <span class="delete">eIdentifier</span><span class="delete"> "," </span><span class="delete">eIdentifier</span><span class="delete"> ( "," </span><span class="delete">aIdentifierOrMarker</span><span class="delete"> "," </span><span class="delete">gIdentifierOrMarker</span><span class="delete"> "," </span><span class="delete">uIdentifierOrMarker</span><span class="delete"> )? </span><span class="delete">optionalAttributeValuePairs</span><span class="delete"> ")"</span>
+
+
+<span class="delete">The following table summarizes how each constituent of a PROV-DM Derivation maps to a PROV-N syntax element.</span>
+
+
+<span class="delete">Derivation</span><span class="delete">Non-Terminal</span>
+
+
+<span class="delete">id</span><span class="delete">optionalIdentifier</span>
+
+<span class="delete">generatedEntity</span><span class="delete">eIdentifier</span>
+
+<span class="delete">usedEntity</span><span class="delete">eIdentifier</span>
+
+<span class="delete">activity</span><span class="delete">aIdentifierOrMarker</span>
+
+
+<span class="delete">generation</span><span class="delete">gIdentifierOrMarker</span>
+
+<span class="delete">usage</span><span class="delete">uIdentifierOrMarker</span>
+
+
+
+<span class="delete">attributes</span><span class="delete">optionalAttributeValuePairs</span>
+
+
+
+
+
+
+
+<span class="delete">Example 19</span>
+ <span class="delete">wasDerivedFrom(d; e2, e1, a, g2, u1, [ex:comment="a righteous derivation"])
+ </span>
+<span class="delete"> Here
+ </span><span class="delete">d</span><span class="delete"> is the optional derivation identifier,
+ </span><span class="delete">e2</span><span class="delete"> is the identifier for the entity being derived,
+ </span><span class="delete">e1</span><span class="delete"> is the identifier of the entity from which </span><span class="delete">e2</span><span class="delete"> is derived,
+ </span><span class="delete">a</span><span class="delete"> is the optional identifier of the activity which used/generated the entities,
+ </span><span class="delete">g2</span><span class="delete"> is the optional identifier of the generation,
+ </span><span class="delete">u1</span><span class="delete"> is the optional identifier of the usage,
+ and </span><span class="delete">[ex:comment="a righteous derivation"]</span><span class="delete"> are optional attributes. </span><span class="delete">
The remaining examples show cases where some of the optionals are omitted.
-<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"])
-wasEndedBy(end; ex:act2)
-wasEndedBy(end; ex:act2, ex:trigger, -, 2011-11-16T16:00:00)
-</pre>
-</div>
-
-
-<p>Additional semantic rules (<a href="#semantic-rules-summary">Section 3.7.5</a>) apply to <code class="content"><a class="grammarRef" href="#prod-endExpression">endExpression</a></code>.</p>
-
-</section>
-
-
-
-<section id="expression-Invalidation">
-<h4><span class="secno">3.1.8 </span>Invalidation</h4>
-
-
-
-
-<table class="grammar">
-
-<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;">
-<tbody><tr><td><b><a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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" 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>
-The remaining examples show cases where some of the optionals are omitted.
-
-<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"])
-wasInvalidatedBy(ex:inv; tr:WD-prov-dm-20111215, ex:edit1, -)
-wasInvalidatedBy(tr:WD-prov-dm-20111215, ex:edit1, -)
-</pre>
-</div>
-
-
-<p>Additional semantic rules (<a href="#semantic-rules-summary">Section 3.7.5</a>) apply to <code class="content"><a class="grammarRef" href="#prod-invalidationExpression">invalidationExpression</a></code>.</p>
-
-
-</section>
-
-
-
-
-</section>
-
-<section id="component2">
-<h3><span class="secno">3.2 </span>Component 2: Derivations</h3>
-<section id="Derivation-Relation">
-<h4><span class="secno">3.2.1 </span>Derivation</h4>
-
-<table class="grammar">
-<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;">
-<tbody><tr><td><b><a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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"><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,
- <span class="name">e2</span> is the identifier for the entity being derived,
- <span class="name">e1</span> is the identifier of the entity from which <span class="name">e2</span> is derived,
- <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>
-The remaining examples show cases where some of the optionals are omitted.
-
-
-<pre class="codeexample">wasDerivedFrom(e2, e1)
+</span><span class="delete">wasDerivedFrom(e2, e1)
wasDerivedFrom(e2, e1, a, g2, u1)
wasDerivedFrom(e2, e1, -, g2, u1)
wasDerivedFrom(e2, e1, a, -, u1)
@@ -1833,608 +1757,608 @@
wasDerivedFrom(e2, e1, -, -, -)
wasDerivedFrom(d; e2, e1, a, g2, u1)
wasDerivedFrom(-; e2, e1, a, g2, u1)
-</pre>
-</div>
-
-</section>
-<section id="expression-Revision">
-<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 <span class="delete">must</span><em class="rfc2119" title="MUST"><span class="insert">MUST</span></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" 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,
+</span>
+
+
+
+
+<span class="delete">3.2.2 </span><span class="delete">Revision</span>
+
+<span class="delete">
+PROV-N provides no dedicated syntax for Revision. Instead, a Revision </span><span class="delete">MUST</span><span class="delete"> be expressed as a
+</span><span class="delete">derivationExpression</span><span class="delete"> with attribute </span><span class="delete">prov:type='prov:Revision'</span><span class="delete">.</span>
+
+
+
+<span class="delete">Example 20</span>
+ <span class="delete">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 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>).
-</p></div>
-
-
-</section>
-<section id="expression-quotation">
-<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 <span class="delete">must</span><em class="rfc2119" title="MUST"><span class="insert">MUST</span></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" 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,
+ </span>
+<span class="delete">Here, the derivation from
+</span><span class="delete">Example 19</span><span class="delete">
+is extended with a </span><span class="delete">prov:type</span><span class="delete"> attribute and value </span><span class="delete">prov:Revision</span><span class="delete">. The expression </span><span class="delete">'prov:Revision'</span><span class="delete"> is </span><span class="delete">convenienceNotation</span><span class="delete"> to denote a </span><span class="delete">QUALIFIED_NAME</span><span class="delete"> literal (See </span><span class="delete">Section 3.7.3. Literal</span><span class="delete">).
+</span>
+
+
+
+
+<span class="delete">3.2.3 </span><span class="delete">Quotation</span>
+
+<span class="delete">
+PROV-N provides no dedicated syntax for Quotation. Instead, a Quotation </span><span class="delete">MUST</span><span class="delete"> be expressed as a
+</span><span class="delete">derivationExpression</span><span class="delete"> with attribute </span><span class="delete">prov:type='prov:Quotation'</span><span class="delete">.</span>
+
+
+
+
+
+<span class="delete">Example 21</span>
+ <span class="delete">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>.
-</p></div>
-
-
-</section>
-
-
-<section id="expression-primary-source">
-<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 <span class="delete">must</span><em class="rfc2119" title="MUST"><span class="insert">MUST</span></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" 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,
+ </span>
+
+<span class="delete">Here, the derivation is provided with a </span><span class="delete">prov:type</span><span class="delete"> attribute and value </span><span class="delete">prov:Quotation</span><span class="delete">.
+</span>
+
+
+
+
+
+
+<span class="delete">3.2.4 </span><span class="delete">Primary Source</span>
+
+
+<span class="delete">
+PROV-N provides no dedicated syntax for PrimarySource. Instead, a PrimarySource </span><span class="delete">MUST</span><span class="delete"> be expressed as a
+</span><span class="delete">derivationExpression</span><span class="delete"> with attribute </span><span class="delete">prov:type='prov:Primary-Source'</span><span class="delete">.</span>
+
+
+<span class="delete">Example 22</span>
+ <span class="delete">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>.
- </p>
-</div>
-
-
-</section>
-
-</section>
-
-
-<section id="component3">
-<h3><span class="secno">3.3 </span>Component 3: Agents, Responsibility, and Influence</h3>
-<section id="expression-Agent">
-<h4><span class="secno">3.3.1 </span>Agent</h4>
-
-
-
-<table class="grammar">
-
-<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;">
-<tbody><tr><td><b><a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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 <span class="delete">must</span><em class="rfc2119" title="MUST"><span class="insert">MUST</span></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" 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>
+<span class="delete">Here, the derivation is provided with a </span><span class="delete">prov:type</span><span class="delete"> attribute and value </span><span class="delete">prov:PrimarySource</span><span class="delete">.
+ </span>
+
+
+
+
+
+
+
+
+
+<span class="delete">3.3 </span><span class="delete">Component 3: Agents, Responsibility, and Influence</span>
+
+<span class="delete">3.3.1 </span><span class="delete">Agent</span>
+
+
+
+
+
+ <span class="delete">[</span><span class="delete">18</span><span class="delete">] </span> <span class="delete">agentExpression</span> <span class="delete"> ::= </span> <span class="delete">"agent" "(" </span><span class="delete">identifier</span> <span class="delete">optionalAttributeValuePairs</span><span class="delete"> ")"</span>
+
+
+
+<span class="delete">The following table summarizes how each constituent of a PROV-DM Agent maps to a PROV-N syntax element.</span>
+
+
+<span class="delete">Agent</span><span class="delete">Non-Terminal</span>
+
+<span class="delete">id</span><span class="delete">identifier</span>
+<span class="delete">attributes</span><span class="delete">optionalAttributeValuePairs</span>
+
+
+
+<span class="delete">
+PROV-N provides no dedicated syntax for Person, Organization, SoftwareAgent. Instead, a Person, an Organization, or a SoftwareAgent </span><span class="delete">MUST</span><span class="delete"> be expressed as an
+</span><span class="delete">agentExpression</span><span class="delete"> with attribute
+</span><span class="delete">prov:type='prov:Person'</span><span class="delete">,
+</span><span class="delete">prov:type='prov:Organization'</span><span class="delete">, or
+</span><span class="delete">prov:type='prov:SoftwareAgent'</span><span class="delete">, respectively.</span>
+
+
+<span class="delete">Example 23</span>
+<span class="delete">agent(ag4, [ prov:type='prov:Person', ex:name="David" ])
+</span>
+<span class="delete">Here </span><span class="delete">ag</span><span class="delete"> is the agent identifier, and
+ </span><span class="delete">[ prov:type='prov:Person', ex:name="David" ]</span><span class="delete"> are optional attributes. </span><span class="delete">
In the next example, the optional attributes are omitted.
-<pre class="codeexample">agent(ag4)
-</pre>
-</div>
-
-
-</section>
-<section id="expression-attribution">
-<h4><span class="secno">3.3.2 </span>Attribution</h4>
-
-
-<table class="grammar">
-
-<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>
-
-
-<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;">
-<tbody><tr><td><b><a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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" 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><span class="delete">agent(ag4)
+</span>
+
+
+
+
+
+<span class="delete">3.3.2 </span><span class="delete">Attribution</span>
+
+
+
+
+ <span class="delete">[</span><span class="delete">19</span><span class="delete">] </span> <span class="delete">attributionExpression</span> <span class="delete"> ::= </span> <span class="delete">"wasAttributedTo" "(" </span><span class="delete">optionalIdentifier</span> <span class="delete">eIdentifier</span><span class="delete"> "," </span><span class="delete">agIdentifier</span> <span class="delete">optionalAttributeValuePairs</span><span class="delete"> ")"</span>
+
+
+
+
+<span class="delete">The following table summarizes how each constituent of a PROV-DM Attribution maps to a PROV-N syntax element.</span>
+
+
+<span class="delete">Attribution</span><span class="delete">Non-Terminal</span>
+
+<span class="delete">id</span><span class="delete">optionalIdentifier</span>
+<span class="delete">entity</span><span class="delete">eIdentifier</span>
+<span class="delete">agent</span><span class="delete">agIdentifier</span>
+
+
+<span class="delete">attributes</span><span class="delete">optionalAttributeValuePairs</span>
+
+
+
+
+
+<span class="delete">Example 24</span>
+
+<span class="delete">wasAttributedTo(attr; e, ag, [ex:license='cc:attributionURL' ])
+ </span>
+<span class="delete"> Here </span><span class="delete">attr</span><span class="delete"> is the optional attribution identifier, </span><span class="delete">e</span><span class="delete"> is an entity identifier,
+ </span><span class="delete">ag</span><span class="delete"> is the identifier of the agent to whom the entity is abscribed,
+and </span><span class="delete">[ex:license='cc:attributionURL' ]</span><span class="delete"> are optional attributes. </span><span class="delete">
The remaining examples show cases where some of the optionals are omitted.
-<pre class="codeexample">wasAttributedTo(e, ag)
+</span><span class="delete">wasAttributedTo(e, ag)
wasAttributedTo(e, ag, [ex:license='cc:attributionURL' ])
-</pre>
-</div>
-
-</section>
-
-
-<section id="expression-Association">
-<h4><span class="secno">3.3.3 </span>Association</h4>
-
-
-<table class="grammar">
-
-<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>
-
-
-<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;">
-<tbody><tr><td><b><a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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 <span class="delete">must</span><em class="rfc2119" title="MUST"><span class="insert">MUST</span></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" id="example_25"><div class="anexampleTitle"><a class="internalDFN" href="#example_25">Example 25</a></div>
-<pre class="codeexample">wasAssociatedWith(ex:assoc; ex:a1, ex:ag1, ex:e1, [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>
+
+
+
+
+
+
+<span class="delete">3.3.3 </span><span class="delete">Association</span>
+
+
+
+
+ <span class="delete">[</span><span class="delete">20</span><span class="delete">] </span> <span class="delete">associationExpression</span> <span class="delete"> ::= </span> <span class="delete">"wasAssociatedWith" "(" </span><span class="delete">optionalIdentifier</span> <span class="delete">aIdentifier</span><span class="delete"> ( "," </span><span class="delete">agIdentifierOrMarker</span><span class="delete"> "," </span><span class="delete">eIdentifierOrMarker</span><span class="delete"> )? </span><span class="delete">optionalAttributeValuePairs</span><span class="delete"> ")"</span>
+
+
+
+
+<span class="delete">The following table summarizes how each constituent of a PROV-DM Association maps to a PROV-N syntax element.</span>
+
+
+<span class="delete">Association</span><span class="delete">Non-Terminal</span>
+
+
+<span class="delete">id</span><span class="delete">optionalIdentifier</span>
+
+<span class="delete">activity</span><span class="delete">aIdentifier</span>
+
+<span class="delete">agent</span><span class="delete">agIdentifierOrMarker</span>
+
+<span class="delete">plan</span><span class="delete">eIdentifierOrMarker</span>
+
+
+<span class="delete">attributes</span><span class="delete">optionalAttributeValuePairs</span>
+
+
+
+
+<span class="delete">
+PROV-N provides no dedicated syntax for Plan. Instead, a Plan </span><span class="delete">MUST</span><span class="delete"> be expressed as an
+</span><span class="delete">entityExpression</span><span class="delete"> with attribute </span><span class="delete">prov:type='prov:Plan'</span><span class="delete">.</span>
+
+
+<span class="delete">Example 25</span>
+<span class="delete">wasAssociatedWith(ex:assoc; ex:a1, ex:ag1, ex:e1, [ex:param1="a", ex:param2="b"])
+ </span>
+
+<span class="delete"> Here </span><span class="delete">ex:assoc</span><span class="delete"> is the optional attribution identifier,
+ </span><span class="delete">ex:a1</span><span class="delete"> is an activity identifier,
+ </span><span class="delete">ex:ag1</span><span class="delete"> is the optional identifier of the agent associated to the activity,
+ </span><span class="delete">ex:e1</span><span class="delete"> is the optional identifier of the plan used by the agent in the context of the activity,
+ and </span><span class="delete"> [ex:param1="a", ex:param2="b"]</span><span class="delete"> are optional attributes. </span><span class="delete">
The remaining examples show cases where some of the optionals are omitted.
-<pre class="codeexample">wasAssociatedWith(ex:a1, -, ex:e1)
+</span><span class="delete">wasAssociatedWith(ex:a1, -, ex:e1)
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)
-</pre>
-</div>
-
-
-<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" id="example_26"><div class="anexampleTitle"><a class="internalDFN" href="#example_26">Example 26</a></div>
-<p>The following expression illustrates a plan.
-</p><pre class="codeexample"> entity(ex:pl1, [ prov:type='prov:Plan' ])
-</pre>
-</div>
-
-
-
-
-</section>
-<section id="expression-delegation">
-<h4><span class="secno">3.3.4 </span>Delegation</h4>
-
-
-<table class="grammar">
-
-<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;">
-<tbody><tr><td><b><a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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" 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>
+</span>
+
+
+
+<span class="delete">Additional semantic rules (</span><span class="delete">Section 3.7.5</span><span class="delete">) apply to </span><span class="delete">associationExpression</span><span class="delete">.</span>
+
+
+<span class="delete">Example 26</span>
+<span class="delete">The following expression illustrates a plan.
+</span><span class="delete"> entity(ex:pl1, [ prov:type='prov:Plan' ])
+</span>
+
+
+
+
+
+
+
+<span class="delete">3.3.4 </span><span class="delete">Delegation</span>
+
+
+
+
+ <span class="delete">[</span><span class="delete">21</span><span class="delete">] </span> <span class="delete">delegationExpression</span> <span class="delete"> ::= </span> <span class="delete">"actedOnBehalfOf" "(" </span><span class="delete">optionalIdentifier</span> <span class="delete">agIdentifier</span><span class="delete"> "," </span><span class="delete">agIdentifier</span><span class="delete"> ( "," </span><span class="delete">aIdentifierOrMarker</span><span class="delete"> )? </span><span class="delete">optionalAttributeValuePairs</span><span class="delete"> ")"</span>
+
+
+
+<span class="delete">The following table summarizes how each constituent of a PROV-DM Delegation maps to a PROV-N syntax element.</span>
+
+
+<span class="delete">Delegation</span><span class="delete">Non-Terminal</span>
+
+
+<span class="delete">id</span><span class="delete">optionalIdentifier</span>
+
+<span class="delete">delegate</span><span class="delete">agIdentifier</span>
+
+<span class="delete">responsible</span><span class="delete">agIdentifier</span>
+
+<span class="delete">activity</span><span class="delete">aIdentifierOrMarker</span>
+
+
+
+<span class="delete">attributes</span><span class="delete">optionalAttributeValuePairs</span>
+
+
+
+
+
+<span class="delete">Example 27</span>
+
+ <span class="delete">actedOnBehalfOf(del1; ag2, ag1, a, [prov:type="contract"])
+ </span>
+<span class="delete"> Here </span><span class="delete">del1</span><span class="delete"> is the optional delegation identifier,
+ </span><span class="delete">ag2</span><span class="delete"> is the identifier for the delegate agent,
+ </span><span class="delete">ag1</span><span class="delete"> is the identifier of the responsible agent,
+ </span><span class="delete">a</span><span class="delete"> is the optional identifier of the activity for which the delegation link holds,
+ and </span><span class="delete">[prov:type="contract"]</span><span class="delete"> are optional attributes. </span><span class="delete">
The remaining examples show cases where some of the optionals are omitted.
-<pre class="codeexample">actedOnBehalfOf(ag1, ag2)
+</span><span class="delete">actedOnBehalfOf(ag1, ag2)
actedOnBehalfOf(ag1, ag2, a)
actedOnBehalfOf(ag1, ag2, -, [prov:type="delegation"])
actedOnBehalfOf(ag2, ag3, a, [prov:type="contract"])
actedOnBehalfOf(del1; ag2, ag3, a, [prov:type="contract"])
-</pre>
-</div>
-
-
-</section>
-
-<section id="expression-influence">
-<h4><span class="secno">3.3.5 </span>Influence</h4>
-
-
-<table class="grammar">
-<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;">
-<tbody><tr><td><b><a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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" 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,
- <span class="name">e2</span> is an entity identifier,
- <span class="name">e1</span> is the identifier for an ancestor entity that <span class="name">e2</span> is influenced by,
- and <span class="name">[ex:param="a"]</span> is the optional set of attributes. </p>
+</span>
+
+
+
+
+
+
+<span class="delete">3.3.5 </span><span class="delete">Influence</span>
+
+
+
+ <span class="delete">[</span><span class="delete">22</span><span class="delete">] </span> <span class="delete">influenceExpression</span> <span class="delete"> ::= </span> <span class="delete">"wasInfluencedBy" "(" </span><span class="delete">optionalIdentifier</span> <span class="delete">eIdentifier</span><span class="delete"> "," </span><span class="delete">eIdentifier</span> <span class="delete">optionalAttributeValuePairs</span><span class="delete"> ")"</span>
+
+
+
+<span class="delete">The following table summarizes how each constituent of a PROV-DM Influence maps to a PROV-N syntax element.</span>
+
+
+<span class="delete">Influence</span><span class="delete">Non-Terminal</span>
+
+
+<span class="delete">id</span><span class="delete">optionalIdentifier</span>
+
+<span class="delete">influencee</span><span class="delete">eIdentifier</span>
+
+<span class="delete">influencer</span><span class="delete">eIdentifier</span>
+
+<span class="delete">attributes</span><span class="delete">optionalAttributeValuePairs</span>
+
+
+
+
+<span class="delete">Example 28</span>
+ <span class="delete">wasInfluencedBy(infl1;e2,e1,[ex:param="a"])
+ </span>
+<span class="delete"> Here,
+ </span><span class="delete">infl1</span><span class="delete"> is the optional influence identifier,
+ </span><span class="delete">e2</span><span class="delete"> is an entity identifier,
+ </span><span class="delete">e1</span><span class="delete"> is the identifier for an ancestor entity that </span><span class="delete">e2</span><span class="delete"> is influenced by,
+ and </span><span class="delete">[ex:param="a"]</span><span class="delete"> is the optional set of attributes. </span><span class="delete">
The remaining examples show cases where some of the optionals are omitted.
- <pre class="codeexample">wasInfluencedBy(e2,e1)
+ </span><span class="delete">wasInfluencedBy(e2,e1)
wasInfluencedBy(e2,e1,[ex:param="a"])
wasInfluencedBy(infl1; e2,e1)
-</pre>
-</div>
-
-</section>
-
-</section>
-
-<section id="component4">
-<h3><span class="secno">3.4 </span>Component 4: Bundles</h3>
-
-<section id="expression-bundle-constructor">
-<h4><span class="secno">3.4.1 </span>Bundle Constructor</h4>
-
-<table class="grammar">
-<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 <span class="delete">nested because </span><span class="insert">nested. It is for this reason that </span>a <code><a class="grammarRef" href="#prod-bundle">bundle</a></code> is not <span class="insert">defined as </span>an <code><a class="grammarRef" href="#prod-expression">expression</a></code>,<span class="delete"> and therefore cannot occur</span><span class="insert"> to prevent the occurrence of a </span><code><a class="grammarRef" href="#prod-bundle"><span class="insert">bundle</span></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, <span class="delete">must</span><em class="rfc2119" title="MUST"><span class="insert">MUST</span></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;">
-<tbody><tr><td><b><a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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"><div class="anexampleTitle"><a class="internalDFN" href="#anexample-bundle1">Example 29</a></div>
- <pre class="codeexample">bundle ex:author-view
+</span>
+
+
+
+
+
+
+
+<span class="delete">3.4 </span><span class="delete">Component 4: Bundles</span>
+
+
+<span class="delete">3.4.1 </span><span class="delete">Bundle Constructor</span>
+
+
+ <span class="delete">[</span><span class="delete">23</span><span class="delete">] </span> <span class="delete">bundle</span> <span class="delete"> ::= </span> <span class="delete">"bundle" </span><span class="delete">identifier</span><span class="delete"> (</span><span class="delete">namespaceDeclarations</span><span class="delete">)? (</span><span class="delete">expression</span><span class="delete">)* "endBundle"</span>
+
+
+<span class="delete">Bundles cannot be nested. It is for this reason that a </span><span class="delete">bundle</span><span class="delete"> is not defined as an </span><span class="delete">expression</span><span class="delete">, to prevent the occurrence of a </span><span class="delete">bundle</span><span class="delete"> inside another </span><span class="delete">bundle</span><span class="delete">.</span>
+
+<span class="delete">Each identifier occurring in a bundle, including the bundle identifier itself, </span><span class="delete">MUST</span><span class="delete"> 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. </span>
+
+
+<span class="delete">The following table summarizes how each constituent of a PROV-DM bundle maps to a PROV-N syntax element.</span>
+
+
+<span class="delete">Bundle</span><span class="delete">Non-Terminal</span>
+
+
+<span class="delete">id</span><span class="delete">optionalIdentifier</span>
+
+<span class="delete">descriptions</span><span class="delete">expression</span>
+
+<span class="delete">namespaceDeclaration</span><span class="delete">namespaceDeclarations</span>
+
+
+
+
+
+
+<span class="delete">Example 29</span>
+ <span class="delete">bundle ex:author-view
prefix ex <http://example.org/>
agent(ex:Paolo, [ prov:type='prov:Person' ])
agent(ex:Simon, [ prov:type='prov:Person' ])
//...
endBundle
- </pre>
-<p> Here <span class="name">ex:author-view</span> is the name of the bundle.
-</p>
-
-
-
-
-</div>
-
-</section>
-
-<section id="expression-bundle-type">
-<h4><span class="secno">3.4.2 </span>Bundle Type</h4>
-
-<p id="provn-type-Bundle">
-When described, a Bundle <span class="delete">must</span><em class="rfc2119" title="MUST"><span class="insert">MUST</span></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 29</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' ])
-</pre>
-</div>
-</section>
-</section>
-
-<section id="component5">
-<h3><span class="secno">3.5 </span>Component 5: Alternate Entities</h3>
-<section id="expression-alternate">
-<h4><span class="secno">3.5.1 </span>Alternate</h4>
-
-
-
-<table class="grammar">
-
-<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>
-
-
-<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;">
-<tbody><tr><td><b><a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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" 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>
-
-
-</section>
-<section id="expression-specialization">
-<h4><span class="secno">3.5.2 </span>Specialization</h4>
-
-
-<table class="grammar">
-
-<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;">
-<tbody><tr><td><b><a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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" 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>
-
-</section>
-
-
-
-
-
-
-
-</section>
-
-
-
-<section id="component6">
-<h3><span class="secno">3.6 </span>Component 6: Collections</h3>
-
-
-<section id="expression-collection">
-<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 <span class="delete">must</span><em class="rfc2119" title="MUST"><span class="insert">MUST</span></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" 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.
-</p><pre class="codeexample"> entity(ex:col1, [ prov:type='prov:Collection' ])
+ </span>
+<span class="delete"> Here </span><span class="delete">ex:author-view</span><span class="delete"> is the name of the bundle.
+</span>
+
+
+
+
+
+
+
+
+
+<span class="delete">3.4.2 </span><span class="delete">Bundle Type</span>
+
+<span class="delete">
+When described, a Bundle </span><span class="delete">MUST</span><span class="delete"> be expressed as an </span><span class="delete">entityExpression</span><span class="delete"> with attribute </span><span class="delete">prov:type='prov:Bundle'</span><span class="delete">.</span>
+
+<span class="delete">Example 30</span>
+<span class="delete">The bundle of
+</span><span class="delete">Example 29</span><span class="delete"> can be referred to as an an entity, and its provenance described.</span>
+<span class="delete"> entity(ex:author-view, [ prov:type='prov:Bundle' ])
+</span>
+
+
+
+
+
+<span class="delete">3.5 </span><span class="delete">Component 5: Alternate Entities</span>
+
+<span class="delete">3.5.1 </span><span class="delete">Alternate</span>
+
+
+
+
+
+ <span class="delete">[</span><span class="delete">24</span><span class="delete">] </span> <span class="delete">alternateExpression</span> <span class="delete"> ::= </span> <span class="delete">"alternateOf" "(" </span><span class="delete">eIdentifier</span><span class="delete"> "," </span><span class="delete">eIdentifier</span><span class="delete"> ")"</span>
+
+
+
+
+<span class="delete">The following table summarizes how each constituent of a PROV-DM Alternate maps to a PROV-N syntax element.</span>
+
+
+<span class="delete">Alternate</span><span class="delete">Non-Terminal</span>
+
+
+
+<span class="delete">alternate1</span><span class="delete">eIdentifier</span>
+
+
+<span class="delete">alternate2</span><span class="delete">eIdentifier</span>
+
+
+
+
+<span class="delete">Example 31</span>
+<span class="delete">alternateOf(tr:WD-prov-dm-20111215,ex:alternate-20111215)
+</span><span class="delete">
+ Here </span><span class="delete">tr:WD-prov-dm-20111215</span><span class="delete"> is alternate for </span><span class="delete">ex:alternate-20111215</span><span class="delete">.
+</span>
+
+
+
+
+<span class="delete">3.5.2 </span><span class="delete">Specialization</span>
+
+
+
+
+ <span class="delete">[</span><span class="delete">25</span><span class="delete">] </span> <span class="delete">specializationExpression</span> <span class="delete"> ::= </span> <span class="delete">"specializationOf" "(" </span><span class="delete">eIdentifier</span><span class="delete"> "," </span><span class="delete">eIdentifier</span><span class="delete"> ")"</span>
+
+
+
+<span class="delete">The following table summarizes how each constituent of a PROV-DM Specialization maps to a PROV-N syntax element.</span>
+
+
+<span class="delete">Specialization</span><span class="delete">Non-Terminal</span>
+
+
+
+<span class="delete">specificEntity</span><span class="delete">eIdentifier</span>
+
+
+<span class="delete">generalEntity</span><span class="delete">eIdentifier</span>
+
+
+
+
+
+<span class="delete">Example 32</span>
+<span class="delete">specializationOf(tr:WD-prov-dm-20111215,tr:prov-dm)
+</span><span class="delete">
+ Here </span><span class="delete">tr:WD-prov-dm-20111215</span><span class="delete"> is a specialization of </span><span class="delete">tr:prov-dm</span><span class="delete">.
+</span>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<span class="delete">3.6 </span><span class="delete">Component 6: Collections</span>
+
+
+
+<span class="delete">3.6.1 </span><span class="delete">Collection</span>
+
+
+<span class="delete">
+PROV-N provides no dedicated syntax for Collection and EmptyCollection. Instead, a Collection or an EmptyCollection </span><span class="delete">MUST</span><span class="delete"> be expressed as an
+</span><span class="delete">entityExpression</span><span class="delete"> with attribute
+</span><span class="delete">prov:type='prov:Collection'</span><span class="delete">, or
+</span><span class="delete">prov:type='prov:EmptyCollection'</span><span class="delete">, respectively.</span>
+
+
+
+<span class="delete">Example 33</span>
+<span class="delete">The following two expressions are about a collection and an empty collection, respectively.
+</span><span class="delete"> entity(ex:col1, [ prov:type='prov:Collection' ])
entity(ex:col2, [ prov:type='prov:EmptyCollection' ])
-</pre>
-</div>
-</section>
-
-
-<section id="expression-collection-membership">
-<h4><span class="secno">3.6.2 </span>Membership</h4>
-
-
-
-<table class="grammar">
-<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;">
-<tbody><tr><td><b><a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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/PR-prov-dm-20130312/#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" 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
+</span>
+
+
+
+
+
+<span class="delete">3.6.2 </span><span class="delete">Membership</span>
+
+
+
+
+ <span class="delete">[</span><span class="delete">26</span><span class="delete">] </span> <span class="delete">membershipExpression</span> <span class="delete"> ::= </span> <span class="delete">"hadMember" "(" </span><span class="delete">cIdentifier</span><span class="delete"> "," </span><span class="delete">eIdentifier</span><span class="delete"> ")"</span>
+
+
+
+<span class="delete">The following table summarizes how each constituent of a PROV-DM Membership maps to a PROV-N syntax element.</span>
+
+
+<span class="delete">Membership</span><span class="delete">Non-Terminal</span>
+
+
+
+<span class="delete">collection</span><span class="delete">cIdentifier</span>
+
+<span class="delete">entity</span><span class="delete">eIdentifier</span>
+
+
+
+
+
+
+<span class="delete">Example 34</span>
+ <span class="delete"> hadMember(c, e1) // c contained e1
hadMember(c, e2) // c contained e2
- </pre>
-<p> Here
- <span class="name">c</span> is the identifier for the collection whose membership is stated, and
- <span class="name">e1</span> and <span class="name">e2</span> are the entities that are members of collection c
-
-
-</p></div>
-
-</section>
-
-</section>
-
-
-
-
-
-<section id="subexpressions">
-<h3><span class="secno">3.7 </span>Further Expressions</h3>
+ </span>
+<span class="delete"> Here
+ </span><span class="delete">c</span><span class="delete"> is the identifier for the collection whose membership is stated, and
+ </span><span class="delete">e1</span><span class="delete"> and </span><span class="delete">e2</span><span class="delete"> are the entities that are members of collection c
+
+
+</span>
+
+
+
+
+
+
+
+
+
+
+<span class="delete">3.7 </span><span class="delete">Further Expressions</span><span class="delete">
This section defines further expressions of PROV-N.
-<section id="expression-identifier">
-<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="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>
-
-
-<p>
-A <dfn id="dfn-qualifiedName">qualified name</dfn> is a name subject to namespace interpretation. It consists of a <span class="delete">namespace</span><span class="delete">,</span><span class="insert">namespace,</span> denoted by an optional prefix, and a local name.
+</span>
+<span class="delete">3.7.1 </span><span class="delete">Identifier</span>
+
+<span class="delete">Various kinds of identifiers are used in productions.</span>
+
+
+ <span class="delete">[</span><span class="delete">27</span><span class="delete">] </span> <span class="delete">eIdentifier</span> <span class="delete"> ::= </span> <span class="delete">identifier</span>
+ <span class="delete">[</span><span class="delete">28</span><span class="delete">] </span> <span class="delete">aIdentifier</span> <span class="delete"> ::= </span> <span class="delete">identifier</span>
+ <span class="delete">[</span><span class="delete">29</span><span class="delete">] </span> <span class="delete">agIdentifier</span> <span class="delete"> ::= </span> <span class="delete">identifier</span>
+ <span class="delete">[</span><span class="delete">30</span><span class="delete">] </span> <span class="delete">gIdentifier</span> <span class="delete"> ::= </span> <span class="delete">identifier</span>
+ <span class="delete">[</span><span class="delete">31</span><span class="delete">] </span> <span class="delete">uIdentifier</span> <span class="delete"> ::= </span> <span class="delete">identifier</span>
+ <span class="delete">[</span><span class="delete">32</span><span class="delete">] </span> <span class="delete">cIdentifier</span> <span class="delete"> ::= </span> <span class="delete">identifier</span>
+
+ <span class="delete">[</span><span class="delete">33</span><span class="delete">] </span> <span class="delete">eIdentifierOrMarker</span> <span class="delete"> ::= </span> <span class="delete">( </span><span class="delete">eIdentifier</span><span class="delete"> | "-" )</span>
+ <span class="delete">[</span><span class="delete">34</span><span class="delete">] </span> <span class="delete">aIdentifierOrMarker</span> <span class="delete"> ::= </span> <span class="delete">( </span><span class="delete">aIdentifier</span><span class="delete"> | "-" )</span>
+ <span class="delete">[</span><span class="delete">35</span><span class="delete">] </span> <span class="delete">agIdentifierOrMarker</span> <span class="delete"> ::= </span> <span class="delete">( </span><span class="delete">agIdentifier</span><span class="delete"> | "-" )</span>
+ <span class="delete">[</span><span class="delete">36</span><span class="delete">] </span> <span class="delete">gIdentifierOrMarker</span> <span class="delete"> ::= </span> <span class="delete">( </span><span class="delete">gIdentifier</span><span class="delete"> | "-" )</span>
+ <span class="delete">[</span><span class="delete">37</span><span class="delete">] </span> <span class="delete">uIdentifierOrMarker</span> <span class="delete"> ::= </span> <span class="delete">( </span><span class="delete">uIdentifier</span><span class="delete"> | "-" )</span>
+ <span class="delete">[</span><span class="delete">38</span><span class="delete">] </span> <span class="delete">identifier</span> <span class="delete"> ::= </span> <span class="delete">QUALIFIED_NAME</span>
+
+
+
+<span class="delete">
+A </span><span class="delete">qualified name</span><span class="delete"> is a name subject to namespace interpretation. It consists of a namespace, denoted by an optional prefix, and a local name.
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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></em>. If a prefix occurs in a
- qualified name, the prefix <span class="delete">must</span><em class="rfc2119" title="MUST"><span class="insert">MUST</span></em> refer to a namespace declared in a namespace declaration. In the absence of prefix, the qualified name
- belongs to the default <span class="delete">namespace</span><span class="delete">.</span><span class="insert">namespace.</span></p>
-
-
-
-
-<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> [<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><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>
-
-
-
-<p>Given that
+ 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. </span>
+
+<span class="delete">A qualified name's prefix is </span><span class="delete">OPTIONAL</span><span class="delete">. If a prefix occurs in a
+ qualified name, the prefix </span><span class="delete">MUST</span><span class="delete"> refer to a namespace declared in a namespace declaration. In the absence of prefix, the qualified name
+ belongs to the default namespace.</span>
+
+
+
+
+<span class="delete">A PROV-N qualified name (production </span><span class="delete">QUALIFIED_NAME</span><span class="delete">) has a more permissive syntax then XML's </span><span class="delete">QName</span><span class="delete"> [</span><span class="delete">XML-NAMES</span><span class="delete">]
+and SPARQL </span><span class="delete">PrefixedName</span><span class="delete"> [</span><span class="delete">RDF-SPARQL-QUERY</span><span class="delete">].
+A </span><span class="delete">QUALIFIED_NAME</span><span class="delete"> consists of a prefix and a local part. Prefixes follow the production </span><span class="delete">PN_PREFIX</span><span class="delete"> defined by SPARQL [</span><span class="delete">RDF-SPARQL-QUERY</span><span class="delete">]. Local parts have to be conformant with </span><span class="delete">PN_LOCAL</span><span class="delete">, which extends the original SPARQL </span><span class="delete">PN_LOCAL</span><span class="delete"> definition
+by allowing further characters (see </span><span class="delete">PN_CHARS_OTHERS</span><span class="delete">):</span>
+
+<span class="delete"> an extra set of characters commonly encountered in IRIs;
+</span><span class="delete"> %-escaped characters (see </span><span class="delete">PERCENT</span><span class="delete">) to be interpreted as per
+ Section 3.1. Mapping of IRIs to URIs in [</span><span class="delete">RFC3987</span><span class="delete">];</span>
+<span class="delete"> and \-escaped characters (see </span><span class="delete">PN_CHARS_ESC</span><span class="delete">).</span>
+
+
+
+
+<span class="delete">Given that
'=' (equal),
''' (single quote),
'(' (left bracket),
@@ -2446,28 +2370,28 @@
'[' (left square bracket),
']' (right square bracket) are used by the PROV notation as delimiters, they are not allowed in local parts.
Instead, among those characters, those that are permitted in SPARQL
-<code class="content"><a class="grammarRef" href="http://www.w3.org/TR/rdf-sparql-query/#rIRI_REF">IRI_REF</a></code> are also allowed in <code class="content"><a class="grammarRef" href="#prod-PN_LOCAL">PN_LOCAL</a></code> if they are escaped by the '\' (backslash character) as per production <code class="content"><a class="grammarRef" href="#prod-PN_CHARS_ESC">PN_CHARS_ESC</a></code>. Furthermore, '.' (dot), ':' (colon), '-' (hyphen) can also be \-escaped.</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>
+</span><span class="delete">IRI_REF</span><span class="delete"> are also allowed in </span><span class="delete">PN_LOCAL</span><span class="delete"> if they are escaped by the '\' (backslash character) as per production </span><span class="delete">PN_CHARS_ESC</span><span class="delete">. Furthermore, '.' (dot), ':' (colon), '-' (hyphen) can also be \-escaped.</span>
+
+
+
+<span class="delete">A PROV-N qualified name </span><span class="delete">QUALIFIED_NAME</span><span class="delete"> can be mapped to a valid IRI [</span><span class="delete">RFC3987</span><span class="delete">] by concatenating the namespace denoted its local name </span><span class="delete">PN_PREFIX</span><span class="delete"> to the local name </span><span class="delete">PN_LOCAL</span><span class="delete">, whose \-escaped characters have been unescaped by dropping the character '\' (backslash).</span>
-<table class="grammar">
-<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="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
+
+ <span class="delete">[</span><span class="delete">52</span><span class="delete">] </span> <span class="delete"><</span><span class="delete">QUALIFIED_NAME</span><span class="delete">></span> <span class="delete"> ::= </span> <span class="delete">( </span><span class="delete">PN_PREFIX</span><span class="delete"> ":" )? </span><span class="delete">PN_LOCAL</span><span class="delete"> | </span><span class="delete">PN_PREFIX</span><span class="delete"> ":"</span>
+ <span class="delete">[</span><span class="delete">53</span><span class="delete">] </span> <span class="delete"><</span><span class="delete">PN_LOCAL</span><span class="delete">></span> <span class="delete"> ::= </span> <span class="delete">( </span><span class="delete">PN_CHARS_U</span><span class="delete"> | [0-9] | </span><span class="delete">PN_CHARS_OTHERS</span><span class="delete"> ) ( ( </span><span class="delete">PN_CHARS</span><span class="delete"> | "." | </span><span class="delete">PN_CHARS_OTHERS</span><span class="delete"> )* ( </span><span class="delete">PN_CHARS</span><span class="delete"> | </span><span class="delete">PN_CHARS_OTHERS</span><span class="delete"> ) )?</span>
+ <span class="delete">[</span><span class="delete">54</span><span class="delete">] </span> <span class="delete"><</span><span class="delete">PN_CHARS_OTHERS</span><span class="delete">></span> <span class="delete"> ::= </span> <span class="delete">"/"</span><span class="delete"> | "@"</span><span class="delete"> | "~"</span><span class="delete"> | "&"</span><span class="delete"> | "+"</span><span class="delete"> | "*"</span><span class="delete"> | "?"</span><span class="delete"> | "#"</span><span class="delete"> | "$"</span><span class="delete"> | "!"</span><span class="delete"> | </span><span class="delete">PERCENT</span><span class="delete"> | </span><span class="delete">PN_CHARS_ESC</span>
+ <span class="delete">[</span><span class="delete">55</span><span class="delete">] </span> <span class="delete"><</span><span class="delete">PN_CHARS_ESC</span><span class="delete">></span> <span class="delete"> ::= </span> <span class="delete">"\" ( "=" | "'" | "(" | ")" | "," | "-" | ":" | ";" | "[" | "]" | "." )</span>
+ <span class="delete">[</span><span class="delete">56</span><span class="delete">] </span> <span class="delete"><</span><span class="delete">PERCENT</span><span class="delete">></span> <span class="delete"> ::= </span> <span class="delete">"%" </span><span class="delete">HEX</span> <span class="delete">HEX</span>
+ <span class="delete">[</span><span class="delete">57</span><span class="delete">] </span> <span class="delete"><</span><span class="delete">HEX</span><span class="delete">></span> <span class="delete"> ::= </span> <span class="delete">[0-9]</span><span class="delete"> | [A-F]</span><span class="delete"> | [a-f]</span>
+
+
+
+
+
+<span class="delete">Example 35</span>
+<span class="delete">Examples of articles on the BBC Web site seen as entities.</span>
+<span class="delete">document
prefix bbc <http://www.bbc.co.uk/>
prefix bbcNews <http://www.bbc.co.uk/news/>
@@ -2478,13 +2402,13 @@
entity(bbcNews:) // an alternative way of referring to the bbc news site
endDocument
-</pre>
-</div>
-
-
-<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
+</span>
+
+
+
+<span class="delete">Example 36</span>
+<span class="delete">Examples of entities with declared and default namespace.</span>
+<span class="delete">document
default <http://example.org/2/>
prefix ex <http://example.org/1/>
@@ -2497,13 +2421,13 @@
entity(c/) // corresponds to IRI http://example.org/2/c/
entity(ex:/) // corresponds to IRI http://example.org/1//
endDocument
-</pre>
-</div>
-
-
-<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
+</span>
+
+
+
+<span class="delete">Example 37</span>
+<span class="delete">Examples of \-escaped characters.</span>
+<span class="delete">document
prefix ex <http://example.org/>
default <http://example.org/default>
@@ -2514,237 +2438,237 @@
used(-;a1,e1,-) // identifier not specified for usage
used(\-;a1,e1,-) // usage identifier corresponds to http://example.org/default-
endDocument
-</pre>
-</div>
-
-
-<p><b>Note:</b> The productions for the terminals <code class="content"><a class="grammarRef" href="#prod-QUALIFIED_NAME">QUALIFIED_NAME</a></code> and <code class="content"><a class="grammarRef" href="http://www.w3.org/TR/rdf-sparql-query/#rPN_PREFIX">PN_PREFIX</a></code> are conflicting.
-Indeed, for a tokenizer operating independently of the parse tree, <code>abc</code> matches both
-<code class="content"><a class="grammarRef" href="#prod-QUALIFIED_NAME">QUALIFIED_NAME</a></code> and
-<code class="content"><a class="grammarRef" href="http://www.w3.org/TR/rdf-sparql-query/#rPN_PREFIX">PN_PREFIX</a></code>.
- In the context of a <code class="content"><a class="grammarRef" href="#prod-namespaceDeclaration">namespaceDeclaration</a></code>, a tokenizer should give preference to the production <code class="content"><a class="grammarRef" href="http://www.w3.org/TR/rdf-sparql-query/#rPN_PREFIX">PN_PREFIX</a></code>.
-</p>
-
-
-</section>
-
-<section id="expression-attribute">
-<h4><span class="secno">3.7.2 </span>Attribute</h4>
-
-
-
-<table class="grammar">
-<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 [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>] (see <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#term-attribute">Section 5.7.2: Attribute</a>).
-</p>
-
-<ol>
-<li> <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#term-attribute-label"><span class="name">prov:label</span></a>
-</li><li> <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#term-attribute-location"><span class="name">prov:location</span></a>
-</li><li> <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#term-attribute-role"><span class="name">prov:role</span></a>
-</li><li> <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#term-attribute-type"><span class="name">prov:type</span></a>
-</li><li> <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#term-attribute-value"><span class="name">prov:value</span></a>
-</li></ol>
-
-
-</section>
-
-
-
-
-
-<section id="expression-literal">
-<h4><span class="secno">3.7.3 </span>Literal</h4>
-
-
-
-<table class="grammar">
-<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/PR-prov-dm-20130312/#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>
+</span>
+
+
+
+<span class="delete">Note:</span><span class="delete"> The productions for the terminals </span><span class="delete">QUALIFIED_NAME</span><span class="delete"> and </span><span class="delete">PN_PREFIX</span><span class="delete"> are conflicting.
+Indeed, for a tokenizer operating independently of the parse tree, </span><span class="delete">abc</span><span class="delete"> matches both
+</span><span class="delete">QUALIFIED_NAME</span><span class="delete"> and
+</span><span class="delete">PN_PREFIX</span><span class="delete">.
+ In the context of a </span><span class="delete">namespaceDeclaration</span><span class="delete">, a tokenizer should give preference to the production </span><span class="delete">PN_PREFIX</span><span class="delete">.
+</span>
+
+
+
+
+
+<span class="delete">3.7.2 </span><span class="delete">Attribute</span>
+
+
+
+
+ <span class="delete">[</span><span class="delete">39</span><span class="delete">] </span> <span class="delete">attribute</span> <span class="delete"> ::= </span> <span class="delete">QUALIFIED_NAME</span>
+
+
+
+<span class="delete">The reserved attributes in the PROV namespace are the following.
+Their meaning is explained by [</span><span class="delete">PROV-DM</span><span class="delete">] (see </span><span class="delete">Section 5.7.2: Attribute</span><span class="delete">).
+</span>
+
+
+ <span class="delete">prov:label</span>
+ <span class="delete">prov:location</span>
+ <span class="delete">prov:role</span>
+ <span class="delete">prov:type</span>
+ <span class="delete">prov:value</span>
+
+
+
+
+
+
+
+
+
+
+<span class="delete">3.7.3 </span><span class="delete">Literal</span>
+
+
+
+
+ <span class="delete">[</span><span class="delete">40</span><span class="delete">] </span> <span class="delete">literal</span> <span class="delete"> ::= </span> <span class="delete">typedLiteral</span><span class="delete"> | </span><span class="delete">convenienceNotation</span>
+ <span class="delete">[</span><span class="delete">41</span><span class="delete">] </span> <span class="delete">typedLiteral</span> <span class="delete"> ::= </span> <span class="delete">STRING_LITERAL</span><span class="delete"> "%%" </span><span class="delete">datatype</span>
+ <span class="delete">[</span><span class="delete">42</span><span class="delete">] </span> <span class="delete">datatype</span> <span class="delete"> ::= </span> <span class="delete">QUALIFIED_NAME</span>
+ <span class="delete">[</span><span class="delete">43</span><span class="delete">] </span> <span class="delete">convenienceNotation</span> <span class="delete"> ::= </span> <span class="delete">STRING_LITERAL</span><span class="delete"> (</span><span class="delete">LANGTAG</span><span class="delete">)?</span><span class="delete"> | </span><span class="delete">INT_LITERAL</span><span class="delete"> | </span><span class="delete">QUALIFIED_NAME_LITERAL</span>
+ <span class="delete">[</span><span class="delete">58</span><span class="delete">] </span> <span class="delete"><</span><span class="delete">STRING_LITERAL</span><span class="delete">></span> <span class="delete"> ::= </span> <span class="delete">STRING_LITERAL2</span><span class="delete"> | </span><span class="delete">STRING_LITERAL_LONG2</span>
+ <span class="delete">[</span><span class="delete">60</span><span class="delete">] </span> <span class="delete"><</span><span class="delete">INT_LITERAL</span><span class="delete">></span> <span class="delete"> ::= </span> <span class="delete">("-")? (</span><span class="delete">DIGIT</span><span class="delete">)+</span>
+ <span class="delete">[</span><span class="delete">62</span><span class="delete">] </span> <span class="delete"><</span><span class="delete">DIGIT</span><span class="delete">></span> <span class="delete"> ::= </span> <span class="delete">[0-9]</span>
+ <span class="delete">[</span><span class="delete">61</span><span class="delete">] </span> <span class="delete"><</span><span class="delete">QUALIFIED_NAME_LITERAL</span><span class="delete">></span> <span class="delete"> ::= </span> <span class="delete">"'" </span><span class="delete">QUALIFIED_NAME</span><span class="delete"> "'"</span>
+
+
+<span class="delete">In production </span><span class="delete">datatype</span><span class="delete">, the </span><span class="delete">QUALIFIED_NAME</span><span class="delete"> is used to denote a </span><span class="delete">PROV data type</span><span class="delete"> [</span><span class="delete">PROV-DM</span><span class="delete">].
+
+
+</span><span class="delete">The non terminals
+</span><span class="delete">STRING_LITERAL</span><span class="delete">,
+</span><span class="delete">INT_LITERAL</span><span class="delete">, and
+</span><span class="delete">QUALIFIED_NAME_LITERAL</span><span class="delete">
are syntactic sugar for quoted strings with datatype
-<code class="content"><a href="http://www.w3.org/TR/xmlschema11-2/#string"><span class="name">xsd:string</span></a></code>,
-<code class="content"><a href="http://www.w3.org/TR/xmlschema11-2/#int"><span class="name">xsd:int</span></a></code>, and
-<code class="content"><a class="grammarRef" href="#prod-QUALIFIED_NAME">prov:QUALIFIED_NAME</a></code>
+</span><span class="delete">xsd:string</span><span class="delete">,
+</span><span class="delete">xsd:int</span><span class="delete">, and
+</span><span class="delete">prov:QUALIFIED_NAME</span><span class="delete">
respectively.
-</p>
-
-<p> In particular, a Literal may be an IRI-typed string (with datatype <span class="name">xsd:anyURI</span>); such IRI has no specific interpretation in the context of PROV.</p>
-
-
-<p><b>Note:</b> The productions for terminals <code class="content"><a class="grammarRef" href="#prod-QUALIFIED_NAME">QUALIFIED_NAME</a></code> and
-<code class="content"><a class="grammarRef" href="#prod-INT_LITERAL">INT_LITERAL</a></code> are conflicting.
-Indeed, for a tokenizer operating independently of the parse tree, <code>1234</code> matches both <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">QUALIFIED_NAME</a></code> (local name without prefix). In the context of
-a <code class="content"><a class="grammarRef" href="#prod-convenienceNotation">convenienceNotation</a></code>, a tokenizer should give preference to the production
-<code class="content"><a class="grammarRef" href="#prod-INT_LITERAL">INT_LITERAL</a></code>.
-</p>
-
-<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
+</span>
+
+<span class="delete"> In particular, a Literal may be an IRI-typed string (with datatype </span><span class="delete">xsd:anyURI</span><span class="delete">); such IRI has no specific interpretation in the context of PROV.</span>
+
+
+<span class="delete">Note:</span><span class="delete"> The productions for terminals </span><span class="delete">QUALIFIED_NAME</span><span class="delete"> and
+</span><span class="delete">INT_LITERAL</span><span class="delete"> are conflicting.
+Indeed, for a tokenizer operating independently of the parse tree, </span><span class="delete">1234</span><span class="delete"> matches both </span><span class="delete">INT_LITERAL</span><span class="delete"> and </span><span class="delete">QUALIFIED_NAME</span><span class="delete"> (local name without prefix). In the context of
+a </span><span class="delete">convenienceNotation</span><span class="delete">, a tokenizer should give preference to the production
+</span><span class="delete">INT_LITERAL</span><span class="delete">.
+</span>
+
+<span class="delete">Example 38</span>
+<span class="delete">
+The following examples illustrate convenience notations.</span>
+
+<span class="delete">The two following expressions are strings; if </span><span class="delete">datatype</span><span class="delete"> is not specified, it is </span><span class="delete">xsd:string</span><span class="delete">.</span>
+<span class="delete"> "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
+</span>
+
+
+<span class="delete">The two following expressions are integers. For convenience, numbers, expressed as digits optionally preceded by a minus sign, can occur without quotes.</span>
+<span class="delete"> "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
+</span>
+
+<span class="delete">The two following expressions are qualified names. Values of type qualified name can be conveniently expressed within single quotes.</span>
+<span class="delete"> "ex:value" %% prov:QUALIFIED_NAME
'ex:value'
-</pre>
-</div>
-
-<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"
+</span>
+
+
+<span class="delete">Example 39</span>
+<span class="delete">
+The following examples respectively are the string "abc", the string (in French) "bonjour", the integer number 1, and the IRI "http://example.org/foo".</span>
+<span class="delete"> "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
+</span>
+<span class="delete">The following examples respectively are the floating point number 1.01 and the boolean true.</span>
+<span class="delete"> "1.01" %% xsd:float
"true" %% xsd:boolean
-</pre>
-</div>
-
-
-
-<section id="expression-types">
-<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 [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>] (see <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#term-attribute-type">Section 5.7.2.4: prov:type</a>).
-</p>
-
-<ol>
-<li> <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#term-bundle-entity"><span class="name">prov:Bundle</span></a>
-</li><li> <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#concept-collection"><span class="name">prov:Collection</span></a>
-</li><li> <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#concept-empty-collection"><span class="name">prov:EmptyCollection</span></a>
-</li><li> <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#concept-organization"><span class="name">prov:Organization</span></a>
-</li><li> <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#concept-person"><span class="name">prov:Person</span></a>
-</li><li> <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#concept-plan"><span class="name">prov:Plan</span></a>
-</li><li> <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#dfn-primary-source"><span class="name">prov:PrimarySource</span></a>
-</li><li> <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#dfn-quotation"><span class="name">prov:Quotation</span></a>
-</li><li> <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#dfn-revision"><span class="name">prov:Revision</span></a>
-</li><li> <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#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' ])
+</span>
+
+
+
+
+
+<span class="delete">3.7.3.1 </span><span class="delete">Reserved Type Values</span>
+
+<span class="delete">The reserved type values in the PROV namespace are the following.
+Their meaning is defined [</span><span class="delete">PROV-DM</span><span class="delete">] (see </span><span class="delete">Section 5.7.2.4: prov:type</span><span class="delete">).
+</span>
+
+
+ <span class="delete">prov:Bundle</span>
+ <span class="delete">prov:Collection</span>
+ <span class="delete">prov:EmptyCollection</span>
+ <span class="delete">prov:Organization</span>
+ <span class="delete">prov:Person</span>
+ <span class="delete">prov:Plan</span>
+ <span class="delete">prov:PrimarySource</span>
+ <span class="delete">prov:Quotation</span>
+ <span class="delete">prov:Revision</span>
+ <span class="delete">prov:SoftwareAgent</span>
+
+
+<span class="delete">Example 40</span>
+<span class="delete">The agent </span><span class="delete">ag</span><span class="delete"> is a person (type: </span><span class="delete">prov:Person</span><span class="delete">), whereas the entity
+</span><span class="delete">pl</span><span class="delete"> is a plan (type: </span><span class="delete">prov:Plan</span><span class="delete">).</span>
+<span class="delete">agent(ag, [ prov:type='prov:Person' ])
entity(pl, [ prov:type='prov:Plan' ])
-</pre>
-</div>
-
-
-</section>
-
-<section id="expression-Time">
-<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="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="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>
-</div>
-
-
-
-
-</section>
-
-
-</section>
-
-
-
-
-
-<section id="expression-NamespaceDeclaration">
-<h4><span class="secno">3.7.4 </span>Namespace Declaration</h4>
-
-
-<table class="grammar">
-
-<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>
-
-<p>A <code><a class="grammarRef" href="#prod-namespaceDeclaration">namespaceDeclaration</a></code> consists of a binding between a prefix and a namespace. Every qualified name with this prefix in the scope of this declaration belongs to this namespace.
-A <code><a class="grammarRef" href="#prod-defaultNamespaceDeclaration">defaultNamespaceDeclaration</a></code> consists of a namespace. Every qualified name without prefix in the scope of this declaration belongs to this namespace. Scope of a prefix-namespace declaration is specified as follows:</p>
-<ul>
-<li>
-The scope of a prefix-namespace declaration directly occurring in a <code><a class="grammarRef" href="#prod-bundle">bundle</a></code> is the <code><a class="grammarRef" href="#prod-bundle">bundle</a></code> itself.</li>
-<li>
-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> <span class="delete">must not</span><em class="rfc2119" title="MUST NOT"><span class="insert">MUST NOT</span></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 <span class="delete">may</span><em class="rfc2119" title="MAY"><span class="insert">MAY</span></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> <span class="delete">must not</span><em class="rfc2119" title="MUST NOT"><span class="insert">MUST NOT</span></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
+</span>
+
+
+
+
+
+
+<span class="delete">3.7.3.2 </span><span class="delete">Time Values</span>
+
+<span class="delete">Time instants</span><span class="delete"> are defined according to xsd:dateTime [</span><span class="delete">XMLSCHEMA11-2</span><span class="delete">].</span>
+
+
+ <span class="delete">[</span><span class="delete">44</span><span class="delete">] </span> <span class="delete">time</span> <span class="delete"> ::= </span> <span class="delete">DATETIME</span>
+
+
+
+<span class="delete">Example 41</span>
+
+<span class="delete">The third argument in the following usage expression is a time instance, namely 4pm on 2011-11-16.</span>
+<span class="delete">used(ex:act2, ar3:0111, 2011-11-16T16:00:00)
+</span>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<span class="delete">3.7.4 </span><span class="delete">Namespace Declaration</span>
+
+
+
+
+ <span class="delete">[</span><span class="delete">45</span><span class="delete">] </span> <span class="delete">namespaceDeclarations</span> <span class="delete"> ::= </span> <span class="delete">( </span><span class="delete">defaultNamespaceDeclaration</span><span class="delete"> | </span><span class="delete">namespaceDeclaration</span><span class="delete"> ) (</span><span class="delete">namespaceDeclaration</span><span class="delete">)*</span>
+ <span class="delete">[</span><span class="delete">46</span><span class="delete">] </span> <span class="delete">namespaceDeclaration</span> <span class="delete"> ::= </span> <span class="delete">"prefix" </span><span class="delete">PN_PREFIX</span> <span class="delete">namespace</span>
+ <span class="delete">[</span><span class="delete">47</span><span class="delete">] </span> <span class="delete">defaultNamespaceDeclaration</span> <span class="delete"> ::= </span> <span class="delete">"default" </span><span class="delete">IRI_REF</span>
+ <span class="delete">[</span><span class="delete">48</span><span class="delete">] </span> <span class="delete">namespace</span> <span class="delete"> ::= </span> <span class="delete">IRI_REF</span>
+
+
+
+<span class="delete">A </span><span class="delete">namespaceDeclaration</span><span class="delete"> consists of a binding between a prefix and a namespace. Every qualified name with this prefix in the scope of this declaration belongs to this namespace.
+A </span><span class="delete">defaultNamespaceDeclaration</span><span class="delete"> consists of a namespace. Every qualified name without prefix in the scope of this declaration belongs to this namespace. Scope of a prefix-namespace declaration is specified as follows:</span>
+
+<span class="delete">
+The scope of a prefix-namespace declaration directly occurring in a </span><span class="delete">bundle</span><span class="delete"> is the </span><span class="delete">bundle</span><span class="delete"> itself.</span>
+<span class="delete">
+The scope of a prefix-namespace declaration directly occurring in a </span><span class="delete">document</span><span class="delete"> is the </span><span class="delete">document</span><span class="delete"> including the </span><span class="delete">bundles</span><span class="delete"> it contains but excluding those </span><span class="delete">bundles</span><span class="delete"> that re-declare this prefix.</span>
+
+
+<span class="delete">A set of namespace declarations </span><span class="delete">namespaceDeclarations</span> <span class="delete">MUST NOT</span><span class="delete"> re-declare the same prefix.</span>
+
+<span class="delete">A set of namespace declarations </span><span class="delete">namespaceDeclarations</span><span class="delete"> occurring in a bundle </span><span class="delete">MAY</span><span class="delete"> re-declare a prefix declared in a surrounding document.</span>
+
+<span class="delete">A namespace declaration </span><span class="delete">namespaceDeclaration</span> <span class="delete">MUST NOT</span><span class="delete"> declare prefixes </span><span class="delete">prov</span><span class="delete"> and </span><span class="delete">xsd</span><span class="delete"> (see </span><span class="delete">Table 1</span><span class="delete"> for their IRI).</span>
+
+
+
+<span class="delete">Example 42</span>
+<span class="delete">The following example declares three namespaces, one default, and two with explicit prefixes </span><span class="delete">ex1</span><span class="delete"> and </span><span class="delete">ex2</span><span class="delete">.</span>
+<span class="delete">document
default <http://example.org/0/>
prefix ex1 <http://example.org/1/>
prefix ex2 <http://example.org/2/>
...
endDocument
-</pre>
-</div>
-
-
-<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.
+</span>
+
+
+
+<span class="delete">Example 43</span>
+<span class="delete">In the following example, a document declares a default namespace and the occurrence of
+</span><span class="delete">e001</span><span class="delete"> 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
+</span><span class="delete">e001</span><span class="delete">, including the bundle name, refer to the latest default namespace.</span>
+<span class="delete">document
default <http://example.org/1/>
entity(e001) // IRI: http://example.org/1/e001
@@ -2753,16 +2677,16 @@
entity(e001) // IRI: http://example.org/2/e001
endBundle
endDocument
-</pre>
-</div>
-
-
-<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.
+</span>
+
+
+
+<span class="delete">Example 44</span>
+<span class="delete">In the following example, a document declares a namespace with prefix </span><span class="delete">ex</span><span class="delete"> and the occurrence of
+</span><span class="delete">ex:e001</span><span class="delete"> 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
+</span><span class="delete">ex:e001</span><span class="delete"> also refers to the same namespace.</span>
+<span class="delete">document
prefix ex <http://example.org/1/>
entity(ex:e001) // IRI: http://example.org/1/e001
@@ -2770,115 +2694,115 @@
entity(ex:001) // IRI: http://example.org/1/e001
endBundle
endDocument
-</pre>
-</div>
-
-
-
-
-</section>
-
-
-
-
-
-<section id="semantic-rules-summary">
-<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>
-<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/PR-prov-dm-20130312/#generation.id"><span class="attribute">id</span></a>, <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#generation.activity"><span class="attribute">activity</span></a>, <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#generation.time"><span class="attribute">time</span></a>, and <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#generation.attributes"><span class="attribute">attributes</span></a> <span class="delete">must</span><em class="rfc2119" title="MUST"><span class="insert">MUST</span></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/PR-prov-dm-20130312/#usage.id"><span class="attribute">id</span></a>, <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#usage.entity"><span class="attribute">entity</span></a>, <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#usage.time"><span class="attribute">time</span></a>, and <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#usage.attributes"><span class="attribute">attributes</span></a> <span class="delete">must</span><em class="rfc2119" title="MUST"><span class="insert">MUST</span></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/PR-prov-dm-20130312/#start.id"><span class="attribute">id</span></a>, <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#start.trigger"><span class="attribute">trigger</span></a>, <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#start.starter"><span class="attribute">starter</span></a>, <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#start.time"><span class="attribute">time</span></a>, and <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#start.attributes"><span class="attribute">attributes</span></a> <span class="delete">must</span><em class="rfc2119" title="MUST"><span class="insert">MUST</span></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/PR-prov-dm-20130312/#end.id"><span class="attribute">id</span></a>, <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#end.trigger"><span class="attribute">trigger</span></a>, <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#end.ender"><span class="attribute">ender</span></a>, <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#end.time"><span class="attribute">time</span></a>, and <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#end.attributes"><span class="attribute">attributes</span></a> <span class="delete">must</span><em class="rfc2119" title="MUST"><span class="insert">MUST</span></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/PR-prov-dm-20130312/#invalidation.id"><span class="attribute">id</span></a>, <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#invalidation.activity"><span class="attribute">activity</span></a>, <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#invalidation.time"><span class="attribute">time</span></a>, and <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#invalidation.attributes"><span class="attribute">attributes</span></a> <span class="delete">must</span><em class="rfc2119" title="MUST"><span class="insert">MUST</span></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/PR-prov-dm-20130312/#association.id"><span class="attribute">id</span></a>, <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#association.agent"><span class="attribute">agent</span></a>, <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#association.plan"><span class="attribute">plan</span></a>, and <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/#association.attributes"><span class="attribute">attributes</span></a> <span class="delete">must</span><em class="rfc2119" title="MUST"><span class="insert">MUST</span></em> be present</td>
-</tr>
-
-</tbody></table>
-</div>
-</section>
-
-</section>
-
-
-</section>
-
-
-
-
-
-<section id="document">
-<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="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:
-</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
-<code><a class="grammarRef" href="#prod-bundle">bundle</a></code>.</li>
-</ul>
-
-
-<p>Thus, bundles <span class="delete">may</span><em class="rfc2119" title="MAY"><span class="insert">MAY</span></em> occur inside a document, but do not appear inside other bundles.
-</p>
-
-
-
-<div class="anexample" id="example_45"><div class="anexampleTitle"><a class="internalDFN" href="#example_45">Example 45</a></div>
-<p>
+</span>
+
+
+
+
+
+
+
+
+
+
+
+
+<span class="delete">3.7.5 </span><span class="delete">Summary of additional semantic rules</span>
+
+<span class="delete">Some of the grammar productions allow for expressions that are syntactically correct, and yet according to [</span><span class="delete">PROV-DM</span><span class="delete">] 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.</span>
+
+
+
+<span class="delete">Table 2: Summary of additional semantic rules for grammar productions</span>
+<span class="delete">Production</span>
+ <span class="delete">Examples of syntactically correct expressions</span>
+ <span class="delete">Additional semantic rule</span>
+
+
+<span class="delete">Generation expression</span>
+ <span class="delete">wasGeneratedBy(e2, -, -)</span><span class="delete">wasGeneratedBy(-; e2, -, -)</span>
+ <span class="delete">At least one of </span><span class="delete">id</span><span class="delete">, </span><span class="delete">activity</span><span class="delete">, </span><span class="delete">time</span><span class="delete">, and </span><span class="delete">attributes</span> <span class="delete">MUST</span><span class="delete"> be present.</span>
+
+<span class="delete">Usage expression</span>
+<span class="delete">used(a2, -, -)</span><span class="delete">used(-; a2, -, -)</span>
+<span class="delete">At least one of </span><span class="delete">id</span><span class="delete">, </span><span class="delete">entity</span><span class="delete">, </span><span class="delete">time</span><span class="delete">, and </span><span class="delete">attributes</span> <span class="delete">MUST</span><span class="delete"> be present</span>
+
+
+<span class="delete">Start expression</span>
+ <span class="delete">wasStartedBy(e2, -, -, -)</span><span class="delete">wasStartedBy(-; e2, -, -, -)</span>
+<span class="delete">At least one of </span><span class="delete">id</span><span class="delete">, </span><span class="delete">trigger</span><span class="delete">, </span><span class="delete">starter</span><span class="delete">, </span><span class="delete">time</span><span class="delete">, and </span><span class="delete">attributes</span> <span class="delete">MUST</span><span class="delete"> be present</span>
+
+
+
+<span class="delete">End expression</span>
+<span class="delete">wasEndedBy(e2, -, -, -)</span><span class="delete">wasEndedBy(-; e2, -, -, -)</span>
+<span class="delete">At least one of </span><span class="delete">id</span><span class="delete">, </span><span class="delete">trigger</span><span class="delete">, </span><span class="delete">ender</span><span class="delete">, </span><span class="delete">time</span><span class="delete">, and </span><span class="delete">attributes</span> <span class="delete">MUST</span><span class="delete"> be present</span>
+
+
+
+<span class="delete">Invalidation expression</span>
+<span class="delete">wasInvalidatedBy(e2, -, -)</span> <span class="delete">wasInvalidatedBy(-; e2, -, -)</span>
+<span class="delete">At least one of </span><span class="delete">id</span><span class="delete">, </span><span class="delete">activity</span><span class="delete">, </span><span class="delete">time</span><span class="delete">, and </span><span class="delete">attributes</span> <span class="delete">MUST</span><span class="delete"> be present</span>
+
+
+
+<span class="delete">Association expression</span>
+<span class="delete">wasAssociatedWith(a, -, -)</span> <span class="delete">wasAssociatedWith(-; a, -, -)</span>
+<span class="delete">At least one of </span><span class="delete">id</span><span class="delete">, </span><span class="delete">agent</span><span class="delete">, </span><span class="delete">plan</span><span class="delete">, and </span><span class="delete">attributes</span> <span class="delete">MUST</span><span class="delete"> be present</span>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<span class="delete">4. </span><span class="delete">Document</span>
+
+<span class="delete">A </span><span class="delete">document</span><span class="delete"> 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 </span><span class="delete">exchanging</span><span class="delete"> them. A document may be used
+ to package up PROV-N expressions in response to a request for the provenance of something ([</span><span class="delete">PROV-AQ</span><span class="delete">]).</span>
+
+<span class="delete"> 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 </span><span class="delete">expression</span><span class="delete">).</span>
+
+
+
+
+
+<span class="delete">A document's text matches the </span><span class="delete">document</span><span class="delete"> production.</span>
+
+
+ <span class="delete">[</span><span class="delete">1</span><span class="delete">] </span> <span class="delete">document</span> <span class="delete"> ::= </span> <span class="delete">"document" (</span><span class="delete">namespaceDeclarations</span><span class="delete">)? (</span><span class="delete">expression</span><span class="delete">)* (</span><span class="delete">bundle</span><span class="delete">)* "endDocument"</span>
+
+
+<span class="delete">A document contains:
+</span>
+<span class="delete">namespaceDeclarations</span><span class="delete">: a set of namespace declarations </span><span class="delete">namespaceDeclarations</span><span class="delete">, declaring namespaces and associated prefixes, which can be used in attributes and identifiers occurring inside </span><span class="delete">expressions</span><span class="delete"> or </span><span class="delete">bundles</span><span class="delete">;</span>
+<span class="delete">expressions</span><span class="delete">: a set of expressions, each matching </span><span class="delete">expression</span><span class="delete">;</span>
+<span class="delete">bundles</span><span class="delete">: a set of expressions, each matching
+</span><span class="delete">bundle</span><span class="delete">.</span>
+
+
+
+<span class="delete">Thus, bundles </span><span class="delete">MAY</span><span class="delete"> occur inside a document, but do not appear inside other bundles.
+</span>
+
+
+
+<span class="delete">Example 45</span>
+<span class="delete">
The following document contains expressions related to the provenance of entity
-<span class="name">e2</span>.
-</p>
-<pre class="codeexample">document
+</span><span class="delete">e2</span><span class="delete">.
+</span>
+<span class="delete">document
default <http://anotherexample.org/>
prefix ex <http://example.org/>
@@ -2890,108 +2814,108 @@
agent(ag2, [ prov:type='prov:Person', ex:name="Bob" ])
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> [<cite><a class="bibref" href="#bib-PROV-AQ">PROV-AQ</a></cite>].
-</p>
-</div>
-
-
-
-</section>
-
-<section id="extensibility">
-<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 <span class="delete">must</span><em class="rfc2119" title="MUST"><span class="insert">MUST</span></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
- <span class="delete">may</span><em class="rfc2119" title="MAY"><span class="insert">MAY</span></em> ignore these expressions.</li>
-<li> Extensions to PROV and PROV-N <span class="delete">may</span><em class="rfc2119" title="MAY"><span class="insert">MAY</span></em> specify more specific productions and interpretations for these expressions, which applications <span class="delete">may</span><em class="rfc2119" title="MAY"><span class="insert">MAY</span></em> elect to follow. </li>
-</ul>
-
-
-<table class="grammar">
-
-<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 <span class="delete">must</span><em class="rfc2119" title="MUST"><span class="insert">MUST</span></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" 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#>
+</span>
+<span class="delete">This container could for instance be returned as the result of a query to a provenance store for the provenance of entity </span><span class="delete">e2</span><span class="delete"> [</span><span class="delete">PROV-AQ</span><span class="delete">].
+</span>
+
+
+
+
+
+
+
+<span class="delete">5. </span><span class="delete">Extensibility</span>
+
+<span class="delete">The PROV data model is extensible by means of attributes </span><span class="delete">prov:type</span><span class="delete"> and </span><span class="delete">prov:role</span><span class="delete"> allowing subtyping of expressions. For some applications, novel syntax may also be convenient. Hence, the normative requirements are as follow.</span>
+
+<span class="delete"> PROV-N compliant parsers </span><span class="delete">MUST</span><span class="delete"> be able to parse expressions matching the </span><span class="delete">extensibilityExpression</span><span class="delete"> production defined below.
+</span><span class="delete"> As PROV provides no definition for these expressions, PROV compliant implementations
+ </span><span class="delete">MAY</span><span class="delete"> ignore these expressions.</span>
+<span class="delete"> Extensions to PROV and PROV-N </span><span class="delete">MAY</span><span class="delete"> specify more specific productions and interpretations for these expressions, which applications </span><span class="delete">MAY</span><span class="delete"> elect to follow. </span>
+
+
+
+
+
+ <span class="delete">[</span><span class="delete">49</span><span class="delete">] </span> <span class="delete">extensibilityExpression</span> <span class="delete"> ::= </span> <span class="delete">QUALIFIED_NAME</span><span class="delete"> "(" </span><span class="delete">optionalIdentifier</span> <span class="delete">extensibilityArgument</span><span class="delete"> ( "," </span><span class="delete">extensibilityArgument</span><span class="delete"> )* </span><span class="delete">optionalAttributeValuePairs</span><span class="delete"> ")"</span>
+ <span class="delete">[</span><span class="delete">50</span><span class="delete">] </span> <span class="delete">extensibilityArgument</span> <span class="delete"> ::= </span> <span class="delete">( </span><span class="delete">identifierOrMarker</span><span class="delete"> | </span><span class="delete">literal</span><span class="delete"> | </span><span class="delete">time</span><span class="delete"> | </span><span class="delete">extensibilityExpression</span><span class="delete"> | </span><span class="delete">extensibilityTuple</span><span class="delete"> )</span>
+ <span class="delete">[</span><span class="delete">51</span><span class="delete">] </span> <span class="delete">extensibilityTuple</span> <span class="delete"> ::= </span> <span class="delete">"{" </span><span class="delete">extensibilityArgument</span><span class="delete"> ( "," </span><span class="delete">extensibilityArgument</span><span class="delete"> )* "}"</span><span class="delete"> | "(" </span><span class="delete">extensibilityArgument</span><span class="delete"> ( "," </span><span class="delete">extensibilityArgument</span><span class="delete"> )* ")"</span>
+
+
+
+<span class="delete">Expressions compatible with the
+</span><span class="delete">extensibilityExpression</span><span class="delete"> production follow a general form of functional syntax, in which the predicate </span><span class="delete">MUST</span><span class="delete"> be a
+</span><span class="delete">qualifiedName</span><span class="delete">
+with a non-empty </span><span class="delete">prefix</span><span class="delete">.</span>
+
+
+
+<span class="delete">Example 46</span>
+
+<span class="delete">Collections</span><span class="delete"> are sets of entities, whose membership can be expressed using the </span><span class="delete">hadMember</span><span class="delete"> relation. The following example shows how one can express membership for </span><span class="delete">dictionaries</span><span class="delete">, an illustrative extension of Collections consisting of sets of key-entity pairs, where a key is a </span><span class="delete">literal</span><span class="delete">. 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><span class="delete">http://example.org/dictionaries</span><span class="delete">.
+</span>
+<span class="delete"> 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#>
+</span><span class="delete">
+
+Note that the generic </span><span class="delete">extensibilityExpression</span><span class="delete"> 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:
+</span><span class="delete"> prefix dictExt <http://example.org/dictionaries#>
dictExt:hadMembers(mid; d, dictExt:set(dictExt:pair("k1",e1),
dictExt:pair("k2",e2),
dictExt:pair("k3",e3)),
[dictExt:uniqueKeys="true"])
-</pre>
+</span>
-</div>
-
-
-
-
-</section>
-
-
-<section id="media-type">
-<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.
-</p>
-
-
- <dl>
- <dt>Contact:</dt>
- <dd>Ivan Herman</dd>
- <dt>See also:</dt>
- <dd><a href="http://www.w3.org/2002/06/registering-mediatype">How to Register a Media Type for a <abbr title="World Wide Web Consortium">W3C</abbr> Specification</a></dd>
- <dd><a href="http://www.w3.org/2001/tag/2002/0129-mime">Internet Media Type registration, consistency of use</a><br>TAG Finding 3 June 2002 (Revised 4 September 2002)</dd>
- </dl>
- <p>The Internet Media Type / MIME Type for PROV-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="https://lists.w3.org/Archives/Member/w3c-archive/2012Nov/0317.html">submitted to the IESG</a> for review, approval, and registration with IANA.</p>
- <dl>
- <dt>Type name:</dt>
- <dd>text</dd>
- <dt>Subtype name:</dt>
- <dd>provenance-notation</dd>
- <dt>Required parameters:</dt>
- <dd><kbd>charset</kbd> — the value of <kbd>charset</kbd> <span class="delete">must</span><em class="rfc2119" title="MUST"><span class="insert">MUST</span></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 [<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 [<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 ([<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> [<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
+
+
+
+
+
+
+
+
+
+<span class="delete">6. </span><span class="delete">Media Type</span>
+
+<span class="delete">
+The media type of PROV-N is </span><span class="delete">text/provenance-notation</span><span class="delete">. The content encoding of PROV-N content is UTF-8.
+</span>
+
+
+
+ <span class="delete">Contact:</span>
+ <span class="delete">Ivan Herman</span>
+ <span class="delete">See also:</span>
+ <span class="delete">How to Register a Media Type for a </span><span class="delete">W3C</span><span class="delete"> Specification</span>
+ <span class="delete">Internet Media Type registration, consistency of use</span><span class="delete">TAG Finding 3 June 2002 (Revised 4 September 2002)</span>
+
+ <span class="delete">The Internet Media Type / MIME Type for PROV-N is "text/provenance-notation".</span>
+ <span class="delete">It is recommended that PROV-N files have the extension ".provn" (all lowercase) on all platforms.</span>
+ <span class="delete">It is recommended that PROV-N files stored on Macintosh HFS file systems be given a file type of "TEXT".</span>
+ <span class="delete">The information that follows has been </span><span class="delete">submitted to the IESG</span><span class="delete"> for review, approval, and registration with IANA.</span>
+
+ <span class="delete">Type name:</span>
+ <span class="delete">text</span>
+ <span class="delete">Subtype name:</span>
+ <span class="delete">provenance-notation</span>
+ <span class="delete">Required parameters:</span>
+ <span class="delete">charset</span><span class="delete"> — the value of </span><span class="delete">charset</span> <span class="delete">MUST</span><span class="delete"> always be </span><span class="delete">UTF-8</span><span class="delete">.</span>
+ <span class="delete">Optional parameters:</span>
+ <span class="delete">None</span>
+
+ <span class="delete">Encoding considerations: 8bit</span>
+ <span class="delete">The syntax of PROV-N is expressed over code points in Unicode [</span><span class="delete">UNICODE</span><span class="delete">]. The encoding is always UTF-8 [</span><span class="delete">UTF-8</span><span class="delete">].</span>
+ <span class="delete">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]</span>
+ <span class="delete">Security considerations:</span>
+ <span class="delete">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 [</span><span class="delete">RFC3023</span><span class="delete">] 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.</span>
+ <span class="delete">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. </span>
+ <span class="delete">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 ([</span><span class="delete">RFC3023</span><span class="delete">] section 10) provide additional guidance around the expression of arbitrary data and markup.</span>
+ <span class="delete">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. </span>
+ <span class="delete">PROV-N uses qualified names mappable to IRIs as term identifiers. Applications interpreting data expressed in PROV-N should address the security issues of
+ </span><span class="delete">Internationalized Resource Identifiers (IRIs)</span><span class="delete"> [</span><span class="delete">RFC3987</span><span class="delete">] Section 8, as well as
+ </span><span class="delete">Uniform Resource Identifier (URI): Generic Syntax</span><span class="delete"> [</span><span class="delete">RFC3986</span><span class="delete">] Section 7.</span>
+ <span class="delete">Multiple IRIs may have the same appearance. Characters in different scripts may
look similar (a Cyrillic "о" may appear similar to a Latin "o"). A character followed
by combining characters may have the same visual representation as another character
(LATIN SMALL LETTER E followed by COMBINING ACUTE ACCENT has the same visual representation
@@ -2999,90 +2923,88 @@
Any person or application that is writing or interpreting data in PROV-N must take care to use the IRI that matches the intended semantics, and avoid IRIs that make look similar.
Further information about matching of similar characters can be found
-in <a class="inform" href="http://www.unicode.org/reports/tr36/">Unicode Security
-Considerations</a> [<cite><a class="bibref" href="#bib-UNISEC">UNISEC</a></cite>] and
-<a class="norm" href="http://www.ietf.org/rfc/rfc3987.txt">Internationalized Resource
-Identifiers (IRIs)</a> [<cite><a class="bibref" href="#bib-RFC3987">RFC3987</a></cite>] Section 8.
-</dd>
-
-
- <dd><span class="insert">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.</span></dd>
-
- <dt>Interoperability considerations:</dt>
- <dd>There are no known interoperability issues.</dd>
- <dt>Published specification:</dt>
- <dd>PROV-N: The Provenance Notation, Moreau, Missier, (eds), Cheney, Soiland-Reyes
- <a href="http://www.w3.org/TR/prov-n/">http://www.w3.org/TR/prov-n/</a>, 2012.</dd>
- <dt>Applications which use this media type:</dt>
- <dd>It may be used by any application for publishing provenance information. This format is designed to be a human-readable form of provenance. </dd>
- <dt>Additional information:</dt>
- <dt>Magic number(s):</dt>
- <dd>PROV-N documents may have the strings 'document' near the beginning of the document.</dd>
- <dt>File extension(s):</dt>
- <dd>".provn"</dd>
- <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>
- <dt>Person & email address to contact for further information:</dt>
- <dd>Ivan Herman, ivan@w3.org</dd>
- <dt>Intended usage:</dt>
- <dd>COMMON</dd>
- <dt>Restrictions on usage:</dt>
- <dd>None</dd>
- <dt>Author/Change controller:</dt>
- <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>
+in </span><span class="delete">Unicode Security
+Considerations</span><span class="delete"> [</span><span class="delete">UNISEC</span><span class="delete">] and
+</span><span class="delete">Internationalized Resource
+Identifiers (IRIs)</span><span class="delete"> [</span><span class="delete">RFC3987</span><span class="delete">] Section 8.
+</span>
+ <span class="delete">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.</span>
-</section>
-
-
-
-
-
-
-
-<section class="appendix informative" id="change-log">
- <h2><span class="secno">A. </span><span class="insert">Change Log</span></h2><p><em><span class="insert">This section is non-normative.</span></em></p>
-
-<section class="appendix informative" id="changes-since-candidate-recommendation">
- <h3><span class="secno"><span class="insert">A.1 </span></span>Changes since <span class="insert">Candidate Recommendation</span></h3><p><em><span class="insert">This section is non-normative.</span></em></p>
-
-<ul>
-<li><span class="insert"> Checked that all fragments resolved.
-</span></li><li><span class="insert"> 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.
-</span></li><li><span class="insert"> Changed all URLs to PROV documents.
-</span></li><li><span class="insert"> Clarified a sentence about the (non) nesting of bundles.
-</span></li><li><span class="insert"> Added html link to provenance.
-</span></li><li><span class="insert"> Updated security consideration for extensibility feature of PROV-N following IANA feedback.
-</span></li></ul>
-</section>
-
-
-<section class="appendix informative" id="changes-since-last-call">
- <h3><span class="secno"><span class="insert">A.2 </span></span><span class="insert">Changes since </span>last <span class="delete">version</span><span class="insert">call</span></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><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" id="acknowledgements">
- <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 (<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>
+ <span class="delete">Interoperability considerations:</span>
+ <span class="delete">There are no known interoperability issues.</span>
+ <span class="delete">Published specification:</span>
+ <span class="delete">PROV-N: The Provenance Notation, Moreau, Missier, (eds), Cheney, Soiland-Reyes
+ </span><span class="delete">http://www.w3.org/TR/prov-n/</span><span class="delete">, 2012.</span>
+ <span class="delete">Applications which use this media type:</span>
+ <span class="delete">It may be used by any application for publishing provenance information. This format is designed to be a human-readable form of provenance. </span>
+ <span class="delete">Additional information:</span>
+ <span class="delete">Magic number(s):</span>
+ <span class="delete">PROV-N documents may have the strings 'document' near the beginning of the document.</span>
+ <span class="delete">File extension(s):</span>
+ <span class="delete">".provn"</span>
+ <span class="delete">Base URI:</span>
+ <span class="delete">There are no constructs in the PROV-N Syntax to change the Base IRI.</span>
+ <span class="delete">Macintosh file type code(s):</span>
+ <span class="delete">"TEXT"</span>
+ <span class="delete">Person & email address to contact for further information:</span>
+ <span class="delete">Ivan Herman, ivan@w3.org</span>
+ <span class="delete">Intended usage:</span>
+ <span class="delete">COMMON</span>
+ <span class="delete">Restrictions on usage:</span>
+ <span class="delete">None</span>
+ <span class="delete">Author/Change controller:</span>
+ <span class="delete">The PROV-N specification is the product of the World Wide Web Consortium's Provenance Working Group. The </span><span class="delete">W3C</span><span class="delete"> has change control over this specification.</span>
+
+
+
+
+
+
+
+
+
+
+
+ <span class="delete">A. </span><span class="delete">Change Log</span><span class="delete">This section is non-normative.</span>
+
+
+ <span class="delete">A.1 </span><span class="delete">Changes since Candidate Recommendation</span><span class="delete">This section is non-normative.</span>
+
+
+<span class="delete"> Checked that all fragments resolved.
+</span><span class="delete"> 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.
+</span><span class="delete"> Changed all URLs to PROV documents.
+</span><span class="delete"> Clarified a sentence about the (non) nesting of bundles.
+</span><span class="delete"> Added html link to provenance.
+</span><span class="delete"> Updated security consideration for extensibility feature of PROV-N following IANA feedback.
+</span>
+
+
+
+
+ <span class="delete">A.2 </span><span class="delete">Changes since last call</span><span class="delete">This section is non-normative.</span>
+<span class="delete"> Please see the </span><span class="delete">Responses to Public Comments on the Last Call Working Draft</span><span class="delete"> for more details about the justification of these changes.</span>
+
+ <span class="delete">ISSUE-543</span><span class="delete">: Uses key-entity pair terminology for example 43.
+</span> <span class="delete">ISSUE-538</span><span class="delete">: Rephrasing of text in example 10.
+</span> <span class="delete">ISSUE-547</span><span class="delete">: Aligned terminology and productions with prov-constraints document, renaming 'toplevel bundle' to 'document', and renaming 'named bundle' to 'bundle'.
+</span> <span class="delete">ISSUE-496</span><span class="delete">: 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.
+</span> <span class="delete">ISSUE-573</span><span class="delete">: Updated Media Type section.
+</span> <span class="delete">ISSUE-589</span><span class="delete">: Updated scoping rule for prefix-namespace declaration. Also refrained from saying bundles are self-contained.
+</span><span class="delete"> Moved feature at Risk mention into a separate note.
+</span><span class="delete"> Editorial's pass pre-publication.
+</span>
+
+
+
+
+ <span class="delete">B. </span><span class="delete">Acknowledgements</span><span class="delete">This section is non-normative.</span>
+ <span class="delete">
+
+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 (</span><span class="delete">W3C</span><span class="delete">/</span><span class="delete">MIT</span><span class="delete">) and Ivan Herman (</span><span class="delete">W3C</span><span class="delete">/</span><span class="delete">ERCIM</span><span class="delete">), </span><span class="delete">W3C</span><span class="delete"> contacts for the Provenance Working Group.
+ </span>
+
+<span class="delete">
The editors acknowledge valuable contributions from the following:
Tom Baker,
David Booth,
@@ -3096,19 +3018,19 @@
Alan Ruttenberg,
Reza Samavi, and
Antoine Zimmermann.
-</p>
-
-<p>
+</span>
+
+<span class="delete">
Members of the Provenance Working Group at the time of publication of this document were:
Ilkay Altintas (Invited expert),
Reza B'Far (Oracle Corporation),
Khalid Belhajjame (University of Manchester),
James Cheney (University of Edinburgh, School of Informatics),
-<span class="delete">Sam Coppens (IBBT),</span><span class="insert">Tom De Nies (iMinds - Ghent University),</span>
+Tom De Nies (iMinds - Ghent University),
David Corsar (University of Aberdeen, Computing Science),
Stephen Cresswell (The National Archives),
-Tom De Nies <span class="delete">(IBBT),</span><span class="insert">(iMinds - Ghent University),</span>
+Tom De Nies (iMinds - Ghent University),
Helena Deus (DERI Galway at the National University of Ireland, Galway, Ireland),
Simon Dobson (Invited expert),
Martin Doerr (Foundation for Research and Technology - Hellas(FORTH)),
@@ -3122,9 +3044,9 @@
Paul Groth (Vrije Universiteit),
Olaf Hartig (Invited expert),
David Hau (National Cancer Institute, NCI),
-Sandro Hawke (<abbr title="World Wide Web Consortium">W3C</abbr>/<abbr title="Massachusetts Institute of Technology">MIT</abbr>),
+Sandro Hawke (</span><span class="delete">W3C</span><span class="delete">/</span><span class="delete">MIT</span><span class="delete">),
Jörn Hees (German Research Center for Artificial Intelligence (DFKI) Gmbh),
-Ivan Herman, (<abbr title="World Wide Web Consortium">W3C</abbr>/<abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr>),
+Ivan Herman, (</span><span class="delete">W3C</span><span class="delete">/</span><span class="delete">ERCIM</span><span class="delete">),
Ralph Hodgson (TopQuadrant),
Hook Hua (Invited expert),
Trung Dong Huynh (University of Southampton),
@@ -3158,41 +3080,33 @@
Stephan Zednik (Rensselaer Polytechnic Institute),
Jun Zhao (University of Oxford),
Yuting Zhao (University of Aberdeen, Computing Science).
-</p>
-
- </section>
+</span>
+
+
-<section id="references" class="appendix"><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/PR-prov-constraints-20130312/"><cite>Constraints of the PROV Data Model</cite></a>. <span class="delete">11 December 2012,</span><span class="insert">12 March 2013,</span> W3C <span class="delete">Candidate</span><span class="insert">Proposed</span> Recommendation. URL: <span class="delete">http://www.w3.org/TR/2012/CR-prov-constraints-20121211/</span><a href="http://www.w3.org/TR/2013/PR-prov-constraints-20130312/"><span class="insert">http://www.w3.org/TR/2013/PR-prov-constraints-20130312/</span></a>
-</dd><dt id="bib-PROV-DM">[PROV-DM]</dt><dd>Luc Moreau; Paolo Missier; eds. <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/"><cite>PROV-DM: The PROV Data Model</cite></a>. <span class="delete">11 December 2012,</span><span class="insert">12 March 2013,</span> W3C <span class="delete">Candidate</span><span class="insert">Proposed</span> Recommendation. URL: <span class="delete">http://www.w3.org/TR/2012/CR-prov-dm-20121211/</span><a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/"><span class="insert">http://www.w3.org/TR/2013/PR-prov-dm-20130312/</span></a>
-</dd><dt id="bib-PROV-O">[PROV-O]</dt><dd>Timothy Lebo; Satya Sahoo; Deborah McGuinness; eds. <a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/"><cite>PROV-O: The PROV Ontology</cite></a>. <span class="delete">11 December 2012,</span><span class="insert">12 March 2013,</span> W3C <span class="delete">Candidate</span><span class="insert">Proposed</span> Recommendation. URL: <span class="delete">http://www.w3.org/TR/2012/CR-prov-o-20121211/</span><a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/"><span class="insert">http://www.w3.org/TR/2013/PR-prov-o-20130312/</span></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 <span class="delete">RDF.</span><span class="insert">RDF</span></cite></a><span class="insert">.</span> 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</cite></a><span class="insert">.</span> January 2001.<span class="delete"> Internet</span> RFC 3023. URL: <a href="http://www.ietf.org/rfc/rfc3023.txt">http://www.ietf.org/rfc/rfc3023.txt</a>
-
-</dd><dt id="bib-RFC3986">[RFC3986]</dt><dd>T. Berners-Lee; R. Fielding; L. Masinter. <a href="http://www.ietf.org/rfc/rfc3986.txt"><cite>Uniform Resource Identifier (URI): Generic <span class="delete">Syntax.</span><span class="insert">Syntax</span></cite></a><span class="insert">.</span> January 2005.<span class="delete"> Internet</span> RFC 3986. URL: <a href="http://www.ietf.org/rfc/rfc3986.txt">http://www.ietf.org/rfc/rfc3986.txt</a>
-
-</dd><dt id="bib-RFC3987">[RFC3987]</dt><dd>M. Dürst; M. Suignard. <a href="http://www.ietf.org/rfc/rfc3987.txt"><cite>Internationalized Resource Identifiers <span class="delete">(IRIs).</span><span class="insert">(IRIs)</span></cite></a><span class="insert">.</span> January 2005.<span class="delete"> Internet</span> RFC 3987. 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 <span class="delete">Tobin;</span><span class="insert">Tobin</span> et al. <a href="http://www.w3.org/TR/2009/REC-xml-names-20091208/"><cite>Namespaces in XML 1.0 (Third <span class="delete">Edition).</span><span class="insert">Edition)</span></cite></a><span class="insert">.</span> 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 <span class="delete">Maler;</span><span class="insert">Maler</span> et al. <a href="http://www.w3.org/TR/2006/REC-xml11-20060816"><cite>Extensible Markup Language (XML) 1.1 (Second <span class="delete">Edition).</span><span class="insert">Edition)</span></cite></a><span class="insert">.</span> 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. <span class="delete">Thompson;</span><span class="insert">Thompson</span> 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: <span class="delete">Datatypes.</span><span class="insert">Datatypes</span></cite></a><span class="insert">.</span> 5 April 2012. W3C <span class="delete">Recommendation</span><span class="insert">Recommendation.</span> 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/WD-prov-aq-20130312/"><cite>Provenance Access and Query</cite></a>. <span class="delete">19 June 2012,</span><span class="insert">12 March 2013,</span> Working Draft. URL: <span class="delete">http://www.w3.org/TR/2012/WD-prov-aq-20120619/</span><a href="http://www.w3.org/TR/2013/WD-prov-aq-20130312/"><span class="insert">http://www.w3.org/TR/2013/WD-prov-aq-20130312/</span></a>
-</dd><dt id="bib-PROV-DC"><span class="insert">[PROV-DC]</span></dt><dd><span class="insert">Daniel Garijo; Kai Eckert; eds. </span><a href="http://www.w3.org/TR/2013/WD-prov-dc-20130312/"><cite><span class="insert">Dublin Core to PROV Mapping</span></cite></a><span class="insert">. 12 March 2013, Working Draft. URL: </span><a href="http://www.w3.org/TR/2013/WD-prov-dc-20130312/"><span class="insert">http://www.w3.org/TR/2013/WD-prov-dc-20130312/</span></a>
-</dd><dt id="bib-PROV-DICTIONARY"><span class="insert">[PROV-DICTIONARY]</span></dt><dd><span class="insert">Tom De Nies; Sam Coppens; eds. </span><a href="http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/"><cite><span class="insert">PROV Dictionary</span></cite></a><span class="insert">. 12 March 2013, Working Draft. URL: </span><a href="http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/"><span class="insert">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/</span></a>
-</dd><dt id="bib-PROV-LINKS"><span class="insert">[PROV-LINKS]</span></dt><dd><span class="insert">Luc Moreau; Timothy Lebo; eds. </span><a href="http://www.w3.org/TR/2013/WD-prov-links-20130312/"><cite><span class="insert">Linking Across Provenance Bundles</span></cite></a><span class="insert">. 12 March 2013, Working Draft. URL: </span><a href="http://www.w3.org/TR/2013/WD-prov-links-20130312/"><span class="insert">http://www.w3.org/TR/2013/WD-prov-links-20130312/</span></a>
-</dd><dt id="bib-PROV-OVERVIEW">[PROV-OVERVIEW]</dt><dd>Paul Groth; Luc Moreau; eds. <a href="http://www.w3.org/TR/2013/WD-prov-overview-20130312/"><cite>PROV-OVERVIEW: An Overview of the PROV Family of Documents</cite></a>. <span class="delete">11 December 2012,</span><span class="insert">12 March 2013,</span> Working Draft. URL: <span class="delete">http://www.w3.org/TR/2012/WD-prov-overview-20121211/</span><a href="http://www.w3.org/TR/2013/WD-prov-overview-20130312/"><span class="insert">http://www.w3.org/TR/2013/WD-prov-overview-20130312/</span></a>
-</dd><dt id="bib-PROV-PRIMER">[PROV-PRIMER]</dt><dd>Yolanda Gil; Simon Miles; eds. <a href="http://www.w3.org/TR/2013/WD-prov-primer-20130312/"><cite>PROV Model Primer</cite></a>. <span class="delete">11 December 2012,</span><span class="insert">12 March 2013,</span> Working Draft. URL: <span class="delete">http://www.w3.org/TR/2012/WD-prov-primer-20121211/</span><a href="http://www.w3.org/TR/2013/WD-prov-primer-20130312/"><span class="insert">http://www.w3.org/TR/2013/WD-prov-primer-20130312/</span></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/WD-prov-sem-20130312"><cite><span class="delete">Formal </span>Semantics of <span class="insert">the </span>PROV<span class="insert"> Data Model</span></cite></a>. <span class="delete">2011, Work in progress.</span><span class="insert">12 March 2013, Working Draft.</span> URL: <span class="delete">http://www.w3.org/2011/prov/wiki/FormalSemanticsED</span><a href="http://www.w3.org/TR/2013/WD-prov-sem-20130312"><span class="insert">http://www.w3.org/TR/2013/WD-prov-sem-20130312</span></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/WD-prov-xml-20130312/"><cite>PROV-XML: The PROV XML Schema</cite></a>. <span class="delete">11 December 2012,</span><span class="insert">12 March 2013,</span> Working Draft. URL: <span class="delete">http://www.w3.org/TR/2012/WD-prov-xml-20121211/</span><a href="http://www.w3.org/TR/2013/WD-prov-xml-20130312/"><span class="insert">http://www.w3.org/TR/2013/WD-prov-xml-20130312/</span></a>
-</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>
-
+<span class="delete">C. </span><span class="delete">References</span><span class="delete">C.1 </span><span class="delete">Normative references</span><span class="delete">[PROV-CONSTRAINTS]</span><span class="delete">James Cheney; Paolo Missier; Luc Moreau; eds. </span><span class="delete">Constraints of the PROV Data Model</span><span class="delete">. 12 March 2013, W3C Proposed Recommendation. URL: </span><span class="delete">http://www.w3.org/TR/2013/PR-prov-constraints-20130312/</span>
+<span class="delete">[PROV-DM]</span><span class="delete">Luc Moreau; Paolo Missier; eds. </span><span class="delete">PROV-DM: The PROV Data Model</span><span class="delete">. 12 March 2013, W3C Proposed Recommendation. URL: </span><span class="delete">http://www.w3.org/TR/2013/PR-prov-dm-20130312/</span>
+<span class="delete">[PROV-O]</span><span class="delete">Timothy Lebo; Satya Sahoo; Deborah McGuinness; eds. </span><span class="delete">PROV-O: The PROV Ontology</span><span class="delete">. 12 March 2013, W3C Proposed Recommendation. URL: </span><span class="delete">http://www.w3.org/TR/2013/PR-prov-o-20130312/</span>
+<span class="delete">[RDF-SPARQL-QUERY]</span><span class="delete">Andy Seaborne; Eric Prud'hommeaux. </span><span class="delete">SPARQL Query Language for RDF</span><span class="delete">. 15 January 2008. W3C Recommendation. URL: </span><span class="delete">http://www.w3.org/TR/2008/REC-rdf-sparql-query-20080115</span>
+<span class="delete">[RFC2119]</span><span class="delete">S. Bradner. </span><span class="delete">Key words for use in RFCs to Indicate Requirement Levels.</span><span class="delete"> March 1997. Internet RFC 2119. URL: </span><span class="delete">http://www.ietf.org/rfc/rfc2119.txt</span>
+<span class="delete">[RFC3023]</span><span class="delete">M. Murata; S. St.Laurent; D. Kohn. </span><span class="delete">XML Media Types</span><span class="delete">. January 2001. RFC 3023. URL: </span><span class="delete">http://www.ietf.org/rfc/rfc3023.txt</span>
+<span class="delete">[RFC3986]</span><span class="delete">T. Berners-Lee; R. Fielding; L. Masinter. </span><span class="delete">Uniform Resource Identifier (URI): Generic Syntax</span><span class="delete">. January 2005. RFC 3986. URL: </span><span class="delete">http://www.ietf.org/rfc/rfc3986.txt</span>
+<span class="delete">[RFC3987]</span><span class="delete">M. Dürst; M. Suignard. </span><span class="delete">Internationalized Resource Identifiers (IRIs)</span><span class="delete">. January 2005. RFC 3987. URL: </span><span class="delete">http://www.ietf.org/rfc/rfc3987.txt</span>
+<span class="delete">[UNICODE]</span><span class="delete">The Unicode Consortium. </span><span class="delete">The Unicode Standard.</span><span class="delete"> 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: </span><span class="delete">http://www.unicode.org/unicode/standard/versions/enumeratedversions.html</span>
+<span class="delete">[UTF-8]</span><span class="delete">F. Yergeau. </span><span class="delete">UTF-8, a transformation format of ISO 10646</span><span class="delete">. IETF RFC 3629. November 2003. URL: </span><span class="delete">http://www.ietf.org/rfc/rfc3629.txt</span>
+<span class="delete">[XML-NAMES]</span><span class="delete">Richard Tobin et al. </span><span class="delete">Namespaces in XML 1.0 (Third Edition)</span><span class="delete">. 8 December 2009. W3C Recommendation. URL: </span><span class="delete">http://www.w3.org/TR/2009/REC-xml-names-20091208/</span>
+<span class="delete">[XML11]</span><span class="delete">Eve Maler et al. </span><span class="delete">Extensible Markup Language (XML) 1.1 (Second Edition)</span><span class="delete">. 16 August 2006. W3C Recommendation. URL: </span><span class="delete">http://www.w3.org/TR/2006/REC-xml11-20060816</span>
+<span class="delete">[XMLSCHEMA11-2]</span><span class="delete">Henry S. Thompson et al. </span><span class="delete">W3C XML Schema Definition Language (XSD) 1.1 Part 2: Datatypes</span><span class="delete">. 5 April 2012. W3C Recommendation. URL: </span><span class="delete">http://www.w3.org/TR/2012/REC-xmlschema11-2-20120405/</span>
+<span class="delete">C.2 </span><span class="delete">Informative references</span><span class="delete">[PROV-AQ]</span><span class="delete">Graham Klyne; Paul Groth; eds. </span><span class="delete">Provenance Access and Query</span><span class="delete">. 12 March 2013, Working Draft. URL: </span><span class="delete">http://www.w3.org/TR/2013/WD-prov-aq-20130312/</span>
+<span class="delete">[PROV-DC]</span><span class="delete">Daniel Garijo; Kai Eckert; eds. </span><span class="delete">Dublin Core to PROV Mapping</span><span class="delete">. 12 March 2013, Working Draft. URL: </span><span class="delete">http://www.w3.org/TR/2013/WD-prov-dc-20130312/</span>
+<span class="delete">[PROV-DICTIONARY]</span><span class="delete">Tom De Nies; Sam Coppens; eds. </span><span class="delete">PROV Dictionary</span><span class="delete">. 12 March 2013, Working Draft. URL: </span><span class="delete">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/</span>
+<span class="delete">[PROV-LINKS]</span><span class="delete">Luc Moreau; Timothy Lebo; eds. </span><span class="delete">Linking Across Provenance Bundles</span><span class="delete">. 12 March 2013, Working Draft. URL: </span><span class="delete">http://www.w3.org/TR/2013/WD-prov-links-20130312/</span>
+<span class="delete">[PROV-OVERVIEW]</span><span class="delete">Paul Groth; Luc Moreau; eds. </span><span class="delete">PROV-OVERVIEW: An Overview of the PROV Family of Documents</span><span class="delete">. 12 March 2013, Working Draft. URL: </span><span class="delete">http://www.w3.org/TR/2013/WD-prov-overview-20130312/</span>
+<span class="delete">[PROV-PRIMER]</span><span class="delete">Yolanda Gil; Simon Miles; eds. </span><span class="delete">PROV Model Primer</span><span class="delete">. 12 March 2013, Working Draft. URL: </span><span class="delete">http://www.w3.org/TR/2013/WD-prov-primer-20130312/</span>
+<span class="delete">[PROV-RDF]</span><span class="delete">James Cheney </span><span class="delete">PROV-RDF Mapping </span><span class="delete">2012, Working in Progress. URL: </span><span class="delete">http://www.w3.org/2011/prov/wiki/ProvRDF</span>
+<span class="delete">[PROV-SEM]</span><span class="delete">James Cheney; ed. </span><span class="delete">Semantics of the PROV Data Model</span><span class="delete">. 12 March 2013, Working Draft. URL: </span><span class="delete">http://www.w3.org/TR/2013/WD-prov-sem-20130312</span><span class="delete">.
+</span><span class="delete">[PROV-XML]</span><span class="delete">Hook Hua; Curt Tilmes; Stephan Zednik; eds. </span><span class="delete">PROV-XML: The PROV XML Schema</span><span class="delete">. 12 March 2013, Working Draft. URL: </span><span class="delete">http://www.w3.org/TR/2013/WD-prov-xml-20130312/</span>
+<span class="delete">[UNISEC]</span><span class="delete"> Mark Davis; Michel Suignard. </span><span class="delete">Unicode Security Considerations</span><span class="delete">. 4 August 2010. URL: </span><span class="delete">http://www.unicode.org/reports/tr36/</span>
+
--- a/model/diff.html Mon Mar 25 15:24:00 2013 +0000
+++ b/model/diff.html Mon Mar 25 15:26:37 2013 +0000
@@ -1,4 +1,3 @@
-
<!DOCTYPE html>
<html lang="en" dir="ltr">
<head><style type="text/css"><!--
@@ -11,19 +10,6 @@
--></style>
<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">
@@ -788,20 +774,20 @@
.section dl.attrs dd, .section dl.eldef dd {
margin-bottom: 0;
}
-</style><link rel="stylesheet" href="http://www.w3.org/StyleSheets/TR/W3C-PR"></head>
+</style><link rel="stylesheet" href="https://www.w3.org/StyleSheets/TR/W3C-REC"></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>
+ <a href="http://www.w3.org/"><img width="72" height="48" src="https://www.w3.org/Icons/w3c_home" alt="W3C"></a>
</p>
<h1 class="title" id="title">PROV-DM: The PROV Data Model</h1>
- <h2 id="w3c-proposed-recommendation-12-march-2013"><abbr title="World Wide Web Consortium">W3C</abbr> <span class="delete">Candidate</span><span class="insert">Proposed</span> Recommendation <span class="delete">11 December 2012</span><span class="insert">12 March 2013</span></h2>
+ <h2 id="w3c-recommendation-30-april-2013"><abbr title="World Wide Web Consortium">W3C</abbr> <span class="delete">Proposed </span>Recommendation <span class="delete">12 March</span><span class="insert">30 April</span> 2013</h2>
<dl>
<dt>This version:</dt>
- <dd><span class="delete">http://www.w3.org/TR/2012/CR-prov-dm-20121211/</span><a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/"><span class="insert">http://www.w3.org/TR/2013/PR-prov-dm-20130312/</span></a></dd>
+ <dd><span class="delete">http://www.w3.org/TR/2013/PR-prov-dm-20130312/</span><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/"><span class="insert">http://www.w3.org/TR/2013/REC-prov-dm-20130430/</span></a></dd>
<dt>Latest published version:</dt>
<dd><a href="http://www.w3.org/TR/prov-dm/">http://www.w3.org/TR/prov-dm/</a></dd>
@@ -809,12 +795,12 @@
<dt>Implementation report:</dt>
- <dd><span class="delete">http://dvcs.w3.org/hg/prov/raw-file/default/reports/prov-implementations.html</span><a href="http://www.w3.org/TR/2013/WD-prov-implementations-20130312/"><span class="insert">http://www.w3.org/TR/2013/WD-prov-implementations-20130312/</span></a></dd>
+ <dd><span class="delete">http://www.w3.org/TR/2013/WD-prov-implementations-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-implementations-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-implementations-20130430/</span></a></dd>
<dt>Previous version:</dt>
- <dd><span class="delete">http://www.w3.org/TR/2012/WD-prov-dm-20120724/</span><a href="http://www.w3.org/TR/2012/CR-prov-dm-20121211/"><span class="insert">http://www.w3.org/TR/2012/CR-prov-dm-20121211/</span></a> <a href="diff.html">(color-coded diff)</a></dd>
+ <dd><span class="delete">http://www.w3.org/TR/2012/CR-prov-dm-20121211/</span><a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/"><span class="insert">http://www.w3.org/TR/2013/PR-prov-dm-20130312/</span></a> <a href="diff.html">(color-coded diff)</a></dd>
<dt>Editors:</dt>
@@ -826,7 +812,7 @@
<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>, <span class="delete">IBBT</span><span class="insert">iMinds</span> - Ghent University</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>
@@ -845,14 +831,25 @@
+
+
+
+
+ <p><span class="insert">
+ The English version of this specification is the only normative version. Non-normative
+ </span><a href="http://www.w3.org/Consortium/Translation/"><span class="insert">translations</span></a><span class="insert"> may also be available.
+ </span></p>
+
+
+
<p class="copyright">
<a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> ©
- <span class="delete">2011-2012</span><span class="insert">2011-2013</span>
+ 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><span class="insert">, </span><a href="http://ev.buaa.edu.cn/"><span class="insert">Beihang</span></a>), All Rights Reserved.
+ <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.
@@ -892,7 +889,7 @@
instances of provenance for human consumption; this notation is used in examples in
this document. </p>
-<p>The <a href="http://www.w3.org/TR/2013/WD-prov-overview-20130312/">PROV Document Overview</a> describes the overall state of PROV, and should be read before other PROV documents. </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" class="introductory"><h2>Status of This Document</h2>
@@ -907,96 +904,80 @@
<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 <span class="delete">are:
-</span>
- <span class="delete">PROV-OVERVIEW</span><span class="delete"> (To be published as Note), an overview of the PROV family of documents</span><span class="insert">are listed below. Please consult the</span> [<cite><a class="bibref" href="#bib-PROV-OVERVIEW">PROV-OVERVIEW</a></cite><span class="insert">] for a guide to reading these documents.
-</span><ul>
-<li> <a href="http://www.w3.org/TR/2013/WD-prov-overview-20130312/"><span class="insert">PROV-OVERVIEW</span></a><span class="insert"> (To be published as Note), an overview of the PROV family of documents [</span><cite><a class="bibref" href="#bib-PROV-OVERVIEW"><span class="insert">PROV-OVERVIEW</span></a></cite>];</li>
-<li> <a href="http://www.w3.org/TR/2013/WD-prov-primer-20130312/">PROV-PRIMER</a> (To be published as Note), a primer for the PROV data model [<cite><a class="bibref" href="#bib-PROV-PRIMER">PROV-PRIMER</a></cite>];</li>
-<li> <a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/">PROV-O</a> <span class="delete">(Candidate</span><span class="insert">(Proposed</span> Recommendation), the PROV ontology, an OWL2 ontology allowing the mapping of PROV to RDF [<cite><a class="bibref" href="#bib-PROV-O">PROV-O</a></cite>];</li>
-<li> <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/">PROV-DM</a> <span class="delete">(Candidate</span><span class="insert">(Proposed</span> Recommendation), the PROV data model for provenance (this document);</li>
-<li> <a href="http://www.w3.org/TR/2013/PR-prov-n-20130312/">PROV-N</a> <span class="delete">(Candidate</span><span class="insert">(Proposed</span> Recommendation), a notation for provenance aimed at human consumption [<cite><a class="bibref" href="#bib-PROV-N">PROV-N</a></cite>];</li>
-<li> <a href="http://www.w3.org/TR/2013/PR-prov-constraints-20130312/">PROV-CONSTRAINTS</a> <span class="delete">(Candidate</span><span class="insert">(Proposed</span> Recommendation), a set of constraints applying to the PROV data model [<cite><a class="bibref" href="#bib-PROV-CONSTRAINTS">PROV-CONSTRAINTS</a></cite>];</li>
-<li> <a href="http://www.w3.org/TR/2013/WD-prov-xml-20130312/"><span class="insert">PROV-XML</span></a><span class="insert"> (To be published as Note), an XML schema for the PROV data model [</span><cite><a class="bibref" href="#bib-PROV-XML"><span class="insert">PROV-XML</span></a></cite><span class="insert">];</span></li>
-<li> <a href="http://www.w3.org/TR/2013/WD-prov-aq-20130312/">PROV-AQ</a> (To be published as Note), the mechanisms for accessing and querying provenance [<cite><a class="bibref" href="#bib-PROV-AQ">PROV-AQ</a></cite>]; </li>
-<li> <span class="delete">PROV-XML</span><a href="http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/"><span class="insert">PROV-DICTIONARY</span></a> (To be published as <span class="delete">Note), an XML schema for the PROV data model</span><span class="insert">Note) introduces a specific type of collection, consisting of key-entity pairs</span> [<cite><span class="delete">PROV-XML</span><a class="bibref" href="#bib-PROV-DICTIONARY"><span class="insert">PROV-DICTIONARY</span></a></cite><span class="insert">];</span></li>
-<li> <a href="http://www.w3.org/TR/2013/WD-prov-dc-20130312/"><span class="insert">PROV-DC</span></a><span class="insert"> (To be published as Note) provides a mapping between PROV and Dublic Core Terms [</span><cite><a class="bibref" href="#bib-PROV-DC"><span class="insert">PROV-DC</span></a></cite><span class="insert">];</span></li>
-<li> <a href="http://www.w3.org/TR/2013/WD-prov-sem-20130312/"><span class="insert">PROV-SEM</span></a><span class="insert"> (To be published as Note), a declarative specification in terms of first-order logic of the PROV data model [</span><cite><a class="bibref" href="#bib-PROV-SEM"><span class="insert">PROV-SEM</span></a></cite><span class="insert">];</span></li>
-<li> <a href="http://www.w3.org/TR/2013/WD-prov-links-20130312/"><span class="insert">PROV-LINKS</span></a><span class="insert"> (To be published as Note) introduces a mechanism to link across bundles [</span><cite><a class="bibref" href="#bib-PROV-LINKS"><span class="insert">PROV-LINKS</span></a></cite>].</li>
-
-
-<span class="delete">How to read the PROV Family of Documents</span>
-
-<span class="delete">[</span><span class="delete">PROV-OVERVIEW</span><span class="delete">] overviews the PROV family of documents. </span>
-<span class="delete">The primer [</span><span class="delete">PROV-PRIMER</span><span class="delete">] is the entry point to PROV offering an introduction to the provenance model.</span>
-<span class="delete">The Linked Data and Semantic Web community should focus on [</span><span class="delete">PROV-O</span><span class="delete">] defining PROV classes and properties specified in an OWL2 ontology. For further details, PROV-DM and [</span><span class="delete">PROV-CONSTRAINTS</span><span class="delete">] specify the constraints applicable to the data model, and its interpretation. </span>
-<span class="delete">The XML community should focus on [</span><span class="delete">PROV-XML</span><span class="delete">] defining an XML schema for PROV. Further details can also be found in PROV-DM and [</span><span class="delete">PROV-CONSTRAINTS</span><span class="delete">].</span>
-<span class="delete">Developers seeking to retrieve or publish provenance should focus on [</span><span class="delete">PROV-AQ</span><span class="delete">].</span>
-<span class="delete">Readers seeking to implement other PROV serializations
-should focus on PROV-DM and [</span><span class="delete">PROV-CONSTRAINTS</span><span class="delete">]. [</span><span class="delete">PROV-O</span><span class="delete">], [</span><span class="delete">PROV-N</span><span class="delete">], and [</span><span class="delete">PROV-XML</span><span class="delete">] offer examples of mapping to RDF, text, and XML, respectively.</span>
+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> <span class="delete">(To be published as Note),</span><span class="insert">(Note),</span> 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> <span class="delete">(To be published as Note),</span><span class="insert">(Note),</span> 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> <span class="delete">(Proposed Recommendation),</span><span class="insert">(Recommendation),</span> the PROV ontology, an OWL2 ontology allowing the mapping of PROV to RDF [<cite><a class="bibref" href="#bib-PROV-O">PROV-O</a></cite>];</li>
+<li> <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/">PROV-DM</a> <span class="delete">(Proposed Recommendation),</span><span class="insert">(Recommendation),</span> 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> <span class="delete">(Proposed Recommendation),</span><span class="insert">(Recommendation),</span> 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> <span class="delete">(Proposed Recommendation),</span><span class="insert">(Recommendation),</span> 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> <span class="delete">(To be published as Note),</span><span class="insert">(Note),</span> 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> <span class="delete">(To be published as Note),</span><span class="insert">(Note),</span> the mechanisms for accessing and querying provenance [<cite><a class="bibref" href="#bib-PROV-AQ">PROV-AQ</a></cite>]; </li>
+<li> <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/">PROV-DICTIONARY</a> <span class="delete">(To be published as Note)</span><span class="insert">(Note)</span> introduces a specific type of collection, consisting of key-entity pairs [<cite><a class="bibref" href="#bib-PROV-DICTIONARY">PROV-DICTIONARY</a></cite>];</li>
+<li> <a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/">PROV-DC</a> <span class="delete">(To be published as Note)</span><span class="insert">(Note)</span> provides a mapping between PROV and Dublic Core Terms [<cite><a class="bibref" href="#bib-PROV-DC">PROV-DC</a></cite>];</li>
+<li> <a href="http://www.w3.org/TR/2013/NOTE-prov-sem-20130430/">PROV-SEM</a> <span class="delete">(To be published as Note),</span><span class="insert">(Note),</span> a declarative specification in terms of first-order logic of the PROV data model [<cite><a class="bibref" href="#bib-PROV-SEM">PROV-SEM</a></cite>];</li>
+<li> <a href="http://www.w3.org/TR/2013/NOTE-prov-links-20130430/">PROV-LINKS</a> <span class="delete">(To be published as Note)</span><span class="insert">(Note)</span> introduces a mechanism to link across bundles [<cite><a class="bibref" href="#bib-PROV-LINKS">PROV-LINKS</a></cite>].</li>
</ul>
-<h4 id="w3c-members-please-review-by-09-april-2013"><abbr title="World Wide Web Consortium"><span class="insert">W3C</span></abbr><span class="insert"> Members </span>Please <span class="delete">Comment</span><span class="insert">Review</span> By <span class="delete">January 31,</span><span class="insert">09 April</span> 2013</h4>
-
-<p>The<span class="delete"> Provenance Working Group seeks to gather experience from </span><span class="delete">implementations</span><span class="delete"> in order to increase confidence in the specifications and meet specific </span><span class="delete">exit criteria</span><span class="delete">. This document will remain a Candidate Recommendation until at least 31 January 31, 2013. After that date, when and if the exit criteria are met, the group intends to request </span><span class="delete">Proposed Recommendation</span><span class="delete"> status.
-
-
-
- </span><span class="delete">
- This document was published by the </span><span class="delete">Provenance Working Group</span><span class="delete"> as a Candidate Recommendation.
-
- This document is intended to become a</span> <abbr title="World Wide Web Consortium">W3C</abbr> <span class="insert">Director seeks review and feedback from </span><abbr title="World Wide Web Consortium"><span class="insert">W3C</span></abbr><span class="insert"> Advisory Committee representatives by 09 April 2013. This will allow the Director to assess consensus and determine whether to issue this document as a </span><abbr title="World Wide Web Consortium"><span class="insert">W3C</span></abbr> Recommendation.<span class="delete">
-
- If you wish</span></p>
-
-<p><span class="insert">Others are encouraged by the Provenance Working Group</span> to <span class="delete">make comments regarding this document, please</span><span class="insert">continue to</span> send <span class="delete">them</span><span class="insert">reports of implementation experience, and other feedback,</span> 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>).
+<span class="delete">W3C</span><span class="delete"> Members Please Review By 09 April 2013</span>
+
+
+
+
+ <p><span class="delete">The </span><span class="delete">W3C</span><span class="delete"> Director seeks review and feedback from </span><span class="delete">W3C</span><span class="delete"> Advisory Committee representatives</span><span class="insert">
+ This document was published</span> by <span class="delete">09 April 2013. This will allow the Director</span><span class="insert">the </span><a href="http://www.w3.org/2011/prov/"><span class="insert">Provenance Working Group</span></a><span class="insert"> as a Recommendation.
- <span class="insert"> Open discussion among developers is also welcome at
-</span><a href="mailto:public-prov-comments@w3.org"><span class="insert">public-prov-comments@w3.org</span></a><span class="insert">
- (</span><a href="mailto:public-prov-comments-request@w3.org?subject=subscribe"><span class="insert">subscribe</span></a><span class="insert">,
- </span><a href="http://lists.w3.org/Archives/Public/public-prov-comments/"><span class="insert">archives</span></a><span class="insert">).</span></p>
-
- <p><span class="insert">
- This document was published by the </span><a href="http://www.w3.org/2011/prov/"><span class="insert">Provenance Working Group</span></a><span class="insert"> as a Proposed Recommendation.
+ If you wish</span> to <span class="delete">assess consensus and determine whether</span><span class="insert">make comments regarding this document, please send them</span> to<span class="delete"> issue this document as a </span><span class="delete">W3C</span><span class="delete"> Recommendation.</span>
+
+<span class="delete">Others are encouraged by the Provenance Working Group to continue to send reports of implementation experience, and other feedback, to
+</span>
+ <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>).<span class="delete"> Open discussion among developers is also welcome at
+</span><span class="delete">public-prov-comments@w3.org</span><span class="delete">
+ (</span><span class="delete">subscribe</span><span class="delete">,
+ </span><span class="delete">archives</span><span class="delete">).</span><span class="insert">
- This document is intended to become a </span><abbr title="World Wide Web Consortium">W3C</abbr> <span class="delete">publishes a Candidate Recommendation </span><span class="insert">Recommendation.
+
+
+
+ All comments are welcome.
+
+
+
+ </span></p>
+
+ <span class="delete">
+ This document was published by the </span><span class="delete">Provenance Working Group</span><span class="delete"> as a Proposed Recommendation.
+
+ This document is intended to become a </span><span class="delete">W3C</span><span class="delete"> Recommendation.
- The </span><abbr title="World Wide Web Consortium"><span class="insert">W3C</span></abbr><span class="insert"> Membership and other interested parties are invited
- </span>to <span class="delete">indicate</span><span class="insert">review the document and send comments to
-
- </span><a href="mailto:public-prov-comments@w3.org"><span class="insert">public-prov-comments@w3.org</span></a><span class="insert">
- (</span><a href="mailto:public-prov-comments-request@w3.org?subject=subscribe"><span class="insert">subscribe</span></a><span class="insert">,
- </span><a href="http://lists.w3.org/Archives/Public/public-prov-comments/"><span class="insert">archives</span></a><span class="insert">)
+ The </span><span class="delete">W3C</span><span class="delete"> Membership and other interested parties are invited
+ to review the document and send comments to
+
+ </span><span class="delete">public-prov-comments@w3.org</span><span class="delete">
+ (</span><span class="delete">subscribe</span><span class="delete">,
+ </span><span class="delete">archives</span><span class="delete">)
through 09 April 2013.
Advisory Committee Representatives should consult their
- </span><a href="https://www.w3.org/2002/09/wbs/myQuestionnaires"><span class="insert">WBS questionnaires</span></a><span class="insert">.
- Note</span> that <span class="delete">the document is believed
- to be stable and to encourage implementation by the developer community. This
- Candidate Recommendation is</span><span class="insert">substantive technical comments were</span> expected <span class="delete">to advance to Proposed Recommendation no earlier than
- 31 January 2013.
-
- All feedback is welcome.</span><span class="insert">during the Last Call review period that ended 18 September 2012.</span>
- </p>
-
-
+ </span><span class="delete">WBS questionnaires</span><span class="delete">.
+ Note that substantive technical comments were expected during the Last Call review period that ended 18 September 2012.
+ </span>
- <p>
- Publication as a <span class="delete">Candidate</span><span class="insert">Proposed</span> Recommendation does not imply endorsement by the <abbr title="World Wide Web Consortium">W3C</abbr> Membership.
+ <span class="delete">
+ Publication as a Proposed Recommendation does not imply endorsement by the </span><span class="delete">W3C</span><span class="delete"> Membership.
This is a draft document and may be updated, replaced or obsoleted by other documents at
any time. It is inappropriate to cite this document as other than work in progress.
- </p>
+ </span>
<p>
@@ -1022,7 +1003,7 @@
</section><section id="toc"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a href="#introduction" class="tocxref"><span class="secno">1. </span>Introduction<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><span class="insert">Change Log</span></a><ul class="toc"><li class="tocline"><a href="#changes-since-candidate-recommendation" class="tocxref"><span class="secno"><span class="insert">B.1 </span></span>Changes since <span class="delete">last version</span><span class="insert">Candidate Recommendation</span></a></li><li class="tocline"><a href="#changes-since-last-call" class="tocxref"><span class="secno"><span class="insert">B.2 </span></span><span class="insert">Changes since Last Call</span></a></li></ul></li><li class="tocline"><a href="#acknowledgements" class="tocxref"><span class="secno">C. </span>Acknowledgements</a></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">D. </span>References</a><ul class="toc"><li class="tocline"><a href="#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>
+</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"><span class="insert">B.1 </span></span><span class="insert">Changes since Proposed Recommendation</span></a></li><li class="tocline"><a href="#changes-since-candidate-recommendation" class="tocxref"><span class="secno"><span class="delete">B.1</span><span class="insert">B.2</span> </span>Changes since Candidate Recommendation</a></li><li class="tocline"><a href="#changes-since-last-call" class="tocxref"><span class="secno"><span class="delete">B.2</span><span class="insert">B.3</span> </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>
@@ -1139,10 +1120,10 @@
-<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
+<p>The key words "<span class="delete">must</span><em class="rfc2119" title="MUST"><span class="insert">MUST</span></em>", "<span class="delete">must not</span><em class="rfc2119" title="MUST NOT"><span class="insert">MUST NOT</span></em>", "<span class="delete">required</span><em class="rfc2119" title="REQUIRED"><span class="insert">REQUIRED</span></em>", "<span class="delete">shall</span><em class="rfc2119" title="SHALL"><span class="insert">SHALL</span></em>", "<span class="delete">shall</span><em class="rfc2119" title="SHALL
+ NOT"><span class="insert">SHALL</span>
+ <span class="delete">not</span><span class="insert">NOT</span></em>", "<span class="delete">should</span><em class="rfc2119" title="SHOULD"><span class="insert">SHOULD</span></em>", "<span class="delete">should not</span><em class="rfc2119" title="SHOULD NOT"><span class="insert">SHOULD NOT</span></em>", "<span class="delete">recommended</span><em class="rfc2119" title="RECOMMENDED"><span class="insert">RECOMMENDED</span></em>", "<span class="delete">may</span><em class="rfc2119" title="MAY"><span class="insert">MAY</span></em>", and
+ "<span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></em>" in this document are to be interpreted as described in
[<cite><a class="bibref" href="#bib-RFC2119">RFC2119</a></cite>].</p>
<p>
@@ -2012,7 +1993,7 @@
and
<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 <em class="rfc2119" title="optional">optional</em> <a title="time" href="#dfn-time" class="internalDFN">time</a> is also permitted.
+The letter 'T' indicates an <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></em> <a title="time" href="#dfn-time" class="internalDFN">time</a> is also permitted.
</p>
@@ -2077,7 +2058,7 @@
<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 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 href="#concept-specialization" class="internalDFN">Specialization</a></td><td><a title="specializationOf" href="#dfn-specializationof" class="internalDFN">specializationOf(infra, supra)</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>
@@ -2122,7 +2103,7 @@
<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 <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>
+<li><span class="attribute" id="entity.attributes">attributes</span>: an <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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="anexampleTitle">Example 17<sup><a class="internalDFN" href="#anexample-entity"><span class="diamond"> ◊</span></a></sup></div>
@@ -2147,9 +2128,9 @@
<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 <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>
+<li><span class="attribute" id="activity.startTime">startTime</span>: an <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></em> time (<span class="name">st</span>) for the start of the activity;</li>
+<li><span class="attribute" id="activity.endTime">endTime</span>: an <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></em> time (<span class="name">et</span>) for the end of the activity;</li>
+<li><span class="attribute" id="activity.attributes">attributes</span>: an <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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="anexampleTitle">Example 18<sup><a class="internalDFN" href="#anexample-activity"><span class="diamond"> ◊</span></a></sup></div>
@@ -2184,15 +2165,15 @@
<p>
</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 <em class="rfc2119" title="optional">optional</em> identifier for a generation;</li>
+<li><span class="attribute" id="generation.id">id</span>: an <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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>
+<li><span class="attribute" id="generation.activity">activity</span>: an <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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 <em class="rfc2119" title="optional">optional</em>, at least one of them <em class="rfc2119" title="must">must</em> be present.</p>
+<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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></em>, at least one of them <span class="delete">must</span><em class="rfc2119" title="MUST"><span class="insert">MUST</span></em> be present.</p>
@@ -2232,17 +2213,17 @@
<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 <em class="rfc2119" title="optional">optional</em> identifier for a usage;</li>
+<li><span class="attribute" id="usage.id">id</span>: an <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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>
+<li><span class="attribute" id="usage.entity">entity</span>: an <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></em> identifier (<span class="name">e</span>) for the entity being used;</li>
+<li><span class="attribute" id="usage.time">time</span>: an <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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 <em class="rfc2119" title="optional">optional</em>, at least one of them <em class="rfc2119" title="must">must</em> 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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></em>, at least one of them <span class="delete">must</span><em class="rfc2119" title="MUST"><span class="insert">MUST</span></em> be present.</p>
<p>
-A reference to a given entity <em class="rfc2119" title="may">may</em> appear in multiple usages that share
+A reference to a given entity <span class="delete">may</span><em class="rfc2119" title="MAY"><span class="insert">MAY</span></em> appear in multiple usages that share
a given activity identifier.
</p>
@@ -2278,10 +2259,10 @@
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 <em class="rfc2119" title="optional">optional</em> identifier identifying the relation;</li>
+<li><span class="attribute" id="communication.id">id</span>: an <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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>
+</li><li><span class="attribute" id="communication.attributes">attributes</span>: an <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></em> set (<span class="name">attrs</span>) of attribute-value pairs representing additional information about this communication.</li>
</ul>
</div>
@@ -2301,23 +2282,23 @@
<section id="term-Start">
<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" 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>
+<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></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 <em class="rfc2119" title="optional">optional</em> identifier for the activity start;</li>
+<li><span class="attribute" id="start.id">id</span>: an <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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><span class="attribute" id="start.trigger">trigger</span>: an <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></em> identifier (<span class="name">e</span>) for the entity triggering the activity;</li>
+<li><span class="attribute" id="start.starter">starter</span>: an <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></em> time (<span class="name">t</span>) at which the activity was started; </li>
+<li><span class="attribute" id="start.attributes">attributes</span>: an <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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 <em class="rfc2119" title="optional">optional</em>, at least one of them <em class="rfc2119" title="must">must</em> be present.</p>
+<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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></em>, at least one of them <span class="delete">must</span><em class="rfc2119" title="MUST"><span class="insert">MUST</span></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>
@@ -2378,23 +2359,23 @@
<section id="term-End">
<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" 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>
+<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></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 <em class="rfc2119" title="optional">optional</em> identifier for the activity end;</li>
+<li><span class="attribute" id="end.id">id</span>: an <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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><li><span class="attribute" id="end.trigger">trigger</span>: an <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></em> time (<span class="name">t</span>) at which the activity was ended; </li>
+<li><span class="attribute" id="end.attributes">attributes</span>: an <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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 <em class="rfc2119" title="optional">optional</em>, at least one of them <em class="rfc2119" title="must">must</em> be present.</p>
+<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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></em>, at least one of them <span class="delete">must</span><em class="rfc2119" title="MUST"><span class="insert">MUST</span></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>
@@ -2402,7 +2383,7 @@
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" ])
activity(a1, [ prov:type="Editing" ])
-wasEndedBy(a1, e1)
+wasEndedBy(a1, <span class="delete">e1)</span><span class="insert">e1, -, -)</span>
</pre>
</div>
</section>
@@ -2436,15 +2417,15 @@
<p>
</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 <em class="rfc2119" title="optional">optional</em> identifier for a invalidation;</li>
+<li><span class="attribute" id="invalidation.id">id</span>: an <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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>
+<li><span class="attribute" id="invalidation.activity">activity</span>: an <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></em> identifier for the activity that invalidated the entity;</li>
+
+<li><span class="attribute" id="invalidation.time">time</span>: an <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></em> "invalidation time", the time at which the entity began to be invalidated;</li>
+
+<li><span class="attribute" id="invalidation.attributes">attributes</span>: an <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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 <em class="rfc2119" title="optional">optional</em>, at least one of them <em class="rfc2119" title="must">must</em> be present.</p>
+<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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></em>, at least one of them <span class="delete">must</span><em class="rfc2119" title="MUST"><span class="insert">MUST</span></em> be present.</p>
@@ -2556,13 +2537,13 @@
<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 <em class="rfc2119" title="optional">optional</em> identifier for a derivation;</li>
+<li><span class="attribute" id="derivation.id">id</span>: an <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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>
+<li><span class="attribute" id="derivation.activity">activity</span>: an <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></em> set (<span class="name">attrs</span>) of attribute-value pairs representing additional information about this derivation.</li>
</ul>
</div>
@@ -2768,20 +2749,19 @@
<ul>
<li><span class="name">SoftwareAgent</span>
-
-<p><span class="glossary-ref"> A <dfn id="concept-software-agent" title="software-agent" class="internalDFN">SoftwareAgent</dfn><sup><a class="internalDFN" href="#concept-software-agent"><span class="diamond"> ◊</span></a></sup> is running software. </span><span class="insert"> The type of a SoftwareAgent is denoted by </span><dfn title="dfn-prov:softwareAgent" id="dfn-prov:softwareAgent" class="internalDFN"><span class="name"><span class="insert">prov:SoftareAgent</span></span></dfn><sup><a class="internalDFN" href="#dfn-prov:softwareAgent"><span class="diamond"><span class="insert"> ◊</span></span></a></sup><span class="insert">.</span></p>
+<p><span class="glossary-ref"> A <dfn id="concept-software-agent" title="software-agent" class="internalDFN">SoftwareAgent</dfn><sup><a class="internalDFN" href="#concept-software-agent"><span class="diamond"> ◊</span></a></sup> is running software. </span> The type of a SoftwareAgent is denoted by <dfn title="dfn-prov:softwareAgent" id="dfn-prov:softwareAgent" class="internalDFN"><span class="name">prov:SoftareAgent</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"> Agents of type <dfn id="concept-organization" class="internalDFN">Organization</dfn><sup><a class="internalDFN" href="#concept-organization"><span class="diamond"> ◊</span></a></sup> are social or legal institutions such as companies, societies, etc. </span><span class="insert"> The type of an Organization agent is denoted by </span><dfn title="dfn-prov:organization" id="dfn-prov:organization" class="internalDFN"><span class="name"><span class="insert">prov:Organization</span></span></dfn><sup><a class="internalDFN" href="#dfn-prov:organization"><span class="diamond"><span class="insert"> ◊</span></span></a></sup><span class="insert">.</span></p>
+<p><span class="glossary-ref"> Agents of type <dfn id="concept-organization" class="internalDFN">Organization</dfn><sup><a class="internalDFN" href="#concept-organization"><span class="diamond"> ◊</span></a></sup> are social or legal institutions such as companies, societies, 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"> Agents of type <dfn id="concept-person" title="Person" class="internalDFN">Person</dfn><sup><a class="internalDFN" href="#concept-person"><span class="diamond"> ◊</span></a></sup> are people. </span><span class="insert"> The type of a Person agent is denoted by </span><dfn title="dfn-prov:person" id="dfn-prov:person" class="internalDFN"><span class="name"><span class="insert">prov:Person</span></span></dfn><sup><a class="internalDFN" href="#dfn-prov:person"><span class="diamond"><span class="insert"> ◊</span></span></a></sup><span class="insert">.</span></p>
+<p><span class="glossary-ref"> Agents of type <dfn id="concept-person" title="Person" class="internalDFN">Person</dfn><sup><a class="internalDFN" href="#concept-person"><span class="diamond"> ◊</span></a></sup> 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>
@@ -2807,10 +2787,10 @@
<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 <em class="rfc2119" title="optional">optional</em> identifier for the relation;</li>
+<li><span class="attribute" id="attribution.id">id</span>: an <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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>
+<li><span class="attribute" id="attribution.attributes">attributes</span>: an <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></em> set (<span class="name">attrs</span>) of attribute-value pairs representing additional information about this attribution.</li>
</ul>
</div>
@@ -2836,31 +2816,22 @@
<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>
-<span class="delete"> A </span><span class="delete">plan</span><span class="delete"> ◊</span><span class="delete"> is an entity that represents a set of actions or steps intended by one or more agents to achieve some goals. </span>
-
-
-
-
-
<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 <em class="rfc2119" title="optional">optional</em> identifier for the association between an activity and an agent;</li>
+<li><span class="attribute" id="association.id">id</span>: an <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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>
+<li><span class="attribute" id="association.agent">agent</span>: an <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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 <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"><span class="insert"> A </span><dfn id="concept-plan" title="Plan" class="internalDFN"><span class="insert">plan</span></dfn><sup><a class="internalDFN" href="#concept-plan"><span class="diamond"><span class="insert"> ◊</span></span></a></sup><span class="insert"> is an entity that represents a set of actions or steps intended by one or more agents to achieve some goals. </span></span><span class="insert"> The type of a Plan entity is denoted by </span><dfn title="dfn-prov:plan" id="dfn-prov:plan" class="internalDFN"><span class="name"><span class="insert">prov:Plan</span></span></dfn><sup><a class="internalDFN" href="#dfn-prov:plan"><span class="diamond"><span class="insert"> ◊</span></span></a></sup><span class="insert">.</span></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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></em>, at least one of them <span class="delete">must</span><em class="rfc2119" title="MUST"><span class="insert">MUST</span></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>
@@ -2918,12 +2889,12 @@
</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 <em class="rfc2119" title="optional">optional</em> identifier for the delegation link between delegate and responsible;</li>
+<li><span class="attribute" id="delegation.id">id</span>: an <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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 <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>
+<li><span class="attribute" id="delegation.activity">activity</span>: an <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></em> set (<span class="name">attrs</span>) of attribute-value pairs representing additional information about this delegation link.</li>
</ul></div>
@@ -2963,21 +2934,21 @@
</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 <em class="rfc2119" title="optional">optional</em> identifier identifying the relation;</li>
+<li><span class="attribute" id="influence.id">id</span>: an <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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>
+</li><li><span class="attribute" id="influence.attributes">attributes</span>: an <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></em> set (<span class="name">attrs</span>) of attribute-value pairs representing additional information about this relation.</li>
</ul></div>
<p>
-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.
+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 <span class="delete">recommended</span><em class="rfc2119" title="RECOMMENDED"><span class="insert">RECOMMENDED</span></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
-<span class="delete">usage</span><a href="#concept-usage" class="internalDFN"><span class="insert">Usage</span></a>, <span class="delete">start</span><a href="#concept-start" class="internalDFN"><span class="insert">Start</span></a>, <span class="delete">end</span><a href="#concept-end" class="internalDFN"><span class="insert">End</span></a>, <span class="delete">generation</span><a href="#concept-generation" class="internalDFN"><span class="insert">Generation</span></a>, <span class="delete">invalidation</span><a href="#concept-invalidation" class="internalDFN"><span class="insert">Invalidation</span></a>, <span class="delete">communication</span><a href="#concept-communication" class="internalDFN"><span class="insert">Communication</span></a>, <a href="#concept-derivation" class="internalDFN"><span class="delete">derivation</span><span class="insert">Derivation</span></a>, <span class="delete">attribution</span><a href="#concept-attribution" class="internalDFN"><span class="insert">Attribution</span></a>, <a href="#concept-association" class="internalDFN"><span class="delete">association</span><span class="insert">Association</span></a>, and <span class="delete">delegation</span><a href="#concept-delegation" class="internalDFN"><span class="insert">Delegation</span></a>.
+<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>
@@ -3082,9 +3053,9 @@
<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" class="internalDFN">type for <span class="delete">bundles:</span><span class="insert">bundles</span></dfn><sup><a class="internalDFN" href="#dfn-bundle-type"><span class="diamond"><span class="insert"> ◊</span></span></a></sup><span class="insert">:</span></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" class="internalDFN"><span class="name">prov:Bundle</span></dfn><sup><a class="internalDFN" href="#dfn-prov:bundle"><span class="diamond"><span class="insert"> ◊</span></span></a></sup> is the type that denotes <span class="delete">bundles</span><span class="delete">.</span><span class="insert">Bundle entities.</span>
+<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>
@@ -3093,7 +3064,7 @@
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,
a type <span>prov:Bundle</span> and
-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.
+an <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></em> set of attribute-value pairs ((<span class="name">attr1</span>, <span class="name">val1</span>), ...) representing additional information about this bundle.
</p>
@@ -3182,7 +3153,7 @@
<p>The fifth component of PROV-DM is concerned with
-relations SpecializationOf (<a href="#concept-specialization" class="internalDFN"><span class="delete">specialization</span><span class="insert">Specialization</span></a>) and AlternateOf (<a href="#concept-alternate" class="internalDFN"><span class="delete">alternate</span><span class="insert">Alternate</span></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>
@@ -3318,7 +3289,7 @@
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 <span class="delete">(HadMember).</span><span class="insert">HadMember (</span><a href="#concept-membership" class="internalDFN"><span class="insert">Membership</span></a><span class="insert">).</span>
+the sixth component with two new classes (Collection, Empty Collection) and one association HadMember (<a href="#concept-membership" class="internalDFN">Membership</a>).
</p>
@@ -3341,9 +3312,9 @@
<p>PROV-DM defines the following types related to collections:</p>
<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 class="insert"> ◊</span></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 class="insert"> ◊</span></span></a></sup> denotes an empty collection.
+ <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>
@@ -3456,7 +3427,7 @@
<p>
<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>
+The value associated with the attribute <span class="name">prov:label</span> <span class="delete">must</span><em class="rfc2119" title="MUST"><span class="insert">MUST</span></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>
@@ -3479,7 +3450,7 @@
<p>
-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.
+The attribute <span class="name">prov:location</span> is an <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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> <span class="delete">must</span><em class="rfc2119" title="MUST"><span class="insert">MUST</span></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>
@@ -3503,7 +3474,7 @@
<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 <em class="rfc2119" title="must">must</em> be a PROV-DM <a title="value" href="#concept-value" class="internalDFN">Value</a>.</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 <span class="delete">must</span><em class="rfc2119" title="MUST"><span class="insert">MUST</span></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>
@@ -3523,7 +3494,7 @@
<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 <em class="rfc2119" title="must">must</em> be a PROV-DM <a title="value" href="#concept-value" class="internalDFN"><span class="delete">Value.</span><span class="insert">Value</span></a><span class="insert">.</span> The attribute <span class="name">prov:type</span>
+the value associated with a <span class="name">prov:type</span> attribute <span class="delete">must</span><em class="rfc2119" title="MUST"><span class="insert">MUST</span></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" id="example_51"><div class="anexampleTitle">Example 51<sup><a class="internalDFN" href="#example_51"><span class="diamond"> ◊</span></a></sup></div>
@@ -3544,7 +3515,7 @@
<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 <span class="delete">5.1.1</span><span class="insert">5.3.3</span></span></a></td><td><a href="#concept-entity" class="internalDFN">Entity</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>
@@ -3561,7 +3532,7 @@
-<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>
+<p>The attribute <span class="name">prov:value</span> is an <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></em> attribute of entity. The value associated with the attribute <span class="name">prov:value</span> <span class="delete">must</span><em class="rfc2119" title="MUST"><span class="insert">MUST</span></em> be a PROV-DM <a title="value" href="#concept-value" class="internalDFN">Value</a>. The attribute <span class="name">prov:value</span> <span class="delete">may</span><em class="rfc2119" title="MAY"><span class="insert">MAY</span></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>.
@@ -3577,7 +3548,7 @@
</div>
<p>
-Two different entities <em class="rfc2119" title="may">may</em> have the same value for the attribute
+Two different entities <span class="delete">may</span><em class="rfc2119" title="MAY"><span class="insert">MAY</span></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
@@ -3610,7 +3581,7 @@
<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 <em class="rfc2119" title="recommended">recommended</em>. </p>
+ Use of the following data types is <span class="delete">recommended</span><em class="rfc2119" title="RECOMMENDED"><span class="insert">RECOMMENDED</span></em>. </p>
<ul>
<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>
@@ -3649,7 +3620,7 @@
"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/PR-prov-n-20130312/#prod-QUALIFIED_NAME">prov:QUALIFIED_NAME</a></span> [<cite><a class="bibref" href="#bib-PROV-N">PROV-N</a></cite>]).
+<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
@@ -3694,12 +3665,12 @@
<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 <a href="#dfn-namespace" class="internalDFN">namespace</a> interpretation. It consists of a <a href="#dfn-namespace" class="internalDFN">namespace</a>, denoted by an optional prefix, and a local name. </span>
+<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 <span class="delete">namespace</span><span class="delete">,</span><span class="insert">namespace,</span> 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 <em class="rfc2119" title="optional">optional</em>. If a prefix occurs in a
+<p>A qualified name's prefix is <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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>
@@ -3795,7 +3766,7 @@
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 [<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
+They <span class="delete">should</span><em class="rfc2119" title="SHOULD"><span class="insert">SHOULD</span></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>
@@ -3825,50 +3796,50 @@
<tr class="component1-color">
<td><a title="Entity" href="#concept-entity" class="internalDFN">Entity</a></td>
-<td><a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/#Entity">Entity</a></td>
-<td><code><a href="http://www.w3.org/TR/2013/PR-prov-n-20130312/#prod-entityExpression">entityExpression</a></code>
+<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" href="#concept-activity" class="internalDFN">Activity</a></td>
-<td><a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/#Entity">Activity</a></td>
-<td><code><a href="http://www.w3.org/TR/2013/PR-prov-n-20130312/#prod-activityExpression">activityExpression</a></code></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" href="#concept-generation" class="internalDFN">Generation</a></td>
-<td><a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/#wasGeneratedBy">wasGeneratedBy</a>, <a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/#Generation">Generation</a></td>
-<td><code><a href="http://www.w3.org/TR/2013/PR-prov-n-20130312/#prod-generationExpression">generationExpression</a></code></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" href="#concept-usage" class="internalDFN">Usage</a></td>
-<td><a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/#used">used</a>, <a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/#Usage">Usage</a></td>
-<td><code><a href="http://www.w3.org/TR/2013/PR-prov-n-20130312/#prod-usageExpression">usageExpression</a></code></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" href="#concept-communication" class="internalDFN">Communication</a></td>
-<td><a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/#wasInformedBy">wasInformedBy</a>, <a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/#Communication">Communication</a></td>
-<td><code><a href="http://www.w3.org/TR/2013/PR-prov-n-20130312/#prod-communicationExpression">communicationExpression</a></code></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" href="#concept-start" class="internalDFN">Start</a></td>
-<td><a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/#wasStartedBy">wasStartedBy</a>, <a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/#Start">Start</a></td>
-<td><code><a href="http://www.w3.org/TR/2013/PR-prov-n-20130312/#prod-startExpression">startExpression</a></code></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" href="#concept-end" class="internalDFN">End</a></td>
-<td><a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/#wasEndedBy">wasEndedBy</a>, <a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/#End">End</a></td>
-<td><code><a href="http://www.w3.org/TR/2013/PR-prov-n-20130312/#prod-endExpression">endExpression</a></code></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" href="#concept-invalidation" class="internalDFN">Invalidation</a></td>
-<td><a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/#wasInvalidatedBy">wasInvalidatedBy</a>, <a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/#Invalidation">Invalidation</a></td>
-<td><code><a href="http://www.w3.org/TR/2013/PR-prov-n-20130312/#prod-invalidationExpression">invalidationExpression</a></code></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>
<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>
@@ -3877,26 +3848,26 @@
<tr class="component2-color">
<td><a title="Derivation" href="#concept-derivation" class="internalDFN">Derivation</a></td>
-<td><a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/#wasDerivedFrom">wasDerivedFrom</a>, <a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/#Derivation">Derivation</a></td>
-<td><code><a href="http://www.w3.org/TR/2013/PR-prov-n-20130312/#prod-derivationExpression">derivationExpression</a></code></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>
</tr>
<tr class="component2-color">
<td class="provType"><a title="Revision" href="#concept-revision" class="internalDFN">Revision</a></td>
-<td><a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/#wasRevisionOf">wasRevisionOf</a>, <a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/#Revision">Revision</a></td>
-<td>type <code><a href="http://www.w3.org/TR/2013/PR-prov-n-20130312/#provn-type-Revision">Revision</a></code></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" href="#concept-quotation" class="internalDFN">Quotation</a></td>
-<td><a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/#wasQuotedFrom">wasQuotedFrom</a>, <a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/#Quotation">Quotation</a></td>
-<td>type <code><a href="http://www.w3.org/TR/2013/PR-prov-n-20130312/#provn-type-Quotation">Quotation</a></code></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" href="#concept-primary-source" class="internalDFN">Primary Source</a></td>
-<td><a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/#hadPrimarySource">hadPrimarySource</a>, <a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/#PrimarySource">PrimarySource</a></td>
-<td>type <code><a href="http://www.w3.org/TR/2013/PR-prov-n-20130312/#provn-type-Primary-Source">PrimarySource</a></code></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>
<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>
@@ -3905,57 +3876,57 @@
<tr class="component3-color" style="border-collapse: collapse; ">
<td><a title="Agent" href="#concept-agent" class="internalDFN">Agent</a></td>
-<td><a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/#Agent">Agent</a></td>
-<td><code><a href="http://www.w3.org/TR/2013/PR-prov-n-20130312/#prod-agentExpression">agentExpression</a></code></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>
</tr>
<tr class="component3-color">
<td><a title="Attribution" href="#concept-attribution" class="internalDFN">Attribution</a></td>
-<td><a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/#wasAttributedTo">wasAttributedTo</a>, <a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/#Attribution">Attribution</a></td>
-<td><code><a href="http://www.w3.org/TR/2013/PR-prov-n-20130312/#prod-attributionExpression">attributionExpression</a></code></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" href="#concept-association" class="internalDFN">Association</a></td>
-<td><a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/#wasAssociatedWith">wasAssociatedWith</a>, <a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/#Association">Association</a></td>
-<td><code><a href="http://www.w3.org/TR/2013/PR-prov-n-20130312/#prod-associationExpression">associationExpression</a></code></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" href="#concept-delegation" class="internalDFN">Delegation</a></td>
-<td><a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/#actedOnBehalfOf">actedOnBehalfOf</a>, <a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/#Delegation">Delegation</a></td>
-<td><code><a href="http://www.w3.org/TR/2013/PR-prov-n-20130312/#prod-delegationExpression">delegationExpression</a></code></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" href="#concept-plan" class="internalDFN">Plan</a></td>
-<td><a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/#Plan">Plan</a></td>
-<td>type <code><a href="http://www.w3.org/TR/2013/PR-prov-n-20130312/#provn-type-Plan">Plan</a></code></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" href="#concept-person" class="internalDFN">Person</a></td>
-<td><a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/#Person">Person</a></td>
-<td>type <code><a href="http://www.w3.org/TR/2013/PR-prov-n-20130312/#provn-type-Person">Person</a></code></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>
<tr class="component3-color">
<td><a title="Organization" href="#concept-organization" class="internalDFN">Organization</a></td>
-<td><a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/#Organization">Organization</a></td>
-<td>type <code><a href="http://www.w3.org/TR/2013/PR-prov-n-20130312/#provn-type-Organization">Organization</a></code></td>
+<td><a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/#Organization">Organization</a></td>
+<td>type <code><a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/#provn-type-Organization">Organization</a></code></td>
</tr>
<tr class="component3-color">
<td><a title="software-agent" href="#concept-software-agent" class="internalDFN">SoftwareAgent</a></td>
-<td><a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/#SoftwareAgent">SoftwareAgent</a></td>
-<td>type <code><a href="http://www.w3.org/TR/2013/PR-prov-n-20130312/#provn-type-SoftwareAgent">SoftwareAgent</a></code></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" href="#concept-influence" class="internalDFN">Influence</a></td>
-<td><a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/#wasInfluencedBy">wasInfluencedBy</a>, <a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/#Influence">Influence</a></td>
-<td><code><a href="http://www.w3.org/TR/2013/PR-prov-n-20130312/#prod-influenceExpression">influenceExpression</a></code></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>
<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>
@@ -3965,14 +3936,14 @@
<tr class="component4-color">
<td><a title="Bundle" href="#concept-bundle" class="internalDFN">Bundle constructor</a></td>
-<td> <a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/#description-bundle">bundle description</a> </td>
-<td><code><a href="http://www.w3.org/TR/2013/PR-prov-n-20130312/#prod-bundle">bundle</a></code></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>
</tr>
<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/PR-prov-o-20130312/#Bundle">Bundle</a></td>
-<td>type <code><a href="http://www.w3.org/TR/2013/PR-prov-n-20130312/#provn-type-Bundle">Bundle</a></code></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>
<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>
@@ -3980,15 +3951,15 @@
<tr class="component5-color">
<td><a title="Alternate" href="#concept-alternate" class="internalDFN">Alternate</a></td>
-<td><a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/#alternateOf">alternateOf</a></td>
-<td><code><a href="http://www.w3.org/TR/2013/PR-prov-n-20130312/#prod-alternateExpression">alternateExpression</a></code></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>
</tr>
<tr class="component5-color">
<td><a title="Specialization" href="#concept-specialization" class="internalDFN">Specialization</a></td>
-<td><a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/#specializationOf">specializationOf</a></td>
-<td><code><a href="http://www.w3.org/TR/2013/PR-prov-n-20130312/#prod-specializationExpression">specializationExpression</a></code></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>
<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>
@@ -3996,46 +3967,55 @@
<tr class="component6-color">
<td><a title="Collection" href="#concept-collection" class="internalDFN">Collection</a></td>
-<td><a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/#Collection">Collection</a></td>
-<td>type <code><a href="http://www.w3.org/TR/2013/PR-prov-n-20130312/#provn-type-Collection">Collection</a></code></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>
</tr>
<tr class="component6-color">
<td><a title="Empty Collection" href="#concept-empty-collection" class="internalDFN">EmptyCollection</a></td>
-<td><a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/#EmptyCollection">EmptyCollection</a></td>
-<td>type <code><a href="http://www.w3.org/TR/2013/PR-prov-n-20130312/#provn-type-EmptyCollection">EmptyCollection</a></code></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" href="#concept-membership" class="internalDFN">Membership</a></td>
-<td><a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/#hadMember">hadMember</a></td>
-<td><code><a href="http://www.w3.org/TR/2013/PR-prov-n-20130312/#prod-membershipExpression">membershipExpression</a></code></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>
</tbody></table>
</div>
</section>
<section class="appendix" id="change-log">
- <h2><span class="secno">B. </span><span class="insert">Change Log</span></h2>
-
+ <h2><span class="secno">B. </span>Change Log</h2>
+
+<section id="changes-since-proposed-recommendation">
+ <h3><span class="secno"><span class="insert">B.1 </span></span><span class="insert">Changes since Proposed Recommendation</span></h3>
+<ul>
+<li><span class="insert"> Changed the status of this document section.
+</span></li><li><span class="insert"> Changed all URLs to PROV documents.
+</span></li><li> <a href="http://www.w3.org/2011/prov/track/issues/653"><span class="insert">ISSUE-653</span></a><span class="insert">: Fixed typo in example to ensure compatibility with prov-n grammar.
+</span></li></ul>
+
+</section>
<section id="changes-since-candidate-recommendation">
- <h3><span class="secno"><span class="insert">B.1 </span></span>Changes since <span class="delete">last version</span><span class="insert">Candidate Recommendation</span></h3>
+ <h3><span class="secno"><span class="delete">B.1</span><span class="insert">B.2</span> </span>Changes since Candidate Recommendation</h3>
<ul>
-<li><span class="insert"> Checked all internal fragments resolved.
-</span></li><li><span class="insert"> 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.
-</span></li><li><span class="insert"> Changed all URLs to PROV documents.
-</span></li><li><span class="insert"> Fixed links to internal anchors, following change in respec.js
-</span></li><li><span class="insert"> Added anchors for prov:Bundle, prov:Collection, prov:Emptycollection, prov:Plan, prov:Person, prov:SoftwareAgent, prov:Organization, to facilitate systematic cross-referencing.
-</span></li><li><span class="insert"> Likewise, added anchor for Bundle Type.
-</span></li><li><span class="insert"> Table 9: fixed section number where plan is defined.
-</span></li><li><span class="insert"> Added html link to provenance.
-</span></li></ul>
+<li> Checked all internal fragments resolved.
+</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 id="changes-since-last-call">
- <h3><span class="secno"><span class="insert">B.2 </span></span><span class="insert">Changes since Last Call</span></h3>
+ <h3><span class="secno"><span class="delete">B.2</span><span class="insert">B.3</span> </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>
@@ -4073,9 +4053,6 @@
</li></ul>
</section>
-
-
-
</section>
<section class="appendix" id="acknowledgements">
@@ -4108,10 +4085,10 @@
Reza B'Far (Oracle Corporation),
Khalid Belhajjame (University of Manchester),
James Cheney (University of Edinburgh, School of Informatics),
-Sam Coppens <span class="delete">(IBBT),</span><span class="insert">(iMinds - Ghent University),</span>
+Sam Coppens (iMinds - Ghent University),
David Corsar (University of Aberdeen, Computing Science),
Stephen Cresswell (The National Archives),
-Tom De Nies <span class="delete">(IBBT),</span><span class="insert">(iMinds - Ghent University),</span>
+Tom De Nies (iMinds - Ghent University),
Helena Deus (DERI Galway at the National University of Ireland, Galway, Ireland),
Simon Dobson (Invited expert),
Martin Doerr (Foundation for Research and Technology - Hellas(FORTH)),
@@ -4167,28 +4144,25 @@
-<section id="references" class="appendix"><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/PR-prov-constraints-20130312/"><cite>Constraints of the PROV Data Model</cite></a>. <span class="delete">11 December 2012,</span><span class="insert">12 March 2013,</span> W3C <span class="delete">Candidate</span><span class="insert">Proposed</span> Recommendation. URL: <span class="delete">http://www.w3.org/TR/2012/CR-prov-constraints-20121211/</span><a href="http://www.w3.org/TR/2013/PR-prov-constraints-20130312/"><span class="insert">http://www.w3.org/TR/2013/PR-prov-constraints-20130312/</span></a>
-</dd><dt id="bib-PROV-N">[PROV-N]</dt><dd>Luc Moreau; Paolo Missier; eds. <a href="http://www.w3.org/TR/2013/PR-prov-n-20130312/"><cite>PROV-N: The Provenance Notation</cite></a>. <span class="delete">11 December 2012,</span><span class="insert">12 March 2013,</span> W3C <span class="delete">Candidate</span><span class="insert">Proposed</span> Recommendation. URL: <span class="delete">http://www.w3.org/TR/2012/CR-prov-n-20121211/</span><a href="http://www.w3.org/TR/2013/PR-prov-n-20130312/"><span class="insert">http://www.w3.org/TR/2013/PR-prov-n-20130312/</span></a>
-</dd><dt id="bib-PROV-O">[PROV-O]</dt><dd>Timothy Lebo; Satya Sahoo; Deborah McGuinness; eds. <a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/"><cite>PROV-O: The PROV Ontology</cite></a>. <span class="delete">11 December 2012,</span><span class="insert">12 March 2013,</span> W3C <span class="delete">Candidate</span><span class="insert">Proposed</span> Recommendation. URL: <span class="delete">http://www.w3.org/TR/2012/CR-prov-o-20121211/</span><a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/"><span class="insert">http://www.w3.org/TR/2013/PR-prov-o-20130312/</span></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 <span class="delete">Syntax.</span><span class="insert">Syntax</span></cite></a><span class="insert">.</span> 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>
-
+<section id="references" class="appendix"><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>. 12 March 2013, W3C Proposed Recommendation. URL: <span class="delete">http://www.w3.org/TR/2013/PR-prov-constraints-20130312/</span><a href="http://www.w3.org/TR/2013/REC-prov-constraints-20130430/"><span class="insert">http://www.w3.org/TR/2013/REC-prov-constraints-20130430/</span></a>
+</dd><dt id="bib-PROV-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>. 12 March 2013, W3C Proposed Recommendation. URL: <span class="delete">http://www.w3.org/TR/2013/PR-prov-n-20130312/</span><a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/"><span class="insert">http://www.w3.org/TR/2013/REC-prov-n-20130430/</span></a>
+</dd><dt id="bib-PROV-O">[PROV-O]</dt><dd>Timothy Lebo; Satya Sahoo; Deborah McGuinness; eds. <a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/"><cite>PROV-O: The PROV Ontology</cite></a>. 12 March 2013, W3C Proposed Recommendation. URL: <span class="delete">http://www.w3.org/TR/2013/PR-prov-o-20130312/</span><a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/"><span class="insert">http://www.w3.org/TR/2013/REC-prov-o-20130430/</span></a>
+</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 <span class="delete">(IRIs).</span><span class="insert">(IRIs)</span></cite></a><span class="insert">.</span> January 2005.<span class="delete"> Internet</span> RFC 3987. 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. <span class="delete">Thompson;</span><span class="insert">Thompson</span> 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: <span class="delete">Datatypes.</span><span class="insert">Datatypes</span></cite></a><span class="insert">.</span> 5 April 2012. W3C <span class="delete">Recommendation</span><span class="insert">Recommendation.</span> 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><dt id="bib-RFC3987">[RFC3987]</dt><dd>M. Dürst; M. Suignard. <a href="http://www.ietf.org/rfc/rfc3987.txt"><cite>Internationalized Resource Identifiers (IRIs)</cite></a>. January 2005. RFC 3987. URL: <a href="http://www.ietf.org/rfc/rfc3987.txt">http://www.ietf.org/rfc/rfc3987.txt</a>
+</dd><dt id="bib-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/WD-prov-aq-20130312/"><cite>Provenance Access and Query</cite></a>. <span class="delete">19 June 2012,</span><span class="insert">12 March 2013,</span> Working Draft. URL: <span class="delete">http://www.w3.org/TR/2012/WD-prov-aq-20120619/</span><a href="http://www.w3.org/TR/2013/WD-prov-aq-20130312/"><span class="insert">http://www.w3.org/TR/2013/WD-prov-aq-20130312/</span></a>
-</dd><dt id="bib-PROV-DC"><span class="insert">[PROV-DC]</span></dt><dd><span class="insert">Daniel Garijo; Kai Eckert; eds. </span><a href="http://www.w3.org/TR/2013/WD-prov-dc-20130312/"><cite><span class="insert">Dublin Core to PROV Mapping</span></cite></a><span class="insert">. 12 March 2013, Working Draft. URL: </span><a href="http://www.w3.org/TR/2013/WD-prov-dc-20130312/"><span class="insert">http://www.w3.org/TR/2013/WD-prov-dc-20130312/</span></a>
-</dd><dt id="bib-PROV-DICTIONARY"><span class="insert">[PROV-DICTIONARY]</span></dt><dd><span class="insert">Tom De Nies; Sam Coppens; eds. </span><a href="http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/"><cite><span class="insert">PROV Dictionary</span></cite></a><span class="insert">. 12 March 2013, Working Draft. URL: </span><a href="http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/"><span class="insert">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/</span></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>. 12 March 2013, Working Draft. URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-aq-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/</span></a>
+</dd><dt id="bib-PROV-DC">[PROV-DC]</dt><dd>Daniel Garijo; Kai Eckert; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/"><cite>Dublin Core to PROV Mapping</cite></a>. 12 March 2013, Working Draft. URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-dc-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/</span></a>
+</dd><dt id="bib-PROV-DICTIONARY">[PROV-DICTIONARY]</dt><dd>Tom De Nies; Sam Coppens; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><cite>PROV Dictionary</cite></a>. 12 March 2013, Working Draft. URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/</span></a>
</dd><dt id="bib-PROV-LAYOUT">[PROV-LAYOUT]</dt><dd>W3C PROV Working Group. <a href="http://www.w3.org/2011/prov/wiki/Diagrams"><cite>PROV Graph Layout Conventions</cite></a>. 2012. URL: <a href="http://www.w3.org/2011/prov/wiki/Diagrams">http://www.w3.org/2011/prov/wiki/Diagrams</a>
-</dd><dt id="bib-PROV-LINKS"><span class="insert">[PROV-LINKS]</span></dt><dd><span class="insert">Luc Moreau; Timothy Lebo; eds. </span><a href="http://www.w3.org/TR/2013/WD-prov-links-20130312/"><cite><span class="insert">Linking Across Provenance Bundles</span></cite></a><span class="insert">. 12 March 2013, Working Draft. URL: </span><a href="http://www.w3.org/TR/2013/WD-prov-links-20130312/"><span class="insert">http://www.w3.org/TR/2013/WD-prov-links-20130312/</span></a>
-</dd><dt id="bib-PROV-OVERVIEW">[PROV-OVERVIEW]</dt><dd>Paul Groth; Luc Moreau; eds. <a href="http://www.w3.org/TR/2013/WD-prov-overview-20130312/"><cite>PROV-OVERVIEW: An Overview of the PROV Family of Documents</cite></a>. <span class="delete">11 December 2012,</span><span class="insert">12 March 2013,</span> Working Draft. URL: <span class="delete">http://www.w3.org/TR/2012/WD-prov-overview-20121211/</span><a href="http://www.w3.org/TR/2013/WD-prov-overview-20130312/"><span class="insert">http://www.w3.org/TR/2013/WD-prov-overview-20130312/</span></a>
-</dd><dt id="bib-PROV-PRIMER">[PROV-PRIMER]</dt><dd>Yolanda Gil; Simon Miles; eds. <a href="http://www.w3.org/TR/2013/WD-prov-primer-20130312/"><cite>PROV Model Primer</cite></a>. <span class="delete">11 December 2012,</span><span class="insert">12 March 2013,</span> Working Draft. URL: <span class="delete">http://www.w3.org/TR/2012/WD-prov-primer-20121211/</span><a href="http://www.w3.org/TR/2013/WD-prov-primer-20130312/"><span class="insert">http://www.w3.org/TR/2013/WD-prov-primer-20130312/</span></a>
-</dd><dt id="bib-PROV-SEM"><span class="insert">[PROV-SEM]</span></dt><dd><span class="insert">James Cheney; ed. </span><a href="http://www.w3.org/TR/2013/WD-prov-sem-20130312"><cite><span class="insert">Semantics of the PROV Data Model</span></cite></a><span class="insert">. 12 March 2013, Working Draft. URL: </span><a href="http://www.w3.org/TR/2013/WD-prov-sem-20130312"><span class="insert">http://www.w3.org/TR/2013/WD-prov-sem-20130312</span></a><span class="insert">.</span>
-</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/WD-prov-xml-20130312/"><cite>PROV-XML: The PROV XML Schema</cite></a>. <span class="delete">11 December 2012,</span><span class="insert">12 March 2013,</span> Working Draft. URL: <span class="delete">http://www.w3.org/TR/2012/WD-prov-xml-20121211/</span><a href="http://www.w3.org/TR/2013/WD-prov-xml-20130312/"><span class="insert">http://www.w3.org/TR/2013/WD-prov-xml-20130312/</span></a>
+</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>. 12 March 2013, Working Draft. URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-links-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-links-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-links-20130430/</span></a>
+</dd><dt id="bib-PROV-OVERVIEW">[PROV-OVERVIEW]</dt><dd>Paul Groth; Luc Moreau; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/"><cite>PROV-OVERVIEW: An Overview of the PROV Family of Documents</cite></a>. 12 March 2013, Working Draft. URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-overview-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/</span></a>
+</dd><dt id="bib-PROV-PRIMER">[PROV-PRIMER]</dt><dd>Yolanda Gil; Simon Miles; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/"><cite>PROV Model Primer</cite></a>. 12 March 2013, Working Draft. URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-primer-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/</span></a>
+</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>. 12 March 2013, Working Draft. URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-sem-20130312</span><a href="http://www.w3.org/TR/2013/NOTE-prov-sem-20130430"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-sem-20130430</span></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>. 12 March 2013, Working Draft. URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-xml-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/</span></a>
</dd><dt 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>
-
+</dd></dl></section></section><div id="GOOGLE_INPUT_CHEXT_FLAG" style="display: none;" input="" input_stat="{}"></div></body></html>
+
--- a/model/diff/Makefile Mon Mar 25 15:24:00 2013 +0000
+++ b/model/diff/Makefile Mon Mar 25 15:26:37 2013 +0000
@@ -11,12 +11,12 @@
./htmldiff ../releases/WD-prov-n-20120724/Overview.html prov-n.html > ../diff-n.html
rel:
- ./htmldiff ../releases/CR-prov-dm-20121211/Overview.html ../releases/PR-prov-dm-20130312/Overview.html > ../diff.html
- ./htmldiff ../releases/CR-prov-n-20121211/Overview.html ../releases/PR-prov-n-20130312/Overview.html > ../diff-n.html
- ./htmldiff ../releases/CR-prov-constraints-20121211/Overview.html ../releases/PR-prov-constraints-20130312/Overview.html > ../diff-c.html
- cp ../diff.html ../releases/PR-prov-dm-20130312/
- cp ../diff-n.html ../releases/PR-prov-n-20130312/
- cp ../diff-c.html ../releases/PR-prov-constraints-20130312/
+ ./htmldiff ../releases/PR-prov-dm-20130312/Overview.html ../releases/REC-prov-dm-20130430/Overview.html > ../diff.html
+ ./htmldiff ../releases/PR-prov-n-20130312/Overview.html ../releases/REC-prov-n-20130430/Overview.html > ../diff-n.html
+ ./htmldiff ../releases/PR-prov-constraints-20130312/Overview.html ../releases/REC-prov-constraints-20130430/Overview.html > ../diff-c.html
+ cp ../diff.html ../releases/REC-prov-dm-20130430/
+ cp ../diff-n.html ../releases/REC-prov-n-20130430/
+ cp ../diff-c.html ../releases/REC-prov-constraints-20130430/
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/model/releases/REC-prov-dm-20130430/diff.html Mon Mar 25 15:26:37 2013 +0000
@@ -0,0 +1,4168 @@
+<!DOCTYPE html>
+<html lang="en" dir="ltr">
+<head><style type="text/css"><!--
+
+.insert { background-color: #aaffaa }
+.delete { background-color: #ff8888; text-decoration: line-through }
+.tagInsert { background-color: #007700; color: #ffffff }
+.tagDelete { background-color: #770000; color: #ffffff }
+
+--></style>
+<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 type="text/javascript">
+/*
+ Written by Jonathan Snook, http://www.snook.ca/jonathan
+ Add-ons by Robert Nyman, http://www.robertnyman.com
+ Author says "The credit comment is all it takes, no license. Go crazy "
+ From http://www.robertnyman.com/2005/11/07/the-ultimate-getelementsbyclassname/
+*/
+
+function getElementsByClassName(oElm, strTagName, oClassNames){
+ var arrElements = (! (! (strTagName == "*") || ! (oElm.all)))? oElm.all : oElm.getElementsByTagName(strTagName);
+ var arrReturnElements = new Array();
+ var arrRegExpClassNames = new Array();
+ if(typeof oClassNames == "object"){
+ for(var i=0; !(i>=oClassNames.length); i++){ /*>*/
+ arrRegExpClassNames.push(new RegExp("(^|\s)" + oClassNames[i].replace(/\-/g, "\-") + "(\s|$)"));
+ }
+ }
+ else{
+ arrRegExpClassNames.push(new RegExp("(^|\s)" + oClassNames.replace(/\-/g, "\-") + "(\s|$)"));
+ }
+ var oElement;
+ var bMatchesAll;
+ for(var j=0; !(j>=arrElements.length); j++){ /*>*/
+ oElement = arrElements[j];
+ bMatchesAll = true;
+ for(var k=0; !(k>=arrRegExpClassNames.length); k++){ /*>*/
+ if(!arrRegExpClassNames[k].test(oElement.className)){
+ bMatchesAll = false;
+ break;
+ }
+ }
+ if(bMatchesAll){
+ arrReturnElements.push(oElement);
+ }
+ }
+ return (arrReturnElements)
+}
+
+function set_display_by_class(el, cls, newValue) {
+ var e = getElementsByClassName(document, el, cls);
+ if (e != null) {
+ for (var i=0; !(i>=e.length); i++) {
+ e[i].style.display = newValue;
+ }
+ }
+}
+
+function set_display_by_id(id, newValue) {
+ var e = document.getElementById(id);
+ if (e != null) {
+ e.style.display = newValue;
+ }
+}
+</script>
+
+
+
+
+<style type="text/css">
+.note { font-size:small; margin-left:50px }
+
+.diamond {
+ font-weight: normal;
+ font-style: normal;
+ font-size:100%;
+ font-family: sans-serif;
+}
+
+table.thinborder {
+ border-width: 1px;
+ border-spacing: 0px;
+ border-style: none;
+ border-color: gray;
+ border-collapse: collapse;
+}
+
+table.thinborder th {
+ border-width: 1px;
+ padding: 0px;
+ border-style: solid;
+ border-color: gray;
+}
+
+table.thinborder td {
+ border-width: 1px;
+ padding: 2px;
+ border-style: solid;
+ border-color: gray;
+}
+
+/*****************************************************************
+ * ReSpec CSS
+ * Robin Berjon (robin at berjon dot com)
+ * v0.05 - 2009-07-31
+ *****************************************************************/
+
+
+/* --- 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;
+}
+
+code {
+ color: #ff4500;
+}
+
+/* --- 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;
+}
+
+
+@media screen {
+ p.practicedesc {
+ position: relative;
+ top: -2em;
+ padding: 0;
+ margin: 1.5em 0.5em -1em 1em;
+ }
+}
+
+/* --- SYNTAX HIGHLIGHTING --- */
+pre.sh_sourceCode {
+ background-color: white;
+ color: black;
+ font-style: normal;
+ font-weight: normal;
+}
+</style>
+
+<style type="text/css">
+/* --- EDITORIAL NOTES --- */
+.component1-color {
+ background-color: rgba(255,42,42,0.2);
+}
+
+.component3-color {
+ background-color: rgba(0,68,170,0.2);
+}
+
+.component2-color {
+ background-color: rgba(0,170,0,0.2);
+}
+.component4-color {
+ background-color: rgba(244,105,14,0.2);
+}
+
+.component6-color {
+ background-color: rgba(11,40,40,0.2);
+}
+
+.component5-color {
+ background-color: rgba(204,255,0,0.2);
+}
+
+.pending {
+ padding: 1em;
+ margin: 1em 0em 0em;
+ border: 1px solid #f00;
+ background: #BFEFFF;
+}
+
+.pending::before {
+ content: "Pending Review";
+ display: block;
+ width: 150px;
+ margin: -1.5em 0 0.5em 0;
+ font-weight: bold;
+ border: 1px solid #f00;
+ background: #fff;
+ padding: 3px 1em;
+}
+
+
+.resolved {
+ padding: 1em;
+ margin: 1em 0em 0em;
+ border: 1px solid #f00;
+ background: #9BCD9B;
+}
+
+.resolved::before {
+ content: "Resolved";
+ display: block;
+ width: 150px;
+ margin: -1.5em 0 0.5em 0;
+ font-weight: bold;
+ border: 1px solid #f00;
+ background: #fff;
+ padding: 3px 1em;
+}
+
+
+.inference {
+ padding: 1em;
+ margin: 1em 0em 0em;
+ border: 1px solid #f00;
+ background: #fff;
+}
+
+.inference[id]::before {
+ content: "Inference: " attr(id);
+ width: 380px; /* How can we compute the length of "Constraint: " attr(id) */
+}
+
+
+.inference::before {
+ content: "Inference";
+ display: block;
+ width: 150px;
+ margin: -1.5em 0 0.5em 0;
+ font-weight: bold;
+ border: 1px solid #f00;
+ background: #fff;
+ padding: 3px 1em;
+}
+
+.syntax {
+ padding: 1em;
+ margin: 1em 0em 0em;
+ border: 1px solid #f00;
+ background: #fff;
+}
+
+.syntax[id]::before {
+ content: "Syntax: " attr(id);
+ width: 380px; /* How can we compute the length of "Constraint: " attr(id) */
+}
+
+
+.syntax::before {
+ content: "Syntax";
+ display: block;
+ width: 150px;
+ margin: -1.5em 0 0.5em 0;
+ font-weight: bold;
+ border: 1px solid #f00;
+ background: #fff;
+ padding: 3px 1em;
+}
+
+.unamedconstraint {
+ padding: 1em;
+ margin: 1em 0em 0em;
+ border: 1px solid #00f;
+ background: #fff;
+}
+
+
+.unamedconstraint::before {
+ content: "Constraint";
+ display: block;
+ width: 150px;
+ margin: -1.5em 0 0.5em 0;
+ font-weight: bold;
+ border: 1px solid #00f;
+ background: #fff;
+ padding: 3px 1em;
+}
+
+
+
+.constraint {
+ padding: 1em;
+ margin: 1em 0em 0em;
+ border: 1px solid #00f;
+ background: #fff;
+}
+
+.constraint[id]::before {
+ content: "Constraint: " attr(id);
+ width: 380px; /* How can we compute the length of "Constraint: " attr(id) */
+}
+
+
+.constraint::before {
+ content: "Constraint";
+ display: block;
+ width: 150px;
+ margin: -1.5em 0 0.5em 0;
+ font-weight: bold;
+ border: 1px solid #00f;
+ background: #fff;
+ padding: 3px 1em;
+}
+
+
+
+.interpretation {
+ padding: 1em;
+ margin: 1em 0em 0em;
+ border: 1px solid #00f;
+ background: #fff;
+}
+
+.interpretation[id]::before {
+ content: "Interpretation: " attr(id);
+ width: 380px; /* How can we compute the length of "Interpretation: " attr(id) */
+}
+
+
+.interpretation::before {
+ content: "Interpretation";
+ display: block;
+ width: 150px;
+ margin: -1.5em 0 0.5em 0;
+ font-weight: bold;
+ border: 1px solid #00f;
+ background: #fff;
+ padding: 3px 1em;
+}
+
+.definition {
+ padding: 1em;
+ margin: 1em 0em 0em;
+ border: 1px solid #777;
+ background: #fff;
+}
+
+.definition[id]::before {
+ content: "Definition: " attr(id);
+ width: 380px;
+}
+
+
+.definition::before {
+ content: "Definition";
+ display: block;
+ width: 150px;
+ margin: -1.5em 0 0.5em 0;
+ font-weight: bold;
+ border: 1px solid #000;
+ background: #fff;
+ padding: 3px 1em;
+}
+
+
+.deprecatedconstraint {
+ padding: 1em;
+ margin: 1em 0em 0em;
+ border: 1px solid #00f;
+ background: #fff;
+}
+
+.deprecatedconstraint[id]::before {
+ content: "Deprecated: " attr(id);
+ width: 380px; /* How can we compute the length of "Deprecatedconstraint: " attr(id) */
+}
+
+
+.deprecatedconstraint::before {
+ content: "Deprecated";
+ display: block;
+ width: 150px;
+ margin: -1.5em 0 0.5em 0;
+ font-weight: bold;
+ border: 1px solid #00f;
+ background: #fff;
+ padding: 3px 1em;
+}
+
+.glossary-ref {
+ font-style: italic;
+}
+
+.dfn {
+ font-weight: bold;
+}
+
+
+.attribute {
+ font-style: italic;
+}
+
+
+.conditional {
+ color: blue;
+}
+
+.grammar {
+ margin-top: 1ex;
+ margin-bottom: 1ex;
+ padding-left: 1ex;
+ padding-right: 1ex;
+ padding-top: 1ex;
+ padding-bottom: 0.6ex;
+ border: 1px dashed #2f6fab;
+ font-size: 80%;
+}
+.nonterminal {
+ font-weight: bold;
+ font-family: sans-serif;
+ font-size: 95%;
+}
+
+.name {
+ font-family: monospace;
+}
+
+
+.xmpl {
+ padding: 1em;
+ margin: 1em 0em 0em;
+ border: 1px solid #f00;
+ background: #fff;
+}
+
+.xmpl::before {
+ content: "Example";
+ display: block;
+ width: 150px;
+ margin: -1.5em 0 0.5em 0;
+ font-weight: bold;
+ border: 1px solid #f00;
+ background: #fff;
+ padding: 3px 1em;
+}
+
+/*
+generating this through java script now.
+
+.anexample[data-count]::before {
+ content: "Example " attr(data-count) ;
+ font-family: sans-serif;
+ font-size: 1.6ex;
+ font-weight: bold;
+}
+
+
+.anexample:before {
+ content: "Example:";
+ font-family: sans-serif;
+ font-size: 1.6ex;
+ font-weight: bold;
+}
+
+*/
+
+.anexample {
+ margin-top: 1ex;
+ margin-bottom: 1ex;
+ padding-left: 1ex;
+ padding-right: 1ex;
+ padding-top: 1ex;
+ padding-bottom: 0.6ex;
+ border: 1px dashed #2f6fab;
+ background-color: #f9f9f9;
+}
+.anexample table {
+ background-color: #f9f9f9;
+}
+
+.anexampleTitle {
+ font-family: sans-serif;
+ font-size: 1.6ex;
+ font-weight: bold;
+}
+
+.anexampleTitle {
+ font-family: sans-serif;
+ font-size: 1.6ex;
+ font-weight: bold;
+}
+
+
+.diamond {
+ font-weight: normal;
+ font-size:100%;
+ font-family: sans-serif;
+}
+
+
+div[class="grammar"] span[class="name"]:before {
+ content: "'";
+}
+
+div[class="grammar"] span[class="name"]:after {
+ content: "'";
+}
+
+
+div[class="grammar"] span[class="optional"]:before {
+ font-weight: normal;
+ font-size:130%;
+ font-family: monospace;
+ content: "(";
+}
+
+div[class="grammar"] span[class="optional"]:after {
+ font-weight: normal;
+ font-size:130%;
+ font-family: monospace;
+ content: ")?";
+}
+
+
+div[class="grammar"] span[class="plus"]:before {
+ font-weight: normal;
+ font-size:130%;
+ font-family: monospace;
+ content: "(";
+}
+
+div[class="grammar"] span[class="plus"]:after {
+ font-weight: normal;
+ font-size:130%;
+ font-family: monospace;
+ content: ")+";
+}
+
+
+div[class="grammar"] span[class="star"]:before {
+ font-weight: normal;
+ font-size:130%;
+ font-family: monospace;
+ content: "(";
+}
+
+div[class="grammar"] span[class="star"]:after {
+ font-weight: normal;
+ font-size:130%;
+ font-family: monospace;
+ content: ")*";
+}
+
+div[class="grammar"] span[class="choice"]:before {
+ font-weight: normal;
+ font-size:130%;
+ font-family: monospace;
+ content: "(";
+}
+
+div[class="grammar"] span[class="choice"]:after {
+ font-weight: normal;
+ font-size:130%;
+ font-family: monospace;
+ content: ")";
+}
+
+div[class="grammar"] span[class="group"]:before {
+ font-weight: normal;
+ font-size:130%;
+ font-family: monospace;
+ content: "(";
+}
+
+div[class="grammar"] span[class="group"]:after {
+ font-weight: normal;
+ font-size:130%;
+ font-family: monospace;
+ content: ")";
+}
+
+table {
+ background-color: #f9f9f9;
+}
+
+
+.interpretation-forward::before {
+ content: "Interpretation: ";
+ font-weight: bold;
+}
+
+.structural-forward::before {
+ content: "Structural constraint: ";
+ font-weight: bold;
+}
+
+.essential {
+ font-weight: bold;
+}
+
+.provType::before {
+}
+
+.pnExpression {
+ font-weight: normal;
+ font-size:120%;
+ font-family: monospace;
+}
+
+
+</style>
+
+ <style>/*****************************************************************
+ * ReSpec 3 CSS
+ * Robin Berjon - http://berjon.com/
+ *****************************************************************/
+
+/* --- INLINES --- */
+em.rfc2119 {
+ text-transform: lowercase;
+ font-variant: small-caps;
+ font-style: normal;
+ color: #900;
+}
+
+h1 acronym, h2 acronym, h3 acronym, h4 acronym, h5 acronym, h6 acronym, a acronym,
+h1 abbr, h2 abbr, h3 abbr, h4 abbr, h5 abbr, h6 abbr, a abbr {
+ border: none;
+}
+
+dfn {
+ font-weight: bold;
+}
+
+a.internalDFN {
+ color: inherit;
+ border-bottom: 1px solid #99c;
+ text-decoration: none;
+}
+
+a.externalDFN {
+ color: inherit;
+ border-bottom: 1px dotted #ccc;
+ text-decoration: none;
+}
+
+a.bibref {
+ text-decoration: none;
+}
+
+cite .bibref {
+ font-style: normal;
+}
+
+code {
+ color: #ff4500;
+}
+
+
+/* --- --- */
+ol.algorithm { counter-reset:numsection; list-style-type: none; }
+ol.algorithm li { margin: 0.5em 0; }
+ol.algorithm li:before { font-weight: bold; counter-increment: numsection; content: counters(numsection, ".") ") "; }
+
+/* --- TOC --- */
+.toc a, .tof a {
+ text-decoration: none;
+}
+
+a .secno, a .figno {
+ color: #000;
+}
+
+ul.tof, ol.tof {
+ list-style: none outside none;
+}
+
+.caption {
+ margin-top: 0.5em;
+ font-style: italic;
+}
+
+/* --- TABLE --- */
+table.simple {
+ border-spacing: 0;
+ border-collapse: collapse;
+ border-bottom: 3px solid #005a9c;
+}
+
+.simple th {
+ background: #005a9c;
+ color: #fff;
+ padding: 3px 5px;
+ text-align: left;
+}
+
+.simple th[scope="row"] {
+ background: inherit;
+ color: inherit;
+ border-top: 1px solid #ddd;
+}
+
+.simple td {
+ padding: 3px 10px;
+ border-top: 1px solid #ddd;
+}
+
+.simple tr:nth-child(even) {
+ background: #f0f6ff;
+}
+
+/* --- DL --- */
+.section dd > p:first-child {
+ margin-top: 0;
+}
+
+.section dd > p:last-child {
+ margin-bottom: 0;
+}
+
+.section dd {
+ margin-bottom: 1em;
+}
+
+.section dl.attrs dd, .section dl.eldef dd {
+ margin-bottom: 0;
+}
+</style><link rel="stylesheet" href="https://www.w3.org/StyleSheets/TR/W3C-REC"></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="https://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> <span class="delete">Proposed </span>Recommendation <span class="delete">12 March</span><span class="insert">30 April</span> 2013</h2>
+ <dl>
+
+ <dt>This version:</dt>
+ <dd><span class="delete">http://www.w3.org/TR/2013/PR-prov-dm-20130312/</span><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/"><span class="insert">http://www.w3.org/TR/2013/REC-prov-dm-20130430/</span></a></dd>
+ <dt>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><span class="delete">http://www.w3.org/TR/2013/WD-prov-implementations-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-implementations-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-implementations-20130430/</span></a></dd>
+
+
+
+ <dt>Previous version:</dt>
+ <dd><span class="delete">http://www.w3.org/TR/2012/CR-prov-dm-20121211/</span><a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/"><span class="insert">http://www.w3.org/TR/2013/PR-prov-dm-20130312/</span></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><span class="insert">
+ The English version of this specification is the only normative version. Non-normative
+ </span><a href="http://www.w3.org/Consortium/Translation/"><span class="insert">translations</span></a><span class="insert"> may also be available.
+ </span></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 <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.
+PROV-DM is organized in six components, respectively dealing with:
+(1) entities and activities, and the time at which they were created, used, or ended;
+(2) derivations of entities from entities;
+(3) agents bearing responsibility for entities that were generated and activities that happened;
+(4) a notion of bundle, a mechanism to support provenance of provenance;
+(5) properties to link entities that refer to the same thing; and,
+(6) collections forming a logical structure for its members.
+</p>
+
+<p>This document introduces the provenance concepts found in
+PROV and defines PROV-DM types and
+relations. The PROV data model is domain-agnostic, but is equipped with
+extensibility points allowing domain-specific information to be included. </p>
+
+<p>Two further documents complete the specification of PROV-DM.
+First, a companion document specifies the set of constraints that
+provenance should follow. Second,
+a separate document describes a provenance notation for expressing
+instances of provenance for human consumption; this notation is used in examples in
+this document. </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" class="introductory"><h2>Status of This Document</h2>
+
+
+
+ <p>
+ <em>This section describes the status of this document at the time of its publication. Other
+ documents may supersede this document. A list of current <abbr title="World Wide Web Consortium">W3C</abbr> publications and the latest revision
+ of this technical report can be found in the <a href="http://www.w3.org/TR/"><abbr title="World Wide Web Consortium">W3C</abbr> technical reports
+ index</a> at http://www.w3.org/TR/.</em>
+ </p>
+
+<h4 id="prov-family-of-documents">PROV Family of Documents</h4>
+This document is part of the PROV family of documents, a set of documents defining various aspects that are necessary to achieve the vision of inter-operable
+interchange of provenance information in heterogeneous environments such as the Web. These documents are listed below. Please consult the [<cite><a class="bibref" href="#bib-PROV-OVERVIEW">PROV-OVERVIEW</a></cite>] for a guide to reading these documents.
+<ul>
+<li> <a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/">PROV-OVERVIEW</a> <span class="delete">(To be published as Note),</span><span class="insert">(Note),</span> 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> <span class="delete">(To be published as Note),</span><span class="insert">(Note),</span> 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> <span class="delete">(Proposed Recommendation),</span><span class="insert">(Recommendation),</span> the PROV ontology, an OWL2 ontology allowing the mapping of PROV to RDF [<cite><a class="bibref" href="#bib-PROV-O">PROV-O</a></cite>];</li>
+<li> <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/">PROV-DM</a> <span class="delete">(Proposed Recommendation),</span><span class="insert">(Recommendation),</span> 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> <span class="delete">(Proposed Recommendation),</span><span class="insert">(Recommendation),</span> 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> <span class="delete">(Proposed Recommendation),</span><span class="insert">(Recommendation),</span> 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> <span class="delete">(To be published as Note),</span><span class="insert">(Note),</span> 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> <span class="delete">(To be published as Note),</span><span class="insert">(Note),</span> the mechanisms for accessing and querying provenance [<cite><a class="bibref" href="#bib-PROV-AQ">PROV-AQ</a></cite>]; </li>
+<li> <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/">PROV-DICTIONARY</a> <span class="delete">(To be published as Note)</span><span class="insert">(Note)</span> introduces a specific type of collection, consisting of key-entity pairs [<cite><a class="bibref" href="#bib-PROV-DICTIONARY">PROV-DICTIONARY</a></cite>];</li>
+<li> <a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/">PROV-DC</a> <span class="delete">(To be published as Note)</span><span class="insert">(Note)</span> provides a mapping between PROV and Dublic Core Terms [<cite><a class="bibref" href="#bib-PROV-DC">PROV-DC</a></cite>];</li>
+<li> <a href="http://www.w3.org/TR/2013/NOTE-prov-sem-20130430/">PROV-SEM</a> <span class="delete">(To be published as Note),</span><span class="insert">(Note),</span> a declarative specification in terms of first-order logic of the PROV data model [<cite><a class="bibref" href="#bib-PROV-SEM">PROV-SEM</a></cite>];</li>
+<li> <a href="http://www.w3.org/TR/2013/NOTE-prov-links-20130430/">PROV-LINKS</a> <span class="delete">(To be published as Note)</span><span class="insert">(Note)</span> introduces a mechanism to link across bundles [<cite><a class="bibref" href="#bib-PROV-LINKS">PROV-LINKS</a></cite>].</li>
+</ul>
+
+<span class="delete">W3C</span><span class="delete"> Members Please Review By 09 April 2013</span>
+
+
+
+
+ <p><span class="delete">The </span><span class="delete">W3C</span><span class="delete"> Director seeks review and feedback from </span><span class="delete">W3C</span><span class="delete"> Advisory Committee representatives</span><span class="insert">
+ This document was published</span> by <span class="delete">09 April 2013. This will allow the Director</span><span class="insert">the </span><a href="http://www.w3.org/2011/prov/"><span class="insert">Provenance Working Group</span></a><span class="insert"> as a Recommendation.
+
+
+ If you wish</span> to <span class="delete">assess consensus and determine whether</span><span class="insert">make comments regarding this document, please send them</span> to<span class="delete"> issue this document as a </span><span class="delete">W3C</span><span class="delete"> Recommendation.</span>
+
+<span class="delete">Others are encouraged by the Provenance Working Group to continue to send reports of implementation experience, and other feedback, to
+</span>
+ <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>).<span class="delete"> Open discussion among developers is also welcome at
+</span><span class="delete">public-prov-comments@w3.org</span><span class="delete">
+ (</span><span class="delete">subscribe</span><span class="delete">,
+ </span><span class="delete">archives</span><span class="delete">).</span><span class="insert">
+
+
+
+
+ All comments are welcome.
+
+
+
+ </span></p>
+
+ <span class="delete">
+ This document was published by the </span><span class="delete">Provenance Working Group</span><span class="delete"> as a Proposed Recommendation.
+
+ This document is intended to become a </span><span class="delete">W3C</span><span class="delete"> Recommendation.
+
+
+
+
+
+
+ The </span><span class="delete">W3C</span><span class="delete"> Membership and other interested parties are invited
+ to review the document and send comments to
+
+ </span><span class="delete">public-prov-comments@w3.org</span><span class="delete">
+ (</span><span class="delete">subscribe</span><span class="delete">,
+ </span><span class="delete">archives</span><span class="delete">)
+ through 09 April 2013.
+ Advisory Committee Representatives should consult their
+ </span><span class="delete">WBS questionnaires</span><span class="delete">.
+ Note that substantive technical comments were expected during the Last Call review period that ended 18 September 2012.
+ </span>
+
+
+
+ <span class="delete">
+ Publication as a Proposed Recommendation does not imply endorsement by the </span><span class="delete">W3C</span><span class="delete"> Membership.
+ This is a draft document and may be updated, replaced or obsoleted by other documents at
+ any time. It is inappropriate to cite this document as other than work in progress.
+ </span>
+
+
+ <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"><span class="insert">B.1 </span></span><span class="insert">Changes since Proposed Recommendation</span></a></li><li class="tocline"><a href="#changes-since-candidate-recommendation" class="tocxref"><span class="secno"><span class="delete">B.1</span><span class="insert">B.2</span> </span>Changes since Candidate Recommendation</a></li><li class="tocline"><a href="#changes-since-last-call" class="tocxref"><span class="secno"><span class="delete">B.2</span><span class="insert">B.3</span> </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><span class="secno">1. </span>Introduction<br>
+</h2>
+
+<p>
+For the purpose of this specification, <dfn id="dfn-provenance" class="internalDFN">provenance</dfn><sup><a class="internalDFN" href="#dfn-provenance"><span class="diamond"> ◊</span></a></sup> is defined as a record that describes the people,
+institutions, entities, and activities involved in producing,
+influencing, or delivering a piece of data or a thing.
+In particular, the provenance of information is crucial in deciding
+whether information is to be trusted, how it should be integrated with
+other diverse information sources, and how to give credit to its
+originators when reusing it. In an open and inclusive environment
+such as the Web, where users find information that is often contradictory or
+questionable, provenance can help those users to make trust judgements.
+</p>
+
+
+<p>
+We present the PROV data model, PROV-DM,
+a generic data model for provenance that allows domain and application specific representations of provenance to be translated into such a data model and <em>interchanged</em> between systems.
+Thus, heterogeneous systems can export their native provenance into such a core data model, and applications that need to make sense of provenance can then import it,
+process it, and reason over it.</p>
+
+
+<p>
+The PROV data model distinguishes <em>core structures</em> from
+<em>extended structures</em>: core structures form the essence of
+provenance information, and are commonly found in various
+domain-specific vocabularies that deal
+with provenance or similar kinds of information [<cite><a class="bibref" href="#bib-Mappings">Mappings</a></cite>].
+Extended structures enhance and refine core
+structures with more expressive capabilities to cater for more
+advanced uses of provenance.
+The PROV data model, comprising both core and extended structures, is a domain-agnostic model, but with clear extensibility points allowing further domain-specific and
+application-specific extensions to be defined.
+</p>
+
+
+<p>
+The PROV data model has a modular design and is structured according to six components covering various facets of provenance:</p>
+<ul>
+<li> component 1: entities and activities, and the time at which they were created, used, or ended;
+</li><li> component 2: derivations of entities from others;
+</li><li> component 3: agents bearing responsibility for entities that were generated and activities that happened;
+</li><li> component 4: bundles, a mechanism to support provenance of provenance;
+</li><li> component 5: properties to link entities that refer to 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
+provenance types and relations, without specific concern for how they are applied.
+With these, it becomes possible to write useful provenance, and publish or embed it alongside the data it relates to. </p>
+
+<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 [<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
+ to infer.
+</p>
+
+<section id="compliance-with-this-document">
+<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>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>.
+</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.
+</li></ul>
+</section>
+
+
+<section class="informative" id="structure-of-this-document">
+<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>
+
+<p><a href="#prov-notation">Section 3</a> overviews the Provenance Notation used to illustrate examples of provenance.</p>
+
+
+<p><a href="#prov-dm-example">Section 4</a> illustrates how the PROV data model can be used
+to express the provenance of a report published on the Web.</p>
+
+
+<p><a href="#data-model-components">Section 5</a> provides the definitions of PROV concepts, structured according to six components.</p>
+
+
+
+<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 [<cite><a class="bibref" href="#bib-PROV-CONSTRAINTS">PROV-CONSTRAINTS</a></cite>].</p>
+
+
+</section>
+
+<section id="conventions">
+<h3><span class="secno">1.3 </span>Notational Conventions</h3>
+
+
+
+<p>The key words "<span class="delete">must</span><em class="rfc2119" title="MUST"><span class="insert">MUST</span></em>", "<span class="delete">must not</span><em class="rfc2119" title="MUST NOT"><span class="insert">MUST NOT</span></em>", "<span class="delete">required</span><em class="rfc2119" title="REQUIRED"><span class="insert">REQUIRED</span></em>", "<span class="delete">shall</span><em class="rfc2119" title="SHALL"><span class="insert">SHALL</span></em>", "<span class="delete">shall</span><em class="rfc2119" title="SHALL
+ NOT"><span class="insert">SHALL</span>
+ <span class="delete">not</span><span class="insert">NOT</span></em>", "<span class="delete">should</span><em class="rfc2119" title="SHOULD"><span class="insert">SHOULD</span></em>", "<span class="delete">should not</span><em class="rfc2119" title="SHOULD NOT"><span class="insert">SHOULD NOT</span></em>", "<span class="delete">recommended</span><em class="rfc2119" title="RECOMMENDED"><span class="insert">RECOMMENDED</span></em>", "<span class="delete">may</span><em class="rfc2119" title="MAY"><span class="insert">MAY</span></em>", and
+ "<span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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 [<cite><a class="bibref" href="#bib-PROV-N">PROV-N</a></cite>].</p>
+
+
+
+</section>
+
+<section class="informative" id="namespaces">
+<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.
+
+</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>
+<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>
+
+
+</section>
+
+</section>
+
+
+
+<section class="informative" id="section-prov-overview">
+<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">
+<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
+influenced in
+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" class="fig-ref">Figure 1</a>.</p>
+
+
+<div style="text-align: center; ">
+ <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.
+They are summarized in <a href="#overview-types-and-relations">Table 2</a>, where they are categorized as
+ type or relation.
+ The first column lists concepts, the second column indicates whether a concept maps to a type or a relation, whereas the third column contains the corresponding name, as it appears in Figure 1. Names of relations have a verbal form in the past tense to express what happened in the past, as opposed to what may or will happen. In the core of PROV, all relations are binary.
+</p>
+
+
+
+
+
+
+<div style="text-align: left;">
+<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>
+<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 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>
+
+
+
+
+
+
+
+
+<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">
+</p>
+</form>
+
+
+
+
+
+ <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,
+physical things such as a mountain, a building, a printed book, or a car as well as abstract concepts and ideas.
+</p>
+
+<p>
+<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"> 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:
+information processing activities
+ may for example move, copy, or duplicate digital entities;
+ physical activities can include
+ driving a car between two locations or printing a book.
+</p>
+
+
+
+<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>
+
+<p>Activities and entities are associated with each other in two different ways: activities utilize entities and activities produce entities. The act of utilizing or producing an entity may have a duration.
+ 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">
+ <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">
+ <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.
+</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).
+</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.
+This is answered by
+considering that a single artifact may
+correspond to several entities; in this case, a car in Boston may be a
+different entity from the same car in Cambridge.
+Thus, among other things,
+an entity "car in Boston" would be used, and a new entity "car in
+Cambridge" would be generated by this activity of driving. The
+provenance trace of the car might include: designed in Japan,
+manufactured in Korea, shipped to Boston USA, purchased by customer,
+driven to Cambridge, serviced by engineer in Cambridge, etc., all of
+which might be important information when deciding whether or not it
+represents a sensible second-hand purchase. Or some of it might
+alternatively be relevant when trying to determine the truth of a web
+page reporting a traffic violation involving that car. This breadth
+of provenance allows descriptions of interactions between physical and
+digital artifacts.
+</p>
+</div>
+
+
+<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">
+ <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.
+</p></div>
+
+
+
+</section>
+
+ <section id="section-derivation">
+<h4><span class="secno">2.1.2 </span>Derivation</h4>
+
+
+
+<p>Activities utilize entities and produce entities. In some cases, utilizing an entity influences the creation of another in some way. This notion of 'influence' is captured by derivations, defined as follows.
+</p>
+
+<p>
+<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="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>
+
+
+<p>
+The focus of derivation is on connecting a generated entity to a used
+entity.
+While the basic idea is simple, the concept of derivation can be quite
+subtle: implicit is the notion that the generated entity was affected
+in some way by the used entity.
+
+If an artifact
+was used by an activity that also generated a new artifact, it does not always follow
+that the second artifact was derived from the first. In the activity
+of creating a painting, an artist may have mixed some paint that was
+never actually applied to the canvas: the painting would typically
+not be considered a derivation from the unused paint.
+
+PROV does not attempt to specify the conditions under which derivations
+exist; rather, derivation is considered to have been determined by unspecified means.
+Thus, while a chain of usage and generation is necessary for a
+derivation to hold between entities, it is not sufficient; some
+form of influence occurring during the activities involved is also needed.
+</p>
+</section>
+
+
+
+<section id="section-agents-attribution-association-delegation">
+<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
+ knowing who or what <em>was reponsible</em> for its production. Data published by
+ a respected independent organization may be considered more
+ trustworthy than that from a lobby organization; a claim by a
+ well-known scientist with an established track record may be more
+ believed than a claim by a new student; a calculation performed by an
+ established software library may be more reliable than by a one-off
+ program.</p>
+
+<p>
+<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="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.
+</p>
+</div>
+
+
+
+
+<p>Agents can be related to entities, activities, and other agents.</p>
+
+<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="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>
+
+<p>
+Agents are defined as having some kind of responsibility for activities. </p>
+
+
+<p>
+<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="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:
+</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>
+</ul>
+</div>
+
+
+
+<p>
+<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="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
+student published a web page, but it may matter significantly that the department
+told the student to put up the web page.
+</p>
+</div>
+</section>
+
+
+</section>
+
+<section id="section-extended-structures">
+<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.
+The purpose of this section is twofold. First, mechanisms to specify these extended structures are introduced. Second, two further kinds of provenance structures are overviewed: they cater for provenance of provenance and collections, respectively.</p>
+
+
+
+
+<section id="section-prov-extended-mechanisms">
+<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
+identification, and new relations.</p>
+
+
+<section id="section-prov-extended-approach-subtyping">
+<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">
+ A <span class="dfn">SoftwareAgent</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"> 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">
+<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>
+
+
+
+<p>To illustrate expanded relations, we revisit the concept of
+association, introduced
+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">
+ 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"> 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
+prescriptive requirement on the nature of plans, their representation, the
+actions or steps they consist of, or their intended goals. Since plans may evolve over time,
+it may become necessary to track their provenance, so plans themselves are
+entities. Representing the plan explicitly in the provenance can be useful for various tasks: for example, to
+validate the execution as represented in the provenance record, to
+manage expectation failures, or to provide explanations.</p>
+
+
+<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).
+
+</p></div>
+</section>
+
+
+<section id="section-prov-extended-approach-optional-identification">
+<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
+some cases, mapping the concept to a relation, whether binary or
+n-ary, is not sufficient: instead, it may be required to
+identify an instance of such concept. In those cases, PROV allows for
+an optional identifier to be
+expressed to identify an instance of an association between two or
+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="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.
+</p></div>
+
+
+</section>
+
+
+
+<section id="section-prov-extended-approach-further-relations">
+<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>
+</section>
+
+
+
+<section id="section-provenance-of-provnance">
+<h4><span class="secno">2.2.2 </span>Provenance of Provenance</h4>
+
+
+
+
+<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
+generated. In other words, users need to be able to determine the provenance of provenance.
+Hence, provenance is also
+regarded as an entity (of type Bundle), by which provenance of provenance can then be
+expressed.
+</p>
+
+<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>
+</div>
+</section>
+
+<section id="section-collections">
+<h4><span class="secno">2.2.3 </span>Collections</h4>
+
+<p>
+<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="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.
+</p></div>
+
+
+</section>
+
+
+
+
+
+</section>
+
+<section id="section-overview-components">
+<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
+thematic manner. </p>
+
+<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.
+
+</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>
+<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>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>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>
+</tbody></table>
+</div>
+
+</section>
+
+</section>
+
+
+<section class="informative" id="prov-notation">
+<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 [<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
+of a name and a list of arguments in parentheses.</li>
+
+<li>The interpretation of PROV-N arguments is defined according to their <em>position</em> in the list of arguments. This convention allows for a compact notation. </li>
+
+<li>The PROV data model defines <em>identifiers</em> as qualified names; in PROV-N, they are expressed as a local name optionally preceded of a prefix and a colon. </li>
+
+
+
+<li>
+PROV-N <em>optional arguments</em> need not be specified:
+the general rule for optional arguments is that, if none of them are used in the expression, then they are simply omitted, resulting in a simpler expression. However, it may be the case that only some of the optional arguments need to be specified. Because the position of the arguments in the expression matters, in this case, an additional marker must be used to indicate that a particular term is not available. The syntactic marker '<span class="name">-</span>' is used for this purpose.
+</li>
+
+<li>Most expressions
+include an identifier
+and a set of attribute-value pairs; both are optional unless otherwise specified. By convention, the identifier occurs in the <em>first position</em>, and the set of attribute-value pairs in the <em>last position</em>.
+Consistent with the convention on arguments, the marker '<span class="name">-</span>' can be used when the identifier is not available, or can be omitted altogether with no ambiguity arising. To further disambiguate expressions that contain an optional identifier, the optional identifier or marker must be followed by '<span class="name">;</span>'.
+</li>
+</ul>
+
+<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>.
+</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)
+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)
+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)
+wasGeneratedBy(-; e2, a1)
+</pre>
+</div>
+
+
+
+</section>
+
+
+<section class="informative" id="prov-dm-example">
+<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>
+
+
+<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 <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><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>
+
+
+
+<p>In this perspective, provenance of the document
+<a href="http://www.w3.org/TR/2011/WD-prov-dm-20111215">http://www.w3.org/TR/2011/WD-prov-dm-20111215</a> is concerned with the editing activity as perceived by authors. This kind of information could be used by authors in their CV or in a narrative about this document. </p>
+
+
+
+
+<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; ">
+ <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>
+ </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>
+</li>
+
+<li>There was an editing activity.
+<pre>activity(ex:edit1, [ prov:type="edit" ])
+</pre>
+</li>
+
+<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' ])
+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" ])
+wasAssociatedWith(ex:edit1, ex:Simon, -, [ prov:role="contributor" ])
+</pre>
+</li>
+</ul>
+
+<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 [<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>
+
+<p>Entities are laid out according to the ordering of their generation. We endeavor to show time progressing from left to right. This means that edges for Usage, Generation,
+Derivation, Association typically point leftwards</p>
+
+
+
+</section>
+
+<section id="section-example-two">
+<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 <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 <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>
+<li> Both <span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111215">tr:WD-prov-dm-20111215</a></span> 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> were published by the WWW Consortium (<span class="name"><a href="http://www.w3.org/Consortium">w3:Consortium</a></span>); </li>
+<li> The publication activity for <span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111215">tr:WD-prov-dm-20111215</a></span> was <span class="name">ex:act2</span>;</li>
+<li> The publication activity for <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> was <span class="name">ex:act1</span>;
+</li>
+
+<li> The document <span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111215">tr:WD-prov-dm-20111215</a></span> was derived from <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>;</li>
+
+<li> The publication activity <span class="name">ex:act1</span> used a <a href="http://www.w3.org/2005/08/01-transitions.html#pubreq">publication request</a> (<span class="name"><a href="https://lists.w3.org/Archives/Member/w3c-archive/2011Oct/0141">email:2011Oct/0141</a></span>) and a <a href="http://www.w3.org/2005/08/01-transitions.html#transreq">transition request</a> (<span class="name"><a href="https://lists.w3.org/Archives/Member/chairs/2011OctDec/0004">chairs:2011OctDec/0004</a></span>);</li>
+<li> The publication activity <span class="name">ex:act2</span> used a <a href="http://www.w3.org/2005/08/01-transitions.html#pubreq">publication request</a> (<span class="name"><a href="https://lists.w3.org/Archives/Member/w3c-archive/2011Dec/0111">email:2011Dec/0111</a></span>);</li>
+<li> Documents were published according to the process rules (<span class="name"><a href="http://www.w3.org/2005/10/Process-20051014/tr.html#rec-advance">process:rec-advance</a></span>), a plan in PROV terminology.</li>
+</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" 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>
+ </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>
+</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" 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 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>
+</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>
+
+
+
+
+
+
+
+
+<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><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
+
+ agent(ex:Paolo, [ prov:type='prov:Person' ])
+ agent(ex:Simon, [ prov:type='prov:Person' ])
+
+
+...
+
+endBundle
+</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
+
+ agent(w3:Consortium, [ prov:type='prov:Organization' ])
+
+...
+
+endBundle
+</pre>
+
+<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>.
+
+</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' ])
+wasAttributedTo(ex:process-view, w3:Consortium)
+</pre>
+
+</section>
+
+</section>
+
+
+<section id="data-model-components">
+
+<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).
+</p>
+
+<div id="prov-dm-components-ul">
+<ul>
+<li><b>Component 1: entities and activities.</b> The first component consists of entities, activities, and concepts linking them, such as generation, usage, start, end. The first component is the only one comprising time-related concepts. </li>
+<li><b>Component 2: derivations.</b> The second component is formed with derivations and derivation subtypes.</li>
+<li><b>Component 3: agents, responsibility, and influence.</b> The third component consists of agents and concepts ascribing responsibility to agents.</li>
+<li><b>Component 4: bundles.</b> The fourth component is concerned with bundles, a mechanism to support provenance of provenance.</li>
+<li><b>Component 5: alternate.</b> The fifth component consists of relations linking entities referring to the same thing. </li>
+<li><b>Component 6: collections.</b> The sixth component is about collections. </li>
+</ul>
+</div>
+
+
+
+<div style="text-align: center;">
+<span class="figure" id="fig-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="alternate" href="#component5" coords="335,0,402,201" alt="alternate" shape="rect">
+<area title="collections" href="#component6" coords="402,0,469,201" alt="collections" shape="rect">
+<area title="activities/entities" href="#component1" coords="67,201,469,268" alt="activities/entities" shape="rect">
+<area title="bundles" href="#component4" coords="268,0,402,201" alt="bundles" shape="rect">
+</map>
+<br>
+<span class="figcaption" id="prov-dm-components">Figure 4<sup><a class="internalDFN" href="#prov-dm-components"><span class="diamond"> ◊:</span></a></sup> PROV-DM Components (Informative)</span>
+</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" 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"><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>
+<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 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" 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" 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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></em> <a title="time" href="#dfn-time" class="internalDFN">time</a> is also permitted.
+</p>
+
+
+<p>
+Some PROV-DM relations are not binary and involve extra optional element. They are summarized in <a href="#secondary-elements-relations-at-a-glance-div">Table 5</a> grouping secondary objects, according to their type. The table also adopts the same color scheme as <a href="#prov-dm-components">Figure 4</a>, allowing components to be readily identified. None of these relations correspond to the core structures introduced
+in <a href="#core-structures">Section 2.1</a>.</p>
+
+
+<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"><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>
+<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>
+
+
+<p><a href="#prov-dm-types-and-relations">Table 6</a> is a complete index of all the types and relations of PROV-DM, color-coded according to the component they belong to. In the first column, concept names link to their informal definition, whereas, in the second column, representations link to the information used to represent the concept. Concept names appearing in bold in the first column are the core structures introduced in <a href="#core-structures">Section 2.1</a>. Likewise, these core structures have their names and parameters highlighted in bold in the second column (prov-n representation); expanded structures are not represented with a bold font.</p>
+
+
+<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"><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>
+<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="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="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="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 href="#concept-organization" class="internalDFN">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 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 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>
+In the rest of the section, each type and relation is defined informally,
+ followed by a summary of the information used to represent the concept, and
+ illustrated with PROV-N examples.</p>
+
+
+<section id="component1">
+<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;">
+<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>
+</span>
+</div>
+
+
+
+
+
+ <section id="term-entity">
+
+<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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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="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>
+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>
+
+
+
+
+ </section>
+
+ <section id="term-Activity">
+
+<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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></em> time (<span class="name">st</span>) for the start of the activity;</li>
+<li><span class="attribute" id="activity.endTime">endTime</span>: an <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></em> time (<span class="name">et</span>) for the end of the activity;</li>
+<li><span class="attribute" id="activity.attributes">attributes</span>: an <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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="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,
+ [ 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>Section 5.7.2.4</span></a>).</p>
+</div>
+
+
+
+<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 [<cite><a class="bibref" href="#bib-Logic">Logic</a></cite>].
+</li>
+</ul>
+
+
+</section>
+
+<section id="term-Generation">
+<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>
+</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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></em>, at least one of them <span class="delete">must</span><em class="rfc2119" title="MUST"><span class="insert">MUST</span></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" ])
+ 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
+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="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>
+</div>
+
+
+</section>
+
+
+<section id="term-Usage">
+<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></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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></em> identifier (<span class="name">e</span>) for the entity being used;</li>
+<li><span class="attribute" id="usage.time">time</span>: an <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></em>, at least one of them <span class="delete">must</span><em class="rfc2119" title="MUST"><span class="insert">MUST</span></em> be present.</p>
+
+<p>
+A reference to a given entity <span class="delete">may</span><em class="rfc2119" title="MAY"><span class="insert">MAY</span></em> appear in multiple usages that share
+ a given activity identifier.
+</p>
+
+
+<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" ])
+ 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>
+</div>
+
+
+
+
+
+
+</section>
+
+<section id="term-Communication">
+<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>
+
+
+
+
+<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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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="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.
+</p><pre class="codeexample">activity(a1, [ prov:type="traffic regulations enforcing" ])
+activity(a2, [ prov:type="fine paying" ])
+wasInformedBy(a2, a1)
+</pre>
+The last line indicates that some implicit entity was generated by <span class="name">a1</span> and used by <span class="name">a2</span>; this entity may be a traffic ticket that had a notice of fine, amount, and payment mailing details.
+</div>
+</section>
+
+<section id="term-Start">
+<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></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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></em> identifier (<span class="name">e</span>) for the entity triggering the activity;</li>
+<li><span class="attribute" id="start.starter">starter</span>: an <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></em> time (<span class="name">t</span>) at which the activity was started; </li>
+<li><span class="attribute" id="start.attributes">attributes</span>: an <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></em>, at least one of them <span class="delete">must</span><em class="rfc2119" title="MUST"><span class="insert">MUST</span></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"] )
+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>
+<p>Alternatively, one can also describe the activity that generated the email message.</p>
+<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:
+</p><pre class="codeexample">wasStartedBy(a1, -, a0, 2011-11-16T16:05:00)
+</pre>
+</div>
+
+<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>.
+</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)
+wasAttributedTo(ex:bang, ex:Bob)
+</pre>
+</div>
+
+<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
+for instance have been the low fuel warning light, the fuel tank
+indicator needle position, or the engine not running properly.
+
+
+</p><pre class="codeexample" id="anexample-start4">activity(ex:filling-fuel)
+activity(ex:observing-low-fuel)
+
+agent(ex:driver, [ prov:type='prov:Person' )
+wasAssociatedWith(ex:filling-fuel, ex:driver)
+wasAssociatedWith(ex:observing-low-fuel, ex:driver)
+
+wasStartedBy(ex:filling-fuel, -, ex:observing-low-fuel, -)
+</pre>
+</div>
+
+<p>The relations wasStartedBy and used are orthogonal, and thus need to be expressed independently, according to the situation being described.</p>
+
+</section>
+
+<section id="term-End">
+<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></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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></em> time (<span class="name">t</span>) at which the activity was ended; </li>
+<li><span class="attribute" id="end.attributes">attributes</span>: an <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></em>, at least one of them <span class="delete">must</span><em class="rfc2119" title="MUST"><span class="insert">MUST</span></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" ])
+activity(a1, [ prov:type="Editing" ])
+wasEndedBy(a1, <span class="delete">e1)</span><span class="insert">e1, -, -)</span>
+</pre>
+</div>
+</section>
+
+<section id="term-Invalidation">
+<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>
+
+<p>
+Entities have a duration. Generation marks the beginning of an entity, whereas invalidation marks its end.
+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><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).
+</p>
+
+
+
+<p>
+</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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></em> identifier for the activity that invalidated the entity;</li>
+
+<li><span class="attribute" id="invalidation.time">time</span>: an <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></em> "invalidation time", the time at which the entity began to be invalidated;</li>
+
+<li><span class="attribute" id="invalidation.attributes">attributes</span>: an <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></em>, at least one of them <span class="delete">must</span><em class="rfc2119" title="MUST"><span class="insert">MUST</span></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>.
+
+</p><pre class="codeexample">entity(ex:The-Painter)
+agent(ex:Picasso)
+wasAttributedTo(ex:The-Painter, ex:Picasso)
+activity(ex:crash)
+wasInvalidatedBy(ex:The-Painter, ex:crash, 1998-09-03T01:31:00, [ ex:circumstances="plane accident" ])
+</pre>
+</div>
+
+<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.
+</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 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="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)
+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)
+wasAttributedTo(buy_one_beer_get_one_free_offer_during_happy_hour, proprietor)
+activity(redeemOffer)
+entity(twoBeers)
+
+wasAssociatedWith(redeemOffer, bob)
+used(redeemOffer,
+ buy_one_beer_get_one_free_offer_during_happy_hour,
+ 2012-03-10T17:15:00)
+wasInvalidatedBy(buy_one_beer_get_one_free_offer_during_happy_hour,
+ redeemOffer,
+ 2012-03-10T17:15:00)
+wasGeneratedBy(twoBeers,redeemOffer)
+</pre>
+<p>We see that the offer was both used to be converted into <span class="name">twoBeers</span> and invalidated by the <span class="name">redeemOffer</span> activity: in other words, the combined usage and invalidation indicate consumption of the offer.</p>
+</div>
+
+
+</section>
+
+
+
+
+
+</section>
+
+
+<section id="component2">
+<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 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;">
+<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>
+</span>
+</div>
+
+<section id="term-Derivation">
+<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>
+
+
+
+
+<p>According to <a href="#section-prov-overview">Section 2</a>, for an entity to be transformed from, created from, or resulting from an update to another, there must be some
+underpinning activity or activities performing the necessary action(s) resulting in such a derivation.
+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></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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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="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)
+wasDerivedFrom(e2, e1, [ prov:type="physical transform" ])
+</pre>
+<p>The following description expresses that activity <span class="name">a</span>,
+using the entity <span class="name">e1</span> according to usage <span class="name">u1</span>,
+ 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)
+wasGeneratedBy(g2; e2, a, -)
+used(u1; a, e1, -)
+</pre>
+<p>With such a comprehensive description of derivation, a program that analyzes provenance can identify the activity underpinning the derivation, it can identify how the preceding entity <span class="name">e1</span> was used by the activity (e.g. for instance, which argument it was passed as, if the activity is the result of a function invocation), and which output the derived entity <span class="name">e2</span> was obtained from (say, for a function returning multiple results).</p>
+</div>
+
+
+
+
+</section>
+
+<section id="term-revision">
+<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 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" 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="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>.
+</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,
+ [ prov:type='prov:Revision' ])
+</pre>
+</div>
+
+
+
+</section>
+
+<section id="term-quotation">
+<h4><span class="secno">5.2.3 </span>Quotation</h4>
+
+<p>
+<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 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" 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="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>.
+</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/)
+entity(dm:bl-dagstuhl)
+agent(ex:Luc)
+agent(ex:Paul)
+wasDerivedFrom(dm:bl-dagstuhl,
+ wp:thoughts-from-the-dagstuhl-principles-of-provenance-workshop/,
+ [ prov:type='prov:Quotation' ])
+wasAttributedTo(dm:bl-dagstuhl, ex:Luc)
+wasAttributedTo(wp:thoughts-from-the-dagstuhl-principles-of-provenance-workshop/, ex:Paul)
+</pre>
+
+</div>
+
+
+</section>
+
+
+<section id="term-primary-source">
+<h4><span class="secno">5.2.4 </span>Primary Source</h4>
+
+<p>
+<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
+of <a href="http://en.wikipedia.org/wiki/Primary_source">primary
+sources</a>, they "speak for themselves" in ways that cannot be
+captured through the filter of secondary sources. As such, it is
+important for secondary sources to reference those primary sources
+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 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" 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="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,
+Minard probably used the journal of Pierre-Irénée Jacob, pharmacist
+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" ])
+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,
+ [ prov:type='prov:PrimarySource' ])
+</pre>
+</div>
+
+
+
+</section>
+
+
+</section>
+
+<section id="component3">
+<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>), 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">SofwareAgent</a>, and <a 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;">
+<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>
+</span>
+</div>
+
+<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;">
+<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>
+</span>
+</div>
+
+<section id="term-agent">
+<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></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>
+</ul></div>
+
+
+<p>
+
+It is useful to define some basic categories of agents from an interoperability perspective.
+There are three types of agents that are common across most anticipated domains of use; it is acknowledged that these types do not cover all kinds of agent. </p>
+<ul>
+<li><span class="name">SoftwareAgent</span>
+
+<p><span class="glossary-ref"> A <dfn id="concept-software-agent" title="software-agent" class="internalDFN">SoftwareAgent</dfn><sup><a class="internalDFN" href="#concept-software-agent"><span class="diamond"> ◊</span></a></sup> is running software. </span> The type of a SoftwareAgent is denoted by <dfn title="dfn-prov:softwareAgent" id="dfn-prov:softwareAgent" class="internalDFN"><span class="name">prov:SoftareAgent</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"> Agents of type <dfn id="concept-organization" class="internalDFN">Organization</dfn><sup><a class="internalDFN" href="#concept-organization"><span class="diamond"> ◊</span></a></sup> are social or legal institutions such as companies, societies, 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"> Agents of type <dfn id="concept-person" title="Person" class="internalDFN">Person</dfn><sup><a class="internalDFN" href="#concept-person"><span class="diamond"> ◊</span></a></sup> 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>
+
+
+
+
+<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>
+<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>
+
+</section>
+
+<section id="term-attribution">
+<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></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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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="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>Section 4.1</span></a>,
+we can ascribe <span class="name">tr:WD-prov-dm-20111215</span> to some agents without an explicit activity.
+</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" ])
+wasAttributedTo(tr:WD-prov-dm-20111215, ex:Simon, [ prov:type="authorship" ])
+</pre>
+</div>
+
+</section>
+
+
+<section id="term-Association">
+<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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></em>, at least one of them <span class="delete">must</span><em class="rfc2119" title="MUST"><span class="insert">MUST</span></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>
+
+
+
+
+
+<p>PROV defines no plan-specific attributes.</p>
+
+
+<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" ])
+wasAssociatedWith(ex:a, ex:ag2, ex:wf, [ prov:role="designer", ex:context="project1" ])
+entity(ex:wf, [ prov:type='prov:Plan' ,
+ ex:label="Workflow 1",
+ prov:location="http://example.org/workflow1.bpel" %% xsd:anyURI ])
+</pre>
+Since the workflow <span class="name">ex:wf</span> is itself an entity, its provenance can also be expressed in PROV: it can be generated by some activity and derived from other entities,
+for instance.
+</div>
+
+<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" ])
+wasAssociatedWith(ex:a, -, ex:wf)
+entity(ex:wf, [ prov:type='prov:Plan',
+ ex:label="Workflow 1",
+ ex:url="http://example.org/workflow1.bpel" %% xsd:anyURI])
+</pre>
+In this case, it is assumed that an agent exists, but it has not been specified.
+</div>
+
+
+
+
+</section>
+
+<section id="term-delegation">
+
+<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
+department chair, who acted on behalf of the university; all those
+agents are responsible in some way for the activity that took place but
+we do not say explicitly who bears responsibility and to what
+degree. </p>
+
+
+<p>
+</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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></em> set (<span class="name">attrs</span>) of attribute-value pairs representing additional information about this delegation link.</li>
+</ul></div>
+
+
+<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" ])
+agent(ag1, [ prov:type="programmer" ])
+agent(ag2, [ prov:type="researcher" ])
+agent(ag3, [ prov:type="funder" ])
+wasAssociatedWith(a, ag1, [ prov:role="loggedInUser" ])
+wasAssociatedWith(a, ag2)
+wasAssociatedWith(a, ag3)
+actedOnBehalfOf(ag1, ag2, a, [ prov:type="line-management" ])
+actedOnBehalfOf(ag2, ag3, a, [ prov:type="contract" ])
+</pre>
+</div>
+
+
+
+</section>
+
+<section id="term-influence">
+<h4><span class="secno">5.3.5 </span>Influence</h4>
+
+<p>
+<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>
+
+
+<p> An influence relation between two objects <span class="name">o2</span> and <span class="name">o1</span> is a generic dependency of <span class="name">o2</span>
+on <span class="name">o1</span> that signifies some form of influence of <span class="name">o1</span> on <span class="name">o2</span>.</p>
+
+
+<p>
+</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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></em> set (<span class="name">attrs</span>) of attribute-value pairs representing additional information about this relation.</li>
+</ul></div>
+
+<p>
+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 <span class="delete">recommended</span><em class="rfc2119" title="RECOMMENDED"><span class="insert">RECOMMENDED</span></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 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>
+<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 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 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 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"><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>.
+</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>
+</div>
+
+
+
+
+</section>
+
+
+</section>
+
+
+
+<section id="component4">
+<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 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;">
+<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">
+
+<h4><span class="secno">5.4.1 </span>Bundle constructor</h4>
+
+
+<p>
+<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>
+</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">
+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>
+</div>
+
+<p>There may be other kinds of bundles not directly expressible by this constructor, such as provenance descriptions handwritten on a letter or a whiteboard, etc. Whatever the means by which bundles are expressed, all can be described, as in the following section.</p>
+</section>
+
+
+
+
+
+<section id="term-bundle-entity">
+
+<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" 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" 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,
+ a type <span>prov:Bundle</span> and
+an <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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 40</span></a>
+and
+<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 ])
+wasGeneratedBy(ex:report1, -, 2012-05-24T10:00:01)
+entity(ex:report2, [ prov:type="report", ex:version=2])
+wasGeneratedBy(ex:report2, -, 2012-05-25T11:00:01)
+wasDerivedFrom(ex:report2, ex:report1)
+</pre>
+
+<p>Let us assume that Bob observed the creation of <span class="name">ex:report1</span>.
+A first bundle can be expressed.</p>
+<pre class="codeexample">
+bundle bob:bundle1
+ entity(ex:report1, [ prov:type="report", ex:version=1 ])
+ wasGeneratedBy(ex:report1, -, 2012-05-24T10:00:01)
+endBundle
+</pre>
+
+<p>In contrast,
+Alice observed the creation of <span class="name">ex:report2</span> and its derivation from <span class="name">ex:report1</span>.
+A separate bundle can also be expressed.</p>
+<pre class="codeexample">
+bundle alice:bundle2
+ entity(ex:report1)
+ entity(ex:report2, [ prov:type="report", ex:version=2 ])
+ wasGeneratedBy(ex:report2, -, 2012-05-25T11:00:01)
+ wasDerivedFrom(ex:report2, ex:report1)
+endBundle
+</pre>
+
+<p>The first bundle contains the descriptions corresponding to Bob observing the creation of <span class="name">ex:report1</span>. Its provenance can be described as follows.</p>
+<pre class="codeexample">
+entity(bob:bundle1, [ prov:type='prov:Bundle' ])
+wasGeneratedBy(bob:bundle1, -, 2012-05-24T10:30:00)
+wasAttributedTo(bob:bundle1, ex:Bob)
+</pre>
+
+<p>In contrast, the second bundle is attributed to Alice who
+observed the derivation of <span class="name">ex:report2</span> from <span class="name">ex:report1</span>.</p>
+<pre class="codeexample">
+entity(alice:bundle2, [ prov:type='prov:Bundle' ])
+wasGeneratedBy(alice:bundle2, -, 2012-05-25T11:15:00)
+wasAttributedTo(alice:bundle2, ex:Alice)
+</pre>
+</div>
+
+<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
+ entity(ex:report1, [ prov:type="report", ex:version=1 ])
+ wasGeneratedBy(ex:report1, -, 2012-05-24T10:00:01)
+
+ entity(ex:report2, [ prov:type="report", ex:version=2 ])
+ wasGeneratedBy(ex:report2, -, 2012-05-25T11:00:01)
+ wasDerivedFrom(ex:report2, ex:report1)
+endBundle
+
+entity(agg:bundle3, [ prov:type='prov:Bundle' ])
+agent(ex:aggregator01, [ prov:type='ex:Aggregator' ])
+wasAttributedTo(agg:bundle3, ex:aggregator01)
+wasDerivedFrom(agg:bundle3, bob:bundle1)
+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.
+</p></div>
+
+
+</section>
+
+
+</section>
+
+
+<section id="component5">
+<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" 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;">
+<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="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>
+The PROV data model introduces relations, called specialization and alternate
+that allow entities to be linked together. They are defined as follows. </p>
+
+
+<section id="term-specialization">
+
+<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>
+Examples of aspects include a time period, an abstraction, and a context associated with the entity.</p>
+
+
+
+
+<p>
+</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>)
+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>
+</ul>
+</div>
+
+<p>A specialization is not, as defined here, also an influence, and therefore does not have an id and attributes.</p>
+
+
+
+<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.
+</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>
+
+
+
+
+
+
+
+</section>
+
+<section id="term-alternate">
+
+<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>
+</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" 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" 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="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,
+ [ prov:type="a news item for desktop"])
+entity(bbc:news/mobile/science-environment-17526723,
+ [ prov:type="a news item for mobile devices"])
+alternateOf(bbc:news/science-environment-17526723,
+ bbc:news/mobile/science-environment-17526723)
+</pre>
+</div>
+
+
+<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.
+</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>
+</div>
+
+</section>
+</section>
+
+
+
+<section id="component6">
+<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 href="#concept-membership" class="internalDFN">Membership</a>).
+</p>
+
+
+<div style="text-align: center;">
+<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">
+<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" 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" 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>
+
+
+</section>
+
+<section id="term-membership">
+<h4><span class="secno">5.6.2 </span>Membership</h4>
+
+<p>A <strong>membership</strong> relation is defined the members of a Collection to be stated. </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>
+</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>
+</ul>
+</div>
+
+
+<p>Membership is not, as defined here, also an influence, and therefore does not have an id and attributes.</p>
+
+
+<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)
+entity(e1)
+entity(e2)
+
+entity(c, [prov:type='prov:Collection' ]) // c is a collection, with unknown content
+hadMember(c, e0)
+hadMember(c, e1)
+hadMember(c, e2)
+</pre>
+</div>
+
+
+</section>
+
+
+
+
+</section>
+
+
+
+
+
+<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.
+
+
+
+
+<section id="term-identifier">
+<h4><span class="secno">5.7.1 </span>Identifier</h4>
+
+<p>
+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 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><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"><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>
+<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>
+
+
+
+
+
+<section id="term-attribute-label">
+<h5><span class="secno">5.7.2.1 </span>prov:label</h5>
+
+
+<p>
+<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> <span class="delete">must</span><em class="rfc2119" title="MUST"><span class="insert">MUST</span></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>
+
+<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>
+</div>
+</section>
+
+
+<section id="term-attribute-location">
+<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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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> <span class="delete">must</span><em class="rfc2119" title="MUST"><span class="insert">MUST</span></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="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>
+<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>
+</div>
+</section>
+
+
+
+<section id="term-attribute-role">
+<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 <span class="delete">must</span><em class="rfc2119" title="MUST"><span class="insert">MUST</span></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>
+<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>
+</div>
+</section>
+
+<section id="term-attribute-type">
+<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 <span class="delete">must</span><em class="rfc2119" title="MUST"><span class="insert">MUST</span></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" 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>
+</div>
+
+<p>The following types are pre-defined in PROV, and are valid values for the <span class="name">prov:type</span> attribute.</p>
+
+
+<table class="thinborder" style="margin-left: auto; margin-right: auto;">
+<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>
+<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" 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">
+<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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></em> attribute of entity. The value associated with the attribute <span class="name">prov:value</span> <span class="delete">must</span><em class="rfc2119" title="MUST"><span class="insert">MUST</span></em> be a PROV-DM <a title="value" href="#concept-value" class="internalDFN">Value</a>. The attribute <span class="name">prov:value</span> <span class="delete">may</span><em class="rfc2119" title="MAY"><span class="insert">MAY</span></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" ])
+entity(ex:out, [ prov:value=4 ])
+activity(ex:len, [ prov:type="string-length" ])
+used(ex:len, ex:in)
+wasGeneratedBy(ex:out, ex:len)
+wasDerivedFrom(ex:out, ex:in)
+</pre>
+</div>
+
+<p>
+Two different entities <span class="delete">may</span><em class="rfc2119" title="MAY"><span class="insert">MAY</span></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"><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 ])
+entity(ex:in2, [ prov:value=1 ])
+entity(ex:out2, [ prov:value=4 ]) // ex:out2 also has value 4
+activity(ex:add1, [ prov:type="addition" ])
+used(ex:add1, ex:in1)
+used(ex:add1, ex:in2)
+wasGeneratedBy(ex:out2, ex:add1)
+</pre>
+</div>
+
+
+</section>
+
+
+
+</section>
+
+<section id="term-value">
+<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 <span class="delete">recommended</span><em class="rfc2119" title="RECOMMENDED"><span class="insert">RECOMMENDED</span></em>. </p>
+<ul>
+<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>
+The normative definitions of these datatypes are provided by their respective specifications.
+</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 <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><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 [<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>
+</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".
+</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> [<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>
+Alternatively, the same value can be expressed using the following convenience notation.
+<pre class="codeexample">
+ 'ex:value'
+</pre>
+</div>
+
+<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> [<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>
+</div>
+
+</section>
+
+<section id="term-NamespaceDeclaration">
+<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" 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" 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><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 <span class="delete">namespace</span><span class="delete">,</span><span class="insert">namespace,</span> 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 <span class="delete">optional</span><em class="rfc2119" title="OPTIONAL"><span class="insert">OPTIONAL</span></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>
+
+</section>
+
+
+
+</section>
+
+
+
+
+ <section id="extensibility-section">
+<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" 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="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.
+</p><pre class="codeexample">
+ wasDerivedFrom(e2,e1, [prov:type='ex:Translation' ])
+</pre>
+</div>
+
+<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.
+</p><pre class="codeexample">
+ entity(e, [prov:type='ex:Car' ])
+</pre>
+</div>
+
+
+
+
+</li>
+
+<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="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.
+</p><pre class="codeexample">
+ activity(ex:work)
+ entity(ex:laptop4)
+ entity(ex:desktop9)
+ used(ex:work, ex:laptop4, [prov:role="day-to-day machine"])
+ used(ex:work, ex:desktop9, [prov:role="backup machine"])
+</pre>
+</div>
+</li>
+
+
+<li> Attribute-value lists occur in all types and most relations of the data model. Applications designers are free to introduce further application-specific attributes. Attributes for a given application can be distinguished by qualifying them with a prefix denoting a namespace
+declared in a namespace declaration. New namespaces and associated prefixes can be declared, allowing attributes and names to be qualified.
+</li>
+
+
+
+</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 [<cite><a class="bibref" href="#bib-PROV-CONSTRAINTS">PROV-CONSTRAINTS</a></cite>]. </p>
+
+
+
+ </section>
+
+
+
+<section id="valid-provenance">
+<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,
+involved in producing, influencing, or delivering a piece of data or a
+thing to be expressed. However, with this data model, it is also possible to compose
+descriptions that would not make sense: for instance, one could
+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 [<cite><a class="bibref" href="#bib-PROV-CONSTRAINTS">PROV-CONSTRAINTS</a></cite>].
+They <span class="delete">should</span><em class="rfc2119" title="SHOULD"><span class="insert">SHOULD</span></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>
+
+
+
+
+<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 [<cite><a class="bibref" href="#bib-PROV-CONSTRAINTS">PROV-CONSTRAINTS</a></cite>].</p>
+
+
+
+</section>
+
+
+
+<section class="appendix" id="cross-references-to-prov-o-and-prov-n">
+<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 [<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"><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>
+<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" 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" 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" 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" 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" 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" 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" 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" 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>
+<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="component2-color">
+<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>
+</tr>
+
+<tr class="component2-color">
+<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" 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" 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>
+<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="component3-color" style="border-collapse: collapse; ">
+<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>
+</tr>
+
+<tr class="component3-color">
+<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" 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" 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" 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" 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>
+
+<tr class="component3-color">
+<td><a title="Organization" href="#concept-organization" class="internalDFN">Organization</a></td>
+<td><a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/#Organization">Organization</a></td>
+<td>type <code><a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/#provn-type-Organization">Organization</a></code></td>
+</tr>
+
+<tr class="component3-color">
+<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" 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>
+
+<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="component4-color">
+<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>
+</tr>
+
+<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>
+
+<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="component5-color">
+<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>
+</tr>
+
+<tr class="component5-color">
+<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>
+
+<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="component6-color">
+<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>
+</tr>
+
+<tr class="component6-color">
+<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" 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>
+</tbody></table>
+</div>
+</section>
+
+<section class="appendix" id="change-log">
+ <h2><span class="secno">B. </span>Change Log</h2>
+
+<section id="changes-since-proposed-recommendation">
+ <h3><span class="secno"><span class="insert">B.1 </span></span><span class="insert">Changes since Proposed Recommendation</span></h3>
+<ul>
+<li><span class="insert"> Changed the status of this document section.
+</span></li><li><span class="insert"> Changed all URLs to PROV documents.
+</span></li><li> <a href="http://www.w3.org/2011/prov/track/issues/653"><span class="insert">ISSUE-653</span></a><span class="insert">: Fixed typo in example to ensure compatibility with prov-n grammar.
+</span></li></ul>
+
+</section>
+<section id="changes-since-candidate-recommendation">
+ <h3><span class="secno"><span class="delete">B.1</span><span class="insert">B.2</span> </span>Changes since Candidate Recommendation</h3>
+
+<ul>
+<li> Checked all internal fragments resolved.
+</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 id="changes-since-last-call">
+ <h3><span class="secno"><span class="delete">B.2</span><span class="insert">B.3</span> </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><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><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><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" id="acknowledgements">
+ <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 (<abbr title="World Wide Web Consortium">W3C</abbr>/<abbr title="Massachusetts Institute of Technology">MIT</abbr>) and Ivan Herman (<abbr title="World Wide Web Consortium">W3C</abbr>/<abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr>), <abbr title="World Wide Web Consortium">W3C</abbr> contacts for the Provenance Working Group.
+ </p>
+
+<p>
+The editors acknowledge valuable contributions from the following:
+Tom Baker,
+David Booth,
+Robert Freimuth,
+Satrajit Ghosh,
+Ralph Hodgson,
+Renato Iannella,
+Jacek Kopecky,
+James Leigh,
+Jacco van Ossenbruggen,
+Alan Ruttenberg,
+Reza Samavi, and
+Antoine Zimmermann.
+</p>
+
+<p>
+Members of the Provenance Working Group at the time of publication of this document were:
+
+Ilkay Altintas (Invited expert),
+Reza B'Far (Oracle Corporation),
+Khalid Belhajjame (University of Manchester),
+James Cheney (University of Edinburgh, School of Informatics),
+Sam Coppens (iMinds - Ghent University),
+David Corsar (University of Aberdeen, Computing Science),
+Stephen Cresswell (The National Archives),
+Tom De Nies (iMinds - Ghent University),
+Helena Deus (DERI Galway at the National University of Ireland, Galway, Ireland),
+Simon Dobson (Invited expert),
+Martin Doerr (Foundation for Research and Technology - Hellas(FORTH)),
+Kai Eckert (Invited expert),
+Jean-Pierre EVAIN (European Broadcasting Union, EBU-UER),
+James Frew (Invited expert),
+Irini Fundulaki (Foundation for Research and Technology - Hellas(FORTH)),
+Daniel Garijo (Universidad Politécnica de Madrid),
+Yolanda Gil (Invited expert),
+Ryan Golden (Oracle Corporation),
+Paul Groth (Vrije Universiteit),
+Olaf Hartig (Invited expert),
+David Hau (National Cancer Institute, NCI),
+Sandro Hawke (<abbr title="World Wide Web Consortium">W3C</abbr>/<abbr title="Massachusetts Institute of Technology">MIT</abbr>),
+Jörn Hees (German Research Center for Artificial Intelligence (DFKI) Gmbh),
+Ivan Herman, (<abbr title="World Wide Web Consortium">W3C</abbr>/<abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr>),
+Ralph Hodgson (TopQuadrant),
+Hook Hua (Invited expert),
+Trung Dong Huynh (University of Southampton),
+Graham Klyne (University of Oxford),
+Michael Lang (Revelytix, Inc.),
+Timothy Lebo (Rensselaer Polytechnic Institute),
+James McCusker (Rensselaer Polytechnic Institute),
+Deborah McGuinness (Rensselaer Polytechnic Institute),
+Simon Miles (Invited expert),
+Paolo Missier (School of Computing Science, Newcastle university),
+Luc Moreau (University of Southampton),
+James Myers (Rensselaer Polytechnic Institute),
+Vinh Nguyen (Wright State University),
+Edoardo Pignotti (University of Aberdeen, Computing Science),
+Paulo da Silva Pinheiro (Rensselaer Polytechnic Institute),
+Carl Reed (Open Geospatial Consortium),
+Adam Retter (Invited Expert),
+Christine Runnegar (Invited expert),
+Satya Sahoo (Invited expert),
+David Schaengold (Revelytix, Inc.),
+Daniel Schutzer (FSTC, Financial Services Technology Consortium),
+Yogesh Simmhan (Invited expert),
+Stian Soiland-Reyes (University of Manchester),
+Eric Stephan (Pacific Northwest National Laboratory),
+Linda Stewart (The National Archives),
+Ed Summers (Library of Congress),
+Maria Theodoridou (Foundation for Research and Technology - Hellas(FORTH)),
+Ted Thibodeau (OpenLink Software Inc.),
+Curt Tilmes (National Aeronautics and Space Administration),
+Craig Trim (IBM Corporation),
+Stephan Zednik (Rensselaer Polytechnic Institute),
+Jun Zhao (University of Oxford),
+Yuting Zhao (University of Aberdeen, Computing Science).
+</p>
+ </section>
+
+
+
+
+<section id="references" class="appendix"><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>. 12 March 2013, W3C Proposed Recommendation. URL: <span class="delete">http://www.w3.org/TR/2013/PR-prov-constraints-20130312/</span><a href="http://www.w3.org/TR/2013/REC-prov-constraints-20130430/"><span class="insert">http://www.w3.org/TR/2013/REC-prov-constraints-20130430/</span></a>
+</dd><dt id="bib-PROV-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>. 12 March 2013, W3C Proposed Recommendation. URL: <span class="delete">http://www.w3.org/TR/2013/PR-prov-n-20130312/</span><a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/"><span class="insert">http://www.w3.org/TR/2013/REC-prov-n-20130430/</span></a>
+</dd><dt id="bib-PROV-O">[PROV-O]</dt><dd>Timothy Lebo; Satya Sahoo; Deborah McGuinness; eds. <a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/"><cite>PROV-O: The PROV Ontology</cite></a>. 12 March 2013, W3C Proposed Recommendation. URL: <span class="delete">http://www.w3.org/TR/2013/PR-prov-o-20130312/</span><a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/"><span class="insert">http://www.w3.org/TR/2013/REC-prov-o-20130430/</span></a>
+</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)</cite></a>. January 2005. RFC 3987. URL: <a href="http://www.ietf.org/rfc/rfc3987.txt">http://www.ietf.org/rfc/rfc3987.txt</a>
+</dd><dt id="bib-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>. 12 March 2013, Working Draft. URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-aq-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/</span></a>
+</dd><dt id="bib-PROV-DC">[PROV-DC]</dt><dd>Daniel Garijo; Kai Eckert; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/"><cite>Dublin Core to PROV Mapping</cite></a>. 12 March 2013, Working Draft. URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-dc-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/</span></a>
+</dd><dt id="bib-PROV-DICTIONARY">[PROV-DICTIONARY]</dt><dd>Tom De Nies; Sam Coppens; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><cite>PROV Dictionary</cite></a>. 12 March 2013, Working Draft. URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/</span></a>
+</dd><dt id="bib-PROV-LAYOUT">[PROV-LAYOUT]</dt><dd>W3C PROV Working Group. <a href="http://www.w3.org/2011/prov/wiki/Diagrams"><cite>PROV Graph Layout Conventions</cite></a>. 2012. URL: <a href="http://www.w3.org/2011/prov/wiki/Diagrams">http://www.w3.org/2011/prov/wiki/Diagrams</a>
+</dd><dt id="bib-PROV-LINKS">[PROV-LINKS]</dt><dd>Luc Moreau; Timothy Lebo; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-links-20130430/"><cite>Linking Across Provenance Bundles</cite></a>. 12 March 2013, Working Draft. URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-links-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-links-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-links-20130430/</span></a>
+</dd><dt id="bib-PROV-OVERVIEW">[PROV-OVERVIEW]</dt><dd>Paul Groth; Luc Moreau; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/"><cite>PROV-OVERVIEW: An Overview of the PROV Family of Documents</cite></a>. 12 March 2013, Working Draft. URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-overview-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/</span></a>
+</dd><dt id="bib-PROV-PRIMER">[PROV-PRIMER]</dt><dd>Yolanda Gil; Simon Miles; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/"><cite>PROV Model Primer</cite></a>. 12 March 2013, Working Draft. URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-primer-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/</span></a>
+</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>. 12 March 2013, Working Draft. URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-sem-20130312</span><a href="http://www.w3.org/TR/2013/NOTE-prov-sem-20130430"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-sem-20130430</span></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>. 12 March 2013, Working Draft. URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-xml-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/</span></a>
+</dd><dt 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><div id="GOOGLE_INPUT_CHEXT_FLAG" style="display: none;" input="" input_stat="{}"></div></body></html>
+