yet another try at html static version
authorDave Reynolds <dave@epimorphics.com>
Thu, 29 Mar 2012 16:10:37 +0100
changeset 147 81cc321941e0
parent 145 7726c698d1d7
child 148 b86477f46404
yet another try at html static version
data-cube/static.html
--- a/data-cube/static.html	Thu Mar 29 15:49:08 2012 +0100
+++ b/data-cube/static.html	Thu Mar 29 16:10:37 2012 +0100
@@ -1,13 +1,11 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+RDFa 1.1//EN"
-                      "http://www.w3.org/MarkUp/DTD/xhtml-rdfa-2.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
+<!DOCTYPE html PUBLIC '-//W3C//DTD XHTML+RDFa 1.1//EN' 'http://www.w3.org/MarkUp/DTD/xhtml-rdfa-2.dtd'>
+<html lang="en" dir="ltr">
 <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/ReSpec.js/js/respec.js" class="remove"></script>
-	<script src="../respec/gld-bib.js" class="remove"></script>
-	<script src="respec-config.js" class="remove"></script>
+	<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+	
+	
+	
   <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: '; }
@@ -17,16 +15,484 @@
 .spare-table td + td { border-left: black 1px solid; padding-left: 1em; padding-right: 1em; }
 .spare-table th + th { border-left: black 1px solid; }
   </style>
-</head>
+<style type="text/css">
+/*****************************************************************
+ * ReSpec CSS
+ * Robin Berjon (robin at berjon dot com)
+ * v0.05 - 2009-07-31
+ *****************************************************************/
 
-<body>
 
