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, 0 added, 3 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,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 === ... ... @@ -56,18 +56,21 @@ 56 56 57 57 ==== 4.3.2.2 Definitions ==== 58 58 57 +: 58 + 59 59 ((( 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 +|**Class**|**Feature**|**Description** 61 +|Codelist|((( 63 63 Inherits from 63 + 64 64 //ItemScheme// 65 -)))| (% style="width:598px" %)A list from which some statistical concepts (coded concepts) take their values.66 -| (% style="width:132px" %)Code|(% style="width:172px" %)(((65 +)))|A list from which some statistical concepts (coded concepts) take their values. 66 +|Code|((( 67 67 Inherits from 68 + 68 68 //Item// 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.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. 71 71 ))) 72 72 73 73 == {{id name="_Toc370992"/}}4.4 Concept Scheme and Concepts == ... ... @@ -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 === ... ... @@ -82,18 +82,18 @@ 82 82 83 83 The ConceptScheme inherits from the //ItemScheme //and therefore has the following attributes: 84 84 85 -* id 86 -* uri 87 -* urn 88 -* version 89 -* validFrom 90 -* validTo 84 +* id// // 85 +* uri// // 86 +* urn// // 87 +* version// // 88 +* validFrom// // 89 +* validTo// // 91 91 * isExternalReference 92 92 * registryURL 93 93 * structureURL 94 94 * repositoryURL 95 -* final 96 -* isPartial 94 +* final// // 95 +* isPartial// // 97 97 98 98 Concept inherits from Item and has the following attributes: 99 99 ... ... @@ -111,8 +111,6 @@ 111 111 112 112 === {{id name="_Toc370995"/}}4.4.3 Class Diagram - Relationship === 113 113 114 -[[image:1747732242162-856.png]] 115 - 116 116 **Figure 17: Relationship class diagram of the Concept Scheme** 117 117 118 118 === {{id name="_Toc370996"/}}4.4.4 Explanation of the diagram === ... ... @@ -119,8 +119,10 @@ 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.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 123 123 121 +MetadataStructureDefinition. 122 + 124 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 125 125 126 126 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. ... ... @@ -133,26 +133,27 @@ 133 133 134 134 ==== 4.4.4.2 Definitions ==== 135 135 135 +: 136 + 136 136 ((( 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" %)((( 138 +|**Class**|**Feature**|**Description** 139 +|ConceptScheme|((( 140 140 Inherits from 141 141 142 142 //ItemScheme// 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" %)(((143 +)))|The descriptive information for an arrangement or division of concepts into groups based on characteristics, which the objects have in common. 144 +|Concept|((( 145 145 Inherits from 146 146 147 147 //Item// 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.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. 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,25 +205,29 @@ 205 205 206 206 ==== 4.5.4.1 Definitions ==== 207 207 208 +: 209 + 208 208 ((( 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" %)((( 211 +|**Class**|**Feature**|**Description** 212 +|CategoryScheme|((( 212 212 Inherits from 214 + 213 213 //ItemScheme// 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" %)(((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|((( 217 217 Inherits from 220 + 218 218 //Item// 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" %)(((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|((( 222 222 Inherits from 226 + 223 223 MaintainableArtefact 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.228 +)))|Associates anIdentifableArtefact with a Category. 229 +| |+categorisedArtefact|Associates the IdentifableArtefact. 230 +| |+categorisedBy|Associates the Category. 227 227 ))) 228 228 229 229 == {{id name="_Toc371002"/}}4.6 Organisation Scheme == ... ... @@ -232,8 +232,7 @@ 232 232 233 233 [[image:SDMX_2-1_SECTION_2_InformationModel_2020-07_dcd0149.png||height="456" width="580"]] 234 234 235 -(% class="wikigeneratedid" id="HFigure20TheOrganisationSchemeclassdiagram" %) 236 -**Figure 20 The Organisation Scheme class diagram** 239 +====== Figure 20 The Organisation Scheme class diagram ====== 237 237 238 238 === {{id name="_Toc371004"/}}4.6.2 Explanation of the Diagram === 239 239 ... ... @@ -254,69 +254,83 @@ 254 254 255 255 ==== 4.6.2.2 Definitions ==== 256 256 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" %)((( 260 +|**Class**|**Feature**|**Description** 261 +|//OrganisationScheme//|((( 260 260 Abstract Class Inherits from 263 + 261 261 //ItemScheme// 265 + 262 262 Sub classes are: 267 + 263 263 AgencyScheme 269 + 264 264 DataProviderScheme 271 + 265 265 DataConsumerScheme 273 + 266 266 OrganisationUnitScheme 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" %)(((275 +)))|A maintained collection of Organisations. 276 +| |/items|Association to the Organisations in the scheme. 277 +|//Organisation//|((( 270 270 Inherits from 279 + 271 271 //Item// 281 + 272 272 Sub classes are: 283 + 273 273 Agency 285 + 274 274 DataProvider 287 + 275 275 DataConsumer 289 + 276 276 OrganisationUnit 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" %)(((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|((( 298 298 Inherits from 313 + 299 299 //Organisation// 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" %)(((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|((( 302 302 Inherits from 318 + 303 303 //Organisation// 304 -)))| (% style="width:429px" %)An organisation that produces data or reference metadata.305 -| (% style="width:181px" %)DataConsumer|(% style="width:217px" %)(((320 +)))|An organisation that produces data or reference metadata. 321 +|DataConsumer|((( 306 306 Inherits from 323 + 307 307 //Organisation// 308 -)))| (% style="width:429px" %)An organisation using data as input for further processing.309 -| (% style="width:181px" %)OrganisationUnit|(% style="width:217px" %)(((325 +)))|An organisation using data as input for further processing. 326 +|OrganisationUnit|((( 310 310 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 314 314 329 +//Organisation // 330 +)))|A designation in the organisational structure. 331 +| |/hierarchy|Association to child Organisation Units 332 + 315 315 == {{id name="_Toc371005"/}}4.7 Reporting Taxonomy == 316 316 317 317 === {{id name="_Toc371006"/}}4.7.1 Class Diagram === 318 318 319 - 320 320 **Figure 21: Class diagram of the Reporting Taxonomy** 321 321 322 322 === {{id name="_Toc371007"/}}4.7.2 Explanation of the Diagram === ... ... @@ -344,19 +344,22 @@ 344 344 345 345 ==== 4.7.2.2 Definitions ==== 346 346 347 -(% style="width:1033.29px" %) 348 -|**Class**|**Feature**|(% style="width:687px" %)**Description** 364 +|**Class**|**Feature**|**Description** 349 349 |ReportingTaxonomy|((( 350 350 Inherits from 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 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 354 354 |ReportingCategory|((( 355 355 Inherits from 373 + 356 356 //Item// 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. 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. 362 362 )))
- 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