--- a/model/prov-dm.html Wed Mar 28 11:45:12 2012 +0100
+++ b/model/prov-dm.html Wed Mar 28 11:53:40 2012 +0100
@@ -1,8 +1,5 @@
<!DOCTYPE html
-[
- <!ATTLIST tag ref CDATA #IMPLIED>
- <!ATTLIST withspan ref CDATA #IMPLIED>
-]>
+>
<html><head>
<title>PROV-DM Part 1: The PROV Data Model</title>
@@ -26,10 +23,10 @@
<script class="remove">
function updateGlossaryRefs() {
$('.glossary-ref').each(function(index) {
- var ref=$(this).attr('ref');
+ var ref=$(this).attr('data-ref');
var span=$(this).attr('withspan')
$(this).removeAttr('withspan');
- $(this).removeAttr('ref');
+ $(this).removeAttr('data-ref');
$('#'+ref+'.glossary').contents().clone().appendTo($(this));
$(this).attr("prov:hadOriginalSource",glossary_hg);
@@ -415,7 +412,7 @@
physical things such as a building or a printed book, or a car as well as abstract concepts and ideas. One can regard any Web resource as an example of Entity in this context. </p>
<p>
-<div class="glossary-ref" ref="glossary-entity" withspan="true">
+<div class="glossary-ref" data-ref="glossary-entity" withspan="true">
</div>
@@ -427,7 +424,7 @@
<p>
-<span class="glossary-ref" ref="glossary-activity" withspan="true"></span> Activities that operate on digital entities may for example move, copy, or duplicate them.
+<span class="glossary-ref" data-ref="glossary-activity" withspan="true"></span> Activities that operate on digital entities may for example move, copy, or duplicate them.
</p>
@@ -445,12 +442,12 @@
The term 'generation' refers to the completion of the the act of producing; likewise, the term 'usage' refers to the beginning of the act of consuming entities. Thus, we define the following notions of generation and usage. </p>
<p>
-<div class="glossary-ref" ref="glossary-generation" withspan="true">
+<div class="glossary-ref" data-ref="glossary-generation" withspan="true">
</div>
<p>
-<div class="glossary-ref" ref="glossary-usage" withspan="true">
+<div class="glossary-ref" data-ref="glossary-usage" withspan="true">
</div>
@@ -474,7 +471,7 @@
<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" withspan="true"></span>
+<span class="glossary-ref" data-ref="glossary-derivation" withspan="true"></span>
@@ -491,7 +488,7 @@
<p>The motivation for introducing agents in the model is to denote the agent's responsibility for activities. </p>
<p>
-<span class="glossary-ref" ref="glossary-agent" withspan="true">
+<span class="glossary-ref" data-ref="glossary-agent" withspan="true">
</span>
</p>
@@ -515,7 +512,7 @@
<p>There are some useful types of entities and agents that are commonly encountered in applications making data and documents available on the Web; we introduce them in the rest of this section. </p>
<p>
-<span class="glossary-ref" ref="glossary-plan" withspan="true">
+<span class="glossary-ref" data-ref="glossary-plan" withspan="true">
</span>
There exist no
prescriptive requirement on the nature of plans, their representation, the
@@ -541,7 +538,7 @@
</div>
<p>
-<span class="glossary-ref" ref="glossary-collection" withspan="true"></span> This concept allows for the provenance of the collection, but also of its constituents to be expressed. Such a notion of collection corresponds to a wide variety of concrete data structures, such as a <em>maps</em>, <em>dictionaries</em>, or <em>associative arrays</em>.</p>
+<span class="glossary-ref" data-ref="glossary-collection" withspan="true"></span> This concept allows for the provenance of the collection, but also of its constituents to be expressed. Such a notion of collection corresponds to a wide variety of concrete data structures, such as a <em>maps</em>, <em>dictionaries</em>, or <em>associative arrays</em>.</p>
<div class="anexample" id="collection-example">
<p>
@@ -551,7 +548,7 @@
<!-- alternative names: provenance record, bundle -->
<p>
-<span class="glossary-ref" ref="glossary-account" withspan="true">
+<span class="glossary-ref" data-ref="glossary-account" withspan="true">
</span>Making an account an entity allows for provenance of provenance to be expressed.
<div class="anexample" id="account-example">
@@ -574,7 +571,7 @@
<p>Agents can be related to entities, activities, and other agents.</p>
-<div class="glossary-ref" ref="glossary-attribution" withspan="true"></div>
+<div class="glossary-ref" data-ref="glossary-attribution" withspan="true"></div>
<div class="anexample" id="association-example">
<p>A blog post can be attributed to an author, a mobile phone to its manufacturer.</p>
@@ -601,7 +598,7 @@
<p>
-<span class="glossary-ref" ref="glossary-activityAssociation" withspan="true"></span>
+<span class="glossary-ref" data-ref="glossary-activityAssociation" withspan="true"></span>
</p>
<div class="anexample" id="association-example2">
@@ -615,7 +612,7 @@
</div>
<p>
-<span class="glossary-ref" ref="glossary-responsibility" withspan="true">
+<span class="glossary-ref" data-ref="glossary-responsibility" withspan="true">
</span> The nature of this relation is intended to be broad, including delegation or contractual relation. </p>
<!--<div class="note">Propose to rephrase as follows: <br/>
@@ -1055,7 +1052,7 @@
<h4>Entity</h4>
-<div class="glossary-ref" ref="glossary-entity"></div>
+<div class="glossary-ref" data-ref="glossary-entity"></div>
<p><div class="attributes" id="attributes-entity">An <dfn title="dfn-Entity">entity</dfn><span class="withPn">, written <span class="pnExpression" id="pn-entity">entity(id, [attr1=val1, ...])</span> in PROV-N, </span> contains:
@@ -1096,7 +1093,7 @@
<h3>Activity</h3>
-<div class="glossary-ref" ref="glossary-activity"></div>
+<div class="glossary-ref" data-ref="glossary-activity"></div>
<p><div class="attributes" id="attributes-activity"> An <dfn title="dfn-Activity">activity</dfn><span class="withPn">, written <span class="pnExpression" id="pn-activity">activity(id, st, et, [attr1=val1, ...])</span> in PROV-N,</span> contains:
<ul>
@@ -1133,7 +1130,7 @@
<section id="term-Generation">
<h4>Generation</h4>
-<div class="glossary-ref" ref="glossary-generation"></div>
+<div class="glossary-ref" data-ref="glossary-generation"></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:
@@ -1182,7 +1179,7 @@
<section id="term-Usage">
<h3>Usage</h3>
-<div class="glossary-ref" ref="glossary-usage"></div>
+<div class="glossary-ref" data-ref="glossary-usage"></div>
<p><div class="attributes" id="attributes-usage"><dfn title="used">Usage</dfn><span class="withPn">, written <span class="pnExpression">used(id,a,e,t,attrs)</span> in PROV-N,</span> has the following constituents:
@@ -1223,7 +1220,7 @@
<section id="term-Start">
<h4>Start</h4>
-<div class="glossary-ref" ref="glossary-start"></div>
+<div class="glossary-ref" data-ref="glossary-start"></div>
<p>An activity <dfn title="wasStartedBy">start</dfn><span class="withPn">, written <span class="pnExpression">wasStartedBy(id,a,e,t,attrs)</span> in PROV-N,</span> contains:</p>
@@ -1270,7 +1267,7 @@
<section id="term-End">
<h4>End</h4>
-<div class="glossary-ref" ref="glossary-end"></div>
+<div class="glossary-ref" data-ref="glossary-end"></div>
<p>An activity <dfn title="wasEndedBy">end</dfn><span class="withAsn">, written <span class="pnExpression">wasEndedBy(id,a,e,t,attrs)</span> in PROV-N,</span> contains:</p>
@@ -1303,7 +1300,7 @@
<section id="term-wasInformedBy">
<h3>Communication</h3>
-<div class="glossary-ref" ref="glossary-communication"></div>
+<div class="glossary-ref" data-ref="glossary-communication"></div>
<p>A communication implies that activity <span class="name">a2</span> is dependent on another <span class="name">a1</span>, by way of some unspecified entity that is generated by <span class="name">a1</span> and used by <span class="name">a2</span>.</p>
@@ -1339,7 +1336,7 @@
<section id="term-wasStartedByActivity">
<h3>Start by Activity</h3>
-<div class="glossary-ref" ref="glossary-startByActivity"></div>
+<div class="glossary-ref" data-ref="glossary-startByActivity"></div>
@@ -1390,7 +1387,7 @@
<section id="term-Agent">
<h3>Agent</h3>
-<div class="glossary-ref" ref="glossary-agent"></div>
+<div class="glossary-ref" data-ref="glossary-agent"></div>
<p><div class="attributes" id="attributes-agent">An <dfn title="dfn-agent">agent</dfn><span class="withPn">, noted <span class="pnExpression" id="pn-agent">agent(id, [attr1=val1, ...])</span> in PROV-N,</span> contains:
@@ -1427,7 +1424,7 @@
<section id="term-attribution">
<h3>Attribution</h3>
-<div class="glossary-ref" ref="glossary-attribution"></div>
+<div class="glossary-ref" data-ref="glossary-attribution"></div>
<p>When an entity <span class="name">e</span> is attributed to agent <span class="name">ag</span>, entity <span class="name">e</span> was generated by some unspecified activity that in turn was associated to agent <span class="name">ag</span>. Thus, this relation is useful when the activity is not known, or irrelevant.</p>
@@ -1458,7 +1455,7 @@
<section id="term-ActivityAssociation">
<h4>Association</h4>
-<div class="glossary-ref" ref="glossary-activityAssociation"></div>
+<div class="glossary-ref" data-ref="glossary-activityAssociation"></div>
<p><div class="attributes" id="attributes-activity-association">An <dfn title="wasAssociatedWith">activity association</dfn><span class="withPn">, written <span class="pnExpression">wasAssociatedWith(id,a,ag,pl,attrs)</span> in PROV-N,</span> has the following
@@ -1506,7 +1503,7 @@
<h4>Responsibility</h4>
-<div class="glossary-ref" ref="glossary-responsibility"></div>
+<div class="glossary-ref" data-ref="glossary-responsibility"></div>
<p>PROV-DM offers a mild version of responsibility
in the form of a relation to represent when an agent acted on another
@@ -1586,7 +1583,7 @@
-<div class="glossary-ref" ref="glossary-derivation"></div>
+<div class="glossary-ref" data-ref="glossary-derivation"></div>
@@ -1644,7 +1641,7 @@
<section id="term-Revision">
<h3>Revision</h3>
-<p><span class="glossary-ref" ref="glossary-revision"></span></p>
+<p><span class="glossary-ref" data-ref="glossary-revision"></span></p>
<p> Deciding whether something is made available as a revision of something else usually involves an agent who takes responsibility for approving that the former is a due variant of the latter.
The agent who is responsible for the revision may optionally be specified.
@@ -1683,7 +1680,7 @@
<h3>Quotation</h3>
<p>
-<span class="glossary-ref" ref="glossary-quotation"></span>
+<span class="glossary-ref" data-ref="glossary-quotation"></span>
</p>
<p>Quotation
@@ -1724,7 +1721,7 @@
<h3>Original Source</h3>
<p>
-<span class="glossary-ref" ref="glossary-original-source"></span>
+<span class="glossary-ref" data-ref="glossary-original-source"></span>
</p>
<p>An <dfn>original source</dfn> relation is a particular case of <a>derivation</a>
@@ -1761,7 +1758,7 @@
<h3>Traceability</h3>
<p>
-<span class="glossary-ref" ref="glossary-traceability"></span>
+<span class="glossary-ref" data-ref="glossary-traceability"></span>
</p>
@@ -1837,7 +1834,7 @@
<h4>Specialization</h4>
-<span class="glossary-ref" ref="glossary-specialization"></span>
+<span class="glossary-ref" data-ref="glossary-specialization"></span>
Examples of constraints include a time period, an abstraction, and a context associated with the entity.
@@ -1879,7 +1876,7 @@
<h4>Alternate</h4>
-<span class="glossary-ref" ref="glossary-alternate"></span>
+<span class="glossary-ref" data-ref="glossary-alternate"></span>
@@ -1964,7 +1961,7 @@
<section id="term-collection-insertion">
<h3>Insertion</h3>
-<span class="glossary-ref" ref="glossary-insertion"></span>
+<span class="glossary-ref" data-ref="glossary-insertion"></span>
<p>
@@ -2006,7 +2003,7 @@
<section id="term-collection-removal">
<h3>Removal</h3>
-<span class="glossary-ref" ref="glossary-removal"></span>
+<span class="glossary-ref" data-ref="glossary-removal"></span>
<p><strong>Derivation-by-Removal</strong> relation <span class="name">derivedByRemovalFrom(c2,c1, {key_1, ... key_n})</span> states that <span class="name">c2</span> is the state of the collection following the removal of the set of pairs corresponding to keys <span class="name">key_1...key_n</span> from <span class="name">c1</span>.
@@ -2051,7 +2048,7 @@
<h3>Membership</h3>
-<span class="glossary-ref" ref="glossary-membership"></span>
+<span class="glossary-ref" data-ref="glossary-membership"></span>
<p>
The insertion and removal relations make insertions and removals explicit as part of the history of a collection. This, however, requires explicit mention of the state of the collection prior to each insertion. The membership relation removes this needs, allowing the state of a collection <span class="name">c</span> to be asserted without having to introduce a prior state. This allows for the natural expression of a collection state, for instance in cases where a program or workflow block produces a new collection <span class="name">c</span> with known content. In such cases,
@@ -2181,7 +2178,7 @@
-<span class="glossary-ref" ref="glossary-annotation"></span>
+<span class="glossary-ref" data-ref="glossary-annotation"></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