prov-asn
authorLuc Moreau <l.moreau@ecs.soton.ac.uk>
Wed, 15 Feb 2012 15:21:17 +0000
changeset 1573 46dcdcef78f9
parent 1572 6c18cf202515
child 1574 34569a78e434
prov-asn
model/working-copy/prov-asn.html
model/working-copy/towards-wd4.html
--- a/model/working-copy/prov-asn.html	Wed Feb 15 14:03:45 2012 +0000
+++ b/model/working-copy/prov-asn.html	Wed Feb 15 15:21:17 2012 +0000
@@ -212,7 +212,7 @@
 <li> PROV-ASN is instrumental in defining the mapping mapping of PROV-DM to concrete syntaxes. Mappings translate each PROV-ASN expression to RDF [[PROV-RDF]] and to XML [[PROV-XML]];</li>
 <li> PROV-ASN is the basis for a
 formal semantics, in which each PROV-ASN expression is provided with an interpretation [[PROV-SEM]].
-</p>
+</ul>
 
 <p>PROV-ASN was designed to be as close as possible to PROV-DM without the syntactic bias and modelling constraints that concrete technologies bring with them, e.g., XML's choice between attribute and element, RDF's reliance on triples, or JSON's usage of dictionaries. </p>
 
@@ -237,6 +237,13 @@
 <li>PROV-SEM: semantics of the PROV-DM data model [[PROV-SEM]];</li>
 </ul>
 
+    <section id="structure-of-this-document"> 
+<h3>Structure of this Document</h3>
+
+<div class='note'>TODO</div>
+
+
+    </section> 
 
 
 <section id="prov-dm-namespace">
@@ -253,6 +260,21 @@
 
 </section>
 
+    <section id="conventions"> 
+<h3>Conventions</h3>
+
+
+
+<p>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
+      NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED",  "MAY", and
+      "OPTIONAL" in this document are to be interpreted as described in
+      [[!RFC2119]].</p>
+    </section> 
+
+</section> 
+
+
+
 </section>
 
 
@@ -301,9 +323,46 @@
 
 <h2>PROV-DM Core</h2>
 
+<p>Instances of the PROV-DM data model are expressed in PROV-ASN by a text conformant with the toplevel <a>production</a> <span class="nonterminal">expression</span> of the grammar. These <span
+class="nonterminal">expression</span>s are grouped in two categories:
+<span class="nonterminal">elementExpression</span> (see section <a href="#expression-element">Element</a>) and
+<span class="nonterminal">relationExpression</span>  (see section <a href="#expression-relation">Relation</a>).</p>
+
+
+<div class='grammar'>
+<span class="nonterminal">expression</span>&nbsp;::=  
+<span class="nonterminal">elementExpression</span> 
+| <span class="nonterminal">relationExpression</span> 
+<br/>
+<!-- -->
+<br/>
+<span class="nonterminal">elementExpression</span>&nbsp;::=  
+<span class="nonterminal">entityExpression</span> 
+| <span class="nonterminal">activityExpression</span> 
+| <span class="nonterminal">agentExpression</span>
+| <span class="nonterminal">noteExpression</span> <br/>
+<!-- -->
+<br/>
+<span class="nonterminal">relationExpression</span>&nbsp;::=  
+<span class="nonterminal">generationExpression</span> 
+| <span class="nonterminal">usageExpression</span> 
+| <span class="nonterminal">derivationExpression</span> 
+| <span class="nonterminal">activityAssociationExpression</span> 
+| <span class="nonterminal">responsibilityExpression</span> 
+| <span class="nonterminal">startExpression</span> 
+| <span class="nonterminal">endExpression</span> 
+| <span class="nonterminal">alternateExpression</span> 
+| <span class="nonterminal">specializationExpression</span>
+| <span class="nonterminal">annotationExpression</span> 
+</div>
+
+
+
+
 <section id="expression-element"> 
 <h3>Element</h3>
 
+<p>PROV-DM elements can be entities, activities, agents, or notes. This section defines a production for the textual representation of each of these element types. </p>
 
    <section id="expression-Entity"> 
       
@@ -341,6 +400,15 @@
 </div>
 </div>
 
+<div class="anexample">
+<pre class="codeexample">
+entity(tr:WD-prov-dm-20111215)
+entity(tr:WD-prov-dm-20111215, [ prov:type="document" ])
+entity(tr:WD-prov-dm-20111215, [ prov:type="document", ex:version=2 ])
+</pre>
+</div>
+
+
     </section> 
 
     <section id="expression-Activity"> 
