Changes for page 3 SDMX Base Package

Summary

• Page properties (2 modified, 0 added, 0 removed)
• Attachments (0 modified, 6 added, 6 removed)
  • image36.png
  • image37.png
  • image38.png
  • image39.png
  • image40.png
  • image41.png
  • 1749246130522-547.jpeg
  • 1749246130530-261.jpeg
  • 1749246130536-128.jpeg
  • 1749246130543-644.jpeg
  • 1749246130548-601.jpeg
  • 1749246130554-995.jpeg
• Objects (0 modified, 1 added, 1 removed)
  • SKMS.Methodology.Code.MethodologyClass[0]
  • SUZ.Methodology.Code.MethodologyClass[0]

Details

Page properties

Content

...	...	@@ -4,19 +4,19 @@
4	4
5	5	== 3.1 Introduction ==
6	6
7		-The constructs in the [[SDMX>>doc:sdmx:Glossary 2\.1.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).
	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).
8	8
9		-The motivation for establishing the [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] Base package is as follows:
	9	+The motivation for establishing the SDMX Base package is as follows:
10	10
11	11	it is accepted “Best Practise” to identify fundamental archetypes occurring in a model// //identification of commonly found structures or “patterns” leads to easier understanding// //identification of patterns encourages re-use
12	12
13		-Each of the class diagrams in this section views classes from the [[SDMX>>doc:sdmx:Glossary 2\.1.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.
	13	+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.
14	14
15	15	== 3.2 Base Structures - Identification, Versioning, and Maintenance ==
16	16
17	17	=== 3.2.1 Class Diagram ===
18	18
19		-[[image:image36.png]]
	19	+[[image:1749246130522-547.jpeg]]
20	20
21	21	**Figure 10: SDMX Identification, Maintenance and Versioning**
22	22
...	...	@@ -24,19 +24,19 @@
24	24
25	25	==== 3.2.2.1 Narrative ====
26	26
27		-This group of classes forms the nucleus of the administration [[facets>>doc:sdmx:Glossary 2\.1.Facet.WebHome]] of [[SDMX>>doc:sdmx:Glossary 2\.1.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.
	27	+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.
28	28
29		-All classes derived from the abstract class //AnnotableArtefact// may have [[Annotations>>doc:sdmx:Glossary 2\.1.Annotation.WebHome]] (or notes): this supports the need to add notes to all [[SDMX-ML>>doc:sdmx:Glossary 2\.1.SDMX-ML.WebHome]] elements. The [[Annotation>>doc:sdmx:Glossary 2\.1.Annotation.WebHome]] is used to convey extra information to describe any [[SDMX>>doc:sdmx:Glossary 2\.1.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).
	29	+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).
30	30
31		-The //IdentifiableArtefact// is an abstract class that comprises the basic [[attributes>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]] needed for identification. Concrete classes based on //IdentifiableArtefact// all inherit the ability to be uniquely identified.
	31	+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.
32	32
33		-The (% style="background-color:#e74c3c" %)//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:sdmx:Glossary 2\.1.Representation.WebHome]] of a description in multiple locales (locale is similar to [[language>>doc:sdmx:Glossary 2\.1.Language.WebHome]] but includes geographic variations such as Canadian French, US English etc.). The //LocalisedString// supports the [[representation>>doc:sdmx:Glossary 2\.1.Representation.WebHome]] of a description in one locale.
	33	+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.
34	34
35		-//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:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] versioning rules in [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] Standards Section 6 “Technical Notes”, paragraph “4.3 Versioning”.
	35	+//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”.
36	36
37	37	//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).
38	38
39		-The inheritance chain from //AnnotableArtefact// through to //MaintainableArtefact// allows [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] classes to inherit the features they need, from simple [[annotation>>doc:sdmx:Glossary 2\.1.Annotation.WebHome]], through identity, naming, to versioning and maintenance.
	39	+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.
40	40
41	41	==== 3.2.2.2 Definitions ====
42	42
...	...	@@ -45,22 +45,22 @@
45	45	|//AnnotableArtefact//|(% style="width:262px" %)(((
46	46	Base inheritance sub classes are:
47	47	//IdentifiableArtefact//
48		-)))|(% style="width:543px" %)Objects of classes derived from this can have attached [[annotations>>doc:sdmx:Glossary 2\.1.Annotation.WebHome]].
49		-|[[Annotation>>doc:sdmx:Glossary 2\.1.Annotation.WebHome]]|(% style="width:262px" %)// //|(% style="width:543px" %)Additional descriptive information attached to an object.
50		-| |(% style="width:262px" %)id|(% style="width:543px" %)Identifier for the [[Annotation>>doc:sdmx:Glossary 2\.1.Annotation.WebHome]]. It can be used to disambiguate one [[Annotation>>doc:sdmx:Glossary 2\.1.Annotation.WebHome]] from another where there are several [[Annotations>>doc:sdmx:Glossary 2\.1.Annotation.WebHome]] for the same annotated object.
51		-| |(% style="width:262px" %)[[title>>doc:sdmx:Glossary 2\.1.Title.WebHome]]|(% style="width:543px" %)A [[title>>doc:sdmx:Glossary 2\.1.Title.WebHome]] used to identify an [[annotation>>doc:sdmx:Glossary 2\.1.Annotation.WebHome]].
52		-| |(% style="width:262px" %)type|(% style="width:543px" %)Specifies how the [[annotation>>doc:sdmx:Glossary 2\.1.Annotation.WebHome]] is to be processed.
	48	+)))|(% style="width:543px" %)Objects of classes derived from this can have attached annotations.
	49	+|Annotation|(% style="width:262px" %)// //|(% style="width:543px" %)Additional descriptive information attached to an object.
	50	+| |(% style="width:262px" %)id|(% style="width:543px" %)Identifier for the Annotation. It can be used to disambiguate one Annotation from another where there are several Annotations for the same annotated object.
	51	+| |(% style="width:262px" %)title|(% style="width:543px" %)A title used to identify an annotation.
	52	+| |(% style="width:262px" %)type|(% style="width:543px" %)Specifies how the annotation is to be processed.
