Changes for page Part IV. Data and Metadata Namespaces

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

From 7.1 to 6.1 From 10.2 to 10.1

From version 10.1

edited by Helena
on 2025/06/24 15:20

Change comment: There is no comment for this version

To version 7.1

edited by Helena
on 2025/06/24 15:09

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

@@ -32,6 +32,7 @@
  |(% style="width:487px" %)http:~/~/www.w3.org/2001/XMLSchema|(% style="width:120px" %)xs
  Contents:
++
 Complex Types
  === 2.1.2 Complex Types ===
@@ -44,9 +44,11 @@
  ** DataSetType
  Attributes:
++
  structureRef, setID?, action?, reportingBeginDate?, reportingEndDate?, validFromDate?, validToDate?, publicationYear?, publicationPeriod?
  Content:
++
  com:Annotations?, DataProvider?, Attributes?, Group*, (Series+ | Obs+)?
  Attribute Documentation:
@@ -82,9 +82,11 @@
  ** GroupType
  Attributes:
++
  type
  Content:
++
  com:Annotations?, GroupKey?, Attributes
  Attribute Documentation:
@@ -109,6 +109,7 @@
  ** SeriesType
  Content:
++
  com:Annotations?, SeriesKey, Attributes?, Obs*
  Element Documentation:
@@ -128,6 +128,7 @@
  ** ObsOnlyType
  Content:
++
  com:Annotations?, ObsKey, ObsValue?, Attributes?
  Element Documentation:
@@ -147,6 +147,7 @@
  ** ObsType
  Content:
++
  com:Annotations?, ObsDimension, ObsValue?, Attributes?
  Element Documentation:
@@ -161,6 +161,7 @@
  **ValuesType: **ValuesType is a general structure which contains a collection of data structure definition component values. This type is used to provide both key and attribute collection values.
  Content:
++
  Value+
  Element Documentation:
@@ -172,9 +172,11 @@
  **BaseValueType: **BaseValueType is a general structure which contains a reference to a data structure definition component and a value for that component. In this structure the reference to the component is optional to allow for usages where the actual reference might be provided in another context.
  Attributes:
++
  id?, value
  Content:
++
  {Empty}
  Attribute Documentation:
@@ -192,9 +192,11 @@
  ** ObsValueType
  Attributes:
++
  id?, value
  Content:
++
  {Empty}
  Attribute Documentation:
@@ -212,9 +212,11 @@
  ** ComponentValueType
  Attributes:
++
  id, value
  Content:
++
  {Empty}
  Attribute Documentation:
@@ -233,9 +233,11 @@
  *** TimeSeriesDataSetType
  Attributes:
++
  structureRef, setID?, action?, reportingBeginDate?, reportingEndDate?, validFromDate?, validToDate?, publicationYear?, publicationPeriod?
  Content:
++
  com:Annotations?, DataProvider?, Attributes?, Group*, Series*
  Attribute Documentation:
@@ -271,6 +271,7 @@
  *** TimeSeriesType
  Content:
++
  com:Annotations?, SeriesKey, Attributes?, Obs*
  Element Documentation:
@@ -291,6 +291,7 @@
  *** TimeSeriesObsType
  Content:
++
  com:Annotations?, ObsDimension, ObsValue?, Attributes?
  Element Documentation:
@@ -310,9 +310,11 @@
  ** TimeValueType
  Attributes:
++
  id?, value
  Content:
++
  {Empty}
  Attribute Documentation:
@@ -336,6 +336,7 @@
  |(% style="width:475px" %)http:~/~/www.w3.org/2001/XMLSchema|(% style="width:549px" %)xs
  Contents:
++
 Complex Types
 Simple Type
@@ -349,9 +349,11 @@
  ** //DataSetType//
  Attributes:
++
  structureRef, setID?, action?, reportingBeginDate?, reportingEndDate?, validFromDate?, validToDate?, publicationYear?, publicationPeriod?, dataScope, REPORTING_YEAR_START_DAY?
  Content:
++
  com:Annotations?, DataProvider?, Group*, (Series+ | Obs+)?
  Attribute Documentation:
@@ -388,9 +388,11 @@
  ** //GroupType//
  Attributes:
++
  type?, REPORTING_YEAR_START_DAY?
  Content:
++
  com:Annotations?
  Attribute Documentation:
@@ -413,9 +413,11 @@
  ** //SeriesType//
  Attributes:
++
  TIME_PERIOD?, REPORTING_YEAR_START_DAY?
  Content:
++
  com:Annotations?, Obs*
  Attribute Documentation:
@@ -439,9 +439,11 @@
  ** //ObsType//
  Attributes:
