Last modified by Artur K. on 2025/09/10 11:19

From version 10.1
edited by Helena K.
on 2025/06/24 15:20
Change comment: There is no comment for this version
To version 9.1
edited by Helena K.
on 2025/06/24 15:17
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -50,7 +50,6 @@
50 50  com:Annotations?, DataProvider?, Attributes?, Group*, (Series+ | Obs+)?
51 51  
52 52  Attribute Documentation:
53 -
54 54  (% style="width:1011.29px" %)
55 55  |**Name**|**Type**|(% style="width:597px" %)**Documentation**
56 56  |structureRef|xs:IDREF|(% style="width:597px" %)The structureRef contains a reference to a structural specification in the header of a data or reference metadata message. The structural specification details which structure the data or reference metadata conforms to, as well as providing additional information such as how the data is structure (e.g. which dimension occurs at the observation level for a data set).
... ... @@ -64,7 +64,6 @@
64 64  |publicationPeriod|com: ObservationalTimePeriodType|(% style="width:597px" %)The publicationPeriod specifies the period of publication of the data or metadata in terms of whatever provisioning agreements might be in force (i.e., "Q1 2005" if that is the time of publication for a data set published on a quarterly basis).
65 65  
66 66  Element Documentation:
67 -
68 68  (% style="width:1016.29px" %)
69 69  |**Name**|**Type**|(% style="width:642px" %)**Documentation**
70 70  |com:Annotations|com:AnnotationsType|(% style="width:642px" %)Annotations is a reusable element the provides for a collection of annotations. It has been made global so that restrictions of types that extend AnnotatableType my reference it.
... ... @@ -77,7 +77,6 @@
77 77  **GroupType: **GroupType defines a structure which is used to communicate attribute values for a group defined in a data structure definition. The group can consist of either a subset of the dimensions defined by the data structure definition, or an association to an attachment constraint, which in turn defines key sets to which attributes can be attached. In the case that the group is based on an attachment constraint, only the identification of group is provided. It is expected that a system which is processing this will relate that identifier to the key sets defined in the constraint and apply the values provided for the attributes appropriately.
78 78  
79 79  Derivation:
80 -
81 81  * //com:AnnotableType// (extension) 
82 82  ** GroupType
83 83  
... ... @@ -88,13 +88,11 @@
88 88  com:Annotations?, GroupKey?, Attributes
89 89  
90 90  Attribute Documentation:
91 -
92 92  (% style="width:1010.29px" %)
93 93  |**Name**|**Type**|(% style="width:709px" %)**Documentation**
94 94  |type|com:IDType|(% style="width:709px" %)The type attribute holds the identifier assigned to the group in the data structure definition for which attribute values are being provided.
95 95  
96 96  Element Documentation:
97 -
98 98  (% style="width:1014.29px" %)
99 99  |**Name**|**Type**|(% style="width:704px" %)**Documentation**
100 100  |com:Annotations|com:AnnotationsType|(% style="width:704px" %)Annotations is a reusable element the provides for a collection of annotations. It has been made global so that restrictions of types that extend AnnotatableType my reference it.
... ... @@ -104,7 +104,6 @@
104 104  **SeriesType: **SeriesType defines a structure which is used to group a collection of observations which have a key in common. The key for a series is every dimension defined in the data structure definition, save the dimension declared to be at the observation level for this data set. In addition to observations, values can be provided for attributes which are associated with the dimensions which make up this series key (so long as the attributes do not specify a group attachment or also have an relationship with the observation dimension). It is possible for the series to contain only observations or only attribute values, or both.
105 105  
106 106  Derivation:
107 -
108 108  * //com:AnnotableType// (extension) 
109 109  ** SeriesType
110 110  
... ... @@ -112,7 +112,6 @@
112 112  com:Annotations?, SeriesKey, Attributes?, Obs*
113 113  
114 114  Element Documentation:
115 -
116 116  (% style="width:999.294px" %)
117 117  |**Name**|**Type**|(% style="width:689px" %)**Documentation**
118 118  |com:Annotations|com:AnnotationsType|(% style="width:689px" %)Annotations is a reusable element the provides for a collection of annotations. It has been made global so that restrictions of types that extend AnnotatableType my reference it.
... ... @@ -123,7 +123,6 @@
123 123  **ObsOnlyType: **ObsOnlyType defines the structure for an un-grouped observation. Unlike a group observation, an un-grouped must provided a full set of values for every dimension declared in the data structure definition. The observation can contain an observed value and/or a collection of attribute values.
124 124  
125 125  Derivation:
126 -
127 127  * //com:AnnotableType// (extension) 
128 128  ** ObsOnlyType
129 129  
... ... @@ -131,7 +131,6 @@
131 131  com:Annotations?, ObsKey, ObsValue?, Attributes?
132 132  
133 133  Element Documentation:
134 -
135 135  (% style="width:996.294px" %)
136 136  |**Name**|**Type**|(% style="width:651px" %)**Documentation**
137 137  |com:Annotations|com:AnnotationsType|(% style="width:651px" %)Annotations is a reusable element the provides for a collection of annotations. It has been made global so that restrictions of types that extend AnnotatableType my reference it.
... ... @@ -142,7 +142,6 @@
142 142  **ObsType: **ObsType defines the structure of a grouped observation. The observation must be provided a value for the dimension which is declared to be at the observation level for this data set. This dimension value should disambiguate the observation within the series in which it is defined (i.e. there should not be another observation with the same dimension value). The observation can contain an observed value and/or attribute values.
143 143  
144 144  Derivation:
145 -
146 146  * //com:AnnotableType// (extension) 
147 147  ** ObsType
148 148  
... ... @@ -150,7 +150,6 @@
150 150  com:Annotations?, ObsDimension, ObsValue?, Attributes?
151 151  
152 152  Element Documentation:
153 -
154 154  (% style="width:1004.29px" %)
155 155  |**Name**|**Type**|(% style="width:694px" %)**Documentation**
156 156  |com:Annotations|com:AnnotationsType|(% style="width:694px" %)Annotations is a reusable element the provides for a collection of annotations. It has been made global so that restrictions of types that extend AnnotatableType my reference it.
... ... @@ -164,7 +164,6 @@
164 164  Value+
165 165  
166 166  Element Documentation:
167 -
168 168  (% style="width:1008.29px" %)
169 169  |**Name**|(% style="width:185px" %)**Type**|(% style="width:692px" %)**Documentation**
170 170  |Value|(% style="width:185px" %)ComponentValueType|(% style="width:692px" %)Value contains a component value and a reference to the component for which a value is being provided.
... ... @@ -178,7 +178,6 @@
178 178  {Empty}
179 179  
180 180  Attribute Documentation:
181 -
182 182  (% style="width:1003.29px" %)
183 183  |**Name**|(% style="width:194px" %)**Type**|(% style="width:664px" %)**Documentation**
184 184  |id|(% style="width:194px" %)com:NCNameIDType|(% style="width:664px" %)The id attribute contains the identifier for the component for which a value is being provided.
... ... @@ -187,7 +187,6 @@
187 187  **ObsValueType: **ObsValueType is a derivation of the BaseValueType which is used to provide an observation value. Since an observation value is always associated with the data structure definition primary measure, and the identifier for the primary measure is fixed, the component reference for this structure is fixed. Note that this means that it is not necessary to provide a value in an instance as the fixed value will be provided in the post validation information set.
188 188  
189 189  Derivation:
190 -
191 191  * BaseValueType (restriction) 
192 192  ** ObsValueType
193 193  
... ... @@ -198,7 +198,6 @@
198 198  {Empty}
199 199  
200 200  Attribute Documentation:
201 -
202 202  (% style="width:1004.29px" %)
203 203  |(% style="width:190px" %)**Name**|(% style="width:213px" %)**Type**|(% style="width:598px" %)**Documentation**
204 204  |(% style="width:190px" %)id (fixed: OBS_VALUE)|(% style="width:213px" %)com:NCNameIDType|(% style="width:598px" %)The id attribute contains a fixed reference to the primary measure component of the data structure definition.
... ... @@ -207,7 +207,6 @@
207 207  **ComponentValueType: **ComponentValueType is a derivation of the BaseValueType which requires that the component reference be provided. This is used when the identification of the component cannot be inferred from another context.
208 208  
209 209  Derivation:
210 -
211 211  * BaseValueType (restriction) 
212 212  ** ComponentValueType
213 213  
... ... @@ -218,7 +218,6 @@
218 218  {Empty}
219 219  
220 220  Attribute Documentation:
221 -
222 222  (% style="width:1008.29px" %)
223 223  |**Name**|(% style="width:184px" %)**Type**|(% style="width:679px" %)**Documentation**
224 224  |id|(% style="width:184px" %)com:NCNameIDType|(% style="width:679px" %)The id attribute contains the identifier for the component for which a value is being provided.
... ... @@ -227,7 +227,6 @@
227 227  **TimeSeriesDataSetType: **TimeSeriesDataSetType is a derivation of the base DataSetType of the generic format the restricts the data set to only allow for grouped observations where the dimension at the observation level is the time dimension of the data structure definition. This means that unlike the base data set structure, there can be no un-grouped observations. Because this derivation is achieved using restriction, data sets conforming to this type will inherently conform to the base data set structure as well. In fact, data structured here will be identical to data in the base data set when the time dimension is the observation dimension. This means that the data contained in this structure can be processed in exactly the same manner as the base structure.
228 228  
229 229  Derivation:
230 -
231 231  * //com:AnnotableType// (extension) 
232 232  ** DataSetType (restriction) 
233 233  *** TimeSeriesDataSetType
... ... @@ -239,7 +239,6 @@
239 239  com:Annotations?, DataProvider?, Attributes?, Group*, Series*
240 240  
241 241  Attribute Documentation:
242 -
243 243  (% style="width:1004.29px" %)
244 244  |**Name**|**Type**|(% style="width:590px" %)**Documentation**
245 245  |structureRef|xs:IDREF|(% style="width:590px" %)The structureRef contains a reference to a structural specification in the header of a data or reference metadata message. The structural specification details which structure the data or reference metadata conforms to, as well as providing additional information such as how the data is structure (e.g. which dimension occurs at the observation level for a data set).
... ... @@ -253,7 +253,6 @@
253 253  |publicationPeriod|com: ObservationalTimePeriodType|(% style="width:590px" %)The publicationPeriod specifies the period of publication of the data or metadata in terms of whatever provisioning agreements might be in force (i.e., "Q1 2005" if that is the time of publication for a data set published on a quarterly basis).
254 254  
255 255  Element Documentation:
256 -
257 257  (% style="width:999.294px" %)
258 258  |**Name**|**Type**|(% style="width:622px" %)**Documentation**
259 259  |com:Annotations|com:AnnotationsType|(% style="width:622px" %)Annotations is a reusable element the provides for a collection of annotations. It has been made global so that restrictions of types that extend AnnotatableType my reference it.
... ... @@ -265,7 +265,6 @@
265 265  **TimeSeriesType: **TimeSeriesType defines a structure which is used to group a collection of observations which have a key in common, organised by time. The key for a series is every dimension defined in the data structure definition, save the time dimension. In addition to observations, values can be provided for attributes which are associated with the dimensions which make up this series key (so long as the attributes do not specify a group attachment or also have an relationship with the time dimension). It is possible for the series to contain only observations or only attribute values, or both.
266 266  
267 267  Derivation:
268 -
269 269  * //com:AnnotableType// (extension) 
270 270  ** SeriesType (restriction) 
271 271  *** TimeSeriesType
... ... @@ -274,7 +274,6 @@
274 274  com:Annotations?, SeriesKey, Attributes?, Obs*
275 275  
276 276  Element Documentation:
277 -
278 278  (% style="width:1012.29px" %)
279 279  |**Name**|**Type**|(% style="width:695px" %)**Documentation**
280 280  |com:Annotations|com:AnnotationsType|(% style="width:695px" %)Annotations is a reusable element the provides for a collection of annotations. It has been made global so that restrictions of types that extend AnnotatableType my reference it.
... ... @@ -285,7 +285,6 @@
285 285  **TimeSeriesObsType: **TimeSeriesObsType defines the structure of a time series observation. The observation must be provided a value for the time dimension. This time value should disambiguate the observation within the series in which it is defined (i.e. there should not be another observation with the same time value). The observation can contain an observed value and/or attribute values.
286 286  
287 287  Derivation:
288 -
289 289  * //com:AnnotableType// (extension) 
290 290  ** ObsType (restriction) 
291 291  *** TimeSeriesObsType
... ... @@ -294,7 +294,6 @@
294 294  com:Annotations?, ObsDimension, ObsValue?, Attributes?
295 295  
296 296  Element Documentation:
297 -
298 298  (% style="width:1019.29px" %)
299 299  |**Name**|**Type**|(% style="width:709px" %)**Documentation**
300 300  |com:Annotations|com:AnnotationsType|(% style="width:709px" %)Annotations is a reusable element the provides for a collection of annotations. It has been made global so that restrictions of types that extend AnnotatableType my reference it.
... ... @@ -305,7 +305,6 @@
305 305  **TimeValueType: **TimeValueType is a derivation of the BaseValueType which is used to provide a value for the time dimension. Since the identifier for the time dimension is fixed, the component reference for this structure is fixed. Note that this means that it is not necessary to provide a value in an instance as the fixed value will be provided in the post validation information set.
306 306  
307 307  Derivation:
308 -
309 309  * BaseValueType (restriction) 
310 310  ** TimeValueType
311 311  
... ... @@ -316,7 +316,6 @@
316 316  {Empty}
317 317  
318 318  Attribute Documentation:
319 -
320 320  (% style="width:1013.29px" %)
321 321  |(% style="width:205px" %)**Name**|(% style="width:277px" %)**Type**|(% style="width:528px" %)**Documentation**
322 322  |(% style="width:205px" %)id (fixed: TIME_PERIOD)|(% style="width:277px" %)com:NCNameIDType|(% style="width:528px" %)The id attribute contains the identifier for the component for which a value is being provided.
... ... @@ -344,7 +344,6 @@
344 344  **//DataSetType//: **DataSetType is the abstract type which defines the base structure for any data structure definition specific data set. A derived data set type will be created that is specific to a data structure definition and the details of the organisation of the data (i.e. which dimension is the observation dimension and whether explicit measures should be used). Data is organised into either a collection of series (grouped observations) or a collection of un-grouped observations. The derived data set type will restrict this choice to be either grouped or un-grouped observations. If this dimension is "AllDimensions" then the derived data set type must consist of a collection of un-grouped observations; otherwise the data set will contain a collection of series with the observations in the series disambiguated by the specified dimension at the observation level. This data set is capable of containing data (observed values) and/or documentation (attribute values) and can be used for incremental updates and deletions (i.e. only the relevant updates or deletes are exchanged). It is assumed that each series or un-grouped observation will be distinct in its purpose. For example, if series contains both data and documentation, it assumed that each series will have a unique key. If the series contains only data or only documentation, then it is possible that another series with the same key might exist, but with not with the same purpose (i.e. to provide data or documentation) as the first series. This base type is designed such that derived types can be processed in a generic manner; it assures that data structure definition specific data will have a consistent structure. The group, series, and observation elements are unqualified, meaning that they are not qualified with a namespace in an instance. This means that in the derived data set types, the elements will always be the same, regardless of the target namespace of the schemas which defines these derived types. This allows for consistent processing of the structure without regard to what the namespace might be for the data structure definition specific schema. The data set can contain values for attributes which do not have an attribute relationship with any data structure definition components. These attribute values will exist in XML attributes in this element based on this type (DataSet). This is specified in the content model with the declaration of anyAttributes in the "local" namespace. The derived data set type will refine this structure so that the attributes are explicit. The XML attributes will be given a name based on the attribute's identifier. These XML attributes will be unqualified (meaning they do not have a namespace associated with them). To allow for generic processing, it is required that the only unqualified XML attributes in the derived data set type (outside of the standard data set attributes) be for attributes declared in the data structure definition. If additional attributes are required, these should be qualified with a namespace so that a generic application can easily distinguish them as not being meant to represent a data structure definition attribute.
345 345  
346 346  Derivation:
347 -
348 348  * //com:AnnotableType// (extension)
349 349  ** //DataSetType//
350 350  
... ... @@ -355,7 +355,6 @@
355 355  com:Annotations?, DataProvider?, Group*, (Series+ | Obs+)?
356 356  
357 357  Attribute Documentation:
358 -
359 359  (% style="width:1005.29px" %)
360 360  |(% style="width:199px" %)**Name**|(% style="width:216px" %)**Type**|(% style="width:521px" %)**Documentation**
361 361  |(% style="width:199px" %)structureRef|(% style="width:216px" %)xs:IDREF|(% style="width:521px" %)The structureRef contains a reference to a structural specification in the header of a data or reference metadata message. The structural specification details which structure the data or reference metadata conforms to, as well as providing additional information such as how the data is structure (e.g. which dimension occurs at the observation level for a data set).
... ... @@ -371,7 +371,6 @@
371 371  |(% style="width:199px" %)REPORTING_YEAR_START_DAY|(% style="width:216px" %)xs:gMonthDay|(% style="width:521px" %)The REPORTING_YEAR_START_DAY attribute is an explict attribute for the reporting year start day, which provides context to the time dimension when its value contains a reporting period (e.g. 2010-Q1). This attribute is used to state the month and day that the reporting year begins (e.g. ~-~-07-01 for July 1st). In the absence of an explicit value provided in this attribute, all reporting period values will be assumed to be based on a reporting year start day of January 1. This is declared in the base schema since it has a fixed identifier and representation. The derived data set type may either require or prohibit this attribute, depending on whether the data structure declared the reporting year start day attribute and if so, the attribute relationship and assignment status assigned to it.
372 372  
373 373  Element Documentation:
374 -
375 375  (% style="width:1005.29px" %)
376 376  |**Name**|**Type**|(% style="width:630px" %)**Documentation**
377 377  |com:Annotations|com:AnnotationsType|(% style="width:630px" %)Annotations is a reusable element the provides for a collection of annotations. It has been made global so that restrictions of types that extend AnnotatableType my reference it.
... ... @@ -383,7 +383,6 @@
383 383  **//GroupType//: **GroupType is the abstract type which defines a structure which is used to communicate attribute values for a group defined in a data structure definition. The group can consist of either a subset of the dimensions defined by the data structure definition, or an association to an attachment constraint, which in turn defines key sets to which attributes can be attached. In the case that the group is based on an attachment constraint, only the identification of group is provided. It is expected that a system which is processing this will relate that identifier to the key sets defined in the constraint and apply the values provided for the attributes appropriately. Data structure definition schemas will drive types based on this for each group defined in the data structure definition. Both the dimension values which make up the key (if applicable) and the attribute values associated with the group will be represented with XML attributes. This is specified in the content model with the declaration of anyAttributes in the "local" namespace. The derived group type will refine this structure so that the attributes are explicit. The XML attributes will be given a name based on the attribute's identifier. These XML attributes will be unqualified (meaning they do not have a namespace associated with them). The dimension XML attributes will be required while the attribute XML attributes will be optional. To allow for generic processing, it is required that the only unqualified XML attributes in the derived group type be for the group dimensions and attributes declared in the data structure definition. If additional attributes are required, these should be qualified with a namespace so that a generic application can easily distinguish them as not being meant to represent a data structure definition dimension or attribute.
384 384  
385 385  Derivation:
386 -
387 387  * //com:AnnotableType// (extension) 
388 388  ** //GroupType//
389 389  
... ... @@ -394,7 +394,6 @@
394 394  com:Annotations?
395 395  
396 396  Attribute Documentation:
397 -
398 398  (% style="width:1008.29px" %)
399 399  |**Name**|**Type**|(% style="width:621px" %)**Documentation**
400 400  |type|com:IDType|(% style="width:621px" %)The type attribute reference the identifier of the group as defined in the data structure definition. This is optional, but derived group types will provide a fixed value for this so that it always available in the post validation information set. This allows the group to be processed in a generic manner.
... ... @@ -401,7 +401,6 @@
401 401  |REPORTING_YEAR_START_DAY|xs:gMonthDay|(% style="width:621px" %)The REPORTING_YEAR_START_DAY attribute is an explict attribute for the reporting year start day, which provides context to the time dimension when its value contains a reporting period (e.g. 2010-Q1). This attribute is used to state the month and day that the reporting year begins (e.g. ~-~-07-01 for July 1st). In the absence of an explicit value provided in this attribute, all reporting period values will be assumed to be based on a reporting year start day of January 1. This is declared in the base schema since it has a fixed identifier and representation. The derived group types may either require or prohibit this attribute, depending on whether the data structure declared the reporting year start day attribute and if so, the attribute relationship and assignment status assigned to it.
402 402  
403 403  Element Documentation:
404 -
405 405  |**Name**|**Type**|**Documentation**
406 406  |com:Annotations|com:AnnotationsType|Annotations is a reusable element the provides for a collection of annotations. It has been made global so that restrictions of types that extend AnnotatableType my reference it.
407 407  
... ... @@ -408,7 +408,6 @@
408 408  **//SeriesType//: **SeriesType is the abstract type which defines a structure which is used to group a collection of observations which have a key in common. The key for a series is every dimension defined in the data structure definition, save the dimension declared to be at the observation level for this data set. In addition to observations, values can be provided for attributes which are associated with the dimensions which make up this series key (so long as the attributes do not specify a group attachment or also have an relationship with the observation dimension). It is possible for the series to contain only observations or only attribute values, or both. Data structure definition schemas will drive a type based on this that is specific to the data structure definition and the variation of the format being expressed in the schema. Both the dimension values which make up the key and the attribute values associated with the key dimensions will be represented with XML attributes. This is specified in the content model with the declaration of anyAttributes in the "local" namespace. The derived series type will refine this structure so that the attributes are explicit. The XML attributes will be given a name based on the attribute's identifier. These XML attributes will be unqualified (meaning they do not have a namespace associated with them). The dimension XML attributes will be required while the attribute XML attributes will be optional. To allow for generic processing, it is required that the only unqualified XML attributes in the derived group type be for the series dimensions and attributes declared in the data structure definition. If additional attributes are required, these should be qualified with a namespace so that a generic application can easily distinguish them as not being meant to represent a data structure definition dimension or attribute.
409 409  
410 410  Derivation:
411 -
412 412  * //com:AnnotableType// (extension) 
413 413  ** //SeriesType//
414 414  
... ... @@ -419,7 +419,6 @@
419 419  com:Annotations?, Obs*
420 420  
421 421  Attribute Documentation:
422 -
423 423  (% style="width:1002.29px" %)
424 424  |**Name**|**Type**|(% style="width:533px" %)**Documentation**
425 425  |TIME_PERIOD|com: ObservationalTimePer iodType|(% style="width:533px" %)The TIME_PERIOD attribute is an explict attribute for the time dimension. This is declared in the base schema since it has a fixed identifier and representation. The derived series type will either require or prohibit this attribute, depending on whether time is the observation dimension. If the time dimension specifies a more specific representation of time the derived type will restrict the type definition to the appropriate type.
... ... @@ -426,7 +426,6 @@
426 426  |REPORTING_YEAR_START_DAY|xs:gMonthDay|(% style="width:533px" %)The REPORTING_YEAR_START_DAY attribute is an explict attribute for the reporting year start day, which provides context to the time dimension when its value contains a reporting period (e.g. 2010-Q1). This attribute is used to state the month and day that the reporting year begins (e.g. ~-~-07-01 for July 1st). In the absence of an explicit value provided in this attribute, all reporting period values will be assumed to be based on a reporting year start day of January 1. This is declared in the base schema since it has a fixed identifier and representation. The derived series type may either require or prohibit this attribute, depending on whether the data structure declared the reporting year start day attribute and if so, the attribute relationship and assignment status assigned to it.
427 427  
428 428  Element Documentation:
429 -
430 430  |**Name**|**Type**|**Documentation**
431 431  |com:Annotations|com:AnnotationsType|Annotations is a reusable element the provides for a collection of annotations. It has been made global so that restrictions of types that extend AnnotatableType my reference it.
432 432  |Obs|//ObsType//|
... ... @@ -434,7 +434,6 @@
434 434  **//ObsType//: **ObsType is the abstract type which defines the structure of a grouped or un-grouped observation. The observation must be provided a key, which is either a value for the dimension which is declared to be at the observation level if the observation is grouped, or a full set of values for all dimensions in the data structure definition if the observation is un-grouped. This key should disambiguate the observation within the context in which it is defined (e.g. there should not be another observation with the same dimension value in a series). The observation can contain an observed value and/or attribute values. Data structure definition schemas will drive a type or types based on this that is specific to the data structure definition and the variation of the format being expressed in the schema. The dimension value(s) which make up the key and the attribute values associated with the key dimension(s) or the primary measure will be represented with XML attributes. This is specified in the content model with the declaration of anyAttributes in the "local" namespace. The derived observation type will refine this structure so that the attributes are explicit. The XML attributes will be given a name based on the attribute's identifier. These XML attributes will be unqualified (meaning they do not have a namespace associated with them). The dimension XML attribute(s) will be required while the attribute XML attributes will be optional. To allow for generic processing, it is required that the only unqualified XML attributes in the derived observation type be for the observation dimension(s) and attributes declared in the data structure definition. If additional attributes are required, these should be qualified with a namespace so that a generic application can easily distinguish them as not being meant to represent a data structure definition dimension or attribute. If the data structure definition specific schema requires that explicit measures be used (only possible when the measure dimension is specified at the observation), then there will be types derived for each measure defined by the measure dimension. In this case, the types will be specific to each measure, which is to say that the representation of the primary measure (i.e. the observed value) will be restricted to that which is specified by the specific measure.
435 435  
436 436  Derivation:
437 -
438 438  * //com:AnnotableType// (extension) 
439 439  ** //ObsType//
440 440  
... ... @@ -445,7 +445,6 @@
445 445  com:Annotations?
446 446  
447 447  Attribute Documentation:
448 -
449 449  (% style="width:1014.29px" %)
450 450  |**Name**|**Type**|(% style="width:505px" %)**Documentation**
451 451  |type|com:IDType|(% style="width:505px" %)The type attribute is used when the derived format requires that explicit measure be used. In this case, the derived type based on the measure will fix this value to be the identification of the measure concept. This will not be required, but since it is fixed it will be available in the post validation information set which will allow for generic processing of the data. If explicit measures are not used, then the derived type will prohibit the use of this attribute.
... ... @@ -454,7 +454,6 @@
454 454  |OBS_VALUE|xs:anySimpleType|(% style="width:505px" %)The OBS_VALUE attribute is an explicit attribute for the primary measure, which is intended to hold the value for the observation. This is declared in the base schema since it has a fixed identifier. This attribute is un-typed, since the representation of the observed value can vary widely. Derived types will restrict this to be a type based on the representation of the primary measure. In the case that an explicit measure is used, the derived type for a given measure might further restrict the type of the primary measure to be more specific to the core representation for the measure concept. Note that it is required that in the case of multiple measures being used, that the representation of the primary measure is broad enough to handle the various representations of the measure concepts.
455 455  
456 456  Element Documentation:
457 -
458 458  |**Name**|**Type**|**Documentation**
459 459  |com:Annotations|com:AnnotationsType|Annotations is a reusable element the provides for a collection of annotations. It has been made global so that restrictions of types that extend AnnotatableType my reference it.
460 460  
... ... @@ -461,7 +461,6 @@
461 461  **//TimeSeriesDataSetType//: **TimeSeriesDataSetType is the abstract type which defines the base structure for any data structure definition specific time series based data set. A derived data set type will be created that is specific to a data structure definition. Unlike the base format, only one variation of this is allowed for a data structure definition. This variation is the time dimension as the observation dimension. Data is organised into a collection of time series. Because this derivation is achieved using restriction, data sets conforming to this type will inherently conform to the base data set structure as well. In fact, data structure specific here will be identical to data in the base data set when the time dimension is the observation dimension, even for the derived data set types. This means that the data contained in this structure can be processed in exactly the same manner as the base structure. The same rules for derivation as the base data set type apply to this specialized data set.
462 462  
463 463  Derivation:
464 -
465 465  * //com:AnnotableType// (extension) 
466 466  ** //DataSetType// (restriction) 
467 467  *** //TimeSeriesDataSetType//
... ... @@ -473,7 +473,6 @@
473 473  com:Annotations?, DataProvider?, Group*, Series*
474 474  
475 475  Attribute Documentation:
476 -
477 477  (% style="width:1003.29px" %)
478 478  |(% style="width:213px" %)**Name**|(% style="width:274px" %)**Type**|(% style="width:461px" %)**Documentation**
479 479  |(% style="width:213px" %)structureRef|(% style="width:274px" %)xs:IDREF|(% style="width:461px" %)The structureRef contains a reference to a structural specification in the header of a data or reference metadata message. The structural specification details which structure the data or reference metadata conforms to, as well as providing additional information such as how the data is structure (e.g. which dimension occurs at the observation level for a data set).
... ... @@ -489,7 +489,6 @@
489 489  |(% style="width:213px" %)REPORTING_YEAR_START_DAY|(% style="width:274px" %)xs:gMonthDay|(% style="width:461px" %)The REPORTING_YEAR_START_DAY attribute is an explict attribute for the reporting year start day, which provides context to the time dimension when its value contains a reporting period (e.g. 2010-Q1). This attribute is used to state the month and day that the reporting year begins (e.g. ~-~-07-01 for July 1st). In the absence of an explicit value provided in this attribute, all reporting period values will be assumed to be based on a reporting year start day of January 1. This is declared in the base schema since it has a fixed identifier and representation. The derived data set type may either require or prohibit this attribute, depending on whether the data structure declared the reporting year start day attribute and if so, the attribute relationship and assignment status assigned to it.
490 490  
491 491  Element Documentation:
492 -
493 493  (% style="width:1007.29px" %)
494 494  |**Name**|**Type**|(% style="width:632px" %)**Documentation**
495 495  |com:Annotations|com:AnnotationsType|(% style="width:632px" %)Annotations is a reusable element the provides for a collection of annotations. It has been made global so that restrictions of types that extend AnnotatableType my reference it.
... ... @@ -500,7 +500,6 @@
500 500  **TimeSeriesType: **TimeSeriesType defines an abstract structure which is used to group a collection of observations which have a key in common, organised by time. The key for a series is every dimension defined in the data structure definition, save the time dimension. In addition to observations, values can be provided for attributes which are associated with the dimensions which make up this series key (so long as the attributes do not specify a group attachment or also have an relationship with the time dimension). It is possible for the series to contain only observations or only attribute values, or both. The same rules for derivation as the base series type apply to this specialized series.
501 501  
502 502  Derivation:
503 -
504 504  * //com:AnnotableType// (extension) 
505 505  ** //SeriesType// (restriction) 
506 506  *** TimeSeriesType
... ... @@ -512,13 +512,11 @@
512 512  com:Annotations?, Obs*
513 513  
514 514  Attribute Documentation:
515 -
516 516  (% style="width:1004.29px" %)
517 517  |**Name**|**Type**|(% style="width:617px" %)**Documentation**
518 518  |REPORTING_YEAR_START_DAY|xs:gMonthDay|(% style="width:617px" %)The REPORTING_YEAR_START_DAY attribute is an explict attribute for the reporting year start day, which provides context to the time dimension when its value contains a reporting period (e.g. 2010-Q1). This attribute is used to state the month and day that the reporting year begins (e.g. ~-~-07-01 for July 1st). In the absence of an explicit value provided in this attribute, all reporting period values will be assumed to be based on a reporting year start day of January 1. This is declared in the base schema since it has a fixed identifier and representation. The derived series type may either require or prohibit this attribute, depending on whether the data structure declared the reporting year start day attribute and if so, the attribute relationship and assignment status assigned to it.
519 519  
520 520  Element Documentation:
521 -
522 522  (% style="width:1003.29px" %)
523 523  |**Name**|**Type**|(% style="width:593px" %)**Documentation**
524 524  |com:Annotations|com:AnnotationsType|(% style="width:593px" %)Annotations is a reusable element the provides for a collection of annotations. It has been made global so that restrictions of types that extend AnnotatableType my reference it.
... ... @@ -527,7 +527,6 @@
527 527  **//TimeSeriesObsType//: **TimeSeriesObsType defines the abstract structure of a time series observation. The observation must be provided a value for the time dimension. This time value should disambiguate the observation within the series in which it is defined (i.e. there should not be another observation with the same time value). The observation can contain an observed value and/or attribute values. The same rules for derivation as the base observation type apply to this specialized observation.
528 528  
529 529  Derivation:
530 -
531 531  * //com:AnnotableType// (extension) 
532 532  ** //ObsType// (restriction) 
533 533  *** //TimeSeriesObsType//
... ... @@ -539,7 +539,6 @@
539 539  com:Annotations?
540 540  
541 541  Attribute Documentation:
542 -
543 543  (% style="width:1005.29px" %)
544 544  |**Name**|**Type**|(% style="width:496px" %)**Documentation**
545 545  |TIME_PERIOD|com: ObservationalTimePeriodType|(% style="width:496px" %)The TIME_PERIOD attribute is an explicit attribute for the time dimension. This is declared in the base schema since it has a fixed identifier and representation. Since this data is structured to be time series only, this attribute is always required. If the time dimension specifies a more specific representation of time the derived type will restrict the type definition to the appropriate type.
... ... @@ -547,7 +547,6 @@
547 547  |OBS_VALUE|xs:anySimpleType|(% style="width:496px" %)The OBS_VALUE attribute is an explicit attribute for the primary measure, which is intended to hold the value for the observation. This is declared in the base schema since it has a fixed identifier. This attribute is un-typed, since the representation of the observed value can vary widely. Derived types will restrict this to be a type based on the representation of the primary measure. In the case that an explicit measure is used, the derived type for a given measure might further restrict the type of the primary measure to be more specific to the core representation for the measure concept. Note that it is required that in the case of multiple measures being used, that the representation of the primary measure is broad enough to handle the various representations of the measure concepts.
548 548  
549 549  Element Documentation:
550 -
551 551  (% style="width:1013.29px" %)
552 552  |**Name**|**Type**|(% style="width:603px" %)**Documentation**
553 553  |com:Annotations|com:AnnotationsType|(% style="width:603px" %)Annotations is a reusable element the provides for a collection of annotations. It has been made global so that restrictions of types that extend AnnotatableType my reference it.
... ... @@ -589,7 +589,6 @@
589 589  **MetadataSetType: **MetadataSetType describes the structure for a metadata set, which contains a collection of reported metadata against a set of values for a given full or partial target identifier, as described in a metadata structure definition. The metadata set may contain reported metadata for multiple report structures defined in a metadata structure definition.
590 590  
591 591  Derivation:
592 -
593 593  * //com:AnnotableType// (extension) 
594 594  ** MetadataSetType
595 595  
... ... @@ -614,7 +614,6 @@
614 614  |publicationPeriod|com: ObservationalTimePeriodType|(% style="width:592px" %)The publicationPeriod specifies the period of publication of the data or metadata in terms of whatever provisioning agreements might be in force (i.e., "Q1 2005" if that is the time of publication for a data set published on a quarterly basis).
615 615  
616 616  Element Documentation:
617 -
618 618  (% style="width:1006.29px" %)
619 619  |**Name**|(% style="width:268px" %)**Type**|(% style="width:562px" %)**Documentation**
620 620  |com:Annotations|(% style="width:268px" %)com:AnnotationsType|(% style="width:562px" %)Annotations is a reusable element the provides for a collection of annotations. It has been made global so that restrictions of types that extend AnnotatableType my reference it.
... ... @@ -625,7 +625,6 @@
625 625  **ReportType: **ReportType contains a set of report attributes and identifies a target objects] to which they apply.
626 626  
627 627  Derivation:
628 -
629 629  * //com:AnnotableType// (extension) 
630 630  ** ReportType
631 631  
... ... @@ -636,13 +636,11 @@
636 636  com:Annotations?, Target, AttributeSet
637 637  
638 638  Attribute Documentation:
639 -
640 640  (% style="width:1003.29px" %)
641 641  |**Name**|**Type**|(% style="width:788px" %)**Documentation**
642 642  |id|com:IDType|(% style="width:788px" %)The id attribute holds the identifier of the report structure as defined in the metadata structure definition. This identifies the report structure which defines the structure of metadata that is being reported.
643 643  
644 644  Element Documentation:
645 -
646 646  (% style="width:1003.29px" %)
647 647  |**Name**|**Type**|(% style="width:593px" %)**Documentation**
648 648  |com:Annotations|com:AnnotationsType|(% style="width:593px" %)Annotations is a reusable element the provides for a collection of annotations. It has been made global so that restrictions of types that extend AnnotatableType my reference it.
... ... @@ -658,13 +658,11 @@
658 658  ReferenceValue+
659 659  
660 660  Attribute Documentation:
661 -
662 662  (% style="width:1003.29px" %)
663 663  |**Name**|**Type**|(% style="width:805px" %)**Documentation**
664 664  |id|com:IDType|(% style="width:805px" %)The id attribute holds the identifier of the metadata target as defined in the metadata structure definition. This identifies the metadata target of the report structure that identifies the target object(s) of the reported metadata.
665 665  
666 666  Element Documentation:
667 -
668 668  (% style="width:1009.29px" %)
669 669  |**Name**|**Type**|(% style="width:710px" %)**Documentation**
670 670  |ReferenceValue|ReferenceValueType|(% style="width:710px" %)ReferenceValue contains a value for a target reference object reference. When this is taken with its sibling elements, they identify the object or objects to which the reported metadata apply. The content of this will either be a reference to an identifiable object, a data key, a reference to a data set, or a report period.
... ... @@ -678,7 +678,6 @@
678 678  (ObjectReference | DataKey | DataSetReference | ConstraintContentReference | ReportPeriod)
679 679  
680 680  Attribute Documentation:
681 -
682 682  (% style="width:1013.29px" %)
683 683  |**Name**|**Type**|(% style="width:847px" %)**Documentation**
684 684  |id|com:IDType|(% style="width:847px" %)The id attribute holds the identifier of the target reference object as defined in the metadata structure definition. This identifies the target reference of the metadata target that identifes one of the target references, that when taken together, identify the target of the reported metadata.
... ... @@ -699,7 +699,6 @@
699 699  ReportedAttribute+
700 700  
701 701  Element Documentation:
702 -
703 703  (% style="width:1023.29px" %)
704 704  |(% style="width:150px" %)**Name**|(% style="width:202px" %)**Type**|(% style="width:668px" %)**Documentation**
705 705  |(% style="width:150px" %)ReportedAttribute|(% style="width:202px" %)ReportedAttributeType|(% style="width:668px" %)ReportedAttribute provides the details of a reported attribute, including a value and/or child reported attributes.
... ... @@ -707,7 +707,6 @@
707 707  **ReportedAttributeType: **ReportedAttributeType defines the structure for a reported metadata attribute. A value for the attribute can be supplied as either a single value, or multi-lingual text values (either structured or unstructured). An optional set of child metadata attributes is also available if the metadata attribute definition defines nested metadata attributes.
708 708  
709 709  Derivation:
710 -
711 711  * //com:AnnotableType// (extension) 
712 712  ** ReportedAttributeType
713 713  
... ... @@ -718,7 +718,6 @@
718 718  com:Annotations?, (com:Text+ | com:StructuredText+)?, AttributeSet?
719 719  
720 720  Attribute Documentation:
721 -
722 722  (% style="width:996.294px" %)
723 723  |**Name**|(% style="width:170px" %)**Type**|(% style="width:657px" %)**Documentation**
724 724  |id|(% style="width:170px" %)com:IDType|(% style="width:657px" %)The id attribute identifies the metadata attribute that the value is being reported for.
... ... @@ -725,7 +725,6 @@
725 725  |value|(% style="width:170px" %)xs:string|(% style="width:657px" %)The value attribute holds any simple value for the metadata attribute.
726 726  
727 727  Element Documentation:
728 -
729 729  (% style="width:999.294px" %)
730 730  |**Name**|**Type**|(% style="width:670px" %)**Documentation**
731 731  |com:Annotations|com:AnnotationsType|(% style="width:670px" %)Annotations is a reusable element the provides for a collection of annotations. It has been made global so that restrictions of types that extend AnnotatableType my reference it.
... ... @@ -755,7 +755,6 @@
755 755  **//MetadataSetType//: **MetadataSetType is an abstract base type the forms the basis for a metadata structure specific metadata set. It is restricted by the metadata structure definition specific schema to meet its needs.
756 756  
757 757  Derivation:
758 -
759 759  * //com:AnnotableType// (extension) 
760 760  ** //MetadataSetType//
761 761  
... ... @@ -767,7 +767,6 @@
767 767  com:Annotations?, com:Name*, DataProvider?, Report+
768 768  
769 769  Attribute Documentation:
770 -
771 771  (% style="width:1003.29px" %)
772 772  |**Name**|**Type**|(% style="width:607px" %)**Documentation**
773 773  |structureRef|xs:IDREF|(% style="width:607px" %)The structureRef contains a reference to a structural specification in the header of a data or reference metadata message. The structural specification details which structure the data or reference metadata conforms to, as well as providing additional information such as how the data is structure (e.g. which dimension occurs at the observation level for a data set).
... ... @@ -781,7 +781,6 @@
781 781  |publicationPeriod|com: ObservationalTimePeriodType|(% style="width:607px" %)The publicationPeriod specifies the period of publication of the data or metadata in terms of whatever provisioning agreements might be in force (i.e., "Q1 2005" if that is the time of publication for a data set published on a quarterly basis).
782 782  
783 783  Element Documentation:
784 -
785 785  (% style="width:1006.29px" %)
786 786  |**Name**|**Type**|(% style="width:631px" %)**Documentation**
787 787  |com:Annotations|com:AnnotationsType|(% style="width:631px" %)Annotations is a reusable element the provides for a collection of annotations. It has been made global so that restrictions of types that extend AnnotatableType my reference it.
... ... @@ -792,7 +792,6 @@
792 792  **//ReportType//: **ReportType is an abstract base type the forms the basis for a metadata structure definition specific report, based on the defined report structures. This type is restricted in the metadata structure definition specific schema so that the Target and AttributeSet conform to the prescribed report structure.
793 793  
794 794  Derivation:
795 -
796 796  * //com:AnnotableType// (extension) 
797 797  ** //ReportType//
798 798  
... ... @@ -803,13 +803,11 @@
803 803  com:Annotations?, Target, AttributeSet
804 804  
805 805  Attribute Documentation:
806 -
807 807  (% style="width:1003.29px" %)
808 808  |**Name**|**Type**|(% style="width:837px" %)**Documentation**
809 809  |id|com:IDType|(% style="width:837px" %)The id attribute holds the identifier of the report structure as defined in the metadata structure definition. This identifies the report structure which defines the structure of metadata that is being reported. This is optional and not expected to be supplied as the metadata structure definition specific schema will specify a fixed value such that the reference to the report structure will always be available if required for processing.
810 810  
811 811  Element Documentation:
812 -
813 813  (% style="width:1005.29px" %)
814 814  |**Name**|**Type**|(% style="width:695px" %)**Documentation**
815 815  |com:Annotations|com:AnnotationsType|(% style="width:695px" %)Annotations is a reusable element the provides for a collection of annotations. It has been made global so that restrictions of types that extend AnnotatableType my reference it.
... ... @@ -825,13 +825,11 @@
825 825  ReferenceValue+
826 826  
827 827  Attribute Documentation:
828 -
829 829  (% style="width:999.294px" %)
830 830  |**Name**|**Type**|(% style="width:833px" %)**Documentation**
831 831  |id|com:IDType|(% style="width:833px" %)The id attribute holds the identifier of the metadata target as defined in the metadata structure definition. This identifies the metadata target of the report structure that identifies the target object(s) of the reported metadata. This is optional and not expected to be supplied as the metadata structure definition specific schema will specify a fixed value such that the reference to the metadata target will always be available if required for processing.
832 832  
833 833  Element Documentation:
834 -
835 835  (% style="width:999.294px" %)
836 836  |**Name**|**Type**|(% style="width:700px" %)**Documentation**
837 837  |ReferenceValue|//ReferenceValueType//|(% style="width:700px" %)ReferenceValue contains a value for a target reference. When this is taken with its sibling elements, they identify the object or objects to which the reported metadata apply. The content of this will either be a reference to an identifiable object, a data key, a reference to a data set, or a report period. This element is unqualified so that the metadata structure definition specific schema can refine the type of the element such that value can be validated against the format defined in the metadata structure definition.
... ... @@ -845,13 +845,11 @@
845 845  (ObjectReference | DataKey | DataSetReference | ConstraintContentReference | ReportPeriod)
846 846  
847 847  Attribute Documentation:
848 -
849 849  (% style="width:1013.29px" %)
850 850  |**Name**|**Type**|(% style="width:847px" %)**Documentation**
851 851  |id|com:IDType|(% style="width:847px" %)The id attribute holds the identifier of the target reference object reference as defined in the metadata structure definition. This identifies the target reference of the metadata target that identifes one of the target references, that when taken together, identify the target of the reported metadata. This is optional and not expected to be supplied as the metadata structure definition specific schema will specify a fixed value such that the reference to the target object definition will always be available if required for processing.
852 852  
853 853  Element Documentation:
854 -
855 855  (% style="width:1000.29px" %)
856 856  |**Name**|**Type**|(% style="width:563px" %)**Documentation**
857 857  |ObjectReference|//com:ReferenceType//|(% style="width:563px" %)ObjectReference provides a reference to an identifiable object in the SDMX information model. An identifiable object target will utilize this option as the representation of the target reference value. This element is unqualified so that the metadata structure definition specific schema can refine the type of the element such that the type of reference is valid according to the object type specified in the identifiable object target in the metadata structure definition. At the very least, the reference will be specific to the type of object being referenced so that a complete set of reference fields must be provided. In cases where an item object is restricted to be from a particular scheme, this type will be further restricted so that only a valid item reference can be supplied. The structure of this reference is such that it can be generically processed without needing to know what the intended target object type is prior to processing, as this information is part of the reference.
... ... @@ -863,7 +863,6 @@
863 863  **//ReportedAttributeType//: **ReportedAttributeType is an abstract base type that forms the basis for a metadata structure specific metadata attribute. A value for the attribute can be supplied as either a single value, or multi-lingual text values (either structured or unstructured). An optional set of child metadata attributes is also available if the metadata attribute definition defines nested metadata attributes. The metadata structure definition specific schema will refine this type for each metadata attribute such that the content can be validation against what is defined in the metadata structure definition.
864 864  
865 865  Derivation:
866 -
867 867  * //com:AnnotableType// (extension) 
868 868  ** //ReportedAttributeType//
869 869  
... ... @@ -874,7 +874,6 @@
874 874  com:Annotations?, (com:Text+ | com:StructuredText+)?, AttributeSet?
875 875  
876 876  Attribute Documentation:
877 -
878 878  (% style="width:999.294px" %)
879 879  |**Name**|**Type**|(% style="width:660px" %)**Documentation**
880 880  |id|com:IDType|(% style="width:660px" %)The id attribute identifies the metadata attribute that the value is being reported for. This is optional and not expected to be supplied as the metadata structure definition specific schema will specify a fixed value such that the reference to the metadata attribute will always be available if required for processing.
... ... @@ -882,7 +882,6 @@
882 882  |isMetadataAttribute (fixed: true)|xs:boolean|(% style="width:660px" %)The isMetadataAttribute attribute is a fixed boolean (true) and is intended to designate to processing applications that a given element represents a reported attribute. This attribute is qualified (meaning that it will be qualified in an instance with the target namespace) to ensure that it can be properly identified by applications. The purpose of this is to allow applications to identify elements with unknown names as reported attributes so that they may process a metadata structure definition specific instance without knowledge of the underlying metadata structure definition.
883 883  
884 884  Element Documentation:
885 -
886 886  (% style="width:997.294px" %)
887 887  |**Name**|**Type**|(% style="width:668px" %)**Documentation**
888 888  |com:Annotations|com:AnnotationsType|(% style="width:668px" %)Annotations is a reusable element the provides for a collection of annotations. It has been made global so that restrictions of types that extend AnnotatableType my reference it.
... ... @@ -1099,7 +1099,6 @@
1099 1099  A complex type named DataSetType must be created. Its content model will be derived via restriction. If the dimension at the observation level is the time dimension (TIME_PERIOD) the base type of the restriction is dsd:TimeSeriesDataSetType. Otherwise, the base type of the restriction is dsd:DataSetType. The complex type content model will be as follows:
1100 1100  
1101 1101  ~1. A sequence consisting of:
1102 -
1103 1103  * a. An element reference to common:Annotations, with a minimum occurrence of 0
1104 1104  * b. A local element named DataProvider with the type common:DataProviderReferenceType, a form of unqualified and a minimum occurrence of 0
1105 1105  * c. If the data structure defines groups, a local element named Group with a form of unqualified, a minimum occurrence of 0, and a maximum occurrence of unbounded. The type of this element should be the type that is described in the GroupType section which follows.
... ... @@ -1106,7 +1106,6 @@
1106 1106  * d. A choice with a minimum occurrence of 0 consisting of:
1107 1107  ** i. If the dimension at the observation level is not AllDimensions, a local element named Series with a form of unqualified, a maximum occurrence of unbounded, and a type of SeriesType (as defined in the SeriesType section which follows)
1108 1108  ** ii. If the dimension at the observation level is AllDimensions, a local element named Obs with a form of unqualified, a maximum occurrence of unbounded, and a type of ObsType (as defined in the ObsType section which follows)
1109 -
1110 1110  2. If the reporting year start day attribute is not declared in the data structure definition or if it is declared but does not declare an attribute relationship of None, an attribute named REPORTING_YEAR_START_DAY with a type of xs:gMonthDay and a usage of prohibited
1111 1111  3. An attribute for each attribute defined in the data structured definition that declares an attribute relationship of None. The XML attribute name and type are defined according to the general rules defined in the previous section, and the usage is optional
1112 1112  
... ... @@ -1115,9 +1115,7 @@
1115 1115  If the data structure definition defines only one group, a complex type with its name taken from the identifier of the lone group must be defined. This type is used for the Group element in the DataSetType. Its content model will be derived via restriction of the dsd:GroupType. The complex type content model will be as follows:
1116 1116  
1117 1117  ~1. A sequence consisting of:
1118 -
1119 1119  * a. An element reference to common:Annotations, with a minimum occurrence of 0
1120 -
1121 1121  2. An attribute for each dimension referenced by the group. The XML attribute name and type are defined according to the general rules defined in the previous section, and the usage is required
1122 1122  3. If the reporting year start day attribute is not declared in the data structure definition or if it is declared but does not declare an attribute relationship with the group and does not specify the group as an attachment group, an attribute named REPORTING_YEAR_START_DAY with a type of xs:gMonthDay and a usage of prohibited
1123 1123  4. An attribute for each attribute defined in the data structure that declares an attribute relationship with the group or specifies the group as an attachment group. The XML attribute name and type are defined according to the general rules defined in the previous section, and the usage is optional
... ... @@ -1126,9 +1126,7 @@
1126 1126  If the data structure definitions defines more than one group, an abstract complex type with name GroupType must be created. This type is used for the Group element in the DataSetType. Its content model will be derived via restriction of the dsd:GroupType. The complex type content model will be as follows:
1127 1127  
1128 1128  ~1. A sequence consisting of:
1129 -
1130 1130  * a. An element reference to common:Annotations, with a minimum occurrence of 0
1131 -
1132 1132  2. An attribute named type with a type of Group.ID, and a usage of optional
1133 1133  3. An anyAttribute declaration with a namespace of ~#~#local
1134 1134  
... ... @@ -1137,9 +1137,7 @@
1137 1137  For each group defined in the data structure definition, a complex type with its name taken from the group identifier is defined. Its content model will be derived via restriction of the previously defined GroupType. The complex type content model will be as follows:
1138 1138  
1139 1139  ~1. A sequence consisting of:
1140 -
1141 1141  * a. An element reference to common:Annotations, with a minimum occurrence of 0
1142 -
1143 1143  2. An attribute for each dimension referenced by the group. The XML attribute name and type are defined according to the general rules defined in the previous section, and the usage is required
1144 1144  3. If the reporting year start day attribute is not declared in the data structure definition or if it is declared but does not declare an attribute relationship with the group and does not specify the group as an attachment group, an attribute named REPORTING_YEAR_START_DAY with a type of xs:gMonthDay and a usage of prohibited
1145 1145  4. An attribute for each attribute defined in the data structure that declares an attribute relationship with the group or specifies the group as an attachment group. The XML attribute name and type are defined according to the general rules defined in the previous section, and the usage is optional
... ... @@ -1150,9 +1150,7 @@
1150 1150  If the dimension at the observation is not AllDimensions, a complex type name SeriesType must be created. Its content model will be derived via restriction. If the dimension at the observation level is the time dimension (TIME_PERIOD) the base type of the restriction is dsd:TimeSeriesType. Otherwise, the base type of the restriction is dsd:SeriesType. The complex type content model will be as follows:
1151 1151  
1152 1152  ~1. A sequence consisting of:
1153 -
1154 1154  * a. An element reference to common:Annotations, with a minimum occurrence of 0
1155 -
1156 1156  2. A local element named Obs with a form of unqualified, a minimum occurrence of 0, a maximum occurrence of unbounded, and a type of ObsType (as defined in the ObsType section which follows)
1157 1157  3. An attribute for each dimension defined by the data structure definition, except for the dimension at the observation level. The XML attribute name and type are defined according to the general rules defined in the previous section, and the usage is required
1158 1158  4. If the reporting year start day attribute is not declared in the data structure definition or if it is declared and declares an attribute relationship of None, or with a group, or the dimension at the observation level, or specifies a group as an attachment group, an attribute named REPORTING_YEAR_START_DAY with a type of xs:gMonthDay and a usage of prohibited
... ... @@ -1163,9 +1163,7 @@
1163 1163  A complex type name ObsType must be created. Its content model will be derived via restriction. If the dimension at the observation level is the time dimension (TIME_PERIOD) the base type of the restriction is dsd:TimeSeriesObsType. Otherwise, the base type of the restriction is dsd:ObsType. If the explicit measure option is used, this complex type must be abstract. The complex type content model will be as follows:
1164 1164  
1165 1165  ~1. A sequence consisting of:
1166 -
1167 1167  * a. An element reference to common:Annotations, with a minimum occurrence of 0
1168 -
1169 1169  2. If the dimension at the observation level is not the time dimension (TIME_PERIOD) an attribute named TIME_PERIOD with a type of common:TimePeriodType and a usage of prohibited
1170 1170  3. If the dimension at the observation level is not the time dimension (TIME_PERIOD) an attribute for the dimension at the observation level. The XML attribute name and type are defined according to the general rules defined in the previous section, and the usage is required
1171 1171  4. An attribute for the primary measure (OBS_VALUE) defined by the data structure definition. The XML attribute name and type is defined according to the general rules defined in the previous section, and the usage is optional
... ... @@ -1176,9 +1176,7 @@
1176 1176  If the explicit measure option is used, then complex type must be created for every concept which make up the representation of the measure dimension which is the dimension at the observation level. The name of this complex type will be taken from the identifier of the concept. Its content model will be derived via restriction of the ObsType. The complex type content model will be as follows:
1177 1177  
1178 1178  ~1. A sequence consisting of:
1179 -
1180 1180  * a. An element reference to common:Annotations, with a minimum occurrence of 0
1181 -
1182 1182  2. If the core representation of the Concept differs from that of the primary measure, an attribute for the primary measure (OBS_VALUE) defined by the data structure definition, except for the dimension at the observation level. The XML name is defined according to the general rules defined in the previous section, and the usage is optional. The type of the attribute is the type that is generated for the core representation of the measure concept. Note that this representation type must have an explicit derivation from the type resulting from the primary measure. For example, if the primary measure type is xyz:CodeType, then the simple type which is defined for the core representation of the concept must restrict xyz:CodeType or one another type which restricts it
1183 1183  
1184 1184  3. An attribute named type with a type of the simple type generated for the representation of the measure dimension that is the dimension at the observation level, a usage of optional, and a fixed value of the concept identifier.
... ... @@ -1194,7 +1194,6 @@
1194 1194  A complex type that must be named MetadataSetType must be created. Its content model will be derived via restriction of the base type, msd:MetadataSetType. The complex type content model will be as follows:
1195 1195  
1196 1196  ~1. A sequence consisting of:
1197 -
1198 1198  * a. An element reference to common:Annotations, with a minimum occurrence of 0
1199 1199  * b. An element reference to common:Name, with a minimum occurrence of 0 and a maximum occurrence of unbounded
1200 1200  * c. A local element named DataProvider with the type common:DataProviderReferenceType, a form of unqualified and a minimum occurrence of 0
... ... @@ -1205,9 +1205,7 @@
1205 1205  An abstract complex type with a recommended name of TargetType must be created. Its content model will be derived via restriction of the msd:TargetType. The complex type content model will be as follows:
1206 1206  
1207 1207  ~1. A sequence consisting of:
1208 -
1209 1209  * a. A local element named ReferenceValue with a type of msd:ReferenceValueType, a form of unqualified, and a maximum occurrence of unbounded
1210 -
1211 1211  2. An attribute named id with a type of Target.ID, and a usage of optional
1212 1212  
1213 1213  A simple type with a recommended name of Target.ID must be created. This should restrict the common:IDType. For each report structure defined by the metadata structure definition, an enumeration will be created within the restriction with a value of the report structure identifier.
... ... @@ -1217,36 +1217,30 @@
1217 1217  An abstract complex type with a recommended name of [metadata target identifier].ReferenceValueType will be created. Its content model will be derived via restriction of the msd:ReferenceValueType. The complex type content model will be as follows:
1218 1218  
1219 1219  ~1. A choice consisting of:
1220 -
1221 1221  * a. A local element named ObjectReference with a type of common:ReferenceType, and a form of unqualified
1222 1222  * b. A local element named DataKey with a type of common:DataKeyType, and a form of unqualified
1223 1223  * c. A local element named DataSetReference with a type of common:SetReferenceType, and a form of unqualified
1224 1224  * d. A local element named ReportPeriod with a type of common:ObservationalTimePeriodType, and a form of unqualified
1225 -
1226 1226  2. An attribute named id with the type defined previously as [metadata target identifier].TargetObject.ID, and a usage of optional
1227 1227  
1228 1228  For each metadata target defined in the metadata structure definition, a content group with a recommended name of [metadata target identifier] with be defined. Its content model will be as follows:
1229 1229  
1230 1230  ~1. A sequence consisting of:
1231 -
1232 1232  * a. A local element named ReferenceValue with the type previously defined as [metadata target identifier].ReferenceValueType, a form of unqualified, and a minimum and maximum occurrence of the number of target objects defined within the metadata target
1233 1233  
1234 1234  For each target object defined by the metadata target, a complex type that must be named [metadata target identifier].[target object identifier] must be created. Its content model will be derived via restriction of the type previously created as [metadata target identifier].ReferenceValueType type created prior to this. The complex type content model will be as follows:
1235 1235  
1236 1236  ~1. A choice consisting of:
1237 -
1238 1238  * a. If the target object is an identifiable object target, a local element named ObjectReference with a type determined as defined in Identifiable Object Target Type Determination:
1239 1239  * b. If the target object is an key descriptor values target, a local element named DataKey with a type of common:DataKeyType, and a form of unqualified
1240 1240  * c. If the target object is a data set target, a local element named DataSetReference with a type of common:SetReferenceType, and a form of unqualified
1241 1241  * d. If the target object is a constraint target, a local element named ConstraintReference with a type of common:AttachmentConstraintReferenceType, and a form of unqualified
1242 1242  * e. If the target object is report period target, a local element named ReportPeriod with a form of unqualified, and a [[type>>path:#_Simple_/_Primitive]] as defined based on the data type of the local representation according to the general rules defined in the previous section
1243 -
1244 1244  2. An attribute named id with a type previously created as [metadata target identifier].TargetObject.ID, a usage of optional, and fixed value of the target object identifier
1245 1245  
1246 1246  The final complex type (which will be the determined type) is derived by restriction from the reference type determined above. The suggested name of this type is [metadata target identifier].[target object identifier].Reference. The content model of this type will be as follows:
1247 1247  
1248 1248  ~1. A choice consisting of:
1249 -
1250 1250  * a. A sequence consisting of
1251 1251  ** i. A local element named Ref, with a form of unqualified and a the type defined above as is [metadata target].[target object].Ref
1252 1252  ** ii. A local element named URN, with a form of unqualified, a minimum occurrence of 0, and the type defined above as [item scheme agency].[item scheme identifier].[item scheme version].URN
... ... @@ -1278,11 +1278,9 @@
1278 1278  An abstract complex type with a recommended name of ReportType must be created. Its content model will be derived via restriction of the msd:ReportType. The complex type content model will be as follows:
1279 1279  
1280 1280  ~1. A sequence consisting of:
1281 -
1282 1282  * a. An element reference to common:Annotations, with a minimum occurrence of 0
1283 1283  * b. A local element named Target with the type previously defined as TargetType and a form of unqualified
1284 1284  * c. A local element named AttributeSet with no type assigned and a form of unqualified
1285 -
1286 1286  2. An attribute named id with a type previously defined as Report.ID, and a usage of optional
1287 1287  
1288 1288  For each report structure defined in the metadata structure definition, a complex type with its name taken from the report structure identifier must be defined. In order to construct this type, some other complex type must be defined first.
... ... @@ -1292,9 +1292,7 @@
1292 1292  An abstract complex type must be create, with a recommended name of [report structure identifier].TargetType. Its content model will be derived by restriction of the type previously created as TargetType. The content model of this type must be as follows:
1293 1293  
1294 1294  ~1. A sequence consisting of:
1295 -
1296 1296  * a. A local element named ReferenceValue with a type of msd:ReferenceValueType, a form of unqualified, and a maximum occurrence of unbounded
1297 -
1298 1298  2. An attribute named id with the type previously created as [report structure identifier].Target.ID, and a use of optional
1299 1299  
1300 1300  For each metadata target referenced from the report structure, a complex type that must be named [report structure identifier].[metadata target identifier] must be created. This type must derived its content by restriction of the type previously defined as [report structure identifier].TargetType. The content model is as follows:
... ... @@ -1305,12 +1305,11 @@
1305 1305  For every metadata attribute defined by the report structure a complex type must be created with the recommended name of [report structure identifier].[nested metadata attribute identifier]. Note that the recommend name assumes the metadata attribute identifier is the nested identifier for the full hierarchy in which the metadata attribute was defined. This content model of this type is derived from restriction of the msd:ReportedAttributeType. The content of this must consists be as follows:
1306 1306  
1307 1307  ~1. A sequence consisting of:
1308 -* a. An element reference to common:Annotations, with a minimum occurrence of 0
1309 -* b. If the isPresentational flag is not set to true:
1310 -* c. If the determined representation has data type of XHTML, an element reference to common:StructuredText with a maximum occurrence of unbounded
1209 +a. An element reference to common:Annotations, with a minimum occurrence of 0
1210 +* a. If the isPresentational flag is not set to true:
1211 +* b. If the determined representation has data type of XHTML, an element reference to common:StructuredText with a maximum occurrence of unbounded
1311 1311  ** i. If the determined representation has is not XHTML, but has a facet of isMultiLinguale, an element reference to common: Text with a maximum occurrence of unbounded
1312 1312  ** ii. If the metadata attribute defines which child metadata attributes, a local element named AttributeSet with a form of unqualified, and a type as defined according to the rules defined in Attribute Set Complex Type Creation
1313 -
1314 1314  2. An attribute named id with a type of common:IDType, a use of optional, and a fixed value of [metadata attribute identifier], where this identifier is not nested
1315 1315  
1316 1316  If the isPresentational flag is not set to true, and the determined representation is not XHTML and does not have a facet of isMultiLingual, an attribute named value where the [[type>>path:#_Simple_/_Primitive]] is defined according to the general rules defined in the previous section, and the use is required
... ... @@ -1318,13 +1318,11 @@
1318 1318  For each report structure defined in the metadata structure, a complex type that must be named [report structure identifier] must be created. Its content model will be derived via restriction of the previously defined ReportType. The complex type content model will be as follows:
1319 1319  
1320 1320  ~1. A sequence consisting of:
1321 -
1322 1322  * a. An element reference to common:Annotations, with a minimum occurrence of 0
1323 1323  * b. A local element named Target with the type previously defined as [report structure identifier].TargetType, and a form of unqualified. This element must define a uniqueness constraint with a recommended name of [report structure identifier].Target.ReferenceValue.Unique. This uniqueness constraint must contain:
1324 1324  ** i. A selector with an xpath of "*"
1325 1325  ** ii. A field with an xpath of "@id"
1326 1326  * c. A local element named AttributeSet with a form of unqualified and a type as defined according to the rules defined in Attribute Set Complex Type Creation
1327 -
1328 1328  2. An attribute named id with the type previously defined as Report.ID, a use of optional, and a fixed value of [report structure identifier]
1329 1329  
1330 1330  ==== 3.5.3.1 Attribute Set Complex Type Creation ====
... ... @@ -1332,7 +1332,6 @@
1332 1332  An attribute set is created for a report structure or a metadata attribute which contains child metadata attributes. This type is a complex type with a recommend name of [report structure identifier].[nested metadata attribute identifier].AttributeSet, where the metadata attribute section only applies to attribute sets created for metadata attributes and is assumed to consist of the full hierarchy of the metadata attribute's definition. This complex type must consists of:
1333 1333  
1334 1334  ~1. A sequence consisting of:
1335 -
1336 1336  * a. A local element for each metadata attribute defined as a direct child of the object for which the attribute set is being created. The recommended name of this element is [metadata attribute identifier] and it has a form of unqualified. If the metadata attribute defines a minOccurs and maxOccurs, these values are translated to this element. The type of this element is the type previously created as [report structure identifier].[nested metadata attribute identifier].
1337 1337  
1338 1338  = 4. Special data functions =
... ... @@ -1343,6 +1343,7 @@
1343 1343  
1344 1344  A dataset with an action of Append is assumed to be an incremental update. This means that one the information provided explicitly in the message should be altered. Any data attribute or observation value that is to be changed must be provided. However, the absence of an observation value or a data attribute at any level does not imply deletion; instead it is simply implied that the value is to remain unchanged. Therefore, it is valid and acceptable to send a data message with an action of Append which contains only a Series elements with attribute values. In this case, the values for the attributes will be updated. Note that it is not permissible to update data attributes using partial keys (outside of those associated with defined groups). In order to update an attribute, a full key must always be provided even if the message format does not require this.
1345 1345  
1243 +
1346 1346  == 4.2 Deletes ==
1347 1347  
1348 1348  Both the generic and the structure-specific data messages allow for incremental deletion of data. This purpose is noted in the action for the data set, which is either inherited from the header of the data message or explicitly stated at the data set level.
© Semantic R&D Group, 2026