53	53	| |(% style="width:262px" %)url|(% style="width:543px" %)A link to external descriptive text.
54		-| |(% style="width:262px" %)value|(% style="width:543px" %)A non-localised version of the [[Annotation>>doc:sdmx:Glossary 2\.1.Annotation.WebHome]] content.
55		-| |(% style="width:262px" %)+url|(% style="width:543px" %)An International URI provides a set of links that are [[language>>doc:sdmx:Glossary 2\.1.Language.WebHome]] specific, via this role.
56		-| |(% style="width:262px" %)+text|(% style="width:543px" %)An [[International String>>doc:sdmx:Glossary 2\.1.International string.WebHome]] provides the multilingual text content of the [[annotation>>doc:sdmx:Glossary 2\.1.Annotation.WebHome]] via this role.
	54	+| |(% style="width:262px" %)value|(% style="width:543px" %)A non-localised version of the Annotation content.
	55	+| |(% style="width:262px" %)+url|(% style="width:543px" %)An International URI provides a set of links that are language specific, via this role.
	56	+| |(% style="width:262px" %)+text|(% style="width:543px" %)An International String provides the multilingual text content of the annotation via this role.
57	57	|InternationalUri|(% style="width:262px" %) |(% style="width:543px" %)The International Uri is a collection of Localised URIs and supports linking to external descriptions in multiple locales.
58		-|LocalisedUri|(% style="width:262px" %) |(% style="width:543px" %)The Localised URI supports the link to an external description in one locale (locale is similar to [[language>>doc:sdmx:Glossary 2\.1.Language.WebHome]] but includes geographic variations such as Canadian French, US English etc.).
	58	+|LocalisedUri|(% style="width:262px" %) |(% style="width:543px" %)The Localised URI supports the link to an external description in one locale (locale is similar to language but includes geographic variations such as Canadian French, US English etc.).
59	59	|//IdentifiableArtefact//|(% style="width:262px" %)(((
60	60	Superclass is //AnnotableArtefact//
61	61	Base inheritance sub classes are:
62	62	//NameableArtefact//
63		-)))|(% style="width:543px" %)Provides identity to all derived classes. It also provides [[annotations>>doc:sdmx:Glossary 2\.1.Annotation.WebHome]] to derived classes because it is a subclass of [[Annotable Artefact>>doc:sdmx:Glossary 2\.1.Annotable artefact.WebHome]].
	63	+)))|(% style="width:543px" %)Provides identity to all derived classes. It also provides annotations to derived classes because it is a subclass of Annotable Artefact.