++
  type?, TIME_PERIOD?, REPORTING_YEAR_START_DAY?, OBS_VALUE?
  Content:
++
  com:Annotations?
  Attribute Documentation:
@@ -467,9 +467,11 @@
  *** //TimeSeriesDataSetType//
  Attributes:
++
  structureRef, setID?, action?, reportingBeginDate?, reportingEndDate?, validFromDate?, validToDate?, publicationYear?, publicationPeriod?, dataScope, REPORTING_YEAR_START_DAY?
  Content:
++
  com:Annotations?, DataProvider?, Group*, Series*
  Attribute Documentation:
@@ -506,9 +506,11 @@
  *** TimeSeriesType
  Attributes:
++
  REPORTING_YEAR_START_DAY?
  Content:
++
  com:Annotations?, Obs*
  Attribute Documentation:
@@ -533,9 +533,11 @@
  *** //TimeSeriesObsType//
  Attributes:
++
  TIME_PERIOD, REPORTING_YEAR_START_DAY?, OBS_VALUE?
  Content:
++
  com:Annotations?
  Attribute Documentation:
@@ -594,9 +594,11 @@
  ** MetadataSetType
  Attributes:
++
  structureRef, setID?, action?, reportingBeginDate?, reportingEndDate?, validFromDate?, validToDate?, publicationYear?, publicationPeriod?
  Content:
++
  com:Annotations?, com:Name*, DataProvider?, Report+
  Attribute Documentation:
@@ -630,9 +630,11 @@
  ** ReportType
  Attributes:
++
  id
  Content:
++
  com:Annotations?, Target, AttributeSet
  Attribute Documentation:
@@ -652,9 +652,11 @@
  **TargetType: **TargetType defines the structure of a target. It contains a set of target reference values which when taken together, identify the object or objects to which the reported metadata apply.
  Attributes:
++
  id
  Content:
++
  ReferenceValue+
  Attribute Documentation:
@@ -672,9 +672,11 @@
  **ReferenceValueType: **ReferenceValueType defines the structure of a target object reference value. A target reference value will either be a reference to an identifiable object, a data key, a reference to a data set, or a report period.
  Attributes:
++
  id
  Content:
++
  (ObjectReference | DataKey | DataSetReference | ConstraintContentReference | ReportPeriod)
  Attribute Documentation:
@@ -696,6 +696,7 @@
  **AttributeSetType: **AttributeSetType defines the structure for a collection of reported metadata attributes.
  Content:
++
  ReportedAttribute+
  Element Documentation:
@@ -712,9 +712,11 @@
  ** ReportedAttributeType
  Attributes:
++
  id, value?
  Content:
++
  com:Annotations?, (com:Text+ | com:StructuredText+)?, AttributeSet?
  Attribute Documentation:
@@ -748,6 +748,7 @@
  |(% style="width:492px" %)http:~/~/www.w3.org/2001/XMLSchema|(% style="width:159px" %)xs
  Contents:
++
 Complex Types
  === 2.4.2 Complex Types ===
@@ -764,6 +764,7 @@
  structureRef, setID?, action?, reportingBeginDate?, reportingEndDate?, validFromDate?, validToDate?, publicationYear?, publicationPeriod?
  Content:
++
  com:Annotations?, com:Name*, DataProvider?, Report+
  Attribute Documentation:
@@ -797,9 +797,11 @@
  ** //ReportType//
  Attributes:
++
  id?
  Content:
++
  com:Annotations?, Target, AttributeSet
  Attribute Documentation:
@@ -819,9 +819,11 @@
  **//TargetType//: **TargetType is an abstract base type that forms the basis of a the metadata report's metadata target value. This type is restricted in the metadata structure definition specific schema so that the ReferenceValue elements conform to the targets specified in the metadata target defined in the metadata structure definition.
  Attributes:
++
  id?
  Content:
++
  ReferenceValue+
  Attribute Documentation:
@@ -839,9 +839,11 @@
  **//ReferenceValueType//: **ReferenceValueType is an abstract base type that forms the basis of a target reference value. A target reference value will either be a reference to an identifiable object, a data key, a reference to a data set, or a report period. The choice of these options will be refined to only one according to the definition of the target in the metadata structure definition.
  Attributes:
++
  id?
  Content:
++
  (ObjectReference | DataKey | DataSetReference | ConstraintContentReference | ReportPeriod)
  Attribute Documentation:
@@ -868,9 +868,11 @@
  ** //ReportedAttributeType//
  Attributes:
++
  id?, value?, isMetadataAttribute?
  Content:
++
  com:Annotations?, (com:Text+ | com:StructuredText+)?, AttributeSet?
  Attribute Documentation:
