replaced BOB by entity, and entity by thing
authorLuc Moreau <l.moreau@ecs.soton.ac.uk>
Wed, 03 Aug 2011 12:04:24 +0100 (2011-08-03)
changeset 81 82a6e2967830
parent 80 001d8fbc9235
child 82 2fecc185c483
replaced BOB by entity, and entity by thing
model/ProvenanceModel.html
model/extra.css
--- a/model/ProvenanceModel.html	Tue Aug 02 22:01:11 2011 -0400
+++ b/model/ProvenanceModel.html	Wed Aug 03 12:04:24 2011 +0100
@@ -123,7 +123,7 @@
 <p>Let us consider a shared file system in which journalists Alice, Bob, Charles, David, and Edith can share and edit a crime statistics file.
 
 <p>
-Time t: Alice creates an empty file in /share/crime.txt. This is recorded as BOB e1.
+Time t: Alice creates an empty file in /share/crime.txt. This is recorded as entity e1.
 </p>
 
 <p>
@@ -131,14 +131,14 @@
 <pre>
 There was a lot of crime in London last month.
 </pre>
-This is recorded as BOB e2.
+This is recorded as entity e2.
 </p>
 
 <p>Time t+2: Charles emails the contents of /share/crime.txt
 <pre>
 cat /share/crime.txt | sendmail ...
 </pre>
-This is BOB e4.
+This is entity e4.
 </p>
 
 <p>
@@ -146,17 +146,17 @@
 <pre>
 There was a lot of crime in London and New-York last month.
 </pre>
-This is BOB e3.
+This is entity e3.
 </p>
 
 <p>Time t+4: Edith emails the contents of /share/crime.txt
 <pre>
 cat /share/crime.txt | sendmail ...
 </pre>
-This is BOB e5.
+This is entity e5.
 </p>
 