64	64	| |(% style="width:262px" %)id|(% style="width:543px" %)The unique identifier of the object.
65	65	| |(% style="width:262px" %)uri|(% style="width:543px" %)Universal resource identifier that may or may not be resolvable.
66	66	| |(% style="width:262px" %)urn|(% style="width:543px" %)Universal resource name – this is for use in registries: all registered objects have a urn.
...	...	@@ -67,11 +67,11 @@
67	67	|//NameableArtefact//|(% style="width:262px" %)(((
68	68	Superclass is //IdentifiableArtefact// Base inheritance sub classes are:
69	69	//VersionableArtefact//
70		-)))|(% style="width:543px" %)Provides a Name and Description to all derived classes in addition to identification and [[annotations>>doc:sdmx:Glossary 2\.1.Annotation.WebHome]].
71		-| |(% style="width:262px" %)+description|(% style="width:543px" %)A multi-lingual description is provided by this role via the [[International String>>doc:sdmx:Glossary 2\.1.International string.WebHome]] class.
72		-| |(% style="width:262px" %)+name|(% style="width:543px" %)A multi-lingual name is provided by this role via the [[International String>>doc:sdmx:Glossary 2\.1.International string.WebHome]] class
73		-|InternationalString|(% style="width:262px" %) |(% style="width:543px" %)The [[International String>>doc:sdmx:Glossary 2\.1.International string.WebHome]] is a collection of Localised Strings and supports the [[representation>>doc:sdmx:Glossary 2\.1.Representation.WebHome]] of text in multiple locales.
74		-|LocalisedString|(% style="width:262px" %) |(% style="width:543px" %)The Localised String supports the [[representation>>doc:sdmx:Glossary 2\.1.Representation.WebHome]] of text in one locale (locale is similar to [[language>>doc:sdmx:Glossary 2\.1.Language.WebHome]] but includes geographic variations such as Canadian French, US English etc.).
	70	+)))|(% style="width:543px" %)Provides a Name and Description to all derived classes in addition to identification and annotations.
	71	+| |(% style="width:262px" %)+description|(% style="width:543px" %)A multi-lingual description is provided by this role via the International String class.
	72	+| |(% style="width:262px" %)+name|(% style="width:543px" %)A multi-lingual name is provided by this role via the International String class
	73	+|InternationalString|(% style="width:262px" %) |(% style="width:543px" %)The International String is a collection of Localised Strings and supports the representation of text in multiple locales.
	74	+|LocalisedString|(% style="width:262px" %) |(% style="width:543px" %)The Localised String supports the representation of text in one locale (locale is similar to language but includes geographic variations such as Canadian French, US English etc.).
75	75	| |(% style="width:262px" %)label|(% style="width:543px" %)Label of the string.
76	76	| |(% style="width:262px" %)locale|(% style="width:543px" %)The geographic locale of the string e.g French, Canadian French.
77	77	|//VersionableArtefact//|(% style="width:262px" %)(((
...	...	@@ -80,18 +80,18 @@
80	80	Base inheritance sub classes are:
81	81	//MaintainableArtefact//
82	82	)))|(% style="width:543px" %)Provides versioning information for all derived objects.
83		-| |(% style="width:262px" %)[[version>>doc:sdmx:Glossary 2\.1.Version.WebHome]]|(% style="width:543px" %)A [[version>>doc:sdmx:Glossary 2\.1.Version.WebHome]] string following [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] versioning rules.
84		-| |(% style="width:262px" %)validFrom|(% style="width:543px" %)Date from which the [[version>>doc:sdmx:Glossary 2\.1.Version.WebHome]] is valid
85		-| |(% style="width:262px" %)validTo|(% style="width:543px" %)Date from which [[version>>doc:sdmx:Glossary 2\.1.Version.WebHome]] is superseded
	83	+| |(% style="width:262px" %)version|(% style="width:543px" %)A version string following SDMX versioning rules.
	84	+| |(% style="width:262px" %)validFrom|(% style="width:543px" %)Date from which the version is valid
	85	+| |(% style="width:262px" %)validTo|(% style="width:543px" %)Date from which version is superseded
86	86	|//MaintainableArtefact//|(% style="width:262px" %)(((
87	87	Inherits from
88	88
89	89	//VersionableArtefact//
90		-)))|(% style="width:543px" %)An abstract class to group together primary [[structural metadata>>doc:sdmx:Glossary 2\.1.Structural metadata.WebHome]] [[artefacts>>doc:sdmx:Glossary 2\.1.Artefact.WebHome]] that are maintained by an Agency.
91		-| |(% style="width:262px" %)[[isExternalReference>>doc:sdmx:Glossary 2\.1.isExternalReference.WebHome]]|(% style="width:543px" %)If set to “true” it indicates that the content of the object is held externally.
92		-| |(% style="width:262px" %)structureURL|(% style="width:543px" %)The URL of an [[SDMX-ML>>doc:sdmx:Glossary 2\.1.SDMX-ML.WebHome]] document containing the external object.
93		-| |(% style="width:262px" %)serviceURL|(% style="width:543px" %)The URL of an [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]]-compliant web service from which the external object can be retrieved.
94		-| |(% style="width:262px" %)+maintainer|(% style="width:543px" %)Association to the [[Maintenance Agency>>doc:sdmx:Glossary 2\.1.Maintenance agency.WebHome]] responsible for maintaining the [[artefact>>doc:sdmx:Glossary 2\.1.Artefact.WebHome]].
	90	+)))|(% style="width:543px" %)An abstract class to group together primary structural metadata artefacts that are maintained by an Agency.
	91	+| |(% style="width:262px" %)isExternalReference|(% style="width:543px" %)If set to “true” it indicates that the content of the object is held externally.
	92	+| |(% style="width:262px" %)structureURL|(% style="width:543px" %)The URL of an SDMX-ML document containing the external object.
	93	+| |(% style="width:262px" %)serviceURL|(% style="width:543px" %)The URL of an SDMX-compliant web service from which the external object can be retrieved.
	94	+| |(% style="width:262px" %)+maintainer|(% style="width:543px" %)Association to the Maintenance Agency responsible for maintaining the artefact.
