Changes for page Part IV. Data and Reference Metadata Namespaces

Summary

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

Details

Page properties

Content

...	...	@@ -48,29 +48,31 @@
48	48
49	49	Attribute Documentation:
50	50
51		-|**Name**|**Type**|**Documentation**|
52		-|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).|
53		-|setID|IDType|The setID provides an identification of the data or metadata set.|
54		-|action|ActionType|The action attribute indicates whether the file is merging, replacing, or deleting.|
55		-|reportingBeginDate|BasicTimePeriodType|The reportingBeginDate indicates the inclusive start time of the data reported in the data or metadata set.|
56		-|reportingEndDate|BasicTimePeriodType|The reportingEndDate indicates the inclusive end time of the data reported in the data or metadata set.|
57		-|validFromDate|xs:dateTime|The validFromDate indicates the inclusive start time indicating the validity of the information in the data or metadata set.|
58		-|validToDate|xs:dateTime|The validToDate indicates the inclusive end time indicating the validity of the information in the data or metadata set.|
59		-|publicationYear|xs:gYear|The publicationYear holds the ISO 8601 four-digit year.|
60		-|publicationPeriod|ObservationalTimePeriodType|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).|
	51	+(% style="width:1152.29px" %)
	52	+|**Name**|**Type**|**Documentation**
	53	+|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).
	54	+|setID|IDType|The setID provides an identification of the data or metadata set.
	55	+|action|ActionType|The action attribute indicates whether the file is merging, replacing, or deleting.
	56	+|reportingBeginDate|BasicTimePeriodType|The reportingBeginDate indicates the inclusive start time of the data reported in the data or metadata set.
	57	+|reportingEndDate|BasicTimePeriodType|The reportingEndDate indicates the inclusive end time of the data reported in the data or metadata set.
	58	+|validFromDate|xs:dateTime|The validFromDate indicates the inclusive start time indicating the validity of the information in the data or metadata set.
	59	+|validToDate|xs:dateTime|The validToDate indicates the inclusive end time indicating the validity of the information in the data or metadata set.
	60	+|publicationYear|xs:gYear|The publicationYear holds the ISO 8601 four-digit year.
	61	+|publicationPeriod|ObservationalTimePeriodType|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).
61	61
62	62	Element Documentation:
63	63
64		-|**Name**|**Type**|**Documentation**|
65		-|Annotations|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 may reference it.|
66		-|DataProvider|DataProviderReferenceType|DataProvider contains a reference to the provider for the data set.|
67		-|Atts|*AttsType*|Atts contains a set of data or metadata attribute values with an attachment level of none (i.e. data set level) or reported against a partial set of dimension values.|
68		-|Group|*GroupType*|Group contains a reference to a defined group in the data structure definition along with its key (if necessary) and values for the attributes which are associated with the group. An attribute is associated to a group by either an explicit group relationship or by a group attachment when the attribute has a relationship with a dimension which is a member of this group.|
69		-|Series|*SeriesType*|Series contains a collection of observations that share a common key (set of dimension values). The key of a series is every dimension defined in the data structure definition, save the dimension at the observation level. In addition to the key and observations, the series contains values for data and metadata attributes which have a relationship with any dimension that is part of the series key, so long as the attribute does not specify an attachment group or also has a relationship with the dimension declared to be at the observation level.|
70		-|Obs|*ObsType*|Obs is an un-grouped observation. This observation has a key which is a set of values for all dimensions declared in the data structure definition. In addition to the key, the value of the observation can be provided along with values for all data and metadata attributes which have an association with the observation or any dimension (so long as it does not specify a group attachment).|
71		-|Metadata|MetadataSetType|Allows for attachment of reference metadata against to the data set.|
	65	+(% style="width:1154.29px" %)
	66	+|**Name**|**Type**|**Documentation**
	67	+|Annotations|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 may reference it.
	68	+|DataProvider|DataProviderReferenceType|DataProvider contains a reference to the provider for the data set.
	69	+|Atts|*AttsType*|Atts contains a set of data or metadata attribute values with an attachment level of none (i.e. data set level) or reported against a partial set of dimension values.
	70	+|Group|*GroupType*|Group contains a reference to a defined group in the data structure definition along with its key (if necessary) and values for the attributes which are associated with the group. An attribute is associated to a group by either an explicit group relationship or by a group attachment when the attribute has a relationship with a dimension which is a member of this group.
	71	+|Series|*SeriesType*|Series contains a collection of observations that share a common key (set of dimension values). The key of a series is every dimension defined in the data structure definition, save the dimension at the observation level. In addition to the key and observations, the series contains values for data and metadata attributes which have a relationship with any dimension that is part of the series key, so long as the attribute does not specify an attachment group or also has a relationship with the dimension declared to be at the observation level.
	72	+|Obs|*ObsType*|Obs is an un-grouped observation. This observation has a key which is a set of values for all dimensions declared in the data structure definition. In addition to the key, the value of the observation can be provided along with values for all data and metadata attributes which have an association with the observation or any dimension (so long as it does not specify a group attachment).
	73	+|Metadata|MetadataSetType|Allows for attachment of reference metadata against to the data set.
72	72
73		-***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 data or metadata 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.
	75	+//**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 data or metadata 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.
74	74
75	75	Derivation:
76	76
...	...	@@ -85,17 +85,19 @@
85	85
86	86	Attribute Documentation:
87	87
88		-|**Name**|**Type**|**Documentation**|
89		-|type|IDType|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.|
	90	+(% style="width:1044.29px" %)
	91	+|**Name**|**Type**|(% style="width:913px" %)**Documentation**
	92	+|type|IDType|(% style="width:913px" %)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.
90	90
91	91	Element Documentation:
92	92
93		-|**Name**|**Type**|**Documentation**|
94		-|Annotations|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 may reference it.|
95		-|Comp|*CompType*|Comp contains the details of group level attributes that have complex representation and cannot be expressed as XML attributes.|
96		-|Metadata|MetadataSetType|Allows for attachment of reference metadata against to the group.|
	96	+(% style="width:1055.29px" %)
	97	+|**Name**|**Type**|(% style="width:717px" %)**Documentation**
	98	+|Annotations|AnnotationsType|(% style="width:717px" %)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 may reference it.
	99	+|Comp|//CompType//|(% style="width:717px" %)Comp contains the details of group level attributes that have complex representation and cannot be expressed as XML attributes.
	100	+|Metadata|MetadataSetType|(% style="width:717px" %)Allows for attachment of reference metadata against to the group.
97	97
98		-***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. Note, if the schema is generated against a dataflow with a dimension constraint, they key includes only the dimensions defined in the dimension constraint. In addition to observations, values can be provided for data and metadata 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 a 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 derive 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.
	102	+//**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. Note, if the schema is generated against a dataflow with a dimension constraint, they key includes only the dimensions defined in the dimension constraint. In addition to observations, values can be provided for data and metadata 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 a 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 derive 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.
99	99
100	100	Derivation:
101	101
...	...	@@ -110,18 +110,20 @@
110	110
111	111	Attribute Documentation:
112	112
113		-|**Name**|**Type**|**Documentation**|
114		-|TIME_PERIOD|ObservationalTimePeriodType|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.|
	117	+(% style="width:1084.29px" %)
	118	+|**Name**|**Type**|**Documentation**
	119	+|TIME_PERIOD|ObservationalTimePeriodType|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.
