| ... |
... |
@@ -1,19 +1,15 @@ |
| 1 |
|
-{{box title="**Contents**"}} |
| 2 |
|
-{{toc/}} |
| 3 |
|
-{{/box}} |
|
1 |
+=== 6.1 Context === |
| 4 |
4 |
|
| 5 |
|
-== 6.1 Context == |
|
3 |
+Some statistical systems create views of data based on a “cube” structure. In essence, a cube is an n-dimensional object where the value of each dimension can be derived from a hierarchical code list. The utility of such cube systems is that it is possible to “roll up” or “drill down” each of the hierarchy levels for each of the dimensions to specify the level of granularity required to give a “view” of the data – some dimensions may be rolled up, others may be drilled down. Such systems give a dynamic view of the data, with aggregated values for rolled up dimension positions. For example, the individual countries may be rolled up into an economic region such as the EU, or a geographical region such as Europe, whilst another dimension, such as “type of road” may be drilled down to its lower level. The resulting measure (such as “number of accidents”) would then be an aggregation of the value for each individual country for the specific type of road. |
| 6 |
6 |
|
| 7 |
|
-Some statistical systems create views of data based on a “cube” [[structure>>doc:IMElements.structure.WebHome]]. In essence, a cube is an n-dimensional object where the [[value>>doc:IMElements.value.WebHome]] of each dimension can be derived from a [[hierarchical code list>>doc:sdmx:Glossary 2\.1.Hierarchical code list.WebHome]]. The utility of such cube systems is that it is possible to “roll up” or “drill down” each of the [[hierarchy>>doc:sdmx:Glossary 2\.1.Hierarchy.WebHome]] levels for each of the [[dimensions>>doc:IMElements.dimensions.WebHome]] to specify the level of granularity required to give a “view” of the data – some [[dimensions>>doc:IMElements.dimensions.WebHome]] may be rolled up, others may be drilled down. Such systems give a dynamic view of the data, with aggregated values for rolled up dimension positions. For example, the individual countries may be rolled up into an economic region such as the EU, or a geographical region such as Europe, whilst another dimension, such as “[[type>>doc:IMElements.type.WebHome]] of road” may be drilled down to its lower level. The resulting measure (such as “number of accidents”) would then be an aggregation of the [[value>>doc:IMElements.value.WebHome]] for each individual country for the specific [[type>>doc:IMElements.type.WebHome]] of road. |
|
5 |
+Such cube systems rely, not on simple code lists, but on hierarchical code sets (see section 8). |
| 8 |
8 |
|
| 9 |
|
-Such cube systems rely, not on simple [[code lists>>doc:sdmx:Glossary 2\.1.Code list.WebHome]], but on [[hierarchical code>>doc:sdmx:Glossary 2\.1.Hierarchical code.WebHome]] sets (see section 8). |
|
7 |
+=== 6.2 Support for the Cube in the Information Model === |
| 10 |
10 |
|
| 11 |
|
-== 6.2 Support for the Cube in the Information Model == |
|
9 |
+Data reported using a Data Structure Definition structure (where each dimension value, if coded, is taken from a flat code list) can be described by a cube definition and can be processed by cube aware systems. The SDMX-IM supports the definition of such cubes in the following way: |
| 12 |
12 |
|
| 13 |
|
-Data reported using a [[Data Structure Definition>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]] [[structure>>doc:IMElements.structure.WebHome]] (where each dimension [[value>>doc:IMElements.value.WebHome]], if coded, is taken from a flat [[code list>>doc:sdmx:Glossary 2\.1.Code list.WebHome]]) can be described by a cube definition and can be processed by cube aware systems. The [[SDMX-IM>>doc:sdmx:Glossary 2\.1.SDMX Information Model.WebHome]] supports the definition of such cubes in the following way: |
| 14 |
|
- |
| 15 |
|
-* The [[Hierarchy>>doc:sdmx:Glossary 2\.1.Hierarchy.WebHome]] defines the (often complex) [[hierarchies>>doc:sdmx:Glossary 2\.1.Hierarchy.WebHome]] of codes. |
|
11 |
+* The Hierarchy defines the (often complex) hierarchies of codes. |
| 16 |
16 |
* If required: |
| 17 |
|
-** The StructureMap can group [[DataStructureDefinition>>doc:IMElements.AnnotableArtefact.IdentifiableArtefact.NameableArtefact.VersionableArtefact.MaintainableArtefact.Structure.DataStructureDefinition.WebHome]] that describe the cube |
|
13 |
+** The StructureMap can group DataStructureDefinition that describe the cube |
| 18 |
18 |
|
| 19 |
|
-The HierarchyAssociation can provide a mechanism to apply a [[Hierarchy>>doc:sdmx:Glossary 2\.1.Hierarchy.WebHome]] to the Codes in the [[Codelists>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] used by the [[DataStructureDefinition>>doc:IMElements.AnnotableArtefact.IdentifiableArtefact.NameableArtefact.VersionableArtefact.MaintainableArtefact.Structure.DataStructureDefinition.WebHome]], providing also the context of which the [[hierarchy>>doc:sdmx:Glossary 2\.1.Hierarchy.WebHome]] applies (e.g., a [[Dataflow>>doc:IMElements.AnnotableArtefact.IdentifiableArtefact.NameableArtefact.VersionableArtefact.MaintainableArtefact.StructureUsage.Dataflow.WebHome]]). |
|
15 |
+The HierarchyAssociation can provide a mechanism to apply a Hierarchy to the Codes in the Codelists used by the DataStructureDefinition, providing also the context of which the hierarchy applies (e.g., a Dataflow). |
