Skip to Content

Changes for page Part VI. Samples

Last modified by Elena on 2025/09/10 11:19
From version 12.1
edited by Helena
on 2025/07/14 14:01
Change comment: There is no comment for this version
To version 5.4
edited by Helena
on 2025/07/03 11:29
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Part VI. Samples
1 +Part VI. Samples: This provides a brief explanation of the currently available sample files
Tags
... ... @@ -1,1 +1,0 @@
1 -Age|Attribute|Code|Code list|Component|Concept scheme|Currency|Data set|Data structure definition|Dataflow|Dimension|Measure|Representation|SDMX-ML|Statistical data and metadata exchange|Structural metadata|Title|Validation and transformation language
Content
... ... @@ -4,17 +4,17 @@
4 4  
5 5  = 1 Introduction =
6 6  
7 -This document provides a brief overview of the [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] XML sample files.
7 +This document provides a brief overview of the SDMX-ML XML sample files.
8 8  
9 -All samples use the xsi:schemaLocation [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] to define the location of the XSD schema files for the relevant namespaces. The samples assume that the schemas are held locally in a directory called 'schemas' and are referenced as a relative file path. For example:
9 +All samples use the xsi:schemaLocation attribute to define the location of the XSD schema files for the relevant namespaces. The samples assume that the schemas are held locally in a directory called 'schemas' and are referenced as a relative file path. For example:
10 10  
11 -`xsi:schemaLocation="http:~/~/www.sdmx.org/resources/sdmxml/schemas/v3_1/message ../../schemas/SDMXMessage.xsd"`
11 +`xsi:schemaLocation="http://www.sdmx.org/resources/sdmxml/schemas/v3_1/message ../../schemas/SDMXMessage.xsd"`
12 12  
13 -Copies of the [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] XSD schemas files will need to be in the appropriate directory in order to validate correctly.
13 +Copies of the SDMX-ML XSD schemas files will need to be in the appropriate directory in order to validate correctly.
14 14  
15 15  = 2 Structure Samples =
16 16  
17 -The Structure Samples provide examples of [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] messages within the //structure// namespace which is used for all [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] artefacts.
17 +The Structure Samples provide examples of SDMX-ML messages within the *structure* namespace which is used for all structural metadata artefacts.
18 18  
19 19  == Codelist ==
20 20  
... ... @@ -21,43 +21,43 @@
21 21  (% class="wikigeneratedid" id="Hcodelist.xml" %)
22 22  **codelist.xml**
23 23  
24 -A simple enumerated [[code list>>doc:sdmx:Glossary.Code list.WebHome]] directly equivalent to those in (% style="color:#e74c3c" %)version(%%) 2.1 and earlier.
24 +A simple enumerated code list directly equivalent to those in version 2.1 and earlier.
25 25  
26 -This example shows the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]:CL_AGE '[[Age>>doc:sdmx:Glossary.Age.WebHome]]' cross domain [[code list>>doc:sdmx:Glossary.Code list.WebHome]].
26 +This example shows the SDMX:CL_AGE 'Age' cross domain code list.
27 27  
28 28  (% class="wikigeneratedid" id="Hcodelist-extended.xml" %)
29 29  **codelist - extended.xml**
30 30  
31 -Extended [[code list>>doc:sdmx:Glossary.Code list.WebHome]].
31 +Extended code list.
32 32  
33 -Illustration of the feature introduced in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] 3.0 allowing [[code lists>>doc:sdmx:Glossary.Code list.WebHome]] to be defined as an extension of others. One use case envisaged is adding additional [[codes>>doc:sdmx:Glossary.Code.WebHome]] to standard cross domain [[code lists>>doc:sdmx:Glossary.Code list.WebHome]] without needing to take and maintain an explicit copy.
33 +Illustration of the feature introduced in SDMX 3.0 allowing code lists to be defined as an extension of others. One use case envisaged is adding additional codes to standard cross domain code lists without needing to take and maintain an explicit copy.
34 34  
35 -The sample message has two [[codelists>>doc:sdmx:Glossary.Code list.WebHome]]:
35 +The sample message has two codelists:
36 36  
37 -* [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]:CL_AGE, a simple enumerated [[codelist>>doc:sdmx:Glossary.Code list.WebHome]]; and
38 -* EXAMPLE:CL_EXTENDED_AGE, an extension of [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]:CL_AGE.
37 +* SDMX:CL_AGE, a simple enumerated codelist; and
38 +* EXAMPLE:CL_EXTENDED_AGE, an extension of SDMX:CL_AGE.
39 39  
40 -CL_EXTENDED_AGE defines two additional [[codes>>doc:sdmx:Glossary.Code.WebHome]] "I" and "S".
40 +CL_EXTENDED_AGE defines two additional codes "I" and "S".
41 41  
42 -In addition, the ExclusiveCodeSelection option to exclude the "Y" [[code>>doc:sdmx:Glossary.Code.WebHome]] from the CL_AGE [[code list>>doc:sdmx:Glossary.Code list.WebHome]]. The result is CL_AGE, minus "Y", plus "I" and "S". The InclusiveCodeSelection option could have been used if a specific set of [[codes>>doc:sdmx:Glossary.Code.WebHome]] were needed from CL_AGE.
42 +In addition, the ExclusiveCodeSelection option to exclude the "Y" code from the CL_AGE code list. The result is CL_AGE, minus "Y", plus "I" and "S". The InclusiveCodeSelection option could have been used if a specific set of codes were needed from CL_AGE.
43 43  
44 44  (% class="wikigeneratedid" id="Hcodelist-discriminatedunion.xml" %)
45 45  **codelist - discriminated union.xml**
46 46  
47 -Discriminated union of [[code lists>>doc:sdmx:Glossary.Code list.WebHome]].
47 +Discriminated union of code lists.
48 48  
49 -This sample illustrates the discriminated union of [[code lists>>doc:sdmx:Glossary.Code list.WebHome]] use case where a classification or breakdown has multiple "variants" which are all valid or mutually exclusive.
49 +This sample illustrates the discriminated union of code lists use case where a classification or breakdown has multiple "variants" which are all valid or mutually exclusive.
50 50  
51 51  Economic activity has been used with ISIC4 and NACE2 examples of two mutually exclusive variants.
52 52  
53 53  In the sample:
54 54  
55 -* [[Code list>>doc:sdmx:Glossary.Code list.WebHome]] extension is used to create a new EXAMPLE:CL_ACTIVITY [[code list>>doc:sdmx:Glossary.Code list.WebHome]] consisting of both the SDMX:CL_ACTIVITY_NACE2 and SDMX:CL_ACTIVITY_ISIC4 [[codelists>>doc:sdmx:Glossary.Code list.WebHome]].
56 -* The [[code list>>doc:sdmx:Glossary.Code list.WebHome]] extension prefix feature has been used to prefix the NACE [[codes>>doc:sdmx:Glossary.Code.WebHome]] with "NACE2_", and similarly the ISIC [[codes>>doc:sdmx:Glossary.Code.WebHome]] with "ISIC4_". This ensures there is no ambiguity where the same [[code>>doc:sdmx:Glossary.Code.WebHome]] appear in both NACE and ISIC [[code lists>>doc:sdmx:Glossary.Code list.WebHome]].
57 -* A [[data structure definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] has been created with an enumerated ACTIVITY [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] using the EXAMPLE:CL_ACTIVITY [[code list>>doc:sdmx:Glossary.Code list.WebHome]].
58 -* Two [[data flows>>doc:sdmx:Glossary.Dataflow.WebHome]] are created referencing the [[data structure definition>>doc:sdmx:Glossary.Data structure definition.WebHome]]. One [[data flow>>doc:sdmx:Glossary.Dataflow.WebHome]] has a data (% style="color:#e74c3c" %)constraint(%%) attached with a CubeRegion for ACTIVITY and Value = "NACE2_%". The other has a similar data (% style="color:#e74c3c" %)constraint(%%) with Value = "ISIC4_%". The "%" is the wildcard character for (% style="color:#e74c3c" %)constraints(%%) introduced in (% style="color:#e74c3c" %)version(%%) 3.0.
55 +* Code list extension is used to create a new EXAMPLE:CL_ACTIVITY code list consisting of both the SDMX:CL_ACTIVITY_NACE2 and SDMX:CL_ACTIVITY_ISIC4 codelists.
56 +* The code list extension prefix feature has been used to prefix the NACE codes with "NACE2_", and similarly the ISIC codes with "ISIC4_". This ensures there is no ambiguity where the same code appear in both NACE and ISIC code lists.
57 +* A data structure definition has been created with an enumerated ACTIVITY dimension using the EXAMPLE:CL_ACTIVITY code list.
58 +* Two data flows are created referencing the data structure definition. One data flow has a data constraint attached with a CubeRegion for ACTIVITY and Value = "NACE2_%". The other has a similar data constraint with Value = "ISIC4_%". The "%" is the wildcard character for constraints introduced in version 3.0.
59 59  
60 -The discriminated unions are achieved by requesting either of the [[data flows>>doc:sdmx:Glossary.Dataflow.WebHome]] with references="all" and detail="referencepartial". The result being CL_ACTIVITY with the extensions resolved and the relevant data (% style="color:#e74c3c" %)constraint(%%) applied. Thus CL_ACTIVITY will only contain [[codes>>doc:sdmx:Glossary.Code.WebHome]] prefixed according to the [[data flow>>doc:sdmx:Glossary.Dataflow.WebHome]]: either beginning "NACE2_" or "ISIC4_"
60 +The discriminated unions are achieved by requesting either of the data flows with references="all" and detail="referencepartial". The result being CL_ACTIVITY with the extensions resolved and the relevant data constraint applied. Thus CL_ACTIVITY will only contain codes prefixed according to the data flow: either beginning "NACE2_" or "ISIC4_"
61 61  
62 62  (% class="wikigeneratedid" id="Hvaluelist.xml" %)
63 63  **valuelist.xml**
... ... @@ -64,11 +64,11 @@
64 64  
65 65  A simple enumerated value list.
66 66  
67 -Value lists were introduced in (% style="color:#e74c3c" %)version(%%) 3.0 to allow the definition of enumerations where the [[codes>>doc:sdmx:Glossary.Code.WebHome]] do not need to comply with the strict [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] rules for identifiers. Thus a "value" can be any string of characters.
67 +Value lists were introduced in version 3.0 to allow the definition of enumerations where the codes do not need to comply with the strict SDMX rules for identifiers. Thus a "value" can be any string of characters.
68 68  
69 -In [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] valuelists are treated as a class of enumeration so appear in the structure message under [[Codelists>>doc:sdmx:Glossary.Code list.WebHome]] alongside simple and extended [[codelists>>doc:sdmx:Glossary.Code list.WebHome]], and specialised geospatial [[codelist>>doc:sdmx:Glossary.Code list.WebHome]] variants.
69 +In SDMX-ML valuelists are treated as a class of enumeration so appear in the structure message under Codelists alongside simple and extended codelists, and specialised geospatial codelist variants.
70 70  
71 -[[Currency>>doc:sdmx:Glossary.Currency.WebHome]] is used as the example with the values being [[currency>>doc:sdmx:Glossary.Currency.WebHome]] symbols including "$", "£", "¥" and "﷼".
71 +Currency is used as the example with the values being currency symbols including "$", "£", "¥" and "﷼".
72 72  
73 73  == Concept Scheme ==
74 74  
... ... @@ -75,136 +75,136 @@
75 75  (% class="wikigeneratedid" id="Hconceptscheme.xml" %)
76 76  **conceptscheme.xml**
77 77  
78 -The example illustrates a single [[concept scheme>>doc:sdmx:Glossary.Concept scheme.WebHome]] ECB:ECB_CONCEPTS containing multiple individual (% style="color:#e74c3c" %)concepts(%%).
78 +The example illustrates a single concept scheme ECB:ECB_CONCEPTS containing multiple individual concepts.
79 79  
80 -== Data Structure Definition ==
80 +## Data Structure Definition##
81 81  
82 -**ECB EXR.xml**
82 +**##ECB EXR.xml##**
83 83  
84 -The example illustrates a [[data structure definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] ([[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]]) for ECB:EXR exchange rates. The (% style="color:#e74c3c" %)concept(%%) of primary [[measure>>doc:sdmx:Glossary.Measure.WebHome]] has been deprecated in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] 3.0 and the [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]]'s MeasureList can contain multiple [[measures>>doc:sdmx:Glossary.Measure.WebHome]]. In this case, a single [[measure>>doc:sdmx:Glossary.Measure.WebHome]] OBS_VALUE is defined.
84 +The example illustrates a data structure definition (DSD) for ECB:EXR exchange rates. The concept of primary measure has been deprecated in SDMX 3.0 and the DSD's MeasureList can contain multiple measures. In this case, a single measure OBS_VALUE is defined.
85 85  
86 -== Dataflow ==
86 +## Dataflow##
87 87  
88 -**dataflow.xml**
88 +##**dataflow.xml**##
89 89  
90 -A simple [[data flow>>doc:sdmx:Glossary.Dataflow.WebHome]] for the ECB:EXR [[data set>>doc:sdmx:Glossary.Data set.WebHome]].
90 +A simple data flow for the ECB:EXR data set.
91 91  
92 -== Geospatial ==
92 +## Geospatial##
93 93  
94 -**geospatial geocomponents.xml**
94 +**##geospatial geocomponents.xml##**
95 95  
96 -An example of the use of the "GeospatialInformation" [[representation>>doc:sdmx:Glossary.Representation.WebHome]] type. The GeospatialInformation type can be assigned to a [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]], DataAttribute, MetadataAttribute or a [[Measure>>doc:sdmx:Glossary.Measure.WebHome]] in conjunction with the "GEO" role. Values of are included directly in data messages or metadata reports and must conform to the Geo Feature Set syntax defined in Section 6 of the Technical Specifications.
96 +An example of the use of the "GeospatialInformation" representation type. The GeospatialInformation type can be assigned to a Dimension, DataAttribute, MetadataAttribute or a Measure in conjunction with the "GEO" role. Values of are included directly in data messages or metadata reports and must conform to the Geo Feature Set syntax defined in Section 6 of the Technical Specifications.
97 97  
98 98  In the sample:
99 99  
100 -* A simple illustrative [[data structure definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] has been defined with IDENTIFIER and TIME_PERIOD [[dimensions>>doc:sdmx:Glossary.Dimension.WebHome]], plus a series [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] AREA.
101 -* The AREA [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] has the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] (% style="color:#e74c3c" %)Concept(%%) Role "GEO" defined identifying it generally as a geospatial [[component>>doc:sdmx:Glossary.Component.WebHome]] following guidelines.
102 -* The AREA [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] also carries a LocalRepresentation with textType="GeospatialInformation".
100 +* A simple illustrative data structure definition has been defined with IDENTIFIER and TIME_PERIOD dimensions, plus a series attribute AREA.
101 +* The AREA attribute has the SDMX Concept Role "GEO" defined identifying it generally as a geospatial component following guidelines.
102 +* The AREA attribute also carries a LocalRepresentation with textType="GeospatialInformation".
103 103  
104 -**geospatial geographiccodelist.xml**
104 +**##geospatial geographiccodelist.xml##**
105 105  
106 -An example of the definition of GeographicCodelists, a specialised form of [[code list>>doc:sdmx:Glossary.Code list.WebHome]] introduced in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] 3.0. GeographicCodelists are used in the same was as simple [[code lists>>doc:sdmx:Glossary.Code list.WebHome]] to assign a closed enumerated list of values to a [[component>>doc:sdmx:Glossary.Component.WebHome]]. The difference being that the definition of each GeoFeatureSetCode explicitly specifies the geospatial features to which it relates as a string expression using the Geo Feature Set syntax set out in Section 6 of the Technical Specifications. As with any other coded [[component>>doc:sdmx:Glossary.Component.WebHome]], [[data sets>>doc:sdmx:Glossary.Data set.WebHome]] only contain the [[codes>>doc:sdmx:Glossary.Code.WebHome]] and not the Feature Set information itself. Thus, GeoFeatureSetCodes act as pointers to the Geo Feature Set information held in the GeographicCodelist.
106 +An example of the definition of GeographicCodelists, a specialised form of code list introduced in SDMX 3.0. GeographicCodelists are used in the same was as simple code lists to assign a closed enumerated list of values to a component. The difference being that the definition of each GeoFeatureSetCode explicitly specifies the geospatial features to which it relates as a string expression using the Geo Feature Set syntax set out in Section 6 of the Technical Specifications. As with any other coded component, data sets only contain the codes and not the Feature Set information itself. Thus, GeoFeatureSetCodes act as pointers to the Geo Feature Set information held in the GeographicCodelist.
107 107  
108 108  In the sample:
109 109  
110 -* A single illustrative GeographicCodelist has been defined which must be under [[Codelists>>doc:sdmx:Glossary.Code list.WebHome]] in the structure message.
111 -* The GeographicCodelist geoType [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] must be given the value of "GeographicCodelist".
110 +* A single illustrative GeographicCodelist has been defined which must be under Codelists in the structure message.
111 +* The GeographicCodelist geoType attribute must be given the value of "GeographicCodelist".
112 112  * Three illustrative GeoFeatureSetCodes have been defined with IDs "A1", "A2" and "A3".
113 -* The GeoFeatureSetCode Value [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] specifies the geospatial features to which the [[code>>doc:sdmx:Glossary.Code.WebHome]] relates as a string expression. Note that the values shown are conceptual examples and are not syntactically valid Geo Feature Set expressions.
113 +* The GeoFeatureSetCode Value attribute specifies the geospatial features to which the code relates as a string expression. Note that the values shown are conceptual examples and are not syntactically valid Geo Feature Set expressions.
114 114  
115 -**geospatial geogridcodelist.xml**
115 +**##geospatial geogridcodelist.xml##**
116 116  
117 -An example of the definition of GeoGridCodelists, the second specialised form of [[codelist>>doc:sdmx:Glossary.Code list.WebHome]] for modelling gridded geographies.
118 -Like GeographicCodelists, GeoGridCodelists act in the same way as simple [[code lists>>doc:sdmx:Glossary.Code list.WebHome]] to assign a closed enumerated list of values to a [[component>>doc:sdmx:Glossary.Component.WebHome]].
119 -GeoGridCodelists define a geographical grid by setting the X and Y coordinates of a reference point, and the [[dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] of each cell. In addition, each GeoGridCode specifies to which cell in the grid it relates using row and column numbers.
117 +An example of the definition of GeoGridCodelists, the second specialised form of codelist for modelling gridded geographies.
118 +Like GeographicCodelists, GeoGridCodelists act in the same way as simple code lists to assign a closed enumerated list of values to a component.
119 +GeoGridCodelists define a geographical grid by setting the X and Y coordinates of a reference point, and the dimensions of each cell. In addition, each GeoGridCode specifies to which cell in the grid it relates using row and column numbers.
120 120  
121 121  In the sample:
122 122  
123 -* A single illustrative GeoGridCodelist has been defined which must be under [[Codelists>>doc:sdmx:Glossary.Code list.WebHome]] in the structure message.
124 -* The GridDefinition element defines the grid for the [[code list>>doc:sdmx:Glossary.Code list.WebHome]] using a string expression conforming to the Geo Grid syntax set out in Section 6 of the Technical Specifications.
125 -* Each GeoGridCode has an ID and a Name in common with the [[codes>>doc:sdmx:Glossary.Code.WebHome]] of simple [[code lists>>doc:sdmx:Glossary.Code list.WebHome]], but also has a GeoCell element containing the row and column of the grid cell as a string expression using the Grid Cell syntax set out in Section 6 of the Technical Specifications.
123 +* A single illustrative GeoGridCodelist has been defined which must be under Codelists in the structure message.
124 +* The GridDefinition element defines the grid for the code list using a string expression conforming to the Geo Grid syntax set out in Section 6 of the Technical Specifications.
125 +* Each GeoGridCode has an ID and a Name in common with the codes of simple code lists, but also has a GeoCell element containing the row and column of the grid cell as a string expression using the Grid Cell syntax set out in Section 6 of the Technical Specifications.
126 126  
127 -== VTL Transformations ==
127 +## VTL Transformations##
128 128  
129 -**VTL Sample 1.xml**
129 +##**VTL Sample 1.xml**##
130 130  
131 -Illustrates the use of [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] Rulesets to validate an [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]]. The validation process adds additional identifiers and [[measures>>doc:sdmx:Glossary.Measure.WebHome]] to the resulting [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[dataset>>doc:sdmx:Glossary.Data set.WebHome]] indicating, on a row by row basis the validation rule applied and the outcome in terms of a valid / invalid. If invalid, details of the error found and its severity are added.
131 +Illustrates the use of VTL Rulesets to validate an SDMX dataflow. The validation process adds additional identifiers and measures to the resulting VTL dataset indicating, on a row by row basis the validation rule applied and the outcome in terms of a valid / invalid. If invalid, details of the error found and its severity are added.
132 132  
133 -A second transformation takes the resulting [[dataset>>doc:sdmx:Glossary.Data set.WebHome]] filtering out high-severity validation errors and persists the result back to a [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] using [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] mappings.
133 +A second transformation takes the resulting dataset filtering out high-severity validation errors and persists the result back to a SDMX dataflow using VTL mappings.
134 134  
135 -**VTL Sample 2.xml**
135 +##**VTL Sample 2.xml**##
136 136  
137 -Illustrates aggregation of an [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] using [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] hierarchical rulesets, filtering and user defined operators.
137 +Illustrates aggregation of an SDMX dataflow using VTL hierarchical rulesets, filtering and user defined operators.
138 138  
139 -After the initial aggregation, unaggregated observations removed are removed from the result [[dataset>>doc:sdmx:Glossary.Data set.WebHome]]. A user defined operator is subsequently applied to calculate a percentage [[measure>>doc:sdmx:Glossary.Measure.WebHome]] with the final persistent result (% style="color:#e74c3c" %)mapped(%%) from [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] to a [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]].
139 +After the initial aggregation, unaggregated observations removed are removed from the result dataset. A user defined operator is subsequently applied to calculate a percentage measure with the final persistent result mapped from VTL to a SDMX dataflow.
140 140  
141 -**VTL Sample 3.xml**
141 +##**VTL Sample 3.xml**##
142 142  
143 -Illustrates the calculation of a GDP per capita [[dataset>>doc:sdmx:Glossary.Data set.WebHome]] from an input (% style="color:#e74c3c" %)mapped(%%) [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] containing GDP and population indicators on a country by country basis.
143 +Illustrates the calculation of a GDP per capita dataset from an input mapped SDMX dataflow containing GDP and population indicators on a country by country basis.
144 144  
145 145  = 3 Data Samples =
146 146  
147 -[[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] 3.0 has a single format for data transmission - the Structure Specific Data message. Alternative formats from (% style="color:#e74c3c" %)version(%%) 2.1 and earlier such as Generic, Utility and Cross Sectional are deprecated.
147 +SDMX-ML 3.0 has a single format for data transmission - the Structure Specific Data message. Alternative formats from version 2.1 and earlier such as Generic, Utility and Cross Sectional are deprecated.
148 148  
149 -The Structure Specific Data message is characterised by the XML elements and [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]] being derived from the [[data structure definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] of the [[data set>>doc:sdmx:Glossary.Data set.WebHome]]. This provides two main benefits:
149 +The Structure Specific Data message is characterised by the XML elements and attributes being derived from the data structure definition of the data set. This provides two main benefits:
150 150  
151 151  1. The message content is relatively compact.
152 -1. It is possible to use an XML schema to validate that the [[data set>>doc:sdmx:Glossary.Data set.WebHome]] contains the correct values as defined by the [[data structure definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] and any (% style="color:#e74c3c" %)constraints(%%) attached to the [[dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]], [[data structure definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] or data provision agreement.
152 +1. It is possible to use an XML schema to validate that the data set contains the correct values as defined by the data structure definition and any constraints attached to the dataflow, data structure definition or data provision agreement.
153 153  
154 -The samples therefore include both the Structure Specific Data XML, and a corresponding example validation schema XSD. Successful schema validation confirms that the XML is both a valid Structure Specific Data message, and the content is valid according to the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]].
154 +The samples therefore include both the Structure Specific Data XML, and a corresponding example validation schema XSD. Successful schema validation confirms that the XML is both a valid Structure Specific Data message, and the content is valid according to the SDMX structural metadata.
155 155  
156 156  == Aggregated Time Series with Simple Data Attributes ==
157 157  
158 -**ECB EXR.xml**
158 +### ECB EXR.xml ##
159 159  
160 160  Structure specific data message.
161 161  
162 -Excerpt from the ECB's Exchange Rates [[dataset>>doc:sdmx:Glossary.Data set.WebHome]].
162 +Excerpt from the ECB's Exchange Rates dataset.
163 163  
164 -In this example which is representative of aggregated time-series [[datasets>>doc:sdmx:Glossary.Data set.WebHome]] with a single [[measure>>doc:sdmx:Glossary.Measure.WebHome]], observations are grouped together under series, which in turn are grouped under the [[dataset>>doc:sdmx:Glossary.Data set.WebHome]] element.
164 +In this example which is representative of aggregated time-series datasets with a single measure, observations are grouped together under series, which in turn are grouped under the dataset element.
165 165  
166 -The [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] values and those of series-(% style="color:#e74c3c" %)level(%%) [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]] are expressed as XML [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]] on each series element. Similarly, the TIME_PERIOD, OBS_VALUE and any observation-(% style="color:#e74c3c" %)level(%%) [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]] are expressed as XML [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]] on each obs element.
166 +The dimension values and those of series-level attributes are expressed as XML attributes on each series element. Similarly, the TIME_PERIOD, OBS_VALUE and any observation-level attributes are expressed as XML attributes on each obs element.
167 167  
168 168  Note that a structure specific namespace ns1 is defined using xsi:schemalocation to reference the validation schema location, in this case ECB_EXR_Dataflow.xsd.
169 169  
170 -**ECB EXR Dataflow.xsd**
170 +### ECB EXR Dataflow.xsd ##
171 171  
172 -Structure-specific schema for validating the [[dataset>>doc:sdmx:Glossary.Data set.WebHome]].
172 +Structure-specific schema for validating the dataset.
173 173  
174 -The schema defines a complex type called DataSetType derived from the [[data set>>doc:sdmx:Glossary.Data set.WebHome]]'s [[data structure definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] and (% style="color:#e74c3c" %)constraints(%%), in this case those attached to the [[dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]].
174 +The schema defines a complex type called DataSetType derived from the data set's data structure definition and constraints, in this case those attached to the dataflow.
175 175  
176 -== Aggregated Time Series with Complex Data Attributes ==
176 +## Aggregated Time Series with Complex Data Attributes##
177 177  
178 -Complex [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]] include those with multilingual text and arrays of values.
178 +Complex attributes include those with multilingual text and arrays of values.
179 179  
180 -**EXB EXR CA.xml**
180 +### EXB EXR CA.xml ##
181 181  
182 182  Structure specific data message.
183 183  
184 -A modification of the ECB's Exchange Rates [[dataset>>doc:sdmx:Glossary.Data set.WebHome]] illustrating the following complex [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] use cases:
184 +A modification of the ECB's Exchange Rates dataset illustrating the following complex attribute use cases:
185 185  
186 -[[TITLE>>doc:sdmx:Glossary.Title.WebHome]] - multi-lingual series-level array [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]]
186 +TITLE - multi-lingual series-level array attribute
187 187  
188 -SOURCE_AGENCY - coded series-level array [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] specifying a minimum of three values
188 +SOURCE_AGENCY - coded series-level array attribute specifying a minimum of three values
189 189  
190 -SOURCE_PUB - uncoded string series-level array [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] with maximum length of 350 characters
190 +SOURCE_PUB - uncoded string series-level array attribute with maximum length of 350 characters
191 191  
192 -OBS_STATUS - coded observation-level array [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]]
192 +OBS_STATUS - coded observation-level array attribute
193 193  
194 194  Note that a structure specific namespace ns1 is defined using xsi:schemalocation to reference the validation schema location, in this case ECB_EXR_Dataflow.xsd.
195 195  
196 -**ECB EXR CA Dataflow.xsd**
196 +### ECB EXR CA Dataflow.xsd ##
197 197  
198 -Structure specific schema for validating the [[dataset>>doc:sdmx:Glossary.Data set.WebHome]].
198 +Structure specific schema for validating the dataset.
199 199  
200 -The schema defines a complex type called DataSetType derived from the [[data set>>doc:sdmx:Glossary.Data set.WebHome]]'s [[data structure definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] and (% style="color:#e74c3c" %)constraints(%%), in this case those attached to the [[dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]].
200 +The schema defines a complex type called DataSetType derived from the data set's data structure definition and constraints, in this case those attached to the dataflow.
201 201  
202 -Complex types based on the abstract [[dsd>>doc:sdmx:Glossary.Data structure definition.WebHome]]:CompType are defined for each complex [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]].
202 +Complex types based on the abstract dsd:CompType are defined for each complex attribute.
203 203  
204 -**ECB EXR CA DSD.xml**
204 +### ECB EXR CA DSD.xml ##
205 205  
206 -Structure message describing the [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] for the above [[dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] illustrating, in particular, the definition of complex [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]]:
206 +Structure message describing the Data Structure Definition for the above dataflow illustrating, in particular, the definition of complex attributes:
207 207  
208 208  The XML attribute isMultiLingual="true" on the \<str:TextFormat…\> element specifies a multi-lingual string representation.
209 209  
210 -Setting the maxOccurs XML [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] to a number greater than 1 (or unbounded) on the \<str:LocalRepresentation…\> element specifies an array.
210 +Setting the maxOccurs XML attribute to a number greater than 1 (or unbounded) on the \<str:LocalRepresentation…\> element specifies an array.
SKMS.Methodology.Code.MethodologyClass[0]
Index
... ... @@ -1,1 +1,0 @@
1 -7
SUZ.Methodology.Code.MethodologyClass[0]
index
... ... @@ -1,0 +1,1 @@
1 +7