115	115
116	116	Element Documentation:
117	117
118		-|**Name**|**Type**|**Documentation**|
119		-|Annotations|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 may reference it.|
120		-|Comp|*CompType*|Comp contains the details of series level attributes that have complex representation and cannot be expressed as XML attributes.|
121		-|Obs|*ObsType*| |
122		-|Metadata|MetadataSetType|Allows for attachment of reference metadata against to the series.|
	123	+(% style="width:1093.29px" %)
	124	+|**Name**|**Type**|**Documentation**
	125	+|Annotations|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 may reference it.
	126	+|Comp|//CompType//|Comp contains the details of series level attributes that have complex representation and cannot be expressed as XML attributes.
	127	+|Obs|//ObsType//|
	128	+|Metadata|MetadataSetType|Allows for attachment of reference metadata against to the series.
123	123
124		-***CompType*:** CompType is the abstract base for any component value (e.g. a data or metadata attribute, or a measure) that cannot be represented as an XML attribute. For example, a repeated value, a text value in multiple languages, or a value with structured text (XHTML) cannot be expressed as an XML attribute. This type is meant to be restricted based on the component to restrict the cardinality and type of its Value element to conform to the component definition. The type of the value element should be restricted to common:SimpleValueType, common:TextValueType, or common:StructuredValueType. In addition, the id attribute should be restricted to be a fixed value with the component identifier. This restricted type based on the component can then be used on Comp elements by using the xsi:type to state the component being expressed and refine the contents of the element to the values allowed by the component.
	130	+//**CompType:**// CompType is the abstract base for any component value (e.g. a data or metadata attribute, or a measure) that cannot be represented as an XML attribute. For example, a repeated value, a text value in multiple languages, or a value with structured text (XHTML) cannot be expressed as an XML attribute. This type is meant to be restricted based on the component to restrict the cardinality and type of its Value element to conform to the component definition. The type of the value element should be restricted to common:SimpleValueType, common:TextValueType, or common:StructuredValueType. In addition, the id attribute should be restricted to be a fixed value with the component identifier. This restricted type based on the component can then be used on Comp elements by using the xsi:type to state the component being expressed and refine the contents of the element to the values allowed by the component.
125	125
126	126	Derivation:
127	127
...	...	@@ -136,16 +136,18 @@
136	136
137	137	Attribute Documentation:
138	138
139		-|**Name**|**Type**|**Documentation**|
140		-|id|NCNameIDType| |
	145	+(% style="width:1007.29px" %)
	146	+|(% style="width:157px" %)**Name**|(% style="width:291px" %)**Type**|(% style="width:556px" %)**Documentation**
	147	+|(% style="width:157px" %)id|(% style="width:291px" %)NCNameIDType|(% style="width:556px" %)
141	141
142	142	Element Documentation:
143	143
144		-|**Name**|**Type**|**Documentation**|
145		-|Annotations|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 may reference it.|
146		-|Value|*ValueType*| |
	151	+(% style="width:1015.29px" %)
	152	+|**Name**|**Type**|(% style="width:684px" %)**Documentation**
	153	+|Annotations|AnnotationsType|(% style="width:684px" %)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 may reference it.
	154	+|Value|//ValueType//|(% style="width:684px" %)
147	147
148		-***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 derive 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 data and metadata 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.
	156	+//**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 derive 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 data and metadata 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.
149	149
150	150	Derivation:
151	151
...	...	@@ -160,16 +160,18 @@
160	160
161	161	Attribute Documentation:
162	162
163		-|**Name**|**Type**|**Documentation**|
164		-|type|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.|
165		-|TIME_PERIOD|ObservationalTimePeriodType|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.|
	171	+(% style="width:1008.29px" %)
	172	+|**Name**|**Type**|(% style="width:648px" %)**Documentation**
	173	+|type|IDType|(% style="width:648px" %)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.
	174	+|TIME_PERIOD|ObservationalTimePeriodType|(% style="width:648px" %)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.
166	166
167	167	Element Documentation:
168	168
169		-|**Name**|**Type**|**Documentation**|
170		-|Annotations|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 may reference it.|
171		-|Comp|*CompType*|Comp contains the details of observation measures or attributes that have complex representation and cannot be expressed as XML attributes.|
172		-|Metadata|MetadataSetType|Allows for attachment of reference metadata against to the observation.|
	178	+(% style="width:1020.29px" %)
	179	+|**Name**|**Type**|**Documentation**
	180	+|Annotations|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 may reference it.
	181	+|Comp|//CompType//|Comp contains the details of observation measures or attributes that have complex representation and cannot be expressed as XML attributes.
	182	+|Metadata|MetadataSetType|Allows for attachment of reference metadata against to the observation.
173	173
174	174	***AttsType*:** AttsType is the abstract type which defines a structure which is used to group a collection of data or metadata attributes which have a key in common. The key for a attribute collection is a subset of the dimension defined in the data structure definition. This is also used for data set level attributes (i.e. those with an attribute relationship of none). In this case, the subset of dimensions is empty. Data structure definition schemas will derive a type based on this that is specific to the data structure definition. The dimension values which make up the key will be represented with local (non-namespace qualified) XML attributes. The metadata attribute values associated with the key dimensions will be expressed as XML local (non-namespace qualified) attributes if they are simple values (e.g. enumerated, dates, numbers) and are not repeatable. Metadata attributes that are repeatable, or do not have simple values (e.g. text) will be expressed using the Comp element. These dimensions and simple attributes are 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.
175	175
...	...	@@ -186,29 +186,31 @@
186	186
187	187	Attribute Documentation:
188	188
189		-|**Name**|**Type**|**Documentation**|
190		-|TIME_PERIOD|ObservationalTimePeriodType|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.|
	199	+(% style="width:1013.29px" %)
	200	+|**Name**|**Type**|**Documentation**
	201	+|TIME_PERIOD|ObservationalTimePeriodType|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.
191	191
192	192	Element Documentation:
193	193
194		-|**Name**|**Type**|**Documentation**|
195		-|Annotations|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 may reference it.|
196		-|Comp|*CompType*|Comp contains the details of the data or metadata attributes that have complex representation and cannot be expressed as XML attributes.|
	205	+(% style="width:1020.29px" %)
	206	+|**Name**|**Type**|**Documentation**
	207	+|Annotations|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 may reference it.
	208	+|Comp|//CompType//|Comp contains the details of the data or metadata attributes that have complex representation and cannot be expressed as XML attributes.
