--- a/model/ProvenanceModel.html Mon Jul 18 23:34:31 2011 +0100
+++ b/model/ProvenanceModel.html Mon Jul 18 23:36:51 2011 +0100
@@ -1,110 +1,520 @@
<!DOCTYPE html>
-<html><head>
+<!-- saved from url=(0032)file:///tmp/ProvenanceModel.html -->
+<html lang="en" dir="ltr"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Provenance Model</title>
- <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+
<!--
=== NOTA BENE ===
For the three scripts below, if your spec resides on dev.w3 you can check them
out in the same tree and use relative links so that they'll work offline,
- -->
- <script src="http://dev.w3.org/2009/dap/ReSpec.js/js/respec.js" class="remove"></script>
- <script class="remove">
- var respecConfig = {
- // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
- specStatus: "ED",
-
- // the specification's short name, as in http://www.w3.org/TR/short-name/
- shortName: "PIL-Model",
-
- // if your specification has a subtitle that goes below the main
- // formal title, define it here
- subtitle : "Initial draft for internal discussion",
-
- // if you wish the publication date to be other than today, set this
- // publishDate: "2009-08-06",
-
- // if the specification's copyright date is a range of years, specify
- // the start date here:
- // copyrightStart: "2005"
-
- // if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
- // and its maturity status
- // previousPublishDate: "1977-03-15",
- // previousMaturity: "WD",
-
- // if there a publicly available Editor's Draft, this is the link
- edDraftURI: "http://www.w3.org/2011/prov/wiki/D1--NOT-YET-AVAILABLE",
-
- // if this is a LCWD, uncomment and set the end of its review period
- // lcEnd: "2009-08-05",
-
- // if you want to have extra CSS, append them to this list
- // it is recommended that the respec.css stylesheet be kept
- extraCSS: ["http://dev.w3.org/2009/dap/ReSpec.js/css/respec.css"],
-
- // editors, add as many as you like
- // only "name" is required
- editors: [
- { name: "Luc Moreau", url: "http://www.ecs.soton.ac.uk/~lavm",
- company: "University of Southampton, UK" },
- { name: "Paolo Missier", url: "http://www.cs.ncl.ac.uk/people/Paolo.Missier",
- company: "Newcastle University, UK" },
- ],
-
- // authors, add as many as you like.
- // This is optional, uncomment if you have authors as well as editors.
- // only "name" is required. Same format as editors.
-
- authors: [
- { name: "TBD"},
- ],
-
- // name of the WG
- wg: "Provenance Working Group",
-
- // URI of the public WG page
- wgURI: "http://www.w3.org/2011/prov/wiki/Main_Page",
-
- // name (with the @w3c.org) of the public mailing to which comments are due
- wgPublicList: "public-prov-wg",
-
- // URI of the patent status for this WG, for Rec-track documents
- // !!!! IMPORTANT !!!!
- // This is important for Rec-track documents, do not copy a patent URI from a random
- // document unless you know what you're doing. If in doubt ask your friendly neighbourhood
- // Team Contact.
- wgPatentURI: "",
- };
- </script>
- </head>
- <body>
- <section id="abstract">
+ -->
+<!-- PM -->
+ <style type="text/css">
+ .note { font-size:small; margin-left:50px }
+ </style>
+
+
+
+ <style type="text/css">
+/*****************************************************************
+ * 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;
+}
+
+
+/* --- WEB IDL --- */
+pre.idl {
+ border-top: 1px solid #90b8de;
+ border-bottom: 1px solid #90b8de;
+ padding: 1em;
+ line-height: 120%;
+}
+
+pre.idl::before {
+ content: "WebIDL";
+ display: block;
+ width: 150px;
+ background: #90b8de;
+ color: #fff;
+ font-family: initial;
+ padding: 3px;
+ font-weight: bold;
+ margin: -1em 0 1em -1em;
+}
+
+.idlType {
+ color: #ff4500;
+ font-weight: bold;
+ text-decoration: none;
+}
+
+/*.idlModule*/
+/*.idlModuleID*/
+/*.idlInterface*/
+.idlInterfaceID {
+ font-weight: bold;
+ color: #005a9c;
+}
+
+.idlSuperclass {
+ font-style: italic;
+ color: #005a9c;
+}
+
+/*.idlAttribute*/
+.idlAttrType, .idlFieldType {
+ color: #005a9c;
+}
+.idlAttrName, .idlFieldName {
+ color: #ff4500;
+}
+.idlAttrName a, .idlFieldName a {
+ color: #ff4500;
+ border-bottom: 1px dotted #ff4500;
+ text-decoration: none;
+}
+
+/*.idlMethod*/
+.idlMethType {
+ color: #005a9c;
+}
+.idlMethName {
+ color: #ff4500;
+}
+.idlMethName a {
+ color: #ff4500;
+ border-bottom: 1px dotted #ff4500;
+ text-decoration: none;
+}
+
+/*.idlParam*/
+.idlParamType {
+ color: #005a9c;
+}
+.idlParamName {
+ font-style: italic;
+}
+
+.extAttr {
+ color: #666;
+}
+
+/*.idlConst*/
+.idlConstType {
+ color: #005a9c;
+}
+.idlConstName {
+ color: #ff4500;
+}
+.idlConstName a {
+ color: #ff4500;
+ border-bottom: 1px dotted #ff4500;
+ text-decoration: none;
+}
+
+/*.idlException*/
+.idlExceptionID {
+ font-weight: bold;
+ color: #c00;
+}
+
+.idlTypedefID, .idlTypedefType {
+ color: #005a9c;
+}
+
+.idlRaises, .idlRaises a.idlType, .idlRaises a.idlType code, .excName a, .excName a code {
+ color: #c00;
+ font-weight: normal;
+}
+
+.excName a {
+ font-family: monospace;
+}
+
+.idlRaises a.idlType, .excName a.idlType {
+ border-bottom: 1px dotted #c00;
+}
+
+.excGetSetTrue, .excGetSetFalse, .prmNullTrue, .prmNullFalse, .prmOptTrue, .prmOptFalse {
+ width: 45px;
+ text-align: center;
+}
+.excGetSetTrue, .prmNullTrue, .prmOptTrue { color: #0c0; }
+.excGetSetFalse, .prmNullFalse, .prmOptFalse { color: #c00; }
+
+.idlImplements a {
+ font-weight: bold;
+}
+
+dl.attributes, dl.methods, dl.constants, dl.fields {
+ margin-left: 2em;
+}
+
+.attributes dt, .methods dt, .constants dt, .fields dt {
+ font-weight: normal;
+}
+
+.attributes dt code, .methods dt code, .constants dt code, .fields dt code {
+ font-weight: bold;
+ color: #000;
+ font-family: monospace;
+}
+
+.attributes dt code, .fields dt code {
+ background: #ffffd2;
+}
+
+.attributes dt .idlAttrType code, .fields dt .idlFieldType code {
+ color: #005a9c;
+ background: transparent;
+ font-family: inherit;
+ font-weight: normal;
+ font-style: italic;
+}
+
+.methods dt code {
+ background: #d9e6f8;
+}
+
+.constants dt code {
+ background: #ddffd2;
+}
+
+.attributes dd, .methods dd, .constants dd, .fields dd {
+ margin-bottom: 1em;
+}
+
+table.parameters, table.exceptions {
+ border-spacing: 0;
+ border-collapse: collapse;
+ margin: 0.5em 0;
+ width: 100%;
+}
+table.parameters { border-bottom: 1px solid #90b8de; }
+table.exceptions { border-bottom: 1px solid #deb890; }
+
+.parameters th, .exceptions th {
+ color: #fff;
+ padding: 3px 5px;
+ text-align: left;
+ font-family: initial;
+ font-weight: normal;
+ text-shadow: #666 1px 1px 0;
+}
+.parameters th { background: #90b8de; }
+.exceptions th { background: #deb890; }
+
+.parameters td, .exceptions td {
+ padding: 3px 10px;
+ border-top: 1px solid #ddd;
+ vertical-align: top;
+}
+
+.parameters tr:first-child td, .exceptions tr:first-child td {
+ border-top: none;
+}
+
+.parameters td.prmName, .exceptions td.excName, .exceptions td.excCodeName {
+ width: 100px;
+}
+
+.parameters td.prmType {
+ width: 120px;
+}
+
+table.exceptions table {
+ border-spacing: 0;
+ border-collapse: collapse;
+ width: 100%;
+}
+
+/* --- TOC --- */
+.toc a {
+ text-decoration: none;
+}
+
+a .secno {
+ color: #000;
+}
+
+/* --- 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;
+}
+
+/* --- EXAMPLES --- */
+pre.example {
+ border-top: 1px solid #ff4500;
+ border-bottom: 1px solid #ff4500;
+ padding: 1em;
+ margin-top: 1em;
+}
+
+pre.example::before {
+ content: "Example";
+ display: block;
+ width: 150px;
+ background: #ff4500;
+ color: #fff;
+ font-family: initial;
+ padding: 3px;
+ font-weight: bold;
+ margin: -1em 0 1em -1em;
+}
+
+/* --- EDITORIAL NOTES --- */
+.issue {
+ padding: 1em;
+ margin: 1em 0em 0em;
+ border: 1px solid #f00;
+ background: #ffc;
+}
+
+.issue::before {
+ content: "Issue";
+ display: block;
+ width: 150px;
+ margin: -1.5em 0 0.5em 0;
+ font-weight: bold;
+ border: 1px solid #f00;
+ background: #fff;
+ padding: 3px 1em;
+}
+
+.note {
+ margin: 1em 0em 0em;
+ padding: 1em;
+ border: 2px solid #cff6d9;
+ background: #e2fff0;
+}
+
+.note::before {
+ content: "Note";
+ display: block;
+ width: 150px;
+ margin: -1.5em 0 0.5em 0;
+ font-weight: bold;
+ border: 1px solid #cff6d9;
+ background: #fff;
+ padding: 3px 1em;
+}
+
+/* --- Best Practices --- */
+div.practice {
+ border: solid #bebebe 1px;
+ margin: 2em 1em 1em 2em;
+}
+
+span.practicelab {
+ margin: 1.5em 0.5em 1em 1em;
+ font-weight: bold;
+ font-style: italic;
+}
+
+span.practicelab { background: #dfffff; }
+
+span.practicelab {
+ position: relative;
+ padding: 0 0.5em;
+ top: -1.5em;
+}
+
+p.practicedesc {
+ margin: 1.5em 0.5em 1em 1em;
+}
+
+@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;
+}
+
+pre.sh_sourceCode .sh_keyword { color: #005a9c; font-weight: bold; } /* language keywords */
+pre.sh_sourceCode .sh_type { color: #666; } /* basic types */
+pre.sh_sourceCode .sh_usertype { color: teal; } /* user defined types */
+pre.sh_sourceCode .sh_string { color: red; font-family: monospace; } /* strings and chars */
+pre.sh_sourceCode .sh_regexp { color: orange; font-family: monospace; } /* regular expressions */
+pre.sh_sourceCode .sh_specialchar { color: #ffc0cb; font-family: monospace; } /* e.g., \n, \t, \\ */
+pre.sh_sourceCode .sh_comment { color: #A52A2A; font-style: italic; } /* comments */
+pre.sh_sourceCode .sh_number { color: purple; } /* literal numbers */
+pre.sh_sourceCode .sh_preproc { color: #00008B; font-weight: bold; } /* e.g., #include, import */
+pre.sh_sourceCode .sh_symbol { color: blue; } /* e.g., *, + */
+pre.sh_sourceCode .sh_function { color: black; font-weight: bold; } /* function calls and declarations */
+pre.sh_sourceCode .sh_cbracket { color: red; } /* block brackets (e.g., {, }) */
+pre.sh_sourceCode .sh_todo { font-weight: bold; background-color: #00FFFF; } /* TODO and FIXME */
+
+/* Predefined variables and functions (for instance glsl) */
+pre.sh_sourceCode .sh_predef_var { color: #00008B; }
+pre.sh_sourceCode .sh_predef_func { color: #00008B; font-weight: bold; }
+
+/* for OOP */
+pre.sh_sourceCode .sh_classname { color: teal; }
+
+/* line numbers (not yet implemented) */
+pre.sh_sourceCode .sh_linenum { display: none; }
+
+/* Internet related */
+pre.sh_sourceCode .sh_url { color: blue; text-decoration: underline; font-family: monospace; }
+
+/* for ChangeLog and Log files */
+pre.sh_sourceCode .sh_date { color: blue; font-weight: bold; }
+pre.sh_sourceCode .sh_time, pre.sh_sourceCode .sh_file { color: #00008B; font-weight: bold; }
+pre.sh_sourceCode .sh_ip, pre.sh_sourceCode .sh_name { color: #006400; }
+
+/* for Prolog, Perl... */
+pre.sh_sourceCode .sh_variable { color: #006400; }
+
+/* for LaTeX */
+pre.sh_sourceCode .sh_italics { color: #006400; font-style: italic; }
+pre.sh_sourceCode .sh_bold { color: #006400; font-weight: bold; }
+pre.sh_sourceCode .sh_underline { color: #006400; text-decoration: underline; }
+pre.sh_sourceCode .sh_fixed { color: green; font-family: monospace; }
+pre.sh_sourceCode .sh_argument { color: #006400; }
+pre.sh_sourceCode .sh_optionalargument { color: purple; }
+pre.sh_sourceCode .sh_math { color: orange; }
+pre.sh_sourceCode .sh_bibtex { color: blue; }
+
+/* for diffs */
+pre.sh_sourceCode .sh_oldfile { color: orange; }
+pre.sh_sourceCode .sh_newfile { color: #006400; }
+pre.sh_sourceCode .sh_difflines { color: blue; }
+
+/* for css */
+pre.sh_sourceCode .sh_selector { color: purple; }
+pre.sh_sourceCode .sh_property { color: blue; }
+pre.sh_sourceCode .sh_value { color: #006400; font-style: italic; }
+
+/* other */
+pre.sh_sourceCode .sh_section { color: black; font-weight: bold; }
+pre.sh_sourceCode .sh_paren { color: red; }
+pre.sh_sourceCode .sh_attribute { color: #006400; }
+
+</style><link href="./ProvenanceModel_files/W3C-ED" rel="stylesheet" type="text/css" charset="utf-8"></head>
+ <body style="display: inherit; "><div class="head"><p><a href="http://www.w3.org/"><img width="72" height="48" src="./ProvenanceModel_files/w3c_home" alt="W3C"></a></p><h1 class="title" id="title">Provenance Model</h1><h2 id="subtitle">Initial draft for internal discussion</h2><h2 id="w3c-editor-s-draft-18-july-2011">W3C Editor's Draft 18 July 2011</h2><dl><dt>This version:</dt><dd><a href="http://www.w3.org/2011/prov/wiki/D1--NOT-YET-AVAILABLE">http://www.w3.org/2011/prov/wiki/D1--NOT-YET-AVAILABLE</a></dd><dt>Latest published version:</dt><dd><a href="http://www.w3.org/TR/PIL-Model/">http://www.w3.org/TR/PIL-Model/</a></dd><dt>Latest editor's draft:</dt><dd><a href="http://www.w3.org/2011/prov/wiki/D1--NOT-YET-AVAILABLE">http://www.w3.org/2011/prov/wiki/D1--NOT-YET-AVAILABLE</a></dd><dt>Previous version:</dt><dd>none</dd><dt>Editors:</dt><dd><a href="http://www.ecs.soton.ac.uk/~lavm">Luc Moreau</a>, University of Southampton, UK</dd>
+<dd><a href="http://www.cs.ncl.ac.uk/people/Paolo.Missier">Paolo Missier</a>, Newcastle University, UK</dd>
+<dt>Author:</dt><dd><span>TBD</span></dd>
+</dl><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2011 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.eu/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <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>
+ <div id="abstract" class="introductory section"><h2>Abstract</h2>
<p>This document defines a data model for Provenance.</p>
<p>
This is a document for internal discussion, which will ultimately
evolve in the first Public Working Draft of the Conceptual Model.</p>
- </section>
+ </div><div id="sotd" class="introductory section"><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 W3C publications and the latest revision of this technical report can be found in the <a href="http://www.w3.org/TR/">W3C technical reports index</a> at http://www.w3.org/TR/.</em></p><p>This document was published by the <a href="http://www.w3.org/2011/prov/wiki/Main_Page">Provenance Working Group</a> as an Editor's Draft. If you wish to make comments regarding this document, please send them to <a href="mailto:public-prov-wg@w3.org">public-prov-wg@w3.org</a> (<a href="mailto:public-prov-wg-request@w3.org?subject=subscribe">subscribe</a>, <a href="http://lists.w3.org/Archives/Public/public-prov-wg/">archives</a>). All feedback is welcome.</p><p>Publication as a Editor's Draft does not imply endorsement by the W3C 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 W3C Patent Policy</a>. W3C maintains a <a href="" 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 W3C Patent Policy</a>.</p></div><div id="toc" class="section"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a href="file:///tmp/ProvenanceModel.html#introduction" class="tocxref"><span class="secno">1. </span>Introduction<br>
+</a></li><li class="tocline"><a href="file:///tmp/ProvenanceModel.html#motivation-and-requirements" class="tocxref"><span class="secno">2. </span>Motivation and Requirements</a></li><li class="tocline"><a href="file:///tmp/ProvenanceModel.html#example" class="tocxref"><span class="secno">3. </span>Example</a></li><li class="tocline"><a href="file:///tmp/ProvenanceModel.html#about-the-provenance-language" class="tocxref"><span class="secno">4. </span>About the Provenance Language</a></li><li class="tocline"><a href="file:///tmp/ProvenanceModel.html#data-model-concepts" class="tocxref"><span class="secno">5. </span>Provenance Data Model</a><ul class="toc"><li class="tocline"><a href="file:///tmp/ProvenanceModel.html#bob" class="tocxref"><span class="secno">5.1 </span>BOB</a></li><li class="tocline"><a href="file:///tmp/ProvenanceModel.html#concept-ProcessExecution" class="tocxref"><span class="secno">5.2 </span>Process Execution</a></li><li class="tocline"><a href="file:///tmp/ProvenanceModel.html#concept-Generation" class="tocxref"><span class="secno">5.3 </span>Generation<br>
+</a></li><li class="tocline"><a href="file:///tmp/ProvenanceModel.html#concept-Use" class="tocxref"><span class="secno">5.4 </span>Use</a></li><li class="tocline"><a href="file:///tmp/ProvenanceModel.html#concept-Derivation" class="tocxref"><span class="secno">5.5 </span>Derivation</a></li><li class="tocline"><a href="file:///tmp/ProvenanceModel.html#concept-Agent" class="tocxref"><span class="secno">5.6 </span>Agent</a></li><li class="tocline"><a href="file:///tmp/ProvenanceModel.html#concept-IVPOf" class="tocxref"><span class="secno">5.7 </span>IVP of</a></li><li class="tocline"><a href="file:///tmp/ProvenanceModel.html#concept-Time" class="tocxref"><span class="secno">5.8 </span>Time</a></li><li class="tocline"><a href="file:///tmp/ProvenanceModel.html#concept-RecipeLink" class="tocxref"><span class="secno">5.9 </span>Recipe Link</a></li><li class="tocline"><a href="file:///tmp/ProvenanceModel.html#concept-Role" class="tocxref"><span class="secno">5.10 </span>Role</a></li><li class="tocline"><a href="file:///tmp/ProvenanceModel.html#concept-Location" class="tocxref"><span class="secno">5.11 </span>Location</a></li><li class="tocline"><a href="file:///tmp/ProvenanceModel.html#concept-OrderingOfProcesses" class="tocxref"><span class="secno">5.12 </span>Ordering of Processes</a></li><li class="tocline"><a href="file:///tmp/ProvenanceModel.html#concept-Revision" class="tocxref"><span class="secno">5.13 </span>Revision</a></li><li class="tocline"><a href="file:///tmp/ProvenanceModel.html#concept-Participation" class="tocxref"><span class="secno">5.14 </span>Participation</a></li><li class="tocline"><a href="file:///tmp/ProvenanceModel.html#concept-Control" class="tocxref"><span class="secno">5.15 </span>Control</a></li><li class="tocline"><a href="file:///tmp/ProvenanceModel.html#concept-ProvenanceContainer" class="tocxref"><span class="secno">5.16 </span>Provenance Container</a></li><li class="tocline"><a href="file:///tmp/ProvenanceModel.html#concept-ViewsOrAccount" class="tocxref"><span class="secno">5.17 </span>View Or Account</a></li><li class="tocline"><a href="file:///tmp/ProvenanceModel.html#concept-Collection" class="tocxref"><span class="secno">5.18 </span>Collection</a></li></ul></li><li class="tocline"><a href="file:///tmp/ProvenanceModel.html#acknowledgements" class="tocxref"><span class="secno">A. </span>Acknowledgements</a></li><li class="tocline"><a href="file:///tmp/ProvenanceModel.html#references" class="tocxref"><span class="secno">B. </span>References</a><ul class="toc"><li class="tocline"><a href="file:///tmp/ProvenanceModel.html#normative-references" class="tocxref"><span class="secno">B.1 </span>Normative references</a></li><li class="tocline"><a href="file:///tmp/ProvenanceModel.html#informative-references" class="tocxref"><span class="secno">B.2 </span>Informative references</a></li></ul></li></ul></div>
- <section>
- <h2>Introduction<br>
+ <div id="introduction" class="section">
+ <!--OddPage--><h2><span class="secno">1. </span>Introduction<br>
</h2>
<p>
- The Provenance language that is being defined by this WG, with name to be determined, is an <em>assertion language</em> which allows asserters to make assertions about <em>Entities</em> and activities in the real world (as they view it) and how they influence each other. <br>
-</p>
- </section>
+ The Provenance language that is being defined by this WG, with name to be determined, is an <em>assertion language</em> which allows asserters to make assertions about <em>Entities</em> and activities in the real world (as they view it) and how such entities and activities influence each other. <br>
- <section>
-<h2>Motivation and Requirements</h2>
- </section>
+</p><div class="note">PM: propose to add a sentence on annotations to assertions, as follows. This WG does not prescribe the means by which assertions are made, for example on the basis of observations, or inferences, or other means. However, it should be possible for asserters to annotate any assertion with a description of the justification for that assertion, as well as additional meta-information, such as authorship of the assertion.</div>
+<p></p>
+ </div>
- <section>
-<h2>Example</h2>
- </section>
+ <div id="motivation-and-requirements" class="section">
+<!--OddPage--><h2><span class="secno">2. </span>Motivation and Requirements</h2>
+ </div>
+
+ <div id="example" class="section">
+<!--OddPage--><h2><span class="secno">3. </span>Example</h2>
+ </div>
- <section >
-<h2>About the Provenance Language</h2>
+ <div id="about-the-provenance-language" class="section">
+<!--OddPage--><h2><span class="secno">4. </span>About the Provenance Language</h2>
<p>In the world (whether real or not), there are entities, which can be
physical, digital, conceptual, or otherwise, and activities involving
@@ -115,39 +525,43 @@
entities</em>, that is, entities, with their state, and situation in
the world, as perceived by their asserters. (NOTE: alternative term could be characterized entity).</p>
-<p>PIL is a language by which:
-<menu>
-<li> representations of the world can be expressed according to a
- constrained vocabulary
-<li> these representations are subjective, they are the point of view
- of their asserters, and in that sense constitute assertions about
- the world.
-</menu>
+<div class="note">This def. of situated entities is not clear to me. It relies on <em>state</em> and <em>situation</em> both of which <strong>do</strong> need a def. IMO. What is it trying to replace?</div>
+
+<p>PIL is a language by which representations of the world can be expressed using terms that are drawn from a controlled
+ vocabulary.
+
+These representations are relative to an asserter. Different asserters will normally contribute different representation, and no attempt is made to define the notion of consistency of such different sets of assertions.
</p>
-<p>All assertions in PIL have to be interpreted as something that has happened.</p>
+<div class="note">I have rephrased your sentence above. Both this version and yours still beg the question, of how one can distinguish amongst assertions made by different asserters. This may eventually boil down to some named graph language construct in the implementation, but for the time being the ability to associate an attribution to each assertion is crucial. I would make this non-optional (<code>must</code>).</div>
+
+<p>All assertions in PIL are interpreted as a record of something that has happened.</p>
+
+<div class="note">this sounds exactly like an <strong>event</strong>. Can we just use the term?</div>
<p> No assumption is made on how PIL Assertions are asserted. They can
be can be made by any means: observing, guessing, lying, or any other
way.</p>
- </section>
+<div class="note">I find this a bit too informal. I have proposed a rephrasing above</div>.
+
+ </div>
- <section id="data-model-concepts">
+ <div id="data-model-concepts" class="section">
-<h2>Provenance Data Model</h2>
+<!--OddPage--><h2><span class="secno">5. </span>Provenance Data Model</h2>
<em>For each construct, I tried to follow the template: short
definition/data structure components/properties/inference. </em>
- <section>
+ <div id="bob" class="section">
-<h3>BOB</h3>
+<h3><span class="secno">5.1 </span>BOB</h3>
-<p>A <dfn id="dfn-bob">BOB</dfn> represents an identifiable situated entity.</p>
+<p>A <dfn id="dfn-bob" title="BOB">BOB</dfn> represents an identifiable situated entity.</p>
<p>A BOB assertion
is about a situated entity, whose state and in the world are variant;
@@ -155,69 +569,84 @@
It includes a set of characteristics, predicate-value pairs, which hold about the situated entity;
</p>
+<div class="note">"whose state and in the world" is that what you wanted to say?</div>
+<div class="note">PLEASE define (a) variant, (b) invariant. This really trips me up as a reader. I think we have agreed that variance/invariance is relative to a scope (time interval, interval between two events?. In any case, these terms must be defined.</div>
+
<p>A BOB assertion:
-<ul>
-<li> MAY contain an identity;</li>
+</p><ul>
+<li> <em class="rfc2119" title="may">may</em> contain an identity;</li>
<li> contains a set of characteristics, predicate-value pairs.</li>
</ul>
-<p>A situated entity MUST exist instantaneously or for a continuous time interval. If a BOB's characteristics hold over multiple time intervals, then we are dealing with multiple situated entities, each with their respective identity.</p>
+<p>A situated entity <em class="rfc2119" title="must">must</em> exist instantaneously or for a continuous time interval. If a BOB's characteristics hold over multiple time intervals, then we are dealing with multiple situated entities, each with their respective identity.</p>
-<p>Identity in a BOB assertion is OPTIONAL to allow for a so far unidentified (though still identifiable!) entities.<p>
+<p>Identity in a BOB assertion is <em class="rfc2119" title="optional">optional</em> to allow for a so far unidentified (though still identifiable!) entities.</p><p>
-<p>There is no assumption that the set of characteristics is complete,
+</p><p>There is no assumption that the set of characteristics is complete,
that the characteristics are independent/orthogonal of each other, or
that the characteristics hold for a continuous time interval.</p>
- </section>
+ </div>
- <section id="concept-ProcessExecution">
+ <div id="concept-ProcessExecution" class="section">
-<h3>Process Execution</h3>
+<h3><span class="secno">5.2 </span>Process Execution</h3>
<p>A <dfn id="dfn-ProcessExecution">process execution</dfn> represents an identifiable activity that performs a piece of work.
-</p>
+
+</p><div class="note">" that performs a piece of work" is redundant as at the top we write that "activity" is a primitive concept to be interpreted in its "informal meaning"</div>
+<p></p>
<p>The activity that a process execution represents has a duration, delimited by its start and its end; hence, it occurs over a continuous time interval.</p>
<p> A process execution assertion:
-<ul>
-<li> MAY contain an identity;
-<li> MAY contain a recipe link;
-<li> MAY contain a start time;
-<li> MAY contain an end time.
-</ul>
-</p>
+</p><ul>
+<li> <em class="rfc2119" title="may">may</em> contain an identity;
+</li><li> <em class="rfc2119" title="may">may</em> contain a recipe link;
+ <div class="note">NB <em>recipe</em> undefined at this point</div>
+</li><li> <em class="rfc2119" title="may">may</em> contain a start time;
+</li><li> <em class="rfc2119" title="may">may</em> contain an end time.
+</li></ul>
+<p></p>
-<p>Identity in a process execution assertion is OPTIONAL to allow for
-unidentified (though still identifiable!) process executions.<p>
+<p>Identity in a process execution assertion is <em class="rfc2119" title="optional">optional</em> to allow for
+unidentified (though still identifiable!) process executions.</p><p>
-<p>From the assertion of a process execution, one can infer that the start precedes the end of the represented activity. </p>
+</p><p>From the assertion of a process execution, one can infer that the start precedes the end of the represented activity. </p>
-</section>
+</div>
-<section id="concept-Generation">
-<h3>Generation<br>
+<div id="concept-Generation" class="section">
+<h3><span class="secno">5.3 </span>Generation<br>
</h3>
<p><dfn id="dfn-Generation">Generation</dfn> represents the creation of a new situated entity by an activity. This situated entity did not exist before creation.</p>
+<div class="note">I think this needs to be qualified: "according to the asserter that makes a generation assertion..."</div>
+
+
<p>A Generation assertion:
-<ul>
-<li> contains a process execution;
-<li> contains a BOB, representing the situated entity that is consumed;
-<li> contains a role, distinguishing all possible generations of a same BOB by a same process execution;
-<li> MAY contain a "generation time", the time at which the situated entity was consumed.</p>
-</ul>
-</p>
+</p><ul>
+<li> refers to a process execution;
+</li><li> refers to a BOB, which represents the situated entity that is consumed;
+ <div class="note">Consumed?? </div>
+</li><li> contains a role, distinguishing all possible generations of a same BOB by a same process execution;
+ <div class="note"> role? bullet item above not clear at all to me. All of a sudden we have multiple possible generations by the same process? this is going to be confusing.</div>
+</li><li> <em class="rfc2119" title="may">may</em> contain a "generation time", the time at which the situated entity was consumed.<p></p>
+</li></ul>
+<p></p>
<p>A given BOB can be generated at most by one process execution.</p>
+<div class="note"> I hope we can discuss the two statements below. Suddenly we have a relational notation for Generation. For consistency with the list above, I would put pe before x.</div>
+
+<div class="note"> Also: characteristics -> properties?</div>
+
<p>Given an assertion <b>Generated(x,pe,r)</b> or <b>Generated(x,pe,r,t)</b>, the
activity denoted by <b>pe</b> and the entities used by <b>pe</b> dermine values of some of <b>x</b>'s characteristics.</p>
@@ -226,23 +655,23 @@
of <b>pe</b> and follows the beginning of <b>pe</b>.
</p>
-</section>
+</div>
-<section id="concept-Use">
-<h3>Use</h3>
+<div id="concept-Use" class="section">
+<h3><span class="secno">5.4 </span>Use</h3>
<p><dfn id="dfn-Use">Use</dfn> represents the consumption of a situated entity by an activity.</p>
<p>A Use assertion:
-<ul>
+</p><ul>
<li> contains a process execution;
-<li> contains a BOB, representing the situated entity that is used;
-<li> contains a role, distinguishing all possible uses of a same BOB by a same process execution;
-<li> MAY contain a "use time", the time at which the situated entity was used.</p>
-</ul>
-</p>
+</li><li> contains a BOB, representing the situated entity that is used;
+</li><li> contains a role, distinguishing all possible uses of a same BOB by a same process execution;
+</li><li> <em class="rfc2119" title="may">may</em> contain a "use time", the time at which the situated entity was used.<p></p>
+</li></ul>
+<p></p>
<p>A given process execution is allowed to use a given BOB multiple
times, but each of those uses must have a different role.</p>
@@ -261,21 +690,21 @@
can infer that the generation of the entity <b>x</b> always precedes
its use. </p>
-</section>
+</div>
-<section id="concept-Derivation">
-<h3>Derivation</h3>
+<div id="concept-Derivation" class="section">
+<h3><span class="secno">5.5 </span>Derivation</h3>
<p><dfn id="dfn-Derivation">Derivation</dfn> expresses that some situated entity is transformed from, created from, or affected by another situated entity. </p>
<p>A Derivation assertion:
-<ul>
+</p><ul>
<li> contains a BOB, denoting the generated situated entity;
-<li> contains a BOB, denoting the used situated entity.
-</ul>
-</p>
+</li><li> contains a BOB, denoting the used situated entity.
+</li></ul>
+<p></p>
@@ -289,10 +718,10 @@
of situated entity denoted by <b>A</b> precedes the generation of
the situated entity denoted by <b>B</b>.
-</section>
+</p></div>
-<section id="concept-Agent">
-<h3>Agent</h3>
+<div id="concept-Agent" class="section">
+<h3><span class="secno">5.6 </span>Agent</h3>
@@ -302,21 +731,19 @@
<p>A situated entity can be asserted to be an agent or can be inferred to be
an agent by involvement in a process execution. </p>
-</section>
+</div>
-<section id="concept-IVPOf">
+<div class="note">I would still like to see entities that "play the role of Agent" in the context of a process execution, as opposed to <em>be</em> an agent</div>
-<h3>IVP of</h3>
+<div id="concept-IVPOf" class="section">
+
+<h3><span class="secno">5.7 </span>IVP of</h3>
<p><dfn id="dfn-IVPof">IVP of</dfn> represents a relationship between two situated entities that are the same entity over some continuous time interval.</p>
-<p>An IVP of assertion, noted <b>IVPof(B,A)</b>:
-<ul>
-<li> contains a BOB, denoting ...
-<li> contains a BOB, denoting ...
-</ul>
-</p>
+<p>An IVP assertion is denoted <b>IVPof(B,A)</b>, where A and B are two BOBs.
+</p><div class="note"> What follows below definitely needs revision</div>
<p>Let A and B be two entity states. An assertion "B is an IVP of A"
indicates that, for its asserter, A and B represent the same entity in
@@ -325,32 +752,34 @@
<p>
An assertion "B is an IVP of A" holds, <em>only if</em>:
-<ol>
+</p><ol>
<li>the characteristics A and B share must have equal values
</li><li>something that changed in A has become a characteristics of B
</li></ol>
Furthermore, B has invariant properties that have no correspondent for A
-</p>
-</section>
+<p></p>
+</div>
-<section id="concept-Time">
-<h3>Time</h3>
+<div id="concept-Time" class="section">
+<h3><span class="secno">5.8 </span>Time</h3>
<p><dfn id="dfn-time">Time</dfn> is defined according to ISO 8601.</p>
-<p>It is OPTIONAL to assert time in use, generation, and process execution.</p>
+<p>It is <em class="rfc2119" title="optional">optional</em> to assert time in use, generation, and process execution.</p>
-</section>
+</div>
-<section id="concept-RecipeLink">
-<h3>Recipe Link</h3>
+<div id="concept-RecipeLink" class="section">
+<h3><span class="secno">5.9 </span>Recipe Link</h3>
+
+<div class="note">move this close to Process Execution, as they seem to mutually refer to each other (which is ok but requires explaining)</div>
<p>A <dfn id="dfn-RecipeLink">recipe link</dfn> is an association between a process execution and a process specification that underpins the process execution.
</p>
<p>
-It is OPTIONAL to assert recipe links.
+It is <em class="rfc2119" title="optional">optional</em> to assert recipe links.
</p>
@@ -358,15 +787,17 @@
Process specifications, as referred to by recipe links, are out of scope of this specification.
</p>
-</section>
+</div>
-<section id="concept-Role">
-<h3>Role</h3>
+<div id="concept-Role" class="section">
+<h3><span class="secno">5.10 </span>Role</h3>
+
+<div class="note">move above first use. </div>
<p>A <dfn id="dfn-Role">role</dfn> is the function assumed by a BOB or
an agent with respect to a specific process execution.</p>
-<p>Use, Generation, and Control assertions MUST contain a role.</p>
+<p>Use, Generation, and Control assertions <em class="rfc2119" title="must">must</em> contain a role.</p>
<p>There is at most one occurrence of a given role for all Use, Generation and Control assertions for a given process execution.</p>
@@ -374,31 +805,32 @@
to. From this specification's viewpoint, a role's meaning is out of
scope; thus, roles are considered as syntactic attributes.</p>
+<div class="note">or: "attributes whose domain is defined by the application? </div>
-</section>
+</div>
-<section id="concept-Location">
-<h3>Location</h3>
+<div id="concept-Location" class="section">
+<h3><span class="secno">5.11 </span>Location</h3>
<p><dfn id="dfn-Location">Location</dfn> is an identifiable geographic place (ISO 19112). As such, there are numerous ways in which location can be specified, such as by a coordinate, address, landmark, row, column, and so forth.</p>
<p>
-Location is an OPTIONAL characteristics of
+Location is an <em class="rfc2119" title="optional">optional</em> characteristics of
BOB, process execution, and agent.
</p>
-</section>
+</div>
-<section id="concept-OrderingOfProcesses">
-<h3>Ordering of Processes</h3>
-</section>
+<div id="concept-OrderingOfProcesses" class="section">
+<h3><span class="secno">5.12 </span>Ordering of Processes</h3>
+</div>
<p>Various relationships of temporal nature exist between process executions.
<dfn id="ControlOrdering">Control ordering</dfn> means that the end of
@@ -408,77 +840,77 @@
</p>
<p>An assertion isScheduledAfter:
-<ul>
+</p><ul>
<li> contains a process execution;
-<li> contains a process execution.
-</ul>
-</p>
+</li><li> contains a process execution.
+</li></ul>
+<p></p>
<p>An assertion isInformedBy:
-<ul>
+</p><ul>
<li> contains a process execution;
-<li> contains a process execution.
-</ul>
-</p>
+</li><li> contains a process execution.
+</li></ul>
+<p></p>
-<section id="concept-Revision">
-<h3>Revision</h3>
+<div id="concept-Revision" class="section">
+<h3><span class="secno">5.13 </span>Revision</h3>
<p> <dfn id="dfn-Revision">Revision</dfn> represents the creation of a situated entity considered to be a variant of another. </p>
<p>An assertion isRevisionOf:
-<ul>
+</p><ul>
<li> contains a BOB, denoting a older version of an entity;
-<li> contains a BOB, denoting a newer version of an entity;
-<li> MAY contain a responsible agent.
-</ul>
-</p>
+</li><li> contains a BOB, denoting a newer version of an entity;
+</li><li> <em class="rfc2119" title="may">may</em> contain a responsible agent.
+</li></ul>
+<p></p>
<p>
From an assertion <b>isRevisionOf(new,old,ag)</b>, one can infer that:
-<ul>
+</p><ul>
<li> The situated entity denoted by <b>new</b> is derived from the situated entity denoted by <b>old</b>
-<li> There exists a BOB <b>X</b>, such that:
+</li><li> There exists a BOB <b>X</b>, such that:
<ul>
<li> <b>new</b> isIVP of <b>X</b>;
-<li> <b>old</b> isIVP of <b>X</b>;
-<li> <b>X</b> MAY have been asserted.
-</ul>
-</ul>
-</p>
+</li><li> <b>old</b> isIVP of <b>X</b>;
+</li><li> <b>X</b> <em class="rfc2119" title="may">may</em> have been asserted.
+</li></ul>
+</li></ul>
+<p></p>
-</section>
+</div>
-<section id="concept-Participation">
-<h3>Participation</h3>
-</section>
+<div id="concept-Participation" class="section">
+<h3><span class="secno">5.14 </span>Participation</h3>
+</div>
-<section id="concept-Control">
-<h3>Control</h3>
+<div id="concept-Control" class="section">
+<h3><span class="secno">5.15 </span>Control</h3>
<p> <dfn id="dfn-Control">Control</dfn> represents the starting or ending of a process execution by an agent. </p>
<p>An assertion <b>startedBy(pe,ag,r)</b>:
-<ul>
+</p><ul>
<li> contains a process execution;
-<li> contains an agent;
-<li> contains a role.
-</ul>
-</p>
+</li><li> contains an agent;
+</li><li> contains a role.
+</li></ul>
+<p></p>
<p>An assertion <b>endedBy(pe,ag,r)</b>:
-<ul>
+</p><ul>
<li> contains a process execution;
-<li> contains an agent;
-<li> contains a role.
-</ul>
-</p>
+</li><li> contains an agent;
+</li><li> contains a role.
+</li></ul>
+<p></p>
<p>
The convenience assertion <b>controlledBy(pe,ag,r)</b> is
@@ -487,30 +919,30 @@
<p><em> Can multiple agents control a process execution? If so, what does it mean to have a start/end time?</em> </p>
-</section>
-
-<section id="concept-ProvenanceContainer">
-<h3>Provenance Container</h3>
-</section>
+</div>
-<section id="concept-ViewsOrAccount">
-<h3>View Or Account</h3>
-</section>
+<div id="concept-ProvenanceContainer" class="section">
+<h3><span class="secno">5.16 </span>Provenance Container</h3>
+</div>
-<section id="concept-Collection">
-<h3>Collection</h3>
-</section>
+<div id="concept-ViewsOrAccount" class="section">
+<h3><span class="secno">5.17 </span>View Or Account</h3>
+</div>
+
+<div id="concept-Collection" class="section">
+<h3><span class="secno">5.18 </span>Collection</h3>
+</div>
- </section>
+ </div>
-<section class="appendix">
- <h2>Acknowledgements</h2>
+<div class="appendix section" id="acknowledgements">
+ <!--OddPage--><h2><span class="secno">A. </span>Acknowledgements</h2>
<p>
WG membership to be listed here.
</p>
- </section>
+ </div>
- </body></html>
-<!-- test -->
+
+<div id="references" class="appendix section"><!--OddPage--><h2><span class="secno">B. </span>References</h2><div id="normative-references" class="section"><h3><span class="secno">B.1 </span>Normative references</h3><p>No normative references.</p></div><div id="informative-references" class="section"><h3><span class="secno">B.2 </span>Informative references</h3><p>No informative references.</p></div></div></body></html>
\ No newline at end of file