Binary file model/examples/w3cpub/w3c-publication1.png has changed

Binary file model/examples/w3cpub/w3c-publication2.png has changed

Binary file model/examples/w3cpub/w3c-publication3.png has changed

--- a/model/examples/w3cpub/w3cpub.txt	Fri Jan 13 00:58:57 2012 +0000
+++ b/model/examples/w3cpub/w3cpub.txt	Fri Jan 13 08:24:52 2012 +0000
@@ -2,13 +2,13 @@
 This example describes the provenance of the prov-dm (version 2)
 document http://www.w3.org/TR/2011/WD-prov-dm-20111215
 
-Three different accounts exist
+We can envisage three different accounts at least.
 
 1. Account 1: the W3C view
 This account contains the kind of provenance records that
 W3C could keep, for auditors to check that due processes are followed.
 
-In this account, we see that
+In this account, we see that:
 - WD-prov-dm-20111215 was derived from WD-prov-dm-20111018
 - both WD-prov-dm-20111215 and WD-prov-dm-20111018 were published by the w3c agent
 - the publication activity for WD-prov-dm-20111215 used a publication request (req3)
@@ -16,51 +16,62 @@
   and a transition request (req1)
 - publications were according to the process rules (a plan).
 
+A simple visualization of Account 1 may be as follows.
+http://dvcs.w3.org/hg/prov/raw-file/default/model/examples/w3cpub/w3c-publication1.pdf
 
 
 2. Account 2: the Web master view
-This account contains the kind of provenance records that a webmaster
+This account contains the kind of provenance records that the webmaster
 could keep.
 
 In this account, we see that
 - WD-prov-dm-20111215 was derived from Overview.html in the mercurial repo
 - WD-prov-dm-20111215 is the result of copying file(s) to the remote web server
 - webmaster was involved
-- and did all this on the basis of the publication request (req3)
-- the publication activity for WD-prov-dm-20111215 used a publication request
-- the publication activity for WD-prov-dm-20111018 used another publication request
-  and a transition request
+- webmaster did all this on the basis of the publication request (req3)
+
+A simple visualization of this account may be as follows.
+http://dvcs.w3.org/hg/prov/raw-file/default/model/examples/w3cpub/w3c-publication2.pdf
 
 
 3. Account 3: the authors view.  
-  That's what each author could keep (for instance, to write in their CV).
+ That's what each author could keep (for instance, to write in their CV).
 - the document WD-prov-dm-20111215 was co-edited by a set of authors, with various roles
 
+Again, visualization could as follows.
+http://dvcs.w3.org/hg/prov/raw-file/default/model/examples/w3cpub/w3c-publication3.pdf
 
-To illustrate this example, written the three accounts in three separate asn files:
+4. We can envisage other accounts.
+- The mercurial log with all edits.
+- An account where other agents claim contribution to the document (faithfully or not)
+- etc
+
+
+
+To illustrate this example, I have written the three accounts in three separate asn files:
 
 http://dvcs.w3.org/hg/prov/raw-file/default/model/examples/w3cpub/w3c-publication1.prov-asn
 http://dvcs.w3.org/hg/prov/raw-file/default/model/examples/w3cpub/w3c-publication2.prov-asn
 http://dvcs.w3.org/hg/prov/raw-file/default/model/examples/w3cpub/w3c-publication3.prov-asn
 
-A simple visualization of these accounts may be as follows.
-http://dvcs.w3.org/hg/prov/raw-file/default/model/examples/w3cpub/w3c-publication1.pdf
-http://dvcs.w3.org/hg/prov/raw-file/default/model/examples/w3cpub/w3c-publication2.pdf
-http://dvcs.w3.org/hg/prov/raw-file/default/model/examples/w3cpub/w3c-publication3.pdf
 
 
-In this example, each WD is identified by a URI
+In this example, each WD is identified by its URI
 http://www.w3.org/TR/2011/WD-prov-dm-20111215
-http://www.w3.org/TR/2011/WD-prov-dm-20111018/
+http://www.w3.org/TR/2011/WD-prov-dm-20111018
 
-The entity records in the different accounts have different attribute
-and different values.
+
+
+The entity records in the different accounts have different attributes
+and different values. (Similarly to example of section 9 in the prov-dm document.)
 
 In account 1, the type that matters for the W3C process is that it is a Working Draft.
 entity(w3:WD-prov-dm-20111215, [ prov:type="WD" ])
 
 In account 2, the type that matters for the W3C master is that it is an html4 document.
 entity(w3:WD-prov-dm-20111215, [ prov:type="html4" ])
+Other attributes that may usefully captured include that the document
+was check to complian with pubrules, it is html4 compliant, etc
 
 In account 3, the authors know this the second version of the prov-dm report.
 Hence, the entity record has the following shape.