197	197
198	198	== 2.2 Generic Reference Metadata Namespace ==
199	199
200		-**http://www.sdmx.org/resources/sdmxml/schemas/v3_1/metadata/generic****
	212	+[[http:~~/~~/www.sdmx.org/resources/sdmxml/schemas/v3_1/metadata/generic>>http://www.sdmx.org/resources/sdmxml/schemas/v3_1/metadata/generic**]]
201	201
202	202	=== 2.2.1 Summary ===
203	203
204	204	Referenced Namespaces:
205	205
206		-|**Namespace**|**Prefix**|
207		-|http://www.sdmx.org/resources/sdmxml/schemas/v3\_1/common|common|
208		-|<http://www.w3.org/2001/XMLSchema>|xs|
	218	+(% style="width:1037.29px" %)
	219	+|(% style="width:516px" %)**Namespace**|(% style="width:518px" %)**Prefix**
	220	+|(% style="width:516px" %)http:~/~/www.sdmx.org/resources/sdmxml/schemas/v3\_1/common|(% style="width:518px" %)common
	221	+|(% style="width:516px" %)<http:~/~/www.w3.org/2001/XMLSchema>|(% style="width:518px" %)xs
209	209
210	210	Contents:
211		-
212	212	1 Global Element
213	213	3 Complex Types
214	214
...	...	@@ -238,26 +238,28 @@
238	238
239	239	Attribute Documentation:
240	240
241		-|**Name**|**Type**|**Documentation**|
242		-|id|IDType|The id is the identifier for the object.|
243		-|urn|MetadataSetUrnType|The urn attribute holds a valid SDMX Registry URN (see SDMX Registry Specification for details).|
244		-|uri|xs:anyURI|The uri attribute holds a URI that contains a link to a resource with additional information about the object, such as a web page. This uri is not a SDMX message.|
245		-|version|VersionType|This version attribute holds a version number (see common:VersionType definition for details). If not supplied, artefact is considered to be un-versioned.|
246		-|validFrom|xs:dateTime|The validFrom attribute provides the inclusive start date for providing supplemental validity information about the version.|
247		-|validTo|xs:dateTime|The validTo attribute provides the inclusive end date for providing supplemental validity information about the version.|
248		-|agencyID|NestedNCNameIDType|The agencyID must be provided and identifies the maintenance agency of the object.|
249		-|isExternalReference (default: false)|xs:boolean|The isExternalReference attribute, if true, indicates that the actual object is not defined the corresponding element, rather its full details are defined elsewhere - indicated by either the registryURL, the repositoryURL, or the structureURL. The purpose of this is so that each structure message does not have to redefine object that are already defined elsewhere. If the isExternalReference attribute is not set, then it is assumed to be false, and the object should contain the full definition of its contents. If more than one of the registryURL, the repositoryURL, and the structureURL are supplied, then the application processing the object can choose the method it finds best suited to retrieve the details of the object.|
250		-|serviceURL|xs:anyURI|The serviceURL attribute indicates the URL of an SDMX SOAP web service from which the details of the object can be retrieved. Note that this can be a registry or and SDMX structural metadata repository, as they both implement that same web service interface.|
251		-|structureURL|xs:anyURI|The structureURL attribute indicates the URL of a SDMX-ML structure message (in the same version as the source document) in which the externally referenced object is contained. Note that this may be a URL of an SDMX RESTful web service which will return the referenced object.|
252		-|isPartialLanguage (default: false)|xs:boolean|The isPartialLanguage attribute, if true, indicates that the object doesn't contain the complete set of all available languages, e.g., when obtained as a response to a GET query that requested specific languages through the HTTP header Accept-Language.|
	253	+(% style="width:1051.29px" %)
	254	+|**Name**|**Type**|(% style="width:669px" %)**Documentation**
	255	+|id|IDType|(% style="width:669px" %)The id is the identifier for the object.
	256	+|urn|MetadataSetUrnType|(% style="width:669px" %)The urn attribute holds a valid SDMX Registry URN (see SDMX Registry Specification for details).
	257	+|uri|xs:anyURI|(% style="width:669px" %)The uri attribute holds a URI that contains a link to a resource with additional information about the object, such as a web page. This uri is not a SDMX message.
	258	+|version|VersionType|(% style="width:669px" %)This version attribute holds a version number (see common:VersionType definition for details). If not supplied, artefact is considered to be un-versioned.
	259	+|validFrom|xs:dateTime|(% style="width:669px" %)The validFrom attribute provides the inclusive start date for providing supplemental validity information about the version.
	260	+|validTo|xs:dateTime|(% style="width:669px" %)The validTo attribute provides the inclusive end date for providing supplemental validity information about the version.
	261	+|agencyID|NestedNCNameIDType|(% style="width:669px" %)The agencyID must be provided and identifies the maintenance agency of the object.
	262	+|isExternalReference (default: false)|xs:boolean|(% style="width:669px" %)The isExternalReference attribute, if true, indicates that the actual object is not defined the corresponding element, rather its full details are defined elsewhere - indicated by either the registryURL, the repositoryURL, or the structureURL. The purpose of this is so that each structure message does not have to redefine object that are already defined elsewhere. If the isExternalReference attribute is not set, then it is assumed to be false, and the object should contain the full definition of its contents. If more than one of the registryURL, the repositoryURL, and the structureURL are supplied, then the application processing the object can choose the method it finds best suited to retrieve the details of the object.
	263	+|serviceURL|xs:anyURI|(% style="width:669px" %)The serviceURL attribute indicates the URL of an SDMX SOAP web service from which the details of the object can be retrieved. Note that this can be a registry or and SDMX structural metadata repository, as they both implement that same web service interface.
	264	+|structureURL|xs:anyURI|(% style="width:669px" %)The structureURL attribute indicates the URL of a SDMX-ML structure message (in the same version as the source document) in which the externally referenced object is contained. Note that this may be a URL of an SDMX RESTful web service which will return the referenced object.
	265	+|isPartialLanguage (default: false)|xs:boolean|(% style="width:669px" %)The isPartialLanguage attribute, if true, indicates that the object doesn't contain the complete set of all available languages, e.g., when obtained as a response to a GET query that requested specific languages through the HTTP header Accept-Language.
253	253
254	254	Element Documentation:
255	255
256		-|**Name**|**Type**|**Documentation**|
257		-|Annotations|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 may reference it.|
258		-|Link|LinkType|Allows for the linking of other resources to identifiable objects. For example, if there is reference metadata associated with a structure, a link to the metadata report can be dynamically inserted in the structure metadata.|
259		-|Name|TextType|Name provides for a human-readable name for the object. This may be provided in multiple, parallel language-equivalent forms.|
260		-|Description|TextType|Description provides for a longer human-readable description of the object. This may be provided in multiple, parallel language-equivalent forms.|
	269	+(% style="width:1057.29px" %)
	270	+|**Name**|**Type**|**Documentation**
	271	+|Annotations|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 may reference it.
	272	+|Link|LinkType|Allows for the linking of other resources to identifiable objects. For example, if there is reference metadata associated with a structure, a link to the metadata report can be dynamically inserted in the structure metadata.
	273	+|Name|TextType|Name provides for a human-readable name for the object. This may be provided in multiple, parallel language-equivalent forms.
	274	+|Description|TextType|Description provides for a longer human-readable description of the object. This may be provided in multiple, parallel language-equivalent forms.
261	261
262	262	**MetadataSetType:** MetadataSetType describes the structure for a metadata set, which contains a collection of reported metadata against a set of targets. The targets should conform to the restrictions described by the metadata provision or the metadataflow. Note that this is maintainable, and as such must specify in agency. In this case, the agency is the metadata provider. If a metadata provision agreement is referenced, it is assumed that the metadata provider described in the provision will be the same as the agency for this set.
263	263
...	...	@@ -280,34 +280,36 @@
280	280
281	281	Attribute Documentation:
282	282
283		-|**Name**|**Type**|**Documentation**|
284		-|id|IDType|The id is the identifier for the object.|
285		-|urn|MetadataSetUrnType|The urn attribute holds a valid SDMX Registry URN (see SDMX Registry Specification for details).|
286		-|uri|xs:anyURI|The uri attribute holds a URI that contains a link to a resource with additional information about the object, such as a web page. This uri is not a SDMX message.|
287		-|version|VersionType|This version attribute holds a version number (see common:VersionType definition for details). If not supplied, artefact is considered to be un-versioned.|
288		-|validFrom|xs:dateTime|The validFrom attribute provides the inclusive start date for providing supplemental validity information about the version.|
289		-|validTo|xs:dateTime|The validTo attribute provides the inclusive end date for providing supplemental validity information about the version.|
290		-|agencyID|NestedNCNameIDType|The agencyID must be provided and identifies the maintenance agency of the object.|
291		-|isExternalReference (default: false)|xs:boolean|The isExternalReference attribute, if true, indicates that the actual object is not defined the corresponding element, rather its full details are defined elsewhere - indicated by either the registryURL, the repositoryURL, or the structureURL. The purpose of this is so that each structure message does not have to redefine object that are already defined elsewhere. If the isExternalReference attribute is not set, then it is assumed to be false, and the object should contain the full definition of its contents. If more than one of the registryURL, the repositoryURL, and the structureURL are supplied, then the application processing the object can choose the method it finds best suited to retrieve the details of the object.|
292		-|serviceURL|xs:anyURI|The serviceURL attribute indicates the URL of an SDMX SOAP web service from which the details of the object can be retrieved. Note that this can be a registry or and SDMX structural metadata repository, as they both implement that same web service interface.|
293		-|structureURL|xs:anyURI|The structureURL attribute indicates the URL of a SDMX-ML structure message (in the same version as the source document) in which the externally referenced object is contained. Note that this may be a URL of an SDMX RESTful web service which will return the referenced object.|
294		-|isPartialLanguage (default: false)|xs:boolean|The isPartialLanguage attribute, if true, indicates that the object doesn't contain the complete set of all available languages, e.g., when obtained as a response to a GET query that requested specific languages through the HTTP header Accept-Language.|
295		-|reportingBeginDate|BasicTimePeriodType|The reportingBeginDate indicates the inclusive start time of the data reported in the data or metadata set.|
296		-|reportingEndDate|BasicTimePeriodType|The reportingEndDate indicates the inclusive end time of the data reported in the data or metadata set.|
297		-|publicationYear|xs:gYear|The publicationYear holds the ISO 8601 four-digit year.|
298		-|publicationPeriod|ObservationalTimePeriodType|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).|
	297	+(% style="width:1050.29px" %)
	298	+|**Name**|**Type**|(% style="width:622px" %)**Documentation**
	299	+|id|IDType|(% style="width:622px" %)The id is the identifier for the object.
	300	+|urn|MetadataSetUrnType|(% style="width:622px" %)The urn attribute holds a valid SDMX Registry URN (see SDMX Registry Specification for details).
	301	+|uri|xs:anyURI|(% style="width:622px" %)The uri attribute holds a URI that contains a link to a resource with additional information about the object, such as a web page. This uri is not a SDMX message.
	302	+|version|VersionType|(% style="width:622px" %)This version attribute holds a version number (see common:VersionType definition for details). If not supplied, artefact is considered to be un-versioned.
	303	+|validFrom|xs:dateTime|(% style="width:622px" %)The validFrom attribute provides the inclusive start date for providing supplemental validity information about the version.
	304	+|validTo|xs:dateTime|(% style="width:622px" %)The validTo attribute provides the inclusive end date for providing supplemental validity information about the version.
	305	+|agencyID|NestedNCNameIDType|(% style="width:622px" %)The agencyID must be provided and identifies the maintenance agency of the object.
	306	+|isExternalReference (default: false)|xs:boolean|(% style="width:622px" %)The isExternalReference attribute, if true, indicates that the actual object is not defined the corresponding element, rather its full details are defined elsewhere - indicated by either the registryURL, the repositoryURL, or the structureURL. The purpose of this is so that each structure message does not have to redefine object that are already defined elsewhere. If the isExternalReference attribute is not set, then it is assumed to be false, and the object should contain the full definition of its contents. If more than one of the registryURL, the repositoryURL, and the structureURL are supplied, then the application processing the object can choose the method it finds best suited to retrieve the details of the object.
	307	+|serviceURL|xs:anyURI|(% style="width:622px" %)The serviceURL attribute indicates the URL of an SDMX SOAP web service from which the details of the object can be retrieved. Note that this can be a registry or and SDMX structural metadata repository, as they both implement that same web service interface.
	308	+|structureURL|xs:anyURI|(% style="width:622px" %)The structureURL attribute indicates the URL of a SDMX-ML structure message (in the same version as the source document) in which the externally referenced object is contained. Note that this may be a URL of an SDMX RESTful web service which will return the referenced object.
	309	+|isPartialLanguage (default: false)|xs:boolean|(% style="width:622px" %)The isPartialLanguage attribute, if true, indicates that the object doesn't contain the complete set of all available languages, e.g., when obtained as a response to a GET query that requested specific languages through the HTTP header Accept-Language.
	310	+|reportingBeginDate|BasicTimePeriodType|(% style="width:622px" %)The reportingBeginDate indicates the inclusive start time of the data reported in the data or metadata set.
	311	+|reportingEndDate|BasicTimePeriodType|(% style="width:622px" %)The reportingEndDate indicates the inclusive end time of the data reported in the data or metadata set.
	312	+|publicationYear|xs:gYear|(% style="width:622px" %)The publicationYear holds the ISO 8601 four-digit year.
	313	+|publicationPeriod|ObservationalTimePeriodType|(% style="width:622px" %)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).
