--- a/model/working-copy/towards-wd4.html	Wed Feb 08 16:55:20 2012 +0000
+++ b/model/working-copy/towards-wd4.html	Wed Feb 08 17:12:05 2012 +0000
@@ -593,14 +593,27 @@
 <figcaption>Provenance of a Tech Report (b)</figcaption>
   </figure>
 </div>
-
-
-
 </section>
 
 <section id="section-example-c"> 
 <h3>Attribution of Provenance</h3>
 
+<p>The two previous sections  provide  two different perspectives on the provenance of a technical report. By design, the PROV approach allows for the provenance of a subject to be provided by multiple sources. For users to decide whether they can place their trust in the technical report, they may want to analyse its provenance, but also determine
+who the provenance is attributed to, and when it was
+generated, etc. In other words, we need to be able to express the provenance of provenance.</p>
+
+<p>No new mechanism is required.  PROV-DM only assumes that provenance statements have been bundled up, and named. For instance, in this case, provenance statements were put in a file and exposed on the Web, respectively at <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/working-copy/examples/w3c-publication1.prov-asn">ex:prov1</a> and <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/working-copy/examples/w3c-publication3.prov-asn">ex:prov3</a>.   To express their respective provenance, these resources must be seen as entities, and all the constructs of PROV-DM are now available to characterize their provenance. In the example below, <span class="name">ex:prov1</span> is attributed to the agent <span class="name">w3:Consortium</a>, whereas <span class="name">ex:prov3</span> to <span class="name">ex:Jim</span>.
+
+<pre>
+entity(ex:prov1, [prov:type="prov:AccountEntity" %% xsd:QName ])
+wasAttributedTo(ex1:prov1,w3:Consortium)
+
+entity(ex:prov2, [prov:type="prov:AccountEntity" %% xsd:QName ])
+wasAttributedTo(ex1:prov1,ex:Jim)
+</pre>
+
+
+
 </section>
 
 </section>