--- a/model/working-copy/towards-wd4.html Fri Feb 10 09:04:52 2012 +0000
+++ b/model/working-copy/towards-wd4.html Fri Feb 10 10:17:44 2012 +0000
@@ -156,7 +156,7 @@
-<section id='changes'>
+<div class='note' id='changes'>
<p> Following F2F2 guidance, in this document we try to:
<ul>
<li> pitch from the start the idea of an upgrade path, from 'scruffy provenance' (term TBD), to 'precise provenance' (term TBD)
@@ -166,8 +166,16 @@
<li>present the upgrade path
<li>contemplating the organization of the deliverable in two/three separate documents.
</ul>
-</section>
-
+</div>
+
+
+
+<div class='note' id='editorial-notes'>
+<ul>
+<li> Term 'record' dropped: we no longer refer to 'entity record', 'activity record', etc but simply to 'entity', 'activity', etc
+<li> Aiming to drop the word 'assertion'. This is work in progress.
+</ul>
+</div>
<section id="introduction">
@@ -222,7 +230,7 @@
<p>This specification intentionally presents the key concepts of the PROV Data Model, without drilling down into all its subtleties. Using these key concepts, it becomes possible to write useful provenance assertions very quickly, and publish or embed them along side the data they relate to. </p>
-<p>However, it becomes challenging for provenance, like for any other form of metadata, when the data it is about changes. To address this challenge, an <em>upgrade path</em> is proposed to enrich simple provenance assertions, with extra-assertions that help qualify the subject of provenance and provenance itself, with attributes and interval, intended to satisfy a comprehensive set of constraints. These aspects are covered in the companion specification (PROV-DM part II, Ref to ADD).
+<p>However, it becomes challenging for provenance, like for any other form of metadata, when the data it is about changes. To address this challenge, an <em>upgrade path</em> is proposed to enrich simple provenance, with extra-descriptions that help qualify the subject of provenance and provenance itself, with attributes and interval, intended to satisfy a comprehensive set of constraints. These aspects are covered in the companion specification (PROV-DM part II, Ref to ADD).
</p>
@@ -288,7 +296,7 @@
-<p><dfn id="concept-entity">Entities</dfn> are things in the world one
+<p><dfn title="concept-entity">Entities</dfn> are things in the world one
wants to provide provenance for. For the purpose of this
specification, things can be physical, digital, conceptual, or
otherwise; the world may be real or imaginary.
@@ -301,7 +309,7 @@
</div>
-->
-<p>An <dfn id="concept-activity">Activity</dfn> is anything that can operate on entities. In particular, activities may produce, consume, or transform an entity. Activities that operate on digital entities may for example move, copy, or duplicate them.
+<p>An <dfn title="concept-activity">Activity</dfn> is anything that can operate on entities. In particular, activities may produce, consume, or transform an entity. Activities that operate on digital entities may for example move, copy, or duplicate them.
@@ -309,7 +317,7 @@
An activity may be the publishing of a document on the web, sending a tweet, extracting metadata embedded in a file, or driving a car from Boston to Cambridge, assembling a data set based on a set of measurements, performing a statistical analysis over a data set, sorting news items according to some criteria, running a sparql query over a triple store, and editing a file.
</div>
-<p>An <dfn id="concept-agent">agent</dfn> is a type of entity that can be associated to an activity, to indicate that it bears some form of responsibility for the activity taking
+<p>An <dfn title="concept-agent">agent</dfn> is a type of entity that can be associated to an activity, to indicate that it bears some form of responsibility for the activity taking
place.
<p>The key purpose of agents is to assign responsibility
@@ -335,10 +343,10 @@
<p>Activities and entities are associated with each other in two different ways: activities are consumers of entities and activities are producers of entities. For provenance purpose, we define the following notions of generation and usage. </p>
-<p><dfn id="concept-generation">Generation</dfn> is the completed production of a new entity by activity.
+<p><dfn title="concept-generation">Generation</dfn> is the completed production of a new entity by activity.
This entity become available for usage after this generation. This entity did not exist before generation. </p>
-<p><dfn id="concept-usage">Usage</dfn> is the beginning on an entity being consumed by an activity.
+<p><dfn title="concept-usage">Usage</dfn> is the beginning on an entity being consumed by an activity.
Before usage, the activity had not begun to consume or use to this entity (and could not have been affected by the entity).</p>
@@ -358,7 +366,7 @@
<p>Activities are consumers of entities and producers of entities. In some case, the consumption of entity influences the creation of another in some way. This notion is captured by derivations, defined as follows.</p>
-<p><dfn id="concept-derivation">Derivation</dfn> is the fact that some entity is transformed from, created from, or affected by another entity in the world. </p>
+<p><dfn title="concept-derivation">Derivation</dfn> is the fact that some entity is transformed from, created from, or affected by another entity in the world. </p>
<!-- doesn't seem right to say fact, should I use influence? -->
<div class="anexample" id="derivation-example">
@@ -373,7 +381,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 this section. </p>
-<p>A <dfn id="concept-plan">Plan</dfn> is an entity that represent a set of
+<p>A <dfn title="concept-plan">Plan</dfn> is an entity that represent a set of
actions or steps intended by one or more agents to achieve some goals. PROV-DM is not
prescriptive about the nature of plans, their representation, the
actions and steps they consist of, and their intended goals. Since plans may evolve over time,
@@ -386,7 +394,7 @@
</p>
</div>
-<p>A <dfn id="concept-collection">Collection</dfn> is an entity that has a logical internal structure consisting of key-value pairs, in which values are themselves entities. 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>
+<p>A <dfn title="concept-collection">Collection</dfn> is an entity that has a logical internal structure consisting of key-value pairs, in which values are themselves entities. 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>
@@ -395,7 +403,7 @@
<!-- alternative names: provenance record, bundle -->
-<p>An <dfn id="concept-accountEntity">AccountEntity</dfn> is an entity that contains a bundle of provenance assertions. </p>
+<p>An <dfn title="concept-accountEntity">AccountEntity</dfn> is an entity that contains a bundle of provenance assertions. </p>
<div class="anexample" id="account-example">
<p>
@@ -450,14 +458,14 @@
-<p>An <dfn id="concept-activityAssociation">activity association</dfn> is a relation between an activity and an agent, indicating that the agent had an active role in the activity. It further allow an activity to be associated with a plan, which a set of
+<p>An <dfn title="concept-activityAssociation">activity association</dfn> is a relation between an activity and an agent, indicating that the agent had an active role in the activity. It further allow an activity to be associated with a plan, which a set of
actions or steps intended by the agent to achieve some goals in the context of this activity.</p>
<div class="anexample" id="association-example">
<p>Examples of association between an activity and agent include designing, participation, initiation and termination, timetabling or sponsoring. </p>
</div>
-<p>An <dfn id="concept-responsibilityChain">responsibility chain</dfn> is a relation between two agents,
+<p>An <dfn title="concept-responsibilityChain">responsibility chain</dfn> is a relation between two agents,
indicating that a "subordinate" agent acted on behalf of a "responsible" agent, in the context of an activity.</p>
@@ -532,7 +540,7 @@
We now paraphrase some PROV-DM asssertions, and illustrate them with the PROV-ASN notation, a notation for PROV-DM aimed at human consumption. Full details of the provenance record can be found <a href="examples/w3c-publication1.prov-asn">here</a>.
<ul>
-<li>There is a technical report, a working draft on the recommendation track (<a href="http://www.w3.org/2005/10/Process-20051014/tr.html#RecsWD">pr:RecsWD</a>), which is regarded as an entity so that we can describe its provenance. Similar assertions exist for all entities.
+<li>There is a technical report, a working draft on the recommendation track (<a href="http://www.w3.org/2005/10/Process-20051014/tr.html#RecsWD">pr:RecsWD</a>), which is regarded as an entity so that we can describe its provenance. Similar descriptions exist for all entities.
<pre>
entity(tr:WD-prov-dm-20111215, [ prov:type="pr:RecsWD" %% xsd:QName ])
</pre>
@@ -543,13 +551,13 @@
</pre>
</li>
-<li>The technical report was generated by the publication activity: this is a Generation assertion.
+<li>The technical report was generated by the publication activity: this is a <a title="concept-Generation">Generation</a>.
<pre>
wasGeneratedBy(tr:WD-prov-dm-20111215, ex:pub2)
</pre>
</li>
-<li>The activity required a publication request: this is a Usage assertion.
+<li>The activity required a publication request: this is a <a title="concept-Usage">Usage</a>.
<pre>
used(ex:pub2,ar3:0111)
</pre>
@@ -563,7 +571,7 @@
</ul>
<p>
-Provenance assertions can be <em>illustrated</em> graphically. The illustration is not intended to represent all the details of the model, but it is intended to show the essence of a set of
+Provenance descriptions can be <em>illustrated</em> graphically. The illustration is not intended to represent all the details of the model, but it is intended to show the essence of a set of
provenance statements. Therefore, it should not be seen as an alternate notation for expressing provenance.</p>
<p>The graphical illustration takes the form of a graph. Entities, activities and agents are represented as nodes, with oval, rectangular, and octogonal shapes, respectively. Usage,
@@ -612,7 +620,7 @@
<pre>
entity(tr:WD-prov-dm-20111215, [ prov:type="document", ex:version="2" ])
</pre>
-<p>While this assertion is about the same report <span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111215">tr:WD-prov-dm-20111215</a></span>, its characterization is different from the author's perspective, it is a document and has it has a version number. </p></li>
+<p>While this description is about the same report <span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111215">tr:WD-prov-dm-20111215</a></span>, its details differ from the author's perspective: it is a document and it has a version number. </p></li>
<li>There is a editing activity.
<pre>
@@ -620,7 +628,7 @@
</pre>
</li>
-<li>The technical report was generated by the editing activity: this is a Generation assertion.
+<li>The technical report was generated by the editing activity: this is a <a title="concept-generation">Generation</a>.
<pre>
wasGeneratedBy(tr:WD-prov-dm-20111215, ex:edit1)
</pre>
@@ -634,7 +642,7 @@
</pre>
</li>
-<li>The activity required a publication request: this is a Usage assertion.
+<li>The activity required a publication request: this is a <a title="concept-usage">Usage</a>.
<pre>
wasAssociatedWith(ex:edit1, ex:Paolo, [prov:role="editor"])
wasAssociatedWith(ex:edit1, ex:Simon, [prov:role="contributor"])
@@ -815,11 +823,11 @@
<h4>Note</h4>
-<p>As provenance assertions are exchanged between systems, it may be useful to add extra-information about such assertions. For instance, a "trust service" may add value-judgements about the
-trustworthiness of some of the assertions made. Likewise, an interactive visualization component may want to enrich a set of provenance assertions with information helping reproduce their
+<p>As provenance descriptions are exchanged between systems, it may be useful to add extra-information about such descriptions. For instance, a "trust service" may add value-judgements about the
+trustworthiness of some of the descriptions. Likewise, an interactive visualization component may want to enrich a set of provenance descriptions with information helping reproduce their
visual representation. To help with inter-operability, PROV-DM introduces a simple annotation mechanism allowing anythig that is identifiable to be associated with notes.</p>
-<p>A <dfn id="dfn-note">note</dfn><span class="withAsn">, noted <span class="name">note(id, [ attr1=val1, ...])</span> in PROV-ASN,</span> contains:</p>
+<p>A <dfn title="dfn-note">note</dfn><span class="withAsn">, noted <span class="name">note(id, [ attr1=val1, ...])</span> in PROV-ASN,</span> contains:</p>
<ul>
<li><em>id</em>: an identifier identifying the note;</li>
<li><em>attributes</em>: a set of attribute-value pairs, whose meaning is application specific.</li>
@@ -828,7 +836,6 @@
-
<p>A separate PROV-DM construct is used to associate a note with something that is identifiable (see <a href="#term-annotation">Section on annotation</a>). A given note may be associated with
multiple asssertions.
</p>
@@ -837,13 +844,13 @@
<div class="anexample">
<p>
The following note consists of a set of application-specific attribute-value pairs, intended
-to help the rendering of the assertion it is associated with, by
+to help the rendering of what it is associated with, by
specifying its color and its position on the screen.</p>
<pre class="codeexample">
-note(n1,[ex:color="blue", ex:screenX=20, ex:screenY=30])
-hasAnnotation(g1,n1)
+note(ex:n1,[ex:color="blue", ex:screenX=20, ex:screenY=30])
+hasAnnotation(tr:WD-prov-dm-20111215,ex:n1)
</pre>
-<p>The note is associated with an assertion <span class="name">g1</span> previously introduced (<a title="annotation">hasAnnotation</a> is
+<p>The note is associated with the entity <span class="name">tr:WD-prov-dm-20111215</span> previously introduced (<a title="annotation">hasAnnotation</a> is
discussed in Section <a href="#term-annotation">Annotation</a>). In this example,
the attribute-value pairs do not constitute a representation of something
in the world; they are just used to help render provenance.
@@ -884,7 +891,7 @@
<h4>Generation</h4>
-<p><dfn id="dfn-Generation">Generation</dfn><span class="withAsn">, written <span class="name">wasGeneratedBy(id,e,a,t,attrs)</span> in PROV-ASN,</span> has the following components:</p>
+<p><dfn title="dfn-Generation">Generation</dfn><span class="withAsn">, written <span class="name">wasGeneratedBy(id,e,a,t,attrs)</span> in PROV-ASN,</span> has the following components:</p>
<ul>
<li><em>id</em>: an OPTIONAL identifier identifying the generation;</li>
<li><em>entity</em>: an identifier identifying a created entity; </li>
@@ -944,7 +951,7 @@
-<p><dfn id="dfn-Usage">Usage</dfn><span class="withAsn">, written <span class="name">used(id,a,e,t,attrs)</span> in PROV-ASN,</span> has the following constituents:</p>
+<p><dfn title="dfn-Usage">Usage</dfn><span class="withAsn">, written <span class="name">used(id,a,e,t,attrs)</span> in PROV-ASN,</span> has the following constituents:</p>
<ul>
<li><em>id</em>: an OPTIONAL identifier identifying the usage;</li>
<li><em>activity</em>: an identifier for the consuming activity;</li>
@@ -1003,7 +1010,7 @@
href="#term-responsibility">Section Responsibility</a>, represents the fact that an agent was acting on behalf of another, in the context of an activity. </p>
-<p>An <dfn id="dfn-activity-association">activity association</dfn><span class="withAsn">, written <span class="name">wasAssociatedWith(id,a,ag2,pl,attrs)</span> in PROV-ASN,</span> has the following
+<p>An <dfn title="dfn-activity-association">activity association</dfn><span class="withAsn">, written <span class="name">wasAssociatedWith(id,a,ag2,pl,attrs)</span> in PROV-ASN,</span> has the following
constituents:</p>
<ul>
<li><em>id</em>: an OPTIONAL identifier for the association between an activity and an agent;</li>
@@ -1014,7 +1021,7 @@
</ul>
<div class="anexample">
-In the following example, a designer and an operator agents are asserted to be associated with an activity. The designer's goals are achieved by a workflow <span class="name">ex:wf</span>.
+In the following example, a designer and an operator agents are associated with an activity. The designer's goals are achieved by a workflow <span class="name">ex:wf</span>.
<pre class="codeexample">
activity(ex:a,[prov:type="workflow execution"])
agent(ex:ag1,[prov:type="operator"])
@@ -1041,8 +1048,8 @@
<section id="term-Start-End">
<h4>Activity Start and Activity End</h4>
-<p> A <dfn id="dfn-Start">activity start</dfn> is a representation of an agent starting an activity.
- An <dfn id="dfn-End">activity end</dfn> is a representation of an agent ending an activity. Both relations are specialized forms of <span class="name">wasAssociatedWith</span>. They contain
+<p> A <dfn title="dfn-Start">activity start</dfn> is a representation of an agent starting an activity.
+ An <dfn title="dfn-End">activity end</dfn> is a representation of an agent ending an activity. Both relations are specialized forms of <span class="name">wasAssociatedWith</span>. They contain
attributes describing the modalities of acting/ending activities.</p>
@@ -1066,13 +1073,13 @@
<div class="anexample">
<p>
-The following assertions</p>
+In the following example,</p>
<pre class="codeexample">
wasStartedBy(a,ag,[ex:mode="manual"])
wasEndedby(a,ag,[ex:mode="manual"])
</pre>
-<p>state that the activity denoted by <span class="name">a</span>
-was started and ended by an agent denoted by <span class="name">ag</span>, in "manual" mode, an application specific characterization of these relations.
+<p>there is an activity denoted by <span class="name">a</span>
+that was started and ended by an agent denoted by <span class="name">ag</span>, in "manual" mode, an application specific characterization of these relations.
</p>
</div>
@@ -1120,7 +1127,7 @@
agents exert over a given activity.</p>
<p>Given an activity association<span class="withAsn">, written <span class="name">wasAssociatedWith(a,ag2,attrs)</span></span>,
-a <dfn id="dfn-responsibility">responsibility chain</dfn><span class="withAsn">, written <span class="name">actedOnBehalfOf(id,ag2,ag1,a,attrs)</span> in PROV-ASN,</span> has the following constituents:</p>
+a <dfn title="dfn-responsibility">responsibility chain</dfn><span class="withAsn">, written <span class="name">actedOnBehalfOf(id,ag2,ag1,a,attrs)</span> in PROV-ASN,</span> has the following constituents:</p>
<ul>
<li><em>id</em>: an OPTIONAL identifier <span class="name">id</span> identifying the responsibility chain;</li>
<li><em>subordinate</em>: an identifier for the agent associated with an activity, acting on behalf of the responsible
@@ -1132,7 +1139,7 @@
<div class="anexample">
-In the following example, a programmer, a researcher and a funder agents are asserted. The programmer and researcher are associated with a workflow activity. The programmer acts on behalf
+In the following example, a programmer, a researcher and a funder agents are described. The programmer and researcher are associated with a workflow activity. The programmer acts on behalf
of the researcher (delegation) encoding the commands specified by the researcher; the researcher acts on behalf of the funder, who has an contractual agreement with the researcher. The terms
'delegation' and 'contact' used in this example are domain specific.
<pre class="codeexample">
@@ -1153,6 +1160,10 @@
<section id="Derivation-Relation">
<h4>Derivation</h4>
+<div class='note'>
+Using asserter/assertion.
+</div>
+
<p>According to <a href="#conceptualization">Section Conceptualization</a>, for an entity to be transformed from, created from, or affected by another in some way, there must be some
underpinning activities performing the necessary actions resulting in such a derivation.
@@ -1209,7 +1220,7 @@
When <span class="name">prov:steps="single"</span>, derivation is due to one activity; when <span class="name">prov:steps="any"</span>, the number of activities is multiple or not known.</p>
-<p>The three kinds of <dfn id="dfn-derivation">derivations</dfn> are successively introduced. Making use of the attribute <span class="name">steps</span>, we can distinguish the various derivation types.</p>
+<p>The three kinds of <dfn title="dfn-derivation">derivations</dfn> are successively introduced. Making use of the attribute <span class="name">steps</span>, we can distinguish the various derivation types.</p>
<p>A <dfn>precise-1 derivation</dfn><span class="withAsn">, written <span class="name">wasDerivedFrom(id, e2, e1, a, g2, u1, attrs)</span> in PROV-ASN,</span> contains:</p>
<ul>
@@ -1253,7 +1264,7 @@
<div class="anexample">
-<p>The following assertions state the existence of derivations.</p>
+<p>The following descriptions state the existence of derivations.</p>
<pre class="codeexample">
wasDerivedFrom(e5,e3,a4,g2,u2)
wasDerivedFrom(e5,e3,a4,g2,u2,[prov:steps="single"])
@@ -1273,7 +1284,7 @@
<span class="name">g2</span>. </p>
<p>
-The third assertion is an imprecise-1 derivation, which is similar for <span class="name">e3</span> and <span class="name">e2</span>, but it leaves the activity and associated attributes implicit. The fourth and fifth assertions are imprecise-n derivations between <span class="name">e2</span> and <span class="name">e1</span>, but no information is provided as to the number and identity of activities underpinning the derivation. The sixth derivation extends the fifth with the derivation time of <span class="name">e2</span>.
+The third line describes an imprecise-1 derivation, which is similar for <span class="name">e3</span> and <span class="name">e2</span>, but it leaves the activity and associated attributes implicit. The fourth and fifth lines are about imprecise-n derivations between <span class="name">e2</span> and <span class="name">e1</span>, but no information is provided as to the number and identity of activities underpinning the derivation. The sixth derivation extends the fifth with the derivation time of <span class="name">e2</span>.
</p>
</div>
@@ -1324,7 +1335,7 @@
-<p>An <dfn id="dfn-Alternate">alternate relation</dfn><span class="withAsn">, written <span class="name">alternateOf(id, alt1, alt2, attrs)</span> in PROV-ASN,</span> addresses case (1). It has the following constituents:</p>
+<p>An <dfn title="dfn-Alternate">alternate relation</dfn><span class="withAsn">, written <span class="name">alternateOf(id, alt1, alt2, attrs)</span> in PROV-ASN,</span> addresses case (1). It has the following constituents:</p>
<ul>
<li><em>id</em>: an OPTIONAL identifier for the association between the two alternates;</li>
@@ -1334,7 +1345,7 @@
</ul>
-<p>A <dfn id="dfn-Specialization">specialization relation</dfn><span class="withAsn">, written <span class="name">specializationOf([id], sub, super, [attrs])</span> in PROV-ASN,</span> addresses case (2). It has the following constituents:</p>
+<p>A <dfn title="dfn-Specialization">specialization relation</dfn><span class="withAsn">, written <span class="name">specializationOf([id], sub, super, [attrs])</span> in PROV-ASN,</span> addresses case (2). It has the following constituents:</p>
<ul>
<li><em>id</em>: an OPTIONAL identifier for the association between the two entities;</li>
@@ -1361,12 +1372,12 @@
<h4>Annotation</h4>
-<p>An <dfn id="concept-annotation">annotation</dfn> establishes a link between something that is identifiable and a note referred to by its identifier. Multiple notes can
+<p>An <dfn title="concept-annotation">annotation</dfn> establishes a link between something that is identifiable and a note referred to by its identifier. 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>
-<p>An <dfn id="dfn-annotation">annotation</dfn><span class="withAsn">, written <span class="name">hasAnnotation(r,n,attrs)</span> in PROV-ASN,</span> has the following constituents:</p>
+<p>An <dfn title="dfn-annotation">annotation</dfn><span class="withAsn">, written <span class="name">hasAnnotation(r,n,attrs)</span> in PROV-ASN,</span> has the following constituents:</p>
<ul>
<li><em>something</em>: the identifier of someting being annnotated;</li>
<li><em>note</em>: an identifier of a note;</li>
@@ -1393,9 +1404,9 @@
note(n2,[ex:style="dotted"])
hasAnnotation(u1,n2)
</pre>
-<p>assert the existence of two documents (attribute-value pair: <span class="name">prov:type="document"</span>) identified by <span class="name">e1</span> and <span
-class="name">e2</span>, and annotate them with a note indicating that the icon (an application specific way of rendering provenance) is <span class="name">doc.png</span>. It also
-asserts an activity, its usage of the first entity, and its generation of the second entity. The <span class="name">usage</span> is annotated with a style (an application specific way
+<p>describe two documents (attribute-value pair: <span class="name">prov:type="document"</span>) identified by <span class="name">e1</span> and <span
+class="name">e2</span>, and their annotation with a note indicating that the icon (an application specific way of rendering provenance) is <span class="name">doc.png</span>. The example also
+includes an activity, its usage of the first entity, and its generation of the second entity. The <a title="dfn-usage">usage</a> is annotated with a style (an application specific way
of rendering this edge graphically). To be able to express this annotation, the usage was provided with an identifier <span class="name">u1</span>, which was then referred to in <span
class="name">hasAnnotation(u1,n2)</span>.
</p>
@@ -1415,13 +1426,13 @@
<section id="term-NamespaceDeclaration">
<h3>Namespace Declaration</h3>
-<p>A PROV-DM <dfn id="dfn-namespace">namespace</dfn> is identified by an IRI reference [[!IRI]]. In PROV-DM, attributes, identifiers, and literals of with datatype <span
+<p>A PROV-DM <dfn title="dfn-namespace">namespace</dfn> is identified by an IRI reference [[!IRI]]. In PROV-DM, attributes, identifiers, and literals of with datatype <span
class="name">xsd:QName</span> can be placed in a namespace using the mechanisms described in this specification. </p>
-<p>A <dfn id="dfn-namespaceDeclaration">namespace declaration</dfn> consists of a binding between a prefix and a namespace. Every qualified name with this prefix in the scope of this
+<p>A <dfn title="dfn-namespaceDeclaration">namespace declaration</dfn> consists of a binding between a prefix and a namespace. Every qualified name with this prefix in the scope of this
declaration refers to this namespace.
-A <dfn id="dfn-defaultNamespaceDeclaration">default namespace declaration</dfn> consists of a namespace. Every unprefixed qualified name in the scope of this default namespace declaration
+A <dfn title="dfn-defaultNamespaceDeclaration">default namespace declaration</dfn> consists of a namespace. Every unprefixed qualified name in the scope of this default namespace declaration
refers to this namespace.</p>
</section>
@@ -1429,12 +1440,12 @@
<h4>Identifier</h4>
<p>
-An <dfn id="dfn-identifier">identifier</dfn> is a <a>qualified
+An <dfn title="dfn-identifier">identifier</dfn> is a <a>qualified
name</a>.
</p>
<p>
-A <dfn id="dfn-qualifiedname">qualified name</dfn> is a name subject to <a>namespace</a> interpretation. It consists of <a>namespace</a>, denoted by an optional prefix, and a local name.</p>
+A <dfn title="dfn-qualifiedname">qualified name</dfn> is a name subject to <a>namespace</a> interpretation. It consists of <a>namespace</a>, denoted by an optional prefix, and a local name.</p>
<p>PROV-DM stipulates that a qualified name can be mapped into an IRI
@@ -1450,7 +1461,7 @@
<section id="term-attribute">
<h4>Attribute</h4>
-<p>An <dfn id="dfn-attribute">attribute</dfn> is a <a>qualified name</a>.
+<p>An <dfn title="dfn-attribute">attribute</dfn> is a <a>qualified name</a>.
<p>The PROV data model introduces a fixed set of attributes in the <a href="#prov-dm-namespace">PROV-DM namespace</a>, which we define below.
@@ -1459,8 +1470,8 @@
<section id="term-attribute-role">
<h4>prov:role</h4>
-<p>The attribute <dfn id="dfn-role"><span class="name">prov:role</span></dfn> denotes the function of an entity with respect to an activity, in the context of a usage, generation,
-activity association, activity start, and activity end. The attribute <span class="name">prov:role</span> is allowed to occur multiple times in such assertions. The value associated with a <span
+<p>The attribute <dfn title="dfn-role"><span class="name">prov:role</span></dfn> denotes the function of an entity with respect to an activity, in the context of a usage, generation,
+activity association, activity start, and activity end. The attribute <span class="name">prov:role</span> is allowed to occur multiple times in a list of attribute-value pairs. The value associated with a <span
class="name">prov:role</span> attribute MUST be conformant with <span class="nonterminal">Literal</span>.</p>
<div class="anexample">
@@ -1474,13 +1485,13 @@
<section id="term-attribute-type">
<h4>prov:type</h4>
-<p>The attribute <dfn id="dfn-type"><span class="name">prov:type</span></dfn> provides further typing information for an element or relation. PROV-DM liberally
+<p>The attribute <dfn title="dfn-type"><span class="name">prov:type</span></dfn> provides further typing information for an element or relation. PROV-DM liberally
defines a type as a category of things having common characteristics. PROV-DM is agnostic about the representation of types, and only states that
the value associated with a <span class="name">prov:type</span> attribute MUST be conformant with <span class="nonterminal">Literal</span>. The attribute <span class="name">prov:type</span>
is allowed to occur multiple times.</p>
<div class="anexample">
-<p>The following assertion declares an agent of type software agent</p>
+<p>The following describes an agent of type software agent.</p>
<pre class="codeexample">
agent(ag, [prov:type="prov:SoftwareAgent" %% xsd:QName])
</pre>
@@ -1490,7 +1501,7 @@
<section id="term-attribute-steps">
<h4>prov:steps</h4>
-<p> The attribute <dfn id="dfn-steps"><span class="name">prov:steps</span></dfn> defines the level of precision associated with a derivation. The value associated with a <span
+<p> The attribute <dfn title="dfn-steps"><span class="name">prov:steps</span></dfn> defines the level of precision associated with a derivation. The value associated with a <span
class="name">prov:steps</span> attribute MUST be <span class="name">"single"</span> or <span class="name">"any"</span>. The attribute <span class="name">prov:step</span> occurs at most
once in a derivation. A derivation without attribute <span class="name">prov:step</span> is considered to be equivalent to the same derivation extended with an extra attribute
<span class="name">prov:step</span> and associated value <span class="name">"any"</span>. </p>
@@ -1507,7 +1518,7 @@
<section id="term-attribute-label">
<h4>prov:label</h4>
-<p> The attribute <dfn id="dfn-label"><span class="name">prov:label</span></dfn> provides a human-readable representation of a PROV-DM element or relation.</p>
+<p> The attribute <dfn title="dfn-label"><span class="name">prov:label</span></dfn> provides a human-readable representation of a PROV-DM element or relation.</p>
<div class='issue'>
This is <a href="http://www.w3.org/2011/prov/track/issues/219">ISSUE-219</a>. </div>
@@ -1518,12 +1529,12 @@
<section id="term-attribute-location">
<h4>prov:location</h4>
-<p><dfn id="dfn-Location">Location</dfn> is an identifiable geographic place (ISO 19112). As such, there are numerous ways in which location can be expressed, such as by a coordinate,
-address, landmark, row, column, and so forth. This document does not specify how to concretely express locations, but instead provide a mechanism to introduce locations in assertions. </p>
+<p><dfn title="dfn-Location">Location</dfn> is an identifiable geographic place (ISO 19112). As such, there are numerous ways in which location can be expressed, such as by a coordinate,
+address, landmark, row, column, and so forth. This document does not specify how to concretely express locations, but instead provide a mechanism to introduce locations, by means of attributes. </p>
<p>
-The attribute <dfn id="dfn-location"><span class="name">prov:location</span></dfn> is an OPTIONAL attribute of entity and activity. The value associated with the attribute <span class="name">prov:location</span> MUST be a <span
+The attribute <dfn title="dfn-location"><span class="name">prov:location</span></dfn> is an OPTIONAL attribute of entity and activity. The value associated with the attribute <span class="name">prov:location</span> MUST be a <span
class="nonterminal">Literal</span>, expected to denote a location.
</p>
@@ -1574,11 +1585,11 @@
<section id="term-Time">
<h4>Time</h4>
-<p><dfn id="dfn-time">Time instants</dfn> are defined according to xsd:dateTime [[!XMLSCHEMA-2]].</p>
-
-
-
-<p>It is OPTIONAL to assert time in usage, generation, and activity</p>
+<p><dfn title="dfn-time">Time instants</dfn> are defined according to xsd:dateTime [[!XMLSCHEMA-2]].</p>
+
+
+
+<p>Time is OPTIONAL in usage, generation, and activity</p>
@@ -1610,12 +1621,12 @@
<section id="term-traceability">
<h3>Traceability</h3>
-<p> A <dfn id="dfn-Traceability">traceability relation</dfn> between two entities <span class="name">e2</span> and <span class="name">e1</span> states a generic dependency of <span class="name">e2</span>
+<p> A <dfn title="dfn-Traceability">traceability relation</dfn> between two entities <span class="name">e2</span> and <span class="name">e1</span> states a generic dependency of <span class="name">e2</span>
on <span class="name">e1</span>. Such dependency may indicate either that <span class="name">e1</span> was necessary for <span class="name">e2</span> to be created, or that <span class="name">e1</span> bears
some responsibility for <span class="name">e2</span>'s existence.
-<p> A traceability assertion<span class="withAsn">, written <span class="name">tracedTo(id,e2,e1,attrs)</span> in PROV-ASN,</span> contains:</p>
+<p> A traceability relation<span class="withAsn">, written <span class="name">tracedTo(id,e2,e1,attrs)</span> in PROV-ASN,</span> contains:</p>
<ul>
<li><em>id</em>: an OPTIONAL identifier identifying the relation;</li>
<li><em>entity</em>: an identifier identifying an entity;
@@ -1633,8 +1644,7 @@
</ul>
<div class="anexample">
-<div class="note"> need an example </div>
-
+<div class="note"> need an example. Text uses 'assertion'. Should we drop the above further considerations. </div>
</div>
</section>
@@ -1646,8 +1656,8 @@
<p>The following relations express dependencies amongst activities.</p>
<ul>
- <li> An <dfn id="InformationFlowOrdering">information flow ordering relation</dfn> states that activity <span class="name">a2</span> is dependent on another <span class="name">a1</span>, by way of some entity <span class="name">e</span> that is generated by <span class="name">a1</span> and used by <span class="name">a2</span>.
- <li>A <dfn id="ControlOrdering">control ordering relation</dfn> states that activity <span class="name">a2</span> was initiated by another activity <span class="name">a1</span>.
+ <li> An <dfn title="InformationFlowOrdering">information flow ordering relation</dfn> states that activity <span class="name">a2</span> is dependent on another <span class="name">a1</span>, by way of some entity <span class="name">e</span> that is generated by <span class="name">a1</span> and used by <span class="name">a2</span>.
+ <li>A <dfn title="ControlOrdering">control ordering relation</dfn> states that activity <span class="name">a2</span> was initiated by another activity <span class="name">a1</span>.
</ul>
<p>
@@ -1668,7 +1678,7 @@
activity(s2,,,[prov:type="service"])
wasInformedBy(s2,s1)
</pre>
-The last assertions indicates that some entity was generated by <span class="name">s1</span> and used by <span class="name">s2</span>.
+The last line indicates that some entity was generated by <span class="name">s1</span> and used by <span class="name">s2</span>.
</div>
@@ -1702,7 +1712,7 @@
<section id="term-Revision">
<h3>Revision</h3>
-<p> A <dfn id="dfn-Revision">revision relation</dfn> is a particular case of <a href="#Derivation-Relation">derivation</a> that states that an entity is a revised version of another. The agent who is responsible for making the revision may optionally be specified.</p>
+<p> A <dfn title="dfn-Revision">revision relation</dfn> is a particular case of <a href="#Derivation-Relation">derivation</a> that states that an entity is a revised version of another. The agent who is responsible for making the revision may optionally be specified.</p>
<p> A revision relation<span class="withAsn">, written <span class="name">wasRevisionOf(e2,e1,ag,attrs)</span> in PROV-ASN,</span> contains:</p>
<ul>
@@ -1718,7 +1728,7 @@
<div class="anexample">
<p>
Suppose document <span class="name">e1</span> is subject to revision by a quality controller, <span class="name">ag</span>.
-The following assertions state that <span class="name">ag</span> has been instrumental in creating a new version <span class="name">e2</span> of document <span class="name">e1</span>:
+The following example states that <span class="name">ag</span> has been instrumental in creating a new version <span class="name">e2</span> of document <span class="name">e1</span>:
<pre class="codeexample">
agent(ag,[prov:type="QualityController"])
entity(e1,[prov:type="document"])
@@ -1741,7 +1751,7 @@
<section id="term-attribution">
<h3>Attribution</h3>
-<p>An <dfn>attribution relation</dfn> states that an entity is attributed to an agent. More precisely, asserting that an entity <span class="name">e</span> is attributed to agent <span class="name">ag</span> means that <span class="name">e</span> was generated by some activity <span class="name">a</span>, which 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>An <dfn>attribution relation</dfn> states that an entity is attributed to an agent. More precisely, 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 activity <span class="name">a</span>, which 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> An attribution relation<span class="withAsn">, written <span class="name"> wasAttributedTo(e,ag,attr)</span> in PROV-ASN,</span> contains the following elements:</p>
<ul>
@@ -1754,7 +1764,7 @@
<div class="anexample">
<p>
Suppose one knows that agent <span class="name">ag</span>, a document quality controller, has been responsible for the generation of a certain version <span class="name">e</span> of a document.
- This can be asserted simply as:
+ This can be expressed simply as:
<pre class="codeexample">
agent(ag,[prov:type="QualityController"])
@@ -1805,7 +1815,7 @@
<p> An <dfn>original source relation</dfn> is a particular case of <a href="#Derivation-Relation">derivation</a> that states that an entity <span class="name">e2</span> (derived) was originally part of some other entity <span class="name">e1</span> (the original source).</p>
-<p> An original source assertion, written <span class="name"> hadOriginalSource(e2,e1,attrs)</span>, contains:</p>
+<p> An original source relation<span class="withAsn">, written <span class="name"> hadOriginalSource(e2,e1,attrs)</span>,</span> contains:</p>
<ul>
<li><em>derived</em>: an identifier for the derived entity; </li>
<li><em>source</em>: an identifier for the original source entity;</li>
@@ -1834,10 +1844,10 @@
The following relations relate a collection <span class="name">c1</span> with a collection <span class="name">c2</span> obtainted after adding or removing a new pair to (resp. from) <span class="name">c1</span>:
<ul>
- <li>Insertion assertion <span class="name">CollectionAfterInsertion(c2,c1, k, v)</span> states that <span class="name">c2</span> is the state of the collection
+ <li>Insertion relation <span class="name">CollectionAfterInsertion(c2,c1, k, v)</span> states that <span class="name">c2</span> is the state of the collection
following the insertion of pair <span class="name">(k,v)</span> into collection <span class="name">c1</span>;</li>
-<li> Removal assertion <span class="name">CollectionAfterRemoval(c2,c1, k)</span> states that <span class="name">c2</span> is the state of the collection following the removal of the pair corresponding to key <span class="name">k</span> from <span class="name">c1</span>.</li>
+<li> Removal relation <span class="name">CollectionAfterRemoval(c2,c1, k)</span> states that <span class="name">c2</span> is the state of the collection following the removal of the pair corresponding to key <span class="name">k</span> from <span class="name">c1</span>.</li>
</ul>
@@ -1856,7 +1866,7 @@
</div>
-<p> An assertion CollectionAfterInsertion<span class="withAsn">, written <span class="name"> CollectionAfterInsertion(collAfter, collBefore, key, value)</span>,</span> contains:</p>
+<p> A relation CollectionAfterInsertion<span class="withAsn">, written <span class="name"> CollectionAfterInsertion(collAfter, collBefore, key, value)</span>,</span> contains:</p>
<ul>
<li><em>after</em>: an identifier for the collection <em>after</em> insertion; </li>
<li><em>before</em>: an identifier for the collection <em>before</em> insertion;</li>
@@ -1864,7 +1874,7 @@
<li><em>value</em>: an identifier for the value that has been inserted with the key.</li>
</ul>
-<p> An assertion CollectionAfterDeletion, written <span class="name"> CollectionAfterDeletion(collAfter, collBefore, key)</span>, contains:</p>
+<p> A relation CollectionAfterDeletion, written <span class="name"> CollectionAfterDeletion(collAfter, collBefore, key)</span>, contains:</p>
<ul>
<li><em>after</em>: an identifier for the collection <em>after</em> the deletion; </li>
<li><em>before</em>: an identifier for the collection <em>before</em> the deletion;</li>
@@ -1882,7 +1892,7 @@
<li>Insertion and removal relations are a particular case of <a href="#Derivation-Relation">derivation</a>.</li>
- <li>This representation of a collection's evolution makes no assumption regarding the underlying data structure used to store and manage collections. In particular, no assumptions are needed regarding the mutability of a data structure that is subject to updates. In fact, the state of a collection (i.e., the set of key-value pairs it contains) at a given point in a sequence of operations is never stated explicitly. Rather, it can be obtained by querying the chain of derivation assertions involving insertions and removals. Entity type <span class="name">emptyCollection</span> can be used in this context as it marks the start of a sequence of collection operations.</li>
+ <li>This representation of a collection's evolution makes no assumption regarding the underlying data structure used to store and manage collections. In particular, no assumptions are needed regarding the mutability of a data structure that is subject to updates. In fact, the state of a collection (i.e., the set of key-value pairs it contains) at a given point in a sequence of operations is never stated explicitly. Rather, it can be obtained by querying the chain of derivations involving insertions and removals. Entity type <span class="name">emptyCollection</span> can be used in this context as it marks the start of a sequence of collection operations.</li>
<!--