--- a/data-cube/index.html	Thu Mar 15 12:03:20 2012 +0000
+++ b/data-cube/index.html	Thu Mar 15 12:46:56 2012 +0000
@@ -1304,7 +1304,6 @@
 
 </section>
 
-
 <section id="namespaces-used-appendix" class="appendix">
 <h2>Namespaces used in this document</h2>
 
@@ -1735,7 +1734,79 @@
 </section>
 
 
-<section id="references">
+<section id="issues">
+<h2>Open issues</h2>
+
+<p>
+  Based on early use experiences with the vocabulary the working group is considering 
+  some clarifications and modifications to the specification. Each of
+  the candidate areas under consideration are listed as issues
+  below. Note that there is, as yet, no commitment that all (or indeed any) of these areas
+  will be addressed by the working group.
+</p>
+
+  <div class='issue'>
+    <h3><a href="http://www.w3.org/2011/gld/track/issues/29">Issue-29</a>:
+    Criteria for well-formedness</h3>
+    <p>Specify additional <em>well-formedness</em> criteria to which
+    cube-publishers should adhere to facilitate tool interoperability.</p>
+  </div>
+
+  <div class='issue'>
+    <h3><a href="http://www.w3.org/2011/gld/track/issues/30">Issue-30</a>:
+      Declaring relations between cubes</h3>
+    <p>Consider extending the vocabulary to support declaring
+      relations between data cubes (or between measures within a cube).</p>
+  </div>
+
+  <div class='issue'>
+    <h3><a href="http://www.w3.org/2011/gld/track/issues/31">Issue-31</a>:
+      Supporting aggregation for other than SKOS hierarchies</h3>
+    <p>The Data Cube vocabulary allows hierarchical code lists to be
+      used as dimensions values by means of SKOS. Consider whether to
+      extend this to support use of other hierarchical relations
+      (e.g. geo-spatial containment) without requiring mapping to SKOS.</p>
+  </div>
+
+  <div class='issue'>
+    <h3><a href="http://www.w3.org/2011/gld/track/issues/32">Issue-32</a>:
+      Relationship to ISO 19156 - Observations & Measurements</h3>
+    <p>
+      One use case for the Data Cube vocabulary is for the publication
+      of observational, sensor network and forecast data
+      sets. Existing standards for such publication include OGC
+      Observations & Measurements (ISO 19156). There are multiple ways
+      that Data Cube can be mapped to the logical model of O&M. 
+      Consider making an explicit statement of the ways in which Data
+      Cube can be related to O&M as guidance for users seeking to
+      work with both specifications.</p>
+  </div>
+
+  <div class='issue'>
+    <h3><a href="http://www.w3.org/2011/gld/track/issues/33">Issue-33</a>:
+      Collections of observations and well-formedness of slices</h3>
+    <p>
+      Experience with Data Cube has shown that publishers often wish
+      to publish slices comprising arbitrary collections of
+      observations.
+      Consider supporting this usage, either through a clarification
+      of <code>qb:Slice</code> or through an additional collection mechanism.</p>
+  </div>
+
+  <div class='issue'>
+    <h3><a href="http://www.w3.org/2011/gld/track/issues/34">Issue-34</a>:
+      Clarify or drop qb:subslice</h3>
+    <p>
+      Use of <code>qb:subslice</code> in abbreviated datasets can result
+      in ambiguity. Consider
+      clarifying or deprecating <code>qb:subslice</code>.</p>
+  </div>
+
+
+</section>
+
+
+<section id="references" class="appendix">
 <p class="todo">Bring all references into W3C style</p>
 </section>