--- a/model/ProvenanceModel.html Fri Nov 25 11:51:16 2011 +0000
+++ b/model/ProvenanceModel.html Fri Nov 25 12:04:34 2011 +0000
@@ -528,20 +528,20 @@
<h2>PROV-DM: An Overview </h2>
<p>
-The following ER diagram provides a high level overview of the <strong>structure of PROV-DM assertions</strong>. Examples of provenance assertions that conform to this schema are provided in the next section (note: cardinality constraints on the associations are 0..* unless otherwise stated)</p>
+The following ER diagram provides a high level overview of the <strong>structure of PROV-DM records</strong>. Examples of provenance assertions that conform to this schema are provided in the next section (note: cardinality constraints on the associations are 0..* unless otherwise stated)</p>
<img src="overview.png" alt="PROV-DM overview"/>
<p>The model includes the following elements:</p>
<ul>
- <li>An <strong>Entity Record</strong> (noted <samp>entity</samp> in the diagram, to reflect the term used in the ASN) is a representation of an <em>entity</em>. The EntityRecord may specify a set of <strong>attributes</strong>. The
- <strong>wasComplementOf</strong> 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.</li>
+ <li>An <a title="entity record">Entity Record</a> (noted <samp>entity</samp> in the diagram, to reflect the term used in the ASN) is a representation of an <em>entity</em>. The EntityRecord may specify a set of <a title="attribute">attributes</a>. 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.</li>
- <li>An <strong>Activity Record </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 <strong>used</strong> and the <strong>wasGeneratedBy</strong> 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 may use multiple <samp>entities</samp>. Finally, entities can be derived from other entities, and this is specified using the <strong>wasDerivedFrom</strong> relation.</li>
+ <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 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 <strong>Agent Record</strong> represent a particular <samp>entity</samp> that can be associated to activities, meaning it is capable of controlling <samp>activitys</samp>.
- Agents have a rather generic connotation: their association with an activity is represented by the <strong>wasAssociatedWith</strong> relationship, which can take up various meanings (attribution, responsibility, supervision, management, etc.), which are not individually specified in the model. Relations <strong>wasStartedBy</strong> and <strong>wasEndedBy</strong> are specializations of <strong>wasAssociatedWith</strong> that can optionaly be used to carry additional meaning.
+ <li>An <a title="agent record">Agent Record</a> represent a particular <samp>entity</samp> that can be associated to activities, meaning it is capable of controlling <samp>activitys</samp>.
+ 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 optionaly be used to carry additional meaning.
</li>
@@ -552,7 +552,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
-their nature. <strong>Role</strong> is a pre-defined attribute.</li>
+their nature. The attributes <a title="prov:role">role</a> and <a title="prov:type">type</a> are pre-defined.</li>
</p>
@@ -560,11 +560,11 @@
<p>
-The model includes a further additional elements: <strong>notes</strong>. These are also structured as sets of attribute-value pairs. Notes 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 in notes attributes and the other attributes is further clarified <a href="#record-note">here</a>.
+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. The difference between attributes in notes attributes and the other attributes is further clarified <a href="#record-note">here</a>.
</p>
<p>
-Attributes and annotations are the main <strong>extensibility points</strong> in the model: individual interest groups are expected to extend PROV-DM by introducing new sets of attributes and annotations as needed to address applications-specific provenance modelling requirements. </p>
+Attributes and annotations are the main <em>extensibility points</em> in the model: individual interest groups are expected to extend PROV-DM by introducing new sets of attributes and annotations as needed to address applications-specific provenance modelling requirements. </p>
</section>
@@ -843,7 +843,7 @@
<h4>Entity Record</h4>
-<p>In PROV-DM, an <dfn id="dfn-entity" title="entity">entity record</dfn> is a representation of an entity.</p>
+<p>In PROV-DM, an <dfn id="dfn-entity">entity record</dfn> is a representation of an entity.</p>