--- a/model/ProvenanceModel.html Tue Nov 22 09:34:55 2011 -0500
+++ b/model/ProvenanceModel.html Wed Nov 23 08:21:37 2011 +0000
@@ -274,6 +274,13 @@
<h3>A Conceptualization of the World</h3>
+
+ <section id='section-entity-activity-agent'>
+<h4>Entity, Activity, Agent</h4>
+
+
+
+
<p>This specification is based on a conceptualization of the world
that is described in this section. In the world (whether real or not),
there are things, which can be physical, digital, conceptual, or
@@ -319,12 +326,41 @@
<p> Even software agents can be assigned some responsibility for the effects they have in the world, so for example if one is using a Text Editor and one's laptop crashes then one would say that the Text Editor was responsible for crashing the laptop. If one invokes a service to buy a book, that service can be considered responsible for drawing funds from one's bank to make the purchase (the company that runs the service and the web site would also be responsible, but the point here is that we assign some measure of responsibility to software as well). So when someone models software as an agent for an activity in our model they mean the agent has some responsibility for that activity.
</p>
+<p> In this specification, the qualifier 'identifiable' is implicit whenever a reference is made to an activity or an entity.</p>
+
+</section>
+
+
+ <section id='section-time-event'>
+<h4>Time and Event</h4>
+
<p>In our conceptualization of the world, instantaneous events, or <dfn id="concept-event">events</dfn> for short, happen in the world, which mark changes in the world, in its activities, and in its entities. This specification assumes that a partial order exists between events. How practically such order is realized is beyond the scope of this specification. Possible implementations of that ordering include a single global notion of time and Lamport's style clocks.</p>
-<p> In this specification, the qualifier 'identifiable' is implicit whenever a reference is made to an activity or an entity.</p>
-
+
+
+<section>
+<h4>Temporal Events</h4>
+Four kinds of discrete events underpin the PROV-DM data model. They are:
+<ol>
+<li>Generation of an entity by an activity: identifies the final instant of an entity's creation timespan, after which it becomes available for use.</li>
+<li>Usage of an entity by an activity: identifies the first instant of an entity's consumption timespan.</li>
+<li>Start of an activity: identifies the instant an activity, represented by an activity, starts;</li>
+<li>End of an activity: identifies the instant an activity, represented by an activity, ends.</li>
+</ol>
+</section>
+
+<section>
+<h4>Event Ordering</h4>
+
+
+<p><dfn id="dfn-follows">Follows</dfn> is a partial order between events, indicating that an event occurs after another. For convenience, <dfn id="dfn-precedes">precedes</dfn> is defined as the symmetric of follows. </p>
+
+<p>This specification introduces inference rules allowing such event ordering to be inferred from provenance constructs.</p>
+</section>
+
+ </section>
</section>
@@ -2181,25 +2217,6 @@
<p>It is OPTIONAL to assert time in use, generation, and activity records.</p>
-<section>
-<h4>Temporal Events</h4>
-Four kinds of discrete events underpin the PROV-DM data model. They are:
-<ol>
-<li>Generation of an entity by an activity: identifies the final instant of an entity's creation timespan, after which it becomes available for use.</li>
-<li>Usage of an entity by an activity: identifies the first instant of an entity's consumption timespan.</li>
-<li>Start of an activity: identifies the instant an activity, represented by an activity, starts;</li>
-<li>End of an activity: identifies the instant an activity, represented by an activity, ends.</li>
-</ol>
-</section>
-
-<section>
-<h4>Event Ordering</h4>
-
-
-<p><dfn id="dfn-follows">Follows</dfn> is a partial order between events, indicating that an event occurs after another. For convenience, <dfn id="dfn-precedes">precedes</dfn> is defined as the symmetric of follows. </p>
-
-<p>This specification introduces inference rules allowing such event ordering to be inferred from provenance constructs.</p>
-</section>
</section>
@@ -2918,6 +2935,7 @@
<section class="appendix">
<h2>Changes Since Previous Version</h2>
<ul>
+<li>11/21/11: Consolidation of event in section 2.1.2</li>
<li>11/21/11: Added wasStartedBy between activities</li>
<li>11/21/11: Added wasInformedBy-ordering constraint.</li>
<li>11/17/11: Added Traceability Record.</li>