--- a/model/ProvenanceModel.html	Wed Oct 05 21:56:53 2011 -0400
+++ b/model/ProvenanceModel.html	Thu Oct 06 10:55:43 2011 +0100
@@ -121,7 +121,7 @@
 <p>
 This document defines PROV-DM, a data model for provenance, and 
 PROV-ASN, an abstract syntax, which allows
-serializations of PROV-DM instances to be created in a technology independent manner,
+serializations of PROV-DM instances to be created for human consumption and in a technology independent manner,
 which facilitates its mapping to concrete syntax, and which is used as the basis for a
 formal semantics.
 </p>
@@ -132,17 +132,62 @@
       <h2>Introduction<br>
 </h2> 
 
-<div class='note'>Introduction needs to be written. It should indicate the aims and scope of this document, and position this document in the family of documents produced by the PROV WG.
-</div>
+<p> 
+The term 'provenance' refers to the sources of information, such
+as people, entities, and processes, involved in producing,
+influencing, or delivering a piece of data or a thing in the world.
+In particular, the provenance of information is crucial in deciding
+whether information is to be trusted, how it should be integrated with
+other diverse information sources, and how to give credit to its
+originators when reusing it.  In an open and inclusive environment
+such as the Web, users find information that is often contradictory or
+questionable:  provenance can help those users to make trust judgments.
+</p>
+
+
+<p>
+The idea that a single way of representing and collecting provenance could be adopted internally by all systems does not seem to be realistic today. Instead, a pragmatic approach is to consider a core data model for provenance that allows  domain and application specific representations of provenance to be translated into such a data model and exchanged between systems.
+Heterogeneous systems can then export their provenance into such a core data model, and applications that need to make sense of provenance in heterogeneous systems can then import it, process it, and reason over it.</p>
+
+<p>A set of specifications define the various aspects
+that are necessary to achieve this vision in an inter-operable
+way:</p>
+<ul>
+<li> This document defines  the PROV-DM data model for provenance, accompanied with a notation to express instances of that data model for human consumption; </li>
+<li> A normative serialization of PROV-DM in RDF [[PROV-OWL2]], specified by means of a mapping to the OWL2 Web Ontology Language [[!OWL2-SYNTAX]];</li>
+<li> The mechanisms for accessing and querying provenance [[PROV-PAQ]].</li>
+</ul>
+
+
+<p>
+The PROV-DM data model for provenance consists of a set of core
+concepts, and a few common extensions, based on these core concepts.  PROV-DM provides extensibility points allowing further domain-specific and application specific extensions to be defined.</p>
+
+<p>This specification also introduces
+PROV-ASN, an abstract syntax that is primarily aimed at human consumption. PROV-ASN allows
+serializations of PROV-DM instances to be created in a technology independent manner,
+it facilitates its mapping to concrete syntax, and it is used as the basis for a
+formal semantics.
+</p>
+
+    <section> 
+<h3>Structure of this Document</h3>
+    </section> 
+
+
+    <section> 
+<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>
 <h2>Preliminaries</h2>
@@ -2123,6 +2168,8 @@
 
 </section>
 
+</section>
+
     <section id="extensibility-section"> 
 <h2>PROV-DM Extensibility Points</h2>