Changes for page Part IV. Data and Metadata Namespaces

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

From 4.1 to 4.2 From 5.1 to 6.1

From version 4.2

edited by Helena
on 2025/06/24 14:47

Change comment: There is no comment for this version

To version 5.1

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

Change comment: There is no comment for this version

Raw
Rendered

Summary

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

Details

Page properties

Content

@@ -74,6 +74,7 @@
  **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.
  Derivation:
++
  * //com:AnnotableType// (extension)
  ** GroupType
@@ -106,6 +106,7 @@
  com:Annotations?, SeriesKey, Attributes?, Obs*
  Element Documentation:
++
  |**Name**|**Type**|**Documentation**
  |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.
  |SeriesKey|ValuesType|SeriesKey contains the values for each all dimensions defined in the data structure definition, except for that which is declared to be at the observation level for this data set. This key is required, and every dimension must be provided a value.
@@ -123,6 +123,7 @@
  com:Annotations?, ObsKey, ObsValue?, Attributes?
  Element Documentation:
++
  |**Name**|**Type**|**Documentation**
  |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.
  |ObsKey|ValuesType|ObsKey contains the values for every dimension defined in the data structure definition. A value must be provided for each dimension. This key serves to disambiguate the un-grouped observation within the data set.
@@ -140,6 +140,7 @@
  com:Annotations?, ObsDimension, ObsValue?, Attributes?
  Element Documentation:
++
  |**Name**|**Type**|**Documentation**
  |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.
  |ObsDimension|BaseValueType|ObsDimension holds the key for the grouped observation, i.e. the value of the observation dimension. Note that in this element, the reference to the dimension is optional, since it can be inferred from the structure specification for the data set. This saves having to repeat the value unnecessarily. It is assumed that any application processing the data set will have the information from the structure specification available, so that if a dimension identifier is not supplied here, the proper reference can be applied.
@@ -152,6 +152,7 @@
  Value+
  Element Documentation:
++
  |**Name**|**Type**|**Documentation**
  |Value|ComponentValueType|Value contains a component value and a reference to the component for which a value is being provided.
@@ -158,11 +158,9 @@
  **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:
@@ -175,15 +175,13 @@
  Derivation:
--BaseValueType (restriction)
--   [[image:1750765436897-317.png]]ObsValueType
++* BaseValueType (restriction)
++** ObsValueType
  Attributes:
--
  id?, value
  Content:
--
  {Empty}
  Attribute Documentation:
@@ -196,15 +196,13 @@
  Derivation:
--BaseValueType (restriction)
--   [[image:1750765436899-296.png]]ComponentValueType
++* BaseValueType (restriction)
++** ComponentValueType
  Attributes:
--
  id, value
  Content:
--
  {Empty}
  Attribute Documentation:
@@ -217,16 +217,14 @@
  Derivation:
--//com:AnnotableType// (extension)
--   [[image:1750765436901-853.png]]DataSetType (restriction)
--         [[image:1750765436906-461.png]]TimeSeriesDataSetType
++* //com:AnnotableType// (extension)
++** DataSetType (restriction)
++*** TimeSeriesDataSetType
  Attributes:
--
  structureRef, setID?, action?, reportingBeginDate?, reportingEndDate?, validFromDate?, validToDate?, publicationYear?, publicationPeriod?
  Content:
--
  com:Annotations?, DataProvider?, Attributes?, Group*, Series*
  Attribute Documentation:
@@ -255,12 +255,11 @@
  Derivation:
--//com:AnnotableType// (extension)
--   [[image:1750765436911-979.png]]SeriesType (restriction)
--         [[image:1750765436912-452.png]]TimeSeriesType
++* //com:AnnotableType// (extension)
++** SeriesType (restriction)
++*** TimeSeriesType
  Content:
--
  com:Annotations?, SeriesKey, Attributes?, Obs*
  Element Documentation:
@@ -275,12 +275,11 @@
  Derivation:
--//com:AnnotableType// (extension)
--   [[image:1750765436913-909.png]]ObsType (restriction)
--         [[image:1750765436914-333.png]]TimeSeriesObsType
++* //com:AnnotableType// (extension)
++** ObsType (restriction)
++*** TimeSeriesObsType
  Content:
--
  com:Annotations?, ObsDimension, ObsValue?, Attributes?
  Element Documentation:
@@ -295,15 +295,13 @@
  Derivation:
