| ... |
... |
@@ -1,4 +1,6 @@ |
| 1 |
|
-= {{id name="_Toc371020"/}}6 Cube = |
|
1 |
+{{box title="**Contents**"}} |
|
2 |
+{{toc/}} |
|
3 |
+{{/box}} |
| 2 |
2 |
|
| 3 |
3 |
== {{id name="_Toc371021"/}}6.1 Context == |
| 4 |
4 |
|
| ... |
... |
@@ -11,6 +11,6 @@ |
| 11 |
11 |
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 |
13 |
* The HierachicalCodelist defines the (often complex) hierarchies of codes |
| 14 |
|
-* If required, the StructureSet can o group DataStructureDefinition that describe the cube |
| 15 |
|
- |
| 16 |
|
-o provide a mapping mechanism between the codes in the flat code lists used by the DataStructureDefinition and a HierarchicalCodelist where the HierarchicalCodelist uses code lists that are not used in the DataStructureDefinition |
|
16 |
+* If required, the StructureSet can |
|
17 |
+** group DataStructureDefinition that describe the cube |
|
18 |
+** provide a mapping mechanism between the codes in the flat code lists used by the DataStructureDefinition and a HierarchicalCodelist where the HierarchicalCodelist uses code lists that are not used in the DataStructureDefinition |
