--- a/model/ProvenanceModel.html Thu Oct 06 12:20:35 2011 +0100
+++ b/model/ProvenanceModel.html Thu Oct 06 12:32:41 2011 +0100
@@ -190,6 +190,17 @@
</section>
+<section id="prov-dm-namespace">
+ <h3>PROV-DM Namespace</h3>
+
+
+<p>The PROV-DM namespace is <span class="name">http://www.w3.org/2011/prov/</span> (TBD).</p>
+
+<p> All the elements, relations, reserved names and attributes introduced in this specification belong to the PROV-DM namespace.
+</p>
+
+</section>
+
<section>
<h3>Conventions</h3>
@@ -222,7 +233,7 @@
<!--
-<div class='paolo'>This is the single most important issue IMO: we hit readers with this "characterised thing" which is unexpected. We need to be absolutely clear about it...
+<div class='paolo'>This is the single most important issue IMO: we hit readers with this "characterized thing" which is unexpected. We need to be absolutely clear about it...
<br/>ok, so it seems that characterized thing is introduced to deal with (1) imprecision, (2) disagreement amongst different "observers" of the same data-related events. I don't think this is about "disambiguation". It's about accommmodating different perspectives on the what is the same abstract "thing". This interpretation fits with the example: "different users may take different perspective..."</div>
-->
@@ -380,7 +391,7 @@
The model includes two additional types: <strong>qualifiers</strong> and <strong>annotations</strong>. These are both structured as sets of attribute-value pairs.
- <ul><li> Qualifiers can be associated to relations, namely <strong>use</strong> and <strong>wasGeneratedBy</strong>, in order to further characterise their nature. <strong>Role</strong> is a standard qualifier.</li>
+ <ul><li> Qualifiers can be associated to relations, namely <strong>use</strong> and <strong>wasGeneratedBy</strong>, in order to further characterize their nature. <strong>Role</strong> is a standard qualifier.</li>
<li> Annotations are used to provide additional, "free-form" information regarding <strong>any</strong> identifiable construct of the model, with no prescribed meaning. The difference between attributes and annotations is further clarified <a href="#expression-annotation">here</a>. </li>
</ul>
@@ -566,7 +577,7 @@
<p>
-Control Expressions (described in <a href="#expression-Control">Section Control</a>): the influence of an agent over a process execution is expressed as control, and the nature of this influence is described by qualifier (construct described in <a href="#expression-qualifier">Section Qualifier</a>). Illustrations of such qualifiers include the role of the participating agenr: are creator, author and communicator.</p>
+Control Expressions (described in <a href="#expression-Control">Section Control</a>): the influence of an agent over a process execution is expressed as control, and the nature of this influence is described by qualifier (construct described in <a href="#expression-qualifier">Section Qualifier</a>). Illustrations of such qualifiers include the role of the participating agent, as creator, author and communicator.</p>
<pre>
wasControlledBy(pe0,a1, qualifier(role="creator"))
wasControlledBy(pe1,a2, qualifier(role="author"))
@@ -1401,10 +1412,10 @@
<p>
The rationale for introducing this relationship is that in general, at any given time, for a thing in the world, there may be multiple ways of characterizing it, and hence multiple representations can be asserted by different asserters. In the example that follows, suppose thing "Royal Society" is represented by two asserters, each using a different set of attributes. If the asserters agree that both representations refer to "The Royal Society", the question of whether any correspondence can be established between the two representations arises naturally. This is particularly relevant when (a) the sets of properties used by the two representations overlap partially, or (b) when one set is subsumed by the other. In both these cases, we have a situation where each of the two asserters has a partial view of "The Royal Society", and establishing a correspondence between them on the shared properties is beneficial, as in case (a) each of the two representation <em>complements</em> the other, and in case (b) one of the two (that with the additional properties) complements the other.</p>
-<p>This intuition is made more precise by considering the entities that form the representations of characterised things at a certain point in time.
+<p>This intuition is made more precise by considering the entities that form the representations of characterized things at a certain point in time.
An entity expression represents, by means of attribute-value pairs, a thing and its situation in the world, which remain constant over a characterization interval.
-As soon as the thing's situation changes, this marks the end of the characterization interval for the entity expression representing it. The thing's novel situation is represented by an attribute with a new value, or an entirely different set of attribute-value pairs, embodied in another entity expression, with a new characterization interval. Thus, if we overlap the timelines (or, more generally, the sequences of value-changing events) for the two characterised things, we can hope to establish correspondences amongst the entity expressions that represent them at various points along that events line. The figure below illustrates this intuition.</p>
+As soon as the thing's situation changes, this marks the end of the characterization interval for the entity expression representing it. The thing's novel situation is represented by an attribute with a new value, or an entirely different set of attribute-value pairs, embodied in another entity expression, with a new characterization interval. Thus, if we overlap the timelines (or, more generally, the sequences of value-changing events) for the two characterized things, we can hope to establish correspondences amongst the entity expressions that represent them at various points along that events line. The figure below illustrates this intuition.</p>
<img src="complement-of.png" alt="illustration complementOf"/>
@@ -2017,7 +2028,7 @@
</ul>
-<p>The PROV data model introduces a specific qualifier <span class="name">role</span> to denote the function of a characterized thing with respect to an activity, in the context of a use/generation/control relation. The value associated with a <span class="name">role</span> attribute MUST be conformant with <span class="nonterminal">Literal</span>. </p>
+<p>The PROV data model introduces the qualifier <span class="name">role</span> in the <a href="#prov-dm-namespace">PROV-DM namespace</a> to denote the function of a characterized thing with respect to an activity, in the context of a use/generation/control relation. The value associated with a <span class="name">role</span> attribute MUST be conformant with <span class="nonterminal">Literal</span>. </p>
<p>
@@ -2208,7 +2219,7 @@
<ul>
<li> Attributes are constructs of the data model that allow representations of aspects of the world's things and activities to be expressed. Applications are free to introduce application-specific attributes, according to their perspective on the world. Attributes for a given application can be distinguished by qualifying them with a prefix denoting a namespace declared in a namespace declaration.
-<p>The PROV DM namespace (TBD) declares a set of reserved attributes: <span class="name">type</span>, <span class="name">location</span>.</li>
+<p>The <a href="#prov-dm-namespace">PROV-DM namespace</a> declares a set of reserved attributes: <span class="name">type</span>, <span class="name">location</span>.</li>
<li>Annotation expressions allow arbitrary metadata to be associated with identifiable expressions of PROV-DM. Annotation expressions consist of name-value pairs. Like attributes, names are qualified by a namespace.</li>
@@ -2217,7 +2228,7 @@
They consist of ordered sequence of name-value pairs. Such names
are also qualified by namespaces.
-<p>The PROV DM namespace (TBD) declares a reserved qualifier: <span class="name">role</span>.</p></li>
+<p>The <a href="#prov-dm-namespace">PROV-DM namespace</a> declares a reserved qualifier: <span class="name">role</span>.</p></li>
<li>Namespaces allow attributes and names to be qualified. </li>