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

...	...	@@ -292,15 +292,13 @@
292	292
293	293	3The Registration has an action attribute which takes one of the following values:
294	294
295		-|(((
296		-**Action**
	295	+|(% style="width:249px" %)(((
	296	+**Action Attribute Value**
	297	+)))|(% style="width:1622px" %)**Behaviour**
	298	+|(% style="width:249px" %)Append|(% style="width:1622px" %)Add this registration to the registry
	299	+|(% style="width:249px" %)Replace|(% style="width:1622px" %)Replace the existing Registration with this Registration identified by the id in the Registration of the Submit Registration Request
	300	+|(% style="width:249px" %)Delete|(% style="width:1622px" %)Delete the existing Registration identified by the id in the Registration of the Submit Registration Request
297	297
298		-**Attribute Value**
299		-)))|**Behaviour**
300		-|Append|Add this registration to the registry
301		-|Replace|Replace the existing Registration with this Registration identified by the id in the Registration of the Submit Registration Request
302		-|Delete|Delete the existing Registration identified by the id in the Registration of the Submit Registration Request
303		-
304	304	The Registration has three Boolean attributes which may be present to determine how an SDMX compliant Dataset or Metadata Set indexing application must index the Datasets or Metadata Set upon registration. The indexing application behaviour is as follows:
305	305
306	306	|**Boolean Attribute**|**Behaviour if Value is “true”**
...	...	@@ -316,10 +316,9 @@
316	316
317	317	The Data and Metadata Discovery Service implements the following Registry Interfaces:
318	318
319		- QueryRegistrationRequest
	317	+* QueryRegistrationRequest
	318	+* QueryRegistrationResponse
320	320
321		- QueryRegistrationResponse
322		-
323	323	=== 5.2.6 Subscription and Notification ===
324	324
325	325	The Subscription and Notification Service implements the following Registry Interfaces:
...	...	@@ -343,13 +343,12 @@
343	343
344	344	The following table defines the behaviour of the SDMX Registry for the various Registry Interface messages.
345	345
346		-|**Interface**|**Behaviour**
347		-|All|(((
	343	+|(% style="width:244px" %)**Interface**|**Behaviour**
	344	+|(% style="width:244px" %)All|(((
348	348	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:
349	349
350	350	* Name – this applies to the Maintainable object and its contained elements, such a Code in a Code list.
351	351	* Description - this applies to the Maintainable object and its contained elements, such a Code in a Code list.
352		-
353	353	* Annotation - this applies to the Maintainable object and its contained elements, such a Code in a Code list.
354	354	* validTo
355	355	* validFrom
...	...	@@ -358,26 +358,24 @@
358	358	* uri
359	359	* isExternalReference
360	360
361		-1. Cross referenced structures MUST exist in either the submitted document (in Structures or Structure Location) or in the registry to which the request is submitted.
362		-1. If the action is set to “delete” then the Registry MUST verify that the object can deleted. In order to qualify for deletion the object must:
	357	+2) Cross referenced structures MUST exist in either the submitted document (in Structures or Structure Location) or in the registry to which the request is submitted.
363	363
364		-1. Not have the final attribute set to “true”
365		-1. Not be referenced from any other object in the Registry.
	359	+3) If the action is set to “delete” then the Registry MUST verify that the object can deleted. In order to qualify for deletion the object must:
366	366
367		-1. The version rules in the SDMX Schema documentation MUST be obeyed.
	361	+а) Not have the final attribute set to “true”
	362	+b) Not be referenced from any other object in the Registry.
368	368
369		-* The specific rules for the elements and attributes documented in the SDMX Schema MUST be obeyed.
	364	+4) The version rules in the SDMX Schema documentation MUST be obeyed.
	365	+
	366	+5) The specific rules for the elements and attributes documented in the SDMX Schema MUST be obeyed.
