--- a/model/ProvenanceModel.html	Thu Oct 06 15:14:17 2011 +0100
+++ b/model/ProvenanceModel.html	Thu Oct 06 15:22:23 2011 +0100
@@ -149,6 +149,8 @@
 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>Thus, the vision is that different provenance-aware systems natively adopt their own model for representing their provenance, but a core provenance data model can be readily adopted as a provenance <em>interchange</em> model across such systems.</p>
+
 <p>A set of specifications define the various aspects
 that are necessary to achieve this vision in an inter-operable
 way:</p>
@@ -161,7 +163,7 @@
 
 <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>
+concepts, and a few common extensions, based on these core concepts.  PROV-DM is a core model, domain-agnotisc, but with well-defined 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