--- a/model/glossary.html Thu Jun 28 10:42:33 2012 +0100
+++ b/model/glossary.html Thu Jun 28 11:12:28 2012 +0100
@@ -178,7 +178,7 @@
</html>
<span class="glossary" id="glossary-influence">
-<dfn id="concept-influence">Influence</dfn> is the capacity an entity, activity, or agent to have an effect on the character, development, or behavior of another by means of usage, start, end, generation, invalidation, derivation, attribution, association, or delegation.
+<dfn id="concept-influence">Influence</dfn> is the capacity an entity, activity, or agent to have an effect on the character, development, or behavior of another by means of usage, start, end, generation, invalidation, communication, derivation, attribution, association, or delegation.
</span>
@@ -297,6 +297,12 @@
</span>
+<span class="glossary" id="glossary-mention">
+An entity that is a <dfn id="concept-mention">mention</dfn> of another entity presents all
+aspects of the latter as per the latter's description in another bundle (referred to as remote bundle), and therefore constitutes a particular case of <a>specialization</a> of the latter entity.
+</span>
+
+
<span class="glossary" id="glossary-contextualization2">
Something that is a <dfn id="concept-contextualiation2">contextualization</dfn> of another presents all aspects of the
latter as per its description in a bundle, and therefore constitutes a <a>specialization</a> of the latter.
--- a/model/glossary.js Thu Jun 28 10:42:33 2012 +0100
+++ b/model/glossary.js Thu Jun 28 11:12:28 2012 +0100
@@ -3,7 +3,7 @@
// with <script src="glossary.js" class="remove"></script>
//Insert glossary definitions with the following
// <div class="glossary-ref" ref="glossary-generation"></div>
-glossary_hg='http://dvcs.w3.org/hg/prov/file/a94341fd52b4/model/glossary.html';
+glossary_hg='http://dvcs.w3.org/hg/prov/file/9dc462fee240/model/glossary.html';
glossary_string=
' ' +
'<html> ' +
@@ -185,7 +185,7 @@
'</html> ' +
' ' +
'<span class="glossary" id="glossary-influence"> ' +
-'<dfn id="concept-influence">Influence</dfn> is the capacity an entity, activity, or agent to have an effect on the character, development, or behavior of another by means of usage, start, end, generation, invalidation, derivation, attribution, association, or delegation. ' +
+'<dfn id="concept-influence">Influence</dfn> is the capacity an entity, activity, or agent to have an effect on the character, development, or behavior of another by means of usage, start, end, generation, invalidation, communication, derivation, attribution, association, or delegation. ' +
'</span> ' +
' ' +
' ' +
@@ -304,6 +304,12 @@
'</span> ' +
' ' +
' ' +
+'<span class="glossary" id="glossary-mention"> ' +
+'An entity that is a <dfn id="concept-mention">mention</dfn> of another entity presents all ' +
+'aspects of the latter as per the latter\'s description in another bundle (referred to as remote bundle), and therefore constitutes a particular case of <a>specialization</a> of the latter entity. ' +
+'</span> ' +
+' ' +
+' ' +
'<span class="glossary" id="glossary-contextualization2"> ' +
'Something that is a <dfn id="concept-contextualiation2">contextualization</dfn> of another presents all aspects of the ' +
'latter as per its description in a bundle, and therefore constitutes a <a>specialization</a> of the latter. ' +
--- a/model/prov-dm.html Thu Jun 28 10:42:33 2012 +0100
+++ b/model/prov-dm.html Thu Jun 28 11:12:28 2012 +0100
@@ -1091,7 +1091,7 @@
<p>
<span class="glossary-ref" data-ref="glossary-collection" data-withspan="true"></span> Many different types of collections exist, such as a <em>sets</em>, <em>dictionaries</em>, or <em>lists</em>.
-Using Collections, one can express the provenance of the collection itself in addition to that of the members. The provenance of the collection is the history of all insertions into and deletions from the collection. This may be complemented by explicit membership statements which enumerate the contents of the collection. </p>
+Using Collections, one can express the provenance of the collection itself in addition to that of the members. </p>
<div class="anexample conceptexample" id="collection-example">
<p>
@@ -1124,9 +1124,9 @@
<tr><td style=" padding: 8px;">1</td><td style="text-align: left;">Entities and Activities</td><td>✔</td><td><a href="#section-entity-activity">2.1.1</a></td><td><a href="#component1">5.1</a></td><td style="text-align: left;">about entities and activities, and their interrelations</td></tr>
<tr><td>2</td><td style="text-align: left;">Derivation</td><td>✔</td><td><a href="#section-derivation">2.1.2</a></td><td><a href="#component3">5.2</a></td><td style="text-align: left;">about derivations and its subtypes</td></tr>
<tr><td>3</td><td style="text-align: left;">Agent and Responsibility</td><td>✔</td><td><a href="#section-agents-attribution-association-delegation">2.1.3</a></td><td><a href="#component2">5.3</a></td><td style="text-align: left;">about agents and concepts ascribing responsibility to them</td></tr>
-<tr><td>4</td><td style="text-align: left;">Alternate</td><td></td><td>—</td><td><a href="#component4">5.4</a></td><td style="text-align: left;">about relations linking entities referring the same thing</td></tr>
-<tr><td>5</td><td style="text-align: left;">Bundles</td><td></td><td><a href="#section-provenance-of-provnance">2.2.2</a></td><td><a href="#component5">5.5</a></td><td style="text-align: left;">about bundles, a mechanism to support provenance of provenance</td></tr>
-<tr><td>6</td><td style="text-align: left;">Collections</td><td></td><td><a href="#section-collections">2.2.3</a></td><td><a href="#component6">5.6</a></td><td style="text-align: left;">about collections and concepts capturing their transformation, such as insertion and removal</td></tr>
+<tr><td>4</td><td style="text-align: left;">Bundles</td><td></td><td><a href="#section-provenance-of-provnance">2.2.2</a></td><td><a href="#component4">5.4</a></td><td style="text-align: left;">about bundles, a mechanism to support provenance of provenance</td></tr>
+<tr><td>5</td><td style="text-align: left;">Alternate</td><td></td><td>—</td><td><a href="#component5">5.5</a></td><td style="text-align: left;">about relations linking entities referring the same thing</td></tr>
+<tr><td>6</td><td style="text-align: left;">Collections</td><td></td><td><a href="#section-collections">2.2.3</a></td><td><a href="#component6">5.6</a></td><td style="text-align: left;">about collections</td></tr>
</table>
</div>
@@ -1432,7 +1432,7 @@
<li><b>Component 3: agents, responsibility, and influence.</b> The third component consists of agents and concepts ascribing responsibility to agents.</li>
<li><b>Component 4: bundles.</b> The fourth component is concerned with bundles, a mechanism to support provenance of provenance.</li>
<li><b>Component 5: alternate.</b> The fifth component consists of relations linking entities referring to the same thing. </li>
-<li><b>Component 6: collections.</b> The sixth component is about collections and concepts capturing their transformation, such as insertion and removal. </li>
+<li><b>Component 6: collections.</b> The sixth component is about collections. </li>
</ul>
</div>
@@ -1465,7 +1465,7 @@
<caption id="relations-at-a-glance">Table 4: PROV-DM Relations At a Glance</caption>
<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><br><a>ContextualizationOf</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; ">R<br>T<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; ">R<br>T<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; ">R<br></td></tr>
@@ -1517,7 +1517,7 @@
<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
<tr class="component5-color"><td><a>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>Specialization</a></td><td><a title="specializationOf">specializationOf(sub, super,bundle)</a></td></tr>
-<!--<tr class="component5-color"><td><a>Contextualization</a></td><td><a title="contextualizationOf">contextualizationOf(i2, i1,bundle)</a></td></tr> -->
+<tr class="component5-color"><td><a>Contextualization</a></td><td><a title="contextualizationOf">contextualizationOf(i2, i1,bundle)</a></td></tr>
<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
@@ -2343,7 +2343,7 @@
wasAssociatedWith(ex:a, ex:ag2, ex:wf, [ prov:role="designer", ex:context="project1" ])
entity(ex:wf, [ prov:type='prov:Plan' ,
ex:label="Workflow 1",
- ex:url="http://example.org/workflow1.bpel" %% xsd:anyURI ])
+ 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,
for instance.
@@ -2442,7 +2442,7 @@
</ul>
<p>
-<a>Usage</a>, <a>start</a>, <a>end</a>, <a>generation</a>, <a>invalidation</a>, <a>derivation</a>, <a>attribution</a>, <a>association</a>, and <a>delegation</a> are particular cases of influence. It is RECOMMENDED to adopt these more specific relations when writing provenance description. It is anticipated that the <a>Influence</a> relation may be useful to express queries over provenance information.
+<a>Usage</a>, <a>start</a>, <a>end</a>, <a>generation</a>, <a>invalidation</a>, <a>communication</a>, <a>derivation</a>, <a>attribution</a>, <a>association</a>, and <a>delegation</a> are particular cases of influence. It is RECOMMENDED to adopt these more specific relations when writing provenance descriptions. It is anticipated that the <a>Influence</a> relation may be useful to express queries over provenance information.
</p>
<div class="anexample">
@@ -2951,7 +2951,7 @@
</section>
-<!--
+
<section id="term-contextualization">
<h4>Contextualization</h4>
@@ -3056,7 +3056,7 @@
</section>
--->
+
</section>
@@ -3400,14 +3400,31 @@
The normative definitions of these datatypes are provided by their respective specifications.
</p>
+<!--
<p>PROV accepts the types that RDF enumerates in
its own specification [[!RDF-CONCEPTS]]. New RDF releases
[[RDF-CONCEPTS11]] may extend the list of datatypes, and PROV would
naturally accept those too.</p>
-
-<div class="note">
-<a href="http://www.w3.org/2011/prov/meeting/2012-06-22#resolution_7">F2F3 Resolution 7</a>: The working group wants to fix the dependency to specific version of RDF</a>
-</div>
+-->
+
+
+
+<p id="conformance-to-rdf-datatypes"><b>Conformance to RDF Datatypes</b> As of the publication of this document, RDF 1.1 Concepts and Abstract Syntax is not yet a W3C Recommendation (see <a href="http://www.w3.org/TR/rdf11-concepts/">http://www.w3.org/TR/rdf11-concepts/</a> for the latest version).
+Both the PROV Working Group and the RDF Working Group are confident that there will be only minor changes before it becomes a W3C Recommendation. In order to take advantage of the anticipated corrections and new features sooner, while also providing stability in case the specification does not advance as expected, conformance to PROV as it relates to RDF Datatypes is defined as follows:</p>
+
+<ul>
+<li>If RDF 1.1 Concepts and Abstract Syntax becomes a W3C Recommendation, all references in PROV to
+RDF Concepts and Abstract Syntax will be normative references to the 1.1 Recommendation.
+<li>Until that time, references in PROV to RDF Concepts and Abstract Syntax features operate as follows:
+<ul>
+<li> If RDF 1.0 defines the features, then the reference is normative to the 1.0 definition [[!RDF-CONCEPTS]];</li>
+<li>otherwise, the feature is optional in PROV and the reference is informative only.</li>
+</ul>
+</ul>
+<p>This "change in normative reference" is effective as of the publication of RDF 1.1 as a W3C Recommendation. However, W3C expects to publish a new edition of PROV once RDF 1.1 becomes a Recommendation to update the reference explicitly.</p>
+
+
+
<!--
Binary file model/uml/component1.png has changed