95	95	|Agency|(% style="width:262px" %) |(% style="width:543px" %)See section on “Organisations”
96	96
97	97	== 3.3 Basic Inheritance ==
...	...	@@ -98,7 +98,7 @@
98	98
99	99	=== 3.3.1 Class Diagram – Basic Inheritance from the Base Inheritance Classes ===
100	100
101		-[[image:image37.png]]
	101	+[[image:1749246130530-261.jpeg]]
102	102
103	103	**Figure 11: Basic Inheritance from the Base Structures**
104	104
...	...	@@ -112,7 +112,7 @@
112	112
113	113	=== 3.4.1 Class Diagram ===
114	114
115		-[[image:image38.png]]
	115	+[[image:1749246130536-128.jpeg]]
116	116
117	117	**Figure 12: Class Diagram of Basic Data Types**
118	118
...	...	@@ -124,7 +124,7 @@
124	124
125	125	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:
126	126
127		-* 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 (% id="confict-imterms-29" %)version(%%) 1.0 of the SDMX Technical Standards.
	127	+* 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.
128	128	* Replace: Data/metadata is to be replaced and may also include additional data/metadata to be appended.
129	129	* Delete: Data/Metadata is to be deleted.
130	130	* Information: Data and metadata are for information purposes.
...	...	@@ -149,9 +149,9 @@
149	149
150	150	=== 3.5.2 Class Diagram ===
151	151
152		-[[image:image39.png]]
	152	+[[image:1749246130543-644.jpeg]]
153	153
154		-**Figure 13 The (% id="confict-imterms-43" %)Item(%%) Scheme pattern**
	154	+**Figure 13 The Item Scheme pattern**
155	155
156	156	=== 3.5.3 Explanation of the Diagram ===
157	157
...	...	@@ -183,46 +183,58 @@
183	183	ReportingTaxonomy
184	184	//OrganisationScheme//
185	185	TransformationScheme
186		-CustomTypeScheme NamePersonalisationScheme
	186	+CustomTypeScheme NamePersonalisationSc heme
187	187	RulesetScheme
188	188	VtlMappingScheme
189		-UserDefinedOperatorScheme
	189	+UserDefinedOperatorSc heme
190	190	)))|(% style="width:583px" %)The descriptive information for an arrangement or division of objects into groups based on characteristics, which the objects have in common.
191	191	| |(% style="width:297px" %)isPartial|(% style="width:583px" %)Denotes whether the Item Scheme contains a subset of the full set of Items in the maintained scheme.
192	192	| |(% style="width:297px" %)/items|(% style="width:583px" %)Association to the Items in the scheme.
193	193	|//Item//|(% style="width:297px" %)(((
194	194	Inherits from:
	195	+
195	195	//NameableArtefact//
	197	+
196	196	Direct sub classes are
	199	+
197	197	Category
	201	+
198	198	Concept
	203	+
199	199	Code
200		-ReportingCategory
201		-//Organisation//
	205	+
	206	+ReportingCategory //Organisation//
	207	+
202	202	Transformation
	209	+
203	203	CustomType
	211	+
204	204	NamePersonalisation
	213	+
205	205	Ruleset
	215	+
206	206	VtlMapping
207		-UserDefinedOperator
	217	+
	218	+UserDefinedOperator// //hierarchy
208	208	)))|(% style="width:583px" %)(((
209	209	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.
	221	+This allows an Item optionally to have one or more child Items
210	210	)))
211		-| |(% style="width:297px" %)hierarchy|(% style="width:583px" %)This allows an Item optionally to have one or more child Items
212	212
213	213	== 3.6 The Structure Pattern ==
214	214
215	215	=== 3.6.1 Context ===
216	216
217		-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 (% id="confict-imterms-88" %)Structure(%%) Definition, and Metadata (% id="confict-imterms-89" %)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.
	228	+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.
218	218
219	219	=== 3.6.2 Class Diagrams ===
220	220
221		-[[image:image40.png]]
	232	+(% class="wikigeneratedid" %)
	233	+[[image:1749246130548-601.jpeg]]
222	222
223	223	**Figure 14: The Structure Pattern**
224	224
225		-[[image:image41.png]]
	237	+[[image:1749246130554-995.jpeg]]