-<section id="abstract">
+/* --- 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;
+}
+
+code {
+    color:  #ff4500;
+}
+
+
+/* --- WEB IDL --- */
+pre.idl {
+    border-top: 1px solid #90b8de;
+    border-bottom: 1px solid #90b8de;
+    padding:    1em;
+    line-height:    120%;
+}
+
+pre.idl::before {
+    content:    "WebIDL";
+    display:    block;
+    width:      150px;
+    background: #90b8de;
+    color:  #fff;
+    font-family:    initial;
+    padding:    3px;
+    font-weight:    bold;
+    margin: -1em 0 1em -1em;
+}
+
+.idlType {
+    color:  #ff4500;
+    font-weight:    bold;
+    text-decoration:    none;
+}
+
+/*.idlModule*/
+/*.idlModuleID*/
+/*.idlInterface*/
+.idlInterfaceID, .idlDictionaryID {
+    font-weight:    bold;
+    color:  #005a9c;
+}
+
+.idlSuperclass {
+    font-style: italic;
+    color:  #005a9c;
+}
+
+/*.idlAttribute*/
+.idlAttrType, .idlFieldType, .idlMemberType {
+    color:  #005a9c;
+}
+.idlAttrName, .idlFieldName, .idlMemberName {
+    color:  #ff4500;
+}
+.idlAttrName a, .idlFieldName a, .idlMemberName a {
+    color:  #ff4500;
+    border-bottom:  1px dotted #ff4500;
+    text-decoration: none;
+}
+
+/*.idlMethod*/
+.idlMethType {
+    color:  #005a9c;
+}
+.idlMethName {
+    color:  #ff4500;
+}
+.idlMethName a {
+    color:  #ff4500;
+    border-bottom:  1px dotted #ff4500;
+    text-decoration: none;
+}
+
+/*.idlParam*/
+.idlParamType {
+    color:  #005a9c;
+}
+.idlParamName {
+    font-style: italic;
+}
+
+.extAttr {
+    color:  #666;
+}
+
+/*.idlConst*/
+.idlConstType {
+    color:  #005a9c;
+}
+.idlConstName {
+    color:  #ff4500;
+}
+.idlConstName a {
+    color:  #ff4500;
+    border-bottom:  1px dotted #ff4500;
+    text-decoration: none;
+}
+
+/*.idlException*/
+.idlExceptionID {
+    font-weight:    bold;
+    color:  #c00;
+}
+
+.idlTypedefID, .idlTypedefType {
+    color:  #005a9c;
+}
+
+.idlRaises, .idlRaises a.idlType, .idlRaises a.idlType code, .excName a, .excName a code {
+    color:  #c00;
+    font-weight:    normal;
+}
+
+.excName a {
+    font-family:    monospace;
+}
+
+.idlRaises a.idlType, .excName a.idlType {
+    border-bottom:  1px dotted #c00;
+}
+
+.excGetSetTrue, .excGetSetFalse, .prmNullTrue, .prmNullFalse, .prmOptTrue, .prmOptFalse {
+    width:  45px;
+    text-align: center;
+}
+.excGetSetTrue, .prmNullTrue, .prmOptTrue { color:  #0c0; }
+.excGetSetFalse, .prmNullFalse, .prmOptFalse { color:  #c00; }
+
+.idlImplements a {
+    font-weight:    bold;
+}
+
+dl.attributes, dl.methods, dl.constants, dl.fields, dl.dictionary-members {
+    margin-left:    2em;
+}
+
+.attributes dt, .methods dt, .constants dt, .fields dt, .dictionary-members dt {
+    font-weight:    normal;
+}
+
+.attributes dt code, .methods dt code, .constants dt code, .fields dt code, .dictionary-members dt code {
+    font-weight:    bold;
+    color:  #000;
+    font-family:    monospace;
+}
+
+.attributes dt code, .fields dt code, .dictionary-members dt code {
+    background:  #ffffd2;
+}
+
+.attributes dt .idlAttrType code, .fields dt .idlFieldType code, .dictionary-members dt .idlMemberType code {
+    color:  #005a9c;
+    background:  transparent;
+    font-family:    inherit;
+    font-weight:    normal;
+    font-style: italic;
+}
+
+.methods dt code {
+    background:  #d9e6f8;
+}
+
+.constants dt code {
+    background:  #ddffd2;
+}
+
+.attributes dd, .methods dd, .constants dd, .fields dd, .dictionary-members dd {
+    margin-bottom:  1em;
+}
+
+table.parameters, table.exceptions {
+    border-spacing: 0;
+    border-collapse:    collapse;
+    margin: 0.5em 0;
+    width:  100%;
+}
+table.parameters { border-bottom:  1px solid #90b8de; }
+table.exceptions { border-bottom:  1px solid #deb890; }
+
+.parameters th, .exceptions th {
+    color:  #fff;
+    padding:    3px 5px;
+    text-align: left;
+    font-family:    initial;
+    font-weight:    normal;
+    text-shadow:    #666 1px 1px 0;
+}
+.parameters th { background: #90b8de; }
+.exceptions th { background: #deb890; }
+
+.parameters td, .exceptions td {
+    padding:    3px 10px;
+    border-top: 1px solid #ddd;
+    vertical-align: top;
+}
+
+.parameters tr:first-child td, .exceptions tr:first-child td {
+    border-top: none;
+}
+
+.parameters td.prmName, .exceptions td.excName, .exceptions td.excCodeName {
+    width:  100px;
+}
+
+.parameters td.prmType {
+    width:  120px;
+}
+
+table.exceptions table {
+    border-spacing: 0;
+    border-collapse:    collapse;
+    width:  100%;
+}
+
+/* --- TOC --- */
+.toc a {
+    text-decoration:    none;
+}
+
+a .secno {
+    color:  #000;
+}
+
+/* --- 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;
+}
+
+/* --- EXAMPLES --- */
+pre.example {
+    border-top: 1px solid #ff4500;
+    border-bottom: 1px solid #ff4500;
+    padding:    1em;
+    margin-top: 1em;
+}
+
+pre.example::before {
+    content:    "Example";
+    display:    block;
+    width:      150px;
+    background: #ff4500;
+    color:  #fff;
+    font-family:    initial;
+    padding:    3px;
+    font-weight:    bold;
+    margin: -1em 0 1em -1em;
+}
+
+/* --- EDITORIAL NOTES --- */
+.issue {
+    padding:    1em;
+    margin: 1em 0em 0em;
+    border: 1px solid #f00;
+    background: #ffc;
+}
+
+.issue::before {
+    content:    "Issue";
+    display:    block;
+    width:  150px;
+    margin: -1.5em 0 0.5em 0;
+    font-weight:    bold;
+    border: 1px solid #f00;
+    background: #fff;
+    padding:    3px 1em;
+}
+
+.note {
+    margin: 1em 0em 0em;
+    padding:    1em;
+    border: 2px solid #cff6d9;
+    background: #e2fff0;
+}
+
+.note::before {
+    content:    "Note";
+    display:    block;
+    width:  150px;
+    margin: -1.5em 0 0.5em 0;
+    font-weight:    bold;
+    border: 1px solid #cff6d9;
+    background: #fff;
+    padding:    3px 1em;
+}
+
+/* --- Best Practices --- */
+div.practice {
+    border: solid #bebebe 1px;
+    margin: 2em 1em 1em 2em;
+}
+
+span.practicelab {
+    margin: 1.5em 0.5em 1em 1em;
+    font-weight: bold;
+    font-style: italic;
+}
+
+span.practicelab   { background: #dfffff; }
+
+span.practicelab {
+    position: relative;
+    padding: 0 0.5em;
+    top: -1.5em;
+}
+
+p.practicedesc {
+    margin: 1.5em 0.5em 1em 1em;
+}
+
[email protected] screen {
+    p.practicedesc {
+        position: relative;
+        top: -2em;
+        padding: 0;
+        margin: 1.5em 0.5em -1em 1em;
+    }
+}
+
+/* --- SYNTAX HIGHLIGHTING --- */
+pre.sh_sourceCode {
+  background-color: white;
+  color: black;
+  font-style: normal;
+  font-weight: normal;
+}
+
+pre.sh_sourceCode .sh_keyword { color: #005a9c; font-weight: bold; }           /* language keywords */
+pre.sh_sourceCode .sh_type { color: #666; }                            /* basic types */
+pre.sh_sourceCode .sh_usertype { color: teal; }                             /* user defined types */
+pre.sh_sourceCode .sh_string { color: red; font-family: monospace; }        /* strings and chars */
+pre.sh_sourceCode .sh_regexp { color: orange; font-family: monospace; }     /* regular expressions */
+pre.sh_sourceCode .sh_specialchar { color: 	#ffc0cb; font-family: monospace; }  /* e.g., \n, \t, \\ */
+pre.sh_sourceCode .sh_comment { color: #A52A2A; font-style: italic; }         /* comments */
+pre.sh_sourceCode .sh_number { color: purple; }                             /* literal numbers */
+pre.sh_sourceCode .sh_preproc { color: #00008B; font-weight: bold; }       /* e.g., #include, import */
+pre.sh_sourceCode .sh_symbol { color: blue; }                            /* e.g., *, + */
+pre.sh_sourceCode .sh_function { color: black; font-weight: bold; }         /* function calls and declarations */
+pre.sh_sourceCode .sh_cbracket { color: red; }                              /* block brackets (e.g., {, }) */
+pre.sh_sourceCode .sh_todo { font-weight: bold; background-color: #00FFFF; }   /* TODO and FIXME */
+
+/* Predefined variables and functions (for instance glsl) */
+pre.sh_sourceCode .sh_predef_var { color: #00008B; }
+pre.sh_sourceCode .sh_predef_func { color: #00008B; font-weight: bold; }
+
+/* for OOP */
+pre.sh_sourceCode .sh_classname { color: teal; }
+
+/* line numbers (not yet implemented) */
+pre.sh_sourceCode .sh_linenum { display: none; }
+
+/* Internet related */
+pre.sh_sourceCode .sh_url { color: blue; text-decoration: underline; font-family: monospace; }
+
+/* for ChangeLog and Log files */
+pre.sh_sourceCode .sh_date { color: blue; font-weight: bold; }
+pre.sh_sourceCode .sh_time, pre.sh_sourceCode .sh_file { color: #00008B; font-weight: bold; }
+pre.sh_sourceCode .sh_ip, pre.sh_sourceCode .sh_name { color: #006400; }
+
+/* for Prolog, Perl... */
+pre.sh_sourceCode .sh_variable { color: #006400; }
+
+/* for LaTeX */
+pre.sh_sourceCode .sh_italics { color: #006400; font-style: italic; }
+pre.sh_sourceCode .sh_bold { color: #006400; font-weight: bold; }
+pre.sh_sourceCode .sh_underline { color: #006400; text-decoration: underline; }
+pre.sh_sourceCode .sh_fixed { color: green; font-family: monospace; }
+pre.sh_sourceCode .sh_argument { color: #006400; }
+pre.sh_sourceCode .sh_optionalargument { color: purple; }
+pre.sh_sourceCode .sh_math { color: orange; }
+pre.sh_sourceCode .sh_bibtex { color: blue; }
+
+/* for diffs */
+pre.sh_sourceCode .sh_oldfile { color: orange; }
+pre.sh_sourceCode .sh_newfile { color: #006400; }
+pre.sh_sourceCode .sh_difflines { color: blue; }
+
+/* for css */
+pre.sh_sourceCode .sh_selector { color: purple; }
+pre.sh_sourceCode .sh_property { color: blue; }
+pre.sh_sourceCode .sh_value { color: #006400; font-style: italic; }
+
+/* other */
+pre.sh_sourceCode .sh_section { color: black; font-weight: bold; }
+pre.sh_sourceCode .sh_paren { color: red; }
+pre.sh_sourceCode .sh_attribute { color: #006400; }
+
+</style><link charset="utf-8" type="text/css" rel="stylesheet" href="http://www.w3.org/StyleSheets/TR/W3C-WD"></head>
+
+<body style="display: inherit;"><div class="head"><p><a href="http://www.w3.org/"><img src="http://www.w3.org/Icons/w3c_home" alt="W3C" height="48" width="72"></a></p><h1 class="title" id="title">The RDF Data Cube Vocabulary</h1><h2 id="w3c-working-draft-03-april-2012"><acronym title="World Wide Web Consortium">W3C</acronym> Working Draft 03 April 2012</h2><dl><dt>This version:</dt><dd><a href="http://www.w3.org/TR/2012/WD-data-cube-20120403/">http://www.w3.org/TR/2012/WD-data-cube-20120403/</a></dd><dt>Latest published version:</dt><dd><a href="http://www.w3.org/TR/data-cube/">http://www.w3.org/TR/data-cube/</a></dd><dt>Latest editor's draft:</dt><dd><a href="http://dvcs.w3.org/hg/gld/raw-file/default/data-cube/index.html">http://dvcs.w3.org/hg/gld/raw-file/default/data-cube/index.html</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>Author:</dt><dd><a href="http://www.jenitennison.com/blog/">Jeni Tennison</a>, <a href="http://www.tso.co.uk/">TSO</a></dd>
+</dl><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2012 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.eu/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. <acronym title="World Wide Web Consortium">W3C</acronym> <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>
+
+<div class="introductory section" id="abstract"><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 W3C <a href="http://www.w3.org/TR/REC-rdf-syntax/">RDF</a>
+vocabulary provides a means to do this using the <acronym title="World Wide Web Consortium">W3C</acronym> <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
@@ -35,13 +501,13 @@
 vocabulary is a core foundation which supports extension
 vocabularies to enable publication of other aspects of
 statistical data flows.</p>
-</section>
+</div><div id="sotd" class="introductory section"><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 <acronym title="World Wide Web Consortium">W3C</acronym> publications and the latest revision of this technical report can be found in the <a href="http://www.w3.org/TR/"><acronym title="World Wide Web Consortium">W3C</acronym> technical reports index</a> at http://www.w3.org/TR/.</em></p><p>This document was published by the <a href="http://www.w3.org/2011/gld/">Government Linked Data Working Group</a> as a First Public Working Draft. This document is intended to become a <acronym title="World Wide Web Consortium">W3C</acronym> 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>). All feedback is welcome.</p><p>Publication as a Working Draft does not imply endorsement by the <acronym title="World Wide Web Consortium">W3C</acronym> 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 <acronym title="World Wide Web Consortium">W3C</acronym> Patent Policy</a>. <acronym title="World Wide Web Consortium">W3C</acronym> maintains a <a href="" 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 <acronym title="World Wide Web Consortium">W3C</acronym> Patent Policy</a>.</p></div><div class="section" id="toc"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a class="tocxref" href="#introduction"><span class="secno">1. </span>Introduction</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#intro-cube"><span class="secno">1.1 </span>A Data Cube vocabulary</a></li><li class="tocline"><a class="tocxref" href="#intro-rdf"><span class="secno">1.2 </span>RDF and Linked Data</a></li><li class="tocline"><a class="tocxref" href="#intro-sdmx"><span class="secno">1.3 </span>SDMX and related standards</a></li><li class="tocline"><a class="tocxref" href="#intro-scovo"><span class="secno">1.4 </span>Relationship to SCOVO</a></li><li class="tocline"><a class="tocxref" href="#intro-audience"><span class="secno">1.5 </span>Audience and scope</a></li><li class="tocline"><a class="tocxref" href="#intro-conventions"><span class="secno">1.6 </span>Document conventions</a></li></ul></li><li class="tocline"><a class="tocxref" href="#data-cubes"><span class="secno">2. </span>Data cubes</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#cubes-model"><span class="secno">2.1 </span>The cube model - dimensions, attributes, measures</a></li><li class="tocline"><a class="tocxref" href="#cubes-slices"><span class="secno">2.2 </span>Slices</a></li></ul></li><li class="tocline"><a class="tocxref" href="#example"><span class="secno">3. </span>An example</a></li><li class="tocline"><a class="tocxref" href="#outline"><span class="secno">4. </span>Outline of the vocabulary</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#index"><span class="secno">4.1 </span>Vocabulary index</a></li></ul></li><li class="tocline"><a class="tocxref" href="#dsd"><span class="secno">5. </span>Creating data structure definitions</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#dsd-dimensions"><span class="secno">5.1 </span>Dimensions, attributes and measures</a></li><li class="tocline"><a class="tocxref" href="#dsd-cog"><span class="secno">5.2 </span>Content oriented guidelines</a></li><li class="tocline"><a class="tocxref" href="#dsd-example"><span class="secno">5.3 </span>Example</a></li><li class="tocline"><a class="tocxref" href="#dsd-dsd"><span class="secno">5.4 </span>ComponentSpecifications and DataStructureDefinitions</a></li><li class="tocline"><a class="tocxref" href="#dsd-mm"><span class="secno">5.5 </span>Handling multiple measures</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#dsd-mm-obs"><span class="secno">5.5.1 </span>Multi-measure observations</a></li><li class="tocline"><a class="tocxref" href="#dsd-mm-dim"><span class="secno">5.5.2 </span>Measure dimension</a></li></ul></li></ul></li><li class="tocline"><a class="tocxref" href="#datasets"><span class="secno">6. </span>Expressing data sets</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#dataset-basic"><span class="secno">6.1 </span>Data sets and observations</a></li></ul></li><li class="tocline"><a class="tocxref" href="#slices"><span class="secno">7. </span>Slices</a></li><li class="tocline"><a class="tocxref" href="#schemes"><span class="secno">8. </span>Concept schemes and code lists</a></li><li class="tocline"><a class="tocxref" href="#metadata"><span class="secno">9. </span>DataSet metadata</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#metadata-categorization"><span class="secno">9.1 </span>Categorizing a data set</a></li><li class="tocline"><a class="tocxref" href="#metadata-publishers"><span class="secno">9.2 </span>Describing publishers</a></li></ul></li><li class="tocline"><a class="tocxref" href="#namespaces-used-appendix"><span class="secno">A. </span>Namespaces used in this document</a></li><li class="tocline"><a class="tocxref" href="#vocab-reference"><span class="secno">B. </span>Vocabulary reference</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#reference-datasets"><span class="secno">B.1 </span>DataSets</a></li><li class="tocline"><a class="tocxref" href="#reference-observations"><span class="secno">B.2 </span>Observations</a></li><li class="tocline"><a class="tocxref" href="#reference-slices"><span class="secno">B.3 </span>Slices</a></li><li class="tocline"><a class="tocxref" href="#reference-components"><span class="secno">B.4 </span>Dimensions, Attributes, Measures</a></li><li class="tocline"><a class="tocxref" href="#reference-component-properties"><span class="secno">B.5 </span>Reusable general purpose component properties</a></li><li class="tocline"><a class="tocxref" href="#reference-dsd"><span class="secno">B.6 </span>Data Structure Definitions</a></li><li class="tocline"><a class="tocxref" href="#reference-compspec"><span class="secno">B.7 </span>Component specifications - for qualifying component use in a DSD</a></li><li class="tocline"><a class="tocxref" href="#reference-slice-definitions"><span class="secno">B.8 </span>Slice definitions</a></li><li class="tocline"><a class="tocxref" href="#reference-concepts"><span class="secno">B.9 </span>Concepts</a></li></ul></li><li class="tocline"><a class="tocxref" href="#acknowledgements"><span class="secno">C. </span>Acknowledgements</a></li><li class="tocline"><a class="tocxref" href="#issues"><span class="secno">D. </span>Open issues</a></li><li class="tocline"><a class="tocxref" href="#references"><span class="secno">E. </span>References</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#normative-references"><span class="secno">E.1 </span>Normative references</a></li><li class="tocline"><a class="tocxref" href="#informative-references"><span class="secno">E.2 </span>Informative references</a></li></ul></li></ul></div>
 
-<section id="introduction">
-<h2>Introduction</h2>
+<div class="section" id="introduction">
+<!--OddPage--><h2><span class="secno">1. </span>Introduction</h2>
 
-<section id="intro-cube">
-<h3>A Data Cube vocabulary</h3>
+<div class="section" id="intro-cube">
+<h3><span class="secno">1.1 </span>A Data Cube vocabulary</h3>
 
 <p>
 Statistical data is a foundation for policy
@@ -56,14 +522,14 @@
 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 the W3C <a href="http://www.w3.org/TR/REC-rdf-syntax/">RDF</a>
+using the the <acronym title="World Wide Web Consortium">W3C</acronym> <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 [[OLAP]].
+such as survey data, spreadsheets and OLAP data cubes [<cite><a href="#bib-OLAP" rel="biblioentry" class="bibref">OLAP</a></cite>].
 </p>
 
 <p>
@@ -73,8 +539,7 @@
 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>)
+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>
 
@@ -89,19 +554,19 @@
   <li><a href="http://purl.org/dc/terms/">Dublin Core Terms</a> for
 metadata</li>
 </ul>
-</section>
+</div>
 
 
-<section id="intro-rdf">
-<h3>RDF and Linked Data</h3>
+<div class="section" id="intro-rdf">
+<h3><span class="secno">1.2 </span>RDF and Linked Data</h3>
 
 <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 [[LOD]]
+  The approach [<cite><a href="#bib-LOD" rel="biblioentry" class="bibref">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 [[RDF-PRIMER]]
+RDF [<cite><a href="#bib-RDF-PRIMER" rel="biblioentry" class="bibref">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>
@@ -124,11 +589,11 @@
 for programmatic access.</li>
   <li>It enables reuse of standardized tools and components.</li>
 </ul>
-</section>
+</div>
 
 
-<section id="intro-sdmx">
-<h3>SDMX and related standards</h3>
+<div class="section" id="intro-sdmx">
+<h3><span class="secno">1.3 </span>SDMX and related standards</h3>
 
 <p>The Statistical Data and Metadata Exchange (SDMX) Initiative
 was organised in 2001 by seven international organisations (BIS,
@@ -168,13 +633,13 @@
 terms are available separately for use along with the Data Cube
 vocabulary.
 </p>
-</section>
+</div>
 
 
-<section id="intro-scovo">
-<h3>Relationship to SCOVO</h3>
+<div class="section" id="intro-scovo">
+<h3><span class="secno">1.4 </span>Relationship to SCOVO</h3>
 
-<p>The Statistical Core Vocabulary (SCOVO) [[SCOVO]] is a lightweight
+<p>The Statistical Core Vocabulary (SCOVO) [<cite><a href="#bib-SCOVO" rel="biblioentry" class="bibref">SCOVO</a></cite>] is a lightweight
 RDF vocabulary for expressing statistical data. Its relative
 simplicity allows easy adoption by data producers and consumers, and
 it can be combined with other RDF vocabularies for greater effect. The
@@ -199,22 +664,22 @@
 The design of the Data Cube vocabulary is informed by SCOVO,
 and every SCOVO dataset can be re-expressed within the vocabulary.
 </p>
-</section>
+</div>
 
 
-<section id="intro-audience">
-<h3>Audience and scope</h3>
+<div class="section" id="intro-audience">
+<h3><span class="secno">1.5 </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 will be covered elsewhere.</p>
-</section>
+</div>
 
 
-<section id="intro-conventions">
-<h3>Document conventions</h3>
+<div class="section" id="intro-conventions">
+<h3><span class="secno">1.6 </span>Document conventions</h3>
 
 <p>
 The names of RDF entities -- classes, predicates, individuals -- are
@@ -239,18 +704,18 @@
 <p>We also introduce the prefix <code>qb</code> for the Data Cube
   namespace <a href="http://purl.org/linked-data/cube#">http://purl.org/linked-data/cube#</a>.</p>
 
-<p>All RDF examples are written in Turtle syntax [[TURTLE-TR]].</p>
-</section>
+<p>All RDF examples are written in Turtle syntax [<cite><a href="#bib-TURTLE-TR" rel="biblioentry" class="bibref">TURTLE-TR</a></cite>].</p>
+</div>
 
-</section>
+</div>
 
 
-<section id="data-cubes">
-<h2>Data cubes</h2>
+<div class="section" id="data-cubes">
+<!--OddPage--><h2><span class="secno">2. </span>Data cubes</h2>
 
 
-<section id="cubes-model">
-<h3>The cube model - dimensions, attributes, measures</h3>
+<div class="section" id="cubes-model">
+<h3><span class="secno">2.1 </span>The cube model - dimensions, attributes, measures</h3>
 
 <p>A statistical data set comprises a collection of observations made
 at some points across some logical space. The collection can be characterized by
@@ -284,11 +749,11 @@
 interpret the observed value(s). They enable specification of the units of
 measures, any scaling factors and metadata such as the status
 of the observation (e.g. <em>estimated</em>, <em>provisional</em>).</p>
-</section>
+</div>
 
 
-<section id="cubes-slices">
-<h3>Slices</h3>
+<div class="section" id="cubes-slices">
+<h3><span class="secno">2.2 </span>Slices</h3>
 
 <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
@@ -315,12 +780,12 @@
 slices and do not give different names to particular types of slice but
 extension vocabularies, such as SDMX-RDF, can easily add such
 concept labels.</p>
-</section>
+</div>
 
-</section>
+</div>
 
-<section id="example">
-<h2>An example</h2>
+<div class="section" id="example">
+<!--OddPage--><h2><span class="secno">3. </span>An example</h2>
 
 <p>In order to illustrate the use of the data cube vocabulary we will
 use a small demonstration
@@ -330,47 +795,36 @@
 (unitary authority), age and time. The extract we will use is:<br>
 </p>
 
-<table style="text-align: left; width: 80%;" border="1" cellpadding="2"
- cellspacing="0">
+<table style="text-align: left; width: 80%;" border="1" cellpadding="2" cellspacing="0">
   <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 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 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 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 style="vertical-align: top; text-align: center; font-weight: bold;">Male<br>
       </td>
-      <td
- style="vertical-align: top; text-align: center; font-weight: bold;">Male<br>
+      <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;">Female<br>
+      <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;">Male<br>
+      <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;">Female<br>
+      <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 style="vertical-align: top; text-align: right; font-weight: bold;">Newport<br>
       </td>
       <td style="vertical-align: top;">76.7<br>
       </td>
@@ -386,8 +840,7 @@
       </td>
     </tr>
     <tr>
-      <td
- style="vertical-align: top; text-align: right; font-weight: bold;">Cardiff<br>
+      <td style="vertical-align: top; text-align: right; font-weight: bold;">Cardiff<br>
       </td>
       <td style="vertical-align: top;">78.7<br>
       </td>
@@ -403,8 +856,7 @@
       </td>
     </tr>
     <tr>
-      <td
- style="vertical-align: top; text-align: right; font-weight: bold;">Monmouthshire<br>
+      <td style="vertical-align: top; text-align: right; font-weight: bold;">Monmouthshire<br>
       </td>
       <td style="vertical-align: top;">76.6<br>
       </td>
@@ -420,8 +872,7 @@
       </td>
     </tr>
     <tr>
-      <td
- style="vertical-align: top; text-align: right; font-weight: bold;">Merthyr
+      <td style="vertical-align: top; text-align: right; font-weight: bold;">Merthyr
 Tydfil<br>
       </td>
       <td style="vertical-align: top;">75.5<br>
@@ -448,60 +899,60 @@
 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>
 
-</section>
+</div>
 
 
-<section id="outline">
-<h2>Outline of the vocabulary</h2>
+<div class="section" id="outline">
+<!--OddPage--><h2><span class="secno">4. </span>Outline of the vocabulary</h2>
 
-<img src="images/qb-fig1.png" />
+<img src="images/qb-fig1.png">
 
-<section id="index">
-<h3>Vocabulary index</h3>
+<div class="section" id="index">
+<h3><span class="secno">4.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_MeasureProperty'>qb:MeasureProperty</a>
-    <a href='#ref_qb_Observation'>qb:Observation</a>
-    <a href='#ref_qb_Slice'>qb:Slice</a>
-    <a href='#ref_qb_SliceKey'>qb:SliceKey</a>
+    <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_MeasureProperty">qb:MeasureProperty</a>
+    <a href="#ref_qb_Observation">qb:Observation</a>
+    <a href="#ref_qb_Slice">qb:Slice</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'>qb:componentProperty</a>
-    <a href='#ref_qb_componentRequired'>qb:componentRequired</a>
-    <a href='#ref_qb_concept'>qb:concept</a>
-    <a href='#ref_qb_dataSet'>qb:dataSet</a>
-    <a href='#ref_qb_dimension'>qb:dimension</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'>qb:observation</a>
-    <a href='#ref_qb_order'>qb:order</a>
-    <a href='#ref_qb_slice'>qb:slice</a>
-    <a href='#ref_qb_sliceKey'>qb:sliceKey</a>
-    <a href='#ref_qb_sliceStructure'>qb:sliceStructure</a>
-    <a href='#ref_qb_structure'>qb:structure</a>
-    <a href='#ref_qb_subSlice'>qb:subSlice</a>
+    <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">qb:componentProperty</a>
+    <a href="#ref_qb_componentRequired">qb:componentRequired</a>
+    <a href="#ref_qb_concept">qb:concept</a>
+    <a href="#ref_qb_dataSet">qb:dataSet</a>
+    <a href="#ref_qb_dimension">qb:dimension</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">qb:observation</a>
+    <a href="#ref_qb_order">qb:order</a>
+    <a href="#ref_qb_slice">qb:slice</a>
+    <a href="#ref_qb_sliceKey">qb:sliceKey</a>
+    <a href="#ref_qb_sliceStructure">qb:sliceStructure</a>
+    <a href="#ref_qb_structure">qb:structure</a>
+    <a href="#ref_qb_subSlice">qb:subSlice</a>
   </p>
-</section>
+</div>
 
-</section>
+</div>
 
 
-<section id="dsd">
-<h2>Creating data structure definitions</h2>
+<div class="section" id="dsd">
+<!--OddPage--><h2><span class="secno">5. </span>Creating data structure definitions</h2>
 
 <p>A <code>qb:DataStructureDefinition</code> defines the structure of one or more
 datasets. In particular, it defines the dimensions, attributes and measures 
@@ -525,8 +976,8 @@
 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>Dimensions, attributes and measures</h3>
+<div class="section" id="dsd-dimensions">
+<h3><span class="secno">5.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>qb:ComponentProperty</code> 
@@ -550,7 +1001,7 @@
 
 <p>To support this reuse of general statistical concepts the data cube vocabulary provides the <code>qb:concept</code> property which
   links a <code>qb:ComponentProperty</code> to the concept it represents. We use the SKOS
-  vocabulary [[SKOS-PRIMER]] to represent such concepts. This is very natural for those cases where the  
+  vocabulary [<cite><a href="#bib-SKOS-PRIMER" rel="biblioentry" class="bibref">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
@@ -586,12 +1037,12 @@
 <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>
+</div>
 
-<section id="dsd-cog">
-<h3>Content oriented guidelines</h3>
+<div class="section" id="dsd-cog">
+<h3><span class="secno">5.2 </span>Content oriented guidelines</h3>
 
-<p>The SDMX standard includes a set of <em>content oriented guidelines</em> (COG) [[COG]]
+<p>The SDMX standard includes a set of <em>content oriented guidelines</em> (COG) [<cite><a href="#bib-COG" rel="biblioentry" class="bibref">COG</a></cite>]
  which define a
    set of common statistical concepts and associated code lists that are intended to be 
    reusable across data sets. As part of the data cube work we have created RDF analogues
@@ -608,11 +1059,11 @@
    terms. However, when the concepts being expressed do match a COG concept it is recommended
    that publishers should reuse the corresponding components and/or concept URIs to simplify comparisons
   across data sets. Given this background we will reuse the relevant COG components in our worked example.</p>
-</section>
+</div>
 
 
-<section id="dsd-example">
-<h3>Example</h3>
+<div class="section" id="dsd-example">
+<h3><span class="secno">5.3 </span>Example</h3>
 
 <p>Turning to our example data set then we can see there are three dimensions to represent
    - time period, region (unitary authority) and sex of the population. There is a single
@@ -624,8 +1075,7 @@
   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>
 
-<pre>
-  eg:refPeriod  a rdf:Property, qb:DimensionProperty;
+<pre>  eg:refPeriod  a rdf:Property, qb:DimensionProperty;
       rdfs:label "reference period"@en;
       rdfs:subPropertyOf sdmx-dimension:refPeriod;
       rdfs:range interval:Interval;
@@ -633,10 +1083,9 @@
 
 <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 Ordanance Survey administrative geography ontology [[OS-GEO]].</p>
+  we can use the Ordanance Survey administrative geography ontology [<cite><a href="#bib-OS-GEO" rel="biblioentry" class="bibref">OS-GEO</a></cite>].</p>
 
-<pre>
-  eg:refArea  a rdf:Property, qb:DimensionProperty;
+<pre>  eg:refArea  a rdf:Property, qb:DimensionProperty;
       rdfs:label "reference area"@en;
       rdfs:subPropertyOf sdmx-dimension:refArea;
       rdfs:range admingeo:UnitaryAuthority;
@@ -650,8 +1099,7 @@
   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>
   
-<pre>
-  eg:lifeExpectancy  a rdf:Property, qb:MeasureProperty;
+<pre>  eg:lifeExpectancy  a rdf:Property, qb:MeasureProperty;
       rdfs:label "life expectancy"@en;
       rdfs:subPropertyOf sdmx-measure:obsValue;
       rdfs:range xsd:decimal . </pre>
@@ -666,11 +1114,11 @@
   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>
+</div>
 
 
-<section id="dsd-dsd">
-<h3>ComponentSpecifications and DataStructureDefinitions</h3>
+<div class="section" id="dsd-dsd">
+<h3><span class="secno">5.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>qb:DataStuctureDefinition</code>
@@ -709,8 +1157,7 @@
 
 <p>So the structure of our example data set (and other similar datasets) can be declared by:</p>
 
-<pre>
-  eg:dsd-le a qb:DataStructureDefinition;
+<pre>  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];
@@ -726,11 +1173,11 @@
  are only useful within the scope of a particular DSD and so we have chosen the represent
  them using blank nodes.
 </p>
-</section>
+</div>
       
 
-<section id="dsd-mm">
-<h3>Handling multiple measures</h3>
+<div class="section" id="dsd-mm">
+<h3><span class="secno">5.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
@@ -751,8 +1198,8 @@
   within the same data set.</p>
   
 
-<section id="dsd-mm-obs">
-<h4>Multi-measure observations</h4>
+<div class="section" id="dsd-mm-obs">
+<h4><span class="secno">5.5.1 </span>Multi-measure observations</h4>
   
 <p> This approach allows multiple observed values to be attached
   to an individual observation. Is suited to representation of things like sensor data and OLAP cubes.
@@ -762,8 +1209,7 @@
 
 <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>
-<pre>
-eg:dsd1 a qb:DataStructureDefinition;
+<pre>eg:dsd1 a qb:DataStructureDefinition;
     rdfs:comment "shipments by time (multiple measures approach)"@en;
     qb:component 
         [ qb:dimension  sdmx-dimension:refTime; ],
@@ -771,8 +1217,7 @@
         [ qb:measure    eg-measure:weight; ] . </pre>
         
 <p>This would correspond to individual observations such as:</p>
-<pre>
-eg:dataset1 a qb:DataSet;
+<pre>eg:dataset1 a qb:DataSet;
     qb:structure eg:dsd1 .
     
 eg:obs1a  a qb:Observation;
@@ -789,11 +1234,11 @@
   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>
+</div>
 
 
-<section id="dsd-mm-dim">
-<h4>Measure dimension</h4>
+<div class="section" id="dsd-mm-dim">
+<h4><span class="secno">5.5.2 </span>Measure dimension</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>.
@@ -813,8 +1258,7 @@
   Thus, qb:measureType is a “magic” dimension property with an implicit code list.</p>
 
 <p>The data structure definition for our above example, using this representation approach, would then be:</p>
-<pre>
-eg:dsd2 a qb:DataStructureDefinition;
+<pre>eg:dsd2 a qb:DataStructureDefinition;
     rdfs:comment "shipments by time (measure dimension approach)"@en;
     qb:component 
         [ qb:dimension  sdmx-dimension:refTime; ],
@@ -823,8 +1267,7 @@
         [ qb:dimension  qb:measureType; ] . </pre>
         
 <p>This would correspond to individual observations such as:</p>
-<pre>
-eg:dataset2 a qb:DataSet;
+<pre>eg:dataset2 a qb:DataSet;
     qb:structure eg:dsd2 .
     
 eg:obs2a  a qb:Observation;
@@ -843,22 +1286,22 @@
 <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>
+  a uniform way of declaring and using measure properties on all kinds of datasets.</p><p>
   
-<p>Those familiar with SDMX should also note that in the RDF representation there is 
+</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. The SDMX-in-RDF extension
   vocabulary addresses the round-tripping of the SDMX primary measure by use of a
   separate annotation on <code>sdmx:DataStructureDefinition</code>.</p>
-</section>
+</div>
 
-</section>
+</div>
 
-</section>
+</div>
 
 
-<section id="datasets">
-<h2>Expressing data sets</h2>
+<div class="section" id="datasets">
+<!--OddPage--><h2><span class="secno">6. </span>Expressing data sets</h2>
 
 <p>A DataSet is a collection of statistical data that corresponds to a given data structure definition. 
 The data in a data set can be roughly described as belonging to one of the following kinds:</p>
@@ -874,7 +1317,7 @@
       Datasets can have additional organizational structure in the form of <em>slices</em> 
     as described earlier in <a href="#cubes-slices">section 2.2</a>.
 
-  <dt>Internal metadata</dt>
+  </dd><dt>Internal 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 
@@ -888,8 +1331,8 @@
 </dl>
 
 
-<section id="dataset-basic">
-<h3>Data sets and observations</h3>
+<div class="section" id="dataset-basic">
+<h3><span class="secno">6.1 </span>Data sets and observations</h3>
 
 <p>A resource representing the entire data set is created and typed as <code>qb:DataSet</code> and
   linked to the corresponding data structure definition via the <tt>qb:structure</tt> property.</p>
@@ -906,8 +1349,7 @@
 
 <p>Thus for our running example we might expect to have:</p>
 
-<pre>
-  eg:dataset-le1 a qb:DataSet;
+<pre>  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 ;
@@ -916,27 +1358,27 @@
   eg:o1 a qb:Observation;
       qb:dataSet  eg:dataset-le1 ;
       eg:refArea                 admingeo:newport_00pr ;                  
-      eg:refPeriod               &lt;http://reference.data.gov.uk/id/gregorian-interval/2004-01-01T00:00:00/P3Y> ;
+      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> ;
+      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                 admingeo:cardiff_00pt ;                  
-      eg:refPeriod               &lt;http://reference.data.gov.uk/id/gregorian-interval/2004-01-01T00:00:00/P3Y> ;
+      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> ;
+      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                 admingeo:monmouthshire_00pp ;                  
-      eg:refPeriod               &lt;http://reference.data.gov.uk/id/gregorian-interval/2004-01-01T00:00:00/P3Y> ;
+      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> ;
+      sdmx-attribute:unitMeasure &lt;http://dbpedia.org/resource/Year&gt; ;
       eg:lifeExpectancy          76.6 ;
       .
 
@@ -951,18 +1393,17 @@
   original Data Structure Declaration we see that we declared the unit of measure to be
   attached at the data set level. So the corrected example is:</p>
 
-<pre>
-  eg:dataset-le1 a qb:DataSet;
+<pre>  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> ;
+      sdmx-attribute:unitMeasure &lt;http://dbpedia.org/resource/Year&gt; ;
       .
       
   eg:o1 a qb:Observation;
       qb:dataSet  eg:dataset-le1 ;
       eg:refArea                 admingeo:newport_00pr ;                  
-      eg:refPeriod               &lt;http://reference.data.gov.uk/id/gregorian-interval/2004-01-01T00:00:00/P3Y> ;
+      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 ;
       .
@@ -970,7 +1411,7 @@
   eg:o2 a qb:Observation;
       qb:dataSet  eg:dataset-le1 ;
       eg:refArea                 admingeo:cardiff_00pt ;                  
-      eg:refPeriod               &lt;http://reference.data.gov.uk/id/gregorian-interval/2004-01-01T00:00:00/P3Y> ;
+      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 ;
       .
@@ -978,7 +1419,7 @@
   eg:o3 a qb:Observation;
       qb:dataSet  eg:dataset-le1 ;
       eg:refArea                 admingeo:monmouthshire_00pp ;                  
-      eg:refPeriod               &lt;http://reference.data.gov.uk/id/gregorian-interval/2004-01-01T00:00:00/P3Y> ;
+      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 ;
       .
@@ -990,13 +1431,13 @@
   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>
+</div>
 
-</section>
+</div>
 
 
-<section id="slices">
-<h2>Slices</h2>
+<div class="section" id="slices">
+<!--OddPage--><h2><span class="secno">7. </span>Slices</h2>
 
 <p>Slices allow us to group subsets of observations together. This not intended
   to represent arbitrary selections from the observations but uniform slices
@@ -1019,8 +1460,7 @@
    lists the component properties (which must be dimensions) which will be fixed in the
    slice. The key is attached to the DSD using <code>qb:sliceKey</code>. For example: </p>
    
-<pre>
-  eg:sliceByRegion a qb:SliceKey;
+<pre>  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 .
@@ -1040,25 +1480,24 @@
   of <code>qb:sliceStructure</code>. Data sets indicate
   the slices they contain by means of <code>qb:slice</code>. Thus in our example we would have:</p>
 
-<pre>
-  eg:dataset-le2 a qb:DataSet;
+<pre>  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> ;
+      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> ;
+      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                 admingeo:newport_00pr ;                  
-      eg:refPeriod               &lt;http://reference.data.gov.uk/id/gregorian-interval/2004-01-01T00:00:00/P3Y> ;
+      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 ;
       .
@@ -1066,7 +1505,7 @@
   eg:o2b a qb:Observation;
       qb:dataSet  eg:dataset-le2 ;
       eg:refArea                 admingeo:cardiff_00pt ;                  
-      eg:refPeriod               &lt;http://reference.data.gov.uk/id/gregorian-interval/2004-01-01T00:00:00/P3Y> ;
+      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 ;
       .
@@ -1074,7 +1513,7 @@
   eg:o3b a qb:Observation;
       qb:dataSet  eg:dataset-le2 ;
       eg:refArea                 admingeo:monmouthshire_00pp ;                  
-      eg:refPeriod               &lt;http://reference.data.gov.uk/id/gregorian-interval/2004-01-01T00:00:00/P3Y> ;
+      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 ;
       .
@@ -1088,8 +1527,7 @@
 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>
-<pre>
-  eg:dsd-le-slice3 a qb:DataStructureDefinition;
+<pre>  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];
@@ -1102,13 +1540,13 @@
       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> ;
+      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> ;
+      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, ... .
 
@@ -1142,11 +1580,11 @@
   in general flat representations are recommended to simplify data consumption. 
   Some tool chains may support (dynamic or static) generation flattened representations from 
   abbreviated data sets.</p>
-</section>
+</div>
 
 
-<section id="schemes">
-<h2>Concept schemes and code lists</h2>
+<div class="section" id="schemes">
+<!--OddPage--><h2><span class="secno">8. </span>Concept schemes and code lists</h2>
 
 <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)
@@ -1166,13 +1604,12 @@
 <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>
 
-<pre>
-sdmx-code:sex a skos:ConceptScheme;
+<pre>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> ;
+    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 .
@@ -1215,8 +1652,7 @@
 
 <p>This code list can then be associated with a coded property, such as a dimension:</p>
 
-<pre>
-  eg:sex a sdmx:DimensionProperty, sdmx:CodedProperty;
+<pre>  eg:sex a sdmx:DimensionProperty, sdmx:CodedProperty;
       qb:codeList sdmx-code:sex ;
       rdfs:range sdmx-code:Sex .
 </pre>
@@ -1235,11 +1671,11 @@
 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>
+</div>
 
 
-<section id="metadata">
-<h2>DataSet metadata</h2>
+<div class="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. Metadata such as a display label (<code>rdfs:label</code>),
@@ -1248,8 +1684,8 @@
 for representing the key metadata annotations commonly needed for DataSets.</p>
 
 
-<section id="metadata-categorization">
-<h3>Categorizing a data set</h3>
+<div class="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>.
@@ -1265,8 +1701,7 @@
 
 <p>Thus our sample dataset might be marked up by:</p>
 
-<pre>
-  eg:dataset1 a qb:DataSet;
+<pre>  eg:dataset1 a qb:DataSet;
       rdfs:label "Life expectancy"@en;
       rdfs:comment "Life expectancy within Welsh Unitary authorities - extracted from Stats Wales"@en;
       dcterms:date "2010-08-11"^^xsd:date;
@@ -1279,33 +1714,32 @@
 
 <p>where <code>eg:Wales</code> is a <code>skos:Concept</code> drawn from an appropriate controlled
 vocabulary for places.</p>
-</section>
+</div>
 
 
-<section id="metadata-publishers">
-<h3>Describing publishers</h3>
+<div class="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>dcterms: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> [[ORG]].</p>
+some more specific subclass such as <code>org:Organization</code> [<cite><a href="#bib-ORG" rel="biblioentry" class="bibref">ORG</a></cite>].</p>
 
-<pre>
-eg:dataset1 a qb:DataSet;
-    dc:publisher &lt;http://example.com/meta#organization> .
+<pre>eg:dataset1 a qb:DataSet;
+    dc:publisher &lt;http://example.com/meta#organization&gt; .
     
-&lt;http://example.com/meta#organization> a org:Organization, foaf:Agent;
+&lt;http://example.com/meta#organization&gt; a org:Organization, foaf:Agent;
     rdfs:label "Example org" .    
 </pre>
 
 <p>Note that the SDMX extension vocabulary supports further description of 
   publication pipelines (data flows, reporting taxonomies, maintainers, provision agreements).</p>
-</section>
+</div>
 
-</section>
+</div>
 
-<section id="namespaces-used-appendix" class="appendix">
-<h2>Namespaces used in this document</h2>
+<div id="namespaces-used-appendix" class="appendix section">
+<!--OddPage--><h2><span class="secno">A. </span>Namespaces used in this document</h2>
 
 <table class="spare-table">
   <thead> <tr>
@@ -1357,17 +1791,17 @@
     </tr>
   </tbody>
 </table>
-</section>
+</div>
 
 
-<section id="vocab-reference" class="appendix">
-<h2>Vocabulary reference</h2>
+<div id="vocab-reference" class="appendix section">
+<!--OddPage--><h2><span class="secno">B. </span>Vocabulary reference</h2>
 
 
-<section id="reference-datasets">
-<h3>DataSets</h3>
+<div class="section" id="reference-datasets">
+<h3><span class="secno">B.1 </span>DataSets</h3>
 
-<dl class='vocab_reference'>
+<dl class="vocab_reference">
 
   <dt id="ref_qb_DataSet">
     <em>Class:</em> <code>qb:DataSet</code>
@@ -1378,13 +1812,13 @@
   </dt>
  <dd>Represents a collection of observations, possibly organized into various slices, conforming to some common dimensional structure.</dd>
 </dl>
-</section>
+</div>
 
 
-<section id="reference-observations">
-<h3>Observations</h3>
+<div class="section" id="reference-observations">
+<h3><span class="secno">B.2 </span>Observations</h3>
 
-<dl class='vocab_reference'>
+<dl class="vocab_reference">
 
   <dt id="ref_qb_Observation">
     <em>Class:</em> <code>qb:Observation</code>
@@ -1399,7 +1833,7 @@
     <em>Property:</em> <code>qb:dataSet</code>
     (
     <code>qb:Observation</code>
-    -> 
+    -&gt; 
     <code>qb:DataSet</code>
   ) 
   </dt>
@@ -1409,19 +1843,19 @@
     <em>Property:</em> <code>qb:observation</code>
     (
     <code>qb:Slice</code>
-    -> 
+    -&gt; 
     <code>qb:Observation</code>
   ) 
   </dt>
   <dd>indicates a observation contained within this slice of the data set</dd>
 </dl>
-</section>
+</div>
 
 
-<section id="reference-slices">
-<h3>Slices</h3>
+<div class="section" id="reference-slices">
+<h3><span class="secno">B.3 </span>Slices</h3>
 
-<dl class='vocab_reference'>
+<dl class="vocab_reference">
 
   <dt id="ref_qb_Slice">
     <em>Class:</em> <code>qb:Slice</code>
@@ -1434,7 +1868,7 @@
     <em>Property:</em> <code>qb:slice</code>
     (
     <code>qb:DataSet</code>
-    -> 
+    -&gt; 
     <code>qb:Slice</code>
   ) 
   </dt>
@@ -1444,18 +1878,18 @@
     <em>Property:</em> <code>qb:subSlice</code>
     (
     <code>qb:Slice</code>
-    -> 
+    -&gt; 
     <code>qb:Slice</code>
   ) 
   </dt>
   <dd>Indicates a narrower slice which has additional fixed dimensional values, for example a time-series slice might a subSlice of a slice which spans both time and geographic area</dd>
 </dl>
-</section>
+</div>
 
 
-<section id="reference-components">
-<h3>Dimensions, Attributes, Measures</h3>
-<dl class='vocab_reference'>
+<div class="section" id="reference-components">
+<h3><span class="secno">B.4 </span>Dimensions, Attributes, Measures</h3>
+<dl class="vocab_reference">
 
   <dt id="ref_qb_Attachable">
     <em>Class:</em> <code>qb:Attachable</code>
@@ -1498,28 +1932,28 @@
   </dt>
  <dd>Superclass of all coded ComponentProperties</dd>
 </dl>
-</section>
+</div>
 
 
-<section id="reference-component-properties">
-<h3>Reusable general purpose component properties</h3>
-<dl class='vocab_reference'>
+<div class="section" id="reference-component-properties">
+<h3><span class="secno">B.5 </span>Reusable general purpose component properties</h3>
+<dl class="vocab_reference">
 
   <dt id="ref_qb_measureType">
     <em>Property:</em> <code>qb:measureType</code>
     (
-    -> 
+    -&gt; 
     <code>qb:MeasureProperty</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 obsValue (or other primary measure)</dd>
 </dl>
-</section>
+</div>
 
 
-<section id="reference-dsd">
-<h3>Data Structure Definitions</h3>
-<dl class='vocab_reference'>
+<div class="section" id="reference-dsd">
+<h3><span class="secno">B.6 </span>Data Structure Definitions</h3>
+<dl class="vocab_reference">
 
   <dt id="ref_qb_DataStructureDefinition">
     <em>Class:</em> <code>qb:DataStructureDefinition</code>
@@ -1532,7 +1966,7 @@
     <em>Property:</em> <code>qb:structure</code>
     (
     <code>qb:DataSet</code>
-    -> 
+    -&gt; 
     <code>qb:DataStructureDefinition</code>
   ) 
   </dt>
@@ -1542,18 +1976,18 @@
     <em>Property:</em> <code>qb:component</code>
     (
     <code>qb:DataStructureDefinition</code>
-    -> 
+    -&gt; 
     <code>qb:ComponentSpecification</code>
   ) 
   </dt>
   <dd>indicates a component specification which is included in the structure of the dataset</dd>
 </dl>
-</section>
+</div>
 
 
-<section id="reference-compspec">
-<h3>Component specifications - for qualifying component use in a DSD</h3>
-<dl class='vocab_reference'>
+<div class="section" id="reference-compspec">
+<h3><span class="secno">B.7 </span>Component specifications - for qualifying component use in a DSD</h3>
+<dl class="vocab_reference">
 
   <dt id="ref_qb_ComponentSpecification">
     <em>Class:</em> <code>qb:ComponentSpecification</code>
@@ -1571,7 +2005,7 @@
     <em>Property:</em> <code>qb:componentProperty</code>
     (
     <code>qb:ComponentSet</code>
-    -> 
+    -&gt; 
     <code>qb:ComponentProperty</code>
   ) 
   </dt>
@@ -1581,7 +2015,7 @@
     <em>Property:</em> <code>qb:order</code>
     (
     <code>qb:ComponentSpecification</code>
-    -> 
+    -&gt; 
     <code>xsd:int</code>
   ) 
   </dt>
@@ -1591,7 +2025,7 @@
     <em>Property:</em> <code>qb:componentRequired</code>
     (
     <code>qb:ComponentSpecification</code>
-    -> 
+    -&gt; 
     <code>xsd:boolean</code>
   ) 
   </dt>
@@ -1601,7 +2035,7 @@
     <em>Property:</em> <code>qb:componentAttachment</code>
     (
     <code>qb:ComponentSpecification</code>
-    -> 
+    -&gt; 
     <code>rdfs:Class</code>
   ) 
   </dt>
@@ -1610,7 +2044,7 @@
   <dt id="ref_qb_dimension">
     <em>Property:</em> <code>qb:dimension</code>
     (
-    -> 
+    -&gt; 
     <code>qb:DimensionProperty</code>
     ; <em>sub property of: </em>
     <code>qb:componentProperty</code>
@@ -1621,7 +2055,7 @@
   <dt id="ref_qb_measure">
     <em>Property:</em> <code>qb:measure</code>
     (
-    -> 
+    -&gt; 
     <code>qb:MeasureProperty</code>
     ; <em>sub property of: </em>
     <code>qb:componentProperty</code>
@@ -1632,7 +2066,7 @@
   <dt id="ref_qb_attribute">
     <em>Property:</em> <code>qb:attribute</code>
     (
-    -> 
+    -&gt; 
     <code>qb:AttributeProperty</code>
     ; <em>sub property of: </em>
     <code>qb:componentProperty</code>
@@ -1643,7 +2077,7 @@
   <dt id="ref_qb_measureDimension">
     <em>Property:</em> <code>qb:measureDimension</code>
     (
-    -> 
+    -&gt; 
     <code>qb:DimensionProperty</code>
     ; <em>sub property of: </em>
     <code>qb:componentProperty</code>
@@ -1651,12 +2085,12 @@
   </dt>
   <dd>An alternative to qb:componentProperty which makes explicit that the component is a measure dimension</dd>
 </dl>
-</section>
+</div>
 
 
-<section id="reference-slice-definitions">
-<h3>Slice definitions</h3>
-<dl class='vocab_reference'>
+<div class="section" id="reference-slice-definitions">
+<h3><span class="secno">B.8 </span>Slice definitions</h3>
+<dl class="vocab_reference">
 
   <dt id="ref_qb_SliceKey">
     <em>Class:</em> <code>qb:SliceKey</code>
@@ -1669,7 +2103,7 @@
     <em>Property:</em> <code>qb:sliceStructure</code>
     (
     <code>qb:Slice</code>
-    -> 
+    -&gt; 
     <code>qb:SliceKey</code>
   ) 
   </dt>
@@ -1679,24 +2113,24 @@
     <em>Property:</em> <code>qb:sliceKey</code>
     (
     <code>qb:DataSet</code>
-    -> 
+    -&gt; 
     <code>qb:SliceKey</code>
   ) 
   </dt>
   <dd>indicates a slice key which is used for slices in this dataset</dd>
 </dl>
-</section>
+</div>
 
 
-<section id="reference-concepts">
-<h3>Concepts</h3>
-<dl class='vocab_reference'>
+<div class="section" id="reference-concepts">
+<h3><span class="secno">B.9 </span>Concepts</h3>
+<dl class="vocab_reference">
 
   <dt id="ref_qb_concept">
     <em>Property:</em> <code>qb:concept</code>
     (
     <code>qb:ComponentProperty</code>
-    -> 
+    -&gt; 
     <code>skos:Concept</code>
   ) 
   </dt>
@@ -1706,19 +2140,19 @@
     <em>Property:</em> <code>qb:codeList</code>
     (
     <code>qb:CodedProperty</code>
-    -> 
+    -&gt; 
     <code>skos:ConceptScheme</code>
   ) 
   </dt>
   <dd>gives the code list associated with a CodedProperty</dd>
 </dl>
-</section>
+</div>
 
-</section>
+</div>
 
 
-<section id="acknowledgements" class="appendix">
-<h2>Acknowledgements</h2>
+<div id="acknowledgements" class="appendix section">
+<!--OddPage--><h2><span class="secno">C. </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
@@ -1731,11 +2165,11 @@
 
 <p>The authors would also like to thank John Sheridan for his comments,
 suggestions and support for this work.</p>
-</section>
+</div>
 
 
-<section id="issues">
-<h2>Open issues</h2>
+<div class="section" id="issues">
+<!--OddPage--><h2><span class="secno">D. </span>Open issues</h2>
 
 <p>
   Based on early use experiences with the vocabulary the working group is considering 
@@ -1745,22 +2179,22 @@
   will be addressed by the working group.
 </p>
 
-  <div class='issue'>
-    <h3><a href="http://www.w3.org/2011/gld/track/issues/29">Issue-29</a>:
+  <div class="issue">
+    <h3 id="issue-29------criteria-for-well-formedness"><a href="http://www.w3.org/2011/gld/track/issues/29">Issue-29</a>:
     Criteria for well-formedness</h3>
     <p>Specify additional <em>well-formedness</em> criteria to which
     cube-publishers should adhere to facilitate tool interoperability.</p>
   </div>
 
-  <div class='issue'>
-    <h3><a href="http://www.w3.org/2011/gld/track/issues/30">Issue-30</a>:
+  <div class="issue">
+    <h3 id="issue-30--------declaring-relations-between-cubes"><a href="http://www.w3.org/2011/gld/track/issues/30">Issue-30</a>:
       Declaring relations between cubes</h3>
     <p>Consider extending the vocabulary to support declaring
       relations between data cubes (or between measures within a cube).</p>
   </div>
 
-  <div class='issue'>
-    <h3><a href="http://www.w3.org/2011/gld/track/issues/31">Issue-31</a>:
+  <div class="issue">
+    <h3 id="issue-31--------supporting-aggregation-for-other-than-skos-hierarchies"><a href="http://www.w3.org/2011/gld/track/issues/31">Issue-31</a>:
       Supporting aggregation for other than SKOS hierarchies</h3>
     <p>The Data Cube vocabulary allows hierarchical code lists to be
       used as dimensions values by means of SKOS. Consider whether to
@@ -1768,22 +2202,22 @@
       (e.g. geo-spatial containment) without requiring mapping to SKOS.</p>
   </div>
 
-  <div class='issue'>
-    <h3><a href="http://www.w3.org/2011/gld/track/issues/32">Issue-32</a>:
-      Relationship to ISO 19156 - Observations & Measurements</h3>
+  <div class="issue">
+    <h3 id="issue-32--------relationship-to-iso-19156---observations---measurements"><a href="http://www.w3.org/2011/gld/track/issues/32">Issue-32</a>:
+      Relationship to ISO 19156 - Observations &amp; Measurements</h3>
     <p>
       One use case for the Data Cube vocabulary is for the publication
       of observational, sensor network and forecast data
       sets. Existing standards for such publication include OGC
-      Observations & Measurements (ISO 19156). There are multiple ways
-      that Data Cube can be mapped to the logical model of O&M. 
+      Observations &amp; Measurements (ISO 19156). There are multiple ways
+      that Data Cube can be mapped to the logical model of O&amp;M. 
       Consider making an explicit statement of the ways in which Data
-      Cube can be related to O&M as guidance for users seeking to
+      Cube can be related to O&amp;M as guidance for users seeking to
       work with both specifications.</p>
   </div>
 
-  <div class='issue'>
-    <h3><a href="http://www.w3.org/2011/gld/track/issues/33">Issue-33</a>:
+  <div class="issue">
+    <h3 id="issue-33--------collections-of-observations-and-well-formedness-of-slices"><a href="http://www.w3.org/2011/gld/track/issues/33">Issue-33</a>:
       Collections of observations and well-formedness of slices</h3>
     <p>
       Experience with Data Cube has shown that publishers often wish
@@ -1793,8 +2227,8 @@
       of <code>qb:Slice</code> or through an additional collection mechanism.</p>
   </div>
 
-  <div class='issue'>
-    <h3><a href="http://www.w3.org/2011/gld/track/issues/34">Issue-34</a>:
+  <div class="issue">
+    <h3 id="issue-34--------clarify-or-drop-qb-subslice"><a href="http://www.w3.org/2011/gld/track/issues/34">Issue-34</a>:
       Clarify or drop qb:subslice</h3>
     <p>
       Use of <code>qb:subslice</code> in abbreviated datasets can result
@@ -1803,12 +2237,22 @@
   </div>
 
 
-</section>
+</div>
 
 
-<section id="references" class="appendix">
-<p class="todo">Bring all references into W3C style</p>
-</section>
 
-</body>
-</html>
+
+
+
+<div class="appendix section" id="references"><!--OddPage--><h2><span class="secno">E. </span>References</h2>
+<p class="todo">Bring all references into <acronym title="World Wide Web Consortium">W3C</acronym> style</p>
+<div class="section" id="normative-references"><h3><span class="secno">E.1 </span>Normative references</h3><p>No normative references.</p></div><div class="section" id="informative-references"><h3><span class="secno">E.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-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 v1, <a href="http://www.ordnancesurvey.co.uk/ontology/v1/AdministrativeGeography.rdf">http://www.ordnancesurvey.co.uk/ontology/v1/AdministrativeGeography.rdf</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-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-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-TURTLE-TR">[TURTLE-TR]</dt><dd>Eric Prud'hommeaux, Gavin Carothers. <a href="http://www.w3.org/TR/2011/WD-turtle-20110809/"><cite>Turtle: Terse RDF Triple Language.</cite></a> 09 August 2011. W3C Working Draft. URL: <a href="http://www.w3.org/TR/2011/WD-turtle-20110809/">http://www.w3.org/TR/2011/WD-turtle-20110809/</a>
+</dd></dl></div></div></body></html>