--- a/model/prov-dm.html Thu Mar 08 22:17:05 2012 +0000
+++ b/model/prov-dm.html Thu Mar 08 22:29:15 2012 +0000
@@ -372,7 +372,7 @@
<p>
<div class="glossary-ref" ref="glossary-entity">
</div>
-</p>
+
<div class="anexample" id="entity-example">
@@ -423,12 +423,12 @@
<p>
<div class="glossary-ref" ref="glossary-generation">
</div>
-</p>
+
<p>
<div class="glossary-ref" ref="glossary-usage">
</div>
-</p>
+
@@ -437,21 +437,21 @@
program, the completed creation of a linked data set, and the completed
publication of a new version of a document.
</div>
-</p>
+
<p>
<div class="anexample" id="usage-example">
Usage examples include a procedure beginning to consume an argument, a service starting to read a value on a port, a program beginning to read a configuration
file, or the point at which an ingredient, such as eggs, is being added in a baking activity. Usage may entirely consume an entity (e.g. eggs are no longer available after being added to
the mix); alternatively, a same entity may be used multiple times, possibly by different activities (e.g. a file on a file system can be read indefinitely).
-</div></p>
+</div>
<p>Activities are consumers of entities and producers of entities. In some case, the consumption of an entity influences the creation of another in some way. This notion is captured by derivations, defined as follows.</p>
<p>
<span class="glossary-ref" ref="glossary-derivation">
-</p>
+
<div class="anexample" id="derivation-example">
@@ -607,7 +607,7 @@
<figure style="max-width: 70%; " >
- <embed src="images/OverviewDiagram.svg" width="600" height="400" alt="PROV-DM overview" type="image/svg+xml" ></embed>
+<embed src="images/OverviewDiagram.svg" width="600" height="400" alt="PROV-DM overview" type="image/svg+xml"></embed>
<!--
<img src="images/OverviewDiagram.svg" alt="PROV-DM overview" style="max-width: 70%; " />-->
@@ -855,10 +855,10 @@
<h4>Entity</h4>
-<div class="glossary-ref" ref="glossary-entity" withspan='true'></div>
-
-
-<p><div class="attributes" id="attributes-entity">An entity<span class="withPn">, written <span class="pnExpression" id="pn-entity">entity(id, [ attr1=val1, ...])</span> in PROV-N, </span> contains:</p>
+<div class="glossary-ref" ref="glossary-entity" withspan="true"></div>
+
+
+<p><div class="attributes" id="attributes-entity">An entity<span class="withPn">, written <span class="pnExpression" id="pn-entity">entity(id, [ attr1=val1, ...])</span> in PROV-N, </span> contains:
<ul>
<li><span class='attribute'>id</span>: an identifier for an entity; </li>
<li><span class='attribute'>attributes</span>: an OPTIONAL set of attribute-value pairs representing this entity's situation in the world.</li>
@@ -908,7 +908,7 @@
<h3>Activity</h3>
-<div class="glossary-ref" ref="glossary-activity" withspan='true'></div>
+<div class="glossary-ref" ref="glossary-activity" withspan="true"></div>
<p><div class="attributes" id="attributes-activity"> An activity<span class="withPn">, written <span class="pnExpression" id="pn-activity">activity(id, st, et, [ attr1=val1, ...])</span> in PROV-N,</span> contains:</p>
<ul>
@@ -945,10 +945,10 @@
<section id="term-Agent">
<h3>Agent</h3>
-<div class="glossary-ref" ref="glossary-agent" withspan='true'></div>
-
-
-<p><div class="attributes" id="attributes-agent">An agent<span class="withPn">, noted <span class="pnExpression" id="pn-agent">agent(id, [ attr1=val1, ...])</span> in PROV-N,</span> contains:</p>
+<div class="glossary-ref" ref="glossary-agent" withspan="true"></div>
+
+
+<p><div class="attributes" id="attributes-agent">An agent<span class="withPn">, noted <span class="pnExpression" id="pn-agent">agent(id, [ attr1=val1, ...])</span> in PROV-N,</span> contains:
<ul>
<li><span class='attribute'>id</span>: an identifier for an agent;</li>
<li><span class='attribute'>attributes</span>: a set of attribute-value pairs representing this agent's situation in the world.
@@ -1064,10 +1064,10 @@
<section id="term-Generation">
<h4>Generation</h4>
-<div class="glossary-ref" ref="glossary-generation" withspan='true'></div>
+<div class="glossary-ref" ref="glossary-generation" withspan="true"></div>
<p>
-<div class="attributes" id="attributes-generation"><dfn title="dfn-Generation">Generation</dfn><span class="withPn">, written <span class="pnExpression">wasGeneratedBy(id,e,a,t,attrs)</span> in PROV-N,</span> has the following components:</p>
+<div class="attributes" id="attributes-generation"><dfn title="dfn-Generation">Generation</dfn><span class="withPn">, written <span class="pnExpression">wasGeneratedBy(id,e,a,t,attrs)</span> in PROV-N,</span> has the following components:
<ul>
<li><span class='attribute'>id</span>: an OPTIONAL identifier for a generation;</li>
<li><span class='attribute'>entity</span>: an identifier for a created entity; </li>
@@ -1114,7 +1114,7 @@
<section id="term-Usage">
<h3>Usage</h3>
-<div class="glossary-ref" ref="glossary-usage" withspan='true'></div>
+<div class="glossary-ref" ref="glossary-usage" withspan="true"></div>
<p><div class="attributes" id="attributes-usage"><dfn title="dfn-Usage">Usage</dfn><span class="withPn">, written <span class="pnExpression">used(id,a,e,t,attrs)</span> in PROV-N,</span> has the following constituents:</p>
@@ -1171,14 +1171,14 @@
<section id="term-ActivityAssociation">
<h4>Activity Association</h4>
-<div class="glossary-ref" ref="glossary-activityAssociation" withspan='true'></div>
+<div class="glossary-ref" ref="glossary-activityAssociation" withspan="true"></div>
<p>As far as responsibility is concerned, PROV-DM offers two kinds of constructs. The first, introduced in this section, is a relation between an agent, a plan, and an activity; the second, introduced in <a
href="#term-responsibility">Section Responsibility</a>, is a relation between agents expressing that an agent was acting on behalf of another, in the context of an activity. </p>
<p><div class="attributes" id="attributes-activity-association">An <dfn title="dfn-activity-association">activity association</dfn><span class="withPn">, written <span class="pnExpression">wasAssociatedWith(id,a,ag,pl,attrs)</span> in PROV-N,</span> has the following
-constituents:</p>
+constituents:
<ul>
<li><span class='attribute'>id</span>: an OPTIONAL identifier for the association between an activity and an agent;</li>
<li><span class='attribute'>activity</span>: an identifier for the activity;</li>
@@ -1270,7 +1270,7 @@
<h4>Responsibility Chain</h4>
-<div class="glossary-ref" ref="glossary-responsibilityChain" withspan='true'></div>
+<div class="glossary-ref" ref="glossary-responsibilityChain" withspan="true"></div>
<p>PROV-DM offers a mild version of responsibility
in the form of a relation to represent when an agent acted on another
@@ -1295,7 +1295,7 @@
might be a need to define specific aspects of control that various
agents exert over a given activity.</p>
-<p><div class="attributes" id="attributes-responsibility-chain">A <dfn title="dfn-responsibility-chain">responsibility chain</dfn><span class="withPn">, written <span class="pnExpression">actedOnBehalfOf(id,ag2,ag1,a,attrs)</span> in PROV-N,</span> has the following constituents:</p>
+<p><div class="attributes" id="attributes-responsibility-chain">A <dfn title="dfn-responsibility-chain">responsibility chain</dfn><span class="withPn">, written <span class="pnExpression">actedOnBehalfOf(id,ag2,ag1,a,attrs)</span> in PROV-N,</span> has the following constituents:
<ul>
<li><span class='attribute'>id</span>: an OPTIONAL identifier for the responsibility chain;</li>
<li><span class='attribute'>subordinate</span>: an identifier for the agent associated with an activity, acting on behalf of the responsible
@@ -1333,7 +1333,7 @@
<h4>Derivation</h4>
-<div class="glossary-ref" ref="glossary-derivation" withspan='true'></div>
+<div class="glossary-ref" ref="glossary-derivation" withspan="true"></div>
@@ -1343,7 +1343,7 @@
A derivation can be described at various levels of precision. In its simplest form, derivation relates two entities. Optionally, attributes can be added to describe modalities of derivation. If the derivation is the result of a single known activity, then this activity can also be optionally expressed. And to provide a completely accurate description of derivation, the generation and usage of the generated and used entities, respectively, can be provided. The reason for optional information such as activity, generation, and usage to be linked to derivations is to aid analysis of provenance and to facilitate provenance-based reproducibility. </p>
-<p><div class="attributes" id="attributes-derivation">A <dfn>derivation</dfn><span class="withPn">, written <span class="pnExpression" id="pn-wasDerivedFrom">wasDerivedFrom(id, e2, e1, a, g2, u1, attrs)</span> in PROV-N,</span> contains:</p>
+<p><div class="attributes" id="attributes-derivation">A <dfn>derivation</dfn><span class="withPn">, written <span class="pnExpression" id="pn-wasDerivedFrom">wasDerivedFrom(id, e2, e1, a, g2, u1, attrs)</span> in PROV-N,</span> contains:
<ul>
<li><em>id</em>: an OPTIONAL identifier for a derivation;</li>
<li><em>generatedEntity</em>: the identifier of the entity generated by the derivation;</li>
@@ -1420,8 +1420,7 @@
<p><div class="attributes" id="attributes-alternate">
-An <dfn title="dfn-Alternate">alternate relation</dfn><span class="withPn">, written <span class="pnExpression">alternateOf(alt1, alt2)</span> in PROV-N,</span> addresses case (1). It has the following constituents:</p>
-
+An <dfn title="dfn-Alternate">alternate relation</dfn><span class="withPn">, written <span class="pnExpression">alternateOf(alt1, alt2)</span> in PROV-N,</span> addresses case (1). It has the following constituents:
<ul>
<li><span class='attribute'>firstAlternate</span>: an identifier of the first of the two entities;</li>
<li><span class='attribute'>secondAlternate</span>: an identifier of the second of the two entities.</li>
@@ -1441,7 +1440,7 @@
<p>
<div class="attributes" id="attributes-specialization">
-A <dfn title="dfn-Specialization">specialization relation</dfn><span class="withPn">, written <span class="pnExpression">specializationOf(sub, super)</span> in PROV-N,</span> addresses case (2). It has the following constituents:</p>
+A <dfn title="dfn-Specialization">specialization relation</dfn><span class="withPn">, written <span class="pnExpression">specializationOf(sub, super)</span> in PROV-N,</span> addresses case (2). It has the following constituents:
<ul>
<li><span class='attribute'>specializedEntity</span>: an identifier of the specialized entity;</li>
@@ -1475,12 +1474,13 @@
<h4>Annotation</h4>
-<p>
-<div class="glossary" id="glossary-annotation">
-An <dfn title="concept-annotation">annotation</dfn> is a link between something that is identifiable and a note referred to by its identifier.</div>Multiple notes can
+
+<span class="glossary-ref" ref="glossary-annotation" withspan="true"></span>
+
+<p>Multiple notes can
be associated with a given identified object; symmetrically, multiple objects can be associated with a given note. Since notes have identifiers, they can also be
annotated. The annotation mechanism (with note and annotation) forms a key aspect of the extensibility mechanism of PROV-DM (see <a
-href="#extensibility-section">extensibility section</a>).</p>
+href="#extensibility-section">extensibility section</a>).</p>
<p>An <dfn title="dfn-annotation">annotation relation</dfn><span class="withPn">, written <span class="pnExpression">hasAnnotation(r,n)</span> in PROV-N,</span> has the following constituents:</p>
<ul>