--- a/model/prov-dm.html Fri Nov 16 10:06:13 2012 +0000
+++ b/model/prov-dm.html Fri Nov 16 11:43:12 2012 +0000
@@ -259,13 +259,8 @@
if (myhref.startsWith("#")) {
- //Problem, this returns all span.secno elements, and concatenates their text
- // I shoul just get the first one
mysectionNumber=$(myhref).find('span.secno').first().text().trim();
-
-
-
console.log( "section ref for " + myhref + " " + mysectionNumber);
$(this).children('span').replaceWith(function(){return $('<span>').append("Section " + mysectionNumber)});
@@ -363,6 +358,7 @@
// and its maturity status
previousPublishDate: "2012-07-24",
previousMaturity: "LC",
+
// if there a publicly available Editor's Draft, this is the link
edDraftURI: "http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html",
@@ -478,12 +474,6 @@
</section>
<section id="sotd">
-<h4>Last Call</h4>
-<p>This is the fifth public release of the PROV-DM document.
-This is a Last Call Working Draft. The design is not expected to change significantly, going forward, and now is the key time for external review.</p>
-
-
-
<h4>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:
@@ -562,7 +552,7 @@
</ul>
-<p>This specification presents the concepts of the PROV Data Model, and
+<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>
@@ -596,7 +586,7 @@
<section class="informative" id="structure-of-this-document">
<h3>Structure of this Document</h3>
-<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="#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>
@@ -643,11 +633,11 @@
<div style="text-align: left;">
<table class="thinborder" style="margin-left: auto; margin-right: auto;">
<caption id="namespace-table">Prefix and Namespaces used in this specification</caption> <!-- Table 1-->
-<tr><td><a><b>prefix</b></a></td><td><b>namespace uri</b></td> <td><b>definition</b></td></tr>
+<tr><td><a><b>prefix</b></a></td><td><b>namespace IRI</b></td> <td><b>definition</b></td></tr>
<tr><td><a>prov</a></td><td>http://www.w3.org/ns/prov#</td><td>The PROV namespace (see <a class="section-ref" href="#term-NamespaceDeclaration"><span>TBD</span></a>)</td></tr>
<tr><td><a>xsd</a></td><td>http://www.w3.org/2000/10/XMLSchema#</td><td>XML Schema Namespace [[!XMLSCHEMA11-2]]</td></tr>
<tr><td><a>rdf</a></td><td>http://www.w3.org/1999/02/22-rdf-syntax-ns#</td><td>The RDF namespace [[!RDF-CONCEPTS]]</td></tr>
-<tr><td><a>(others)</a></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 [[!URI]]</td></tr>
+<tr><td><a>(others)</a></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 [[!IRI]]</td></tr>
</table>
</div>
@@ -662,7 +652,7 @@
<h1>PROV Overview</h1>
<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 core and extended provenance structure described below.
+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>
@@ -749,7 +739,7 @@
<div class="anexample conceptexample" id="entity-example">
-<p>An entity may be the document at URI <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>
+<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>
@@ -762,7 +752,7 @@
information processing activities
may for example move, copy, or duplicate digital entities;
physical activities can include
- driving a car from Boston to Cambridge or printing a book.
+ driving a car between two locations or printing a book.
</p>
@@ -1017,7 +1007,7 @@
<p><a class="section-ref" href="#core-structures"><span>TBD</span></a> shows that seven concepts are mapped to binary relations in the core of PROV. However, some advanced uses of these concepts cannot be captured by a binary relation, but require relations to be expanded to n-ary relations.</p>
-<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 'WasDerivedFrom' relationship. Applications are free to decide which level of granularity they want describe, and PROV gives them the way to do that.</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>
@@ -1064,7 +1054,7 @@
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-DM allows for
+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
@@ -1082,7 +1072,7 @@
<section id="section-prov-extended-approach-further-relations">
<h2>Further Relations</h2>
-<p>Finally, PROV-DM supports further relations that are not subtypes or expanded versions of existing relations (such as <a>specialization</a>, <a>alternate</a>).</p>
+<p>Finally, PROV supports further relations that are not subtypes or expanded versions of existing relations (such as <a>specialization</a>, <a>alternate</a>).</p>
</section>
@@ -1112,7 +1102,7 @@
<div class="anexample conceptexample" id="bundle-example">
<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 their provenance, which may help determine whether it can be trusted.
+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>
@@ -1252,7 +1242,7 @@
-<p>We paraphrase some PROV-DM descriptions, express them with the PROV-N notation, and depict them with a graphical illustration (see <a href="#prov-a-document1-top">Figure 2</a>).
+<p>We paraphrase some PROV descriptions, express them with the PROV-N notation, and depict them with a graphical illustration (see <a href="#prov-a-document1-top">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; ">
@@ -1300,7 +1290,7 @@
<p>
Provenance descriptions can be <em>illustrated</em> graphically. The illustration is not intended to represent all the details of the model, but it is intended to show the essence of a set of
-provenance descriptions. Therefore, it should not be seen as an alternate notation for expressing provenance.</p>
+provenance descriptions [[PROV-LAYOUT]]. 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>
@@ -1323,11 +1313,11 @@
must be preceded by a "publication request" to the Webmaster. The
very first version of a document must also be preceded by a
"transition request" to be approved by the W3C director. All working
-drafts are made available at a unique URI. In this scenario, we consider two successive versions of a given document, the policy according to which they were published, and the associated requests.
+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 URIs (some of which refer archived email messages, available to W3C Members).</p>
+We describe the kind of provenance record that the <a href="http://www.w3.org/Consortium">WWW Consortium</a> could keep for auditors to check that due processes are followed. All entities involved in this example are Web resources, with well-defined IRIs (some of which refer archived email messages, available to W3C 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>
@@ -1340,7 +1330,7 @@
<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-DM terminology.</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>
@@ -1400,7 +1390,7 @@
-<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 URIs, 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 URI scheme developed by W3C is particularly suited for expressing provenance of these documents, since each URI denotes a specific version of a document. It then becomes easy to relate the various versions with PROV-DM relations. We note that an Association is a ternary relation (represented by a multi-edge labeled wasAssociatedWith) from an activity to an agent and a plan.</p>
+<p> This simple example has shown a variety of PROV concepts, such as Entity, Agent, Activity, Usage, Generation, Derivation, and Association. In this example, it happens that all entities were already Web resources, with readily available IRIs, which we used. We note that some of the resources are public, whereas others have restricted access: provenance statements only make use of their identifiers. If identifiers do not pre-exist, e.g. for activities, then they can be generated, for instance <span class="name">ex:act2</span>, occurring in the namespace identified by prefix <span class="name">ex</span>. We note that the IRI scheme developed by W3C is particularly suited for expressing provenance of these documents, since each IRI denotes a specific version of a document. It then becomes easy to relate the various versions with PROV relations. We note that an Association is a ternary relation (represented by a multi-edge labeled wasAssociatedWith) from an activity to an agent and a plan.</p>
</section>
@@ -1495,7 +1485,6 @@
<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>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.
-Note that for simplicity, this table does not include collection-oriented relations.
Relation names appearing in bold correspond to the core structures introduced
in <a href="#core-structures">Section 2.1</a>.</p>
@@ -1505,7 +1494,7 @@
<caption id="relations-at-a-glance">PROV-DM Relations At a Glance</caption> <!-- Table 4 -->
<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td colspan="6">Object</td></tr>
<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">WasDerivedFrom</a><br><a>Revision</a><br><a>Quotation</a><br><a>PrimarySource</a></div><div class="component5-color"><a>AlternateOf</a><br><a>SpecializationOf</a></div></td><td class="component1-color"><a class="essential"
+<tr><td rowspan="3">Subject</td><td>Entity</td><td colspan="2"><div class="component2-color"><a class="essential">WasDerivedFrom</a><br><a>Revision</a><br><a>Quotation</a><br><a>PrimarySource</a></div><div class="component5-color"><a>AlternateOf</a><br><a>SpecializationOf</a></div><div class="component6-color"><a>HadMember</a></div></td><td class="component1-color"><a class="essential"
title="wasGeneratedBy">WasGeneratedBy</a><br><a
title="wasInvalidatedBy">WasInvalidatedBy</a></td><td class="component1-color" style="font-style: italic; "><a title="role">R</a><br><a title="time">T</a><br><a title="location">L</a><br></td><td class="component3-color" colspan="2"><a class="essential">WasAttributedTo</a></td></tr>
<tr><td>Activity</td><td class="component1-color"><a class="essential">Used</a><br><a>WasStartedBy</a><br><a>WasEndedBy</a></td><td class="component1-color" style="font-style: italic; "><a title="role">R</a><br><a title="time">T</a><br><a title="location">L</a><br></td><td colspan="2" class="component1-color"><a class="essential">WasInformedBy</a></td><td class="component3-color"><a class="essential">WasAssociatedWith</a></td><td class="component3-color" style="font-style: italic; "><a title="role">R</a><br></td></tr>
@@ -1523,7 +1512,7 @@
<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 associations correspond to the core structures introduced
+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>
@@ -1578,11 +1567,11 @@
-<tr class="component4-color"><td><a title="bundle">Bundle constructor</a></td><td><a title="dfn-bundle">bundle id description_1 ... description_n endBundle</a></td><td rowspan="2"><a href="#component5">Component 4: Bundles</a></td></tr>
+<tr class="component4-color"><td><a title="bundle">Bundle constructor</a></td><td><a title="dfn-bundle">bundle id description_1 ... description_n endBundle</a></td><td rowspan="2"><a href="#component4">Component 4: Bundles</a></td></tr>
<tr class="component4-color"><td class="provType"><a title="bundle">Bundle type</a></td><td><a title="bundle">... prov:type='prov:Bundle' ...</a></td></tr>
<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
-<tr class="component5-color"><td><a>Alternate</a></td><td><a title="alternateOf">alternateOf(alt1, alt2)</a></td><td rowspan="3"><a href="#component4">Component 5: Alternate</a></td></tr>
+<tr class="component5-color"><td><a>Alternate</a></td><td><a title="alternateOf">alternateOf(alt1, alt2)</a></td><td rowspan="3"><a href="#component5">Component 5: Alternate</a></td></tr>
<tr class="component5-color"><td><a>Specialization</a></td><td><a title="specializationOf">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>
@@ -1717,9 +1706,9 @@
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>, are created by an
+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 is available on port <span class="name">p1</span>, whereas the other is available on port <span class="name">p2</span>. The semantics of <span class="name">port</span> are application specific.
+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>
@@ -1951,7 +1940,9 @@
<li> an entity is time limited: e.g. the BBC news site on April 3rd, 2012;
<li> an entity attribute is changing: e.g. the traffic light changed from green to red.
</ul>
-<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 traffic light became red and therefore is regarded as a different entity to the green light.
+<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 (anohter entity with a fixed aspect red light).
</p>
@@ -2047,7 +2038,7 @@
-<p>The third component of PROV-DM is concerned with: <a title="derivation">derivations</a> of <a title="entity">entities</a> from other entities and derivation subtypes WasRevisionOf (<a>Revision</a>), WasQuotedFrom (<a>Quotation</a>), and HasPrimarySource (<a>Primary Source</a>).
+<p>The second component of PROV-DM is concerned with: <a title="derivation">derivations</a> of <a title="entity">entities</a> from other entities and derivation subtypes WasRevisionOf (<a>Revision</a>), WasQuotedFrom (<a>Quotation</a>), and HasPrimarySource (<a>Primary Source</a>).
<a href="#figure-component2">Figure 6</a> depicts the third component
with PROV core structures in the yellow area, including two classes
(<a>Entity</a>, <a>Activity</a>) and binary association WasDerivedFrom
@@ -2087,8 +2078,8 @@
<li><span class='attribute' id="derivation.generatedEntity">generatedEntity</span>: the identifier (<span class="name">e2</span>) of the entity generated by the derivation;</li>
<li><span class='attribute' id="derivation.usedEntity">usedEntity</span>: the identifier (<span class="name">e1</span>) of the entity used by the derivation;</li>
<li><span class='attribute' id="derivation.activity">activity</span>: an OPTIONAL identifier (<span class="name">a</span>) for the activity using and generating the above entities;</li>
-<li><span class='attribute' id="derivation.generation">generation</span>: an OPTIONAL identifier (<span class="name">g2</span>) for the generation involving the generated entity (<span class="name">e2</span>) and activity;</li>
-<li><span class='attribute' id="derivation.usage">usage</span>: an OPTIONAL identifier (<span class="name">u1</span>) for the usage involving the used entity (<span class="name">e1</span>) and activity;</li>
+<li><span class='attribute' id="derivation.generation">generation</span>: an OPTIONAL identifier (<span class="name">g2</span>) for the generation involving the generated entity (<span class="name">e2</span>) and activity (<span class="name">a</span>);</li>
+<li><span class='attribute' id="derivation.usage">usage</span>: an OPTIONAL identifier (<span class="name">u1</span>) for the usage involving the used entity (<span class="name">e1</span>) and activity (<span class="name">a</span>);</li>
<li><span class='attribute' id="derivation.attributes">attributes</span>: an OPTIONAL set (<span class="name">attrs</span>) of attribute-value pairs representing additional information about this derivation.</li>
</ul>
</div>
@@ -2164,7 +2155,7 @@
<p>A <dfn>quotation</dfn> relation
is a kind of <a>derivation</a> relation, for which an entity was derived from a preceding entity by copying, or "quoting", some or all of it.
-The type is of a quotation derivation is denoted by:
+The type of a quotation relation is denoted by:
<dfn title="dfn-prov:quotation" id="dfn-prov:quotation"><span class="name">prov:Quotation</span></dfn>.
PROV defines no quotation-specific attributes.
</p>
@@ -2219,7 +2210,7 @@
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 is of a primary source derivation is denoted by:
+The type of a primary source relation is denoted by:
<dfn title="dfn-prov:primary-source" id="dfn-prov:primary-source"><span class="name">prov:PrimarySource</span></dfn>.
PROV defines no attributes specific to primary source.
</p>
@@ -2253,9 +2244,9 @@
<section id="component3">
<h3>Component 3: Agents, Responsibility, and Influence</h3>
-<p>The second component of PROV-DM, depicted in <a href="#figure-component3">Figure 7</a>, is concerned with <a title="agent">agents</a> and the relations WasAttributedTo
+<p>The third component of PROV-DM, depicted in <a href="#figure-component3">Figure 7</a>, is concerned with <a title="agent">agents</a> and the relations WasAttributedTo
(<a>Attribution</a>), WasAssociatedWith (<a>Association</a>), ActedOnBehalfOf (<a>Delegation</a>), relating agents to entities, activities, and agents, respectively.
- Core structures are displayed in the yellow area and include three classes and three binary associations. Outside the yellow area, extended structures comprise UML association classes to express expanded n-ary relations, and subclasses <a>Plan</a>, <a>Person</a>, <a title="software-agent">SofwareAgent</a>, and <a>Organization</a>. The subclasses are marked by the UML stereotype "prov:type" to indicate that that these are valid values for the attribute <a href="#term-attribute-type">prov:type</a>
+ Core structures are displayed in the yellow area and include three classes and three binary associations. Outside the yellow area, extended structures comprise UML association classes to express expanded n-ary relations, and subclasses <a>Plan</a>, <a>Person</a>, <a title="software-agent">SofwareAgent</a>, and <a>Organization</a>. The subclasses are marked by the UML stereotype "prov:type" to indicate that that these are valid values for the attribute <a href="#term-attribute-type">prov:type</a>.
</p>
@@ -2348,7 +2339,7 @@
<p>
Revisiting the example of
<a class="section-ref" href="#section-example-one"><span>TBD</span></a>,
-we can ascribe <span class="name">tr:WD-prov-dm-20111215</span> to some agents without an explicit activity. The reserved attribute <span class="name">role</span> (see <a class="section-ref" href="#term-attribute-role"><span>TBD</span></a>) allows for role of the agent in the attribution to be specified.
+we can ascribe <span class="name">tr:WD-prov-dm-20111215</span> to some agents without an explicit activity.
<pre class="codeexample">
agent(ex:Paolo, [ prov:type='prov:Person' ])
agent(ex:Simon, [ prov:type='prov:Person' ])
@@ -2397,7 +2388,7 @@
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-DM: it can be generated by some activity and derived from other entities,
+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>
@@ -2425,7 +2416,7 @@
<div class="glossary-ref" data-ref="glossary-delegation"></div>
<p>For example, a
-student acted on behalf of his supervisor, who acted on behalf of the
+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
@@ -2801,7 +2792,7 @@
<p>
Note that <a title="alternateOf">alternateOf</a> is a necessarily very general
relationship that, in reasoning, only states that the two
-alternate entities fix different aspects of some common thing
+alternate entities respectively fix some aspects of some common thing
(possibly evolving over time), and so there is some relevant
connection between the provenance of the alternates. In a
specific application context, <a title="alternateOf">alternateOf</a>, or a subtype of it,
@@ -3084,7 +3075,7 @@
<tr><td><a title="empty collection"><span class="name">prov:EmptyCollection</span></a></td><td><a class="section-ref" href="#term-collection"><span>TBD</span></a></td><td><a>Entity</a></td></tr>
<tr><td><a title="organization"><span class="name">prov:Organization</span></a></td><td><a class="section-ref" href="#term-agent"><span>TBD</span></a></td><td><a>Agent</a></td></tr>
<tr><td><a title="person"><span class="name">prov:Person</span></a></td><td><a class="section-ref" href="#term-agent"><span>TBD</span></a></td><td><a>Agent</a></td></tr>
-<tr><td><a title="plan"><span class="name">prov:Plan</span></a></td> <td><a class="section-ref" href="#term-entity"><span>TBD</span></a></td><td><a>Entity</a></td></tr>
+<tr><td><a title="plan"><span class="name">prov:Plan</span></a></td><td><a class="section-ref" href="#term-entity"><span>TBD</span></a></td><td><a>Entity</a></td></tr>
<tr><td><a title="primary source"><span class="name">prov:PrimarySource</span></a></td><td><a class="section-ref" href="#term-primary-source"><span>TBD</span></a></td><td><a>Derivation</a></td></tr>
<tr><td><a title="Quotation"><span class="name">prov:Quotation</span></a></td><td><a class="section-ref" href="#term-quotation"><span>TBD</span></a></td><td><a>Derivation</a></td></tr>
<tr><td><a title="Revision"><span class="name">prov:Revision</span></a></td><td><a class="section-ref" href="#term-revision"><span>TBD</span></a></td><td><a>Derivation</a></td></tr>
@@ -3203,7 +3194,7 @@
</pre>
</div>
-<p>We note that PROV-DM <dfn title="time">time instants</dfn> are defined according to xsd:dateTime [[!XMLSCHEMA11-2]].</p>
+<p>We note that PROV <dfn title="time">time instants</dfn> are defined according to xsd:dateTime [[!XMLSCHEMA11-2]].</p>
<div class="anexample" id="anexample-time">
@@ -3220,7 +3211,7 @@
<section id="term-NamespaceDeclaration">
<h3>Namespace Declaration</h3>
-<p>A PROV-DM <dfn id="dfn-namespace">namespace</dfn> is identified by an IRI [[!IRI]]. In PROV-DM, attributes, identifiers, and values with <a title="qualified name">qualified names</a> as data type can be placed in a namespace using the mechanisms described in this specification. </p>
+<p>A <dfn id="dfn-namespace">namespace</dfn> is identified by an IRI [[!IRI]]. In PROV-DM, attributes, identifiers, and values with <a title="qualified name">qualified names</a> as data type can be placed in a namespace using the mechanisms described in this specification. </p>
<p>A <dfn id="dfn-namespaceDeclaration">namespace declaration</dfn> consists of a binding between a prefix and a namespace. Every qualified name with this prefix in the scope of this
@@ -3229,7 +3220,7 @@
<p>A <dfn id="dfn-defaultNamespaceDeclaration">default namespace declaration</dfn> consists of a namespace. Every un-prefixed qualified name
refers to default namespace declaration.</p>
-<p>The <dfn title="prov-namespace">PROV namespace</dfn> is identified by the URI <a href="http://www.w3.org/ns/prov#">http://www.w3.org/ns/prov#</a>.</p>
+<p>The <dfn title="prov-namespace">PROV namespace</dfn> is identified by the IRI <a href="http://www.w3.org/ns/prov#">http://www.w3.org/ns/prov#</a>.</p>
</section>
@@ -3339,8 +3330,8 @@
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 began its existence after the entity
-generation. A set of constraints have been defined for PROV-DM and
+activity that generated an entity started after the entity
+generation. A set of constraints have been defined for PROV and
can be found in a companion specification [[!PROV-CONSTRAINTS]].
They SHOULD be used by developers to compose provenance descriptions that are valid, and
by implementers of reasoning engines aiming to check whether provenance descriptions have problems. </li>
@@ -3348,19 +3339,14 @@
<li>
-<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, a URI 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-DM allows asserters to describe "<em>partial states</em>" of entities by means of attributes and associated values. Some further constraints apply to the use of these attributes, since the values associated with them are expected to remain unchanged for some period of time. The constraints associated to attributes allow provenance descriptions to be refined, they can also be found in the companion specification [[!PROV-CONSTRAINTS]].</p>
+<p> The example of <a href="#prov-dm-example">section 3</a> contains identifiers such as <span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111215">tr:WD-prov-dm-20111215</a></span>, which denotes a specific version of a technical report. On the other hand, an IRI such as <a href="http://www.w3.org/TR/prov-dm/">http://www.w3.org/TR/prov-dm/</a> denotes the latest version of a document. One needs to ensure that provenance descriptions for the latter resource remain valid as the resource state changes. </p>
+
+<p>To this end, PROV allows asserters to describe "<em>partial states</em>" of entities by means of attributes and associated values. Some further constraints apply to the use of these attributes, since the values associated with them are expected to remain unchanged for some period of time. The constraints associated to attributes allow provenance descriptions to be refined, they can also be found in the companion specification [[!PROV-CONSTRAINTS]].</p>
</li>
-<li>
-<p>The idea of bundling provenance descriptions is crucial to the PROV approach. Indeed, it allows multiple provenance perspectives to be provided for a given entity. It is also the mechanism by which provenance of provenance can be expressed.
-Descriptions in bundles are expected to satisfy constraints specified in the companion specification [[!PROV-CONSTRAINTS]].</p>
-</li>
-
</ul>
@@ -3627,6 +3613,22 @@
</p>
<p>
+The editors acknowledge valuable contributions from the following:
+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 PROV Working Group at the time of publication of this document were:
Ilkay Altintas (Invited expert),
--- a/model/provbib.js Fri Nov 16 10:06:13 2012 +0000
+++ b/model/provbib.js Fri Nov 16 11:43:12 2012 +0000
@@ -10,65 +10,71 @@
var provReferences = {
"PROV-DM":
- "Luc Moreau and Paolo Missier (eds.) Khalid Belhajjame, Reza B'Far, James Cheney, Sam Coppens, Stephen Cresswell, Yolanda Gil, Paul Groth, Graham Klyne, Tim Lebo, Jim McCusker, Simon Miles, James Myers, Satya Sahoo, and Curt Tilmes "+
+ "Luc Moreau and Paolo Missier (eds.) Khalid Belhajjame, Reza B'Far, James Cheney, Sam Coppens, Stephen Cresswell, Yolanda Gil, Paul Groth, Graham Klyne, Tim Lebo, Jim McCusker, Simon Miles, James Myers, Satya Sahoo, and Curt Tilmes. "+
"<a href=\"http://www.w3.org/TR/prov-dm/\"><cite>PROV-DM: The PROV Data Model</cite></a>. "+
- "2012, Working Draft. "+
- "URL: <a href=\"http://www.w3.org/TR/2012/CR-prov-dm-20121211/\">http://www.w3.org/TR/2012/CR-prov-dm-20121211/</a>",
+ "2012, Candidate Recommendation. "+
+ "URL: <a href=\"http://www.w3.org/TR/2012/CR-prov-dm-20121211/\">http://www.w3.org/TR/2012/CR-prov-dm-20121211/</a>.",
"PROV-SEM":
- "James Cheney "+
+ "James Cheney. "+
"<a href=\"http://www.w3.org/2011/prov/wiki/FormalSemanticsStrawman\"><cite>Formal Semantics Strawman</cite></a>. "+
"2011, Work in progress. "+
- "URL: <a href=\"http://www.w3.org/2011/prov/wiki/FormalSemanticsStrawman\">http://www.w3.org/2011/prov/wiki/FormalSemanticsStrawman</a>",
+ "URL: <a href=\"http://www.w3.org/2011/prov/wiki/FormalSemanticsStrawman\">http://www.w3.org/2011/prov/wiki/FormalSemanticsStrawman</a>.",
"PROV-PRIMER":
- "Yolanda Gil and Simon Miles (eds.) Khalid Belhajjame, Helena Deus, Daniel Garijo, Graham Klyne, Paolo Missier, Stian Soiland-Reyes, and Stephan Zednik "+
+ "Yolanda Gil and Simon Miles (eds.) Khalid Belhajjame, Helena Deus, Daniel Garijo, Graham Klyne, Paolo Missier, Stian Soiland-Reyes, and Stephan Zednik. "+
"<a href=\"http://www.w3.org/TR/2012/WD-prov-primer-20121211/\"><cite>Prov Model Primer</cite></a>. "+
"2012, Working Draft. "+
- "URL: <a href=\"http://www.w3.org/TR/2012/WD-prov-primer-20121211/\">http://www.w3.org/TR/2012/WD-prov-primer-20121211/</a>",
+ "URL: <a href=\"http://www.w3.org/TR/2012/WD-prov-primer-20121211/\">http://www.w3.org/TR/2012/WD-prov-primer-20121211/</a>.",
"PROV-O":
- "Timothy Lebo, Satya Sahoo and Deborah McGuinness (eds.) Khalid Belhajjame, James Cheney, David Corsar, Daniel Garijo, Stian Soiland-Reyes, Stephan Zednik, and Jun Zhao "+
+ "Timothy Lebo, Satya Sahoo and Deborah McGuinness (eds.) Khalid Belhajjame, James Cheney, David Corsar, Daniel Garijo, Stian Soiland-Reyes, Stephan Zednik, and Jun Zhao. "+
"<a href=\"http://www.w3.org/TR/2012/CR-prov-o-20121211/\"><cite>Provenance Formal Model</cite></a>. "+
- "2012, Working Draft. "+
- "URL: <a href=\"http://www.w3.org/TR/2012/CR-prov-o-20121211/\">http://www.w3.org/TR/2012/CR-prov-o-20121211/</a>",
+ "2012, Candidate Recommendation. "+
+ "URL: <a href=\"http://www.w3.org/TR/2012/CR-prov-o-20121211/\">http://www.w3.org/TR/2012/CR-prov-o-20121211/</a>.",
"PROV-CONSTRAINTS":
- "James Cheney, Paolo Missier, and Luc Moreau (eds.), Tom De Nies "+
+ "James Cheney, Paolo Missier, and Luc Moreau (eds.), Tom De Nies. "+
"<a href=\"http://www.w3.org/TR/2012/CR-prov-constraints-20121211/\"><cite>Constraints of the PROV Data Model</cite></a>. "+
- "2012, Working Draft. "+
- "URL: <a href=\"http://www.w3.org/TR/2012/CR-prov-constraints-20121211/\">http://www.w3.org/TR/2012/CR-prov-constraints-20121211/</a>",
+ "2012, Candidate Recommendation. "+
+ "URL: <a href=\"http://www.w3.org/TR/2012/CR-prov-constraints-20121211/\">http://www.w3.org/TR/2012/CR-prov-constraints-20121211/</a>.",
"PROV-N":
- "Luc Moreau and Paolo Missier (eds.) James Cheney, Stian Soiland-Reyes "+
+ "Luc Moreau and Paolo Missier (eds.) James Cheney, Stian Soiland-Reyes. "+
"<a href=\"http://www.w3.org/TR/2012/CR-prov-n-20121211/\"><cite>PROV-N: The Provenance Notation</cite></a>. "+
- "2012, Working Draft. "+
- "URL: <a href=\"http://www.w3.org/TR/2012/CR-prov-n-20121211/\">http://www.w3.org/TR/2012/CR-prov-n-20121211/</a>",
+ "2012, Candidate Recommendation. "+
+ "URL: <a href=\"http://www.w3.org/TR/2012/CR-prov-n-20121211/\">http://www.w3.org/TR/2012/CR-prov-n-20121211/</a>.",
"PROV-XML":
- "Hook Hua, Curt Tilmes, and Stephan Zednik (eds.) Luc Moreau "+
+ "Hook Hua, Curt Tilmes, and Stephan Zednik (eds.) Luc Moreau. "+
"<a href=\"http://www.w3.org/TR/2012/WD-prov-xml-20121211/\"><cite>PROV-XML: The PROV XML Schema</cite></a>. "+
- "2012, Working Draft. "+
- "URL: <a href=\"http://www.w3.org/TR/2012/WD-prov-xml-20121211/\">http://www.w3.org/TR/2012/WD-prov-xml-20121211/</a>",
+ "2012, Candidate Recommendation. "+
+ "URL: <a href=\"http://www.w3.org/TR/2012/WD-prov-xml-20121211/\">http://www.w3.org/TR/2012/WD-prov-xml-20121211/</a>.",
"PROV-OVERVIEW":
- "AUTHORS TBD "+
+ "AUTHORS TBD. "+
"<a href=\"http://www.w3.org/TR/2012/WD-prov-overview-20121211/\"><cite>PROV-OVERVIEW: The PROV Family of Documents</cite></a>. "+
"2012, Working Draft. "+
- "URL: <a href=\"http://www.w3.org/TR/2012/WD-prov-overview-20121211/\">http://www.w3.org/TR/2012/WD-prov-overview-20121211/</a>",
+ "URL: <a href=\"http://www.w3.org/TR/2012/WD-prov-overview-20121211/\">http://www.w3.org/TR/2012/WD-prov-overview-20121211/</a>.",
"PROV-AQ":
- "Graham Klyne and Paul Groth (eds.) Luc Moreau, Olaf Hartig, Yogesh Simmhan, James Meyers, Timothy Lebo, Khalid Belhajjame, and Simon Miles "+
+ "Graham Klyne and Paul Groth (eds.) Luc Moreau, Olaf Hartig, Yogesh Simmhan, James Meyers, Timothy Lebo, Khalid Belhajjame, and Simon Miles. "+
"<a href=\"http://www.w3.org/TR/2012/WD-prov-aq-20120619/\"><cite>Provenance Access and Query</cite></a>. "+
"2012, Working Draft. "+
- "URL: <a href=\"http://www.w3.org/TR/2012/WD-prov-aq-20120619/\">http://www.w3.org/TR/2012/WD-prov-aq-20120619/</a>",
+ "URL: <a href=\"http://www.w3.org/TR/2012/WD-prov-aq-20120619/\">http://www.w3.org/TR/2012/WD-prov-aq-20120619/</a>.",
"PROV-MENTION":
- "Tim Lebo and Luc Moreau"+
+ "Tim Lebo and Luc Moreau. "+
"<a href=\"http://www.w3.org/TR/2012/WD-prov-mention-20121211/\"><cite>MENTION</cite></a>. "+
"2012, Working Draft. "+
- "URL: <a href=\"http://www.w3.org/TR/2012/WD-prov-mention-20121211/\">http://www.w3.org/TR/2012/WD-prov-mention-20121211/</a>",
+ "URL: <a href=\"http://www.w3.org/TR/2012/WD-prov-mention-20121211/\">http://www.w3.org/TR/2012/WD-prov-mention-20121211/</a>.",
+
+ "PROV-LAYOUT":
+ "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>.",