prov-dm-constraints
authorLuc Moreau <l.moreau@ecs.soton.ac.uk>
Mon, 13 Feb 2012 22:17:34 +0000
changeset 1542 b440fa146360
parent 1541 b9155b40e34f
child 1543 78a266e418bf
prov-dm-constraints
model/working-copy/prov-dm-constraints.html
--- a/model/working-copy/prov-dm-constraints.html	Mon Feb 13 22:15:47 2012 +0000
+++ b/model/working-copy/prov-dm-constraints.html	Mon Feb 13 22:17:34 2012 +0000
@@ -509,7 +509,7 @@
 
    <section id="record-Entity"> 
       
-<h4>Entity Record</h4>
+<h4>Entity</h4>
 
 
 <p>
@@ -565,7 +565,7 @@
 
     <section id="record-Activity"> 
       
-<h3>Activity Record</h3>
+<h3>Activity</h3>
 
 
 
@@ -610,7 +610,7 @@
 </section> 
 
 <section id="record-Agent">
-<h3>Agent Record</h3>
+<h3>Agent</h3>
 
 
 
@@ -635,7 +635,7 @@
 
    <section id="record-note"> 
       
-<h4>Note Record</h4>
+<h4>Note</h4>
 
 
 <p>
@@ -662,7 +662,7 @@
 
 
 <section id="record-Generation">
-<h4>Generation Record</h4>
+<h4>Generation</h4>
 
 
 <p>In PROV-DM, a <dfn id="dfn-Generation">generation record</dfn> is a representation of an instantaneous world <a title="entity generation event">event</a>, the completed creation of a new
@@ -673,8 +673,8 @@
 
 
 <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
-derivations (see <a href="#Derivation-Relation">Derivation Record</a>).
+A generation record's id is OPTIONAL. It MUST be used when annotating generation records (see Section <a href="#record-annotation">Annotation</a>) or when defining precise-1
+derivations (see <a href="#Derivation-Relation">Derivation</a>).
 </p>
 
 
@@ -700,7 +700,7 @@
 
 
 <section id="record-Usage">
-<h3>Usage Record</h3>
+<h3>Usage</h3>
 
 
 
@@ -712,8 +712,8 @@
 
 
 <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 href="#Derivation-Relation">Derivation Record</a>).</p>
+A usage record's id is OPTIONAL. It MUST be present when annotating usage records (see Section <a href="#record-annotation">Annotation</a>) or when defining precise-1 derivations (see
+<a href="#Derivation-Relation">Derivation</a>).</p>
 
 <p>
 A reference to a given entity record MAY appear in multiple usage records that share
@@ -735,7 +735,7 @@
 
 
 <section id="record-ActivityAssociation">
-<h4>Activity Association Record</h4>
+<h4>Activity Association</h4>
 
 
 
@@ -750,7 +750,7 @@
 </section>
 
 <section id="record-Start-End">
-<h4>Start and End Records</h4>
+<h4>Start and Ends</h4>
 
 
 <div class='issue'> 
@@ -769,7 +769,7 @@
 
 <section id="record-responsibility">
 
-<h4>Responsibility Record</h4>
+<h4>Responsibility</h4>
 
 
 Nothing here.
@@ -777,7 +777,7 @@
 </section>
 
 <section id="Derivation-Relation">
-<h4>Derivation Record</h4>
+<h4>Derivation</h4>
 
 
 
@@ -903,7 +903,7 @@
 
 <section id="record-alternate-specialization">
 
-<h4>Alternate  and Specialization Records</h4>
+<h4>Alternate  and Specializations</h4>
 
 In order to further convey the intended meaning, the following properties are associated to these two relations.
 
@@ -949,7 +949,7 @@
 
 
 <section id="record-traceability">
-<h3>Traceability Record</h3>
+<h3>Traceability</h3>
 
 
 <p>A traceability record can be inferred from existing records, or can be asserted stating that such a dependency path exists without the asserter knowing its individual steps, as expressed
@@ -1007,7 +1007,7 @@
 </section>
 
 <section id="record-OrderingOfActivities">
-<h3>Activity Ordering Record</h3>
+<h3>Activity Ordering</h3>
 
 
 
@@ -1082,7 +1082,7 @@
 </section>
 
 <section id="record-Revision">
-<h3>Revision Record</h3>
+<h3>Revision</h3>
 
 
 
@@ -1113,7 +1113,7 @@
 
 
 <section id="recod-attribution">
-<h3>Attribution Record</h3> 
+<h3>Attribution</h3> 
 
 
 <div class='inference' id='attribution-implication'>
@@ -1133,7 +1133,7 @@
 
 
 <section id="record-quotation">
-<h3>Quotation Record</h3>
+<h3>Quotation</h3>
 
 
 <div class='inference' id='quotation-implication'>
@@ -1152,7 +1152,7 @@
 
 
 <section id="record-summary">
-<h3>Summary Record</h3>
+<h3>Summary</h3>
 
 <div class='issue'>Drop this relation  <a href="http://www.w3.org/2011/prov/track/issues/220">ISSUE-220</a>.</div>
 
@@ -1161,7 +1161,7 @@
 </section>
 
 <section id="record-orignal-source">
-<h3>Original Source Record</h3>
+<h3>Original Source</h3>
 
 <p>Nothing specific.</p>
 
@@ -1279,7 +1279,7 @@
 
 
       <section id="record-Account">
-	<h3>Account Record</h3>
+	<h3>Account</h3>
 
 	<p>It is common for multiple provenance records to co-exist. For instance, when emailing
 	  a file, there could be a provenance record kept by the mail client,