--- a/data-cube/index.html	Sun Mar 03 15:21:55 2013 +0000
+++ b/data-cube/index.html	Sun Mar 03 22:05:53 2013 +0000
@@ -269,6 +269,33 @@
 
 </section>
 
+
+<section id="conformance">
+<h2>Conformance</h2>
+
+@@TODO improve references to WF section
+
+<p>A data interchange, however that interchange occurs, is conformant
+  with Data Cube if:
+<ul>
+<li>it uses terms (classes and properties) from Data Cube in a way consistent with
+  their semantics as declared in this specification, in particular the exchanged RDF graphs constitute
+  either <em><a href="wf">well-formed</a></em> or <em><a href="wf">well-formed abbreviated</a></em> Data Cubes;</li>
+<li>it does <strong>not</strong> use terms from other vocabularies <strong>instead</strong> of ones defined
+ in this vocabulary that could reasonably be used (use of such
+ terms <strong>in addition</strong> to Data Cube terms is permissible).</li>
+</ul>
+</p>
+
+<p>A conforming data interchange:
+<ul>
+<li><em class="rfc2119" title="may">may</em> include terms from other vocabularies;</li>
+<li><em class="rfc2119" title="may">may</em> use only a subset of Data Cube terms.</li>
+</ul>
+</p>
+
+</section>
+
 <section id="data-cubes" class="informative">
 <h2>Data cubes</h2>
 
@@ -746,7 +773,7 @@
 
 <p>So the structure of our example data set (and other similar datasets) can be declared by:</p>
 
-<pre class="example">
+<pre id="attachment-example" class="example">
   eg:dsd-le a qb:DataStructureDefinition;
       # The dimensions
       qb:component [qb:dimension eg:refArea;         qb:order 1];
@@ -1429,6 +1456,38 @@
 
 </section>
 
+<section id="normalize">
+<h2>Abbreviation and normalization</h2>
+
+<p>In normal form then the observations which make up a Data Cube have property values
+for each of the required dimensions, attributes and measures as declared in the associated data structure
+definition. This form for a Data Cube is termed <em><dfn>flattened</dfn></em>. It is a convenient format
+for querying data and makes it possible to write uniform queries which extract 
+sets of observations, including from across multiple cubes. However, the verbosity of a
+fully flattened representation incurs overheads in transmission and storage of Data Cubes
+which may be problematic in some applications. 
+</p>
+
+<p>To address this the Data Cube vocabulary supports a notion of an <em><dfn>abbreviated</dfn></em> format 
+in which component properties may be <em><dfn>attached</dfn></em> to other levels in the Data Cube.
+Specifically they may be attached to 
+a <code><a>qb:DataSet</a></code>, <code><a>qb:Slice</a></code> or <code><a>qb:MeasureProperty</a></code>.
+In those cases the attached property is taken to be applied to all the <code><a>qb:Observation</a></code> 
+instances associated with that attachment point. See <a href="attachment-example">example 4</a>
+in which the unit of measure is declared as to be attached to the whole data set and need not
+be repeated for every observation.</p>
+
+@@@@@@@@
+
+<p>@@TODO</p>
+</section>
+
+<section id="wf">
+<h2>Validating well-formed cubes</h2>
+
+<p>@@TODO</p>
+</section>
+
 <section id="vocab-reference">
 <h2>Vocabulary reference</h2>