299	299
300	300	Element Documentation:
301	301
302		-|**Name**|**Type**|**Documentation**|
303		-|Annotations|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 may reference it.|
304		-|Link|LinkType|Allows for the linking of other resources to identifiable objects. For example, if there is reference metadata associated with a structure, a link to the metadata report can be dynamically inserted in the structure metadata.|
305		-|Name|TextType|Name provides for a human-readable name for the object. This may be provided in multiple, parallel language-equivalent forms.|
306		-|Description|TextType|Description provides for a longer human-readable description of the object. This may be provided in multiple, parallel language-equivalent forms.|
307		-|MetadataProvision<br/>Agreement|MetadataProvisionAgree<br/>mentReferenceType|Metadataflow provides a reference to the metadata provision agreement the metadata set is being reported against.|
308		-|Metadataflow|MetadataflowReference<br/>Type|Metadataflow provides a reference to the metadataflow the metadata set is being reported against.|
309		-|Target|WildcardUrnType|Target references the target structures for which metadata is being reported. These must conform with the constraints defined by the metadata provision agreement and/or the metadataflow.|
310		-|Attribute|AttributeType|Att elements hold the reported metadata attribute values being reported in the metadata set. These conform to the metadata structure definition.|
	317	+(% style="width:1054.29px" %)
	318	+|**Name**|(% style="width:185px" %)**Type**|(% style="width:412px" %)**Documentation**
	319	+|Annotations|(% style="width:185px" %)AnnotationsType|(% style="width:412px" %)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 may reference it.
	320	+|Link|(% style="width:185px" %)LinkType|(% style="width:412px" %)Allows for the linking of other resources to identifiable objects. For example, if there is reference metadata associated with a structure, a link to the metadata report can be dynamically inserted in the structure metadata.
	321	+|Name|(% style="width:185px" %)TextType|(% style="width:412px" %)Name provides for a human-readable name for the object. This may be provided in multiple, parallel language-equivalent forms.
	322	+|Description|(% style="width:185px" %)TextType|(% style="width:412px" %)Description provides for a longer human-readable description of the object. This may be provided in multiple, parallel language-equivalent forms.
	323	+|MetadataProvision<br/>Agreement|(% style="width:185px" %)MetadataProvisionAgree<br/>mentReferenceType|(% style="width:412px" %)Metadataflow provides a reference to the metadata provision agreement the metadata set is being reported against.
	324	+|Metadataflow|(% style="width:185px" %)MetadataflowReference<br/>Type|(% style="width:412px" %)Metadataflow provides a reference to the metadataflow the metadata set is being reported against.
	325	+|Target|(% style="width:185px" %)WildcardUrnType|(% style="width:412px" %)Target references the target structures for which metadata is being reported. These must conform with the constraints defined by the metadata provision agreement and/or the metadataflow.
	326	+|Attribute|(% style="width:185px" %)AttributeType|(% style="width:412px" %)Att elements hold the reported metadata attribute values being reported in the metadata set. These conform to the metadata structure definition.
