--- a/model/prov-dm.html Tue Oct 16 15:11:47 2012 +0100
+++ b/model/prov-dm.html Tue Oct 16 15:16:44 2012 +0100
@@ -2788,143 +2788,6 @@
</section>
-<!-- <section id="term-hasProvenanceIn">
-
-<h3>Provenance Locator</h3>
-
-
-In <a href="#anexample-provenance-of-provenance" class="anexample-ref"><span>Example REF</span></a>, we initially presented a scenario involving two entities <span class="name">report1</span> and <span class="name">report2</span>, and showed how their descriptions can be organized into two bundles. There is no explicit indication that the second bundle "is a continuation" of the description offered by the first bundle. Given that bundles may be retrieved separately [[PROV-AQ]], it is not obvious for a provenance consumer to navigate descriptions across bundles. To aid consumers,
- Alice may wish to express that there is further provenance information about <span class="name">report1</span> in bundle <span class="name">bob:bundle1</span>. To this end, PROV introduces the notion of provenance locator, inspired by [[PROV-AQ]].
-
-
-<p><div class="glossary-ref" data-ref="glossary-provenance-locator"></div>
-
-<p>
-
-
-<div class="attributes" id="attributes-hasProvenanceIn">
-A <dfn title="hasProvenanceIn">provenance locator</dfn>,
-written
-<span class="pnExpression">hasProvenanceIn(id, subject, bundle, target, attrs)</span>, has:
-<ul>
-<li><span class='attribute' id="prov.locator.id">id</span>: an identifier for a provenance locator; </li>
-<li><span class='attribute' id="prov.locator.subject">subject</span>: an identifier denoting something (entity, activity, agent, or relation instance);</li>
-<li><span class='attribute' id="prov.locator.bundle">bundle</span>: an OPTIONAL identifier (<span class="name">bundle</span>) for a bundle;
-<li><span class='attribute' id="prov.locator.target">target</span>: an OPTIONAL identifier (<span class="name">target</span>) denoting something described in another set of descriptions (referred to as <a href="http://www.w3.org/TR/prov-aq/#dfn-target-uri">Target-URI</a> in [[PROV-AQ]]);
-<li><span class='attribute' id="prov.locator.attributes">attributes</span>: an OPTIONAL set (<span class="name">attrs</span>) of attribute-value pairs representing additional information about this locator; it optionally includes
-<a href="#term-attribute-service-uri"><span class="name">prov:service-uri</span></a>
-or
-<a href="#term-attribute-provenance-uri"><span class="name">prov:provenance-uri</span></a>.</li>
-</ul>
-<p>If the target is not specified, it is assumed that target is the same identifier as subject.
-</div>
-
-<p>When the subject and optional target denote entities,
-a provenance locator not only provides a <em>located context</em>, but it also expresses an <a>alternate</a> relation between the entity denoted by <span class="name">subject</span> and the entity described in the located context. This is an alternate since the entity denoted by <span class="name">subject</span> in the current context presents other aspects than the entity in the located one.</p>
-
-<div class="anexample" id="anexample-provenance-locator">
-<p>According to the following provenance locator, provenance descriptions about <span class="name">ex:report1</span> can be found in bundle <span class="name">bob:bundle1</span>.</p>
-<pre class="codeexample">
-hasProvenanceIn(ex:report1, bob:bundle1, -)
-</pre>
-<p>According to the following provenance locator, provenance descriptions about <span class="name">ex:report1</span> can be found in bundle <span class="name">bob:bundle1</span>, which is available from the provenance service identified by the provided URI.</p>
-<pre class="codeexample">
-hasProvenanceIn(ex:report1, bob:bundle1, -, [ prov:service-uri="http://example.com/service" %% xsd:anyURI ])
-</pre>
-</div>
-
-
-<div class="anexample" id="anexample-provenance-locator2">
-<p>Let us again consider the same scenario involving two entities <span class="name">ex:report1</span> and <span class="name">ex:report2</span>.</p>
-<p>The first bundle can be expressed with all Bob's observations about the creation of <span class="name">ex:report1</span>.
-</p>
-<pre class="codeexample">
-bundle bob:bundle4
- entity(ex:report1, [ prov:type="report", ex:version=1 ])
- wasGeneratedBy(ex:report1, -, 2012-05-24T10:00:01)
-endBundle
-</pre>
-
-<p>Likewise, Alice's observation about the derivation of <span class="name">ex:report2</span> from <span class="name">ex:report1</span>, is expressed in a separate bundle.</p>
-<pre class="codeexample">
-bundle alice:bundle5
- entity(ex:report1)
- hasProvenanceIn(ex:report1, bob:bundle4, -)
- entity(ex:report2, [ prov:type="report", ex:version=2 ])
- wasGeneratedBy(ex:report2, -, 2012-05-25T11:00:01)
- wasDerivedFrom(ex:report2, ex:report1)
-endBundle
-</pre>
-<p>In bundle <span class="name">alice:bundle5</span>, there is a description for entity <span class="name">ex:report1</span>, and
-a provenance locator pointing to bundle <span class="name">bob:bundle4</span>.
-The locator indicates that some provenance description for <span class="name">ex:report1</span> can be found in bundle <span class="name">bob:bundle4</span>. The purpose of the locator is twofold. First, it allows for <a href="http://www.w3.org/TR/prov-aq/#incremental-provenance-retrieval">incremental navigation</a> of provenance [[PROV-AQ]]. Second, it makes entity <span class="name">ex:report1</span> described in <span class="name">alice:bundle5</span> an <a>alternate</a> of <span class="name">ex:report1</span> described in <span class="name">bob:bundle4</span>.
-</p>
-</div>
-
-
-<div class="anexample" id="anexample-provenance-locator3">
-<p>Alternatively, Alice may have decided to use a different identifier for <span class="name">ex:report1</span>.</p>
-<pre class="codeexample">
-bundle alice:bundle6
- entity(alice:report1)
- hasProvenanceIn(alice:report1, bob:bundle4, ex:report1)
- entity(ex:report2, [ prov:type="report", ex:version=2 ])
- wasGeneratedBy(ex:report2, -, 2012-05-25T11:00:01)
- wasDerivedFrom(ex:report2, alice:report1)
-endBundle
-</pre>
-<p>Alice can specify the <a href="#prov.locator.target">target</a> in the provenance locator to be <span class="name">ex:report1</span>.
-With such a statement, Alice states that provenance information about <span class="name">alice:report1</span> can be found in bundle
-<span class="name">bob:bundle4</span> under the name <span class="name">ex:report1</span>. In effect, <span class="name">alice:report1</span> and <span class="name">ex:report1</span> are declared to be alternate.</p>
-</div>
-
-<div class="anexample" id="aexample-note">
-<p>Consider the following bundle of descriptions, in which derivation and generations have been identified.
-<pre class="codeexample">
-bundle obs:bundle7
- 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:d; ex:report2, ex:report1)
-endBundle
-entity(obs:bundle7, [ prov:type='prov:Bundle' ])
-wasAttributedTo(obs:bundle7, ex:observer01)
-</pre>
-Bundle <span class="name">obs:bundle7</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:bundle8
- entity(tool:bundle8, [ prov:type='viz:Configuration', prov:type='prov:Bundle' ])
- wasAttributedTo(tool:bundle8, viz:Visualizer)
-
- entity(ex:report1, [viz:color="orange"]) // ex:report1 is a reused identifier
- hasProvenanceIn(ex:report1, obs:bundle7, -)
-
- entity(tool:r2, [viz:color="blue"]) // tool:r2 is a new identifier
- hasProvenanceIn(tool:r2, obs:bundle7, ex:report2)
-
- wasDerivedBy(ex:d; ex:report2, ex:report1, [viz:style="dotted"])
- hasProvenanceIn(ex:d, obs:bundle7, -)
-endBundle
-</pre>
-
-<p>In bundle <span class="name">tool:bundle8</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:bundle8</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>For the purpose of illustration, we show that the visualisation tool
-reused identifier <span class="name">ex:report1</span>, but created a new identifier <span class="name">tool:r2</span>.
-They denote entities which are alternates of with <span class="name">ex:report1</span> and <span class="name">ex:report2</span>, described in bundle <span class="name">obs:bundle7</span>, with visualization attribute for the color to be used when rendering these entities.
-Likewise, the derivation has a style attribute. </p>
-
-<p>According to their definition,
-derivations have an <a href="#derivation.id">optional identifier</a>.
-To express an alternate for a derivation, we need to be able to reference it, by means of an identifier. Hence, it is necessary for it to have an identifier in the first place (<span class="name">ex:d</span>).</p>
-</div>
-
-</section>
--->
</section>
@@ -3170,112 +3033,6 @@
</section>
-<!--
-<section id="term-contextualization">
-
-<h4>Contextualization (As Before F2F3)</h4>
-
-<p>The following notion is a relation between two entities with regard to a bundle (referred to as remote bundle). In contrast, the bundle in which this relation occurs is referred to as local bundle.</p>
-
-
-<span class="glossary-ref" data-ref="glossary-contextualization"></span>
-
-
-<p>A bundle's
-descriptions provide a context in which to interpret an entity in a
-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.
-</p>
-
-<p><div class="attributes" id="attributes-contextualization">A <dfn title="contextualizationOf">contextualization</dfn> relation<span class="withPn">, written <span class="pnExpression">contextualizationOf(l, e, b)</span> in PROV-N,</span> has:
-<ul>
-<li><span class='attribute' id="contextualization.local">local</span>: an identifier (<span class="name">l</span>) for an entity in the local bundle (not explicitly identified) presenting the aspects of <span class="name">e</span> in remote bundle <span class="name">b</span> ;</li>
-<li><span class='attribute' id="contextualization.contextualized">contextualized</span>: an identifier (<span class="name">e</span>) of an entity in some remote bundle <span class="name">b</span>;</li>
-<li><span class='attribute' id="contextualization.context">bundle</span>: an identifier (<span class="name">b</span>) for a remote bundle.</li>
-</ul>
-</div>
-
-
-<div class="anexample" id="anexample-mention-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"])
- contextualizationOf(tool:Bob-2011-11-16, ex:Bob, ex:run1)
-
- agent(tool:Bob-2011-11-17, [perf:rating="bad"])
- contextualizationOf(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"])
- contextualizationOf(tool:report1, obs:bundle1, ex:report1)
-
- entity(tool:report2, [viz:color="blue"])
- contextualizationOf(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>
-
-
-
-</section>
--->
-
</section>
@@ -3549,65 +3306,10 @@
</pre>
</div>
-<!-- <div class="note">Should we also have prov:encoding?</div> -->
-
-</section>
-
-<!--
-<section id="term-attribute-provenance-uri">
-<h4>prov:provenance-uri</h4>
-
-<p><span class="glossary-ref" data-ref="glossary-provenance-uri"></span> (See <a href="http://www.w3.org/TR/prov-aq/#dfn-provenance-uri">Provenance-URI</a> in [[PROV-AQ]].) </p>
-
-<p> The attribute <dfn title="provenance-uri-attribute"><span class="name">prov:provenance-uri</span></dfn> provides
- an OPTIONAL <a>provenance-URI</a>.</p>
-
-
-<p>The attributes <a href="#term-attribute-service-uri"><span class="name">prov:service-uri</span></a>
-and
-<a href="#term-attribute-provenance-uri"><span class="name">prov:provenance-uri</span></a> are mutually exclusive.</p>
-
-
-<div class="anexample" id="anexample-provenance-uri">
-<p>According to the following provenance locator, provenance descriptions about <span class="name">ex:report1</span> can be found in bundle <span class="name">bob:bundle1</span>, which is available from the provenance service identified by the provided URI.</p>
-<pre class="codeexample">
-hasProvenanceIn(ex:report1, bob:bundle1, -, [ prov:provenance-uri="http://example.com/service" %% xsd:anyURI ])
-</pre>
-</div>
-
-
</section>
-<section id="term-attribute-service-uri">
-<h4>prov:service-uri</h4>
-
-<p><span class="glossary-ref" data-ref="glossary-provenance-service"></span> (See <a href="http://www.w3.org/TR/prov-aq/#dfn-provenance-service">provenance service</a> in [[PROV-AQ]].)</p>
-
-<p><span class="glossary-ref" data-ref="glossary-service-uri"></span> (See <a href="http://www.w3.org/TR/prov-aq/#dfn-service-uri">Service-URI</a> in [[PROV-AQ]].)</p>
-
-
-<p> The attribute <dfn title="service-uri-attribute"><span class="name">prov:service-uri</span></dfn> provides
- an OPTIONAL <a>service-URI</a> </p>
-
-
-<p>The attributes <a href="#term-attribute-service-uri"><span class="name">prov:service-uri</span></a>
-and
-<a href="#term-attribute-provenance-uri"><span class="name">prov:provenance-uri</span></a> are mutually exclusive.</p>
-
-
-<div class="anexample" id="anexample-service-uri">
-<p>According to the following provenance locator, provenance descriptions about <span class="name">ex:report1</span> can be found in the resource identified by the provided URI.</p>
-<pre class="codeexample">
-hasProvenanceIn(ex:report1, [ prov:service=uri="http://example.com/some-provenance.pn" %% xsd:anyURI ])
-</pre>
-</div>
-
-</section>
-
--->
-
</section>