--BaseValueType (restriction)
--   [[image:1750765436914-771.png]]TimeValueType
++* BaseValueType (restriction)
++** TimeValueType
  Attributes:
--
  id?, value
  Content:
--
  {Empty}
  Attribute Documentation:
@@ -312,14 +312,11 @@
  |id (fixed: TIME_PERIOD)|com:NCNameIDType|The id attribute contains the identifier for the component for which a value is being provided.
  |value|com: ObservationalTimePer iodType|The value attribute contains the provided component value.
--1.
--11. Structure Specific Data Namespace
++== 2.2 Structure Specific Data Namespace ==
  **http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/data/structurespecific**
--1.
--11.
--111. Summary
++=== Summary ===
  Referenced Namespaces:
@@ -329,27 +329,22 @@
  |http:~/~/www.w3.org/2001/XMLSchema|xs
  Contents:
--
 Complex Types
 Simple Type
--1.
--11.
--111. Complex Types
++=== Complex Types ===
  **//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.
  Derivation:
--//com:AnnotableType// (extension)
--   [[image:1750765436915-836.png]]//DataSetType//
++* //com:AnnotableType// (extension)
++** //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:
@@ -380,15 +380,13 @@
  Derivation:
--//com:AnnotableType// (extension)
--   [[image:1750765436916-983.png]]//GroupType//
++* //com:AnnotableType// (extension)
++** //GroupType//
  Attributes:
--
  type?, REPORTING_YEAR_START_DAY?
  Content:
--
  com:Annotations?
  Attribute Documentation:
@@ -406,15 +406,13 @@
  Derivation:
--//com:AnnotableType// (extension)
--   //SeriesType//
++* //com:AnnotableType// (extension)
++** //SeriesType//
  Attributes:
--
  TIME_PERIOD?, REPORTING_YEAR_START_DAY?
  Content:
--
  com:Annotations?, Obs*
  Attribute Documentation:
@@ -433,15 +433,13 @@
  Derivation:
--//com:AnnotableType// (extension)
--   //ObsType//
++* //com:AnnotableType// (extension)
++** //ObsType//
  Attributes:
--
  type?, TIME_PERIOD?, REPORTING_YEAR_START_DAY?, OBS_VALUE?
  Content:
--
  com:Annotations?
  Attribute Documentation:
@@ -461,16 +461,14 @@
  Derivation:
--//com:AnnotableType// (extension)
--   //DataSetType// (restriction)
--         //TimeSeriesDataSetType//
++* //com:AnnotableType// (extension)
++** //DataSetType// (restriction)
++*** //TimeSeriesDataSetType//
  Attributes:
--
  structureRef, setID?, action?, reportingBeginDate?, reportingEndDate?, validFromDate?, validToDate?, publicationYear?, publicationPeriod?, dataScope, REPORTING_YEAR_START_DAY?
  Content:
--
  com:Annotations?, DataProvider?, Group*, Series*
  Attribute Documentation:
@@ -500,16 +500,14 @@
  Derivation:
--//com:AnnotableType// (extension)
--   //SeriesType// (restriction)
--         TimeSeriesType
++* //com:AnnotableType// (extension)
++** //SeriesType// (restriction)
++*** TimeSeriesType
  Attributes:
--
  REPORTING_YEAR_START_DAY?
  Content:
--
  com:Annotations?, Obs*
  Attribute Documentation:
@@ -527,16 +527,14 @@
  Derivation:
--//com:AnnotableType// (extension)
--   //ObsType// (restriction)
--         //TimeSeriesObsType//
++* //com:AnnotableType// (extension)
++** //ObsType// (restriction)
++*** //TimeSeriesObsType//
  Attributes:
--
  TIME_PERIOD, REPORTING_YEAR_START_DAY?, OBS_VALUE?
  Content:
--
  com:Annotations?
  Attribute Documentation:
@@ -551,9 +551,7 @@
  |**Name**|**Type**|**Documentation**
  |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.
--1.
--11.
--111. Simple Types
++=== Simple Types ===
  **DataScopeType: **DataScopeType is an enumeration of the possible validity scopes for a data set. These scopes indicate the level at which the data is stated to be valid.
@@ -567,14 +567,11 @@
  |Dataflow|The data set conforms to the known allowable content constraints applied to the dataflow.
  |ProvisionAgreement|The data set conforms to the known allowable content constraints applied to the provision agreement.
