Updating CR document ready for publication
authorDave Reynolds <dave@epimorphics.com>
Sun, 26 May 2013 12:30:32 +0100
changeset 525 66ef2afdf530
parent 524 c268814a29e9
child 526 d4e0c2501ab0
Updating CR document ready for publication
data-cube/index.html
data-cube/respec-config-cr.js
data-cube/respec-config.js
data-cube/static-cr-respec.html
data-cube/static-cr.html
data-cube/static-cr.patch
data-cube/static-diff.html
--- a/data-cube/index.html	Fri May 24 15:58:09 2013 +0100
+++ b/data-cube/index.html	Sun May 26 12:30:32 2013 +0100
@@ -46,7 +46,42 @@
 </section>
 
 <section id="sotd">
-  <p>This publication transitions <a href="http://publishing-statistical-data.googlecode.com/svn/trunk/specs/src/main/html/cube.html">previous work</a> on this subject onto the W3C Recommendation Track.</p>
+  <p>This vocabulary was originally developed and <a href="http://publishing-statistical-data.googlecode.com/svn/trunk/specs/src/main/html/cube.html">published</a> outside of W3C, but has been extended and further developed within the Government Linked Data Working Group.</p>
+
+<h4 class="no-toc no-num">Summary of changes</h4>
+
+<p>There have been no substantive changes since the Last Call version. 
+   For details on the minor changes see the <a href="#change-history">change log</a>.</p>
+
+
+<h4 class="no-toc no-num" id="please">Please Comment By 28 June 2013</h4>
+
+<p>
+  This document was published by
+  the <a href="http://www.w3.org/2011/gld/">Government Linked Data
+  Working Group</a> as a Candidate Recommendation.  <abbr title="World
+  Wide Web Consortium">W3C</abbr> publishes a Candidate Recommendation
+  to indicate that the document is believed to be stable and to
+  encourage implementation by the developer community.</p>
+
+<p> The Working
+  Group seeks to gather experience from implementations in order to
+  increase confidence in the specification and meet
+  defined <a href="http://www.w3.org/2011/gld/wiki/Data_Cube_CR_Exit_Criteria">exit
+  criteria</a>. This document will remain a Candidate Recommendation
+  until at least 28 June 2013. After that date, when and if the exit
+  criteria are met, the group intends to
+  request <a href="http://www.w3.org/2005/10/Process-20051014/tr.html#RecsPR">Proposed
+  Recommendation</a> status.</p>
+
+    <p>Please send <a href="http://www.w3.org/2011/gld/wiki/How_to_submit_a_Data_Cube_Implementation_Report">reports of implementation experience</a>, and other
+    feedback, to 
+ <a href="mailto:[email protected]">[email protected]</a> 
+          (<a href="mailto:[email protected]?subject=subscribe">subscribe</a>,
+          <a href="http://lists.w3.org/Archives/Public/public-gld-comments/">archives</a>).</p>
+
+<h4 class="no-toc no-num" id="no-endorsement">No Endorsement</h4>
+
 </section>
 
 
--- a/data-cube/respec-config-cr.js	Fri May 24 15:58:09 2013 +0100
+++ b/data-cube/respec-config-cr.js	Sun May 26 12:30:32 2013 +0100
@@ -7,7 +7,7 @@
     shortName:            "vocab-data-cube",
     //subtitle:             "",
     // if you wish the publication date to be other than today, set this
-    publishDate:  "2013-05-23",
+    publishDate:  "2013-05-30",
 
     // if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
     // and its maturity status
@@ -21,7 +21,7 @@
 
     // if this is a LCWD, uncomment and set the end of its review period
     //lcEnd: "2013-04-08",
-    crEnd: "2013-06-20",
+    crEnd: "2013-06-28",
 
     // if you want to have extra CSS, append them to this list
     // it is recommended that the respec.css stylesheet be kept
--- a/data-cube/respec-config.js	Fri May 24 15:58:09 2013 +0100
+++ b/data-cube/respec-config.js	Sun May 26 12:30:32 2013 +0100
@@ -1,18 +1,18 @@
 var respecConfig = {
     // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
-    specStatus:           "CR",
+    specStatus:           "ED",
     //copyrightStart:       "2010",
 
     // the specification's short name, as in http://www.w3.org/TR/short-name/
     shortName:            "vocab-data-cube",
     //subtitle:             "",
     // if you wish the publication date to be other than today, set this
-    publishDate:  "2013-05-23",
+    // publishDate:  "2013-03-12",
 
     // if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
     // and its maturity status
-    previousPublishDate:  "2013-03-12",
-    previousMaturity:     "LC",
+    previousPublishDate:  "2012-04-05",
+    previousMaturity:     "WD",
     //previousDiffURI:      "http://dvcs.w3.org/hg/gld/bp/",
     //diffTool:             "http://www.aptest.com/standards/htmldiff/htmldiff.pl",
 
@@ -20,8 +20,7 @@
     edDraftURI:           "https://dvcs.w3.org/hg/gld/raw-file/default/data-cube/index.html",
 
     // if this is a LCWD, uncomment and set the end of its review period
-    //lcEnd: "2013-04-08",
-    crEnd: "2013-06-20",
+    lcEnd: "2013-04-08",
 
     // if you want to have extra CSS, append them to this list
     // it is recommended that the respec.css stylesheet be kept
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/data-cube/static-cr-respec.html	Sun May 26 12:30:32 2013 +0100
@@ -0,0 +1,3366 @@
+<!DOCTYPE html>
+<html lang="en">
+<head>
+	<title>The RDF Data Cube Vocabulary</title>
+	<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+        
+<!--	<script type="text/javascript" src="respec-ref.js" class="remove"></script> -->
+	
+		
+<!--	<script type="text/javascript"  src="../respec/gld-config.js" class="remove"></script>  -->
+	 
+
+  <style type="text/css">
+.todo { background-color: #fdd; border: 1px solid #800; margin: 1em 0em; padding: 1em; page-break-inside: avoid ; font-style: italic; }
+.todo:before { content: 'TODO: '; }
+.spare-table { border-collapse: collapse; margin-left: 5ex; }
+.spare-table thead { border-bottom: black 1px solid; }
+.spare-table td { padding-left: 1em; padding-right: 1em; }
+.spare-table td + td { border-left: black 1px solid; padding-left: 1em; padding-right: 1em; }
+.spare-table th + th { border-left: black 1px solid; }
+dl.vocab_reference dt { margin-top: 1em; }
+.bordered-table { border: black 1px solid;}
+.bordered-table th { border-bottom: black 1px solid;}
+.bordered-table td { padding-right: 1em; background: #fcfaee }
+table#example-data { border: black 1px solid; border-collapse:collapse; border-spacing: 0;  }
+table#example-data td { border: black 1px solid; padding: 3px; text-align: right; }
+  </style>
+<style>/*****************************************************************
+ * ReSpec 3 CSS
+ * Robin Berjon - http://berjon.com/
+ *****************************************************************/
+
+/* --- INLINES --- */
+em.rfc2119 { 
+    text-transform:     lowercase;
+    font-variant:       small-caps;
+    font-style:         normal;
+    color:              #900;
+}
+
+h1 acronym, h2 acronym, h3 acronym, h4 acronym, h5 acronym, h6 acronym, a acronym,
+h1 abbr, h2 abbr, h3 abbr, h4 abbr, h5 abbr, h6 abbr, a abbr {
+    border: none;
+}
+
+dfn {
+    font-weight:    bold;
+}
+
+a.internalDFN {
+    color:  inherit;
+    border-bottom:  1px solid #99c;
+    text-decoration:    none;
+}
+
+a.externalDFN {
+    color:  inherit;
+    border-bottom:  1px dotted #ccc;
+    text-decoration:    none;
+}
+
+a.bibref {
+    text-decoration:    none;
+}
+
+cite .bibref {
+    font-style: normal;
+}
+
+code {
+    color:  #ff4500;
+}
+
+
+/* --- --- */
+ol.algorithm { counter-reset:numsection; list-style-type: none; }
+ol.algorithm li { margin: 0.5em 0; }
+ol.algorithm li:before { font-weight: bold; counter-increment: numsection; content: counters(numsection, ".") ") "; }
+
+/* --- TOC --- */
+.toc a, .tof a {
+    text-decoration:    none;
+}
+
+a .secno, a .figno {
+    color:  #000;
+}
+
+ul.tof, ol.tof {
+    list-style: none outside none;
+}
+
+.caption {
+    margin-top: 0.5em;
+    font-style:   italic;
+}
+
+/* --- TABLE --- */
+table.simple {
+    border-spacing: 0;
+    border-collapse:    collapse;
+    border-bottom:  3px solid #005a9c;
+}
+
+.simple th {
+    background: #005a9c;
+    color:  #fff;
+    padding:    3px 5px;
+    text-align: left;
+}
+
+.simple th[scope="row"] {
+    background: inherit;
+    color:  inherit;
+    border-top: 1px solid #ddd;
+}
+
+.simple td {
+    padding:    3px 10px;
+    border-top: 1px solid #ddd;
+}
+
+.simple tr:nth-child(even) {
+    background: #f0f6ff;
+}
+
+/* --- DL --- */
+.section dd > p:first-child {
+    margin-top: 0;
+}
+
+.section dd > p:last-child {
+    margin-bottom: 0;
+}
+
+.section dd {
+    margin-bottom:  1em;
+}
+
+.section dl.attrs dd, .section dl.eldef dd {
+    margin-bottom:  0;
+}
+</style><style>/* --- EXAMPLES --- */
+div.example-title {
+    min-width: 7.5em;
+    color: #b9ab2d;
+}
+div.example-title span {
+    text-transform: uppercase;   
+}
+aside.example, div.example, div.illegal-example {
+    padding: 0.5em;
+    margin: 1em 0;
+    position: relative;
+    clear: both;
+}
+div.illegal-example { color: red }
+div.illegal-example p { color: black }
+aside.example, div.example {
+    padding: .5em;
+    border-left-width: .5em;
+    border-left-style: solid;
+    border-color: #e0cb52;
+    background: #fcfaee;    
+}
+
+aside.example div.example {
+    border-left-width: .1em;
+    border-color: #999;
+    background: #fff;
+}
+aside.example div.example div.example-title {
+    color: #999;
+}
+</style><style>/* --- ISSUES/NOTES --- */
+div.issue-title, div.note-title {
+    padding-right:  1em;
+    min-width: 7.5em;
+    color: #b9ab2d;
+}
+div.issue-title { color: #e05252; }
+div.note-title { color: #52e052; }
+div.issue-title span, div.note-title span {
+    text-transform: uppercase;
+}
+div.note, div.issue {
+    margin-top: 1em;
+    margin-bottom: 1em;
+}
+.note > p:first-child, .issue > p:first-child { margin-top: 0 }
+.issue, .note {
+    padding: .5em;
+    border-left-width: .5em;
+    border-left-style: solid;
+}
+div.issue, div.note {
+    padding: 0.5em;
+    margin: 1em 0;
+    position: relative;
+    clear: both;
+}
+span.note, span.issue { padding: .1em .5em .15em; }
+
+.issue {
+    border-color: #e05252;
+    background: #fbe9e9;
+}
+.note {
+    border-color: #52e052;
+    background: #e9fbe9;
+}
+
+
+</style><link rel="stylesheet" href="http://www.w3.org/StyleSheets/TR/W3C-CR"><!--[if lt IE 9]><script src='http://www.w3.org/2008/site/js/html5shiv.js'></script><![endif]--></head>
+
+<body><div class="head">
+  <p>
+    
+      <a href="http://www.w3.org/"><img width="72" height="48" src="http://www.w3.org/Icons/w3c_home" alt="W3C"></a>
+    
+  </p>
+  <h1 class="title" id="title">The RDF Data Cube Vocabulary</h1>
+  
+  <h2 id="w3c-candidate-recommendation-30-may-2013"><abbr title="World
+  Wide Web Consortium">W3C</abbr> Candidate Recommendation 30 May 2013</h2>
+  <dl>
+    
+      <dt>This version:</dt>
+      <dd><a href="http://www.w3.org/TR/2013/CR-vocab-data-cube-20130530/">http://www.w3.org/TR/2013/CR-vocab-data-cube-20130530/</a></dd>
+      <dt>Latest published version:</dt>
+      <dd><a href="http://www.w3.org/TR/vocab-data-cube/">http://www.w3.org/TR/vocab-data-cube/</a></dd>
+    
+    
+      <dt>Latest editor's draft:</dt>
+      <dd><a href="https://dvcs.w3.org/hg/gld/raw-file/default/data-cube/index.html">https://dvcs.w3.org/hg/gld/raw-file/default/data-cube/index.html</a></dd>
+    
+    
+    
+    
+    
+      <dt>Previous version:</dt>
+      <dd><a href="http://www.w3.org/TR/2013/WD-vocab-data-cube-20130312/">http://www.w3.org/TR/2013/WD-vocab-data-cube-20130312/</a></dd>
+    
+    
+    <dt>Editors:</dt>
+    <dd><a href="http://richard.cyganiak.de/">Richard Cyganiak</a>, <a href="http://www.deri.ie/">DERI, NUI Galway</a></dd>
+<dd><span>Dave Reynolds</span>, <a href="http://www.epimorphics.com/">Epimorphics Ltd</a></dd>
+
+    
+  <dt>Contributor:</dt> <dd><a href="http://www.jenitennison.com/">Jeni Tennison</a></dd></dl>
+  
+  
+  
+  
+    
+      <p class="copyright">
+        <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 
+        2013
+        
+        <a href="http://www.w3.org/"><abbr title="World Wide Web Consortium">W3C</abbr></a><sup>®</sup> 
+        (<a href="http://www.csail.mit.edu/"><abbr title="Massachusetts Institute of Technology">MIT</abbr></a>,
+        <a href="http://www.ercim.eu/"><abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr></a>,
+        <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved.
+        <abbr title="World
+  Wide Web Consortium">W3C</abbr> <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>,
+        <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and
+        <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.
+      </p>
+    
+  
+  <hr>
+</div>
+
+<section id="abstract" class="introductory"><h2>Abstract</h2>
+<p>There are many situations where it would be useful to be able to
+publish
+multi-dimensional data, such as statistics, on the web in such a way
+that it can be linked to related data sets and concepts. The Data Cube
+vocabulary provides a means to do this using the <abbr title="World
+  Wide Web Consortium">W3C</abbr> <a href="http://www.w3.org/TR/REC-rdf-syntax/">RDF</a>
+(Resource Description Framework) standard. The model underpinning the
+Data Cube vocabulary is
+compatible with the cube model that underlies <a href="http://sdmx.org">SDMX</a> (Statistical Data
+and Metadata eXchange), an ISO standard for exchanging and sharing
+statistical data and metadata among organizations. The Data Cube
+vocabulary is a core foundation which supports extension
+vocabularies to enable publication of other aspects of
+statistical data flows or other multi-dimensional data sets.</p>
+</section><section id="sotd" class="introductory"><h2>Status of This Document</h2>
+  
+    
+      
+        <p>
+          <em>This section describes the status of this document at the time of its publication. Other
+          documents may supersede this document. A list of current <abbr title="World
+  Wide Web Consortium">W3C</abbr> publications and the latest revision
+          of this technical report can be found in the <a href="http://www.w3.org/TR/"><abbr title="World
+  Wide Web Consortium">W3C</abbr> technical reports
+          index</a> at http://www.w3.org/TR/.</em>
+        </p>
+        
+  <p>This vocabulary was originally developed and <a href="http://publishing-statistical-data.googlecode.com/svn/trunk/specs/src/main/html/cube.html">published</a> outside of <abbr title="World
+  Wide Web Consortium">W3C</abbr>, but has been extended and further developed within the Government Linked Data Working Group.</p>
+
+<h4 class="no-toc no-num" id="summary-of-changes">Summary of changes</h4>
+
+<p>There have been no substantive changes since the Last Call version. 
+   For details on the minor changes see the <a href="#change-history">change log</a>.</p>
+
+
+<h4 class="no-toc no-num" id="please">Please Comment By 28 June 2013</h4>
+
+<p>
+  This document was published by
+  the <a href="http://www.w3.org/2011/gld/">Government Linked Data
+  Working Group</a> as a Candidate Recommendation.  <abbr title="World
+  Wide Web Consortium">W3C</abbr> publishes a Candidate Recommendation
+  to indicate that the document is believed to be stable and to
+  encourage implementation by the developer community.</p>
+
+<p> The Working
+  Group seeks to gather experience from implementations in order to
+  increase confidence in the specification and meet
+  defined <a href="http://www.w3.org/2011/gld/wiki/Data_Cube_CR_Exit_Criteria">exit
+  criteria</a>. This document will remain a Candidate Recommendation
+  until at least 28 June 2013. After that date, when and if the exit
+  criteria are met, the group intends to
+  request <a href="http://www.w3.org/2005/10/Process-20051014/tr.html#RecsPR">Proposed
+  Recommendation</a> status.</p>
+
+    <p>Please send <a href="http://www.w3.org/2011/gld/wiki/How_to_submit_a_Data_Cube_Implementation_Report">reports of implementation experience</a>, and other
+    feedback, to 
+ <a href="mailto:[email protected]">[email protected]</a> 
+          (<a href="mailto:[email protected]?subject=subscribe">subscribe</a>,
+          <a href="http://lists.w3.org/Archives/Public/public-gld-comments/">archives</a>).</p>
+
+<h4 class="no-toc no-num" id="no-endorsement">No Endorsement</h4>
+
+
+        <p>
+          This document was published by the <a href="http://www.w3.org/2011/gld/">Government Linked Data Working Group</a> as a Candidate Recommendation.
+          
+            This document is intended to become a <abbr title="World
+  Wide Web Consortium">W3C</abbr> Recommendation.
+          
+          
+          If you wish to make comments regarding this document, please send them to 
+          <a href="mailto:[email protected]">[email protected]</a> 
+          (<a href="mailto:[email protected]?subject=subscribe">subscribe</a>,
+          <a href="http://lists.w3.org/Archives/Public/public-gld-comments/">archives</a>).
+          
+          
+          
+            <abbr title="World
+  Wide Web Consortium">W3C</abbr> publishes a Candidate Recommendation to indicate that the document is believed
+            to be stable and to encourage implementation by the developer community. This
+            Candidate Recommendation is expected to advance to Proposed Recommendation no earlier than
+            28 June 2013.
+          
+          
+        All comments are welcome.
+        
+        
+          </p><p>
+            Publication as a Candidate Recommendation does not imply endorsement by the <abbr title="World
+  Wide Web Consortium">W3C</abbr> Membership.
+            This is a draft document and may be updated, replaced or obsoleted by other documents at 
+            any time. It is inappropriate to cite this document as other than work in progress.
+          </p>
+        
+        
+        <p>
+          
+            This document was produced by a group operating under the 
+            <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 <abbr title="World
+  Wide Web Consortium">W3C</abbr> Patent Policy</a>.
+          
+          
+          
+            
+              <abbr title="World
+  Wide Web Consortium">W3C</abbr> maintains a <a href="http://www.w3.org/2004/01/pp-impl/47663/status" rel="disclosure">public list of any patent disclosures</a> 
+            
+            made in connection with the deliverables of the group; that page also includes instructions for 
+            disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains
+            <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential Claim(s)</a> must disclose the
+            information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section
+            6 of the <abbr title="World
+  Wide Web Consortium">W3C</abbr> Patent Policy</a>.
+          
+          
+        </p>
+        
+      
+    
+  
+</section><section id="toc"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a href="#outline" class="tocxref"><span class="secno">1. </span>Outline of the vocabulary</a><ul class="toc"><li class="tocline"><a href="#index" class="tocxref"><span class="secno">1.1 </span>Vocabulary index</a></li></ul></li><li class="tocline"><a href="#introduction" class="tocxref"><span class="secno">2. </span>Introduction</a><ul class="toc"><li class="tocline"><a href="#intro-rdf" class="tocxref"><span class="secno">2.1 </span>RDF and Linked Data</a></li><li class="tocline"><a href="#intro-sdmx" class="tocxref"><span class="secno">2.2 </span>SDMX and related standards</a></li><li class="tocline"><a href="#intro-audience" class="tocxref"><span class="secno">2.3 </span>Audience and scope</a></li></ul></li><li class="tocline"><a href="#namespaces" class="tocxref"><span class="secno">3. </span>Namespaces and Document Conventions</a></li><li class="tocline"><a href="#conformance" class="tocxref"><span class="secno">4. </span>Conformance</a></li><li class="tocline"><a href="#data-cubes" class="tocxref"><span class="secno">5. </span>Data cubes</a><ul class="toc"><li class="tocline"><a href="#cubes-model-datasets" class="tocxref"><span class="secno">5.1 </span>Data Sets</a></li><li class="tocline"><a href="#cubes-model" class="tocxref"><span class="secno">5.2 </span>The cube model - dimensions, attributes, measures</a></li><li class="tocline"><a href="#cubes-slices" class="tocxref"><span class="secno">5.3 </span>Introducing Slices</a></li><li class="tocline"><a href="#example" class="tocxref"><span class="secno">5.4 </span>An example</a></li></ul></li><li class="tocline"><a href="#dsd" class="tocxref"><span class="secno">6. </span>Creating data structure definitions</a><ul class="toc"><li class="tocline"><a href="#dsd-dimensions" class="tocxref"><span class="secno">6.1 </span>Dimensions, attributes and measures</a></li><li class="tocline"><a href="#dsd-cog" class="tocxref"><span class="secno">6.2 </span>Content oriented guidelines</a></li><li class="tocline"><a href="#dsd-example" class="tocxref"><span class="secno">6.3 </span>Example dimensions and measure</a></li><li class="tocline"><a href="#dsd-dsd" class="tocxref"><span class="secno">6.4 </span>ComponentSpecifications and DataStructureDefinitions</a></li><li class="tocline"><a href="#dsd-mm" class="tocxref"><span class="secno">6.5 </span>Handling multiple measures</a><ul class="toc"><li class="tocline"><a href="#dsd-mm-obs" class="tocxref"><span class="secno">6.5.1 </span>Multi-measure observations</a></li><li class="tocline"><a href="#dsd-mm-dim" class="tocxref"><span class="secno">6.5.2 </span><span>Measure dimension</span></a></li></ul></li></ul></li><li class="tocline"><a href="#datasets" class="tocxref"><span class="secno">7. </span>Expressing data sets</a><ul class="toc"><li class="tocline"><a href="#dataset-basic" class="tocxref"><span class="secno">7.1 </span>Data sets and observations</a></li><li class="tocline"><a href="#slices" class="tocxref"><span class="secno">7.2 </span>Slices and groups of observations</a></li></ul></li><li class="tocline"><a href="#schemes" class="tocxref"><span class="secno">8. </span>Concept schemes and code lists</a><ul class="toc"><li class="tocline"><a href="#schemes-intro" class="tocxref"><span class="secno">8.1 </span>Coded values for components properties</a></li><li class="tocline"><a href="#schemes-hierarchy" class="tocxref"><span class="secno">8.2 </span>Hierarchical code lists</a></li><li class="tocline"><a href="#schemes-hierarchy-nonskos" class="tocxref"><span class="secno">8.3 </span>Non-SKOS hierarchies</a></li><li class="tocline"><a href="#schemes-aggregation" class="tocxref"><span class="secno">8.4 </span>Aggregation</a></li></ul></li><li class="tocline"><a href="#metadata" class="tocxref"><span class="secno">9. </span>DataSet metadata</a><ul class="toc"><li class="tocline"><a href="#metadata-categorization" class="tocxref"><span class="secno">9.1 </span>Categorizing a data set</a></li><li class="tocline"><a href="#metadata-publishers" class="tocxref"><span class="secno">9.2 </span>Describing publishers</a></li></ul></li><li class="tocline"><a href="#normalize" class="tocxref"><span class="secno">10. </span>Abbreviated and normalized data cubes</a><ul class="toc"><li class="tocline"><a href="#normalize-algorithm" class="tocxref"><span class="secno">10.1 </span>Normalization algorithm</a></li></ul></li><li class="tocline"><a href="#wf" class="tocxref"><span class="secno">11. </span>Well-formed cubes</a><ul class="toc"><li class="tocline"><a href="#wf-rules" class="tocxref"><span class="secno">11.1 </span>Integrity constraints</a></li></ul></li><li class="tocline"><a href="#vocab-reference" class="tocxref"><span class="secno">12. </span>Vocabulary reference</a><ul class="toc"><li class="tocline"><a href="#reference-datasets" class="tocxref"><span class="secno">12.1 </span>DataSets</a></li><li class="tocline"><a href="#reference-observations" class="tocxref"><span class="secno">12.2 </span>Observations</a></li><li class="tocline"><a href="#reference-slices" class="tocxref"><span class="secno">12.3 </span>Slices</a></li><li class="tocline"><a href="#reference-components" class="tocxref"><span class="secno">12.4 </span>Dimensions, Attributes, Measures</a></li><li class="tocline"><a href="#reference-component-properties" class="tocxref"><span class="secno">12.5 </span>Reusable general purpose component properties</a></li><li class="tocline"><a href="#reference-dsd" class="tocxref"><span class="secno">12.6 </span>Data Structure Definitions</a></li><li class="tocline"><a href="#reference-compspec" class="tocxref"><span class="secno">12.7 </span>Component specifications - for qualifying component use in a DSD</a></li><li class="tocline"><a href="#reference-slice-definitions" class="tocxref"><span class="secno">12.8 </span>Slice definitions</a></li><li class="tocline"><a href="#reference-concepts" class="tocxref"><span class="secno">12.9 </span>Concepts</a></li><li class="tocline"><a href="#reference-nonskos-hierarchy" class="tocxref"><span class="secno">12.10 </span>Non-SKOS Hierarchies</a></li></ul></li><li class="tocline"><a href="#acknowledgements" class="tocxref"><span class="secno">A. </span>Acknowledgements</a></li><li class="tocline"><a href="#change-history" class="tocxref"><span class="secno">B. </span>Change history </a></li><li class="tocline"><a href="#full-example" class="tocxref"><span class="secno">C. </span>Complete example Data Cube</a></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">D. </span>References</a><ul class="toc"><li class="tocline"><a href="#normative-references" class="tocxref"><span class="secno">D.1 </span>Normative references</a></li><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">D.2 </span>Informative references</a></li></ul></li></ul></section>
+
+
+
+
+<section id="outline">
+<!--OddPage--><h2><span class="secno">1. </span>Outline of the vocabulary</h2>
+
+<figure id="fig-pictorial-summary-of-key-terms-and-their-relationship">
+  <img src="images/qb-fig1.png" alt="UML-style block diagram of the terms in this vocabulary">
+  <figcaption>Fig. <span class="figno">1</span> <span class="fig-title">Pictorial summary of key terms and their relationship</span></figcaption>
+</figure>
+
+
+<section id="index">
+<h3><span class="secno">1.1 </span>Vocabulary index</h3>
+
+  <p><b>Classes:</b>
+    <a href="#ref_qb_Attachable">qb:Attachable</a>
+    <a href="#ref_qb_AttributeProperty">qb:AttributeProperty</a>
+    <a href="#ref_qb_CodedProperty">qb:CodedProperty</a>
+    <a href="#ref_qb_ComponentProperty">qb:ComponentProperty</a>
+    <a href="#ref_qb_ComponentSet">qb:ComponentSet</a>
+    <a href="#ref_qb_ComponentSpecification">qb:ComponentSpecification</a>
+    <a href="#ref_qb_DataSet">qb:DataSet</a>
+    <a href="#ref_qb_DataStructureDefinition">qb:DataStructureDefinition</a>
+    <a href="#ref_qb_DimensionProperty">qb:DimensionProperty</a>
+    <a href="#ref_qb_HierarchicalCodeList">qb:HierarchicalCodeList</a>
+    <a href="#ref_qb_MeasureProperty">qb:MeasureProperty</a>
+    <a href="#ref_qb_Observation">qb:Observation</a>
+    <a href="#ref_qb_Slice">qb:Slice</a>
+    <a href="#ref_qb_ObservationGroup">qb:ObservationGroup</a>
+    <a href="#ref_qb_SliceKey">qb:SliceKey</a>
+  </p>
+  <p><b>Properties:</b>
+    <a href="#ref_qb_attribute">qb:attribute</a>
+    <a href="#ref_qb_codeList">qb:codeList</a>
+    <a href="#ref_qb_component">qb:component</a>
+    <a href="#ref_qb_componentAttachment">qb:componentAttachment</a>
+    <a href="#ref_qb_componentProperty_LC">qb:componentProperty</a>
+    <a href="#ref_qb_componentRequired">qb:componentRequired</a>
+    <a href="#ref_qb_concept">qb:concept</a>
+    <a href="#ref_qb_dataSet_LC">qb:dataSet</a>
+    <a href="#ref_qb_dimension">qb:dimension</a>
+    <a href="#ref_qb_hierarchyRoot">qb:hierarchyRoot</a>
+    <a href="#ref_qb_measure">qb:measure</a>
+    <a href="#ref_qb_measureDimension">qb:measureDimension</a>
+    <a href="#ref_qb_measureType">qb:measureType</a>
+    <a href="#ref_qb_observation_LC">qb:observation</a>
+    <a href="#ref_qb_observationGroup">qb:observationGroup</a>
+    <a href="#ref_qb_order">qb:order</a>
+    <a href="#ref_qb_parentChildProperty">qb:parentChildProperty</a>
+    <a href="#ref_qb_slice_LC">qb:slice</a>
+    <a href="#ref_qb_sliceKey_LC">qb:sliceKey</a>
+    <a href="#ref_qb_sliceStructure">qb:sliceStructure</a>
+    <a href="#ref_qb_structure">qb:structure</a>
+  </p>
+</section>
+
+</section>
+
+<section id="introduction" class="informative">
+<!--OddPage--><h2><span class="secno">2. </span>Introduction</h2><p><em>This section is non-normative.</em></p>
+
+<p>
+Statistical data is a foundation for policy
+prediction, planning and adjustments and
+underpins many of the mash-ups and visualisations
+we see on the web. There is strong interest
+in being able to publish statistical data in a web-friendly format
+to enable it to be linked and combined with related information.
+</p>
+
+<p>
+At the heart of a statistical dataset is a set of observed values
+organized along a group of dimensions, together with associated metadata.
+The Data Cube vocabulary enables such information to be represented
+using the <abbr title="World
+  Wide Web Consortium">W3C</abbr> <a href="http://www.w3.org/TR/REC-rdf-syntax/">RDF</a>
+(Resource Description Framework) standard and published following the
+principles of
+<a href="http://linkeddata.org/">linked data</a>.
+The vocabulary is based upon the approach used by the SDMX ISO standard
+for statistical data exchange. This <em>cube</em> model is very
+general and so the Data Cube vocabulary can be used for other data sets
+such as survey data, spreadsheets and OLAP data cubes [<cite><a class="bibref" href="#bib-OLAP">OLAP</a></cite>].
+</p>
+
+<p>
+The Data Cube vocabulary is focused purely on the
+publication of multi-dimensional data on the web. We envisage a series of modular
+vocabularies being developed which extend this core foundation. In
+particular, we see the need for an SDMX extension vocabulary to support the
+publication of additional context to statistical data (such as the encompassing Data
+Flows and associated Provision Agreements). Other extensions are possible to
+support metadata for surveys (so called "micro-data", as encompassed by <a href="http://www.ddialliance.org/">DDI</a>)
+or publication of statistical reference metadata.
+</p>
+
+<p>The Data Cube in turn builds upon the following existing RDF
+vocabularies:</p>
+<ul>
+  <li><a href="http://www.w3.org/2004/02/skos/">SKOS</a> for concept schemes</li>
+  <li><a href="http://sw.joanneum.at/scovo/schema.html">SCOVO</a> for
+core statistical structures</li>
+  <li><a href="http://purl.org/dc/terms/">Dublin Core Terms</a> for metadata</li>
+  <li><a href="http://rdfs.org/ns/void-guide">VoiD</a> for data access</li>
+  <li><a href="http://xmlns.com/foaf/0.1/">FOAF</a> for agents</li>
+  <li><a href="http://www.w3.org/ns/org#">ORG</a> for organizations</li>
+</ul>
+
+
+<section id="intro-rdf">
+<h3><span class="secno">2.1 </span>RDF and Linked Data</h3><p><em>This section is non-normative.</em></p>
+
+<p><em>Linked data</em> is an approach to publishing data on the web, enabling
+datasets to be linked together through references to common concepts.
+  The approach [<cite><a class="bibref" href="#bib-LOD">LOD</a></cite>]
+recommends use of HTTP URIs to name the entities and concepts so that consumers of
+the data can look-up those URIs to get more information, including links
+to other related URIs.
+RDF [<cite><a class="bibref" href="#bib-RDF-PRIMER">RDF-PRIMER</a></cite>]
+provides a standard for the representation of the
+information that describes those entities and concepts, and is returned
+by dereferencing the URIs. </p>
+
+<p>There are a number of benefits to being able to publish multi-dimensional data, such as statistics,
+using RDF and the linked data approach:</p>
+<ul>
+  <li>The individual observations, and groups of observations, become
+(web) addressable. This allows publishers and third parties to annotate
+and link to this data; for example a report can reference the specific
+figures it is based on allowing for fine grained provenance trace-back.</li>
+  <li>Data can be flexibly combined across datasets sets (for example <em>find all
+Religious schools in census areas with high values for National
+Indicators pertaining to religious tolerance</em>). The statistical
+data becomes an integral part of the broader web of linked data.</li>
+  <li>For publishers who currently only offer static files then
+publishing as linked-data offers a flexible, non-proprietary, machine
+readable means of publication that supports an out-of-the-box web API
+for programmatic access.</li>
+  <li>It enables reuse of standardized tools and components.</li>
+</ul>
+</section>
+
+
+<section id="intro-sdmx">
+<h3><span class="secno">2.2 </span>SDMX and related standards</h3>
+
+<p>The Statistical Data and Metadata Exchange (SDMX) Initiative
+was organised in 2001 by seven international organizations (BIS,
+ECB, Eurostat, IMF, OECD, World Bank and the UN) to
+realise greater efficiencies in statistical practice. These
+organisations all
+collect significant amounts of data, mostly from the national level,
+to support policy. They also disseminate data at the supra-national
+and international levels.</p>
+
+<p>
+There have been a number of important results from this work: two
+versions of a set of technical specifications - ISO:TS 17369
+(SDMX) - and the release of several recommendations for
+structuring and harmonising cross-domain statistics, the SDMX
+Content-Oriented Guidelines. All of the products are available at
+<a href="http://www.sdmx.org">www.sdmx.org</a>. The standards are now
+being widely adopted
+around the world for the collection, exchange, processing, and
+dissemination of aggregate statistics by official statistical
+organisations. The UN Statistical Commission recommended
+SDMX as the preferred standard for statistics in 2007.
+</p>
+
+<p>The SDMX specification defines a core <em>information model</em>
+which is reflected in concrete form in two syntaxes - SDMX-ML (an XML
+syntax) and SDMX-EDI.
+</p>
+
+<p>The RDF Data Cube vocabulary builds upon the core of the
+  the SDMX 2.0 Information Model [<cite><a class="bibref" href="#bib-SDMX20">SDMX20</a></cite>].</p>
+
+<p>Readers may find the SDMX User Guide [<cite><a class="bibref" href="#bib-SDMX-GUIDE">SDMX-GUIDE</a></cite>] useful
+  background.</p>
+
+<p>A key component of the SDMX standards package are
+the <strong>Content-Oriented Guidelines</strong> (COGs), a set of
+cross-domain concepts, code lists, and categories that support
+interoperability and comparability between datasets by providing a
+shared terminology between SDMX implementers [<cite><a class="bibref" href="#bib-COG">COG</a></cite>]. RDF versions of these
+terms are available separately for use along with the Data Cube
+vocabulary, see <a href="#dsd-cog">Content oriented guidelines</a> for
+  further details. These external resources do not form a normative part of the
+  Data Cube Vocabulary specification.
+</p>
+</section>
+
+
+<section id="intro-audience">
+<h3><span class="secno">2.3 </span>Audience and scope</h3>
+
+<p>This document describes the Data Cube vocabulary
+It is aimed at people wishing to publish
+statistical or other multi-dimension data in RDF.
+Mechanics of cross-format translation from other
+formats such as SDMX-ML are not covered here.</p>
+</section>
+
+</section>
+
+<section id="namespaces">
+<!--OddPage--><h2><span class="secno">3. </span>Namespaces and Document Conventions</h2>
+
+<p>
+The names of RDF entities -- classes, predicates, individuals -- are
+URIs. These are usually expressed using a compact notation where the
+name is written <code>prefix:localname</code>, and where the <code>prefix</code>
+identifies a <i>namespace URI</i>. The namespace identified by the prefix is 
+ prepended to the <code>localname</code> to obtain the full URI.
+</p>
+
+<p>The following namespaces are used in this document:</p>
+
+<table>
+  <thead><tr><th>Prefix</th><th>Namespace</th><th>Reference</th></tr></thead>
+  <tbody>
+    <tr><td>qb</td><td><a href="http://purl.org/linked-data/cube#">http://purl.org/linked-data/cube#</a></td><td><em>This document</em></td></tr>
+    <tr><td>skos</td><td><a href="http://www.w3.org/2004/02/skos/core">http://www.w3.org/2004/02/skos/core#</a></td><td>[<cite><a class="bibref" href="#bib-SKOS-REFERENCE">SKOS-REFERENCE</a></cite>]</td></tr>
+    <tr><td>scovo</td><td><a href="http://purl.org/NET/scovo#">http://purl.org/NET/scovo#</a></td><td>[<cite><a class="bibref" href="#bib-SCOVO">SCOVO</a></cite>]</td></tr>
+    <tr><td>void</td><td><a href="http://rdfs.org/ns/void#">http://rdfs.org/ns/void#</a></td><td>[<cite><a class="bibref" href="#bib-VOID">VOID</a></cite>]</td></tr>
+    <tr><td>foaf</td><td><a href="http://xmlns.com/foaf/0.1/">http://xmlns.com/foaf/0.1/</a></td><td>[<cite><a class="bibref" href="#bib-FOAF">FOAF</a></cite>]</td></tr>
+    <tr><td>org</td><td><a href="http://www.w3.org/ns/org#">http://www.w3.org/ns/org#</a></td><td>[<cite><a class="bibref" href="#bib-ORG">ORG</a></cite>]</td></tr>
+    <tr><td>dct</td><td><a href="http://purl.org/dc/terms/">http://purl.org/dc/terms/</a></td><td>[<cite><a class="bibref" href="#bib-DC11">DC11</a></cite>]</td></tr>
+    <tr><td>owl</td><td><a href="http://www.w3.org/2002/07/owl">http://www.w3.org/2002/07/owl#</a></td><td>[<cite><a class="bibref" href="#bib-OWL2-PRIMER">OWL2-PRIMER</a></cite>]</td></tr>
+    <tr><td>rdf</td><td><a href="http://www.w3.org/1999/02/22-rdf-syntax-ns">http://www.w3.org/1999/02/22-rdf-syntax-ns#</a></td><td>[<cite><a class="bibref" href="#bib-RDF-CONCEPTS">RDF-CONCEPTS</a></cite>]</td></tr>
+    <tr><td>rdfs</td><td><a href="http://www.w3.org/2000/01/rdf-schema">http://www.w3.org/2000/01/rdf-schema#</a></td><td>[<cite><a class="bibref" href="#bib-RDF-SCHEMA">RDF-SCHEMA</a></cite>]</td></tr>
+    <tr><td>admingeo</td><td><a href="http://data.ordnancesurvey.co.uk/ontology/admingeo/">http://data.ordnancesurvey.co.uk/ontology/admingeo/</a></td><td><em>(Non-normative, used for examples only)</em></td></tr>
+    <tr><td>interval</td><td><a href="http://reference.data.gov.uk/def/intervals/">http://reference.data.gov.uk/def/intervals/</a></td><td><em>(Non-normative, used for examples only)</em></td></tr>
+
+    <tr><td>eg</td><td><a href="http://example.org/ns#">http://example.org/ns#</a></td><td><em>(Non-normative, used for examples only)</em></td></tr>
+  </tbody>
+</table>
+	
+<p>All RDF examples are written in Turtle syntax [<cite><a class="bibref" href="#bib-TURTLE-TR">TURTLE-TR</a></cite>].</p>
+
+</section>
+
+
+<section id="conformance"><!--OddPage--><h2><span class="secno">4. </span>Conformance</h2>
+<p>
+  As well as sections marked as non-normative, all authoring guidelines, diagrams, examples,
+  and notes in this specification are non-normative. Everything else in this specification is
+  normative.
+</p>
+<p>
+  The key words <em class="rfc2119" title="must">must</em>, <em class="rfc2119" title="must not">must not</em>, <em class="rfc2119" title="required">required</em>, <em class="rfc2119" title="should">should</em>, <em class="rfc2119" title="should not">should not</em>, <em class="rfc2119" title="recommended">recommended</em>, <em class="rfc2119" title="may">may</em>,
+  and <em class="rfc2119" title="optional">optional</em> in this specification are to be interpreted as described in [<cite><a class="bibref" href="#bib-RFC2119">RFC2119</a></cite>].
+</p>
+
+
+<p>A data interchange, however that interchange occurs, is conformant
+  with Data Cube if:
+</p><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="#dfn-well-formed" class="internalDFN">well-formed</a></em> or <em><a href="#dfn-well-formed-abbreviated" class="internalDFN">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>
+
+<p>A conforming data interchange:
+</p><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></p>
+
+</section>
+
+<section id="data-cubes" class="informative">
+<!--OddPage--><h2><span class="secno">5. </span>Data cubes</h2><p><em>This section is non-normative.</em></p>
+
+<section id="cubes-model-datasets" class="informative">
+<h3><span class="secno">5.1 </span>Data Sets</h3><p><em>This section is non-normative.</em></p>
+
+<p>A DataSet is a collection of statistical data that corresponds to a
+  defined structure. The data in a data set can be roughly described as belonging to one of the following kinds:</p>
+
+<dl>
+  <dt>Observations</dt>
+  <dd>This is the actual data, the measured values. In a statistical table, the observations 
+       would be the values in the table cells.</dd>
+
+  <dt>Organizational structure</dt>
+  <dd>To locate an observation within the hypercube, one has at least to know the value of each 
+      dimension at which the observation is located, so these values must be specified for each observation. 
+      Datasets can have additional organizational structure in the form of <em>slices</em> 
+    as described in <a href="#slices">section 7.2</a>.
+
+  </dd><dt>Structural metadata</dt>
+  <dd>Having located an observation, we need certain metadata in order to be able to interpret it. 
+    What is the unit of measurement? Is it a normal value or a series break? 
+    Is the value measured or estimated? These metadata are provided as <em>attributes</em> and can 
+    be attached to individual observations, or to higher levels.</dd>
+
+  <dt>Reference metadata</dt>
+  <dd>This is metadata that describes the dataset as a whole, such as categorization of the 
+       dataset, its publisher, and a SPARQL endpoint where it can be accessed. 
+      External metadata is described in <a href="#metadata">section 9</a>.</dd>
+</dl>
+</section>
+
+<section id="cubes-model" class="informative">
+<h3><span class="secno">5.2 </span>The cube model - dimensions, attributes, measures</h3><p><em>This section is non-normative.</em></p>
+
+<p>A statistical data set comprises a collection of observations made
+at some points across some logical space. The collection can be characterized by
+a set of dimensions that define what the observation applies to (e.g. time,
+area, gender) along with metadata describing what has been
+measured (e.g. economic activity, population), how it was measured and how the
+observations are expressed (e.g. units, multipliers, status). We can
+think of the statistical data set as a multi-dimensional
+space, or hyper-cube, indexed by those dimensions. This space is
+commonly referred to
+as a <em>cube</em> for short; though the name shouldn't be taken
+literally, it is not meant to imply that
+there are exactly three dimensions (there can be more or fewer) nor
+that
+all the dimensions are somehow similar in size.</p>
+
+<p>A cube is organized according to a set of <em>dimensions</em>,
+<em>attributes</em> and <em>measures</em>. We collectively call these <em>components</em>.</p>
+
+<p>The <em>dimension</em> components serve to identify
+the observations. A set of values for all the dimension
+components
+is sufficient to identify a single observation. Examples of dimensions
+include the
+time to which the observation applies, or a geographic region which the observation covers.</p>
+
+<p>The <em>measure</em> components represent the phenomenon being
+observed.</p>
+
+<p>The <em>attribute</em> components allow us to qualify and
+interpret the observed value(s). They enable specification of the units of
+measure, any scaling factors and metadata such as the status
+of the observation (e.g. <em>estimated</em>, <em>provisional</em>).</p>
+</section>
+
+
+<section id="cubes-slices" class="informative">
+<h3><span class="secno">5.3 </span>Introducing Slices</h3><p><em>This section is non-normative.</em></p>
+
+<p>It is frequently useful to group subsets of observations within a
+dataset. In particular to fix all but one (or a small subset) of the
+dimensions and be able to refer to all observations with those
+dimension values as a single entity. We call such a selection a <em>slice</em>
+through the cube. For example, given a data set on regional performance
+indicators then we might group together all the observations about a given indicator
+and a given region. Each such group would be a slice representing a time
+  series of observed values.</p>
+
+<p>A data publisher may identify slices through the data for various
+purposes. They can be a useful grouping to which metadata might be attached, for example to note a
+change in measurement process which
+affects a particular time or region. Slices also enable the publisher to
+identify and label particular subsets of the data which should be presented to the
+user - they can enable the consuming application to more easily
+  construct the appropriate graph or chart for presentation.</p>
+
+<p>In statistical applications it is common to work with
+slices in which a single dimension is left unspecified. 
+In particular,
+to refer to such slices in which the single free dimension is time as <em>Time
+Series</em> and to refer slices along non-time dimensions as <em>Sections</em>.
+Within the Data Cube vocabulary we allow arbitrary dimensionality
+slices and do not give different names to particular types of
+  slice. Such sub-classes of slice could be added in extension vocabularies.</p>
+
+</section>
+
+<section id="example" class="informative">
+<h3><span class="secno">5.4 </span>An example</h3><p><em>This section is non-normative.</em></p>
+
+<p>In order to illustrate the use of the data cube vocabulary we will
+use a small demonstration
+data set extracted from
+<a href="http://statswales.wales.gov.uk/index.htm">StatsWales</a> report
+number 003311 which describes life expectancy broken down by region
+(unitary authority), age and time. The extract we will use is:<br>
+</p>
+
+<table id="example-data" style="text-align: left; width: 80%;">
+  <tbody>
+    <tr>
+      <td style="vertical-align: top;"><br>
+      </td>
+      <td colspan="2" rowspan="1" style="vertical-align: top; text-align: center; font-weight: bold;">2004-2006<br>
+      </td>
+      <td colspan="2" rowspan="1" style="vertical-align: top; text-align: center; font-weight: bold;">2005-2007<br>
+      </td>
+      <td colspan="2" rowspan="1" style="vertical-align: top; text-align: center; font-weight: bold;">2006-2008<br>
+      </td>
+    </tr>
+    <tr>
+      <td style="vertical-align: top;"><br>
+      </td>
+      <td style="vertical-align: top; text-align: center; font-weight: bold;">Male<br>
+      </td>
+      <td style="vertical-align: top; text-align: center; font-weight: bold;">Female<br>
+      </td>
+      <td style="vertical-align: top; text-align: center; font-weight: bold;">Male<br>
+      </td>
+      <td style="vertical-align: top; text-align: center; font-weight: bold;">Female<br>
+      </td>
+      <td style="vertical-align: top; text-align: center; font-weight: bold;">Male<br>
+      </td>
+      <td style="vertical-align: top; text-align: center; font-weight: bold;">Female<br>
+      </td>
+    </tr>
+    <tr>
+      <td style="vertical-align: top; text-align: right; font-weight: bold;">Newport<br>
+      </td>
+      <td style="vertical-align: top;">76.7<br>
+      </td>
+      <td style="vertical-align: top;">80.7<br>
+      </td>
+      <td style="vertical-align: top;">77.1<br>
+      </td>
+      <td style="vertical-align: top;">80.9<br>
+      </td>
+      <td style="vertical-align: top;">77.0<br>
+      </td>
+      <td style="vertical-align: top;">81.5<br>
+      </td>
+    </tr>
+    <tr>
+      <td style="vertical-align: top; text-align: right; font-weight: bold;">Cardiff<br>
+      </td>
+      <td style="vertical-align: top;">78.7<br>
+      </td>
+      <td style="vertical-align: top;">83.3<br>
+      </td>
+      <td style="vertical-align: top;">78.6<br>
+      </td>
+      <td style="vertical-align: top;">83.7<br>
+      </td>
+      <td style="vertical-align: top;">78.7<br>
+      </td>
+      <td style="vertical-align: top;">83.4<br>
+      </td>
+    </tr>
+    <tr>
+      <td style="vertical-align: top; text-align: right; font-weight: bold;">Monmouthshire<br>
+      </td>
+      <td style="vertical-align: top;">76.6<br>
+      </td>
+      <td style="vertical-align: top;">81.3<br>
+      </td>
+      <td style="vertical-align: top;">76.5<br>
+      </td>
+      <td style="vertical-align: top;">81.5<br>
+      </td>
+      <td style="vertical-align: top;">76.6<br>
+      </td>
+      <td style="vertical-align: top;">81.7<br>
+      </td>
+    </tr>
+    <tr>
+      <td style="vertical-align: top; text-align: right; font-weight: bold;">Merthyr
+Tydfil<br>
+      </td>
+      <td style="vertical-align: top;">75.5<br>
+      </td>
+      <td style="vertical-align: top;">79.1<br>
+      </td>
+      <td style="vertical-align: top;">75.5<br>
+      </td>
+      <td style="vertical-align: top;">79.4<br>
+      </td>
+      <td style="vertical-align: top;">74.9<br>
+      </td>
+      <td style="vertical-align: top;">79.6<br>
+      </td>
+    </tr>
+  </tbody>
+</table>
+
+<p>We can see that there are three dimensions - time period (rolling averages over three year timespans),
+  region and sex. Each observation represents the life expectancy for that population (the measure) and
+  we will need an attribute to define the units (years) of the measured values.</p>
+
+<p>An example of slicing the data would be to define slices in which the time and sex are
+fixed for each slice. Such slices then show the variation in life expectancy across the 
+  different regions, i.e. corresponding to the columns in the above tabular layout.</p>
+
+<p>A complete encoding of this data as a Data Cube, including such a
+  slice structure, is shown in <a href="#full-example">Appendix C</a>.</p>
+
+</section>
+
+</section>
+
+
+<section id="dsd">
+<!--OddPage--><h2><span class="secno">6. </span>Creating data structure definitions</h2>
+
+<p>A <code><a href="#dfn-qb-datastructuredefinition" class="internalDFN">qb:DataStructureDefinition</a></code> defines the structure of one or more
+datasets. In particular, it defines the dimensions, attributes and measures 
+used in the dataset along with qualifying information such as ordering of
+  dimensions and whether attributes are required or optional. For well-formed
+  data sets much of this information is implicit within the RDF component properties
+  found on the observations. However, the explicit declaration of the structure has
+  several benefits:</p>
+
+<ul>
+  <li>it enables verification that the data set matches the expected structure,
+   in particular helps with detection of incoherent sets obtained by 
+   combining differently structured source data;</li>
+  <li>it allows a consumer to easily determine what dimensions are available for query
+    and their presentational order, which in turn simplifies data
+    consumption, for example for UI construction;</li>
+  <li>it supports transmission of the structure information in
+  associated SDMX data flows (see below).</li>
+</ul>
+
+<p>It is common, when publishing statistical data, to have a regular series of publications which
+all follow the same structure. The notion of a Data Structure Definition (DSD) allows us to define
+that structure once and then reuse it for each publication in the series. Consumers can then be
+  confident that the structure of the data has not changed.</p>
+
+<section id="dsd-dimensions">
+<h3><span class="secno">6.1 </span>Dimensions, attributes and measures</h3>
+
+<p>The Data Cube vocabulary represents the dimensions, attributes and measures
+  as RDF properties. Each is an instance of the abstract <code><a href="#dfn-qb-componentproperty" class="internalDFN">qb:ComponentProperty</a></code> 
+  class,  which in turn has sub-classes <code><a href="#dfn-qb-dimensionproperty" class="internalDFN">qb:DimensionProperty</a></code>,
+  <code><a href="#dfn-qb-attributeproperty" class="internalDFN">qb:AttributeProperty</a></code> and <code><a href="#dfn-qb-measureproperty" class="internalDFN">qb:MeasureProperty</a></code>.</p>
+
+<p>A component property encapsulates several pieces of information:</p>
+<ul>
+  <li>the concept being represented (e.g. time or geographic area),</li>
+  <li>the nature of the component (dimension, attribute or measure) as represented by the type of the component property,</li>
+  <li>the type or code list used to represent the value.</li>
+</ul>
+
+<p>The same <em>concept</em> can be manifested in different components. For example, the concept
+  of <em>currency</em> may be used as a dimension (in a data set dealing with exchange rates) or as
+  an attribute (when describing the currency in which an observed trade took place). The concept of time
+  is typically used only as a dimension but may be encoded as a data value (e.g. an <code>xsd:dateTime</code>)
+  or as a symbolic value (e.g. a URI drawn from the reference time URI set developed by data.gov.uk).
+  In statistical agencies it is common to have a standard thesaurus of statistical concepts which 
+  underpin the components used in multiple different data sets.</p>
+
+<p>To support this reuse of general statistical concepts the data cube vocabulary provides the <code><a href="#dfn-qb-concept" class="internalDFN">qb:concept</a></code> property which
+  links a <code><a href="#dfn-qb-componentproperty" class="internalDFN">qb:ComponentProperty</a></code> to the concept it represents. We use the SKOS
+  vocabulary [<cite><a class="bibref" href="#bib-SKOS-PRIMER">SKOS-PRIMER</a></cite>] to represent such concepts. This is very natural for those cases where the  
+  concepts are already maintained as a controlled term list or thesaurus.
+   When developing a data structure definition for an informal data set there may not be an appropriate 
+   concept already. In those cases, if the concept is likely to be reused in other guises it is recommended to
+   publish a <code>skos:Concept</code> along with the specific <code><a href="#dfn-qb-componentproperty" class="internalDFN">qb:ComponentProperty</a></code>. However, if
+  such reuse is not expected then it is not required to do so - the <code><a href="#dfn-qb-concept" class="internalDFN">qb:concept</a></code>
+  link is optional and a simple instance of the appropriate subclass of <code><a href="#dfn-qb-componentproperty" class="internalDFN">qb:ComponentProperty</a></code> is
+  sufficient.</p>
+
+<p>The representation of the possible values of the component is described using the <code>rdfs:range</code>
+   property of the component in the usual RDF manner. Thus, for example, values of a time dimension might
+  be represented using literals of type <code>xsd:dateTime</code> or as URIs drawn from a time reference service.</p>
+
+<p>In statistical data sets it is common
+   for values to be encoded using some (possibly hierarchical) code list and it can be useful to be 
+   able to easily identify the overall code list in some more structured form. To cater for this a 
+  component can also be optionally annotated with  a <code><a href="#dfn-qb-codelist" class="internalDFN">qb:codeList</a></code> to indicate a set of 
+  <code>skos:Concept</code>s which may be used as codes. The  <code><a href="#dfn-qb-codelist" class="internalDFN">qb:codeList</a></code> value may be a
+  <code>skos:ConceptScheme</code>,  <code>skos:Collection</code> or <code><a href="#dfn-qb-hierarchicalcodelist" class="internalDFN">qb:HierarchicalCodeList</a></code>.
+  In such a case the <code>rdfs:range</code> of the component might be left as simply <code>skos:Concept</code> but 
+  a useful design pattern is to also define an <code>rdfs:Class</code>
+  whose members are all the <code>skos:Concept</code>s within a particular scheme. In that way 
+  the <code>rdfs:range</code> can be made more specific which enables generic RDF tools to perform
+  appropriate range checking.</p>
+
+<p>Note that in any SDMX extension vocabulary there would be one further item of information to encode
+  about components - the role that they play within the structure definition. In particular, it is sometimes
+  convenient for consumers to be able to easily identify which is the time dimension,
+  which component is the primary measure and so forth. It turns out that such roles are intrinsic to
+  the concepts and so this information can be encoded by providing subclasses of <code>skos:Concept</code>
+  for each role. The particular choice of roles here is specific to the SDMX standard and so is not 
+  included within the core Data Cube vocabulary.</p>
+
+<p>Before illustrating the components needed for our running example, there is one more piece
+  of machinery to introduce, a reusable set of concepts and components based on SDMX. 
+</p>
+</section>
+
+<section id="dsd-cog" class="informative">
+<h3><span class="secno">6.2 </span>Content oriented guidelines</h3><p><em>This section is non-normative.</em></p>
+
+<p>The SDMX standard includes a set of <em>content oriented guidelines</em> (COG) [<cite><a class="bibref" href="#bib-COG">COG</a></cite>]
+ which define a  set of common statistical concepts and associated code lists that are intended to be 
+   reusable across data sets. A <a href="https://code.google.com/p/publishing-statistical-data/">community group</a> 
+   has developed RDF encodings of these guidelines. These comprise:
+
+</p><table id="namespaces-table">
+  <thead><tr><th>Prefix</th><th>Namespace</th><th>Description</th></tr></thead>
+  <tbody>
+    <tr><td><code>sdmx-concept</code></td><td><a href="http://purl.org/linked-data/sdmx/2009/concept#">http://purl.org/linked-data/sdmx/2009/concept#</a></td><td>SKOS Concepts for each COG defined concept</td>
+    </tr><tr><td><code>sdmx-code</code></td><td><a href="http://purl.org/linked-data/sdmx/2009/code#">http://purl.org/linked-data/sdmx/2009/code#</a></td><td>SKOS Concepts and ConceptSchemes for each COG defined code list</td>
+    </tr><tr><td><code>sdmx-dimension</code></td><td><a href="http://purl.org/linked-data/sdmx/2009/dimension#">http://purl.org/linked-data/sdmx/2009/dimension#</a></td><td>component properties corresponding to each COG concept that can be used as a dimension</td>
+    </tr><tr><td><code>sdmx-attribute</code></td><td><a href="http://purl.org/linked-data/sdmx/2009/attribute#">http://purl.org/linked-data/sdmx/2009/attribute#</a></td><td>component properties corresponding to each COG concept that can be used as an attribute</td>
+    </tr><tr><td><code>sdmx-measure</code></td><td><a href="http://purl.org/linked-data/sdmx/2009/measure#">http://purl.org/linked-data/sdmx/2009/measure#</a></td><td>component properties corresponding to each COG concept that can be used as a measure</td>
+  
+  </tr></tbody>
+</table>
+
+<p>These community resources are provided as a convenience and do not form part
+  of the Data Cube specification. However, they are used
+  by a number of existing Data Cube publications and so we will
+  reference them within our worked examples.</p>
+
+</section>
+
+
+<section id="dsd-example" class="informative">
+<h3><span class="secno">6.3 </span>Example dimensions and measure</h3><p><em>This section is non-normative.</em></p>
+
+<p>Turning to our example data set then we can see there are three dimensions to represent
+   - time period, region (unitary authority) and sex. There is a single
+   (primary) measure which corresponds to the topic of the data set (life expectancy) and
+  encodes a value in years. Hence, we need the following components.</p>
+
+<p><b>Time.</b> There is a suitable predefined concept in the SMDX-COG for this, REF_PERIOD, so 
+  we could reuse the corresponding component property <code>sdmx-dimension:refPeriod</code>. However,
+  to represent the time period itself it would be convenient to use the data.gov.uk reference
+  time service and to declare this within the data structure definition.</p>
+
+<div class="example"><div class="example-title"><span>Example 1</span></div><pre class="example">eg:refPeriod  a rdf:Property, qb:DimensionProperty;
+    rdfs:label "reference period"@en;
+    rdfs:subPropertyOf sdmx-dimension:refPeriod;
+    rdfs:range interval:Interval;
+    qb:concept sdmx-concept:refPeriod . </pre></div>
+
+<p><b>Region.</b> Again there is a suitable COG concept and associated component that
+we can use for this, and again we can customize the range of the component. In this case
+  we can use the Ordnance Survey Administrative Geography Ontology [<cite><a class="bibref" href="#bib-OS-GEO">OS-GEO</a></cite>].</p>
+
+<div class="example"><div class="example-title"><span>Example 2</span></div><pre class="example">eg:refArea  a rdf:Property, qb:DimensionProperty;
+    rdfs:label "reference area"@en;
+    rdfs:subPropertyOf sdmx-dimension:refArea;
+    rdfs:range admingeo:UnitaryAuthority;
+    qb:concept sdmx-concept:refArea . </pre></div>
+
+<p><b>Sex.</b> In this case we can use the corresponding COG component <code>sdmx-dimension:sex</code> 
+    directly, since the default code list for it includes the terms we need.</p>
+
+<p><b>Measure.</b> This property will give the value of each observation.
+  We could use the default <code>smdx-measure:obsValue</code> for this (defining
+  the topic being observed using metadata). However, it can aid readability and processing
+  of the RDF data sets to use a specific measure corresponding to the phenomenon being observed.</p>
+  
+<div class="example"><div class="example-title"><span>Example 3</span></div><pre class="example">eg:lifeExpectancy  a rdf:Property, qb:MeasureProperty;
+    rdfs:label "life expectancy"@en;
+    rdfs:subPropertyOf sdmx-measure:obsValue;
+    rdfs:range xsd:decimal . </pre></div>
+  
+<p><b>Unit measure attribute.</b> The primary measure on its own is a plain decimal value.
+  To correctly interpret this value we need to define what units it is measured in (years in this case).
+  This is defined using attributes which qualify the interpretation of the observed value.
+  Specifically in this example we can use the predefined <code>sdmx-attribute:unitMeasure</code>
+  which in turn corresponds to the COG concept of <code>UNIT_MEASURE</code>. To express
+  the value of this attribute we would typically use a common thesaurus of units of measure.
+  For the sake of this simple example we will use the DBpedia resource <code>http://dbpedia.org/resource/Year</code>
+  which corresponds to the topic of the Wikipedia page on "Years".</p>
+
+<p>This covers the minimal components needed to define the structure of this data set.</p>
+</section>
+
+
+<section id="dsd-dsd">
+<h3><span class="secno">6.4 </span>ComponentSpecifications and DataStructureDefinitions</h3>
+
+<p>To combine the components into a specification for the structure of this
+  dataset we need to declare a <code><a>qb:DataStuctureDefinition</a></code>
+  resource which in turn will reference a set of <code><a href="#dfn-qb-componentspecification" class="internalDFN">qb:ComponentSpecification</a></code> resources.
+  The <code><a>qb:DataStuctureDefinition</a></code> will be reusable across other data sets with the same structure.</p>
+
+<p>In the simplest case the <code><a href="#dfn-qb-componentspecification" class="internalDFN">qb:ComponentSpecification</a></code> simply references the
+  corresponding <code><a href="#dfn-qb-componentproperty" class="internalDFN">qb:ComponentProperty</a></code> (usually using one of the sub properties
+  <code><a href="#dfn-qb-dimension" class="internalDFN">qb:dimension</a></code>, <code><a href="#dfn-qb-measure" class="internalDFN">qb:measure</a></code> or <code><a href="#dfn-qb-attribute" class="internalDFN">qb:attribute</a></code>). 
+  However, it is also possible to qualify the
+  component specification in several ways.</p>
+
+<ul>
+  <li>Attributes may be declared as optional or required. If an
+  attribute is required to be present for every observation then the specification should set 
+    <code><a href="#dfn-qb-componentrequired" class="internalDFN">qb:componentRequired</a></code>. In the
+    absence of such a declaration an attribute is assumed to be
+    optional. The  <code><a href="#dfn-qb-componentrequired" class="internalDFN">qb:componentRequired</a></code>
+    declaration may only be applied to component specifications of
+    attributes -  measures and dimensions are always required.</li>
+  <li>The components may be ordered by giving an integer value for <code><a href="#dfn-qb-order" class="internalDFN">qb:order</a></code>. 
+    This order carries no semantics but can be useful to aid consuming agents in generating
+    appropriate user interfaces. It can also be useful in the publication chain to enable
+    synthesis of appropriate URIs for observations.</li>
+  <li>By default the values of all of the components will be attached to each individual observation,
+    this is called the <em><a href="#dfn-normalized" class="internalDFN">normalized</a></em> representation.
+    This allows such observations to stand alone, so that a SPARQL query to retrieve the observation
+    can immediately locate the attributes which enable the observation to be interpreted. However,
+    it is also permissible to attach attributes to the
+    overall data set, to an intervening slice or to a specific Measure (in the case of multiple measures).
+    This reduces some of the redundancy in the encoding of the instance data. To declare such an
+    abbreviated structure, the <code><a href="#dfn-qb-componentattachment" class="internalDFN">qb:componentAttachment</a></code> property of the specification should
+    reference the class corresponding to the attachment level (e.g. <code><a href="#dfn-qb-dataset" class="internalDFN">qb:DataSet</a></code> for attributes
+    that will be attached to the overall data set). The classes 
+    which can be used as such attachment levels are all subclasses of <code><a href="#dfn-qb-attachable" class="internalDFN">qb:Attachable</a></code>.</li>
+</ul>
+
+<p>In the case of our running example the dimensions can be usefully ordered. There is only one
+   attribute, the unit measure, and this is required. In the interest of illustrating the vocabulary
+   use we will declare that this attribute will be attached at the level of the data set, however 
+   normalized representations are in general easier to query and combine.</p>
+
+<p>So the structure of our example data set (and other similar datasets) can be declared by:</p>
+
+<div class="example"><div class="example-title"><span>Example 4</span></div><pre id="attachment-example" class="example">eg:dsd-le a qb:DataStructureDefinition;
+    # The dimensions
+    qb:component [ qb:dimension eg:refArea;         qb:order 1 ];
+    qb:component [ qb:dimension eg:refPeriod;       qb:order 2 ];
+    qb:component [ qb:dimension sdmx-dimension:sex; qb:order 3 ];
+    # The measure(s)
+    qb:component [ qb:measure eg:lifeExpectancy];
+    # The attributes
+    qb:component [ qb:attribute sdmx-attribute:unitMeasure; 
+                   qb:componentRequired "true"^^xsd:boolean;
+                   qb:componentAttachment qb:DataSet; ] .</pre></div>
+
+<p>Note that we have given the data structure definition (DSD) a URI since it will be
+ reused across different datasets with the same structure. Similarly the component properties
+ themselves can be reused across different DSDs. However, the component specifications
+ are only useful within the scope of a particular DSD and so we have chosen to represent
+ them using blank nodes.
+</p>
+</section>
+      
+
+<section id="dsd-mm">
+<h3><span class="secno">6.5 </span>Handling multiple measures</h3>
+
+<p>Our example data set is relatively simple in having a single observable (in this case "life expectancy") 
+  that is being measured. In other data sets there can be multiple measures. These measures
+  may be of similar nature (e.g. a data set on local government performance might provide
+  multiple different performance indicators for each region) or quite different (e.g. a data set
+  on trades might provide quantity, value, weight for each trade).</p>
+  
+<p>There are two approaches to representing multiple measures supported by the Data Cube vocabulary.</p>
+
+<p>In the first approach each observation records a single observed value for one measure.
+We introduce an additional dimension whose value indicates the measure being conveyed by 
+each observation. This <em>measure dimension</em> approach is the one supported by the SDMX information model. </p>
+
+<p>In the second approach a single observation can provide values for multiple different measures.
+This is particularly appropriate in cases where each of those values relates to a single
+observational event such as a multi-spectral sensor measurement. This <em>multi-measure</em>
+approach is commonly used in applications such as Business Intelligence and OLAP.</p>
+
+<p>The Data Cube vocabulary permits either representation approach to be used though they cannot be mixed
+  within the same data set. </p>
+
+<p>Both representation approaches require
+  that, for every point in the space of dimensions for which there is
+  an observation, a value must be given for every measure. In the
+  case of multi-measure observations each measure must be
+  present on each observation. In cubes which use a measure dimension
+  there are sets of observations for each populated point in the
+  cube and within each of those sets there must be an observation giving each measure.</p>
+  
+
+<section id="dsd-mm-obs">
+<h4><span class="secno">6.5.1 </span>Multi-measure observations</h4>
+  
+<p> This approach allows multiple observed values to be attached
+  to an individual observation. It is suited to representation of things like sensor data and OLAP cubes.
+  To use this representation you simply declare multiple <code><a href="#dfn-qb-measureproperty" class="internalDFN">qb:MeasureProperty</a></code> components
+  in the data structure definition and attach an instance of each property to the observations within 
+  the data set.</p>
+
+<p>For example, if we have a set of shipment data containing unit count and total weight for each
+  shipment then we might have a data structure definition such as:</p>
+<div class="example"><div class="example-title"><span>Example 5</span></div><pre class="example">eg:dsd1 a qb:DataStructureDefinition;
+    rdfs:comment "shipments by time (multiple measures approach)"@en;
+    qb:component 
+        [ qb:dimension  sdmx-dimension:refTime; ],
+        [ qb:measure    eg-measure:quantity; ],
+        [ qb:measure    eg-measure:weight; ] . </pre></div>
+        
+<p>This would correspond to individual observations such as:</p>
+<div class="example"><div class="example-title"><span>Example 6</span></div><pre class="example">eg:dataset1 a qb:DataSet;
+    qb:structure eg:dsd1 .
+    
+eg:obs1a  a qb:Observation;
+    qb:dataSet eg:dataset1;
+    sdmx-dimension:refTime "2010-07-30"^^xsd:date;
+    eg-measure:weight 1.3 ;
+    eg-measure:quantity 42 ;
+    . </pre></div>
+    
+<p>Note that one limitation of the multi-measure approach is that it is not possible to attach
+  an attribute to a single observed value. An attribute attached to the observation instance
+  will apply to the whole observation (e.g. to indicate who made the observation). Attributes
+  can also be attached directly to the <code><a href="#dfn-qb-measureproperty" class="internalDFN">qb:MeasureProperty</a></code> itself (e.g. to indicate
+  the <em>unit of measure</em> for that measure) but that attachment applies to the whole data
+  set (indeed any data set using that measure property) and cannot vary for different observations.
+  For applications where this limitation is a problem then use the <em>measure dimension</em> approach.</p> 
+</section>
+
+
+<section id="dsd-mm-dim">
+<h4><span class="secno">6.5.2 </span><dfn id="dfn-measure-dimension">Measure dimension</dfn></h4>
+  
+<p>This approach restricts observations to having a single measured value but allows
+  a data set to carry multiple measures by adding an extra dimension, a <em>measure dimension</em>.
+  The value of the measure dimension denotes which particular measure is being conveyed by the 
+  observation. This is the representation approach used within SDMX and an extension vocabulary
+  could introduce a sub-class of <code><a href="#dfn-qb-datastructuredefinition" class="internalDFN">qb:DataStructureDefinition</a></code> which enforces
+  such a single-measure restriction.</p>
+  
+<p>To use this representation you declare an additional dimension within the data structure
+  definition to play the role of the measure dimension. For use within the Data Cube vocabulary
+  we provide a single distinguished component for this purpose -- <code><a href="#dfn-qb-measuretype" class="internalDFN">qb:measureType</a></code>.
+  An extension vocabulary could generalize this through the provision of roles to
+  identify concepts which
+  act as measure types, enabling other measure dimensions to be declared. 
+</p>
+
+ <p>
+  In the special case of using <code><a href="#dfn-qb-measuretype" class="internalDFN">qb:measureType</a></code> as the measure dimension, the set of allowed 
+  measures is assumed to be those measures declared within the DSD. There is no need to 
+  define a separate code list or enumerated class to duplicate this information. 
+  Thus, <code><a href="#dfn-qb-measuretype" class="internalDFN">qb:measureType</a></code> is a “magic” dimension
+  property with an implicit code list. This notion of an implicit
+  code list for <code><a href="#dfn-qb-measuretype" class="internalDFN">qb:measureType</a></code> is a small divergence
+  from SDMX usage.</p>
+
+<p>The data structure definition for our above example, using this representation approach, would then be:</p>
+<div class="example"><div class="example-title"><span>Example 7</span></div><pre class="example">eg:dsd2 a qb:DataStructureDefinition;
+    rdfs:comment "shipments by time (measure dimension approach)"@en;
+    qb:component 
+        [ qb:dimension  sdmx-dimension:refTime; ],
+        [ qb:measure    eg-measure:quantity; ],
+        [ qb:measure    eg-measure:weight; ],
+        [ qb:dimension  qb:measureType; ] . </pre></div>
+        
+<p>This would correspond to individual observations such as:</p>
+<div class="example"><div class="example-title"><span>Example 8</span></div><pre class="example">eg:dataset2 a qb:DataSet;
+    qb:structure eg:dsd2 .
+    
+eg:obs2a  a qb:Observation;
+    qb:dataSet eg:dataset2;
+    sdmx-dimension:refTime "2010-07-30"^^xsd:date;
+    qb:measureType eg-measure:weight ;
+    eg-measure:weight 1.3 .
+    
+eg:obs2b  a qb:Observation;
+    qb:dataSet eg:dataset2;
+    sdmx-dimension:refTime "30-07-2010"^^xsd:date;
+    qb:measureType eg-measure:quantity ;
+    eg-measure:quantity 42 . </pre></div>
+    
+
+<p>Note the duplication of having the measure property show up both as the property that 
+  carries the measured value, and as the value of the measure dimension. We accept 
+  this duplication as necessary to ensure the uniform cube/dimension mechanism and 
+  a uniform way of declaring and using measure properties on all kinds of datasets.</p><p>
+  
+</p><p>Those familiar with SDMX should also note that in the RDF representation there is 
+  no need for a separate "primary measure" which subsumes each of the individual 
+  measures, those individual measures are used directly. Extension vocabularies
+  could address the round-tripping of the SDMX primary measure by use of a
+  separate annotation on the data structure definition.
+</p></section>
+
+</section>
+
+</section>
+
+
+<section id="datasets">
+<!--OddPage--><h2><span class="secno">7. </span>Expressing data sets</h2>
+
+<section id="dataset-basic">
+<h3><span class="secno">7.1 </span>Data sets and observations</h3>
+
+<p>A resource representing the entire data set is created and typed as <code><a href="#dfn-qb-dataset" class="internalDFN">qb:DataSet</a></code> and
+  linked to the corresponding data structure definition via the <code><a href="#dfn-qb-structure" class="internalDFN">qb:structure</a></code> property.</p>
+
+<p><strong>Pitfall</strong>: Note the capitalization of <code>qb:<strong>D</strong>ata<strong>S</strong>et</code>, 
+which differs from the capitalization in other vocabularies, such as
+<a href="http://semanticweb.org/wiki/VoiD">void:Dataset</a> and <a href="http://www.w3.org/egov/wiki/Data_Catalog_Vocabulary">dcat:Dataset</a>. This unusual capitalization is chosen for compatibility
+with the SDMX standard. The same applies to the related property <code>qb:data<strong>S</strong>et</code>.</p>
+
+<p>Each observation is represented as an instance of type <code><a href="#dfn-qb-observation" class="internalDFN">qb:Observation</a></code>.
+  In the basic case then values for each of the attributes, dimensions and measurements are attached directly to the observation (remember 
+  that these components are all RDF properties). The observation is linked to the containing
+  data set using the <code><a href="#dfn-qb-dataset-1" class="internalDFN">qb:dataSet</a></code> property. </p>
+
+<p>Thus for our running example we might expect to have:</p>
+
+<div class="example"><div class="example-title"><span>Example 9</span></div><pre class="example">eg:dataset-le1 a qb:DataSet;
+    rdfs:label "Life expectancy"@en;
+    rdfs:comment "Life expectancy within Welsh Unitary authorities - extracted from Stats Wales"@en;
+    qb:structure eg:dsd-le ;
+    .  
+
+eg:o1 a qb:Observation;
+    qb:dataSet  eg:dataset-le1 ;
+    eg:refArea                 ex-geo:newport_00pr ;                  
+    eg:refPeriod               &lt;http://reference.data.gov.uk/id/gregorian-interval/2004-01-01T00:00:00/P3Y&gt; ;
+    sdmx-dimension:sex         sdmx-code:sex-M ;
+    sdmx-attribute:unitMeasure &lt;http://dbpedia.org/resource/Year&gt; ;
+    eg:lifeExpectancy          76.7 ;
+    .
+
+eg:o2 a qb:Observation;
+    qb:dataSet  eg:dataset-le1 ;
+    eg:refArea                 ex-geo:cardiff_00pt ;                  
+    eg:refPeriod               &lt;http://reference.data.gov.uk/id/gregorian-interval/2004-01-01T00:00:00/P3Y&gt; ;
+    sdmx-dimension:sex         sdmx-code:sex-M ;
+    sdmx-attribute:unitMeasure &lt;http://dbpedia.org/resource/Year&gt; ;
+    eg:lifeExpectancy          78.7 ;
+    .
+
+eg:o3 a qb:Observation;
+    qb:dataSet  eg:dataset-le1 ;
+    eg:refArea                 ex-geo:monmouthshire_00pp ;                  
+    eg:refPeriod               &lt;http://reference.data.gov.uk/id/gregorian-interval/2004-01-01T00:00:00/P3Y&gt; ;
+    sdmx-dimension:sex         sdmx-code:sex-M ;
+    sdmx-attribute:unitMeasure &lt;http://dbpedia.org/resource/Year&gt; ;
+    eg:lifeExpectancy          76.6 ;
+    .
+
+...</pre></div>
+
+<p>This <a href="#dfn-normalized" class="internalDFN">normalized</a> structure makes it easy to query and combine data sets 
+  but there is some redundancy here. For example, the unit of measure for the
+  life expectancy is uniform across the whole data set and does not change between
+  observations. To cater for situations like this the Data Cube vocabulary allows components
+  to be attached at a high level in the nested structure. Indeed if we re-examine our
+  original Data Structure Declaration we see that we declared the unit of measure to be
+  attached at the data set level. So an shortened version of the example is:</p>
+
+<div class="example"><div class="example-title"><span>Example 10</span></div><pre class="example">eg:dataset-le1 a qb:DataSet;
+    rdfs:label "Life expectancy"@en;
+    rdfs:comment "Life expectancy within Welsh Unitary authorities - extracted from Stats Wales"@en;
+    qb:structure eg:dsd-le ;  
+    sdmx-attribute:unitMeasure &lt;http://dbpedia.org/resource/Year&gt; ;
+    .
+    
+eg:o1 a qb:Observation;
+    qb:dataSet  eg:dataset-le1 ;
+    eg:refArea                 ex-geo:newport_00pr ;                  
+    eg:refPeriod               &lt;http://reference.data.gov.uk/id/gregorian-interval/2004-01-01T00:00:00/P3Y&gt; ;
+    sdmx-dimension:sex         sdmx-code:sex-M ;
+    eg:lifeExpectancy          76.7 ;
+    .
+    
+eg:o2 a qb:Observation;
+    qb:dataSet  eg:dataset-le1 ;
+    eg:refArea                 ex-geo:cardiff_00pt ;                  
+    eg:refPeriod               &lt;http://reference.data.gov.uk/id/gregorian-interval/2004-01-01T00:00:00/P3Y&gt; ;
+    sdmx-dimension:sex         sdmx-code:sex-M ;
+    eg:lifeExpectancy          78.7 ;
+    .
+
+eg:o3 a qb:Observation;
+    qb:dataSet  eg:dataset-le1 ;
+    eg:refArea                 ex-geo:monmouthshire_00pp ;                  
+    eg:refPeriod               &lt;http://reference.data.gov.uk/id/gregorian-interval/2004-01-01T00:00:00/P3Y&gt; ;
+    sdmx-dimension:sex         sdmx-code:sex-M ;
+    eg:lifeExpectancy          76.6 ;
+    .
+
+...</pre></div>
+
+<p>In a data set containing just observations with no intervening structure then each observation
+  must have a complete set of dimension values, along with all the measure values. If the
+  set is structured by using slices then further abbreviation is possible, as discussed
+  in the next section.</p>
+</section>
+
+
+<section id="slices">
+<h3><span class="secno">7.2 </span>Slices and groups of observations</h3>
+
+<p>Slices allow us to group subsets of observations together. This is not intended
+  to represent arbitrary selections from the observations but uniform slices
+  through the cube in which one or more of the dimension values are fixed.</p>
+  
+<p>Slices may be used for a number of reasons:</p>
+<ul>
+  <li>to guide consuming applications in how to present the data (e.g. to organize
+      data as a set of time series);</li>
+  <li>to provide an identity (URI) for the slice to enable it to be annotated or externally referenced;</li>
+  <li>to reduce the verbosity of the data set by only stating each fixed dimensional value once.</li>
+</ul>  
+
+<p>To illustrate the use of slices let us group the sample data set into geographic series.
+ That will enable us to refer to e.g. "male life expectancy observations for 2004-2006" 
+ and guide applications to present a comparative chart across regions. </p>
+
+<p>We first define the structure of the slices we want by associating a "slice key" with the
+   data structure definition. This is done by creating a <code><a href="#dfn-qb-slicekey" class="internalDFN">qb:SliceKey</a></code> to
+   list the component properties (which must be dimensions) which will be fixed in the
+   slice. The key is attached to the DSD using <code><a href="#dfn-qb-slicekey-1" class="internalDFN">qb:sliceKey</a></code>. For example: </p>
+   
+<div class="example"><div class="example-title"><span>Example 11</span></div><pre class="example">eg:sliceByRegion a qb:SliceKey;
+    rdfs:label "slice by region"@en;
+    rdfs:comment "Slice by grouping regions together, fixing sex and time values"@en;
+    qb:componentProperty eg:refPeriod, sdmx-dimension:sex .
+    
+eg:dsd-le-slice1 a qb:DataStructureDefinition;
+    qb:component 
+        [ qb:dimension eg:refArea;         qb:order 1 ],
+        [ qb:dimension eg:refPeriod;       qb:order 2 ],
+        [ qb:dimension sdmx-dimension:sex; qb:order 3 ],
+        [ qb:measure eg:lifeExpectancy];
+        [qb:attribute sdmx-attribute:unitMeasure; qb:componentAttachment qb:DataSet; ] ;
+    qb:sliceKey eg:sliceByRegion .</pre></div>   
+
+<p>In the instance data then slices are represented by instances of <code><a href="#dfn-qb-slice" class="internalDFN">qb:Slice</a></code> which 
+  link to the observations in the slice via <code><a href="#dfn-qb-observation-1" class="internalDFN">qb:observation</a></code> and to the key by means
+  of <code><a href="#dfn-qb-slicestructure" class="internalDFN">qb:sliceStructure</a></code>. Data sets indicate
+  the slices they contain by means of <code><a href="#dfn-qb-slice-1" class="internalDFN">qb:slice</a></code>. Thus in our example we would have:</p>
+
+<div class="example"><div class="example-title"><span>Example 12</span></div><pre class="example">eg:dataset-le2 a qb:DataSet;
+    rdfs:label "Life expectancy"@en;
+    rdfs:comment "Life expectancy within Welsh Unitary authorities - extracted from Stats Wales"@en;
+    qb:structure eg:dsd-le-slice2 ;  
+    sdmx-attribute:unitMeasure &lt;http://dbpedia.org/resource/Year&gt; ;
+    qb:slice eg:slice2;
+    .
+
+eg:slice2 a qb:Slice;
+    qb:sliceStructure  eg:sliceByRegion ;
+    eg:refPeriod               &lt;http://reference.data.gov.uk/id/gregorian-interval/2004-01-01T00:00:00/P3Y&gt; ;
+    sdmx-dimension:sex         sdmx-code:sex-M ;
+    qb:observation eg:o1b, eg:o2b, eg:o3b, ... .
+
+eg:o1b a qb:Observation;
+    qb:dataSet  eg:dataset-le2 ;
+    eg:refArea                 ex-geo:newport_00pr ;                  
+    eg:refPeriod               &lt;http://reference.data.gov.uk/id/gregorian-interval/2004-01-01T00:00:00/P3Y&gt; ;
+    sdmx-dimension:sex         sdmx-code:sex-M ;
+    eg:lifeExpectancy          76.7 ;
+    .
+    
+eg:o2b a qb:Observation;
+    qb:dataSet  eg:dataset-le2 ;
+    eg:refArea                 ex-geo:cardiff_00pt ;                  
+    eg:refPeriod               &lt;http://reference.data.gov.uk/id/gregorian-interval/2004-01-01T00:00:00/P3Y&gt; ;
+    sdmx-dimension:sex         sdmx-code:sex-M ;
+    eg:lifeExpectancy          78.7 ;
+    .
+
+eg:o3b a qb:Observation;
+    qb:dataSet  eg:dataset-le2 ;
+    eg:refArea                 ex-geo:monmouthshire_00pp ;                  
+    eg:refPeriod               &lt;http://reference.data.gov.uk/id/gregorian-interval/2004-01-01T00:00:00/P3Y&gt; ;
+    sdmx-dimension:sex         sdmx-code:sex-M ;
+    eg:lifeExpectancy          76.6 ;
+    .
+
+...</pre></div>
+
+<p>Note that here we are still repeating the dimension values on the individual observations.
+This normalized representation means that a consuming application can still query 
+for observed values uniformly without having to first parse the data structure
+definition and search for slice definitions. If it is desired, this redundancy can be reduced
+by declaring different attachment levels for the dimensions. For example:
+</p>
+<div class="example"><div class="example-title"><span>Example 13</span></div><pre class="example">eg:dsd-le-slice3 a qb:DataStructureDefinition;
+    qb:component 
+        [ qb:dimension eg:refArea;         qb:order 1 ];
+        [ qb:dimension eg:refPeriod;       qb:order 2; qb:componentAttachment qb:Slice ];
+        [ qb:dimension sdmx-dimension:sex; qb:order 3; qb:componentAttachment qb:Slice ];
+        [ qb:measure eg:lifeExpectancy];
+        [ qb:attribute sdmx-attribute:unitMeasure; qb:componentAttachment qb:DataSet; ] ;
+    qb:sliceKey eg:sliceByRegion .
+
+eg:dataset-le3 a qb:DataSet;
+    rdfs:label "Life expectancy"@en;
+    rdfs:comment "Life expectancy within Welsh Unitary authorities - extracted from Stats Wales"@en;
+    qb:structure eg:dsd-le-slice3 ;  
+    sdmx-attribute:unitMeasure &lt;http://dbpedia.org/resource/Year&gt; ;
+    qb:slice eg:slice3 ;
+    .
+
+eg:slice3 a qb:Slice;
+    qb:sliceStructure  eg:sliceByRegion ;
+    eg:refPeriod               &lt;http://reference.data.gov.uk/id/gregorian-interval/2004-01-01T00:00:00/P3Y&gt; ;
+    sdmx-dimension:sex         sdmx-code:sex-M ;
+    qb:observation eg:o1c, eg:o2c, eg:o3c, ... .
+
+eg:o1c a qb:Observation;
+    qb:dataSet  eg:dataset-le3 ;
+    eg:refArea                 ex-geo:newport_00pr ;                  
+    eg:lifeExpectancy          76.7 ;
+    .
+    
+eg:o2c a qb:Observation;
+    qb:dataSet  eg:dataset-le3 ;
+    eg:refArea                 ex-geo:cardiff_00pt ;                  
+    eg:lifeExpectancy          78.7 ;
+    .
+
+eg:o3c a qb:Observation;
+    qb:dataSet  eg:dataset-le3 ;
+    eg:refArea                 ex-geo:monmouthshire_00pp ;                  
+    eg:lifeExpectancy          76.6 ;
+    .
+
+...</pre></div>
+
+<p>There are also situations in which a publisher wishes to group a set of observations
+together for ease of access or presentation purposes but where that set is not defined
+by simply fixing a set of dimension values. For example, in
+  representing weather observations it can be desirable to group
+  together the latest observation available from each station even though
+  each observation may have been taken at a different time.
+  For those situations the Data Cube vocabulary supports
+<code><a href="#dfn-qb-observationgroup" class="internalDFN">qb:ObservationGroup</a></code>. A <code><a href="#dfn-qb-observationgroup" class="internalDFN">qb:ObservationGroup</a></code> can contain an arbitrary
+collection of observations.  A <code><a href="#dfn-qb-slice" class="internalDFN">qb:Slice</a></code> is a special case of a  <code><a href="#dfn-qb-observationgroup" class="internalDFN">qb:ObservationGroup</a></code>.
+
+</p></section>
+
+</section>
+
+
+<section id="schemes">
+<!--OddPage--><h2><span class="secno">8. </span>Concept schemes and code lists</h2>
+
+<section id="schemes-intro">
+<h3><span class="secno">8.1 </span>Coded values for components properties</h3>
+
+<p>The values for dimensions within a data set must be unambiguously
+   defined. They may be typed values (e.g. <code>xsd:dateTime</code> for time instances)
+   or codes drawn from some code list. Similarly, many attributes
+   used in data sets represent coded values from some controlled term list rather 
+   than free text descriptions. In the Data Cube vocabulary such codes are
+   represented by URI references in the usual RDF fashion.</p>
+ 
+<p>Sometimes
+   appropriate URI sets already exist for the relevant dimensions (e.g. the representations
+   of area and time periods in our running example). In other cases the data set being
+   converted may use controlled terms from some scheme which does not yet have
+   associated URIs. In those cases we recommend use of SKOS, representing
+   the individual code values using <code>skos:Concept</code> and the overall
+   set of admissible values using <code>skos:ConceptScheme</code> or <code>skos:Collection</code>.</p>
+   
+<p>We illustrate this with an example drawn from the translation of the SDMX COG
+  code list for gender, as used already in our worked example. The relevant subset of this code list is:</p>
+
+<div class="example"><div class="example-title"><span>Example 14</span></div><pre class="example">sdmx-code:sex a skos:ConceptScheme;
+    skos:prefLabel "Code list for Sex (SEX) - codelist scheme"@en;
+    rdfs:label "Code list for Sex (SEX) - codelist scheme"@en;
+    skos:notation "CL_SEX";
+    skos:note "This  code list provides the gender."@en;
+    skos:definition &lt;http://sdmx.org/wp-content/uploads/2009/01/02_sdmx_cog_annex_2_cl_2009.pdf&gt; ;
+    rdfs:seeAlso sdmx-code:Sex ;
+    sdmx-code:sex skos:hasTopConcept sdmx-code:sex-F ;
+    sdmx-code:sex skos:hasTopConcept sdmx-code:sex-M .
+
+sdmx-code:Sex a rdfs:Class, owl:Class;
+    rdfs:subClassOf skos:Concept ;
+    rdfs:label "Code list for Sex (SEX) - codelist class"@en;
+    rdfs:comment "This  code list provides the gender."@en;
+    rdfs:seeAlso sdmx-code:sex .
+
+sdmx-code:sex-F a skos:Concept, sdmx-code:Sex;
+    skos:topConceptOf sdmx-code:sex;
+    skos:prefLabel "Female"@en ;
+    skos:notation "F" ;
+    skos:inScheme sdmx-code:sex .
+
+sdmx-code:sex-M a skos:Concept, sdmx-code:Sex;
+    skos:topConceptOf sdmx-code:sex;
+    skos:prefLabel "Male"@en ;
+    skos:notation "M" ; 
+    skos:inScheme sdmx-code:sex .</pre></div>
+
+<p><code>skos:prefLabel</code> is used to give a name to the code, 
+<code>skos:note</code> gives a description and <code>skos:notation</code> can be used 
+to record a short form code which might appear in other serializations. 
+The SKOS specification [<cite><a class="bibref" href="#bib-SKOS-REFERENCE">SKOS-REFERENCE</a></cite>] recommends the generation of a custom datatype for
+each use of <code>skos:notation</code> but here the notation is not intended for use
+within RDF encodings, it merely documents the notation used in other representations 
+(which do not use such a datatype).</p>
+
+<p>It is convenient and good practice when developing a code list to also 
+create a Class to denote all the codes within the code
+list, irrespective of hierarchical structure. This allows the range of an
+<code><a href="#dfn-qb-componentproperty" class="internalDFN">qb:ComponentProperty</a></code> to be defined by using <code>rdfs:range</code>
+which then permits standard RDF closed-world checkers to validate use of the
+code list without requiring custom SDMX-RDF-aware tooling. We do that in the
+above example by using the common convention that the class name is the
+same as that of the concept scheme but with leading upper case.</p>
+
+<p>This code list can then be associated with a coded property, such as a dimension:</p>
+
+<div class="example"><div class="example-title"><span>Example 15</span></div><pre class="example">eg:sex a qb:DimensionProperty, qb:CodedProperty;
+    qb:codeList sdmx-code:sex ;
+    rdfs:range sdmx-code:Sex .</pre></div>
+
+<p>Explicitly declaring  the code list using <code><a href="#dfn-qb-codelist" class="internalDFN">qb:codeList</a></code>
+  is not mandatory but can be helpful in those cases where a concept scheme has been defined.</p>
+</section>
+
+<section id="schemes-hierarchy">  
+<h3><span class="secno">8.2 </span>Hierarchical code lists</h3>
+
+<p>In some cases code lists have a hierarchical structure. In particular, this is 
+used in SDMX when the data cube includes aggregations of data values 
+(e.g. aggregating a measure across geographic regions).
+Hierarchical code lists <em class="rfc2119" title="should">should</em> be represented using the 
+<code>skos:narrower</code> relationship, or a sub-property of it,
+to link from the <code>skos:hasTopConcept</code>
+codes down through the tree or lattice of child codes. 
+In some publishing tool chains the corresponding transitive closure 
+<code>skos:narrowerTransitive</code> will be automatically inferred. 
+The use of <code>skos:narrower</code> makes it possible to declare new 
+concept schemes which extend an existing scheme by adding additional aggregation layers on top.
+All items are linked to the scheme via <code>skos:inScheme</code>.</p>
+</section>
+
+<section id="schemes-hierarchy-nonskos">  
+<h3><span class="secno">8.3 </span>Non-SKOS hierarchies</h3>
+
+<p>It is sometimes convenient to be able to specify a hierarchical arrangement of 
+concepts other than through the use of the SKOS relation <code>skos:narrower</code>. 
+There are several situations where this is useful, for example:</p>
+
+<ul>
+<li>In some cases publishers wish to be able to reuse existing reference data as their
+code lists. This particularly occurs where a geographic or admin-geographic hierarchy
+is already maintained by a separate authority but which uses non-SKOS containment or part-of relationships.</li>
+<li>Where such maintained reference data is to be reused there can be multiple hierarchies which relate
+the same codes. In particular a set of geographic entities may participate in both a geographic-containment hierarchy
+and an administrative hierarchy which do not precisely align. </li>
+</ul>
+
+<p>The Data Cube vocabulary supports this situation through the <code><a href="#dfn-qb-hierarchicalcodelist" class="internalDFN">qb:HierarchicalCodeList</a></code> class.
+An instance of <code><a href="#dfn-qb-hierarchicalcodelist" class="internalDFN">qb:HierarchicalCodeList</a></code> defines a set of root concepts in the hierarchy 
+(<code><a href="#dfn-qb-hierarchyroot" class="internalDFN">qb:hierarchyRoot</a></code>) and a parent-to-child relationship (<code><a href="#dfn-qb-parentchildproperty" class="internalDFN">qb:parentChildProperty</a></code>) which
+links a term in the hierarchy to its immediate sub-terms. </p>
+
+<p>Thus a <code><a href="#dfn-qb-hierarchicalcodelist" class="internalDFN">qb:HierarchicalCodeList</a></code>
+is similar to a <code>skos:ConceptScheme</code> in which <code><a href="#dfn-qb-hierarchyroot" class="internalDFN">qb:hierarchyRoot</a></code> plays the same
+role as <code>skos:hasTopConcept</code>, and the value of <code><a href="#dfn-qb-parentchildproperty" class="internalDFN">qb:parentChildProperty</a></code> plays
+the same role as <code>skos:narrower</code>.  In the case where a code
+  list is already available as a SKOS concept scheme or collection, or
+  could reasonable me made so, then those <em class="rfc2119" title="should">should</em> be used
+  directly. <code><a href="#dfn-qb-hierarchicalcodelist" class="internalDFN">qb:HierarchicalCodeList</a></code> is provided
+  for cases where the 
+terms are not available as SKOS but are available in some other RDF representation suitable for reuse.
+</p>
+
+<p>For example, the Ordnance Survey of Great Britain publishes a geographic hierarchy which has 
+eleven roots (European Regions such as Wales, Scotland, the South West) and uses a spatial relations 
+ontology to define a containment hierarchy. This could be represented as a  <code><a href="#dfn-qb-hierarchicalcodelist" class="internalDFN">qb:HierarchicalCodeList</a></code> using the following.</p>
+
+<div class="example"><div class="example-title"><span>Example 16</span></div><pre class="example">@prefix spatial: &lt;http://data.ordnancesurvey.co.uk/ontology/spatialrelations/&gt; .
+
+eg:GBgeoHierarchy a qb:HierarchicalCodeList;
+    rdfs:label "Geographic Hierarchy for Great Britain"@en;
+    qb:hierarchyRoot 
+      &lt;http://data.ordnancesurvey.co.uk/id/7000000000041427&gt;, # South West
+      &lt;http://data.ordnancesurvey.co.uk/id/7000000000041426&gt;, # West Midlands
+      &lt;http://data.ordnancesurvey.co.uk/id/7000000000041421&gt;, # South East
+      &lt;http://data.ordnancesurvey.co.uk/id/7000000000041430&gt;, # Yorkshire &amp; the Humber
+      &lt;http://data.ordnancesurvey.co.uk/id/7000000000041423&gt;, # East Midlands
+      &lt;http://data.ordnancesurvey.co.uk/id/7000000000041425&gt;, # Eastern
+      &lt;http://data.ordnancesurvey.co.uk/id/7000000000041428&gt;, # London
+      &lt;http://data.ordnancesurvey.co.uk/id/7000000000041431&gt;, # North West
+      &lt;http://data.ordnancesurvey.co.uk/id/7000000000041422&gt;, # North East
+      &lt;http://data.ordnancesurvey.co.uk/id/7000000000041424&gt;, # Wales
+      &lt;http://data.ordnancesurvey.co.uk/id/7000000000041429&gt;; # Scotland
+    qb:parentChildProperty  spatial:contains;
+    .
+
+eg:geoDimension a qb:DimensionProperty ;
+    qb:codeList eg:GBgeoHierarchy .</pre></div>
+
+<p>Note that in some cases  the hierarchy to be reused may only have a
+  property relating child concepts to parent concepts. This situation
+  is handled by declaring
+  the <code><a href="#dfn-qb-parentchildproperty" class="internalDFN">qb:parentChildProperty</a></code> to be
+  the <code>owl:inverseOf</code> of the child-to-parent property. For
+  example:</p>
+
+<div class="example"><div class="example-title"><span>Example 17</span></div><pre class="example">@prefix spatial: &lt;http://data.ordnancesurvey.co.uk/ontology/spatialrelations/&gt; .
+
+eg:GBgeoHierarchy a qb:HierarchicalCodeList;
+    qb:parentChildProperty  [owl:inverseOf spatial:within] .</pre></div>
+ 
+<p>Future extensions of Data Cube may support additional sub classes
+  of <code><a href="#dfn-qb-hierarchicalcodelist" class="internalDFN">qb:HierarchicalCodeList</a></code>, for example to
+  declare hierarchies in which each parent is a disjoint union of its children.</p>
+
+</section>
+
+<section id="schemes-aggregation">  
+<h3><span class="secno">8.4 </span>Aggregation</h3>
+
+<p>The use of SKOS, or non-SKOS, hierarchies makes it possible to publish aggregated
+statistics for the non-leaf concepts in the hierarchy. The Data Cube vocabulary itself imposes
+no constraints on how such aggregation is done. Indeed in statistical applications the
+appropriate statistical corrections to make to aggregated values may be non-trivial and dependent on 
+the data and precise analysis methodology. Similarly in other
+  applications such as OLAP a number of different aggregation operators are commonly used.
+</p>
+
+<p>Vocabulary terms to represent the aggregation operations employed within a given dataset, and how one dataset 
+might be derived from another, are not supported in this version of the Data Cube specification. This
+area may be addressed by future extensions to Data Cube.</p>
+</section>
+
+</section>
+
+
+<section id="metadata">
+<!--OddPage--><h2><span class="secno">9. </span>DataSet metadata</h2>
+
+<p>DataSets should be marked up with metadata to support discovery, presentation and
+  processing. Dublin Core Terms [<cite><a class="bibref" href="#bib-DC11">DC11</a></cite>] <em class="rfc2119" title="should">should</em> be used
+  for representing the key metadata annotations commonly needed for
+  DataSets. The RDFS terms for display label (<code>rdfs:label</code>)
+  descriptive comment (<code>rdfs:comment</code>) <em class="rfc2119" title="should">should</em> be given as
+  well for compatibility with earlier versions of Data Cube and common
+  RDF practice.
+</p>
+
+<p>The recommend core set of metadata terms is:</p>
+<ul>
+  <li><code>dct:title</code></li>
+  <li><code>rdfs:label</code> - may be same as <code>dct:title</code></li>
+  <li><code>dct:description</code></li>
+  <li><code>rdfs:comment</code> - may be same as <code>dct:description</code></li>
+  <li><code>dct:issued</code></li>
+  <li><code>dct:modified</code></li>
+  <li><code>dct:subject</code></li>
+  <li><code>dct:publisher</code></li>
+  <li><code>dct:license</code></li>
+</ul>
+
+<p>Other documents, notably [<cite><a class="bibref" href="#bib-DCAT">DCAT</a></cite>], provide additional
+  recommendations for metadata terms for data sets
+  which may be used for describing Data Cube DataSets.</p>
+  
+<section id="metadata-categorization">
+<h3><span class="secno">9.1 </span>Categorizing a data set</h3>
+
+<p>Publishers of statistics often categorize their data sets into different statistical 
+domains, such as <em>Education</em>, <em>Labour</em>, or <em>Transportation</em>.
+We encourage use of <code>dct:subject</code> to record such a classification of
+a whole data set.
+The classification terms can include coarse grained classifications, such
+as the List of Subject-matter Domains from the SDMX Content-oriented Guidelines, 
+and fine grained classifications to support discovery of data sets.</p>
+
+<p>The classification schemes are typically represented using the SKOS vocabulary. For 
+convenience the SMDX Subject-matter Domains have been encoded as a SKOS concept scheme
+at <a href="http://purl.org/linked-data/sdmx/2009/subject">http://purl.org/linked-data/sdmx/2009/subject#</a>.</p>
+
+<p>Thus our sample dataset might be marked up by:</p>
+
+<div class="example"><div class="example-title"><span>Example 18</span></div><pre class="example">eg:dataset1 a qb:DataSet;
+    rdfs:label      "Life expectancy"@en;
+    dct:title       "Life expectancy"@en;
+    rdfs:comment    "Life expectancy within Welsh Unitary authorities - extracted from Stats Wales"@en;
+    dct:description "Life expectancy within Welsh Unitary authorities - extracted from Stats Wales"@en;
+    dct:issued      "2010-08-11"^^xsd:date;
+    dct:subject
+        sdmx-subject:3.2 ,      # regional and small area statistics
+        sdmx-subject:1.4 ,      # Health
+        ex:wales;               # Wales
+    ...</pre></div>
+
+<p>where <code>eg:Wales</code> is a <code>skos:Concept</code> drawn from an appropriate controlled
+vocabulary for places.</p>
+</section>
+
+
+<section id="metadata-publishers">
+<h3><span class="secno">9.2 </span>Describing publishers</h3>
+
+<p>The organization that publishes a dataset should be recorded as part of the dataset metadata.
+Again we recommend use of the Dublin Core term <code>dct:publisher</code> for this.
+The organization should be represented as an instance of <code>foaf:Agent</code>, or
+some more specific subclass such as <code>org:Organization</code> [<cite><a class="bibref" href="#bib-ORG">ORG</a></cite>].</p>
+
+<div class="example"><div class="example-title"><span>Example 19</span></div><pre class="example">eg:dataset1 a qb:DataSet;
+    dct:publisher &lt;http://example.com/meta#organization&gt; .
+    
+&lt;http://example.com/meta#organization&gt; a org:Organization, foaf:Agent;
+    rdfs:label "Example org" .    </pre></div>
+
+<p>Extension vocabularies may provide additional metadata properties and may impose
+ constraints on what metadata must be provided.</p>
+</section>
+
+</section>
+
+<section id="normalize">
+<!--OddPage--><h2><span class="secno">10. </span>Abbreviated and normalized data cubes</h2>
+
+<p>In normal form then the <code><a href="#dfn-qb-observation" class="internalDFN">qb:Observation</a></code>s 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 id="dfn-normalized">normalized</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 normalized representation
+incurs overheads in transmission and storage of Data Cubes which may
+be problematic in some settings. Note that abbreviated form is
+  provided as an option and there is requirement that it be used. In
+  many settings standard compression techniques can eliminate much of the
+  overhead of normalized form.
+</p>
+
+<p>To address this the Data Cube vocabulary supports a notion of
+an <em><dfn id="dfn-abbreviated">abbreviated</dfn></em> format in which component
+properties may be <em><dfn id="dfn-attached">attached</dfn></em> to other levels in the
+Data Cube.  Specifically they may be attached to
+a <code><a href="#dfn-qb-dataset" class="internalDFN">qb:DataSet</a></code> or <code><a href="#dfn-qb-slice" class="internalDFN">qb:Slice</a></code>.
+In those cases the attached property is taken to be applied to all
+the <code><a href="#dfn-qb-observation" class="internalDFN">qb:Observation</a></code> instances associated with that
+attachment point. For illustration
+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>It is also possible to attach attributes to a <code><a href="#dfn-qb-measureproperty" class="internalDFN">qb:MeasureProperty</a></code>
+ in which case the attribute is intended to apply only to that property and not
+ to the observations in which that property occurs.</p>
+
+<section id="normalize-algorithm">
+<h3><span class="secno">10.1 </span>Normalization algorithm</h3>
+
+<div class="note"><div class="note-title"><span>Note</span></div><div class="">
+This section is At Risk. The working group believes this formulation to 
+be correct and compatible with earlier versions of the Data Cube vocabulary.
+However as a new addition it has not received as much
+scrutiny as other parts of the specification. If problems are uncovered
+during the Candidate Recommendation process the working group may retract all or part of this section. 
+</div></div>
+
+<p>We define these notions by means of a transformation algorithm
+  which can normalize an abbreviated Data Cube. We express this transformation using the SPARQL 1.1
+  Update language [<cite><a class="bibref" href="#bib-SPARQL-UPDATE-11">SPARQL-UPDATE-11</a></cite>]. Use of this notation does not imply that
+  the transformation must be implemented this way. Information
+  exchanges using Data Cube may retain data in abbreviated form and
+  use other techniques such as query rewriting to ease access, may
+  implement the normalization algorithm by other means or may handle
+  all data in normalized form or any mix of these.</p>
+
+
+<p>The normalization algorithm comprises two sets of SPARQL Update
+  operations which should be applied in turn to a SPARQL Dataset in which the
+  default graph contains the Data Cube RDF graph to be normalized.</p>
+
+<p>The first update operation performs selective type and property closure
+  operations. These serve two purposes. They ensure
+  that <code>rdf:type</code> assertions on instances 
+  of <code><a href="#dfn-qb-observation" class="internalDFN">qb:Observation</a></code> and <code><a href="#dfn-qb-slice" class="internalDFN">qb:Slice</a></code>
+  may be omitted in an abbreviated Data Cube. They also simplify 
+  the second set of update operations by expanding
+  the sub properties of <code><a href="#dfn-qb-componentproperty-1" class="internalDFN">qb:componentProperty</a></code>
+  (specifically <code><a href="#dfn-qb-dimension" class="internalDFN">qb:dimension</a></code>,  <code><a href="#dfn-qb-measure" class="internalDFN">qb:measure</a></code>
+  and <code><a href="#dfn-qb-attribute" class="internalDFN">qb:attribute</a></code>).</p>
+
+<table class="bordered-table">
+  <thead>
+   <tr><th>Phase 1: Type and property closure</th></tr>
+  </thead>
+  <tbody><tr><td>
+<pre>PREFIX rdf:            &lt;http://www.w3.org/1999/02/22-rdf-syntax-ns#&gt;
+PREFIX qb:             &lt;http://purl.org/linked-data/cube#&gt;
+
+INSERT {
+    ?o rdf:type qb:Observation .
+} WHERE {
+    [] qb:observation ?o .
+};
+
+INSERT {
+    ?o rdf:type qb:Observation .
+} WHERE {
+    ?o qb:dataSet [] .
+};
+
+INSERT {
+    ?s rdf:type qb:Slice .
+} WHERE {
+    [] qb:slice ?s.
+};
+
+INSERT {
+    ?cs qb:componentProperty ?p .
+    ?p  rdf:type qb:DimensionProperty .
+} WHERE {
+    ?cs qb:dimension ?p .
+};
+
+INSERT {
+    ?cs qb:componentProperty ?p .
+    ?p  rdf:type qb:MeasureProperty .
+} WHERE {
+    ?cs qb:measure ?p .
+};
+
+INSERT {
+    ?cs qb:componentProperty ?p .
+    ?p  rdf:type qb:AttributeProperty .
+} WHERE {
+    ?cs qb:attribute ?p .
+}
+</pre>
+  </td></tr></tbody>
+</table>
+
+
+<p>These closure operations are implied by the RDFS semantics of the
+  Data Cube vocabulary. Data Cube processors <em class="rfc2119" title="may">may</em> apply full RDFS
+  closure in place of the update operation defined here.</p>
+
+<p>The second update operation checks the components of the data
+  structure definition of the data set for declared attachment levels.
+  For each of the possible attachments levels it looks for occurrences
+  of that component to be pushed down to the corresponding
+  observations. 
+</p>
+
+<table class="bordered-table">
+  <thead>
+   <tr><th>Phase 2: Push down attachment levels</th></tr>
+  </thead>
+  <tbody><tr><td>
+<pre>PREFIX qb:             &lt;http://purl.org/linked-data/cube#&gt;
+
+# Dataset attachments
+INSERT {
+    ?obs  ?comp ?value
+} WHERE {
+    ?spec    qb:componentProperty ?comp ;
+             qb:componentAttachment qb:DataSet .
+    ?dataset qb:structure [qb:component ?spec];
+             ?comp ?value .
+    ?obs     qb:dataSet ?dataset.
+};
+
+# Slice attachments
+INSERT {
+    ?obs  ?comp ?value
+} WHERE {
+    ?spec    qb:componentProperty ?comp;
+             qb:componentAttachment qb:Slice .
+    ?dataset qb:structure [qb:component ?spec];
+             qb:slice ?slice .
+    ?slice ?comp ?value;
+           qb:observation ?obs .
+};
+
+# Dimension values on slices
+INSERT {
+    ?obs  ?comp ?value
+} WHERE {
+    ?spec    qb:componentProperty ?comp .
+    ?comp a  qb:DimensionProperty .
+    ?dataset qb:structure [qb:component ?spec];
+             qb:slice ?slice .
+    ?slice ?comp ?value;
+           qb:observation ?obs .
+}
+</pre>
+  </td></tr></tbody>
+</table>
+
+
+</section>
+
+</section>
+
+<section id="wf">
+<!--OddPage--><h2><span class="secno">11. </span>Well-formed cubes</h2>
+
+<div class="note"><div class="note-title"><span>Note</span></div><div class="">
+This section is At Risk. The working group believes these criteria to
+be correct and compatible with earlier versions of the Data Cube vocabulary.
+However as a new addition they have not received as much
+scrutiny as other parts of the specification. If problems are uncovered
+during the Candidate Recommendation process the working group may retract all or part of this section. 
+</div></div>
+
+<p>An instance of an RDF Data Cube should conform to a set of
+  integrity constraints which we define in this section.</p>
+
+<p>A <dfn id="dfn-well-formed">well-formed</dfn> RDF Data Cube is an a RDF graph describing
+  one or more instances of <code><a href="#dfn-qb-dataset" class="internalDFN">qb:DataSet</a></code> for which
+  each of the integrity checks defined here passes.</p>
+
+<p>A <dfn id="dfn-well-formed-abbreviated">well-formed abbreviated</dfn> RDF Data Cube is an a RDF
+  graph which, when expanded using
+  the <a href="#normalize-algorithm">normalization algorithm</a>,
+  yields a <a>well-formed RDF Data Cube</a>.</p>
+
+<section id="wf-rules">
+<h3><span class="secno">11.1 </span>Integrity constraints</h3>
+
+<p>Each integrity constraint is expressed as narrative prose and, where possible, a SPARQL
+  [<cite><a class="bibref" href="#bib-SPARQL-QUERY-11">SPARQL-QUERY-11</a></cite>] ASK query or query template. If the ASK query  is applied to an RDF graph then it
+  will return <em>true</em> if that graph contains one or more Data Cube instances which
+  violate the corresponding constraint.
+</p>
+<p>
+  Using SPARQL queries to
+  express the integrity constraints does not imply that integrity
+  checking must be performed this way. Implementations are free
+  to use alternative query formulations or alternative implementation
+  techniques to perform equivalent checks. </p>
+
+<p>Each integrity constraint query assumes the following set of prefix bindings:</p>
+<pre>PREFIX rdf:     &lt;http://www.w3.org/1999/02/22-rdf-syntax-ns#&gt;
+PREFIX rdfs:    &lt;http://www.w3.org/2000/01/rdf-schema#&gt;
+PREFIX skos:    &lt;http://www.w3.org/2004/02/skos/core#&gt;
+PREFIX qb:      &lt;http://purl.org/linked-data/cube#&gt;
+PREFIX xsd:     &lt;http://www.w3.org/2001/XMLSchema#&gt;
+PREFIX owl:     &lt;http://www.w3.org/2002/07/owl#&gt;
+</pre>
+
+<p>The complete set of constraints is listed below.</p>
+
+<h3 id="ic-0">IC-0. Datatype consistency</h3>
+<p>
+The RDF graph must be consistent under RDF D-entailment [<cite><a class="bibref" href="#bib-RDF-MT">RDF-MT</a></cite>]
+using a datatype map containing all the datatypes used within the graph. 
+</p>
+
+<h3 id="ic-1">IC-1.  Unique DataSet</h3>
+<p>
+Every <code><a href="#dfn-qb-observation" class="internalDFN">qb:Observation</a></code> has exactly one associated <code><a href="#dfn-qb-dataset" class="internalDFN">qb:DataSet</a></code>.
+</p> 
+<table class="bordered-table">
+  <tbody>
+    <tr><td><pre>ASK {
+  {
+    # Check observation has a data set
+    ?obs a qb:Observation .
+    FILTER NOT EXISTS { ?obs qb:dataSet ?dataset1 . }
+  } UNION {
+    # Check has just one data set
+    ?obs a qb:Observation ;
+       qb:dataSet ?dataset1, ?dataset2 .
+    FILTER (?dataset1 != ?dataset2)
+  }
+}
+    </pre></td></tr>
+  </tbody>
+</table> 
+
+<h3 id="ic-2">IC-2. Unique DSD</h3>
+<p>
+Every <code><a href="#dfn-qb-dataset" class="internalDFN">qb:DataSet</a></code> has exactly one associated <code><a href="#dfn-qb-datastructuredefinition" class="internalDFN">qb:DataStructureDefinition</a></code>.
+</p>
+<table class="bordered-table">
+  <tbody> 
+    <tr><td><pre>ASK {
+  {
+    # Check dataset has a dsd
+    ?dataset a qb:DataSet .
+    FILTER NOT EXISTS { ?dataset qb:structure ?dsd . }
+  } UNION { 
+    # Check has just one dsd
+    ?dataset a qb:DataSet ;
+       qb:structure ?dsd1, ?dsd2 .
+    FILTER (?dsd1 != ?dsd2)
+  }
+}
+    </pre></td></tr>
+  </tbody>
+</table>
+
+<h3 id="ic-3">IC-3. DSD includes measure</h3>
+<p>
+Every <code><a href="#dfn-qb-datastructuredefinition" class="internalDFN">qb:DataStructureDefinition</a></code> must include at least one declared measure.
+</p>
+<table class="bordered-table">
+  <tbody>
+    <tr><td><pre>ASK {
+  ?dsd a qb:DataStructureDefinition .
+  FILTER NOT EXISTS { ?dsd qb:component [qb:componentProperty [a qb:MeasureProperty]] }
+}
+    </pre></td></tr>
+  </tbody>
+</table>
+
+<h3 id="ic-4">IC-4. Dimensions have range</h3>
+<p>
+Every dimension declared in a <code><a href="#dfn-qb-datastructuredefinition" class="internalDFN">qb:DataStructureDefinition</a></code> must have a declared <code><a>rdfs:range</a></code>.
+</p>
+<table class="bordered-table">
+  <tbody>
+    <tr><td><pre>ASK {
+  ?dim a qb:DimensionProperty .
+  FILTER NOT EXISTS { ?dim rdfs:range [] }
+}
+    </pre></td></tr>
+  </tbody>
+</table>
+
+<h3 id="ic-5">IC-5. Concept dimensions have code lists</h3>
+<p>
+Every dimension with range <code><a>skos:Concept</a></code> must have a <code><a href="#dfn-qb-codelist" class="internalDFN">qb:codeList</a></code>.
+</p>
+<table class="bordered-table">
+  <tbody>
+    <tr><td><pre>ASK {
+  ?dim a qb:DimensionProperty ;
+       rdfs:range skos:Concept .
+  FILTER NOT EXISTS { ?dim qb:codeList [] }
+}
+    </pre></td></tr>
+  </tbody>
+</table>
+
+<h3 id="ic-6">IC-6. Only attributes may be optional</h3>
+<p>
+The only components of
+a <code><a href="#dfn-qb-datastructuredefinition" class="internalDFN">qb:DataStructureDefinition</a></code> that may be marked as
+optional, using <code><a href="#dfn-qb-componentrequired" class="internalDFN">qb:componentRequired</a></code> are attributes.
+</p>
+
+<table class="bordered-table">
+  <tbody>
+    <tr><td><pre>ASK {
+  ?dsd qb:component ?componentSpec .
+  ?componentSpec qb:componentRequired "false"^^xsd:boolean ;
+                 qb:componentProperty ?component .
+  FILTER NOT EXISTS { ?component a qb:AttributeProperty }
+}
+    </pre></td></tr>
+  </tbody>
+</table>
+
+<h3 id="ic-7">IC-7. Slice Keys must be declared</h3>
+<p>
+Every <code><a href="#dfn-qb-slicekey" class="internalDFN">qb:SliceKey</a></code> must be associated with a <code><a href="#dfn-qb-datastructuredefinition" class="internalDFN">qb:DataStructureDefinition</a></code>.
+</p>
+
+<table class="bordered-table">
+  <tbody>
+    <tr><td><pre>ASK {
+    ?sliceKey a qb:SliceKey .
+    FILTER NOT EXISTS { [a qb:DataStructureDefinition] qb:sliceKey ?sliceKey }
+}
+    </pre></td></tr>
+  </tbody>
+</table>
+
+<h3 id="ic-8">IC-8. Slice Keys consistent with DSD</h3>
+<p>
+Every <code><a href="#dfn-qb-componentproperty-1" class="internalDFN">qb:componentProperty</a></code> on a <code><a href="#dfn-qb-slicekey" class="internalDFN">qb:SliceKey</a></code> must also be declared as a <code><a href="#dfn-qb-component" class="internalDFN">qb:component</a></code> of the associated <code><a href="#dfn-qb-datastructuredefinition" class="internalDFN">qb:DataStructureDefinition</a></code>.
+</p>
+
+<table class="bordered-table">
+  <tbody>
+    <tr><td><pre>ASK {
+  ?slicekey a qb:SliceKey;
+      qb:componentProperty ?prop .
+  ?dsd qb:sliceKey ?sliceKey .
+  FILTER NOT EXISTS { ?dsd qb:component [qb:componentProperty ?prop] }
+}
+    </pre></td></tr>
+  </tbody>
+</table>
+
+<h3 id="ic-9">IC-9. Unique slice structure</h3>
+<p>
+Each <code><a href="#dfn-qb-slice" class="internalDFN">qb:Slice</a></code> must have exactly one associated <code><a href="#dfn-qb-slicestructure" class="internalDFN">qb:sliceStructure</a></code>.
+</p>
+
+<table class="bordered-table">
+  <tbody>
+    <tr><td><pre>ASK {
+  {
+    # Slice has a key
+    ?slice a qb:Slice .
+    FILTER NOT EXISTS { ?slice qb:sliceStructure ?key }
+  } UNION {
+    # Slice has just one key
+    ?slice a qb:Slice ;
+           qb:sliceStructure ?key1, ?key2;
+    FILTER (?key1 != ?key2)
+  }
+}
+    </pre></td></tr>
+  </tbody>
+</table>
+
+
+<h3 id="ic-10">IC-10. Slice dimensions complete</h3>
+<p>
+Every <code><a href="#dfn-qb-slice" class="internalDFN">qb:Slice</a></code> must have a value for every dimension declared in its <code><a href="#dfn-qb-slicestructure" class="internalDFN">qb:sliceStructure</a></code>.
+</p>
+<table class="bordered-table">
+  <tbody>
+    <tr><td><pre>ASK {
+  ?slice qb:sliceStructure [qb:componentProperty ?dim] .
+  FILTER NOT EXISTS { ?slice ?dim [] }
+}
+    </pre></td></tr>
+  </tbody>
+</table>
+
+<h3 id="ic-11">IC-11. All dimensions required</h3>
+<p>
+Every <code><a href="#dfn-qb-observation" class="internalDFN">qb:Observation</a></code> has a value for each dimension declared in its associated <code><a href="#dfn-qb-datastructuredefinition" class="internalDFN">qb:DataStructureDefinition</a></code>.
+</p>
+
+<table class="bordered-table">
+  <tbody>
+    <tr><td><pre>ASK {
+    ?obs qb:dataSet/qb:structure/qb:component/qb:componentProperty ?dim .
+    ?dim a qb:DimensionProperty;
+    FILTER NOT EXISTS { ?obs ?dim [] }
+}
+    </pre></td></tr>
+  </tbody>
+</table>
+
+<h3 id="ic-12">IC-12. No duplicate observations</h3>
+<p>
+No two <code><a href="#dfn-qb-observation" class="internalDFN">qb:Observation</a></code>s in the same <code><a href="#dfn-qb-dataset" class="internalDFN">qb:DataSet</a></code> may have the same value for all dimensions.
+</p>
+<table class="bordered-table">
+  <tbody>
+    <tr><td><pre>ASK {
+  FILTER( ?allEqual )
+  {
+    # For each pair of observations test if all the dimension values are the same
+    SELECT (MIN(?equal) AS ?allEqual) WHERE {
+        ?obs1 qb:dataSet ?dataset .
+        ?obs2 qb:dataSet ?dataset .
+        FILTER (?obs1 != ?obs2)
+        ?dataset qb:structure/qb:component/qb:componentProperty ?dim .
+        ?dim a qb:DimensionProperty .
+        ?obs1 ?dim ?value1 .
+        ?obs2 ?dim ?value2 .
+        BIND( ?value1 = ?value2 AS ?equal)
+    } GROUP BY ?obs1 ?obs2
+  }
+}
+    </pre></td></tr>
+  </tbody>
+</table>
+
+<h3 id="ic-13">IC-13. Required attributes</h3>
+<p>
+Every <code><a href="#dfn-qb-observation" class="internalDFN">qb:Observation</a></code> has a value for each declared attribute that is marked as required.
+</p>
+<table class="bordered-table">
+  <tbody>
+    <tr><td><pre>ASK {
+    ?obs qb:dataSet/qb:structure/qb:component ?component .
+    ?component qb:componentRequired "true"^^xsd:boolean ;
+               qb:componentProperty ?attr .
+    FILTER NOT EXISTS { ?obs ?attr [] }
+}
+    </pre></td></tr>
+  </tbody>
+</table>
+
+<h3 id="ic-14">IC-14. All measures present</h3>
+<p>
+In a <code><a href="#dfn-qb-dataset" class="internalDFN">qb:DataSet</a></code> which does not use a <a href="#dfn-measure-dimension" class="internalDFN">Measure dimension</a> then each individual <code><a href="#dfn-qb-observation" class="internalDFN">qb:Observation</a></code> must have a value for every declared measure.
+</p>
+
+<table class="bordered-table">
+  <tbody>
+    <tr><td><pre>ASK {
+    # Observation in a non-measureType cube
+    ?obs qb:dataSet/qb:structure ?dsd .
+    FILTER NOT EXISTS { ?dsd qb:component/qb:componentProperty qb:measureType }
+
+    # verify every measure is present
+    ?dsd qb:component/qb:componentProperty ?measure .
+    ?measure a qb:MeasureProperty;
+    FILTER NOT EXISTS { ?obs ?measure [] }
+}
+    </pre></td></tr>
+  </tbody>
+</table>
+
+<h3 id="ic-15">IC-15. Measure dimension consistent</h3>
+<p>
+In a <code><a href="#dfn-qb-dataset" class="internalDFN">qb:DataSet</a></code> which uses a <a href="#dfn-measure-dimension" class="internalDFN">Measure dimension</a> then each <code><a href="#dfn-qb-observation" class="internalDFN">qb:Observation</a></code> must have a value for the measure corresponding to its given <code><a href="#dfn-qb-measuretype" class="internalDFN">qb:measureType</a></code>.
+</p>
+<table class="bordered-table">
+  <tbody>
+    <tr><td><pre>ASK {
+    # Observation in a measureType-cube
+    ?obs qb:dataSet/qb:structure ?dsd ;
+         qb:measureType ?measure .
+    ?dsd qb:component/qb:componentProperty qb:measureType .
+    # Must have value for its measureType
+    FILTER NOT EXISTS { ?obs ?measure [] }
+}
+    </pre></td></tr>
+  </tbody>
+</table>
+
+<h3 id="ic-16">IC-16. Single measure on measure dimension observation</h3>
+<p>
+In a <code><a href="#dfn-qb-dataset" class="internalDFN">qb:DataSet</a></code> which uses a <a href="#dfn-measure-dimension" class="internalDFN">Measure dimension</a> then each <code><a href="#dfn-qb-observation" class="internalDFN">qb:Observation</a></code> must only have a value for one measure (by IC-15 this will be the measure corresponding to its <code><a href="#dfn-qb-measuretype" class="internalDFN">qb:measureType</a></code>).
+</p>
+<table class="bordered-table">
+  <tbody>
+    <tr><td><pre>ASK {
+    # Observation with measureType
+    ?obs qb:dataSet/qb:structure ?dsd ;
+         qb:measureType ?measure ;
+         ?omeasure [] .
+    # Any measure on the observation
+    ?dsd qb:component/qb:componentProperty qb:measureType ;
+         qb:component/qb:componentProperty ?omeasure .
+    ?omeasure a qb:MeasureProperty .
+    # Must be the same as the measureType
+    FILTER (?omeasure != ?measure)
+}
+    </pre></td></tr>
+  </tbody>
+</table>
+
+<h3 id="ic-17">IC-17. All measures present in measures dimension cube </h3>
+<p>
+In a <code><a href="#dfn-qb-dataset" class="internalDFN">qb:DataSet</a></code> which uses a <a href="#dfn-measure-dimension" class="internalDFN">Measure dimension</a> then if there is a Observation for some combination of non-measure dimensions then there must be other Observations with the same non-measure dimension values for each of the declared measures.
+</p>
+<table class="bordered-table">
+  <tbody>
+    <tr><td><pre>ASK {
+  {
+      # Count number of other measures found at each point 
+      SELECT ?numMeasures (COUNT(?obs2) AS ?count) WHERE {
+          {
+              # Find the DSDs and check how many measures they have
+              SELECT ?dsd (COUNT(?m) AS ?numMeasures) WHERE {
+                  ?dsd qb:component/qb:componentProperty ?m.
+                  ?m a qb:MeasureProperty .
+              } GROUP BY ?dsd
+          }
+        
+          # Observation in measureType cube
+          ?obs1 qb:dataSet/qb:structure ?dsd;
+                qb:dataSet ?dataset ;
+                qb:measureType ?m1 .
+    
+          # Other observation at same dimension value
+          ?obs2 qb:dataSet ?dataset ;
+                qb:measureType ?m2 .
+          FILTER NOT EXISTS { 
+              ?dsd qb:component/qb:componentProperty ?dim .
+              FILTER (?dim != qb:measureType)
+              ?dim a qb:DimensionProperty .
+              ?obs1 ?dim ?v1 . 
+              ?obs2 ?dim ?v2. 
+              FILTER (?v1 != ?v2)
+          }
+          
+      } GROUP BY ?obs1 ?numMeasures
+        HAVING (?count != ?numMeasures)
+  }
+}
+    </pre></td></tr>
+  </tbody>
+</table>
+
+<h3 id="ic-18">IC-18. Consistent data set links</h3>
+<p>
+If a <code><a href="#dfn-qb-dataset" class="internalDFN">qb:DataSet</a></code> D has a <code><a href="#dfn-qb-slice-1" class="internalDFN">qb:slice</a></code> S, and S has an <code><a href="#dfn-qb-observation-1" class="internalDFN">qb:observation</a></code> O, then the <code><a href="#dfn-qb-dataset-1" class="internalDFN">qb:dataSet</a></code> corresponding to O must be D.
+</p>
+<table class="bordered-table">
+  <tbody>
+    <tr><td><pre>ASK {
+    ?dataset qb:slice       ?slice .
+    ?slice   qb:observation ?obs .
+    FILTER NOT EXISTS { ?obs qb:dataSet ?dataset . }
+}
+    </pre></td></tr>
+  </tbody>
+</table>
+
+<h3 id="ic-19">IC-19. Codes from code list</h3>
+<p>
+If a dimension property has a <code><a href="#dfn-qb-codelist" class="internalDFN">qb:codeList</a></code>, then the value of the dimension property on every <code><a href="#dfn-qb-observation" class="internalDFN">qb:Observation</a></code> must be in the code list.
+</p>
+<p>The following integrity check queries must be applied to an RDF graph which contains the 
+definition of the code list as well as the Data Cube to be checked. In the case
+of a <code>skos:ConceptScheme</code> then each concept must be linked to the scheme using
+<code>skos:inScheme</code>. In the case of a <code>skos:Collection</code> then the
+collection must link to each concept (or to nested collections) using <code>skos:member</code>. If the
+collection uses <code>skos:memberList</code> then the entailment of <code>skos:member</code>
+values defined by <a href="http://www.w3.org/TR/2009/REC-skos-reference-20090818/#S36">S36</a>
+in [<cite><a class="bibref" href="#bib-SKOS-REFERENCE">SKOS-REFERENCE</a></cite>] must be materialized before this check is applied. </p>
+
+<table class="bordered-table">
+  <tbody>
+    <tr><td><pre>ASK {
+    ?obs qb:dataSet/qb:structure/qb:component/qb:componentProperty ?dim .
+    ?dim a qb:DimensionProperty ;
+        qb:codeList ?list .
+    ?list a skos:ConceptScheme .
+    ?obs ?dim ?v .
+    FILTER NOT EXISTS { ?v a skos:Concept ; skos:inScheme ?list }
+}
+
+ASK {
+    ?obs qb:dataSet/qb:structure/qb:component/qb:componentProperty ?dim .
+    ?dim a qb:DimensionProperty ;
+        qb:codeList ?list .
+    ?list a skos:Collection .
+    ?obs ?dim ?v .
+    FILTER NOT EXISTS { ?v a skos:Concept . ?list skos:member+ ?v }
+}
+    </pre></td></tr>
+  </tbody>
+</table>
+
+<h3 id="ic-20">IC-20. Codes from hierarchy</h3>
+<p>
+If a dimension property has
+a <code><a href="#dfn-qb-hierarchicalcodelist" class="internalDFN">qb:HierarchicalCodeList</a></code> with a
+non-blank <code><a href="#dfn-qb-parentchildproperty" class="internalDFN">qb:parentChildProperty</a></code> then the value of
+that dimension property on every <code><a href="#dfn-qb-observation" class="internalDFN">qb:Observation</a></code>
+must be reachable from a root of the hierarchy using zero or more hops along the <code><a href="#dfn-qb-parentchildproperty" class="internalDFN">qb:parentChildProperty</a></code> links.
+</p>
+<p>
+This check cannot be made by a simple fixed SPARQL query. Instead a
+query template is supplied. 
+An instance of the template should be generated
+for each <code><a href="#dfn-qb-hierarchicalcodelist" class="internalDFN">qb:HierarchicalCodeList</a></code> which has an IRI
+value for its  <code><a href="#dfn-qb-parentchildproperty" class="internalDFN">qb:parentChildProperty</a></code>.
+That is for each binding of <code>?p</code> in the following
+instantiation query:</p>
+<pre>SELECT ?p WHERE {
+    ?hierarchy a qb:HierarchicalCodeList ;
+                 qb:parentChildProperty ?p .
+    FILTER ( isIRI(?p) )
+}
+</pre>
+
+<p>The template is then instantiated by replacing the
+  string <code>$p</code> by the IRI found by the
+  instantiation query. The template is:</p>
+
+<table class="bordered-table">
+  <tbody>
+    <tr><td><pre>ASK {
+    ?obs qb:dataSet/qb:structure/qb:component/qb:componentProperty ?dim .
+    ?dim a qb:DimensionProperty ;
+        qb:codeList ?list .
+    ?list a qb:HierarchicalCodeList .
+    ?obs ?dim ?v .
+    FILTER NOT EXISTS { ?list qb:hierarchyRoot/&lt;$p&gt;* ?v }
+}
+    </pre></td></tr>
+  </tbody>
+</table>
+
+<h3 id="ic-21">IC-21. Codes from hierarchy (inverse)</h3>
+<p>
+If a dimension property has
+a <code><a href="#dfn-qb-hierarchicalcodelist" class="internalDFN">qb:HierarchicalCodeList</a></code> with an
+inverse <code><a href="#dfn-qb-parentchildproperty" class="internalDFN">qb:parentChildProperty</a></code> then the value of
+that dimension property on every <code><a href="#dfn-qb-observation" class="internalDFN">qb:Observation</a></code>
+must be reachable from a root of the hierarchy using zero or more hops along the inverse  <code><a href="#dfn-qb-parentchildproperty" class="internalDFN">qb:parentChildProperty</a></code> links.
+</p>
+
+<p>
+This check cannot be made by a simple fixed SPARQL query. Instead a
+query template is supplied. 
+An instance of the template should be generated
+for each <code><a href="#dfn-qb-hierarchicalcodelist" class="internalDFN">qb:HierarchicalCodeList</a></code> which has a blank-node
+value for its  <code><a href="#dfn-qb-parentchildproperty" class="internalDFN">qb:parentChildProperty</a></code>, with an 
+associated inverse property.
+That is for each binding of <code>?p</code> in the following
+instantiation query:</p>
+<pre>SELECT ?p WHERE {
+    ?hierarchy a qb:HierarchicalCodeList;
+                 qb:parentChildProperty ?pcp .
+    FILTER( isBlank(?pcp) )
+    ?pcp  owl:inverseOf ?p .
+    FILTER( isIRI(?p) )
+}
+</pre>
+
+<p>The template is then instantiated by replacing the
+  string <code>$p</code> by the IRI found by the
+  instantiation query. The template is:</p>
+
+<table class="bordered-table">
+  <tbody>
+    <tr><td><pre>ASK {
+    ?obs qb:dataSet/qb:structure/qb:component/qb:componentProperty ?dim .
+    ?dim a qb:DimensionProperty ;
+         qb:codeList ?list .
+    ?list a qb:HierarchicalCodeList .
+    ?obs ?dim ?v .
+    FILTER NOT EXISTS { ?list qb:hierarchyRoot/(^&lt;$p&gt;)* ?v }
+}
+    </pre></td></tr>
+  </tbody>
+</table>
+
+</section>
+
+</section>
+
+<section id="vocab-reference">
+<!--OddPage--><h2><span class="secno">12. </span>Vocabulary reference</h2>
+
+
+<section id="reference-datasets">
+<h3><span class="secno">12.1 </span>DataSets</h3>
+
+<p><em>See Section <a href="#datasets">Expressing data sets</a>.</em></p>
+
+<dl class="vocab_reference">
+
+  <dt id="ref_qb_DataSet">
+    <em>Class:</em> <code><dfn id="dfn-qb-dataset">qb:DataSet</dfn></code>
+    <em>Sub class of: </em>
+      <code><a href="#dfn-qb-attachable" class="internalDFN">qb:Attachable</a></code>
+    <em>Equivalent to: </em>
+      <code>scovo:Dataset</code>
+  </dt>
+ <dd>Represents a collection of observations, possibly organized into various slices, conforming to some common dimensional structure.</dd>
+</dl>
+</section>
+
+
+<section id="reference-observations">
+<h3><span class="secno">12.2 </span>Observations</h3>
+<p><em>See Section <a href="#datasets">Expressing data sets</a>.</em></p>
+
+<dl class="vocab_reference">
+
+  <dt id="ref_qb_Observation">
+    <em>Class:</em> <code><dfn id="dfn-qb-observation">qb:Observation</dfn></code>
+    <em>Sub class of: </em>
+      <code><a href="#dfn-qb-attachable" class="internalDFN">qb:Attachable</a></code>
+    <em>Equivalent to: </em>
+      <code>scovo:Item</code>
+  </dt>
+ <dd>A single observation in the cube, may have one or more associated measured values.</dd>
+
+  <dt id="ref_qb_dataSet_LC">
+    <em>Property:</em> <code><dfn id="dfn-qb-dataset-1">qb:dataSet</dfn></code>
+    ( <em>Domain:</em>
+    <code><a href="#dfn-qb-observation" class="internalDFN">qb:Observation</a></code>
+    -&gt; <em>Range:</em> 
+    <code><a href="#dfn-qb-dataset" class="internalDFN">qb:DataSet</a></code>
+  ) 
+  </dt>
+  <dd>Indicates the data set of which this observation is a part.</dd>
+
+  <dt id="ref_qb_observation_LC">
+    <em>Property:</em> <code><dfn id="dfn-qb-observation-1">qb:observation</dfn></code>
+    ( <em>Domain:</em>
+    <code><a href="#dfn-qb-observationgroup" class="internalDFN">qb:ObservationGroup</a></code>
+    -&gt; <em>Range:</em> 
+    <code><a href="#dfn-qb-observation" class="internalDFN">qb:Observation</a></code>
+  ) 
+  </dt>
+  <dd>Indicates a observation contained within this slice of the data set.</dd>
+</dl>
+</section>
+
+
+<section id="reference-slices">
+<h3><span class="secno">12.3 </span>Slices</h3>
+<p><em>See Section <a href="#slices">Slices</a>.</em></p>
+
+<dl class="vocab_reference">
+
+  <dt id="ref_qb_ObservationGroup">
+    <em>Class:</em> <code><dfn id="dfn-qb-observationgroup">qb:ObservationGroup</dfn></code>
+  </dt>
+ <dd>A, possibly arbitrary, group of observations.</dd>
+
+
+  <dt id="ref_qb_Slice">
+    <em>Class:</em> <code><dfn id="dfn-qb-slice">qb:Slice</dfn></code>
+    <em>Sub class of: </em>
+      <code><a href="#dfn-qb-attachable" class="internalDFN">qb:Attachable</a></code>,
+      <code><a href="#dfn-qb-observationgroup" class="internalDFN">qb:ObservationGroup</a></code>
+  </dt>
+ <dd>Denotes a subset of a DataSet defined by fixing a subset of the dimensional values, component properties on the Slice.</dd>
+
+  <dt id="ref_qb_slice_LC">
+    <em>Property:</em> <code><dfn id="dfn-qb-slice-1">qb:slice</dfn></code>
+    ( <em>Domain:</em>
+    <code><a href="#dfn-qb-dataset" class="internalDFN">qb:DataSet</a></code>
+    -&gt; <em>Range:</em> 
+    <code><a href="#dfn-qb-slice" class="internalDFN">qb:Slice</a></code>;
+    <em>sub property of:</em>
+    <code><a href="#dfn-qb-observationgroup-1" class="internalDFN">qb:observationGroup</a></code>
+  ) 
+  </dt>
+  <dd>Indicates a subset of a DataSet defined by fixing a subset of the dimensional values.</dd>
+
+  <dt id="ref_qb_observationGroup">
+    <em>Property:</em> <code><dfn id="dfn-qb-observationgroup-1">qb:observationGroup</dfn></code>
+    ( <em>Domain:</em>
+    -&gt; <em>Range:</em> 
+    <code><a href="#dfn-qb-observationgroup" class="internalDFN">qb:ObservationGroup</a></code>
+  ) 
+  </dt>
+  <dd>Indicates a group of observations. The domain of this property is left open so that a group may be attached to different resources and need not be restricted to a single DataSet.</dd>
+
+</dl>
+</section>
+
+
+<section id="reference-components">
+<h3><span class="secno">12.4 </span>Dimensions, Attributes, Measures</h3>
+<p><em>See Section <a href="#dsd-dimensions">Dimensions, attributes and measures</a>.</em></p>
+
+<dl class="vocab_reference">
+
+  <dt id="ref_qb_Attachable">
+    <em>Class:</em> <code><dfn id="dfn-qb-attachable">qb:Attachable</dfn></code>
+  </dt>
+ <dd>Abstract superclass for everything that can have attributes and dimensions.</dd>
+
+  <dt id="ref_qb_ComponentProperty">
+    <em>Class:</em> <code><dfn id="dfn-qb-componentproperty">qb:ComponentProperty</dfn></code>
+    <em>Sub class of: </em>
+      <code>rdf:Property</code>
+  </dt>
+ <dd>Abstract super-class of all properties representing dimensions, attributes or measures.</dd>
+
+  <dt id="ref_qb_DimensionProperty">
+    <em>Class:</em> <code><dfn id="dfn-qb-dimensionproperty">qb:DimensionProperty</dfn></code>
+    <em>Sub class of: </em>
+      <code><a href="#dfn-qb-componentproperty" class="internalDFN">qb:ComponentProperty</a></code>,
+      <code><a href="#dfn-qb-codedproperty" class="internalDFN">qb:CodedProperty</a></code>
+  </dt>
+ <dd>The class of component properties which represent the dimensions of the cube.</dd>
+
+  <dt id="ref_qb_AttributeProperty">
+    <em>Class:</em> <code><dfn id="dfn-qb-attributeproperty">qb:AttributeProperty</dfn></code>
+    <em>Sub class of: </em>
+      <code><a href="#dfn-qb-componentproperty" class="internalDFN">qb:ComponentProperty</a></code>
+  </dt>
+ <dd>The class of component properties which represent attributes of observations in the cube, e.g. unit of measurement.</dd>
+
+  <dt id="ref_qb_MeasureProperty">
+    <em>Class:</em> <code><dfn id="dfn-qb-measureproperty">qb:MeasureProperty</dfn></code>
+    <em>Sub class of: </em>
+      <code><a href="#dfn-qb-componentproperty" class="internalDFN">qb:ComponentProperty</a></code>
+  </dt>
+ <dd>The class of component properties which represent the measured value of the phenomenon being observed.</dd>
+
+  <dt id="ref_qb_CodedProperty">
+    <em>Class:</em> <code><dfn id="dfn-qb-codedproperty">qb:CodedProperty</dfn></code>
+    <em>Sub class of: </em>
+      <code><a href="#dfn-qb-componentproperty" class="internalDFN">qb:ComponentProperty</a></code>
+  </dt>
+ <dd>Superclass of all coded component properties.</dd>
+</dl>
+</section>
+
+
+<section id="reference-component-properties">
+<h3><span class="secno">12.5 </span>Reusable general purpose component properties</h3>
+<p><em>See Section <a href="#dsd-mm-dim">Measure dimensions</a>.</em></p>
+
+<dl class="vocab_reference">
+
+  <dt id="ref_qb_measureType">
+    <em>Property:</em> <code><dfn id="dfn-qb-measuretype">qb:measureType</dfn></code>
+    ( <em>Domain:</em>
+    -&gt; <em>Range:</em> 
+    <code><a href="#dfn-qb-measureproperty" class="internalDFN">qb:MeasureProperty</a></code>
+  ) 
+  </dt>
+  <dd>Generic measure dimension, the value of this dimension indicates which measure (from the set of measures in the DSD) is being given by the observation.</dd>
+</dl>
+</section>
+
+
+<section id="reference-dsd">
+<h3><span class="secno">12.6 </span>Data Structure Definitions</h3>
+<p><em>See Section <a href="#dsd-dsd">ComponentSpecifications and DataStructureDefinitions</a>.</em></p>
+
+<dl class="vocab_reference">
+
+  <dt id="ref_qb_DataStructureDefinition">
+    <em>Class:</em> <code><dfn id="dfn-qb-datastructuredefinition">qb:DataStructureDefinition</dfn></code>
+    <em>Sub class of: </em>
+      <code><a href="#dfn-qb-componentset" class="internalDFN">qb:ComponentSet</a></code>
+  </dt>
+ <dd>Defines the structure of a DataSet or slice.</dd>
+
+  <dt id="ref_qb_structure">
+    <em>Property:</em> <code><dfn id="dfn-qb-structure">qb:structure</dfn></code>
+    ( <em>Domain:</em>
+    <code><a href="#dfn-qb-dataset" class="internalDFN">qb:DataSet</a></code>
+    -&gt; <em>Range:</em> 
+    <code><a href="#dfn-qb-datastructuredefinition" class="internalDFN">qb:DataStructureDefinition</a></code>
+  ) 
+  </dt>
+  <dd>Indicates the structure to which this data set conforms</dd>
+
+  <dt id="ref_qb_component">
+    <em>Property:</em> <code><dfn id="dfn-qb-component">qb:component</dfn></code>
+    ( <em>Domain:</em>
+    <code><a href="#dfn-qb-datastructuredefinition" class="internalDFN">qb:DataStructureDefinition</a></code>
+    -&gt; <em>Range:</em> 
+    <code><a href="#dfn-qb-componentspecification" class="internalDFN">qb:ComponentSpecification</a></code>
+  ) 
+  </dt>
+  <dd>Indicates a component specification which is included in the structure of the dataset.</dd>
+</dl>
+</section>
+
+
+<section id="reference-compspec">
+<h3><span class="secno">12.7 </span>Component specifications - for qualifying component use in a DSD</h3>
+<p><em>See Section <a href="#dsd-dsd">ComponentSpecifications and DataStructureDefinitions</a>.</em></p>
+
+<dl class="vocab_reference">
+
+  <dt id="ref_qb_ComponentSpecification">
+    <em>Class:</em> <code><dfn id="dfn-qb-componentspecification">qb:ComponentSpecification</dfn></code>
+    <em>Sub class of: </em>
+      <code><a href="#dfn-qb-componentset" class="internalDFN">qb:ComponentSet</a></code>
+  </dt>
+ <dd>Used to define properties of a component (attribute, dimension etc) which are specific to its usage in a DSD.</dd>
+
+  <dt id="ref_qb_ComponentSet">
+    <em>Class:</em> <code><dfn id="dfn-qb-componentset">qb:ComponentSet</dfn></code>
+  </dt>
+ <dd>Abstract class of things which reference one or more ComponentProperties</dd>
+
+  <dt id="ref_qb_componentProperty_LC">
+    <em>Property:</em> <code><dfn id="dfn-qb-componentproperty-1">qb:componentProperty</dfn></code>
+    ( <em>Domain:</em>
+    <code><a href="#dfn-qb-componentset" class="internalDFN">qb:ComponentSet</a></code>
+    -&gt; <em>Range:</em> 
+    <code><a href="#dfn-qb-componentproperty" class="internalDFN">qb:ComponentProperty</a></code>
+  ) 
+  </dt>
+  <dd>Indicates a ComponentProperty (i.e. attribute/dimension) expected on a DataSet, or a dimension fixed in a SliceKey.</dd>
+
+  <dt id="ref_qb_order">
+    <em>Property:</em> <code><dfn id="dfn-qb-order">qb:order</dfn></code>
+    ( <em>Domain:</em>
+    <code><a href="#dfn-qb-componentspecification" class="internalDFN">qb:ComponentSpecification</a></code>
+    -&gt; <em>Range:</em> 
+    <code>xsd:int</code>
+  ) 
+  </dt>
+  <dd>Indicates a priority order for the components of sets with this structure, used to guide presentations - lower order numbers come before higher numbers, un-numbered components come last.</dd>
+
+  <dt id="ref_qb_componentRequired">
+    <em>Property:</em> <code><dfn id="dfn-qb-componentrequired">qb:componentRequired</dfn></code>
+    ( <em>Domain:</em>
+    <code><a href="#dfn-qb-componentspecification" class="internalDFN">qb:ComponentSpecification</a></code>
+    -&gt; <em>Range:</em> 
+    <code>xsd:boolean</code>
+  ) 
+  </dt>
+  <dd>Indicates whether a component property is required (true) or optional (false) in the context of a DSD. Only applicable
+    to components corresponding to an attribute. Defaults to false (optional).</dd>
+
+  <dt id="ref_qb_componentAttachment">
+    <em>Property:</em> <code><dfn id="dfn-qb-componentattachment">qb:componentAttachment</dfn></code>
+    ( <em>Domain:</em>
+    <code><a href="#dfn-qb-componentspecification" class="internalDFN">qb:ComponentSpecification</a></code>
+    -&gt; <em>Range:</em> 
+    <code>rdfs:Class</code>
+  ) 
+  </dt>
+  <dd>Indicates the level at which the component property should be attached, this might be an qb:DataSet, qb:Slice or qb:Observation, or a qb:MeasureProperty.</dd>
+
+  <dt id="ref_qb_dimension">
+    <em>Property:</em> <code><dfn id="dfn-qb-dimension">qb:dimension</dfn></code>
+    ( <em>Domain:</em>
+    -&gt; <em>Range:</em> 
+    <code><a href="#dfn-qb-dimensionproperty" class="internalDFN">qb:DimensionProperty</a></code>
+    ; <em>sub property of: </em>
+    <code><a href="#dfn-qb-componentproperty-1" class="internalDFN">qb:componentProperty</a></code>
+  ) 
+  </dt>
+  <dd>An alternative to qb:componentProperty which makes explicit that the component is a dimension.</dd>
+
+  <dt id="ref_qb_measure">
+    <em>Property:</em> <code><dfn id="dfn-qb-measure">qb:measure</dfn></code>
+    ( <em>Domain:</em>
+    -&gt; <em>Range:</em> 
+    <code><a href="#dfn-qb-measureproperty" class="internalDFN">qb:MeasureProperty</a></code>
+    ; <em>sub property of: </em>
+    <code><a href="#dfn-qb-componentproperty-1" class="internalDFN">qb:componentProperty</a></code>
+  ) 
+  </dt>
+  <dd>An alternative to qb:componentProperty which makes explicit that the component is a measure.</dd>
+
+  <dt id="ref_qb_attribute">
+    <em>Property:</em> <code><dfn id="dfn-qb-attribute">qb:attribute</dfn></code>
+    ( <em>Domain:</em>
+    -&gt; <em>Range:</em> 
+    <code><a href="#dfn-qb-attributeproperty" class="internalDFN">qb:AttributeProperty</a></code>
+    ; <em>sub property of: </em>
+    <code><a href="#dfn-qb-componentproperty-1" class="internalDFN">qb:componentProperty</a></code>
+  ) 
+  </dt>
+  <dd>An alternative to qb:componentProperty which makes explicit that the component is a attribute.</dd>
+
+  <dt id="ref_qb_measureDimension">
+    <em>Property:</em> <code><dfn id="dfn-qb-measuredimension">qb:measureDimension</dfn></code>
+    ( <em>Domain:</em>
+    -&gt; <em>Range:</em> 
+    <code><a href="#dfn-qb-dimensionproperty" class="internalDFN">qb:DimensionProperty</a></code>
+    ; <em>sub property of: </em>
+    <code><a href="#dfn-qb-componentproperty-1" class="internalDFN">qb:componentProperty</a></code>
+  ) 
+  </dt>
+  <dd>An alternative to qb:componentProperty which makes explicit that the component is a measure dimension.</dd>
+</dl>
+</section>
+
+
+<section id="reference-slice-definitions">
+<h3><span class="secno">12.8 </span>Slice definitions</h3>
+<p><em>See Section <a href="#slices">Slices</a>.</em></p>
+
+<dl class="vocab_reference">
+
+  <dt id="ref_qb_SliceKey">
+    <em>Class:</em> <code><dfn id="dfn-qb-slicekey">qb:SliceKey</dfn></code>
+    <em>Sub class of: </em>
+      <code><a href="#dfn-qb-componentset" class="internalDFN">qb:ComponentSet</a></code>
+  </dt>
+ <dd>Denotes a subset of the component properties of a DataSet which are fixed in the corresponding slices.</dd>
+
+  <dt id="ref_qb_sliceStructure">
+    <em>Property:</em> <code><dfn id="dfn-qb-slicestructure">qb:sliceStructure</dfn></code>
+    ( <em>Domain:</em>
+    <code><a href="#dfn-qb-slice" class="internalDFN">qb:Slice</a></code>
+    -&gt; <em>Range:</em> 
+    <code><a href="#dfn-qb-slicekey" class="internalDFN">qb:SliceKey</a></code>
+  ) 
+  </dt>
+  <dd>Indicates the slice key corresponding to this slice.</dd>
+
+  <dt id="ref_qb_sliceKey_LC">
+    <em>Property:</em> <code><dfn id="dfn-qb-slicekey-1">qb:sliceKey</dfn></code>
+    ( <em>Domain:</em>
+    <code><a href="#dfn-qb-dataset" class="internalDFN">qb:DataSet</a></code>
+    -&gt; <em>Range:</em> 
+    <code><a href="#dfn-qb-slicekey" class="internalDFN">qb:SliceKey</a></code>
+  ) 
+  </dt>
+  <dd>Indicates a slice key which is used for slices in this dataset.</dd>
+</dl>
+</section>
+
+
+<section id="reference-concepts">
+<h3><span class="secno">12.9 </span>Concepts</h3>
+<p><em>See Section <a href="#schemes">Concept schemes and code lists</a>.</em></p>
+
+<dl class="vocab_reference">
+
+  <dt id="ref_qb_concept">
+    <em>Property:</em> <code><dfn id="dfn-qb-concept">qb:concept</dfn></code>
+    ( <em>Domain:</em>
+    <code><a href="#dfn-qb-componentproperty" class="internalDFN">qb:ComponentProperty</a></code>
+    -&gt; <em>Range:</em> 
+    <code>skos:Concept</code>
+  ) 
+  </dt>
+  <dd>Gives the concept which is being measured or indicated by a ComponentProperty.</dd>
+
+  <dt id="ref_qb_codeList">
+    <em>Property:</em> <code><dfn id="dfn-qb-codelist">qb:codeList</dfn></code>
+    ( <em>Domain:</em>
+    <code><a href="#dfn-qb-codedproperty" class="internalDFN">qb:CodedProperty</a></code>
+    -&gt; <em>Range:</em> 
+    <code>owl:unionOf(skos:ConceptScheme skos:Collection qb:HierarchicalCodeList)</code>
+  ) 
+  </dt>
+  <dd>Gives the code list associated with a CodedProperty.</dd>
+</dl></section>
+
+<section id="reference-nonskos-hierarchy">
+<h3><span class="secno">12.10 </span>Non-SKOS Hierarchies</h3>
+<p><em>See Section <a href="#schemes-hierarchy-nonskos">Non-SKOS hierarchies</a>.</em></p>
+
+<dl class="vocab_reference">
+
+  <dt id="ref_qb_HierarchicalCodeList">
+    <em>Class:</em> <code><dfn id="dfn-qb-hierarchicalcodelist">qb:HierarchicalCodeList</dfn></code>
+  </dt>
+ <dd>Represents a generalized hierarchy of concepts which can be used for coding. The hierarchy is defined by one or more roots together with a property which relates concepts in the hierarchy to their child concept .  The same concepts may be members of multiple hierarchies provided that different qb:parentChildProperty values are used for each hierarchy.</dd>
+  <dt id="ref_qb_hierarchyRoot">
+    <em>Property:</em> <code><dfn id="dfn-qb-hierarchyroot">qb:hierarchyRoot</dfn></code>
+    ( <em>Domain:</em>
+    <code><a href="#dfn-qb-hierarchicalcodelist" class="internalDFN">qb:HierarchicalCodeList</a></code>
+    ) 
+  </dt>
+  <dd>Specifies a root of the hierarchy. A hierarchy may have multiple roots but must have at least one. </dd>
+
+  <dt id="ref_qb_parentChildProperty">
+    <em>Property:</em> <code><dfn id="dfn-qb-parentchildproperty">qb:parentChildProperty</dfn></code>
+    ( <em>Domain:</em>
+    <code><a href="#dfn-qb-hierarchicalcodelist" class="internalDFN">qb:HierarchicalCodeList</a></code>
+    -&gt; <em>Range:</em> 
+    <code>rdf:Property</code>
+  ) 
+  </dt>
+  <dd>Specifies a property which relates a parent concept in the hierarchy to a child concept. Note that a child may have more than one parent.</dd>
+
+</dl>
+</section>
+
+</section>
+
+
+<section id="acknowledgements" class="appendix">
+<!--OddPage--><h2><span class="secno">A. </span>Acknowledgements</h2>
+
+<p>This work is based on a collaboration that was initiated in a
+workshop on Publishing statistical datasets in SDMX and the semantic
+web, hosted by ONS in Sunningdale, United Kingdom in February 2010 and
+continued at the ODaF 2010 workshop in Tilburg. The authors would like
+to thank all the participants at those workshops for their input into
+this work but especially Arofan Gregory for his patient
+explanations of SDMX and insight in the need and requirements 
+for a core Data Cube representation.</p>
+
+<p>The editors would like to thank John Sheridan for his comments,
+suggestions and support for the original work.</p>
+
+<p>Many individuals provided valuable comments on this specification
+as it made its way through the <abbr title="World
+  Wide Web Consortium">W3C</abbr> process. We would like to 
+especially acknowledge the contributions of
+Benedikt Kaempgen, Sarven Capadisli and Curran  Kelleher.</p>
+
+</section>
+
+<section id="change-history" class="appendix">
+<!--OddPage--><h2><span class="secno">B. </span>Change history </h2>
+
+<p>Changes
+  since <a href="http://www.w3.org/TR/2013/WD-vocab-data-cube-20130312/"><abbr title="World
+  Wide Web Consortium">W3C</abbr>
+    Last Call Working Draft 12 March 2013</a>:</p>
+
+<ul>
+  <li>Section 1. Modified diagram to clarify that <code><a href="#dfn-qb-slice" class="internalDFN">qb:Slice</a></code> is a sub
+  class of <code><a href="#dfn-qb-observationgroup" class="internalDFN">qb:ObservationGroup</a></code> </li>
+  <li>Section 5.1. Moved description of data set here for greater
+  clarity, was in section 7.</li>
+  <li>Section 6.2. Further clarified the status of COG RDF vocabularies.</li>
+  <li>Example 6.3. Retitled for clarity.</li>
+  <li>Section 6.4, corrected "with multiple observations" to "with
+  multiple measures".</li>
+  <li>Section 6.4. Added mention of <code><a href="#dfn-qb-attachable" class="internalDFN">qb:Attachable</a></code> (previously only
+  mentioned in the vocabulary reference).</li>
+  <li>Section 6.5. Rewritten description of handling of multiple
+  measures for greater clarity.</li>
+  <li>Section 6.5.2. Removed reference to "SDMX-in-RDF vocabulary"
+  which is not part of this specification.</li>
+  <li>Section 6.5.2 clarified that the special nature of
+  <code><a href="#dfn-qb-measuretype" class="internalDFN">qb:measureType</a></code> is a divergence from SDMX.</li>
+  <li>Section 7. Change terminology from "internal and external
+  metadata" to "structural and reference" metadata for compatibility
+  with SDMX terminology.</li>
+  <li>Section 8.2. Clarified that sub properties of <code>skos:narrower</code> may
+  be used.</li>
+  <li>Section 8.3. Removed third bullet on the motivation for
+  <code><a href="#dfn-qb-hierarchicalcodelist" class="internalDFN">qb:HierarchicalCodeList</a></code> (exhaustivity and mutual exclusion).</li>
+  <li>Added reference to SDMX User Guide as additional background context.</li>
+  <li>Added complete example Data Cube as an appendix, providing a
+  link to it from earlier on in the document.
+  </li><li>Section 10. Clarified that abbreviated form is an option, and
+  there is no requirement to use it in place of normalized form.</li>
+  <li>Section 12.2. Corrected domain of  <code><a href="#dfn-qb-observation-1" class="internalDFN">qb:observation</a></code> from  <code><a href="#dfn-qb-slice" class="internalDFN">qb:Slice</a></code> to
+   <code><a href="#dfn-qb-observationgroup" class="internalDFN">qb:ObservationGroup</a></code>, was given correctly in the ontology and text
+  body but was mis-stated in the reference section.</li>
+  <li>Various typographical corrections.</li>
+</ul>
+
+<p>Changes since <a href="http://www.w3.org/TR/2012/WD-vocab-data-cube-20120405/"><abbr title="World
+  Wide Web Consortium">W3C</abbr> Working Draft 5 April 2012</a>:</p>
+
+<ul>
+  <li>Added <a href="#wf">section</a> on criteria for well-formed cubes. <a href="http://www.w3.org/2011/gld/track/issues/29">ISSUE-29</a></li>
+  <li>Added <a href="#normalize">section</a> on normalization algorithm
+  for handling abbreviated cubes.</li>
+  <li>Added <a href="#conformance">conformance section</a>.
+  </li><li>Clarified that <code><a href="#dfn-qb-componentrequired" class="internalDFN">qb:componentRequired</a></code> is only applicable to
+  attributes and that it defaults to optional.</li>
+  <li>Moved vocabulary reference into the normative body of the specification, adding hyperlinks for all qb: terms.</li>
+  <li>Added <a href="#schemes-hierarchy-nonskos">section</a> on non-skos hierarchies. <a href="http://www.w3.org/2011/gld/track/issues/31">ISSUE-31</a>.</li>
+  <li>Added <a href="#schemes-aggregation">note</a> that aggregation operations and inter-cube relations are out of scope for this version. <a href="http://www.w3.org/2011/gld/track/issues/30">ISSUE-30</a>.</li>
+  <li>Added <code><a href="#dfn-qb-observationgroup" class="internalDFN">qb:ObservationGroup</a></code> as a generalization of <code><a href="#dfn-qb-slice" class="internalDFN">qb:Slice</a></code>. <a href="http://www.w3.org/2011/gld/track/issues/33">ISSUE-33</a>.</li>
+  <li>Removed <code><a>qb:subSlice</a></code> as being problematic in how
+  they interact with attachment levels. <a href="http://www.w3.org/2011/gld/track/issues/34">ISSUE-34</a>.</li>
+  <li>Generalized range of <code><a href="#dfn-qb-codelist" class="internalDFN">qb:codeList</a></code> to allow <code>skos:Collection</code>. <a href="http://www.w3.org/2011/gld/track/issues/39">ISSUE-39</a>.</li>
+  <li>Moved namespace definitions to a normative <a href="#namespaces">section</a> within the body of the specification.</li>
+  <li>Moved Jeni Tennison from being listed as an author to being a
+  contributor. </li>
+</ul>
+
+
+</section>
+
+<section id="full-example" class="appendix">
+
+<!--OddPage--><h2><span class="secno">C. </span>Complete example Data Cube</h2>
+
+<p>This is a complete Data Cube encoding of the running example
+   introduced in <a href="#example">section 5.4</a>. 
+   It uses the abbreviated format so that it can be concisely
+   presented. It passes all the integrity checks (when the
+   declaration of <code>sdmx-dimension:sex</code> is included 
+   from <a href="http://purl.org/linked-data/sdmx/2009/dimension">http://purl.org/linked-data/sdmx/2009/dimension</a>)
+   and so is a well-formed abbreviated Data Cube.
+   </p>
+
+<pre>@prefix rdf:      &lt;http://www.w3.org/1999/02/22-rdf-syntax-ns#&gt; .
[email protected] rdfs:     &lt;http://www.w3.org/2000/01/rdf-schema#&gt; .
[email protected] owl:      &lt;http://www.w3.org/2002/07/owl#&gt; .
[email protected] xsd:      &lt;http://www.w3.org/2001/XMLSchema#&gt; .
[email protected] skos:     &lt;http://www.w3.org/2004/02/skos/core#&gt; .
[email protected] void:     &lt;http://rdfs.org/ns/void#&gt; .
[email protected] dct:      &lt;http://purl.org/dc/terms/&gt; .
[email protected] foaf:     &lt;http://xmlns.com/foaf/0.1/&gt; .
[email protected] org:      &lt;http://www.w3.org/ns/org#&gt; .
[email protected] admingeo: &lt;http://data.ordnancesurvey.co.uk/ontology/admingeo/&gt; .
[email protected] interval: &lt;http://reference.data.gov.uk/def/intervals/&gt; .
+
[email protected] qb:       &lt;http://purl.org/linked-data/cube#&gt; .
+
[email protected] sdmx-concept:    &lt;http://purl.org/linked-data/sdmx/2009/concept#&gt; .
[email protected] sdmx-dimension:  &lt;http://purl.org/linked-data/sdmx/2009/dimension#&gt; .
[email protected] sdmx-attribute:  &lt;http://purl.org/linked-data/sdmx/2009/attribute#&gt; .
[email protected] sdmx-measure:    &lt;http://purl.org/linked-data/sdmx/2009/measure#&gt; .
[email protected] sdmx-metadata:   &lt;http://purl.org/linked-data/sdmx/2009/metadata#&gt; .
[email protected] sdmx-code:       &lt;http://purl.org/linked-data/sdmx/2009/code#&gt; .
[email protected] sdmx-subject:    &lt;http://purl.org/linked-data/sdmx/2009/subject#&gt; .
+
[email protected] ex-geo:   &lt;http://example.org/geo#&gt; .
[email protected] eg:       &lt;http://example.org/ns#&gt; .
+
+# -- Data Set --------------------------------------------
+
+eg:dataset-le3 a qb:DataSet;
+    dct:title       "Life expectancy"@en;
+    rdfs:label      "Life expectancy"@en;
+    rdfs:comment    "Life expectancy within Welsh Unitary authorities - extracted from Stats Wales"@en;
+    dct:description "Life expectancy within Welsh Unitary authorities - extracted from Stats Wales"@en;
+    dct:publisher   eg:organization ;
+    dct:issued      "2010-08-11"^^xsd:date;
+    dct:subject
+        sdmx-subject:3.2 ,      # regional and small area statistics
+        sdmx-subject:1.4 ,      # Health
+        ex-geo:wales;           # Wales
+    qb:structure eg:dsd-le3 ;  
+    sdmx-attribute:unitMeasure &lt;http://dbpedia.org/resource/Year&gt; ;
+    qb:slice eg:slice1, eg:slice2, eg:slice3, eg:slice4, eg:slice5, eg:slice6 ;
+    .
+
+eg:organization a org:Organization, foaf:Agent;
+    rdfs:label "Example org"@en .    
+        
+# -- Data structure definition ----------------------------
+
+eg:dsd-le3 a qb:DataStructureDefinition;
+    qb:component 
+    # The dimensions
+        [ qb:dimension eg:refArea;         qb:order 1 ],
+        [ qb:dimension eg:refPeriod;       qb:order 2; qb:componentAttachment qb:Slice ],
+        [ qb:dimension sdmx-dimension:sex; qb:order 3; qb:componentAttachment qb:Slice ];
+        
+    # The measure(s)
+    qb:component [ qb:measure eg:lifeExpectancy];
+    
+    # The attributes
+    qb:component [ qb:attribute sdmx-attribute:unitMeasure; 
+                   qb:componentRequired "true"^^xsd:boolean;
+                   qb:componentAttachment qb:DataSet; ] ;
+    
+    # slices
+    qb:sliceKey eg:sliceByRegion ;
+    .
+    
+eg:sliceByRegion a qb:SliceKey;
+    rdfs:label "slice by region"@en;
+    rdfs:comment "Slice by grouping regions together, fixing sex and time values"@en;
+    qb:componentProperty eg:refPeriod, sdmx-dimension:sex ;
+    .
+                   
+# -- Dimensions and measures  ----------------------------
+
+eg:refPeriod  a rdf:Property, qb:DimensionProperty;
+    rdfs:label "reference period"@en;
+    rdfs:subPropertyOf sdmx-dimension:refPeriod;
+    rdfs:range interval:Interval;
+    qb:concept sdmx-concept:refPeriod ;
+    .
+
+
+eg:refArea  a rdf:Property, qb:DimensionProperty;
+    rdfs:label "reference area"@en;
+    rdfs:subPropertyOf sdmx-dimension:refArea;
+    rdfs:range admingeo:UnitaryAuthority;
+    qb:concept sdmx-concept:refArea ;
+    .
+
+eg:lifeExpectancy  a rdf:Property, qb:MeasureProperty;
+    rdfs:label "life expectancy"@en;
+    rdfs:subPropertyOf sdmx-measure:obsValue;
+    rdfs:range xsd:decimal ;
+    .
+    
+# -- Observations -----------------------------------------
+
+# Column 1
+    
+eg:slice1 a qb:Slice;
+    qb:sliceStructure  eg:sliceByRegion ;
+    eg:refPeriod               &lt;http://reference.data.gov.uk/id/gregorian-interval/2004-01-01T00:00:00/P3Y&gt; ;
+    sdmx-dimension:sex         sdmx-code:sex-M ;
+    qb:observation eg:o11, eg:o12, eg:o13, eg:o14 ;
+    .
+
+eg:o11 a qb:Observation;
+    qb:dataSet  eg:dataset-le3 ;
+    eg:refArea                 ex-geo:newport_00pr ;                  
+    eg:lifeExpectancy          76.7 ;
+    .
+    
+eg:o12 a qb:Observation;
+    qb:dataSet  eg:dataset-le3 ;
+    eg:refArea                 ex-geo:cardiff_00pt ;                  
+    eg:lifeExpectancy          78.7 ;
+    .
+
+eg:o13 a qb:Observation;
+    qb:dataSet  eg:dataset-le3 ;
+    eg:refArea                 ex-geo:monmouthshire_00pp ;                  
+    eg:lifeExpectancy          76.6 ;
+    .
+
+eg:o14 a qb:Observation;
+    qb:dataSet  eg:dataset-le3 ;
+    eg:refArea                 ex-geo:merthyr_tdfil_00ph ;
+    eg:lifeExpectancy          75.5 ;
+    .
+
+# Column 2
+    
+eg:slice2 a qb:Slice;
+    qb:sliceStructure  eg:sliceByRegion ;
+    eg:refPeriod               &lt;http://reference.data.gov.uk/id/gregorian-interval/2004-01-01T00:00:00/P3Y&gt; ;
+    sdmx-dimension:sex         sdmx-code:sex-F ;
+    qb:observation eg:o21, eg:o22, eg:o23, eg:o24 ;
+    .
+
+eg:o21 a qb:Observation;
+    qb:dataSet  eg:dataset-le3 ;
+    eg:refArea                 ex-geo:newport_00pr ;                  
+    eg:lifeExpectancy          80.7 ;
+    .
+    
+eg:o22 a qb:Observation;
+    qb:dataSet  eg:dataset-le3 ;
+    eg:refArea                 ex-geo:cardiff_00pt ;                  
+    eg:lifeExpectancy          83.3 ;
+    .
+
+eg:o23 a qb:Observation;
+    qb:dataSet  eg:dataset-le3 ;
+    eg:refArea                 ex-geo:monmouthshire_00pp ;                  
+    eg:lifeExpectancy          81.3 ;
+    .
+
+eg:o24 a qb:Observation;
+    qb:dataSet  eg:dataset-le3 ;
+    eg:refArea                 ex-geo:merthyr_tdfil_00ph ;
+    eg:lifeExpectancy          79.1 ;
+    .
+
+# Column 3
+    
+eg:slice3 a qb:Slice;
+    qb:sliceStructure  eg:sliceByRegion ;
+    eg:refPeriod               &lt;http://reference.data.gov.uk/id/gregorian-interval/2005-01-01T00:00:00/P3Y&gt; ;
+    sdmx-dimension:sex         sdmx-code:sex-M ;
+    qb:observation eg:o31, eg:o32, eg:o33, eg:o34 ;
+    .
+
+eg:o31 a qb:Observation;
+    qb:dataSet  eg:dataset-le3 ;
+    eg:refArea                 ex-geo:newport_00pr ;                  
+    eg:lifeExpectancy          77.1 ;
+    .
+    
+eg:o32 a qb:Observation;
+    qb:dataSet  eg:dataset-le3 ;
+    eg:refArea                 ex-geo:cardiff_00pt ;                  
+    eg:lifeExpectancy          78.6 ;
+    .
+
+eg:o33 a qb:Observation;
+    qb:dataSet  eg:dataset-le3 ;
+    eg:refArea                 ex-geo:monmouthshire_00pp ;                  
+    eg:lifeExpectancy          76.5 ;
+    .
+
+eg:o34 a qb:Observation;
+    qb:dataSet  eg:dataset-le3 ;
+    eg:refArea                 ex-geo:merthyr_tdfil_00ph ;
+    eg:lifeExpectancy          75.5 ;
+    .
+
+# Column 4
+    
+eg:slice4 a qb:Slice;
+    qb:sliceStructure  eg:sliceByRegion ;
+    eg:refPeriod               &lt;http://reference.data.gov.uk/id/gregorian-interval/2005-01-01T00:00:00/P3Y&gt; ;
+    sdmx-dimension:sex         sdmx-code:sex-F ;
+    qb:observation eg:o41, eg:o42, eg:o43, eg:o44 ;
+    .
+
+eg:o41 a qb:Observation;
+    qb:dataSet  eg:dataset-le3 ;
+    eg:refArea                 ex-geo:newport_00pr ;                  
+    eg:lifeExpectancy          80.9 ;
+    .
+    
+eg:o42 a qb:Observation;
+    qb:dataSet  eg:dataset-le3 ;
+    eg:refArea                 ex-geo:cardiff_00pt ;                  
+    eg:lifeExpectancy          83.7 ;
+    .
+
+eg:o43 a qb:Observation;
+    qb:dataSet  eg:dataset-le3 ;
+    eg:refArea                 ex-geo:monmouthshire_00pp ;                  
+    eg:lifeExpectancy          81.5 ;
+    .
+
+eg:o44 a qb:Observation;
+    qb:dataSet  eg:dataset-le3 ;
+    eg:refArea                 ex-geo:merthyr_tdfil_00ph ;
+    eg:lifeExpectancy          79.4 ;
+    .
+
+# Column 5
+    
+eg:slice5 a qb:Slice;
+    qb:sliceStructure  eg:sliceByRegion ;
+    eg:refPeriod               &lt;http://reference.data.gov.uk/id/gregorian-interval/2006-01-01T00:00:00/P3Y&gt; ;
+    sdmx-dimension:sex         sdmx-code:sex-M ;
+    qb:observation eg:o51, eg:o52, eg:o53, eg:o54 ;
+    .
+
+eg:o51 a qb:Observation;
+    qb:dataSet  eg:dataset-le3 ;
+    eg:refArea                 ex-geo:newport_00pr ;                  
+    eg:lifeExpectancy          77.0 ;
+    .
+    
+eg:o52 a qb:Observation;
+    qb:dataSet  eg:dataset-le3 ;
+    eg:refArea                 ex-geo:cardiff_00pt ;                  
+    eg:lifeExpectancy          78.7 ;
+    .
+
+eg:o53 a qb:Observation;
+    qb:dataSet  eg:dataset-le3 ;
+    eg:refArea                 ex-geo:monmouthshire_00pp ;                  
+    eg:lifeExpectancy          76.6 ;
+    .
+
+eg:o54 a qb:Observation;
+    qb:dataSet  eg:dataset-le3 ;
+    eg:refArea                 ex-geo:merthyr_tdfil_00ph ;
+    eg:lifeExpectancy          74.9 ;
+    .
+
+# Column 6
+    
+eg:slice6 a qb:Slice;
+    qb:sliceStructure  eg:sliceByRegion ;
+    eg:refPeriod               &lt;http://reference.data.gov.uk/id/gregorian-interval/2006-01-01T00:00:00/P3Y&gt; ;
+    sdmx-dimension:sex         sdmx-code:sex-F ;
+    qb:observation eg:o61, eg:o62, eg:o63, eg:o64 ;
+    .
+
+eg:o61 a qb:Observation;
+    qb:dataSet  eg:dataset-le3 ;
+    eg:refArea                 ex-geo:newport_00pr ;                  
+    eg:lifeExpectancy          81.5 ;
+    .
+    
+eg:o62 a qb:Observation;
+    qb:dataSet  eg:dataset-le3 ;
+    eg:refArea                 ex-geo:cardiff_00pt ;                  
+    eg:lifeExpectancy          83.4 ;
+    .
+
+eg:o63 a qb:Observation;
+    qb:dataSet  eg:dataset-le3 ;
+    eg:refArea                 ex-geo:monmouthshire_00pp ;                  
+    eg:lifeExpectancy          81.7 ;
+    .
+
+eg:o64 a qb:Observation;
+    qb:dataSet  eg:dataset-le3 ;
+    eg:refArea                 ex-geo:merthyr_tdfil_00ph ;
+    eg:lifeExpectancy          79.6 ;
+    .
+</pre>
+   
+</section>
+
+<section id="references_section" class="appendix">
+</section>
+
+
+
+<section id="references" class="appendix"><!--OddPage--><h2><span class="secno">D. </span>References</h2><section id="normative-references"><h3><span class="secno">D.1 </span>Normative references</h3><dl class="bibliography"><dt id="bib-DC11">[DC11]</dt><dd>Dublin Core metadata initiative. <a href="http://dublincore.org/documents/dcmi-terms/"><cite>Dublin Core metadata element set, version 1.1.</cite></a> July 1999. Dublin Core recommendation. URL: <a href="http://dublincore.org/documents/dcmi-terms/">http://dublincore.org/documents/dcmi-terms/</a>
+</dd><dt id="bib-OWL2-PRIMER">[OWL2-PRIMER]</dt><dd>Pascal Hitzler; Markus Krötzsch; Bijan Parsia; Peter F. Patel-Schneider; Sebastian Rudolph. <a href="http://www.w3.org/TR/2009/REC-owl2-primer-20091027/"><cite>OWL 2 Web Ontology Language:Primer.</cite></a> 27 October 2009. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2009/REC-owl2-primer-20091027/">http://www.w3.org/TR/2009/REC-owl2-primer-20091027/</a>
+</dd><dt id="bib-RDF-CONCEPTS">[RDF-CONCEPTS]</dt><dd>Graham Klyne; Jeremy J. Carroll. <a href="http://www.w3.org/TR/2004/REC-rdf-concepts-20040210"><cite>Resource Description Framework (RDF): Concepts and Abstract Syntax.</cite></a> 10 February 2004. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2004/REC-rdf-concepts-20040210">http://www.w3.org/TR/2004/REC-rdf-concepts-20040210</a>
+</dd><dt id="bib-RDF-MT">[RDF-MT]</dt><dd>Patrick Hayes. <a href="http://www.w3.org/TR/2004/REC-rdf-mt-20040210"><cite>RDF Semantics.</cite></a> 10 February 2004. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2004/REC-rdf-mt-20040210">http://www.w3.org/TR/2004/REC-rdf-mt-20040210</a>
+</dd><dt id="bib-RDF-PRIMER">[RDF-PRIMER]</dt><dd>Frank Manola; Eric Miller. <a href="http://www.w3.org/TR/2004/REC-rdf-primer-20040210/"><cite>RDF Primer.</cite></a> 10 February 2004. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2004/REC-rdf-primer-20040210/">http://www.w3.org/TR/2004/REC-rdf-primer-20040210/</a>
+</dd><dt id="bib-RDF-SCHEMA">[RDF-SCHEMA]</dt><dd>Dan Brickley; Ramanathan V. Guha. <a href="http://www.w3.org/TR/2004/REC-rdf-schema-20040210"><cite>RDF Vocabulary Description Language 1.0: RDF Schema.</cite></a> 10 February 2004. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2004/REC-rdf-schema-20040210">http://www.w3.org/TR/2004/REC-rdf-schema-20040210</a>
+</dd><dt id="bib-RFC2119">[RFC2119]</dt><dd>S. Bradner. <a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>Key words for use in RFCs to Indicate Requirement Levels.</cite></a> March 1997. Internet RFC 2119.  URL: <a href="http://www.ietf.org/rfc/rfc2119.txt">http://www.ietf.org/rfc/rfc2119.txt</a> 
+</dd><dt id="bib-SKOS-REFERENCE">[SKOS-REFERENCE]</dt><dd>Sean Bechhofer; Alistair Miles. <a href="http://www.w3.org/TR/2009/REC-skos-reference-20090818/"><cite>SKOS Simple Knowledge Organization System Reference.</cite></a> 18 August 2009. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2009/REC-skos-reference-20090818/">http://www.w3.org/TR/2009/REC-skos-reference-20090818/</a>
+</dd><dt id="bib-SPARQL-QUERY-11">[SPARQL-QUERY-11]</dt><dd>Steve Harris; Andy Seaborne. <a href="http://www.w3.org/TR/2012/PR-sparql11-query-20121108/"><cite>SPARQL 1.1 Query Language</cite></a> 8 November 2012. W3C Proposed Recommendation. URL: <a href="http://www.w3.org/TR/2012/PR-sparql11-query-20121108/">http://www.w3.org/TR/2012/PR-sparql11-query-20121108/</a>
+</dd><dt id="bib-SPARQL-UPDATE-11">[SPARQL-UPDATE-11]</dt><dd>Paul Gearon; Alexandre Passant; Axel Polleres. <a href="http://www.w3.org/TR/2012/PR-sparql11-update-20121108/"><cite>SPARQL 1.1 Update</cite></a> 8 November 2012. W3C Proposed Recommendation. URL: <a href="http://www.w3.org/TR/2012/PR-sparql11-update-20121108/">http://www.w3.org/TR/2012/PR-sparql11-update-20121108/</a>
+</dd><dt id="bib-TURTLE-TR">[TURTLE-TR]</dt><dd>Eric Prud'hommeaux, Gavin Carothers. <a href="http://www.w3.org/TR/2013/CR-turtle-20130219/"><cite>Turtle: Terse RDF Triple Language.</cite></a> 19 February 2013. W3C Candidate Recommendation. URL: <a href="http://www.w3.org/TR/2013/CR-turtle-20130219/">http://www.w3.org/TR/2013/CR-turtle-20130219/</a>
+</dd></dl></section><section id="informative-references"><h3><span class="secno">D.2 </span>Informative references</h3><dl class="bibliography"><dt id="bib-COG">[COG]</dt><dd>SDMX Contnent Oriented Guidelines, <a href="http://sdmx.org/?page_id=11">http://sdmx.org/?page_id=11</a>
+</dd><dt id="bib-DCAT">[DCAT]</dt><dd>Fadi Maali; John Erickson; Phil Archer. <a href="http://www.w3.org/TR/vocab-dcat/"><cite>Data Catalog Vocabulary (DCAT)</cite></a> W3C Working Draft. 12 March 2013. URL: <a href="http://www.w3.org/TR/vocab-dcat/">http://www.w3.org/TR/vocab-dcat/</a>
+</dd><dt id="bib-FOAF">[FOAF]</dt><dd>Dan Brickley, Libby Miller. <a href="http://xmlns.com/foaf/spec/"><cite>FOAF Vocabulary Specification 0.98.</cite></a> 9 August 2010. URL: <a href="http://xmlns.com/foaf/spec/">http://xmlns.com/foaf/spec/</a>
+</dd><dt id="bib-LOD">[LOD]</dt><dd>Linked Data, <a href="http://linkeddata.org/">http://linkeddata.org/</a>
+</dd><dt id="bib-OLAP">[OLAP]</dt><dd>Online Analytical Processing Data Cubes, <a href="http://en.wikipedia.org/wiki/OLAP_cube">http://en.wikipedia.org/wiki/OLAP_cube</a>
+</dd><dt id="bib-ORG">[ORG]</dt><dd>An Organization Ontology, <a href="http://www.epimorphics.com/public/vocabulary/org.html">http://www.epimorphics.com/public/vocabulary/org.html</a>
+</dd><dt id="bib-OS-GEO">[OS-GEO]</dt><dd>Ordnance Survey Administrative Geography Ontology, <a href="http://data.ordnancesurvey.co.uk/ontology/admingeo/">http://data.ordnancesurvey.co.uk/ontology/admingeo/</a>
+</dd><dt id="bib-SCOVO">[SCOVO]</dt><dd>The Statistical Core Vocabulary, <a href="http://sw.joanneum.at/scovo/schema.html">http://sw.joanneum.at/scovo/schema.html</a><br>SCOVO: Using Statistics on the Web of data, <a href="http://sw-app.org/pub/eswc09-inuse-scovo.pdf">http://sw-app.org/pub/eswc09-inuse-scovo.pdf</a>
+</dd><dt id="bib-SDMX-GUIDE">[SDMX-GUIDE]</dt><dd>SDMX User Guide, Version 2009.1, January 2009.  Statistical Data and Metadata Exchange Initiative. URL: <a href="http://sdmx.org/wp-content/uploads/2009/02/sdmx-userguide-version2009-1-71.pdf">http://sdmx.org/wp-content/uploads/2009/02/sdmx-userguide-version2009-1-71.pdf</a>
+</dd><dt id="bib-SDMX20">[SDMX20]</dt><dd>SDMX Information Model: UML Conceptual Design (Version 2.0), November 2005, Statistical Data and Metadata Exchange Initiative. URL: <a href="http://sdmx.org/docs/2_0/SDMX_2_0%20SECTION_02_InformationModel.pdf">http://sdmx.org/docs/2_0/SDMX_2_0%20SECTION_02_InformationModel.pdf</a>
+</dd><dt id="bib-SKOS-PRIMER">[SKOS-PRIMER]</dt><dd>Antoine Isaac; Ed Summers. <a href="http://www.w3.org/TR/2009/NOTE-skos-primer-20090818/"><cite>SKOS Simple Knowledge Organization System Primer.</cite></a> 18 August 2009. W3C Note. URL: <a href="http://www.w3.org/TR/2009/NOTE-skos-primer-20090818/">http://www.w3.org/TR/2009/NOTE-skos-primer-20090818/</a>
+</dd><dt id="bib-VOID">[VOID]</dt><dd>Keith Alexander; Richard Cyganiak; Michael Hausenblas; Jun Zhao. <a href="http://www.w3.org/TR/void/"><cite>Describing Linked Datasets with the VoID Vocabulary</cite></a> 03 March 2011. Interest Group Note. URL: <a href="http://www.w3.org/TR/void/">http://www.w3.org/TR/void/</a>
+</dd></dl></section></section></body></html>
--- a/data-cube/static-cr.html	Fri May 24 15:58:09 2013 +0100
+++ b/data-cube/static-cr.html	Sun May 26 12:30:32 2013 +0100
@@ -221,11 +221,12 @@
   </p>
   <h1 class="title" id="title">The RDF Data Cube Vocabulary</h1>
   
-  <h2 id="w3c-candidate-recommendation-23-may-2013"><abbr title="World Wide Web Consortium">W3C</abbr> Candidate Recommendation 23 May 2013</h2>
+  <h2 id="w3c-candidate-recommendation-30-may-2013"><abbr title="World
+  Wide Web Consortium">W3C</abbr> Candidate Recommendation 30 May 2013</h2>
   <dl>
     
       <dt>This version:</dt>
-      <dd><a href="http://www.w3.org/TR/2013/CR-vocab-data-cube-20130523/">http://www.w3.org/TR/2013/CR-vocab-data-cube-20130523/</a></dd>
+      <dd><a href="http://www.w3.org/TR/2013/CR-vocab-data-cube-20130530/">http://www.w3.org/TR/2013/CR-vocab-data-cube-20130530/</a></dd>
       <dt>Latest published version:</dt>
       <dd><a href="http://www.w3.org/TR/vocab-data-cube/">http://www.w3.org/TR/vocab-data-cube/</a></dd>
     
@@ -266,7 +267,6 @@
 and <a 
 href="http://www.w3.org/Consortium/Legal/copyright-documents">document 
 use</a> rules apply.</p>
-  
     
   
   <hr>
@@ -277,7 +277,8 @@
 publish
 multi-dimensional data, such as statistics, on the web in such a way
 that it can be linked to related data sets and concepts. The Data Cube
-vocabulary provides a means to do this using the <abbr title="World Wide Web Consortium">W3C</abbr> <a href="http://www.w3.org/TR/REC-rdf-syntax/">RDF</a>
+vocabulary provides a means to do this using the <abbr title="World
+  Wide Web Consortium">W3C</abbr> <a href="http://www.w3.org/TR/REC-rdf-syntax/">RDF</a>
 (Resource Description Framework) standard. The model underpinning the
 Data Cube vocabulary is
 compatible with the cube model that underlies <a href="http://sdmx.org">SDMX</a> (Statistical Data
@@ -292,57 +293,77 @@
       
         <p>
           <em>This section describes the status of this document at the time of its publication. Other
-          documents may supersede this document. A list of current <abbr title="World Wide Web Consortium">W3C</abbr> publications and the latest revision
-          of this technical report can be found in the <a href="http://www.w3.org/TR/"><abbr title="World Wide Web Consortium">W3C</abbr> technical reports
+          documents may supersede this document. A list of current <abbr title="World
+  Wide Web Consortium">W3C</abbr> publications and the latest revision
+          of this technical report can be found in the <a href="http://www.w3.org/TR/"><abbr title="World
+  Wide Web Consortium">W3C</abbr> technical reports
           index</a> at http://www.w3.org/TR/.</em>
         </p>
         
-  <p>This publication transitions <a href="http://publishing-statistical-data.googlecode.com/svn/trunk/specs/src/main/html/cube.html">previous work</a> on this subject onto the <abbr title="World Wide Web Consortium">W3C</abbr> Recommendation Track.</p>
-
-        <p>
-          This document was published by the <a href="http://www.w3.org/2011/gld/">Government Linked Data Working Group</a> as a Candidate Recommendation.
-          
-            This document is intended to become a <abbr title="World Wide Web Consortium">W3C</abbr> Recommendation.
-          
-          
-          If you wish to make comments regarding this document, please send them to 
-          <a href="mailto:[email protected]">[email protected]</a> 
+  <p>This vocabulary was originally developed and <a href="http://publishing-statistical-data.googlecode.com/svn/trunk/specs/src/main/html/cube.html">published</a> outside of <abbr title="World
+  Wide Web Consortium">W3C</abbr>, but has been extended and further developed within the Government Linked Data Working Group.</p>
+
+<h4 class="no-toc no-num" id="summary-of-changes">Summary of changes</h4>
+
+<p>There have been no substantive changes since the Last Call version. 
+   For details on the minor changes see the <a href="#change-history">change log</a>.</p>
+
+
+<h4 class="no-toc no-num" id="please">Please Comment By 28 June 2013</h4>
+
+<p>
+  This document was published by
+  the <a href="http://www.w3.org/2011/gld/">Government Linked Data
+  Working Group</a> as a Candidate Recommendation.  <abbr title="World
+  Wide Web Consortium">W3C</abbr> publishes a Candidate Recommendation
+  to indicate that the document is believed to be stable and to
+  encourage implementation by the developer community.</p>
+
+<p> The Working
+  Group seeks to gather experience from implementations in order to
+  increase confidence in the specification and meet
+  defined <a href="http://www.w3.org/2011/gld/wiki/Data_Cube_CR_Exit_Criteria">exit
+  criteria</a>. This document will remain a Candidate Recommendation
+  until at least 28 June 2013. After that date, when and if the exit
+  criteria are met, the group intends to
+  request <a href="http://www.w3.org/2005/10/Process-20051014/tr.html#RecsPR">Proposed
+  Recommendation</a> status.</p>
+
+    <p>Please send <a href="http://www.w3.org/2011/gld/wiki/How_to_submit_a_Data_Cube_Implementation_Report">reports of implementation experience</a>, and other
+    feedback, to 
+ <a href="mailto:[email protected]">[email protected]</a> 
           (<a href="mailto:[email protected]?subject=subscribe">subscribe</a>,
-          <a href="http://lists.w3.org/Archives/Public/public-gld-comments/">archives</a>).
-          
-          
-          
-            <abbr title="World Wide Web Consortium">W3C</abbr> publishes a Candidate Recommendation to indicate that the document is believed
-            to be stable and to encourage implementation by the developer community. This
-            Candidate Recommendation is expected to advance to Proposed Recommendation no earlier than
-            20 June 2013.
-          
-          
-        All comments are welcome.
-        
-        
+          <a href="http://lists.w3.org/Archives/Public/public-gld-comments/">archives</a>).</p>
+
+<h4 class="no-toc no-num" id="no-endorsement">No Endorsement</h4>
+
           </p><p>
-            Publication as a Candidate Recommendation does not imply endorsement by the <abbr title="World Wide Web Consortium">W3C</abbr> Membership.
+            Publication as a Candidate Recommendation does not imply endorsement by the <abbr title="World
+  Wide Web Consortium">W3C</abbr> Membership.
             This is a draft document and may be updated, replaced or obsoleted by other documents at 
             any time. It is inappropriate to cite this document as other than work in progress.
           </p>
         
+<h4 class="no-toc no-num" id="patents">Patents</h4>
         
         <p>
           
             This document was produced by a group operating under the 
-            <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 <abbr title="World Wide Web Consortium">W3C</abbr> Patent Policy</a>.
+            <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 <abbr title="World
+  Wide Web Consortium">W3C</abbr> Patent Policy</a>.
           
           
           
             
-              <abbr title="World Wide Web Consortium">W3C</abbr> maintains a <a href="http://www.w3.org/2004/01/pp-impl/47663/status" rel="disclosure">public list of any patent disclosures</a> 
+              <abbr title="World
+  Wide Web Consortium">W3C</abbr> maintains a <a href="http://www.w3.org/2004/01/pp-impl/47663/status" rel="disclosure">public list of any patent disclosures</a> 
             
             made in connection with the deliverables of the group; that page also includes instructions for 
             disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains
             <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential Claim(s)</a> must disclose the
             information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section
-            6 of the <abbr title="World Wide Web Consortium">W3C</abbr> Patent Policy</a>.
+            6 of the <abbr title="World
+  Wide Web Consortium">W3C</abbr> Patent Policy</a>.
           
           
         </p>
@@ -427,7 +448,8 @@
 At the heart of a statistical dataset is a set of observed values
 organized along a group of dimensions, together with associated metadata.
 The Data Cube vocabulary enables such information to be represented
-using the <abbr title="World Wide Web Consortium">W3C</abbr> <a href="http://www.w3.org/TR/REC-rdf-syntax/">RDF</a>
+using the <abbr title="World
+  Wide Web Consortium">W3C</abbr> <a href="http://www.w3.org/TR/REC-rdf-syntax/">RDF</a>
 (Resource Description Framework) standard and published following the
 principles of
 <a href="http://linkeddata.org/">linked data</a>.
@@ -2903,7 +2925,8 @@
 suggestions and support for the original work.</p>
 
 <p>Many individuals provided valuable comments on this specification
-as it made its way through the <abbr title="World Wide Web Consortium">W3C</abbr> process. We would like to 
+as it made its way through the <abbr title="World
+  Wide Web Consortium">W3C</abbr> process. We would like to 
 especially acknowledge the contributions of
 Benedikt Kaempgen, Sarven Capadisli and Curran  Kelleher.</p>
 
@@ -2913,7 +2936,8 @@
 <!--OddPage--><h2><span class="secno">B. </span>Change history </h2>
 
 <p>Changes
-  since <a href="http://www.w3.org/TR/2013/WD-vocab-data-cube-20130312/"><abbr title="World Wide Web Consortium">W3C</abbr>
+  since <a href="http://www.w3.org/TR/2013/WD-vocab-data-cube-20130312/"><abbr title="World
+  Wide Web Consortium">W3C</abbr>
     Last Call Working Draft 12 March 2013</a>:</p>
 
 <ul>
@@ -2951,7 +2975,8 @@
   <li>Various typographical corrections.</li>
 </ul>
 
-<p>Changes since <a href="http://www.w3.org/TR/2012/WD-vocab-data-cube-20120405/"><abbr title="World Wide Web Consortium">W3C</abbr> Working Draft 5 April 2012</a>:</p>
+<p>Changes since <a href="http://www.w3.org/TR/2012/WD-vocab-data-cube-20120405/"><abbr title="World
+  Wide Web Consortium">W3C</abbr> Working Draft 5 April 2012</a>:</p>
 
 <ul>
   <li>Added <a href="#wf">section</a> on criteria for well-formed cubes. <a href="http://www.w3.org/2011/gld/track/issues/29">ISSUE-29</a></li>
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/data-cube/static-cr.patch	Sun May 26 12:30:32 2013 +0100
@@ -0,0 +1,80 @@
+--- static-cr-respec.html	2013-05-26 12:18:36.900047482 +0100
++++ static-cr.html	2013-05-26 12:19:36.520049908 +0100
[email protected]@ -251,21 +251,22 @@
+   
+   
+   
+-  
+-    
+-      <p class="copyright">
+-        <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 
+-        2013
+-        
+-        <a href="http://www.w3.org/"><abbr title="World Wide Web Consortium">W3C</abbr></a><sup>®</sup> 
+-        (<a href="http://www.csail.mit.edu/"><abbr title="Massachusetts Institute of Technology">MIT</abbr></a>,
+-        <a href="http://www.ercim.eu/"><abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr></a>,
+-        <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved.
+-        <abbr title="World
+-  Wide Web Consortium">W3C</abbr> <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>,
+-        <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and
+-        <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.
+-      </p>
++ <p class="copyright"><a 
++href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> 
++© 2013 <a href="http://www.w3.org/"><abbr title="World Wide Web 
++Consortium">W3C</abbr></a><sup>®</sup> (<a 
++href="http://www.csail.mit.edu/"><abbr title="Massachusetts Institute of 
++Technology">MIT</abbr></a>, <a href="http://www.ercim.eu/"><abbr 
++title="European Research Consortium for Informatics and 
++Mathematics">ERCIM</abbr></a>, <a 
++href="http://www.keio.ac.jp/">Keio</a>, <a 
++href="http://ev.buaa.edu.cn/">Beihang</a>), All Rights Reserved. W3C <a 
++href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, 
++<a 
++href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> 
++and <a 
++href="http://www.w3.org/Consortium/Legal/copyright-documents">document 
++use</a> rules apply.</p>
+     
+   
+   <hr>
[email protected]@ -336,31 +337,6 @@
+ 
+ <h4 class="no-toc no-num" id="no-endorsement">No Endorsement</h4>
+ 
+-
+-        <p>
+-          This document was published by the <a href="http://www.w3.org/2011/gld/">Government Linked Data Working Group</a> as a Candidate Recommendation.
+-          
+-            This document is intended to become a <abbr title="World
+-  Wide Web Consortium">W3C</abbr> Recommendation.
+-          
+-          
+-          If you wish to make comments regarding this document, please send them to 
+-          <a href="mailto:[email protected]">[email protected]</a> 
+-          (<a href="mailto:[email protected]?subject=subscribe">subscribe</a>,
+-          <a href="http://lists.w3.org/Archives/Public/public-gld-comments/">archives</a>).
+-          
+-          
+-          
+-            <abbr title="World
+-  Wide Web Consortium">W3C</abbr> publishes a Candidate Recommendation to indicate that the document is believed
+-            to be stable and to encourage implementation by the developer community. This
+-            Candidate Recommendation is expected to advance to Proposed Recommendation no earlier than
+-            28 June 2013.
+-          
+-          
+-        All comments are welcome.
+-        
+-        
+           </p><p>
+             Publication as a Candidate Recommendation does not imply endorsement by the <abbr title="World
+   Wide Web Consortium">W3C</abbr> Membership.
[email protected]@ -368,6 +344,7 @@
+             any time. It is inappropriate to cite this document as other than work in progress.
+           </p>
+         
++<h4 class="no-toc no-num" id="patents">Patents</h4>
+         
+         <p>
+           
--- a/data-cube/static-diff.html	Fri May 24 15:58:09 2013 +0100
+++ b/data-cube/static-diff.html	Sun May 26 12:30:32 2013 +0100
@@ -221,11 +221,12 @@
   </p>
   <h1 class="title" id="title">The RDF Data Cube Vocabulary</h1>
   
-  <h2 id="w3c-candidate-recommendation-23-may-2013"><abbr title="World Wide Web Consortium">W3C</abbr>  <s><del>Working</del></s> <s><del>Draft</del></s> <s><del>12</del></s> <s><del>March</del></s><u><ins>Candidate</ins></u> <u><ins>Recommendation</ins></u> <u><ins>23</ins></u> <u><ins>May</ins></u> 2013</h2>
+  <h2 id="w3c-candidate-recommendation-30-may-2013"><abbr title="World
+  Wide Web Consortium">W3C</abbr>  <s><del>Working</del></s> <s><del>Draft</del></s> <s><del>12</del></s> <s><del>March</del></s><u><ins>Candidate</ins></u> <u><ins>Recommendation</ins></u> <u><ins>30</ins></u> <u><ins>May</ins></u> 2013</h2>
   <dl>
     
       <dt>This version:</dt>
-      <dd><a href="http://www.w3.org/TR/2013/CR-vocab-data-cube-20130523/"> <s><del>http://www.w3.org/TR/2013/WD-vocab-data-cube-20130312/</del></s><u><ins>http://www.w3.org/TR/2013/CR-vocab-data-cube-20130523/</ins></u></a></dd>
+      <dd><a href="http://www.w3.org/TR/2013/CR-vocab-data-cube-20130530/"> <s><del>http://www.w3.org/TR/2013/WD-vocab-data-cube-20130312/</del></s><u><ins>http://www.w3.org/TR/2013/CR-vocab-data-cube-20130530/</ins></u></a></dd>
       <dt>Latest published version:</dt>
       <dd><a href="http://www.w3.org/TR/vocab-data-cube/">http://www.w3.org/TR/vocab-data-cube/</a></dd>
     
@@ -266,7 +267,6 @@
 and <a 
 href="http://www.w3.org/Consortium/Legal/copyright-documents">document 
 use</a> rules apply.</p>
-  
     
   
   <hr>
@@ -277,7 +277,8 @@
 publish
 multi-dimensional data, such as statistics, on the web in such a way
 that it can be linked to related data sets and concepts. The Data Cube
-vocabulary provides a means to do this using the <abbr title="World Wide Web Consortium">W3C</abbr> <a href="http://www.w3.org/TR/REC-rdf-syntax/">RDF</a>
+vocabulary provides a means to do this using the <abbr title="World
+  Wide Web Consortium">W3C</abbr> <a href="http://www.w3.org/TR/REC-rdf-syntax/">RDF</a>
 (Resource Description Framework) standard. The model underpinning the
 Data Cube vocabulary is
 compatible with the cube model that underlies <a href="http://sdmx.org">SDMX</a> (Statistical Data
@@ -292,57 +293,77 @@
       
         <p>
           <em>This section describes the status of this document at the time of its publication. Other
-          documents may supersede this document. A list of current <abbr title="World Wide Web Consortium">W3C</abbr> publications and the latest revision
-          of this technical report can be found in the <a href="http://www.w3.org/TR/"><abbr title="World Wide Web Consortium">W3C</abbr> technical reports
+          documents may supersede this document. A list of current <abbr title="World
+  Wide Web Consortium">W3C</abbr> publications and the latest revision
+          of this technical report can be found in the <a href="http://www.w3.org/TR/"><abbr title="World
+  Wide Web Consortium">W3C</abbr> technical reports
           index</a> at http://www.w3.org/TR/.</em>
         </p>
         
-  <p>This publication transitions <a href="http://publishing-statistical-data.googlecode.com/svn/trunk/specs/src/main/html/cube.html">previous work</a> on this subject onto the <abbr title="World Wide Web Consortium">W3C</abbr> Recommendation Track.</p>
-
-        <p>
-          This document was published by the <a href="http://www.w3.org/2011/gld/">Government Linked Data Working Group</a> as a  <s><del>Last</del></s> <s><del>Call</del></s> <s><del>Working</del></s> <s><del>Draft.</del></s><u><ins>Candidate</ins></u> <u><ins>Recommendation.</ins></u>
-          
-            This document is intended to become a <abbr title="World Wide Web Consortium">W3C</abbr> Recommendation.
-          
-          
-          If you wish to make comments regarding this document, please send them to 
-          <a href="mailto:[email protected]">[email protected]</a> 
+  <p>This  <s><del>publication</del></s> <s><del>transitions</del></s> <s><del>previous</del></s> <s><del>work</del></s><u><ins>vocabulary</ins></u> <u><ins>was</ins></u> <u><ins>originally</ins></u> <u><ins>developed</ins></u> <u><ins>and</ins></u> <a href="http://publishing-statistical-data.googlecode.com/svn/trunk/specs/src/main/html/cube.html"><u><ins>published</ins></u></a> <u><ins>outside</ins></u> <u><ins>of</ins></u> <abbr title="World
+  Wide Web Consortium"><u><ins>W3C</ins></u></abbr><u><ins>,</ins></u> <u><ins>but</ins></u> <u><ins>has</ins></u> <u><ins>been</ins></u> <u><ins>extended</ins></u> <u><ins>and</ins></u> <u><ins>further</ins></u> <u><ins>developed</ins></u> <u><ins>within</ins></u> <u><ins>the</ins></u> <u><ins>Government</ins></u> <u><ins>Linked</ins></u> <u><ins>Data</ins></u> <u><ins>Working</ins></u> <u><ins>Group.</ins></u></p>
+
+<h4 class="no-toc no-num" id="summary-of-changes"><u><ins>Summary</ins></u> <u><ins>of</ins></u> <u><ins>changes</ins></u></h4>
+
+<p><u><ins>There</ins></u> <u><ins>have</ins></u> <u><ins>been</ins></u> <u><ins>no</ins></u> <u><ins>substantive</ins></u> <u><ins>changes</ins></u> <u><ins>since</ins></u> <u><ins>the</ins></u> <u><ins>Last</ins></u> <u><ins>Call</ins></u> <u><ins>version.</ins></u> 
+   <u><ins>For</ins></u> <u><ins>details</ins></u> on  <s><del>this</del></s> <s><del>subject</del></s> <s><del>onto</del></s>the  <s><del>W3C</del></s> <s><del>Recommendation</del></s> <s><del>Track.</del></s><u><ins>minor</ins></u> <u><ins>changes</ins></u> <u><ins>see</ins></u> <u><ins>the</ins></u> <a href="#change-history"><u><ins>change</ins></u> <u><ins>log</ins></u></a><u><ins>.</ins></u></p>
+
+
+<h4 class="no-toc no-num" id="please"><u><ins>Please</ins></u> <u><ins>Comment</ins></u> <u><ins>By</ins></u> <u><ins>28</ins></u> <u><ins>June</ins></u> <u><ins>2013</ins></u></h4>
+
+<p>
+  This document was published by
+  the <a href="http://www.w3.org/2011/gld/">Government Linked Data
+  Working Group</a> as a  <s><del>Last</del></s> <s><del>Call</del></s> <s><del>Working</del></s> <s><del>Draft.</del></s> <s><del>This</del></s><u><ins>Candidate</ins></u> <u><ins>Recommendation.</ins></u>  <abbr title="World
+  Wide Web Consortium"><u><ins>W3C</ins></u></abbr> <u><ins>publishes</ins></u> <u><ins>a</ins></u> <u><ins>Candidate</ins></u> <u><ins>Recommendation</ins></u>
+  <u><ins>to</ins></u> <u><ins>indicate</ins></u> <u><ins>that</ins></u> <u><ins>the</ins></u> document is  <s><del>intended</del></s><u><ins>believed</ins></u> to  <s><del>become</del></s><u><ins>be</ins></u> <u><ins>stable</ins></u> <u><ins>and</ins></u> <u><ins>to</ins></u>
+  <u><ins>encourage</ins></u> <u><ins>implementation</ins></u> <u><ins>by</ins></u> <u><ins>the</ins></u> <u><ins>developer</ins></u> <u><ins>community.</ins></u></p>
+
+<p> <u><ins>The</ins></u> <u><ins>Working</ins></u>
+  <u><ins>Group</ins></u> <u><ins>seeks</ins></u> <u><ins>to</ins></u> <u><ins>gather</ins></u> <u><ins>experience</ins></u> <u><ins>from</ins></u> <u><ins>implementations</ins></u> <u><ins>in</ins></u> <u><ins>order</ins></u> <u><ins>to</ins></u>
+  <u><ins>increase</ins></u> <u><ins>confidence</ins></u> <u><ins>in</ins></u> <u><ins>the</ins></u> <u><ins>specification</ins></u> <u><ins>and</ins></u> <u><ins>meet</ins></u>
+  <u><ins>defined</ins></u> <a href="http://www.w3.org/2011/gld/wiki/Data_Cube_CR_Exit_Criteria"><u><ins>exit</ins></u>
+  <u><ins>criteria</ins></u></a><u><ins>.</ins></u> <u><ins>This</ins></u> <u><ins>document</ins></u> <u><ins>will</ins></u> <u><ins>remain</ins></u> a  <s><del>W3C</del></s> <s><del>Recommendation.</del></s> <s><del>If</del></s> <s><del>you</del></s> <s><del>wish</del></s><u><ins>Candidate</ins></u> <u><ins>Recommendation</ins></u>
+  <u><ins>until</ins></u> <u><ins>at</ins></u> <u><ins>least</ins></u> <u><ins>28</ins></u> <u><ins>June</ins></u> <u><ins>2013.</ins></u> <u><ins>After</ins></u> <u><ins>that</ins></u> <u><ins>date,</ins></u> <u><ins>when</ins></u> <u><ins>and</ins></u> <u><ins>if</ins></u> <u><ins>the</ins></u> <u><ins>exit</ins></u>
+  <u><ins>criteria</ins></u> <u><ins>are</ins></u> <u><ins>met,</ins></u> <u><ins>the</ins></u> <u><ins>group</ins></u> <u><ins>intends</ins></u> to
+   <s><del>make</del></s> <s><del>comments</del></s> <s><del>regarding</del></s> <s><del>this</del></s> <s><del>document,</del></s> <s><del>please</del></s><u><ins>request</ins></u> <a href="http://www.w3.org/2005/10/Process-20051014/tr.html#RecsPR"><u><ins>Proposed</ins></u>
+  <u><ins>Recommendation</ins></u></a> <u><ins>status.</ins></u></p>
+
+    <p><u><ins>Please</ins></u> send <a href="http://www.w3.org/2011/gld/wiki/How_to_submit_a_Data_Cube_Implementation_Report"> <s><del>them</del></s><u><ins>reports</ins></u> <u><ins>of</ins></u> <u><ins>implementation</ins></u> <u><ins>experience</ins></u></a><u><ins>,</ins></u> <u><ins>and</ins></u> <u><ins>other</ins></u>
+    <u><ins>feedback,</ins></u> to 
+ <a href="mailto:[email protected]">[email protected]</a> 
           (<a href="mailto:[email protected]?subject=subscribe">subscribe</a>,
-          <a href="http://lists.w3.org/Archives/Public/public-gld-comments/">archives</a>).
-          
-          
-          
-            <abbr title="World Wide Web Consortium"> <s><del>The</del></s> <s><del>Last</del></s> <s><del>Call</del></s> <s><del>period</del></s> <s><del>ends</del></s> <s><del>08</del></s> <s><del>April</del></s><u><ins>W3C</ins></u></abbr> <u><ins>publishes</ins></u> <u><ins>a</ins></u> <u><ins>Candidate</ins></u> <u><ins>Recommendation</ins></u> <u><ins>to</ins></u> <u><ins>indicate</ins></u> <u><ins>that</ins></u> <u><ins>the</ins></u> <u><ins>document</ins></u> <u><ins>is</ins></u> <u><ins>believed</ins></u>
-            <u><ins>to</ins></u> <u><ins>be</ins></u> <u><ins>stable</ins></u> <u><ins>and</ins></u> <u><ins>to</ins></u> <u><ins>encourage</ins></u> <u><ins>implementation</ins></u> <u><ins>by</ins></u> <u><ins>the</ins></u> <u><ins>developer</ins></u> <u><ins>community.</ins></u> <u><ins>This</ins></u>
-            <u><ins>Candidate</ins></u> <u><ins>Recommendation</ins></u> <u><ins>is</ins></u> <u><ins>expected</ins></u> <u><ins>to</ins></u> <u><ins>advance</ins></u> <u><ins>to</ins></u> <u><ins>Proposed</ins></u> <u><ins>Recommendation</ins></u> <u><ins>no</ins></u> <u><ins>earlier</ins></u> <u><ins>than</ins></u>
-            <u><ins>20</ins></u> <u><ins>June</ins></u> 2013.
-          
-          
-        All comments are welcome.
-        
-        
+          <a href="http://lists.w3.org/Archives/Public/public-gld-comments/">archives</a>).</p>
+
+<h4 class="no-toc no-num" id="no-endorsement"> <s><del>The</del></s> <s><del>Last</del></s> <s><del>Call</del></s> <s><del>period</del></s> <s><del>ends</del></s> <s><del>08</del></s> <s><del>April</del></s> <s><del>2013.</del></s> <s><del>All</del></s> <s><del>comments</del></s> <s><del>are</del></s> <s><del>welcome.</del></s><u><ins>No</ins></u> <u><ins>Endorsement</ins></u></h4>
+
           </p><p>
-            Publication as a  <s><del>Last</del></s> <s><del>Call</del></s> <s><del>Working</del></s> <s><del>Draft</del></s><u><ins>Candidate</ins></u> <u><ins>Recommendation</ins></u> does not imply endorsement by the <abbr title="World Wide Web Consortium">W3C</abbr> Membership.
+            Publication as a  <s><del>Last</del></s> <s><del>Call</del></s> <s><del>Working</del></s> <s><del>Draft</del></s><u><ins>Candidate</ins></u> <u><ins>Recommendation</ins></u> does not imply endorsement by the <abbr title="World
+  Wide Web Consortium">W3C</abbr> Membership.
             This is a draft document and may be updated, replaced or obsoleted by other documents at 
             any time. It is inappropriate to cite this document as other than work in progress.
           </p>
         
+<h4 class="no-toc no-num" id="patents"> <s><del>This</del></s> <s><del>is</del></s> <s><del>a</del></s> <s><del>Last</del></s> <s><del>Call</del></s> <s><del>Working</del></s> <s><del>Draft</del></s> <s><del>and</del></s> <s><del>thus</del></s> <s><del>the</del></s> <s><del>Working</del></s> <s><del>Group</del></s> <s><del>has</del></s> <s><del>determined</del></s> <s><del>that</del></s> <s><del>this</del></s> <s><del>document</del></s> <s><del>has</del></s> <s><del>satisfied</del></s> <s><del>the</del></s> <s><del>relevant</del></s> <s><del>technical</del></s> <s><del>requirements</del></s> <s><del>and</del></s> <s><del>is</del></s> <s><del>sufficiently</del></s> <s><del>stable</del></s> <s><del>to</del></s> <s><del>advance</del></s> <s><del>through</del></s> <s><del>the</del></s> <s><del>Technical</del></s> <s><del>Recommendation</del></s> <s><del>process.</del></s><u><ins>Patents</ins></u></h4>
         
         <p>
           
-            This  <s><del>is</del></s> <s><del>a</del></s> <s><del>Last</del></s> <s><del>Call</del></s> <s><del>Working</del></s> <s><del>Draft</del></s> <s><del>and</del></s> <s><del>thus</del></s> <s><del>the</del></s> <s><del>Working</del></s> <s><del>Group</del></s> <s><del>has</del></s> <s><del>determined</del></s> <s><del>that</del></s> <s><del>this</del></s> <s><del>document</del></s> <s><del>has</del></s> <s><del>satisfied</del></s> <s><del>the</del></s> <s><del>relevant</del></s> <s><del>technical</del></s> <s><del>requirements</del></s> <s><del>and</del></s> <s><del>is</del></s> <s><del>sufficiently</del></s> <s><del>stable</del></s> <s><del>to</del></s> <s><del>advance</del></s> <s><del>through</del></s> <s><del>the</del></s> <s><del>Technical</del></s> <s><del>Recommendation</del></s> <s><del>process.</del></s> <s><del>This</del></s>document was produced by a group operating under the 
-            <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 <abbr title="World Wide Web Consortium">W3C</abbr> Patent Policy</a>.
+            This document was produced by a group operating under the 
+            <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 <abbr title="World
+  Wide Web Consortium">W3C</abbr> Patent Policy</a>.
           
           
           
             
-              <abbr title="World Wide Web Consortium">W3C</abbr> maintains a <a href="http://www.w3.org/2004/01/pp-impl/47663/status" rel="disclosure">public list of any patent disclosures</a> 
+              <abbr title="World
+  Wide Web Consortium">W3C</abbr> maintains a <a href="http://www.w3.org/2004/01/pp-impl/47663/status" rel="disclosure">public list of any patent disclosures</a> 
             
             made in connection with the deliverables of the group; that page also includes instructions for 
             disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains
             <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential Claim(s)</a> must disclose the
             information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section
-            6 of the <abbr title="World Wide Web Consortium">W3C</abbr> Patent Policy</a>.
+            6 of the <abbr title="World
+  Wide Web Consortium">W3C</abbr> Patent Policy</a>.
           
           
         </p>
@@ -427,7 +448,8 @@
 At the heart of a statistical dataset is a set of observed values
 organized along a group of dimensions, together with associated metadata.
 The Data Cube vocabulary enables such information to be represented
-using the <abbr title="World Wide Web Consortium">W3C</abbr> <a href="http://www.w3.org/TR/REC-rdf-syntax/">RDF</a>
+using the <abbr title="World
+  Wide Web Consortium">W3C</abbr> <a href="http://www.w3.org/TR/REC-rdf-syntax/">RDF</a>
 (Resource Description Framework) standard and published following the
 principles of
 <a href="http://linkeddata.org/">linked data</a>.
@@ -635,28 +657,28 @@
 <h3><span class="secno">5.1 </span> <s><del>The</del></s> <s><del>cube</del></s> <s><del>model</del></s> <s><del>-</del></s> <s><del>dimensions,</del></s> <s><del>attributes,</del></s> <s><del>measures</del></s><u><ins>Data</ins></u> <u><ins>Sets</ins></u></h3><p><em>This section is non-normative.</em></p>
 
 <p>A  <s><del>statistical</del></s> <s><del>data</del></s> <s><del>set</del></s> <s><del>comprises</del></s><u><ins>DataSet</ins></u> <u><ins>is</ins></u> a collection of  <s><del>observations</del></s> <s><del>made</del></s> <s><del>at</del></s> <s><del>some</del></s> <s><del>points</del></s> <s><del>across</del></s> <s><del>some</del></s> <s><del>logical</del></s> <s><del>space.</del></s><u><ins>statistical</ins></u> <u><ins>data</ins></u> <u><ins>that</ins></u> <u><ins>corresponds</ins></u> <u><ins>to</ins></u> <u><ins>a</ins></u>
-  <u><ins>defined</ins></u> <u><ins>structure.</ins></u> The  <s><del>collection</del></s> <s><del>can</del></s> <s><del>be</del></s> <s><del>characterized</del></s> <s><del>by</del></s><u><ins>data</ins></u> <u><ins>in</ins></u> a <u><ins>data</ins></u> set  <s><del>of</del></s> <s><del>dimensions</del></s> <s><del>that</del></s> <s><del>define</del></s> <s><del>what</del></s> <s><del>the</del></s> <s><del>observation</del></s> <s><del>applies</del></s> <s><del>to</del></s> <s><del>(e.g.</del></s> <s><del>time,</del></s> <s><del>area,</del></s> <s><del>gender)</del></s> <s><del>along</del></s> <s><del>with</del></s> <s><del>metadata</del></s> <s><del>describing</del></s> <s><del>what</del></s> <s><del>has</del></s> <s><del>been</del></s> <s><del>measured</del></s> <s><del>(e.g.</del></s> <s><del>economic</del></s> <s><del>activity,</del></s> <s><del>population),</del></s> <s><del>how</del></s> <s><del>it</del></s> <s><del>was</del></s> <s><del>measured</del></s> <s><del>and</del></s> <s><del>how</del></s> <s><del>the</del></s> <s><del>observations</del></s> <s><del>are</del></s> <s><del>expressed</del></s> <s><del>(e.g.</del></s> <s><del>units,</del></s> <s><del>multipliers,</del></s> <s><del>status).</del></s> <s><del>We</del></s>can  <s><del>think</del></s><u><ins>be</ins></u> <u><ins>roughly</ins></u> <u><ins>described</ins></u> <u><ins>as</ins></u> <u><ins>belonging</ins></u> <u><ins>to</ins></u> <u><ins>one</ins></u> of the  <s><del>statistical</del></s> <s><del>data</del></s> <s><del>set</del></s> <s><del>as</del></s> <s><del>a</del></s> <s><del>multi-dimensional</del></s> <s><del>space,</del></s> <s><del>or</del></s> <s><del>hyper-cube,</del></s> <s><del>indexed</del></s> <s><del>by</del></s> <s><del>those</del></s> <s><del>dimensions.</del></s><u><ins>following</ins></u> <u><ins>kinds:</ins></u></p>
+  <u><ins>defined</ins></u> <u><ins>structure.</ins></u> The  <s><del>collection</del></s> <s><del>can</del></s><u><ins>data</ins></u> <u><ins>in</ins></u> <u><ins>a</ins></u> <u><ins>data</ins></u> <u><ins>set</ins></u> <u><ins>can</ins></u> <u><ins>be</ins></u> <u><ins>roughly</ins></u> <u><ins>described</ins></u> <u><ins>as</ins></u> <u><ins>belonging</ins></u> <u><ins>to</ins></u> <u><ins>one</ins></u> <u><ins>of</ins></u> <u><ins>the</ins></u> <u><ins>following</ins></u> <u><ins>kinds:</ins></u></p>
 
 <dl>
   <dt><u><ins>Observations</ins></u></dt>
-  <dd>This  <s><del>space</del></s>is  <s><del>commonly</del></s> <s><del>referred</del></s> <s><del>to</del></s> <s><del>as</del></s> <s><del>a</del></s> <s><del>cube</del></s> <s><del>for</del></s> <s><del>short;</del></s> <s><del>though</del></s>the  <s><del>name</del></s> <s><del>shouldn't</del></s> <s><del>be</del></s> <s><del>taken</del></s> <s><del>literally,</del></s> <s><del>it</del></s> <s><del>is</del></s> <s><del>not</del></s> <s><del>meant</del></s> <s><del>to</del></s> <s><del>imply</del></s> <s><del>that</del></s> <s><del>there</del></s> <s><del>are</del></s> <s><del>exactly</del></s> <s><del>three</del></s> <s><del>dimensions</del></s> <s><del>(there</del></s> <s><del>can</del></s> <s><del>be</del></s> <s><del>more</del></s> <s><del>or</del></s> <s><del>fewer)</del></s> <s><del>nor</del></s> <s><del>that</del></s> <s><del>all</del></s><u><ins>actual</ins></u> <u><ins>data,</ins></u> the  <s><del>dimensions</del></s> <s><del>are</del></s> <s><del>somehow</del></s> <s><del>similar</del></s> <s><del>in</del></s> <s><del>size.</del></s> <s><del>A</del></s> <s><del>cube</del></s> <s><del>is</del></s> <s><del>organized</del></s> <s><del>according</del></s> <s><del>to</del></s><u><ins>measured</ins></u> <u><ins>values.</ins></u> <u><ins>In</ins></u> a  <s><del>set</del></s> <s><del>of</del></s> <s><del>dimensions</del></s> <s><del>,</del></s> <s><del>attributes</del></s> <s><del>and</del></s> <s><del>measures</del></s> <s><del>.</del></s> <s><del>We</del></s> <s><del>collectively</del></s> <s><del>call</del></s> <s><del>these</del></s> <s><del>components</del></s> <s><del>.</del></s> <s><del>The</del></s> <s><del>dimension</del></s> <s><del>components</del></s> <s><del>serve</del></s> <s><del>to</del></s> <s><del>identify</del></s><u><ins>statistical</ins></u> <u><ins>table,</ins></u> <u><ins>the</ins></u> <u><ins>observations</ins></u> 
-       <u><ins>would</ins></u> <u><ins>be</ins></u> the  <s><del>observations.</del></s> <s><del>A</del></s> <s><del>set</del></s> <s><del>of</del></s>values  <s><del>for</del></s> <s><del>all</del></s><u><ins>in</ins></u> the  <s><del>dimension</del></s> <s><del>components</del></s> <s><del>is</del></s> <s><del>sufficient</del></s> <s><del>to</del></s> <s><del>identify</del></s> <s><del>a</del></s> <s><del>single</del></s> <s><del>observation.</del></s> <s><del>Examples</del></s> <s><del>of</del></s> <s><del>dimensions</del></s> <s><del>include</del></s><u><ins>table</ins></u> <u><ins>cells.</ins></u></dd>
+  <dd><u><ins>This</ins></u> <u><ins>is</ins></u> <u><ins>the</ins></u> <u><ins>actual</ins></u> <u><ins>data,</ins></u> <u><ins>the</ins></u> <u><ins>measured</ins></u> <u><ins>values.</ins></u> <u><ins>In</ins></u> <u><ins>a</ins></u> <u><ins>statistical</ins></u> <u><ins>table,</ins></u> <u><ins>the</ins></u> <u><ins>observations</ins></u> 
+       <u><ins>would</ins></u> <u><ins>be</ins></u> <u><ins>the</ins></u> <u><ins>values</ins></u> <u><ins>in</ins></u> <u><ins>the</ins></u> <u><ins>table</ins></u> <u><ins>cells.</ins></u></dd>
 
   <dt><u><ins>Organizational</ins></u> <u><ins>structure</ins></u></dt>
-  <dd><u><ins>To</ins></u> <u><ins>locate</ins></u> <u><ins>an</ins></u> <u><ins>observation</ins></u> <u><ins>within</ins></u> the  <s><del>time</del></s><u><ins>hypercube,</ins></u> <u><ins>one</ins></u> <u><ins>has</ins></u> <u><ins>at</ins></u> <u><ins>least</ins></u> to  <s><del>which</del></s><u><ins>know</ins></u> the  <s><del>observation</del></s> <s><del>applies,</del></s> <s><del>or</del></s> <s><del>a</del></s> <s><del>geographic</del></s> <s><del>region</del></s><u><ins>value</ins></u> <u><ins>of</ins></u> <u><ins>each</ins></u> 
-      <u><ins>dimension</ins></u> <u><ins>at</ins></u> which the observation  <s><del>covers.</del></s> <s><del>The</del></s> <s><del>measure</del></s> <s><del>components</del></s> <s><del>represent</del></s> <s><del>the</del></s> <s><del>phenomenon</del></s> <s><del>being</del></s> <s><del>observed.</del></s> <s><del>The</del></s> <s><del>attribute</del></s> <s><del>components</del></s> <s><del>allow</del></s> <s><del>us</del></s> <s><del>to</del></s> <s><del>qualify</del></s> <s><del>and</del></s> <s><del>interpret</del></s> <s><del>the</del></s> <s><del>observed</del></s> <s><del>value(s).</del></s> <s><del>They</del></s> <s><del>enable</del></s> <s><del>specification</del></s> <s><del>of</del></s><u><ins>is</ins></u> <u><ins>located,</ins></u> <u><ins>so</ins></u> <u><ins>these</ins></u> <u><ins>values</ins></u> <u><ins>must</ins></u> <u><ins>be</ins></u> <u><ins>specified</ins></u> <u><ins>for</ins></u> <u><ins>each</ins></u> <u><ins>observation.</ins></u> 
-      <u><ins>Datasets</ins></u> <u><ins>can</ins></u> <u><ins>have</ins></u> <u><ins>additional</ins></u> <u><ins>organizational</ins></u> <u><ins>structure</ins></u> <u><ins>in</ins></u> the  <s><del>units</del></s><u><ins>form</ins></u> of <em> <s><del>measure,</del></s> <s><del>any</del></s> <s><del>scaling</del></s> <s><del>factors</del></s> <s><del>and</del></s> <s><del>metadata</del></s> <s><del>such</del></s><u><ins>slices</ins></u></em> 
-    as  <s><del>the</del></s> <s><del>status</del></s> <s><del>of</del></s> <s><del>the</del></s> <s><del>observation</del></s> <s><del>(e.g.</del></s> <s><del>estimated</del></s> <s><del>,</del></s> <s><del>provisional</del></s> <s><del>).</del></s> <s><del>5.2</del></s> <s><del>Introducing</del></s> <s><del>Slices</del></s> <s><del>This</del></s><u><ins>described</ins></u> <u><ins>in</ins></u> <a href="#slices">section  <s><del>is</del></s> <s><del>non-normative.</del></s> <s><del>It</del></s> <s><del>is</del></s> <s><del>frequently</del></s> <s><del>useful</del></s><u><ins>7.2</ins></u></a><u><ins>.</ins></u>
+  <dd><u><ins>To</ins></u> <u><ins>locate</ins></u> <u><ins>an</ins></u> <u><ins>observation</ins></u> <u><ins>within</ins></u> <u><ins>the</ins></u> <u><ins>hypercube,</ins></u> <u><ins>one</ins></u> <u><ins>has</ins></u> <u><ins>at</ins></u> <u><ins>least</ins></u> <u><ins>to</ins></u> <u><ins>know</ins></u> <u><ins>the</ins></u> <u><ins>value</ins></u> <u><ins>of</ins></u> <u><ins>each</ins></u> 
+      <u><ins>dimension</ins></u> <u><ins>at</ins></u> <u><ins>which</ins></u> <u><ins>the</ins></u> <u><ins>observation</ins></u> <u><ins>is</ins></u> <u><ins>located,</ins></u> <u><ins>so</ins></u> <u><ins>these</ins></u> <u><ins>values</ins></u> <u><ins>must</ins></u> <u><ins>be</ins></u> <u><ins>specified</ins></u> <u><ins>for</ins></u> <u><ins>each</ins></u> <u><ins>observation.</ins></u> 
+      <u><ins>Datasets</ins></u> <u><ins>can</ins></u> <u><ins>have</ins></u> <u><ins>additional</ins></u> <u><ins>organizational</ins></u> <u><ins>structure</ins></u> <u><ins>in</ins></u> <u><ins>the</ins></u> <u><ins>form</ins></u> <u><ins>of</ins></u> <em><u><ins>slices</ins></u></em> 
+    <u><ins>as</ins></u> <u><ins>described</ins></u> <u><ins>in</ins></u> <a href="#slices"><u><ins>section</ins></u> <u><ins>7.2</ins></u></a><u><ins>.</ins></u>
 
   </dd><dt><u><ins>Structural</ins></u> <u><ins>metadata</ins></u></dt>
-  <dd><u><ins>Having</ins></u> <u><ins>located</ins></u> <u><ins>an</ins></u> <u><ins>observation,</ins></u> <u><ins>we</ins></u> <u><ins>need</ins></u> <u><ins>certain</ins></u> <u><ins>metadata</ins></u> <u><ins>in</ins></u> <u><ins>order</ins></u> to  <s><del>group</del></s> <s><del>subsets</del></s><u><ins>be</ins></u> <u><ins>able</ins></u> <u><ins>to</ins></u> <u><ins>interpret</ins></u> <u><ins>it.</ins></u> 
-    <u><ins>What</ins></u> <u><ins>is</ins></u> <u><ins>the</ins></u> <u><ins>unit</ins></u> of  <s><del>observations</del></s> <s><del>within</del></s><u><ins>measurement?</ins></u> <u><ins>Is</ins></u> <u><ins>it</ins></u> a  <s><del>dataset.</del></s> <s><del>In</del></s> <s><del>particular</del></s> <s><del>to</del></s> <s><del>fix</del></s> <s><del>all</del></s> <s><del>but</del></s> <s><del>one</del></s> <s><del>(or</del></s><u><ins>normal</ins></u> <u><ins>value</ins></u> <u><ins>or</ins></u> a  <s><del>small</del></s> <s><del>subset)</del></s> <s><del>of</del></s><u><ins>series</ins></u> <u><ins>break?</ins></u> 
-    <u><ins>Is</ins></u> the  <s><del>dimensions</del></s><u><ins>value</ins></u> <u><ins>measured</ins></u> <u><ins>or</ins></u> <u><ins>estimated?</ins></u> <u><ins>These</ins></u> <u><ins>metadata</ins></u> <u><ins>are</ins></u> <u><ins>provided</ins></u> <u><ins>as</ins></u> <em><u><ins>attributes</ins></u></em> and <u><ins>can</ins></u> 
-    be  <s><del>able</del></s><u><ins>attached</ins></u> to  <s><del>refer</del></s><u><ins>individual</ins></u> <u><ins>observations,</ins></u> <u><ins>or</ins></u> to  <s><del>all</del></s> <s><del>observations</del></s> <s><del>with</del></s> <s><del>those</del></s> <s><del>dimension</del></s> <s><del>values</del></s><u><ins>higher</ins></u> <u><ins>levels.</ins></u></dd>
+  <dd><u><ins>Having</ins></u> <u><ins>located</ins></u> <u><ins>an</ins></u> <u><ins>observation,</ins></u> <u><ins>we</ins></u> <u><ins>need</ins></u> <u><ins>certain</ins></u> <u><ins>metadata</ins></u> <u><ins>in</ins></u> <u><ins>order</ins></u> <u><ins>to</ins></u> <u><ins>be</ins></u> <u><ins>able</ins></u> <u><ins>to</ins></u> <u><ins>interpret</ins></u> <u><ins>it.</ins></u> 
+    <u><ins>What</ins></u> <u><ins>is</ins></u> <u><ins>the</ins></u> <u><ins>unit</ins></u> <u><ins>of</ins></u> <u><ins>measurement?</ins></u> <u><ins>Is</ins></u> <u><ins>it</ins></u> <u><ins>a</ins></u> <u><ins>normal</ins></u> <u><ins>value</ins></u> <u><ins>or</ins></u> <u><ins>a</ins></u> <u><ins>series</ins></u> <u><ins>break?</ins></u> 
+    <u><ins>Is</ins></u> <u><ins>the</ins></u> <u><ins>value</ins></u> <u><ins>measured</ins></u> <u><ins>or</ins></u> <u><ins>estimated?</ins></u> <u><ins>These</ins></u> <u><ins>metadata</ins></u> <u><ins>are</ins></u> <u><ins>provided</ins></u> <u><ins>as</ins></u> <em><u><ins>attributes</ins></u></em> <u><ins>and</ins></u> <u><ins>can</ins></u> 
+    <u><ins>be</ins></u> <u><ins>attached</ins></u> <u><ins>to</ins></u> <u><ins>individual</ins></u> <u><ins>observations,</ins></u> <u><ins>or</ins></u> <u><ins>to</ins></u> <u><ins>higher</ins></u> <u><ins>levels.</ins></u></dd>
 
   <dt><u><ins>Reference</ins></u> <u><ins>metadata</ins></u></dt>
-  <dd><u><ins>This</ins></u> <u><ins>is</ins></u> <u><ins>metadata</ins></u> <u><ins>that</ins></u> <u><ins>describes</ins></u> <u><ins>the</ins></u> <u><ins>dataset</ins></u> as a  <s><del>single</del></s> <s><del>entity.</del></s> <s><del>We</del></s> <s><del>call</del></s><u><ins>whole,</ins></u> such  <s><del>a</del></s> <s><del>selection</del></s> <s><del>a</del></s> <s><del>slice</del></s> <s><del>through</del></s><u><ins>as</ins></u> <u><ins>categorization</ins></u> <u><ins>of</ins></u> the 
-        <s><del>cube.</del></s> <s><del>For</del></s> <s><del>example,</del></s> <s><del>given</del></s><u><ins>dataset,</ins></u> <u><ins>its</ins></u> <u><ins>publisher,</ins></u> <u><ins>and</ins></u> a <u><ins>SPARQL</ins></u> <u><ins>endpoint</ins></u> <u><ins>where</ins></u> <u><ins>it</ins></u> <u><ins>can</ins></u> <u><ins>be</ins></u> <u><ins>accessed.</ins></u> 
+  <dd><u><ins>This</ins></u> <u><ins>is</ins></u> <u><ins>metadata</ins></u> <u><ins>that</ins></u> <u><ins>describes</ins></u> <u><ins>the</ins></u> <u><ins>dataset</ins></u> <u><ins>as</ins></u> <u><ins>a</ins></u> <u><ins>whole,</ins></u> <u><ins>such</ins></u> <u><ins>as</ins></u> <u><ins>categorization</ins></u> <u><ins>of</ins></u> <u><ins>the</ins></u> 
+       <u><ins>dataset,</ins></u> <u><ins>its</ins></u> <u><ins>publisher,</ins></u> <u><ins>and</ins></u> <u><ins>a</ins></u> <u><ins>SPARQL</ins></u> <u><ins>endpoint</ins></u> <u><ins>where</ins></u> <u><ins>it</ins></u> <u><ins>can</ins></u> <u><ins>be</ins></u> <u><ins>accessed.</ins></u> 
       <u><ins>External</ins></u> <u><ins>metadata</ins></u> <u><ins>is</ins></u> <u><ins>described</ins></u> <u><ins>in</ins></u> <a href="#metadata"><u><ins>section</ins></u> <u><ins>9</ins></u></a><u><ins>.</ins></u></dd>
 </dl>
 </section>
@@ -664,81 +686,81 @@
 <section id="cubes-model" class="informative">
 <h3><span class="secno"><u><ins>5.2</ins></u> </span><u><ins>The</ins></u> <u><ins>cube</ins></u> <u><ins>model</ins></u> <u><ins>-</ins></u> <u><ins>dimensions,</ins></u> <u><ins>attributes,</ins></u> <u><ins>measures</ins></u></h3><p><em><u><ins>This</ins></u> <u><ins>section</ins></u> <u><ins>is</ins></u> <u><ins>non-normative.</ins></u></em></p>
 
-<p><u><ins>A</ins></u> <u><ins>statistical</ins></u> data set  <s><del>on</del></s> <s><del>regional</del></s> <s><del>performance</del></s> <s><del>indicators</del></s> <s><del>then</del></s> <s><del>we</del></s> <s><del>might</del></s> <s><del>group</del></s> <s><del>all</del></s> <s><del>the</del></s> <s><del>observations</del></s> <s><del>about</del></s> <s><del>a</del></s> <s><del>given</del></s> <s><del>indicator</del></s> <s><del>and</del></s> <s><del>a</del></s> <s><del>given</del></s> <s><del>region</del></s> <s><del>into</del></s> <s><del>a</del></s> <s><del>slice,</del></s> <s><del>each</del></s> <s><del>slice</del></s> <s><del>would</del></s> <s><del>then</del></s> <s><del>represent</del></s><u><ins>comprises</ins></u> a  <s><del>time</del></s> <s><del>series</del></s><u><ins>collection</ins></u> of  <s><del>observed</del></s> <s><del>values.</del></s> <s><del>A</del></s> <s><del>data</del></s> <s><del>publisher</del></s> <s><del>may</del></s> <s><del>identify</del></s> <s><del>slices</del></s> <s><del>through</del></s> <s><del>the</del></s> <s><del>data</del></s> <s><del>for</del></s> <s><del>various</del></s> <s><del>purposes.</del></s> <s><del>They</del></s><u><ins>observations</ins></u> <u><ins>made</ins></u>
-<u><ins>at</ins></u> <u><ins>some</ins></u> <u><ins>points</ins></u> <u><ins>across</ins></u> <u><ins>some</ins></u> <u><ins>logical</ins></u> <u><ins>space.</ins></u> <u><ins>The</ins></u> <u><ins>collection</ins></u> can be <u><ins>characterized</ins></u> <u><ins>by</ins></u>
-a  <s><del>useful</del></s> <s><del>grouping</del></s> <s><del>to</del></s> <s><del>which</del></s> <s><del>metadata</del></s> <s><del>might</del></s> <s><del>be</del></s> <s><del>attached,</del></s> <s><del>for</del></s> <s><del>example</del></s> <s><del>to</del></s> <s><del>note</del></s> <s><del>a</del></s> <s><del>change</del></s> <s><del>in</del></s> <s><del>measurement</del></s> <s><del>process</del></s> <s><del>which</del></s> <s><del>affects</del></s> <s><del>a</del></s> <s><del>particular</del></s> <s><del>time</del></s> <s><del>or</del></s> <s><del>region.</del></s> <s><del>Slices</del></s> <s><del>also</del></s> <s><del>enable</del></s> <s><del>the</del></s> <s><del>publisher</del></s> <s><del>to</del></s> <s><del>identify</del></s> <s><del>and</del></s> <s><del>label</del></s> <s><del>particular</del></s> <s><del>subsets</del></s><u><ins>set</ins></u> of <u><ins>dimensions</ins></u> <u><ins>that</ins></u> <u><ins>define</ins></u> <u><ins>what</ins></u> the  <s><del>data</del></s> <s><del>which</del></s> <s><del>should</del></s> <s><del>be</del></s> <s><del>presented</del></s><u><ins>observation</ins></u> <u><ins>applies</ins></u> to <u><ins>(e.g.</ins></u> <u><ins>time,</ins></u>
-<u><ins>area,</ins></u> <u><ins>gender)</ins></u> <u><ins>along</ins></u> <u><ins>with</ins></u> <u><ins>metadata</ins></u> <u><ins>describing</ins></u> <u><ins>what</ins></u> <u><ins>has</ins></u> <u><ins>been</ins></u>
-<u><ins>measured</ins></u> <u><ins>(e.g.</ins></u> <u><ins>economic</ins></u> <u><ins>activity,</ins></u> <u><ins>population),</ins></u> <u><ins>how</ins></u> <u><ins>it</ins></u> <u><ins>was</ins></u> <u><ins>measured</ins></u> <u><ins>and</ins></u> <u><ins>how</ins></u> the
- <s><del>user</del></s> <s><del>-</del></s> <s><del>they</del></s><u><ins>observations</ins></u> <u><ins>are</ins></u> <u><ins>expressed</ins></u> <u><ins>(e.g.</ins></u> <u><ins>units,</ins></u> <u><ins>multipliers,</ins></u> <u><ins>status).</ins></u> <u><ins>We</ins></u> can
- <s><del>enable</del></s> <s><del>the</del></s> <s><del>consuming</del></s> <s><del>application</del></s> <s><del>to</del></s> <s><del>more</del></s> <s><del>easily</del></s> <s><del>construct</del></s><u><ins>think</ins></u> <u><ins>of</ins></u> the  <s><del>appropriate</del></s> <s><del>graph</del></s><u><ins>statistical</ins></u> <u><ins>data</ins></u> <u><ins>set</ins></u> <u><ins>as</ins></u> <u><ins>a</ins></u> <u><ins>multi-dimensional</ins></u>
-<u><ins>space,</ins></u> or  <s><del>chart</del></s><u><ins>hyper-cube,</ins></u> <u><ins>indexed</ins></u> <u><ins>by</ins></u> <u><ins>those</ins></u> <u><ins>dimensions.</ins></u> <u><ins>This</ins></u> <u><ins>space</ins></u> <u><ins>is</ins></u>
-<u><ins>commonly</ins></u> <u><ins>referred</ins></u> <u><ins>to</ins></u>
-<u><ins>as</ins></u> <u><ins>a</ins></u> <em><u><ins>cube</ins></u></em> for  <s><del>presentation.</del></s> <s><del>In</del></s> <s><del>statistical</del></s> <s><del>applications</del></s><u><ins>short;</ins></u> <u><ins>though</ins></u> <u><ins>the</ins></u> <u><ins>name</ins></u> <u><ins>shouldn't</ins></u> <u><ins>be</ins></u> <u><ins>taken</ins></u>
-<u><ins>literally,</ins></u> it is  <s><del>common</del></s><u><ins>not</ins></u> <u><ins>meant</ins></u> to  <s><del>work</del></s> <s><del>with</del></s> <s><del>slices</del></s><u><ins>imply</ins></u> <u><ins>that</ins></u>
-<u><ins>there</ins></u> <u><ins>are</ins></u> <u><ins>exactly</ins></u> <u><ins>three</ins></u> <u><ins>dimensions</ins></u> <u><ins>(there</ins></u> <u><ins>can</ins></u> <u><ins>be</ins></u> <u><ins>more</ins></u> <u><ins>or</ins></u> <u><ins>fewer)</ins></u> <u><ins>nor</ins></u>
-<u><ins>that</ins></u>
-<u><ins>all</ins></u> <u><ins>the</ins></u> <u><ins>dimensions</ins></u> <u><ins>are</ins></u> <u><ins>somehow</ins></u> <u><ins>similar</ins></u> in  <s><del>which</del></s> <s><del>a</del></s> <s><del>single</del></s> <s><del>dimension</del></s><u><ins>size.</ins></u></p>
-
-<p><u><ins>A</ins></u> <u><ins>cube</ins></u> is  <s><del>left</del></s> <s><del>unspecified.</del></s> <s><del>In</del></s> <s><del>particular,</del></s><u><ins>organized</ins></u> <u><ins>according</ins></u> to  <s><del>refer</del></s><u><ins>a</ins></u> <u><ins>set</ins></u> <u><ins>of</ins></u> <em><u><ins>dimensions</ins></u></em><u><ins>,</ins></u>
-<em><u><ins>attributes</ins></u></em> <u><ins>and</ins></u> <em><u><ins>measures</ins></u></em><u><ins>.</ins></u> <u><ins>We</ins></u> <u><ins>collectively</ins></u> <u><ins>call</ins></u> <u><ins>these</ins></u> <em><u><ins>components</ins></u></em><u><ins>.</ins></u></p>
-
-<p><u><ins>The</ins></u> <em><u><ins>dimension</ins></u></em> <u><ins>components</ins></u> <u><ins>serve</ins></u> to  <s><del>such</del></s> <s><del>slices</del></s> <s><del>in</del></s> <s><del>which</del></s><u><ins>identify</ins></u>
-<u><ins>the</ins></u> <u><ins>observations.</ins></u> <u><ins>A</ins></u> <u><ins>set</ins></u> <u><ins>of</ins></u> <u><ins>values</ins></u> <u><ins>for</ins></u> <u><ins>all</ins></u> the  <s><del>single</del></s> <s><del>free</del></s>dimension
-<u><ins>components</ins></u>
-is  <s><del>time</del></s> <s><del>as</del></s> <s><del>Time</del></s> <s><del>Series</del></s> <s><del>and</del></s><u><ins>sufficient</ins></u> to  <s><del>refer</del></s> <s><del>slices</del></s> <s><del>along</del></s> <s><del>non-time</del></s><u><ins>identify</ins></u> <u><ins>a</ins></u> <u><ins>single</ins></u> <u><ins>observation.</ins></u> <u><ins>Examples</ins></u> <u><ins>of</ins></u> dimensions
- <s><del>as</del></s> <s><del>Sections</del></s> <s><del>.</del></s> <s><del>Within</del></s><u><ins>include</ins></u> the
- <s><del>Data</del></s> <s><del>Cube</del></s> <s><del>vocabulary</del></s> <s><del>we</del></s><u><ins>time</ins></u> <u><ins>to</ins></u> <u><ins>which</ins></u> <u><ins>the</ins></u> <u><ins>observation</ins></u> <u><ins>applies,</ins></u> <u><ins>or</ins></u> <u><ins>a</ins></u> <u><ins>geographic</ins></u> <u><ins>region</ins></u> <u><ins>which</ins></u> <u><ins>the</ins></u> <u><ins>observation</ins></u> <u><ins>covers.</ins></u></p>
-
-<p><u><ins>The</ins></u> <em><u><ins>measure</ins></u></em> <u><ins>components</ins></u> <u><ins>represent</ins></u> <u><ins>the</ins></u> <u><ins>phenomenon</ins></u> <u><ins>being</ins></u>
-<u><ins>observed.</ins></u></p>
-
-<p><u><ins>The</ins></u> <em><u><ins>attribute</ins></u></em> <u><ins>components</ins></u> allow  <s><del>arbitrary</del></s> <s><del>dimensionality</del></s> <s><del>slices</del></s> <s><del>and</del></s> <s><del>do</del></s> <s><del>not</del></s> <s><del>give</del></s> <s><del>different</del></s> <s><del>names</del></s><u><ins>us</ins></u> to  <s><del>particular</del></s> <s><del>types</del></s><u><ins>qualify</ins></u> <u><ins>and</ins></u>
-<u><ins>interpret</ins></u> <u><ins>the</ins></u> <u><ins>observed</ins></u> <u><ins>value(s).</ins></u> <u><ins>They</ins></u> <u><ins>enable</ins></u> <u><ins>specification</ins></u> of  <s><del>slice.</del></s> <s><del>Such</del></s> <s><del>sub</del></s> <s><del>classes</del></s><u><ins>the</ins></u> <u><ins>units</ins></u> of
- <s><del>slice</del></s> <s><del>could</del></s> <s><del>be</del></s> <s><del>added</del></s> <s><del>in</del></s> <s><del>extension</del></s> <s><del>vocabularies.</del></s><u><ins>measure,</ins></u> <u><ins>any</ins></u> <u><ins>scaling</ins></u> <u><ins>factors</ins></u> <u><ins>and</ins></u> <u><ins>metadata</ins></u> <u><ins>such</ins></u> <u><ins>as</ins></u> <u><ins>the</ins></u> <u><ins>status</ins></u>
-<u><ins>of</ins></u> <u><ins>the</ins></u> <u><ins>observation</ins></u> <u><ins>(e.g.</ins></u> <em><u><ins>estimated</ins></u></em><u><ins>,</ins></u> <em><u><ins>provisional</ins></u></em><u><ins>).</ins></u></p>
+<p><u><ins>A</ins></u> <u><ins>statistical</ins></u> <u><ins>data</ins></u> <u><ins>set</ins></u> <u><ins>comprises</ins></u> <u><ins>a</ins></u> <u><ins>collection</ins></u> <u><ins>of</ins></u> <u><ins>observations</ins></u> <u><ins>made</ins></u>
+<u><ins>at</ins></u> <u><ins>some</ins></u> <u><ins>points</ins></u> <u><ins>across</ins></u> <u><ins>some</ins></u> <u><ins>logical</ins></u> <u><ins>space.</ins></u> <u><ins>The</ins></u> <u><ins>collection</ins></u> <u><ins>can</ins></u> be characterized by
+a set of dimensions that define what the observation applies to (e.g. time,
+area, gender) along with metadata describing what has been
+measured (e.g. economic activity, population), how it was measured and how the
+observations are expressed (e.g. units, multipliers, status). We can
+think of the statistical data set as a multi-dimensional
+space, or hyper-cube, indexed by those dimensions. This space is
+commonly referred to
+as a <em>cube</em> for short; though the name shouldn't be taken
+literally, it is not meant to imply that
+there are exactly three dimensions (there can be more or fewer) nor
+that
+all the dimensions are somehow similar in size.</p>
+
+<p>A cube is organized according to a set of <em>dimensions</em>,
+<em>attributes</em> and <em>measures</em>. We collectively call these <em>components</em>.</p>
+
+<p>The <em>dimension</em> components serve to identify
+the observations. A set of values for all the dimension
+components
+is sufficient to identify a single observation. Examples of dimensions
+include the
+time to which the observation applies, or a geographic region which the observation covers.</p>
+
+<p>The <em>measure</em> components represent the phenomenon being
+observed.</p>
+
+<p>The <em>attribute</em> components allow us to qualify and
+interpret the observed value(s). They enable specification of the units of
+measure, any scaling factors and metadata such as the status
+of the observation (e.g. <em>estimated</em>, <em>provisional</em>).</p>
 </section>
 
 
 <section id="cubes-slices" class="informative">
-<h3><span class="secno">5.3 </span> <s><del>An</del></s> <s><del>example</del></s><u><ins>Introducing</ins></u> <u><ins>Slices</ins></u></h3><p><em>This section is non-normative.</em></p>
-
-<p><u><ins>It</ins></u> <u><ins>is</ins></u> <u><ins>frequently</ins></u> <u><ins>useful</ins></u> <u><ins>to</ins></u> <u><ins>group</ins></u> <u><ins>subsets</ins></u> <u><ins>of</ins></u> <u><ins>observations</ins></u> <u><ins>within</ins></u> <u><ins>a</ins></u>
-<u><ins>dataset.</ins></u> In  <s><del>order</del></s><u><ins>particular</ins></u> to  <s><del>illustrate</del></s> <s><del>the</del></s> <s><del>use</del></s><u><ins>fix</ins></u> <u><ins>all</ins></u> <u><ins>but</ins></u> <u><ins>one</ins></u> <u><ins>(or</ins></u> <u><ins>a</ins></u> <u><ins>small</ins></u> <u><ins>subset)</ins></u> of the
- <s><del>data</del></s> <s><del>cube</del></s> <s><del>vocabulary</del></s> <s><del>we</del></s> <s><del>will</del></s> <s><del>use</del></s><u><ins>dimensions</ins></u> <u><ins>and</ins></u> <u><ins>be</ins></u> <u><ins>able</ins></u> <u><ins>to</ins></u> <u><ins>refer</ins></u> <u><ins>to</ins></u> <u><ins>all</ins></u> <u><ins>observations</ins></u> <u><ins>with</ins></u> <u><ins>those</ins></u>
-<u><ins>dimension</ins></u> <u><ins>values</ins></u> <u><ins>as</ins></u> <u><ins>a</ins></u> <u><ins>single</ins></u> <u><ins>entity.</ins></u> <u><ins>We</ins></u> <u><ins>call</ins></u> <u><ins>such</ins></u> <u><ins>a</ins></u> <u><ins>selection</ins></u> <u><ins>a</ins></u> <em><u><ins>slice</ins></u></em>
-<u><ins>through</ins></u> <u><ins>the</ins></u> <u><ins>cube.</ins></u> <u><ins>For</ins></u> <u><ins>example,</ins></u> <u><ins>given</ins></u> a  <s><del>small</del></s> <s><del>demonstration</del></s>data set  <s><del>extracted</del></s> <s><del>from</del></s> <s><del>StatsWales</del></s> <s><del>report</del></s> <s><del>number</del></s> <s><del>003311</del></s> <s><del>which</del></s> <s><del>describes</del></s> <s><del>life</del></s> <s><del>expectancy</del></s> <s><del>broken</del></s> <s><del>down</del></s> <s><del>by</del></s> <s><del>region</del></s> <s><del>(unitary</del></s> <s><del>authority),</del></s> <s><del>age</del></s><u><ins>on</ins></u> <u><ins>regional</ins></u> <u><ins>performance</ins></u>
-<u><ins>indicators</ins></u> <u><ins>then</ins></u> <u><ins>we</ins></u> <u><ins>might</ins></u> <u><ins>group</ins></u> <u><ins>together</ins></u> <u><ins>all</ins></u> <u><ins>the</ins></u> <u><ins>observations</ins></u> <u><ins>about</ins></u> <u><ins>a</ins></u> <u><ins>given</ins></u> <u><ins>indicator</ins></u>
-<u><ins>and</ins></u> <u><ins>a</ins></u> <u><ins>given</ins></u> <u><ins>region.</ins></u> <u><ins>Each</ins></u> <u><ins>such</ins></u> <u><ins>group</ins></u> <u><ins>would</ins></u> <u><ins>be</ins></u> <u><ins>a</ins></u> <u><ins>slice</ins></u> <u><ins>representing</ins></u> <u><ins>a</ins></u> <u><ins>time</ins></u>
-  <u><ins>series</ins></u> <u><ins>of</ins></u> <u><ins>observed</ins></u> <u><ins>values.</ins></u></p>
-
-<p><u><ins>A</ins></u> <u><ins>data</ins></u> <u><ins>publisher</ins></u> <u><ins>may</ins></u> <u><ins>identify</ins></u> <u><ins>slices</ins></u> <u><ins>through</ins></u> <u><ins>the</ins></u> <u><ins>data</ins></u> <u><ins>for</ins></u> <u><ins>various</ins></u>
-<u><ins>purposes.</ins></u> <u><ins>They</ins></u> <u><ins>can</ins></u> <u><ins>be</ins></u> <u><ins>a</ins></u> <u><ins>useful</ins></u> <u><ins>grouping</ins></u> <u><ins>to</ins></u> <u><ins>which</ins></u> <u><ins>metadata</ins></u> <u><ins>might</ins></u> <u><ins>be</ins></u> <u><ins>attached,</ins></u> <u><ins>for</ins></u> <u><ins>example</ins></u> <u><ins>to</ins></u> <u><ins>note</ins></u> <u><ins>a</ins></u>
-<u><ins>change</ins></u> <u><ins>in</ins></u> <u><ins>measurement</ins></u> <u><ins>process</ins></u> <u><ins>which</ins></u>
-<u><ins>affects</ins></u> <u><ins>a</ins></u> <u><ins>particular</ins></u> <u><ins>time</ins></u> <u><ins>or</ins></u> <u><ins>region.</ins></u> <u><ins>Slices</ins></u> <u><ins>also</ins></u> <u><ins>enable</ins></u> <u><ins>the</ins></u> <u><ins>publisher</ins></u> <u><ins>to</ins></u>
-<u><ins>identify</ins></u> <u><ins>and</ins></u> <u><ins>label</ins></u> <u><ins>particular</ins></u> <u><ins>subsets</ins></u> <u><ins>of</ins></u> <u><ins>the</ins></u> <u><ins>data</ins></u> <u><ins>which</ins></u> <u><ins>should</ins></u> <u><ins>be</ins></u> <u><ins>presented</ins></u> <u><ins>to</ins></u> <u><ins>the</ins></u>
-<u><ins>user</ins></u> <u><ins>-</ins></u> <u><ins>they</ins></u> <u><ins>can</ins></u> <u><ins>enable</ins></u> <u><ins>the</ins></u> <u><ins>consuming</ins></u> <u><ins>application</ins></u> <u><ins>to</ins></u> <u><ins>more</ins></u> <u><ins>easily</ins></u>
-  <u><ins>construct</ins></u> <u><ins>the</ins></u> <u><ins>appropriate</ins></u> <u><ins>graph</ins></u> <u><ins>or</ins></u> <u><ins>chart</ins></u> <u><ins>for</ins></u> <u><ins>presentation.</ins></u></p>
-
-<p><u><ins>In</ins></u> <u><ins>statistical</ins></u> <u><ins>applications</ins></u> <u><ins>it</ins></u> <u><ins>is</ins></u> <u><ins>common</ins></u> <u><ins>to</ins></u> <u><ins>work</ins></u> <u><ins>with</ins></u>
-<u><ins>slices</ins></u> <u><ins>in</ins></u> <u><ins>which</ins></u> <u><ins>a</ins></u> <u><ins>single</ins></u> <u><ins>dimension</ins></u> <u><ins>is</ins></u> <u><ins>left</ins></u> <u><ins>unspecified.</ins></u> 
-<u><ins>In</ins></u> <u><ins>particular,</ins></u>
-<u><ins>to</ins></u> <u><ins>refer</ins></u> <u><ins>to</ins></u> <u><ins>such</ins></u> <u><ins>slices</ins></u> <u><ins>in</ins></u> <u><ins>which</ins></u> <u><ins>the</ins></u> <u><ins>single</ins></u> <u><ins>free</ins></u> <u><ins>dimension</ins></u> <u><ins>is</ins></u> <u><ins>time</ins></u> <u><ins>as</ins></u> <em><u><ins>Time</ins></u>
-<u><ins>Series</ins></u></em> <u><ins>and</ins></u> <u><ins>to</ins></u> <u><ins>refer</ins></u> <u><ins>slices</ins></u> <u><ins>along</ins></u> <u><ins>non-time</ins></u> <u><ins>dimensions</ins></u> <u><ins>as</ins></u> <em><u><ins>Sections</ins></u></em><u><ins>.</ins></u>
-<u><ins>Within</ins></u> <u><ins>the</ins></u> <u><ins>Data</ins></u> <u><ins>Cube</ins></u> <u><ins>vocabulary</ins></u> <u><ins>we</ins></u> <u><ins>allow</ins></u> <u><ins>arbitrary</ins></u> <u><ins>dimensionality</ins></u>
-<u><ins>slices</ins></u> <u><ins>and</ins></u> <u><ins>do</ins></u> <u><ins>not</ins></u> <u><ins>give</ins></u> <u><ins>different</ins></u> <u><ins>names</ins></u> <u><ins>to</ins></u> <u><ins>particular</ins></u> <u><ins>types</ins></u> <u><ins>of</ins></u>
-  <u><ins>slice.</ins></u> <u><ins>Such</ins></u> <u><ins>sub-classes</ins></u> <u><ins>of</ins></u> <u><ins>slice</ins></u> <u><ins>could</ins></u> <u><ins>be</ins></u> <u><ins>added</ins></u> <u><ins>in</ins></u> <u><ins>extension</ins></u> <u><ins>vocabularies.</ins></u></p>
+<h3><span class="secno"> <s><del>5.2</del></s><u><ins>5.3</ins></u> </span>Introducing Slices</h3><p><em>This section is non-normative.</em></p>
+
+<p>It is frequently useful to group subsets of observations within a
+dataset. In particular to fix all but one (or a small subset) of the
+dimensions and be able to refer to all observations with those
+dimension values as a single entity. We call such a selection a <em>slice</em>
+through the cube. For example, given a data set on regional performance
+indicators then we might group <u><ins>together</ins></u> all the observations about a given indicator
+and a given  <s><del>region</del></s> <s><del>into</del></s><u><ins>region.</ins></u> <u><ins>Each</ins></u> <u><ins>such</ins></u> <u><ins>group</ins></u> <u><ins>would</ins></u> <u><ins>be</ins></u> a  <s><del>slice,</del></s> <s><del>each</del></s>slice  <s><del>would</del></s> <s><del>then</del></s> <s><del>represent</del></s><u><ins>representing</ins></u> a time
+  series of observed values.</p>
+
+<p>A data publisher may identify slices through the data for various
+purposes. They can be a useful grouping to which metadata might be attached, for example to note a
+change in measurement process which
+affects a particular time or region. Slices also enable the publisher to
+identify and label particular subsets of the data which should be presented to the
+user - they can enable the consuming application to more easily
+  construct the appropriate graph or chart for presentation.</p>
+
+<p>In statistical applications it is common to work with
+slices in which a single dimension is left unspecified. 
+In particular,
+to refer to such slices in which the single free dimension is time as <em>Time
+Series</em> and to refer slices along non-time dimensions as <em>Sections</em>.
+Within the Data Cube vocabulary we allow arbitrary dimensionality
+slices and do not give different names to particular types of
+  slice. Such  <s><del>sub</del></s> <s><del>classes</del></s><u><ins>sub-classes</ins></u> of slice could be added in extension vocabularies.</p>
 
 </section>
 
 <section id="example" class="informative">
-<h3><span class="secno"><u><ins>5.4</ins></u> </span><u><ins>An</ins></u> <u><ins>example</ins></u></h3><p><em><u><ins>This</ins></u> <u><ins>section</ins></u> <u><ins>is</ins></u> <u><ins>non-normative.</ins></u></em></p>
-
-<p><u><ins>In</ins></u> <u><ins>order</ins></u> <u><ins>to</ins></u> <u><ins>illustrate</ins></u> <u><ins>the</ins></u> <u><ins>use</ins></u> <u><ins>of</ins></u> <u><ins>the</ins></u> <u><ins>data</ins></u> <u><ins>cube</ins></u> <u><ins>vocabulary</ins></u> <u><ins>we</ins></u> <u><ins>will</ins></u>
-<u><ins>use</ins></u> <u><ins>a</ins></u> <u><ins>small</ins></u> <u><ins>demonstration</ins></u>
-<u><ins>data</ins></u> <u><ins>set</ins></u> <u><ins>extracted</ins></u> <u><ins>from</ins></u>
-<a href="http://statswales.wales.gov.uk/index.htm"><u><ins>StatsWales</ins></u></a> <u><ins>report</ins></u>
-<u><ins>number</ins></u> <u><ins>003311</ins></u> <u><ins>which</ins></u> <u><ins>describes</ins></u> <u><ins>life</ins></u> <u><ins>expectancy</ins></u> <u><ins>broken</ins></u> <u><ins>down</ins></u> <u><ins>by</ins></u> <u><ins>region</ins></u>
-<u><ins>(unitary</ins></u> <u><ins>authority),</ins></u> <u><ins>age</ins></u> and time. The extract we will use is:<br>
+<h3><span class="secno"> <s><del>5.3</del></s><u><ins>5.4</ins></u> </span>An example</h3><p><em>This section is non-normative.</em></p>
+
+<p>In order to illustrate the use of the data cube vocabulary we will
+use a small demonstration
+data set extracted from
+<a href="http://statswales.wales.gov.uk/index.htm">StatsWales</a> report
+number 003311 which describes life expectancy broken down by region
+(unitary authority), age and time. The extract we will use is:<br>
 </p>
 
 <table id="example-data" style="text-align: left; width: 80%;">
@@ -869,9 +891,9 @@
    in particular helps with detection of incoherent sets obtained by 
    combining differently structured source data;</li>
   <li>it allows a consumer to easily determine what dimensions are available for query
-    and their presentational order, which in turn simplifies <u><ins>data</ins></u>
-    <u><ins>consumption,</ins></u> <u><ins>for</ins></u> <u><ins>example</ins></u> <u><ins>for</ins></u> UI construction;</li>
-  <li>it supports transmission of the structure information in
+    and their presentational order, which in turn simplifies  <s><del>UI</del></s> <s><del>construction;</del></s> <s><del>it</del></s><u><ins>data</ins></u>
+    <u><ins>consumption,</ins></u> <u><ins>for</ins></u> <u><ins>example</ins></u> <u><ins>for</ins></u> <u><ins>UI</ins></u> <u><ins>construction;</ins></u></li>
+  <li><u><ins>it</ins></u> supports transmission of the structure information in
   associated SDMX data  <s><del>flows.</del></s><u><ins>flows</ins></u> <u><ins>(see</ins></u> <u><ins>below).</ins></u></li>
 </ul>
 
@@ -1240,8 +1262,8 @@
 <section id="dataset-basic">
 <h3><span class="secno"><u><ins>7.1</ins></u> </span><u><ins>Data</ins></u> <u><ins>sets</ins></u> <u><ins>and</ins></u> <u><ins>observations</ins></u></h3>
 
-<p>A  <s><del>DataSet</del></s> <s><del>is</del></s> <s><del>a</del></s> <s><del>collection</del></s> <s><del>of</del></s> <s><del>statistical</del></s> <s><del>data</del></s> <s><del>that</del></s> <s><del>corresponds</del></s> <s><del>to</del></s> <s><del>a</del></s> <s><del>given</del></s> <s><del>data</del></s> <s><del>structure</del></s> <s><del>definition.</del></s> <s><del>The</del></s> <s><del>data</del></s> <s><del>in</del></s> <s><del>a</del></s><u><ins>resource</ins></u> <u><ins>representing</ins></u> <u><ins>the</ins></u> <u><ins>entire</ins></u> data set  <s><del>can</del></s> <s><del>be</del></s> <s><del>roughly</del></s> <s><del>described</del></s><u><ins>is</ins></u> <u><ins>created</ins></u> <u><ins>and</ins></u> <u><ins>typed</ins></u> as <code><a href="#dfn-qb-dataset" class="internalDFN"> <s><del>belonging</del></s> <s><del>to</del></s> <s><del>one</del></s> <s><del>of</del></s> <s><del>the</del></s> <s><del>following</del></s> <s><del>kinds:</del></s> <s><del>Observations</del></s> <s><del>This</del></s> <s><del>is</del></s> <s><del>the</del></s> <s><del>actual</del></s> <s><del>data,</del></s> <s><del>the</del></s> <s><del>measured</del></s> <s><del>numbers.</del></s> <s><del>In</del></s> <s><del>a</del></s> <s><del>statistical</del></s> <s><del>table,</del></s> <s><del>the</del></s> <s><del>observations</del></s> <s><del>would</del></s> <s><del>be</del></s> <s><del>the</del></s> <s><del>numbers</del></s> <s><del>in</del></s> <s><del>the</del></s> <s><del>table</del></s> <s><del>cells.</del></s> <s><del>Organizational</del></s> <s><del>structure</del></s> <s><del>To</del></s> <s><del>locate</del></s> <s><del>an</del></s> <s><del>observation</del></s> <s><del>within</del></s> <s><del>the</del></s> <s><del>hypercube,</del></s> <s><del>one</del></s> <s><del>has</del></s> <s><del>at</del></s> <s><del>least</del></s> <s><del>to</del></s> <s><del>know</del></s> <s><del>the</del></s> <s><del>value</del></s> <s><del>of</del></s> <s><del>each</del></s> <s><del>dimension</del></s> <s><del>at</del></s> <s><del>which</del></s> <s><del>the</del></s> <s><del>observation</del></s> <s><del>is</del></s> <s><del>located,</del></s> <s><del>so</del></s> <s><del>these</del></s> <s><del>values</del></s> <s><del>must</del></s> <s><del>be</del></s> <s><del>specified</del></s> <s><del>for</del></s> <s><del>each</del></s> <s><del>observation.</del></s> <s><del>Datasets</del></s> <s><del>can</del></s> <s><del>have</del></s> <s><del>additional</del></s> <s><del>organizational</del></s> <s><del>structure</del></s> <s><del>in</del></s> <s><del>the</del></s> <s><del>form</del></s> <s><del>of</del></s> <s><del>slices</del></s> <s><del>as</del></s> <s><del>described</del></s> <s><del>earlier</del></s> <s><del>in</del></s> <s><del>section</del></s> <s><del>7.2</del></s> <s><del>.</del></s> <s><del>Internal</del></s> <s><del>metadata</del></s> <s><del>Having</del></s> <s><del>located</del></s> <s><del>an</del></s> <s><del>observation,</del></s> <s><del>we</del></s> <s><del>need</del></s> <s><del>certain</del></s> <s><del>metadata</del></s> <s><del>in</del></s> <s><del>order</del></s> <s><del>to</del></s> <s><del>be</del></s> <s><del>able</del></s> <s><del>to</del></s> <s><del>interpret</del></s> <s><del>it.</del></s> <s><del>What</del></s> <s><del>is</del></s> <s><del>the</del></s> <s><del>unit</del></s> <s><del>of</del></s> <s><del>measurement?</del></s> <s><del>Is</del></s> <s><del>it</del></s> <s><del>a</del></s> <s><del>normal</del></s> <s><del>value</del></s> <s><del>or</del></s> <s><del>a</del></s> <s><del>series</del></s> <s><del>break?</del></s> <s><del>Is</del></s> <s><del>the</del></s> <s><del>value</del></s> <s><del>measured</del></s> <s><del>or</del></s> <s><del>estimated?</del></s> <s><del>These</del></s> <s><del>metadata</del></s> <s><del>are</del></s> <s><del>provided</del></s> <s><del>as</del></s> <s><del>attributes</del></s> <s><del>and</del></s> <s><del>can</del></s> <s><del>be</del></s> <s><del>attached</del></s> <s><del>to</del></s> <s><del>individual</del></s> <s><del>observations,</del></s> <s><del>or</del></s> <s><del>to</del></s> <s><del>higher</del></s> <s><del>levels</del></s> <s><del>as</del></s> <s><del>defined</del></s> <s><del>by</del></s> <s><del>the</del></s> <s><del>ComponentSpecification</del></s> <s><del>described</del></s> <s><del>earlier.</del></s> <s><del>External</del></s> <s><del>metadata</del></s> <s><del>This</del></s> <s><del>is</del></s> <s><del>metadata</del></s> <s><del>that</del></s> <s><del>describes</del></s> <s><del>the</del></s> <s><del>dataset</del></s> <s><del>as</del></s> <s><del>a</del></s> <s><del>whole,</del></s> <s><del>such</del></s> <s><del>as</del></s> <s><del>categorization</del></s> <s><del>of</del></s> <s><del>the</del></s> <s><del>dataset,</del></s> <s><del>its</del></s> <s><del>publisher,</del></s> <s><del>and</del></s> <s><del>a</del></s> <s><del>SPARQL</del></s> <s><del>endpoint</del></s> <s><del>where</del></s> <s><del>it</del></s> <s><del>can</del></s> <s><del>be</del></s> <s><del>accessed.</del></s> <s><del>External</del></s> <s><del>metadata</del></s> <s><del>is</del></s> <s><del>described</del></s> <s><del>in</del></s> <s><del>section</del></s> <s><del>9</del></s> <s><del>.</del></s> <s><del>7.1</del></s> <s><del>Data</del></s> <s><del>sets</del></s> <s><del>and</del></s> <s><del>observations</del></s> <s><del>A</del></s> <s><del>resource</del></s> <s><del>representing</del></s> <s><del>the</del></s> <s><del>entire</del></s> <s><del>data</del></s> <s><del>set</del></s> <s><del>is</del></s> <s><del>created</del></s> <s><del>and</del></s> <s><del>typed</del></s> <s><del>as</del></s> <s><del>qb:DataSet</del></s> <s><del>and</del></s> <s><del>linked</del></s><u><ins>qb:DataSet</ins></u></a></code> <u><ins>and</ins></u>
-  <u><ins>linked</ins></u> to the corresponding data structure definition via the <code><a href="#dfn-qb-structure" class="internalDFN">qb:structure</a></code> property.</p>
+<p>A  <s><del>DataSet</del></s> <s><del>is</del></s> <s><del>a</del></s> <s><del>collection</del></s> <s><del>of</del></s> <s><del>statistical</del></s><u><ins>resource</ins></u> <u><ins>representing</ins></u> <u><ins>the</ins></u> <u><ins>entire</ins></u> data  <s><del>that</del></s> <s><del>corresponds</del></s><u><ins>set</ins></u> <u><ins>is</ins></u> <u><ins>created</ins></u> <u><ins>and</ins></u> <u><ins>typed</ins></u> <u><ins>as</ins></u> <code><a href="#dfn-qb-dataset" class="internalDFN"><u><ins>qb:DataSet</ins></u></a></code> <u><ins>and</ins></u>
+  <u><ins>linked</ins></u> to  <s><del>a</del></s> <s><del>given</del></s> <s><del>data</del></s> <s><del>structure</del></s> <s><del>definition.</del></s> <s><del>The</del></s> <s><del>data</del></s> <s><del>in</del></s> <s><del>a</del></s> <s><del>data</del></s> <s><del>set</del></s> <s><del>can</del></s> <s><del>be</del></s> <s><del>roughly</del></s> <s><del>described</del></s> <s><del>as</del></s> <s><del>belonging</del></s> <s><del>to</del></s> <s><del>one</del></s> <s><del>of</del></s> <s><del>the</del></s> <s><del>following</del></s> <s><del>kinds:</del></s> <s><del>Observations</del></s> <s><del>This</del></s> <s><del>is</del></s> <s><del>the</del></s> <s><del>actual</del></s> <s><del>data,</del></s> <s><del>the</del></s> <s><del>measured</del></s> <s><del>numbers.</del></s> <s><del>In</del></s> <s><del>a</del></s> <s><del>statistical</del></s> <s><del>table,</del></s> <s><del>the</del></s> <s><del>observations</del></s> <s><del>would</del></s> <s><del>be</del></s> <s><del>the</del></s> <s><del>numbers</del></s> <s><del>in</del></s> <s><del>the</del></s> <s><del>table</del></s> <s><del>cells.</del></s> <s><del>Organizational</del></s> <s><del>structure</del></s> <s><del>To</del></s> <s><del>locate</del></s> <s><del>an</del></s> <s><del>observation</del></s> <s><del>within</del></s> <s><del>the</del></s> <s><del>hypercube,</del></s> <s><del>one</del></s> <s><del>has</del></s> <s><del>at</del></s> <s><del>least</del></s> <s><del>to</del></s> <s><del>know</del></s> <s><del>the</del></s> <s><del>value</del></s> <s><del>of</del></s> <s><del>each</del></s> <s><del>dimension</del></s> <s><del>at</del></s> <s><del>which</del></s> <s><del>the</del></s> <s><del>observation</del></s> <s><del>is</del></s> <s><del>located,</del></s> <s><del>so</del></s> <s><del>these</del></s> <s><del>values</del></s> <s><del>must</del></s> <s><del>be</del></s> <s><del>specified</del></s> <s><del>for</del></s> <s><del>each</del></s> <s><del>observation.</del></s> <s><del>Datasets</del></s> <s><del>can</del></s> <s><del>have</del></s> <s><del>additional</del></s> <s><del>organizational</del></s> <s><del>structure</del></s> <s><del>in</del></s> <s><del>the</del></s> <s><del>form</del></s> <s><del>of</del></s> <s><del>slices</del></s> <s><del>as</del></s> <s><del>described</del></s> <s><del>earlier</del></s> <s><del>in</del></s> <s><del>section</del></s> <s><del>7.2</del></s> <s><del>.</del></s> <s><del>Internal</del></s> <s><del>metadata</del></s> <s><del>Having</del></s> <s><del>located</del></s> <s><del>an</del></s> <s><del>observation,</del></s> <s><del>we</del></s> <s><del>need</del></s> <s><del>certain</del></s> <s><del>metadata</del></s> <s><del>in</del></s> <s><del>order</del></s> <s><del>to</del></s> <s><del>be</del></s> <s><del>able</del></s> <s><del>to</del></s> <s><del>interpret</del></s> <s><del>it.</del></s> <s><del>What</del></s> <s><del>is</del></s> <s><del>the</del></s> <s><del>unit</del></s> <s><del>of</del></s> <s><del>measurement?</del></s> <s><del>Is</del></s> <s><del>it</del></s> <s><del>a</del></s> <s><del>normal</del></s> <s><del>value</del></s> <s><del>or</del></s> <s><del>a</del></s> <s><del>series</del></s> <s><del>break?</del></s> <s><del>Is</del></s> <s><del>the</del></s> <s><del>value</del></s> <s><del>measured</del></s> <s><del>or</del></s> <s><del>estimated?</del></s> <s><del>These</del></s> <s><del>metadata</del></s> <s><del>are</del></s> <s><del>provided</del></s> <s><del>as</del></s> <s><del>attributes</del></s> <s><del>and</del></s> <s><del>can</del></s> <s><del>be</del></s> <s><del>attached</del></s> <s><del>to</del></s> <s><del>individual</del></s> <s><del>observations,</del></s> <s><del>or</del></s> <s><del>to</del></s> <s><del>higher</del></s> <s><del>levels</del></s> <s><del>as</del></s> <s><del>defined</del></s> <s><del>by</del></s> <s><del>the</del></s> <s><del>ComponentSpecification</del></s> <s><del>described</del></s> <s><del>earlier.</del></s> <s><del>External</del></s> <s><del>metadata</del></s> <s><del>This</del></s> <s><del>is</del></s> <s><del>metadata</del></s> <s><del>that</del></s> <s><del>describes</del></s> <s><del>the</del></s> <s><del>dataset</del></s> <s><del>as</del></s> <s><del>a</del></s> <s><del>whole,</del></s> <s><del>such</del></s> <s><del>as</del></s> <s><del>categorization</del></s> <s><del>of</del></s> <s><del>the</del></s> <s><del>dataset,</del></s> <s><del>its</del></s> <s><del>publisher,</del></s> <s><del>and</del></s> <s><del>a</del></s> <s><del>SPARQL</del></s> <s><del>endpoint</del></s> <s><del>where</del></s> <s><del>it</del></s> <s><del>can</del></s> <s><del>be</del></s> <s><del>accessed.</del></s> <s><del>External</del></s> <s><del>metadata</del></s> <s><del>is</del></s> <s><del>described</del></s> <s><del>in</del></s> <s><del>section</del></s> <s><del>9</del></s> <s><del>.</del></s> <s><del>7.1</del></s> <s><del>Data</del></s> <s><del>sets</del></s> <s><del>and</del></s> <s><del>observations</del></s> <s><del>A</del></s> <s><del>resource</del></s> <s><del>representing</del></s> <s><del>the</del></s> <s><del>entire</del></s> <s><del>data</del></s> <s><del>set</del></s> <s><del>is</del></s> <s><del>created</del></s> <s><del>and</del></s> <s><del>typed</del></s> <s><del>as</del></s> <s><del>qb:DataSet</del></s> <s><del>and</del></s> <s><del>linked</del></s> <s><del>to</del></s> <s><del>the</del></s> <s><del>corresponding</del></s><u><ins>the</ins></u> <u><ins>corresponding</ins></u> data structure definition via the <code><a href="#dfn-qb-structure" class="internalDFN">qb:structure</a></code> property.</p>
 
 <p><strong>Pitfall</strong>: Note the capitalization of <code>qb:<strong>D</strong>ata<strong>S</strong>et</code>, 
 which differs from the capitalization in other vocabularies, such as
@@ -1597,7 +1619,7 @@
 and an administrative hierarchy which do not precisely align. </li>
 </ul>
 
-<p>The  <s><del>SKOS</del></s> <s><del>relations</del></s> <s><del>do</del></s> <s><del>not</del></s> <s><del>define</del></s> <s><del>when</del></s> <s><del>the</del></s> <s><del>child</del></s> <s><del>concepts</del></s> <s><del>are</del></s> <s><del>disjoint</del></s> <s><del>(mutually</del></s> <s><del>exclusive)</del></s> <s><del>or</del></s> <s><del>when</del></s> <s><del>they</del></s> <s><del>form</del></s> <s><del>a</del></s> <s><del>complete</del></s> <s><del>cover</del></s> <s><del>of</del></s> <s><del>the</del></s> <s><del>parent</del></s> <s><del>concept</del></s> <s><del>(exhaustive).</del></s> <s><del>The</del></s> <s><del>Data</del></s> <s><del>Cube</del></s> <s><del>vocabulary</del></s> <s><del>supports</del></s> <s><del>this</del></s> <s><del>situation</del></s> <s><del>through</del></s><u><ins>Data</ins></u> <u><ins>Cube</ins></u> <u><ins>vocabulary</ins></u> <u><ins>supports</ins></u> <u><ins>this</ins></u> <u><ins>situation</ins></u> <u><ins>through</ins></u> the <code><a href="#dfn-qb-hierarchicalcodelist" class="internalDFN">qb:HierarchicalCodeList</a></code> class.
+<p>The  <s><del>SKOS</del></s> <s><del>relations</del></s> <s><del>do</del></s> <s><del>not</del></s> <s><del>define</del></s> <s><del>when</del></s> <s><del>the</del></s> <s><del>child</del></s> <s><del>concepts</del></s> <s><del>are</del></s> <s><del>disjoint</del></s> <s><del>(mutually</del></s> <s><del>exclusive)</del></s> <s><del>or</del></s> <s><del>when</del></s> <s><del>they</del></s> <s><del>form</del></s> <s><del>a</del></s> <s><del>complete</del></s> <s><del>cover</del></s> <s><del>of</del></s> <s><del>the</del></s> <s><del>parent</del></s> <s><del>concept</del></s> <s><del>(exhaustive).</del></s> <s><del>The</del></s>Data Cube vocabulary supports this situation through the <code><a href="#dfn-qb-hierarchicalcodelist" class="internalDFN">qb:HierarchicalCodeList</a></code> class.
 An instance of <code><a href="#dfn-qb-hierarchicalcodelist" class="internalDFN">qb:HierarchicalCodeList</a></code> defines a set of root concepts in the hierarchy 
 (<code><a href="#dfn-qb-hierarchyroot" class="internalDFN">qb:hierarchyRoot</a></code>) and a parent-to-child relationship (<code><a href="#dfn-qb-parentchildproperty" class="internalDFN">qb:parentChildProperty</a></code>) which
 links a term in the hierarchy to its immediate sub-terms. </p>
@@ -2903,7 +2925,8 @@
 suggestions and support for the original work.</p>
 
 <p>Many individuals provided valuable comments on this specification
-as it made its way through the <abbr title="World Wide Web Consortium">W3C</abbr> process. We would like to 
+as it made its way through the <abbr title="World
+  Wide Web Consortium">W3C</abbr> process. We would like to 
 especially acknowledge the contributions of
 Benedikt Kaempgen, Sarven Capadisli and Curran  Kelleher.</p>
 
@@ -2913,35 +2936,36 @@
 <!--OddPage--><h2><span class="secno">B. </span>Change history </h2>
 
 <p>Changes
-  since <a href="http://www.w3.org/TR/2013/WD-vocab-data-cube-20130312/"><abbr title="World Wide Web Consortium">W3C</abbr>
-    <u><ins>Last</ins></u> <u><ins>Call</ins></u> Working Draft <u><ins>12</ins></u> <u><ins>March</ins></u> <u><ins>2013</ins></u></a><u><ins>:</ins></u></p>
+  since <a href="http://www.w3.org/TR/2013/WD-vocab-data-cube-20130312/"><abbr title="World
+  Wide Web Consortium">W3C</abbr>
+    <u><ins>Last</ins></u> <u><ins>Call</ins></u> Working Draft  <s><del>5</del></s> <s><del>April</del></s> <s><del>2012</del></s><u><ins>12</ins></u> <u><ins>March</ins></u> <u><ins>2013</ins></u></a>:</p>
 
 <ul>
-  <li><u><ins>Section</ins></u> <u><ins>1.</ins></u> <u><ins>Modified</ins></u> <u><ins>diagram</ins></u> <u><ins>to</ins></u> <u><ins>clarify</ins></u> <u><ins>that</ins></u> <code><a href="#dfn-qb-slice" class="internalDFN"><u><ins>qb:Slice</ins></u></a></code> <u><ins>is</ins></u> <u><ins>a</ins></u> <u><ins>sub</ins></u>
+  <li> <s><del>Added</del></s> <s><del>section</del></s> <s><del>on</del></s> <s><del>criteria</del></s><u><ins>Section</ins></u> <u><ins>1.</ins></u> <u><ins>Modified</ins></u> <u><ins>diagram</ins></u> <u><ins>to</ins></u> <u><ins>clarify</ins></u> <u><ins>that</ins></u> <code><a href="#dfn-qb-slice" class="internalDFN"><u><ins>qb:Slice</ins></u></a></code> <u><ins>is</ins></u> <u><ins>a</ins></u> <u><ins>sub</ins></u>
   <u><ins>class</ins></u> <u><ins>of</ins></u> <code><a href="#dfn-qb-observationgroup" class="internalDFN"><u><ins>qb:ObservationGroup</ins></u></a></code> </li>
-  <li><u><ins>Section</ins></u> <u><ins>5.1.</ins></u> <u><ins>Moved</ins></u> <u><ins>description</ins></u> <u><ins>of</ins></u> <u><ins>data</ins></u> <u><ins>set</ins></u> <u><ins>here</ins></u> <u><ins>for</ins></u> <u><ins>greater</ins></u>
-  <u><ins>clarity,</ins></u> <u><ins>was</ins></u> <u><ins>in</ins></u> <u><ins>section</ins></u> <u><ins>7.</ins></u></li>
+  <li><u><ins>Section</ins></u> <u><ins>5.1.</ins></u> <u><ins>Moved</ins></u> <u><ins>description</ins></u> <u><ins>of</ins></u> <u><ins>data</ins></u> <u><ins>set</ins></u> <u><ins>here</ins></u> for  <s><del>well-formed</del></s> <s><del>cubes.</del></s> <s><del>ISSUE-29</del></s> <s><del>Added</del></s><u><ins>greater</ins></u>
+  <u><ins>clarity,</ins></u> <u><ins>was</ins></u> <u><ins>in</ins></u> section  <s><del>on</del></s> <s><del>normalization</del></s> <s><del>algorithm</del></s><u><ins>7.</ins></u></li>
   <li><u><ins>Section</ins></u> <u><ins>6.2.</ins></u> <u><ins>Further</ins></u> <u><ins>clarified</ins></u> <u><ins>the</ins></u> <u><ins>status</ins></u> <u><ins>of</ins></u> <u><ins>COG</ins></u> <u><ins>RDF</ins></u> <u><ins>vocabularies.</ins></u></li>
-  <li><u><ins>Example</ins></u> <u><ins>6.3.</ins></u> <u><ins>Retitled</ins></u> <u><ins>for</ins></u> <u><ins>clarity.</ins></u></li>
+  <li><u><ins>Example</ins></u> <u><ins>6.3.</ins></u> <u><ins>Retitled</ins></u> for  <s><del>handling</del></s> <s><del>abbreviated</del></s> <s><del>cubes.</del></s><u><ins>clarity.</ins></u></li>
   <li><u><ins>Section</ins></u> <u><ins>6.4,</ins></u> <u><ins>corrected</ins></u> <u><ins>"with</ins></u> <u><ins>multiple</ins></u> <u><ins>observations"</ins></u> <u><ins>to</ins></u> <u><ins>"with</ins></u>
   <u><ins>multiple</ins></u> <u><ins>measures".</ins></u></li>
-  <li><u><ins>Section</ins></u> <u><ins>6.4.</ins></u> <u><ins>Added</ins></u> <u><ins>mention</ins></u> <u><ins>of</ins></u> <code><a href="#dfn-qb-attachable" class="internalDFN"><u><ins>qb:Attachable</ins></u></a></code> <u><ins>(previously</ins></u> <u><ins>only</ins></u>
+  <li><u><ins>Section</ins></u> <u><ins>6.4.</ins></u> Added  <s><del>conformance</del></s> <s><del>section</del></s> <s><del>.</del></s> <s><del>Clarified</del></s><u><ins>mention</ins></u> <u><ins>of</ins></u> <code><a href="#dfn-qb-attachable" class="internalDFN"><u><ins>qb:Attachable</ins></u></a></code> <u><ins>(previously</ins></u> <u><ins>only</ins></u>
   <u><ins>mentioned</ins></u> <u><ins>in</ins></u> <u><ins>the</ins></u> <u><ins>vocabulary</ins></u> <u><ins>reference).</ins></u></li>
   <li><u><ins>Section</ins></u> <u><ins>6.5.</ins></u> <u><ins>Rewritten</ins></u> <u><ins>description</ins></u> <u><ins>of</ins></u> <u><ins>handling</ins></u> <u><ins>of</ins></u> <u><ins>multiple</ins></u>
   <u><ins>measures</ins></u> <u><ins>for</ins></u> <u><ins>greater</ins></u> <u><ins>clarity.</ins></u></li>
   <li><u><ins>Section</ins></u> <u><ins>6.5.2.</ins></u> <u><ins>Removed</ins></u> <u><ins>reference</ins></u> <u><ins>to</ins></u> <u><ins>"SDMX-in-RDF</ins></u> <u><ins>vocabulary"</ins></u>
   <u><ins>which</ins></u> <u><ins>is</ins></u> <u><ins>not</ins></u> <u><ins>part</ins></u> <u><ins>of</ins></u> <u><ins>this</ins></u> <u><ins>specification.</ins></u></li>
-  <li><u><ins>Section</ins></u> <u><ins>6.5.2</ins></u> <u><ins>clarified</ins></u> <u><ins>that</ins></u> <u><ins>the</ins></u> <u><ins>special</ins></u> <u><ins>nature</ins></u> <u><ins>of</ins></u>
-  <code><a href="#dfn-qb-measuretype" class="internalDFN"><u><ins>qb:measureType</ins></u></a></code> <u><ins>is</ins></u> <u><ins>a</ins></u> <u><ins>divergence</ins></u> <u><ins>from</ins></u> <u><ins>SDMX.</ins></u></li>
+  <li><u><ins>Section</ins></u> <u><ins>6.5.2</ins></u> <u><ins>clarified</ins></u> that  <s><del>qb:componentRequired</del></s><u><ins>the</ins></u> <u><ins>special</ins></u> <u><ins>nature</ins></u> <u><ins>of</ins></u>
+  <code><a href="#dfn-qb-measuretype" class="internalDFN"><u><ins>qb:measureType</ins></u></a></code> is  <s><del>only</del></s> <s><del>applicable</del></s><u><ins>a</ins></u> <u><ins>divergence</ins></u> <u><ins>from</ins></u> <u><ins>SDMX.</ins></u></li>
   <li><u><ins>Section</ins></u> <u><ins>7.</ins></u> <u><ins>Change</ins></u> <u><ins>terminology</ins></u> <u><ins>from</ins></u> <u><ins>"internal</ins></u> <u><ins>and</ins></u> <u><ins>external</ins></u>
-  <u><ins>metadata"</ins></u> <u><ins>to</ins></u> <u><ins>"structural</ins></u> <u><ins>and</ins></u> <u><ins>reference"</ins></u> <u><ins>metadata</ins></u> <u><ins>for</ins></u> <u><ins>compatibility</ins></u>
+  <u><ins>metadata"</ins></u> to  <s><del>attributes</del></s><u><ins>"structural</ins></u> and <u><ins>reference"</ins></u> <u><ins>metadata</ins></u> <u><ins>for</ins></u> <u><ins>compatibility</ins></u>
   <u><ins>with</ins></u> <u><ins>SDMX</ins></u> <u><ins>terminology.</ins></u></li>
-  <li><u><ins>Section</ins></u> <u><ins>8.2.</ins></u> <u><ins>Clarified</ins></u> <u><ins>that</ins></u> <u><ins>sub</ins></u> <u><ins>properties</ins></u> <u><ins>of</ins></u> <code><u><ins>skos:narrower</ins></u></code> <u><ins>may</ins></u>
+  <li><u><ins>Section</ins></u> <u><ins>8.2.</ins></u> <u><ins>Clarified</ins></u> that  <s><del>it</del></s> <s><del>defaults</del></s> <s><del>to</del></s> <s><del>optional.</del></s> <s><del>Moved</del></s> <s><del>vocabulary</del></s> <s><del>reference</del></s> <s><del>into</del></s> <s><del>the</del></s> <s><del>normative</del></s> <s><del>body</del></s><u><ins>sub</ins></u> <u><ins>properties</ins></u> of <code><u><ins>skos:narrower</ins></u></code> <u><ins>may</ins></u>
   <u><ins>be</ins></u> <u><ins>used.</ins></u></li>
-  <li><u><ins>Section</ins></u> <u><ins>8.3.</ins></u> <u><ins>Removed</ins></u> <u><ins>third</ins></u> <u><ins>bullet</ins></u> <u><ins>on</ins></u> <u><ins>the</ins></u> <u><ins>motivation</ins></u> <u><ins>for</ins></u>
-  <code><a href="#dfn-qb-hierarchicalcodelist" class="internalDFN"><u><ins>qb:HierarchicalCodeList</ins></u></a></code> <u><ins>(exhaustivity</ins></u> <u><ins>and</ins></u> <u><ins>mutual</ins></u> <u><ins>exclusion).</ins></u></li>
-  <li><u><ins>Added</ins></u> <u><ins>reference</ins></u> <u><ins>to</ins></u> <u><ins>SDMX</ins></u> <u><ins>User</ins></u> <u><ins>Guide</ins></u> <u><ins>as</ins></u> <u><ins>additional</ins></u> <u><ins>background</ins></u> <u><ins>context.</ins></u></li>
-  <li><u><ins>Added</ins></u> <u><ins>complete</ins></u> <u><ins>example</ins></u> <u><ins>Data</ins></u> <u><ins>Cube</ins></u> <u><ins>as</ins></u> <u><ins>an</ins></u> <u><ins>appendix,</ins></u> <u><ins>providing</ins></u> <u><ins>a</ins></u>
+  <li><u><ins>Section</ins></u> <u><ins>8.3.</ins></u> <u><ins>Removed</ins></u> <u><ins>third</ins></u> <u><ins>bullet</ins></u> <u><ins>on</ins></u> the  <s><del>specification,</del></s> <s><del>adding</del></s> <s><del>hyperlinks</del></s><u><ins>motivation</ins></u> for
+  <code><a href="#dfn-qb-hierarchicalcodelist" class="internalDFN"> <s><del>all</del></s> <s><del>qb:</del></s> <s><del>terms.</del></s><u><ins>qb:HierarchicalCodeList</ins></u></a></code> <u><ins>(exhaustivity</ins></u> <u><ins>and</ins></u> <u><ins>mutual</ins></u> <u><ins>exclusion).</ins></u></li>
+  <li>Added  <s><del>section</del></s> <s><del>on</del></s> <s><del>non-skos</del></s> <s><del>hierarchies.</del></s> <s><del>ISSUE-31</del></s> <s><del>.</del></s><u><ins>reference</ins></u> <u><ins>to</ins></u> <u><ins>SDMX</ins></u> <u><ins>User</ins></u> <u><ins>Guide</ins></u> <u><ins>as</ins></u> <u><ins>additional</ins></u> <u><ins>background</ins></u> <u><ins>context.</ins></u></li>
+  <li>Added  <s><del>note</del></s> <s><del>that</del></s> <s><del>aggregation</del></s><u><ins>complete</ins></u> <u><ins>example</ins></u> <u><ins>Data</ins></u> <u><ins>Cube</ins></u> <u><ins>as</ins></u> <u><ins>an</ins></u> <u><ins>appendix,</ins></u> <u><ins>providing</ins></u> <u><ins>a</ins></u>
   <u><ins>link</ins></u> <u><ins>to</ins></u> <u><ins>it</ins></u> <u><ins>from</ins></u> <u><ins>earlier</ins></u> <u><ins>on</ins></u> <u><ins>in</ins></u> <u><ins>the</ins></u> <u><ins>document.</ins></u>
   </li><li><u><ins>Section</ins></u> <u><ins>10.</ins></u> <u><ins>Clarified</ins></u> <u><ins>that</ins></u> <u><ins>abbreviated</ins></u> <u><ins>form</ins></u> <u><ins>is</ins></u> <u><ins>an</ins></u> <u><ins>option,</ins></u> <u><ins>and</ins></u>
   <u><ins>there</ins></u> <u><ins>is</ins></u> <u><ins>no</ins></u> <u><ins>requirement</ins></u> <u><ins>to</ins></u> <u><ins>use</ins></u> <u><ins>it</ins></u> <u><ins>in</ins></u> <u><ins>place</ins></u> <u><ins>of</ins></u> <u><ins>normalized</ins></u> <u><ins>form.</ins></u></li>
@@ -2951,7 +2975,8 @@
   <li><u><ins>Various</ins></u> <u><ins>typographical</ins></u> <u><ins>corrections.</ins></u></li>
 </ul>
 
-<p><u><ins>Changes</ins></u> <u><ins>since</ins></u> <a href="http://www.w3.org/TR/2012/WD-vocab-data-cube-20120405/"><abbr title="World Wide Web Consortium"><u><ins>W3C</ins></u></abbr> <u><ins>Working</ins></u> <u><ins>Draft</ins></u> <u><ins>5</ins></u> <u><ins>April</ins></u> <u><ins>2012</ins></u></a><u><ins>:</ins></u></p>
+<p><u><ins>Changes</ins></u> <u><ins>since</ins></u> <a href="http://www.w3.org/TR/2012/WD-vocab-data-cube-20120405/"><abbr title="World
+  Wide Web Consortium"><u><ins>W3C</ins></u></abbr> <u><ins>Working</ins></u> <u><ins>Draft</ins></u> <u><ins>5</ins></u> <u><ins>April</ins></u> <u><ins>2012</ins></u></a><u><ins>:</ins></u></p>
 
 <ul>
   <li><u><ins>Added</ins></u> <a href="#wf"><u><ins>section</ins></u></a> <u><ins>on</ins></u> <u><ins>criteria</ins></u> <u><ins>for</ins></u> <u><ins>well-formed</ins></u> <u><ins>cubes.</ins></u> <a href="http://www.w3.org/2011/gld/track/issues/29"><u><ins>ISSUE-29</ins></u></a></li>
@@ -2962,8 +2987,8 @@
   <u><ins>attributes</ins></u> <u><ins>and</ins></u> <u><ins>that</ins></u> <u><ins>it</ins></u> <u><ins>defaults</ins></u> <u><ins>to</ins></u> <u><ins>optional.</ins></u></li>
   <li><u><ins>Moved</ins></u> <u><ins>vocabulary</ins></u> <u><ins>reference</ins></u> <u><ins>into</ins></u> <u><ins>the</ins></u> <u><ins>normative</ins></u> <u><ins>body</ins></u> <u><ins>of</ins></u> <u><ins>the</ins></u> <u><ins>specification,</ins></u> <u><ins>adding</ins></u> <u><ins>hyperlinks</ins></u> <u><ins>for</ins></u> <u><ins>all</ins></u> <u><ins>qb:</ins></u> <u><ins>terms.</ins></u></li>
   <li><u><ins>Added</ins></u> <a href="#schemes-hierarchy-nonskos"><u><ins>section</ins></u></a> <u><ins>on</ins></u> <u><ins>non-skos</ins></u> <u><ins>hierarchies.</ins></u> <a href="http://www.w3.org/2011/gld/track/issues/31"><u><ins>ISSUE-31</ins></u></a><u><ins>.</ins></u></li>
-  <li><u><ins>Added</ins></u> <a href="#schemes-aggregation"><u><ins>note</ins></u></a> <u><ins>that</ins></u> <u><ins>aggregation</ins></u> <u><ins>operations</ins></u> <u><ins>and</ins></u> <u><ins>inter-cube</ins></u> <u><ins>relations</ins></u> <u><ins>are</ins></u> <u><ins>out</ins></u> <u><ins>of</ins></u> <u><ins>scope</ins></u> <u><ins>for</ins></u> <u><ins>this</ins></u> <u><ins>version.</ins></u> <a href="http://www.w3.org/2011/gld/track/issues/30"><u><ins>ISSUE-30</ins></u></a><u><ins>.</ins></u></li>
-  <li><u><ins>Added</ins></u> <code><a href="#dfn-qb-observationgroup" class="internalDFN"><u><ins>qb:ObservationGroup</ins></u></a></code> <u><ins>as</ins></u> <u><ins>a</ins></u> <u><ins>generalization</ins></u> <u><ins>of</ins></u> <code><a href="#dfn-qb-slice" class="internalDFN"><u><ins>qb:Slice</ins></u></a></code><u><ins>.</ins></u> <a href="http://www.w3.org/2011/gld/track/issues/33"><u><ins>ISSUE-33</ins></u></a><u><ins>.</ins></u></li>
+  <li><u><ins>Added</ins></u> <a href="#schemes-aggregation"><u><ins>note</ins></u></a> <u><ins>that</ins></u> <u><ins>aggregation</ins></u> operations and inter-cube relations are out of scope for this version. <a href="http://www.w3.org/2011/gld/track/issues/30">ISSUE-30</a>.</li>
+  <li> <s><del>Added</del></s> <s><del>qb:ObservationGroup</del></s> <s><del>as</del></s><u><ins>Added</ins></u> <code><a href="#dfn-qb-observationgroup" class="internalDFN"><u><ins>qb:ObservationGroup</ins></u></a></code> <u><ins>as</ins></u> <u><ins>a</ins></u> <u><ins>generalization</ins></u> <u><ins>of</ins></u> <code><a href="#dfn-qb-slice" class="internalDFN"><u><ins>qb:Slice</ins></u></a></code><u><ins>.</ins></u> <a href="http://www.w3.org/2011/gld/track/issues/33"><u><ins>ISSUE-33</ins></u></a><u><ins>.</ins></u></li>
   <li><u><ins>Removed</ins></u> <code><a><u><ins>qb:subSlice</ins></u></a></code> <u><ins>as</ins></u> <u><ins>being</ins></u> <u><ins>problematic</ins></u> <u><ins>in</ins></u> <u><ins>how</ins></u>
   <u><ins>they</ins></u> <u><ins>interact</ins></u> <u><ins>with</ins></u> <u><ins>attachment</ins></u> <u><ins>levels.</ins></u> <a href="http://www.w3.org/2011/gld/track/issues/34"><u><ins>ISSUE-34</ins></u></a><u><ins>.</ins></u></li>
   <li><u><ins>Generalized</ins></u> <u><ins>range</ins></u> <u><ins>of</ins></u> <code><a href="#dfn-qb-codelist" class="internalDFN"><u><ins>qb:codeList</ins></u></a></code> <u><ins>to</ins></u> <u><ins>allow</ins></u> <code><u><ins>skos:Collection</ins></u></code><u><ins>.</ins></u> <a href="http://www.w3.org/2011/gld/track/issues/39"><u><ins>ISSUE-39</ins></u></a><u><ins>.</ins></u></li>
@@ -3179,106 +3204,106 @@
     <u><ins>eg:lifeExpectancy</ins></u>          <u><ins>76.5</ins></u> <u><ins>;</ins></u>
     <u><ins>.</ins></u>
 
-<u><ins>eg:o34</ins></u> <u><ins>a</ins></u> <u><ins>qb:Observation;</ins></u>
+<u><ins>eg:o34</ins></u> a  <s><del>generalization</del></s> <s><del>of</del></s> <s><del>qb:Slice</del></s><u><ins>qb:Observation;</ins></u>
     <u><ins>qb:dataSet</ins></u>  <u><ins>eg:dataset-le3</ins></u> <u><ins>;</ins></u>
     <u><ins>eg:refArea</ins></u>                 <u><ins>ex-geo:merthyr_tdfil_00ph</ins></u> <u><ins>;</ins></u>
     <u><ins>eg:lifeExpectancy</ins></u>          <u><ins>75.5</ins></u> <u><ins>;</ins></u>
-    <u><ins>.</ins></u>
-
-<u><ins>#</ins></u> <u><ins>Column</ins></u> <u><ins>4</ins></u>
+    .
+
+ <s><del>ISSUE-33</del></s><u><ins>#</ins></u> <u><ins>Column</ins></u> <u><ins>4</ins></u>
     
 <u><ins>eg:slice4</ins></u> <u><ins>a</ins></u> <u><ins>qb:Slice;</ins></u>
     <u><ins>qb:sliceStructure</ins></u>  <u><ins>eg:sliceByRegion</ins></u> <u><ins>;</ins></u>
     <u><ins>eg:refPeriod</ins></u>               <u><ins>&lt;http://reference.data.gov.uk/id/gregorian-interval/2005-01-01T00:00:00/P3Y&gt;</ins></u> <u><ins>;</ins></u>
     <u><ins>sdmx-dimension:sex</ins></u>         <u><ins>sdmx-code:sex-F</ins></u> <u><ins>;</ins></u>
     <u><ins>qb:observation</ins></u> <u><ins>eg:o41,</ins></u> <u><ins>eg:o42,</ins></u> <u><ins>eg:o43,</ins></u> <u><ins>eg:o44</ins></u> <u><ins>;</ins></u>
-    <u><ins>.</ins></u>
-
-<u><ins>eg:o41</ins></u> <u><ins>a</ins></u> <u><ins>qb:Observation;</ins></u>
+    .
+
+ <s><del>Removed</del></s> <s><del>qb:subSlice</del></s> <s><del>as</del></s> <s><del>being</del></s> <s><del>problematic</del></s> <s><del>in</del></s> <s><del>how</del></s> <s><del>they</del></s> <s><del>interact</del></s> <s><del>with</del></s> <s><del>attachment</del></s> <s><del>levels.</del></s> <s><del>ISSUE-34</del></s><u><ins>eg:o41</ins></u> <u><ins>a</ins></u> <u><ins>qb:Observation;</ins></u>
     <u><ins>qb:dataSet</ins></u>  <u><ins>eg:dataset-le3</ins></u> <u><ins>;</ins></u>
     <u><ins>eg:refArea</ins></u>                 <u><ins>ex-geo:newport_00pr</ins></u> <u><ins>;</ins></u>                  
     <u><ins>eg:lifeExpectancy</ins></u>          <u><ins>80.9</ins></u> <u><ins>;</ins></u>
-    <u><ins>.</ins></u>
+    .
     
-<u><ins>eg:o42</ins></u> <u><ins>a</ins></u> <u><ins>qb:Observation;</ins></u>
+ <s><del>Generalized</del></s> <s><del>range</del></s> <s><del>of</del></s> <s><del>qb:codeList</del></s> <s><del>to</del></s> <s><del>allow</del></s> <s><del>skos:Collection</del></s><u><ins>eg:o42</ins></u> <u><ins>a</ins></u> <u><ins>qb:Observation;</ins></u>
     <u><ins>qb:dataSet</ins></u>  <u><ins>eg:dataset-le3</ins></u> <u><ins>;</ins></u>
     <u><ins>eg:refArea</ins></u>                 <u><ins>ex-geo:cardiff_00pt</ins></u> <u><ins>;</ins></u>                  
     <u><ins>eg:lifeExpectancy</ins></u>          <u><ins>83.7</ins></u> <u><ins>;</ins></u>
-    <u><ins>.</ins></u>
-
-<u><ins>eg:o43</ins></u> <u><ins>a</ins></u> <u><ins>qb:Observation;</ins></u>
+    .
+
+ <s><del>ISSUE-39</del></s><u><ins>eg:o43</ins></u> <u><ins>a</ins></u> <u><ins>qb:Observation;</ins></u>
     <u><ins>qb:dataSet</ins></u>  <u><ins>eg:dataset-le3</ins></u> <u><ins>;</ins></u>
     <u><ins>eg:refArea</ins></u>                 <u><ins>ex-geo:monmouthshire_00pp</ins></u> <u><ins>;</ins></u>                  
     <u><ins>eg:lifeExpectancy</ins></u>          <u><ins>81.5</ins></u> <u><ins>;</ins></u>
-    <u><ins>.</ins></u>
-
-<u><ins>eg:o44</ins></u> <u><ins>a</ins></u> <u><ins>qb:Observation;</ins></u>
+    .
+
+ <s><del>Moved</del></s> <s><del>namespace</del></s> <s><del>definitions</del></s> <s><del>to</del></s><u><ins>eg:o44</ins></u> a  <s><del>normative</del></s> <s><del>section</del></s> <s><del>within</del></s> <s><del>the</del></s> <s><del>body</del></s> <s><del>of</del></s> <s><del>the</del></s> <s><del>specification.</del></s> <s><del>Moved</del></s> <s><del>Jeni</del></s> <s><del>Tennison</del></s> <s><del>from</del></s> <s><del>being</del></s> <s><del>listed</del></s> <s><del>as</del></s> <s><del>an</del></s> <s><del>author</del></s> <s><del>to</del></s> <s><del>being</del></s><u><ins>qb:Observation;</ins></u>
     <u><ins>qb:dataSet</ins></u>  <u><ins>eg:dataset-le3</ins></u> <u><ins>;</ins></u>
     <u><ins>eg:refArea</ins></u>                 <u><ins>ex-geo:merthyr_tdfil_00ph</ins></u> <u><ins>;</ins></u>
     <u><ins>eg:lifeExpectancy</ins></u>          <u><ins>79.4</ins></u> <u><ins>;</ins></u>
     <u><ins>.</ins></u>
 
-<u><ins>#</ins></u> <u><ins>Column</ins></u> 5
+<u><ins>#</ins></u> <u><ins>Column</ins></u> <u><ins>5</ins></u>
     
- <s><del>April</del></s> <s><del>2012</del></s> <s><del>:</del></s> <s><del>Added</del></s> <s><del>section</del></s> <s><del>on</del></s> <s><del>criteria</del></s> <s><del>for</del></s> <s><del>well-formed</del></s> <s><del>cubes.</del></s> <s><del>ISSUE-29</del></s> <s><del>Added</del></s> <s><del>section</del></s> <s><del>on</del></s> <s><del>normalization</del></s> <s><del>algorithm</del></s> <s><del>for</del></s> <s><del>handling</del></s> <s><del>abbreviated</del></s> <s><del>cubes.</del></s> <s><del>Added</del></s> <s><del>conformance</del></s> <s><del>section</del></s><u><ins>eg:slice5</ins></u> <u><ins>a</ins></u> <u><ins>qb:Slice;</ins></u>
+<u><ins>eg:slice5</ins></u> a  <s><del>contributor.</del></s> <s><del>C.</del></s><u><ins>qb:Slice;</ins></u>
     <u><ins>qb:sliceStructure</ins></u>  <u><ins>eg:sliceByRegion</ins></u> <u><ins>;</ins></u>
     <u><ins>eg:refPeriod</ins></u>               <u><ins>&lt;http://reference.data.gov.uk/id/gregorian-interval/2006-01-01T00:00:00/P3Y&gt;</ins></u> <u><ins>;</ins></u>
     <u><ins>sdmx-dimension:sex</ins></u>         <u><ins>sdmx-code:sex-M</ins></u> <u><ins>;</ins></u>
     <u><ins>qb:observation</ins></u> <u><ins>eg:o51,</ins></u> <u><ins>eg:o52,</ins></u> <u><ins>eg:o53,</ins></u> <u><ins>eg:o54</ins></u> <u><ins>;</ins></u>
-    .
-
- <s><del>Clarified</del></s> <s><del>that</del></s> <s><del>qb:componentRequired</del></s> <s><del>is</del></s> <s><del>only</del></s> <s><del>applicable</del></s> <s><del>to</del></s> <s><del>attributes</del></s> <s><del>and</del></s> <s><del>that</del></s> <s><del>it</del></s> <s><del>defaults</del></s> <s><del>to</del></s> <s><del>optional.</del></s> <s><del>Moved</del></s> <s><del>vocabulary</del></s> <s><del>reference</del></s> <s><del>into</del></s> <s><del>the</del></s> <s><del>normative</del></s> <s><del>body</del></s> <s><del>of</del></s> <s><del>the</del></s> <s><del>specification,</del></s> <s><del>adding</del></s> <s><del>hyperlinks</del></s> <s><del>for</del></s> <s><del>all</del></s> <s><del>qb:</del></s> <s><del>terms.</del></s> <s><del>Added</del></s> <s><del>section</del></s> <s><del>on</del></s> <s><del>non-skos</del></s> <s><del>hierarchies.</del></s> <s><del>ISSUE-31</del></s><u><ins>eg:o51</ins></u> <u><ins>a</ins></u> <u><ins>qb:Observation;</ins></u>
+    <u><ins>.</ins></u>
+
+<u><ins>eg:o51</ins></u> <u><ins>a</ins></u> <u><ins>qb:Observation;</ins></u>
     <u><ins>qb:dataSet</ins></u>  <u><ins>eg:dataset-le3</ins></u> <u><ins>;</ins></u>
     <u><ins>eg:refArea</ins></u>                 <u><ins>ex-geo:newport_00pr</ins></u> <u><ins>;</ins></u>                  
     <u><ins>eg:lifeExpectancy</ins></u>          <u><ins>77.0</ins></u> <u><ins>;</ins></u>
-    .
+    <u><ins>.</ins></u>
     
- <s><del>Added</del></s> <s><del>note</del></s> <s><del>that</del></s> <s><del>aggregation</del></s> <s><del>operations</del></s> <s><del>and</del></s> <s><del>inter-cube</del></s> <s><del>relations</del></s> <s><del>are</del></s> <s><del>out</del></s> <s><del>of</del></s> <s><del>scope</del></s> <s><del>for</del></s> <s><del>this</del></s> <s><del>version.</del></s> <s><del>ISSUE-30</del></s><u><ins>eg:o52</ins></u> <u><ins>a</ins></u> <u><ins>qb:Observation;</ins></u>
+<u><ins>eg:o52</ins></u> <u><ins>a</ins></u> <u><ins>qb:Observation;</ins></u>
     <u><ins>qb:dataSet</ins></u>  <u><ins>eg:dataset-le3</ins></u> <u><ins>;</ins></u>
     <u><ins>eg:refArea</ins></u>                 <u><ins>ex-geo:cardiff_00pt</ins></u> <u><ins>;</ins></u>                  
     <u><ins>eg:lifeExpectancy</ins></u>          <u><ins>78.7</ins></u> <u><ins>;</ins></u>
-    .
-
- <s><del>Added</del></s> <s><del>qb:ObservationGroup</del></s> <s><del>as</del></s><u><ins>eg:o53</ins></u> a  <s><del>generalization</del></s> <s><del>of</del></s> <s><del>qb:Slice</del></s><u><ins>qb:Observation;</ins></u>
+    <u><ins>.</ins></u>
+
+<u><ins>eg:o53</ins></u> <u><ins>a</ins></u> <u><ins>qb:Observation;</ins></u>
     <u><ins>qb:dataSet</ins></u>  <u><ins>eg:dataset-le3</ins></u> <u><ins>;</ins></u>
     <u><ins>eg:refArea</ins></u>                 <u><ins>ex-geo:monmouthshire_00pp</ins></u> <u><ins>;</ins></u>                  
     <u><ins>eg:lifeExpectancy</ins></u>          <u><ins>76.6</ins></u> <u><ins>;</ins></u>
-    .
-
- <s><del>ISSUE-33</del></s><u><ins>eg:o54</ins></u> <u><ins>a</ins></u> <u><ins>qb:Observation;</ins></u>
+    <u><ins>.</ins></u>
+
+<u><ins>eg:o54</ins></u> <u><ins>a</ins></u> <u><ins>qb:Observation;</ins></u>
     <u><ins>qb:dataSet</ins></u>  <u><ins>eg:dataset-le3</ins></u> <u><ins>;</ins></u>
     <u><ins>eg:refArea</ins></u>                 <u><ins>ex-geo:merthyr_tdfil_00ph</ins></u> <u><ins>;</ins></u>
     <u><ins>eg:lifeExpectancy</ins></u>          <u><ins>74.9</ins></u> <u><ins>;</ins></u>
-    .
-
- <s><del>Removed</del></s> <s><del>qb:subSlice</del></s> <s><del>as</del></s> <s><del>being</del></s> <s><del>problematic</del></s> <s><del>in</del></s> <s><del>how</del></s> <s><del>they</del></s> <s><del>interact</del></s> <s><del>with</del></s> <s><del>attachment</del></s> <s><del>levels.</del></s> <s><del>ISSUE-34</del></s><u><ins>#</ins></u> <u><ins>Column</ins></u> <u><ins>6</ins></u>
+    <u><ins>.</ins></u>
+
+<u><ins>#</ins></u> <u><ins>Column</ins></u> <u><ins>6</ins></u>
     
 <u><ins>eg:slice6</ins></u> <u><ins>a</ins></u> <u><ins>qb:Slice;</ins></u>
     <u><ins>qb:sliceStructure</ins></u>  <u><ins>eg:sliceByRegion</ins></u> <u><ins>;</ins></u>
     <u><ins>eg:refPeriod</ins></u>               <u><ins>&lt;http://reference.data.gov.uk/id/gregorian-interval/2006-01-01T00:00:00/P3Y&gt;</ins></u> <u><ins>;</ins></u>
     <u><ins>sdmx-dimension:sex</ins></u>         <u><ins>sdmx-code:sex-F</ins></u> <u><ins>;</ins></u>
     <u><ins>qb:observation</ins></u> <u><ins>eg:o61,</ins></u> <u><ins>eg:o62,</ins></u> <u><ins>eg:o63,</ins></u> <u><ins>eg:o64</ins></u> <u><ins>;</ins></u>
-    .
-
- <s><del>Generalized</del></s> <s><del>range</del></s> <s><del>of</del></s> <s><del>qb:codeList</del></s> <s><del>to</del></s> <s><del>allow</del></s> <s><del>skos:Collection</del></s><u><ins>eg:o61</ins></u> <u><ins>a</ins></u> <u><ins>qb:Observation;</ins></u>
+    <u><ins>.</ins></u>
+
+<u><ins>eg:o61</ins></u> <u><ins>a</ins></u> <u><ins>qb:Observation;</ins></u>
     <u><ins>qb:dataSet</ins></u>  <u><ins>eg:dataset-le3</ins></u> <u><ins>;</ins></u>
     <u><ins>eg:refArea</ins></u>                 <u><ins>ex-geo:newport_00pr</ins></u> <u><ins>;</ins></u>                  
     <u><ins>eg:lifeExpectancy</ins></u>          <u><ins>81.5</ins></u> <u><ins>;</ins></u>
-    .
+    <u><ins>.</ins></u>
     
- <s><del>ISSUE-39</del></s><u><ins>eg:o62</ins></u> <u><ins>a</ins></u> <u><ins>qb:Observation;</ins></u>
+<u><ins>eg:o62</ins></u> <u><ins>a</ins></u> <u><ins>qb:Observation;</ins></u>
     <u><ins>qb:dataSet</ins></u>  <u><ins>eg:dataset-le3</ins></u> <u><ins>;</ins></u>
     <u><ins>eg:refArea</ins></u>                 <u><ins>ex-geo:cardiff_00pt</ins></u> <u><ins>;</ins></u>                  
     <u><ins>eg:lifeExpectancy</ins></u>          <u><ins>83.4</ins></u> <u><ins>;</ins></u>
-    .
-
- <s><del>Moved</del></s> <s><del>namespace</del></s> <s><del>definitions</del></s> <s><del>to</del></s><u><ins>eg:o63</ins></u> a  <s><del>normative</del></s> <s><del>section</del></s> <s><del>within</del></s> <s><del>the</del></s> <s><del>body</del></s> <s><del>of</del></s> <s><del>the</del></s> <s><del>specification.</del></s> <s><del>Moved</del></s> <s><del>Jeni</del></s> <s><del>Tennison</del></s> <s><del>from</del></s> <s><del>being</del></s> <s><del>listed</del></s> <s><del>as</del></s> <s><del>an</del></s> <s><del>author</del></s> <s><del>to</del></s> <s><del>being</del></s><u><ins>qb:Observation;</ins></u>
+    <u><ins>.</ins></u>
+
+<u><ins>eg:o63</ins></u> <u><ins>a</ins></u> <u><ins>qb:Observation;</ins></u>
     <u><ins>qb:dataSet</ins></u>  <u><ins>eg:dataset-le3</ins></u> <u><ins>;</ins></u>
     <u><ins>eg:refArea</ins></u>                 <u><ins>ex-geo:monmouthshire_00pp</ins></u> <u><ins>;</ins></u>                  
     <u><ins>eg:lifeExpectancy</ins></u>          <u><ins>81.7</ins></u> <u><ins>;</ins></u>
     <u><ins>.</ins></u>
 
-<u><ins>eg:o64</ins></u> a  <s><del>contributor.</del></s> <s><del>C.</del></s><u><ins>qb:Observation;</ins></u>
+<u><ins>eg:o64</ins></u> <u><ins>a</ins></u> <u><ins>qb:Observation;</ins></u>
     <u><ins>qb:dataSet</ins></u>  <u><ins>eg:dataset-le3</ins></u> <u><ins>;</ins></u>
     <u><ins>eg:refArea</ins></u>                 <u><ins>ex-geo:merthyr_tdfil_00ph</ins></u> <u><ins>;</ins></u>
     <u><ins>eg:lifeExpectancy</ins></u>          <u><ins>79.6</ins></u> <u><ins>;</ins></u>