@@ -367,6 +435,14 @@
 </div>
 </div>
 
+<div class="anexample">
+<pre class="codeexample">
+activity(ex:edit1,,)
+activity(ex:edit1,,,[prov:type="edit"])
+activity(ex:a0, 2011-11-16T16:00:00,,[prov:type="createFile"])
+activity(ex:a0, 2011-11-16T16:00:00,2011-11-16T16:00:01, [prov:type="createFile"])
+</pre>
+</div>
 
 
 </section> 
@@ -390,6 +466,14 @@
 </div>
 </div>
 
+<div class="anexample">
+<pre class="codeexample">
+agent(ag4)
+agent(ag4, [ prov:type="prov:Human" %% xsd:QName, ex:name="David" ])
+</pre>
+</div>
+
+
 </section>
 
    <section id="expression-note"> 
@@ -413,6 +497,12 @@
 </div>
 </div>
 
+<div class="anexample">
+<pre class="codeexample">
+note(ann1,[ex:color="blue", ex:screenX=20, ex:screenY=30])
+</pre>
+</div>
+
    </section> 
 
 </section>
@@ -421,7 +511,9 @@
 <section id="expression-relation">
 <h3>Relation</h3>
 
-<p>In PROV-ASN, relation expressions are  conformant to the <span class='nonterminal'>relationExpression</span> production of the grammar.</p>
+<p>
+PROV-DM relatiosn can be generation, usage, derivation, activity association, responsibility chain, activity start, activity end, alternate, specialization, or annotations. This section defines a production for the textual representation of each of these relation types. </p>
+
 
 
 <section id="expression-Generation">
@@ -874,6 +966,8 @@
 <div class="note">
 Has not been edited yet.
 </div>
+<p>In PROV-ASN, a record container is compliant with the production <span class="nonterminal">recordContainer</span> (see section <a href="#RecordContainer">Record Container</a>). </p>
+
 
 <p>In this section, two constructs are introduced to group
 PROV-DM records.  The first
--- a/model/working-copy/towards-wd4.html	Wed Feb 15 14:03:45 2012 +0000
+++ b/model/working-copy/towards-wd4.html	Wed Feb 15 15:21:17 2012 +0000
@@ -903,19 +903,20 @@
 to help the rendering of what it is associated with, by
 specifying its color and its position on the screen.</p>
 <pre class="codeexample">
-note(ex:n1,[ex:color="blue", ex:screenX=20, ex:screenY=30])
-hasAnnotation(tr:WD-prov-dm-20111215,ex:n1)
+note(ex2:n1,[ex2:color="blue", ex2:screenX=20, ex2:screenY=30])
+hasAnnotation(tr:WD-prov-dm-20111215,ex2:n1)
 </pre>
 <p>The note is associated with the entity <span class="name">tr:WD-prov-dm-20111215</span> previously introduced (<a title="annotation">hasAnnotation</a> is 
-discussed in Section <a href="#term-annotation">Annotation</a>).  
+discussed in Section <a href="#term-annotation">Annotation</a>).  The note's identifier and attributes are declares in a separate namespace denoted by prefix <span class="name">ex2</span>.
 </p>
 
 <p>Alternatively, a reputation service may enrich a provenance record with notes providing reputation ratings about agents. In the following fragment, both agents <span class="name">ex:Simon</span> and <span class="name">ex:Paolo</span> are rated "excellent".</p>
 <pre class="codeexample">
-note(ex:n2,[ex:reputation:"excellent"])
-hasAnnotation(ex:Simon,ex:n2)
-hasAnnotation(ex:Paolo,ex:n2)
+note(ex3:n2,[ex3:reputation:"excellent"])
+hasAnnotation(ex:Simon,ex3:n2)
+hasAnnotation(ex:Paolo,ex3:n2)
 </pre>
+<p>The note's identifier and attributes are declares in a separate namespace denoted by prefix <span class="name">ex3</span>.</p>
 
 </div>
 
@@ -928,7 +929,8 @@
 <section id="term-relation">
 <h3>Relation</h3>
 
-<p>This section describes all the PROV-DM relations between the elements introduced in <a href="#term-element">Section Element</a>. While these relations are not
+<p>
+This section describes all the PROV-DM relations between the elements introduced in <a href="#term-element">Section Element</a>. While these relations are not
 binary,  they all involve two primary elements. They can be summarized as follows. </p>