Changes for page 4 Specific Item Schemes
Last modified by Artur on 2025/09/10 11:19
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 3 added, 0 removed)
Details
- Page properties
-
- 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,8 @@ 106 106 107 107 === {{id name="_Toc370995"/}}4.4.3 Class Diagram - Relationship === 108 108 114 +[[image:1747732242162-856.png]] 115 + 109 109 **Figure 17: Relationship class diagram of the Concept Scheme** 110 110 111 111 === {{id name="_Toc370996"/}}4.4.4 Explanation of the diagram === ... ... @@ -112,14 +112,10 @@ 112 112 113 113 ==== 4.4.4.1 Narrative ==== 114 114 115 -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. 116 116 117 -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. 118 118 119 -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 120 - 121 -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. 122 - 123 123 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. 124 124 125 125 The Representation is documented in more detail in the section on the SDMX Base. ... ... @@ -128,27 +128,26 @@ 128 128 129 129 ==== 4.4.4.2 Definitions ==== 130 130 131 -: 132 - 133 133 ((( 134 -|**Class**|**Feature**|**Description** 135 -|ConceptScheme|((( 135 +(% style="width:931.294px" %) 136 +|(% style="width:195px" %)**Class**|(% style="width:210px" %)**Feature**|(% style="width:522px" %)**Description** 137 +|(% style="width:195px" %)ConceptScheme|(% style="width:210px" %)((( 136 136 Inherits from 137 137 138 138 //ItemScheme// 139 -)))|The descriptive information for an arrangement or division of concepts into groups based on characteristics, which the objects have in common. 140 -|Concept|((( 141 +)))|(% style="width:522px" %)The descriptive information for an arrangement or division of concepts into groups based on characteristics, which the objects have in common. 142 +|(% style="width:195px" %)Concept|(% style="width:210px" %)((( 141 141 Inherits from 142 142 143 143 //Item// 144 -)))|A concept is a unit of knowledge created by a unique combination of characteristics. 145 -| |/hierarchy|Associates the parent and the child concept. 146 -| |coreRepresentation|Associates a Representation. 147 -| |+ISOConcept|Association to an ISO concept reference. 148 -|ISOConceptReference| |The identity of an ISO concept definition. 149 -| |conceptAgency|The maintenance agency of the concept scheme containing the concept. 150 -| |conceptSchemeID|The identifier of the concept scheme. 151 -| |conceptID|The identifier of the concept. 146 +)))|(% style="width:522px" %)A concept is a unit of knowledge created by a unique combination of characteristics. 147 +|(% style="width:195px" %) |(% style="width:210px" %)/hierarchy|(% style="width:522px" %)Associates the parent and the child concept. 148 +|(% style="width:195px" %) |(% style="width:210px" %)coreRepresentation|(% style="width:522px" %)Associates a Representation. 149 +|(% style="width:195px" %) |(% style="width:210px" %)+ISOConcept|(% style="width:522px" %)Association to an ISO concept reference. 150 +|(% style="width:195px" %)ISOConceptReference|(% style="width:210px" %) |(% style="width:522px" %)The identity of an ISO concept definition. 151 +|(% style="width:195px" %) |(% style="width:210px" %)conceptAgency|(% style="width:522px" %)The maintenance agency of the concept scheme containing the concept. 152 +|(% style="width:195px" %) |(% style="width:210px" %)conceptSchemeID|(% style="width:522px" %)The identifier of the concept scheme. 153 +|(% style="width:195px" %) |(% style="width:210px" %)conceptID|(% style="width:522px" %)The identifier of the concept. 152 152 ))) 153 153 154 154 == {{id name="_Toc370997"/}}4.5 Category Scheme == ... ... @@ -167,7 +167,7 @@ 167 167 168 168 The categories are modelled as a hierarchical //ItemScheme//. The CategoryScheme inherits from the //ItemScheme// and has the following attributes: 169 169 170 -* id // //172 +* id 171 171 * uri 172 172 * urn 173 173 * version ... ... @@ -177,7 +177,7 @@ 177 177 * structureURL 178 178 * serviceURL 179 179 * final 180 -* isPartial // //182 +* isPartial 181 181 182 182 Category inherits from //Item// and has the following attributes: 183 183 ... ... @@ -201,29 +201,25 @@ 201 201 202 202 ==== 4.5.4.1 Definitions ==== 203 203 204 -: 205 - 206 206 ((( 207 -|**Class**|**Feature**|**Description** 208 -|CategoryScheme|((( 207 +(% style="width:965.294px" %) 208 +|(% style="width:171px" %)**Class**|(% style="width:213px" %)**Feature**|(% style="width:577px" %)**Description** 209 +|(% 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|((( 212 +)))|(% style="width:577px" %)The descriptive information for an arrangement or division of categories into groups based on characteristics, which the objects have in common. 213 +|(% style="width:171px" %) |(% style="width:213px" %)/items|(% style="width:577px" %)Associates the categories. 214 +|(% 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|((( 217 +)))|(% style="width:577px" %)An item at any level within a classification, typically tabulation categories, sections, subsections, divisions, subdivisions, groups, subgroups, classes and subclasses. 218 +|(% style="width:171px" %) |(% style="width:213px" %)/hierarchy|(% style="width:577px" %)Associates the parent and the child Category. 219 +|(% 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. 222 +)))|(% style="width:577px" %)Associates anIdentifableArtefact with a Category. 223 +|(% style="width:171px" %) |(% style="width:213px" %)+categorisedArtefact|(% style="width:577px" %)Associates the IdentifableArtefact. 224 +|(% 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 ====== 233 +(% class="wikigeneratedid" id="HFigure20TheOrganisationSchemeclassdiagram" %) 234 +**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,69 @@ 253 253 254 254 ==== 4.6.2.2 Definitions ==== 255 255 256 -|**Class**|**Feature**|**Description** 257 -|//OrganisationScheme//|((( 255 +(% style="width:845.294px" %) 256 +|(% style="width:181px" %)**Class**|(% style="width:217px" %)**Feature**|(% style="width:429px" %)**Description** 257 +|(% 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//|((( 265 +)))|(% style="width:429px" %)A maintained collection of Organisations. 266 +|(% style="width:181px" %) |(% style="width:217px" %)/items|(% style="width:429px" %)Association to the Organisations in the scheme. 267 +|(% 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|((( 275 +)))|(% 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. 276 +|(% style="width:181px" %) |(% style="width:217px" %)+contact|(% style="width:429px" %)Association to the Contact information. 277 +|(% style="width:181px" %) |(% style="width:217px" %)/hierarchy|(% style="width:429px" %)Association to child Organisations. 278 +|(% 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. 279 +|(% style="width:181px" %) |(% style="width:217px" %)name|(% style="width:429px" %)The designation of the Contact person by a linguistic expression. 280 +|(% 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. 281 +|(% 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. 282 +|(% style="width:181px" %) |(% style="width:217px" %)telephone|(% style="width:429px" %)The telephone number of the Contact. 283 +|(% style="width:181px" %) |(% style="width:217px" %)fax|(% style="width:429px" %)The fax number of the Contact. 284 +|(% style="width:181px" %) |(% style="width:217px" %)email|(% style="width:429px" %)The Internet e-mail address of the Contact. 285 +|(% style="width:181px" %) |(% style="width:217px" %)X400|(% style="width:429px" %)The X400 address of the Contact. 286 +|(% style="width:181px" %) |(% style="width:217px" %)uri|(% style="width:429px" %)The URL address of the Contact. 287 +|(% style="width:181px" %)AgencyScheme|(% style="width:217px" %) |(% style="width:429px" %)A maintained collection of Maintenace Agencies. 288 +|(% style="width:181px" %) |(% style="width:217px" %)/items|(% style="width:429px" %)Association to the Maintenance Agency in the scheme. 289 +|(% style="width:181px" %)DataProviderScheme|(% style="width:217px" %) |(% style="width:429px" %)A maintained collection of Data Providers. 290 +|(% style="width:181px" %) |(% style="width:217px" %)/items|(% style="width:429px" %)Association to the Data Providers in the scheme. 291 +|(% style="width:181px" %)DataConsumerScheme|(% style="width:217px" %) |(% style="width:429px" %)A maintained collection of Data Consumers. 292 +|(% style="width:181px" %) |(% style="width:217px" %)/items|(% style="width:429px" %)Association to the Data Consumers in the scheme. 293 +|(% style="width:181px" %)OrganisationUnitScheme|(% style="width:217px" %) |(% style="width:429px" %)A maintained collection of Organisation Units. 294 +|(% style="width:181px" %) |(% style="width:217px" %)/items|(% style="width:429px" %)Association to the Organisation Units in the scheme. 295 +|(% 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|((( 298 +)))|(% 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. 299 +|(% 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|((( 302 +)))|(% style="width:429px" %)An organisation that produces data or reference metadata. 303 +|(% 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|((( 306 +)))|(% style="width:429px" %)An organisation using data as input for further processing. 307 +|(% style="width:181px" %)OrganisationUnit|(% style="width:217px" %)((( 323 323 Inherits from 309 +//Organisation// 310 +)))|(% style="width:429px" %)A designation in the organisational structure. 311 +|(% 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 317 + 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** 345 +(% style="width:1033.29px" %) 346 +|**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 349 +//ItemScheme// 350 +)))|(% 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. 351 +| |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. 355 +)))|(% style="width:687px" %)A component that gives structure to the report and links to data and metadata. 356 +| |hierarchy|(% style="width:687px" %)Associates child Reporting Category. 357 +| |+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. 358 +| |+structure|(% style="width:687px" %)((( 359 +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