Changes for page 4 Specific Item Schemes

Last modified by Helena K. on 2026/06/08 16:44

From version 3.3
edited by Helena K.
on 2025/06/08 01:06
Change comment: There is no comment for this version
To version 36.4
edited by Helena K.
on 2026/06/08 16:24
Change comment: There is no comment for this version

Summary

Details

Page properties
Tags
... ... @@ -1,0 +1,1 @@
1 +Artefact|Attribute|Categorisation|Category Scheme|Codelist|Concept Scheme|Constraint|Contact phone number|Data Consumer|Data Provider|Data Structure Definition|Hierarchy|Language|Maintenance agency|Metadata Set|Metadata Structure Definition|Reference metadata|Reporting Category|Statistical Data and Metadata eXchange|Statistical classification|Statistical unit|Structural metadata|Validation and Transformation Language
Content
... ... @@ -4,33 +4,21 @@
4 4  
5 5  == 4.1 Introduction ==
6 6  
7 -The structures that are an arrangement of objects into hierarchies or lists based on characteristics, and which are maintained as a group inherit from //ItemScheme//. These concrete classes are:
7 +The structures that are an arrangement of objects into [[hierarchies>>doc:sdmx:Glossary 2\.1.Hierarchy.WebHome]] or lists based on characteristics, and which are maintained as a group inherit from //ItemScheme//. These concrete classes are:
8 8  
9 -Codelist
10 -
9 +[[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]]
11 11  ConceptScheme
12 -
13 13  CategoryScheme
14 -
15 -AgencyScheme, DataProviderScheme, MetadataProviderScheme,
16 -
17 -DataConsumerScheme, OrganisationUnitScheme, which all inherit from the abstract class //OrganisationScheme//
18 -
12 +AgencyScheme, DataProviderScheme, MetadataProviderScheme, DataConsumerScheme, OrganisationUnitScheme, which all inherit from the abstract class //OrganisationScheme//
19 19  ReportingTaxonomy
20 -
21 21  TransformationScheme
22 -
23 23  RulesetScheme
24 -
25 25  UserDefinedOperatorScheme
26 -
27 27  NamePersonalisationScheme
28 -
29 29  CustomTypeScheme
30 -
31 31  VtlMappingScheme
32 32  
33 -Note that the VTL related schemes (the last 6 of the above list) are detailed in a dedicated section below (section 15).
21 +Note that the [[VTL>>doc:sdmx:Glossary 2\.1.Validation and transformation language.WebHome]] related schemes (the last 6 of the above list) are detailed in a dedicated section below ([[section 15>>doc:Methodology.SDMX 3\.1 Standards\. Section 2\. Information model.15 Validation and Transformation Language.WebHome]]).
34 34  
35 35  == 4.2 Inheritance View ==
36 36  
... ... @@ -38,9 +38,9 @@
38 38  
39 39  == 4.3 Codelist ==
40 40  
41 -==== 4.3.1 Class Diagram ====
29 +=== 4.3.1 Class Diagram ===
42 42  
43 -[[image:1749246291075-895.jpeg]]
31 +[[image:image42.png]]
44 44  
45 45  **Figure 16: Class diagram of the Codelist**
46 46  
... ... @@ -48,75 +48,74 @@
48 48  
49 49  ==== 4.3.2.1 Narrative ====
50 50  
51 -The Codelist inherits from the //ItemScheme// and therefore has the following attributes: id uri urn version validFrom validTo isExternalReference serviceURL structureURL isPartial
39 +The [[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] inherits from the //ItemScheme// and therefore has the following [[attributes>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]]: id uri urn [[version>>doc:sdmx:Glossary 2\.1.Version.WebHome]] validFrom validTo [[isExternalReference>>doc:sdmx:Glossary 2\.1.isExternalReference.WebHome]] serviceURL structureURL isPartial
52 52  
53 -The Code inherits from //Item// and has the following attributes:
41 +The [[Code>>doc:sdmx:Glossary 2\.1.Code.WebHome]] inherits from //Item// and has the following [[attributes>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]]:
54 54  
55 -id uri urn
43 +id
44 +uri
45 +urn
56 56  
57 -Both Codelist and Code have the association to InternationalString to support a multilingual name, an optional multi-lingual description, and an association to Annotation to support notes (not shown).
47 +Both [[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] and [[Code>>doc:sdmx:Glossary 2\.1.Code.WebHome]] have the association to InternationalString to support a multilingual name, an optional multi-lingual description, and an association to [[Annotation>>doc:sdmx:Glossary 2\.1.Annotation.WebHome]] to support notes (not shown).
58 58  
59 -Through the inheritance the Codelist comprise one or more Codes, and the Code itself can have one or more child Codes in the (inherited) hierarchy association. Note that a child Code can have only one parent Code in this association. A more complex Hierarhcy, which allows multiple parents is described later.
49 +Through the inheritance the [[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] comprise one or more [[Codes>>doc:sdmx:Glossary 2\.1.Code.WebHome]], and the [[Code>>doc:sdmx:Glossary 2\.1.Code.WebHome]] itself can have one or more child [[Codes>>doc:sdmx:Glossary 2\.1.Code.WebHome]] in the (inherited) [[hierarchy>>doc:sdmx:Glossary 2\.1.Hierarchy.WebHome]] association. Note that a child [[Code>>doc:sdmx:Glossary 2\.1.Code.WebHome]] can have only one parent [[Code>>doc:sdmx:Glossary 2\.1.Code.WebHome]] in this association. A more complex Hierarhcy, which allows multiple parents is described later.
60 60  
61 -A partial Codelist (where isPartial is set to 'true') is identical to a Codelist and contains the Code and associated names and descriptions, just as in a normal Codelist. However, its content is a subset of the full Codelist. The way this works is described in section 3.5.3.1 on //ItemScheme//.
51 +A partial [[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] (where isPartial is set to 'true') is identical to a [[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] and contains the [[Code>>doc:sdmx:Glossary 2\.1.Code.WebHome]] and associated names and descriptions, just as in a normal [[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]]. However, its content is a subset of the full [[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]]. The way this works is described in section [[3.5.3.1>>doc:Methodology.SDMX 3\.1 Standards\. Section 2\. Information model.3 SDMX Base Package.WebHome||anchor="H3.5.3.1Narrative"]] on //ItemScheme//.
62 62  
63 63  ==== 4.3.2.2 Definitions ====
64 64  
65 -|**Class**|**Feature**|**Description**
66 -|Codelist|(((
55 +(% style="width:912.835px" %)
56 +|**Class**|**Feature**|(% style="width:656px" %)**Description**
57 +|(%%)(% style="background-color:#d35400" %)[[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]]|(((
67 67  Inherits from
68 -
69 69  //ItemScheme//
70 -)))|A list from which some statistical concepts (coded concepts) take their values.
71 -|Code|(((
60 +)))|(% style="width:656px" %)A list from which some statistical [[concepts>>doc:sdmx:Glossary 2\.1.Concept.WebHome]] (coded [[concepts>>doc:sdmx:Glossary 2\.1.Concept.WebHome]]) take their values.
61 +|[[Code>>doc:Glossary 2\.1.Code.WebHome]]|(((
72 72  Inherits from
73 -
74 74  Item
75 -)))|A language independent set of letters, numbers or symbols that represent a concept whose meaning is described in a natural language.
76 -| |hierarchy|Associates the parent and the child codes.
77 -| |extends|Associates a Codelist with any Codelists that it may extend.
64 +)))|(% style="width:656px" %)A [[language>>doc:sdmx:Glossary 2\.1.Language.WebHome]] independent set of letters, numbers or symbols that represent a [[concept>>doc:sdmx:Glossary 2\.1.Concept.WebHome]] whose meaning is described in a natural [[language>>doc:sdmx:Glossary 2\.1.Language.WebHome]].
65 +| |[[hierarchy>>doc:sdmx:Glossary 2\.1.Hierarchy.WebHome]]|(% style="width:656px" %)Associates the parent and the child [[codes>>doc:sdmx:Glossary 2\.1.Code.WebHome]].
66 +| |extends|(% style="width:656px" %)Associates a [[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] with any [[Codelists>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] that it may extend.
78 78  
79 79  ==== 4.3.3 Class Diagram – Codelist Extension ====
80 80  
81 -[[image:1749246291156-936.jpeg]]
70 +[[image:image43.png]]
82 82  
83 83  **Figure 17: Class diagram for Codelist Extension**
84 84  
85 85  ==== 4.3.3.1 Narrative ====
86 86  
87 -A Codelist may extend other Codelists via the CodelistExtension class. The latter, via the sequence, indicates the order of precedence of the extended Codelists for conflict resolution of Codes. Besides that, the prefix property is used to ensure uniqueness of inherited Codes in the extending[[(% class="wikiinternallink wikiinternallink" %)^^~[1~]^^>>path:#_ftn1]](%%) Codelist in case conflicting Codes must be included in the latter. Each CodelistExtension association may include one InclusiveCodeSelection or one ExclusiveCodeSelection; those allow including or excluding a specific selection of Codes from the extended Codelists.
76 +A Codelist may extend other Codelists via the CodelistExtension class. The latter, via the sequence, indicates the order of precedence of the extended Codelists for conflict resolution of Codes. Besides that, the prefix property is used to ensure uniqueness of inherited Codes in the extending{{footnote}}The Codelist that extends 0..* Codelists is the 'extending' Codelist, while the Codelist(s) that are inherited is/are the 'extended' Codelist(s).{{/footnote}} Codelist in case conflicting Codes must be included in the latter. Each CodelistExtension association may include one InclusiveCodeSelection or one ExclusiveCodeSelection; those allow including or excluding a specific selection of Codes from the extended Codelists.
88 88  
89 89  The code selection classes may have MemberValues in order to specify the subset of the Codes that should be included or excluded from the extended Codelist. A MemberValue may have a value that corresponds to a Code, including its children Codes (via the cascadeValues property), or even include instances of the wildcard character ‘%’ in order to point to a set of Codes with common parts in their identifiers.
90 90  
91 91  ==== 4.3.3.2 Definitions ====
92 92  
93 -|**Class**|**Feature**|**Description**
94 -|CodelistExtension| |The association between Codelists that may extend other Codelists.
95 -| |prefix|A prefix to be used for a Codelist used in a extension, in order to avoid Code Conflicts.
96 -| |sequence|(((
97 -The order that will be used when extending a
98 -
99 -Codelist, for resolving Code conflicts. The latest Codelist used overrides any previous Codelist.
82 +(% style="width:970.835px" %)
83 +|**Class**|**Feature**|(% style="width:655px" %)**Description**
84 +|CodelistExtension| |(% style="width:655px" %)The association between Codelists that may extend other Codelists.
85 +| |prefix|(% style="width:655px" %)A prefix to be used for a Codelist used in a extension, in order to avoid Code Conflicts.
86 +| |sequence|(% style="width:655px" %)(((
87 +The order that will be used when extending a Codelist, for resolving Code conflicts. The latest Codelist used overrides any previous Codelist.
100 100  )))
101 -|InclusiveCodeSelection| |The subset of Codes to be included when extending a Codelist.
102 -|ExclusiveCodeSelection| |The subset of Codes to be excluded when extending a Codelist.
89 +|InclusiveCodeSelection| |(% style="width:655px" %)The subset of Codes to be included when extending a Codelist.
90 +|ExclusiveCodeSelection| |(% style="width:655px" %)The subset of Codes to be excluded when extending a Codelist.
103 103  |MemberValue|(((
104 104  Inherits from:
105 -
106 106  //SelectionValue//
107 -)))|A collection of values based on Codes and their children.
108 -| |cascadeValues|A property to indicate if the child Codes of the selected Code shall be included in the selection. It is also possible to include children and exclude the Code by using the 'excluderoot' value.
109 -| |value|The value of the Code to include in the selection. It may include the ‘%’ character as a wildcard.
94 +)))|(% style="width:655px" %)A collection of values based on Codes and their children.
95 +| |cascadeValues|(% style="width:655px" %)A property to indicate if the child Codes of the selected Code shall be included in the selection. It is also possible to include children and exclude the Code by using the 'excluderoot' value.
96 +| |value|(% style="width:655px" %)The value of the Code to include in the selection. It may include the ‘%’ character as a wildcard.
110 110  
111 111  === 4.3.4 Class Diagram – Geospatial Codelist ===
112 112  
113 113  The geospatial support is implemented via an extension of the normal Codelist. This is illustrated in the following diagrams.
114 114  
115 -[[image:1749246291164-838.jpeg]]
102 +[[image:image44.png]]
116 116  
117 117  **Figure 18: Inheritance for the GeoCodelist**
118 118  
119 -[[image:1749246291175-231.jpeg]]
106 +[[image:image45.png]]
120 120  
121 121  **Figure 19: Class diagram for Geospatial Codelist**
122 122  
... ... @@ -134,37 +134,33 @@
134 134  
135 135  ==== 4.3.4.2 Definitions ====
136 136  
137 -|**Class**|**Feature**|**Description**
124 +(% style="width:960.835px" %)
125 +|**Class**|**Feature**|(% style="width:559px" %)**Description**
138 138  |//GeoCodelist//|(((
139 139  Abstract Class Sub Classes:
140 -
141 141  GeographicCodelist
142 -
143 143  GeoGridCodelist
144 -)))|The abstract class that represents a special type of Codelist, which includes geospatial information.
145 -| |geoType|The type of Geo Codelist that the Codelist will become.
130 +)))|(% style="width:559px" %)The abstract class that represents a special type of Codelist, which includes geospatial information.
131 +| |geoType|(% style="width:559px" %)The type of Geo Codelist that the Codelist will become.
146 146  |//GeoRefCode//|(((
147 147  Abstract Class
148 -
149 149  Sub Classes:
150 -
151 151  GeoFeatureSetCode
152 -
153 153  GeoGridCode
154 -)))|The abstract class that represents a special type of Code, which includes geospatial information.
155 -|GeographicCodelist| |A special Codelist that has been extended to add a geographical feature set to each of its items, typically, this would include all types of administrative geographies.
156 -|GeoGridCodelist| |A code list that has defined a geographical grid composed of cells representing regular squared portions of the Earth.
157 -| |gridDefinition|Contains a regular expression string corresponding to the grid definition for the GeoGrid Codelist.
158 -|GeoFeatureSetCode| |A Code that has a geo feature set.
159 -| |value|The geo feature set of the Code, which represents a set of points defining a feature in a format defined a predefined pattern (see section 6).
160 -|GeoGridCode| |A Code that represents a Geo Grid Cell belonging in a specific grid definition.
161 -| |geoCell|The value used to assign the Code to one cell in the grid.
137 +)))|(% style="width:559px" %)The abstract class that represents a special type of Code, which includes geospatial information.
138 +|GeographicCodelist| |(% style="width:559px" %)A special Codelist that has been extended to add a geographical feature set to each of its items, typically, this would include all types of administrative geographies.
139 +|GeoGridCodelist| |(% style="width:559px" %)A code list that has defined a geographical grid composed of cells representing regular squared portions of the Earth.
140 +| |gridDefinition|(% style="width:559px" %)Contains a regular expression string corresponding to the grid definition for the GeoGridCodelist.
141 +|GeoFeatureSetCode| |(% style="width:559px" %)A Code that has a geo feature set.
142 +| |value|(% style="width:559px" %)The geo feature set of the Code, which represents a set of points defining a feature in a format defined a predefined pattern (see section 6).
143 +|GeoGridCode| |(% style="width:559px" %)A Code that represents a Geo Grid Cell belonging in a specific grid definition.
144 +| |geoCell|(% style="width:559px" %)The value used to assign the Code to one cell in the grid.
162 162  
163 163  == 4.4 ValueList ==
164 164  
165 165  === 4.4.1 Class Diagram ===
166 166  
167 -[[image:1749246291179-291.jpeg]]
150 +[[image:image46.png]]
168 168  
169 169  **Figure 20: Class diagram of the ValueList**
170 170  
... ... @@ -174,7 +174,16 @@
174 174  
175 175  A ValueList inherits from //EnumeratedList// (and hence the //MaintenableArtefact//) and thus has the following attributes:
176 176  
177 -id// //uri// //urn// //version// //validFrom// //validTo// //isExternalReference registryURL structureURL repositoryURL
160 +id
161 +uri
162 +urn
163 +version
164 +validFrom
165 +validTo
166 +isExternalReference
167 +registryURL
168 +structureURL
169 +repositoryURL
178 178  
179 179  ValueItem inherits from //EnumeratedItem//, which adds an id, with relaxed constraints, to the former.
180 180  
... ... @@ -184,41 +184,54 @@
184 184  
185 185  ==== 4.4.2.2 Definitions ====
186 186  
187 -|**Class**|**Feature**|**Description**
188 -|ValueList|(((
179 +(% style="width:929.835px" %)
180 +|**Class**|(% style="width:175px" %)**Feature**|(% style="width:632px" %)**Description**
181 +|ValueList|(% style="width:175px" %)(((
189 189  Inherits from
190 -
191 191  //EnumeratedList//
192 -)))|A list from which some statistical concepts (enumerated concepts) take their values.
193 -|ValueItem|(((
184 +)))|(% style="width:632px" %)A list from which some statistical concepts (enumerated concepts) take their values.
185 +|ValueItem|(% style="width:175px" %)(((
194 194  Inherits from
195 -
196 196  //EnumeratedItem//
197 -)))|A language independent set of letters, numbers or symbols that represent a concept whose meaning is described in a natural language.
188 +)))|(% style="width:632px" %)A language independent set of letters, numbers or symbols that represent a concept whose meaning is described in a natural language.
198 198  
199 199  == 4.5 Concept Scheme and Concepts ==
200 200  
201 201  === 4.5.1 Class Diagram - Inheritance ===
202 202  
203 -[[image:1749246291184-799.jpeg]]
194 +[[image:image47.png]]
204 204  
205 205  **Figure 21 Class diagram of the Concept Scheme**
206 206  
207 207  === 4.5.2 Explanation of the Diagram ===
208 208  
209 -The ConceptScheme inherits from the //ItemScheme //and therefore has the following attributes: id uri urn version validFrom validTo isExternalReference registryURL structureURL repositoryURL isPartial Concept inherits from Item and has the following attributes:
200 +The ConceptScheme inherits from the //ItemScheme //and therefore has the following attributes:
210 210  
211 -id uri urn
202 +id
203 +uri
204 +urn
205 +version validFrom validTo
206 +isExternalReference
207 +registryURL
208 +structureURL
209 +repositoryURL
210 +isPartial
212 212  
212 +Concept inherits from Item and has the following attributes:
213 +
214 +id
215 +uri
216 +urn
217 +
213 213  Through the inheritance from //NameableArtefact// both ConceptScheme and Concept have the association to InternationalString to support a multi-lingual name, an optional multilingual description, and an association to Annotation to support notes (not shown).
214 214  
215 215  Through the inheritance from //ItemScheme// the ConceptScheme comprise one or more Concepts, and the Concept itself can have one or more child Concepts in the (inherited) hierarchy association. Note that a child Concept can have only one parent Concept in this association.
216 216  
217 -A partial ConceptScheme (where isPartial is set to “true”) is identical to a ConceptScheme and contains the Concept and associated names and descriptions, just as in a normal ConceptScheme. However, its content is a subset of the full ConceptScheme. The way this works is described in section 3.5.3.1 on ItemScheme.
222 +A partial ConceptScheme (where isPartial is set to “true”) is identical to a ConceptScheme and contains the Concept and associated names and descriptions, just as in a normal ConceptScheme. However, its content is a subset of the full ConceptScheme. The way this works is described in section [[3.5.3.1>>doc:Methodology.SDMX 3\.1 Standards\. Section 2\. Information model.3 SDMX Base Package.WebHome||anchor="H3.5.3.1Narrative"]] on ItemScheme.
218 218  
219 219  === 4.5.3 Class Diagram Relationship ===
220 220  
221 -[[image:1749246291189-654.jpeg]]
226 +[[image:image48.png]]
222 222  
223 223  **Figure 22: Relationship class diagram of the Concept Scheme**
224 224  
... ... @@ -236,28 +236,25 @@
236 236  
237 237  ==== 4.5.4.2 Definitions ====
238 238  
239 -|**Class**|**Feature**|**Description**
240 -|(((
244 +(% style="width:912.835px" %)
245 +|(% style="width:170px" %)**Class**|(% style="width:184px" %)**Feature**|(% style="width:548px" %)**Description**
246 +|(% style="width:170px" %)(((
241 241  ConceptScheme
242 -
243 -
244 -)))|(((
248 +)))|(% style="width:184px" %)(((
245 245  Inherits from
246 -
247 247  //ItemScheme//
248 -)))|The descriptive information for an arrangement or division of concepts into groups based on characteristics, which the objects have in common.
249 -|Concept|(((
251 +)))|(% style="width:548px" %)The descriptive information for an arrangement or division of concepts into groups based on characteristics, which the objects have in common.
252 +|(% style="width:170px" %)Concept|(% style="width:184px" %)(((
250 250  Inherits from
251 -
252 252  //Item//
253 -)))|A concept is a unit of knowledge created by a unique combination of characteristics.
254 -| |/hierarchy|Associates the parent and the child concept.
255 -| |coreRepresentation|Associates a Representation.
256 -| |+ISOConcept|Association to an ISO concept reference.
257 -|ISOConceptReference| |The identity of an ISO concept definition.
258 -| |conceptAgency|The maintenance agency of the concept scheme containing the concept.
259 -| |conceptSchemeID|The identifier of the concept scheme.
260 -| |conceptID|The identifier of the concept.
255 +)))|(% style="width:548px" %)A concept is a unit of knowledge created by a unique combination of characteristics.
256 +|(% style="width:170px" %) |(% style="width:184px" %)/hierarchy|(% style="width:548px" %)Associates the parent and the child concept.
257 +|(% style="width:170px" %) |(% style="width:184px" %)coreRepresentation|(% style="width:548px" %)Associates a Representation.
258 +|(% style="width:170px" %) |(% style="width:184px" %)+ISOConcept|(% style="width:548px" %)Association to an ISO concept reference.
259 +|(% style="width:170px" %)ISOConceptReference|(% style="width:184px" %) |(% style="width:548px" %)The identity of an ISO concept definition.
260 +|(% style="width:170px" %) |(% style="width:184px" %)conceptAgency|(% style="width:548px" %)The maintenance agency of the concept scheme containing the concept.
261 +|(% style="width:170px" %) |(% style="width:184px" %)conceptSchemeID|(% style="width:548px" %)The identifier of the concept scheme.
262 +|(% style="width:170px" %) |(% style="width:184px" %)conceptID|(% style="width:548px" %)The identifier of the concept.
261 261  
262 262  == 4.6 Category Scheme ==
263 263  
... ... @@ -267,7 +267,7 @@
267 267  
268 268  === 4.6.2 Class diagram Inheritance ===
269 269  
270 -[[image:1749246291193-743.jpeg]]
272 +[[image:image49.png]]
271 271  
272 272  **Figure 23 Inheritance Class diagram of the Category Scheme**
273 273  
... ... @@ -277,21 +277,32 @@
277 277  
278 278  The categories are modelled as a hierarchical //ItemScheme//. The CategoryScheme inherits from the //ItemScheme// and has the following attributes:
279 279  
280 -id uri urn version validFrom validTo isExternalReference structureURL serviceURL isPartial
282 +id
283 +uri
284 +urn
285 +version
286 +validFrom
287 +validTo
288 +isExternalReference
289 +structureURL
290 +serviceURL
291 +isPartial
281 281  
282 282  Category inherits from //Item// and has the following attributes:
283 283  
284 -id uri urn
295 +id
296 +uri
297 +urn
285 285  
286 286  Both CategoryScheme and Category have the association to InternationalString to support a multi-lingual name, an optional multi-lingual description, and an association to Annotation to support notes (not shown on the model).
287 287  
288 288  Through the inheritance the CategoryScheme comprise one or more Categorys, and the Category itself can have one or more child Category in the (inherited) hierarchy association. Note that a child Category can have only one parent Category in this association.
289 289  
290 -A partial CategoryScheme (where isPartial is set to “true”) is identical to a CategoryScheme and contains the Category and associated names and descriptions, just as in a normal CategoryScheme. However, its content is a subset of the full CategoryScheme. The way this works is described in section 3.5.3.1 on ItemScheme.
303 +A partial CategoryScheme (where isPartial is set to “true”) is identical to a CategoryScheme and contains the Category and associated names and descriptions, just as in a normal CategoryScheme. However, its content is a subset of the full CategoryScheme. The way this works is described in section [[3.5.3.1>>doc:Methodology.SDMX 3\.1 Standards\. Section 2\. Information model.3 SDMX Base Package.WebHome||anchor="H3.5.3.1Narrative"]] on ItemScheme.
291 291  
292 292  === 4.6.4 Class diagram Relationship ===
293 293  
294 -[[image:1749246291197-631.jpeg]]
307 +[[image:image50.png]]
295 295  
296 296  **Figure 24: Relationship Class diagram of the Category Scheme**
297 297  
... ... @@ -299,38 +299,36 @@
299 299  
300 300  ==== 4.6.4.1 Definitions ====
301 301  
302 -|**Class**|**Feature**|**Description**
315 +(% style="width:935.835px" %)
316 +|**Class**|**Feature**|(% style="width:601px" %)**Description**
303 303  |CategoryScheme|(((
304 304  Inherits from
305 -
306 306  //ItemScheme//
307 -)))|The descriptive information for an arrangement or division of categories into groups based on characteristics, which the objects have in common.
308 -| |/items|Associates the categories.
320 +)))|(% style="width:601px" %)The descriptive information for an arrangement or division of categories into groups based on characteristics, which the objects have in common.
321 +| |/items|(% style="width:601px" %)Associates the categories.
309 309  |Category|(((
310 310  Inherits from
311 -
312 312  //Item//
313 -)))|An item at any level within a classification, typically tabulation categories, sections, subsections, divisions, subdivisions, groups, subgroups, classes and subclasses.
314 -| |/hierarchy|Associates the parent and the child Category.
325 +)))|(% style="width:601px" %)An item at any level within a classification, typically tabulation categories, sections, subsections, divisions, subdivisions, groups, subgroups, classes and subclasses.
326 +| |/hierarchy|(% style="width:601px" %)Associates the parent and the child Category.
315 315  |Categorisation|(((
316 316  Inherits from
317 -
318 318  //MaintainableArtefact//
319 -)))|Associates an Identifable Artefact with a Category.
320 -| |+categorisedArtefact|Associates the Identifable Artefact.
321 -| |+categorisedBy|Associates the Category.
330 +)))|(% style="width:601px" %)Associates an Identifable Artefact with a Category.
331 +| |+categorisedArtefact|(% style="width:601px" %)Associates the Identifable Artefact.
332 +| |+categorisedBy|(% style="width:601px" %)Associates the Category.
322 322  
323 323  == 4.7 Organisation Scheme ==
324 324  
325 -==== Class Diagram ====
336 +=== 4.7.1 Class Diagram ===
326 326  
327 -[[image:1749246291201-410.jpeg]]
338 +[[image:image51.png]]
328 328  
329 329  **Figure 25 The Organisation Scheme class diagram**
330 330  
331 -===== 4.7.2    Explanation of the Diagram =====
342 +=== 4.7.2 Explanation of the Diagram ===
332 332  
333 -====== 4.7.2.1 Narrative ======
344 +==== 4.7.2.1 Narrative ====
334 334  
335 335  The //OrganisationScheme// is abstract. It contains //Organisation// which is also abstract. The //Organisation// can have child //Organisation//.
336 336  
... ... @@ -340,115 +340,96 @@
340 340  1. DataProviderScheme – contains DataProvider which is restricted to a flat list of agencies (i.e., there is no hierarchy).
341 341  1. MetadataProviderScheme – contains MetadataProvider which is restricted to a flat list of agencies (i.e., there is no hierarchy).
342 342  1. DataConsumerScheme – contains DataConsumer which is restricted to a flat list of agencies (i.e., there is no hierarchy).
343 -1. OrganisationUnitScheme – contains OrganisationUnit which does inherit the /hierarchy association from Organisation.
354 +1. (% style="background-color:#d35400" %)OrganisationUnitScheme(%%) – contains OrganisationUnit which does inherit the /hierarchy association from Organisation.
344 344  
345 345  Reference metadata can be attached to the //Organisation// by means of the metadata attachment mechanism. This mechanism is explained in the Reference Metadata section of this document (see section 7). This means that the model does not specify the specific reference metadata that can be attached to a DataProvider, MetadataProvider, DataConsumer, OrganisationUnit or Agency, except for limited Contact information.
346 346  
347 -A partial //OrganisationScheme// (where isPartial is set to “true”) is identical to an //OrganisationScheme// and contains the //Organisation// and associated names and descriptions, just as in a normal //OrganisationScheme//. However, its content is a subset of the full //OrganisationScheme//. The way this works is described in section 3.5.3.1 on //ItemScheme//.
358 +A partial //OrganisationScheme// (where isPartial is set to “true”) is identical to an //OrganisationScheme// and contains the //Organisation// and associated names and descriptions, just as in a normal //OrganisationScheme//. However, its content is a subset of the full //OrganisationScheme//. The way this works is described in section [[3.5.3.1>>doc:Methodology.SDMX 3\.1 Standards\. Section 2\. Information model.3 SDMX Base Package.WebHome||anchor="H3.5.3.1Narrative"]] on //ItemScheme//.
348 348  
349 -====== 4.7.2.2 Definitions ======
360 +==== 4.7.2.2 Definitions ====
350 350  
351 -|**Class**|**Feature**|**Description**
362 +(% style="width:946.835px" %)
363 +|**Class**|**Feature**|(% style="width:540px" %)**Description**
352 352  |//OrganisationScheme//|(((
353 353  Abstract Class
354 -
355 355  Inherits from
356 -
357 357  //ItemScheme//
358 -
359 359  Sub classes are:
360 -
361 361  AgencyScheme
362 -
363 363  DataProviderScheme
364 -
365 365  MetadataProviderScheme
366 -
367 367  DataConsumerScheme
368 -
369 369  OrganisationUnitScheme
370 -)))|A maintained collection of Organisations.
371 -| |/items|Association to the Organisations in the scheme.
374 +)))|(% style="width:540px" %)A maintained collection of Organisations.
375 +| |/items|(% style="width:540px" %)Association to the Organisations in the scheme.
372 372  |//Organisation//|(((
373 373  Abstract Class
374 -
375 375  Inherits from
376 -
377 377  //Item//
378 -
379 379  Sub classes are:
380 -
381 381  Agency
382 -
383 383  DataProvider
384 -
385 385  MetadataProvider
386 -
387 387  DataConsumer
388 -
389 389  OrganisationUnit
390 -)))|An organisation is a unique framework of authority within which a person or persons act, or are designated to act, towards some purpose.
391 -| |+contact|Association to the Contact information.
392 -| |/hierarchy|Association to child Organisations.
393 -|Contact| |An instance of a role of an individual or an organization (or organization part or organization person) to whom an information item(s), a material object(s) and/or person(s) can be sent to or from in a specified context.
394 -| |name|The designation of the Contact person by a linguistic expression.
395 -| |organisationUnit|The designation of the organisational structure by a linguistic expression, within which Contact person works.
396 -| |responsibility|The function of the contact person with respect to the organisation role for which this person is the Contact.
397 -| |telephone|The telephone number of the Contact.
398 -| |fax|The fax number of the Contact.
399 -| |email|The Internet e-mail address of the Contact.
400 -| |X400|The X400 address of the Contact.
401 -| |uri|The URL address of the Contact.
402 -|AgencyScheme| |A maintained collection of Maintenance Agencies.
403 -| |/items|Association to the Maintenance Agency in the scheme.
404 -|DataProviderScheme| |A maintained collection of Data Providers.
405 -| |/items|Association to the Data Providers in the scheme.
406 -|MetadataProviderScheme| |A maintained collection of Metadata Providers.
407 -| |/items|Association to the Metadata Providers in the scheme.
408 -|DataConsumerScheme| |A maintained collection of Data Consumers.
409 -| |/items|Association to the Data Consumers in the scheme.
410 -|OrganisationUnitScheme| |A maintained collection of Organisation Units.
411 -| |/items|Association to the Organisation Units in the scheme.
386 +)))|(% style="width:540px" %)An organisation is a unique framework of authority within which a person or persons act, or are designated to act, towards some purpose.
387 +| |+contact|(% style="width:540px" %)Association to the Contact information.
388 +| |/hierarchy|(% style="width:540px" %)Association to child Organisations.
389 +|Contact| |(% style="width:540px" %)An instance of a role of an individual or an organization (or organization part or organization person) to whom an information item(s), a material object(s) and/or person(s) can be sent to or from in a specified context.
390 +| |name|(% style="width:540px" %)The designation of the Contact person by a linguistic expression.
391 +| |organisationUnit|(% style="width:540px" %)The designation of the organisational structure by a linguistic expression, within which Contact person works.
392 +| |responsibility|(% style="width:540px" %)The function of the contact person with respect to the organisation role for which this person is the Contact.
393 +| |telephone|(% style="width:540px" %)The telephone number of the Contact.
394 +| |fax|(% style="width:540px" %)The fax number of the Contact.
395 +| |email|(% style="width:540px" %)The Internet e-mail address of the Contact.
396 +| |X400|(% style="width:540px" %)The X400 address of the Contact.
397 +| |uri|(% style="width:540px" %)The URL address of the Contact.
398 +|AgencyScheme| |(% style="width:540px" %)A maintained collection of Maintenance Agencies.
399 +| |/items|(% style="width:540px" %)Association to the Maintenance Agency in the scheme.
400 +|DataProviderScheme| |(% style="width:540px" %)A maintained collection of Data Providers.
401 +| |/items|(% style="width:540px" %)Association to the Data Providers in the scheme.
402 +|MetadataProviderScheme| |(% style="width:540px" %)A maintained collection of Metadata Providers.
403 +| |/items|(% style="width:540px" %)Association to the Metadata Providers in the scheme.
404 +|DataConsumerScheme| |(% style="width:540px" %)A maintained collection of Data Consumers.
405 +| |/items|(% style="width:540px" %)Association to the Data Consumers in the scheme.
406 +|(%%)(% style="background-color:#d35400" %)OrganisationUnitScheme| |(% style="width:540px" %)A maintained collection of Organisation Units.
407 +| |/items|(% style="width:540px" %)Association to the Organisation Units in the scheme.
412 412  |Agency|(((
413 413  Inherits from
414 -
415 415  //Organisation//
416 -)))|Responsible agency for maintaining artefacts such as statistical classifications, glossaries, structural metadata such as Data and Metadata Structure Definitions, Concepts and Code lists.
411 +)))|(% style="width:540px" %)Responsible agency for maintaining artefacts such as statistical classifications, glossaries, structural metadata such as Data and Metadata Structure Definitions, Concepts and Code lists.
417 417  |DataProvider|(((
418 418  Inherits from
419 -
420 420  //Organisation//
421 -)))|An organisation that produces data.
415 +)))|(% style="width:540px" %)An organisation that produces data.
422 422  |MetadataProvider|(((
423 423  Inherits from
424 -
425 425  //Organisation//
426 -)))|An organisation that produces reference metadata.
419 +)))|(% style="width:540px" %)An organisation that produces reference metadata.
427 427  |DataConsumer|(((
428 428  Inherits from
429 -
430 430  //Organisation//
431 -)))|An organisation using data as input for further processing.
423 +)))|(% style="width:540px" %)An organisation using data as input for further processing.
432 432  |OrganisationUnit|(((
433 433  Inherits from
434 -
435 435  //Organisation//
436 -)))|A designation in the organisational structure.
437 -| |/hierarchy|Association to child Organisation Units
427 +)))|(% style="width:540px" %)A designation in the organisational structure.
428 +| |/hierarchy|(% style="width:540px" %)Association to child Organisation Units
438 438  
430 +(% style="width:946.835px" %)
431 +|(% style="width:540px" %)
439 439  
433 +== 4.8 Reporting Taxonomy ==
440 440  
441 -=== 4.8 Reporting Taxonomy ===
435 +=== 4.8.1 Class Diagram ===
442 442  
443 -==== 4.8.1 Class Diagram ====
437 +[[image:image52.png]]
444 444  
445 -[[image:1749246291205-630.jpeg]]
446 -
447 447  **Figure 26: Class diagram of the Reporting Taxonomy**
448 448  
449 -===== 4.8.2 Explanation of the Diagram =====
441 +=== 4.8.2 Explanation of the Diagram ===
450 450  
451 -====== 4.8.2.1 Narrative ======
443 +==== 4.8.2.1 Narrative ====
452 452  
453 453  In some data reporting environments, and in particular those in primary reporting, a report may comprise a variety of heterogeneous data, each described by a different //Structure//. Equally, a specific disseminated or published report may also comprise a variety of heterogeneous data. The definition of the set of linked sub reports is supported by the ReportingTaxonomy.
454 454  
... ... @@ -466,24 +466,22 @@
466 466  
467 467  Here, the nodes of Section 1 and Section 2 would not be linked to Dataflow but the other would be linked to a Dataflow (and hence the DataStructureDefinition).
468 468  
469 -A partial ReportingTaxonomy (where isPartial is set to “true”) is identical to a ReportingTaxonomy and contains the ReportingCategory and associated names and descriptions, just as in a normal ReportingTaxonomy. However, its content is a sub set of the full ReportingTaxonomy The way this works is described in section 3.5.3.1 on //ItemScheme//.
461 +A partial ReportingTaxonomy (where isPartial is set to “true”) is identical to a ReportingTaxonomy and contains the ReportingCategory and associated names and descriptions, just as in a normal ReportingTaxonomy. However, its content is a sub set of the full ReportingTaxonomy The way this works is described in section [[3.5.3.1>>doc:Methodology.SDMX 3\.1 Standards\. Section 2\. Information model.3 SDMX Base Package.WebHome||anchor="H3.5.3.1Narrative"]] on //ItemScheme//.
470 470  
471 -====== 4.8.2.2 Definitions ======
463 +==== 4.8.2.2 Definitions ====
472 472  
473 -|**Class**|**Feature**|**Description**
465 +(% style="width:969.835px" %)
466 +|**Class**|**Feature**|(% style="width:668px" %)**Description**
474 474  |ReportingTaxonomy|(((
475 475  Inherits from
476 -
477 477  //ItemScheme//
478 -)))|A scheme which defines the composition structure of a data report where each component can be described by an independent Dataflow or Metadataflow.
479 -| |/items|Associates the Reporting Category
480 -|ReportingCategory|Inherits from //Item//|A component that gives structure to the report and links to data and metadata.
481 -| |/hierarchy|Associates child Reporting Category.
482 -| |+flow|Association to the data and metadata flows that link to metadata about the provisioning and related data and metadata sets, and the structures that define them.
483 -| |+structure|Association to the Data Structure Definition and Metadata Structure Definitions which define the structural metadata describing the data and metadata that are contained at this part of the report.
470 +)))|(% style="width:668px" %)A scheme which defines the composition structure of a data report where each component can be described by an independent Dataflow or Metadataflow.
471 +| |/items|(% style="width:668px" %)Associates the Reporting Category
472 +|ReportingCategory|Inherits from //Item//|(% style="width:668px" %)A component that gives structure to the report and links to data and metadata.
473 +| |/hierarchy|(% style="width:668px" %)Associates child Reporting Category.
474 +| |+flow|(% style="width:668px" %)Association to the data and metadata flows that link to metadata about the provisioning and related data and metadata sets, and the structures that define them.
475 +| |+structure|(% style="width:668px" %)Association to the Data Structure Definition and Metadata Structure Definitions which define the structural metadata describing the data and metadata that are contained at this part of the report.
484 484  
485 -
486 -
487 487  ----
488 488  
489 -[[~[1~]>>path:#_ftnref1]] The Codelist that extends 0..* Codelists is the 'extending' Codelist, while the Codelist(s) that are inherited is/are the 'extended' Codelist(s).
479 +{{putFootnotes/}}
1749246291075-895.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -37.6 KB
Content
1749246291156-936.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -42.9 KB
Content
1749246291164-838.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -58.9 KB
Content
1749246291175-231.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -40.1 KB
Content
1749246291179-291.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -39.1 KB
Content
1749246291184-799.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -41.0 KB
Content
1749246291189-654.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -25.6 KB
Content
1749246291193-743.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -46.9 KB
Content
1749246291197-631.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -27.5 KB
Content
1749246291201-410.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -38.1 KB
Content
1749246291205-630.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -50.9 KB
Content
image42.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +72.0 KB
Content
image43.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +36.8 KB
Content
image44.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +103.3 KB
Content
image45.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +36.1 KB
Content
image46.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +54.8 KB
Content
image47.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +34.7 KB
Content
image48.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +34.9 KB
Content
image49.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +38.0 KB
Content
image50.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +33.5 KB
Content
image51.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +111.9 KB
Content
image52.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +54.8 KB
Content
SUZ.Methodology.Code.MethodologyClass[0]
index
... ... @@ -1,1 +1,0 @@
1 -5
SKMS.Methodology.Code.MethodologyClass[0]
Index
... ... @@ -1,0 +1,1 @@
1 +5
© Semantic R&D Group, 2026