Skip to Content
Last modified by Helena on 2025/09/10 11:19
From version 2.3
edited by Helena
on 2025/05/21 14:19
Change comment: There is no comment for this version
To version 2.7
edited by Helena
on 2025/05/21 14:27
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -524,15 +524,15 @@
524 524  
525 525  __Actual object is a maintainable__
526 526  
527 -SDMXPrefix.SDMX-IM package name.classname=agency id:maintained-object-id(version)
527 +> SDMXPrefix.SDMX-IM package name.classname=agency id:maintained-object-id(version)
528 528  
529 529  __Actual object is contained in a maintained object with no intermediate containing object__
530 530  
531 -SDMXPrefix.SDMX-IM package name.classname=agency id:maintained-object-id(version).object-id
531 +> SDMXPrefix.SDMX-IM package name.classname=agency id:maintained-object-id(version).object-id
532 532  
533 533  __Actual object is contained in a maintained object with an intermediate containing object__
534 534  
535 -SDMXPrefix.SDMX-IM package name.classname=agency
535 +> SDMXPrefix.SDMX-IM package name.classname=agency
536 536  
537 537  id:maintained-object-id(version).contained-object-id.object-id
538 538  
... ... @@ -540,37 +540,37 @@
540 540  
541 541  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
542 542  
543 -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
544 544  
545 545  __Actual object is contained in a maintained object with an intermediate containing object and the object type itself is hierarchical__
546 546  
547 547  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
548 548  
549 -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
550 550  
551 -===== //Concrete Examples of the URN Structure// =====
551 +===== __**//Concrete Examples of the URN Structure//**__ =====
552 552  
553 553  The Data Structure Definition CRED_EXT_DEBT version 1.0 maintained by the top level Agency TFFS would have the URN:
554 554  
555 -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)
556 556  
557 557  The URN for a code for Argentina maintained by ISO in the code list CL_3166A2 version 1.0 would be:
558 558  
559 -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
560 560  
561 561  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:
562 562  
563 -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
564 564  
565 565  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
566 566  
567 567  CONTACT_DETAILS/CONTACT_NAME would be:
568 568  
569 -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
570 570  
571 571  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:
572 572  
573 -urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=TFFS.ABC:EX
573 +> urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=TFFS.ABC:EX
574 574  
575 575  TERNAL_DEBT(1.0)
576 576  
... ... @@ -585,112 +585,94 @@
585 585  
586 586  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.
587 587  
588 -|**Package**|(((
589 -**URN Classname (model classname**
590 -
591 -**where this is different)**
588 +|(% style="width:127px" %)**Package**|(% style="width:1745px" %)(((
589 +**URN Classname (model classname where this is different)**
592 592  )))
593 -|base|Agency
594 -| |OrganisationUnitScheme
595 -| |AgencyScheme
596 -| |DataProviderScheme
597 -| |DataConsumerScheme
598 -| |OrganisationUnit
599 -| |DataProvider
600 -| |DataConsumer
601 -| |
602 -|datastructure|DataStructure (DataStructureDefinition)
603 -| |AttributeDescriptor
604 -| |DataAttribute
605 -| |GroupDimensionDescriptor
606 -| |DimensionDescriptor
607 -| |Dimension
608 -| |MeasureDimension
609 -| |TimeDimension
610 -| |MeasureDescriptor
611 -| |PrimaryMeasure
612 -| |Dataflow (DataflowDefinition)
613 -| |
614 -|metadatastructure|MetadataTarget
615 -| |DimensionDescriptorValueTarget
616 -| |IdentifiableObjectTarget
617 -| |ReportPeriodTarget
618 -| |DataSetTarget
619 -| |ReportStructure
620 -| |MetadataAttribute
621 -| |(((
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" %)(((
622 622  MetadataStructure
623 623  
624 624  (MetadataStructureDefinition)
625 625  )))
626 -| |Metadataflow (MetadataflowDefinition)
627 -| |
628 -|process|Process
629 -| |ProcessStep
630 -| |Transition
631 -| |
632 -|registry|ProvisionAgreement
633 -| |AttachmentConstraint
634 -| |ContentConstraint
635 -| |Subscription
636 -| |
637 -|mapping|StructureMap
638 -| |StructureSet
639 -| |ComponentMap
640 -|**Package**|(((
641 -**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
642 642  
643 -**where this is different)**
644 -)))
645 -| |ConceptSchemeMap
646 -| |OrganisationSchemeMap
647 -| |CodelistMap
648 -| |CategorySchemeMap
649 -| |ReportingTaxonomyMap
650 -| |ConceptMap
651 -| |OrganisationMap
652 -| |CodeMap
653 -| |HybridCodelistMap
654 -| |CategoryMap
655 -| |HybridCodeMap
656 -| |ReportingCategoryMap
657 -| |
658 -|codelist|Codelist
659 -| |HierarchicalCodelist
660 -| |Hierarchy
661 -| |Hierarchy
662 -| |Code
663 -| |HierarchicalCode
664 -| |Level
665 -| |
666 -|categoryscheme|CategoryScheme
667 -| |Category
668 -| |Categorisation
669 -| |ReportingTaxonomy
670 -| |ReportingCategory
671 -| |
672 -|conceptscheme|ConceptScheme
673 -| |Concept
674 -| |
675 -|transformation|TransformationScheme
676 -| |Transformation
677 -| |CustomTypeScheme
678 -| |CustomType
679 -| |NamePersonalisationScheme
680 -| |NamePersonalisation
681 -| |VtlCodelistMapping
682 -| |VtlConceptMapping
683 -| |VtlDataflowMapping
684 -| |VtlConceptSchemeMapping
685 -| |RulesetScheme
686 -| |Ruleset
687 -| |UserDefinedOperatorScheme
688 -| |UserDefinedOperator
689 -| |
690 -
691 691  **Table 2: SDMX-IM Packages and Contained Classes**
692 692  
693 -
694 694  === 6.2.4 URN Identification components of SDMX objects ===
695 695  
696 696  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.
... ... @@ -699,9 +699,8 @@
699 699  
700 700  Note that for brevity the URN examples omit the prefix. All URNs have the prefix
701 701  
702 -urn:sdmx.org.sdmx.infomodel.{package}.{classname}=
684 +> urn:sdmx.org.sdmx.infomodel.{package}.{classname}=
703 703  
704 -
705 705  |**SDMX Class**|**Key attribute(s)**|**Example of URN**
706 706  |Agency|The URN for an Agency is shown later in this table. 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.|(((
707 707  IMF