--- a/data-cube/index.html Thu Mar 07 16:49:46 2013 +0000
+++ b/data-cube/index.html Thu Mar 07 17:10:17 2013 +0000
@@ -108,9 +108,6 @@
<section id="introduction" class="informative">
<h2>Introduction</h2>
-<section id="intro-cube" class="informative">
-<h3>A Data Cube vocabulary</h3>
-
<p>
Statistical data is a foundation for policy
prediction, planning and adjustments and
@@ -158,10 +155,8 @@
<li><a href="http://www.w3.org/ns/org#">ORG</a> for organizations</li>
</ul>
-</section>
-
-<section id="intro-rdf" class="informative">
+<section id="intro-rdf" >
<h3>RDF and Linked Data</h3>
<p><em>Linked data</em> is an approach to publishing data on the web, enabling
@@ -196,7 +191,7 @@
</section>
-<section id="intro-sdmx" class="informative">
+<section id="intro-sdmx" >
<h3>SDMX and related standards</h3>
<p>The Statistical Data and Metadata Exchange (SDMX) Initiative
@@ -241,38 +236,7 @@
</section>
-<section id="intro-scovo" class="informative">
-<h3>Relationship to SCOVO</h3>
-
-<p>The Statistical Core Vocabulary (SCOVO) [[SCOVO]] 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
-model is extensible both on the schema and the instance level for more
-specialized use cases.</p>
-<p>While SCOVO addresses the basic use case of expressing statistical
-data in RDF, its minimalist design is limiting, and it does not
-support important scenarios that occur in statistical publishing, such
-as:</p>
-
-<ul>
- <li>definition and publication of the structure of a dataset
-independent from concrete data,</li>
- <li>data flows which group together datasets that share the same
-structure, for example from different national data providers,</li>
- <li>definition of "slices" through a dataset, such as an individual
-time series or cross-section, for individual annotation,</li>
- <li>distinctions between dimensions, attributes and measures.</li>
-</ul>
-
-<p>
-The design of the Data Cube vocabulary is informed by SCOVO,
-and every SCOVO dataset can be re-expressed within the Data Cube vocabulary.
-</p>
-</section>
-
-
-<section id="intro-audience" class="informative">
+<section id="intro-audience" >
<h3>Audience and scope</h3>
<p>This document describes the Data Cube vocabulary
@@ -282,9 +246,10 @@
formats such as SDMX-ML are not covered here.</p>
</section>
+</section>
-<section id="intro-conventions">
-<h3>Document conventions</h3>
+<section id="namespaces">
+<h2>Namespaces and Document Conventions</h2>
<p>
The names of RDF entities -- classes, predicates, individuals -- are
@@ -292,22 +257,14 @@
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>All RDF examples are written in Turtle syntax [[!TURTLE-TR]].</p>
-</section>
-
-</section>
-
-<section id="namespaces">
-<h2>Namespaces</h2>
-
<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>[[!SKOS-REFERENCE]]</td></tr>
<tr><td>scovo</td><td><a href="http://purl.org/NET/scovo#">http://purl.org/NET/scovo#</a></td><td>[[SCOVO]]</td></tr>
<tr><td>void</td><td><a href="http://rdfs.org/ns/void#">http://rdfs.org/ns/void#</a></td><td>[[VOID]]</td></tr>
@@ -318,11 +275,11 @@
<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>[[!RDF-CONCEPTS]]</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>[[!RDF-SCHEMA]]</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>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>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>
@@ -422,8 +379,6 @@
</section>
-</section>
-
<section id="example" class="informative">
<h2>An example</h2>
@@ -554,6 +509,9 @@
</section>
+</section>
+
+
<section id="dsd">
<h2>Creating data structure definitions</h2>
@@ -755,13 +713,13 @@
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,
- a so called <em><a>flattened</a></em> representation.
+ well call this the <em><a>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 a
- non-flat structure, the <code><a>qb:componentAttachment</a></code> property of the specification should
+ This reduces some of the redundancy in the encoding of the instance data. To declare such an
+ abbreviated structure, the <code><a>qb:componentAttachment</a></code> property of the specification should
reference the class corresponding to the attachment level (e.g. <code><a>qb:DataSet</a></code> for attributes
that will be attached to the overall data set).</li>
</ul>
@@ -769,7 +727,7 @@
<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
- flattened representations are in general easier to query and combine.</p>
+ 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>
@@ -950,7 +908,7 @@
<dt>External 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 11</a>.</dd>
+ External metadata is described in <a href="#metadata">section 10</a>.</dd>
</dl>
@@ -1009,7 +967,7 @@
...
</pre>
-<p>This <a>flattened</a> structure makes it easy to query and combine data sets
+<p>This <a>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
@@ -1149,7 +1107,7 @@
</pre>
<p>Note that here we are still repeating the dimension values on the individual observations.
-This flattened representation means that a consuming application can still query
+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:
@@ -1472,16 +1430,16 @@
</section>
<section id="normalize">
-<h2>Abbreviation and normalization</h2>
+<h2>Abbreviated and normalized data cubes</h2>
<p>In normal form then the <code><a>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>flattened</dfn></em>. It is a convenient format for
+termed <em><dfn>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 flattened representation
+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.
</p>
@@ -1508,20 +1466,19 @@
<div class="note">
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 is has not received as much
+However as a new addition it has not received as much
scrutiny as other parts of the specification. If problems are uncovered
during the Last Call process the working group may retract all or part of this section.
</div>
<p>We define these notions by means of a transformation algorithm
- which can normalize an abbreviated Data Cube to a flattened
- representation. We express this transformation using the SPARQL 1.1
+ which can normalize an abbreviated Data Cube. We express this transformation using the SPARQL 1.1
Update language [[!SPARQL-UPDATE-11]]. 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 flattened form or any mix of these.</p>
+ all data in normalized form or any mix of these.</p>
<p>The normalization algorithm comprises two sets of SPARQL Update
@@ -1597,13 +1554,13 @@
<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 flattened down to the corresponding
+ of that component to be pushed down to the corresponding
observations.
</p>
<table class="bordered-table">
<thead>
- <tr><th>Phase 2: Flatten attachment levels</th></tr>
+ <tr><th>Phase 2: Push down attachment levels</th></tr>
</thead>
<tbody><tr><td>
<pre>
@@ -2659,7 +2616,7 @@
<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 flattening algorithm
+ <li>Added <a href="#normalize">section</a> on normalization algorithm
for handling abbreviated cubes.</li>
<li>Added <a href="#conformance">conformance section</a>.
<li>Clarified that <code><a>qb:componentRequired</a></code> is only applicable to
--- a/data-cube/static.html Thu Mar 07 16:49:46 2013 +0000
+++ b/data-cube/static.html Thu Mar 07 17:10:17 2013 +0000
@@ -249,9 +249,22 @@
<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>, <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>
-
-<p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2013 <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>, <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>
+
+ <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>
@@ -334,7 +347,7 @@
-</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-cube" class="tocxref"><span class="secno">2.1 </span>A Data Cube vocabulary</a></li><li class="tocline"><a href="#intro-rdf" class="tocxref"><span class="secno">2.2 </span>RDF and Linked Data</a></li><li class="tocline"><a href="#intro-sdmx" class="tocxref"><span class="secno">2.3 </span>SDMX and related standards</a></li><li class="tocline"><a href="#intro-scovo" class="tocxref"><span class="secno">2.4 </span>Relationship to SCOVO</a></li><li class="tocline"><a href="#intro-audience" class="tocxref"><span class="secno">2.5 </span>Audience and scope</a></li><li class="tocline"><a href="#intro-conventions" class="tocxref"><span class="secno">2.6 </span>Document conventions</a></li></ul></li><li class="tocline"><a href="#namespaces" class="tocxref"><span class="secno">3. </span>Namespaces</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" class="tocxref"><span class="secno">5.1 </span>The cube model - dimensions, attributes, measures</a></li><li class="tocline"><a href="#cubes-slices" class="tocxref"><span class="secno">5.2 </span>Slices</a></li></ul></li><li class="tocline"><a href="#example" class="tocxref"><span class="secno">6. </span>An example</a></li><li class="tocline"><a href="#dsd" class="tocxref"><span class="secno">7. </span>Creating data structure definitions</a><ul class="toc"><li class="tocline"><a href="#dsd-dimensions" class="tocxref"><span class="secno">7.1 </span>Dimensions, attributes and measures</a></li><li class="tocline"><a href="#dsd-cog" class="tocxref"><span class="secno">7.2 </span>Content oriented guidelines</a></li><li class="tocline"><a href="#dsd-example" class="tocxref"><span class="secno">7.3 </span>Example</a></li><li class="tocline"><a href="#dsd-dsd" class="tocxref"><span class="secno">7.4 </span>ComponentSpecifications and DataStructureDefinitions</a></li><li class="tocline"><a href="#dsd-mm" class="tocxref"><span class="secno">7.5 </span>Handling multiple measures</a><ul class="toc"><li class="tocline"><a href="#dsd-mm-obs" class="tocxref"><span class="secno">7.5.1 </span>Multi-measure observations</a></li><li class="tocline"><a href="#dsd-mm-dim" class="tocxref"><span class="secno">7.5.2 </span><span>Measure dimension</span></a></li></ul></li></ul></li><li class="tocline"><a href="#datasets" class="tocxref"><span class="secno">8. </span>Expressing data sets</a><ul class="toc"><li class="tocline"><a href="#dataset-basic" class="tocxref"><span class="secno">8.1 </span>Data sets and observations</a></li></ul></li><li class="tocline"><a href="#slices" class="tocxref"><span class="secno">9. </span>Slices</a></li><li class="tocline"><a href="#schemes" class="tocxref"><span class="secno">10. </span>Concept schemes and code lists</a><ul class="toc"><li class="tocline"><a href="#schemes-intro" class="tocxref"><span class="secno">10.1 </span>Coded values for components properties</a></li><li class="tocline"><a href="#schemes-hierarchy" class="tocxref"><span class="secno">10.2 </span>Hierarchical code lists</a></li><li class="tocline"><a href="#schemes-hierarchy-nonskos" class="tocxref"><span class="secno">10.3 </span>Non-SKOS hierarchies</a></li><li class="tocline"><a href="#schemes-aggregation" class="tocxref"><span class="secno">10.4 </span>Aggregation</a></li></ul></li><li class="tocline"><a href="#metadata" class="tocxref"><span class="secno">11. </span>DataSet metadata</a><ul class="toc"><li class="tocline"><a href="#metadata-categorization" class="tocxref"><span class="secno">11.1 </span>Categorizing a data set</a></li><li class="tocline"><a href="#metadata-publishers" class="tocxref"><span class="secno">11.2 </span>Describing publishers</a></li></ul></li><li class="tocline"><a href="#normalize" class="tocxref"><span class="secno">12. </span>Abbreviation and normalization</a><ul class="toc"><li class="tocline"><a href="#normalize-algorithm" class="tocxref"><span class="secno">12.1 </span>Normalization algorithm</a></li></ul></li><li class="tocline"><a href="#wf" class="tocxref"><span class="secno">13. </span>Well-formed cubes</a><ul class="toc"><li class="tocline"><a href="#wf-rules" class="tocxref"><span class="secno">13.1 </span>Integrity constraints</a></li></ul></li><li class="tocline"><a href="#vocab-reference" class="tocxref"><span class="secno">14. </span>Vocabulary reference</a><ul class="toc"><li class="tocline"><a href="#reference-datasets" class="tocxref"><span class="secno">14.1 </span>DataSets</a></li><li class="tocline"><a href="#reference-observations" class="tocxref"><span class="secno">14.2 </span>Observations</a></li><li class="tocline"><a href="#reference-slices" class="tocxref"><span class="secno">14.3 </span>Slices</a></li><li class="tocline"><a href="#reference-components" class="tocxref"><span class="secno">14.4 </span>Dimensions, Attributes, Measures</a></li><li class="tocline"><a href="#reference-component-properties" class="tocxref"><span class="secno">14.5 </span>Reusable general purpose component properties</a></li><li class="tocline"><a href="#reference-dsd" class="tocxref"><span class="secno">14.6 </span>Data Structure Definitions</a></li><li class="tocline"><a href="#reference-compspec" class="tocxref"><span class="secno">14.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">14.8 </span>Slice definitions</a></li><li class="tocline"><a href="#reference-concepts" class="tocxref"><span class="secno">14.9 </span>Concepts</a></li><li class="tocline"><a href="#reference-nonskos-hierarchy" class="tocxref"><span class="secno">14.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="#references" class="tocxref"><span class="secno">C. </span>References</a><ul class="toc"><li class="tocline"><a href="#normative-references" class="tocxref"><span class="secno">C.1 </span>Normative references</a></li><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">C.2 </span>Informative references</a></li></ul></li></ul></section>
+</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" class="tocxref"><span class="secno">5.1 </span>The cube model - dimensions, attributes, measures</a></li><li class="tocline"><a href="#cubes-slices" class="tocxref"><span class="secno">5.2 </span>Slices</a></li><li class="tocline"><a href="#example" class="tocxref"><span class="secno">5.3 </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</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></ul></li><li class="tocline"><a href="#slices" class="tocxref"><span class="secno">8. </span>Slices</a></li><li class="tocline"><a href="#schemes" class="tocxref"><span class="secno">9. </span>Concept schemes and code lists</a><ul class="toc"><li class="tocline"><a href="#schemes-intro" class="tocxref"><span class="secno">9.1 </span>Coded values for components properties</a></li><li class="tocline"><a href="#schemes-hierarchy" class="tocxref"><span class="secno">9.2 </span>Hierarchical code lists</a></li><li class="tocline"><a href="#schemes-hierarchy-nonskos" class="tocxref"><span class="secno">9.3 </span>Non-SKOS hierarchies</a></li><li class="tocline"><a href="#schemes-aggregation" class="tocxref"><span class="secno">9.4 </span>Aggregation</a></li></ul></li><li class="tocline"><a href="#metadata" class="tocxref"><span class="secno">10. </span>DataSet metadata</a><ul class="toc"><li class="tocline"><a href="#metadata-categorization" class="tocxref"><span class="secno">10.1 </span>Categorizing a data set</a></li><li class="tocline"><a href="#metadata-publishers" class="tocxref"><span class="secno">10.2 </span>Describing publishers</a></li></ul></li><li class="tocline"><a href="#normalize" class="tocxref"><span class="secno">11. </span>Abbreviated and normalized data cubes</a><ul class="toc"><li class="tocline"><a href="#normalize-algorithm" class="tocxref"><span class="secno">11.1 </span>Normalization algorithm</a></li></ul></li><li class="tocline"><a href="#wf" class="tocxref"><span class="secno">12. </span>Well-formed cubes</a><ul class="toc"><li class="tocline"><a href="#wf-rules" class="tocxref"><span class="secno">12.1 </span>Integrity constraints</a></li></ul></li><li class="tocline"><a href="#vocab-reference" class="tocxref"><span class="secno">13. </span>Vocabulary reference</a><ul class="toc"><li class="tocline"><a href="#reference-datasets" class="tocxref"><span class="secno">13.1 </span>DataSets</a></li><li class="tocline"><a href="#reference-observations" class="tocxref"><span class="secno">13.2 </span>Observations</a></li><li class="tocline"><a href="#reference-slices" class="tocxref"><span class="secno">13.3 </span>Slices</a></li><li class="tocline"><a href="#reference-components" class="tocxref"><span class="secno">13.4 </span>Dimensions, Attributes, Measures</a></li><li class="tocline"><a href="#reference-component-properties" class="tocxref"><span class="secno">13.5 </span>Reusable general purpose component properties</a></li><li class="tocline"><a href="#reference-dsd" class="tocxref"><span class="secno">13.6 </span>Data Structure Definitions</a></li><li class="tocline"><a href="#reference-compspec" class="tocxref"><span class="secno">13.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">13.8 </span>Slice definitions</a></li><li class="tocline"><a href="#reference-concepts" class="tocxref"><span class="secno">13.9 </span>Concepts</a></li><li class="tocline"><a href="#reference-nonskos-hierarchy" class="tocxref"><span class="secno">13.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="#references" class="tocxref"><span class="secno">C. </span>References</a><ul class="toc"><li class="tocline"><a href="#normative-references" class="tocxref"><span class="secno">C.1 </span>Normative references</a></li><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">C.2 </span>Informative references</a></li></ul></li></ul></section>
@@ -397,9 +410,6 @@
<section id="introduction" class="informative">
<!--OddPage--><h2><span class="secno">2. </span>Introduction</h2><p><em>This section is non-normative.</em></p>
-<section id="intro-cube" class="informative">
-<h3><span class="secno">2.1 </span>A Data Cube vocabulary</h3><p><em>This section is non-normative.</em></p>
-
<p>
Statistical data is a foundation for policy
prediction, planning and adjustments and
@@ -446,11 +456,9 @@
<li><a href="http://www.w3.org/ns/org#">ORG</a> for organizations</li>
</ul>
-</section>
-
-
-<section id="intro-rdf" class="informative">
-<h3><span class="secno">2.2 </span>RDF and Linked Data</h3><p><em>This section is non-normative.</em></p>
+
+<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.
@@ -484,8 +492,8 @@
</section>
-<section id="intro-sdmx" class="informative">
-<h3><span class="secno">2.3 </span>SDMX and related standards</h3><p><em>This section is non-normative.</em></p>
+<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 organisations (BIS,
@@ -529,39 +537,8 @@
</section>
-<section id="intro-scovo" class="informative">
-<h3><span class="secno">2.4 </span>Relationship to SCOVO</h3><p><em>This section is non-normative.</em></p>
-
-<p>The Statistical Core Vocabulary (SCOVO) [<cite><a class="bibref" href="#bib-SCOVO">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
-model is extensible both on the schema and the instance level for more
-specialized use cases.</p>
-<p>While SCOVO addresses the basic use case of expressing statistical
-data in RDF, its minimalist design is limiting, and it does not
-support important scenarios that occur in statistical publishing, such
-as:</p>
-
-<ul>
- <li>definition and publication of the structure of a dataset
-independent from concrete data,</li>
- <li>data flows which group together datasets that share the same
-structure, for example from different national data providers,</li>
- <li>definition of "slices" through a dataset, such as an individual
-time series or cross-section, for individual annotation,</li>
- <li>distinctions between dimensions, attributes and measures.</li>
-</ul>
-
-<p>
-The design of the Data Cube vocabulary is informed by SCOVO,
-and every SCOVO dataset can be re-expressed within the Data Cube vocabulary.
-</p>
-</section>
-
-
-<section id="intro-audience" class="informative">
-<h3><span class="secno">2.5 </span>Audience and scope</h3><p><em>This section is non-normative.</em></p>
+<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
@@ -570,9 +547,10 @@
formats such as SDMX-ML are not covered here.</p>
</section>
-
-<section id="intro-conventions">
-<h3><span class="secno">2.6 </span>Document conventions</h3>
+</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
@@ -580,22 +558,14 @@
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>All RDF examples are written in Turtle syntax [<cite><a class="bibref" href="#bib-TURTLE-TR">TURTLE-TR</a></cite>].</p>
-</section>
-
-</section>
-
-<section id="namespaces">
-<!--OddPage--><h2><span class="secno">3. </span>Namespaces</h2>
-
<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>
@@ -606,11 +576,11 @@
<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>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>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 [<cite><a class="bibref" href="#bib-TURTLE-TR">TURTLE-TR</a></cite>].</p>
</section>
@@ -720,10 +690,8 @@
</section>
-</section>
-
<section id="example" class="informative">
-<!--OddPage--><h2><span class="secno">6. </span>An example</h2><p><em>This section is non-normative.</em></p>
+<h3><span class="secno">5.3 </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
@@ -839,8 +807,11 @@
</section>
+</section>
+
+
<section id="dsd">
-<!--OddPage--><h2><span class="secno">7. </span>Creating data structure definitions</h2>
+<!--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
@@ -865,7 +836,7 @@
confident that the structure of the data has not changed.</p>
<section id="dsd-dimensions">
-<h3><span class="secno">7.1 </span>Dimensions, attributes and measures</h3>
+<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>
@@ -928,7 +899,7 @@
</section>
<section id="dsd-cog" class="informative">
-<h3><span class="secno">7.2 </span>Content oriented guidelines</h3><p><em>This section is non-normative.</em></p>
+<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
@@ -956,7 +927,7 @@
<section id="dsd-example" class="informative">
-<h3><span class="secno">7.3 </span>Example</h3><p><em>This section is non-normative.</em></p>
+<h3><span class="secno">6.3 </span>Example</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 of the population. There is a single
@@ -1011,7 +982,7 @@
<section id="dsd-dsd">
-<h3><span class="secno">7.4 </span>ComponentSpecifications and DataStructureDefinitions</h3>
+<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>
@@ -1037,13 +1008,13 @@
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,
- a so called <em><a href="#dfn-flattened" class="internalDFN">flattened</a></em> representation.
+ well call this 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 a
- non-flat structure, the <code><a href="#dfn-qb-componentattachment" class="internalDFN">qb:componentAttachment</a></code> property of the specification should
+ 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).</li>
</ul>
@@ -1051,7 +1022,7 @@
<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
- flattened representations are in general easier to query and combine.</p>
+ 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>
@@ -1077,7 +1048,7 @@
<section id="dsd-mm">
-<h3><span class="secno">7.5 </span>Handling multiple measures</h3>
+<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
@@ -1099,7 +1070,7 @@
<section id="dsd-mm-obs">
-<h4><span class="secno">7.5.1 </span>Multi-measure observations</h4>
+<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.
@@ -1138,7 +1109,7 @@
<section id="dsd-mm-dim">
-<h4><span class="secno">7.5.2 </span><dfn id="dfn-measure-dimension">Measure dimension</dfn></h4>
+<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>.
@@ -1201,7 +1172,7 @@
<section id="datasets">
-<!--OddPage--><h2><span class="secno">8. </span>Expressing data sets</h2>
+<!--OddPage--><h2><span class="secno">7. </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>
@@ -1227,12 +1198,12 @@
<dt>External 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 11</a>.</dd>
+ External metadata is described in <a href="#metadata">section 10</a>.</dd>
</dl>
<section id="dataset-basic">
-<h3><span class="secno">8.1 </span>Data sets and observations</h3>
+<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>
@@ -1284,7 +1255,7 @@
...</pre></div>
-<p>This <a href="#dfn-flattened" class="internalDFN">flattened</a> structure makes it easy to query and combine data sets
+<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
@@ -1335,7 +1306,7 @@
<section id="slices">
-<!--OddPage--><h2><span class="secno">9. </span>Slices</h2>
+<!--OddPage--><h2><span class="secno">8. </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
@@ -1418,7 +1389,7 @@
...</pre></div>
<p>Note that here we are still repeating the dimension values on the individual observations.
-This flattened representation means that a consuming application can still query
+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:
@@ -1479,10 +1450,10 @@
<section id="schemes">
-<!--OddPage--><h2><span class="secno">10. </span>Concept schemes and code lists</h2>
+<!--OddPage--><h2><span class="secno">9. </span>Concept schemes and code lists</h2>
<section id="schemes-intro">
-<h3><span class="secno">10.1 </span>Coded values for components properties</h3>
+<h3><span class="secno">9.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)
@@ -1558,7 +1529,7 @@
</section>
<section id="schemes-hierarchy">
-<h3><span class="secno">10.2 </span>Hierarchical code lists</h3>
+<h3><span class="secno">9.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
@@ -1574,7 +1545,7 @@
</section>
<section id="schemes-hierarchy-nonskos">
-<h3><span class="secno">10.3 </span>Non-SKOS hierarchies</h3>
+<h3><span class="secno">9.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>.
@@ -1646,7 +1617,7 @@
</section>
<section id="schemes-aggregation">
-<h3><span class="secno">10.4 </span>Aggregation</h3>
+<h3><span class="secno">9.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
@@ -1665,7 +1636,7 @@
<section id="metadata">
-<!--OddPage--><h2><span class="secno">11. </span>DataSet metadata</h2>
+<!--OddPage--><h2><span class="secno">10. </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>),
@@ -1675,7 +1646,7 @@
<section id="metadata-categorization">
-<h3><span class="secno">11.1 </span>Categorizing a data set</h3>
+<h3><span class="secno">10.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>.
@@ -1707,7 +1678,7 @@
<section id="metadata-publishers">
-<h3><span class="secno">11.2 </span>Describing publishers</h3>
+<h3><span class="secno">10.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.
@@ -1727,16 +1698,16 @@
</section>
<section id="normalize">
-<!--OddPage--><h2><span class="secno">12. </span>Abbreviation and normalization</h2>
+<!--OddPage--><h2><span class="secno">11. </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-flattened">flattened</dfn></em>. It is a convenient format for
+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 flattened representation
+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.
</p>
@@ -1758,25 +1729,24 @@
to the observations in which that property occurs.</p>
<section id="normalize-algorithm">
-<h3><span class="secno">12.1 </span>Normalization algorithm</h3>
+<h3><span class="secno">11.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 is has not received as much
+However as a new addition it has not received as much
scrutiny as other parts of the specification. If problems are uncovered
during the Last Call 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 to a flattened
- representation. We express this transformation using the SPARQL 1.1
+ 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 flattened form or any mix of these.</p>
+ all data in normalized form or any mix of these.</p>
<p>The normalization algorithm comprises two sets of SPARQL Update
@@ -1851,13 +1821,13 @@
<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 flattened down to the corresponding
+ of that component to be pushed down to the corresponding
observations.
</p>
<table class="bordered-table">
<thead>
- <tr><th>Phase 2: Flatten attachment levels</th></tr>
+ <tr><th>Phase 2: Push down attachment levels</th></tr>
</thead>
<tbody><tr><td>
<pre>PREFIX qb: <http://purl.org/linked-data/cube#>
@@ -1906,7 +1876,7 @@
</section>
<section id="wf">
-<!--OddPage--><h2><span class="secno">13. </span>Well-formed cubes</h2>
+<!--OddPage--><h2><span class="secno">12. </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
@@ -1929,7 +1899,7 @@
yields a <a>well-formed RDF Data Cube</a>.</p>
<section id="wf-rules">
-<h3><span class="secno">13.1 </span>Integrity constraints</h3>
+<h3><span class="secno">12.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
@@ -2440,11 +2410,11 @@
</section>
<section id="vocab-reference">
-<!--OddPage--><h2><span class="secno">14. </span>Vocabulary reference</h2>
+<!--OddPage--><h2><span class="secno">13. </span>Vocabulary reference</h2>
<section id="reference-datasets">
-<h3><span class="secno">14.1 </span>DataSets</h3>
+<h3><span class="secno">13.1 </span>DataSets</h3>
<p><em>See Section <a href="#datasets">Expressing data sets</a>.</em></p>
@@ -2463,7 +2433,7 @@
<section id="reference-observations">
-<h3><span class="secno">14.2 </span>Observations</h3>
+<h3><span class="secno">13.2 </span>Observations</h3>
<p><em>See Section <a href="#datasets">Expressing data sets</a>.</em></p>
<dl class="vocab_reference">
@@ -2501,7 +2471,7 @@
<section id="reference-slices">
-<h3><span class="secno">14.3 </span>Slices</h3>
+<h3><span class="secno">13.3 </span>Slices</h3>
<p><em>See Section <a href="#slices">Slices</a>.</em></p>
<dl class="vocab_reference">
@@ -2546,7 +2516,7 @@
<section id="reference-components">
-<h3><span class="secno">14.4 </span>Dimensions, Attributes, Measures</h3>
+<h3><span class="secno">13.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">
@@ -2596,7 +2566,7 @@
<section id="reference-component-properties">
-<h3><span class="secno">14.5 </span>Reusable general purpose component properties</h3>
+<h3><span class="secno">13.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">
@@ -2614,7 +2584,7 @@
<section id="reference-dsd">
-<h3><span class="secno">14.6 </span>Data Structure Definitions</h3>
+<h3><span class="secno">13.6 </span>Data Structure Definitions</h3>
<p><em>See Section <a href="#dsd-dsd">ComponentSpecifications and DataStructureDefinitions</a>.</em></p>
<dl class="vocab_reference">
@@ -2650,7 +2620,7 @@
<section id="reference-compspec">
-<h3><span class="secno">14.7 </span>Component specifications - for qualifying component use in a DSD</h3>
+<h3><span class="secno">13.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">
@@ -2756,7 +2726,7 @@
<section id="reference-slice-definitions">
-<h3><span class="secno">14.8 </span>Slice definitions</h3>
+<h3><span class="secno">13.8 </span>Slice definitions</h3>
<p><em>See Section <a href="#slices">Slices</a>.</em></p>
<dl class="vocab_reference">
@@ -2792,7 +2762,7 @@
<section id="reference-concepts">
-<h3><span class="secno">14.9 </span>Concepts</h3>
+<h3><span class="secno">13.9 </span>Concepts</h3>
<p><em>See Section <a href="#schemes">Concept schemes and code lists</a>.</em></p>
<dl class="vocab_reference">
@@ -2819,7 +2789,7 @@
</dl></section>
<section id="reference-nonskos-hierarchy">
-<h3><span class="secno">14.10 </span>Non-SKOS Hierarchies</h3>
+<h3><span class="secno">13.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">
@@ -2888,7 +2858,7 @@
<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 flattening algorithm
+ <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
@@ -2935,3 +2905,4 @@
</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>
+