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
-
... ... @@ -6,11 +6,11 @@ 6 6 7 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 8 9 -* Codelist // //10 -* ConceptScheme // //11 -* CategoryScheme // //9 +* Codelist 10 +* ConceptScheme 11 +* CategoryScheme 12 12 * AgencyScheme, DataProviderScheme, DataConsumerScheme, OrganisationUnitScheme which all inherit from the abstract class //OrganisationScheme// 13 -* Reporting Taxonomy // //13 +* Reporting Taxonomy 14 14 15 15 == {{id name="_Toc370988"/}}4.2 Inheritance View == 16 16 ... ... @@ -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 === ... ... @@ -54,21 +54,18 @@ 54 54 55 55 ==== 4.3.2.2 Definitions ==== 56 56 57 -: 58 - 59 59 ((( 60 -|**Class**|**Feature**|**Description** 61 -|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" %)((( 62 62 Inherits from 63 - 64 64 //ItemScheme// 65 -)))|A list from which some statistical concepts (coded concepts) take their values. 66 -|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" %)((( 67 67 Inherits from 68 - 69 69 //Item// 70 -)))|A language independent set of letters, numbers or symbols that represent a concept whose meaning is described in a natural language. 71 -| |/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. 72 72 ))) 73 73 74 74 == {{id name="_Toc370992"/}}4.4 Concept Scheme and Concepts == ... ... @@ -75,6 +75,8 @@ 75 75 76 76 === {{id name="_Toc370993"/}}4.4.1 Class Diagram - Inheritance === 77 77 77 +[[image:1747732287949-594.png]] 78 + 78 78 **Figure 16 Class diagram of the Concept Scheme** 79 79 80 80 === {{id name="_Toc370994"/}}4.4.2 Explanation of the Diagram === ... ... @@ -81,18 +81,18 @@ 81 81 82 82 The ConceptScheme inherits from the //ItemScheme //and therefore has the following attributes: 83 83 84 -* id // //85 -* uri // //86 -* urn // //87 -* version // //88 -* validFrom // //89 -* validTo // //85 +* id 86 +* uri 87 +* urn 88 +* version 89 +* validFrom 90 +* validTo 90 90 * isExternalReference 91 91 * registryURL 92 92 * structureURL 93 93 * repositoryURL 94 -* final // //95 -* isPartial // //95 +* final 96 +* isPartial 96 96 97 97 Concept inherits from Item and has the following attributes: 98 98 ... ... @@ -110,6 +110,8 @@ 110 110 111 111 === {{id name="_Toc370995"/}}4.4.3 Class Diagram - Relationship === 112 112 114 +[[image:1747732242162-856.png]] 115 + 113 113 **Figure 17: Relationship class diagram of the Concept Scheme** 114 114 115 115 === {{id name="_Toc370996"/}}4.4.4 Explanation of the diagram === ... ... @@ -116,10 +116,8 @@ 116 116 117 117 ==== 4.4.4.1 Narrative ==== 118 118 119 -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. 120 120 121 -MetadataStructureDefinition. 122 - 123 123 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 124 124 125 125 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. ... ... @@ -132,27 +132,26 @@ 132 132 133 133 ==== 4.4.4.2 Definitions ==== 134 134 135 -: 136 - 137 137 ((( 138 -|**Class**|**Feature**|**Description** 139 -|ConceptScheme|((( 137 +(% style="width:931.294px" %) 138 +|(% style="width:195px" %)**Class**|(% style="width:210px" %)**Feature**|(% style="width:522px" %)**Description** 139 +|(% style="width:195px" %)ConceptScheme|(% style="width:210px" %)((( 140 140 Inherits from 141 141 142 142 //ItemScheme// 143 -)))|The descriptive information for an arrangement or division of concepts into groups based on characteristics, which the objects have in common. 144 -|Concept|((( 143 +)))|(% style="width:522px" %)The descriptive information for an arrangement or division of concepts into groups based on characteristics, which the objects have in common. 144 +|(% style="width:195px" %)Concept|(% style="width:210px" %)((( 145 145 Inherits from 146 146 147 147 //Item// 148 -)))|A concept is a unit of knowledge created by a unique combination of characteristics. 149 -| |/hierarchy|Associates the parent and the child concept. 150 -| |coreRepresentation|Associates a Representation. 151 -| |+ISOConcept|Association to an ISO concept reference. 152 -|ISOConceptReference| |The identity of an ISO concept definition. 153 -| |conceptAgency|The maintenance agency of the concept scheme containing the concept. 154 -| |conceptSchemeID|The identifier of the concept scheme. 155 -| |conceptID|The identifier of the concept. 148 +)))|(% style="width:522px" %)A concept is a unit of knowledge created by a unique combination of characteristics. 149 +|(% style="width:195px" %) |(% style="width:210px" %)/hierarchy|(% style="width:522px" %)Associates the parent and the child concept. 150 +|(% style="width:195px" %) |(% style="width:210px" %)coreRepresentation|(% style="width:522px" %)Associates a Representation. 151 +|(% style="width:195px" %) |(% style="width:210px" %)+ISOConcept|(% style="width:522px" %)Association to an ISO concept reference. 152 +|(% style="width:195px" %)ISOConceptReference|(% style="width:210px" %) |(% style="width:522px" %)The identity of an ISO concept definition. 153 +|(% style="width:195px" %) |(% style="width:210px" %)conceptAgency|(% style="width:522px" %)The maintenance agency of the concept scheme containing the concept. 154 +|(% style="width:195px" %) |(% style="width:210px" %)conceptSchemeID|(% style="width:522px" %)The identifier of the concept scheme. 155 +|(% style="width:195px" %) |(% style="width:210px" %)conceptID|(% style="width:522px" %)The identifier of the concept. 156 156 ))) 157 157 158 158 == {{id name="_Toc370997"/}}4.5 Category Scheme == ... ... @@ -171,7 +171,7 @@ 171 171 172 172 The categories are modelled as a hierarchical //ItemScheme//. The CategoryScheme inherits from the //ItemScheme// and has the following attributes: 173 173 174 -* id // //174 +* id 175 175 * uri 176 176 * urn 177 177 * version ... ... @@ -181,7 +181,7 @@ 181 181 * structureURL 182 182 * serviceURL 183 183 * final 184 -* isPartial // //184 +* isPartial 185 185 186 186 Category inherits from //Item// and has the following attributes: 187 187 ... ... @@ -205,29 +205,25 @@ 205 205 206 206 ==== 4.5.4.1 Definitions ==== 207 207 208 -: 209 - 210 210 ((( 211 -|**Class**|**Feature**|**Description** 212 -|CategoryScheme|((( 209 +(% style="width:965.294px" %) 210 +|(% style="width:171px" %)**Class**|(% style="width:213px" %)**Feature**|(% style="width:577px" %)**Description** 211 +|(% style="width:171px" %)CategoryScheme|(% style="width:213px" %)((( 213 213 Inherits from 214 - 215 215 //ItemScheme// 216 -)))|The descriptive information for an arrangement or division of categories into groups based on characteristics, which the objects have in common. 217 -| |/items|Associates the categories. 218 -|Category|((( 214 +)))|(% style="width:577px" %)The descriptive information for an arrangement or division of categories into groups based on characteristics, which the objects have in common. 215 +|(% style="width:171px" %) |(% style="width:213px" %)/items|(% style="width:577px" %)Associates the categories. 216 +|(% style="width:171px" %)Category|(% style="width:213px" %)((( 219 219 Inherits from 220 - 221 221 //Item// 222 -)))|An item at any level within a classification, typically tabulation categories, sections, subsections, divisions, subdivisions, groups, subgroups, classes and subclasses. 223 -| |/hierarchy|Associates the parent and the child Category. 224 -|Categorisation|((( 219 +)))|(% style="width:577px" %)An item at any level within a classification, typically tabulation categories, sections, subsections, divisions, subdivisions, groups, subgroups, classes and subclasses. 220 +|(% style="width:171px" %) |(% style="width:213px" %)/hierarchy|(% style="width:577px" %)Associates the parent and the child Category. 221 +|(% style="width:171px" %)Categorisation|(% style="width:213px" %)((( 225 225 Inherits from 226 - 227 227 MaintainableArtefact 228 -)))|Associates anIdentifableArtefact with a Category. 229 -| |+categorisedArtefact|Associates the IdentifableArtefact. 230 -| |+categorisedBy|Associates the Category. 224 +)))|(% style="width:577px" %)Associates anIdentifableArtefact with a Category. 225 +|(% style="width:171px" %) |(% style="width:213px" %)+categorisedArtefact|(% style="width:577px" %)Associates the IdentifableArtefact. 226 +|(% style="width:171px" %) |(% style="width:213px" %)+categorisedBy|(% style="width:577px" %)Associates the Category. 231 231 ))) 232 232 233 233 == {{id name="_Toc371002"/}}4.6 Organisation Scheme == ... ... @@ -236,7 +236,8 @@ 236 236 237 237 [[image:SDMX_2-1_SECTION_2_InformationModel_2020-07_dcd0149.png||height="456" width="580"]] 238 238 239 -====== Figure 20 The Organisation Scheme class diagram ====== 235 +(% class="wikigeneratedid" id="HFigure20TheOrganisationSchemeclassdiagram" %) 236 +**Figure 20 The Organisation Scheme class diagram** 240 240 241 241 === {{id name="_Toc371004"/}}4.6.2 Explanation of the Diagram === 242 242 ... ... @@ -257,83 +257,69 @@ 257 257 258 258 ==== 4.6.2.2 Definitions ==== 259 259 260 -|**Class**|**Feature**|**Description** 261 -|//OrganisationScheme//|((( 257 +(% style="width:845.294px" %) 258 +|(% style="width:181px" %)**Class**|(% style="width:217px" %)**Feature**|(% style="width:429px" %)**Description** 259 +|(% style="width:181px" %)//OrganisationScheme//|(% style="width:217px" %)((( 262 262 Abstract Class Inherits from 263 - 264 264 //ItemScheme// 265 - 266 266 Sub classes are: 267 - 268 268 AgencyScheme 269 - 270 270 DataProviderScheme 271 - 272 272 DataConsumerScheme 273 - 274 274 OrganisationUnitScheme 275 -)))|A maintained collection of Organisations. 276 -| |/items|Association to the Organisations in the scheme. 277 -|//Organisation//|((( 267 +)))|(% style="width:429px" %)A maintained collection of Organisations. 268 +|(% style="width:181px" %) |(% style="width:217px" %)/items|(% style="width:429px" %)Association to the Organisations in the scheme. 269 +|(% style="width:181px" %)//Organisation//|(% style="width:217px" %)((( 278 278 Inherits from 279 - 280 280 //Item// 281 - 282 282 Sub classes are: 283 - 284 284 Agency 285 - 286 286 DataProvider 287 - 288 288 DataConsumer 289 - 290 290 OrganisationUnit 291 -)))|An organisation is a unique framework of authority within which a person or persons act, or are designated to act, towards some purpose. 292 -| |+contact|Association to the Contact information. 293 -| |/hierarchy|Association to child Organisations. 294 -|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. 295 -| |name|The designation of the Contact person by a linguistic expression. 296 -| |organisationUnit|The designation of the organisational structure by a linguistic expression, within which Contact person works. 297 -| |responsibility|The function of the contact person with respect to the organisation role for which this person is the Contact. 298 -| |telephone|The telephone number of the Contact. 299 -| |fax|The fax number of the Contact. 300 -| |email|The Internet e-mail address of the Contact. 301 -| |X400|The X400 address of the Contact. 302 -| |uri|The URL address of the Contact. 303 -|AgencyScheme| |A maintained collection of Maintenace Agencies. 304 -| |/items|Association to the Maintenance Agency in the scheme. 305 -|DataProviderScheme| |A maintained collection of Data Providers. 306 -| |/items|Association to the Data Providers in the scheme. 307 -|DataConsumerScheme| |A maintained collection of Data Consumers. 308 -| |/items|Association to the Data Consumers in the scheme. 309 -|OrganisationUnitScheme| |A maintained collection of Organisation Units. 310 -| |/items|Association to the Organisation Units in the scheme. 311 -|Agency|((( 277 +)))|(% 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. 278 +|(% style="width:181px" %) |(% style="width:217px" %)+contact|(% style="width:429px" %)Association to the Contact information. 279 +|(% style="width:181px" %) |(% style="width:217px" %)/hierarchy|(% style="width:429px" %)Association to child Organisations. 280 +|(% 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. 281 +|(% style="width:181px" %) |(% style="width:217px" %)name|(% style="width:429px" %)The designation of the Contact person by a linguistic expression. 282 +|(% 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. 283 +|(% 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. 284 +|(% style="width:181px" %) |(% style="width:217px" %)telephone|(% style="width:429px" %)The telephone number of the Contact. 285 +|(% style="width:181px" %) |(% style="width:217px" %)fax|(% style="width:429px" %)The fax number of the Contact. 286 +|(% style="width:181px" %) |(% style="width:217px" %)email|(% style="width:429px" %)The Internet e-mail address of the Contact. 287 +|(% style="width:181px" %) |(% style="width:217px" %)X400|(% style="width:429px" %)The X400 address of the Contact. 288 +|(% style="width:181px" %) |(% style="width:217px" %)uri|(% style="width:429px" %)The URL address of the Contact. 289 +|(% style="width:181px" %)AgencyScheme|(% style="width:217px" %) |(% style="width:429px" %)A maintained collection of Maintenace Agencies. 290 +|(% style="width:181px" %) |(% style="width:217px" %)/items|(% style="width:429px" %)Association to the Maintenance Agency in the scheme. 291 +|(% style="width:181px" %)DataProviderScheme|(% style="width:217px" %) |(% style="width:429px" %)A maintained collection of Data Providers. 292 +|(% style="width:181px" %) |(% style="width:217px" %)/items|(% style="width:429px" %)Association to the Data Providers in the scheme. 293 +|(% style="width:181px" %)DataConsumerScheme|(% style="width:217px" %) |(% style="width:429px" %)A maintained collection of Data Consumers. 294 +|(% style="width:181px" %) |(% style="width:217px" %)/items|(% style="width:429px" %)Association to the Data Consumers in the scheme. 295 +|(% style="width:181px" %)OrganisationUnitScheme|(% style="width:217px" %) |(% style="width:429px" %)A maintained collection of Organisation Units. 296 +|(% style="width:181px" %) |(% style="width:217px" %)/items|(% style="width:429px" %)Association to the Organisation Units in the scheme. 297 +|(% style="width:181px" %)Agency|(% style="width:217px" %)((( 312 312 Inherits from 313 - 314 314 //Organisation// 315 -)))|Responsible agency for maintaining artefacts such as statistical classifications, glossaries, structural metadata such as Data and Metadata Structure Definitions, Concepts and Code lists. 316 -|DataProvider|((( 300 +)))|(% 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. 301 +|(% style="width:181px" %)DataProvider|(% style="width:217px" %)((( 317 317 Inherits from 318 - 319 319 //Organisation// 320 -)))|An organisation that produces data or reference metadata. 321 -|DataConsumer|((( 304 +)))|(% style="width:429px" %)An organisation that produces data or reference metadata. 305 +|(% style="width:181px" %)DataConsumer|(% style="width:217px" %)((( 322 322 Inherits from 323 - 324 324 //Organisation// 325 -)))|An organisation using data as input for further processing. 326 -|OrganisationUnit|((( 308 +)))|(% style="width:429px" %)An organisation using data as input for further processing. 309 +|(% style="width:181px" %)OrganisationUnit|(% style="width:217px" %)((( 327 327 Inherits from 311 +//Organisation// 312 +)))|(% style="width:429px" %)A designation in the organisational structure. 313 +|(% style="width:181px" %) |(% style="width:217px" %)/hierarchy|(% style="width:429px" %)Association to child Organisation Units 328 328 329 -//Organisation // 330 -)))|A designation in the organisational structure. 331 -| |/hierarchy|Association to child Organisation Units 332 - 333 333 == {{id name="_Toc371005"/}}4.7 Reporting Taxonomy == 334 334 335 335 === {{id name="_Toc371006"/}}4.7.1 Class Diagram === 336 336 319 + 337 337 **Figure 21: Class diagram of the Reporting Taxonomy** 338 338 339 339 === {{id name="_Toc371007"/}}4.7.2 Explanation of the Diagram === ... ... @@ -361,22 +361,19 @@ 361 361 362 362 ==== 4.7.2.2 Definitions ==== 363 363 364 -|**Class**|**Feature**|**Description** 347 +(% style="width:1033.29px" %) 348 +|**Class**|**Feature**|(% style="width:687px" %)**Description** 365 365 |ReportingTaxonomy|((( 366 366 Inherits from 367 - 368 -//ItemScheme // 369 -)))|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. 370 -| |items|Associates the Reporting Category 351 +//ItemScheme// 352 +)))|(% 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. 353 +| |items|(% style="width:687px" %)Associates the Reporting Category 371 371 |ReportingCategory|((( 372 372 Inherits from 373 - 374 374 //Item// 375 -)))|A component that gives structure to the report and links to data and metadata. 376 -| |hierarchy|Associates child Reporting Category. 377 -| |+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. 378 -| |+structure|((( 379 -Association to the Data Structure Definition and Metadata Structure 380 - 381 -Definitions which define the structural metadata describing the data and metadata that are contained at this part of the report. 357 +)))|(% style="width:687px" %)A component that gives structure to the report and links to data and metadata. 358 +| |hierarchy|(% style="width:687px" %)Associates child Reporting Category. 359 +| |+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. 360 +| |+structure|(% style="width:687px" %)((( 361 +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. 382 382 )))
- 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