--- a/model/comments/issue-437-jun.txt Mon Jul 09 09:28:32 2012 +0100
+++ b/model/comments/issue-437-jun.txt Mon Jul 09 10:35:57 2012 +0100
@@ -28,6 +28,8 @@
> Abstract:
>
> - and, (5) --> ; and (6)
+
+Yes.
>
> - I guess PROV-DM is PROV data model? It will be nice to define this
> abbreviation in the first place of mentioning. This also applies to
@@ -42,26 +44,55 @@
>
> Status of this document
> - Is this the sixth public release?
+
+Last one was fourth. This one is fifth.
+
> - prov-o is not an OWL-RL ontology, but OWL-RL++.
+
+Just updated to OWL2.
>
> - Do we have a PROV-XML? I am not aware of this, and just pointed it
> out that this is mentioned.
+
+Very early draft is available. Currently pointing to a wiki page.
+
>
> Section 2.1
>
> - Before the table, when saying "in the core of PROV, all relations
> are binary", might be worthwhile pointing out where they are not
> binary?
+
+That's the purpose of section 2.2.1.2.
+
+
> - Can we say a few words about what the purpose of the "Name" column is?
+
+Updated text as follows:
+
+the third column contains the corresponding name, as it appears in Figure 1.
+
>
> 2.1.1
> - aspect -> aspects
+
+Done
+
>
> 2.2.1.3
>
> Based on the narrative of this section it's still not clear to me why
> we need to identify an instance of relation. It's not technical, nor
> critical to the release for LC.
+
+The text says:
+
+"This optional identifier can then be used to refer to an instance as part of other concepts."
+
+
+The concrete use case is in derivations, in which a usage and generation instance can be provided.
+Without identity, we wouldn't be able to do this.
+
>
> 2.3
>
@@ -69,15 +100,25 @@
> whereas only the first three define core structures."? To me, these
> components are used to express the core and extended structures, not
> to define these structures.
+
+Rephrased as follows:
+
+All components contain extended structures, whereas only the first three contain core structures.
+
>
> 5.1
>
> - Figure 5 and many others (6, 7) do not fit into a page when
> printed. Is easy to scale them down for this purpose, if not losing
> the quality?
+
+Hopefully, this is fixed. Now defined as <figure style="max-width: 90%; ">
>
> 5.1.6
> - have valid -> be valid
+
+Fixed
+
>
> 5.3.5
>
@@ -88,6 +129,12 @@
> other concepts. In my opinion such an example is key to illustrate
> the purpose of this concept.
>
+
+
+See email discussion with Tim. It is fine to have the document also attributed
+to W3C (since the W3C is the actual published).
+
+
> 5.4.1
>
> - I don't understand the "There may be other kinds of bundles not
--- a/model/comments/issue-437-satya.txt Mon Jul 09 09:28:32 2012 +0100
+++ b/model/comments/issue-437-satya.txt Mon Jul 09 10:35:57 2012 +0100
@@ -23,12 +23,18 @@
> a broad range of notions: information processing activities and
> physical activities."
>
+
+TODO
+
> As Example 2 already describes the information processing activity and
> driving of car from Boston to Cambridge.
>
> 2. Example 5 is not clear - is this in context of UK news - phone
> tapping issue (it is very country specific)
- >
+ >
+
+TODO
+
> Section 5.1.6
> 1. Start: By defining all the attributes except Activity (being
> started) as optional leads to potentially confusing scenarios. If only
@@ -98,7 +104,12 @@
> The relevance of such a construct in DM is not clear.
-TODO
+The text says:
+"A bundle constructor allows the content and the name of a bundle to be specified;"
+
+Can you explain what the issue is? Is it a question of naming? Or is the idea
+that we want to express the content and name?
+
>
@@ -141,7 +152,11 @@
> Since, there is not correlation between wasDerivedFrom and alternateOf
> (as far as I know), suggest removing Example 44.
-Checking with James if this is OK.
+I checked with James. He says:
+
+ "The fact that one of the entities is derived from the other is immaterial: we are not saying that there is any correlation between derivation and alternateOf (there isn't, and either can hold without the other, I think)."
+
+Given this, can you explain what your concern is for this example?
>
> Section 5.6
@@ -154,7 +169,7 @@
> provenance of provenance).
>
-bundles are sets of descriptions. Descriptions are not
+Bundles are sets of descriptions. Descriptions are not
entities. Satya, you were one of those opposed to the idea of
identifiable records ....
--- a/model/prov-dm.html Mon Jul 09 09:28:32 2012 +0100
+++ b/model/prov-dm.html Mon Jul 09 10:35:57 2012 +0100
@@ -406,8 +406,8 @@
(1) entities and activities, and the time at which they were created, used, or ended;
(2) derivations of entities from entities;
(3) agents bearing responsibility for entities that were generated and activities that happened;
-(4) a notion of bundle, a mechanism to support provenance of provenance; and,
-(5) properties to link entities that refer to the same thing;
+(4) a notion of bundle, a mechanism to support provenance of provenance;
+(5) properties to link entities that refer to the same thing; and,
(6) collections forming a logical structure for its members.
</p>
@@ -645,7 +645,7 @@
<div style="text-align: center; ">
- <figure style="max-width: 70%; " id="prov-core-structures-top">
+ <figure style="max-width: 70%; " id="prov-core-structures-top">
<!-- <img src="../images/OverviewDiagram.png" alt="PROV Core Structures" style="max-width: 70%; " /> -->
<img src="uml/essentials.png" alt="PROV Core Structures" style="max-width: 70%; " /><br>
<figcaption id="prov-core-structures">Figure 1: PROV Core Structures</figcaption>
@@ -655,7 +655,7 @@
<p>The concepts found in the core of PROV are introduced in the rest of this section.
They are summarized in <a href="#overview-types-and-relations">Table 2</a>, where they are categorized as
type or relation.
- The first column lists concepts, the second column indicates whether a concept maps to a type or a relation, whereas the third column contains the corresponding name. Names of relations have a verbal form in the past tense to express what happened in the past, as opposed to what may or will happen. In the core of PROV, all relations are binary.
+ The first column lists concepts, the second column indicates whether a concept maps to a type or a relation, whereas the third column contains the corresponding name, as it appears in Figure 1. Names of relations have a verbal form in the past tense to express what happened in the past, as opposed to what may or will happen. In the core of PROV, all relations are binary.
</p>
@@ -672,7 +672,7 @@
<tr><td><a>Activity</a></td><td><a title="dfn-Activity">Activity</a></td><td style="text-align: center;"><a class="section-ref" href="#section-entity-activity"><span>TBD</span></a></td></tr>
<tr><td><a>Agent</a></td><td><a title="dfn-agent">Agent</a></td><td style="text-align: center;"><a class="section-ref" href="#section-agents-attribution-association-delegation"><span>TBD</span></a></td></tr>
<tr>
-<td><a>Generation</a></td><td rowspan="7" style="text-align: center;">PROV-DM Relations</td><td><a title="wasGeneratedBy">wasGeneratedBy</a></td><td style="text-align: center;"><a class="section-ref" href="#section-entity-activity"><span>TBD</span></a></td></tr>
+<td><a>Generation</a></td><td rowspan="7" style="text-align: center;">PROV-DM Relations</td><td><a title="wasGeneratedBy">WasGeneratedBy</a></td><td style="text-align: center;"><a class="section-ref" href="#section-entity-activity"><span>TBD</span></a></td></tr>
<tr><td><a>Usage</a></td><td><a title="used">Used</a></td><td style="text-align: center;"><a class="section-ref" href="#section-entity-activity"><span>TBD</span></a></td></tr>
<tr><td><a>Communication</a></td><td><a title="wasInformedBy">WasInformedBy</a></td><td style="text-align: center;"><a class="section-ref" href="#section-entity-activity"><span>TBD</span></a></td></tr>
<tr><td><a>Derivation</a></td><td><a title="wasDerivedFrom">WasDerivedFrom</a></td><td style="text-align: center;"><a class="section-ref" href="#section-derivation"><span>TBD</span></a></td></tr>
@@ -1118,7 +1118,7 @@
is further organized according to components, grouping concepts in a
thematic manner. </p>
-<p> <a href="#components-overview">Table 3</a> enumerates the six components, five of which have already been implicitly overviewed in this section. All components specify extended structures, whereas only the first three define core structures.
+<p> <a href="#components-overview">Table 3</a> enumerates the six components, five of which have already been implicitly overviewed in this section. All components contain extended structures, whereas only the first three contain core structures.
<div id="components-overview-div" style="text-align: center;">
<table class="thinborder" style="margin-left: auto; margin-right: auto;">
@@ -1443,7 +1443,7 @@
<!-- TODO: update map for linking -->
<div style="text-align: center;">
-<figure style="max-width: 90%; ">
+<figure style="max-width: 95%; ">
<img usemap="#componentMap" src="images/components-dependencies.png" alt="PROV-DM Components" style="max-width: 90%; " />
<map id="componentMap" name="componentMap">
<area title="collections" href="#component5" coords="220,0,440,70" alt="collections" shape="rect"/>
@@ -1553,7 +1553,7 @@
</p>
<div style="text-align: center;">
-<figure>
+<figure style="max-width: 95%; ">
<!--<img src="images/Entities-Activities.png" alt="entities and activities"/> -->
<img src="uml/component1.png" alt="entities and activities"/><br>
<figcaption id="figure-component1">Figure 5: Entities and Activities Component Overview</figcaption>
@@ -1804,7 +1804,7 @@
wasGeneratedBy(e1, a0)
wasStartedBy(a1, e1, a0, 2011-11-16T16:05:00)
</pre>
-<p>If <span class="name">e1</span> is not known, it would also have valid to write:
+<p>If <span class="name">e1</span> is not known, it would also be valid to write:
<pre class="codeexample">
wasStartedBy(a1, -, a0, 2011-11-16T16:05:00)
</pre>
@@ -2001,7 +2001,7 @@
<div style="text-align: center;">
-<figure>
+<figure style="max-width: 95%; ">
<!-- <img src="images/Derivation.png" alt="derivation"/> -->
<img src="uml/component2.png" alt="derivation"/><br>
<figcaption id="figure-component2">Figure 6: Derivation Component Overview</figcaption>
@@ -2227,7 +2227,7 @@
<div style="text-align: center;">
-<figure>
+<figure style="max-width: 95%; ">
<!-- <img src="images/Agents-Responsibility.png" alt="agents and responsibilities"/> -->
<img src="uml/component3.png" alt="agents and responsibilities"/><br>
<figcaption id="figure-component3">Figure 7: Agents and Responsibility Overview</figcaption>
@@ -2238,7 +2238,7 @@
<div style="text-align: center;">
-<figure>
+<figure style="max-width: 95%; ">
<img src="uml/Component3b.png" alt="Influence"/><br>
<figcaption id="figure-component3b">Figure 8: Influence</figcaption>
</figure>
@@ -2492,7 +2492,7 @@
</p>
<div style="text-align: center;">
-<figure>
+<figure style="max-width: 95%; ">
<img src="uml/component4.png" alt="bundles"/><br>
<figcaption id="figure-component4">Figure 9: Bundle Component Overview</figcaption>
@@ -2781,7 +2781,7 @@
<div style="text-align: center;">
-<figure>
+<figure style="max-width: 95%; ">
<!-- <img src="images/Alternates.png" alt="alternates"/> -->
<img src="uml/component5.png" alt="alternates"/><br>
<figcaption id="figure-component5">Figure 10: Alternates Component Overview</figcaption>