--- a/model/comments/issue-437-james.txt Mon Jul 09 08:38:00 2012 +0100
+++ b/model/comments/issue-437-james.txt Mon Jul 09 09:10:19 2012 +0100
@@ -17,6 +17,8 @@
> credit people that contributed to it.
>
> 1. S5, "itself dependen on" - spelling
+
+Fixed.
>
> 2. Table 5 and sec. 5.6.2: I have trouble reading
> "memberOf(c,{e1,...,en})" - the elements e1,...,en are members of c,
@@ -27,24 +29,48 @@
> vocabularies that have membership. Why not just "memberOf(element,
> collection)"? This is what I thought we agreed at f2f3. We could
> also omit EmptyCollection and the completeness flag.
+
+TODO. Non alignment between prov-o and prov-dm.
+
+
+
>
> 3. Figure 7 and 7b: I suggest renumbering, or renaming "Figure 7" to
> "Figure 7a"
+
+Figure 7b is Figure 8.
+
>
> 4. S5.3.5. "capacity an entity" -> "capacity of an entity"
+
+Fixed.
+
>
> 5. Example 45. I am afraid I don't understand how the current
> definition of mentionOf accommodates the example. Why doesn't bondle
> tool:analysis1 rate the two activities Bob was associated with (or the
> associations themselves) rather than rating (different mentions of)
> Bob?
+
+
+This example is concerned with a performance rating tool that reads
+and processes provenance to determine the performance of agents. To
+keep the example simple, an agent's performance is determined by the
+duration of the activities it is associated with.
+
+Text was updated accordingly.
+
>
> 6. In example 46 (which I'm also not sure I understand, but never
> mind), the bundles in mentionOf are the second arguments, I think they
> should be third.
+
+Thanks. Fixed.
+
>
> 7. I would also suggest that the bundle in mentionOf should be
- > mandatory, not optional. -- The University of Edinburgh is a
- > charitable body, registered in Scotland, with registration number
- > SC005336.
- >
+ > mandatory, not optional.
+
+
+Correct, this was fixed.
+
--- a/model/glossary.html Mon Jul 09 08:38:00 2012 +0100
+++ b/model/glossary.html Mon Jul 09 09:10:19 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, communication, derivation, attribution, association, or delegation.
+<dfn id="concept-influence">Influence</dfn> is the capacity of 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>
--- a/model/glossary.js Mon Jul 09 08:38:00 2012 +0100
+++ b/model/glossary.js Mon Jul 09 09:10:19 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/49acfc0a4219/model/glossary.html';
+glossary_hg='http://dvcs.w3.org/hg/prov/file/bbe46c9db287/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, communication, derivation, attribution, association, or delegation. ' +
+'<dfn id="concept-influence">Influence</dfn> is the capacity of 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> ' +
' ' +
' ' +
--- a/model/prov-dm.html Mon Jul 09 08:38:00 2012 +0100
+++ b/model/prov-dm.html Mon Jul 09 09:10:19 2012 +0100
@@ -1426,7 +1426,7 @@
<h2>PROV-DM Types and Relations</h2>
<p>Provenance concepts, expressed as PROV-DM types and relations, are organized according to six components that are defined in this section.
-The components and their dependencies are illustrated in <a href="#prov-dm-components">Figure 4</a>. A component that relies on concepts defined in another is displayed above it in the figure. So, for example, component 5 (alternate) depends on concepts defined in component 4 (bundles), itself dependen on concepts defined in component 1 (entity and activity).
+The components and their dependencies are illustrated in <a href="#prov-dm-components">Figure 4</a>. A component that relies on concepts defined in another is displayed above it in the figure. So, for example, component 5 (alternate) depends on concepts defined in component 4 (bundles), itself dependent on concepts defined in component 1 (entity and activity).
</p>
<div id="prov-dm-components-ul">
@@ -2234,13 +2234,13 @@
</figure>
</div>
-<p>Component 3 further defines a general notion of <a>influence</a>, as a super-relation of all relations defined so far. <a href="#figure-component3b">Figure 7b</a> displays one new association class, generalizing previously introduced associations.</p>
+<p>Component 3 further defines a general notion of <a>influence</a>, as a super-relation of all relations defined so far. <a href="#figure-component3b">Figure 8</a> displays one new association class, generalizing previously introduced associations.</p>
<div style="text-align: center;">
<figure>
<img src="uml/Component3b.png" alt="Influence"/><br>
-<figcaption id="figure-component3b">Figure 7b: Influence</figcaption>
+<figcaption id="figure-component3b">Figure 8: Influence</figcaption>
</figure>
</div>
@@ -2488,14 +2488,14 @@
<p>The fourth component of PROV-DM is concerned with bundles, a mechanism to support provenance of provenance.
-<a href="#figure-component4">Figure 8</a> depicts a UML class diagram for the fourth component. It comprises a <a>Bundle</a> class defined as a subclass of <a>Entity</a>.
+<a href="#figure-component4">Figure 9</a> depicts a UML class diagram for the fourth component. It comprises a <a>Bundle</a> class defined as a subclass of <a>Entity</a>.
</p>
<div style="text-align: center;">
<figure>
<img src="uml/component4.png" alt="bundles"/><br>
-<figcaption id="figure-component4">Figure 8: Bundle Component Overview</figcaption>
+<figcaption id="figure-component4">Figure 9: Bundle Component Overview</figcaption>
</figure>
</div>
@@ -2775,7 +2775,7 @@
<p>The fifth component of PROV-DM is concerned with
relations <a>specialization</a>, <a>alternate</a>, and <a>mention</a> between entities.
- <a href="#figure-component5">Figure 9</a> depicts
+ <a href="#figure-component5">Figure 10</a> depicts
the fifth component with a single class, two binary associations, and a ternary association.
</p>
@@ -2784,7 +2784,7 @@
<figure>
<!-- <img src="images/Alternates.png" alt="alternates"/> -->
<img src="uml/component5.png" alt="alternates"/><br>
-<figcaption id="figure-component5">Figure 9: Alternates Component Overview</figcaption>
+<figcaption id="figure-component5">Figure 10: Alternates Component Overview</figcaption>
</figure>
</div>
@@ -2933,20 +2933,21 @@
</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>
+<p>This example is concerned with a performance rating tool that reads and processes provenance to determine the performance of agents. To keep the example simple, an agent's performance is determined by the duration of the activities it is associated with. </p>
+<p>As an illustration, we consider that 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"])
+ 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"])
+ 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 mention of <span class="name">ex:Bob</span> as described in 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.
+<p>The 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 mention of <span class="name">ex:Bob</span> as described in 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
@@ -2973,17 +2974,17 @@
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.
+Bundle <span class="name">obs:bundle1</span> is rendered by a visualisation tool. It may useful for the visualization layout of 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"])
- mentionOf(tool:report1, obs:bundle1, ex:report1)
+ mentionOf(tool:report1, ex:report1, obs:bundle1)
entity(tool:report2, [viz:color="blue"])
- mentionOf(tool:report2, obs:bundle1, ex:report2)
+ mentionOf(tool:report2, ex:report2, obs:bundle1)
endBundle
</pre>
@@ -3119,7 +3120,7 @@
<p>The sixth component of PROV-DM is concerned with the notion of collections.
A collection is an entity that has some members. The members are themselves entities, and therefore their provenance can be expressed. Some applications need to be able to express the provenance of the collection itself: e.g. who maintains the collection (attribution), which members it contains as it evolves, and how it was assembled. The purpose of Component 6 is to define the types and relations that are useful to express the provenance of collections. </p>
-<p><a href="#figure-component6">Figure 10</a> depicts
+<p><a href="#figure-component6">Figure 11</a> depicts
the sixth component with two new classes (Collection, Empty Collection) and one association (MemberOf).
</p>
@@ -3127,7 +3128,7 @@
<div style="text-align: center;">
<figure style="max-width: 95%; ">
<img src="uml/component6.png" alt="collection"/><br>
-<figcaption id="figure-component6">Figure 10: Collections Component Overview</figcaption>
+<figcaption id="figure-component6">Figure 11: Collections Component Overview</figcaption>
</figure>
</div>