311	311
312	312	**AttributeType:** AttributeType defines the structure for a reported metadata attribute. A value for the attribute can be supplied as either a single value (enumerated or non-enumerated single value), or multi-lingual text values (either structured or unstructured). Optional child attributes are also available if the metadata attribute definition defines nested metadata attributes.
313	313
...	...	@@ -324,17 +324,19 @@
324	324
325	325	Attribute Documentation:
326	326
327		-|**Name**|**Type**|**Documentation**|
328		-|id|IDType|The id attribute identifies the metadata attribute that the value is being reported for.|
	343	+(% style="width:1037.29px" %)
	344	+|(% style="width:113px" %)**Name**|(% style="width:162px" %)**Type**|(% style="width:760px" %)**Documentation**
	345	+|(% style="width:113px" %)id|(% style="width:162px" %)IDType|(% style="width:760px" %)The id attribute identifies the metadata attribute that the value is being reported for.
329	329
330	330	Element Documentation:
331	331
332		-|**Name**|**Type**|**Documentation**|
333		-|Annotations|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 may reference it.|
334		-|Value|xs:anySimpleType|Value holds any simple value (enumerated or not) for the metadata attribute. It can be repeated if this metadata attribute allows for multiple values.|
335		-|Text|TextType|Text is used to supply parallel multi-lingual textual values for the reported metadata attribute. This will be used if the text format of the metadata attribute has a type of string, and the multi-lingual value is set to true.|
336		-|StructuredText|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.|
337		-|Attribute|AttributeType|Att contains the reported metadata attribute values for the child metadata attributes.|
	349	+(% style="width:1095.29px" %)
	350	+|**Name**|**Type**|(% style="width:821px" %)**Documentation**
	351	+|Annotations|AnnotationsType|(% style="width:821px" %)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 may reference it.
	352	+|Value|xs:anySimpleType|(% style="width:821px" %)Value holds any simple value (enumerated or not) for the metadata attribute. It can be repeated if this metadata attribute allows for multiple values.
	353	+|Text|TextType|(% style="width:821px" %)Text is used to supply parallel multi-lingual textual values for the reported metadata attribute. This will be used if the text format of the metadata attribute has a type of string, and the multi-lingual value is set to true.
	354	+|StructuredText|XHTMLType|(% style="width:821px" %)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.
	355	+|Attribute|AttributeType|(% style="width:821px" %)Att contains the reported metadata attribute values for the child metadata attributes.
338	338
339	339	= 3 Mapping to Structure-Specific Schemas =
340	340
...	...	@@ -349,10 +349,10 @@
349	349	In the subsequent sections, the following namespace prefixes are used:
350	350
351	351	|**Namespace**|**Prefix**|
352		-|http://www.w3.org/2001/XMLSchema|xs|
353		-|http://www.sdmx.org/resources/sdmxml/schemas/v3_1/common|common|
354		-|http://www.sdmx.org/resources/sdmxml/schemas/v3_1/data/structurespecific|dsd|
355		-|<http://www.sdmx.org/resources/sdmxml/schemas/v3_1/metadata/generic>|metadata|
	370	+|http:~/~/www.w3.org/2001/XMLSchema|xs|
	371	+|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v3_1/common|common|
	372	+|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v3_1/data/structurespecific|dsd|
	373	+|<http:~/~/www.sdmx.org/resources/sdmxml/schemas/v3_1/metadata/generic>|metadata|
356	356
357	357	It is assumed that in order to use this guide, the reader is familiar with schema terminology. However, for convenience the following is list of the terminology used here:
358	358
...	...	@@ -416,8 +416,8 @@
416	416	The representation of a component is determined by the following precedence:
417	417
418	418	1. The local representation defined by the component
419		-2. The core representation defined in the concept from which the component takes its semantic
420		-3. A default representation of an un-faceted text format with a data type of String.
	437	+1. The core representation defined in the concept from which the component takes its semantic
	438	+1. A default representation of an un-faceted text format with a data type of String.
