--- a/model/ProvenanceModel.html Mon Dec 05 12:00:11 2011 +0000
+++ b/model/ProvenanceModel.html Mon Dec 05 12:06:24 2011 +0000
@@ -242,7 +242,7 @@
<p><a href="#prov-dm-overview">Section 3</a> provides an overview of PROV-DM listing its core types and their relations.</p>
<p>In <a href="#prov-dm-example">section 4</a>, PROV-DM is
-applied to a short scenario, encoded in PROV-ASM, and illustrated
+applied to a short scenario, encoded in PROV-ASN, and illustrated
graphically.</p>
<p><a href="#data-model-concepts">Section 5</a> provides the normative definition of PROV-DM and the notation PROV-ASN.</p>
@@ -317,7 +317,7 @@
<li>a report available at URL: fixes the nature of the thing, i.e. a document, and its location; </li>
<li>the version of the report available there today: fixes its version number, contents, and its date;</li>
<li>the report independent of where it is hosted and of its content over time: fixes the nature of the thing as a conceptual artifact.</li></ul>
-The provenance of these three entities may differ, and may be along the follow lines:
+The provenance of these three entities may differ, and may be along the following lines:
<ul>
<li>the provenance of a report available at URL may include: the act of publishing it and making it available at a given location, possibly under some license and access control;</li>
<li>the provenance of the version of the report available there today may include: the authorship of the specific content, and reference to imported content;</li>
@@ -423,7 +423,7 @@
scope of this specification. </p>
<p>PROV-DM also allows for time observations to be inserted in specific
-provenance records, for each of the recognized <a>event</a> introduced
+provenance records, for each recognized <a>event</a> introduced
in this specification. The presence of a time observation for a
given <a>event</a> fixes the mapping of this <a>event</a> to the
timeline. It can also help with the verification of associated
@@ -583,7 +583,7 @@
<li>An <a title="activity record">Activity Record</a> </strong>(noted <samp>activity</samp> in the diagram) represents an activity that has an effect on entities, namely it either <em>generates</em> or <em>uses</em> one or more entities. Usage and generation are modelled by means of the <a title="usage record">used</a> and the <a title="generation record">wasGeneratedBy</a> relationships. Activities may include not only computations, but also any other type of activity that can be described in terms of their effect on <samp>entities</samp>.
Note that multiple <samp>activities</samp> may <em>use</em> the same <samp>entity</samp>, and each activity may use multiple <samp>entities</samp>. Finally, entities can be derived from other entities, and this is specified using the <a title="derivation record">wasDerivedFrom</a> relation.</li>
- <li>An <a title="agent record">Agent Record</a> represent a particular <samp>entity</samp> that can be associated to activities, meaning that it can be assigned some degree of responsibility for an <samp>activity</samp> taking place.
+ <li>An <a title="agent record">Agent Record</a> represents a particular <samp>entity</samp> that can be associated to activities, meaning that it can be assigned some degree of responsibility for an <samp>activity</samp> taking place.
Agents have a rather generic connotation: their association with an activity is represented by the <a title="activity association record">wasAssociatedWith</a> relationship, which can take up various meanings (attribution, responsibility, supervision, management, etc.), which are not individually specified in the model. Relations <a title="start record">wasStartedBy</a> and <a title="end record">wasEndedBy</a> are specializations of <a title="activity association record">wasAssociatedWith</a> that can optionally be used to carry additional meaning. Furthermore, it is recognized that agents can act on behalf of others: hence, the relation <a title="responsibility record">actedOnBehalfOf</a> allows for chains of responsibility to be stated.
</li>
@@ -591,7 +591,7 @@
</ul>
-<p> Set of attribute-value pairs can be associated to all element and relations of the PROV model in order to further characterize
+<p> A set of attribute-value pairs can be associated to elements and relations of the PROV model in order to further characterize
their nature.
The <a title="complementarity record">wasComplementOf</a> relationship is used to denote that two <samp>entities</samp> <em>complement</em> each other, in the sense that they each represent a partial, but mutually compatible characterization of the same thing.
The attributes <a title="prov:role">role</a> and <a title="prov:type">type</a> are pre-defined.
@@ -602,7 +602,7 @@
<p>
-The model includes a further additional elements: <a title="note record">notes</a>. These are also structured as sets of attribute-value pairs. Notes are used to provide additional, "free-form" information regarding <em>any</em> identifiable construct of the model, with no prescribed meaning. Notes are described in detail <a href="#record-note">here</a>.
+The model includes a further additional element: <a title="note record">notes</a>. These are also structured as sets of attribute-value pairs. Notes are used to provide additional, "free-form" information regarding <em>any</em> identifiable construct of the model, with no prescribed meaning. Notes are described in detail <a href="#record-note">here</a>.
</p>
<p>
@@ -3246,6 +3246,7 @@
<h2>Changes Since First Public Working Draft</h2>
<ul>
<li>12/05/11: Changed syntax of recordContainer to be more user friendly, and removed list of account ids, since redundant. </li>
+<li>12/05/11: Changed syntax of namespace declaration to be more user friendly. </li>
<li>12/05/11: Simplified Typed literals, now allows for intLiteral, and datatype adjusted to be qualified name. </li>
<li>11/29/11: Introduced typed identifiers to make grammar clearer. </li>
<li>11/29/11: Added section 2.4 on grammar notation. </li>