--- a/model/ProvenanceModel.html Tue Jan 17 11:51:58 2012 +0000
+++ b/model/ProvenanceModel.html Tue Jan 17 12:42:37 2012 +0000
@@ -968,7 +968,7 @@
<div class="issue">
There is still some confusion about what the identifiers really denote. For instance, are they entity identifiers or entity record identifiers. This is <a href="http://www.w3.org/2011/prov/track/issues/183">ISSUE-183</a>.
-An example and questions appear in <a href="http://www.w3.org/2011/prov/track/issues/215">ISSUE-215</a>
+An example and questions appear in <a href="http://www.w3.org/2011/prov/track/issues/215">ISSUE-215</a>. A related issued is also raised in <a href="http://www.w3.org/2011/prov/track/issues/145">ISSUE-145</a>.
</div>
<section id="record-Entity">
@@ -1375,7 +1375,7 @@
<div class="interpretation-forward">
-For the interpretation of a generation record, see <a href="#generation-activity-ordering">generation-activity-ordering</a>.
+For the interpretation of a generation record, see <a href="#generation-within-activity">generation-within-activity</a>.
</div>
@@ -1383,7 +1383,7 @@
<p>The assertion of a generation record implies ordering of <a title="event">events</a> in the world.</p>
-<div class='interpretation' id='generation-activity-ordering'><span class='conditional'>If</span> an assertion <span class="name">wasGeneratedBy(x,a,attrs)</span> or <span class="name">wasGeneratedBy(x,a,attrs,t)</span> holds, <span class='conditional'>then</span> the following temporal constraint also holds: the <a title="entity generation event">generation</a> of the entity denoted by <span class="name">x</span> <a>precedes</a> the <a title="activity end event">end</a>
+<div class='interpretation' id='generation-within-activity'><span class='conditional'>If</span> an assertion <span class="name">wasGeneratedBy(x,a,attrs)</span> or <span class="name">wasGeneratedBy(x,a,attrs,t)</span> holds, <span class='conditional'>then</span> the following temporal constraint also holds: the <a title="entity generation event">generation</a> of the entity denoted by <span class="name">x</span> <a>precedes</a> the <a title="activity end event">end</a>
of <span class="name">a</span> and <a>follows</a> the <a title="activity start event">start</a> of <span class="name">a</span>.
</div>
-->
@@ -1483,7 +1483,7 @@
<div class="interpretation-forward">
-For the interpretation of a usage record, see <a href="#usage-generation-ordering">usage-generation-ordering</a> and <a href="#usage-activity-ordering">usage-activity-ordering</a>.
+For the interpretation of a usage record, see <a href="#generation-precedes-usage">generation-precedes-usage</a> and <a href="#usage-within-activity">usage-within-activity</a>.
</div>
@@ -3390,12 +3390,12 @@
<h3>PROV-DM Interpretation</h3>
<p>Section <a href="#section-time-event">section-time-event</a>
-introduced a notion of <a title="event">instantaneous event</a>
+introduces a notion of <a title="event">instantaneous event</a>
marking changes in the world, in its activities and entities. PROV-DM
identifies four kinds of <a title="event">instantaneous events</a>, namely <a>entity generation
event</a>, <a>entity usage event</a>, <a>activity start event</a>
and <a>activity end event</a>. PROV-DM adopts Lamport's clock
-assumptions [[CLOCK]] in the form of a partial order <a>follows</a>
+assumptions [[CLOCK]] in the form of a reflexive, transitive partial order <a>follows</a>
(and its inverse <a>precedes</a>) between <a title="event">instantaneous events</a>. Furthermore,
PROV-DM assumes the existence of a mapping from <a title="event">instantaneous events</a> to time clocks,
though the actual mapping is not in scope of this specification.</p>
@@ -3419,7 +3419,7 @@
of <a title="event">instantaneous events</a> introduced in this specification. The
presence of a time observation for a given <a>instantaneous event</a> fixes the
mapping of this <a>instantaneous event</a> to the timeline. The presence of time
-information in a provenance instantiates the ordering constraint with
+information in a provenance record instantiates the ordering constraint with
that time information. It is expected that such instantiated
constraint can help corroborate provenance information. We anticipate
that verification algorithms could be developed though this
@@ -3434,7 +3434,7 @@
activities. The four kind of <a title="event">instantaneous events</a> are represented by vertical
dotted lines (adjacent to the vertical sides of an activity's
rectangle, or intersecting usage and generation edges). The ordering
-constraints are represented by triangles.</p>
+constraints are represented by triangles: an occurrence of a triangle between two <a title="event">instantaneous event</a> vertical dotted lines represents that the event denoted by the left line precedes the event denoted by the right line.</p>
<div style="text-align: center;">
<img src="constraints.png" alt="constraints between events" />
@@ -3448,26 +3448,27 @@
<div class='interpretation' id='start-precedes-end'> The following ordering constraint holds for any activity record: the
<a title="activity start event">start event</a> <a>precedes</a> the <a title="activity end event">end event</a>.</div>
-<p>The assertion of a generation record implies ordering of <a title="event">events</a> in the world, since the corresponding event had to occur during the associated activity. This is
-illustrated by Subfigure <a href="#constraint-summary">constraint-summary</a> (c) and expressed by constraint <a href="#generation-activity-ordering">generation-activity-ordering</a>.</p>
-
-<div class='interpretation' id='generation-activity-ordering'><span class='conditional'>If</span> an assertion <span class="name">wasGeneratedBy(x,a,attrs)</span> or <span class="name">wasGeneratedBy(x,a,attrs,t)</span> holds, <span class='conditional'>then</span> the following ordering constraint also holds: the <a title="entity generation event">generation</a> of the entity denoted by <span class="name">x</span> <a>precedes</a> the <a title="activity end event">end</a>
-of <span class="name">a</span> and <a>follows</a> the <a title="activity start event">start</a> of <span class="name">a</span>.
-</div>
-
-
<p>The assertion of a usage record implies ordering of <a title="event">events</a> in the world, since the corresponding event had to occur during the associated activity. This is
-illustrated by Subfigure <a href="#constraint-summary">constraint-summary</a> (e) and expressed by constraint <a href="#usage-activity-ordering">usage-activity-ordering</a>.</p>
-
-<div class='interpretation' id='usage-activity-ordering'>Given an activity record identified by <span class="name">a</span>, an entity record identified by <span class="name">e</span>, a set of attribute-value pairs <span class="name">attrs</span>, and optional time <span class="name">t</span>, <span class='conditional'>if</span>
+illustrated by Subfigure <a href="#constraint-summary">constraint-summary</a> (c) and expressed by constraint <a href="#usage-within-activity">usage-within-activity</a>.</p>
+
+<div class='interpretation' id='usage-within-activity'>Given an activity record identified by <span class="name">a</span>, an entity record identified by <span class="name">e</span>, a set of attribute-value pairs <span class="name">attrs</span>, and optional time <span class="name">t</span>, <span class='conditional'>if</span>
assertion <span class="name">used(a,e,attrs)</span> or <span class="name">used(a,e,attrs,t)</span> holds, <span class='conditional'>then</span> the following ordering constraint holds:
the <a title="entity usage event">usage</a> of the entity represented by entity record identified by <span class="name">e</span> <a>precedes</a> the <a title="activity end event">end</a> of activity represented by record identified by <span class="name">a</span> and <a>follows</a> its <a title="activity start event">start</a>.
</div>
+<p>The assertion of a generation record implies ordering of <a title="event">events</a> in the world, since the corresponding event had to occur during the associated activity. This is
+illustrated by Subfigure <a href="#constraint-summary">constraint-summary</a> (e) and expressed by constraint <a href="#generation-within-activity">generation-within-activity</a>.</p>
+
+<div class='interpretation' id='generation-within-activity'><span class='conditional'>If</span> an assertion <span class="name">wasGeneratedBy(x,a,attrs)</span> or <span class="name">wasGeneratedBy(x,a,attrs,t)</span> holds, <span class='conditional'>then</span> the following ordering constraint also holds: the <a title="entity generation event">generation</a> of the entity denoted by <span class="name">x</span> <a>precedes</a> the <a title="activity end event">end</a>
+of <span class="name">a</span> and <a>follows</a> the <a title="activity start event">start</a> of <span class="name">a</span>.
+</div>
+
+
+
<p>Furthemore, assertion of a usage record and a generation record for a given entity implies ordering of <a title="event">events</a> in the world, since the <a title="entity generation event">generation event</a> had to precede the <a title="entity usage event">usage event</a>. This is
-illustrated by Subfigure <a href="#constraint-summary">constraint-summary</a> (b) and expressed by constraint <a href="#usage-generation-ordering">usage-generation-ordering</a>.</p>
-
-<div class='interpretation' id='usage-generation-ordering'>For any entity, the following ordering constraint holds: the <a title="entity generation event">generation</a> of an entity always <a>precedes</a> any of its <a title="entity usage event">usages</a>.
+illustrated by Subfigure <a href="#constraint-summary">constraint-summary</a> (b) and expressed by constraint <a href="#generation-precedes-usage">generation-precedes-usage</a>.</p>
+
+<div class='interpretation' id='generation-precedes-usage'>For any entity, the following ordering constraint holds: the <a title="entity generation event">generation</a> of an entity always <a>precedes</a> any of its <a title="entity usage event">usages</a>.
</div>
@@ -3524,10 +3525,10 @@
the activity record denoted by <span class="name">a2</span>.
</div>
-<div class="note">
+<div class="issue">
For completeness, we should define ordering constraint for wasAssociatedWith and actedOnBehalfOf.
For wasAssociatedWith(a,ag), it feels that ag must have some overlap with a.
-For actedOnBehalfOf(ag1,ag2,a), it seem that ag2 should have existed before the overlap between ag1 and a.
+For actedOnBehalfOf(ag1,ag2,a), it seem that ag2 should have existed before the overlap between ag1 and a. This is <a href="http://www.w3.org/2011/prov/track/issues/221">ISSUE-221</a>.
</div>
</section>
--- a/model/constraints.svg Tue Jan 17 11:51:58 2012 +0000
+++ b/model/constraints.svg Tue Jan 17 12:42:37 2012 +0000
@@ -951,15 +951,15 @@
borderopacity="1.0"
inkscape:pageopacity="0.0"
inkscape:pageshadow="2"
- inkscape:zoom="0.71458288"
- inkscape:cx="372.04724"
+ inkscape:zoom="0.73168726"
+ inkscape:cx="200.52587"
inkscape:cy="526.18109"
inkscape:document-units="px"
inkscape:current-layer="g8502"
showgrid="false"
inkscape:window-width="1280"
- inkscape:window-height="1003"
- inkscape:window-x="0"
+ inkscape:window-height="1001"
+ inkscape:window-x="1280"
inkscape:window-y="0"
inkscape:window-maximized="1"
showguides="true"
@@ -972,7 +972,7 @@
<dc:format>image/svg+xml</dc:format>
<dc:type
rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
- <dc:title></dc:title>
+ <dc:title />
</cc:Work>
</rdf:RDF>
</metadata>
@@ -1100,7 +1100,7 @@
sodipodi:nodetypes="cc" />
</g>
<g
- transform="translate(0,-32)"
+ transform="translate(0,166.1721)"
id="g5005"
inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/path6912.png"
inkscape:export-xdpi="79.550438"
@@ -1296,7 +1296,8 @@
id="g6677"
inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/path6912.png"
inkscape:export-xdpi="79.550438"
- inkscape:export-ydpi="79.550438">
+ inkscape:export-ydpi="79.550438"
+ transform="translate(0,-219.07201)">
<path
id="path6949-5-1"
d="m 205.48904,417.35914 c 0,164.59929 0,164.24301 0,164.24301"
@@ -2521,7 +2522,7 @@
sodipodi:linespacing="100%"
id="text7931"
y="376.30768"
- x="50.433823"
+ x="73.654388"
style="font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
xml:space="preserve"
inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/path6912.png"
@@ -2529,22 +2530,22 @@
inkscape:export-ydpi="79.550438"><tspan
id="tspan7985"
y="376.30768"
- x="50.433823"
- sodipodi:role="line">(c) generation-activity-ordering</tspan></text>
+ x="73.654388"
+ sodipodi:role="line">(c) usage-within-activity</tspan></text>
<text
sodipodi:linespacing="100%"
id="text7931-0"
y="594.55798"
- x="58.549366"
+ x="57.35751"
style="font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
xml:space="preserve"
inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/path6912.png"
inkscape:export-xdpi="79.550438"
inkscape:export-ydpi="79.550438"><tspan
y="594.55798"
- x="58.549366"
+ x="57.35751"
id="tspan7933-2"
- sodipodi:role="line">(e) usage-activity-ordering</tspan></text>
+ sodipodi:role="line">(e) generation-within-activity</tspan></text>
<text
sodipodi:linespacing="100%"
id="text7927-2"