@@ -1000,6 +1000,7 @@
  > </xs:annotation>
  > </xs:enumeration>
++
  === 3.3.5 Representation with Text Format ===
  A representation which defines a text format will result in a simple type or primitive type. The first step is to determine the base type from the text format data type:
@@ -1057,7 +1057,7 @@
  |(% style="width:291px" %)**SDMX Facet**|(% style="width:479px" %)**XML Schema Facet**
  |(% style="width:291px" %)minLength|(% style="width:479px" %)xs:minLength
  |(% style="width:291px" %)maxLength|(% style="width:479px" %)xs:maxLength
--|(% style="width:291px" %)minValue{{footnote}}Note that these options only apply to numeric representations and should be ignored if the data type is non-numeric{{/footnote}}|(% style="width:479px" %)if ExclusiveValueRange: xs:minExclusives, else: xs:minInclusive
++|(% style="width:291px" %)minValue{{footnote}}Note that these options only apply to numeric representations and should be ignored if the data type is non-numeric{{/footnote}}^^{{footnote}}Note that these options only apply to numeric representations and should be ignored if the data type is non-numeric{{/footnote}}^^|(% style="width:479px" %)if ExclusiveValueRange: xs:minExclusives, else: xs:minInclusive
  |(% style="width:291px" %)maxValue^^2^^|(% style="width:479px" %)if ExclusiveValueRange: xs:maxExclusives, else: xs:maxInclusive
  |(% style="width:291px" %)decimals^^2^^|(% style="width:479px" %)xs:fractionDigits
  |(% style="width:291px" %)pattern|(% style="width:479px" %)xs:pattern
@@ -1108,6 +1108,7 @@
  ** 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)
 . 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
++
 . 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
  === 3.4.2 GroupType ===
@@ -1119,8 +1119,11 @@
  * a. An element reference to common:Annotations, with a minimum occurrence of 0
 . 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
++
 . 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
++
 . 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
++
 . An attribute named type with a type of common:IDType, usage of optional, and a fixed value of the identifier of the group
  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:
@@ -1130,6 +1130,7 @@
  * a. An element reference to common:Annotations, with a minimum occurrence of 0
 . An attribute named type with a type of Group.ID, and a usage of optional
++
 . An anyAttribute declaration with a namespace of ~#~#local
  A simple type named Group.ID must be created. This should restrict the common:IDType. For each group defined by the data structure definition, an enumeration will be created within the restriction with a value of the group identifier.
@@ -1141,8 +1141,11 @@
  * a. An element reference to common:Annotations, with a minimum occurrence of 0
 . 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
++
 . 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
++
 . 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
++
 . An attribute named type with a type of Group.ID, usage of optional, and a fixed value of the identifier of the group
  === 3.4.3 SeriesType ===
@@ -1154,8 +1154,11 @@
  * a. An element reference to common:Annotations, with a minimum occurrence of 0
 . 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)
++
 . 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
++
 . 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
++
 . An attribute for each attribute defined in the data structure that declares an attribute relationship with any dimension outside of the dimension at the observation level (so long as it does not also declare 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.
  === 3.4.4 ObsType ===
@@ -1167,8 +1167,11 @@
  * a. An element reference to common:Annotations, with a minimum occurrence of 0
 . 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
++
 . 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
++
 . 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
++
 . An attribute for each attribute defined in the data structure that declares an attribute relationship with the dimension at the observation level or the primary measure (OBS_VALUE). The XML attribute name and type are defined according to the general rules defined in the previous section, and the usage is optional
  An attribute named type. If the explicit measure option is not used, this attribute must have a type of common:IDType and a usage of prohibited. If the explicit measure option is used, this attribute must have a type of the simple type generated for the representation of the measure dimension that is the dimension at the observation level (this will be an simple type with enumerations with values of the concept identifiers which make up the concept scheme that is the representation of the measure dimension) a and a usage of optional
@@ -1305,9 +1305,11 @@
  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:
  ~1. A sequence consisting of:
--* a. An element reference to common:Annotations, with a minimum occurrence of 0
--* b. If the isPresentational flag is not set to true:
--* c. If the determined representation has data type of XHTML, an element reference to common:StructuredText with a maximum occurrence of unbounded
++
++a. An element reference to common:Annotations, with a minimum occurrence of 0
++
++* a. If the isPresentational flag is not set to true:
++* b. If the determined representation has data type of XHTML, an element reference to common:StructuredText with a maximum occurrence of unbounded
  ** 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
  ** 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
@@ -1343,6 +1343,7 @@
  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.
++
  == 4.2 Deletes ==
  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.