--1.
--11. Generic Metadata Namespace
++== Generic Metadata Namespace ==
  **http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/metadata/generic**
--1.
--11.
--111. Summary
++=== Summary ===
  Referenced Namespaces:
@@ -583,26 +583,21 @@
  |http:~/~/www.w3.org/2001/XMLSchema|xs
  Contents:
--
 Complex Types
--1.
--11.
--111. Complex Types
++=== Complex Types ===
  **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.
  Derivation:
--//com:AnnotableType// (extension)
--   MetadataSetType
++* //com:AnnotableType// (extension)
++** MetadataSetType
  Attributes:
--
  structureRef, setID?, action?, reportingBeginDate?, reportingEndDate?, validFromDate?, validToDate?, publicationYear?, publicationPeriod?
  Content:
--
  com:Annotations?, com:Name*, DataProvider?, Report+
  Attribute Documentation:
@@ -630,15 +630,13 @@
  Derivation:
--//com:AnnotableType// (extension)
--   ReportType
++* //com:AnnotableType// (extension)
++** ReportType
  Attributes:
--
  id
  Content:
--
  com:Annotations?, Target, AttributeSet
  Attribute Documentation:
@@ -656,11 +656,9 @@
  **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:
@@ -676,11 +676,9 @@
  **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:
@@ -700,7 +700,6 @@
  **AttributeSetType: **AttributeSetType defines the structure for a collection of reported metadata attributes.
  Content:
--
  ReportedAttribute+
  Element Documentation:
@@ -712,15 +712,13 @@
  Derivation:
--//com:AnnotableType// (extension)
--   ReportedAttributeType
++* //com:AnnotableType// (extension)
++** ReportedAttributeType
  Attributes:
--
  id, value?
  Content:
--
  com:Annotations?, (com:Text+ | com:StructuredText+)?, AttributeSet?
  Attribute Documentation:
@@ -737,14 +737,11 @@
  |com:StructuredText|com:XHTMLType|StructuredText is used to supply parallel multi-lingual structured (as XHTML) textual values for the reported metadata attribute. This will be used if the text format of the metadata attribute has a type of XHTML and the multi-lingual value is set to true.
  |AttributeSet|AttributeSetType|AttributeSet contains the reported metadata attribute values for the child metadata attributes.
--1.
--11. Structure Specific Metadata Namespace
++== Structure Specific Metadata Namespace ==
  **http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/metadata/structurespecific**
--1.
--11.
--111. Summary
++=== Summary ===
  Referenced Namespaces:
@@ -754,26 +754,21 @@
  |http:~/~/www.w3.org/2001/XMLSchema|xs
  Contents:
--
 Complex Types
--1.
--11.
--111. Complex Types
++=== Complex Types ===
  **//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.
  Derivation:
--//com:AnnotableType// (extension)
--   //MetadataSetType//
++* //com:AnnotableType// (extension)
++** //MetadataSetType//
  Attributes:
--
  structureRef, setID?, action?, reportingBeginDate?, reportingEndDate?, validFromDate?, validToDate?, publicationYear?, publicationPeriod?
  Content:
--
  com:Annotations?, com:Name*, DataProvider?, Report+
  Attribute Documentation:
@@ -801,15 +801,13 @@
  Derivation:
--//com:AnnotableType// (extension)
--   //ReportType//
++* //com:AnnotableType// (extension)
++** //ReportType//
  Attributes:
--
  id?
  Content:
--
  com:Annotations?, Target, AttributeSet
  Attribute Documentation:
@@ -827,11 +827,9 @@
  **//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:
@@ -847,11 +847,9 @@
  **//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:
@@ -872,15 +872,13 @@
  Derivation:
--//com:AnnotableType// (extension)
--   //ReportedAttributeType//
++* //com:AnnotableType// (extension)
++** //ReportedAttributeType//
  Attributes:
--
  id?, value?, isMetadataAttribute?
  Content:
--
  com:Annotations?, (com:Text+ | com:StructuredText+)?, AttributeSet?
  Attribute Documentation:
