--- a/data-cube/static.html Thu Mar 07 16:21:15 2013 +0000
+++ b/data-cube/static.html Thu Mar 07 16:26:52 2013 +0000
@@ -1,18 +1,13 @@
-<?xml version='1.0' encoding='UTF-8'?>
-<!DOCTYPE html PUBLIC '-//W3C//DTD XHTML 1.0 Transitional//EN' 'http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd'>
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
+<!DOCTYPE html>
+<html lang="en">
<head>
<title>The RDF Data Cube Vocabulary</title>
- <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
-
<!-- <script type="text/javascript" src="respec-ref.js" class="remove"></script> -->
-
-
<!-- <script type="text/javascript" src="../respec/gld-config.js" class="remove"></script> -->
-
<style type="text/css">
@@ -215,14 +210,12 @@
}
-</style><link rel="stylesheet" href="http://www.w3.org/StyleSheets/TR/W3C-WD" />
-<!--[if lt IE 9]><script src='http://www.w3.org/2008/site/js/html5shiv.js'></script><![endif]-->
-</head>
+</style><link rel="stylesheet" href="https://www.w3.org/StyleSheets/TR/W3C-WD"><!--[if lt IE 9]><script src='https://www.w3.org/2008/site/js/html5shiv.js'></script><![endif]--></head>
<body><div class="head">
<p>
- <a href="http://www.w3.org/"><img width="72" height="48" src="http://www.w3.org/Icons/w3c_home" alt="W3C" /></a>
+ <a href="http://www.w3.org/"><img width="72" height="48" src="https://www.w3.org/Icons/w3c_home" alt="W3C"></a>
</p>
<h1 class="title" id="title">The RDF Data Cube Vocabulary</h1>
@@ -272,7 +265,7 @@
</p>
- <hr />
+ <hr>
</div>
<section id="abstract" class="introductory"><h2>Abstract</h2>
@@ -359,15 +352,11 @@
<section id="outline">
-
-<!--OddPage-->
-<h2><span class="secno">1. </span>Outline of the vocabulary</h2>
-
+<!--OddPage--><h2><span class="secno">1. </span>Outline of the vocabulary</h2>
<!-- <img src="images/qb-fig1.png" alt="UML-style block diagram of the terms in this vocabulary"/> -->
-
-<img src="images/qb-fig1-proposed.png" alt="UML-style block diagram of the terms in this vocabulary" />
+<img src="images/qb-fig1-proposed.png" alt="UML-style block diagram of the terms in this vocabulary">
<section id="index">
<h3><span class="secno">1.1 </span>Vocabulary index</h3>
@@ -418,9 +407,7 @@
</section>
<section id="introduction" class="informative">
-
-<!--OddPage-->
-<h2><span class="secno">2. </span>Introduction</h2><p><em>This section is non-normative.</em></p>
+<!--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>
@@ -455,7 +442,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>
@@ -573,7 +560,7 @@
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
+ <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>
@@ -614,9 +601,7 @@
</section>
<section id="namespaces">
-
-<!--OddPage-->
-<h2><span class="secno">3. </span>Namespaces</h2>
+<!--OddPage--><h2><span class="secno">3. </span>Namespaces</h2>
<p>The following namespaces are used in this document:</p>
@@ -642,9 +627,7 @@
</section>
-<section id="conformance">
-<!--OddPage-->
-<h2><span class="secno">4. </span>Conformance</h2>
+<section id="conformance"><!--OddPage--><h2><span class="secno">4. </span>Conformance</h2>
<p>
As well as sections marked as non-normative, all authoring guidelines, diagrams, examples,
and notes in this specification are non-normative. Everything else in this specification is
@@ -678,9 +661,7 @@
</section>
<section id="data-cubes" class="informative">
-
-<!--OddPage-->
-<h2><span class="secno">5. </span>Data cubes</h2><p><em>This section is non-normative.</em></p>
+<!--OddPage--><h2><span class="secno">5. </span>Data cubes</h2><p><em>This section is non-normative.</em></p>
<section id="cubes-model" class="informative">
@@ -754,109 +735,107 @@
</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>
+<!--OddPage--><h2><span class="secno">6. </span>An example</h2><p><em>This section is non-normative.</em></p>
<p>In order to illustrate the use of the data cube vocabulary we will
use a small demonstration
data set extracted from
<a href="http://statswales.wales.gov.uk/index.htm">StatsWales</a> report
number 003311 which describes life expectancy broken down by region
-(unitary authority), age and time. The extract we will use is:<br />
+(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">
<tbody>
<tr>
- <td style="vertical-align: top;"><br />
- </td>
- <td colspan="2" rowspan="1" style="vertical-align: top; text-align: center; font-weight: bold;">2004-2006<br />
- </td>
- <td colspan="2" rowspan="1" style="vertical-align: top; text-align: center; font-weight: bold;">2005-2007<br />
- </td>
- <td colspan="2" rowspan="1" style="vertical-align: top; text-align: center; font-weight: bold;">2006-2008<br />
+ <td style="vertical-align: top;"><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 colspan="2" rowspan="1" style="vertical-align: top; text-align: center; font-weight: bold;">2004-2006<br>
</td>
- <td style="vertical-align: top; text-align: center; font-weight: bold;">Female<br />
- </td>
- <td style="vertical-align: top; text-align: center; font-weight: bold;">Male<br />
+ <td colspan="2" rowspan="1" style="vertical-align: top; text-align: center; font-weight: bold;">2005-2007<br>
</td>
- <td style="vertical-align: top; text-align: center; font-weight: bold;">Female<br />
- </td>
- <td style="vertical-align: top; text-align: center; font-weight: bold;">Male<br />
- </td>
- <td style="vertical-align: top; text-align: center; font-weight: bold;">Female<br />
+ <td 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; text-align: right; font-weight: bold;">Newport<br />
- </td>
- <td style="vertical-align: top;">76.7<br />
- </td>
- <td style="vertical-align: top;">80.7<br />
+ <td style="vertical-align: top;"><br>
</td>
- <td style="vertical-align: top;">77.1<br />
+ <td style="vertical-align: top; text-align: center; font-weight: bold;">Male<br>
</td>
- <td style="vertical-align: top;">80.9<br />
+ <td style="vertical-align: top; text-align: center; font-weight: bold;">Female<br>
</td>
- <td style="vertical-align: top;">77.0<br />
+ <td style="vertical-align: top; text-align: center; font-weight: bold;">Male<br>
</td>
- <td style="vertical-align: top;">81.5<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;">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;">Cardiff<br />
- </td>
- <td style="vertical-align: top;">78.7<br />
- </td>
- <td style="vertical-align: top;">83.3<br />
+ <td style="vertical-align: top; text-align: right; font-weight: bold;">Newport<br>
</td>
- <td style="vertical-align: top;">78.6<br />
+ <td style="vertical-align: top;">76.7<br>
</td>
- <td style="vertical-align: top;">83.7<br />
+ <td style="vertical-align: top;">80.7<br>
</td>
- <td style="vertical-align: top;">78.7<br />
+ <td style="vertical-align: top;">77.1<br>
</td>
- <td style="vertical-align: top;">83.4<br />
+ <td style="vertical-align: top;">80.9<br>
+ </td>
+ <td style="vertical-align: top;">77.0<br>
+ </td>
+ <td style="vertical-align: top;">81.5<br>
</td>
</tr>
<tr>
- <td style="vertical-align: top; text-align: right; font-weight: bold;">Monmouthshire<br />
- </td>
- <td style="vertical-align: top;">76.6<br />
- </td>
- <td style="vertical-align: top;">81.3<br />
+ <td style="vertical-align: top; text-align: right; font-weight: bold;">Cardiff<br>
</td>
- <td style="vertical-align: top;">76.5<br />
+ <td style="vertical-align: top;">78.7<br>
</td>
- <td style="vertical-align: top;">81.5<br />
+ <td style="vertical-align: top;">83.3<br>
</td>
- <td style="vertical-align: top;">76.6<br />
+ <td style="vertical-align: top;">78.6<br>
</td>
- <td style="vertical-align: top;">81.7<br />
+ <td style="vertical-align: top;">83.7<br>
+ </td>
+ <td style="vertical-align: top;">78.7<br>
+ </td>
+ <td style="vertical-align: top;">83.4<br>
+ </td>
+ </tr>
+ <tr>
+ <td style="vertical-align: top; text-align: right; font-weight: bold;">Monmouthshire<br>
+ </td>
+ <td style="vertical-align: top;">76.6<br>
+ </td>
+ <td style="vertical-align: top;">81.3<br>
+ </td>
+ <td style="vertical-align: top;">76.5<br>
+ </td>
+ <td style="vertical-align: top;">81.5<br>
+ </td>
+ <td style="vertical-align: top;">76.6<br>
+ </td>
+ <td style="vertical-align: top;">81.7<br>
</td>
</tr>
<tr>
<td style="vertical-align: top; text-align: right; font-weight: bold;">Merthyr
-Tydfil<br />
- </td>
- <td style="vertical-align: top;">75.5<br />
- </td>
- <td style="vertical-align: top;">79.1<br />
+Tydfil<br>
</td>
- <td style="vertical-align: top;">75.5<br />
+ <td style="vertical-align: top;">75.5<br>
</td>
- <td style="vertical-align: top;">79.4<br />
+ <td style="vertical-align: top;">79.1<br>
</td>
- <td style="vertical-align: top;">74.9<br />
+ <td style="vertical-align: top;">75.5<br>
</td>
- <td style="vertical-align: top;">79.6<br />
+ <td style="vertical-align: top;">79.4<br>
+ </td>
+ <td style="vertical-align: top;">74.9<br>
+ </td>
+ <td style="vertical-align: top;">79.6<br>
</td>
</tr>
</tbody>
@@ -873,9 +852,7 @@
</section>
<section id="dsd">
-
-<!--OddPage-->
-<h2><span class="secno">7. </span>Creating data structure definitions</h2>
+<!--OddPage--><h2><span class="secno">7. </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
@@ -1004,7 +981,7 @@
time service and to declare this within the data structure definition.</p>
<div class="example"><div class="example-title"><span>Example 1</span></div><pre class="example">eg:refPeriod a rdf:Property, qb:DimensionProperty;
- rdfs:label "reference period"@en;
+ rdfs:label "reference period"@en;
rdfs:subPropertyOf sdmx-dimension:refPeriod;
rdfs:range interval:Interval;
qb:concept sdmx-concept:refPeriod . </pre></div>
@@ -1014,7 +991,7 @@
we can use the Ordnance Survey Administrative Geography Ontology [<cite><a class="bibref" href="#bib-OS-GEO">OS-GEO</a></cite>].</p>
<div class="example"><div class="example-title"><span>Example 2</span></div><pre class="example">eg:refArea a rdf:Property, qb:DimensionProperty;
- rdfs:label "reference area"@en;
+ rdfs:label "reference area"@en;
rdfs:subPropertyOf sdmx-dimension:refArea;
rdfs:range admingeo:UnitaryAuthority;
qb:concept sdmx-concept:refArea . </pre></div>
@@ -1028,7 +1005,7 @@
of the RDF data sets to use a specific measure corresponding to the phenomenon being observed.</p>
<div class="example"><div class="example-title"><span>Example 3</span></div><pre class="example">eg:lifeExpectancy a rdf:Property, qb:MeasureProperty;
- rdfs:label "life expectancy"@en;
+ rdfs:label "life expectancy"@en;
rdfs:subPropertyOf sdmx-measure:obsValue;
rdfs:range xsd:decimal . </pre></div>
@@ -1039,7 +1016,7 @@
which in turn corresponds to the COG concept of <code>UNIT_MEASURE</code>. To express
the value of this attribute we would typically us a common thesaurus of units of measure.
For the sake of this simple example we will use the DBpedia resource <code>http://dbpedia.org/resource/Year</code>
- which corresponds to the topic of the Wikipedia page on "Years".</p>
+ 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>
@@ -1099,7 +1076,7 @@
qb:component [qb:measure eg:lifeExpectancy];
# The attributes
qb:component [qb:attribute sdmx-attribute:unitMeasure;
- qb:componentRequired "true"^^xsd:boolean;
+ qb:componentRequired "true"^^xsd:boolean;
qb:componentAttachment qb:DataSet;] .</pre></div>
<p>Note that we have given the data structure definition (DSD) a URI since it will be
@@ -1114,7 +1091,7 @@
<section id="dsd-mm">
<h3><span class="secno">7.5 </span>Handling multiple measures</h3>
-<p>Our example data set is relatively simple in having a single observable (in this case "life expectancy")
+<p>Our example data set is relatively simple in having a single observable (in this case "life expectancy")
that is being measured. In other data sets there can be multiple measures. These measures
may be of similar nature (e.g. a data set on local government performance might provide
multiple different performance indicators for each region) or quite different (e.g. a data set
@@ -1125,7 +1102,7 @@
add an additional dimension whose value indicates the measure. This is appropriate for applications
where the measures are separate aggregate statistics. In other domains such as a clinical statistics
or sensor networks then the term <em>observation</em> usually denotes an observation event which can include multiple
- observed values. Similarly in Business Intelligence applications and OLAP, a single "cell" in the data cube will
+ observed values. Similarly in Business Intelligence applications and OLAP, a single "cell" in the data cube will
typically contain values for multiple measures.
</p>
@@ -1145,7 +1122,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>
<div class="example"><div class="example-title"><span>Example 5</span></div><pre class="example">eg:dsd1 a qb:DataStructureDefinition;
- rdfs:comment "shipments by time (multiple measures approach)"@en;
+ rdfs:comment "shipments by time (multiple measures approach)"@en;
qb:component
[ qb:dimension sdmx-dimension:refTime; ],
[ qb:measure eg-measure:quantity; ],
@@ -1157,7 +1134,7 @@
eg:obs1a a qb:Observation;
qb:dataSet eg:dataset1;
- sdmx-dimension:refTime "30-07-2010"^^xsd:date;
+ sdmx-dimension:refTime "30-07-2010"^^xsd:date;
eg-measure:weight 1.3 ;
eg-measure:quantity 42 ;
. </pre></div>
@@ -1194,7 +1171,7 @@
<p>The data structure definition for our above example, using this representation approach, would then be:</p>
<div class="example"><div class="example-title"><span>Example 7</span></div><pre class="example">eg:dsd2 a qb:DataStructureDefinition;
- rdfs:comment "shipments by time (measure dimension approach)"@en;
+ rdfs:comment "shipments by time (measure dimension approach)"@en;
qb:component
[ qb:dimension sdmx-dimension:refTime; ],
[ qb:measure eg-measure:quantity; ],
@@ -1207,13 +1184,13 @@
eg:obs2a a qb:Observation;
qb:dataSet eg:dataset2;
- sdmx-dimension:refTime "30-07-2010"^^xsd:date;
+ sdmx-dimension:refTime "30-07-2010"^^xsd:date;
qb:measureType eg-measure:weight ;
eg-measure:weight 1.3 .
eg:obs2b a qb:Observation;
qb:dataSet eg:dataset2;
- sdmx-dimension:refTime "30-07-2010"^^xsd:date;
+ sdmx-dimension:refTime "30-07-2010"^^xsd:date;
qb:measureType eg-measure:quantity ;
eg-measure:quantity 42 . </pre></div>
@@ -1224,7 +1201,7 @@
a uniform way of declaring and using measure properties on all kinds of datasets.</p><p>
</p><p>Those familiar with SDMX should also note that in the RDF representation there is
- no need for a separate "primary measure" which subsumes each of the individual
+ no need for a separate "primary measure" which subsumes each of the individual
measures, those individual measures are used directly. Extension vocabularies
could address the round-tripping of the SDMX primary measure by use of a
separate annotation on the data structure definition.
@@ -1236,9 +1213,7 @@
<section id="datasets">
-
-<!--OddPage-->
-<h2><span class="secno">8. </span>Expressing data sets</h2>
+<!--OddPage--><h2><span class="secno">8. </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>
@@ -1287,8 +1262,8 @@
<p>Thus for our running example we might expect to have:</p>
<div class="example"><div class="example-title"><span>Example 9</span></div><pre class="example">eg:dataset-le1 a qb:DataSet;
- rdfs:label "Life expectancy"@en;
- rdfs:comment "Life expectancy within Welsh Unitary authorities - extracted from Stats Wales"@en;
+ rdfs:label "Life expectancy"@en;
+ rdfs:comment "Life expectancy within Welsh Unitary authorities - extracted from Stats Wales"@en;
qb:structure eg:dsd-le ;
.
@@ -1330,8 +1305,8 @@
attached at the data set level. So an improved version of the example is:</p>
<div class="example"><div class="example-title"><span>Example 10</span></div><pre class="example">eg:dataset-le1 a qb:DataSet;
- rdfs:label "Life expectancy"@en;
- rdfs:comment "Life expectancy within Welsh Unitary authorities - extracted from Stats Wales"@en;
+ 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 <http://dbpedia.org/resource/Year> ;
.
@@ -1372,9 +1347,7 @@
<section id="slices">
-
-<!--OddPage-->
-<h2><span class="secno">9. </span>Slices</h2>
+<!--OddPage--><h2><span class="secno">9. </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
@@ -1389,17 +1362,17 @@
</ul>
<p>To illustrate the use of slices let us group the sample data set into geographic series.
- That will enable us to refer to e.g. "male life expectancy observations for 2004-2006"
+ That will enable us to refer to e.g. "male life expectancy observations for 2004-2006"
and guide applications to present a comparative chart across regions. </p>
-<p>We first define the structure of the slices we want by associating a "slice key" which the
+<p>We first define the structure of the slices we want by associating a "slice key" which the
data structure definition. This is done by creating a <code><a href="#dfn-qb-slicekey" class="internalDFN">qb:SliceKey</a></code> which
lists the component properties (which must be dimensions) which will be fixed in the
slice. The key is attached to the DSD using <code><a href="#dfn-qb-slicekey-1" class="internalDFN">qb:sliceKey</a></code>. For example: </p>
<div class="example"><div class="example-title"><span>Example 11</span></div><pre class="example">eg:sliceByRegion a qb:SliceKey;
- rdfs:label "slice by region"@en;
- rdfs:comment "Slice by grouping regions together, fixing sex and time values"@en;
+ rdfs:label "slice by region"@en;
+ rdfs:comment "Slice by grouping regions together, fixing sex and time values"@en;
qb:componentProperty eg:refPeriod, sdmx-dimension:sex .
eg:dsd-le-slice1 a qb:DataStructureDefinition;
@@ -1417,8 +1390,8 @@
the slices they contain by means of <code><a href="#dfn-qb-slice-1" class="internalDFN">qb:slice</a></code>. Thus in our example we would have:</p>
<div class="example"><div class="example-title"><span>Example 12</span></div><pre class="example">eg:dataset-le2 a qb:DataSet;
- rdfs:label "Life expectancy"@en;
- rdfs:comment "Life expectancy within Welsh Unitary authorities - extracted from Stats Wales"@en;
+ 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 <http://dbpedia.org/resource/Year> ;
qb:slice eg:slice2;
@@ -1472,8 +1445,8 @@
qb:sliceKey eg:sliceByRegion .
eg:dataset-le3 a qb:DataSet;
- rdfs:label "Life expectancy"@en;
- rdfs:comment "Life expectancy within Welsh Unitary authorities - extracted from Stats Wales"@en;
+ 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 <http://dbpedia.org/resource/Year> ;
qb:slice eg:slice3 ;
@@ -1518,9 +1491,7 @@
<section id="schemes">
-
-<!--OddPage-->
-<h2><span class="secno">10. </span>Concept schemes and code lists</h2>
+<!--OddPage--><h2><span class="secno">10. </span>Concept schemes and code lists</h2>
<section id="schemes-intro">
<h3><span class="secno">10.1 </span>Coded values for components properties</h3>
@@ -1544,10 +1515,10 @@
code list for gender, as used already in our worked example. The relevant subset of this code list is:</p>
<div class="example"><div class="example-title"><span>Example 14</span></div><pre class="example">sdmx-code:sex a skos:ConceptScheme;
- skos:prefLabel "Code list for Sex (SEX) - codelist scheme"@en;
- rdfs:label "Code list for Sex (SEX) - codelist scheme"@en;
- skos:notation "CL_SEX";
- skos:note "This code list provides the gender."@en;
+ skos: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 <http://sdmx.org/wp-content/uploads/2009/01/02_sdmx_cog_annex_2_cl_2009.pdf> ;
rdfs:seeAlso sdmx-code:Sex ;
sdmx-code:sex skos:hasTopConcept sdmx-code:sex-F ;
@@ -1555,20 +1526,20 @@
sdmx-code:Sex a rdfs:Class, owl:Class;
rdfs:subClassOf skos:Concept ;
- rdfs:label "Code list for Sex (SEX) - codelist class"@en;
- rdfs:comment "This code list provides the gender."@en;
+ rdfs:label "Code list for Sex (SEX) - codelist class"@en;
+ rdfs:comment "This code list provides the gender."@en;
rdfs:seeAlso sdmx-code:sex .
sdmx-code:sex-F a skos:Concept, sdmx-code:Sex;
skos:topConceptOf sdmx-code:sex;
- skos:prefLabel "Female"@en ;
- skos:notation "F" ;
+ skos:prefLabel "Female"@en ;
+ skos:notation "F" ;
skos:inScheme sdmx-code:sex .
sdmx-code:sex-M a skos:Concept, sdmx-code:Sex;
skos:topConceptOf sdmx-code:sex;
- skos:prefLabel "Male"@en ;
- skos:notation "M" ;
+ skos:prefLabel "Male"@en ;
+ skos:notation "M" ;
skos:inScheme sdmx-code:sex .</pre></div>
<p><code>skos:prefLabel</code> is used to give a name to the code,
@@ -1643,7 +1614,7 @@
<div class="example"><div class="example-title"><span>Example 16</span></div><pre class="example">PREFIX spatial: <http://data.ordnancesurvey.co.uk/ontology/spatialrelations/> .
eg:GBgeoHierarchy a qb:HierarchicalCodeList;
- rdfs:label "Geographic Hierarchy for Great Britain"@en;
+ rdfs:label "Geographic Hierarchy for Great Britain"@en;
qb:hierarchy Root
<http://data.ordnancesurvey.co.uk/id/7000000000041427>, # South West
<http://data.ordnancesurvey.co.uk/id/7000000000041426>, # West Midlands
@@ -1678,14 +1649,12 @@
of <code><a href="#dfn-qb-hierarchicalcodelist" class="internalDFN">qb:HierarchicalCodeList</a></code>, for example to
declare hierarchies in which each parent is a disjoint union of its children.</p>
-
<!--
<p>A sub class of <code><a>qb:HierarchicalCodeList</a></code>, <code><a>qb:AggregatableHierarchy</a></code>, is provided to declare
hierarchies where for each parent concept the set of child concepts form a disjoint cover (i.e. a
mutually-exclusive and exhaustive decomposition) of the parent.</p>
-->
-
</section>
<section id="schemes-aggregation">
@@ -1708,9 +1677,7 @@
<section id="metadata">
-
-<!--OddPage-->
-<h2><span class="secno">11. </span>DataSet metadata</h2>
+<!--OddPage--><h2><span class="secno">11. </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>),
@@ -1737,9 +1704,9 @@
<p>Thus our sample dataset might be marked up by:</p>
<div class="example"><div class="example-title"><span>Example 18</span></div><pre class="example">eg:dataset1 a qb:DataSet;
- rdfs:label "Life expectancy"@en;
- rdfs:comment "Life expectancy within Welsh Unitary authorities - extracted from Stats Wales"@en;
- dcterms:date "2010-08-11"^^xsd:date;
+ 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;
dcterms:subject
sdmx-subject:3.2 , # regional and small area statistics
sdmx-subject:1.4 , # Health
@@ -1763,7 +1730,7 @@
dc:publisher <http://example.com/meta#organization> .
<http://example.com/meta#organization> a org:Organization, foaf:Agent;
- rdfs:label "Example org" . </pre></div>
+ rdfs:label "Example org" . </pre></div>
<p>Extension vocabularies may provide additional metadata properties and may impose
constraints on what metadata must be provided.</p>
@@ -1772,9 +1739,7 @@
</section>
<section id="normalize">
-
-<!--OddPage-->
-<h2><span class="secno">12. </span>Abbreviation and normalization</h2>
+<!--OddPage--><h2><span class="secno">12. </span>Abbreviation and normalization</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
@@ -1953,9 +1918,7 @@
</section>
<section id="wf">
-
-<!--OddPage-->
-<h2><span class="secno">13. </span>Well-formed cubes</h2>
+<!--OddPage--><h2><span class="secno">13. </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
@@ -2107,7 +2070,7 @@
<tbody>
<tr><td><pre>ASK {
?dsd qb:component ?componentSpec .
- ?componentSpec qb:componentRequired "false"^^xsd:boolean ;
+ ?componentSpec qb:componentRequired "false"^^xsd:boolean ;
qb:componentProperty ?component .
FILTER NOT EXISTS { ?component a qb:AttributeProperty }
}
@@ -2235,7 +2198,7 @@
<tbody>
<tr><td><pre>ASK {
?obs qb:dataSet/qb:structure/qb:component ?component .
- ?component qb:componentRequired "true"^^xsd:boolean ;
+ ?component qb:componentRequired "true"^^xsd:boolean ;
qb:componentProperty ?attr .
FILTER NOT EXISTS { ?obs ?attr [] }
}
@@ -2489,9 +2452,7 @@
</section>
<section id="vocab-reference">
-
-<!--OddPage-->
-<h2><span class="secno">14. </span>Vocabulary reference</h2>
+<!--OddPage--><h2><span class="secno">14. </span>Vocabulary reference</h2>
<section id="reference-datasets">
@@ -2897,7 +2858,6 @@
</dt>
<dd>Specifies a property which relates a parent concept in the hierarchy to a child concept. Note that a child may have more than one parent.</dd>
-
<!--
<dt id="ref_qb_AggregatableHierarchy">
<em>Class:</em> <code><dfn>qb:AggregatableHierarchy</dfn></code>
@@ -2905,7 +2865,6 @@
<dd>Indicates a hierarchy in which each parent concept is a disjoint union of its child concepts. So that measures such as simple counts may be aggregated up the hierarchy.</dd>
-->
-
</dl>
</section>
@@ -2913,9 +2872,7 @@
<section id="acknowledgements" class="appendix">
-
-<!--OddPage-->
-<h2><span class="secno">A. </span>Acknowledgements</h2>
+<!--OddPage--><h2><span class="secno">A. </span>Acknowledgements</h2>
<p>This work is based on a collaboration that was initiated in a
workshop on Publishing statistical datasets in SDMX and the semantic
@@ -2937,9 +2894,7 @@
</section>
<section id="acknowledgements" class="appendix">
-
-<!--OddPage-->
-<h2><span class="secno">B. </span>Change history </h2>
+<!--OddPage--><h2><span class="secno">B. </span>Change history </h2>
Changes since <a href="http://www.w3.org/TR/2012/WD-vocab-data-cube-20120405/"><abbr title="World Wide Web Consortium">W3C</abbr> Working Draft 5 April 2012</a>:
@@ -2970,9 +2925,7 @@
-<section id="references" class="appendix">
-<!--OddPage-->
-<h2><span class="secno">C. </span>References</h2><section id="normative-references"><h3><span class="secno">C.1 </span>Normative references</h3><dl class="bibliography"><dt id="bib-OWL2-PRIMER">[OWL2-PRIMER]</dt><dd>Pascal Hitzler; Markus Krötzsch; Bijan Parsia; Peter F. Patel-Schneider; Sebastian Rudolph. <a href="http://www.w3.org/TR/2009/REC-owl2-primer-20091027/"><cite>OWL 2 Web Ontology Language:Primer.</cite></a> 27 October 2009. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2009/REC-owl2-primer-20091027/">http://www.w3.org/TR/2009/REC-owl2-primer-20091027/</a>
+<section id="references" class="appendix"><!--OddPage--><h2><span class="secno">C. </span>References</h2><section id="normative-references"><h3><span class="secno">C.1 </span>Normative references</h3><dl class="bibliography"><dt id="bib-OWL2-PRIMER">[OWL2-PRIMER]</dt><dd>Pascal Hitzler; Markus Krötzsch; Bijan Parsia; Peter F. Patel-Schneider; Sebastian Rudolph. <a href="http://www.w3.org/TR/2009/REC-owl2-primer-20091027/"><cite>OWL 2 Web Ontology Language:Primer.</cite></a> 27 October 2009. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2009/REC-owl2-primer-20091027/">http://www.w3.org/TR/2009/REC-owl2-primer-20091027/</a>
</dd><dt id="bib-RDF-CONCEPTS">[RDF-CONCEPTS]</dt><dd>Graham Klyne; Jeremy J. Carroll. <a href="http://www.w3.org/TR/2004/REC-rdf-concepts-20040210"><cite>Resource Description Framework (RDF): Concepts and Abstract Syntax.</cite></a> 10 February 2004. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2004/REC-rdf-concepts-20040210">http://www.w3.org/TR/2004/REC-rdf-concepts-20040210</a>
</dd><dt id="bib-RDF-MT">[RDF-MT]</dt><dd>Patrick Hayes. <a href="http://www.w3.org/TR/2004/REC-rdf-mt-20040210"><cite>RDF Semantics.</cite></a> 10 February 2004. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2004/REC-rdf-mt-20040210">http://www.w3.org/TR/2004/REC-rdf-mt-20040210</a>
</dd><dt id="bib-RDF-PRIMER">[RDF-PRIMER]</dt><dd>Frank Manola; Eric Miller. <a href="http://www.w3.org/TR/2004/REC-rdf-primer-20040210/"><cite>RDF Primer.</cite></a> 10 February 2004. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2004/REC-rdf-primer-20040210/">http://www.w3.org/TR/2004/REC-rdf-primer-20040210/</a>
@@ -2989,7 +2942,7 @@
</dd><dt id="bib-OLAP">[OLAP]</dt><dd>Online Analytical Processing Data Cubes, <a href="http://en.wikipedia.org/wiki/OLAP_cube">http://en.wikipedia.org/wiki/OLAP_cube</a>
</dd><dt id="bib-ORG">[ORG]</dt><dd>An Organization Ontology, <a href="http://www.epimorphics.com/public/vocabulary/org.html">http://www.epimorphics.com/public/vocabulary/org.html</a>
</dd><dt id="bib-OS-GEO">[OS-GEO]</dt><dd>Ordnance Survey Administrative Geography Ontology, <a href="http://data.ordnancesurvey.co.uk/ontology/admingeo/">http://data.ordnancesurvey.co.uk/ontology/admingeo/</a>
-</dd><dt id="bib-SCOVO">[SCOVO]</dt><dd>The Statistical Core Vocabulary, <a href="http://sw.joanneum.at/scovo/schema.html">http://sw.joanneum.at/scovo/schema.html</a><br />SCOVO: Using Statistics on the Web of data, <a href="http://sw-app.org/pub/eswc09-inuse-scovo.pdf">http://sw-app.org/pub/eswc09-inuse-scovo.pdf</a>
+</dd><dt id="bib-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-SDMX20">[SDMX20]</dt><dd>SDMX Information Model: UML Conceptual Design (Version 2.0), November 2005, Statistical Data and Metadata Exchange Initiative. URL: <a href="http://sdmx.org/docs/2_0/SDMX_2_0%20SECTION_02_InformationModel.pdf">http://sdmx.org/docs/2_0/SDMX_2_0%20SECTION_02_InformationModel.pdf</a>
</dd><dt id="bib-SKOS-PRIMER">[SKOS-PRIMER]</dt><dd>Antoine Isaac; Ed Summers. <a href="http://www.w3.org/TR/2009/NOTE-skos-primer-20090818/"><cite>SKOS Simple Knowledge Organization System Primer.</cite></a> 18 August 2009. W3C Note. URL: <a href="http://www.w3.org/TR/2009/NOTE-skos-primer-20090818/">http://www.w3.org/TR/2009/NOTE-skos-primer-20090818/</a>
</dd><dt id="bib-VOID">[VOID]</dt><dd>Keith Alexander; Richard Cyganiak; Michael Hausenblas; Jun Zhao. <a href="http://www.w3.org/TR/void/"><cite>Describing Linked Datasets with the VoID Vocabulary</cite></a> 03 March 2011. Interest Group Note. URL: <a href="http://www.w3.org/TR/void/">http://www.w3.org/TR/void/</a>