421	421
422	422	The representation will either define a text format, an enumeration with an enumeration format, or a union of the former with the value of a irrelevant representation ‘’ (tilde).
423	423
...	...	@@ -442,7 +442,6 @@
442	442	</xs:annotation>
443	443	</xs:enumeration>
444	444
445		-
446	446	=== 3.3.5 Representation with Value List Enumeration ===
447	447
448	448	A representation which defines an enumeration from a value list will result in a simple type that is a restriction of the xs:string data type. The simple type will define enumerations for each value item in the value list. 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.
...	...	@@ -457,58 +457,60 @@
457	457
458	458	If the representation is not simple, see the rules in the following section for complex text formats. If the representation is simple, the first step is to determine the base type from the text format data type:
459	459
460		-|**SDMX Data Type**|**XML Schema Data Type**|
461		-|String|xs:string|
462		-|AlphaNumeric|common:AlphaNumericType|
463		-|Alpha|common:AlphaType|
464		-|Numeric|common:NumericType|
465		-|BigInteger|xs:integer|
466		-|Integer|xs:int|
467		-|Long|xs:long|
468		-|Short|xs:short|
469		-|Decimal|xs:decimal|
470		-|Float|xs:float|
471		-|Double|xs:double|
472		-|Boolean|xs:Boolean|
473		-|URI|xs:anyURI|
474		-|Count|xs:integer|
475		-|InclusiveValueRange|xs:decimal|
476		-|ExclusiveValueRange|xs: decimal|
477		-|Incremental|xs: decimal|
478		-|ObservationalTimePeriod|common:ObservationalTimePeriodType|
479		-|StandardTimePeriod|common:StandardTimePeriodType|
480		-|BasicTimePeriod|common:BasicTimePeriodType|
481		-|GregorianTimePeriod|common:GregorianTimePeriodType|
482		-|GregorianYear|xs:gYear|
483		-|GregorianYearMonth|xs:gYearMonth|
484		-|GregorianDay|xs:date|
485		-|ReportingTimePeriod|common:ReportingTimePeriodType|
486		-|ReportingYear|common:ReportingYearType|
487		-|ReportingSemester|common:ReportingSemesterType|
488		-|ReportingTrimester|common:ReportingTrimesterType|
489		-|ReportingQuarter|common:ReportingQuarterType|
490		-|ReportingMonth|common:ReportingMonthType|
491		-|ReportingWeek|common:ReportingWeekType|
492		-|ReportingDay|common:ReportingDayType|
493		-|DateTime|xs:dateTime|
494		-|TimeRange|common:TimeRangeType|
495		-|Month|xs:gMonth|
496		-|MonthDay|xs:gMonthDay|
497		-|Day|xs:gDay|
498		-|Time|xs:time|
499		-|Duration|xs:duration|
500		-|GeospatialInformation|xs:string|
501		-|XHTML|See the following section for complex representations|
	477	+(% style="width:679.294px" %)
	478	+|(% style="width:286px" %)**SDMX Data Type**|(% style="width:390px" %)**XML Schema Data Type**
	479	+|(% style="width:286px" %)String|(% style="width:390px" %)xs:string
	480	+|(% style="width:286px" %)AlphaNumeric|(% style="width:390px" %)common:AlphaNumericType
	481	+|(% style="width:286px" %)Alpha|(% style="width:390px" %)common:AlphaType
	482	+|(% style="width:286px" %)Numeric|(% style="width:390px" %)common:NumericType
	483	+|(% style="width:286px" %)BigInteger|(% style="width:390px" %)xs:integer
	484	+|(% style="width:286px" %)Integer|(% style="width:390px" %)xs:int
	485	+|(% style="width:286px" %)Long|(% style="width:390px" %)xs:long
	486	+|(% style="width:286px" %)Short|(% style="width:390px" %)xs:short
	487	+|(% style="width:286px" %)Decimal|(% style="width:390px" %)xs:decimal
	488	+|(% style="width:286px" %)Float|(% style="width:390px" %)xs:float
	489	+|(% style="width:286px" %)Double|(% style="width:390px" %)xs:double
	490	+|(% style="width:286px" %)Boolean|(% style="width:390px" %)xs:Boolean
	491	+|(% style="width:286px" %)URI|(% style="width:390px" %)xs:anyURI
	492	+|(% style="width:286px" %)Count|(% style="width:390px" %)xs:integer
	493	+|(% style="width:286px" %)InclusiveValueRange|(% style="width:390px" %)xs:decimal
	494	+|(% style="width:286px" %)ExclusiveValueRange|(% style="width:390px" %)xs: decimal
	495	+|(% style="width:286px" %)Incremental|(% style="width:390px" %)xs: decimal
	496	+|(% style="width:286px" %)ObservationalTimePeriod|(% style="width:390px" %)common:ObservationalTimePeriodType
	497	+|(% style="width:286px" %)StandardTimePeriod|(% style="width:390px" %)common:StandardTimePeriodType
	498	+|(% style="width:286px" %)BasicTimePeriod|(% style="width:390px" %)common:BasicTimePeriodType
	499	+|(% style="width:286px" %)GregorianTimePeriod|(% style="width:390px" %)common:GregorianTimePeriodType
	500	+|(% style="width:286px" %)GregorianYear|(% style="width:390px" %)xs:gYear
	501	+|(% style="width:286px" %)GregorianYearMonth|(% style="width:390px" %)xs:gYearMonth
	502	+|(% style="width:286px" %)GregorianDay|(% style="width:390px" %)xs:date
	503	+|(% style="width:286px" %)ReportingTimePeriod|(% style="width:390px" %)common:ReportingTimePeriodType
	504	+|(% style="width:286px" %)ReportingYear|(% style="width:390px" %)common:ReportingYearType
	505	+|(% style="width:286px" %)ReportingSemester|(% style="width:390px" %)common:ReportingSemesterType
	506	+|(% style="width:286px" %)ReportingTrimester|(% style="width:390px" %)common:ReportingTrimesterType
	507	+|(% style="width:286px" %)ReportingQuarter|(% style="width:390px" %)common:ReportingQuarterType
	508	+|(% style="width:286px" %)ReportingMonth|(% style="width:390px" %)common:ReportingMonthType
	509	+|(% style="width:286px" %)ReportingWeek|(% style="width:390px" %)common:ReportingWeekType
	510	+|(% style="width:286px" %)ReportingDay|(% style="width:390px" %)common:ReportingDayType
	511	+|(% style="width:286px" %)DateTime|(% style="width:390px" %)xs:dateTime
	512	+|(% style="width:286px" %)TimeRange|(% style="width:390px" %)common:TimeRangeType
	513	+|(% style="width:286px" %)Month|(% style="width:390px" %)xs:gMonth
	514	+|(% style="width:286px" %)MonthDay|(% style="width:390px" %)xs:gMonthDay
	515	+|(% style="width:286px" %)Day|(% style="width:390px" %)xs:gDay
	516	+|(% style="width:286px" %)Time|(% style="width:390px" %)xs:time
	517	+|(% style="width:286px" %)Duration|(% style="width:390px" %)xs:duration
	518	+|(% style="width:286px" %)GeospatialInformation|(% style="width:390px" %)xs:string
	519	+|(% style="width:286px" %)XHTML|(% style="width:390px" %)See the following section for complex representations
502	502
503	503	If the text format does not specify any further facets, then the determined type is the listed type or a type which derives from the listed type without placing any addition restrictions on it. However, if one or more facets are specified, then a simple type based on the listed type is necessary. The simple type derives via restriction from the listed type and adds facets according to the following table (the values are mapped as is):
504	504
505		-|**SDMX Facet**|**XML Schema Facet**|
506		-|minLength|xs:minLength|
507		-|maxLength|xs:maxLength|
508		-|minValue[^1]|if ExclusiveValueRange: xs:minExclusives, else: xs:minInclusive|
509		-|maxValue[^1]|if ExclusiveValueRange: xs:maxExclusives, else: xs:maxInclusive|
510		-|decimals[^1]|xs:fractionDigits|
511		-|pattern|xs:pattern|
	523	+(% style="width:1007.29px" %)
	524	+|(% style="width:267px" %)**SDMX Facet**|(% style="width:729px" %)**XML Schema Facet**
	525	+|(% style="width:267px" %)minLength|(% style="width:729px" %)xs:minLength
	526	+|(% style="width:267px" %)maxLength|(% style="width:729px" %)xs:maxLength
	527	+|(% style="width:267px" %)minValue[^1]|(% style="width:729px" %)if ExclusiveValueRange: xs:minExclusives, else: xs:minInclusive
	528	+|(% style="width:267px" %)maxValue[^1]|(% style="width:729px" %)if ExclusiveValueRange: xs:maxExclusives, else: xs:maxInclusive
	529	+|(% style="width:267px" %)decimals[^1]|(% style="width:729px" %)xs:fractionDigits
	530	+|(% style="width:267px" %)pattern|(% style="width:729px" %)xs:pattern
