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)
Details
- Page properties
-
- Content
-
... ... @@ -7,27 +7,15 @@ 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 9 Codelist 10 - 11 11 ConceptScheme 12 - 13 13 CategoryScheme 14 - 15 -AgencyScheme, DataProviderScheme, MetadataProviderScheme, 16 - 17 -DataConsumerScheme, OrganisationUnitScheme, which all inherit from the abstract class //OrganisationScheme// 18 - 12 +AgencyScheme, DataProviderScheme, MetadataProviderScheme, DataConsumerScheme, OrganisationUnitScheme, which all inherit from the abstract class //OrganisationScheme// 19 19 ReportingTaxonomy 20 - 21 21 TransformationScheme 22 - 23 23 RulesetScheme 24 - 25 25 UserDefinedOperatorScheme 26 - 27 27 NamePersonalisationScheme 28 - 29 29 CustomTypeScheme 30 - 31 31 VtlMappingScheme 32 32 33 33 Note that the VTL related schemes (the last 6 of the above list) are detailed in a dedicated section below (section 15). ... ... @@ -48,11 +48,24 @@ 48 48 49 49 ==== 4.3.2.1 Narrative ==== 50 50 51 -The Codelist inherits from the //ItemScheme// and therefore has the following attributes: id uri urn version validFrom validTo isExternalReference serviceURL structureURL isPartial39 +The Codelist inherits from the //ItemScheme// and therefore has the following attributes: 52 52 41 +id 42 +uri 43 +urn 44 +version 45 +validFrom 46 +validTo 47 +isExternalReference 48 +serviceURL 49 +structureURL 50 +isPartial 51 + 53 53 The Code inherits from //Item// and has the following attributes: 54 54 55 -id uri urn 54 +id 55 +uri 56 +urn 56 56 57 57 Both Codelist and Code have the association to InternationalString to support a multilingual name, an optional multi-lingual description, and an association to Annotation to support notes (not shown). 58 58 ... ... @@ -87,14 +87,12 @@ 87 87 88 88 ==== 4.3.3.1 Narrative ==== 89 89 90 -A Codelist may extend other Codelists via the CodelistExtension class. The latter, via the sequence, indicates the order of precedence of the extended Codelists for conflict resolution of Codes. Besides that, the prefix property is used to ensure uniqueness of inherited Codes in the extending ^^[[(%class="wikiinternallinkwikiinternallink"%)^^2^^>>path:#sdfootnote2sym||name="sdfootnote2anc"]](%%)^^Codelist in case conflicting Codes must be included in the latter. Each CodelistExtension association may include one InclusiveCodeSelection or one ExclusiveCodeSelection; those allow including or excluding a specific selection of Codes from the extended Codelists.91 +A Codelist may extend other Codelists via the CodelistExtension class. The latter, via the sequence, indicates the order of precedence of the extended Codelists for conflict resolution of Codes. Besides that, the prefix property is used to ensure uniqueness of inherited Codes in the extending{{footnote}}The Codelist that extends 0..* Codelists is the 'extending' Codelist, while the Codelist(s) that are inherited is/are the 'extended' Codelist(s).{{/footnote}} Codelist in case conflicting Codes must be included in the latter. Each CodelistExtension association may include one InclusiveCodeSelection or one ExclusiveCodeSelection; those allow including or excluding a specific selection of Codes from the extended Codelists. 91 91 92 92 The code selection classes may have MemberValues in order to specify the subset of the Codes that should be included or excluded from the extended Codelist. A MemberValue may have a value that corresponds to a ,,Code,,, including its children ,,Code,,s (via the ,,cascadeValues,, property), or even include instances of the wildcard character ‘%’ in order to point to a set of ,,Code,,s with common parts in their identifiers. 93 93 94 94 ==== 4.3.3.2 Definitions ==== 95 95 96 -: 97 - 98 98 ((( 99 99 (% style="width:753.039px" %) 100 100 |(% style="width:184px" %)**Class**|(% style="width:145px" %)**Feature**|(% style="width:421px" %)**Description** ... ... @@ -114,7 +114,7 @@ 114 114 115 115 === 4.3.4 Class Diagram – Geospatial Codelist === 116 116 117 -The geospatial support is implemented via an extension of the normal ,,Codelist,,. This is illustrated in the following diagrams.116 +The geospatial support is implemented via an extension of the normal //Codelist//. This is illustrated in the following diagrams. 118 118 119 119 [[image:SDMX 3-0-0 SECTION 2 FINAL-1.0 (1)_en_472b895.jpg||height="863" width="466"]] 120 120 ... ... @@ -129,7 +129,6 @@ 129 129 A //GeoCodelist// is a specialisation of Codelist that includes geospatial information, by comprising a set of special Codes, i.e., //GeoRefCode//s. A //GeoCodelist// may be implemented by any of the two following classes, via the geoType property: 130 130 131 131 GeographicCodelist 132 - 133 133 GeoGridCodelist 134 134 135 135 The former, i.e., GeographicCodelist, comprises a set of GeoFeatureSetCodes, by adding a value in the Code that follows a pattern to represent a geo feature set. ... ... @@ -151,9 +151,7 @@ 151 151 ))) 152 152 |(% colspan="2" %)//GeoRefCode//|(% colspan="4" %)((( 153 153 Abstract Class Sub Classes: 154 - 155 155 GeoFeatureSet 156 - 157 157 GeoGridCode 158 158 )))|The abstract class that represents a special type of Code, which includes geospatial information. 159 159 |(% colspan="2" %)GeographicCodelist|(% colspan="4" %) |A special Codelist that has been extended to add a geographical feature set to each of its items, typically, this would include all types of administrative geographies. ... ... @@ -178,7 +178,16 @@ 178 178 179 179 A ValueList inherits from //EnumeratedList// (and hence the //MaintenableArtefact//) and thus has the following attributes: 180 180 181 -id// //uri// //urn// //version// //validFrom// //validTo// //isExternalReference registryURL structureURL repositoryURL 177 +id 178 +uri 179 +urn 180 +version 181 +validFrom 182 +validTo 183 +isExternalReference 184 +registryURL 185 +structureURL 186 +repositoryURL 182 182 183 183 ValueItem inherits from //EnumeratedItem//, which adds an id, with relaxed constraints, to the former. 184 184 ... ... @@ -188,17 +188,18 @@ 188 188 189 189 ==== 4.4.2.2 Definitions ==== 190 190 191 -|**Class**|**Feature**|**Description** 196 +(% style="width:749.039px" %) 197 +|**Class**|**Feature**|(% style="width:421px" %)**Description** 192 192 |ValueList|((( 193 193 Inherits from 194 194 195 195 //EnumeratedList// 196 -)))|A list from which some statistical concepts (enumerated concepts) take their values. 202 +)))|(% style="width:421px" %)A list from which some statistical concepts (enumerated concepts) take their values. 197 197 |ValueItem|((( 198 198 Inherits from 199 199 200 200 //EnumeratedItem// 201 -)))|A language independent set of letters, numbers or symbols that represent a concept whose meaning is described in a natural language. 207 +)))|(% style="width:421px" %)A language independent set of letters, numbers or symbols that represent a concept whose meaning is described in a natural language. 202 202 203 203 == 4.5 Concept Scheme and Concepts == 204 204 ... ... @@ -210,10 +210,26 @@ 210 210 211 211 === 4.5.2 Explanation of the Diagram === 212 212 213 -The ConceptScheme inherits from the //ItemScheme //and therefore has the following attributes: id uri urn version validFrom validTo isExternalReference registryURL structureURL repositoryURL isPartial Concept inherits from Item and has the following attributes:219 +The ConceptScheme inherits from the //ItemScheme //and therefore has the following attributes: 214 214 215 -id uri urn 221 +id 222 +uri 223 +urn 224 +version 225 +validFrom 226 +validTo 227 +isExternalReference 228 +registryURL 229 +structureURL 230 +repositoryURL 231 +isPartial 216 216 233 +Concept inherits from Item and has the following attributes: 234 + 235 +id 236 +uri 237 +urn 238 + 217 217 Through the inheritance from //NameableArtefact// both ConceptScheme and Concept have the association to InternationalString to support a multi-lingual name, an optional multilingual description, and an association to Annotation to support notes (not shown). 218 218 219 219 Through the inheritance from //ItemScheme// the ConceptScheme comprise one or more Concepts, and the Concept itself can have one or more child Concepts in the (inherited) hierarchy association. Note that a child Concept can have only one parent Concept in this association. ... ... @@ -240,24 +240,23 @@ 240 240 241 241 ==== 4.5.4.2 Definitions ==== 242 242 243 -|**Class**|**Feature**|**Description** 244 -|ConceptScheme|((( 265 +(% style="width:765.039px" %) 266 +|(% style="width:204px" %)**Class**|(% style="width:222px" %)**Feature**|(% style="width:337px" %)**Description** 267 +|(% style="width:204px" %)ConceptScheme|(% style="width:222px" %)((( 245 245 Inherits from 246 - 247 247 //ItemScheme// 248 -)))|The descriptive information for an arrangement or division of concepts into groups based on characteristics, which the objects have in common. 249 -|Concept|((( 270 +)))|(% style="width:337px" %)The descriptive information for an arrangement or division of concepts into groups based on characteristics, which the objects have in common. 271 +|(% style="width:204px" %)Concept|(% style="width:222px" %)((( 250 250 Inherits from 251 - 252 252 //Item// 253 -)))|A concept is a unit of knowledge created by a unique combination of characteristics. 254 -| |/hierarchy|Associates the parent and the child concept. 255 -| |coreRepresentation|Associates a Representation. 256 -| |+ISOConcept|Association to an ISO concept reference. 257 -|ISOConceptReference| |The identity of an ISO concept definition. 258 -| |conceptAgency|The maintenance agency of the concept scheme containing the concept. 259 -| |conceptSchemeID|The identifier of the concept scheme. 260 -| |conceptID|The identifier of the concept. 274 +)))|(% style="width:337px" %)A concept is a unit of knowledge created by a unique combination of characteristics. 275 +|(% style="width:204px" %) |(% style="width:222px" %)/hierarchy|(% style="width:337px" %)Associates the parent and the child concept. 276 +|(% style="width:204px" %) |(% style="width:222px" %)coreRepresentation|(% style="width:337px" %)Associates a Representation. 277 +|(% style="width:204px" %) |(% style="width:222px" %)+ISOConcept|(% style="width:337px" %)Association to an ISO concept reference. 278 +|(% style="width:204px" %)ISOConceptReference|(% style="width:222px" %) |(% style="width:337px" %)The identity of an ISO concept definition. 279 +|(% style="width:204px" %) |(% style="width:222px" %)conceptAgency|(% style="width:337px" %)The maintenance agency of the concept scheme containing the concept. 280 +|(% style="width:204px" %) |(% style="width:222px" %)conceptSchemeID|(% style="width:337px" %)The identifier of the concept scheme. 281 +|(% style="width:204px" %) |(% style="width:222px" %)conceptID|(% style="width:337px" %)The identifier of the concept. 261 261 262 262 == 4.6 Category Scheme == 263 263 ... ... @@ -277,11 +277,22 @@ 277 277 278 278 The categories are modelled as a hierarchical //ItemScheme//. The CategoryScheme inherits from the //ItemScheme// and has the following attributes: 279 279 280 -id uri urn version validFrom validTo isExternalReference structureURL serviceURL isPartial 301 +id 302 +uri 303 +urn 304 +version 305 +validFrom 306 +validTo 307 +isExternalReference 308 +structureURL 309 +serviceURL 310 +isPartial 281 281 282 282 Category inherits from //Item// and has the following attributes: 283 283 284 -id uri urn 314 +id 315 +uri 316 +urn 285 285 286 286 Both CategoryScheme and Category have the association to InternationalString to support a multi-lingual name, an optional multi-lingual description, and an association to Annotation to support notes (not shown on the model). 287 287 ... ... @@ -299,22 +299,20 @@ 299 299 300 300 ==== 4.6.4.1 Definitions ==== 301 301 334 +(% style="width:753.039px" %) 302 302 |**Class**|(% colspan="2" %)**Feature**|**Description** 303 303 |CategoryScheme|(% colspan="2" %)((( 304 304 Inherits from 305 - 306 306 //ItemScheme// 307 307 )))|The descriptive information for an arrangement or division of categories into groups based on characteristics, which the objects have in common. 308 308 | |(% colspan="2" %)/items|Associates the categories. 309 309 |Category|((( 310 310 Inherits from 311 - 312 312 //Item// 313 313 )))|(% colspan="2" %)An item at any level within a classification, typically tabulation categories, sections, subsections, divisions, subdivisions, groups, subgroups, classes and subclasses. 314 314 | |/hierarchy|(% colspan="2" %)Associates the parent and the child Category. 315 315 |Categorisation|((( 316 316 Inherits from 317 - 318 318 //MaintainableArtefact// 319 319 )))|(% colspan="2" %)Associates an Identifable Artefact with a Category. 320 320 | |+categorisedArtefact|(% colspan="2" %)Associates the Identifable Artefact. ... ... @@ -348,91 +348,75 @@ 348 348 349 349 ==== 4.7.2.2 Definitions ==== 350 350 351 -|**Class**|**Feature**|**Description** 352 -|//OrganisationScheme//|((( 381 +(% style="width:763.039px" %) 382 +|**Class**|(% style="width:246px" %)**Feature**|(% style="width:336px" %)**Description** 383 +|//OrganisationScheme//|(% style="width:246px" %)((( 353 353 Abstract Class Inherits from 354 - 355 355 //ItemScheme// 356 356 357 357 Sub classes are: 358 - 359 359 AgencyScheme 360 - 361 361 DataProviderScheme 362 - 363 363 MetadataProviderScheme DataConsumerScheme 364 - 365 365 OrganisationUnitScheme 366 -)))|A maintained collection of Organisations. 367 -| |/items|((( 392 +)))|(% style="width:336px" %)A maintained collection of Organisations. 393 +| |(% style="width:246px" %)/items|(% style="width:336px" %)((( 368 368 Association to the 369 369 370 370 Organisations in the scheme. 371 371 ))) 372 -|//Organisation//|((( 398 +|//Organisation//|(% style="width:246px" %)((( 373 373 Abstract Class 400 +Inherits from //Item// 374 374 375 -Inherits from 376 - 377 -//Item// 378 - 379 379 Sub classes are: 380 - 381 381 Agency 382 - 383 383 DataProvider 384 - 385 385 MetadataProvider DataConsumer 386 - 387 387 OrganisationUnit 388 -)))|An organisation is a unique framework of authority within which a person or persons act, or are designated to act, towards some purpose. 389 -| |+contact|Association to the Contact information. 390 -| |/hierarchy|Association to child Organisations. 391 -|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. 392 -| |name|The designation of the Contact person by a linguistic expression. 393 -| |organisationUnit|The designation of the organisational structure by a linguistic expression, within which Contact person works. 394 -| |responsibility|The function of the contact person with respect to the organisation role for which this person is the Contact. 395 -| |telephone|The telephone number of the Contact. 396 -| |fax|The fax number of the Contact. 397 -| |email|The Internet e-mail address of the Contact. 398 -| |X400|The X400 address of the Contact. 399 -| |uri|The URL address of the Contact. 400 -|AgencyScheme| |A maintained collection of Maintenance Agencies. 401 -| |/items|Association to the Maintenance Agency in the scheme. 402 -|DataProviderScheme| |A maintained collection of Data Providers. 403 -| |/items|Association to the Data Providers in the scheme. 404 -|MetadataProviderScheme| |A maintained collection of Metadata Providers. 405 -| |/items|Association to the Metadata Providers in the scheme. 406 -|DataConsumerScheme| |A maintained collection of Data Consumers. 407 -| |/items|Association to the Data Consumers in the scheme. 408 -|OrganisationUnitScheme| |A maintained collection of Organisation Units. 409 -| |/items|Association to the Organisation Units in the scheme. 410 -|Agency|((( 407 +)))|(% style="width:336px" %)An organisation is a unique framework of authority within which a person or persons act, or are designated to act, towards some purpose. 408 +| |(% style="width:246px" %)+contact|(% style="width:336px" %)Association to the Contact information. 409 +| |(% style="width:246px" %)/hierarchy|(% style="width:336px" %)Association to child Organisations. 410 +|Contact|(% style="width:246px" %) |(% style="width:336px" %)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. 411 +| |(% style="width:246px" %)name|(% style="width:336px" %)The designation of the Contact person by a linguistic expression. 412 +| |(% style="width:246px" %)organisationUnit|(% style="width:336px" %)The designation of the organisational structure by a linguistic expression, within which Contact person works. 413 +| |(% style="width:246px" %)responsibility|(% style="width:336px" %)The function of the contact person with respect to the organisation role for which this person is the Contact. 414 +| |(% style="width:246px" %)telephone|(% style="width:336px" %)The telephone number of the Contact. 415 +| |(% style="width:246px" %)fax|(% style="width:336px" %)The fax number of the Contact. 416 +| |(% style="width:246px" %)email|(% style="width:336px" %)The Internet e-mail address of the Contact. 417 +| |(% style="width:246px" %)X400|(% style="width:336px" %)The X400 address of the Contact. 418 +| |(% style="width:246px" %)uri|(% style="width:336px" %)The URL address of the Contact. 419 +|AgencyScheme|(% style="width:246px" %) |(% style="width:336px" %)A maintained collection of Maintenance Agencies. 420 +| |(% style="width:246px" %)/items|(% style="width:336px" %)Association to the Maintenance Agency in the scheme. 421 +|DataProviderScheme|(% style="width:246px" %) |(% style="width:336px" %)A maintained collection of Data Providers. 422 +| |(% style="width:246px" %)/items|(% style="width:336px" %)Association to the Data Providers in the scheme. 423 +|MetadataProviderScheme|(% style="width:246px" %) |(% style="width:336px" %)A maintained collection of Metadata Providers. 424 +| |(% style="width:246px" %)/items|(% style="width:336px" %)Association to the Metadata Providers in the scheme. 425 +|DataConsumerScheme|(% style="width:246px" %) |(% style="width:336px" %)A maintained collection of Data Consumers. 426 +| |(% style="width:246px" %)/items|(% style="width:336px" %)Association to the Data Consumers in the scheme. 427 +|OrganisationUnitScheme|(% style="width:246px" %) |(% style="width:336px" %)A maintained collection of Organisation Units. 428 +| |(% style="width:246px" %)/items|(% style="width:336px" %)Association to the Organisation Units in the scheme. 429 +|Agency|(% style="width:246px" %)((( 411 411 Inherits from 412 - 413 413 //Organisation// 414 -)))|Responsible agency for maintaining artefacts such as statistical classifications, glossaries, structural metadata such as Data and Metadata Structure Definitions, Concepts and Code lists. 415 -|DataProvider|((( 432 +)))|(% style="width:336px" %)Responsible agency for maintaining artefacts such as statistical classifications, glossaries, structural metadata such as Data and Metadata Structure Definitions, Concepts and Code lists. 433 +|DataProvider|(% style="width:246px" %)((( 416 416 Inherits from 417 - 418 418 //Organisation// 419 -)))|An organisation that produces data. 420 -|MetadataProvider|((( 436 +)))|(% style="width:336px" %)An organisation that produces data. 437 +|MetadataProvider|(% style="width:246px" %)((( 421 421 Inherits from 422 - 423 423 //Organisation// 424 -)))|An organisation that produces reference metadata. 425 -|DataConsumer|((( 440 +)))|(% style="width:336px" %)An organisation that produces reference metadata. 441 +|DataConsumer|(% style="width:246px" %)((( 426 426 Inherits from 427 - 428 428 //Organisation// 429 -)))|An organisation using data as input for further processing. 430 -|OrganisationUnit|((( 444 +)))|(% style="width:336px" %)An organisation using data as input for further processing. 445 +|OrganisationUnit|(% style="width:246px" %)((( 431 431 Inherits from 432 - 433 433 //Organisation// 434 -)))|A designation in the organisational structure. 435 -| |/hierarchy|Association to child Organisation Units 448 +)))|(% style="width:336px" %)A designation in the organisational structure. 449 +| |(% style="width:246px" %)/hierarchy|(% style="width:336px" %)Association to child Organisation Units 436 436 437 437 == 4.8 Reporting Taxonomy == 438 438 ... ... @@ -466,22 +466,23 @@ 466 466 467 467 ==== 4.8.2.2 Definitions ==== 468 468 469 -|**Class**|**Feature**|**Description** 470 -|ReportingTaxonomy|((( 483 +(% style="width:759.039px" %) 484 +|(% style="width:177px" %)**Class**|(% style="width:152px" %)**Feature**|(% style="width:428px" %)**Description** 485 +|(% style="width:177px" %)ReportingTaxonomy|(% style="width:152px" %)((( 471 471 Inherits from 472 472 473 473 //ItemScheme// 474 -)))|A scheme which defines the composition structure of a data report where each component can be described by an independent Dataflow or Metadataflow. 475 -| |/items|Associates the Reporting Category 476 -|ReportingCategory|((( 489 +)))|(% style="width:428px" %)A scheme which defines the composition structure of a data report where each component can be described by an independent Dataflow or Metadataflow. 490 +|(% style="width:177px" %) |(% style="width:152px" %)/items|(% style="width:428px" %)Associates the Reporting Category 491 +|(% style="width:177px" %)ReportingCategory|(% style="width:152px" %)((( 477 477 Inherits from 478 478 479 479 //Item// 480 -)))|A component that gives structure to the report and links to data and metadata. 481 -| |/hierarchy|Associates child Reporting Category. 482 -| |+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. 483 -| |+structure|((( 484 -Association to the Data Structure 485 - 486 -Definition and Metadata Structure Definitions which define the structural metadata describing the data and metadata that are contained at this part of the report. 495 +)))|(% style="width:428px" %)A component that gives structure to the report and links to data and metadata. 496 +|(% style="width:177px" %) |(% style="width:152px" %)/hierarchy|(% style="width:428px" %)Associates child Reporting Category. 497 +|(% style="width:177px" %) |(% style="width:152px" %)+flow|(% style="width:428px" %)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. 498 +|(% style="width:177px" %) |(% style="width:152px" %)+structure|(% style="width:428px" %)((( 499 +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. 487 487 ))) 501 + 502 +{{putFootnotes/}}