--- a/model/comments/wd6-Graham.txt	Tue May 29 09:32:12 2012 +0100
+++ b/model/comments/wd6-Graham.txt	Tue May 29 09:37:08 2012 +0100
@@ -91,12 +91,13 @@
   > follow on from entities and activities (or folded in with those).
   > More detail later in discussion of core structures.
 
-I personally would prefer to see 
+We have reorganized components as follows,
+addressing your concern that derivation follows entities and activities, 
+generation and usage.
+
   component 2: derivation
   component 3: agent/responsibility.
-
-Paul, Paolo, Put this up for vote?
-Issue: tracedTo (currently with derivation, should be moved to new component 3)
+  tracedTo (was moved to new component 3)
 
 
   > 

--- a/model/prov-dm.html	Tue May 29 09:32:12 2012 +0100
+++ b/model/prov-dm.html	Tue May 29 09:37:08 2012 +0100
@@ -1908,7 +1908,7 @@
 <p>The following descriptions are about derivations between  <span class="name">e2</span> and  <span class="name">e1</span>, but no information is provided as to the identity of the activity (and usage and generation) underpinning the derivation. In the second line, a type attribute is also provided.</p>
 <pre class="codeexample">
 wasDerivedFrom(e2, e1)
-wasDerivedFrom(e2, e1, [prov:type="physical transform"])
+wasDerivedFrom(e2, e1, [ prov:type="physical transform" ])
 </pre>
 <p>The following description expresses that activity  <span class="name">a</span>, 
 using the entity <span class="name">e1</span> according to usage <span class="name">u1</span>,