Skip to Content
Last modified by Helena on 2025/09/10 11:19
From version 17.1
edited by Helena
on 2025/05/15 14:05
Change comment: There is no comment for this version
To version 21.6
edited by Helena
on 2025/05/15 14:12
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -1 Introduction
1 +SDMX STANDARDS: SECTION 5
Content
... ... @@ -1,14 +1,17 @@
1 -**Revision History**
1 +{{box title="**Contents**"}}
2 +{{toc/}}
3 +{{/box}}
2 2  
3 -:
5 += Revision History =
4 4  
5 5  (((
6 -|**Revision**|**Date**|**Contents**
7 -|DRAFT 1.0|May 2021|Draft release updated for SDMX 3.0 for public consultation
8 -|1.0|October 2021|Public release for SDMX 3.0
8 +(% style="width:838.294px" %)
9 +|(% style="width:188px" %)**Revision**|(% style="width:205px" %)**Date**|(% style="width:441px" %)**Contents**
10 +|(% style="width:188px" %)DRAFT 1.0|(% style="width:205px" %)May 2021|(% style="width:441px" %)Draft release updated for SDMX 3.0 for public consultation
11 +|(% style="width:188px" %)1.0|(% style="width:205px" %)October 2021|(% style="width:441px" %)Public release for SDMX 3.0
9 9  )))
10 10  
11 -= {{id name="_Toc93831"/}}1 Introduction =
14 += 1 Introduction =
12 12  
13 13  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:
14 14  
... ... @@ -30,12 +30,10 @@
30 30  
31 31  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:
32 32  
33 -• structural metadata repository
36 +* structural metadata repository
37 +* data and metadata registration
38 +* query
34 34  
35 -• data and metadata registration
36 -
37 -• query
38 -
39 39  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.
40 40  
41 41  = {{id name="_Toc93832"/}}2 Scope and Normative Status =
... ... @@ -78,7 +78,8 @@
78 78  
79 79  [[image:SDMX 3-0-0 SECTION 5 FINAL-1.0_en_28806f51.jpg||height="539" width="443"]]
80 80  
81 -====== Figure 1: Schematic of the Basic Structural Artefacts in the SDMX-IM ======
82 +(% class="wikigeneratedid" id="HFigure1:SchematicoftheBasicStructuralArtefactsintheSDMX-IM" %)
83 +**Figure 1: Schematic of the Basic Structural Artefacts in the SDMX-IM**
82 82  
83 83  Note that in Figure 1 (but also most of the relevant subsequent figures) terms that include both data and metadata have been used. For example:
84 84  
... ... @@ -105,7 +105,7 @@
105 105  
106 106  Notifying interested parties of newly published or re-published data, reference metadata or changes in structural metadata involves:
107 107  
108 -• 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.
110 +* 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.
109 109  
110 110  == {{id name="_Toc93838"/}}3.5 Discovery ==
111 111  
... ... @@ -164,9 +164,8 @@
164 164  
165 165  The registry interfaces are invoked in one of two ways:
166 166  
167 -*
168 -*1. The interface is the name of the root node of the SDMX-ML document
169 -*1. The interface is invoked as a child element of the RegistryInterface message where the RegistryInterface is the root node of the SDMX-ML document.
169 +1. The interface is the name of the root node of the SDMX-ML document
170 +1. The interface is invoked as a child element of the RegistryInterface message where the RegistryInterface is the root node of the SDMX-ML document.
170 170  
171 171  In addition to these interfaces the registry must support a mechanism for submitting and querying for structural metadata. This is detailed in sections 5.2.2 and 5.2.3.
172 172  
... ... @@ -242,23 +242,22 @@
242 242  * that the components (Dimensions, Attributes, Measures, Metadata Attributes, etc.) are consistent with the Data Structure Definition or Metadata Structure Definition;
243 243  * that the valid representations of the concepts to which these components correspond conform to the definition in the Data Structure Definition or Metadata Structure Definition. The Registration has an action attribute which takes one of the following values:
244 244  
245 -|**Action Attribute Value**|**Behaviour**
246 -|Append|Add this registration to the registry
247 -|Replace|Replace the existing Registration with this Registration identified by the id in the Registration of the Submit Registration Request
248 -|Delete|Delete the existing Registration identified by the id in the Registration of the Submit Registration Request
246 +(% style="width:755.294px" %)
247 +|(% style="width:187px" %)**Action Attribute Value**|(% style="width:566px" %)**Behaviour**
248 +|(% style="width:187px" %)Append|(% style="width:566px" %)Add this registration to the registry
249 +|(% style="width:187px" %)Replace|(% style="width:566px" %)Replace the existing Registration with this Registration identified by the id in the Registration of the Submit Registration Request
250 +|(% style="width:187px" %)Delete|(% style="width:566px" %)Delete the existing Registration identified by the id in the Registration of the Submit Registration Request
249 249  
250 250  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:
251 251  
252 -|**Boolean Attribute**|**Behaviour if Value is “true”**
253 -|indexTimeSeries|A compliant indexing application must index all the time series keys (for a Dataset registration) or metadata target values (for a Metadataset registration)
254 -|indexDataSet|(((
255 -A compliant indexing application must index the range of actual
256 -
257 -(present) values for each dimension of the Dataset (for a Dataset registration) or the range of actual (present) values for each Metadata Attribute which takes an enumerated value.
258 -
254 +(% style="width:759.294px" %)
255 +|(% style="width:191px" %)**Boolean Attribute**|(% style="width:565px" %)**Behaviour if Value is “true”**
256 +|(% style="width:191px" %)indexTimeSeries|(% style="width:565px" %)A compliant indexing application must index all the time series keys (for a Dataset registration) or metadata target values (for a Metadataset registration)
257 +|(% style="width:191px" %)indexDataSet|(% style="width:565px" %)(((
258 +A compliant indexing application must index the range of actual (present) values for each dimension of the Dataset (for a Dataset registration) or the range of actual (present) values for each Metadata Attribute which takes an enumerated value.
259 259  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
260 260  )))
261 -|indexReportingPeriod|A compliant indexing application must index the time period range(s) for which data are present in the Dataset. The validity period of the Metadatasets may also be indexed.
261 +|(% style="width:191px" %)indexReportingPeriod|(% style="width:565px" %)A compliant indexing application must index the time period range(s) for which data are present in the Dataset. The validity period of the Metadatasets may also be indexed.
262 262  
263 263  === {{id name="_Toc93850"/}}5.2.5 Data and Reference Metadata Discovery ===
264 264  
... ... @@ -292,8 +292,9 @@
292 292  
293 293  Given the above, the behaviour described in the following table concerns either draft Artefacts using semantic versioning or any Artefacts using the old versioning scheme. Nevertheless, in the case of semantic versioning the registry must respect the versioning rules when performing the actions below. For example, it is not possible to replace a non-draft Artefact that follows semantic versioning, unless a newer version is introduced according to the semantic versioning rules. Furthermore, even when draft Artefacts are submitted, the registry has to verify semantic versioning is respected against the previous non-draft versions. It is worth noting that the rules for semantic versioning and replacing or maintaining semantically versioned Artefacts applies to externally shared Artefacts. This means that any system may internally perform any change within a version of an Artefact, until the latter is shared outside of that system or becomes public. Then (as also explained in the SDMX Standards Section 6 “Technical Notes”) the Artefacts must adhere to the Semantic Versioning rules.
294 294  
295 -|**Interface**|**Behaviour**
296 -|All|(((
295 +(% style="width:757.294px" %)
296 +|(% style="width:188px" %)**Interface**|(% style="width:542px" %)**Behaviour**
297 +|(% style="width:188px" %)All|(% style="width:542px" %)(((
297 297  1. If the action is set to “replace” (or a maintainable Artefact is PUT or POSTed) then the entire contents of the existing maintainable object in the Registry MUST be replaced by the object submitted.
298 298  1. Cross referenced structures MUST exist in either the submitted document (in Structures or Structure Location) or in the registry to which the request is submitted.
299 299  1. If the action is set to “delete” (or a maintainable Artefact is DELETEd) then the Registry MUST verify that the object can be deleted. In order to qualify for deletion, the object must:
... ... @@ -300,14 +300,14 @@
300 300  
301 301  a) Be a draft version.
302 302  )))
303 -|**Interface**|**Behaviour**
304 -||(((
305 -b) Not be explicitly^^[[^^1^^>>path:#sdfootnote1sym||name="sdfootnote1anc"]]^^ referenced from any other object in the Registry.
304 +|(% style="width:188px" %)**Interface**|(% style="width:542px" %)**Behaviour**
305 +|(% style="width:188px" %) |(% style="width:542px" %)(((
306 +b) Not be explicitly{{footnote}}With semantic versioning, it is allowed to reference a range of artefacts, e.g., a DSD referencing a Codelist with version 1.2.3+ means all patch versions greater than 1.2.3. This means that deleting 1.2.4-draft does not break integrity of the aforementioned DSD.{{/footnote}} referenced from any other object in the Registry.
306 306  
307 307  4) The semantic versioning rules in the SDMX documentation MUST be obeyed.
308 308  )))
309 -|Structure submission|Structures are submitted at the level of the Maintainable Artefact and the behaviour in “All” above is therefore at the level of the Maintainable Artefact.
310 -|SubmitRegistrationRequest|If the datasource is a file (simple datasource) then the file MAY be retrieved and indexed according to the Boolean attributes set in the Registration. For a queryable datasource the Registry MAY validate that the source exists and can accept an SDMX data query.
310 +|(% style="width:188px" %)Structure submission|(% style="width:542px" %)Structures are submitted at the level of the Maintainable Artefact and the behaviour in “All” above is therefore at the level of the Maintainable Artefact.
311 +|(% style="width:188px" %)SubmitRegistrationRequest|(% style="width:542px" %)If the datasource is a file (simple datasource) then the file MAY be retrieved and indexed according to the Boolean attributes set in the Registration. For a queryable datasource the Registry MAY validate that the source exists and can accept an SDMX data query.
311 311  
312 312  = {{id name="_Toc93853"/}}6 Identification of SDMX Objects =
313 313  
... ... @@ -334,30 +334,31 @@
334 334  * //Versionable//
335 335  * //Maintainable//
336 336  
337 -:
338 +:
338 338  
339 339  (((
340 -|**Object Type**|**Data Attributes**|**Status**|**Data type**|**Notes**
341 -|(% rowspan="4" %)//Annotable//|AnnotationTitle|C|string|
342 -|AnnotationType|C|string|
343 -|AnnotationURN|C|string|
344 -|AnnotationText in the form of InternationalString|C||This can have languagespecific variants
345 -|(% rowspan="4" %)//Identifiable//|All content as for //Annotable// plus|||
346 -|id|M|string|
347 -|uri|C|string|
348 -|urn|C|string|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.
349 -|(% rowspan="3" %)//Nameable//|All content as for //Identifiable// plus|||
350 -|Name in the form of InternationalString|M|string|This can have language specific variants.
351 -|Description in the form of InternationalString|C|string|This can have language specific variants.
352 -|(% rowspan="4" %)//Versionable//|All content as for //Identifiable// plus|||
353 -|version|M|string|This is the version number according to SDMX versioning rules.
354 -|validFrom|C|Date/time|
355 -|validTo|C|Date/time|
356 -|//Maintainable//|All content as for //Versionable// plus|||
357 -||isExternalReference|C|boolean|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.
358 -|\\|serviceURL|C|string|The url of the service that can be queried for this resource.
359 -||structureURL|C|string|The url of the resource.
360 -||(Maintenance) organisationId|M|string|The object must be linked to a maintenance organisation, i.e., Agency or Metadata Provider.
341 +(% style="width:1052.29px" %)
342 +|**Object Type**|(% style="width:241px" %)**Data Attributes**|(% style="width:156px" %)**Status**|**Data type**|(% style="width:457px" %)**Notes**
343 +|(% rowspan="4" %)//Annotable//|(% style="width:241px" %)AnnotationTitle|(% style="width:156px" %)C|string|(% style="width:457px" %)
344 +|(% style="width:241px" %)AnnotationType|(% style="width:156px" %)C|string|(% style="width:457px" %)
345 +|(% style="width:241px" %)AnnotationURN|(% style="width:156px" %)C|string|(% style="width:457px" %)
346 +|(% style="width:241px" %)AnnotationText in the form of InternationalString|(% style="width:156px" %)C| |(% style="width:457px" %)This can have languagespecific variants
347 +|(% rowspan="4" %)//Identifiable//|(% style="width:241px" %)All content as for //Annotable// plus|(% style="width:156px" %) | |(% style="width:457px" %)
348 +|(% style="width:241px" %)id|(% style="width:156px" %)M|string|(% style="width:457px" %)
349 +|(% style="width:241px" %)uri|(% style="width:156px" %)C|string|(% style="width:457px" %)
350 +|(% style="width:241px" %)urn|(% style="width:156px" %)C|string|(% style="width:457px" %)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.
351 +|(% rowspan="3" %)//Nameable//|(% style="width:241px" %)All content as for //Identifiable// plus|(% style="width:156px" %) | |(% style="width:457px" %)
352 +|(% style="width:241px" %)Name in the form of InternationalString|(% style="width:156px" %)M|string|(% style="width:457px" %)This can have language specific variants.
353 +|(% style="width:241px" %)Description in the form of InternationalString|(% style="width:156px" %)C|string|(% style="width:457px" %)This can have language specific variants.
354 +|(% rowspan="4" %)//Versionable//|(% style="width:241px" %)All content as for //Identifiable// plus|(% style="width:156px" %) | |(% style="width:457px" %)
355 +|(% style="width:241px" %)version|(% style="width:156px" %)M|string|(% style="width:457px" %)This is the version number according to SDMX versioning rules.
356 +|(% style="width:241px" %)validFrom|(% style="width:156px" %)C|Date/time|(% style="width:457px" %)
357 +|(% style="width:241px" %)validTo|(% style="width:156px" %)C|Date/time|(% style="width:457px" %)
358 +|//Maintainable//|(% style="width:241px" %)All content as for //Versionable// plus|(% style="width:156px" %) | |(% style="width:457px" %)
359 +| |(% style="width:241px" %)isExternalReference|(% style="width:156px" %)C|boolean|(% style="width:457px" %)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.
360 +| |(% style="width:241px" %)serviceURL|(% style="width:156px" %)C|string|(% style="width:457px" %)The url of the service that can be queried for this resource.
361 +| |(% style="width:241px" %)structureURL|(% style="width:156px" %)C|string|(% style="width:457px" %)The url of the resource.
362 +| |(% style="width:241px" %)(Maintenance) organisationId|(% style="width:156px" %)M|string|(% style="width:457px" %)The object must be linked to a maintenance organisation, i.e., Agency or Metadata Provider.
361 361  )))
362 362  
363 363  **Table 1: Common Attributes of Object Types**
... ... @@ -438,13 +438,13 @@
438 438  
439 439  Following the same principles, the Metadata Provider is the maintenance organisation for a special subset of Maintainable Artefacts, i.e., the Metadatasets; the latter are the containers of reference metadata combined with a target that those metadata refer to.
440 440  
441 -===== {{id name="_Toc93858"/}}6.2.2 Universal Resource Name (URN) =====
443 +=== {{id name="_Toc93858"/}}6.2.2 Universal Resource Name (URN) ===
442 442  
443 -**6.2.2.1 Introduction**
445 +==== 6.2.2.1 Introduction ====
444 444  
445 445  To provide interoperability between SDMX Registry/Repositories in a distributed network environment, it is important to have a scheme for uniquely identifying (and thus accessing) all first-class (Identifiable) SDMX-IM objects. Most of these unique identifiers are composite (containing maintenance agency, or parent object identifiers), and there is a need to be able to construct a unique reference as a single string. This is achieved by having a globally unique identifier called a universal resource name (URN) which is generated from the actual identification components in the SDMX-RR APIs. In other words, the URN for any Identifiable Artefact is constructed from its component identifiers (agency, id, version etc.).
446 446  
447 -**6.2.2.2 URN Structure //__Case Rules for URN__//**// //
449 +==== 6.2.2.2 URN Structure //__Case Rules for URN__ // ====
448 448  
449 449  For the URN, all parts of the string are case sensitive. The generic structure of the URN is as follows:
450 450  
... ... @@ -537,79 +537,79 @@
537 537  
538 538  |**Package**|**URN class name (model class name where this is different)**
539 539  |base|Agency
540 -||AgencyScheme
541 -||DataConsumer
542 -||DataConsumerScheme
543 -||DataProvider
544 -||DataProviderScheme
545 -||MetadataProvider
546 -||MetadataProviderScheme
547 -||OrganisationUnit
548 -||OrganisationUnitScheme
542 +| |AgencyScheme
543 +| |DataConsumer
544 +| |DataConsumerScheme
545 +| |DataProvider
546 +| |DataProviderScheme
547 +| |MetadataProvider
548 +| |MetadataProviderScheme
549 +| |OrganisationUnit
550 +| |OrganisationUnitScheme
549 549  |datastructure|AttributeDescriptor
550 -||DataAttribute
551 -||Dataflow
552 -||DataStructure (DataStructureDefinition)
553 -||Dimension
554 -||DimensionDescriptor
555 -||GroupDimensionDescriptor
556 -||Measure
557 -||MeasureDescriptor
558 -||TimeDimension
559 -||
552 +| |DataAttribute
553 +| |Dataflow
554 +| |DataStructure (DataStructureDefinition)
555 +| |Dimension
556 +| |DimensionDescriptor
557 +| |GroupDimensionDescriptor
558 +| |Measure
559 +| |MeasureDescriptor
560 +| |TimeDimension
561 +| |
560 560  |metadatastructure|MetadataAttribute
561 -||MetadataAttributeDescriptor
562 -||MetadataStructure MetadataStructureDefinition)
563 -||Metadataflow
564 -||MetadataSet
565 -||
563 +| |MetadataAttributeDescriptor
564 +| |MetadataStructure MetadataStructureDefinition)
565 +| |Metadataflow
566 +| |MetadataSet
567 +| |
566 566  |process|Process
567 -||ProcessStep
568 -||Transition
569 -||
569 +| |ProcessStep
570 +| |Transition
571 +| |
570 570  |registry|DataConstraint
571 -||MetadataConstraint
572 -||MetadataProvisionAgreement
573 -||ProvisionAgreement
574 -||Subscription
575 -||
573 +| |MetadataConstraint
574 +| |MetadataProvisionAgreement
575 +| |ProvisionAgreement
576 +| |Subscription
577 +| |
576 576  |structuremapping|CategorySchemeMap
577 -||ConceptSchemeMap
578 -||OrganisationSchemeMap
579 -||ReportingTaxonomyMap
580 -||RepresentationMap
581 -||StructureMap
582 -||
579 +| |ConceptSchemeMap
580 +| |OrganisationSchemeMap
581 +| |ReportingTaxonomyMap
582 +| |RepresentationMap
583 +| |StructureMap
584 +| |
583 583  |codelist|Code
584 -||Codelist
585 -||HierarchicalCode
586 -||Hierarchy
587 -||HierarchyAssociation
588 -||Level
589 -||ValueList
590 -||
586 +| |Codelist
587 +| |HierarchicalCode
588 +| |Hierarchy
589 +| |HierarchyAssociation
590 +| |Level
591 +| |ValueList
592 +| |
591 591  |categoryscheme|Categorisation
592 -||Category
593 -||CategoryScheme
594 -||ReportingCategory
595 -||ReportingTaxonomy
594 +| |Category
595 +| |CategoryScheme
596 +| |ReportingCategory
597 +| |ReportingTaxonomy
596 596  |conceptscheme|Concept
597 -||ConceptScheme
598 -||
599 +| |ConceptScheme
600 +| |
599 599  |transformation|CustomType
600 -||CustomTypeScheme
601 -||NamePersonalisation
602 -||NamePersonalisationScheme
603 -||Ruleset
604 -||RulesetScheme
605 -||Transformation
606 -||TransformationScheme
607 -||UserDefinedOperator
608 -||UserDefinedOperatorScheme
609 -||VtlCodelistMapping
610 -||VtlConceptMapping
611 -||VtlDataflowMapping
612 -||VtlMappingScheme
602 +| |CustomTypeScheme
603 +| |NamePersonalisation
604 +| |NamePersonalisationScheme
605 +| |Ruleset
606 +| |RulesetScheme
607 +| |Transformation
608 +| |TransformationScheme
609 +| |UserDefinedOperator
610 +| |UserDefinedOperatorScheme
611 +| |VtlCodelistMapping
612 +| |VtlConceptMapping
613 +| |VtlDataflowMapping
614 +| |VtlMappingScheme
613 613  
614 614  **Table 2: SDMX-IM Packages and Contained Classes**
615 615  
... ... @@ -622,7 +622,7 @@
622 622  urn:sdmx.org.sdmx.infomodel.{package}.{classname}=
623 623  
624 624  |**Classname**|**Ending URN pattern**|**Example**
625 -|Agency^^[[^^2^^>>path:#sdfootnote2sym||name="sdfootnote2anc"]]^^|agencySchemeAgencyId:**AGENCIES**(**1.0**).agencyId|ECB:**AGENCIES**(**1.0**).AA
627 +|Agency^^[[(% class="wikiinternallink wikiinternallink wikiinternallink" %)^^2^^>>path:#sdfootnote2sym||name="sdfootnote2anc"]](%%)^^|agencySchemeAgencyId:**AGENCIES**(**1.0**).agencyId|ECB:**AGENCIES**(**1.0**).AA
626 626  |//AgencyScheme//|agencySchemeAgencyId:**AGENCIES**(**1.0**)|ECB:**AGENCIES**(**1.0**)
627 627  |//Categorisation//|categorisationAgencyId:categorisationId(version)|IMF:cat001(1.0.0)
628 628  |Category|categorySchemeAgencyId:categorySchemeId(versi on).categoryId.categoryId.categoryId etc.|IMF:SDDS(1.0.0):level_1_category.level_2_category …
... ... @@ -775,22 +775,22 @@
775 775  The following table lists the Maintainable Artefacts.
776 776  
777 777  |(% colspan="2" %)**Maintainable Artefacts**|**Content**
778 -|**Abstract Class**|**Concrete Class**|
780 +|**Abstract Class**|**Concrete Class**|
779 779  |Item Scheme|Codelist|Code
780 -||Concept Scheme|Concept
781 -||Category Scheme|Category
782 -||Organisation Unit Scheme|Organisation Unit
783 -||Agency Scheme|Agency
784 -||Data Provider Scheme|Data Provider
785 -||Metadata Provider Scheme|Metadata Provider
786 -||Data Consumer Scheme|Data Consumer
787 -||Reporting Taxonomy|Reporting Category
788 -||Transformation Scheme|Transformation
789 -||Custom Type Scheme|Custom Type
790 -||Name Personalisation Scheme|Name Personalisation
791 -||Vtl Mapping Scheme|Vtl Codelist Mapping Vtl Concept Mapping
792 -||Ruleset Scheme|Ruleset
793 -||User Defined Operator Scheme|User Defined Operator
782 +| |Concept Scheme|Concept
783 +| |Category Scheme|Category
784 +| |Organisation Unit Scheme|Organisation Unit
785 +| |Agency Scheme|Agency
786 +| |Data Provider Scheme|Data Provider
787 +| |Metadata Provider Scheme|Metadata Provider
788 +| |Data Consumer Scheme|Data Consumer
789 +| |Reporting Taxonomy|Reporting Category
790 +| |Transformation Scheme|Transformation
791 +| |Custom Type Scheme|Custom Type
792 +| |Name Personalisation Scheme|Name Personalisation
793 +| |Vtl Mapping Scheme|Vtl Codelist Mapping Vtl Concept Mapping
794 +| |Ruleset Scheme|Ruleset
795 +| |User Defined Operator Scheme|User Defined Operator
794 794  |Enumerated List|ValueList|Value Item
795 795  |Structure|Data Structure Definition|(((
796 796  Dimension Descriptor
... ... @@ -809,9 +809,9 @@
809 809  
810 810  Measure
811 811  )))
812 -||Metadata Structure Definition|Metadata Attribute Descriptor Metadata Attribute
813 -|Structure Usage|Dataflow|
814 -||Metadataflow|
814 +| |Metadata Structure Definition|Metadata Attribute Descriptor Metadata Attribute
815 +|Structure Usage|Dataflow|
816 +| |Metadataflow|
815 815  |None|Process|Process Step
816 816  |None|Structure Map|(((
817 817  Component Map
... ... @@ -822,14 +822,14 @@
822 822  )))
823 823  |None|Representation Map|Representation Mapping
824 824  |Item Scheme Map|Organisation Scheme Map|Item Map
825 -||Concept Scheme Map|Item Map
826 -||Category Scheme Map|Item Map
827 -||Reporting Taxonomy Map|Item Map
828 -|None|Provision Agreement|
829 -|None|Metadata Provision Agreement|
827 +| |Concept Scheme Map|Item Map
828 +| |Category Scheme Map|Item Map
829 +| |Reporting Taxonomy Map|Item Map
830 +|None|Provision Agreement|
831 +|None|Metadata Provision Agreement|
830 830  |None|Hierarchy|Hierarchical Code
831 -|None|Hierarchy Association|
832 -|None|Categorisation|
833 +|None|Hierarchy Association|
834 +|None|Categorisation|
833 833  
834 834  **Table 4: Table of Maintainable Artefacts for Structural Definition Metadata**
835 835  
... ... @@ -839,7 +839,7 @@
839 839  
840 840  • 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)
841 841  
842 -• All types of Enumerated List (ValueList)^^[[^^3^^>>path:#sdfootnote3sym||name="sdfootnote3anc"]]^^
844 +• All types of Enumerated List (ValueList)^^[[(% class="wikiinternallink wikiinternallink wikiinternallink" %)^^3^^>>path:#sdfootnote3sym||name="sdfootnote3anc"]](%%)^^
843 843  
844 844  • All types of Structure (Data Structure Definition, Metadata Structure Definition)
845 845  
... ... @@ -971,7 +971,7 @@
971 971  
972 972  The Registration has an action attribute which takes one of the following values:
973 973  
974 -:
976 +:
975 975  
976 976  (((
977 977  |**Action Attribute Value**|**Behaviour**
... ... @@ -998,7 +998,7 @@
998 998  
999 999  Information in the data or metadata set is extracted and placed in one or more //Constraint//s (see the //Constraint// model in the SDMX Information Model – Section 2 of the SDMX Standards). The information to be extracted is indicated by the Boolean values set on the ProvisionAgreement or MetadataProvisionAgreement as shown in the table below.
1000 1000  
1001 -:
1003 +:
1002 1002  
1003 1003  (((
1004 1004  |**Indexing Required**|**Registration Process Activity**
... ... @@ -1063,7 +1063,7 @@
1063 1063  1. A selector which specifies which type of events are of interest. The set of event types is:
1064 1064  
1065 1065  :
1066 -::
1068 +::
1067 1067  
1068 1068  (((
1069 1069  |**Event Type**|**Comment**
... ... @@ -1137,7 +1137,7 @@
1137 1137  
1138 1138  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:
1139 1139  
1140 -:
1142 +:
1141 1141  
1142 1142  (((
1143 1143  |**Selector**|**Comment**
... ... @@ -1184,3 +1184,5 @@
1184 1184  IMF.SubAgency1
1185 1185  
1186 1186  [[3>>path:#sdfootnote3anc||name="sdfootnote3sym"]] Note that Codelist is also an EnumeratedList.
1189 +
1190 +{{putFootnotes/}}
SDMX 3-0-0 SECTION 5 FINAL-1.0_en_1edb9829.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +50.9 KB
Content
SDMX 3-0-0 SECTION 5 FINAL-1.0_en_8a88db1c.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +184.8 KB
Content
SDMX 3-0-0 SECTION 5 FINAL-1.0_en_99c4cc7e.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +126.4 KB
Content
SDMX 3-0-0 SECTION 5 FINAL-1.0_en_eaceb05e.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +33.7 KB
Content