226	226
227	227	**Figure 15: Representation within the Structure Pattern**
228	228
...	...	@@ -237,9 +237,13 @@
237	237	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:
238	238
239	239	DimensionDescriptor: Dimension, TimeDimension
	252	+
240	240	GroupDimensionDescriptor: Dimension, TimeDimension
	254	+
241	241	MeasureDescriptor: Measure
	256	+
242	242	AttributeDescriptor: DataAttribute, MetadataAttributeRef
	258	+
243	243	MetadataAttributeDescriptor: MetadataAttribute
244	244
245	245	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,53 +260,72 @@
260	260
261	261	==== 3.6.3.2 Definitions ====
262	262
263		-(% style="width:1368.29px" %)
264		-|**Class**|**Feature**|(% style="width:897px" %)**Description**
	279	+|**Class**|**Feature**|**Description**
265	265	|StructureUsage|(((
266	266	Inherits from:
	282	+
267	267	//MaintainableArtefact//
	284	+
268	268	Sub classes are:
	286	+
269	269	Dataflow
	288	+
270	270	Metadataflow
271		-)))|(% style="width:897px" %)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.
272		-| |structure|(% style="width:897px" %)An association to a Structure specifying the structure of the artefact.
	290	+)))|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.
	291	+| |structure|An association to a Structure specifying the structure of the artefact.
273	273	|Structure|(((
274	274	Inherits from:
	294	+
275	275	//MaintainableArtefact//
	296	+
276	276	Sub classes are:
277		-DataStructureDefinition MetadataStructureDefinition
278		-)))|(% style="width:897px" %)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.
279		-| |grouping|(% style="width:897px" %)A composite association to one or more component lists.
	298	+
	299	+DataStructureDefinition MetadataStructureDefinit ion
	300	+)))|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.
	301	+| |grouping|A composite association to one or more component lists.
280	280	|//ComponentList//|(((
281	281	Inherits from:
	304	+
282	282	//IdentifiableArtefact//
	306	+
283	283	Sub classes are:
	308	+
284	284	DimensionDescriptor
	310	+
285	285	GroupDimensionDescriptor
	312	+
286	286	MeasureDescriptor
287		-AttributeDescriptor MetadataAttributeDescriptor
288		-)))|(% style="width:897px" %)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.
289		-| |components|(% style="width:897px" %)An aggregate association to one or more components which make up the list.
	314	+
	315	+AttributeDescriptor MetadataAttributeDescrip tor
	316	+)))|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.
	317	+| |components|An aggregate association to one or more components which make up the list.
290	290	|//Component//|(((
291	291	Inherits from:
	320	+
292	292	//IdentifiableArtefact//
	322	+
293	293	Sub classes are:
	324	+
294	294	Measure
295		-//AttributeComponent
296		-DimensionComponent//
297		-)))|(% style="width:897px" %)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.
298		-| |conceptIdentity|(% style="width:897px" %)Association to a Concept in a Concept Scheme that identifies and defines the semantic of the Component.
299		-| |localRepresentation|(% style="width:897px" %)(((
300		-Association to the Representation of the Component if this is different from the coreRepresentation of the Concept, which the Component uses (ConceptUsage).
	326	+
	327	+//AttributeComponent//
	328	+
	329	+//DimensionComponent//
	330	+)))|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.
	331	+| |conceptIdentity|Association to a Concept in a Concept Scheme that identifies and defines the semantic of the Component.
	332	+| |localRepresentation|(((
	333	+Association to the Representation of the Component if this is different from the coreRepresentation of the
	334	+
	335	+Concept, which the Component uses (ConceptUsage).
301	301	)))
302		-|Representation| |(% style="width:897px" %)The allowable value or format for Component or Concept
303		-| |+enumerated|(% style="width:897px" %)Association to an enumerated list that contains the allowable content for the Component when reported in a data or metadata set. The type of enumerated list that is allowed for any concrete Component is shown in the constraints on the association.
304		-| |+nonEnumerated|(% style="width:897px" %)Association to a set of Facets that define the allowable format for the content of the Component when reported in a data or metadata set.
305		-|Facet| |(% style="width:897px" %)Defines the format for the content of the Component when reported in a data or metadata set.
306		-| |facetType|(% style="width:897px" %)A specific content type, which is constrained by the Facet Type enumeration.
307		-| |facetValueType|(% style="width:897px" %)The format of the value of a Component when reported in a data or metadata set. This is constrained by the Facet Value Type enumeration.
308		-| |+itemSchemeFacet|(% style="width:897px" %)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.
309		-|ExtendedFacet| |(% style="width:897px" %)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.
	337	+|Representation| |The allowable value or format for Component or Concept
	338	+| |+enumerated|Association to an enumerated list that contains the allowable content for the Component when reported in a data or metadata set. The type of enumerated list that is allowed for any concrete Component is shown in the constraints on the association.
	339	+| |+nonEnumerated|Association to a set of Facets that define the allowable format for the content of the Component when reported in a data or metadata set.
	340	+|Facet| |Defines the format for the content of the Component when reported in a data or metadata set.
	341	+| |facetType|A specific content type, which is constrained by the Facet Type enumeration.
	342	+| |facetValueType|The format of the value of a Component when reported in a data or metadata set. This is constrained by the Facet Value Type enumeration.
	343	+| |+itemSchemeFacet|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.
	344	+|ExtendedFacet| |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.