512	512
513	513	[^1]: Note that these options only apply to numeric representations and should be ignored if the data type is non-numeric.
514	514
...	...	@@ -546,35 +546,36 @@
546	546
547	547	For convenience the common schema provides the union types for the following data types.
548	548
549		-|**SDMX Data Type**|**XML Schema Data Type**|
550		-|AlphaNumeric|common:AlphaNumericOrNotApplicableType|
551		-|Alpha|common:AlphaOrNotApplicableType|
552		-|Numeric|common:NumericOrNotApplicableType|
553		-|BigInteger|common:IntegerOrNotApplicableType|
554		-|Integer|common:IntOrNotApplicableType|
555		-|Long|common:LongOrNotApplicableType|
556		-|Short|common:ShortOrNotApplicableType|
557		-|Decimal|common:DecimalOrNotApplicableType|
558		-|Float|common:FloatOrNotApplicableType|
559		-|Double|common:DoubleOrNotApplicableType|
560		-|Boolean|common:BooleanOrNotApplicableType|
561		-|Count|common:IntegerOrNotApplicableType|
562		-|InclusiveValueRange|common:DecimalOrNotApplicableType|
563		-|ExclusiveValueRange|common:DecimalOrNotApplicableType|
564		-|Incremental|common:DecimalOrNotApplicableType|
565		-|ObservationalTimePeriod|common:ObservationalTimePeriodOrNotApplicableType|
566		-|StandardTimePeriod|common:StandardTimePeriodOrNotApplicableType|
567		-|BasicTimePeriod|common:BasicTimePeriodType|
568		-|GregorianTimePeriod|common:GregorianTimePeriodOrNotApplicableType|
569		-|ReportingTimePeriod|common:ReportingTimePeriodOrNotApplicableType|
570		-|ReportingYear|common:ReportingYearOrNotApplicableType|
571		-|ReportingSemester|common:ReportingSemesterOrNotApplicableType|
572		-|ReportingTrimester|common:ReportingTrimesterOrNotApplicableType|
573		-|ReportingQuarter|common:ReportingQuarterOrNotApplicableType|
574		-|ReportingMonth|common:ReportingMonthOrNotApplicableType|
575		-|ReportingWeek|common:ReportingWeekOrNotApplicableType|
576		-|ReportingDay|common:ReportingDayOrNotApplicableType|
577		-|TimeRange|common:TimeRangeOrNotApplicableType|
	568	+(% style="width:747.294px" %)
	569	+|**SDMX Data Type**|(% style="width:418px" %)**XML Schema Data Type**
	570	+|AlphaNumeric|(% style="width:418px" %)common:AlphaNumericOrNotApplicableType
	571	+|Alpha|(% style="width:418px" %)common:AlphaOrNotApplicableType
	572	+|Numeric|(% style="width:418px" %)common:NumericOrNotApplicableType
	573	+|BigInteger|(% style="width:418px" %)common:IntegerOrNotApplicableType
	574	+|Integer|(% style="width:418px" %)common:IntOrNotApplicableType
	575	+|Long|(% style="width:418px" %)common:LongOrNotApplicableType
	576	+|Short|(% style="width:418px" %)common:ShortOrNotApplicableType
	577	+|Decimal|(% style="width:418px" %)common:DecimalOrNotApplicableType
	578	+|Float|(% style="width:418px" %)common:FloatOrNotApplicableType
	579	+|Double|(% style="width:418px" %)common:DoubleOrNotApplicableType
	580	+|Boolean|(% style="width:418px" %)common:BooleanOrNotApplicableType
	581	+|Count|(% style="width:418px" %)common:IntegerOrNotApplicableType
	582	+|InclusiveValueRange|(% style="width:418px" %)common:DecimalOrNotApplicableType
	583	+|ExclusiveValueRange|(% style="width:418px" %)common:DecimalOrNotApplicableType
	584	+|Incremental|(% style="width:418px" %)common:DecimalOrNotApplicableType
	585	+|ObservationalTimePeriod|(% style="width:418px" %)common:ObservationalTimePeriodOrNotApplicableType
	586	+|StandardTimePeriod|(% style="width:418px" %)common:StandardTimePeriodOrNotApplicableType
	587	+|BasicTimePeriod|(% style="width:418px" %)common:BasicTimePeriodType
	588	+|GregorianTimePeriod|(% style="width:418px" %)common:GregorianTimePeriodOrNotApplicableType
	589	+|ReportingTimePeriod|(% style="width:418px" %)common:ReportingTimePeriodOrNotApplicableType
	590	+|ReportingYear|(% style="width:418px" %)common:ReportingYearOrNotApplicableType
	591	+|ReportingSemester|(% style="width:418px" %)common:ReportingSemesterOrNotApplicableType
	592	+|ReportingTrimester|(% style="width:418px" %)common:ReportingTrimesterOrNotApplicableType
	593	+|ReportingQuarter|(% style="width:418px" %)common:ReportingQuarterOrNotApplicableType
	594	+|ReportingMonth|(% style="width:418px" %)common:ReportingMonthOrNotApplicableType
	595	+|ReportingWeek|(% style="width:418px" %)common:ReportingWeekOrNotApplicableType
	596	+|ReportingDay|(% style="width:418px" %)common:ReportingDayOrNotApplicableType
	597	+|TimeRange|(% style="width:418px" %)common:TimeRangeOrNotApplicableType
