Last modified by Artur on 2025/09/30 13:28
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,0 +1,1 @@ 1 +1 Introduction - Content
-
... ... @@ -1,16 +5,15 @@ 1 -{{box title="**Contents**"}} 2 -{{toc/}} 3 -{{/box}} 4 - 5 5 **Revision History** 6 6 7 -(% style="width:824.835px" %) 8 -|(% style="width:184px" %)**Revision**|(% style="width:195px" %)**Date**|(% style="width:442px" %)**Contents** 9 -|(% style="width:184px" %)DRAFT 1.0|(% style="width:195px" %)December 2024|(% style="width:442px" %)Draft release updated for SDMX 3.1 for public consultation 10 -|(% style="width:184px" %)1.0|(% style="width:195px" %)May 2025|(% style="width:442px" %)Public release for SDMX 3.1 3 +: 11 11 12 -= 1 Introduction = 5 +((( 6 +|**Revision**|**Date**|**Contents** 7 +|DRAFT 1.0|December 2024|Draft release updated for SDMX 3.1 for public consultation 8 +|1.0|May 2025|Public release for SDMX 3.1 9 +))) 13 13 11 += {{id name="_Toc90780"/}}1 Introduction = 12 + 14 14 The business vision for SDMX envisages the promotion of a “data sharing” model to facilitate low-cost, high-quality statistical data and metadata exchange. Data sharing reduces the reporting burden of organisations by allowing them to publish data once and let their counterparties “pull” data and related metadata as required. The scenario is based on: 15 15 16 16 * the availability of an abstract information model capable of supporting time series and cross-sectional data, structural metadata, and reference metadata (SDMX-IM) ... ... @@ -31,13 +31,15 @@ 31 31 32 32 These architectural standards address the ‘how’, rather than the ‘what’, and are aimed at enabling existing SDMX standards to achieve their mission. The architectural standards address registry services, which initially comprise: 33 33 34 -* structural metadata repository 35 -* data and metadata registration 36 -* query 33 +• structural metadata repository 37 37 35 +• data and metadata registration 36 + 37 +• query 38 + 38 38 The registry services outlined in this specification are designed to help the SDMX community manage the proliferation of SDMX assets and to support data sharing for reporting and dissemination. 39 39 40 -= 2 Scope and Normative Status = 41 += {{id name="_Toc90781"/}}2 Scope and Normative Status = 41 41 42 42 The scope of this document is to specify the logical interfaces for the SDMX registry in terms of the functions required and the data that may be present in the function call, and the behaviour expected of the registry. 43 43 ... ... @@ -54,9 +54,9 @@ 54 54 55 55 Note that although the term “authorised user” is used in this document, the SDMX standards do not define an access control mechanism. Such a mechanism, if required, must be chosen and implemented by the registry software provider. 56 56 57 -= 3 Scope of the SDMX Registry/Repository = 58 += {{id name="_Toc90782"/}}3 Scope of the SDMX Registry/Repository = 58 58 59 -== 3.1 Objective == 60 +=== {{id name="_Toc90783"/}}3.1 Objective === 60 60 61 61 The objective of the SDMX registry/repository is, in broad terms, to allow organisations to publish statistical data and reference metadata in known formats such that interested third parties can discover these data and interpret them accurately and correctly. The mechanism for doing this is twofold: 62 62 ... ... @@ -63,7 +63,7 @@ 63 63 1. To maintain and publish structural metadata that describes the structure and valid content of data and reference metadata sources such as databases, metadata repositories, data sets, metadata sets. This structural metadata enables software applications to understand and to interpret the data and reference metadata in these sources. 64 64 1. To enable applications, organisations, and individuals to share and to discover data and reference metadata. This facilitates data and reference metadata dissemination by implementing the data sharing vision of SDMX. 65 65 66 -== 3.2 Structural Metadata == 67 +=== {{id name="_Toc90784"/}}3.2 Structural Metadata === 67 67 68 68 Setting up structural metadata and the exchange context (referred to as “data provisioning”) involves the following steps for maintenance agencies: 69 69 ... ... @@ -89,7 +89,7 @@ 89 89 90 90 In that context, the term “Metadata” refers to reference metadata. 91 91 92 -== 3.3 Registration == 93 +=== {{id name="_Toc90785"/}}3.3 Registration === 93 93 94 94 Publishing the data and reference metadata involves the following steps for a Data/Metadata Provider: 95 95 ... ... @@ -100,13 +100,13 @@ 100 100 101 101 **Figure 2: Schematic of Registered Data and Metadata Sources in the SDMX-IM** 102 102 103 -== 3.4 Notification == 104 +=== {{id name="_Toc90786"/}}3.4 Notification === 104 104 105 105 Notifying interested parties of newly published or re-published data, reference metadata or changes in structural metadata involves: 106 106 107 107 • registry support of a subscription-based notification service which sends an email or notifies an HTTP address announcing all published data that meets the criteria contained in the subscription request. 108 108 109 -== 3.5 Discovery == 110 +=== {{id name="_Toc90787"/}}3.5 Discovery === 110 110 111 111 Discovering published data and reference metadata involves interaction with the registry to fulfil the following logical steps that would be carried out by a user interacting with a service that itself interacts with the registry and an SDMX-enabled data or reference metadata resource: 112 112 ... ... @@ -118,9 +118,9 @@ 118 118 119 119 **Figure 3: Schematic of Data and Metadata Discovery and Query in the SDMX-IM** 120 120 121 -= 4 SDMX Registry/Repository Architecture = 122 += {{id name="_Toc90788"/}}4 SDMX Registry/Repository Architecture = 122 122 123 -== 4.1 Architectural Schematic == 124 +=== {{id name="_Toc90789"/}}4.1 Architectural Schematic === 124 124 125 125 The architecture of the SDMX registry/repository is derived from the objectives stated above. It is a layered architecture that is founded by a structural metadata repository which supports a provisioning metadata repository which supports the registry services. These are all supported by the SDMX-ML schemas. Applications can be built on top of these services which support the reporting, storage, retrieval, and dissemination aspects of the statistical lifecycle as well as the maintenance of the structural metadata required to drive these applications. 126 126 ... ... @@ -128,7 +128,7 @@ 128 128 129 129 **Figure 4: Schematic of the Registry Content and Services** 130 130 131 -== 4.2 Structural Metadata Repository == 132 +=== {{id name="_Toc90790"/}}4.2 Structural Metadata Repository === 132 132 133 133 The basic layer is that of a structural metadata service which supports the lifecycle of SDMX structural metadata artefacts such as Maintenance Agencies, Data Structure Definitions, Metadata Structure Definitions, Provision Agreements, Processes etc. This layer is supported by the Structure Submission and Query Service. 134 134 ... ... @@ -139,15 +139,15 @@ 139 139 140 140 As of the initial version of SDMX 3.0 no messages are defined to support these artefacts; hence, users may need to use SDMX 2.1 Registry Interface messages, instead. 141 141 142 -== 4.3 Provisioning Metadata Repository == 143 +=== {{id name="_Toc90791"/}}4.3 Provisioning Metadata Repository === 143 143 144 144 The function of this repository is to support the definition of the structural metadata that describes the various types of data-store which model SDMX-conformant databases or files, and to link to these data sources. These links can be specified for a data/metadata provider, for a specific data or metadata flow. In the SDMX model this is called the Provision or Metadata Provision Agreement. 145 145 146 146 This layer is supported by the Data and Metadata Registration Service. 147 147 148 -= 5 Registry Interfaces and Services = 149 += {{id name="_Toc90792"/}}5 Registry Interfaces and Services = 149 149 150 -== 5.1 Registry Interfaces == 151 +=== {{id name="_Toc90793"/}}5.1 Registry Interfaces === 151 151 152 152 The Registry Interfaces are: 153 153 ... ... @@ -173,17 +173,17 @@ 173 173 174 174 It should be noted that all interactions are assumed to be synchronous, with the exception of Notify Registry Event. This document is sent by the SDMX-RR to all subscribers whenever an even occurs to which any users have subscribed. Thus, it does not conform to the requestresponse pattern, because it is inherently asynchronous. 175 175 176 -== 5.2 Registry Services == 177 +=== {{id name="_Toc90794"/}}5.2 Registry Services === 177 177 178 -=== 5.2.1 Introduction === 179 +===== {{id name="_Toc90795"/}}5.2.1 Introduction ===== 179 179 180 180 The services described in this section do not imply that each is implemented as a discrete web service. 181 181 182 -=== 5.2.2 Structure Submission Service === 183 +===== {{id name="_Toc90796"/}}5.2.2 Structure Submission Service ===== 183 183 184 184 The registry must support a mechanism for submitting structural metadata. This mechanism can be the SDMX REST interface for structural metadata (this is defined in the corresponding GitHub project, dedicated to the SDMX REST API: __[[https:~~/~~/github.com/sdmx>>url:https://github.com/sdmx-twg/sdmx-rest]][[->>url:https://github.com/sdmx-twg/sdmx-rest]][[twg/sdmx>>url:https://github.com/sdmx-twg/sdmx-rest]][[->>url:https://github.com/sdmx-twg/sdmx-rest]][[rest>>url:https://github.com/sdmx-twg/sdmx-rest]]__[[)>>url:https://github.com/sdmx-twg/sdmx-rest]]. In order for the architecture to be scalable, the finest-grained piece of structural metadata that can be processed by the SDMX-RR is a MaintainableArtefact, with the exception of Item Schemes, where changes at an Item level is also possible (see next section on the SDMX Information Model). 185 185 186 -=== 5.2.3 Structure Query Service === 187 +===== {{id name="_Toc90797"/}}5.2.3 Structure Query Service ===== 187 187 188 188 The registry must support a mechanism for querying for structural metadata. This mechanism can be the SDMX REST interface for structural metadata (this is defined in the corresponding GitHub project, dedicated to the SDMX REST API: __[[https:~~/~~/github.com/sdmx>>url:https://github.com/sdmx-twg/sdmx-rest]][[->>url:https://github.com/sdmx-twg/sdmx-rest]][[twg/sdmx>>url:https://github.com/sdmx-twg/sdmx-rest]][[->>url:https://github.com/sdmx-twg/sdmx-rest]][[rest>>url:https://github.com/sdmx-twg/sdmx-rest]]__[[)>>url:https://github.com/sdmx-twg/sdmx-rest]]. The registry response to this query mechanism is the SDMX Structure message, which has as its root node: 189 189 ... ... @@ -191,7 +191,7 @@ 191 191 192 192 The SDMX structural artefacts that may be queried are defined in the SDMX structure web service specification which is compatible with this release of the standard __[[https:~~/~~/github.com/sdmx>>url:https://github.com/sdmx-twg/sdmx-rest/blob/master/doc/structures.md]][[->>url:https://github.com/sdmx-twg/sdmx-rest/blob/master/doc/structures.md]][[twg/sdmx>>url:https://github.com/sdmx-twg/sdmx-rest/blob/master/doc/structures.md]][[->>url:https://github.com/sdmx-twg/sdmx-rest/blob/master/doc/structures.md]][[rest/blob/master/doc/structures.md>>url:https://github.com/sdmx-twg/sdmx-rest/blob/master/doc/structures.md]]__[[url:https://github.com/sdmx-twg/sdmx-rest/blob/master/doc/structures.md]] 193 193 194 -=== 5.2.4 Data and Reference Metadata Registration Service === 195 +===== {{id name="_Toc90798"/}}5.2.4 Data and Reference Metadata Registration Service ===== 195 195 196 196 This service must implement the following Registry Interfaces: 197 197 ... ... @@ -214,22 +214,21 @@ 214 214 215 215 The Registration has an action attribute which takes one of the following values: 216 216 217 -(% style="width:893.835px" %) 218 -|(% style="width:241px" %)**Action Attribute Value**|(% style="width:650px" %)**Behaviour** 219 -|(% style="width:241px" %)Append|(% style="width:650px" %)Add this registration to the registry 220 -|(% style="width:241px" %)Replace|(% style="width:650px" %)Replace the existing Registration with this Registration identified by the id in the Registration of the Submit Registration Request 221 -|(% style="width:241px" %)Delete|(% style="width:650px" %)Delete the existing Registration identified by the id in the Registration of the Submit Registration Request 218 +|**Action Attribute Value**|**Behaviour** 219 +|Append|Add this registration to the registry 220 +|Replace|Replace the existing Registration with this Registration identified by the id in the Registration of the Submit Registration Request 221 +|Delete|Delete the existing Registration identified by the id in the Registration of the Submit Registration Request 222 222 223 223 The Registration has three Boolean attributes which may be present to determine how an SDMX compliant dataset or metadataset indexing application must index the datasets or metadatasets upon registration. The indexing application behaviour is as follows: 224 224 225 -(% style="width:896.835px" %) 226 -|**Boolean Attribute**|(% style="width:712px" %)**Behaviour if Value is “true”** 227 -|indexTimeSeries|(% style="width:712px" %)A compliant indexing application must index all the time series keys 228 -|indexDataSet|(% style="width:712px" %)((( 225 +|**Boolean Attribute**|**Behaviour if Value is “true”** 226 +|indexTimeSeries|A compliant indexing application must index all the time series keys 227 +|indexDataSet|((( 229 229 A compliant indexing application must index the range of actual (present) values for each dimension of the Dataset. 229 + 230 230 Note that for data this requires much less storage than full key indexing, but this method cannot guarantee that a specific combination of Dimension values (the Key) is actually present in the Dataset 231 231 ))) 232 -|indexReportingPeriod| (% style="width:712px" %)A compliant indexing application must index the time period range(s) for which data are present in the Dataset.232 +|indexReportingPeriod|A compliant indexing application must index the time period range(s) for which data are present in the Dataset. 233 233 234 234 ===== {{id name="_Toc90799"/}}5.2.5 Data Discovery ===== 235 235 ... ... @@ -271,7 +271,7 @@ 271 271 272 272 1. Be a draft version. 273 273 274 -b) Not be explicitly^^[[ (% class="wikiinternallink wikiinternallink" %)^^1^^>>path:#sdfootnote1sym||name="sdfootnote1anc"]](%%)^^ referenced from any other object in the Registry.274 +b) Not be explicitly^^[[^^1^^>>path:#sdfootnote1sym||name="sdfootnote1anc"]]^^ referenced from any other object in the Registry. 275 275 276 276 4) The semantic versioning rules in the SDMX documentation MUST be obeyed. 277 277 ))) ... ... @@ -309,47 +309,47 @@ 309 309 310 310 • //Maintainable// 311 311 312 -| 313 -| 314 -| 315 -| 316 -| 312 +||(% colspan="2" %)**Object Type**|(% colspan="2" %)**Data Attributes**|(% colspan="2" %)**Status**|(% colspan="2" %)**Data type**|(% colspan="2" %)**Notes** 313 +||(% colspan="2" rowspan="4" %)//Annotable//|(% colspan="2" %)AnnotationTitle|(% colspan="2" %)C|(% colspan="2" %)string|(% colspan="2" %) 314 +||(% colspan="2" %)AnnotationType|(% colspan="2" %)C|(% colspan="2" %)string|(% colspan="2" %) 315 +||(% colspan="2" %)AnnotationURN|(% colspan="2" %)C|(% colspan="2" %)string|(% colspan="2" %) 316 +||(% colspan="2" %)((( 317 317 AnnotationText in the form of 318 318 319 319 InternationalString 320 -)))|(% colspan="2" %)C|(% colspan="2" %) 321 -| 322 -| 323 -| 324 -| 325 -| 320 +)))|(% colspan="2" %)C|(% colspan="2" %)|(% colspan="2" %)This can have languagespecific variants 321 +||(% colspan="2" rowspan="4" %)//Identifiable//|(% colspan="2" %)All content as for //Annotable// plus|(% colspan="2" %)|(% colspan="2" %)|(% colspan="2" %) 322 +||(% colspan="2" %)id|(% colspan="2" %)M|(% colspan="2" %)string|(% colspan="2" %) 323 +||(% colspan="2" %)uri|(% colspan="2" %)C|(% colspan="2" %)string|(% colspan="2" %) 324 +||(% colspan="2" %)urn|(% colspan="2" %)C|(% colspan="2" %)string|(% colspan="2" %)Although the urn is computable and therefore may not be submitted or stored physically, the Registry must return the urn for each object, and must be able to service a query on an object referenced solely by its urn. 325 +||(% colspan="2" rowspan="3" %)//Nameable//|(% colspan="2" %)((( 326 326 All content as for 327 327 328 328 //Identifiable// plus 329 -)))|(% colspan="2" %) 330 -| 329 +)))|(% colspan="2" %)|(% colspan="2" %)|(% colspan="2" %) 330 +||(% colspan="2" %)((( 331 331 Name in the form of 332 332 333 333 InternationalString 334 334 )))|(% colspan="2" %)M|(% colspan="2" %)string|(% colspan="2" %)This can have language specific variants. 335 -| 335 +||(% colspan="2" %)((( 336 336 Description in the form of 337 337 338 338 InternationalString 339 339 )))|(% colspan="2" %)C|(% colspan="2" %)string|(% colspan="2" %)This can have language specific variants. 340 -| 340 +||(% colspan="2" rowspan="4" %)//Versionable//|(% colspan="2" %)((( 341 341 All content as for 342 342 343 343 //Identifiable// plus 344 -)))|(% colspan="2" %) 345 -| 346 -| 347 -| 348 -|(% colspan="2" rowspan="5" %)//Maintainable//|(% colspan="2" %)All content as for //Versionable// plus|(% colspan="2" %) 349 -|(% colspan="2" %)isExternalReference|(% colspan="2" %)C|(% colspan="2" %)boolean|(% colspan="2" %)Value of “true” indicates that the actual resource is held outside of this registry. The actual reference is given in the registry URI or the structureURL, each of which must return a valid SDMX-ML file.| 350 -|(% colspan="2" %)serviceURL|(% colspan="2" %)C|(% colspan="2" %)string|(% colspan="2" %)The url of the service that can be queried for this resource.| 351 -|(% colspan="2" %)structureURL|(% colspan="2" %)C|(% colspan="2" %)string|(% colspan="2" %)The url of the resource.| 352 -|(% colspan="2" %)(Maintenance) organisationId|(% colspan="2" %)M|(% colspan="2" %)string|(% colspan="2" %)The object must be linked to a maintenance organisation, i.e., Agency or Metadata Provider.| 344 +)))|(% colspan="2" %)|(% colspan="2" %)|(% colspan="2" %) 345 +||(% colspan="2" %)version|(% colspan="2" %)M|(% colspan="2" %)string|(% colspan="2" %)This is the version number according to SDMX versioning rules. 346 +||(% colspan="2" %)validFrom|(% colspan="2" %)C|(% colspan="2" %)Date/time|(% colspan="2" %) 347 +||(% colspan="2" %)validTo|(% colspan="2" %)C|(% colspan="2" %)Date/time|(% colspan="2" %) 348 +|(% colspan="2" rowspan="5" %)//Maintainable//|(% colspan="2" %)All content as for //Versionable// plus|(% colspan="2" %)|(% colspan="2" %)|(% colspan="2" %)| 349 +|(% colspan="2" %)isExternalReference|(% colspan="2" %)C|(% colspan="2" %)boolean|(% colspan="2" %)Value of “true” indicates that the actual resource is held outside of this registry. The actual reference is given in the registry URI or the structureURL, each of which must return a valid SDMX-ML file.| 350 +|(% colspan="2" %)serviceURL|(% colspan="2" %)C|(% colspan="2" %)string|(% colspan="2" %)The url of the service that can be queried for this resource.| 351 +|(% colspan="2" %)structureURL|(% colspan="2" %)C|(% colspan="2" %)string|(% colspan="2" %)The url of the resource.| 352 +|(% colspan="2" %)(Maintenance) organisationId|(% colspan="2" %)M|(% colspan="2" %)string|(% colspan="2" %)The object must be linked to a maintenance organisation, i.e., Agency or Metadata Provider.| 353 353 354 354 **Table 1: Common Attributes of Object Types** 355 355 ... ... @@ -511,92 +511,92 @@ 511 511 512 512 |**Package**|**URN class name (model class name where this is different)** 513 513 |base|Agency 514 -| 515 -| 516 -| 517 -| 518 -| 519 -| 520 -| 521 -| 522 -| 523 -| 514 +||AgencyScheme 515 +||DataConsumer 516 +||DataConsumerScheme 517 +||DataProvider 518 +||DataProviderScheme 519 +||MetadataProvider 520 +||MetadataProviderScheme 521 +||OrganisationUnit 522 +||OrganisationUnitScheme 523 +|| 524 524 |datastructure|AttributeDescriptor 525 -| 526 -| 527 -| 528 -| 529 -| 530 -| 531 -| 532 -| 533 -| 534 -| 525 +||DataAttribute 526 +||Dataflow 527 +||DataStructure (DataStructureDefinition) 528 +||Dimension 529 +||DimensionDescriptor 530 +||GroupDimensionDescriptor 531 +||Measure 532 +||MeasureDescriptor 533 +||TimeDimension 534 +|| 535 535 |metadatastructure|MetadataAttribute 536 -| 537 -| 536 +||MetadataAttributeDescriptor 537 +||((( 538 538 MetadataStructure 539 539 540 540 (MetadataStructureDefinition) 541 541 ))) 542 542 543 -: 543 +: 544 544 545 545 ((( 546 546 |**Package**|**URN class name (model class name where this is different)** 547 -| 548 -| 549 -| 547 +||Metadataflow 548 +||MetadataSet 549 +|| 550 550 |process|Process 551 -| 552 -| 553 -| 551 +||ProcessStep 552 +||Transition 553 +|| 554 554 |registry|DataConstraint 555 -| 556 -| 557 -| 558 -| 559 -| 555 +||MetadataConstraint 556 +||MetadataProvisionAgreement 557 +||ProvisionAgreement 558 +||Subscription 559 +|| 560 560 |structuremapping|CategorySchemeMap 561 -| 562 -| 563 -| 564 -| 565 -| 566 -| 561 +||ConceptSchemeMap 562 +||OrganisationSchemeMap 563 +||ReportingTaxonomyMap 564 +||RepresentationMap 565 +||StructureMap 566 +|| 567 567 |codelist|Code 568 -| 569 -| 570 -| 571 -| 572 -| 573 -| 574 -| 568 +||Codelist 569 +||HierarchicalCode 570 +||Hierarchy 571 +||HierarchyAssociation 572 +||Level 573 +||ValueList 574 +|| 575 575 |categoryscheme|Categorisation 576 -| 577 -| 578 -| 579 -| 576 +||Category 577 +||CategoryScheme 578 +||ReportingCategory 579 +||ReportingTaxonomy 580 580 |**Package**|**URN class name (model class name where this is different)** 581 -| 581 +|| 582 582 |conceptscheme|Concept 583 -| 584 -| 583 +||ConceptScheme 584 +|| 585 585 |transformation|CustomType 586 -| 587 -| 588 -| 589 -| 590 -| 591 -| 592 -| 593 -| 594 -| 595 -| 596 -| 597 -| 598 -| 599 -| 586 +||CustomTypeScheme 587 +||NamePersonalisation 588 +||NamePersonalisationScheme 589 +||Ruleset 590 +||RulesetScheme 591 +||Transformation 592 +||TransformationScheme 593 +||UserDefinedOperator 594 +||UserDefinedOperatorScheme 595 +||VtlCodelistMapping 596 +||VtlConceptMapping 597 +||VtlDataflowMapping 598 +||VtlMappingScheme 599 +|| 600 600 ))) 601 601 602 602 **Table 2: SDMX-IM Packages and Contained Classes** ... ... @@ -610,7 +610,7 @@ 610 610 urn:sdmx.org.sdmx.infomodel.{package}.{classname}= 611 611 612 612 |**Classname**|**Ending URN pattern**|**Example** 613 -|Agency^^[[ (% class="wikiinternallink wikiinternallink" %)^^2^^>>path:#sdfootnote2sym||name="sdfootnote2anc"]](%%)^^|agencySchemeAgencyId:**AGENCIES**(**1.0**).agencyId|ECB:**AGENCIES**(**1.0**).AA613 +|Agency^^[[^^2^^>>path:#sdfootnote2sym||name="sdfootnote2anc"]]^^|agencySchemeAgencyId:**AGENCIES**(**1.0**).agencyId|ECB:**AGENCIES**(**1.0**).AA 614 614 |//AgencyScheme//|agencySchemeAgencyId:**AGENCIES**(**1.0**)|ECB:**AGENCIES**(**1.0**) 615 615 |//Categorisation//|categorisationAgencyId:categorisationId(version)|IMF:cat001(1.0.0) 616 616 |Category|categorySchemeAgencyId:categorySchemeId(versi on).categoryId.categoryId.categoryId etc.|IMF:SDDS(1.0.0):level_1_category.level_2_category … ... ... @@ -769,22 +769,22 @@ 769 769 The following table lists the Maintainable Artefacts. 770 770 771 771 |(% colspan="2" %)**Maintainable Artefacts**|**Content** 772 -|**Abstract Class**|**Concrete Class**| 772 +|**Abstract Class**|**Concrete Class**| 773 773 |Item Scheme|Codelist|Code 774 -| 775 -| 776 -| 777 -| 778 -| 779 -| 780 -| 781 -| 782 -| 783 -| 784 -| 785 -| 786 -| 787 -| 774 +||Concept Scheme|Concept 775 +||Category Scheme|Category 776 +||Organisation Unit Scheme|Organisation Unit 777 +||Agency Scheme|Agency 778 +||Data Provider Scheme|Data Provider 779 +||Metadata Provider Scheme|Metadata Provider 780 +||Data Consumer Scheme|Data Consumer 781 +||Reporting Taxonomy|Reporting Category 782 +||Transformation Scheme|Transformation 783 +||Custom Type Scheme|Custom Type 784 +||Name Personalisation Scheme|Name Personalisation 785 +||Vtl Mapping Scheme|Vtl Codelist Mapping Vtl Concept Mapping 786 +||Ruleset Scheme|Ruleset 787 +||User Defined Operator Scheme|User Defined Operator 788 788 |Enumerated List|ValueList|Value Item 789 789 |Structure|Data Structure Definition|((( 790 790 Dimension Descriptor ... ... @@ -803,9 +803,9 @@ 803 803 804 804 Measure 805 805 ))) 806 -| 807 -|Structure Usage|Dataflow| 808 -| 806 +||Metadata Structure Definition|Metadata Attribute Descriptor Metadata Attribute 807 +|Structure Usage|Dataflow| 808 +||Metadataflow| 809 809 |None|Process|Process Step 810 810 |None|Structure Map|((( 811 811 Component Map ... ... @@ -816,16 +816,16 @@ 816 816 ))) 817 817 |None|Representation Map|Representation Mapping 818 818 |Item Scheme Map|Organisation Scheme Map|Item Map 819 -| 820 -| 821 -| 822 -|None|Provision Agreement| 823 -|None|Metadata Provision Agreement| 819 +||Concept Scheme Map|Item Map 820 +||Category Scheme Map|Item Map 821 +||Reporting Taxonomy Map|Item Map 822 +|None|Provision Agreement| 823 +|None|Metadata Provision Agreement| 824 824 |None|Hierarchy|Hierarchical Code 825 -|None|Hierarchy Association| 826 -|None|Categorisation| 825 +|None|Hierarchy Association| 826 +|None|Categorisation| 827 827 |Constraint|Data Constraint|DataKeySet 828 -| 828 +|||CubeRegion 829 829 |Constraint|Metadata Constraint|MetadataTargetRegion 830 830 831 831 **Table 4: Table of Maintainable Artefacts for Structural Definition Metadata** ... ... @@ -835,7 +835,7 @@ 835 835 The artefacts included in the structural definitions are: 836 836 837 837 * All types of Item Scheme (Codelist, Concept Scheme, Category Scheme, Organisation Scheme, Agency Scheme, Data Provider Scheme, Metadata Provider Scheme, Data Consumer Scheme, Organisation Unit Scheme, Transformation Scheme, Name Personalisation Scheme, Custom Type Scheme, Vtl Mapping Scheme, Ruleset Scheme, User Defined Operator Scheme) 838 -* All types of Enumerated List (ValueList)^^[[ (% class="wikiinternallink wikiinternallink" %)^^3^^>>path:#sdfootnote3sym||name="sdfootnote3anc"]](%%)^^838 +* All types of Enumerated List (ValueList)^^[[^^3^^>>path:#sdfootnote3sym||name="sdfootnote3anc"]]^^ 839 839 * All types of Structure (Data Structure Definition, Metadata Structure Definition) 840 840 * All types of Structure Usage (Dataflow, Metadataflow) 841 841 ... ... @@ -971,7 +971,7 @@ 971 971 972 972 The Registration has an action attribute which takes one of the following values: 973 973 974 -: 974 +: 975 975 976 976 ((( 977 977 |**Action Attribute Value**|**Behaviour** ... ... @@ -996,7 +996,7 @@ 996 996 997 997 https:~/~/github.com/sdmx-twg/sdmx-rest/blob/master/doc/availability.md 998 998 999 -: 999 +: 1000 1000 1001 1001 ((( 1002 1002 |**Indexing Required**|**Registration Process Activity** ... ... @@ -1019,7 +1019,7 @@ 1019 1019 Components of the Constraints model in the 1020 1020 ))) 1021 1021 |**Indexing Required**|**Registration Process Activity** 1022 -| 1022 +||SDMX-IM. Note that the content is not stored in the Selection Value. 1023 1023 ))) 1024 1024 1025 1025 Constraints that specify the contents of a //QueryDatasource// are submitted to the Registry via the structure submission service (i.e., the RESTful API). ... ... @@ -1062,7 +1062,7 @@ 1062 1062 1. A selector which specifies which type of events are of interest. The set of event types is: 1063 1063 1064 1064 : 1065 -:: 1065 +:: 1066 1066 1067 1067 ((( 1068 1068 |**Event Type**|**Comment** ... ... @@ -1136,7 +1136,7 @@ 1136 1136 1137 1137 Whenever a dataset or metadata-set is registered a registration event is created. A subscription may be observing all data or metadata registrations, or it may focus on specific registrations as shown in the table below: 1138 1138 1139 -: 1139 +: 1140 1140 1141 1141 ((( 1142 1142 |**Selector**|**Comment**