--- a/model/working-copy/towards-wd4.html Fri Feb 10 08:48:23 2012 +0000
+++ b/model/working-copy/towards-wd4.html Fri Feb 10 09:04:52 2012 +0000
@@ -512,7 +512,7 @@
<p>
-In this section, we show the kind of provenance records the <a href="http://www.w3.org/Consortium">WWW Consortium</a> could keep for auditors to check that due processes are followed. All entities involved in this example are Web resources, with well defined URIs (some of which locating archived email messages, available to W3C Members).</p>
+In this section, we show the kind of provenance record that the <a href="http://www.w3.org/Consortium">WWW Consortium</a> could keep for auditors to check that due processes are followed. All entities involved in this example are Web resources, with well defined URIs (some of which locating archived email messages, available to W3C Members).</p>
<ul>
<li> Two versions of the technical report are involved: <span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111215">tr:WD-prov-dm-20111215</a></span> (second working draft) and <span class="name"><span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018">tr:WD-prov-dm-20111018</a></span></span> (first working draft);</li>
@@ -679,11 +679,11 @@
<h2>PROV-DM Core</h2>
-<section id="record-element">
+<section id="term-element">
<h3>Element</h3>
- <section id="record-Entity">
+ <section id="term-Entity">
<h4>Entity</h4>
@@ -711,7 +711,7 @@
</ul>
-<div class='issue'>The characterization interval of an entity record is currently implicit. Making it explicit would allow us to define wasComplementOf more precisely.
+<div class='issue'>The characterization interval of an entity is currently implicit. Making it explicit would allow us to define wasComplementOf more precisely.
Beginning and end of characterization interval could be expressed by attributes (similarly to activities).
How do we define the end of an entity? This is <a href="http://www.w3.org/2011/prov/track/issues/204">ISSUE-204</a>.
</div>
@@ -727,7 +727,7 @@
</section>
- <section id="record-Activity">
+ <section id="term-Activity">
<h3>Activity</h3>
@@ -770,7 +770,7 @@
</section>
-<section id="record-Agent">
+<section id="term-Agent">
<h3>Agent</h3>
@@ -786,7 +786,7 @@
<p>
From an inter-operability perspective, it is useful to define some basic categories of agents since
-it will improve the use of provenance records by applications.
+it will improve the use of provenance by applications.
There should be very few of these basic categories to keep the model simple and accessible.
There are three types of agents in the model since they are common across most anticipated domain of use:
<ul>
@@ -811,7 +811,7 @@
</section>
- <section id="record-note">
+ <section id="term-note">
<h4>Note</h4>
@@ -829,7 +829,7 @@
-<p>A separate PROV-DM construct is used to associate a note with something that is identifiable (see <a href="#record-annotation">Section on annotation</a>). A given note may be associated with
+<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>
@@ -843,8 +843,8 @@
note(n1,[ex:color="blue", ex:screenX=20, ex:screenY=30])
hasAnnotation(g1,n1)
</pre>
-<p>The note is associated with an assertion <span class="name">g1</span> previously introduced (<a title="annotation record">hasAnnotation</a> is
-discussed in Section <a href="#record-annotation">Annotation</a>). In this example,
+<p>The note is associated with an assertion <span class="name">g1</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.
</p>
@@ -856,10 +856,10 @@
</section>
-<section id="record-relation">
+<section id="term-relation">
<h3>Relation</h3>
-<p>This section describes all the PROV-DM relations between the elements introduced in <a href="#record-element">Section Element</a>. While these relations are not
+<p>This section describes all the PROV-DM relations between the elements introduced in <a href="#term-element">Section Element</a>. While these relations are not
binary, they all involve two primary elements. They can be summarized as follows. </p>
@@ -867,7 +867,7 @@
<table border="1" style="margin-left: auto; margin-right: auto;">
<caption>PROV-DM Core Relation Summary</caption>
<tr><td></td><td>Entity</td><td>Activity</td><td>Agent</td><td>Note</td></tr>
-<tr><td>Entity</td><td><a title="derivations">wasDerivedFrom</a><br><a title="alternate record">alternateOf</a><br><a title="specialization record">specializationOf</a></td><td><a
+<tr><td>Entity</td><td><a title="derivations">wasDerivedFrom</a><br><a title="alternate">alternateOf</a><br><a title="specialization record">specializationOf</a></td><td><a
title="generation">wasGeneratedBy</a></td><td>—</td><td><a title="annotation">hasAnnotation</a></td></tr>
<tr><td>Activity</td><td><a title="usage">used</a></td><td>—</td><td><a title="start record">wasStartedBy</a><br><a title="end record">wasEndedBy</a><br><a title="activity association">wasAssociatedWith</a></td><td><a title="annotation">hasAnnotation</a></td></tr>
<tr><td>Agent</td><td>—</td><td>—</td><td><a title="responsibility chain">actedOnBehalfOf</a></td><td><a title="annotation">hasAnnotation</a></td></tr>
@@ -880,7 +880,7 @@
<section id="activity-entity-relation">
<h3>Activity-Entity Relation</h3>
-<section id="record-Generation">
+<section id="term-Generation">
<h4>Generation</h4>
@@ -926,7 +926,7 @@
<div class='note'>
<p>?????????
-A generation record's id is OPTIONAL. It MUST be used when annotating generation records (see Section <a href="#record-annotation">Annotation Record</a>) or when defining precise-1
+A generation's id is OPTIONAL. It MUST be used when annotating generations (see Section <a href="#term-annotation">Annotation Record</a>) or when defining precise-1
derivations (see <a href="#Derivation-Relation">Derivation Record</a>).
</p>
</div>
@@ -938,7 +938,7 @@
</section>
-<section id="record-Usage">
+<section id="term-Usage">
<h3>Usage</h3>
@@ -978,7 +978,7 @@
<p>
-A usage record's id is OPTIONAL. It MUST be present when annotating usage records (see Section <a href="#record-annotation">Annotation Record</a>) or when defining precise-1 derivations (see
+A usage record's id is OPTIONAL. It MUST be present when annotating usage records (see Section <a href="#term-annotation">Annotation Record</a>) or when defining precise-1 derivations (see
<a href="#Derivation-Relation">Derivation</a>).</p>
</div>
@@ -995,12 +995,12 @@
<section id="activity-agent-relation">
<h3>Activity-Agent Relation</h3>
-<section id="record-ActivityAssociation">
+<section id="term-ActivityAssociation">
<h4>Activity Association</h4>
<p>As far as responsibility is concerned, PROV-DM offers two kinds of constructs. The first, introduced in this section, represents an association between an agent, a plan, and an activity; the second, introduced in <a
-href="#record-responsibility">Section Responsibility</a>, represents the fact that an agent was acting on behalf of another, in the context of an activity. </p>
+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
@@ -1038,7 +1038,7 @@
</section>
-<section id="record-Start-End">
+<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.
@@ -1071,8 +1071,8 @@
wasStartedBy(a,ag,[ex:mode="manual"])
wasEndedby(a,ag,[ex:mode="manual"])
</pre>
-<p>state that the activity, represented by the activity record denoted by <span class="name">a</span>
-was started and ended by an agent, represented by record denoted by <span class="name">ag</span>, in "manual" mode, an application specific characterization of these relations.
+<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>
</div>
@@ -1092,7 +1092,7 @@
<section id="entity-entity-agent-agent-relation">
<h4>Entity-Entity or Agent-Agent Relation</h4>
-<section id="record-responsibility">
+<section id="term-responsibility">
<h4>Responsibility Chain</h4>
@@ -1159,7 +1159,7 @@
However, asserters may not assert or have knowledge of these activities and associated details: they may not assert or know their number, they may not assert or know their identity, they may
not assert or know the attributes characterizing how the relevant entities are used or generated. To accommodate the varying circumstances of the various asserters, PROV-DM allows more or
less precise derivations to be asserted. Hence, PROV-DM uses the terms <em>precise</em> and <em>imprecise</em> to characterize the different kinds of derivations. We note
-that the derivation itself is exact (i.e., deterministic, non-probabilistic), but it is its description, expressed in a derivation record, that may be imprecise. </p>
+that the derivation itself is exact (i.e., deterministic, non-probabilistic), but it is its description, expressed in a derivation assertion, that may be imprecise. </p>
<p>The lack of precision may come from two sources:</p>
<ul>
@@ -1273,7 +1273,7 @@
<span class="name">g2</span>. </p>
<p>
-The third record 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 records 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 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>.
</p>
</div>
@@ -1294,7 +1294,7 @@
</section>
-<section id="record-alternate-specialization">
+<section id="term-alternate-specialization">
<h4>Alternate and Specialization</h4>
@@ -1357,7 +1357,7 @@
-<section id="record-annotation">
+<section id="term-annotation">
<h4>Annotation</h4>
@@ -1373,7 +1373,7 @@
<li><em>attributes</em>: an OPTIONAL set of attribute-value pairs to further describe this annotation.</li>
</ul>
-<p>The interpretation of notes is application-specific. See Section <a href="#record-note">Note</a> for a discussion of the difference between note attributes and other records attributes.
+<p>The interpretation of notes is application-specific. See Section <a href="#term-note">Note</a> for a discussion of the difference between note attributes and other attributes in elements and relations.
We also note the present tense in this term to indicate that it may not denote something in the past.</p>
<div class="anexample">
@@ -1407,12 +1407,12 @@
-<section id="sub-record">
+<section id="second-class-elements">
<h3>Further Elements of PROV-DM</h3>
This section introduces further elements of PROV-DM.
-<section id="record-NamespaceDeclaration">
+<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
@@ -1425,7 +1425,7 @@
refers to this namespace.</p>
</section>
-<section id="record-identifier">
+<section id="term-identifier">
<h4>Identifier</h4>
<p>
@@ -1447,7 +1447,7 @@
</section>
-<section id="record-attribute">
+<section id="term-attribute">
<h4>Attribute</h4>
<p>An <dfn id="dfn-attribute">attribute</dfn> is a <a>qualified name</a>.
@@ -1456,7 +1456,7 @@
<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.
The interpretation of any attribute declared in another namespace is out of scope.</p>
-<section id="record-attribute-role">
+<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,
@@ -1471,7 +1471,7 @@
</div>
</section>
-<section id="record-attribute-type">
+<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
@@ -1480,14 +1480,14 @@
is allowed to occur multiple times.</p>
<div class="anexample">
-<p>The following record declares an agent of type software agent</p>
+<p>The following assertion declares an agent of type software agent</p>
<pre class="codeexample">
agent(ag, [prov:type="prov:SoftwareAgent" %% xsd:QName])
</pre>
</div>
</section>
-<section id="record-attribute-steps">
+<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
@@ -1504,7 +1504,7 @@
</div>
</section>
-<section id="record-attribute-label">
+<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>
@@ -1515,7 +1515,7 @@
-<section id="record-attribute-location">
+<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,
@@ -1538,7 +1538,7 @@
-<section id="record-literal">
+<section id="term-literal">
<h4>Literal</h4>
<p>
@@ -1571,14 +1571,14 @@
-<section id="record-Time">
+<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 records.</p>
+<p>It is OPTIONAL to assert time in usage, generation, and activity</p>
@@ -1607,7 +1607,7 @@
<div class='note'>will turn into UML</div>
-<section id="record-traceability">
+<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>
@@ -1628,7 +1628,7 @@
<ul>
<li>Traceability is more general than <a href="#Derivation-Relation">Derivation</a>. This means that an assertion of the form: <span class="name">tracedTo(...,e2,e1,...)</span> can be inferred from an assertion of the form:
<span class="name">wasDerivedFrom(e2,e1,..)</span>. The precise inference rules are specified in [REF].
- <li>Traceability is related to responsibility by way of inference rules that involve <a href="#record-responsibility">responsibility chain</a> and <a href="#record-Generation">generation</a> relations.
+ <li>Traceability is related to responsibility by way of inference rules that involve <a href="#term-responsibility">responsibility chain</a> and <a href="#term-Generation">generation</a> relations.
These rules are specified in [REF]
</ul>
@@ -1639,19 +1639,19 @@
</section>
-<section id="record-OrderingOfActivities">
+<section id="term-OrderingOfActivities">
<h3>Activity Ordering</h3>
-The following relation is used to express dependencies amongst activities.
+<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 record</dfn> states that activity <span class="name">a2</span> was initiated by another activity <span class="name">a1</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>.
</ul>
<p>
-An information flow ordering assertion<span class="withAsn">, written as
+An information flow ordering relation<span class="withAsn">, written as
<span class="name">wasInformedBy(id,a2,a1,attrs)</span> in PROV-ASN,</span> contains:
<ul>
<li><em>id</em>: an OPTIONAL identifier identifying the relation;</li>
@@ -1673,7 +1673,7 @@
<p>
-A control ordering assertion<span class="withAsn">, written as
+A control ordering relation<span class="withAsn">, written as
<span class="name">wasStartedBy(a2,a1, attrs)</span> in PROV-ASN,</span> contains: </p>
<ul>
<li><em>id</em>: an OPTIONAL identifier of the relation;</li>
@@ -1683,11 +1683,7 @@
</ul>
-<p>Further considerations:</p>
-
-<ul>
- <li> Relation <span class="name">wasInformedBy</span> is not transitive.
-</ul>
+<p> Relation <span class="name">wasInformedBy</span> is not transitive.</p>
<div class="anexample">
@@ -1703,18 +1699,18 @@
</section>
-<section id="record-Revision">
+<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 revision assertion<span class="withAsn">, written <span class="name">wasRevisionOf(e2,e1,ag,attrs)</span> in PROV-ASN,</span> contains:</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>
<li><em>id</em>: an OPTIONAL identifier for the relation;</li>
<li><em>newer</em>: the identifier of the revised entity;
<li><em>older</em>: the identifier of the older entity;
<li><em>responsibility</em>: an OPTIONAL identifier for the agent who approved that newer entity is a variant of the older;
-<li><em>attributes</em>: an OPTIONAL set of attribute-value pairs to further describe this record.</li>
+<li><em>attributes</em>: an OPTIONAL set of attribute-value pairs to further describe the properties of this relation.</li>
</ul>
@@ -1742,12 +1738,12 @@
</section> <!-- end revision -->
-<section id="record-attribution">
+<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 attribution assertion<span class="withAsn">, written <span class="name"> wasAttributedTo(e,ag,attr)</span> in PROV-ASN,</span> contains the following elements:</p>
+<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>
<li><em>id</em>: an OPTIONAL identifier for the relation;</li>
<li><em>entity</em>: an entity identifier;</li>
@@ -1770,14 +1766,14 @@
</section> <!-- end attribution -->
-<section id="record-quotation">
-<h3>Quotation Record</h3>
+<section id="term-quotation">
+<h3>Quotation</h3>
<div class="note">I find that quotation is really a misnomer. This expands into derivation with attribution, in what sense is the derived entity a "quote" of the original? . The agent that is quoted is particularly obscure. It does not seem to be involved in the quoting at all. Why isn't quoting an activity with the quoting agent associated with it? [PM]</div>
<p> A <dfn>quotation relation</dfn> is a particular case of <a href="#Derivation-Relation">derivation</a> that states that entity <span class="name">e2</span> is derived from entity <span class="name">e1</span> by copying, or "quoting", parts of it.</p>
-<p> A quotation assertion<span class="withAsn">, written <span class="name"> wasQuotedFrom(id,e2,e1,ag2,ag1,attrs)</span> in PROV-ASN,</span> contains:</p>
+<p> A quotation relation<span class="withAsn">, written <span class="name"> wasQuotedFrom(id,e2,e1,ag2,ag1,attrs)</span> in PROV-ASN,</span> contains:</p>
<ul>
<li><em>id</em>: an OPTIONAL identifier for the relation;</li>
<li><em>quote</em>: an identifier of the entity that represents the quote (the partial copy);
@@ -1791,7 +1787,7 @@
</section> <!-- end quotation -->
-<section id="record-summary">
+<section id="term-summary">
<h3>Summary</h3>
<div class="note">Omitted as this is likely to be removed [PM]</div>
@@ -1802,7 +1798,7 @@
</section> <!-- end summary -->
-<section id="record-orignal-source">
+<section id="term-orignal-source">
<h3>Original Source</h3>
<div class="note"> I find this relation confusing. Please add an example. I wouldn't really know when to use this. [PM]</div>
@@ -1820,7 +1816,7 @@
-<section id="record-Collection">
+<section id="term-Collection">
<h3>Collections</h3>
<p><strong>Collection relations</strong> address the need to describe the evolution of entities that have a collection structure, that is, which may contain other entities. Specifically this section introduces a new built-in type for entities, called <span class="name">collection</span>, and two relations to describe the effect of adding elements to, and removing elements from, a collection entity.
@@ -2007,7 +2003,7 @@
<p>The PROV data model is designed to be application and technology independent, but specializations of PROV-DM are welcome and encouraged. To ensure inter-operability, specializations of
the PROV data model that exploit the extensibility points summarized in this section MUST preserve the semantics specified in this document. For instance, a qualified attribute on a domain
-specific entity MUST represent an aspect of an entity and this aspect MUST remain unchanged during the characterization's interval of this entity record.</p>
+specific entity MUST represent an aspect of an entity and this aspect MUST remain unchanged during the characterization's interval of this entity.</p>