--- a/model/glossary.html Wed Jun 27 10:09:58 2012 +0100
+++ b/model/glossary.html Wed Jun 27 10:10:26 2012 +0100
@@ -203,7 +203,7 @@
</span>
<span class="glossary" id="glossary-specialization">
-An entity that is a <dfn id="concept-specialization">specialization</dfn> of another shares all aspects of the latter, and additionally presents more specific aspects of the same thing as the latter. In particular, the lifetime of the specialized entity contains that of any specialization.
+An entity that is a <dfn id="concept-specialization">specialization</dfn> of another shares all aspects of the latter, and additionally presents more specific aspects of the same thing as the latter. In particular, the lifetime of the entity being specialized contains that of any specialization.
</span>
<span class="glossary" id="glossary-qualifiedName">
--- a/model/glossary.js Wed Jun 27 10:09:58 2012 +0100
+++ b/model/glossary.js Wed Jun 27 10:10:26 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/79762cbb0988/model/glossary.html';
+glossary_hg='http://dvcs.w3.org/hg/prov/file/a94341fd52b4/model/glossary.html';
glossary_string=
' ' +
'<html> ' +
@@ -184,12 +184,9 @@
'</span> ' +
'</html> ' +
' ' +
-'<span class="glossary" id="glossary-trace"> ' +
-'<dfn id="concept-trace">Trace</dfn> is the ability to link back an entity to another by means of derivation or responsibility relations, possibly repeatedly traversed. ' +
+'<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. ' +
'</span> ' +
-'<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. ' +
-'</span> ' +
' ' +
' ' +
'<span class="glossary" id="glossary-insertion"> ' +
@@ -213,7 +210,7 @@
'</span> ' +
' ' +
'<span class="glossary" id="glossary-specialization"> ' +
-'An entity that is a <dfn id="concept-specialization">specialization</dfn> of another shares all aspects of the latter, and additionally presents more specific aspects of the same thing as the latter. In particular, the lifetime of the specialized entity contains that of any specialization. ' +
+'An entity that is a <dfn id="concept-specialization">specialization</dfn> of another shares all aspects of the latter, and additionally presents more specific aspects of the same thing as the latter. In particular, the lifetime of the entity being specialized contains that of any specialization. ' +
'</span> ' +
' ' +
'<span class="glossary" id="glossary-qualifiedName"> ' +
--- a/model/prov-dm.html Wed Jun 27 10:09:58 2012 +0100
+++ b/model/prov-dm.html Wed Jun 27 10:10:26 2012 +0100
@@ -1461,7 +1461,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>WasRevisionOf</a><br><a>WasQuotedFrom</a><br><a>HadPrimarySource</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"
+<tr><td rowspan="3">Subject</td><td>Entity</td><td colspan="2"><div class="component2-color"><a class="essential">WasDerivedFrom</a><br><a>WasRevisionOf</a><br><a>WasQuotedFrom</a><br><a>HadPrimarySource</a></div><div class="component5-color"><a>AlternateOf</a><br><a>SpecializationOf</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>
@@ -1513,7 +1513,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>
@@ -2791,14 +2791,19 @@
<div class="attributes" id="attributes-specialization">A <dfn title="specializationOf">specialization</dfn> relation<span class="withPn">, written <span class="pnExpression">specializationOf(infra, supra, b)</span> in PROV-N,</span> has:
<ul>
-<li><span class='attribute' id="specialization.specificEntity">specificEntity</span>: an identifier (<span class="name">infra</span>) of the specialized entity;</li>
+<li><span class='attribute' id="specialization.specificEntity">specificEntity</span>: an identifier (<span class="name">infra</span>)
+of the entity that is a specialization of the general entity (<span class="name">supra</span>);</li>
<li><span class='attribute' id="specialization.generalEntity">generalEntity</span>: an identifier (<span class="name">supra</span>) of the entity that is being specialized.</li>
-<li><span class='attribute' id="specialization.bundle">bundle</span>: an OPTIONAL identifier (<span class="name">b</span>) of a bundle that contains a description of entity <span class="name">supra</span>, and that constitutes an additional aspect of the specialized entity <span class="name">infra</span>.</li>
+<li><span class='attribute' id="specialization.bundle">bundle</span>: an OPTIONAL identifier (<span class="name">b</span>) of a bundle that contains a description of <span class="name">supra</span> and further constitutes one additional aspect presented by <span class="name">infra</span>.</li>
</ul>
</div>
<div class="note">
The attribute <a href="#specialization.bundle">bundle</a> is a <b>FEATURE AT RISK</b>.
+If this attribute is removed, then Examples
+<a href="#anexample-specialization-rating" class="anexample-ref"><span>Example REF</span></a> and
+<a href="#aexample-specialization-viz" class="anexample-ref"><span>Example REF</span></a>
+will be removed from the specification.
</div>
<div class="anexample" id="anexample-specialization">
@@ -2813,11 +2818,81 @@
</div>
-
-
-<!--
-<p>To promote take up of these relations, it is not specified whether they are transitive or symmetric. We anticipate that applications will specialize these relations according to their needs. </p>
--->
+<p>The following two examples illustrate the use of the <a href="#specialization.bundle">bundle attribute</a> in a <a>specialization</a> relation. The descriptions in a bundle allow
+an entity to be interpreted in
+domain-specific manner. <a href="#anexample-specialization-rating" class="anexample-ref"><span>Example REF</span></a> illustrates how the performance of an agent can be determined.
+</p>
+
+
+<div class="anexample" id="anexample-specialization-rating">
+<p>In the following example, two bundles <span class="name">ex:run1</span> and <span class="name">ex:run2</span> refer to an agent <span class="name">ex:Bob</span> that controlled two activities <span class="name">ex:a1</span> and <span class="name">ex:a2</span>. </p>
+
+<pre class="codeexample">
+bundle ex:run1
+ activity(ex:a1, 2011-11-16T16:00:00,2011-11-16T17:00:00) //duration: 1hour
+ wasAssociatedWith(ex:a1,ex:Bob,[prov:role="controller"])
+endBundle
+
+bundle ex:run2
+ activity(ex:a2, 2011-11-17T10:00:00,2011-11-17T17:00:00) //duration: 7hours
+ wasAssociatedWith(ex:a2,ex:Bob,[prov:role="controller"])
+endBundle
+</pre>
+<p>A performance rating tool reads these bundles, and rates the performance of the agent described in these bundles. The performance rating tool creates a new bundle <span class="name">tool:analysis01</span> containing the following. A new agent <span class="name">tool:Bob-2011-11-16</span> is declared as a contextualization of <span class="name">ex:Bob</span> as described in remote bundle <span class="name">ex:run1</span>, and likewise for <span class="name">tool:Bob-2011-11-17</span> with respect to <span class="name">ex:run2</span>. The tool adds a domain-specific performance attribute to each of these specialized entities as follows: the performance of the agent in the first bundle is judged to be good since the duration of <span class="name">ex:a1</span> is one hour, whereas it is judged to be bad in the second bundle since <span class="name">ex:a2</span>'s duration is seven hours.
+
+<pre class="codeexample">
+bundle tool:analysis01
+ agent(tool:Bob-2011-11-16, [perf:rating="good"])
+ specializationOf(tool:Bob-2011-11-16, ex:Bob, ex:run1)
+
+ agent(tool:Bob-2011-11-17, [perf:rating="bad"])
+ specializationOf(tool:Bob-2011-11-17, ex:Bob, ex:run2)
+endBundle
+</pre>
+</div>
+
+
+<div class="anexample" id="aexample-specialization-viz">
+<p>Consider the following bundle of descriptions, in which derivation and generations have been identified.
+<pre class="codeexample">
+bundle obs:bundle1
+ entity(ex:report1, [prov:type="report", ex:version=1])
+ wasGeneratedBy(ex:g1; ex:report1,-,2012-05-24T10:00:01)
+ entity(ex:report2, [prov:type="report", ex:version=2])
+ wasGeneratedBy(ex:g2; ex:report2,-,2012-05-25T11:00:01)
+ wasDerivedFrom(ex:report2, ex:report1)
+endBundle
+entity(obs:bundle1, [ prov:type='prov:Bundle' ])
+wasAttributedTo(obs:bundle1, ex:observer01)
+</pre>
+Bundle <span class="name">obs:bundle1</span> is rendered by a visualisation tool. It may useful for the tool configuration for this bundle to be shared along with the provenance descriptions, so that other users can render provenance as it was originally rendered. The original bundle obviously cannot be changed. However, one can create a new bundle, as follows.
+<pre class="codeexample">
+bundle tool:bundle2
+ entity(tool:bundle2, [ prov:type='viz:Configuration', prov:type='prov:Bundle' ])
+ wasAttributedTo(tool:bundle2, viz:Visualizer)
+
+ entity(tool:report1, [viz:color="orange"])
+ specializationOf(tool:report1, obs:bundle1, ex:report1)
+
+ entity(tool:report2, [viz:color="blue"])
+ specializationOf(tool:report2, obs:bundle1, ex:report2)
+endBundle
+</pre>
+
+<p>In bundle <span class="name">tool:bundle2</span>, the prefix <span class="name">viz</span> is used for naming visualisation-specific attributes, types or values.</p>
+
+<p>Bundle <span class="name">tool:bundle2</span> is given type <span class="name">viz:Configuration</span> to indicate that it consists of descriptions that pertain to the configuration of the visualisation tool. This type attribute can be used for searching bundles containing visualization-related descriptions.
+</p>
+
+<p>The visualisation tool
+ created new identifiers <span class="name">tool:report1</span> and
+<span class="name">tool:report2</span>.
+They denote entities which are specializations of <span class="name">ex:report1</span> and <span class="name">ex:report2</span>, described in bundle <span class="name">obs:bundle1</span>, with visualization attribute for the color to be used when rendering these entities. </p>
+
+</div>
+
+
+
@@ -2867,6 +2942,7 @@
</section>
+<!--
<section id="term-contextualization">
<h4>Contextualization</h4>
@@ -2882,12 +2958,10 @@
domain-specific manner. The contextualization of this entity with respect to this bundle offers the opportunity to specialize it according to some domain-specific interpretation.
</p>
-<!--
<p>A contextualization of an entity in a bundle implies the specialization of this entity by "fixing" the bundle that it is in.
</p>
--->
<p>A contextualization of an entity in a remote bundle results in a specialization of this entity with extra fixed aspects, including the remote bundle that it is described in.
@@ -2902,7 +2976,7 @@
</div>
-<div class="anexample" id="anexample-contextualization1">
+<div class="anexample" id="anexample-specialization-rating">
<p>In the following example, two bundles <span class="name">ex:run1</span> and <span class="name">ex:run2</span> refer to an agent <span class="name">ex:Bob</span> that controlled two activities <span class="name">ex:a1</span> and <span class="name">ex:a2</span>. </p>
<pre class="codeexample">
@@ -2930,7 +3004,7 @@
</div>
-<div class="anexample" id="aexample-contextualization-viz">
+<div class="anexample" id="aexample-specialization-viz">
<p>Consider the following bundle of descriptions, in which derivation and generations have been identified.
<pre class="codeexample">
bundle obs:bundle1
@@ -2973,6 +3047,8 @@
</section>
+-->
+
</section>
<section id="component6">
Binary file model/uml/component3.png has changed
Binary file model/uml/component5.png has changed
Binary file model/uml/component6.png has changed