Skip to Content
Last modified by Helena on 2025/09/10 11:19
From version 1.5
edited by Helena
on 2025/05/21 13:47
Change comment: There is no comment for this version
To version 2.6
edited by Helena
on 2025/05/21 14:26
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -340,8 +340,8 @@
340 340  
341 341  The following table defines the behaviour of the SDMX Registry for the various Registry Interface messages.
342 342  
343 -|(% style="width:143px" %)**Interface**|(% style="width:1729px" %)**Behaviour**
344 -|(% style="width:143px" %)All|(% style="width:1729px" %)(((
343 +|(% style="width:244px" %)**Interface**|**Behaviour**
344 +|(% style="width:244px" %)All|(((
345 345  1) If the action is set to “replace” then the entire contents of the existing maintainable object in the Registry MUST be replaced by the object submitted, unless the final attribute is set to “true” in which case the only changes that are allowed are to the following constructs:
346 346  
347 347  * Name – this applies to the Maintainable object and its contained elements, such a Code in a Code list.
... ... @@ -365,11 +365,10 @@
365 365  
366 366  5) The specific rules for the elements and attributes documented in the SDMX Schema MUST be obeyed.
367 367  )))
368 -|(% style="width:143px" %)SubmitStructureRequest|(% style="width:1729px" %)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.
369 -|(% style="width:143px" %)SubmitProvisioningRequest|(% style="width:1729px" %)No additional behaviour.
370 -|(% style="width:143px" %)Submit Registration Request|(% style="width:1729px" %)(((
368 +|(% style="width:244px" %)SubmitStructureRequest|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.
369 +|(% style="width:244px" %)SubmitProvisioningRequest|No additional behaviour.
370 +|(% style="width:244px" %)Submit Registration Request|(((
371 371  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.
372 -
373 373  For a queryable datasource the Registry MAY validate that the source exists and can accept an SDMX-ML data query.
374 374  )))
375 375  
... ... @@ -386,6 +386,8 @@
386 386  
387 387  === 6.1.1 Identification, Naming, Versioning, and Maintenance Model ===
388 388  
388 +[[image:1747824504225-229.png]]
389 +
389 389  **Figure 5: Class diagram of fundamental artefacts in the SDMX-IM**
390 390  
391 391  The table below shows the identification and related data attributes to be stored in a registry for objects that are one of:
... ... @@ -396,38 +396,34 @@
396 396  * Versionable
397 397  * Maintainable
398 398  
399 -|**Object Type**|**Data Attributes**|**Status**|**Data type**|**Notes**
400 -|Annotable|AnnotationTitle|C|string|
401 -| |AnnotationType|C|string|
402 -| |AnnotationURN|C|string|
403 -| |(((
404 -AnnotationText in the form of
400 +(% style="width:935.294px" %)
401 +|**Object Type**|(% style="width:244px" %)**Data Attributes**|(% style="width:99px" %)**Status**|**Data type**|(% style="width:389px" %)**Notes**
402 +|Annotable|(% style="width:244px" %)AnnotationTitle|(% style="width:99px" %)C|string|(% style="width:389px" %)
403 +| |(% style="width:244px" %)AnnotationType|(% style="width:99px" %)C|string|(% style="width:389px" %)
404 +| |(% style="width:244px" %)AnnotationURN|(% style="width:99px" %)C|string|(% style="width:389px" %)
405 +| |(% style="width:244px" %)(((
406 +AnnotationText in the form of International String
407 +)))|(% style="width:99px" %)C| |(% style="width:389px" %)This can have languagespecific variants.
408 +|Identifiable|(% style="width:244px" %)all content as for Annotable plus|(% style="width:99px" %) | |(% style="width:389px" %)
409 +| |(% style="width:244px" %)id|(% style="width:99px" %)M|string|(% style="width:389px" %)
410 +| |(% style="width:244px" %)uri|(% style="width:99px" %)C|string|(% style="width:389px" %)
411 +| |(% style="width:244px" %)urn|(% style="width:99px" %)C|string|(% style="width:389px" %)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.
412 +|Nameable|(% style="width:244px" %)all content as for Identifiable plus|(% style="width:99px" %) | |(% style="width:389px" %)
413 +| |(% style="width:244px" %)Name in the form of International String|(% style="width:99px" %)M|string|(% style="width:389px" %)This can have languagespecific variants.
414 +| |(% style="width:244px" %)(((
415 +Description in the form of International String
416 +)))|(% style="width:99px" %)C|string|(% style="width:389px" %)This can have languagespecific variants.
417 +|Versionable|(% style="width:244px" %)All content as for Identifiable plus|(% style="width:99px" %) | |(% style="width:389px" %)
418 +| |(% style="width:244px" %)version|(% style="width:99px" %)C|string|(% style="width:389px" %)This is the version number. If not present the default is 1.0
419 +| |(% style="width:244px" %)validFrom|(% style="width:99px" %)C|Date/time|(% style="width:389px" %)
420 +| |(% style="width:244px" %)validTo|(% style="width:99px" %)C|Date/time|(% style="width:389px" %)
421 +|Maintainable|(% style="width:244px" %)All content as for Versionable plus|(% style="width:99px" %) | |(% style="width:389px" %)
422 +| |(% style="width:244px" %)final|(% style="width:99px" %) |boolean|(% style="width:389px" %)Value of “true” indicates that this is a final specification and it cannot be changed except as a new version. Note that providing a “final’ object is not referenced from another object then it may be deleted.
423 +| |(% style="width:244px" %)isExternalReference|(% style="width:99px" %)C|boolean|(% style="width:389px" %)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 structureURI, each of which must return a valid SDMX-ML file.
424 +| |(% style="width:244px" %)serviceURL|(% style="width:99px" %)C|string|(% style="width:389px" %)The url of the service that can be queried for this resource
425 +| |(% style="width:244px" %)structureURL|(% style="width:99px" %)C|string|(% style="width:389px" %)The url of the resource.
426 +| |(% style="width:244px" %)(Maintenance) agencyId|(% style="width:99px" %)M|string|(% style="width:389px" %)The object must be linked to a maintenance agency.
405 405  
406 -International String
407 -)))|C| |This can have languagespecific variants.
408 -| | | | |
409 -|Identifiable|all content as for Annotable plus| | |
410 -| |id|M|string|
411 -| |uri|C|string|
412 -| |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.
413 -|Nameable|all content as for Identifiable plus| | |
414 -| |Name in the form of International String|M|string|This can have languagespecific variants.
415 -| |(((
416 -Description in the form of International
417 -
418 -String
419 -)))|C|string|This can have languagespecific variants.
420 -|Versionable|All content as for Identifiable plus| | |
421 -| |version|C|string|This is the version number. If not present the default is 1.0
422 -| |validFrom|C|Date/time|
423 -| |validTo|C|Date/time|
424 -|Maintainable|All content as for Versionable plus| | |
425 -| |final| |boolean|Value of “true” indicates that this is a final specification and it cannot be changed except as a new version. Note that providing a “final’ object is not referenced from another object then it may be deleted.
426 -| |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 structureURI, each of which must return a valid SDMX-ML file.
427 -| |serviceURL|C|string|The url of the service that can be queried for this resource
428 -| |structureURL|C|string|The url of the resource.
429 -| |(Maintenance) agencyId|M|string|The object must be linked to a maintenance agency.
430 -
431 431  **Table 1: Common Attributes of Object Types**
432 432  
433 433  == 6.2 Unique identification of SDMX objects ==
... ... @@ -472,11 +472,11 @@
472 472  
473 473  An example of this is shown in the XML snippet below.
474 474  
472 +[[image:1747824123013-196.jpeg||height="309" width="446"]]
475 475  
476 -[[image:1747824123013-196.jpeg]]
474 +(% class="wikigeneratedid" id="HFigure8:ExampleShowingUseofAgencyIdentifiers" %)
475 +**Figure 8: Example Showing Use of Agency Identifiers**
477 477  
478 -==== Figure 8: Example Showing Use of Agency Identifiers ====
479 -
480 480  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.
481 481  
482 482  === 6.2.2 Universal Resource Name (URN) ===
... ... @@ -515,10 +515,8 @@
515 515  
516 516  **(maintainable-object-version)** is the version of the maintainable object and is enclosed in round brackets (). It will always be present.
517 517  
518 -**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 (Code List) and has no intermediary container object, whereas a Metadata Attribute has an intermediary container object (Report Structure) and may have an intermediary container object which is its parent Metadata Attribute. 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 Attribute Descriptor, Dimension Descriptor, and Measure Descriptor where there can be only one such object and this object has a fixed id. Therefore, whilst each of these has a
515 +**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 (Code List) and has no intermediary container object, whereas a Metadata Attribute has an intermediary container object (Report Structure) and may have an intermediary container object which is its parent Metadata Attribute. 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 Attribute Descriptor, Dimension Descriptor, and Measure Descriptor 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 Attribute Descriptor, Dimension Descriptor, and Measure Descriptor is not included when the actual object is a Data Attribute or a Dimension/Measure Dimension/ Time Dimension, or a Measure.
519 519  
520 -URN, the id of the Attribute Descriptor, Dimension Descriptor, and Measure Descriptor is not included when the actual object is a Data Attribute or a Dimension/Measure Dimension/ Time Dimension, or a Measure.
521 -
522 522  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 container-object-id.
523 523  
524 524  For example the sequence is agency:DSDid(version).DimensionId and not agency:DSDid(version).DimensionDescriptorId.DimensionId.
... ... @@ -525,58 +525,57 @@
525 525  
526 526  **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.
527 527  
528 -===== //Generic Examples of the URN Structure// =====
523 +===== __**//Generic Examples of the URN Structure//**__ =====
529 529  
525 +__Actual object is a maintainable__
530 530  
531 -Actual object is a maintainable
527 +> SDMXPrefix.SDMX-IM package name.classname=agency id:maintained-object-id(version)
532 532  
533 -SDMXPrefix.SDMX-IM package name.classname=agency id:maintained-object-id(version)
529 +__Actual object is contained in a maintained object with no intermediate containing object__
534 534  
535 -Actual object is contained in a maintained object with no intermediate containing object
531 +> SDMXPrefix.SDMX-IM package name.classname=agency id:maintained-object-id(version).object-id
536 536  
537 -SDMXPrefix.SDMX-IM package name.classname=agency id:maintained-object-id(version).object-id
533 +__Actual object is contained in a maintained object with an intermediate containing object__
538 538  
539 -Actual object is contained in a maintained object with an intermediate containing object
535 +> SDMXPrefix.SDMX-IM package name.classname=agency
540 540  
541 -SDMXPrefix.SDMX-IM package name.classname=agency
542 -
543 543  id:maintained-object-id(version).contained-object-id.object-id
544 544  
545 -Actual object is contained in a maintained object with no intermediate containing object but the object type itself is hierarchical
539 +__Actual object is contained in a maintained object with no intermediate containing object but the object type itself is hierarchical__
546 546  
547 547  In this case the object id may not be unique in itself but only within the context of the hierarchy. In the general syntax of the URN all intermediary objects in the structure (with the exception, of course, of the maintained object) are shown as a contained object. An example here would be a Category in a Category Scheme. The Category is hierarchical and all intermediate Categories are shown as a contained object. The example below shows the generic structure for Category Scheme/Category/Category
548 548  
549 -SDMXPrefix.SDMX-IM package name.classname=agency id:maintained-object-id(version).contained-object-id.object-id
543 +> SDMXPrefix.SDMX-IM package name.classname=agency id:maintained-object-id(version).contained-object-id.object-id
550 550  
551 -Actual object is contained in a maintained object with an intermediate containing object and the object type itself is hierarchical
545 +__Actual object is contained in a maintained object with an intermediate containing object and the object type itself is hierarchical__
552 552  
553 553  In this case the generic syntax is the same as for the example above as the parent object is regarded as a containing object, even if it is of the same type. An example here is a Metadata Attribute where the contained objects are Report Structure (first contained object id) and Metadata Attribute (subsequent contained object Ids). The example below shows the generic structure for MSD/Report Structure/Metadata Attribute/Metadata Attribute
554 554  
555 -SDMXPrefix.SDMX-IM package name.classname=agency id:maintained-object-id(version).contained-object-id. contained-object-id contained-object-id.object-id
549 +> SDMXPrefix.SDMX-IM package name.classname=agency id:maintained-object-id(version).contained-object-id. contained-object-id contained-object-id.object-id
556 556  
557 -===== //Concrete Examples of the URN Structure// =====
551 +===== __**//Concrete Examples of the URN Structure//**__ =====
558 558  
559 559  The Data Structure Definition CRED_EXT_DEBT version 1.0 maintained by the top level Agency TFFS would have the URN:
560 560  
561 -urn:sdmx:org.sdmx.infomodel.datastructure.DataStucture=TFFS:CRED_EXT_ DEBT(1.0)
555 +> urn:sdmx:org.sdmx.infomodel.datastructure.DataStucture=TFFS:CRED_EXT_ DEBT(1.0)
562 562  
563 563  The URN for a code for Argentina maintained by ISO in the code list CL_3166A2 version 1.0 would be:
564 564  
565 -urn:sdmx:org.sdmx.infomodel.codelist.Code=ISO:CL_3166A2(1.0).AR
559 +> urn:sdmx:org.sdmx.infomodel.codelist.Code=ISO:CL_3166A2(1.0).AR
566 566  
567 567  The URN for a category (id of 1) which has parent category (id of 2) maintained by SDMX in the category scheme SUBJECT_MATTER_DOMAINS version 1.0 would be:
568 568  
569 -urn:sdmx:org.sdmx.infomodel.categoryscheme.Category=SDMX:SUBJE CT_MATTER_DOMAINS(1.0).1.2
563 +> urn:sdmx:org.sdmx.infomodel.categoryscheme.Category=SDMX:SUBJE CT_MATTER_DOMAINS(1.0).1.2
570 570  
571 571  The URN for a Metadata Attribute maintained by SDMX in the MSD CONTACT_METADATA version 1.0 in the Report Structure CONTACT_REPORT where the hierarchy of the Metadata Attribute is
572 572  
573 573  CONTACT_DETAILS/CONTACT_NAME would be:
574 574  
575 -urn:sdmx:org.sdmx.infomodel.metadatastructure.MetadataAttribut e=SDMX:CONTACT_METADATA(1.0).CONTACT_REPORT.CONTACT_DETAILS.CO NTACT_NAME
569 +> urn:sdmx:org.sdmx.infomodel.metadatastructure.MetadataAttribut e=SDMX:CONTACT_METADATA(1.0).CONTACT_REPORT.CONTACT_DETAILS.CO NTACT_NAME
576 576  
577 577  The TFFS defines ABC as a sub Agency of TFFS then the URN of a Dataflow maintained by ABC and identified as EXTERNAL_DEBT version 1.0 would be:
578 578  
579 -urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=TFFS.ABC:EX
573 +> urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=TFFS.ABC:EX
580 580  
581 581  TERNAL_DEBT(1.0)
582 582  
... ... @@ -591,112 +591,94 @@
591 591  
592 592  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.
593 593  
594 -|**Package**|(((
595 -**URN Classname (model classname**
596 -
597 -**where this is different)**
588 +|(% style="width:127px" %)**Package**|(% style="width:1745px" %)(((
589 +**URN Classname (model classname where this is different)**
598 598  )))
599 -|base|Agency
600 -| |OrganisationUnitScheme
601 -| |AgencyScheme
602 -| |DataProviderScheme
603 -| |DataConsumerScheme
604 -| |OrganisationUnit
605 -| |DataProvider
606 -| |DataConsumer
607 -| |
608 -|datastructure|DataStructure (DataStructureDefinition)
609 -| |AttributeDescriptor
610 -| |DataAttribute
611 -| |GroupDimensionDescriptor
612 -| |DimensionDescriptor
613 -| |Dimension
614 -| |MeasureDimension
615 -| |TimeDimension
616 -| |MeasureDescriptor
617 -| |PrimaryMeasure
618 -| |Dataflow (DataflowDefinition)
619 -| |
620 -|metadatastructure|MetadataTarget
621 -| |DimensionDescriptorValueTarget
622 -| |IdentifiableObjectTarget
623 -| |ReportPeriodTarget
624 -| |DataSetTarget
625 -| |ReportStructure
626 -| |MetadataAttribute
627 -| |(((
591 +|(% style="width:127px" %)base|(% style="width:45px" %)Agency
592 +|(% style="width:127px" %) |(% style="width:45px" %)OrganisationUnitScheme
593 +|(% style="width:127px" %) |(% style="width:45px" %)AgencyScheme
594 +|(% style="width:127px" %) |(% style="width:45px" %)DataProviderScheme
595 +|(% style="width:127px" %) |(% style="width:45px" %)DataConsumerScheme
596 +|(% style="width:127px" %) |(% style="width:45px" %)OrganisationUnit
597 +|(% style="width:127px" %) |(% style="width:45px" %)DataProvider
598 +|(% style="width:127px" %) |(% style="width:45px" %)DataConsumer
599 +|(% style="width:127px" %)datastructure|(% style="width:45px" %)DataStructure (DataStructureDefinition)
600 +|(% style="width:127px" %) |(% style="width:45px" %)AttributeDescriptor
601 +|(% style="width:127px" %) |(% style="width:45px" %)DataAttribute
602 +|(% style="width:127px" %) |(% style="width:45px" %)GroupDimensionDescriptor
603 +|(% style="width:127px" %) |(% style="width:45px" %)DimensionDescriptor
604 +|(% style="width:127px" %) |(% style="width:45px" %)Dimension
605 +|(% style="width:127px" %) |(% style="width:45px" %)MeasureDimension
606 +|(% style="width:127px" %) |(% style="width:45px" %)TimeDimension
607 +|(% style="width:127px" %) |(% style="width:45px" %)MeasureDescriptor
608 +|(% style="width:127px" %) |(% style="width:45px" %)PrimaryMeasure
609 +|(% style="width:127px" %) |(% style="width:45px" %)Dataflow (DataflowDefinition)
610 +|(% style="width:127px" %)metadatastructure|(% style="width:45px" %)MetadataTarget
611 +|(% style="width:127px" %) |(% style="width:45px" %)DimensionDescriptorValueTarget
612 +|(% style="width:127px" %) |(% style="width:45px" %)IdentifiableObjectTarget
613 +|(% style="width:127px" %) |(% style="width:45px" %)ReportPeriodTarget
614 +|(% style="width:127px" %) |(% style="width:45px" %)DataSetTarget
615 +|(% style="width:127px" %) |(% style="width:45px" %)ReportStructure
616 +|(% style="width:127px" %) |(% style="width:45px" %)MetadataAttribute
617 +|(% style="width:127px" %) |(% style="width:45px" %)(((
628 628  MetadataStructure
629 629  
630 630  (MetadataStructureDefinition)
631 631  )))
632 -| |Metadataflow (MetadataflowDefinition)
633 -| |
634 -|process|Process
635 -| |ProcessStep
636 -| |Transition
637 -| |
638 -|registry|ProvisionAgreement
639 -| |AttachmentConstraint
640 -| |ContentConstraint
641 -| |Subscription
642 -| |
643 -|mapping|StructureMap
644 -| |StructureSet
645 -| |ComponentMap
646 -|**Package**|(((
647 -**URN Classname (model classname**
622 +|(% style="width:127px" %) |(% style="width:45px" %)Metadataflow (MetadataflowDefinition)
623 +|(% style="width:127px" %)process|(% style="width:45px" %)Process
624 +|(% style="width:127px" %) |(% style="width:45px" %)ProcessStep
625 +|(% style="width:127px" %) |(% style="width:45px" %)Transition
626 +|(% style="width:127px" %)registry|(% style="width:45px" %)ProvisionAgreement
627 +|(% style="width:127px" %) |(% style="width:45px" %)AttachmentConstraint
628 +|(% style="width:127px" %) |(% style="width:45px" %)ContentConstraint
629 +|(% style="width:127px" %) |(% style="width:45px" %)Subscription
630 +|(% style="width:127px" %)mapping|(% style="width:45px" %)StructureMap
631 +|(% style="width:127px" %) |(% style="width:45px" %)StructureSet
632 +|(% style="width:127px" %) |(% style="width:45px" %)ComponentMap
633 +|(% style="width:127px" %) |(% style="width:1745px" %)ConceptSchemeMap
634 +|(% style="width:127px" %) |(% style="width:1745px" %)OrganisationSchemeMap
635 +|(% style="width:127px" %) |(% style="width:1745px" %)CodelistMap
636 +|(% style="width:127px" %) |(% style="width:1745px" %)CategorySchemeMap
637 +|(% style="width:127px" %) |(% style="width:1745px" %)ReportingTaxonomyMap
638 +|(% style="width:127px" %) |(% style="width:1745px" %)ConceptMap
639 +|(% style="width:127px" %) |(% style="width:1745px" %)OrganisationMap
640 +|(% style="width:127px" %) |(% style="width:1745px" %)CodeMap
641 +|(% style="width:127px" %) |(% style="width:1745px" %)HybridCodelistMap
642 +|(% style="width:127px" %) |(% style="width:1745px" %)CategoryMap
643 +|(% style="width:127px" %) |(% style="width:1745px" %)HybridCodeMap
644 +|(% style="width:127px" %) |(% style="width:1745px" %)ReportingCategoryMap
645 +|(% style="width:127px" %)codelist|(% style="width:1745px" %)Codelist
646 +|(% style="width:127px" %) |(% style="width:1745px" %)HierarchicalCodelist
647 +|(% style="width:127px" %) |(% style="width:1745px" %)Hierarchy
648 +|(% style="width:127px" %) |(% style="width:1745px" %)Hierarchy
649 +|(% style="width:127px" %) |(% style="width:1745px" %)Code
650 +|(% style="width:127px" %) |(% style="width:1745px" %)HierarchicalCode
651 +|(% style="width:127px" %) |(% style="width:1745px" %)Level
652 +|(% style="width:127px" %)categoryscheme|(% style="width:1745px" %)CategoryScheme
653 +|(% style="width:127px" %) |(% style="width:1745px" %)Category
654 +|(% style="width:127px" %) |(% style="width:1745px" %)Categorisation
655 +|(% style="width:127px" %) |(% style="width:1745px" %)ReportingTaxonomy
656 +|(% style="width:127px" %) |(% style="width:1745px" %)ReportingCategory
657 +|(% style="width:127px" %)conceptscheme|(% style="width:1745px" %)ConceptScheme
658 +|(% style="width:127px" %) |(% style="width:1745px" %)Concept
659 +|(% style="width:127px" %)transformation|(% style="width:1745px" %)TransformationScheme
660 +|(% style="width:127px" %) |(% style="width:1745px" %)Transformation
661 +|(% style="width:127px" %) |(% style="width:1745px" %)CustomTypeScheme
662 +|(% style="width:127px" %) |(% style="width:1745px" %)CustomType
663 +|(% style="width:127px" %) |(% style="width:1745px" %)NamePersonalisationScheme
664 +|(% style="width:127px" %) |(% style="width:1745px" %)NamePersonalisation
665 +|(% style="width:127px" %) |(% style="width:1745px" %)VtlCodelistMapping
666 +|(% style="width:127px" %) |(% style="width:1745px" %)VtlConceptMapping
667 +|(% style="width:127px" %) |(% style="width:1745px" %)VtlDataflowMapping
668 +|(% style="width:127px" %) |(% style="width:1745px" %)VtlConceptSchemeMapping
669 +|(% style="width:127px" %) |(% style="width:1745px" %)RulesetScheme
670 +|(% style="width:127px" %) |(% style="width:1745px" %)Ruleset
671 +|(% style="width:127px" %) |(% style="width:1745px" %)UserDefinedOperatorScheme
672 +|(% style="width:127px" %) |(% style="width:1745px" %)UserDefinedOperator
648 648  
649 -**where this is different)**
650 -)))
651 -| |ConceptSchemeMap
652 -| |OrganisationSchemeMap
653 -| |CodelistMap
654 -| |CategorySchemeMap
655 -| |ReportingTaxonomyMap
656 -| |ConceptMap
657 -| |OrganisationMap
658 -| |CodeMap
659 -| |HybridCodelistMap
660 -| |CategoryMap
661 -| |HybridCodeMap
662 -| |ReportingCategoryMap
663 -| |
664 -|codelist|Codelist
665 -| |HierarchicalCodelist
666 -| |Hierarchy
667 -| |Hierarchy
668 -| |Code
669 -| |HierarchicalCode
670 -| |Level
671 -| |
672 -|categoryscheme|CategoryScheme
673 -| |Category
674 -| |Categorisation
675 -| |ReportingTaxonomy
676 -| |ReportingCategory
677 -| |
678 -|conceptscheme|ConceptScheme
679 -| |Concept
680 -| |
681 -|transformation|TransformationScheme
682 -| |Transformation
683 -| |CustomTypeScheme
684 -| |CustomType
685 -| |NamePersonalisationScheme
686 -| |NamePersonalisation
687 -| |VtlCodelistMapping
688 -| |VtlConceptMapping
689 -| |VtlDataflowMapping
690 -| |VtlConceptSchemeMapping
691 -| |RulesetScheme
692 -| |Ruleset
693 -| |UserDefinedOperatorScheme
694 -| |UserDefinedOperator
695 -| |
696 -
697 697  **Table 2: SDMX-IM Packages and Contained Classes**
698 698  
699 -
700 700  === 6.2.4 URN Identification components of SDMX objects ===
701 701  
702 702  The table below describes the identification components for all SDMX object types that have identification. Note the actual attributes are all Id, but have been prefixed by their class name or multiple class names to show navigation, e.g. conceptSchemeAgencyId is really the Id attribute of the Agency class that is associated to the ConceptScheme.
1747824504225-229.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +52.8 KB
Content