370	370	)))
371		-|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.
372		-|SubmitProvisioningRequest|No additional behaviour.
373		-|Submit Registration Request|(((
	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|(((
374	374	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.
375		-
376	376	For a queryable datasource the Registry MAY validate that the source exists and can accept an SDMX-ML data query.
377	377	)))
378	378
379		-
380		-
381	381	= 6 Identification of SDMX Objects =
382	382
383	383	== 6.1 Identification, Versioning, and Maintenance ==
...	...	@@ -384,7 +384,6 @@
384	384
385	385	All major classes of the SDMX Information model inherit from one of:
386	386
387		-
388	388	* **IdentifiableArtefact** - this gives an object the ability to be uniquely identified (see following section on identification), to have a user-defined URI, and to have multi-lingual annotations.
389	389	* **NamableArtefact **- this has all of the features of IdentifiableArtefact plus the ability to have a multi-lingual name and description,
390	390	* **VersionableArtefact **– this has all of the above features plus a version number and a validity period.
...	...	@@ -392,6 +392,8 @@
392	392
393	393	=== 6.1.1 Identification, Naming, Versioning, and Maintenance Model ===
394	394
	388	+[[image:1747824504225-229.png]]
	389	+
395	395	**Figure 5: Class diagram of fundamental artefacts in the SDMX-IM**
396	396
397	397	The table below shows the identification and related data attributes to be stored in a registry for objects that are one of:
...	...	@@ -402,38 +402,34 @@
402	402	* Versionable
403	403	* Maintainable
404	404
405		-|**Object Type**|**Data Attributes**|**Status**|**Data type**|**Notes**
406		-|Annotable|AnnotationTitle|C|string|
407		-| |AnnotationType|C|string|
408		-| |AnnotationURN|C|string|
409		-| |(((
410		-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.
411	411
412		-International String
413		-)))|C| |This can have languagespecific variants.
414		-| | | | |
415		-|Identifiable|all content as for Annotable plus| | |
416		-| |id|M|string|
417		-| |uri|C|string|
418		-| |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.
419		-|Nameable|all content as for Identifiable plus| | |
420		-| |Name in the form of International String|M|string|This can have languagespecific variants.
421		-| |(((
422		-Description in the form of International
423		-
424		-String
425		-)))|C|string|This can have languagespecific variants.
426		-|Versionable|All content as for Identifiable plus| | |
427		-| |version|C|string|This is the version number. If not present the default is 1.0
428		-| |validFrom|C|Date/time|
429		-| |validTo|C|Date/time|
430		-|Maintainable|All content as for Versionable plus| | |
431		-| |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.
432		-| |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.
433		-| |serviceURL|C|string|The url of the service that can be queried for this resource
434		-| |structureURL|C|string|The url of the resource.
435		-| |(Maintenance) agencyId|M|string|The object must be linked to a maintenance agency.
436		-
437	437	**Table 1: Common Attributes of Object Types**
438	438
439	439	== 6.2 Unique identification of SDMX objects ==
...	...	@@ -478,11 +478,11 @@
478	478
479	479	An example of this is shown in the XML snippet below.
480	480
	472	+[[image:1747824123013-196.jpeg||height="309" width="446"]]
481	481
482		-[[image:1747824123013-196.jpeg]]
	474	+(% class="wikigeneratedid" id="HFigure8:ExampleShowingUseofAgencyIdentifiers" %)
	475	+**Figure 8: Example Showing Use of Agency Identifiers**
483	483
484		-==== Figure 8: Example Showing Use of Agency Identifiers ====
485		-
486	486	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.
487	487
488	488	=== 6.2.2 Universal Resource Name (URN) ===
...	...	@@ -521,10 +521,8 @@
521	521
522	522	**(maintainable-object-version)** is the version of the maintainable object and is enclosed in round brackets (). It will always be present.
523	523
524		-**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.
525	525
526		-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.
527		-
528	528	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.
529	529
530	530	For example the sequence is agency:DSDid(version).DimensionId and not agency:DSDid(version).DimensionDescriptorId.DimensionId.
...	...	@@ -531,58 +531,57 @@
531	531
532	532	**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.
533	533
534		-===== //Generic Examples of the URN Structure// =====
	523	+===== __**//Generic Examples of the URN Structure//**__ =====
535	535
	525	+__Actual object is a maintainable__
536	536
537		-Actual object is a maintainable
	527	+> SDMXPrefix.SDMX-IM package name.classname=agency id:maintained-object-id(version)
538	538
539		-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__
540	540
541		-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
542	542
543		-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__
544	544
545		-Actual object is contained in a maintained object with an intermediate containing object
	535	+> SDMXPrefix.SDMX-IM package name.classname=agency
546	546
547		-SDMXPrefix.SDMX-IM package name.classname=agency
548		-
549	549	id:maintained-object-id(version).contained-object-id.object-id
550	550
551		-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__
552	552
553	553	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
554	554
555		-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
556	556
557		-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__
558	558
559	559	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
560	560
561		-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
562	562
563		-===== //Concrete Examples of the URN Structure// =====
	551	+===== __**//Concrete Examples of the URN Structure//**__ =====
564	564
565	565	The Data Structure Definition CRED_EXT_DEBT version 1.0 maintained by the top level Agency TFFS would have the URN:
566	566
567		-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)
568	568
569	569	The URN for a code for Argentina maintained by ISO in the code list CL_3166A2 version 1.0 would be:
570	570
571		-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
572	572
573	573	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:
574	574
575		-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
576	576
577	577	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
578	578
579	579	CONTACT_DETAILS/CONTACT_NAME would be:
580	580
581		-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
582	582
583	583	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:
584	584
585		-urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=TFFS.ABC:EX
	573	+> urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=TFFS.ABC:EX
586	586
587	587	TERNAL_DEBT(1.0)
588	588
...	...	@@ -597,112 +597,94 @@
597	597
598	598	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.
599	599
600		-|**Package**|(((
601		-**URN Classname (model classname**
602		-
603		-**where this is different)**
	588	+|(% style="width:127px" %)**Package**|(% style="width:1745px" %)(((
	589	+**URN Classname (model classname where this is different)**
604	604	)))
605		-|base|Agency
606		-| |OrganisationUnitScheme
607		-| |AgencyScheme
608		-| |DataProviderScheme
609		-| |DataConsumerScheme
610		-| |OrganisationUnit
611		-| |DataProvider
612		-| |DataConsumer
613		-| |
614		-|datastructure|DataStructure (DataStructureDefinition)
615		-| |AttributeDescriptor
616		-| |DataAttribute
617		-| |GroupDimensionDescriptor
618		-| |DimensionDescriptor
619		-| |Dimension
620		-| |MeasureDimension
621		-| |TimeDimension
622		-| |MeasureDescriptor
623		-| |PrimaryMeasure
624		-| |Dataflow (DataflowDefinition)
625		-| |
626		-|metadatastructure|MetadataTarget
627		-| |DimensionDescriptorValueTarget
628		-| |IdentifiableObjectTarget
629		-| |ReportPeriodTarget
630		-| |DataSetTarget
631		-| |ReportStructure
632		-| |MetadataAttribute
633		-| |(((
	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" %)(((
634	634	MetadataStructure
635	635
636	636	(MetadataStructureDefinition)
637	637	)))
638		-| |Metadataflow (MetadataflowDefinition)
639		-| |
640		-|process|Process
641		-| |ProcessStep
642		-| |Transition
643		-| |
644		-|registry|ProvisionAgreement
645		-| |AttachmentConstraint
646		-| |ContentConstraint
647		-| |Subscription
648		-| |
649		-|mapping|StructureMap
650		-| |StructureSet
651		-| |ComponentMap
652		-|**Package**|(((
653		-**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
654	654
655		-**where this is different)**
656		-)))
657		-| |ConceptSchemeMap
658		-| |OrganisationSchemeMap
659		-| |CodelistMap
660		-| |CategorySchemeMap
661		-| |ReportingTaxonomyMap
662		-| |ConceptMap
663		-| |OrganisationMap
664		-| |CodeMap
665		-| |HybridCodelistMap
666		-| |CategoryMap
667		-| |HybridCodeMap
668		-| |ReportingCategoryMap
669		-| |
670		-|codelist|Codelist
671		-| |HierarchicalCodelist
672		-| |Hierarchy
673		-| |Hierarchy
674		-| |Code
675		-| |HierarchicalCode
676		-| |Level
677		-| |
678		-|categoryscheme|CategoryScheme
679		-| |Category
680		-| |Categorisation
681		-| |ReportingTaxonomy
682		-| |ReportingCategory
683		-| |
684		-|conceptscheme|ConceptScheme
685		-| |Concept
686		-| |
687		-|transformation|TransformationScheme
688		-| |Transformation
689		-| |CustomTypeScheme
690		-| |CustomType
691		-| |NamePersonalisationScheme
692		-| |NamePersonalisation
693		-| |VtlCodelistMapping
694		-| |VtlConceptMapping
695		-| |VtlDataflowMapping
696		-| |VtlConceptSchemeMapping
697		-| |RulesetScheme
698		-| |Ruleset
699		-| |UserDefinedOperatorScheme
700		-| |UserDefinedOperator
701		-| |
702		-
703	703	**Table 2: SDMX-IM Packages and Contained Classes**
704	704
705		-
706	706	=== 6.2.4 URN Identification components of SDMX objects ===
707	707
708	708	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.
...	...	@@ -711,60 +711,44 @@
711	711
712	712	Note that for brevity the URN examples omit the prefix. All URNs have the prefix
713	713
714		-urn:sdmx.org.sdmx.infomodel.{package}.{classname}=
	684	+> urn:sdmx.org.sdmx.infomodel.{package}.{classname}=
715	715
716		-
717		-|**SDMX Class**|**Key attribute(s)**|**Example of URN**
718		-|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" %)(((
719	719	IMF
720	720
	691	+(((
	692	+Sub agency in the IMF AGENCIES
721	721
722		-Sub agency in the IMF AGENCIES
723		-
724		-
725	725	IMF.SubAgency1
726	726	)))
727		-|*ConceptScheme|conceptSchemeAgencyId:conceptSchemeId(ve rsion)|SDMX:CROSS_DOMAIN_CONCEPTS(1.0)
728		-|Concept|(((
729		-conceptSchemeAgencyId:
730		-
731		-conceptSchemeId(version).conceptId
732		-)))|SDMX:CROSS_DOMAIN_CONCEPTS(1.0).FREQ
733		-|*Codelist|codeListAgencyId:codeListId(version)|SDMX:CL_FREQ(1.0)
734		-|Code|codeListAgencyId:codelistId(version).codeId|(((
735		-SDMX:CL_FREQ(1.0).Q
736		-
737		-
738	738	)))
739		-
740		-
741		-
742		-|(((
743		-*Hierarchical
744		-
745		-Codelist
746		-)))|hierachicalCodelistAgencyId: hierarchicalCodelistId(version)|(((
747		-UNESCO:CL_EXP_SOURCE(1.0)
748		-
749		-
	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" %))
750	750	)))
751		-|Hierarchy|(((
	707	+|(% style="width:191px" %)Hierarchy|(% style="width:413px" %)(((
752	752	hierachicalcodeListAgencyId:
753		-
754	754	hierarchicalcodelistId(version).Hierarchy
755		-)))|UNESCO:CL_EXP_SOURCE(1.0). H-C-GOV
756		-|Level|(((
	710	+)))|(% style="width:431px" %)UNESCO:CL_EXP_SOURCE(1.0). H-C-GOV
	711	+|(% style="width:191px" %)Level|(% style="width:413px" %)(((
757	757	hierachicalcodeListAgencyId:
758		-
759	759	hierarchicalcodelistId(version).Hierarchy.Level
760		-)))|(((
	714	+)))|(% style="width:431px" %)(((
761	761	ESTAT:HCL_REGION(1.0).H_1.COUNTRY
762	762
763	763
764	764	)))
765		-|HierarchicalCode|hierachicalCodeListAgencyId: hierarchicalcodelistId(version).hierarchy.hierarc hicalCode|UNESCO:CL_EXP_SOURCE(1.0). H-C-GOV.GOV_CODE1
766		-|*DataStructure|dataStructureDefintitionAgencyId: dataStructureDefintitionId(version)|TFFS:EXT_DEBT(1.0)
767		-|(((
	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" %)(((
768	768	Dimension
769	769
770	770	Descriptor
...	...	@@ -776,13 +776,11 @@
776	776	Attribute
777	777
778	778	Descriptor
779		-)))|(((
	733	+)))|(% style="width:413px" %)(((
780	780	dataStructureDefinitionAgencyId: dataStructureDefinitionId(version).
781		-
782	782	componentListId
783		-
784	784	where the componentListId is the name of the class (there is only one occurrence of each in the Data Structure Definition)
785		-)))|(((
	737	+)))|(% style="width:431px" %)(((
786	786	TFFS:EXT_DEBT(1.0).DimensionDescriptor
787	787
788	788	TFFS:EXT_DEBT(1.0).MeasureDescriptor
...	...	@@ -789,64 +789,59 @@
789	789
790	790	TFFS:EXT_DEBT(1.0).AttributeDescriptor
791	791	)))
792		-|(((
	744	+|(% style="width:191px" %)(((
793	793	GroupDimension
794	794
795	795	Descriptor
796		-)))|(((
	748	+)))|(% style="width:413px" %)(((
797	797	dataStructureDefinitionAgencyId: dataStructureDefinitionId(version).
798		-
799	799	groupDimensionDescriptorId
800		-)))|TFFS:EXT_DEBT(1.0).SIBLING
801		-|Dimension|(((
	751	+)))|(% style="width:431px" %)TFFS:EXT_DEBT(1.0).SIBLING
	752	+|(% style="width:191px" %)Dimension|(% style="width:413px" %)(((
802	802	dataStructureDefinitionAgencyId: dataStructureDefinition (version).
803		-
804	804	dimensionId
805		-)))|TFFS:EXT_DEBT(1.0).FREQ
806		-|TimeDimension|(((
	755	+)))|(% style="width:431px" %)TFFS:EXT_DEBT(1.0).FREQ
	756	+|(% style="width:191px" %)TimeDimension|(% style="width:413px" %)(((
807	807	dataStructureDefinitionAgencyId: dataStructureDefinition (version).
808		-
809	809	timeDimensionId
810		-)))|TFFS:EXT_DEBT(1.0).TIME_PERIOD
811		-|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
812	812
813		-
814		-
815		-| |measureDimensionId|
816		-|DataAttrribute|dataStructureDefinitionAgencyId: dataStructureDefinition (version). dataAttributeId|TFFS:EXT_DEBT(1.0).OBS_STATUS
817		-|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" %)(((
818	818	dataStructureDefinitionAgencyId: dataStructureDefinition (version).
819		-
820	820	primaryMeasureId
821		-)))|TFFS:EXT_DEBT(1.0).OBS_VALUE
822		-|(((
	768	+)))|(% style="width:446px" %)TFFS:EXT_DEBT(1.0).OBS_VALUE
	769	+|(% style="width:170px" %)(((
823	823	*Category
824	824
825	825	Scheme
826		-)))|categorySchemeAgencyId: categorySchemeId(version)|IMF:SDDS(1.0)
827		-|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" %)(((
828	828	IMF:SDDS(1.0):
829	829
830	830	level_1_category.level_2_category …
831	831	)))
832		-|(((
	779	+|(% style="width:170px" %)(((
833	833	*Reporting
834	834
835	835	Taxonomy
836		-)))|reportingTaxonomyAgencyId: reportingTaxonomyId(version)| IMF:REP_1(1.0)
837		-|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" %)(((
838	838	IMF:REP_1(1.0):
839	839
840	840	level_1_repcategory.level_2_repcategory …
841	841	)))
842		-|*Categorisation|categorisationAgencyId: categorisationId(version)|IMF:cat001(1.0)
843		-|(((
	789	+|(% style="width:170px" %)*Categorisation|(% style="width:367px" %)categorisationAgencyId: categorisationId(version)|(% style="width:446px" %)IMF:cat001(1.0)
	790	+|(% style="width:170px" %)(((
844	844	*Organisation
845	845
846	846	Unit Scheme
847		-)))|organisationUnitSchemeAgencyId: organisationUnitSchemeId(version)|ECB:ORGANISATIONS(1.0)
848		-|Organisation Unit|organisationUnitSchemeAgencyId: organisationUnitSchemeId(version). organisationUnitId|ECB:ORGANISATIONS(1.0).1F
849		-|*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)
850	850
851	851
852	852

1747824504225-229.png

Author

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

Size

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

Content