--- a/model/working-copy/wd5-prov-dm-components.html Mon Mar 12 11:17:46 2012 +0000
+++ b/model/working-copy/wd5-prov-dm-components.html Mon Mar 12 11:23:28 2012 +0000
@@ -1822,7 +1822,7 @@
<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 with <a title="qualified name">qualified names</a> as data type can be placed in a namespace using the mechanisms described in this specification. </p>
+<p>A PROV-DM <dfn id="dfn-namespace">namespace</dfn> is identified by an IRI reference [[!IRI]]. In PROV-DM, attributes, identifiers, and values with <a title="qualified name">qualified names</a> as data type 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
@@ -1869,7 +1869,7 @@
<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 a PROV-DM <a title="literal">Literal</a>.</p>
+class="name">prov:role</span> attribute MUST be a PROV-DM <a title="value">Value</a>.</p>
<div class="anexample">
<p>The following activity start describes the role of the agent identified by <span class="name">ag</span> in this start relation with activity <span class="name">a</span>. </p>
@@ -1884,7 +1884,7 @@
<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 a PROV-DM Literal. The attribute <span class="name">prov:type</span>
+the value associated with a <span class="name">prov:type</span> attribute MUST be a PROV-DM <a title="value">Value.</a> The attribute <span class="name">prov:type</span>
is allowed to occur multiple times.</p>
<div class="anexample">
@@ -1915,7 +1915,7 @@
<p>
-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 PROV-DM Literal, expected to denote a location.
+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 PROV-DM <a title="value">Value</a>, expected to denote a location.
</p>
<div class="anexample">
@@ -1931,11 +1931,11 @@
</section>
-<section id="term-literal">
+<section id="term-value">
<h4>Value</h4>
<p>
-By means of attribute-value pairs, the PROV data model can refer to values such as strings, numbers, time and IRIs.
+By means of attribute-value pairs, the PROV data model can refer to <dfn title="value">values</dfn> such as strings, numbers, time and IRIs.
The interpretation of such values is outside the scope of PROV-DM.</p>
Each kind of such values is called a <em>datatype</em>. Each datatype is identified by an IRI.</p>
@@ -2120,7 +2120,7 @@
<li>Sub-typing of elements and relations is allowed by means of the reserved attribute <span class="name">type</span>.</li>
-<li>Domain specific values can be expressed by means of typed literals. </li>
+<li>Domain specific values can be expressed by means of typed values. </li>
</ul>
<p>The PROV data model is designed to be application and technology independent, but specializations of PROV-DM are welcome and encouraged. To ensure interoperability, specializations of