--- a/model/ProvenanceModel.html Tue Dec 20 10:45:04 2011 +0000
+++ b/model/ProvenanceModel.html Tue Dec 20 10:45:21 2011 +0000
@@ -2074,7 +2074,7 @@
One may make several assertions to establish that these entity records refer to the same entity "Bob", either in different contexts, or at different levels of abstraction. For example:
<ol>
- <li> <span class="name">e2</span> provides a more concrete characterization of Bob than <span class="name">e1</span> does
+ <li> Each of <span class="name">e1</span> , <span class="name">e2</span> provide a <em>more concrete</em> characterization of Bob than <span class="name">e3</span> does
<li> <span class="name">e1</span> and <span class="name">e2</span> provide two different characterizations of the same entity.
</ol>
@@ -2105,10 +2105,10 @@
<h5>Case of entities with known limited validity</h5>
-As we know from [entity record], entity records may only be valid within certain events interval. Let <span class="name">val(e)</span> denote the validity interval of <span class="name">e</span>.
+As we know from [entity record], entity records may only be valid within certain event's interval. Let <span class="name">char(e)</span> denote the validity interval of <span class="name">e</span>.
When these intervals are known, relations <span class="name">ViewOf(e2,e1)</span> and <span class="name">foobar(e2,e1)</span> can only be asserted if
-<span class="name">val(e1)</span> is a sub-interval of <span class="name">val(e2)</span>. This condition ensures transitivity.
+the validity interval of <span class="name">e1</span> is a sub-interval of that of <span class="name">e2</span>. This condition ensures transitivity.
<!--
--- a/primer/Primer.html Tue Dec 20 10:45:04 2011 +0000
+++ b/primer/Primer.html Tue Dec 20 10:45:21 2011 +0000
@@ -15,23 +15,23 @@
<script src="http://dev.w3.org/2009/dap/ReSpec.js/js/respec.js" class="remove"></script>
<script class="remove">
- var addExtraReferences = function() {
- for (var k in extraReferences)
- berjon.biblio[k] = extraReferences[k];
- };
- var extraReferences = {
- "PROV-DM":
- "Luc Moreau, Paolo Missier"+
- "<a href=\"http://www.w3.org/TR/2011/WD-prov-dm-20111018/\"><cite>The PROV Data Model and Abstract Syntax Notation</cite></a>. "+
- "18 October 2011. W3C Working Draft. (Work in progress.) "+
- "URL: <a href=\"http://www.w3.org/TR/2011/WD-prov-dm-20111018/\">http://www.w3.org/TR/2011/WD-prov-dm-20111018/</a>",
+ var addExtraReferences = function() {
+ for (var k in extraReferences)
+ berjon.biblio[k] = extraReferences[k];
+ };
+ var extraReferences = {
+ "PROV-DM":
+ "Luc Moreau, Paolo Missier"+
+ "<a href=\"http://www.w3.org/TR/2011/WD-prov-dm-20111215/\"><cite>The PROV Data Model and Abstract Syntax Notation</cite></a>. "+
+ "15 December 2011. W3C Working Draft. (Work in progress.) "+
+ "URL: <a href=\"http://www.w3.org/TR/2011/WD-prov-dm-20111215/\">http://www.w3.org/TR/2011/WD-prov-dm-20111215/</a>",
- "PROV-O":
- "Satya Sahoo, Deborah McGuinness"+
- "<a href=\"http://www.w3.org/TR/2011/WD-prov-o-20111213/\"><cite>The PROV Ontology: Model and Formal Semantics</cite></a>. "+
- "13 December 2011. W3C Working Draft. (Work in progress.) "+
- "URL: <a href=\"http://www.w3.org/TR/2011/WD-prov-o-20111213/\">http://www.w3.org/TR/2011/WD-prov-o-20111213</a>"
- };
+ "PROV-O":
+ "Satya Sahoo, Deborah McGuinness"+
+ "<a href=\"http://www.w3.org/TR/2011/WD-prov-o-20111213/\"><cite>The PROV Ontology: Model and Formal Semantics</cite></a>. "+
+ "13 December 2011. W3C Working Draft. (Work in progress.) "+
+ "URL: <a href=\"http://www.w3.org/TR/2011/WD-prov-o-20111213/\">http://www.w3.org/TR/2011/WD-prov-o-20111213</a>"
+ };
var respecConfig = {
// specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
@@ -42,7 +42,7 @@
// if your specification has a subtitle that goes below the main
// formal title, define it here
- subtitle : "Initial draft for internal discussion",
+ subtitle : "",
// if you wish the publication date to be other than today, set this
// publishDate: "2009-08-06",
@@ -80,20 +80,20 @@
// only "name" is required. Same format as editors.
authors: [
- { name: "Khalid Belhajjame",
- company: "University of Manchester" },
+ { name: "<a href=\"http://semanticweb.org/wiki/Khalid_Belhajjame\">Khalid Belhajjame</a>",
+ company: "University of Manchester" },
{ name: "Helena Deus",
- company: "Digital Enterprise Research Institute (DERI), NUI Galway" },
- { name: "Daniel Garijo",
- company: "Universidad Politécnica de Madrid" },
+ company: "Digital Enterprise Research Institute (DERI), NUI Galway" },
+ { name: "<a href=\"http://www.oeg-upm.net/index.php/en/phdstudents/28-dgarijo\">Daniel Garijo</a>",
+ company: "Universidad Politécnica de Madrid" },
{ name: "Graham Klyne",
- company: "University of Oxford" },
- { name: "Paolo Missier",
- company: "Newcastle University" },
- { name: "Stian Soiland-Reyes",
- company: "University of Manchester" },
- { name: "Stephan Zednik",
- company: "Rensselaer Polytechnic Institute" },
+ company: "University of Oxford" },
+ { name: "<a href=\"http://www.cs.ncl.ac.uk/people/Paolo.Missier\">Paolo Missier</a>",
+ company: "Newcastle University" },
+ { name: "<a href=\"http://soiland-reyes.com/stian/\">Stian Soiland-Reyes</a>",
+ company: "University of Manchester" },
+ { name: "<a href=\"http://tw.rpi.edu/web/person/StephanZednik\">Stephan Zednik</a>",
+ company: "Rensselaer Polytechnic Institute" },
],
// name of the WG
@@ -110,7 +110,7 @@
// 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: "",
+ wgPatentURI: "http://www.w3.org/2004/01/pp-impl/46974/status",
// Add extraReferences to bibliography database
preProcess: [addExtraReferences]
@@ -120,14 +120,14 @@
<body>
<section id="abstract">
<p>
- This document provides an intuitive introduction and guide to the
- PROV data model for provenance [[PROV-DM]]. PROV-DM is a core data model for
- provenance for building representations of the entities, people and
- processes involved in producing a piece of data or thing in the world.
- This primer explains the fundamental PROV-DM concepts in non-normative
- terms, and provides worked examples applying the PROV-O OWL2
- ontology [[PROV-O]]. The primer is intended as a starting point for those wishing
- to create or make use of PROV-DM data.
+ This document provides an intuitive introduction and guide to the
+ PROV data model for provenance [[PROV-DM]]. PROV-DM is a core data model for
+ provenance for building representations of the entities, people and
+ processes involved in producing a piece of data or thing in the world.
+ This primer explains the fundamental PROV-DM concepts in non-normative
+ terms, and provides worked examples applying the PROV-O OWL2
+ ontology [[PROV-O]]. The primer is intended as a starting point for those wishing
+ to create or make use of PROV-DM data.
</p>
<p>
@@ -135,16 +135,16 @@
evolve in the first Public Working Draft of the Primer.</p>
</section>
- <section id="sotd">
- This document is part of a set of specifications aiming to define the
- various aspects that are necessary to achieve the vision of
- interoperable interchange of provenance information in heterogeneous
- environments such as the Web. This document is a non-normative,
- intuitive introduction and guide to the [PROV-DM] data model for
- provenance. It includes simple worked examples applying the [PROV-O]
- OWL2 ontology.
- </section>
-
+ <section id="sotd">
+ This document is part of a set of specifications aiming to define the
+ various aspects that are necessary to achieve the vision of
+ interoperable interchange of provenance information in heterogeneous
+ environments such as the Web. This document is a non-normative,
+ intuitive introduction and guide to the [PROV-DM] data model for
+ provenance. It includes simple worked examples applying the [PROV-O]
+ OWL2 ontology.
+ </section>
+
<section>
<h2>Introduction</h2>
<p>
@@ -223,21 +223,26 @@
<section>
<h2>Intuitive overview of PROV-DM</h2>
- <p><i>This section provides an intuitive explanation of the concepts in PROV-DM.
- As with the rest of this document, it should be treated as a starting point for
- understanding the model, and not normative in itself. The PROV-DM model specification
- provides precise definitions and constraints to be used.</i></p>
+ <p>This section provides an intuitive explanation of the concepts in PROV-DM.
+ As with the rest of this document, it should be treated as a starting point for
+ understanding the model, and not normative in itself. The PROV-DM model specification
+ provides precise definitions and constraints to be used.</p>
+ <div class='note'>
+ Please note that, as they
+ are being developed in parallel, there will be points at which this document
+ does not yet exactly match the current data model or ontology.
+ </div>
-<p>
-The following ER diagram provides a high level overview of the <strong>structure of PROV-DM records</strong>.
-The diagram is the same that appears in the
-<a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html">PROV Data Model and Abstract Syntax Notation document</a>,
-but note that this primer document only describes some of the terms shown in the diagram.
-</p>
+ <p>
+ The following ER diagram provides a high level overview of the <strong>structure of PROV-DM records</strong>.
+ The diagram is the same that appears in the
+ <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html">PROV Data Model and Abstract Syntax Notation document</a>,
+ but note that this primer document only describes some of the terms shown in the diagram.
+ </p>
-<div style="text-align: center;">
- <img src="overview.png" alt="PROV-DM overview"/>
-</div>
+ <div style="text-align: center;">
+ <img src="overview.png" alt="PROV-DM overview"/>
+ </div>
<section>
<h3>Entities</h3>
@@ -262,13 +267,13 @@
so on).
</p>
<p>
- The characterization of an entity means that the provenance assertions
- about the entity are only about the thing when it has those attributes.
- For example, the second version of document D is characterized by being the
- second version, and so assertions about who reviewed that entity apply only
- to the document as it is in its second version. When the document becomes
- the third version, a new entity exists (the third version of D) and the
- provenance assertions about who reviewed the second version do not apply.
+ The characterization of an entity means that the provenance assertions
+ about the entity are only about the thing when it has those attributes.
+ For example, the second version of document D is characterized by being the
+ second version, and so assertions about who reviewed that entity apply only
+ to the document as it is in its second version. When the document becomes
+ the third version, a new entity exists (the third version of D) and the
+ provenance assertions about who reviewed the second version do not apply.
</p>
</section>
@@ -645,7 +650,7 @@
from the revised data set.
</p>
</section>
-
+ </section>
<section>
<h2>Frequently asked questions</h2>
@@ -666,7 +671,7 @@
entity(ex1:chart1).
</pre>
</section>
-
+
<section>
<h3>Activities</h3>
<pre class="example asn">