example of specialization and constraint on alternate
authorLuc Moreau <l.moreau@ecs.soton.ac.uk>
Mon, 02 Apr 2012 13:51:47 +0100
changeset 2197 c5f4add94d48
parent 2196 142d6ad29c42
child 2198 471cf17a0ebd
example of specialization and constraint on alternate
model/prov-dm-constraints.html
--- a/model/prov-dm-constraints.html	Mon Apr 02 13:35:06 2012 +0100
+++ b/model/prov-dm-constraints.html	Mon Apr 02 13:51:47 2012 +0100
@@ -123,9 +123,9 @@
           // only "name" is required. Same format as editors.
  
       //authors:  ,
-          authors:  [
-              { name: "TBD" },
-         ],
+//          authors:  [
+//              { name: "TBD" },
+//         ],
           
           // name of the WG
           wg:           "Provenance Working Group",
@@ -1028,6 +1028,11 @@
 <p>Specialization is <em>transitive</em>. Indeed if <span class="name">specializationOf(e1,e2)</span> holds, then there is some common thing, say <span class="name">T1-2</span> they both refer to. Likewise, if <span class="name">specializationOf(e2,e3)</span> holds, then there is some common thing, say <span class="name">T2-3</span> they both refer to.  The Things <span class="name">T1-2</span> and <span class="name">T2-3</span> are the same since <span class="name">e2</span> refers to only one thing. </p>
 
 
+<div class="anexample" id="anexample-specialization-is-transitive">
+A specialization of "this  email message" would be, for example, the "printed version on my desk", which is a specialization of "my thoughts on this email thread".  So, the "printed version on my desk" is also a specialization   "my thoughts on this email thread".
+</div>
+
+
 </section> 
 
 <section id="term-Alternate">
@@ -1408,7 +1413,7 @@
 <a>precedes</a> the entity <a title="entity invalidation event">invalidation</a> event.
 </div>
 
-<p>Finally, for responsibility, two agents need to have some overlap.</p>
+<p>For responsibility, two agents need to have some overlap.</p>
 
 
 <div class='interpretation' id='actedOnBehalfOf-ordering'>
@@ -1422,6 +1427,24 @@
 <a>precedes</a>  <a title="entity invalidation event">invalidation</a> event for <span class="name">ag2</span>.
 </div>
 
+
+<p>Finally, two entities that are alternate of each other need to have some overlap.</p>
+
+<div class="note">
+Introduce a relation overlap to simplify these constraints
+</div>
+
+<div class='interpretation' id='alternate-ordering'>
+Given two agents <span class="name">e1</span> and <span class="name">e2</span>, <span class='conditional'>if</span> <span
+class="name">alternate(e2,e1)</span>
+ holds, <span class='conditional'>then</span> the following ordering constraints hold: the
+<a title="entity generation event">generation</a> event of the agent  denoted by <span class="name">e2</span>
+precedes the invalidation event of 
+agent <span class="name">e1</span>, and 
+ the <a title="entity generation event">generation event</a> for agent denoted by <span class="name">e1</span>
+<a>precedes</a>  <a title="entity invalidation event">invalidation</a> event for <span class="name">ag2</span>.
+</div>
+
 </section>
 
 <section id="structural-constraints">