Last modified by Helena on 2025/09/10 11:19
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 1 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -107,7 +107,7 @@ 107 107 108 108 Notifying interested parties of newly published or re-published data, reference metadata or changes in structural metadata involves: 109 109 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.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. 111 111 112 112 == {{id name="_Toc93838"/}}3.5 Discovery == 113 113 ... ... @@ -166,9 +166,8 @@ 166 166 167 167 The registry interfaces are invoked in one of two ways: 168 168 169 -* 170 -*1. The interface is the name of the root node of the SDMX-ML document 171 -*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. 172 172 173 173 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. 174 174 ... ... @@ -244,23 +244,22 @@ 244 244 * that the components (Dimensions, Attributes, Measures, Metadata Attributes, etc.) are consistent with the Data Structure Definition or Metadata Structure Definition; 245 245 * 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: 246 246 247 -|**Action Attribute Value**|**Behaviour** 248 -|Append|Add this registration to the registry 249 -|Replace|Replace the existing Registration with this Registration identified by the id in the Registration of the Submit Registration Request 250 -|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 251 251 252 252 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: 253 253 254 -|**Boolean Attribute**|**Behaviour if Value is “true”** 255 -|indexTimeSeries|A compliant indexing application must index all the time series keys (for a Dataset registration) or metadata target values (for a Metadataset registration) 256 -|indexDataSet|((( 257 -A compliant indexing application must index the range of actual 258 - 259 -(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. 260 - 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. 261 261 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 262 262 ))) 263 -|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. 264 264 265 265 === {{id name="_Toc93850"/}}5.2.5 Data and Reference Metadata Discovery === 266 266 ... ... @@ -294,8 +294,9 @@ 294 294 295 295 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. 296 296 297 -|**Interface**|**Behaviour** 298 -|All|((( 295 +(% style="width:757.294px" %) 296 +|(% style="width:188px" %)**Interface**|(% style="width:542px" %)**Behaviour** 297 +|(% style="width:188px" %)All|(% style="width:542px" %)((( 299 299 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. 300 300 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. 301 301 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: ... ... @@ -302,14 +302,14 @@ 302 302 303 303 a) Be a draft version. 304 304 ))) 305 -|**Interface**|**Behaviour** 306 -| |((( 307 -b) Not be explicitly ^^[[(%class="wikiinternallinkwikiinternallink"%)^^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. 308 308 309 309 4) The semantic versioning rules in the SDMX documentation MUST be obeyed. 310 310 ))) 311 -|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. 312 -|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. 313 313 314 314 = {{id name="_Toc93853"/}}6 Identification of SDMX Objects = 315 315 ... ... @@ -339,27 +339,28 @@ 339 339 : 340 340 341 341 ((( 342 -|**Object Type**|**Data Attributes**|**Status**|**Data type**|**Notes** 343 -|(% rowspan="4" %)//Annotable//|AnnotationTitle|C|string| 344 -|AnnotationType|C|string| 345 -|AnnotationURN|C|string| 346 -|AnnotationText in the form of InternationalString|C| |This can have languagespecific variants 347 -|(% rowspan="4" %)//Identifiable//|All content as for //Annotable// plus| | | 348 -|id|M|string| 349 -|uri|C|string| 350 -|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. 351 -|(% rowspan="3" %)//Nameable//|All content as for //Identifiable// plus| | | 352 -|Name in the form of InternationalString|M|string|This can have language specific variants. 353 -|Description in the form of InternationalString|C|string|This can have language specific variants. 354 -|(% rowspan="4" %)//Versionable//|All content as for //Identifiable// plus| | | 355 -|version|M|string|This is the version number according to SDMX versioning rules. 356 -|validFrom|C|Date/time| 357 -|validTo|C|Date/time| 358 -|//Maintainable//|All content as for //Versionable// plus| | | 359 -| |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. 360 -| |serviceURL|C|string|The url of the service that can be queried for this resource. 361 -| |structureURL|C|string|The url of the resource. 362 -| |(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. 363 363 ))) 364 364 365 365 **Table 1: Common Attributes of Object Types** ... ... @@ -408,32 +408,8 @@ 408 408 409 409 An example of this is shown in the XML snippet below: 410 410 411 - **<str:Codelists>**411 +[[image:1747307906944-697.png]] 412 412 413 -**<str:Codelist id="CL_FREQ" agencyID="SDMX" version="1.0.0">** 414 - 415 -**<com:Name xml:lang="en">Standard frequency Codelist</com:Name>** 416 - 417 -**</str:Codelist>** 418 - 419 -**<str:Codelist id="CL_FREQ" agencyID="AA" version="1.0.0">** 420 - 421 -**<com:Name xml:lang="en">Codelist maintained by agency AA</com:Name>** 422 - 423 -**</str:Codelist>** 424 - 425 -**<str:Codelist id="CL_FREQ" agencyID="AA.CC" version="1.0.0">** 426 - 427 -**<com:Name xml:lang="en">Codelist maintained by the AA unit CC</com:Name>** 428 - 429 -**</str:Codelist>** 430 - 431 -**<str:Codelist id="CL_FREQ" agencyID="BB.CC" version="1.0.0">** 432 - 433 -**<com:Name xml:lang="en">Codelist maintained by the BB unit CC</com:Name>** 434 - 435 -**</str:Codelist>** 436 - 437 437 **Figure 8: Example Showing Use of Agency Identifiers** 438 438 439 439 Each of these maintenance agencies has an identical Code list with the Id CL_BOP. However, each is uniquely identified by means of the hierarchic agency structure. ... ... @@ -440,14 +440,16 @@ 440 440 441 441 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. 442 442 443 -=== =={{id name="_Toc93858"/}}6.2.2 Universal Resource Name (URN) =====419 +=== {{id name="_Toc93858"/}}6.2.2 Universal Resource Name (URN) === 444 444 445 - **6.2.2.1 Introduction**421 +==== 6.2.2.1 Introduction ==== 446 446 447 447 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.). 448 448 449 - **6.2.2.2 URN Structure//__Case Rules for URN__//**// //425 +==== 6.2.2.2 URN Structure ==== 450 450 427 +===== **//__Case Rules for URN__//** ===== 428 + 451 451 For the URN, all parts of the string are case sensitive. The generic structure of the URN is as follows: 452 452 453 453 SDMXprefix.SDMX-IM-package-name.class-name=agencyid:maintainedobjectid(maintainedobject-version).*containerobject-id.object-id ... ... @@ -458,7 +458,7 @@ 458 458 459 459 The Maintenance agency identifier is separated from the maintainable artefact identifier by a colon ‘:’. All other identifiers in the SDMX URN syntax are separated by a period ‘.’. The version information is encapsulated in parentheses ‘()’ and adheres to the SDMX versioning rules, as explained in SDMX Standards Section 6 “Technical Notes”, paragraph “4.3 Versioning. 460 460 461 - **6.2.2.3 Explanation of the generic structure**439 +==== 6.2.2.3 Explanation of the generic structure ==== 462 462 463 463 In the explanation below the actual object that is the target of the URN is called the **actual object**. 464 464 ... ... @@ -468,10 +468,32 @@ 468 468 469 469 The packages are: 470 470 471 -base codelist conceptscheme datastructure categoryscheme registry metadatastructure process structuremapping transformation449 +base 472 472 473 - **maintainable-object-id** is the identifierof the maintainable object. This will always be present as all identifiable objects are either a maintainable object or contained in a maintainable object. **maintainable-object-version** isthe version, according to the SDMX versioning rules, of the maintainable object and is enclosed in parentheses ‘()’, which are always present. **container-object-id** is the identifier of an intermediary object that contains the actual object which the URN is identifying. It is not mandatory as many actual objects do not have an intermediary container object. For instance, a Code is in a maintained object (Codelist) and has no intermediary container object, whereas a MetadataAttribute has an intermediary container object (MetadataAttributeDescriptor) and may have an intermediary container object, which is its parent MetadataAttribute. For this reason, the container object id may repeat, with each repetition identifying the object at the next-lower level in its hierarchy. Note that if there is only a single containing object in the model then it is NOT included in the URN structure. This applies to AttributeDescriptor, DimensionDescriptor, and MeasureDescriptor where there can be only one such object and this object has a fixed id. Therefore, whilst each of these has a URN, the id of the AttributeDescriptor, DimensionDescriptor, and MeasureDescriptor is not included when the actual object is a DataAttribute or a Dimension/ TimeDimension, or a Measure.451 +codelist 474 474 453 +conceptscheme 454 + 455 +datastructure 456 + 457 +categoryscheme 458 + 459 +registry 460 + 461 +metadatastructure 462 + 463 +process 464 + 465 +structuremapping 466 + 467 +transformation 468 + 469 +**maintainable-object-id** is the identifier of the maintainable object. This will always be present as all identifiable objects are either a maintainable object or contained in a maintainable object. 470 + 471 +**maintainable-object-version** is the version, according to the SDMX versioning rules, of the maintainable object and is enclosed in parentheses ‘()’, which are always present. 472 + 473 +**container-object-id** is the identifier of an intermediary object that contains the actual object which the URN is identifying. It is not mandatory as many actual objects do not have an intermediary container object. For instance, a Code is in a maintained object (Codelist) and has no intermediary container object, whereas a MetadataAttribute has an intermediary container object (MetadataAttributeDescriptor) and may have an intermediary container object, which is its parent MetadataAttribute. For this reason, the container object id may repeat, with each repetition identifying the object at the next-lower level in its hierarchy. Note that if there is only a single containing object in the model then it is NOT included in the URN structure. This applies to AttributeDescriptor, DimensionDescriptor, and MeasureDescriptor where there can be only one such object and this object has a fixed id. Therefore, whilst each of these has a URN, the id of the AttributeDescriptor, DimensionDescriptor, and MeasureDescriptor is not included when the actual object is a DataAttribute or a Dimension/ TimeDimension, or a Measure. 474 + 475 475 Note that although a Code can have a parent Code and a Concept can have a parent Concept these are maintained in a flat structure and therefore do not have a containerobject-id. 476 476 477 477 For example, the sequence is agency:DSDid(version).DimensionId and not agency:DSDid(version).DimensionDescriptorId.DimensionId. ... ... @@ -478,7 +478,7 @@ 478 478 479 479 object-id is the identifier of the actual object unless the actual object is a //Maintainable// object. If present it is always the last id and is not followed by any other character. 480 480 481 -//__**Generic Examples of the URN Structure**__// 481 +===== //__**Generic Examples of the URN Structure**__// ===== 482 482 483 483 __Actual object is a maintainable__ 484 484 ... ... @@ -504,7 +504,7 @@ 504 504 505 505 SDMXPrefix.SDMX-IM-package-name.classname=agencyid:maintained-objectid(version).contained-object-id.contained-object-id contained-objectid.object-id 506 506 507 -//__**Concrete Examples of the URN Structure**__// 507 +===== //__**Concrete Examples of the URN Structure**__// ===== 508 508 509 509 The Data Structure Definition CRED_EXT_DEBT of legacy version 2.1 maintained by the toplevel Agency TFFS would have the URN: 510 510 ... ... @@ -533,85 +533,86 @@ 533 533 534 534 The SDMX-RR MUST be able to resolve the unique identifier of an SDMX artefact and to produce an SDMX-ML rendering of that artefact if it is located in the Registry. 535 535 536 -=== =={{id name="_Toc93859"/}}6.2.3 Table of SDMX-IM Packages and Classes =====536 +=== {{id name="_Toc93859"/}}6.2.3 Table of SDMX-IM Packages and Classes === 537 537 538 538 The table below lists all of the packages in the SDMX-IM together with the concrete classes that are in these packages and whose objects have a URN. 539 539 540 -|**Package**|**URN class name (model class name where this is different)** 541 -|base|Agency 542 -| |AgencyScheme 543 -| |DataConsumer 544 -| |DataConsumerScheme 545 -| |DataProvider 546 -| |DataProviderScheme 547 -| |MetadataProvider 548 -| |MetadataProviderScheme 549 -| |OrganisationUnit 550 -| |OrganisationUnitScheme 551 -|datastructure|AttributeDescriptor 552 -| |DataAttribute 553 -| |Dataflow 554 -| |DataStructure (DataStructureDefinition) 555 -| |Dimension 556 -| |DimensionDescriptor 557 -| |GroupDimensionDescriptor 558 -| |Measure 559 -| |MeasureDescriptor 560 -| |TimeDimension 561 -| | 562 -|metadatastructure|MetadataAttribute 563 -| |MetadataAttributeDescriptor 564 -| |MetadataStructure MetadataStructureDefinition) 565 -| |Metadataflow 566 -| |MetadataSet 567 -| | 568 -|process|Process 569 -| |ProcessStep 570 -| |Transition 571 -| | 572 -|registry|DataConstraint 573 -| |MetadataConstraint 574 -| |MetadataProvisionAgreement 575 -| |ProvisionAgreement 576 -| |Subscription 577 -| | 578 -|structuremapping|CategorySchemeMap 579 -| |ConceptSchemeMap 580 -| |OrganisationSchemeMap 581 -| |ReportingTaxonomyMap 582 -| |RepresentationMap 583 -| |StructureMap 584 -| | 585 -|codelist|Code 586 -| |Codelist 587 -| |HierarchicalCode 588 -| |Hierarchy 589 -| |HierarchyAssociation 590 -| |Level 591 -| |ValueList 592 -| | 593 -|categoryscheme|Categorisation 594 -| |Category 595 -| |CategoryScheme 596 -| |ReportingCategory 597 -| |ReportingTaxonomy 598 -|conceptscheme|Concept 599 -| |ConceptScheme 600 -| | 601 -|transformation|CustomType 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 540 +(% style="width:651.294px" %) 541 +|(% style="width:134px" %)**Package**|(% style="width:502px" %)**URN class name (model class name where this is different)** 542 +|(% style="width:134px" %)base|(% style="width:502px" %)Agency 543 +|(% style="width:134px" %) |(% style="width:502px" %)AgencyScheme 544 +|(% style="width:134px" %) |(% style="width:502px" %)DataConsumer 545 +|(% style="width:134px" %) |(% style="width:502px" %)DataConsumerScheme 546 +|(% style="width:134px" %) |(% style="width:502px" %)DataProvider 547 +|(% style="width:134px" %) |(% style="width:502px" %)DataProviderScheme 548 +|(% style="width:134px" %) |(% style="width:502px" %)MetadataProvider 549 +|(% style="width:134px" %) |(% style="width:502px" %)MetadataProviderScheme 550 +|(% style="width:134px" %) |(% style="width:502px" %)OrganisationUnit 551 +|(% style="width:134px" %) |(% style="width:502px" %)OrganisationUnitScheme 552 +|(% style="width:134px" %)datastructure|(% style="width:502px" %)AttributeDescriptor 553 +|(% style="width:134px" %) |(% style="width:502px" %)DataAttribute 554 +|(% style="width:134px" %) |(% style="width:502px" %)Dataflow 555 +|(% style="width:134px" %) |(% style="width:502px" %)DataStructure (DataStructureDefinition) 556 +|(% style="width:134px" %) |(% style="width:502px" %)Dimension 557 +|(% style="width:134px" %) |(% style="width:502px" %)DimensionDescriptor 558 +|(% style="width:134px" %) |(% style="width:502px" %)GroupDimensionDescriptor 559 +|(% style="width:134px" %) |(% style="width:502px" %)Measure 560 +|(% style="width:134px" %) |(% style="width:502px" %)MeasureDescriptor 561 +|(% style="width:134px" %) |(% style="width:502px" %)TimeDimension 562 +|(% style="width:134px" %) |(% style="width:502px" %) 563 +|(% style="width:134px" %)metadatastructure|(% style="width:502px" %)MetadataAttribute 564 +|(% style="width:134px" %) |(% style="width:502px" %)MetadataAttributeDescriptor 565 +|(% style="width:134px" %) |(% style="width:502px" %)MetadataStructure MetadataStructureDefinition) 566 +|(% style="width:134px" %) |(% style="width:502px" %)Metadataflow 567 +|(% style="width:134px" %) |(% style="width:502px" %)MetadataSet 568 +|(% style="width:134px" %) |(% style="width:502px" %) 569 +|(% style="width:134px" %)process|(% style="width:502px" %)Process 570 +|(% style="width:134px" %) |(% style="width:502px" %)ProcessStep 571 +|(% style="width:134px" %) |(% style="width:502px" %)Transition 572 +|(% style="width:134px" %) |(% style="width:502px" %) 573 +|(% style="width:134px" %)registry|(% style="width:502px" %)DataConstraint 574 +|(% style="width:134px" %) |(% style="width:502px" %)MetadataConstraint 575 +|(% style="width:134px" %) |(% style="width:502px" %)MetadataProvisionAgreement 576 +|(% style="width:134px" %) |(% style="width:502px" %)ProvisionAgreement 577 +|(% style="width:134px" %) |(% style="width:502px" %)Subscription 578 +|(% style="width:134px" %) |(% style="width:502px" %) 579 +|(% style="width:134px" %)structuremapping|(% style="width:502px" %)CategorySchemeMap 580 +|(% style="width:134px" %) |(% style="width:502px" %)ConceptSchemeMap 581 +|(% style="width:134px" %) |(% style="width:502px" %)OrganisationSchemeMap 582 +|(% style="width:134px" %) |(% style="width:502px" %)ReportingTaxonomyMap 583 +|(% style="width:134px" %) |(% style="width:502px" %)RepresentationMap 584 +|(% style="width:134px" %) |(% style="width:502px" %)StructureMap 585 +|(% style="width:134px" %) |(% style="width:502px" %) 586 +|(% style="width:134px" %)codelist|(% style="width:502px" %)Code 587 +|(% style="width:134px" %) |(% style="width:502px" %)Codelist 588 +|(% style="width:134px" %) |(% style="width:502px" %)HierarchicalCode 589 +|(% style="width:134px" %) |(% style="width:502px" %)Hierarchy 590 +|(% style="width:134px" %) |(% style="width:502px" %)HierarchyAssociation 591 +|(% style="width:134px" %) |(% style="width:502px" %)Level 592 +|(% style="width:134px" %) |(% style="width:502px" %)ValueList 593 +|(% style="width:134px" %) |(% style="width:502px" %) 594 +|(% style="width:134px" %)categoryscheme|(% style="width:502px" %)Categorisation 595 +|(% style="width:134px" %) |(% style="width:502px" %)Category 596 +|(% style="width:134px" %) |(% style="width:502px" %)CategoryScheme 597 +|(% style="width:134px" %) |(% style="width:502px" %)ReportingCategory 598 +|(% style="width:134px" %) |(% style="width:502px" %)ReportingTaxonomy 599 +|(% style="width:134px" %)conceptscheme|(% style="width:502px" %)Concept 600 +|(% style="width:134px" %) |(% style="width:502px" %)ConceptScheme 601 +|(% style="width:134px" %) |(% style="width:502px" %) 602 +|(% style="width:134px" %)transformation|(% style="width:502px" %)CustomType 603 +|(% style="width:134px" %) |(% style="width:502px" %)CustomTypeScheme 604 +|(% style="width:134px" %) |(% style="width:502px" %)NamePersonalisation 605 +|(% style="width:134px" %) |(% style="width:502px" %)NamePersonalisationScheme 606 +|(% style="width:134px" %) |(% style="width:502px" %)Ruleset 607 +|(% style="width:134px" %) |(% style="width:502px" %)RulesetScheme 608 +|(% style="width:134px" %) |(% style="width:502px" %)Transformation 609 +|(% style="width:134px" %) |(% style="width:502px" %)TransformationScheme 610 +|(% style="width:134px" %) |(% style="width:502px" %)UserDefinedOperator 611 +|(% style="width:134px" %) |(% style="width:502px" %)UserDefinedOperatorScheme 612 +|(% style="width:134px" %) |(% style="width:502px" %)VtlCodelistMapping 613 +|(% style="width:134px" %) |(% style="width:502px" %)VtlConceptMapping 614 +|(% style="width:134px" %) |(% style="width:502px" %)VtlDataflowMapping 615 +|(% style="width:134px" %) |(% style="width:502px" %)VtlMappingScheme 615 615 616 616 **Table 2: SDMX-IM Packages and Contained Classes** 617 617 ... ... @@ -623,136 +623,118 @@ 623 623 624 624 urn:sdmx.org.sdmx.infomodel.{package}.{classname}= 625 625 626 -|**Classname**|**Ending URN pattern**|**Example** 627 -|Agency^^[[(% class="wikiinternallink wikiinternallink" %)^^2^^>>path:#sdfootnote2sym||name="sdfootnote2anc"]](%%)^^|agencySchemeAgencyId:**AGENCIES**(**1.0**).agencyId|ECB:**AGENCIES**(**1.0**).AA 628 -|//AgencyScheme//|agencySchemeAgencyId:**AGENCIES**(**1.0**)|ECB:**AGENCIES**(**1.0**) 629 -|//Categorisation//|categorisationAgencyId:categorisationId(version)|IMF:cat001(1.0.0) 630 -|Category|categorySchemeAgencyId:categorySchemeId(versi on).categoryId.categoryId.categoryId etc.|IMF:SDDS(1.0.0):level_1_category.level_2_category … 631 -|//CategoryScheme//|categorySchemeAgencyId:categorySchemeId(versi on)|IMF:SDDS(1.0.0) 627 +(% style="width:1311.29px" %) 628 +|(% style="width:252px" %)**Classname**|(% style="width:639px" %)**Ending URN pattern**|(% style="width:418px" %)**Example** 629 +|(% style="width:252px" %)Agency{{footnote}}The identification of an Agency in the URN structure for the maintainable object is by means of the agencyId. The AgencyScheme is not identified as SDMX has a mechanism for identifying an Agency uniquely by its Id. Note that this Id may be hierarchical. For example, a sub-agency of IMF is referred like this: IMF.SubAgency1{{/footnote}}|(% style="width:639px" %)agencySchemeAgencyId:**AGENCIES**(**1.0**).agencyId|(% style="width:418px" %)ECB:**AGENCIES**(**1.0**).AA 630 +|(% style="width:252px" %)//AgencyScheme//|(% style="width:639px" %)agencySchemeAgencyId:**AGENCIES**(**1.0**)|(% style="width:418px" %)ECB:**AGENCIES**(**1.0**) 631 +|(% style="width:252px" %)//Categorisation//|(% style="width:639px" %)categorisationAgencyId:categorisationId(version)|(% style="width:418px" %)IMF:cat001(1.0.0) 632 +|(% style="width:252px" %)Category|(% style="width:639px" %)categorySchemeAgencyId:categorySchemeId(versi on).categoryId.categoryId.categoryId etc.|(% style="width:418px" %)IMF:SDDS(1.0.0):level_1_category.level_2_category … 633 +|(% style="width:252px" %)//CategoryScheme//|(% style="width:639px" %)categorySchemeAgencyId:categorySchemeId(versi on)|(% style="width:418px" %)IMF:SDDS(1.0.0) 632 632 633 -|**Classname**|**Ending URN pattern**|**Example** 634 -|//CategorySchemeMap//|((( 635 -catSchemeMapAgencyId:catSchemeMapId(version 636 - 637 -) 638 -)))|SDMX:EUROSTAT_SUBJECT_DOMAIN(1.0.0) 639 -|Code|codeListAgencyId:codelistId(version).codeId|SDMX:CL_FREQ(1.0.0).Q 640 -|//Codelist//|codeListAgencyId:codeListId(version)|SDMX:CL_FREQ(1.0.0) 641 -|ComponentMap|structureMapAgencyId:structureMap(version).com ponentMapId|SDMX:BOP_STRUCTURES(1.0.0).REF_AREA_TO_COUNT RY 642 -|Concept|conceptSchemeAgencyId:conceptSchemeId(versio n).conceptId|SDMX:CROSS_DOMAIN_CONCEPTS(1.0.0).FREQ 643 -|//ConceptScheme//|conceptSchemeAgencyId:conceptSchemeId(versio n)|SDMX:CROSS_DOMAIN_CONCEPTS(1.0.0) 644 -|//ConceptSchemeMap//|((( 635 +|(% style="width:250px" %)**Classname**|(% style="width:639px" %)**Ending URN pattern**|(% style="width:1049px" %)**Example** 636 +|(% style="width:250px" %)//CategorySchemeMap//|(% style="width:639px" %)((( 637 +catSchemeMapAgencyId:catSchemeMapId(version) 638 +)))|(% style="width:1049px" %)SDMX:EUROSTAT_SUBJECT_DOMAIN(1.0.0) 639 +|(% style="width:250px" %)Code|(% style="width:639px" %)codeListAgencyId:codelistId(version).codeId|(% style="width:1049px" %)SDMX:CL_FREQ(1.0.0).Q 640 +|(% style="width:250px" %)//Codelist//|(% style="width:639px" %)codeListAgencyId:codeListId(version)|(% style="width:1049px" %)SDMX:CL_FREQ(1.0.0) 641 +|(% style="width:250px" %)ComponentMap|(% style="width:639px" %)structureMapAgencyId:structureMap(version).com ponentMapId|(% style="width:1049px" %)SDMX:BOP_STRUCTURES(1.0.0).REF_AREA_TO_COUNT RY 642 +|(% style="width:250px" %)Concept|(% style="width:639px" %)conceptSchemeAgencyId:conceptSchemeId(versio n).conceptId|(% style="width:1049px" %)SDMX:CROSS_DOMAIN_CONCEPTS(1.0.0).FREQ 643 +|(% style="width:250px" %)//ConceptScheme//|(% style="width:639px" %)conceptSchemeAgencyId:conceptSchemeId(versio n)|(% style="width:1049px" %)SDMX:CROSS_DOMAIN_CONCEPTS(1.0.0) 644 +|(% style="width:250px" %)//ConceptSchemeMap//|(% style="width:639px" %)((( 645 645 conceptSchemeMapAgencyId:conceptSchemeMap 646 - 647 647 Id(version) 648 -)))|SDMX:CONCEPT_MAP(1.0.0) 649 -|CustomType|customTypeSchemeAgencyId customTypeSchemeId(version) customTypeId|ECB: CUSTOM_TYPE_SCHEME(1.0.0).CUSTOM_TYPE_1 650 -|//CustomTypeScheme//|customTypeSchemeAgencyId customTypeSchemeId(version)|ECB:CUSTOM_TYPE_SCHEME(1.0.0) 651 -|DataAttrribute|dataStructureDefinitionAgencyId:dataStructureDef initionId(version).dataAttributeId|TFFS:EXT_DEBT(1.0.0).OBS_STATUS 652 -|//DataConstraint//|dataConstraintAgencyId:dataConstraintId(version)|TFFS:CREDITOR_DATA_CONTENT(1.0.0) 647 +)))|(% style="width:1049px" %)SDMX:CONCEPT_MAP(1.0.0) 648 +|(% style="width:250px" %)CustomType|(% style="width:639px" %)customTypeSchemeAgencyId customTypeSchemeId(version) customTypeId|(% style="width:1049px" %)ECB: CUSTOM_TYPE_SCHEME(1.0.0).CUSTOM_TYPE_1 649 +|(% style="width:250px" %)//CustomTypeScheme//|(% style="width:639px" %)customTypeSchemeAgencyId customTypeSchemeId(version)|(% style="width:1049px" %)ECB:CUSTOM_TYPE_SCHEME(1.0.0) 650 +|(% style="width:250px" %)DataAttrribute|(% style="width:639px" %)dataStructureDefinitionAgencyId:dataStructureDef initionId(version).dataAttributeId|(% style="width:1049px" %)TFFS:EXT_DEBT(1.0.0).OBS_STATUS 651 +|(% style="width:250px" %)//DataConstraint//|(% style="width:639px" %)dataConstraintAgencyId:dataConstraintId(version)|(% style="width:1049px" %)TFFS:CREDITOR_DATA_CONTENT(1.0.0) 653 653 654 -|**Classname**|**Ending URN pattern**|**Example** 655 -|DataConsumer|dataConsumerSchemeAgencyId:**DATA_CONSUME RS**(**1.0**).dataConsumerId|SDMX:**DATA_CONSUMERS**(**1.0**).CONSUMER_1 656 -|//DataConsumerScheme//|((( 657 -dataConsumerSchemeAgencyId:**DATA_CONSUME** 658 - 659 -**RS**(**1.0**) 660 -)))|SDMX:**DATA_CONSUMERS**(**1.0**) 661 -|//Dataflow//|dataflowAgencyId:dataflowId(version)|TFFS:CRED_EXT_DEBT(1.0.0) 662 -|DataProvider|((( 663 -dataProviderSchemeAgencyId:**DATA_PROVIDERS**( 664 - 665 -**1.0**).dataProviderId 666 -)))|SDMX:**DATA_PROVIDERS**(**1.0**).PROVIDER_1 667 -|//DataProviderScheme//|((( 668 -dataProviderSchemeAgencyId:**DATA_PROVIDERS**( 669 - 670 -**1.0**) 671 -)))|SDMX:**DATA_PROVIDERS**(**1.0**) 672 -|//DataStructure//|dataStructureDefinitionAgencyId:dataStructureDef initionId(version)|TFFS:EXT_DEBT(1.0.0) 673 -|Dimension|dataStructureDefinitionAgencyId:dataStructureDef initionId(version).dimensionId|TFFS:EXT_DEBT(1.0.0).FREQ 674 -|((( 653 +|(% style="width:248px" %)**Classname**|(% style="width:643px" %)**Ending URN pattern**|(% style="width:1047px" %)**Example** 654 +|(% style="width:248px" %)DataConsumer|(% style="width:643px" %)dataConsumerSchemeAgencyId:**DATA_CONSUME RS**(**1.0**).dataConsumerId|(% style="width:1047px" %)SDMX:**DATA_CONSUMERS**(**1.0**).CONSUMER_1 655 +|(% style="width:248px" %)//DataConsumerScheme//|(% style="width:643px" %)((( 656 +dataConsumerSchemeAgencyId:**DATA_CONSUME RS**(**1.0**) 657 +)))|(% style="width:1047px" %)SDMX:**DATA_CONSUMERS**(**1.0**) 658 +|(% style="width:248px" %)//Dataflow//|(% style="width:643px" %)dataflowAgencyId:dataflowId(version)|(% style="width:1047px" %)TFFS:CRED_EXT_DEBT(1.0.0) 659 +|(% style="width:248px" %)DataProvider|(% style="width:643px" %)((( 660 +dataProviderSchemeAgencyId:**DATA_PROVIDERS**(**1.0**).dataProviderId 661 +)))|(% style="width:1047px" %)SDMX:**DATA_PROVIDERS**(**1.0**).PROVIDER_1 662 +|(% style="width:248px" %)//DataProviderScheme//|(% style="width:643px" %)((( 663 +dataProviderSchemeAgencyId:**DATA_PROVIDERS**(**1.0**) 664 +)))|(% style="width:1047px" %)SDMX:**DATA_PROVIDERS**(**1.0**) 665 +|(% style="width:248px" %)//DataStructure//|(% style="width:643px" %)dataStructureDefinitionAgencyId:dataStructureDef initionId(version)|(% style="width:1047px" %)TFFS:EXT_DEBT(1.0.0) 666 +|(% style="width:248px" %)Dimension|(% style="width:643px" %)dataStructureDefinitionAgencyId:dataStructureDef initionId(version).dimensionId|(% style="width:1047px" %)TFFS:EXT_DEBT(1.0.0).FREQ 667 +|(% style="width:248px" %)((( 675 675 DimensionDescriptor 676 - 677 677 MeasureDescriptor 678 - 679 679 AttributeDescriptor 680 -)))|dataStructureDefinitionAgencyId:dataStructureDef initionId(version).componentListId where the componentListId is the name of the class (there is only one occurrence of each in the Data Structure Definition)|((( 671 +)))|(% style="width:643px" %)dataStructureDefinitionAgencyId:dataStructureDef initionId(version).componentListId where the componentListId is the name of the class (there is only one occurrence of each in the Data Structure Definition)|(% style="width:1047px" %)((( 681 681 TFFS:EXT_DEBT(1.0.0).DimensionDescriptor 682 - 683 683 TFFS:EXT_DEBT(1.0.0).MeasureDescriptor 684 - 685 685 TFFS:EXT_DEBT(1.0.0).AttributeDescriptor 686 686 ))) 687 -|GroupDimensionDescriptor|dataStructureDefinitionAgencyId:dataStructureDef initionId(version).groupDimensionDescriptorId|TFFS:EXT_DEBT(1.0.0).SIBLING 688 -|HierarchicalCode|hierarchyAgencyId:hierarchyId(version).hierarchica lCode.hierarchicalCode|UNESCO:H-C-GOV(1.0.0).GOV_CODE1.GOV_CODE1_1 676 +|(% style="width:248px" %)GroupDimensionDescriptor|(% style="width:643px" %)dataStructureDefinitionAgencyId:dataStructureDef initionId(version).groupDimensionDescriptorId|(% style="width:1047px" %)TFFS:EXT_DEBT(1.0.0).SIBLING 677 +|(% style="width:248px" %)HierarchicalCode|(% style="width:643px" %)hierarchyAgencyId:hierarchyId(version).hierarchica lCode.hierarchicalCode|(% style="width:1047px" %)UNESCO:H-C-GOV(1.0.0).GOV_CODE1.GOV_CODE1_1 689 689 690 -|**Classname**|**Ending URN pattern**|**Example** 691 -|//Hierarchy//|hierarchyAgencyId:hierarchyId(version)|UNESCO:H-C-GOV(1.0.0) 692 -|//HierarchyAssociation//|hierarchyAssociationAgencyId:hierarchyAssociatio nId(version)|UNESCO:CL_EXP_SOURCE(1.0.0) 693 -|Level|hierarchyAgencyId:hierarchyId(version).level|UNESCO:H-C-GOV(1.0.0).LVL1 694 -|Measure|dataStructureDefinitionAgencyId:dataStructureDef initionId(version).measureId|TFFS:EXT_DEBT(1.0.0).OBS_VALUE 695 -|MetadataAttribute|((( 679 +|(% style="width:248px" %)**Classname**|(% style="width:646px" %)**Ending URN pattern**|(% style="width:1044px" %)**Example** 680 +|(% style="width:248px" %)//Hierarchy//|(% style="width:646px" %)hierarchyAgencyId:hierarchyId(version)|(% style="width:1044px" %)UNESCO:H-C-GOV(1.0.0) 681 +|(% style="width:248px" %)//HierarchyAssociation//|(% style="width:646px" %)hierarchyAssociationAgencyId:hierarchyAssociatio nId(version)|(% style="width:1044px" %)UNESCO:CL_EXP_SOURCE(1.0.0) 682 +|(% style="width:248px" %)Level|(% style="width:646px" %)hierarchyAgencyId:hierarchyId(version).level|(% style="width:1044px" %)UNESCO:H-C-GOV(1.0.0).LVL1 683 +|(% style="width:248px" %)Measure|(% style="width:646px" %)dataStructureDefinitionAgencyId:dataStructureDef initionId(version).measureId|(% style="width:1044px" %)TFFS:EXT_DEBT(1.0.0).OBS_VALUE 684 +|(% style="width:248px" %)MetadataAttribute|(% style="width:646px" %)((( 696 696 msdAgencyId:msdId(version).metadataAttributeId. 697 - 698 698 metadataAttributeId 699 -)))|IMF:SDDS_MSD(1.0.0).COMPILATION.METHOD 700 -|MetadataAttributeDescriptor|msdAgencyId:msdId(version).metadataAttributeDe scriptorId|IMF:SDDS_MSD(1.0.0).MetadataAttributeDescriptor 701 -|//MetadataConstraint//|metadataConstraintAgencyId:metadataConstraintI d(version)|TFFS:CREDITOR_METADATA_CONTENT(1.0.0) 702 -|//Metadataflow//|metadataflowAgencyId:metadataflowId(version)|IMF:SDDS_MDF(1.0.0) 703 -|MetadataProvider|metadataProviderSchemeAgencyId:**METADATA_P ROVIDERS**(**1.0**).metadataProviderId|SDMX:**METADATA_PROVIDERS**(**1.0**).MD_PROVIDER_1 704 -|//MetadataProviderScheme//|metadataProviderSchemeAgencyId:**METADATA_P ROVIDERS**(**1.0**)|SDMX:**METADATA_PROVIDERS**(**1.0**) 705 -|//MetadataProvisionAgreement//|metadataProvisionAgreementAgencyId:metadataP rovisionAgreementId(version)|IMF:SDDS_MDF_AB(1.0.0) 706 -|//MetadataSet//|metadataProviderId:metadataSetId(version)|MD_PROVIDER:METADATASET(1.0.0) 707 -|//MetadataStructure//|msdAgencyId:msdId(version)|IMF:SDDS_MSD(1.0.0) 687 +)))|(% style="width:1044px" %)IMF:SDDS_MSD(1.0.0).COMPILATION.METHOD 688 +|(% style="width:248px" %)MetadataAttributeDescriptor|(% style="width:646px" %)msdAgencyId:msdId(version).metadataAttributeDe scriptorId|(% style="width:1044px" %)IMF:SDDS_MSD(1.0.0).MetadataAttributeDescriptor 689 +|(% style="width:248px" %)//MetadataConstraint//|(% style="width:646px" %)metadataConstraintAgencyId:metadataConstraintI d(version)|(% style="width:1044px" %)TFFS:CREDITOR_METADATA_CONTENT(1.0.0) 690 +|(% style="width:248px" %)//Metadataflow//|(% style="width:646px" %)metadataflowAgencyId:metadataflowId(version)|(% style="width:1044px" %)IMF:SDDS_MDF(1.0.0) 691 +|(% style="width:248px" %)MetadataProvider|(% style="width:646px" %)metadataProviderSchemeAgencyId:**METADATA_P ROVIDERS**(**1.0**).metadataProviderId|(% style="width:1044px" %)SDMX:**METADATA_PROVIDERS**(**1.0**).MD_PROVIDER_1 692 +|(% style="width:248px" %)//MetadataProviderScheme//|(% style="width:646px" %)metadataProviderSchemeAgencyId:**METADATA_P ROVIDERS**(**1.0**)|(% style="width:1044px" %)SDMX:**METADATA_PROVIDERS**(**1.0**) 693 +|(% style="width:248px" %)//MetadataProvisionAgreement//|(% style="width:646px" %)metadataProvisionAgreementAgencyId:metadataP rovisionAgreementId(version)|(% style="width:1044px" %)IMF:SDDS_MDF_AB(1.0.0) 694 +|(% style="width:248px" %)//MetadataSet//|(% style="width:646px" %)metadataProviderId:metadataSetId(version)|(% style="width:1044px" %)MD_PROVIDER:METADATASET(1.0.0) 695 +|(% style="width:248px" %)//MetadataStructure//|(% style="width:646px" %)msdAgencyId:msdId(version)|(% style="width:1044px" %)IMF:SDDS_MSD(1.0.0) 708 708 709 -|**Classname**|**Ending URN pattern**|**Example** 710 -|NamePersonalisation|namePersonalisationSchemeAgencyId namePersonalisationSchemeId(version) namePersonalisationId|ECB:PSN_SCHEME(1.0.0).PSN1234 711 -|//NamePersonalisationScheme//|namePersonalisationSchemeAgencyId namePersonalisationSchemeId(version)|ECB:PSN_SCHEME(1.0.0) 712 -|//OrganisationSchemeMap//|orgSchemeMapAgencyId:orgSchemeMapId(versio n)|SDMX:AGENCIES_PROVIDERS(1.0.0) 713 -|OrganisationUnit|organisationUnitSchemeAgencyId:organisationUni 714 -|//OrganisationUnitScheme//|organisationUnitSchemeAgencyId:organisationUni tSchemeId(version)|ECB:ORGANISATIONS(1.0.0) 715 -|//Process//|processAgencyId:processId{version)|BIS:PROCESS1(1.0.0) 716 -|ProcessStep|((( 697 +|(% style="width:248px" %)**Classname**|(% style="width:629px" %)**Ending URN pattern**|(% style="width:1061px" %)**Example** 698 +|(% style="width:248px" %)NamePersonalisation|(% style="width:629px" %)namePersonalisationSchemeAgencyId namePersonalisationSchemeId(version) namePersonalisationId|(% style="width:1061px" %)ECB:PSN_SCHEME(1.0.0).PSN1234 699 +|(% style="width:248px" %)//NamePersonalisationScheme//|(% style="width:629px" %)namePersonalisationSchemeAgencyId namePersonalisationSchemeId(version)|(% style="width:1061px" %)ECB:PSN_SCHEME(1.0.0) 700 +|(% style="width:248px" %)//OrganisationSchemeMap//|(% style="width:629px" %)orgSchemeMapAgencyId:orgSchemeMapId(versio n)|(% style="width:1061px" %)SDMX:AGENCIES_PROVIDERS(1.0.0) 701 +|(% style="width:248px" %)OrganisationUnit|(% style="width:629px" %)organisationUnitSchemeAgencyId:organisationUnitSchemeId(version).organisationUnitId|(% style="width:1061px" %)ECB:ORGANISATIONS(1.0.0).1F 702 +|(% style="width:248px" %)//OrganisationUnitScheme//|(% style="width:629px" %)organisationUnitSchemeAgencyId:organisationUni tSchemeId(version)|(% style="width:1061px" %)ECB:ORGANISATIONS(1.0.0) 703 +|(% style="width:248px" %)//Process//|(% style="width:629px" %)processAgencyId:processId{version)|(% style="width:1061px" %)BIS:PROCESS1(1.0.0) 704 +|(% style="width:248px" %)ProcessStep|(% style="width:629px" %)((( 717 717 processAgencyId:processId(version).processStepId. 718 - 719 719 processStepId 720 -)))|BIS:PROCESS1(1.0.0).STEP1.STEP1_1 721 -|//ProvisionAgreement//|provisionAgreementAgencyId:provisionAgreement Id(version)|TFFS:CRED_EXT_DEBT_AB(1.0.0) 722 -|ReportingCategory|((( 707 +)))|(% style="width:1061px" %)BIS:PROCESS1(1.0.0).STEP1.STEP1_1 708 +|(% style="width:248px" %)//ProvisionAgreement//|(% style="width:629px" %)provisionAgreementAgencyId:provisionAgreement Id(version)|(% style="width:1061px" %)TFFS:CRED_EXT_DEBT_AB(1.0.0) 709 +|(% style="width:248px" %)ReportingCategory|(% style="width:629px" %)((( 723 723 reportingTaxonomyAgencyId: 724 - 725 725 reportingTaxonomyId(version).reportingCategoryI d.reportingCategoryId 726 -)))|IMF:REP_1(1.0.0):LVL1_REP_CAT.LVL2_REP_CAT 727 -|//ReportingTaxonomy//|reportingTaxonomyAgencyId:reportingTaxonomyI d(version)|IMF:REP_1(1.0.0) 728 -|//ReportingTaxonomyMap//|repTaxonomyAgencyId:repTaxonomyId(version)|SDMX:RT_MAP(1.0.0) 712 +)))|(% style="width:1061px" %)IMF:REP_1(1.0.0):LVL1_REP_CAT.LVL2_REP_CAT 713 +|(% style="width:248px" %)//ReportingTaxonomy//|(% style="width:629px" %)reportingTaxonomyAgencyId:reportingTaxonomyI d(version)|(% style="width:1061px" %)IMF:REP_1(1.0.0) 714 +|(% style="width:248px" %)//ReportingTaxonomyMap//|(% style="width:629px" %)repTaxonomyAgencyId:repTaxonomyId(version)|(% style="width:1061px" %)SDMX:RT_MAP(1.0.0) 729 729 730 -|**Classname**|**Ending URN pattern**|**Example** 731 -|//RepresentationMap//|repMapAgencyId:repMapId(version)|SDMX:REF_AREA_MAPPING(1.0.0) 732 -|Ruleset|rulesetSchemeAgencyId rulesetSchemeId(version) rulesetId|ECB:RULESET_23(1.0.0).SET111 733 -|//RulesetScheme//|rulesetSchemeAgencyId rulesetSchemeId(version)|ECB:RULESET_23(1.0.0) 734 -|//StructureMap//|structureMapAgencyId:structureMap(version)|SDMX:BOP_STRUCTURES(1.0.0) 735 -|Subscription|((( 716 +|(% style="width:247px" %)**Classname**|(% style="width:649px" %)**Ending URN pattern**|(% style="width:1042px" %)**Example** 717 +|(% style="width:247px" %)//RepresentationMap//|(% style="width:649px" %)repMapAgencyId:repMapId(version)|(% style="width:1042px" %)SDMX:REF_AREA_MAPPING(1.0.0) 718 +|(% style="width:247px" %)Ruleset|(% style="width:649px" %)rulesetSchemeAgencyId rulesetSchemeId(version) rulesetId|(% style="width:1042px" %)ECB:RULESET_23(1.0.0).SET111 719 +|(% style="width:247px" %)//RulesetScheme//|(% style="width:649px" %)rulesetSchemeAgencyId rulesetSchemeId(version)|(% style="width:1042px" %)ECB:RULESET_23(1.0.0) 720 +|(% style="width:247px" %)//StructureMap//|(% style="width:649px" %)structureMapAgencyId:structureMap(version)|(% style="width:1042px" %)SDMX:BOP_STRUCTURES(1.0.0) 721 +|(% style="width:247px" %)Subscription|(% style="width:649px" %)((( 736 736 The Subscription is not itself an Identifiable Artefact and therefore it does not follow the rules for URN structure. 737 - 738 738 The name of the URN is registryURN There is no pre-determined format. 739 -)))|This cannot be generated by a common mechanism as subscriptions, although maintainable in the sense that they can be submitted and deleted, are not mandated to be created by a maintenance agency and have no versioning mechanism. It is therefore the responsibility of the target registry to generate a unique Id for the Subscription, and for the application creating the subscription to store the registry URN that is returned from the registry in the subscription response message. 740 -|TimeDimension|dataStructureDefinitionAgencyId:dataStructureDef initionId(version).timeDimensionId|TFFS:EXT_DEBT(1.0.0).TIME_PERIOD 741 -|Transformation|transformationSchemeAgencyId transformationSchemeId(version) transformationId|ECB:TRANSFORMATION_SCHEME(1.0.0).TRANS_1 742 -|//TransformationScheme//|transformationSchemeAgencyId transformationSchemeId(version)|ECB: TRANSFORMATION_SCHEME(1.0.0) 743 -|**Classname**|**Ending URN pattern**|**Example** 744 -|Transition|((( 724 +)))|(% style="width:1042px" %)This cannot be generated by a common mechanism as subscriptions, although maintainable in the sense that they can be submitted and deleted, are not mandated to be created by a maintenance agency and have no versioning mechanism. It is therefore the responsibility of the target registry to generate a unique Id for the Subscription, and for the application creating the subscription to store the registry URN that is returned from the registry in the subscription response message. 725 +|(% style="width:247px" %)TimeDimension|(% style="width:649px" %)dataStructureDefinitionAgencyId:dataStructureDef initionId(version).timeDimensionId|(% style="width:1042px" %)TFFS:EXT_DEBT(1.0.0).TIME_PERIOD 726 +|(% style="width:247px" %)Transformation|(% style="width:649px" %)transformationSchemeAgencyId transformationSchemeId(version) transformationId|(% style="width:1042px" %)ECB:TRANSFORMATION_SCHEME(1.0.0).TRANS_1 727 +|(% style="width:247px" %)//TransformationScheme//|(% style="width:649px" %)transformationSchemeAgencyId transformationSchemeId(version)|(% style="width:1042px" %)ECB: TRANSFORMATION_SCHEME(1.0.0) 728 +|(% style="width:247px" %)Transition|(% style="width:649px" %)((( 745 745 processAgencyId:processId(version).processStepId. 746 - 747 747 transitionId 748 -)))|BIS:PROCESS1(1.0.0).STEP1.TRANSITION1 749 -|UserDefinedOperator|userDefinedOperatorSchemeAgencyId userDefinedOperatorSchemeId(version) usserDefinedOperatorId|ECB:OS_CALC(1.2.0).OS267 750 -|//UserDefinedOperatorScheme//|userDefinedOperatorSchemeAgencyId userDefinedOperatorSchemeId(version)|ECB:OS_CALC(1.2.0) 751 -|//ValueList//|valuelistAgencyId:valuelistId(version)|SDMX:VLIST(1.0.0) 752 -|VtlCodelistMapping|vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlCodelistMappingId|ECB:CLIST_MP(2.0.0).ABZ 753 -|VtlConceptMapping|vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlConceptMappingId|ECB:CLIST_MP(1.0.0).XYA 754 -|VtlDataflowMapping|vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlDataflowMappingId|ECB:CLIST_MP(1.0.0).MOQ 755 -|//VtlMappingScheme//|vtlMappingSchemeAgencyId VtlMappingSchemeId(version)|ECB:CLIST_MP(2.0.0) 731 +)))|(% style="width:1042px" %)BIS:PROCESS1(1.0.0).STEP1.TRANSITION1 732 +|(% style="width:247px" %)UserDefinedOperator|(% style="width:649px" %)userDefinedOperatorSchemeAgencyId userDefinedOperatorSchemeId(version) usserDefinedOperatorId|(% style="width:1042px" %)ECB:OS_CALC(1.2.0).OS267 733 +|(% style="width:247px" %)//UserDefinedOperatorScheme//|(% style="width:649px" %)userDefinedOperatorSchemeAgencyId userDefinedOperatorSchemeId(version)|(% style="width:1042px" %)ECB:OS_CALC(1.2.0) 734 +|(% style="width:247px" %)//ValueList//|(% style="width:649px" %)valuelistAgencyId:valuelistId(version)|(% style="width:1042px" %)SDMX:VLIST(1.0.0) 735 +|(% style="width:247px" %)VtlCodelistMapping|(% style="width:649px" %)vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlCodelistMappingId|(% style="width:1042px" %)ECB:CLIST_MP(2.0.0).ABZ 736 +|(% style="width:247px" %)VtlConceptMapping|(% style="width:649px" %)vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlConceptMappingId|(% style="width:1042px" %)ECB:CLIST_MP(1.0.0).XYA 737 +|(% style="width:247px" %)VtlDataflowMapping|(% style="width:649px" %)vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlDataflowMappingId|(% style="width:1042px" %)ECB:CLIST_MP(1.0.0).MOQ 738 +|(% style="width:247px" %)//VtlMappingScheme//|(% style="width:649px" %)vtlMappingSchemeAgencyId VtlMappingSchemeId(version)|(% style="width:1042px" %)ECB:CLIST_MP(2.0.0) 756 756 757 757 **Table 3: Table of identification components for SDMX Identifiable Artefacts** 758 758 ... ... @@ -776,62 +776,54 @@ 776 776 777 777 The following table lists the Maintainable Artefacts. 778 778 779 -|(% colspan="2" %)**Maintainable Artefacts**|**Content** 780 -|**Abstract Class**|**Concrete Class**| 781 -|Item Scheme|Codelist|Code 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 796 -|Enumerated List|ValueList|Value Item 797 -|Structure|Data Structure Definition|((( 762 +(% style="width:881.294px" %) 763 +|(% colspan="2" style="width:522px" %)**Maintainable Artefacts**|(% style="width:490px" %)**Content** 764 +|(% style="width:198px" %)**Abstract Class**|(% style="width:324px" %)**Concrete Class**|(% style="width:490px" %) 765 +|(% style="width:198px" %)Item Scheme|(% style="width:324px" %)Codelist|(% style="width:490px" %)Code 766 +|(% style="width:198px" %) |(% style="width:324px" %)Concept Scheme|(% style="width:490px" %)Concept 767 +|(% style="width:198px" %) |(% style="width:324px" %)Category Scheme|(% style="width:490px" %)Category 768 +|(% style="width:198px" %) |(% style="width:324px" %)Organisation Unit Scheme|(% style="width:490px" %)Organisation Unit 769 +|(% style="width:198px" %) |(% style="width:324px" %)Agency Scheme|(% style="width:490px" %)Agency 770 +|(% style="width:198px" %) |(% style="width:324px" %)Data Provider Scheme|(% style="width:490px" %)Data Provider 771 +|(% style="width:198px" %) |(% style="width:324px" %)Metadata Provider Scheme|(% style="width:490px" %)Metadata Provider 772 +|(% style="width:198px" %) |(% style="width:324px" %)Data Consumer Scheme|(% style="width:490px" %)Data Consumer 773 +|(% style="width:198px" %) |(% style="width:324px" %)Reporting Taxonomy|(% style="width:490px" %)Reporting Category 774 +|(% style="width:198px" %) |(% style="width:324px" %)Transformation Scheme|(% style="width:490px" %)Transformation 775 +|(% style="width:198px" %) |(% style="width:324px" %)Custom Type Scheme|(% style="width:490px" %)Custom Type 776 +|(% style="width:198px" %) |(% style="width:324px" %)Name Personalisation Scheme|(% style="width:490px" %)Name Personalisation 777 +|(% style="width:198px" %) |(% style="width:324px" %)Vtl Mapping Scheme|(% style="width:490px" %)Vtl Codelist Mapping Vtl Concept Mapping 778 +|(% style="width:198px" %) |(% style="width:324px" %)Ruleset Scheme|(% style="width:490px" %)Ruleset 779 +|(% style="width:198px" %) |(% style="width:324px" %)User Defined Operator Scheme|(% style="width:490px" %)User Defined Operator 780 +|(% style="width:198px" %)Enumerated List|(% style="width:324px" %)ValueList|(% style="width:490px" %)Value Item 781 +|(% style="width:198px" %)Structure|(% style="width:324px" %)Data Structure Definition|(% style="width:490px" %)((( 798 798 Dimension Descriptor 799 - 800 800 Group Dimension Descriptor 801 - 802 802 Dimension 803 - 804 804 Time Dimension 805 - 806 806 Attribute Descriptor 807 - 808 808 Data Attribute 809 - 810 810 Measure Descriptor 811 - 812 812 Measure 813 813 ))) 814 -| |Metadata Structure Definition|Metadata Attribute Descriptor Metadata Attribute 815 -|Structure Usage|Dataflow| 816 -| |Metadataflow| 817 -|None|Process|Process Step 818 -|None|Structure Map|((( 791 +|(% style="width:198px" %) |(% style="width:324px" %)Metadata Structure Definition|(% style="width:490px" %)Metadata Attribute Descriptor Metadata Attribute 792 +|(% style="width:198px" %)Structure Usage|(% style="width:324px" %)Dataflow|(% style="width:490px" %) 793 +|(% style="width:198px" %) |(% style="width:324px" %)Metadataflow|(% style="width:490px" %) 794 +|(% style="width:198px" %)None|(% style="width:324px" %)Process|(% style="width:490px" %)Process Step 795 +|(% style="width:198px" %)None|(% style="width:324px" %)Structure Map|(% style="width:490px" %)((( 819 819 Component Map 820 - 821 821 Epoch Map 822 - 823 823 Date Pattern Map 824 824 ))) 825 -|None|Representation Map|Representation Mapping 826 -|Item Scheme Map|Organisation Scheme Map|Item Map 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| 832 -|None|Hierarchy|Hierarchical Code 833 -|None|Hierarchy Association| 834 -|None|Categorisation| 800 +|(% style="width:198px" %)None|(% style="width:324px" %)Representation Map|(% style="width:490px" %)Representation Mapping 801 +|(% style="width:198px" %)Item Scheme Map|(% style="width:324px" %)Organisation Scheme Map|(% style="width:490px" %)Item Map 802 +|(% style="width:198px" %) |(% style="width:324px" %)Concept Scheme Map|(% style="width:490px" %)Item Map 803 +|(% style="width:198px" %) |(% style="width:324px" %)Category Scheme Map|(% style="width:490px" %)Item Map 804 +|(% style="width:198px" %) |(% style="width:324px" %)Reporting Taxonomy Map|(% style="width:490px" %)Item Map 805 +|(% style="width:198px" %)None|(% style="width:324px" %)Provision Agreement|(% style="width:490px" %) 806 +|(% style="width:198px" %)None|(% style="width:324px" %)Metadata Provision Agreement|(% style="width:490px" %) 807 +|(% style="width:198px" %)None|(% style="width:324px" %)Hierarchy|(% style="width:490px" %)Hierarchical Code 808 +|(% style="width:198px" %)None|(% style="width:324px" %)Hierarchy Association|(% style="width:490px" %) 809 +|(% style="width:198px" %)None|(% style="width:324px" %)Categorisation|(% style="width:490px" %) 835 835 836 836 **Table 4: Table of Maintainable Artefacts for Structural Definition Metadata** 837 837 ... ... @@ -839,14 +839,11 @@ 839 839 840 840 The artefacts included in the structural definitions are: 841 841 842 -• 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) 817 +* 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) 818 +* All types of Enumerated List (ValueList){{footnote}}Note that Codelist is also an EnumeratedList.{{/footnote}} 819 +* All types of Structure (Data Structure Definition, Metadata Structure Definition) 820 +* All types of Structure Usage (Dataflow, Metadataflow) 843 843 844 -• All types of Enumerated List (ValueList)^^[[(% class="wikiinternallink wikiinternallink" %)^^3^^>>path:#sdfootnote3sym||name="sdfootnote3anc"]](%%)^^ 845 - 846 -• All types of Structure (Data Structure Definition, Metadata Structure Definition) 847 - 848 -• All types of Structure Usage (Dataflow, Metadataflow) 849 - 850 850 ===== {{id name="_Toc93865"/}}7.1.3 Structure Usage ===== 851 851 852 852 **7.1.3.1 Structure Usage: Basic Concepts** ... ... @@ -1186,3 +1186,5 @@ 1186 1186 IMF.SubAgency1 1187 1187 1188 1188 [[3>>path:#sdfootnote3anc||name="sdfootnote3sym"]] Note that Codelist is also an EnumeratedList. 1161 + 1162 +{{putFootnotes/}}
- 1747307906944-697.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.helena - Size
-
... ... @@ -1,0 +1,1 @@ 1 +37.9 KB - Content