Skip to Content
Last modified by Helena on 2025/09/10 11:19
From version 1.7
edited by Helena
on 2025/05/21 13:49
Change comment: There is no comment for this version
To version 2.9
edited by Helena
on 2025/05/21 14:40
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  
... ... @@ -470,9 +470,10 @@
470 470  
471 471  An example of this is shown in the XML snippet below.
472 472  
473 -[[image:1747824123013-196.jpeg]]
472 +[[image:1747824123013-196.jpeg||height="309" width="446"]]
474 474  
475 -==== Figure 8: Example Showing Use of Agency Identifiers ====
474 +(% class="wikigeneratedid" id="HFigure8:ExampleShowingUseofAgencyIdentifiers" %)
475 +**Figure 8: Example Showing Use of Agency Identifiers**
476 476  
477 477  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.
478 478  
... ... @@ -512,10 +512,8 @@
512 512  
513 513  **(maintainable-object-version)** is the version of the maintainable object and is enclosed in round brackets (). It will always be present.
514 514  
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
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.
516 516  
517 -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.
518 -
519 519  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.
520 520  
521 521  For example the sequence is agency:DSDid(version).DimensionId and not agency:DSDid(version).DimensionDescriptorId.DimensionId.
... ... @@ -522,58 +522,57 @@
522 522  
523 523  **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.
524 524  
525 -===== //Generic Examples of the URN Structure// =====
523 +===== __**//Generic Examples of the URN Structure//**__ =====
526 526  
525 +__Actual object is a maintainable__
527 527  
528 -Actual object is a maintainable
527 +> SDMXPrefix.SDMX-IM package name.classname=agency id:maintained-object-id(version)
529 529  
530 -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__
531 531  
532 -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
533 533  
534 -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__
535 535  
536 -Actual object is contained in a maintained object with an intermediate containing object
535 +> SDMXPrefix.SDMX-IM package name.classname=agency
537 537  
538 -SDMXPrefix.SDMX-IM package name.classname=agency
539 -
540 540  id:maintained-object-id(version).contained-object-id.object-id
541 541  
542 -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__
543 543  
544 544  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
545 545  
546 -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
547 547  
548 -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__
549 549  
550 550  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
551 551  
552 -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
553 553  
554 -===== //Concrete Examples of the URN Structure// =====
551 +===== __**//Concrete Examples of the URN Structure//**__ =====
555 555  
556 556  The Data Structure Definition CRED_EXT_DEBT version 1.0 maintained by the top level Agency TFFS would have the URN:
557 557  
558 -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)
559 559  
560 560  The URN for a code for Argentina maintained by ISO in the code list CL_3166A2 version 1.0 would be:
561 561  
562 -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
563 563  
564 564  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:
565 565  
566 -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
567 567  
568 568  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
569 569  
570 570  CONTACT_DETAILS/CONTACT_NAME would be:
571 571  
572 -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
573 573  
574 574  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:
575 575  
576 -urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=TFFS.ABC:EX
573 +> urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=TFFS.ABC:EX
577 577  
578 578  TERNAL_DEBT(1.0)
579 579  
... ... @@ -588,112 +588,94 @@
588 588  
589 589  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.
590 590  
591 -|**Package**|(((
592 -**URN Classname (model classname**
593 -
594 -**where this is different)**
588 +|(% style="width:127px" %)**Package**|(% style="width:1745px" %)(((
589 +**URN Classname (model classname where this is different)**
595 595  )))
596 -|base|Agency
597 -| |OrganisationUnitScheme
598 -| |AgencyScheme
599 -| |DataProviderScheme
600 -| |DataConsumerScheme
601 -| |OrganisationUnit
602 -| |DataProvider
603 -| |DataConsumer
604 -| |
605 -|datastructure|DataStructure (DataStructureDefinition)
606 -| |AttributeDescriptor
607 -| |DataAttribute
608 -| |GroupDimensionDescriptor
609 -| |DimensionDescriptor
610 -| |Dimension
611 -| |MeasureDimension
612 -| |TimeDimension
613 -| |MeasureDescriptor
614 -| |PrimaryMeasure
615 -| |Dataflow (DataflowDefinition)
616 -| |
617 -|metadatastructure|MetadataTarget
618 -| |DimensionDescriptorValueTarget
619 -| |IdentifiableObjectTarget
620 -| |ReportPeriodTarget
621 -| |DataSetTarget
622 -| |ReportStructure
623 -| |MetadataAttribute
624 -| |(((
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" %)(((
625 625  MetadataStructure
626 626  
627 627  (MetadataStructureDefinition)
628 628  )))
629 -| |Metadataflow (MetadataflowDefinition)
630 -| |
631 -|process|Process
632 -| |ProcessStep
633 -| |Transition
634 -| |
635 -|registry|ProvisionAgreement
636 -| |AttachmentConstraint
637 -| |ContentConstraint
638 -| |Subscription
639 -| |
640 -|mapping|StructureMap
641 -| |StructureSet
642 -| |ComponentMap
643 -|**Package**|(((
644 -**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
645 645  
646 -**where this is different)**
647 -)))
648 -| |ConceptSchemeMap
649 -| |OrganisationSchemeMap
650 -| |CodelistMap
651 -| |CategorySchemeMap
652 -| |ReportingTaxonomyMap
653 -| |ConceptMap
654 -| |OrganisationMap
655 -| |CodeMap
656 -| |HybridCodelistMap
657 -| |CategoryMap
658 -| |HybridCodeMap
659 -| |ReportingCategoryMap
660 -| |
661 -|codelist|Codelist
662 -| |HierarchicalCodelist
663 -| |Hierarchy
664 -| |Hierarchy
665 -| |Code
666 -| |HierarchicalCode
667 -| |Level
668 -| |
669 -|categoryscheme|CategoryScheme
670 -| |Category
671 -| |Categorisation
672 -| |ReportingTaxonomy
673 -| |ReportingCategory
674 -| |
675 -|conceptscheme|ConceptScheme
676 -| |Concept
677 -| |
678 -|transformation|TransformationScheme
679 -| |Transformation
680 -| |CustomTypeScheme
681 -| |CustomType
682 -| |NamePersonalisationScheme
683 -| |NamePersonalisation
684 -| |VtlCodelistMapping
685 -| |VtlConceptMapping
686 -| |VtlDataflowMapping
687 -| |VtlConceptSchemeMapping
688 -| |RulesetScheme
689 -| |Ruleset
690 -| |UserDefinedOperatorScheme
691 -| |UserDefinedOperator
692 -| |
693 -
694 694  **Table 2: SDMX-IM Packages and Contained Classes**
695 695  
696 -
697 697  === 6.2.4 URN Identification components of SDMX objects ===
698 698  
699 699  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.
... ... @@ -702,78 +702,52 @@
702 702  
703 703  Note that for brevity the URN examples omit the prefix. All URNs have the prefix
704 704  
705 -urn:sdmx.org.sdmx.infomodel.{package}.{classname}=
684 +> urn:sdmx.org.sdmx.infomodel.{package}.{classname}=
706 706  
707 -
708 -|**SDMX Class**|**Key attribute(s)**|**Example of URN**
709 -|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.|(((
686 +(% style="width:1038.29px" %)
687 +|(% style="width:191px" %)**SDMX Class**|(% style="width:413px" %)**Key attribute(s)**|(% style="width:431px" %)**Example of URN**
688 +|(% style="width:191px" %)Agency|(% style="width:413px" %)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.|(% style="width:431px" %)(((
710 710  IMF
711 -
712 -
713 713  Sub agency in the IMF AGENCIES
714 -
715 -
716 716  IMF.SubAgency1
717 717  )))
718 -|*ConceptScheme|conceptSchemeAgencyId:conceptSchemeId(ve rsion)|SDMX:CROSS_DOMAIN_CONCEPTS(1.0)
719 -|Concept|(((
720 -conceptSchemeAgencyId:
721 -
722 -conceptSchemeId(version).conceptId
723 -)))|SDMX:CROSS_DOMAIN_CONCEPTS(1.0).FREQ
724 -|*Codelist|codeListAgencyId:codeListId(version)|SDMX:CL_FREQ(1.0)
725 -|Code|codeListAgencyId:codelistId(version).codeId|(((
726 -SDMX:CL_FREQ(1.0).Q
727 -
728 -
693 +|(% style="width:191px" %)*ConceptScheme|(% style="width:413px" %)conceptSchemeAgencyId:conceptSchemeId(ve rsion)|(% style="width:431px" %)SDMX:CROSS_DOMAIN_CONCEPTS(1.0)
694 +|(% style="width:191px" %)Concept|(% style="width:413px" %)conceptSchemeAgencyId:
695 +conceptSchemeId(version).conceptId|(% style="width:431px" %)SDMX:CROSS_DOMAIN_CONCEPTS(1.0).FREQ
696 +|(% style="width:191px" %)*Codelist|(% style="width:413px" %)codeListAgencyId:codeListId(version)|(% style="width:431px" %)SDMX:CL_FREQ(1.0)
697 +|(% style="width:191px" %)Code|(% style="width:413px" %)codeListAgencyId:codelistId(version).codeId|(% style="width:431px" %)SDMX:CL_FREQ(1.0).Q
698 +|(% style="width:191px" %)(((
699 +*Hierarchical Codelist
700 +)))|(% style="width:413px" %)hierachicalCodelistAgencyId: hierarchicalCodelistId(version)|(% style="width:431px" %)(((
701 +UNESCO:CL_EXP_SOURCE(1.0(% style="background-color:transparent" %))
729 729  )))
730 -
731 -
732 -
733 -|(((
734 -*Hierarchical
735 -
736 -Codelist
737 -)))|hierachicalCodelistAgencyId: hierarchicalCodelistId(version)|(((
738 -UNESCO:CL_EXP_SOURCE(1.0)
739 -
740 -
741 -)))
742 -|Hierarchy|(((
703 +|(% style="width:191px" %)Hierarchy|(% style="width:413px" %)(((
743 743  hierachicalcodeListAgencyId:
744 -
745 745  hierarchicalcodelistId(version).Hierarchy
746 -)))|UNESCO:CL_EXP_SOURCE(1.0). H-C-GOV
747 -|Level|(((
706 +)))|(% style="width:431px" %)UNESCO:CL_EXP_SOURCE(1.0).
707 +H-C-GOV
708 +|(% style="width:191px" %)Level|(% style="width:413px" %)(((
748 748  hierachicalcodeListAgencyId:
749 -
750 750  hierarchicalcodelistId(version).Hierarchy.Level
751 -)))|(((
711 +)))|(% style="width:431px" %)(((
752 752  ESTAT:HCL_REGION(1.0).H_1.COUNTRY
753 753  
754 754  
755 755  )))
756 -|HierarchicalCode|hierachicalCodeListAgencyId: hierarchicalcodelistId(version).hierarchy.hierarc hicalCode|UNESCO:CL_EXP_SOURCE(1.0). H-C-GOV.GOV_CODE1
757 -|*DataStructure|dataStructureDefintitionAgencyId: dataStructureDefintitionId(version)|TFFS:EXT_DEBT(1.0)
758 -|(((
716 +|(% style="width:191px" %)HierarchicalCode|(% style="width:413px" %)hierachicalCodeListAgencyId: hierarchicalcodelistId(version).hierarchy.hierarc hicalCode|(% style="width:431px" %)UNESCO:CL_EXP_SOURCE(1.0). H-C-GOV.GOV_CODE1
717 +|(% style="width:191px" %)*DataStructure|(% style="width:413px" %)dataStructureDefintitionAgencyId: dataStructureDefintitionId(version)|(% style="width:431px" %)TFFS:EXT_DEBT(1.0)
718 +|(% style="width:191px" %)(((
759 759  Dimension
760 -
761 761  Descriptor
762 -
763 763  Measure
764 -
765 765  Descriptor
766 -
767 767  Attribute
768 -
769 769  Descriptor
770 -)))|(((
725 +)))|(% style="width:413px" %)(((
771 771  dataStructureDefinitionAgencyId: dataStructureDefinitionId(version).
772 -
773 773  componentListId
774 -
775 775  where the componentListId is the name of the class (there is only one occurrence of each in the Data Structure Definition)
776 -)))|(((
729 +)))|(% style="width:431px" %)(((
777 777  TFFS:EXT_DEBT(1.0).DimensionDescriptor
778 778  
779 779  TFFS:EXT_DEBT(1.0).MeasureDescriptor
... ... @@ -780,67 +780,54 @@
780 780  
781 781  TFFS:EXT_DEBT(1.0).AttributeDescriptor
782 782  )))
783 -|(((
736 +|(% style="width:191px" %)(((
784 784  GroupDimension
785 -
786 786  Descriptor
787 -)))|(((
739 +)))|(% style="width:413px" %)(((
788 788  dataStructureDefinitionAgencyId: dataStructureDefinitionId(version).
789 -
790 790  groupDimensionDescriptorId
791 -)))|TFFS:EXT_DEBT(1.0).SIBLING
792 -|Dimension|(((
742 +)))|(% style="width:431px" %)TFFS:EXT_DEBT(1.0).SIBLING
743 +|(% style="width:191px" %)Dimension|(% style="width:413px" %)(((
793 793  dataStructureDefinitionAgencyId: dataStructureDefinition (version).
794 -
795 795  dimensionId
796 -)))|TFFS:EXT_DEBT(1.0).FREQ
797 -|TimeDimension|(((
746 +)))|(% style="width:431px" %)TFFS:EXT_DEBT(1.0).FREQ
747 +|(% style="width:191px" %)TimeDimension|(% style="width:413px" %)(((
798 798  dataStructureDefinitionAgencyId: dataStructureDefinition (version).
799 -
800 800  timeDimensionId
801 -)))|TFFS:EXT_DEBT(1.0).TIME_PERIOD
802 -|Measure Dimension|dataStructureDefinitionAgencyId: dataStructureDefinition (version).|TFFS:EXT_DEBT(1.0).STOCK_FLOW
803 -
804 -
805 -
806 -| |measureDimensionId|
807 -|DataAttrribute|dataStructureDefinitionAgencyId: dataStructureDefinition (version). dataAttributeId|TFFS:EXT_DEBT(1.0).OBS_STATUS
808 -|PrimaryMeasure|(((
750 +)))|(% style="width:431px" %)TFFS:EXT_DEBT(1.0).TIME_PERIOD
751 +|(% style="width:191px" %)Measure Dimension|(% style="width:413px" %)dataStructureDefinitionAgencyId: dataStructureDefinition (version).
752 +measureDimensionId|(% style="width:431px" %)TFFS:EXT_DEBT(1.0).STOCK_FLOW
753 +|(% style="width:191px" %)DataAttrribute|(% style="width:415px" %)dataStructureDefinitionAgencyId: dataStructureDefinition (version). dataAttributeId|(% style="width:429px" %)TFFS:EXT_DEBT(1.0).OBS_STATUS
754 +|(% style="width:191px" %)PrimaryMeasure|(% style="width:415px" %)(((
809 809  dataStructureDefinitionAgencyId: dataStructureDefinition (version).
810 -
811 811  primaryMeasureId
812 -)))|TFFS:EXT_DEBT(1.0).OBS_VALUE
813 -|(((
814 -*Category
815 -
816 -Scheme
817 -)))|categorySchemeAgencyId: categorySchemeId(version)|IMF:SDDS(1.0)
818 -|Category|categorySchemeAgencyId: categorySchemeId(version). categoryId.categoryId categoryId.categoryId etc.|(((
757 +)))|(% style="width:429px" %)TFFS:EXT_DEBT(1.0).OBS_VALUE
758 +|(% style="width:191px" %)(((
759 +*Category Scheme
760 +)))|(% style="width:415px" %)categorySchemeAgencyId:
761 +categorySchemeId(version)|(% style="width:429px" %)IMF:SDDS(1.0)
762 +|(% style="width:191px" %)Category|(% style="width:415px" %)categorySchemeAgencyId:
763 +categorySchemeId(version).
764 +categoryId.categoryId categoryId.categoryId etc.|(% style="width:429px" %)(((
819 819  IMF:SDDS(1.0):
820 -
821 821  level_1_category.level_2_category …
822 822  )))
823 -|(((
824 -*Reporting
825 -
826 -Taxonomy
827 -)))|reportingTaxonomyAgencyId: reportingTaxonomyId(version)| IMF:REP_1(1.0)
828 -|ReportingCategory|reportingTaxonomyAgencyId: reportingTaxonomyId(version) reportingcategoryId.reportingcategoryId|(((
768 +|(% style="width:191px" %)(((
769 +*Reporting Taxonomy
770 +)))|(% style="width:415px" %)reportingTaxonomyAgencyId: reportingTaxonomyId(version)|(% style="width:429px" %) IMF:REP_1(1.0)
771 +|(% style="width:191px" %)ReportingCategory|(% style="width:415px" %)reportingTaxonomyAgencyId: reportingTaxonomyId(version) reportingcategoryId.reportingcategoryId|(% style="width:429px" %)(((
829 829  IMF:REP_1(1.0):
830 -
831 831  level_1_repcategory.level_2_repcategory …
832 832  )))
833 -|*Categorisation|categorisationAgencyId: categorisationId(version)|IMF:cat001(1.0)
834 -|(((
835 -*Organisation
775 +|(% style="width:191px" %)*Categorisation|(% style="width:415px" %)categorisationAgencyId: categorisationId(version)|(% style="width:429px" %)IMF:cat001(1.0)
776 +|(% style="width:191px" %)(((
777 +*Organisation Unit Scheme
778 +)))|(% style="width:415px" %)organisationUnitSchemeAgencyId: organisationUnitSchemeId(version)|(% style="width:429px" %)ECB:ORGANISATIONS(1.0)
779 +|(% style="width:191px" %)Organisation Unit|(% style="width:415px" %)organisationUnitSchemeAgencyId: organisationUnitSchemeId(version). organisationUnitId|(% style="width:429px" %)ECB:ORGANISATIONS(1.0).1F
780 +|(% style="width:191px" %)*AgencyScheme|(% style="width:415px" %)agencySchemeAgencyId: agencySchemeId(version)|(% style="width:429px" %)ECB:AGENCIES(1.0)
836 836  
837 -Unit Scheme
838 -)))|organisationUnitSchemeAgencyId: organisationUnitSchemeId(version)|ECB:ORGANISATIONS(1.0)
839 -|Organisation Unit|organisationUnitSchemeAgencyId: organisationUnitSchemeId(version). organisationUnitId|ECB:ORGANISATIONS(1.0).1F
840 -|*AgencyScheme|agencySchemeAgencyId: agencySchemeId(version)|ECB:AGENCIES(1.0)
841 841  
842 842  
843 -
844 844  |Agency|agencySchemeAgencyId: agencySchemeId(version). agencyId|ECB:AGENCY(1.0).AA
845 845  |(((
846 846  *DataProvider