Skip to Content
Last modified by Artur on 2025/09/10 11:19
From version 4.4
edited by Helena
on 2025/06/24 14:50
Change comment: There is no comment for this version
To version 4.5
edited by Helena
on 2025/06/24 14:51
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -389,20 +389,16 @@
389 389  **//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.
390 390  
391 391  Derivation:
392 +* //com:AnnotableType// (extension) 
393 +** //ObsType//
392 392  
393 -//com:AnnotableType// (extension) 
394 - //ObsType//
395 -
396 396  Attributes:
397 -
398 398  type?, TIME_PERIOD?, REPORTING_YEAR_START_DAY?, OBS_VALUE?
399 399  
400 400  Content:
401 -
402 402  com:Annotations?
403 403  
404 404  Attribute Documentation:
405 -
406 406  |**Name**|**Type**|**Documentation**
407 407  |type|com:IDType|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.
408 408  |TIME_PERIOD|com: ObservationalTimePer iodType|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. 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.
... ... @@ -417,21 +417,17 @@
417 417  **//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.
418 418  
419 419  Derivation:
416 +* //com:AnnotableType// (extension) 
417 +** //DataSetType// (restriction) 
418 +*** //TimeSeriesDataSetType//
420 420  
421 -//com:AnnotableType// (extension) 
422 - //DataSetType// (restriction) 
423 - //TimeSeriesDataSetType//
424 -
425 425  Attributes:
426 -
427 427  structureRef, setID?, action?, reportingBeginDate?, reportingEndDate?, validFromDate?, validToDate?, publicationYear?, publicationPeriod?, dataScope, REPORTING_YEAR_START_DAY?
428 428  
429 429  Content:
430 -
431 431  com:Annotations?, DataProvider?, Group*, Series*
432 432  
433 433  Attribute Documentation:
434 -
435 435  |**Name**|**Type**|**Documentation**
436 436  |structureRef|xs:IDREF|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).
437 437  |setID|com:IDType|The setID provides an identification of the data or metadata set.
... ... @@ -456,21 +456,17 @@
456 456  **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.
457 457  
458 458  Derivation:
451 +* //com:AnnotableType// (extension) 
452 +** //SeriesType// (restriction) 
453 +*** TimeSeriesType
459 459  
460 -//com:AnnotableType// (extension) 
461 - //SeriesType// (restriction) 
462 - TimeSeriesType
463 -
464 464  Attributes:
465 -
466 466  REPORTING_YEAR_START_DAY?
467 467  
468 468  Content:
469 -
470 470  com:Annotations?, Obs*
471 471  
472 472  Attribute Documentation:
473 -
474 474  |**Name**|**Type**|**Documentation**
475 475  |REPORTING_YEAR_START_DAY|xs:gMonthDay|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.
476 476