sections on PASN and representation
authorLuc Moreau <l.moreau@ecs.soton.ac.uk>
Tue, 06 Sep 2011 21:40:00 +0100
changeset 223 a2793d1ec846
parent 222 45969fa72992
child 224 8f76e41e9e58
sections on PASN and representation
model/ProvenanceModel.html
--- a/model/ProvenanceModel.html	Tue Sep 06 20:26:30 2011 +0100
+++ b/model/ProvenanceModel.html	Tue Sep 06 21:40:00 2011 +0100
@@ -15,6 +15,22 @@
     <script src="http://dev.w3.org/2009/dap/ReSpec.js/js/respec.js" class="remove"></script> 
 
     <script class="remove"> 
+      var addExtraReferences = function() {
+          for (var k in extraReferences)
+              berjon.biblio[k] = extraReferences[k];
+      };
+      var extraReferences = {
+        "PROV-SEMANTICS":
+          "James Cheney "+
+          "<a href=\"http://www.w3.org/2011/prov/wiki/FormalSemanticsStrawman\"><cite>Formal Semantics Strawman</cite></a>. "+
+          "2011, Work in progress. "+
+          "URL: <a href=\"http://www.w3.org/2011/prov/wiki/FormalSemanticsStrawman\">http://www.w3.org/2011/prov/wiki/FormalSemanticsStrawman</a>",
+        "PROV-OWL2":
+          "Satya Sahoo and Deborah McGuinness "+
+          "<a href=\"http://dvcs.w3.org/hg/prov/raw-file/default/ontology/ProvenanceFormalModel.html\"><cite>Provenance Formal Model</cite></a>. "+
+          "2011, Work in progress. "+
+          "URL: <a href=\"http://dvcs.w3.org/hg/prov/raw-file/default/ontology/ProvenanceFormalModel.html\">http://dvcs.w3.org/hg/prov/raw-file/default/ontology/ProvenanceFormalModel.html</a>",
+      };
       var respecConfig = {
           // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
           specStatus:           "ED",
@@ -80,12 +96,21 @@
           // document unless you know what you're doing. If in doubt ask your friendly neighbourhood
           // Team Contact.
           wgPatentURI:  "",
+
+          // Add extraReferences to bibliography database
+          preProcess: [addExtraReferences],
       };
     </script> 
   </head> 
   <body> 
     <section id="abstract">
-<p>This document defines a data model for Provenance.</p>
+<p>
+This document defines PIDM (placeholder name), a data model for provenance, and the
+Provenance Abstract Syntax Notation, an abstract syntax, which allows
+serializations of PIDM instances in a technology independent manner,
+facilitates its mapping to concrete syntax, and is used to provide a
+formal semantics.
+</p>
 
 <p>
 This is a document for internal discussion, which will ultimately
@@ -145,8 +170,63 @@
     <section> 
 <h2>The Provenance Abstract Syntax Notation</h2>
 
+<p>This specification defines PIDM, a data model for provenance, and relies on a language, the Provenance Abstract Syntax Notation, to express
+<em>instances</em> of that data model. </p>
+
+<p>The Provenance Abstract Syntax Notation is an abstract syntax, whose goals are:
+<ul>
+<li>to allow serializations of PIDM instances in a technology independent manner, which makes it more readable for human consumption;
+<li>to facilitate the mapping of PIDM to concrete syntax;
+<li>to provide the basis for a formal semantics.
+</ul>
+
+<p>This specification provides a grammar for the Provenance Abstract
+Syntax Notation. Each expression of the PIDM data model is explained
+in terms of the production of this grammar.</p>
+
+<div class='note'>TODO: define the BNF notation</div>
+
+
+<p>The formal semantics of PIDM is defined at
+[[PROV-SEMANTICS]] and its encoding in the OWL2 Web Ontology Language at [[PROV-OWL2]].
+</p>
+
+
     </section> 
 
+    <section> 
+<h2>Representation, Assertion, and Inference</h2>
+
+<p>
+PIDM is a provenance data model designed to express <em>representations</em> of the world. 
+These representations are relative to an asserter, and in that sense constitute assertions stating properties of the world, as represented by an asserter. Different asserters will normally contribute different representations, and no attempt is made to define a notion of consistency of such different sets of assertions. The data model provides the means to associate attribution to assertions.
+</p>
+
+<p>The data model is designed to capture events that happened in the past, as opposed to event
+that may or will happen. 
+However, this distinction is not formally enforced.
+Therefore, all PIDM assertions SHOULD be interpreted as a record of what has happened, as opposed to what may or will happen.</p>
+
+<div class='note'>Can this be enforced formally?</div>
+
+
+<p> 
+This specification does not prescribe the means by which an asserter arrives at assertions; for example, assertions can be composed on the basis of observations, reasoning, or any other means. 
+</p>
+
+
+<p>
+Sometimes, inferences about the world can be made from representations
+conformant to the PIDM data model. When this is the case, this
+specification defines such inferences. Hence, representations of the
+world can result either from direct assertions by asserters or from
+application of inferences defined by this specification.
+</p>
+
+
+
+
+</section>
 
     <section class="informative"> 
 <h2>Example</h2>