@@ -898,9 +898,10 @@
  |com:StructuredText|com:XHTMLType|StructuredText is used to supply parallel multi-lingual structured (as XHTML) textual values for the reported metadata attribute. This will be used if the text format of the metadata attribute has a type of XHTML and the multi-lingual value is set to true. If the multi-lingual flag is not set to true, it is expected that the maximum occurrence of this will be refined to be 1 in the metadata structure definition specific schema.
  |AttributeSet|xs:anyType|AttributeSet contains the reported metadata attribute values for the child metadata attributes. This element is unqualified and un-typed so that it can refined by the metadata structure definition specific schema to validate that the reported metadata attributes conform to those prescribed by the metadata attribute definition. The content of this must be element only, and these elements must always represent a reported attribute. Since this can not be strictly enforced in XML Schema, additional steps have been added to make generic processing of this element simpler. When processing this element, any element found with the attribute isMetadataAttribute in this target namespace is assumed to be a reported metadata attribute and can be processed as such.
--1. Mapping to Structure-Specific Schemas
--11. General
++= Mapping to Structure-Specific Schemas =
++== General ==
++
  Data structure and metadata structure-specific schemas are each based on one single core construct found in their respective structure-specific namespaces;
  Data  - http:~/~/www.SDMX.org/resources/SDMXML/schemas/v2_1/data/structurespecific
@@ -909,9 +909,7 @@
  For a metadata structure, only a single schema will be created for the entire structure definition. For data structures, many variations of the base schema are possible, each specific as to how the data is organised. This will be discussed in more details in the specific rules for the data structure schemas.
--1.
--11.
--111. Basic Terminology
++=== Basic Terminology ===
  In the subsequent sections, the following namespace prefixes are used:
@@ -957,8 +957,7 @@
  **XML Attribute:** Refers to the definition of an XML attribute for a complex type (i.e. and xs:attribute element in a xs:complexType element). An attribute must define a name and type (name and type attributes) and may also specify a usage (use attribute).
--1.
--11. Namespace Rules
++== Namespace Rules ==
  Each format specific schema will specify its namespace in the target namespace of the schema (the targetNamespace attribute of the schema). This document also assumes that the root namespace (that which is defined by the xmlns attribute) of the schema will be the same as the target namespace. Therefore any types or global elements referenced in these descriptions without a namespace prefix are assumed to be in the format specific namespace.
@@ -966,21 +966,17 @@
  For the purpose of the descriptions here, the default element form for the schema (as specified in the elementFormDefault attribute of the schema) is “qualified", and the default attribute form (as specified in the attributeFormDefault attribute of the schema) is "unqualified".
--1.
--11. General Rules
++== General Rules ==
  The following section details the general rules which apply to all structure specific schema creation.
--1.
--11.
--111. Component Name Determination
++=== Component Name Determination ===
  When required to create an XML element or attribute, the name for a component is always its identifier. However, the identifier may be inherited. Therefore, the general rules is as follows:
--1. If the component defines an identifier, the element or attribute name is the value of that identifier
--1. Otherwise, the element or attribute name is the identifier of the concept from which it takes its semantic (Note that this is technically the component identifer).
--11.
--111. Representation Determination
++If the component defines an identifier, the element or attribute name is the value of that identifier
++Otherwise, the element or attribute name is the identifier of the concept from which it takes its semantic (Note that this is technically the component identifer).
++Representation Determination
  Every component has a representation associated with it, whether it is defined as a local representation in the component definition, or it is inherited from the concept from which the component takes it semantic (as defined in the concept identity of the component).
@@ -994,40 +994,27 @@
  A text format consists of a data type and an optional collection of facets. It is the combination of these which determine the exact nature of the component representation. An enumeration consists of a reference to an item scheme, for which an enumerated list of possible values can be created.