310	310
311	311	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.
312	312
...	...	@@ -314,28 +314,28 @@
314	314
315	315	The majority of SDMX FacetValueTypes are compatible with those found in XML Schema, and have equivalents in most current implementation platforms:
316	316
317		-|(% style="width:198px" %)(((
	352	+|(% style="width:188px" %)(((
318	318	**SDMX Facet Value Type**
319		-)))|(% style="width:204px" %)**XML Schema Data Type**|(% style="width:209px" %)**JSON Schema Data Type**|(% style="width:187px" %)(((
	354	+)))|(% style="width:203px" %)**XML Schema Data Type**|(% style="width:207px" %)**JSON Schema Data Type**|(% style="width:184px" %)(((
320	320	**.NET Framework Type**
321		-)))|(% style="width:817px" %)**Java Data Type**
322		-|(% style="width:198px" %)String|(% style="width:204px" %)xsd:string|(% style="width:209px" %)string|(% style="width:187px" %)System.String|(% style="width:817px" %)java.lang.String
323		-|(% style="width:198px" %)Big Integer|(% style="width:204px" %)xsd:integer|(% style="width:209px" %)integer|(% style="width:187px" %)System.Decimal|(% style="width:817px" %)java.math.BigInteger
324		-|(% style="width:198px" %)Integer|(% style="width:204px" %)xsd:int|(% style="width:209px" %)integer|(% style="width:187px" %)System.Int32|(% style="width:817px" %)int
325		-|(% style="width:198px" %)Long|(% style="width:204px" %)xsd.long|(% style="width:209px" %)integer|(% style="width:187px" %)System.Int64|(% style="width:817px" %)long
326		-|(% style="width:198px" %)Short|(% style="width:204px" %)xsd:short|(% style="width:209px" %)integer|(% style="width:187px" %)System.Int16|(% style="width:817px" %)short
327		-|(% style="width:198px" %)Decimal|(% style="width:204px" %)xsd:decimal|(% style="width:209px" %)number|(% style="width:187px" %)System.Decimal|(% style="width:817px" %)java.math.BigDecimal
328		-|(% style="width:198px" %)Float|(% style="width:204px" %)xsd:float|(% style="width:209px" %)number|(% style="width:187px" %)System.Single|(% style="width:817px" %)float
329		-|(% style="width:198px" %)Double|(% style="width:204px" %)xsd:double|(% style="width:209px" %)number|(% style="width:187px" %)System.Double|(% style="width:817px" %)double
330		-|(% style="width:198px" %)Boolean|(% style="width:204px" %)xsd:boolean|(% style="width:209px" %)boolean|(% style="width:187px" %)System.Boolean|(% style="width:817px" %)boolean
331		-|(% style="width:198px" %)URI|(% style="width:204px" %)xsd:anyURI|(% style="width:209px" %)string:uri|(% style="width:187px" %)System.Uri|(% style="width:817px" %)Java.net.URI or java.lang.String
332		-|(% style="width:198px" %)DateTime|(% style="width:204px" %)xsd:dateTime|(% style="width:209px" %)string:datetime|(% style="width:187px" %)System.DateTime|(% style="width:817px" %)javax.xml.datatype.XML GregorianCalendar
333		-|(% style="width:198px" %)Time|(% style="width:204px" %)xsd:time|(% style="width:209px" %)string:time|(% style="width:187px" %)System.DateTime|(% style="width:817px" %)javax.xml.datatype.XML GregorianCalendar
334		-|(% style="width:198px" %)GregorianYear|(% style="width:204px" %)xsd:gYear|(% style="width:209px" %)string{{footnote}}In the JSON schemas, more complex data types are complemented with regular expressions, whenever no direct mapping to a standard type exists.{{/footnote}}|(% style="width:187px" %)System.DateTime|(% style="width:817px" %)javax.xml.datatype.XML GregorianCalendar
335		-|(% style="width:198px" %)GregorianMonth|(% style="width:204px" %)xsd:gYearMonth|(% style="width:209px" %)string|(% style="width:187px" %)System.DateTime|(% style="width:817px" %)javax.xml.datatype.XML GregorianCalendar
336		-|(% style="width:198px" %)GregorianDay|(% style="width:204px" %)xsd:date|(% style="width:209px" %)string|(% style="width:187px" %)System.DateTime|(% style="width:817px" %)javax.xml.datatype.XML GregorianCalendar
337		-|(% style="width:198px" %)Day, MonthDay, Month|(% style="width:204px" %)xsd:g*|(% style="width:209px" %)string|(% style="width:187px" %)System.DateTime|(% style="width:817px" %)javax.xml.datatype.XML GregorianCalendar
338		-|(% style="width:198px" %)Duration|(% style="width:204px" %)xsd:duration|(% style="width:209px" %)string|(% style="width:187px" %)System.TimeSpan|(% style="width:817px" %)javax.xml.datatype.Dur ation
	356	+)))|(% style="width:833px" %)**Java Data Type**
	357	+|(% style="width:188px" %)String|(% style="width:203px" %)xsd:string|(% style="width:207px" %)string|(% style="width:184px" %)System.String|(% style="width:833px" %)java.lang.String
	358	+|(% style="width:188px" %)Big Integer|(% style="width:203px" %)xsd:integer|(% style="width:207px" %)integer|(% style="width:184px" %)System.Decimal|(% style="width:833px" %)java.math.BigInteger
	359	+|(% style="width:188px" %)Integer|(% style="width:203px" %)xsd:int|(% style="width:207px" %)integer|(% style="width:184px" %)System.Int32|(% style="width:833px" %)int
	360	+|(% style="width:188px" %)Long|(% style="width:203px" %)xsd.long|(% style="width:207px" %)integer|(% style="width:184px" %)System.Int64|(% style="width:833px" %)long
	361	+|(% style="width:188px" %)Short|(% style="width:203px" %)xsd:short|(% style="width:207px" %)integer|(% style="width:184px" %)System.Int16|(% style="width:833px" %)short
	362	+|(% style="width:188px" %)Decimal|(% style="width:203px" %)xsd:decimal|(% style="width:207px" %)number|(% style="width:184px" %)System.Decimal|(% style="width:833px" %)java.math.BigDecimal
	363	+|(% style="width:188px" %)Float|(% style="width:203px" %)xsd:float|(% style="width:207px" %)number|(% style="width:184px" %)System.Single|(% style="width:833px" %)float
	364	+|(% style="width:188px" %)Double|(% style="width:203px" %)xsd:double|(% style="width:207px" %)number|(% style="width:184px" %)System.Double|(% style="width:833px" %)double
	365	+|(% style="width:188px" %)Boolean|(% style="width:203px" %)xsd:boolean|(% style="width:207px" %)boolean|(% style="width:184px" %)System.Boolean|(% style="width:833px" %)boolean
	366	+|(% style="width:188px" %)URI|(% style="width:203px" %)xsd:anyURI|(% style="width:207px" %)string:uri|(% style="width:184px" %)System.Uri|(% style="width:833px" %)Java.net.URI or java.lang.String
	367	+|(% style="width:188px" %)DateTime|(% style="width:203px" %)xsd:dateTime|(% style="width:207px" %)string:datetime|(% style="width:184px" %)System.DateTime|(% style="width:833px" %)javax.xml.datatype.XML GregorianCalendar
	368	+|(% style="width:188px" %)Time|(% style="width:203px" %)xsd:time|(% style="width:207px" %)string:time|(% style="width:184px" %)System.DateTime|(% style="width:833px" %)javax.xml.datatype.XML GregorianCalendar
	369	+|(% style="width:188px" %)GregorianYear|(% style="width:203px" %)xsd:gYear|(% style="width:207px" %)string[[(% class="wikiinternallink wikiinternallink" %)^^~[1~]^^>>path:#_ftn1]]|(% style="width:184px" %)System.DateTime|(% style="width:833px" %)javax.xml.datatype.XML GregorianCalendar
	370	+|(% style="width:188px" %)GregorianMonth|(% style="width:203px" %)xsd:gYearMonth|(% style="width:207px" %)string|(% style="width:184px" %)System.DateTime|(% style="width:833px" %)javax.xml.datatype.XML GregorianCalendar
	371	+|(% style="width:188px" %)GregorianDay|(% style="width:203px" %)xsd:date|(% style="width:207px" %)string|(% style="width:184px" %)System.DateTime|(% style="width:833px" %)javax.xml.datatype.XML GregorianCalendar
	372	+|(% style="width:188px" %)Day, MonthDay, Month|(% style="width:203px" %)xsd:g*|(% style="width:207px" %)string|(% style="width:184px" %)System.DateTime|(% style="width:833px" %)javax.xml.datatype.XML GregorianCalendar
	373	+|(% style="width:188px" %)Duration|(% style="width:203px" %)xsd:duration|(% style="width:207px" %)string|(% style="width:184px" %)System.TimeSpan|(% style="width:833px" %)javax.xml.datatype.Dur ation
339	339
340	340	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.
341	341
...	...	@@ -342,7 +342,7 @@
342	342	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.
343	343
344	344	(% style="width:981.835px" %)
345		-|(% style="width:107px" %)**Facet Type**|(% style="width:872px" %)**Explanation**
	380	+|(% style="width:107px" %)**Facet Type**|(% style="width:872px" %)**Explanation**
346	346	|(% style="width:107px" %)isSequence|(% style="width:872px" %)The isSequence facet indicates whether the values are intended to be ordered, and it may work in combination with the interval, startValue,and endValue facet or the timeInterval, startTime, and endTime, facets. If this attribute holds a value of true, a start value or time and a numeric or time interval must be supplied. If an end value is not given, then the sequence continues indefinitely.
347	347	|(% style="width:107px" %)interval|(% style="width:872px" %)The interval attribute specifies the permitted interval (increment) in a sequence. In order for this to be used, the isSequence attribute must have a value of true.
348	348	|(% style="width:107px" %)startValue|(% style="width:872px" %)The startValue facet is used in conjunction with the isSequence and interval facets (which must be set in order to use this facet). This facet isused for a numeric sequence and indicates the starting point of the sequence. This value is mandatory for a numeric sequence to be expressed.
...	...	@@ -357,6 +357,8 @@
357	357	|(% style="width:107px" %)Decimals|(% style="width:872px" %)The decimals facet indicates the number of characters allowed after the decimal separator.
358	358	|(% style="width:107px" %)pattern|(% style="width:872px" %)The pattern attribute holds any regular expression permitted in the implementation syntax (e.g., W3C XML Schema).
359	359
	395	+
	396	+
360	360	----
361	361
362		-{{putFootnotes/}}
	399	+[[~[1~]>>path:#_ftnref1]] In the JSON schemas, more complex data types are complemented with regular expressions, whenever no direct mapping to a standard type exists.

image36.png

Author

...	...	@@ -1,1 +1,0 @@
1		-xwiki:XWiki.arturkryazhev

Size

...	...	@@ -1,1 +1,0 @@
1		-50.2 KB

Content

image37.png

Author

...	...	@@ -1,1 +1,0 @@
1		-xwiki:XWiki.helena

Size

...	...	@@ -1,1 +1,0 @@
1		-131.4 KB

Content

image38.png

Author

...	...	@@ -1,1 +1,0 @@
1		-xwiki:XWiki.helena

Size

...	...	@@ -1,1 +1,0 @@
1		-97.3 KB

Content

image39.png

Author

...	...	@@ -1,1 +1,0 @@
1		-xwiki:XWiki.helena

Size

...	...	@@ -1,1 +1,0 @@
1		-150.0 KB

Content

image40.png

Author

...	...	@@ -1,1 +1,0 @@
1		-xwiki:XWiki.helena

Size

...	...	@@ -1,1 +1,0 @@
1		-104.9 KB

Content

image41.png

Author

...	...	@@ -1,1 +1,0 @@
1		-xwiki:XWiki.helena

Size

...	...	@@ -1,1 +1,0 @@
1		-130.6 KB

Content

1749246130522-547.jpeg

Author

...	...	@@ -1,0 +1,1 @@
	1	+xwiki:XWiki.helena

Size

...	...	@@ -1,0 +1,1 @@
	1	+53.8 KB

Content

1749246130530-261.jpeg

Author

...	...	@@ -1,0 +1,1 @@
	1	+xwiki:XWiki.helena

Size

...	...	@@ -1,0 +1,1 @@
	1	+73.2 KB

Content

1749246130536-128.jpeg

Author

...	...	@@ -1,0 +1,1 @@
	1	+xwiki:XWiki.helena

Size

...	...	@@ -1,0 +1,1 @@
	1	+73.1 KB

Content

1749246130543-644.jpeg

Author

...	...	@@ -1,0 +1,1 @@
	1	+xwiki:XWiki.helena

Size

...	...	@@ -1,0 +1,1 @@
	1	+50.8 KB

Content

1749246130548-601.jpeg

Author

...	...	@@ -1,0 +1,1 @@
	1	+xwiki:XWiki.helena

Size

...	...	@@ -1,0 +1,1 @@
	1	+61.3 KB

Content

1749246130554-995.jpeg

Author

...	...	@@ -1,0 +1,1 @@
	1	+xwiki:XWiki.helena

Size

...	...	@@ -1,0 +1,1 @@
	1	+55.9 KB

Content

SKMS.Methodology.Code.MethodologyClass[0]

Index

...	...	@@ -1,1 +1,0 @@
1		-4

SUZ.Methodology.Code.MethodologyClass[0]

index

...	...	@@ -1,0 +1,1 @@
	1	+4