Changes for page SDMX 2.1 Standards. Section 5. Registry Specification: Logical Interfaces

Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 1 added, 0 removed)
  • 1747824504225-229.png

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.
...	...	@@ -705,60 +705,44 @@
705	705
706	706	Note that for brevity the URN examples omit the prefix. All URNs have the prefix
707	707
708		-urn:sdmx.org.sdmx.infomodel.{package}.{classname}=
	684	+> urn:sdmx.org.sdmx.infomodel.{package}.{classname}=
709	709
710		-
711		-|**SDMX Class**|**Key attribute(s)**|**Example of URN**
712		-|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" %)(((
713	713	IMF
714	714
	691	+(((
	692	+Sub agency in the IMF AGENCIES
715	715
716		-Sub agency in the IMF AGENCIES
717		-
718		-
719	719	IMF.SubAgency1
720	720	)))
721		-|*ConceptScheme|conceptSchemeAgencyId:conceptSchemeId(ve rsion)|SDMX:CROSS_DOMAIN_CONCEPTS(1.0)
722		-|Concept|(((
723		-conceptSchemeAgencyId:
724		-
725		-conceptSchemeId(version).conceptId
726		-)))|SDMX:CROSS_DOMAIN_CONCEPTS(1.0).FREQ
727		-|*Codelist|codeListAgencyId:codeListId(version)|SDMX:CL_FREQ(1.0)
728		-|Code|codeListAgencyId:codelistId(version).codeId|(((
729		-SDMX:CL_FREQ(1.0).Q
730		-
731		-
732	732	)))
733		-
734		-
735		-
736		-|(((
737		-*Hierarchical
738		-
739		-Codelist
740		-)))|hierachicalCodelistAgencyId: hierarchicalCodelistId(version)|(((
741		-UNESCO:CL_EXP_SOURCE(1.0)
742		-
743		-
	697	+|(% style="width:191px" %)*ConceptScheme|(% style="width:413px" %)conceptSchemeAgencyId:conceptSchemeId(ve rsion)|(% style="width:431px" %)SDMX:CROSS_DOMAIN_CONCEPTS(1.0)
	698	+|(% style="width:191px" %)Concept|(% style="width:413px" %)conceptSchemeAgencyId:
	699	+conceptSchemeId(version).conceptId|(% style="width:431px" %)SDMX:CROSS_DOMAIN_CONCEPTS(1.0).FREQ
	700	+|(% style="width:191px" %)*Codelist|(% style="width:413px" %)codeListAgencyId:codeListId(version)|(% style="width:431px" %)SDMX:CL_FREQ(1.0)
	701	+|(% style="width:191px" %)Code|(% style="width:413px" %)codeListAgencyId:codelistId(version).codeId|(% style="width:431px" %)SDMX:CL_FREQ(1.0).Q
	702	+|(% style="width:191px" %)(((
	703	+*Hierarchical Codelist
	704	+)))|(% style="width:413px" %)hierachicalCodelistAgencyId: hierarchicalCodelistId(version)|(% style="width:431px" %)(((
	705	+UNESCO:CL_EXP_SOURCE(1.0(% style="background-color:transparent" %))
744	744	)))
745		-|Hierarchy|(((
	707	+|(% style="width:191px" %)Hierarchy|(% style="width:413px" %)(((
746	746	hierachicalcodeListAgencyId:
747		-
748	748	hierarchicalcodelistId(version).Hierarchy
749		-)))|UNESCO:CL_EXP_SOURCE(1.0). H-C-GOV
750		-|Level|(((
	710	+)))|(% style="width:431px" %)UNESCO:CL_EXP_SOURCE(1.0). H-C-GOV
	711	+|(% style="width:191px" %)Level|(% style="width:413px" %)(((
751	751	hierachicalcodeListAgencyId:
752		-
753	753	hierarchicalcodelistId(version).Hierarchy.Level
754		-)))|(((
	714	+)))|(% style="width:431px" %)(((
755	755	ESTAT:HCL_REGION(1.0).H_1.COUNTRY
756	756
757	757
758	758	)))
759		-|HierarchicalCode|hierachicalCodeListAgencyId: hierarchicalcodelistId(version).hierarchy.hierarc hicalCode|UNESCO:CL_EXP_SOURCE(1.0). H-C-GOV.GOV_CODE1
760		-|*DataStructure|dataStructureDefintitionAgencyId: dataStructureDefintitionId(version)|TFFS:EXT_DEBT(1.0)
761		-|(((
	719	+|(% 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
	720	+|(% style="width:191px" %)*DataStructure|(% style="width:413px" %)dataStructureDefintitionAgencyId: dataStructureDefintitionId(version)|(% style="width:431px" %)TFFS:EXT_DEBT(1.0)
	721	+|(% style="width:191px" %)(((
762	762	Dimension
763	763
764	764	Descriptor
...	...	@@ -770,13 +770,11 @@
770	770	Attribute
771	771
772	772	Descriptor
773		-)))|(((
	733	+)))|(% style="width:413px" %)(((
774	774	dataStructureDefinitionAgencyId: dataStructureDefinitionId(version).
775		-
776	776	componentListId
777		-
778	778	where the componentListId is the name of the class (there is only one occurrence of each in the Data Structure Definition)
779		-)))|(((
	737	+)))|(% style="width:431px" %)(((
780	780	TFFS:EXT_DEBT(1.0).DimensionDescriptor
781	781
782	782	TFFS:EXT_DEBT(1.0).MeasureDescriptor
...	...	@@ -783,64 +783,59 @@
783	783
784	784	TFFS:EXT_DEBT(1.0).AttributeDescriptor
785	785	)))
786		-|(((
	744	+|(% style="width:191px" %)(((
787	787	GroupDimension
788	788
789	789	Descriptor
790		-)))|(((
	748	+)))|(% style="width:413px" %)(((
791	791	dataStructureDefinitionAgencyId: dataStructureDefinitionId(version).
792		-
793	793	groupDimensionDescriptorId
794		-)))|TFFS:EXT_DEBT(1.0).SIBLING
795		-|Dimension|(((
	751	+)))|(% style="width:431px" %)TFFS:EXT_DEBT(1.0).SIBLING
	752	+|(% style="width:191px" %)Dimension|(% style="width:413px" %)(((
796	796	dataStructureDefinitionAgencyId: dataStructureDefinition (version).
797		-
798	798	dimensionId
799		-)))|TFFS:EXT_DEBT(1.0).FREQ
800		-|TimeDimension|(((
	755	+)))|(% style="width:431px" %)TFFS:EXT_DEBT(1.0).FREQ
	756	+|(% style="width:191px" %)TimeDimension|(% style="width:413px" %)(((
801	801	dataStructureDefinitionAgencyId: dataStructureDefinition (version).
802		-
803	803	timeDimensionId
804		-)))|TFFS:EXT_DEBT(1.0).TIME_PERIOD
805		-|Measure Dimension|dataStructureDefinitionAgencyId: dataStructureDefinition (version).|TFFS:EXT_DEBT(1.0).STOCK_FLOW
	759	+)))|(% style="width:431px" %)TFFS:EXT_DEBT(1.0).TIME_PERIOD
	760	+|(% style="width:191px" %)Measure Dimension|(% style="width:413px" %)dataStructureDefinitionAgencyId: dataStructureDefinition (version).|(% style="width:431px" %)TFFS:EXT_DEBT(1.0).STOCK_FLOW
806	806
807		-
808		-
809		-| |measureDimensionId|
810		-|DataAttrribute|dataStructureDefinitionAgencyId: dataStructureDefinition (version). dataAttributeId|TFFS:EXT_DEBT(1.0).OBS_STATUS
811		-|PrimaryMeasure|(((
	762	+(% style="width:987.294px" %)
	763	+|(% style="width:170px" %) |(% style="width:367px" %)measureDimensionId|(% style="width:446px" %)
	764	+|(% style="width:170px" %)DataAttrribute|(% style="width:367px" %)dataStructureDefinitionAgencyId: dataStructureDefinition (version). dataAttributeId|(% style="width:446px" %)TFFS:EXT_DEBT(1.0).OBS_STATUS
	765	+|(% style="width:170px" %)PrimaryMeasure|(% style="width:367px" %)(((
812	812	dataStructureDefinitionAgencyId: dataStructureDefinition (version).
813		-
814	814	primaryMeasureId
815		-)))|TFFS:EXT_DEBT(1.0).OBS_VALUE
816		-|(((
	768	+)))|(% style="width:446px" %)TFFS:EXT_DEBT(1.0).OBS_VALUE
	769	+|(% style="width:170px" %)(((
817	817	*Category
818	818
819	819	Scheme
820		-)))|categorySchemeAgencyId: categorySchemeId(version)|IMF:SDDS(1.0)
821		-|Category|categorySchemeAgencyId: categorySchemeId(version). categoryId.categoryId categoryId.categoryId etc.|(((
	773	+)))|(% style="width:367px" %)categorySchemeAgencyId: categorySchemeId(version)|(% style="width:446px" %)IMF:SDDS(1.0)
	774	+|(% style="width:170px" %)Category|(% style="width:367px" %)categorySchemeAgencyId: categorySchemeId(version). categoryId.categoryId categoryId.categoryId etc.|(% style="width:446px" %)(((
822	822	IMF:SDDS(1.0):
823	823
824	824	level_1_category.level_2_category …
825	825	)))
826		-|(((
	779	+|(% style="width:170px" %)(((
827	827	*Reporting
828	828
829	829	Taxonomy
830		-)))|reportingTaxonomyAgencyId: reportingTaxonomyId(version)| IMF:REP_1(1.0)
831		-|ReportingCategory|reportingTaxonomyAgencyId: reportingTaxonomyId(version) reportingcategoryId.reportingcategoryId|(((
	783	+)))|(% style="width:367px" %)reportingTaxonomyAgencyId: reportingTaxonomyId(version)|(% style="width:446px" %) IMF:REP_1(1.0)
	784	+|(% style="width:170px" %)ReportingCategory|(% style="width:367px" %)reportingTaxonomyAgencyId: reportingTaxonomyId(version) reportingcategoryId.reportingcategoryId|(% style="width:446px" %)(((
832	832	IMF:REP_1(1.0):
833	833
834	834	level_1_repcategory.level_2_repcategory …
835	835	)))
836		-|*Categorisation|categorisationAgencyId: categorisationId(version)|IMF:cat001(1.0)
837		-|(((
	789	+|(% style="width:170px" %)*Categorisation|(% style="width:367px" %)categorisationAgencyId: categorisationId(version)|(% style="width:446px" %)IMF:cat001(1.0)
	790	+|(% style="width:170px" %)(((
838	838	*Organisation
839	839
840	840	Unit Scheme
841		-)))|organisationUnitSchemeAgencyId: organisationUnitSchemeId(version)|ECB:ORGANISATIONS(1.0)
842		-|Organisation Unit|organisationUnitSchemeAgencyId: organisationUnitSchemeId(version). organisationUnitId|ECB:ORGANISATIONS(1.0).1F
843		-|*AgencyScheme|agencySchemeAgencyId: agencySchemeId(version)|ECB:AGENCIES(1.0)
	794	+)))|(% style="width:367px" %)organisationUnitSchemeAgencyId: organisationUnitSchemeId(version)|(% style="width:446px" %)ECB:ORGANISATIONS(1.0)
	795	+|(% style="width:170px" %)Organisation Unit|(% style="width:367px" %)organisationUnitSchemeAgencyId: organisationUnitSchemeId(version). organisationUnitId|(% style="width:446px" %)ECB:ORGANISATIONS(1.0).1F
	796	+|(% style="width:170px" %)*AgencyScheme|(% style="width:367px" %)agencySchemeAgencyId: agencySchemeId(version)|(% style="width:446px" %)ECB:AGENCIES(1.0)
844	844
845	845
846	846

1747824504225-229.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+xwiki:XWiki.helena

Size

...	...	@@ -1,0 +1,1 @@
	1	+52.8 KB

Content