Changes for page 4 Specific Item Schemes
Last modified by Artur on 2025/09/10 11:19
Summary
-
Page properties (3 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 6 removed)
-
Objects (0 modified, 0 added, 1 removed)
Details
- Page properties
-
- Parent
-
... ... @@ -1,1 +1,0 @@ 1 -Methodology.SDMX 2\.1 Standards\. Section 2\. Information model\: UML conceptual design.WebHome - Content
-
... ... @@ -20,8 +20,6 @@ 20 20 21 21 === {{id name="_Toc370990"/}}4.3.1 Class Diagram === 22 22 23 -[[image:1747732337979-971.png]] 24 - 25 25 **Figure 15 Class diagram of the Codelist** 26 26 27 27 === {{id name="_Toc370991"/}}4.3.2 Explanation of the Diagram === ... ... @@ -74,8 +74,6 @@ 74 74 75 75 === {{id name="_Toc370993"/}}4.4.1 Class Diagram - Inheritance === 76 76 77 -[[image:1747732287949-594.png]] 78 - 79 79 **Figure 16 Class diagram of the Concept Scheme** 80 80 81 81 === {{id name="_Toc370994"/}}4.4.2 Explanation of the Diagram === ... ... @@ -111,7 +111,6 @@ 111 111 112 112 === {{id name="_Toc370995"/}}4.4.3 Class Diagram - Relationship === 113 113 114 -[[image:1747732242162-856.png]] 115 115 116 116 **Figure 17: Relationship class diagram of the Concept Scheme** 117 117 ... ... @@ -119,10 +119,14 @@ 119 119 120 120 ==== 4.4.4.1 Narrative ==== 121 121 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 +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 123 123 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 aMetadataStructureDefinition, 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 +MetadataStructureDefinition. 125 125 121 +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 122 + 123 +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. 124 + 126 126 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. 127 127 128 128 The Representation is documented in more detail in the section on the SDMX Base. ... ... @@ -161,12 +161,8 @@ 161 161 162 162 === {{id name="_Toc370999"/}}4.5.2 Class diagram - Inheritance === 163 163 164 -(% class="wikigeneratedid" id="H" %) 165 -[[image:1747732448450-721.png]] 163 +====== Figure 18 Inheritance Class diagram of the Category Scheme ====== 166 166 167 -(% class="wikigeneratedid" id="HFigure18InheritanceClassdiagramoftheCategoryScheme" %) 168 -**Figure 18 Inheritance Class diagram of the Category Scheme** 169 - 170 170 === {{id name="_Toc371000"/}}4.5.3 Explanation of the Diagram === 171 171 172 172 ==== 4.5.3.1 Narrative ==== ... ... @@ -199,12 +199,12 @@ 199 199 200 200 === {{id name="_Toc371001"/}}4.5.4 Class diagram - Relationship === 201 201 202 -[[image:1747732486733-495.png]] 203 - 204 204 **Figure 19: Relationship Class diagram of the Category Scheme** 205 205 206 -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 +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 207 207 201 +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. 202 + 208 208 ==== 4.5.4.1 Definitions ==== 209 209 210 210 ((( ... ... @@ -256,70 +256,83 @@ 256 256 257 257 ==== 4.6.2.2 Definitions ==== 258 258 259 -(% style="width:845.294px" %) 260 -|(% style="width:181px" %)**Class**|(% style="width:217px" %)**Feature**|(% style="width:429px" %)**Description** 261 -|(% style="width:181px" %)//OrganisationScheme//|(% style="width:217px" %)((( 254 +|**Class**|**Feature**|**Description** 255 +|//OrganisationScheme//|((( 262 262 Abstract Class Inherits from 257 + 263 263 //ItemScheme// 259 + 264 264 Sub classes are: 261 + 265 265 AgencyScheme 263 + 266 266 DataProviderScheme 265 + 267 267 DataConsumerScheme 267 + 268 268 OrganisationUnitScheme 269 -)))| (% style="width:429px" %)A maintained collection of Organisations.270 -| (%style="width:181px" %)|(% style="width:217px" %)/items|(% style="width:429px" %)Association to the Organisations in the scheme.271 -| (% style="width:181px" %)//Organisation//|(% style="width:217px" %)(((269 +)))|A maintained collection of Organisations. 270 +| |/items|Association to the Organisations in the scheme. 271 +|//Organisation//|((( 272 272 Inherits from 273 + 273 273 //Item// 275 + 274 274 Sub classes are: 277 + 275 275 Agency 279 + 276 276 DataProvider 281 + 277 277 DataConsumer 283 + 278 278 OrganisationUnit 279 -)))| (% 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.280 -| (%style="width:181px" %)|(% style="width:217px" %)+contact|(% style="width:429px" %)Association to the Contact information.281 -| (%style="width:181px" %)|(% style="width:217px" %)/hierarchy|(% style="width:429px" %)Association to child Organisations.282 -| (% 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.283 -| (%style="width:181px" %)|(% style="width:217px" %)name|(% style="width:429px" %)The designation of the Contact person by a linguistic expression.284 -| (%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.285 -| (%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.286 -| (%style="width:181px" %)|(% style="width:217px" %)telephone|(% style="width:429px" %)The telephone number of the Contact.287 -| (%style="width:181px" %)|(% style="width:217px" %)fax|(% style="width:429px" %)The fax number of the Contact.288 -| (%style="width:181px" %)|(% style="width:217px" %)email|(% style="width:429px" %)The Internet e-mail address of the Contact.289 -| (%style="width:181px" %)|(% style="width:217px" %)X400|(% style="width:429px" %)The X400 address of the Contact.290 -| (%style="width:181px" %)|(% style="width:217px" %)uri|(% style="width:429px" %)The URL address of the Contact.291 -| (% style="width:181px" %)AgencyScheme|(%style="width:217px" %)|(% style="width:429px" %)A maintained collection of Maintenace Agencies.292 -| (%style="width:181px" %)|(% style="width:217px" %)/items|(% style="width:429px" %)Association to the Maintenance Agency in the scheme.293 -| (% style="width:181px" %)DataProviderScheme|(%style="width:217px" %)|(% style="width:429px" %)A maintained collection of Data Providers.294 -| (%style="width:181px" %)|(% style="width:217px" %)/items|(% style="width:429px" %)Association to the Data Providers in the scheme.295 -| (% style="width:181px" %)DataConsumerScheme|(%style="width:217px" %)|(% style="width:429px" %)A maintained collection of Data Consumers.296 -| (%style="width:181px" %)|(% style="width:217px" %)/items|(% style="width:429px" %)Association to the Data Consumers in the scheme.297 -| (% style="width:181px" %)OrganisationUnitScheme|(%style="width:217px" %)|(% style="width:429px" %)A maintained collection of Organisation Units.298 -| (%style="width:181px" %)|(% style="width:217px" %)/items|(% style="width:429px" %)Association to the Organisation Units in the scheme.299 -| (% style="width:181px" %)Agency|(% style="width:217px" %)(((285 +)))|An organisation is a unique framework of authority within which a person or persons act, or are designated to act, towards some purpose. 286 +| |+contact|Association to the Contact information. 287 +| |/hierarchy|Association to child Organisations. 288 +|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. 289 +| |name|The designation of the Contact person by a linguistic expression. 290 +| |organisationUnit|The designation of the organisational structure by a linguistic expression, within which Contact person works. 291 +| |responsibility|The function of the contact person with respect to the organisation role for which this person is the Contact. 292 +| |telephone|The telephone number of the Contact. 293 +| |fax|The fax number of the Contact. 294 +| |email|The Internet e-mail address of the Contact. 295 +| |X400|The X400 address of the Contact. 296 +| |uri|The URL address of the Contact. 297 +|AgencyScheme| |A maintained collection of Maintenace Agencies. 298 +| |/items|Association to the Maintenance Agency in the scheme. 299 +|DataProviderScheme| |A maintained collection of Data Providers. 300 +| |/items|Association to the Data Providers in the scheme. 301 +|DataConsumerScheme| |A maintained collection of Data Consumers. 302 +| |/items|Association to the Data Consumers in the scheme. 303 +|OrganisationUnitScheme| |A maintained collection of Organisation Units. 304 +| |/items|Association to the Organisation Units in the scheme. 305 +|Agency|((( 300 300 Inherits from 307 + 301 301 //Organisation// 302 -)))| (% 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.303 -| (% style="width:181px" %)DataProvider|(% style="width:217px" %)(((309 +)))|Responsible agency for maintaining artefacts such as statistical classifications, glossaries, structural metadata such as Data and Metadata Structure Definitions, Concepts and Code lists. 310 +|DataProvider|((( 304 304 Inherits from 312 + 305 305 //Organisation// 306 -)))| (% style="width:429px" %)An organisation that produces data or reference metadata.307 -| (% style="width:181px" %)DataConsumer|(% style="width:217px" %)(((314 +)))|An organisation that produces data or reference metadata. 315 +|DataConsumer|((( 308 308 Inherits from 317 + 309 309 //Organisation// 310 -)))| (% style="width:429px" %)An organisation using data as input for further processing.311 -| (% style="width:181px" %)OrganisationUnit|(% style="width:217px" %)(((319 +)))|An organisation using data as input for further processing. 320 +|OrganisationUnit|((( 312 312 Inherits from 313 -//Organisation// 314 -)))|(% style="width:429px" %)A designation in the organisational structure. 315 -|(% style="width:181px" %) |(% style="width:217px" %)/hierarchy|(% style="width:429px" %)Association to child Organisation Units 316 316 323 +//Organisation // 324 +)))|A designation in the organisational structure. 325 +| |/hierarchy|Association to child Organisation Units 326 + 317 317 == {{id name="_Toc371005"/}}4.7 Reporting Taxonomy == 318 318 319 319 === {{id name="_Toc371006"/}}4.7.1 Class Diagram === 320 320 321 -[[image:1747732548003-370.png]] 322 - 323 323 **Figure 21: Class diagram of the Reporting Taxonomy** 324 324 325 325 === {{id name="_Toc371007"/}}4.7.2 Explanation of the Diagram === ... ... @@ -332,9 +332,10 @@ 332 332 333 333 Section 1 334 334 335 -1. linked to DatafowDefinition_1 336 -1. linked to DatafowDefinition_2 343 +~1. linked to DatafowDefinition_1 337 337 345 +2 linked to DatafowDefinition_2 346 + 338 338 Section 2 339 339 340 340 1. linked toDatafowDefinition_3 ... ... @@ -346,19 +346,22 @@ 346 346 347 347 ==== 4.7.2.2 Definitions ==== 348 348 349 -(% style="width:1033.29px" %) 350 -|**Class**|**Feature**|(% style="width:687px" %)**Description** 358 +|**Class**|**Feature**|**Description** 351 351 |ReportingTaxonomy|((( 352 352 Inherits from 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 361 + 362 +//ItemScheme // 363 +)))|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. 364 +| |items|Associates the Reporting Category 356 356 |ReportingCategory|((( 357 357 Inherits from 367 + 358 358 //Item// 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. 369 +)))|A component that gives structure to the report and links to data and metadata. 370 +| |hierarchy|Associates child Reporting Category. 371 +| |+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. 372 +| |+structure|((( 373 +Association to the Data Structure Definition and Metadata Structure 374 + 375 +Definitions which define the structural metadata describing the data and metadata that are contained at this part of the report. 364 364 )))
- 1747732242162-856.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.helena - Size
-
... ... @@ -1,1 +1,0 @@ 1 -21.8 KB - Content
- 1747732287949-594.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.helena - Size
-
... ... @@ -1,1 +1,0 @@ 1 -42.4 KB - Content
- 1747732337979-971.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.helena - Size
-
... ... @@ -1,1 +1,0 @@ 1 -39.3 KB - Content
- 1747732448450-721.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.helena - Size
-
... ... @@ -1,1 +1,0 @@ 1 -34.0 KB - Content
- 1747732486733-495.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.helena - Size
-
... ... @@ -1,1 +1,0 @@ 1 -18.6 KB - Content
- 1747732548003-370.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.helena - Size
-
... ... @@ -1,1 +1,0 @@ 1 -48.9 KB - Content
- SUZ.Methodology.Code.MethodologyClass[0]
-
- index
-
... ... @@ -1,1 +1,0 @@ 1 -5