Skip to Content

Changes for page 3 SDMX Base Package

Last modified by Helena on 2025/09/10 11:19
From version 11.1
edited by Helena
on 2025/05/15 10:29
Change comment: There is no comment for this version
To version 13.1
edited by Helena
on 2025/05/16 22:47
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -4,17 +4,15 @@
4 4  
5 5  == 3.1 Introduction ==
6 6  
7 -The constructs in the SDMX Base package comprise the fundamental building blocks that support many of the other structures in the model. For this reason, many of the classes in this package are abstract (i.e., only derived sub-classes can exist in an implementation).
7 +The constructs in the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] Base package comprise the fundamental building blocks that support many of the other structures in the model. For this reason, many of the classes in this package are abstract (i.e., only derived sub-classes can exist in an implementation).
8 8  
9 -The motivation for establishing the SDMX Base package is as follows:
9 +The motivation for establishing the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] Base package is as follows:
10 10  
11 11  it is accepted “Best Practise” to identify fundamental archetypes occurring in a model
12 -
13 13  identification of commonly found structures or “patterns” leads to easier understanding
14 -
15 15  identification of patterns encourages re-use
16 16  
17 -Each of the class diagrams in this section views classes from the SDMX Base package from a different perspective. There are detailed views of specific patterns, plus overviews showing inheritance between classes, and relationships amongst classes.
15 +Each of the class diagrams in this section views classes from the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] Base package from a different perspective. There are detailed views of specific patterns, plus overviews showing inheritance between classes, and relationships amongst classes.
18 18  
19 19  == 3.2 Base Structures - Identification, Versioning, and Maintenance ==
20 20  
... ... @@ -28,19 +28,19 @@
28 28  
29 29  ==== 3.2.2.1 Narrative ====
30 30  
31 -This group of classes forms the nucleus of the administration facets of SDMX objects. They provide features which are reusable by derived classes to support horizontal functionality such as identity, versioning etc.
29 +This group of classes forms the nucleus of the administration [[facets>>doc:xwiki:Glossary.Facet.WebHome]] of [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] objects. They provide features which are reusable by derived classes to support horizontal functionality such as identity, versioning etc.
32 32  
33 -All classes derived from the abstract class //AnnotableArtefact// may have Annotations (or notes): this supports the need to add notes to all SDMX-ML elements. The Annotation is used to convey extra information to describe any SDMX construct. This information may be in the form of a URL reference and/or a multilingual text (represented by the association to InternationalString).
31 +All classes derived from the abstract class //AnnotableArtefact// may have [[Annotations>>doc:xwiki:Glossary.Annotation.WebHome]] (or notes): this supports the need to add notes to all [[SDMX-ML>>doc:xwiki:Glossary.SDMX-ML.WebHome]] elements. The [[Annotation>>doc:xwiki:Glossary.Annotation.WebHome]] is used to convey extra information to describe any [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] construct. This information may be in the form of a URL reference and/or a multilingual text (represented by the association to InternationalString).
34 34  
35 -The //IdentifiableArtefact// is an abstract class that comprises the basic attributes needed for identification. Concrete classes based on //IdentifiableArtefact// all inherit the ability to be uniquely identified.
33 +The //IdentifiableArtefact// is an abstract class that comprises the basic [[attributes>>doc:xwiki:Glossary.Attribute.WebHome]] needed for identification. Concrete classes based on //IdentifiableArtefact// all inherit the ability to be uniquely identified.
36 36  
37 -The //NamableArtefact// is an abstract class that inherits from //IdentifiableArtefact //and in addition the +description and +name roles support multilingual descriptions and names for all objects based on //NameableArtefact//. The InternationalString supports the representation of a description in multiple locales (locale is similar to language but includes geographic variations such as Canadian French, US English etc.). The //LocalisedString// supports the representation of a description in one locale.
35 +The //NamableArtefact// is an abstract class that inherits from //IdentifiableArtefact //and in addition the +description and +name roles support multilingual descriptions and names for all objects based on //NameableArtefact//. The InternationalString supports the [[representation>>doc:xwiki:Glossary.Representation.WebHome]] of a description in multiple locales (locale is similar to language but includes geographic variations such as Canadian French, US English etc.). The //LocalisedString// supports the [[representation>>doc:xwiki:Glossary.Representation.WebHome]] of a description in one locale.
38 38  
39 -//VersionableArtefact// is an abstract class which inherits from //NameableArtefact// and adds versioning ability to all classes derived from it, as explained in the SDMX versioning rules in SDMX Standards Section 6 “Technical Notes”, paragraph “4.3 Versioning”.
37 +//VersionableArtefact// is an abstract class which inherits from //NameableArtefact// and adds versioning ability to all classes derived from it, as explained in the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] versioning rules in [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] Standards Section 6 “Technical Notes”, paragraph “4.3 Versioning”.
40 40  
41 41  //MaintainableArtefact// further adds the ability for derived classes to be maintained via its association to an //Organisation//, and adds locational information (i.e., from where the object can be retrieved).
42 42  
43 -The inheritance chain from //AnnotableArtefact// through to //MaintainableArtefact// allows SDMX classes to inherit the features they need, from simple annotation, through identity, naming, to versioning and maintenance.
41 +The inheritance chain from //AnnotableArtefact// through to //MaintainableArtefact// allows [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] classes to inherit the features they need, from simple [[annotation>>doc:xwiki:Glossary.Annotation.WebHome]], through identity, naming, to versioning and maintenance.
44 44  
45 45  ==== 3.2.2.2 Definitions ====
46 46  
... ... @@ -48,7 +48,6 @@
48 48  |**Class**|(% style="width:244px" %)**Feature**|(% style="width:514px" %)**Description**
49 49  |//AnnotableArtefact//|(% style="width:244px" %)(((
50 50  Base inheritance sub classes are:
51 -
52 52  //IdentifiableArtefact//
53 53  )))|(% style="width:514px" %)Objects of classes derived from this can have attached annotations.
54 54  |Annotation|(% style="width:244px" %) |(% style="width:514px" %)Additional descriptive information attached to an object.
... ... @@ -139,30 +139,30 @@
139 139  
140 140  ==== 3.4.2.1 Narrative ====
141 141  
142 -The FacetType and FacetValueType enumerations are used to specify the valid format of the content of a non-enumerated Concept or the usage of a Concept when specified for use on a //Component// on a //Structure// (such as a Dimension in a DataStructureDefinition). The description of the various types can be found in the chapter on ConceptScheme (section 4.5).
139 +The FacetType and FacetValueType enumerations are used to specify the valid format of the content of a non-enumerated (% style="color:#2ecc71" %)Concept(%%) or the usage of a (% style="color:#2ecc71" %)Concept(%%) when specified for use on a //[[Component>>doc:xwiki:Glossary.Component.WebHome]]// on a //Structure// (such as a [[Dimension>>doc:xwiki:Glossary.Dimension.WebHome]] in a DataStructureDefinition). The description of the various types can be found in the chapter on ConceptScheme (section 4.5).
143 143  
144 144  The ActionType enumeration is used to specify the action that a receiving system should take when processing the content that is the object of the action. It is enumerated as follows:
145 145  
146 -* Append: Data or metadata is an incremental update for an existing data/metadata set or the provision of new data or documentation (attribute values) formerly absent. If any of the supplied data or metadata is already present, it will not replace that data or metadata. This corresponds to the "Update" value found in version 1.0 of the SDMX Technical Standards.
143 +* Append: Data or metadata is an [[incremental update>>doc:xwiki:Glossary.Incremental update.WebHome]] for an existing data/[[metadata set>>doc:xwiki:Glossary.Metadata set.WebHome]] or the provision of new data or documentation ([[attribute>>doc:xwiki:Glossary.Attribute.WebHome]] values) formerly absent. If any of the supplied data or metadata is already present, it will not replace that data or metadata. This corresponds to the "Update" value found in (% style="color:#2ecc71" %)version(%%) 1.0 of the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] Technical Standards.
147 147  * Replace: Data/metadata is to be replaced and may also include additional data/metadata to be appended.
148 148  * Delete: Data/Metadata is to be deleted.
149 149  * Information: Data and metadata are for information purposes.
150 150  
151 -The ToValueType data type contains the attributes to support transformations defined in the StructureMap (see Section 0).
148 +The ToValueType data type contains the [[attributes>>doc:xwiki:Glossary.Attribute.WebHome]] to support transformations defined in the StructureMap (see Section 0).
152 152  
153 -The ConstraintRoleType data type contains the attributes that identify the purpose of a Constraint (allowableContent, actualContent).
150 +The ConstraintRoleType data type contains the [[attributes>>doc:xwiki:Glossary.Attribute.WebHome]] that identify the purpose of a (% style="color:#2ecc71" %)Constraint(%%) (allowableContent, actualContent).
154 154  
155 -The ComponentRoleType data type contains the predefined Concept roles that can be assigned to any Component.
152 +The ComponentRoleType data type contains the predefined (% style="color:#2ecc71" %)Concept(%%) roles that can be assigned to any [[Component>>doc:xwiki:Glossary.Component.WebHome]].
156 156  
157 -The CascadeValues data type contains the possible values for a MemberValue within a CubeRegion, in order to enable cascading to all children Codes of a selected Code, while including/excluding the latter in the selection.
154 +The CascadeValues data type contains the possible values for a MemberValue within a CubeRegion, in order to enable cascading to all children [[Codes>>doc:xwiki:Glossary.Code.WebHome]] of a selected [[Code>>doc:xwiki:Glossary.Code.WebHome]], while including/excluding the latter in the selection.
158 158  
159 -The VersionType data types provides the details for versioning according to SDMX versioning rules, as explained in SDMX Standards Section 6, paragraph “4.3 Versioning”.
156 +The VersionType data types provides the details for versioning according to [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] versioning rules, as explained in [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] Standards Section 6, paragraph “4.3 Versioning”.
160 160  
161 161  == 3.5 The Item Scheme Pattern ==
162 162  
163 163  === 3.5.1 Context ===
164 164  
165 -The Item Scheme is a basic architectural pattern that allows the creation of list schemes for use in simple taxonomies, for example.
162 +The [[Item Scheme>>doc:xwiki:Glossary.Item scheme.WebHome]] is a basic architectural pattern that allows the creation of list schemes for use in simple taxonomies, for example.
166 166  
167 167  The //ItemScheme// is the basis for CategoryScheme, Codelist, ConceptScheme, ReportingTaxonomy, //OrganisationScheme//, TransformationScheme, CustomTypeScheme, NamePersonalisationScheme, RulesetScheme, VtlMappingScheme and UserDefinedOperatorScheme.
168 168  
... ... @@ -176,15 +176,15 @@
176 176  
177 177  ==== 3.5.3.1 Narrative ====
178 178  
179 -The //ItemScheme// is an abstract class which defines a set of //Item// (this class is also abstract). Its main purpose is to define a mechanism which can be used to create taxonomies which can classify other parts of the SDMX Information Model. It is derived from //MaintainableArtefact// which gives it the ability to be annotated, have identity, naming, versioning and be associated with an Agency. An example of a concrete class is a ConceptScheme. The associated Concepts are //Item//s.
176 +The //ItemScheme// is an abstract class which defines a set of //Item// (this class is also abstract). Its main purpose is to define a mechanism which can be used to create taxonomies which can classify other parts of the [[SDMX Information Model>>doc:xwiki:Glossary.SDMX Information Model.WebHome]]. It is derived from //MaintainableArtefact// which gives it the ability to be annotated, have identity, naming, versioning and be associated with an Agency. An example of a concrete class is a ConceptScheme. The associated (% style="color:#2ecc71" %)Concepts(%%) are //Item//s.
180 180  
181 -In an exchange environment an //ItemScheme// is allowed to contain a sub-set of the //Item//s in the maintained //ItemScheme//. If such an ItemScheme is disseminated with a sub-set of the //Item//s then the fact that this is a sub-set is denoted by setting the isPartial attribute to "true".
178 +In an exchange environment an //ItemScheme// is allowed to contain a sub-set of the //Item//s in the maintained //ItemScheme//. If such an ItemScheme is disseminated with a sub-set of the //Item//s then the fact that this is a sub-set is denoted by setting the isPartial [[attribute>>doc:xwiki:Glossary.Attribute.WebHome]] to "true".
182 182  
183 -A “partial” //ItemScheme// cannot be maintained independently in its partial form i.e., it cannot contain //Item//s that are not present in the full //ItemScheme// and the content of any one //Item //(e.g., names and descriptions) cannot deviate from the content in the full //ItemScheme//. Furthermore, the id of the //ItemScheme// where isPartial is set to "true" is the same as the id of the full //ItemScheme// (agencyId, id, version). This is important as this is the id that that is referenced in other structures (e.g., a Codelist referenced in a DSD) and this id is always the same, regardless of whether the disseminated //ItemScheme// is the full //ItemScheme// or a partial //ItemScheme//.
180 +A “partial” //ItemScheme// cannot be maintained independently in its partial form i.e., it cannot contain //Item//s that are not present in the full //ItemScheme// and the content of any one //Item //(e.g., names and descriptions) cannot deviate from the content in the full //ItemScheme//. Furthermore, the id of the //ItemScheme// where isPartial is set to "true" is the same as the id of the full //ItemScheme// (agencyId, id, (% style="color:#2ecc71" %)version(%%)). This is important as this is the id that that is referenced in other structures (e.g., a Codelist referenced in a [[DSD>>doc:xwiki:Glossary.Data structure definition.WebHome]]) and this id is always the same, regardless of whether the disseminated //ItemScheme// is the full //ItemScheme// or a partial //ItemScheme//.
184 184  
185 -The purpose of a partial //ItemScheme// is to support the exchange and dissemination of a subset //ItemScheme// without the need to maintain multiple //ItemScheme//s which contain the same //Item//s. For instance, when a Codelist is used in a DataStructureDefinition it is sometimes the case that only a sub-set of the Codes in a Codelist are relevant. In this case a partial Codelist can be constructed using the Constraint mechanism explained later in this document.
182 +The purpose of a partial //ItemScheme// is to support the exchange and dissemination of a subset //ItemScheme// without the need to maintain multiple //ItemScheme//s which contain the same //Item//s. For instance, when a Codelist is used in a DataStructureDefinition it is sometimes the case that only a sub-set of the [[Codes>>doc:xwiki:Glossary.Code.WebHome]] in a Codelist are relevant. In this case a partial Codelist can be constructed using the (% style="color:#2ecc71" %)Constraint(%%) mechanism explained later in this document.
186 186  
187 -//Item// inherits from //NameableArtefact// which gives it the ability to be annotated and have identity, and therefore has id, uri and urn attributes, a name and a description in the form of an InternationalString. Unlike the parent //ItemScheme//, the //Item// itself is not a //MaintainableArtefact// and therefore cannot have an independent Agency (i.e., it implicitly has the same agencyId as the //ItemScheme//).
184 +//Item// inherits from //NameableArtefact// which gives it the ability to be annotated and have identity, and therefore has id, uri and urn [[attributes>>doc:xwiki:Glossary.Attribute.WebHome]], a name and a description in the form of an InternationalString. Unlike the parent //ItemScheme//, the //Item// itself is not a //MaintainableArtefact// and therefore cannot have an independent Agency (i.e., it implicitly has the same agencyId as the //ItemScheme//).
188 188  
189 189  The //Item// can be hierarchic and so one //Item// can have child //Item//s. The restriction of the hierarchic association is that a child //Item// can have only parent //Item//.
190 190  
... ... @@ -194,27 +194,17 @@
194 194  |**Class**|(% style="width:272px" %)**Feature**|(% style="width:422px" %)**Description**
195 195  |//ItemScheme//|(% style="width:272px" %)(((
196 196  Inherits from:
197 -
198 198  //MaintainableArtefact//
199 -
200 200  Direct sub classes are:
201 -
202 202  CategoryScheme
203 -
204 204  ConceptScheme
205 -
206 206  Codelist
207 -
208 208  ReportingTaxonomy
209 -
210 210  //OrganisationScheme//
211 -
212 212  TransformationScheme
213 -
214 -CustomTypeScheme NamePersonalisationSc heme
215 -
202 +CustomTypeScheme
203 +NamePersonalisationSc heme
216 216  RulesetScheme
217 -
218 218  VtlMappingScheme UserDefinedOperatorSc heme
219 219  )))|(% style="width:422px" %)The descriptive information for an arrangement or division of objects into groups based on characteristics, which the objects have in common.
220 220  | |(% style="width:272px" %)isPartial|(% style="width:422px" %)Denotes whether the Item Scheme contains a subset of the full set of Items in the maintained scheme.
... ... @@ -223,29 +223,17 @@
223 223  Inherits from:
224 224  
225 225  //NameableArtefact//
226 -
227 227  Direct sub classes are
228 -
229 229  Category
230 -
231 231  Concept
232 -
233 233  Code
234 -
235 235  ReportingCategory
236 -
237 237  //Organisation//
238 -
239 239  Transformation
240 -
241 241  CustomType
242 -
243 243  NamePersonalisation
244 -
245 245  Ruleset
246 -
247 247  VtlMapping
248 -
249 249  UserDefinedOperator
250 250  )))|(% style="width:422px" %)The Item is an item of content in an Item Scheme. This may be a node in a taxonomy or ontology, a code in a code list etc. Node that at the conceptual level the Organisation is not hierarchic.
251 251  | |(% style="width:272px" %)hierarchy|(% style="width:422px" %)This allows an Item optionally to have one or more child Items.
... ... @@ -254,7 +254,7 @@
254 254  
255 255  === 3.6.1 Context ===
256 256  
257 -The Structure Pattern is a basic architectural pattern which allows the specification of complex tabular structures which are often found in statistical data (such as Data Structure Definition, and Metadata Structure Definition). A Structure is a set of ordered lists. A pattern to underpin this tabular structure has been developed, so that commonalities between these structure definitions can be supported by common software and common syntax structures.
232 +The Structure Pattern is a basic architectural pattern which allows the specification of complex tabular structures which are often found in statistical data (such as [[Data Structure Definition>>doc:xwiki:Glossary.Data structure definition.WebHome]], and [[Metadata Structure Definition>>doc:xwiki:Glossary.Metadata structure definition.WebHome]]). A Structure is a set of ordered lists. A pattern to underpin this tabular structure has been developed, so that commonalities between these structure definitions can be supported by common software and common syntax structures.
258 258  
259 259  === 3.6.2 Class Diagrams ===
260 260  
... ... @@ -272,33 +272,29 @@
272 272  
273 273  The //Structure// is an abstract class which contains a set of one or more //ComponentList//(s) (this class is also abstract). An example of a concrete //Structure// is DataStructureDefinition.
274 274  
275 -The //ComponentList// is a list of one or more //Component//(s//)//. The //ComponentList// has several concrete descriptor classes based on it: DimensionDescriptor, GroupDimensionDescriptor, MeasureDescriptor, and AttributeDescriptor of the DataStructureDefinition and MetadataAttributeDescriptor of the MetadataStructureDefinition.
250 +The //ComponentList// is a list of one or more //[[Component>>doc:xwiki:Glossary.Component.WebHome]]//(s//)//. The //ComponentList// has several concrete descriptor classes based on it: DimensionDescriptor, GroupDimensionDescriptor, MeasureDescriptor, and AttributeDescriptor of the DataStructureDefinition and MetadataAttributeDescriptor of the MetadataStructureDefinition.
276 276  
277 -The //Component// is contained in a //ComponentList//. The type of //Component// in a //ComponentList// is dependent on the concrete class of the ComponentList as follows:
252 +The //[[Component>>doc:xwiki:Glossary.Component.WebHome]]// is contained in a //ComponentList//. The type of //[[Component>>doc:xwiki:Glossary.Component.WebHome]]// in a //ComponentList// is dependent on the concrete class of the ComponentList as follows:
278 278  
279 -DimensionDescriptor: Dimension, TimeDimension
280 -
281 -GroupDimensionDescriptor: Dimension, TimeDimension
282 -
283 -MeasureDescriptor: Measure
284 -
254 +DimensionDescriptor: [[Dimension>>doc:xwiki:Glossary.Dimension.WebHome]], TimeDimension
255 +GroupDimensionDescriptor: [[Dimension>>doc:xwiki:Glossary.Dimension.WebHome]], TimeDimension
256 +MeasureDescriptor: [[Measure>>doc:xwiki:Glossary.Measure.WebHome]]
285 285  AttributeDescriptor: DataAttribute, MetadataAttributeRef
286 -
287 287  MetadataAttributeDescriptor: MetadataAttribute
288 288  
289 -Each //Component// takes its semantic (and possibly also its representation) from a Concept in a ConceptScheme. This is represented by the conceptIdentity association to Concept.
260 +Each //[[Component>>doc:xwiki:Glossary.Component.WebHome]]// takes its semantic (and possibly also its [[representation>>doc:xwiki:Glossary.Representation.WebHome]]) from a (% style="color:#2ecc71" %)Concept(%%) in a ConceptScheme. This is represented by the conceptIdentity association to (% style="color:#2ecc71" %)Concept(%%).
290 290  
291 -The //Component// may also have a localRepresentation. This allows a concrete class, such as Dimension, to specify its representation which is local to the //Structure// in which it is contained (for Dimension this will be DataStructureDefinition), and thus overrides any coreRepresentation specified for the Concept.
262 +The //[[Component>>doc:xwiki:Glossary.Component.WebHome]]// may also have a localRepresentation. This allows a concrete class, such as [[Dimension>>doc:xwiki:Glossary.Dimension.WebHome]], to specify its [[representation>>doc:xwiki:Glossary.Representation.WebHome]] which is local to the //Structure// in which it is contained (for [[Dimension>>doc:xwiki:Glossary.Dimension.WebHome]] this will be DataStructureDefinition), and thus overrides any coreRepresentation specified for the (% style="color:#2ecc71" %)Concept(%%).
292 292  
293 -The Representation can be enumerated or non-enumerated. The valid content of an enumerated representation is specified either in an //ItemScheme// which can be one of Codelist, ValueList or //GeoCodelist//. The valid content of a non-enumerated representation is specified as one or more Facet(s) (for example, these may specify minimum and maximum values). For any Attribute this is achieved by one of more ExtendedFacet(s), which allow the additional representation of XHTML.
264 +The [[Representation>>doc:xwiki:Glossary.Representation.WebHome]] can be enumerated or non-enumerated. The valid content of an enumerated [[representation>>doc:xwiki:Glossary.Representation.WebHome]] is specified either in an //ItemScheme// which can be one of Codelist, ValueList or //GeoCodelist//. The valid content of a non-enumerated [[representation>>doc:xwiki:Glossary.Representation.WebHome]] is specified as one or more Facet(s) (for example, these may specify minimum and maximum values). For any [[Attribute>>doc:xwiki:Glossary.Attribute.WebHome]] this is achieved by one of more ExtendedFacet(s), which allow the additional [[representation>>doc:xwiki:Glossary.Representation.WebHome]] of XHTML.
294 294  
295 -The types of representation that are valid for specific components is expressed in the model as a constraint on the association:
266 +The types of [[representation>>doc:xwiki:Glossary.Representation.WebHome]] that are valid for specific [[components>>doc:xwiki:Glossary.Component.WebHome]] is expressed in the model as a (% style="color:#2ecc71" %)constraint(%%) on the association:
296 296  
297 -* The Dimension, DataAttribute, Measure, MetadataAttribute may be enumerated and, if so, use an //EnumeratedList//.
298 -* The Dimension and Measure may be non-enumerated and, if so, use one or more Facet(s), note that the FacetValueType applicable to the TimeDimension is restricted to those that represent time.
268 +* The [[Dimension>>doc:xwiki:Glossary.Dimension.WebHome]], DataAttribute, [[Measure>>doc:xwiki:Glossary.Measure.WebHome]], MetadataAttribute may be enumerated and, if so, use an //EnumeratedList//.
269 +* The [[Dimension>>doc:xwiki:Glossary.Dimension.WebHome]] and [[Measure>>doc:xwiki:Glossary.Measure.WebHome]] may be non-enumerated and, if so, use one or more Facet(s), note that the FacetValueType applicable to the TimeDimension is restricted to those that represent time.
299 299  * The MetadataAttribute and DataAttribute may be non-enumerated and, if so, use one or more ExtendedFacet(s).
300 300  
301 -The //Structure// may be used by one or more //StructureUsage//(s). An example of this, in terms of concrete classes, is that a Dataflow (sub class of //StructureUsage//) may use a particular DataStructureDefinition (sub class of //Structure//), and similar constructs apply for the Metadataflow (link to MetadataStructureDefinition).
272 +The //Structure// may be used by one or more //StructureUsage//(s). An example of this, in terms of concrete classes, is that a [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]] (sub class of //StructureUsage//) may use a particular DataStructureDefinition (sub class of //Structure//), and similar constructs apply for the [[Metadataflow>>doc:xwiki:Glossary.Metadataflow.WebHome]] (link to MetadataStructureDefinition).
302 302  
303 303  ==== 3.6.3.2 Definitions ====
304 304  
... ... @@ -306,54 +306,38 @@
306 306  |**Class**|(% style="width:284px" %)**Feature**|(% style="width:353px" %)**Description**
307 307  |StructureUsage|(% style="width:284px" %)(((
308 308  Inherits from:
309 -
310 310  //MaintainableArtefact//
311 311  
312 312  Sub classes are:
313 -
314 314  Dataflow
315 -
316 316  Metadataflow
317 317  )))|(% style="width:353px" %)An artefact whose components are described by a Structure. In concrete terms (sub-classes) an example would be a Dataflow which is linked to a given structure – in this case the Data Structure Definition.
318 318  | |(% style="width:284px" %)structure|(% style="width:353px" %)An association to a Structure specifying the structure of the artefact.
319 319  |Structure|(% style="width:284px" %)(((
320 320  Inherits from:
321 -
322 -//MaintainableArtefact//
323 -
324 -Sub classes are:
325 -
289 +//MaintainableArtefact//Sub classes are:
326 326  DataStructureDefinition MetadataStructureDefinit ion
327 327  )))|(% style="width:353px" %)Abstract specification of a list of lists to define a complex tabular structure. A concrete example of this would be statistical concepts, code lists, and their organisation in a data or metadata structure definition, defined by a centre institution, usually for the exchange of statistical information with its partners.
328 328  | |(% style="width:284px" %)grouping|(% style="width:353px" %)A composite association to one or more component lists.
329 329  |//ComponentList//|(% style="width:284px" %)(((
330 330  Inherits from:
331 -
332 332  //IdentifiableArtefact//
333 333  
334 334  Sub classes are:
335 -
336 336  DimensionDescriptor
337 -
338 338  GroupDimensionDescriptor
339 -
340 340  MeasureDescriptor
341 -
342 342  AttributeDescriptor MetadataAttributeDescriptor
343 343  )))|(% style="width:353px" %)An abstract definition of a list of components. A concrete example is a Dimension Descriptor, which defines the list of Dimensions in a Data Structure Definition.
344 344  | |(% style="width:284px" %)components|(% style="width:353px" %)An aggregate association to one or more components which make up the list.
345 345  |//Component//|(% style="width:284px" %)(((
346 346  Inherits from:
347 -
348 348  //IdentifiableArtefact//
349 349  
350 350  Sub classes are:
351 -
352 352  Measure
353 -
354 -//AttributeComponent//
355 -
356 -//DimensionComponent//
310 +//AttributeComponent
311 +DimensionComponent//
357 357  )))|(% style="width:353px" %)A Component is an abstract super class used to define qualitative and quantitative data and metadata items that belong to a Component List and hence a Structure. Component is refined through its sub-classes.
358 358  | |(% style="width:284px" %)conceptIdentity|(% style="width:353px" %)(((
359 359  Association to a Concept in a Concept Scheme that identifies and defines the
... ... @@ -370,11 +370,11 @@
370 370  | |(% style="width:284px" %) |(% style="width:353px" %)Defines the format of the identifiers in an Item Scheme used by a Component. Typically, this would define the number of characters (length) of the identifier.
371 371  |ExtendedFacet|(% style="width:284px" %)+itemSchemeFacet|(% style="width:353px" %)This has the same function as Facet but allows additionally an XHTML representation. This is constrained for use with a Metadata Attribute and a Data Attribute.
372 372  
373 -The specification of the content and use of the sub classes to //ComponentList// and //Component// can be found in the section in which they are used (DataStructureDefinition and MetadataStructureDefinition). Moreover, the FacetType SentinelValues is explained in the datastructure representation diagram (see 5.3.2.2), since it only concerns DataStructureDefinitions.
328 +The specification of the content and use of the sub classes to //ComponentList// and //[[Component>>doc:xwiki:Glossary.Component.WebHome]]// can be found in the section in which they are used (DataStructureDefinition and MetadataStructureDefinition). Moreover, the FacetType SentinelValues is explained in the datastructure [[representation>>doc:xwiki:Glossary.Representation.WebHome]] diagram (see 5.3.2.2), since it only concerns DataStructureDefinitions.
374 374  
375 375  ==== 3.6.3.3 Representation Constructs ====
376 376  
377 -The majority of SDMX FacetValueTypes are compatible with those found in XML Schema, and have equivalents in most current implementation platforms:
332 +The majority of [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] FacetValueTypes are compatible with those found in XML Schema, and have equivalents in most current implementation platforms:
378 378  
379 379  (% style="width:923.039px" %)
380 380  |(% style="width:167px" %)**SDMX Facet Value Type**|(% style="width:148px" %)**XML Schema Data Type**|(% style="width:158px" %)**JSON Schema Data Type**|(% style="width:161px" %)**.NET Framework Type**|(% style="width:285px" %)**Java Data Type**
... ... @@ -398,9 +398,9 @@
398 398  |(% style="width:167px" %)Day, MonthDay, Month|(% style="width:148px" %)xsd:g*|(% style="width:158px" %)string|(% style="width:161px" %)System.DateTime|(% style="width:285px" %)javax.xml.datatype.XML GregorianCalendar
399 399  |(% style="width:167px" %)Duration|(% style="width:148px" %)xsd:duration|(% style="width:158px" %)string|(% style="width:161px" %)System.TimeSpan|(% style="width:285px" %)javax.xml.datatype.Dur ation
400 400  
401 -There are also a number of SDMX data types which do not have these direct correspondences, often because they are composite representations or restrictions of a broader data type. These are detailed in Section 6 of the standards.
356 +There are also a number of [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] data types which do not have these direct correspondences, often because they are composite [[representations>>doc:xwiki:Glossary.Representation.WebHome]] or restrictions of a broader data type. These are detailed in Section 6 of the standards.
402 402  
403 -The Representation is composed of Facets, each of which conveys characteristic information related to the definition of a value domain. Often a set of Facets are needed to convey the required semantic. For example, a sequence is defined by a minimum of two Facets: one to define the start value, and one to define the interval.
358 +The [[Representation>>doc:xwiki:Glossary.Representation.WebHome]] is composed of [[Facets>>doc:xwiki:Glossary.Facet.WebHome]], each of which conveys characteristic information related to the definition of a value domain. Often a set of [[Facets>>doc:xwiki:Glossary.Facet.WebHome]] are needed to convey the required semantic. For example, a sequence is defined by a minimum of two [[Facets>>doc:xwiki:Glossary.Facet.WebHome]]: one to define the start value, and one to define the interval.
404 404  
405 405  (% style="width:921.039px" %)
406 406  |**Facet Type**|(% style="width:827px" %)**Explanation**
... ... @@ -421,8 +421,6 @@
421 421  |decimals|(% style="width:827px" %)The decimals facet indicates the number of characters allowed after the decimal separator.
422 422  |pattern|(% style="width:827px" %)The pattern attribute holds any regular expression permitted in the implementation syntax (e.g., W3C XML Schema).
423 423  
424 -[[image:SDMX 3-0-0 SECTION 2 FINAL-1.0 (1)_en_59eee18f.gif||alt="Shape29" height="1" width="192"]]
379 +----
425 425  
426 -^^2^^ In the JSON schemas, more complex data types are complemented with regular expressions, whenever no direct mapping to a standard type exists.
427 -
428 428  {{putFootnotes/}}