578	578
579	579	=== 3.3.8 Representation for Intentionally Missing Measure and Attribute Values ===
580	580
...	...	@@ -613,35 +613,36 @@
613	613
614	614	For convenience the common schema provides the union types for the following data types.
615	615
616		-|**SDMX Data Type**|**XML Schema Data Type**|
617		-|AlphaNumeric|common:AlphaNumericOrMissingType|
618		-|Alpha|common:AlphaOrMissingType|
619		-|Numeric|common:NumericOrMissingType|
620		-|BigInteger|common:IntegerOrMissingType|
621		-|Integer|common:IntOrMissingType|
622		-|Long|common:LongOrMissingType|
623		-|Short|common:ShortOrMissingType|
624		-|Decimal|common:DecimalOrMissingType|
625		-|Float|common:FloatOrMissingType|
626		-|Double|common:DoubleOrMissingType|
627		-|Boolean|common:BooleanOrMissingType|
628		-|Count|common:IntegerOrMissingType|
629		-|InclusiveValueRange|common:DecimalOrMissingType|
630		-|ExclusiveValueRange|common:DecimalOrMissingType|
631		-|Incremental|common:DecimalOrMissingType|
632		-|ObservationalTimePeriod|common:ObservationalTimePeriodOrMissingType|
633		-|StandardTimePeriod|common:StandardTimePeriodOrMissingType|
634		-|BasicTimePeriod|common:BasicTimePeriodType|
635		-|GregorianTimePeriod|common:GregorianTimePeriodOrMissingType|
636		-|ReportingTimePeriod|common:ReportingTimePeriodOrMissingType|
637		-|ReportingYear|common:ReportingYearOrMissingType|
638		-|ReportingSemester|common:ReportingSemesterOrMissingType|
639		-|ReportingTrimester|common:ReportingTrimesterOrMissingType|
640		-|ReportingQuarter|common:ReportingQuarterOrMissingType|
641		-|ReportingMonth|common:ReportingMonthOrMissingType|
642		-|ReportingWeek|common:ReportingWeekOrMissingType|
643		-|ReportingDay|common:ReportingDayOrMissingType|
644		-|TimeRange|common:TimeRangeOrMissingType|
	636	+(% style="width:804.294px" %)
	637	+|(% style="width:279px" %)**SDMX Data Type**|(% style="width:522px" %)**XML Schema Data Type**
	638	+|(% style="width:279px" %)AlphaNumeric|(% style="width:522px" %)common:AlphaNumericOrMissingType
	639	+|(% style="width:279px" %)Alpha|(% style="width:522px" %)common:AlphaOrMissingType
	640	+|(% style="width:279px" %)Numeric|(% style="width:522px" %)common:NumericOrMissingType
	641	+|(% style="width:279px" %)BigInteger|(% style="width:522px" %)common:IntegerOrMissingType
	642	+|(% style="width:279px" %)Integer|(% style="width:522px" %)common:IntOrMissingType
	643	+|(% style="width:279px" %)Long|(% style="width:522px" %)common:LongOrMissingType
	644	+|(% style="width:279px" %)Short|(% style="width:522px" %)common:ShortOrMissingType
	645	+|(% style="width:279px" %)Decimal|(% style="width:522px" %)common:DecimalOrMissingType
	646	+|(% style="width:279px" %)Float|(% style="width:522px" %)common:FloatOrMissingType
	647	+|(% style="width:279px" %)Double|(% style="width:522px" %)common:DoubleOrMissingType
	648	+|(% style="width:279px" %)Boolean|(% style="width:522px" %)common:BooleanOrMissingType
	649	+|(% style="width:279px" %)Count|(% style="width:522px" %)common:IntegerOrMissingType
	650	+|(% style="width:279px" %)InclusiveValueRange|(% style="width:522px" %)common:DecimalOrMissingType
	651	+|(% style="width:279px" %)ExclusiveValueRange|(% style="width:522px" %)common:DecimalOrMissingType
	652	+|(% style="width:279px" %)Incremental|(% style="width:522px" %)common:DecimalOrMissingType
	653	+|(% style="width:279px" %)ObservationalTimePeriod|(% style="width:522px" %)common:ObservationalTimePeriodOrMissingType
	654	+|(% style="width:279px" %)StandardTimePeriod|(% style="width:522px" %)common:StandardTimePeriodOrMissingType
	655	+|(% style="width:279px" %)BasicTimePeriod|(% style="width:522px" %)common:BasicTimePeriodType
	656	+|(% style="width:279px" %)GregorianTimePeriod|(% style="width:522px" %)common:GregorianTimePeriodOrMissingType
	657	+|(% style="width:279px" %)ReportingTimePeriod|(% style="width:522px" %)common:ReportingTimePeriodOrMissingType
	658	+|(% style="width:279px" %)ReportingYear|(% style="width:522px" %)common:ReportingYearOrMissingType
	659	+|(% style="width:279px" %)ReportingSemester|(% style="width:522px" %)common:ReportingSemesterOrMissingType
	660	+|(% style="width:279px" %)ReportingTrimester|(% style="width:522px" %)common:ReportingTrimesterOrMissingType
	661	+|(% style="width:279px" %)ReportingQuarter|(% style="width:522px" %)common:ReportingQuarterOrMissingType
	662	+|(% style="width:279px" %)ReportingMonth|(% style="width:522px" %)common:ReportingMonthOrMissingType
	663	+|(% style="width:279px" %)ReportingWeek|(% style="width:522px" %)common:ReportingWeekOrMissingType
	664	+|(% style="width:279px" %)ReportingDay|(% style="width:522px" %)common:ReportingDayOrMissingType
	665	+|(% style="width:279px" %)TimeRange|(% style="width:522px" %)common:TimeRangeOrMissingType
645	645
646	646	=== 3.3.9 Representation with Complex Text Format ===
647	647
...	...	@@ -698,16 +698,17 @@
698	698
699	699	A complex type named DataSetType must be created. Its content model will be derived via restriction. The base type of the restriction is dsd:DataSetType. The complex type content model will be as follows:
700	700
701		-1. A sequence consisting of:
702		-1. An element reference to common:Annotations, with a minimum occurrence of 0
703		- 2. A local element named DataProvider with the type common:DataProviderReferenceType, a form of unqualified and a minimum occurrence of 0
704		- 3. A choice with a minimum occurrence of 0 and a maximum occurrence of unbounded consisting of:
705		-1. A local element named Atts with a form of unqualified and a type of AttsType (as defined in the AttsType section which follows)
706		- 2. If the data structure defines groups, a local element named Group with a form of unqualified. The type of this element should be the type that is described in the GroupType section which follows.
707		- 3. If the dimension at the observation level is not AllDimensions, a local element named Series with a form of unqualified and a type of SeriesType (as defined in the SeriesType section which follows)
708		- 4. If the dimension at the observation level is AllDimensions, a local element named Obs with a form of unqualified and a type of ObsType (as defined in the ObsType section which follows)
709		- 4. If any metadata attribute usages defined in the data structure that declares an attribute relationship of dataflow, a local element named Metadata with the type metadata:MetadataSetType a form of unqualified, and a minimum occurences of 0
	722	+~1. A sequence consisting of:
710	710
	724	+* i. An element reference to common:Annotations, with a minimum occurrence of 0
	725	+* ii  A local element named DataProvider with the type common:DataProviderReferenceType, a form of unqualified and a minimum occurrence of 0
	726	+* iii  A choice with a minimum occurrence of 0 and a maximum occurrence of unbounded consisting of:
	727	+** a.  A local element named Atts with a form of unqualified and a type of AttsType (as defined in the AttsType section which follows)
	728	+** b. If the data structure defines groups, a local element named Group with a form of unqualified. The type of this element should be the type that is described in the GroupType section which follows.
	729	+** c. If the dimension at the observation level is not AllDimensions, a local element named Series with a form of unqualified and a type of SeriesType (as defined in the SeriesType section which follows)
	730	+** d. If the dimension at the observation level is AllDimensions, a local element named Obs with a form of unqualified and a type of ObsType (as defined in the ObsType section which follows)
	731	+* iv. If any metadata attribute usages defined in the data structure that declares an attribute relationship of dataflow, a local element named Metadata with the type metadata:MetadataSetType a form of unqualified, and a minimum occurences of 0
	732	+
711	711	=== 3.4.2 GroupType ===
712	712
713	713	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: