Skip to Content

Wiki source code of 4 Specific Item Schemes

Version 16.1 by Helena on 2025/05/16 13:48
Show last authors
1 {{box title="**Contents**"}}
2 {{toc/}}
3 {{/box}}
4
5 == 4.1 Introduction ==
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:
8
9 Codelist
10 ConceptScheme
11 CategoryScheme
12 AgencyScheme, DataProviderScheme, MetadataProviderScheme, DataConsumerScheme, OrganisationUnitScheme, which all inherit from the abstract class //OrganisationScheme//
13 ReportingTaxonomy
14 TransformationScheme
15 RulesetScheme
16 UserDefinedOperatorScheme
17 NamePersonalisationScheme
18 CustomTypeScheme
19 VtlMappingScheme
20
21 Note that the VTL related schemes (the last 6 of the above list) are detailed in a dedicated section below (section 15).
22
23 == 4.2 Inheritance View ==
24
25 The inheritance and relationship views are shown together in each of the diagrams in the specific sections below.
26
27 == 4.3 Codelist ==
28
29 === 4.3.1 Class Diagram ===
30
31 [[image:SDMX 3-0-0 SECTION 2 FINAL-1.0 (1)_en_98388f74.jpg||height="674" width="433"]]
32
33 **Figure 16: Class diagram of the Codelist**
34
35 === 4.3.2 Explanation of the Diagram ===
36
37 ==== 4.3.2.1 Narrative ====
38
39 The Codelist inherits from the //ItemScheme// and therefore has the following attributes:
40
41 id
42 uri
43 urn
44 version
45 validFrom
46 validTo
47 isExternalReference
48 serviceURL
49 structureURL
50 isPartial
51
52 The Code inherits from //Item// and has the following attributes:
53
54 id
55 uri
56 urn
57
58 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).
59
60 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.
61
62 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
63
64 //ItemScheme//.
65
66 ==== 4.3.2.2 Definitions ====
67
68 (% style="width:743.039px" %)
69 |**Class**|**Feature**|(% style="width:465px" %)**Description**
70 |Codelist|(((
71 Inherits from
72
73 //ItemScheme//
74 )))|(% style="width:465px" %)A list from which some statistical concepts (coded concepts) take their values.
75 |Code|(((
76 Inherits from
77
78 Item
79 )))|(% style="width:465px" %)A language independent set of letters, numbers or symbols that represent a concept whose meaning is described in a natural language.
80 | |hierarchy|(% style="width:465px" %)Associates the parent and the child codes.
81 | |extends|(% style="width:465px" %)Associates a Codelist with any Codelists that it may extend.
82
83 === 4.3.3 Class Diagram – Codelist Extension ===
84
85 [[image:SDMX 3-0-0 SECTION 2 FINAL-1.0 (1)_en_e758cbcf.jpg||height="546" width="559"]]
86
87 **Figure 17: Class diagram for Codelist Extension**
88
89 ==== 4.3.3.1 Narrative ====
90
91 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.
92
93 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 ,,Code,,s (via the ,,cascadeValues,, property), or even include instances of the wildcard character ‘%’ in order to point to a set of ,,Code,,s with common parts in their identifiers.
94
95 ==== 4.3.3.2 Definitions ====
96
97 (((
98 (% style="width:753.039px" %)
99 |(% style="width:184px" %)**Class**|(% style="width:145px" %)**Feature**|(% style="width:421px" %)**Description**
100 |(% style="width:184px" %)CodelistExtension|(% style="width:145px" %) |(% style="width:421px" %)The association between Codelists that may extend other Codelists.
101 |(% style="width:184px" %) |(% style="width:145px" %)prefix|(% style="width:421px" %)A prefix to be used for a Codelist used in a extension, in order to avoid Code Conflicts.
102 |(% style="width:184px" %) |(% style="width:145px" %)sequence|(% style="width:421px" %)The order that will be used when extending a Codelist, for resolving Code conflicts. The latest Codelist used overrides any previous Codelist.
103 |(% style="width:184px" %)InclusiveCodeSelection|(% style="width:145px" %) |(% style="width:421px" %)The subset of Codes to be included when extending a Codelist.
104 |(% style="width:184px" %)ExclusiveCodeSelection|(% style="width:145px" %) |(% style="width:421px" %)The subset of Codes to be excluded when extending a Codelist.
105 |(% style="width:184px" %)MemberValue|(% style="width:145px" %)(((
106 Inherits from:
107
108 //SelectionValue//
109 )))|(% style="width:421px" %)A collection of values based on Codes and their children.
110 |(% style="width:184px" %) |(% style="width:145px" %)cascadeValues|(% style="width:421px" %)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.
111 |(% style="width:184px" %) |(% style="width:145px" %)value|(% style="width:421px" %)The value of the Code to include in the selection. It may include the ‘%’ character as a wildcard.
112 )))
113
114 === 4.3.4 Class Diagram – Geospatial Codelist ===
115
116 The geospatial support is implemented via an extension of the normal //Codelist//. This is illustrated in the following diagrams.
117
118 [[image:SDMX 3-0-0 SECTION 2 FINAL-1.0 (1)_en_472b895.jpg||height="863" width="466"]]
119
120 **Figure 18: Inheritance for the GeoCodelist**
121
122 [[image:SDMX 3-0-0 SECTION 2 FINAL-1.0 (1)_en_410255be.jpg||height="405" width="559"]]
123
124 **Figure 19: Class diagram for Geospatial Codelist**
125
126 ==== 4.3.4.1 Narrative ====
127
128 A //GeoCodelist// is a specialisation of Codelist that includes geospatial information, by comprising a set of special Codes, i.e., //GeoRefCode//s. A //GeoCodelist// may be implemented by any of the two following classes, via the geoType property:
129
130 GeographicCodelist
131 GeoGridCodelist
132
133 The former, i.e., GeographicCodelist, comprises a set of GeoFeatureSetCodes, by adding a value in the Code that follows a pattern to represent a geo feature set.
134
135 The latter, i.e., GeoGridCodelist, comprises a set of GridCodes, which are related to the gridDefinition specified in the GeoGridCodelist.
136
137 ==== 4.3.4.2 Definitions ====
138
139 (% style="width:760.039px" %)
140 |(% colspan="2" %)**Class**|(% colspan="4" %)**Feature**|**Description**
141 |(% colspan="2" %)//GeoCodelist//|(% colspan="4" %)(((
142 Abstract Class Sub Classes:
143
144 GeographicCodelist GeoGridCodelist geoType
145 )))|(((
146 The abstract class that represents a special type of Codelist, which includes geospatial information.
147
148 The type of Geo Codelist that the Codelist will become.
149 )))
150 |(% colspan="2" %)//GeoRefCode//|(% colspan="4" %)(((
151 Abstract Class Sub Classes:
152 GeoFeatureSet
153 GeoGridCode
154 )))|The abstract class that represents a special type of Code, which includes geospatial information.
155 |(% colspan="2" %)GeographicCodelist|(% colspan="4" %) |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 |(% colspan="2" %)GeoGridCodelist|(% colspan="4" %) |A code list that has defined a geographical grid composed of cells representing regular squared portions of the Earth.
157 |(% colspan="2" %) |(% colspan="4" %)gridDefinition|Contains a regular expression string corresponding to the grid definition for the GeoGrid Codelist.
158 |(% colspan="2" %)GeoFeatureSetCode|(% colspan="4" %) |A Code that has a geo feature set.
159 |(% colspan="2" %) |(% colspan="4" %)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 |(% colspan="2" %)GeoGridCode|(% colspan="4" %) |A Code that represents a Geo Grid Cell belonging in a specific grid definition.
161 |(% colspan="2" %) |(% colspan="4" %)geoCell|The value used to assign the Code to one cell in the grid.
162
163 == 4.4 ValueList ==
164
165 === 4.4.1 Class Diagram ===
166
167 [[image:SDMX 3-0-0 SECTION 2 FINAL-1.0 (1)_en_4d9e301b.jpg||height="695" width="526"]]
168
169 **Figure 20: Class diagram of the ValueList**
170
171 === 4.4.2 Explanation of the Diagram ===
172
173 ==== 4.4.2.1 Narrative ====
174
175 A ValueList inherits from //EnumeratedList// (and hence the //MaintenableArtefact//) and thus has the following attributes:
176
177 id
178 uri
179 urn
180 version
181 validFrom
182 validTo
183 isExternalReference
184 registryURL
185 structureURL
186 repositoryURL
187
188 ValueItem inherits from //EnumeratedItem//, which adds an id, with relaxed constraints, to the former.
189
190 Through the inheritance from //NameableArtefact// the ValueList has 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). Similarly, the ValueItem, inherits the association to InternationalString and to the Annotation from the //EnumeratedItem//.
191
192 The ValueList can have one or more ValueItems.
193
194 ==== 4.4.2.2 Definitions ====
195
196 (% style="width:749.039px" %)
197 |**Class**|**Feature**|(% style="width:421px" %)**Description**
198 |ValueList|(((
199 Inherits from
200
201 //EnumeratedList//
202 )))|(% style="width:421px" %)A list from which some statistical concepts (enumerated concepts) take their values.
203 |ValueItem|(((
204 Inherits from
205
206 //EnumeratedItem//
207 )))|(% style="width:421px" %)A language independent set of letters, numbers or symbols that represent a concept whose meaning is described in a natural language.
208
209 == 4.5 Concept Scheme and Concepts ==
210
211 === 4.5.1 Class Diagram - Inheritance ===
212
213 [[image:SDMX 3-0-0 SECTION 2 FINAL-1.0 (1)_en_e6942837.jpg||height="717" width="457"]]
214
215 **Figure 21 Class diagram of the Concept Scheme**
216
217 === 4.5.2 Explanation of the Diagram ===
218
219 The ConceptScheme inherits from the //ItemScheme //and therefore has the following attributes:
220
221 id
222 uri
223 urn
224 version
225 validFrom
226 validTo
227 isExternalReference
228 registryURL
229 structureURL
230 repositoryURL
231 isPartial
232
233 Concept inherits from Item and has the following attributes:
234
235 id
236 uri
237 urn
238
239 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).
240
241 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.
242
243 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.
244
245 === 4.5.3 Class Diagram Relationship ===
246
247 [[image:SDMX 3-0-0 SECTION 2 FINAL-1.0 (1)_en_d9b0bdf4.jpg||height="450" width="461"]]
248
249 **Figure 22: Relationship class diagram of the Concept Scheme**
250
251 === 4.5.4 Explanation of the diagram ===
252
253 ==== 4.5.4.1 Narrative ====
254
255 The ConceptScheme can have one or more Concepts. A Concept can have zero or more child Concepts, thus supporting a hierarchy of Concepts. Note that a child Concept can have only one parent Concept in this association. The purpose of the hierarchy is to relate concepts that have a semantic relationship: for example, a Reporting_Country and Vis_a_Vis_Country may both have Country as a parent concept, or a CONTACT may have a PRIMARY_CONTACT as a child concept. It is not the purpose of such schemes to define reporting structures: these reporting structures are defined in the MetadataStructureDefinition.
256
257 The Concept can be associated with a coreRepresentation. The coreRepresentation is the specification of the format and value domain of the Concept when used on a structure like a DataStructureDefinition or a MetadataStructureDefinition, unless the specification of the Representation is overridden in the relevant structure definition. In a hierarchical ConceptScheme the Representation is inherited from the parent Concept unless overridden at the level of the child Concept.
258
259 The Representation is documented in more detail in the section on the SDMX Base.
260
261 The Concept may be related to a concept described in terms of the ISO/IEC 11179 standard. The ISOConceptReference identifies this concept and concept scheme in which it is contained.
262
263 ==== 4.5.4.2 Definitions ====
264
265 (% style="width:765.039px" %)
266 |(% style="width:204px" %)**Class**|(% style="width:222px" %)**Feature**|(% style="width:337px" %)**Description**
267 |(% style="width:204px" %)ConceptScheme|(% style="width:222px" %)(((
268 Inherits from
269 //ItemScheme//
270 )))|(% style="width:337px" %)The descriptive information for an arrangement or division of concepts into groups based on characteristics, which the objects have in common.
271 |(% style="width:204px" %)Concept|(% style="width:222px" %)(((
272 Inherits from
273 //Item//
274 )))|(% style="width:337px" %)A concept is a unit of knowledge created by a unique combination of characteristics.
275 |(% style="width:204px" %) |(% style="width:222px" %)/hierarchy|(% style="width:337px" %)Associates the parent and the child concept.
276 |(% style="width:204px" %) |(% style="width:222px" %)coreRepresentation|(% style="width:337px" %)Associates a Representation.
277 |(% style="width:204px" %) |(% style="width:222px" %)+ISOConcept|(% style="width:337px" %)Association to an ISO concept reference.
278 |(% style="width:204px" %)ISOConceptReference|(% style="width:222px" %) |(% style="width:337px" %)The identity of an ISO concept definition.
279 |(% style="width:204px" %) |(% style="width:222px" %)conceptAgency|(% style="width:337px" %)The maintenance agency of the concept scheme containing the concept.
280 |(% style="width:204px" %) |(% style="width:222px" %)conceptSchemeID|(% style="width:337px" %)The identifier of the concept scheme.
281 |(% style="width:204px" %) |(% style="width:222px" %)conceptID|(% style="width:337px" %)The identifier of the concept.
282
283 == 4.6 Category Scheme ==
284
285 === 4.6.1 Context ===
286
287 This package defines the structure that supports the definition of and relationships between categories in a category scheme. It is similar to the package for concept scheme. An example of a category scheme is one which categorises data – sometimes known as a subject matter domain scheme or a data category scheme. Importantly, as will be seen later, the individual nodes in the scheme (the “categories”) can be associated to any set of IdentiableArtefacts in a Categorisation.
288
289 === 4.6.2 Class diagram Inheritance ===
290
291 [[image:SDMX 3-0-0 SECTION 2 FINAL-1.0 (1)_en_3a450acd.jpg||height="776" width="452"]]
292
293 **Figure 23 Inheritance Class diagram of the Category Scheme**
294
295 === 4.6.3 Explanation of the Diagram ===
296
297 ==== 4.6.3.1 Narrative ====
298
299 The categories are modelled as a hierarchical //ItemScheme//. The CategoryScheme inherits from the //ItemScheme// and has the following attributes:
300
301 id
302 uri
303 urn
304 version
305 validFrom
306 validTo
307 isExternalReference
308 structureURL
309 serviceURL
310 isPartial
311
312 Category inherits from //Item// and has the following attributes:
313
314 id
315 uri
316 urn
317
318 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).
319
320 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.
321
322 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.
323
324 === 4.6.4 Class diagram Relationship ===
325
326 [[image:SDMX 3-0-0 SECTION 2 FINAL-1.0 (1)_en_3696e610.jpg||height="407" width="525"]]
327
328 **Figure 24: Relationship Class diagram of the Category Scheme**
329
330 The CategoryScheme can have one or more Categorys. The Category is Identifiable and has identity information. A Category can have zero or more child Categorys, thus supporting a hierarchy of Categorys. Any IdentifiableArtefact can be +categorisedBy a Category. This is achieved by means of a Categorisation. Each Categorisation can associate one IdentifiableArtefact with one Category. Multiple Categorisations can be used to build a set of IdentifiableArtefacts that are +categorisedBy the same Category. Note that there is no navigation (i.e. no embedded reference) to the Categorisation from the Category. From an implementation perspective this is necessary as Categorisation has no affect on the versioning of either the Category or the IdentifiableArtefact.
331
332 ==== 4.6.4.1 Definitions ====
333
334 (% style="width:753.039px" %)
335 |**Class**|(% colspan="2" %)**Feature**|**Description**
336 |CategoryScheme|(% colspan="2" %)(((
337 Inherits from
338 //ItemScheme//
339 )))|The descriptive information for an arrangement or division of categories into groups based on characteristics, which the objects have in common.
340 | |(% colspan="2" %)/items|Associates the categories.
341 |Category|(((
342 Inherits from
343 //Item//
344 )))|(% colspan="2" %)An item at any level within a classification, typically tabulation categories, sections, subsections, divisions, subdivisions, groups, subgroups, classes and subclasses.
345 | |/hierarchy|(% colspan="2" %)Associates the parent and the child Category.
346 |Categorisation|(((
347 Inherits from
348 //MaintainableArtefact//
349 )))|(% colspan="2" %)Associates an Identifable Artefact with a Category.
350 | |+categorisedArtefact|(% colspan="2" %)Associates the Identifable Artefact.
351 | |+categorisedBy|(% colspan="2" %)Associates the Category.
352
353 == 4.7 Organisation Scheme ==
354
355 === 4.7.1 Class Diagram ===
356
357 [[image:SDMX 3-0-0 SECTION 2 FINAL-1.0 (1)_en_e9f53aa7.jpg||height="470" width="588"]]
358
359 **Figure 25 The Organisation Scheme class diagram**
360
361 === 4.7.2 Explanation of the Diagram ===
362
363 ==== 4.7.2.1 Narrative ====
364
365 The //OrganisationScheme// is abstract. It contains //Organisation// which is also abstract. The //Organisation// can have child //Organisation//.
366
367 The //OrganisationScheme// can be one of five types:
368
369 1. AgencyScheme – contains Agency which is restricted to a flat list of agencies (i.e., there is no hierarchy). Note that the SDMX system of (Maintenance) Agency can be hierarchic and this is explained in more detail in the SDMX Standards Section 6 “Technical Notes”.
370 1. DataProviderScheme – contains DataProvider which is restricted to a flat list of agencies (i.e., there is no hierarchy).
371 1. MetadataProviderScheme – contains MetadataProvider which is restricted to a flat list of agencies (i.e., there is no hierarchy).
372 1. DataConsumerScheme – contains DataConsumer which is restricted to a flat list of agencies (i.e., there is no hierarchy).
373 1. OrganisationUnitScheme – contains OrganisationUnit which does inherit the /hierarchy association from Organisation.
374
375 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.
376
377 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//.
378
379 ==== 4.7.2.2 Definitions ====
380
381 (% style="width:763.039px" %)
382 |**Class**|(% style="width:246px" %)**Feature**|(% style="width:336px" %)**Description**
383 |//OrganisationScheme//|(% style="width:246px" %)(((
384 Abstract Class Inherits from
385 //ItemScheme//
386
387 Sub classes are:
388 AgencyScheme
389 DataProviderScheme
390 MetadataProviderScheme DataConsumerScheme
391 OrganisationUnitScheme
392 )))|(% style="width:336px" %)A maintained collection of Organisations.
393 | |(% style="width:246px" %)/items|(% style="width:336px" %)(((
394 Association to the
395
396 Organisations in the scheme.
397 )))
398 |//Organisation//|(% style="width:246px" %)(((
399 Abstract Class
400 Inherits from //Item//
401
402 Sub classes are:
403 Agency
404 DataProvider
405 MetadataProvider DataConsumer
406 OrganisationUnit
407 )))|(% style="width:336px" %)An organisation is a unique framework of authority within which a person or persons act, or are designated to act, towards some purpose.
408 | |(% style="width:246px" %)+contact|(% style="width:336px" %)Association to the Contact information.
409 | |(% style="width:246px" %)/hierarchy|(% style="width:336px" %)Association to child Organisations.
410 |Contact|(% style="width:246px" %) |(% style="width:336px" %)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.
411 | |(% style="width:246px" %)name|(% style="width:336px" %)The designation of the Contact person by a linguistic expression.
412 | |(% style="width:246px" %)organisationUnit|(% style="width:336px" %)The designation of the organisational structure by a linguistic expression, within which Contact person works.
413 | |(% style="width:246px" %)responsibility|(% style="width:336px" %)The function of the contact person with respect to the organisation role for which this person is the Contact.
414 | |(% style="width:246px" %)telephone|(% style="width:336px" %)The telephone number of the Contact.
415 | |(% style="width:246px" %)fax|(% style="width:336px" %)The fax number of the Contact.
416 | |(% style="width:246px" %)email|(% style="width:336px" %)The Internet e-mail address of the Contact.
417 | |(% style="width:246px" %)X400|(% style="width:336px" %)The X400 address of the Contact.
418 | |(% style="width:246px" %)uri|(% style="width:336px" %)The URL address of the Contact.
419 |AgencyScheme|(% style="width:246px" %) |(% style="width:336px" %)A maintained collection of Maintenance Agencies.
420 | |(% style="width:246px" %)/items|(% style="width:336px" %)Association to the Maintenance Agency in the scheme.
421 |DataProviderScheme|(% style="width:246px" %) |(% style="width:336px" %)A maintained collection of Data Providers.
422 | |(% style="width:246px" %)/items|(% style="width:336px" %)Association to the Data Providers in the scheme.
423 |MetadataProviderScheme|(% style="width:246px" %) |(% style="width:336px" %)A maintained collection of Metadata Providers.
424 | |(% style="width:246px" %)/items|(% style="width:336px" %)Association to the Metadata Providers in the scheme.
425 |DataConsumerScheme|(% style="width:246px" %) |(% style="width:336px" %)A maintained collection of Data Consumers.
426 | |(% style="width:246px" %)/items|(% style="width:336px" %)Association to the Data Consumers in the scheme.
427 |OrganisationUnitScheme|(% style="width:246px" %) |(% style="width:336px" %)A maintained collection of Organisation Units.
428 | |(% style="width:246px" %)/items|(% style="width:336px" %)Association to the Organisation Units in the scheme.
429 |Agency|(% style="width:246px" %)(((
430 Inherits from
431 //Organisation//
432 )))|(% style="width:336px" %)Responsible agency for maintaining artefacts such as statistical classifications, glossaries, structural metadata such as Data and Metadata Structure Definitions, Concepts and Code lists.
433 |DataProvider|(% style="width:246px" %)(((
434 Inherits from
435 //Organisation//
436 )))|(% style="width:336px" %)An organisation that produces data.
437 |MetadataProvider|(% style="width:246px" %)(((
438 Inherits from
439 //Organisation//
440 )))|(% style="width:336px" %)An organisation that produces reference metadata.
441 |DataConsumer|(% style="width:246px" %)(((
442 Inherits from
443 //Organisation//
444 )))|(% style="width:336px" %)An organisation using data as input for further processing.
445 |OrganisationUnit|(% style="width:246px" %)(((
446 Inherits from
447 //Organisation//
448 )))|(% style="width:336px" %)A designation in the organisational structure.
449 | |(% style="width:246px" %)/hierarchy|(% style="width:336px" %)Association to child Organisation Units
450
451 == 4.8 Reporting Taxonomy ==
452
453 === 4.8.1 Class Diagram ===
454
455 [[image:SDMX 3-0-0 SECTION 2 FINAL-1.0 (1)_en_b041cf76.jpg||height="763" width="533"]]
456
457 **Figure 26: Class diagram of the Reporting Taxonomy**
458
459 === 4.8.2 Explanation of the Diagram ===
460
461 ==== 4.8.2.1 Narrative ====
462
463 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.
464
465 The ReportingTaxonomy is a specialised form of //ItemScheme//. Each ReportingCategory of the ReportingTaxonomy can link to one or more //StructureUsage// which itself can be one of Dataflow, or Metadataflow, and one or more //Structure//, which itself can be one of DataStructureDefinition or MetadataStructureDefinition. It is expected that within a specific ReportingTaxonomy each Category that is linked in this way will be linked to the same class (e.g. all Category in the scheme will link to a Dataflow). Note that a ReportingCategory can have child ReportingCategory and in this way it is possible to define a hierarchical ReportingTaxonomy. It is possible in this taxonomy that some ReportingCategory are defined just to give a reporting structure. For instance:
466
467 Section 1
468
469 1. linked to Datafow_1
470 1. linked to Datafow_2
471
472 Section 2
473
474 1. linked to Datafow_3
475 1. linked to Datafow_4
476
477 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).
478
479 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//.
480
481 ==== 4.8.2.2 Definitions ====
482
483 (% style="width:759.039px" %)
484 |(% style="width:177px" %)**Class**|(% style="width:152px" %)**Feature**|(% style="width:428px" %)**Description**
485 |(% style="width:177px" %)ReportingTaxonomy|(% style="width:152px" %)(((
486 Inherits from
487 //ItemScheme//
488 )))|(% style="width:428px" %)A scheme which defines the composition structure of a data report where each component can be described by an independent Dataflow or Metadataflow.
489 |(% style="width:177px" %) |(% style="width:152px" %)/items|(% style="width:428px" %)Associates the Reporting Category
490 |(% style="width:177px" %)ReportingCategory|(% style="width:152px" %)(((
491 Inherits from
492 //Item//
493 )))|(% style="width:428px" %)A component that gives structure to the report and links to data and metadata.
494 |(% style="width:177px" %) |(% style="width:152px" %)/hierarchy|(% style="width:428px" %)Associates child Reporting Category.
495 |(% style="width:177px" %) |(% style="width:152px" %)+flow|(% style="width:428px" %)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.
496 |(% style="width:177px" %) |(% style="width:152px" %)+structure|(% style="width:428px" %)(((
497 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.
498 )))
499
500 {{putFootnotes/}}