--1.
--11.
--111. Simple / Primitive Type Determination
++=== Simple / Primitive Type Determination ===
  For any given representation, there exist rules for determining the simple or primitive type which should be used to validate the value. There are no specific requirements to how a simple type is named or if it is referenced or used as an anonymous type. This section simply serves to state the requirements of the type for a component based on its [[determined representation>>path:#_Representation_Determination:]].
  For example, a dimension may inherit its representation for a concept, and the data type of a representation data type may be a String. The simplest solution would be to use the xs:string primitive type. However, an implementer may have chosen to generate simple types for all concepts to avoid having to look up the concept core representation for very component. In this case, the type may be given a name based on the concept and be a simple derivation from the xs:string type that places no further restrictions. The result would be that the type that is actually used for the dimension, although named after the concept, is effectively the required xs:string. These rules are meant to allow such flexibility in how types are created. The only requirement is that the type meet the requirements stated here.
--1.
--11.
--111. Representation with Enumeration
++=== Representation with Enumeration ===
  A representation which defines an enumeration will result in a simple type that is a restriction of the common:IDType. The simple type will define enumerations for each item in the item scheme. The value for these enumerations will be identifier of the item. If desired, the names of the item may be placed in the documentation of the enumeration, but this is not required. Example:
++> <xs:simpleType name="ESTAT.CL_COUNTRY.1.0">
++> <xs:restriction base="common:IDType">
++> <xs:enumeration value="BE">
++> <xs:annotation>
++> <xs:documentation xml:lang="en">Belgium</xs:documentation>
++> </xs:annotation>
++> </xs:enumeration>
--<xs:simpleType name="ESTAT.CL_COUNTRY.1.0">
--<xs:restriction base="common:IDType">
++=== Representation with Text Format ===
--<xs:enumeration value="BE">
--
--<xs:annotation>
--
--<xs:documentation xml:lang="en">Belgium</xs:documentation>
--
--</xs:annotation>
--
--</xs:enumeration>
--
--
--1.
--11.
--111. 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:
  |**SDMX Data Type**|**XML Schema Data Type**
@@ -1070,7 +1070,7 @@
  |Day|xs:gDay
  |Time|xs:time
  |Duration|xs:duration
--|XHTML|N/A[[~[1~]>>path:#_ftn1]]
++|XHTML|N/A{{footnote}}These types are only used in complex types and will be discussed within their appropriate context.{{/footnote}}
  |KeyValues|N/A^^1^^
  |IdentifiableReference|N/A^^1^^
  |DataSetReference|N/A^^1^^
@@ -1081,7 +1081,7 @@
  |**SDMX Facet**|**XML Schema Facet**
  |minLength|xs:minLength
  |maxLength|xs:maxLength
--|minValue[[~[2~]>>path:#_ftn2]]|if ExclusiveValueRange: xs:minExclusives, else: xs:minInclusive
++|minValue{{footnote}}Note that these options only apply to numeric representations and should be ignored if the data type is non-numeric{{/footnote}}|if ExclusiveValueRange: xs:minExclusives, else: xs:minInclusive
  |maxValue^^2^^|if ExclusiveValueRange: xs:maxExclusives, else: xs:maxInclusive
  |decimals^^2^^|xs:fractionDigits
  |pattern|xs:pattern
@@ -1088,9 +1088,7 @@
  Any other facets are informational only, and will not affect the determined type.
--1.
--11.
--111. //Type Names//
++=== Type Names ===
  These rules will only dictate type names where absolutely necessary. In all other cases, it is the decision of the implementer as to how to name or use the type. It is also the implementer's requirement to ensure that any type name is properly unique within its scope. To assist in this, the following recommendations are offered for naming types such that they are unique.
@@ -1117,16 +1117,13 @@
  Only the constructs that will be detailed in the data and metadata structure-specific rules below are required to be in the specified target namespace of the structure-specific schema. So long as any other generated type conforms to the rules specified, it may exist in any namespace.
--1.
--11. Data Structure Specific Schema
++== Data Structure Specific Schema ==
  Separate schemas will be created for the data structure depending on which dimension occurs at the observation level, and whether explicit measures are used in the case that the observation dimension is the measure dimension. The recommended target namespace of the data structured specific schema is: [Data Structure URN]:ObsLevelDim:[Observation Dimensions](:explicit)?. Note that the explicit trailer is only used when the measure dimension is used at the observation level and the explicit measure concepts are to be used.
  The rules for generating the data structure specific-schema are broken into sections based on the level within the structure (i.e. data set, group, series, observation). Each section will state the rules for each variation of the structure specific format.
--1.
--11.
--111. DataSetType
++=== DataSetType ===
  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:
@@ -1139,9 +1139,10 @@
 . 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>>path:#_Component_Name_Determination]] and [[type>>path:#_Simple_/_Primitive]] are defined according to the general rules defined in the previous section, and the usage is optional
--11.
--111. GroupType
++11.
++=== GroupType ===
++
  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:
 . A sequence consisting of:
@@ -1168,9 +1168,9 @@
 . 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>>path:#_Component_Name_Determination]] and [[type>>path:#_Simple_/_Primitive]] 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
--11.
--111. SeriesType
++=== SeriesType ===
++
  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:
 . A sequence consisting of:
@@ -1179,9 +1179,9 @@
 . An attribute for each dimension defined by the data structure definition, except for the dimension at the observation level. The XML attribute [[name>>path:#_Component_Name_Determination]] and [[type>>path:#_Simple_/_Primitive]] 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>>path:#_Component_Name_Determination]] and [[type>>path:#_Simple_/_Primitive]] are defined according to the general rules defined in the previous section, and the usage is optional
--11.
--111. ObsType
++=== ObsType ===
++
  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:
 . A sequence consisting of:
@@ -1204,9 +1204,7 @@
  The rules for generating the data structure specific-schema are broken into sections based on the level within the structure (i.e. metadata set, metadata targets, reports, metadata attributes). These rules will recommend names for generated types, and will refer back to these names throughout the description. These names are simply recommendations that should produce a unique name, but there is no requirement to use them. When a name is required, it will be made clear this is the case.
--1.
--11.
--111. MetadataSetType
++=== MetadataSetType ===
  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:
@@ -1258,9 +1258,11 @@
 . A local element named Ref, with a form of unqualified and a the type defined above as is [metadata target].[target object].Ref
 . 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
 . A local element named URN, with a form of unqualified, and the type defined above as [item scheme agency].[item scheme identifier].[item scheme version].URN
--111.
--1111. Identifiable Object Target Type Determination
++
++
++==== Identifiable Object Target Type Determination ====
++
  An identifiable object target is meant to reference an SDMX identifiable object. In the metadata structure specific schema, the complex type which defines the reference is restricted according to the local representation and object type of the identifiable object target. If the identifiable object target does not provide an enumeration in its local representation, then the complex type for the target object is the specific reference type from the common namespace, based on the object type defined by the target object. For example, if the object type is DataProivder, the type will be common:DataProviderReferenceType. The general rule for the name of this type is common:[object type]ReferenceType.
  If the target object defines an enumeration in its local representation, then the declared object type must be for the items contained the enumeration's referenced item scheme. If this is not true, the reference type as defined above is the type for the target object.
@@ -1277,9 +1277,9 @@
 . An attribute named maintinableParentID with a type of common:IDType, a use of required, and a fixed value of the identifier of the item scheme referenced from the enumeration
 . An attribute named maintainableParentVersion with a type of common:VersionType, a use of optional, and a fixed value of the version of the item scheme referenced from the enumeration
 . An attribute named id, with a use of option, and the type defined above as [item scheme agency].[item scheme identifier].[item scheme version].ID.
--11.
--111. ReportType
++=== ReportType ===
++
  A simple type with a recommend name of Report.ID must be created. This must 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.
  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:
@@ -1327,34 +1327,28 @@
 .
 . 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
 . An attribute named id with the type previously defined as Report.ID, a use of optional, and a fixed value of [report structure identifier]
--11.
--111.
--1111. Attribute Set Complex Type Creation
++=== Attribute Set Complex Type Creation ===
++
  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:
 . A sequence consisting of:
 . 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].
--1. Special data functions
--11. Updates
++= Special data functions =
++== Updates ==
++
  Both the generic and the structure-specific data messages allow for incremental updating 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.
--
  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.
--1.
--11. Deletes
++== 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.
--
  A dataset with an action of Delete is assumed to be an incremental deletion. The deletion is assumed to take place of the lowest level of detail provided in the message. For example, if a delete message is sent with only a data set element, the entire data set will be deleted. On the other hand, if that data set contains a data attribute, only that data attribute value will be deleted. This same dynamic continues through the data set hierarchy. A data set containing only a series with no data attributes or observations will result in that entire series (all observations and data attributes) being deleted. If the series contains data attributes, only the supplied data attributes for that series will be deleted. Finally, if a series contains observations, then only the specified observations will be deleted. If an entire observation is to be deleted (value and data attributes), only the observation dimension should be provided. If only the observation value or particular data attributes are to be deleted, then these should be specified for the observation. Note that a group can only be used to delete the data attributes associated with it. Although the format might not require it, a full key must be provided to delete a series or observation. It is not permissible to wild card a key in order to delete more than one series or observation. Finally, to delete a data attribute or observation value it is recommended that the value to be deleted be supplied; however, it is only required that any valid value be provided.
--
  ----
--[[~[1~]>>path:#_ftnref1]] These types are only used in complex types and will be discussed within their appropriate context.
--
--[[~[2~]>>path:#_ftnref2]] Note that these options only apply to numeric representations and should be ignored if the data type is non-numeric
++{{putFootnotes/}}