--- a/model/ProvenanceModel.html Thu Aug 04 22:02:17 2011 +0100
+++ b/model/ProvenanceModel.html Thu Aug 04 23:04:32 2011 +0100
@@ -123,8 +123,8 @@
<p>This scenario is concerned with the evolution of a crime statistics
file (referred to as e0) stored on a shared file system and which
journalists Alice, Bob, Charles, David, and Edith can share and
-edit. We now consider various events in the evolution of file (e0);
-events follow each other, unless specified otherwise.</p>
+edit. We consider various events in the evolution of file e0;
+events listed below follow each other, unless otherwise specified.</p>
@@ -141,7 +141,7 @@
</p>
<p>Event evt3: Charles emails (pe2) the contents of /share/crime.txt, as an
-attachment, which refer to as e4.
+attachment, which we refer to as e4.
</p>
<p>
@@ -164,7 +164,7 @@
<section>
<h3>Encoding using the Provenance Abstract Syntax Notation</h3>
-In this section, the example is encoded according to the Provenance data model (specified in section <a href="\data-model-concepts">concepts</a>), expressed in the Provenance Abstract Syntax Notation. Details about the Provenance Abstract Syntax Notation can be found in <a href="'#PASN-convention'">appendix</a>.
+In this section, the example is encoded according to the provenance data model (specified in section <a href="\data-model-concepts">concepts</a>) and expressed in the Provenance Abstract Syntax Notation. Details about the Provenance Abstract Syntax Notation can be found in <a href="#PASN-convention">appendix</a>.
<p>
Entities (construct described in <a href="#concept-Entity">Section Entity</a>). The file in its various forms and its copies are modelled as entities.
<pre>
@@ -179,7 +179,7 @@
</p>
-<p>The entities, as characterized, hold during intervals delimited by events. The following table lists all events and their corresponding validity events, where evt5 is considered to be the most recent event.
+<p>The entities, as characterized, hold during intervals delimited by events. The following table lists all entities and their corresponding validity intervals; evt5 is considered to be the most recent event.
<blockquote>
<table>
<tr><td>Entity</td><td>Interval</td></tr>
@@ -255,7 +255,7 @@
<p>
-Agents (construct described at <a href="#concept-Agent">Section Agent</a>): in the provenance model, the various users are represented as agents, themselves being a type of entity.
+Agents (construct described at <a href="#concept-Agent">Section Agent</a>): the various users are represented as agents, themselves being a type of entity.
<pre>
entity(e7, [ type: "Person", name: "Alice" ])
agent(e7)
@@ -305,7 +305,7 @@
<section >
<h2>About the Provenance Data Model</h2>
-<div class='issue'>The name of the language still has to be decided by the WG. This is <a href="http://www.w3.org/2011/prov/track/issues/31">ISSUE-31</a></div>
+<div class='issue'>The name of the data model still has to be decided by the WG. Current placeholder name is PIDM. This is <a href="http://www.w3.org/2011/prov/track/issues/31">ISSUE-31</a></div>
<div class='pending'>Data model vs Language. Misc comments raised at <a href="http://www.w3.org/2011/prov/track/issues/62">ISSUE-62</a></div>
@@ -487,7 +487,7 @@
</pre>
</p>
-<p>A given entity can be generated at most by one process execution.
+<p>A given entity can be generated at most by one process execution in the scope of a given <a href="#concept-Account">account</a>.
The rationale for this constraint is as follows.
If two process executions sequentially set different values to some attribute by means of two different generate events, then they generate distinct entities. Alternatively, for two process executions to generate an entity simultaneously, they would require some synchronization by which they agree the entity is released for use; the end of this synchronization would constitute the actual generation of the entity, but is performed by a single process execution. </p>
</p>
@@ -961,7 +961,7 @@
<h3>Provenance Container</h3>
-<p>A <dfn id="dfn-ProvenanceContainer">Provenance Container</dfn> is an identifiable wrapper for a set of PIDM constructs, including other containers, which allows for additional meta-information pertaining to these constructs to be expressed.</p>
+<p>A <dfn id="dfn-ProvenanceContainer">Provenance Container</dfn> is an identifiable wrapper for a set of PIDM constructs, which allows for additional meta-information pertaining to these constructs to be expressed. A provenance container MAY contain other provenance containers.</p>
<p>Such meta-information may be authorship, date of creation, justification for assertions, and cryptographic signature. </p>
@@ -987,7 +987,7 @@
<section id="concept-Account">
<h3>Account</h3>
-<p>An <dfn id="dfn-Account">Account</dfn> is a kind of provenance container forming a perspective on the world. </p>
+<p>An <dfn id="dfn-Account">Account</dfn> is a kind of provenance container forming a perspective on the world. </p>
<p>It is expected that an account offers some coherence and consistency from the viewpoint of its asserter, and in that sense is distinct from an arbitrary container. Hence, an account has a mandatory asserter.</p>
@@ -1004,6 +1004,8 @@
<section id="concept-Collection">
<h3>Collection</h3>
+
+<div class='note'>To be written in september.</div>
</section>
@@ -1014,6 +1016,43 @@
<h2>Shortcuts and extensions</h2>
<div class='issue'>There are a number of commonly used provenance relations in particular for the web that are not in the model. For practical use and uptake, it would be good to have definitions of these in the provenance model. These concepts should be defined in terms of the already existing "core" concepts. This is <a href="http://www.w3.org/2011/prov/track/issues/44">ISSUE-44</a>.</div>
+
+<div class='note'>Text copied from issue. Needs editing.</div>
+
+<section>
+<h3>isQuoteOf</h3>
+
+A quote. Specifically, it represents a characterized entity that is part of another characterized entity.
+
+A constrained version of isRevisionOf
+
+see http://daringfireball.net/2011/07/attribution_and_credit
+</section>
+
+<section>
+<h3>isAttributedTo</h3>
+
+Represents that a characterized identity was the product of an agent or can be attributed to that agent.
+
+A constrained version of isDerivedFrom
+
+see http://www.buzzmachine.com/2010/06/27/the-importance-of-provenance/
+</section>
+
+<section>
+<h3>isSummaryOf</h3>
+
+Represents a characterized entity that is a synopsis or abbreviation of another entity.
+
+constrained version of isDerivedFrom
+</section>
+
+<section>
+<h3>hasOriginalSource</h3>
+Represents a characterized entity in which another characterized entity first appeared.
+
+A constrained version of isDerivedFrom
+</section>
</section>
@@ -1044,7 +1083,7 @@
</section>
-<section id='PASN-convention'>>
+<section id='PASN-convention'>
<h3>Provenance Abstract Syntax Notation Conventions</h3>
<ul>
<li>Language constructs are represented as <b>name(arg0, arg1, ...)</b>, where the name of the construct occurs first, and is followed by its arguments.</li>