Skip to Content

Changes for page 4 Specific Item Schemes

Last modified by Artur on 2025/09/10 11:19
From version 3.4
edited by Helena
on 2025/05/20 12:03
Change comment: There is no comment for this version
To version 4.2
edited by Artur
on 2025/05/20 14:28
Change comment: Update document after refactoring.

Summary

Details

Page properties
Parent
... ... @@ -1,0 +1,1 @@
1 +Methodology.SDMX 2\.1 Standards\. Section 2\. Information model\: UML conceptual design.WebHome
Author
... ... @@ -1,1 +1,1 @@
1 -xwiki:XWiki.helena
1 +xwiki:XWiki.arturkryazhev
Content
... ... @@ -20,6 +20,8 @@
20 20  
21 21  === {{id name="_Toc370990"/}}4.3.1 Class Diagram ===
22 22  
23 +[[image:1747732337979-971.png]]
24 +
23 23  **Figure 15 Class diagram of the Codelist**
24 24  
25 25  === {{id name="_Toc370991"/}}4.3.2 Explanation of the Diagram ===
... ... @@ -55,16 +55,17 @@
55 55  ==== 4.3.2.2 Definitions ====
56 56  
57 57  (((
58 -|**Class**|**Feature**|**Description**
59 -|Codelist|(((
60 +(% style="width:905.294px" %)
61 +|(% style="width:132px" %)**Class**|(% style="width:172px" %)**Feature**|(% style="width:598px" %)**Description**
62 +|(% style="width:132px" %)Codelist|(% style="width:172px" %)(((
60 60  Inherits from
61 61  //ItemScheme//
62 -)))|A list from which some statistical concepts (coded concepts) take their values.
63 -|Code|(((
65 +)))|(% style="width:598px" %)A list from which some statistical concepts (coded concepts) take their values.
66 +|(% style="width:132px" %)Code|(% style="width:172px" %)(((
64 64  Inherits from
65 65  //Item//
66 -)))|A language independent set of letters, numbers or symbols that represent a concept whose meaning is described in a natural language.
67 -| |/hierarchy|Associates the parent and the child codes.
69 +)))|(% style="width:598px" %)A language independent set of letters, numbers or symbols that represent a concept whose meaning is described in a natural language.
70 +|(% style="width:132px" %) |(% style="width:172px" %)/hierarchy|(% style="width:598px" %)Associates the parent and the child codes.
68 68  )))
69 69  
70 70  == {{id name="_Toc370992"/}}4.4 Concept Scheme and Concepts ==
... ... @@ -71,6 +71,8 @@
71 71  
72 72  === {{id name="_Toc370993"/}}4.4.1 Class Diagram - Inheritance ===
73 73  
77 +[[image:1747732287949-594.png]]
78 +
74 74  **Figure 16 Class diagram of the Concept Scheme**
75 75  
76 76  === {{id name="_Toc370994"/}}4.4.2 Explanation of the Diagram ===
... ... @@ -106,6 +106,7 @@
106 106  
107 107  === {{id name="_Toc370995"/}}4.4.3 Class Diagram - Relationship ===
108 108  
114 +[[image:1747732242162-856.png]]
109 109  
110 110  **Figure 17: Relationship class diagram of the Concept Scheme**
111 111  
... ... @@ -113,14 +113,10 @@
113 113  
114 114  ==== 4.4.4.1 Narrative ====
115 115  
116 -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
122 +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.
117 117  
118 -MetadataStructureDefinition.
124 +The Concept can be associated with a coreRepresentation. The coreRepresentation isthe 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.
119 119  
120 -The Concept can be associated with a coreRepresentation. The coreRepresentation isthe specification of the format and value domain of the Concept when used on a structure like a DataStructureDefinition or a
121 -
122 -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.
123 -
124 124  Note that the ConceptScheme is used as the Representation of the MeasureDimension in a DataStructureDefinition (see 5.3.2). Each Concept in this ConceptScheme is a specific measure, each of which can be given a coreRepresentation. Thus the valid format of the observation for each measure when reported in a data set for the MeasureDimension is specified in the Concept. This allows a different format for each measure. This is covered in more detail in 5.3.
125 125  
126 126  The Representation is documented in more detail in the section on the SDMX Base.
... ... @@ -159,8 +159,11 @@
159 159  
160 160  === {{id name="_Toc370999"/}}4.5.2 Class diagram - Inheritance ===
161 161  
162 -====== Figure 18 Inheritance Class diagram of the Category Scheme ======
164 +====== [[image:1747732448450-721.png]] ======
163 163  
166 +(% class="wikigeneratedid" id="HFigure18InheritanceClassdiagramoftheCategoryScheme" %)
167 +**Figure 18 Inheritance Class diagram of the Category Scheme**
168 +
164 164  === {{id name="_Toc371000"/}}4.5.3 Explanation of the Diagram ===
165 165  
166 166  ==== 4.5.3.1 Narrative ====
... ... @@ -193,37 +193,33 @@
193 193  
194 194  === {{id name="_Toc371001"/}}4.5.4 Class diagram - Relationship ===
195 195  
201 +[[image:1747732486733-495.png]]
202 +
196 196  **Figure 19: Relationship Class diagram of the Category Scheme**
197 197  
198 -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
205 +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.
199 199  
200 -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.
201 -
202 202  ==== 4.5.4.1 Definitions ====
203 203  
204 -:
205 -
206 206  (((
207 -|**Class**|**Feature**|**Description**
208 -|CategoryScheme|(((
210 +(% style="width:965.294px" %)
211 +|(% style="width:171px" %)**Class**|(% style="width:213px" %)**Feature**|(% style="width:577px" %)**Description**
212 +|(% style="width:171px" %)CategoryScheme|(% style="width:213px" %)(((
209 209  Inherits from
210 -
211 211  //ItemScheme//
212 -)))|The descriptive information for an arrangement or division of categories into groups based on characteristics, which the objects have in common.
213 -| |/items|Associates the categories.
214 -|Category|(((
215 +)))|(% style="width:577px" %)The descriptive information for an arrangement or division of categories into groups based on characteristics, which the objects have in common.
216 +|(% style="width:171px" %) |(% style="width:213px" %)/items|(% style="width:577px" %)Associates the categories.
217 +|(% style="width:171px" %)Category|(% style="width:213px" %)(((
215 215  Inherits from
216 -
217 217  //Item//
218 -)))|An item at any level within a classification, typically tabulation categories, sections, subsections, divisions, subdivisions, groups, subgroups, classes and subclasses.
219 -| |/hierarchy|Associates the parent and the child Category.
220 -|Categorisation|(((
220 +)))|(% style="width:577px" %)An item at any level within a classification, typically tabulation categories, sections, subsections, divisions, subdivisions, groups, subgroups, classes and subclasses.
221 +|(% style="width:171px" %) |(% style="width:213px" %)/hierarchy|(% style="width:577px" %)Associates the parent and the child Category.
222 +|(% style="width:171px" %)Categorisation|(% style="width:213px" %)(((
221 221  Inherits from
222 -
223 223  MaintainableArtefact
224 -)))|Associates anIdentifableArtefact with a Category.
225 -| |+categorisedArtefact|Associates the IdentifableArtefact.
226 -| |+categorisedBy|Associates the Category.
225 +)))|(% style="width:577px" %)Associates anIdentifableArtefact with a Category.
226 +|(% style="width:171px" %) |(% style="width:213px" %)+categorisedArtefact|(% style="width:577px" %)Associates the IdentifableArtefact.
227 +|(% style="width:171px" %) |(% style="width:213px" %)+categorisedBy|(% style="width:577px" %)Associates the Category.
227 227  )))
228 228  
229 229  == {{id name="_Toc371002"/}}4.6 Organisation Scheme ==
... ... @@ -232,7 +232,8 @@
232 232  
233 233  [[image:SDMX_2-1_SECTION_2_InformationModel_2020-07_dcd0149.png||height="456" width="580"]]
234 234  
235 -====== Figure 20 The Organisation Scheme class diagram ======
236 +(% class="wikigeneratedid" id="HFigure20TheOrganisationSchemeclassdiagram" %)
237 +**Figure 20 The Organisation Scheme class diagram**
236 236  
237 237  === {{id name="_Toc371004"/}}4.6.2 Explanation of the Diagram ===
238 238  
... ... @@ -253,83 +253,70 @@
253 253  
254 254  ==== 4.6.2.2 Definitions ====
255 255  
256 -|**Class**|**Feature**|**Description**
257 -|//OrganisationScheme//|(((
258 +(% style="width:845.294px" %)
259 +|(% style="width:181px" %)**Class**|(% style="width:217px" %)**Feature**|(% style="width:429px" %)**Description**
260 +|(% style="width:181px" %)//OrganisationScheme//|(% style="width:217px" %)(((
258 258  Abstract Class Inherits from
259 -
260 260  //ItemScheme//
261 -
262 262  Sub classes are:
263 -
264 264  AgencyScheme
265 -
266 266  DataProviderScheme
267 -
268 268  DataConsumerScheme
269 -
270 270  OrganisationUnitScheme
271 -)))|A maintained collection of Organisations.
272 -| |/items|Association to the Organisations in the scheme.
273 -|//Organisation//|(((
268 +)))|(% style="width:429px" %)A maintained collection of Organisations.
269 +|(% style="width:181px" %) |(% style="width:217px" %)/items|(% style="width:429px" %)Association to the Organisations in the scheme.
270 +|(% style="width:181px" %)//Organisation//|(% style="width:217px" %)(((
274 274  Inherits from
275 -
276 276  //Item//
277 -
278 278  Sub classes are:
279 -
280 280  Agency
281 -
282 282  DataProvider
283 -
284 284  DataConsumer
285 -
286 286  OrganisationUnit
287 -)))|An organisation is a unique framework of authority within which a person or persons act, or are designated to act, towards some purpose.
288 -| |+contact|Association to the Contact information.
289 -| |/hierarchy|Association to child Organisations.
290 -|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.
291 -| |name|The designation of the Contact person by a linguistic expression.
292 -| |organisationUnit|The designation of the organisational structure by a linguistic expression, within which Contact person works.
293 -| |responsibility|The function of the contact person with respect to the organisation role for which this person is the Contact.
294 -| |telephone|The telephone number of the Contact.
295 -| |fax|The fax number of the Contact.
296 -| |email|The Internet e-mail address of the Contact.
297 -| |X400|The X400 address of the Contact.
298 -| |uri|The URL address of the Contact.
299 -|AgencyScheme| |A maintained collection of Maintenace Agencies.
300 -| |/items|Association to the Maintenance Agency in the scheme.
301 -|DataProviderScheme| |A maintained collection of Data Providers.
302 -| |/items|Association to the Data Providers in the scheme.
303 -|DataConsumerScheme| |A maintained collection of Data Consumers.
304 -| |/items|Association to the Data Consumers in the scheme.
305 -|OrganisationUnitScheme| |A maintained collection of Organisation Units.
306 -| |/items|Association to the Organisation Units in the scheme.
307 -|Agency|(((
278 +)))|(% style="width:429px" %)An organisation is a unique framework of authority within which a person or persons act, or are designated to act, towards some purpose.
279 +|(% style="width:181px" %) |(% style="width:217px" %)+contact|(% style="width:429px" %)Association to the Contact information.
280 +|(% style="width:181px" %) |(% style="width:217px" %)/hierarchy|(% style="width:429px" %)Association to child Organisations.
281 +|(% style="width:181px" %)Contact|(% style="width:217px" %) |(% style="width:429px" %)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.
282 +|(% style="width:181px" %) |(% style="width:217px" %)name|(% style="width:429px" %)The designation of the Contact person by a linguistic expression.
283 +|(% style="width:181px" %) |(% style="width:217px" %)organisationUnit|(% style="width:429px" %)The designation of the organisational structure by a linguistic expression, within which Contact person works.
284 +|(% style="width:181px" %) |(% style="width:217px" %)responsibility|(% style="width:429px" %)The function of the contact person with respect to the organisation role for which this person is the Contact.
285 +|(% style="width:181px" %) |(% style="width:217px" %)telephone|(% style="width:429px" %)The telephone number of the Contact.
286 +|(% style="width:181px" %) |(% style="width:217px" %)fax|(% style="width:429px" %)The fax number of the Contact.
287 +|(% style="width:181px" %) |(% style="width:217px" %)email|(% style="width:429px" %)The Internet e-mail address of the Contact.
288 +|(% style="width:181px" %) |(% style="width:217px" %)X400|(% style="width:429px" %)The X400 address of the Contact.
289 +|(% style="width:181px" %) |(% style="width:217px" %)uri|(% style="width:429px" %)The URL address of the Contact.
290 +|(% style="width:181px" %)AgencyScheme|(% style="width:217px" %) |(% style="width:429px" %)A maintained collection of Maintenace Agencies.
291 +|(% style="width:181px" %) |(% style="width:217px" %)/items|(% style="width:429px" %)Association to the Maintenance Agency in the scheme.
292 +|(% style="width:181px" %)DataProviderScheme|(% style="width:217px" %) |(% style="width:429px" %)A maintained collection of Data Providers.
293 +|(% style="width:181px" %) |(% style="width:217px" %)/items|(% style="width:429px" %)Association to the Data Providers in the scheme.
294 +|(% style="width:181px" %)DataConsumerScheme|(% style="width:217px" %) |(% style="width:429px" %)A maintained collection of Data Consumers.
295 +|(% style="width:181px" %) |(% style="width:217px" %)/items|(% style="width:429px" %)Association to the Data Consumers in the scheme.
296 +|(% style="width:181px" %)OrganisationUnitScheme|(% style="width:217px" %) |(% style="width:429px" %)A maintained collection of Organisation Units.
297 +|(% style="width:181px" %) |(% style="width:217px" %)/items|(% style="width:429px" %)Association to the Organisation Units in the scheme.
298 +|(% style="width:181px" %)Agency|(% style="width:217px" %)(((
308 308  Inherits from
309 -
310 310  //Organisation//
311 -)))|Responsible agency for maintaining artefacts such as statistical classifications, glossaries, structural metadata such as Data and Metadata Structure Definitions, Concepts and Code lists.
312 -|DataProvider|(((
301 +)))|(% style="width:429px" %)Responsible agency for maintaining artefacts such as statistical classifications, glossaries, structural metadata such as Data and Metadata Structure Definitions, Concepts and Code lists.
302 +|(% style="width:181px" %)DataProvider|(% style="width:217px" %)(((
313 313  Inherits from
314 -
315 315  //Organisation//
316 -)))|An organisation that produces data or reference metadata.
317 -|DataConsumer|(((
305 +)))|(% style="width:429px" %)An organisation that produces data or reference metadata.
306 +|(% style="width:181px" %)DataConsumer|(% style="width:217px" %)(((
318 318  Inherits from
319 -
320 320  //Organisation//
321 -)))|An organisation using data as input for further processing.
322 -|OrganisationUnit|(((
309 +)))|(% style="width:429px" %)An organisation using data as input for further processing.
310 +|(% style="width:181px" %)OrganisationUnit|(% style="width:217px" %)(((
323 323  Inherits from
312 +//Organisation//
313 +)))|(% style="width:429px" %)A designation in the organisational structure.
314 +|(% style="width:181px" %) |(% style="width:217px" %)/hierarchy|(% style="width:429px" %)Association to child Organisation Units
324 324  
325 -//Organisation //
326 -)))|A designation in the organisational structure.
327 -| |/hierarchy|Association to child Organisation Units
328 -
329 329  == {{id name="_Toc371005"/}}4.7 Reporting Taxonomy ==
330 330  
331 331  === {{id name="_Toc371006"/}}4.7.1 Class Diagram ===
332 332  
320 +[[image:1747732548003-370.png]]
321 +
333 333  **Figure 21: Class diagram of the Reporting Taxonomy**
334 334  
335 335  === {{id name="_Toc371007"/}}4.7.2 Explanation of the Diagram ===
... ... @@ -357,22 +357,19 @@
357 357  
358 358  ==== 4.7.2.2 Definitions ====
359 359  
360 -|**Class**|**Feature**|**Description**
349 +(% style="width:1033.29px" %)
350 +|**Class**|**Feature**|(% style="width:687px" %)**Description**
361 361  |ReportingTaxonomy|(((
362 362  Inherits from
363 -
364 -//ItemScheme //
365 -)))|A scheme which defines the composition structure of a data report where each component can be described by an independent Dataflow Definition or Metdataflow Definition.
366 -| |items|Associates the Reporting Category
353 +//ItemScheme//
354 +)))|(% style="width:687px" %)A scheme which defines the composition structure of a data report where each component can be described by an independent Dataflow Definition or Metdataflow Definition.
355 +| |items|(% style="width:687px" %)Associates the Reporting Category
367 367  |ReportingCategory|(((
368 368  Inherits from
369 -
370 370  //Item//
371 -)))|A component that gives structure to the report and links to data and metadata.
372 -| |hierarchy|Associates child Reporting Category.
373 -| |+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.
374 -| |+structure|(((
375 -Association to the Data Structure Definition and Metadata Structure
376 -
377 -Definitions which define the structural metadata describing the data and metadata that are contained at this part of the report.
359 +)))|(% style="width:687px" %)A component that gives structure to the report and links to data and metadata.
360 +| |hierarchy|(% style="width:687px" %)Associates child Reporting Category.
361 +| |+flow|(% style="width:687px" %)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.
362 +| |+structure|(% style="width:687px" %)(((
363 +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.
378 378  )))
1747732242162-856.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +21.8 KB
Content
1747732287949-594.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +42.4 KB
Content
1747732337979-971.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +39.3 KB
Content
1747732448450-721.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +34.0 KB
Content
1747732486733-495.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +18.6 KB
Content
1747732548003-370.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +48.9 KB
Content