-<p>During interval [t+3, t+4[ a separate assertion is made about the characterized entity represented by the file. This includes the new <em>disclaimer</em> attribue and is recorded as BOB e6. 
+<p>During interval [t+3, t+4[ a separate assertion is made about the characterized thing represented by the file. This includes the new <em>disclaimer</em> attribue and is recorded as entity e6. 
 <pre>
 cat /share/crime.txt | sendmail ...
 </pre>
@@ -168,15 +168,15 @@
     <section> 
 <h3>Encoding in PIL</h3>
 <p>
-BOBs:
+Entities:
 <pre>
-bob(e0, [ type: "File", location: "/shared/crime.txt", creator: "Alice" ])
-bob(e1, [ type: "File", location: "/shared/crime.txt", creator: "Alice", content: "" ])
-bob(e2, [ type: "File", location: "/shared/crime.txt", creator: "Alice", content: "There was a lot of crime in London last month."])
-bob(e3, [ type: "File", location: "/shared/crime.txt", creator: "Alice", content: "There was a lot of crime in London and New York last month."])
-bob(e4)
-bob(e5)
-bob(e6, [ type: "File", location: "/shared/crime.txt", creator: "Alice", content: "There was a lot of crime in London and New York last month.", disclaimer: "some text"])
+entity(e0, [ type: "File", location: "/shared/crime.txt", creator: "Alice" ])
+entity(e1, [ type: "File", location: "/shared/crime.txt", creator: "Alice", content: "" ])
+entity(e2, [ type: "File", location: "/shared/crime.txt", creator: "Alice", content: "There was a lot of crime in London last month."])
+entity(e3, [ type: "File", location: "/shared/crime.txt", creator: "Alice", content: "There was a lot of crime in London and New York last month."])
+entity(e4)
+entity(e5)
+entity(e6, [ type: "File", location: "/shared/crime.txt", creator: "Alice", content: "There was a lot of crime in London and New York last month.", disclaimer: "some text"])
 </pre>
 </p>
 
@@ -189,7 +189,7 @@
 <tr><td>e3:</td><td> holds in interval [t+3,t+4[</td></tr>
 <tr><td>e4:</td><td> the information piped to sendmail at t+2 (that's a copy of e2's content)</td></tr>
 <tr><td>e5:</td><td> the information piped to sendmail at t+4 (that's a copy of e3's content)</td></tr>
-<tr><td>e6:</td><td> holds in interval [t+3,t+4[; a different view of the characterized entity represented by e3. </td></tr>
+<tr><td>e6:</td><td> holds in interval [t+3,t+4[; a different view of the characterized thing represented by e3. </td></tr>
 </table>
 </p>
 
@@ -246,26 +246,26 @@
 ivpOf(e3,e0)
 ivpOf(e6,e3) 
 </pre>
-Note that e6 strictly contains all of e3's attributes, and it has an extra one, "disclaimer", and is therefore an ivpOf e3. Note that no other assertions (i.e., on generation) is available for this BOB.
+Note that e6 strictly contains all of e3's attributes, and it has an extra one, "disclaimer", and is therefore an ivpOf e3. Note that no other assertions (i.e., on generation) is available for this entity.
 </p>
 
 
 <p>
 Agents:
 <pre>
-bob(ag_al, [ type: "Person", name: "Alice" ])
+entity(ag_al, [ type: "Person", name: "Alice" ])
 agent(ag_al)
 
-bob(ag_bo, [ type: "Person", name: "Bob" ])
+entity(ag_bo, [ type: "Person", name: "Bob" ])
 agent(ag_bo)
 
-bob(ag_ch, [ type: "Person", name: "Charles" ])
+entity(ag_ch, [ type: "Person", name: "Charles" ])
 agent(ag_ch)
 
-bob(ag_da, [ type: "Person", name: "David" ])
+entity(ag_da, [ type: "Person", name: "David" ])
 agent(ag_da)
 
-bob(ag_ed, [ type: "Person", name: "Edith" ])
+entity(ag_ed, [ type: "Person", name: "Edith" ])
 agent(ag_ed)
 </pre>
 </p>
@@ -305,7 +305,7 @@
 
 <p>In the world (whether real or not), there are entities, which can be
 physical, digital, conceptual, or otherwise, and activities involving
-entities.  Words such entity or activity should be understood with
+entities.  Words such thing or activity should be understood with
 their informal meaning.</p>
 
 <p>Furthermore, this specification is concerned with <em>characterized
@@ -346,7 +346,7 @@
 
 
 <p>In this specification, when an assertion is defined to refer to another assertion about something, it does so by means of that thing's identifier.<p>
-
+<div class='note'>This occurrence of thing should be changed.</div>
 <p>
 Sometimes, inferences about the world can be made from assertions of the provenance data model. When this is the case, this specification defines such inferences.
 </p>
@@ -365,19 +365,17 @@
     
     <section> 
       
-<h3>BOB</h3>
+<h3>Entity</h3>
 
-<div class='issue'>The name BOB is a placeholder. The WG still has to choose a name for this construct. This is <a href="http://www.w3.org/2011/prov/track/issues/30">ISSUE-30</a></div>
- 
-<p>A  <dfn id="dfn-bob" title="BOB">BOB</dfn> represents an identifiable characterized entity.</p>
+<p>An  <dfn id="dfn-entity" title="Entity">Entity</dfn> represents an identifiable characterized thing.</p>
 
-<p>A BOB assertion
- is about a characterized entity, whose  situation in the world is variant.
- A BOB assertion is made at a particular point and is invariant, in the sense that 
-all the attributes are assigned a value as part of that assertion.
+<p>An entity assertion
+ is about a characterized thing, whose  situation in the world may be variant.
+ An entity assertion is made at a particular point and is invariant, in the sense that 
+its attributes are assigned a value as part of that assertion.
 </p>
 
-<p>A BOB assertion, noted <b>bob(id, [ attr: val, ...])</b>:
+<p>An entity assertion, noted <b>entity(id, [ attr: val, ...])</b>:
 <ul>
 <li> contains an identifier <b>id</b>;</li>
 <li> contains a set of attribute-value pairs <b>[ attr: val, ...]</b>.</li>
@@ -385,22 +383,26 @@
 
 <p>
 <pre class="example">
-bob(e0, [ type: "File", location: "/shared/crime.txt", creator: "Alice" ])
+entity(e0, [ type: "File", location: "/shared/crime.txt", creator: "Alice" ])
 </pre>
 </p>
 
 
-<p>A BOB assertion MUST describe a characterized entity over a continuous time interval in the world (which may collapse into a single instant).
-Characterizing an entity over multiple time intervals requires multiple BOB assertions, each with its own identifier. Some attributes may retain their values across multiple assertions.</p>
+<p>An entity assertion MUST describe a characterized thing over a continuous time interval in the world (which may collapse into a single instant).
+Characterizing a thing over multiple time intervals requires multiple entity assertions, each with its own identifier. Some attributes may retain their values across multiple assertions.</p>
 
 <p>There is no assumption that the set of attributes is complete and
 that the attributes are independent/orthogonal of each other.</p>
 
-<div class='issue'>Characterized entity may be variant. This is <a href="http://www.w3.org/2011/prov/track/issues/32">ISSUE-32</a></div>
+<div class='pending'>Characterized entity may be variant. This is <a href="http://www.w3.org/2011/prov/track/issues/32">ISSUE-32</a></div>
 
 <div class='issue'>How is domain specific data combined with the provenance model? This is <a href="http://www.w3.org/2011/prov/track/issues/65">ISSUE-65</a>.</div>
 
 <div class='issue'> Comments on bob <a href="http://www.w3.org/2011/prov/track/issues/60">ISSUE-60</a>.</div>
+
+<div class='resolved'>The name <b>entity</b> is used as a replacement for placeholder BOB. This is <a href="http://www.w3.org/2011/prov/track/issues/30">ISSUE-30</a>.</div>
+ 
+
     </section> 
 
     <section id="concept-ProcessExecution"> 
@@ -438,16 +440,16 @@
 
 
 
-<p><dfn id="dfn-Generation">Generation</dfn> represents the creation of a new characterized entity by an activity. This characterized entity did not exist before creation.</p>
+<p><dfn id="dfn-Generation">Generation</dfn> represents the creation of a new characterized thing by an activity. This characterized thing did not exist before creation.</p>
 
 
 
 <p>A Generation assertion, noted <b>isGeneratedBy(b,pe,r,t)</b>:
 <ul>
-<li> refers to a BOB <b>b</b>, which represents the characterized entity that is created;
+<li> refers to an entity <b>b</b>, which represents the characterized thing that is created;
 <li> refers to a process execution <b>pe</b>;
 <li> contains a <a href="#concept-Role">role</a> <b>r</b>;
-<li> MAY contain a "generation time" <b>t</b>, the time at which the characterized entity was created.</p>
+<li> MAY contain a "generation time" <b>t</b>, the time at which the characterized thing was created.</p>
 </ul>
 </p>
 
@@ -457,13 +459,13 @@
 </pre>
 </p>
 
-<p>A given BOB can be generated at most by one process execution.</p>
+<p>A given entity can be generated at most by one process execution.</p>
 
 <p>Given an assertion <b>isGeneratedBy(x,pe,r)</b> or <b>isGeneratedBy(x,pe,r,t)</b>, the
 activity denoted by <b>pe</b> and the entities used by <b>pe</b> dermine values of some of <b>x</b>'s attributes.</p>
 
 <p>Given an assertion <b>isGeneratedBy(x,pe,r)</b> or <b>isGeneratedBy(x,pe,r,t)</b>, one can
-infer that the generation of the entity denoted by <b>x</b> precedes the end
+infer that the generation of the thing denoted by <b>x</b> precedes the end
 of <b>pe</b> and follows the beginning of <b>pe</b>. 
 </p> 
 
@@ -480,15 +482,15 @@
 
 <div class='issue'>Various comments raised at <a href="http://www.w3.org/2011/prov/track/issues/64">ISSUE-64</a>.</div>
 
-<p><dfn id="dfn-Use">Use</dfn> represents the consumption of a characterized entity by an activity.</p>
+<p><dfn id="dfn-Use">Use</dfn> represents the consumption of a characterized thing by an activity.</p>
 
 
 <p>A Use assertion, <b>uses(pe,b,r,t)</b>:
 <ul>
 <li> refers to a process execution <b>pe</b>;
-<li> refers to a BOB <b>b</b>, representing the characterized entity that is used;
+<li> refers to an entity <b>b</b>, representing the characterized thing that is used;
 <li> contains a <a href="#concept-Role">role</a> <b>r</b>;
-<li> MAY contain a "use time" <b>t</b>, the time at which the characterized entity was used.</p>
+<li> MAY contain a "use time" <b>t</b>, the time at which the characterized thing was used.</p>
 </ul>
 </p>
 
@@ -499,7 +501,7 @@
 </p>
 
 
-<p>A reference to a given BOB may appear in multiple use assertions that refer
+<p>A reference to a given entity may appear in multiple use assertions that refer
 to a given process execution, but each of those use assertions MUST have a
 distinct role.</p>
 
@@ -513,9 +515,9 @@
 
 
 <p>Given an assertion <b>uses(pe,x,r)</b> or <b>uses(pe,x,r,t)</b>, one can
-infer that the use of the entity denoted by <b>x</b> precedes the end
+infer that the use of the thing denoted by <b>x</b> precedes the end
 of <b>pe</b> and follows the beginning of <b>pe</b>. Furthermore, we
-can infer that the generation of the entity <b>x</b> always precedes
+can infer that the generation of the thing <b>x</b> always precedes
 its use.  </p>
 
 
@@ -528,12 +530,12 @@
 <h3>Derivation</h3>
 
 
-<p><dfn id="dfn-Derivation">Derivation</dfn> expresses that some characterized entity is transformed from, created from, or affected by another characterized entity.  </p>
+<p><dfn id="dfn-Derivation">Derivation</dfn> expresses that some characterized thing is transformed from, created from, or affected by another characterized thing.  </p>
 
 <p>A Derivation assertion, <b>isDerivedFrom(b1,b2)</b>:
 <ul>
-<li> refers to a BOB <b>b1</b>, denoting the generated characterized entity;
-<li> refers to a BOB <b>b2</b>, denoting the used characterized entity.
+<li> refers to an entity <b>b1</b>, denoting the generated characterized thing;
+<li> refers to an entity <b>b2</b>, denoting the used characterized thing.
 </ul>
 </p>
 
@@ -551,14 +553,14 @@
 
 
 <p>Given an assertion <b>isDerivedFrom(B,A)</b>, one can infer that the use
-of characterized entity denoted by <b>A</b> precedes the generation of
-the characterized entity denoted by <b>B</b>.
+of characterized thing denoted by <b>A</b> precedes the generation of
+the characterized thing denoted by <b>B</b>.
 
 <section>
 <h4>Relationship between derivation and process execution</h4>
 
 
-<p>A derivation, which by definition expresses that some characterized entity is transformed from, created from, or affected by another characterized entity, entails a process execution that transforms, creates or affects this characterized entity.</p>
+<p>A derivation, which by definition expresses that some characterized thing is transformed from, created from, or affected by another characterized thing, entails a process execution that transforms, creates or affects this characterized thing.</p>
 
 <p>This is formalized by the following inference rule, referred to as <em>process execution introduction</em>:<br/>
 if <b>isDerivedFrom(e1,e0)</b> holds, then there exists a process execution <b>pe</b>, and roles <b>r0</b>,<b>r1</b>,
@@ -596,7 +598,7 @@
 
 <div class='issue'> Transitivity does not seem to follow from above definition. This is <a href="http://www.w3.org/2011/prov/track/issues/56">ISSUE-56</a>.</div>
 
-<div class='issue'> What's the difference between one step and multi-step derivation assertion. Justification of why one BOB can be generated at most once.  Multi-step derivation is also transitive. This is all in <a href="http://www.w3.org/2011/prov/track/issues/67">ISSUE-67</a>.</div>
+<div class='issue'> What's the difference between one step and multi-step derivation assertion. Justification of why one entity can be generated at most once.  Multi-step derivation is also transitive. This is all in <a href="http://www.w3.org/2011/prov/track/issues/67">ISSUE-67</a>.</div>
 
 
 </section>
@@ -606,24 +608,24 @@
 
 
 
-<p>An <dfn id="dfn-Agent">agent</dfn> represents a characterized entity capable of
+<p>An <dfn id="dfn-Agent">agent</dfn> represents a characterized thing capable of
 activity.</p> 
 
 <p> An agent assertion, <b>agent(b)</b>:
 <ul>
-<li> refers to a BOB <b>b</b>
+<li> refers to an entity <b>b</b>
 </ul>
 </p>
 
-<p>A characterized entity can be asserted to be an agent or can be inferred to be
+<p>A characterized thing can be asserted to be an agent or can be inferred to be
 an agent by involvement in a process execution.  </p>
 
 <p>
 <pre class="example">
-bob(alice, [Employee="1234"])  and agent(alice)
+entity(alice, [Employee="1234"])  and agent(alice)
 
 
-bob(david) and isControlledBy(pe,david)
+entity(david) and isControlledBy(pe,david)
 </pre>
 </p>
 
@@ -635,12 +637,12 @@
 <section id="concept-Control">
 <h3>Control</h3>
 
-<p> <dfn id="dfn-Control">Control</dfn> represents the involvement of an agent or a BOB in a process execution; a role qualifies this involvement.</p>
+<p> <dfn id="dfn-Control">Control</dfn> represents the involvement of an agent or an entity in a process execution; a role qualifies this involvement.</p>
 
 <p>A Control assertion, noted <b>isControlledBy(pe,ag,r)</b>:
 <ul>
 <li> refers to a process execution <b>pe</b>;
-<li> refers to an agent or a BOB <b>ag</b>;
+<li> refers to an agent or an entity <b>ag</b>;
 <li> contains a role <b>r</b>.
 </ul>
 </p>
@@ -662,36 +664,36 @@
 
 <p><dfn id="IVP-of">IVP of</dfn> is a relationship between two characterized entities asserted to have compatible characterization over some continuous time interval.<br/>
 
-The rationale for introducing this relationship is that in general, at any given time there will be multiple representations of a characterized entity, which are reflected in assertions possibly made by different asserters. In the example that follows, suppose entity "Royal Society" is represented by two asserters, each using a different set of attributes. If the asserters agree that both representations refer to "The  Royal Society", the question of whether any correspondence can be established between the two representations arises naturally. This is particularly relevant when (a) the sets of properties used by the two representations overlap partially, or (b) when one set is subsumed by the other. In both these cases, we have a situation where each of the two asserters has a partial view of "The  Royal Society", and establishing a correspondence between them on the shared properties is beneficial, as in case (a) each of the two representation <em>complements</em> the other, and in case (b) one of the two (that with the additional properties) complements the other.
+The rationale for introducing this relationship is that in general, at any given time there will be multiple representations of a characterized thing, which are reflected in assertions possibly made by different asserters. In the example that follows, suppose thing "Royal Society" is represented by two asserters, each using a different set of attributes. If the asserters agree that both representations refer to "The  Royal Society", the question of whether any correspondence can be established between the two representations arises naturally. This is particularly relevant when (a) the sets of properties used by the two representations overlap partially, or (b) when one set is subsumed by the other. In both these cases, we have a situation where each of the two asserters has a partial view of "The  Royal Society", and establishing a correspondence between them on the shared properties is beneficial, as in case (a) each of the two representation <em>complements</em> the other, and in case (b) one of the two (that with the additional properties) complements the other.
 <p/>
-This intuition is made more precise by considering the BOBs that embody the representation of a characterised entity at a certain point in time. A BOB, as defined above, exists only as long as all of its attributes do not change their value. As soon as one attribute, say X changes value, say from v1 to v2, the BOB no longer exists and is replaced by a new one in which X=v2. Thus, if we overlap the timelines (or, more generally, the sequences of value-changing events) for the two characterised entities, we can hope two establish correspondences amongst the BOBs that represent them at various points along that events line. The figure below illustrates this intuition.<p/>
+This intuition is made more precise by considering the entities that embody the representation of a characterised thing at a certain point in time. an entity, as defined above, exists only as long as all of its attributes do not change their value. As soon as one attribute, say X changes value, say from v1 to v2, the entity no longer exists and is replaced by a new one in which X=v2. Thus, if we overlap the timelines (or, more generally, the sequences of value-changing events) for the two characterised entities, we can hope two establish correspondences amongst the entities that represent them at various points along that events line. The figure below illustrates this intuition.<p/>
 
 <img src="complement-of.png"/>
 
 <p/>
-Relation <em>complement-of</em> between two BOBs is intended to capture these correspondences, as follows. Suppose BOBs A and B share a set P of properties, and each of them has other properties in addition to P. If the values assigned to each property in P are <em>compatible</em> between A and B, then we say that <em>A is-complement-of B</em>, and <em>B is-complement-of A</em>, in a symmetrical fashion. In the particular case where the set P of properties of B is a struct superset of A's properties, then we say that <em>B is-complement-of A</em>, but in this case the opposite does not hold. In this case, the relation is not symmetric.  (as a special case, A and B may not share any attributes at all, and yet the asserters may still stipulate that they are representing the same entity "Royal Society". The symmetric relation may hold trivially in this case).
+Relation <em>complement-of</em> between two entities is intended to capture these correspondences, as follows. Suppose entities A and B share a set P of properties, and each of them has other properties in addition to P. If the values assigned to each property in P are <em>compatible</em> between A and B, then we say that <em>A is-complement-of B</em>, and <em>B is-complement-of A</em>, in a symmetrical fashion. In the particular case where the set P of properties of B is a struct superset of A's properties, then we say that <em>B is-complement-of A</em>, but in this case the opposite does not hold. In this case, the relation is not symmetric.  (as a special case, A and B may not share any attributes at all, and yet the asserters may still stipulate that they are representing the same thing "Royal Society". The symmetric relation may hold trivially in this case).
 <p/>
-The term <em>compatible</em> used above means that a mapping can be established amongst the values of attributes in P and found in the two BOBs. This is generalizes to the case where attribute sets P1 and P2 of A, and B, respectively, are not identical but they can be mapped to one another. The simplest case is the identity mapping, in which A and B share attribute set P, and furthermore the values assigned to attributes in P match exactly.<br/>
+The term <em>compatible</em> used above means that a mapping can be established amongst the values of attributes in P and found in the two entities. This is generalizes to the case where attribute sets P1 and P2 of A, and B, respectively, are not identical but they can be mapped to one another. The simplest case is the identity mapping, in which A and B share attribute set P, and furthermore the values assigned to attributes in P match exactly.<br/>
 
-It is important to note that the relation holds only as long as the BOBs involved are valid. As soon as one attribute changes value in one of them, new correspondences need to be found amongst the new BOBs. Thus, the relation has a validity span that can be expressed in terms of the event lines of the entity.
+It is important to note that the relation holds only as long as the entities involved are valid. As soon as one attribute changes value in one of them, new correspondences need to be found amongst the new entities. Thus, the relation has a validity span that can be expressed in terms of the event lines of the thing.
 
 <!--
-The "IVP of" relationship is designed to represent pairs of BOBs that correspond to each other. By their own nature, a BOB remains valid only as long as all of its attributes do not change their value. It follows that the correspondence "B IVP of A" is only valid within the time interval during which such invariance property holds for both A and B. When any of the property values change in either A or B, those BOBs are replaced by new ones, and a new correspondence may be established. Thus, "IVP of" is defined relative to the intersection of the temporal intervals for which A and B are valid.
+The "IVP of" relationship is designed to represent pairs of entities that correspond to each other. By their own nature, an entity remains valid only as long as all of its attributes do not change their value. It follows that the correspondence "B IVP of A" is only valid within the time interval during which such invariance property holds for both A and B. When any of the property values change in either A or B, those entities are replaced by new ones, and a new correspondence may be established. Thus, "IVP of" is defined relative to the intersection of the temporal intervals for which A and B are valid.
 -->
 </p>
 
-<p>An IVP assertion is denoted <b>ivpOf(B,A)</b>, where A and B are two BOBs.
+<p>An IVP assertion is denoted <b>ivpOf(B,A)</b>, where A and B are two entities.
 
 <p>
 <pre class="example">
-bob(rs,[created: "1870"])
+entity(rs,[created: "1870"])
 
-bob(rs_l1,[location: "loc2"])
-bob(rs_l2,[location: "The Mall"])
+entity(rs_l1,[location: "loc2"])
+entity(rs_l2,[location: "The Mall"])
 
-bob(rs_m1,[membership: "250", year: "1900"])
-bob(rs_m2,[membership: "300", year: "1945"])
-bob(rs_m3,[membership: "270",  year: "2010"])
+entity(rs_m1,[membership: "250", year: "1900"])
+entity(rs_m2,[membership: "300", year: "1945"])
+entity(rs_m3,[membership: "270",  year: "2010"])
 
 ivpOf(rs_m3, rs_l2)
 ivpOf(rs_m2, rs_l1)
@@ -737,8 +739,8 @@
 <h4>Temporal Events</h4>
 Four kinds of discrete events underpin the provenance language. They are:
 <ol>
-<li>Generation of a BOB by a process execution:  identifies the final instant of a BOB's creation timespan, after which the characterized entity represented by a BOB becomes available for use.</li>
-<li>Use of a BOB by a process execution:  identifies the first instant of a BOB's consumption timespan.</li>
+<li>Generation of an entity by a process execution:  identifies the final instant of an entity's creation timespan, after which the characterized thing represented by an entity becomes available for use.</li>
+<li>Use of an entity by a process execution:  identifies the first instant of an entity's consumption timespan.</li>
 <li>Start of a process execution: identifies the instant an activity represented by a the process execution starts</li>
 <li>End of a process execution: identifies the instant an activity represented by a process execution ends</li>
 </ol>
@@ -778,7 +780,7 @@
 <h3>Role</h3>
 
 
-<p>A <dfn id="dfn-Role">role</dfn> is a label that names the function assumed by a BOB or
+<p>A <dfn id="dfn-Role">role</dfn> is a label that names the function assumed by an entity or
 an agent with respect to a specific process execution.</p> 
 
 <p>Use, Generation, and Control assertions MUST contain a role.  Roles
@@ -819,7 +821,7 @@
 
 <p>
 Location is an OPTIONAL characteristics of 
-BOB, process execution, and agent.
+entity, process execution, and agent.
 </p>
 
 
@@ -834,7 +836,7 @@
 <dfn id="ControlOrdering">Control ordering</dfn> means that the end of
 a process execution precedes the start of another process execution,
 by a same agent.
-<dfn id="InformationOrdering">Information flow</dfn> means that a characterized entity was generated by a process execution before it was used by another process execution.
+<dfn id="InformationOrdering">Information flow</dfn> means that a characterized thing was generated by a process execution before it was used by another process execution.
 </p>
 
 <p>An assertion isScheduledAfter:
@@ -857,12 +859,12 @@
 <section id="concept-Revision">
 <h3>Revision</h3>
 
-<p> <dfn id="dfn-Revision">Revision</dfn> represents the creation of a characterized entity considered to be a variant of another. </p>
+<p> <dfn id="dfn-Revision">Revision</dfn> represents the creation of a characterized thing considered to be a variant of another. </p>
 
 <p>An assertion isRevisionOf, noted <b>isRevisionOf(b2,b1,ag)</b>:
 <ul>
-<li> refers to a BOB <b>b2</b>, denoting a newer version of an entity;
-<li> refers a BOB <b>b1</b>, denoting a older version of an entity;
+<li> refers to an entity <b>b2</b>, denoting a newer version of a thing;
+<li> refers to an entity <b>b1</b>, denoting a older version of a thing;
 <li> MAY refer to a responsible agent <b>ag</b>.
 </ul>
 </p>
@@ -871,8 +873,8 @@
 <p>
 From an assertion <b>isRevisionOf(new,old,ag)</b>, one can infer that: 
 <ul>
-<li> The characterized entity denoted by <b>new</b> is derived from the characterized entity denoted by <b>old</b>
-<li> There exists a BOB <b>X</b>, such that:
+<li> The characterized thing denoted by <b>new</b> is derived from the characterized thing denoted by <b>old</b>
+<li> There exists an entity <b>X</b>, such that:
 <ul> 
 <li> <b>new</b> isIVP of <b>X</b>;
 <li> <b>old</b> isIVP of <b>X</b>;
@@ -941,11 +943,11 @@
 
 <li>The graphical illustration is a graph. </li>
 
-<li>BOBs, process executions and agents are represented as nodes, with oval, rectangular, and half-hexagonal shapes, respectively.  </li>
+<li>entities, process executions and agents are represented as nodes, with oval, rectangular, and half-hexagonal shapes, respectively.  </li>
 
 <li>Use, Generation, Derivation, IVPof are represented as directed edges.</li>
 
-<li>BOBs are layed out according to temporal order (the temporal event at which they are generated).  Time SHOULD progress from left to right or from top to bottom.  This means that edges for Use, Generation and Derivation typically point from right to left or from bottom to top.</li>
+<li>entities are layed out according to temporal order (the temporal event at which they are generated).  Time SHOULD progress from left to right or from top to bottom.  This means that edges for Use, Generation and Derivation typically point from right to left or from bottom to top.</li>
 
 </ul>
 
--- a/model/extra.css	Tue Aug 02 22:01:11 2011 -0400
+++ b/model/extra.css	Wed Aug 03 12:04:24 2011 +0100
@@ -4,7 +4,7 @@
     padding:    1em;
     margin: 1em 0em 0em;
     border: 1px solid #f00;
-    background: #ff0;
+    background: #BFEFFF;
 }
 
 .pending::before {
@@ -17,3 +17,22 @@
     background: #fff;
     padding:    3px 1em;
 }
+
+
+.resolved {
+    padding:    1em;
+    margin: 1em 0em 0em;
+    border: 1px solid #f00;
+    background: #9BCD9B;
+}
+
+.resolved::before {
+    content:    "Resolved";
+    display:    block;
+    width:  150px;
+    margin: -1.5em 0 0.5em 0;
+    font-weight:    bold;
+    border: 1px solid #f00;
+    background: #fff;
+    padding:    3px 1em;
+}