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, 0 added, 7 removed)
  • 1747824504225-229.png
  • 1747829078194-749.png
  • 1747829109466-595.png
  • 1747829139951-378.png
  • 1747829204737-370.png
  • 1747829290890-122.png
  • 1747829477882-750.png

Details

Page properties

Content

...	...	@@ -192,8 +192,10 @@
192	192
193	193	In addition to these interfaces the registry must support a mechanism for querying for structural metadata. This is detailed in 5.2.2.
194	194
195		-All these interactions with the Registry – with the exception of Notify Registry Event – are designed in pairs. The first document – the one which invokes the SDMX-RR interface, is a “Request” document. The message returned by the interface is a “Response” document.
	195	+All these interactions with the Registry – with the exception of Notify Registry Event – are designed in pairs. The first document – the one which invokes the SDMX-RR interface, is a “Request” document. The message returned by the interface is a
196	196
	197	+“Response” document.
	198	+
197	197	It should be noted that all interactions are assumed to be synchronous, with the exception of Notify Registry Event. This document is sent by the SDMX-RR to all subscribers whenever an even occurs to which any users have subscribed. Thus, it does not conform to the request-response pattern, because it is inherently asynchronous.
198	198
199	199	== 5.2 Registry Services ==
...	...	@@ -292,13 +292,15 @@
292	292
293	293	3The Registration has an action attribute which takes one of the following values:
294	294
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	+|(((
	298	+**Action**
301	301
	300	+**Attribute Value**
	301	+)))|**Behaviour**
	302	+|Append|Add this registration to the registry
	303	+|Replace|Replace the existing Registration with this Registration identified by the id in the Registration of the Submit Registration Request
	304	+|Delete|Delete the existing Registration identified by the id in the Registration of the Submit Registration Request
	305	+
302	302	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:
303	303
304	304	|**Boolean Attribute**|**Behaviour if Value is “true”**
...	...	@@ -314,9 +314,10 @@
314	314
315	315	The Data and Metadata Discovery Service implements the following Registry Interfaces:
316	316
317		-* QueryRegistrationRequest
318		-* QueryRegistrationResponse
	321	+ QueryRegistrationRequest
319	319
	323	+ QueryRegistrationResponse
	324	+
320	320	=== 5.2.6 Subscription and Notification ===
321	321
322	322	The Subscription and Notification Service implements the following Registry Interfaces:
...	...	@@ -340,12 +340,13 @@
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:244px" %)**Interface**|**Behaviour**
344		-|(% style="width:244px" %)All|(((
	348	+|**Interface**|**Behaviour**
	349	+|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.
348	348	* Description - this applies to the Maintainable object and its contained elements, such a Code in a Code list.
	354	+
349	349	* Annotation - this applies to the Maintainable object and its contained elements, such a Code in a Code list.
350	350	* validTo
351	351	* validFrom
...	...	@@ -354,24 +354,26 @@
354	354	* uri
355	355	* isExternalReference
356	356
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	+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.
	364	+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:
358	358
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	+1. Not have the final attribute set to “true”
	367	+1. Not be referenced from any other object in the Registry.
360	360
361		-а) Not have the final attribute set to “true”
362		-b) Not be referenced from any other object in the Registry.
	369	+1. The version rules in the SDMX Schema documentation MUST be obeyed.
363	363
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.
	371	+* The specific rules for the elements and attributes documented in the SDMX Schema MUST be obeyed.
367	367	)))
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|(((
	373	+|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.
	374	+|SubmitProvisioningRequest|No additional behaviour.
	375	+|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.
	377	+
372	372	For a queryable datasource the Registry MAY validate that the source exists and can accept an SDMX-ML data query.
373	373	)))
374	374
	381	+
	382	+
375	375	= 6 Identification of SDMX Objects =
376	376
377	377	== 6.1 Identification, Versioning, and Maintenance ==
...	...	@@ -378,6 +378,7 @@
378	378
379	379	All major classes of the SDMX Information model inherit from one of:
380	380
	389	+
381	381	* **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.
382	382	* **NamableArtefact **- this has all of the features of IdentifiableArtefact plus the ability to have a multi-lingual name and description,
383	383	* **VersionableArtefact **– this has all of the above features plus a version number and a validity period.
...	...	@@ -385,8 +385,6 @@
385	385
386	386	=== 6.1.1 Identification, Naming, Versioning, and Maintenance Model ===
387	387
388		-[[image:1747824504225-229.png]]
389		-
390	390	**Figure 5: Class diagram of fundamental artefacts in the SDMX-IM**
391	391
392	392	The table below shows the identification and related data attributes to be stored in a registry for objects that are one of:
...	...	@@ -397,34 +397,38 @@
397	397	* Versionable
398	398	* Maintainable
399	399
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.
	407	+|**Object Type**|**Data Attributes**|**Status**|**Data type**|**Notes**
	408	+|Annotable|AnnotationTitle|C|string|
	409	+| |AnnotationType|C|string|
	410	+| |AnnotationURN|C|string|
	411	+| |(((
	412	+AnnotationText in the form of
427	427
	414	+International String
	415	+)))|C| |This can have languagespecific variants.
	416	+| | | | |
	417	+|Identifiable|all content as for Annotable plus| | |
	418	+| |id|M|string|
	419	+| |uri|C|string|
	420	+| |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.
	421	+|Nameable|all content as for Identifiable plus| | |
	422	+| |Name in the form of International String|M|string|This can have languagespecific variants.
	423	+| |(((
	424	+Description in the form of International
	425	+
	426	+String
	427	+)))|C|string|This can have languagespecific variants.
	428	+|Versionable|All content as for Identifiable plus| | |
	429	+| |version|C|string|This is the version number. If not present the default is 1.0
	430	+| |validFrom|C|Date/time|
	431	+| |validTo|C|Date/time|
	432	+|Maintainable|All content as for Versionable plus| | |
	433	+| |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.
	434	+| |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.
	435	+| |serviceURL|C|string|The url of the service that can be queried for this resource
	436	+| |structureURL|C|string|The url of the resource.
	437	+| |(Maintenance) agencyId|M|string|The object must be linked to a maintenance agency.
	438	+
428	428	**Table 1: Common Attributes of Object Types**
429	429
430	430	== 6.2 Unique identification of SDMX objects ==
...	...	@@ -469,11 +469,11 @@
469	469
470	470	An example of this is shown in the XML snippet below.
471	471
472		-[[image:1747824123013-196.jpeg||height="309" width="446"]]
473	473
474		-(% class="wikigeneratedid" id="HFigure8:ExampleShowingUseofAgencyIdentifiers" %)
475		-**Figure 8: Example Showing Use of Agency Identifiers**
	484	+[[image:1747824123013-196.jpeg]]
476	476
	486	+==== Figure 8: Example Showing Use of Agency Identifiers ====
	487	+
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
479	479	=== 6.2.2 Universal Resource Name (URN) ===
...	...	@@ -512,8 +512,10 @@
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 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.
	526	+**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
516	516
	528	+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.
	529	+
517	517	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.
518	518
519	519	For example the sequence is agency:DSDid(version).DimensionId and not agency:DSDid(version).DimensionDescriptorId.DimensionId.
...	...	@@ -520,57 +520,58 @@
520	520
521	521	**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.
522	522
523		-===== __**//Generic Examples of the URN Structure//**__ =====
	536	+===== //Generic Examples of the URN Structure// =====
524	524
525		-__Actual object is a maintainable__
526	526
527		-> SDMXPrefix.SDMX-IM package name.classname=agency id:maintained-object-id(version)
	539	+Actual object is a maintainable
528	528
529		-__Actual object is contained in a maintained object with no intermediate containing object__
	541	+SDMXPrefix.SDMX-IM package name.classname=agency id:maintained-object-id(version)
530	530
531		-> SDMXPrefix.SDMX-IM package name.classname=agency id:maintained-object-id(version).object-id
	543	+Actual object is contained in a maintained object with no intermediate containing object
532	532
533		-__Actual object is contained in a maintained object with an intermediate containing object__
	545	+SDMXPrefix.SDMX-IM package name.classname=agency id:maintained-object-id(version).object-id
534	534
535		-> SDMXPrefix.SDMX-IM package name.classname=agency
	547	+Actual object is contained in a maintained object with an intermediate containing object
536	536
	549	+SDMXPrefix.SDMX-IM package name.classname=agency
	550	+
537	537	id:maintained-object-id(version).contained-object-id.object-id
538	538
539		-__Actual object is contained in a maintained object with no intermediate containing object but the object type itself is hierarchical__
	553	+Actual object is contained in a maintained object with no intermediate containing object but the object type itself is hierarchical
540	540
541	541	In this case the object id may not be unique in itself but only within the context of the hierarchy. In the general syntax of the URN all intermediary objects in the structure (with the exception, of course, of the maintained object) are shown as a contained object. An example here would be a Category in a Category Scheme. The Category is hierarchical and all intermediate Categories are shown as a contained object. The example below shows the generic structure for Category Scheme/Category/Category
542	542
543		-> SDMXPrefix.SDMX-IM package name.classname=agency id:maintained-object-id(version).contained-object-id.object-id
	557	+SDMXPrefix.SDMX-IM package name.classname=agency id:maintained-object-id(version).contained-object-id.object-id
544	544
545		-__Actual object is contained in a maintained object with an intermediate containing object and the object type itself is hierarchical__
	559	+Actual object is contained in a maintained object with an intermediate containing object and the object type itself is hierarchical
546	546
547	547	In this case the generic syntax is the same as for the example above as the parent object is regarded as a containing object, even if it is of the same type. An example here is a Metadata Attribute where the contained objects are Report Structure (first contained object id) and Metadata Attribute (subsequent contained object Ids). The example below shows the generic structure for MSD/Report Structure/Metadata Attribute/Metadata Attribute
548	548
549		-> SDMXPrefix.SDMX-IM package name.classname=agency id:maintained-object-id(version).contained-object-id. contained-object-id contained-object-id.object-id
	563	+SDMXPrefix.SDMX-IM package name.classname=agency id:maintained-object-id(version).contained-object-id. contained-object-id contained-object-id.object-id
550	550
551		-===== __**//Concrete Examples of the URN Structure//**__ =====
	565	+===== //Concrete Examples of the URN Structure// =====
552	552
553	553	The Data Structure Definition CRED_EXT_DEBT version 1.0 maintained by the top level Agency TFFS would have the URN:
554	554
555		-> urn:sdmx:org.sdmx.infomodel.datastructure.DataStucture=TFFS:CRED_EXT_ DEBT(1.0)
	569	+urn:sdmx:org.sdmx.infomodel.datastructure.DataStucture=TFFS:CRED_EXT_ DEBT(1.0)
556	556
557	557	The URN for a code for Argentina maintained by ISO in the code list CL_3166A2 version 1.0 would be:
558	558
559		-> urn:sdmx:org.sdmx.infomodel.codelist.Code=ISO:CL_3166A2(1.0).AR
	573	+urn:sdmx:org.sdmx.infomodel.codelist.Code=ISO:CL_3166A2(1.0).AR
560	560
561	561	The URN for a category (id of 1) which has parent category (id of 2) maintained by SDMX in the category scheme SUBJECT_MATTER_DOMAINS version 1.0 would be:
562	562
563		-> urn:sdmx:org.sdmx.infomodel.categoryscheme.Category=SDMX:SUBJE CT_MATTER_DOMAINS(1.0).1.2
	577	+urn:sdmx:org.sdmx.infomodel.categoryscheme.Category=SDMX:SUBJE CT_MATTER_DOMAINS(1.0).1.2
564	564
565	565	The URN for a Metadata Attribute maintained by SDMX in the MSD CONTACT_METADATA version 1.0 in the Report Structure CONTACT_REPORT where the hierarchy of the Metadata Attribute is
566	566
567	567	CONTACT_DETAILS/CONTACT_NAME would be:
568	568
569		-> urn:sdmx:org.sdmx.infomodel.metadatastructure.MetadataAttribut e=SDMX:CONTACT_METADATA(1.0).CONTACT_REPORT.CONTACT_DETAILS.CO NTACT_NAME
	583	+urn:sdmx:org.sdmx.infomodel.metadatastructure.MetadataAttribut e=SDMX:CONTACT_METADATA(1.0).CONTACT_REPORT.CONTACT_DETAILS.CO NTACT_NAME
570	570
571	571	The TFFS defines ABC as a sub Agency of TFFS then the URN of a Dataflow maintained by ABC and identified as EXTERNAL_DEBT version 1.0 would be:
572	572
573		-> urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=TFFS.ABC:EX
	587	+urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=TFFS.ABC:EX
574	574
575	575	TERNAL_DEBT(1.0)
576	576
...	...	@@ -585,94 +585,112 @@
585	585
586	586	The table below lists all of the packages in the SDMX-IM together with the concrete classes that are in these packages and whose objects have a URN.
587	587
588		-|(% style="width:127px" %)**Package**|(% style="width:1745px" %)(((
589		-**URN Classname (model classname where this is different)**
	602	+|**Package**|(((
	603	+**URN Classname (model classname**
	604	+
	605	+**where this is different)**
590	590	)))
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" %)(((
	607	+|base|Agency
	608	+| |OrganisationUnitScheme
	609	+| |AgencyScheme
	610	+| |DataProviderScheme
	611	+| |DataConsumerScheme
	612	+| |OrganisationUnit
	613	+| |DataProvider
	614	+| |DataConsumer
	615	+| |
	616	+|datastructure|DataStructure (DataStructureDefinition)
	617	+| |AttributeDescriptor
	618	+| |DataAttribute
	619	+| |GroupDimensionDescriptor
	620	+| |DimensionDescriptor
	621	+| |Dimension
	622	+| |MeasureDimension
	623	+| |TimeDimension
	624	+| |MeasureDescriptor
	625	+| |PrimaryMeasure
	626	+| |Dataflow (DataflowDefinition)
	627	+| |
	628	+|metadatastructure|MetadataTarget
	629	+| |DimensionDescriptorValueTarget
	630	+| |IdentifiableObjectTarget
	631	+| |ReportPeriodTarget
	632	+| |DataSetTarget
	633	+| |ReportStructure
	634	+| |MetadataAttribute
	635	+| |(((
618	618	MetadataStructure
619	619
620	620	(MetadataStructureDefinition)
621	621	)))
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
	640	+| |Metadataflow (MetadataflowDefinition)
	641	+| |
	642	+|process|Process
	643	+| |ProcessStep
	644	+| |Transition
	645	+| |
	646	+|registry|ProvisionAgreement
	647	+| |AttachmentConstraint
	648	+| |ContentConstraint
	649	+| |Subscription
	650	+| |
	651	+|mapping|StructureMap
	652	+| |StructureSet
	653	+| |ComponentMap
	654	+|**Package**|(((
	655	+**URN Classname (model classname**
673	673
	657	+**where this is different)**
	658	+)))
	659	+| |ConceptSchemeMap
	660	+| |OrganisationSchemeMap
	661	+| |CodelistMap
	662	+| |CategorySchemeMap
	663	+| |ReportingTaxonomyMap
	664	+| |ConceptMap
	665	+| |OrganisationMap
	666	+| |CodeMap
	667	+| |HybridCodelistMap
	668	+| |CategoryMap
	669	+| |HybridCodeMap
	670	+| |ReportingCategoryMap
	671	+| |
	672	+|codelist|Codelist
	673	+| |HierarchicalCodelist
	674	+| |Hierarchy
	675	+| |Hierarchy
	676	+| |Code
	677	+| |HierarchicalCode
	678	+| |Level
	679	+| |
	680	+|categoryscheme|CategoryScheme
	681	+| |Category
	682	+| |Categorisation
	683	+| |ReportingTaxonomy
	684	+| |ReportingCategory
	685	+| |
	686	+|conceptscheme|ConceptScheme
	687	+| |Concept
	688	+| |
	689	+|transformation|TransformationScheme
	690	+| |Transformation
	691	+| |CustomTypeScheme
	692	+| |CustomType
	693	+| |NamePersonalisationScheme
	694	+| |NamePersonalisation
	695	+| |VtlCodelistMapping
	696	+| |VtlConceptMapping
	697	+| |VtlDataflowMapping
	698	+| |VtlConceptSchemeMapping
	699	+| |RulesetScheme
	700	+| |Ruleset
	701	+| |UserDefinedOperatorScheme
	702	+| |UserDefinedOperator
	703	+| |
	704	+
674	674	**Table 2: SDMX-IM Packages and Contained Classes**
675	675
	707	+
676	676	=== 6.2.4 URN Identification components of SDMX objects ===
677	677
678	678	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.
...	...	@@ -681,52 +681,78 @@
681	681
682	682	Note that for brevity the URN examples omit the prefix. All URNs have the prefix
683	683
684		-> urn:sdmx.org.sdmx.infomodel.{package}.{classname}=
	716	+urn:sdmx.org.sdmx.infomodel.{package}.{classname}=
685	685
686		-(% style="width:1091.29px" %)
687		-|(% style="width:250px" %)**SDMX Class**|(% style="width:444px" %)**Key attribute(s)**|(% style="width:396px" %)**Example of URN**
688		-|(% style="width:250px" %)Agency|(% style="width:444px" %)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:396px" %)(((
	718	+
	719	+|**SDMX Class**|**Key attribute(s)**|**Example of URN**
	720	+|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.|(((
689	689	IMF
	722	+
	723	+
690	690	Sub agency in the IMF AGENCIES
	725	+
	726	+
691	691	IMF.SubAgency1
692	692	)))
693		-|(% style="width:250px" %)*ConceptScheme|(% style="width:444px" %)conceptSchemeAgencyId:conceptSchemeId(ve rsion)|(% style="width:396px" %)SDMX:CROSS_DOMAIN_CONCEPTS(1.0)
694		-|(% style="width:250px" %)Concept|(% style="width:444px" %)conceptSchemeAgencyId:
695		-conceptSchemeId(version).conceptId|(% style="width:396px" %)SDMX:CROSS_DOMAIN_CONCEPTS(1.0).FREQ
696		-|(% style="width:250px" %)*Codelist|(% style="width:444px" %)codeListAgencyId:codeListId(version)|(% style="width:396px" %)SDMX:CL_FREQ(1.0)
697		-|(% style="width:250px" %)Code|(% style="width:444px" %)codeListAgencyId:codelistId(version).codeId|(% style="width:396px" %)SDMX:CL_FREQ(1.0).Q
698		-|(% style="width:250px" %)(((
699		-*Hierarchical Codelist
700		-)))|(% style="width:444px" %)hierachicalCodelistAgencyId: hierarchicalCodelistId(version)|(% style="width:396px" %)(((
701		-UNESCO:CL_EXP_SOURCE(1.0(% style="background-color:transparent" %))
	729	+|*ConceptScheme|conceptSchemeAgencyId:conceptSchemeId(ve rsion)|SDMX:CROSS_DOMAIN_CONCEPTS(1.0)
	730	+|Concept|(((
	731	+conceptSchemeAgencyId:
	732	+
	733	+conceptSchemeId(version).conceptId
	734	+)))|SDMX:CROSS_DOMAIN_CONCEPTS(1.0).FREQ
	735	+|*Codelist|codeListAgencyId:codeListId(version)|SDMX:CL_FREQ(1.0)
	736	+|Code|codeListAgencyId:codelistId(version).codeId|(((
	737	+SDMX:CL_FREQ(1.0).Q
	738	+
	739	+
702	702	)))
703		-|(% style="width:250px" %)Hierarchy|(% style="width:444px" %)(((
	741	+
	742	+
	743	+
	744	+|(((
	745	+*Hierarchical
	746	+
	747	+Codelist
	748	+)))|hierachicalCodelistAgencyId: hierarchicalCodelistId(version)|(((
	749	+UNESCO:CL_EXP_SOURCE(1.0)
	750	+
	751	+
	752	+)))
	753	+|Hierarchy|(((
704	704	hierachicalcodeListAgencyId:
	755	+
705	705	hierarchicalcodelistId(version).Hierarchy
706		-)))|(% style="width:396px" %)UNESCO:CL_EXP_SOURCE(1.0).
707		-H-C-GOV
708		-|(% style="width:250px" %)Level|(% style="width:444px" %)(((
	757	+)))|UNESCO:CL_EXP_SOURCE(1.0). H-C-GOV
	758	+|Level|(((
709	709	hierachicalcodeListAgencyId:
	760	+
710	710	hierarchicalcodelistId(version).Hierarchy.Level
711		-)))|(% style="width:396px" %)(((
	762	+)))|(((
712	712	ESTAT:HCL_REGION(1.0).H_1.COUNTRY
713	713
714	714
715	715	)))
716		-|(% style="width:250px" %)HierarchicalCode|(% style="width:444px" %)hierachicalCodeListAgencyId: hierarchicalcodelistId(version).hierarchy.hierarc hicalCode|(% style="width:396px" %)UNESCO:CL_EXP_SOURCE(1.0). H-C-GOV.GOV_CODE1
717		-|(% style="width:250px" %)*DataStructure|(% style="width:444px" %)dataStructureDefintitionAgencyId: dataStructureDefintitionId(version)|(% style="width:396px" %)TFFS:EXT_DEBT(1.0)
718		-|(% style="width:250px" %)(((
	767	+|HierarchicalCode|hierachicalCodeListAgencyId: hierarchicalcodelistId(version).hierarchy.hierarc hicalCode|UNESCO:CL_EXP_SOURCE(1.0). H-C-GOV.GOV_CODE1
	768	+|*DataStructure|dataStructureDefintitionAgencyId: dataStructureDefintitionId(version)|TFFS:EXT_DEBT(1.0)
	769	+|(((
719	719	Dimension
	771	+
720	720	Descriptor
	773	+
721	721	Measure
	775	+
722	722	Descriptor
	777	+
723	723	Attribute
	779	+
724	724	Descriptor
725		-)))|(% style="width:444px" %)(((
	781	+)))|(((
726	726	dataStructureDefinitionAgencyId: dataStructureDefinitionId(version).
	783	+
727	727	componentListId
	785	+
728	728	where the componentListId is the name of the class (there is only one occurrence of each in the Data Structure Definition)
729		-)))|(% style="width:396px" %)(((
	787	+)))|(((
730	730	TFFS:EXT_DEBT(1.0).DimensionDescriptor
731	731
732	732	TFFS:EXT_DEBT(1.0).MeasureDescriptor
...	...	@@ -733,132 +733,181 @@
733	733
734	734	TFFS:EXT_DEBT(1.0).AttributeDescriptor
735	735	)))
736		-|(% style="width:250px" %)(((
	794	+|(((
737	737	GroupDimension
	796	+
738	738	Descriptor
739		-)))|(% style="width:444px" %)(((
	798	+)))|(((
740	740	dataStructureDefinitionAgencyId: dataStructureDefinitionId(version).
	800	+
741	741	groupDimensionDescriptorId
742		-)))|(% style="width:396px" %)TFFS:EXT_DEBT(1.0).SIBLING
743		-|(% style="width:250px" %)Dimension|(% style="width:444px" %)(((
	802	+)))|TFFS:EXT_DEBT(1.0).SIBLING
	803	+|Dimension|(((
744	744	dataStructureDefinitionAgencyId: dataStructureDefinition (version).
	805	+
745	745	dimensionId
746		-)))|(% style="width:396px" %)TFFS:EXT_DEBT(1.0).FREQ
747		-|(% style="width:250px" %)TimeDimension|(% style="width:444px" %)(((
	807	+)))|TFFS:EXT_DEBT(1.0).FREQ
	808	+|TimeDimension|(((
748	748	dataStructureDefinitionAgencyId: dataStructureDefinition (version).
	810	+
749	749	timeDimensionId
750		-)))|(% style="width:396px" %)TFFS:EXT_DEBT(1.0).TIME_PERIOD
751		-|(% style="width:250px" %)Measure Dimension|(% style="width:444px" %)dataStructureDefinitionAgencyId: dataStructureDefinition (version).
752		-measureDimensionId|(% style="width:396px" %)TFFS:EXT_DEBT(1.0).STOCK_FLOW
753		-|(% style="width:250px" %)DataAttrribute|(% style="width:444px" %)dataStructureDefinitionAgencyId: dataStructureDefinition (version). dataAttributeId|(% style="width:396px" %)TFFS:EXT_DEBT(1.0).OBS_STATUS
754		-|(% style="width:250px" %)PrimaryMeasure|(% style="width:444px" %)(((
	812	+)))|TFFS:EXT_DEBT(1.0).TIME_PERIOD
	813	+|Measure Dimension|dataStructureDefinitionAgencyId: dataStructureDefinition (version).|TFFS:EXT_DEBT(1.0).STOCK_FLOW
	814	+
	815	+
	816	+
	817	+| |measureDimensionId|
	818	+|DataAttrribute|dataStructureDefinitionAgencyId: dataStructureDefinition (version). dataAttributeId|TFFS:EXT_DEBT(1.0).OBS_STATUS
	819	+|PrimaryMeasure|(((
755	755	dataStructureDefinitionAgencyId: dataStructureDefinition (version).
	821	+
756	756	primaryMeasureId
757		-)))|(% style="width:396px" %)TFFS:EXT_DEBT(1.0).OBS_VALUE
758		-|(% style="width:250px" %)(((
759		-*Category Scheme
760		-)))|(% style="width:444px" %)categorySchemeAgencyId:
761		-categorySchemeId(version)|(% style="width:396px" %)IMF:SDDS(1.0)
762		-|(% style="width:250px" %)Category|(% style="width:444px" %)categorySchemeAgencyId:
763		-categorySchemeId(version).
764		-categoryId.categoryId categoryId.categoryId etc.|(% style="width:396px" %)(((
	823	+)))|TFFS:EXT_DEBT(1.0).OBS_VALUE
	824	+|(((
	825	+*Category
	826	+
	827	+Scheme
	828	+)))|categorySchemeAgencyId: categorySchemeId(version)|IMF:SDDS(1.0)
	829	+|Category|categorySchemeAgencyId: categorySchemeId(version). categoryId.categoryId categoryId.categoryId etc.|(((
765	765	IMF:SDDS(1.0):
	831	+
766	766	level_1_category.level_2_category …
767	767	)))
768		-|(% style="width:250px" %)(((
769		-*Reporting Taxonomy
770		-)))|(% style="width:444px" %)reportingTaxonomyAgencyId: reportingTaxonomyId(version)|(% style="width:396px" %) IMF:REP_1(1.0)
771		-|(% style="width:250px" %)ReportingCategory|(% style="width:444px" %)reportingTaxonomyAgencyId: reportingTaxonomyId(version) reportingcategoryId.reportingcategoryId|(% style="width:396px" %)(((
	834	+|(((
	835	+*Reporting
	836	+
	837	+Taxonomy
	838	+)))|reportingTaxonomyAgencyId: reportingTaxonomyId(version)| IMF:REP_1(1.0)
	839	+|ReportingCategory|reportingTaxonomyAgencyId: reportingTaxonomyId(version) reportingcategoryId.reportingcategoryId|(((
772	772	IMF:REP_1(1.0):
	841	+
773	773	level_1_repcategory.level_2_repcategory …
774	774	)))
775		-|(% style="width:250px" %)*Categorisation|(% style="width:444px" %)categorisationAgencyId: categorisationId(version)|(% style="width:396px" %)IMF:cat001(1.0)
776		-|(% style="width:250px" %)(((
777		-*Organisation Unit Scheme
778		-)))|(% style="width:444px" %)organisationUnitSchemeAgencyId: organisationUnitSchemeId(version)|(% style="width:396px" %)ECB:ORGANISATIONS(1.0)
779		-|(% style="width:250px" %)Organisation Unit|(% style="width:444px" %)organisationUnitSchemeAgencyId: organisationUnitSchemeId(version). organisationUnitId|(% style="width:396px" %)ECB:ORGANISATIONS(1.0).1F
780		-|(% style="width:250px" %)*AgencyScheme|(% style="width:444px" %)agencySchemeAgencyId: agencySchemeId(version)|(% style="width:396px" %)ECB:AGENCIES(1.0)
	844	+|*Categorisation|categorisationAgencyId: categorisationId(version)|IMF:cat001(1.0)
	845	+|(((
	846	+*Organisation
781	781
782		-|(% style="width:262px" %)Agency|(% style="width:369px" %)agencySchemeAgencyId: agencySchemeId(version). agencyId|(% style="width:1262px" %)ECB:AGENCY(1.0).AA
783		-|(% style="width:262px" %)(((
784		-*DataProvider Scheme
785		-)))|(% style="width:369px" %)dataProviderSchemeAgencyId: dataProviderSchemeId(version)|(% style="width:1262px" %)SDMX:DATA_PROVIDERS(1.0)
786		-|(% style="width:262px" %)DataProvider|(% style="width:369px" %)dataProviderSchemeAgencyId: dataProviderSchemeId(version) dataProviderId|(% style="width:1262px" %)SDMX:DATA_PROVIDERS(1.0).PROVIDER_1
787		-|(% style="width:262px" %)(((
788		-*DataConsumer Scheme
789		-)))|(% style="width:369px" %)dataConsumerSchemeAgencyId: dataConsumerSchemeId(version)|(% style="width:1262px" %)SDMX:DATA_CONSUMERS(1.0)
790		-|(% style="width:262px" %)Data Consumer|(% style="width:369px" %)dataConsumerSchemeAgencyId: dataConsumerSchemeId(version) dataConsumerId|(% style="width:1262px" %)SDMX:DATA_CONSUMERS(1.0).CONSUMER_1
791		-|(% style="width:262px" %)(((
792		-*Metadata Structure
793		-)))|(% style="width:369px" %)MSDAgencyId:MSDId(version)|(% style="width:1262px" %)IMF:SDDS_MSD(1.0)
794		-|(% style="width:262px" %)MetadataTarget|(% style="width:369px" %)(((
	848	+Unit Scheme
	849	+)))|organisationUnitSchemeAgencyId: organisationUnitSchemeId(version)|ECB:ORGANISATIONS(1.0)
	850	+|Organisation Unit|organisationUnitSchemeAgencyId: organisationUnitSchemeId(version). organisationUnitId|ECB:ORGANISATIONS(1.0).1F
	851	+|*AgencyScheme|agencySchemeAgencyId: agencySchemeId(version)|ECB:AGENCIES(1.0)
	852	+
	853	+
	854	+
	855	+|Agency|agencySchemeAgencyId: agencySchemeId(version). agencyId|ECB:AGENCY(1.0).AA
	856	+|(((
	857	+*DataProvider
	858	+
	859	+Scheme
	860	+)))|dataProviderSchemeAgencyId: dataProviderSchemeId(version)|SDMX:DATA_PROVIDERS(1.0)
	861	+|DataProvider|dataProviderSchemeAgencyId: dataProviderSchemeId(version) dataProviderId|SDMX:DATA_PROVIDERS(1.0).PROVIDER_1
	862	+|(((
	863	+*DataConsumer
	864	+
	865	+Scheme
	866	+)))|dataConsumerSchemeAgencyId: dataConsumerSchemeId(version)|SDMX:DATA_CONSUMERS(1.0)
	867	+|Data Consumer|dataConsumerSchemeAgencyId: dataConsumerSchemeId(version) dataConsumerId|SDMX:DATA_CONSUMERS(1.0).CONSUMER_1
	868	+|(((
	869	+*Metadata
	870	+
	871	+Structure
	872	+)))|MSDAgencyId:MSDId(version)|IMF:SDDS_MSD(1.0)
	873	+|MetadataTarget|(((
795	795	MSDAgencyId:
	875	+
796	796	MSDId(version).metadataTargetId
797		-)))|(% style="width:1262px" %)IMF:SDDS_MSD(1.0).AGENCY
798		-|(% style="width:262px" %)(((
	877	+)))|IMF:SDDS_MSD(1.0).AGENCY
	878	+|(((
799	799	Dimension
	880	+
800	800	DescriptorValues
	882	+
801	801	Target
802		-)))|(% style="width:369px" %)(((
	884	+)))|(((
803	803	MSDAgencyId: MSDId(version).
	886	+
804	804	metadataTargetId.keyDescriptorValueTargetId
805		-)))|(% style="width:1262px" %)IMF:SDDS_MSD(1.0).AGENCY.KEY
806		-|(% style="width:262px" %)Identifiable Object Target|(% style="width:369px" %)(((
807		-MSDAgencyId: MSDId(version).metadataTargetId.identifiableObjectTargetId
808		-)))|(% style="width:1262px" %)IMF:SDDS_MSD(1.0).AGENCY.STR-OBJECT
809		-|(% style="width:262px" %)DataSetTarget|(% style="width:369px" %)(((
	888	+)))|IMF:SDDS_MSD(1.0).AGENCY.KEY
	889	+|Identifiable ObjectTarget|(((
810	810	MSDAgencyId:
811		-MSDId(version).metadataTargetId.dataSetTargetId
812		-)))|(% style="width:1262px" %)IMF:SDDS_MSD(1.0).AGENCY.D1101
813		-|(% style="width:262px" %)PeportPeriod Target|(% style="width:369px" %)(((
814		-MSDAgencyId: MSDId(version).metadataTargetId.reportPeriodTargetId
815		-)))|(% style="width:1262px" %)IMF:SDDS_MSD(1.0).AGENCY.REP_PER
816	816
817		-|(% style="width:251px" %)(((
	892	+MSDId(version).metadataTargetId.identifiable
	893	+
	894	+ObjectTargetId
	895	+)))|IMF:SDDS_MSD(1.0).AGENCY.STR-OBJECT
	896	+|DataSetTarget|(((
	897	+MSDAgencyId:
	898	+
	899	+MSDId(version).metadataTargetId.dataSet
	900	+
	901	+TargetId
	902	+)))|IMF:SDDS_MSD(1.0).AGENCY.D1101
	903	+|PeportPeriod Target|(((
	904	+MSDAgencyId:
	905	+
	906	+MSDId(version).metadataTargetId.reportPeriod
	907	+
	908	+TargetId
	909	+)))|IMF:SDDS_MSD(1.0).AGENCY.REP_PER
	910	+
	911	+
	912	+
	913	+|(((
818	818	ReportStructure
819	819
820	820
821		-)))|(% style="width:442px" %)(((
822		-MSDAgencyId: MSDId(version).reportStructureId
823		-)))|(% style="width:1178px" %)IMF:SDDS_MSD(1.0).AGENCY_REPORT
824		-|(% style="width:251px" %)(((
	917	+)))|(((
	918	+MSDAgencyId:
	919	+
	920	+MSDId(version).reportStructureId
	921	+)))|IMF:SDDS_MSD(1.0).AGENCY_REPORT
	922	+|(((
825	825	Metadata
826	826
827	827	Attribute
828		-)))|(% style="width:442px" %)(((
829		-MSDAgencyId: MSDId(version).reportStructureId.metadataattri buteID
830		-)))|(% style="width:1178px" %)IMF:SDDS_MSD(1.0).AGENCY_REPORT.COMPILATION
831		-|(% style="width:251px" %)*Dataflow|(% style="width:442px" %)dataflowAgencyId: dataflowId(version)|(% style="width:1178px" %)TFFS:CRED_EXT_DEBT(1.0)
832		-|(% style="width:251px" %)*Provision Agreement|(% style="width:442px" %)(((
	926	+)))|(((
	927	+MSDAgencyId:
	928	+
	929	+MSDId(version).reportStructureId.metadataattri buteID
	930	+)))|IMF:SDDS_MSD(1.0).AGENCY_REPORT.COMPILATION
	931	+|*Dataflow|dataflowAgencyId: dataflowId(version)|TFFS:CRED_EXT_DEBT(1.0)
	932	+|*Provision Agreement|(((
833	833	provisionAgreementAgencyId:provisionAgreem entId(version)
834		-)))|(% style="width:1178px" %)(((
	934	+
	935	+
	936	+)))|(((
835	835	TFFS:CRED_EXT_DEBT_AB(1.0)
	938	+
	939	+
	940	+
836	836	)))
837		-|(% style="width:251px" %)(((
	942	+|(((
838	838	*Content
839	839
840	840	Constraint
841		-)))|(% style="width:442px" %)constraintAgencyId:ContentConstraintId(versio n)|(% style="width:1178px" %)TFFS:CREDITOR_DATA_CONTENT(1.0)
842		-|(% style="width:251px" %)(((
	946	+)))|constraintAgencyId:ContentConstraintId(versio n)|TFFS:CREDITOR_DATA_CONTENT(1.0)
	947	+|(((
843	843	*Attachment
844	844
845	845	Constraint
846		-)))|(% style="width:442px" %)(((
	951	+)))|(((
847	847	constraintAgencyId:
848	848
849	849	attachmentConstraintId(version)
850		-)))|(% style="width:1178px" %)TFFS:CREDITOR_DATA_ATTACHMENT_CONSTRAINT_ONE(1.0)
851		-|(% style="width:251px" %)*Metadataflow|(% style="width:442px" %)metadataflowAgencyId: metadataflowId(version)|(% style="width:1178px" %)IMF:SDDS_FLOW(1.0)
852		-|(% style="width:251px" %)*StructureSet|(% style="width:442px" %)structureSetAgencyId: structureSetId(version)|(% style="width:1178px" %)SDMX:BOP_STRUCTURES(1.0)
853		-|(% style="width:251px" %)StructureMap|(% style="width:442px" %)structureSetAgencyId: structureSetId(version). structureMapId|(% style="width:1178px" %)SDMX:BOP_STRUCTURES(1.0).TABLE1_TABLE2
854		-|(% style="width:251px" %)Component Map|(% style="width:442px" %)(((
	955	+)))|TFFS:CREDITOR_DATA_ATTACHMENT_CONSTRAINT_ONE(1.0)
	956	+|*Metadataflow|metadataflowAgencyId: metadataflowId(version)|IMF:SDDS_FLOW(1.0)
	957	+|*StructureSet|structureSetAgencyId: structureSetId(version)|SDMX:BOP_STRUCTURES(1.0)
	958	+|StructureMap|structureSetAgencyId: structureSetId(version). structureMapId|SDMX:BOP_STRUCTURES(1.0).TABLE1_TABLE2
	959	+|Component Map|(((
855	855	structureSetAgencyId: structureSetId(version).
856	856
857	857	structureMapId. componentMapId
858		-)))|(% style="width:1178px" %)SDMX:BOP_STRUCTURES(1.0).TABLE1_TABLE2. REFAREA_REPCOUNTRY
859		-|(% style="width:251px" %)CodelistMap|(% style="width:442px" %)structureSetAgencyId: structureSetId(version). codelistMapId|(% style="width:1178px" %)SDMX:BOP_STRUCTURES(1.0).CLREFAREA_CLREPCOUNTRY
860		-|(% style="width:251px" %)CodeMap|(% style="width:442px" %)structureSetAgencyId: structureSetId(version).|(% style="width:1178px" %)SDMX:BOP_STRUCTURES(1.0).CLREFAREA_CLREPCOUNTRY. DE_GER
	963	+)))|SDMX:BOP_STRUCTURES(1.0).TABLE1_TABLE2. REFAREA_REPCOUNTRY
	964	+|CodelistMap|structureSetAgencyId: structureSetId(version). codelistMapId|SDMX:BOP_STRUCTURES(1.0).CLREFAREA_CLREPCOUNTRY
	965	+|CodeMap|structureSetAgencyId: structureSetId(version).|SDMX:BOP_STRUCTURES(1.0).CLREFAREA_CLREPCOUNTRY. DE_GER
861	861
	967	+
	968	+
862	862	| |(((
863	863	codeListMapId.
864	864
...	...	@@ -966,6 +966,7 @@
966	966
967	967	7**Table 3: Table of identification components for SDMX Identifiable Artefacts**
968	968
	1076	+
969	969	= 7 Implementation Notes =
970	970
971	971	== 7.1 Structural Definition Metadata ==
...	...	@@ -986,72 +986,109 @@
986	986
987	987	The following table lists the Maintainable Artefacts.
988	988
989		-(% style="width:640.294px" %)
990		-|(% colspan="2" rowspan="1" style="width:186px" %)**Maintainable Artefacts**|(% style="width:206px" %)**Content**
991		-|(% style="width:171px" %)**Abstract Class**|(% style="width:232px" %)**Concrete Class**|(% style="width:206px" %)
992		-|(% style="width:171px" %)Item Scheme|(% style="width:232px" %)Codelist|(% style="width:206px" %)Code
993		-|(% style="width:171px" %) |(% style="width:232px" %)Concept Scheme|(% style="width:206px" %)Concept
994		-|(% style="width:171px" %) |(% style="width:232px" %)Category Scheme|(% style="width:206px" %)Category
995		-|(% style="width:171px" %) |(% style="width:232px" %)Organisation Unit Scheme|(% style="width:206px" %)Organisation Unit
996		-|(% style="width:171px" %) |(% style="width:232px" %)Agency Scheme|(% style="width:206px" %)Agency
997		-|(% style="width:171px" %) |(% style="width:232px" %)Data Provider Scheme|(% style="width:206px" %)Data Provider
998		-|(% style="width:171px" %) |(% style="width:232px" %)Data Consumer Scheme|(% style="width:206px" %)Data Consumer
999		-|(% style="width:171px" %) |(% style="width:232px" %)Reporting Taxonomy|(% style="width:206px" %)Reporting Category
1000		-|(% style="width:171px" %) |(% style="width:232px" %)Transformation Scheme|(% style="width:206px" %)Transformation
1001		-|(% style="width:171px" %) |(% style="width:232px" %)Custom Type Scheme|(% style="width:206px" %)Custom Type
1002		-|(% style="width:171px" %) |(% style="width:232px" %)Name Personalisation Scheme|(% style="width:206px" %)Name Personalisation
1003		-|(% style="width:171px" %) |(% style="width:232px" %)Vtl Mapping Scheme|(% style="width:206px" %)Vtl Codelist Mapping
1004		-|(% style="width:171px" %) |(% style="width:232px" %) |(% style="width:206px" %)Vtl Dataflow Mapping
1005		-|(% style="width:171px" %) |(% style="width:232px" %) |(% style="width:206px" %)Vtl Concept Scheme Mapping
1006		-|(% style="width:171px" %) |(% style="width:232px" %)Ruleset Scheme|(% style="width:206px" %)Ruleset
1007		-|(% style="width:171px" %) |(% style="width:232px" %)User Defined Operator Scheme|(% style="width:206px" %)User Defined Operator
1008		-|(% style="width:171px" %) |(% style="width:232px" %) |(% style="width:206px" %)User Defined Operator
1009		-|(% style="width:171px" %)Structure|(% style="width:232px" %)Data Structure Definition|(% style="width:206px" %)(((
	1097	+|(% colspan="4" %)**Maintainable Artefacts**|(% colspan="2" %)**Content**|
	1098	+|(% colspan="2" %)**Abstract Class**|(% colspan="2" %)**Concrete Class**|(% colspan="2" %) |
	1099	+|(% colspan="2" %)Item Scheme|(% colspan="2" %)Codelist|(% colspan="2" %)Code|
	1100	+|(% colspan="2" %) |(% colspan="2" %)Concept Scheme|(% colspan="2" %)Concept|
	1101	+|(% colspan="2" %) |(% colspan="2" %)Category Scheme|(% colspan="2" %)Category|
	1102	+|(% colspan="2" %) |(% colspan="2" %)Organisation Unit Scheme|(% colspan="2" %)Organisation Unit|
	1103	+|(% colspan="2" %) |(% colspan="2" %)Agency Scheme|(% colspan="2" %)Agency|
	1104	+|(% colspan="2" %) |(% colspan="2" %)Data Provider Scheme|(% colspan="2" %)Data Provider|
	1105	+|(% colspan="2" %) |(% colspan="2" %)Data Consumer Scheme|(% colspan="2" %)Data Consumer|
	1106	+|(% colspan="2" %) |(% colspan="2" %)Reporting Taxonomy|(% colspan="2" %)Reporting Category|
	1107	+|(% colspan="2" %) |(% colspan="2" %)Transformation Scheme|(% colspan="2" %)Transformation|
	1108	+|(% colspan="2" %) |(% colspan="2" %)Custom Type Scheme|(% colspan="2" %)Custom Type|
	1109	+| |(% colspan="4" %)**Maintainable Artefacts**|(% colspan="2" %)**Content**
	1110	+| |(% colspan="2" %)**Abstract Class**|(% colspan="2" %)**Concrete Class**|(% colspan="2" %)
	1111	+| |(% colspan="2" %) |(% colspan="2" %)Name Personalisation Scheme|(% colspan="2" %)Name Personalisation
	1112	+| |(% colspan="2" %) |(% colspan="2" %)Vtl Mapping Scheme|(% colspan="2" %)Vtl Codelist Mapping
	1113	+| |(% colspan="2" %) |(% colspan="2" %) |(% colspan="2" %)Vtl Concept Mapping
	1114	+| |(% colspan="2" %) |(% colspan="2" %) |(% colspan="2" %)Vtl Dataflow Mapping
	1115	+| |(% colspan="2" %) |(% colspan="2" %) |(% colspan="2" %)(((
	1116	+Vtl Concept Scheme
	1117	+
	1118	+Mapping
	1119	+)))
	1120	+| |(% colspan="2" %) |(% colspan="2" %)Ruleset Scheme|(% colspan="2" %)Ruleset
	1121	+| |(% colspan="2" %) |(% colspan="2" %)User Defined Operator Scheme|(% colspan="2" %)User Defined Operator
	1122	+| |(% colspan="2" %) |(% colspan="2" %) |(% colspan="2" %)
	1123	+| |(% colspan="2" %)Structure|(% colspan="2" %)Data Structure Definition|(% colspan="2" %)(((
1010	1010	Dimension Descriptor
	1125	+
1011	1011	Group Dimension
	1127	+
1012	1012	Descriptor
	1129	+
1013	1013	Dimension
	1131	+
1014	1014	Measure Dimension
	1133	+
1015	1015	Time Dimension
	1135	+
1016	1016	Attribute Descriptor
	1137	+
1017	1017	Data Attribute
	1139	+
1018	1018	Measure Descriptor
	1141	+
1019	1019	Primary Measure
1020	1020	)))
1021		-|(% style="width:171px" %) |(% style="width:232px" %)Metadata Structure Definition|(% style="width:206px" %)(((
1022		-Metadata Target, Dimension Descriptor
	1144	+| |(% colspan="2" %) |(% colspan="2" %)Metadata Structure Definition|(% colspan="2" %)(((
	1145	+Metadata Target,
	1146	+
	1147	+Dimension Descriptor
	1148	+
1023	1023	Values Target Identifiable
	1150	+
1024	1024	Object Target
	1152	+
1025	1025	Report Period Target
	1154	+
1026	1026	Data SetTarget
	1156	+
1027	1027	Report Structure
	1158	+
1028	1028	Metadata Attribute
1029	1029	)))
1030		-|(% style="width:171px" %)Structure Usage|(% style="width:232px" %)Dataflow Definition|(% style="width:206px" %)
1031		-|(% style="width:171px" %) |(% style="width:232px" %)Metadataflow Definition|(% style="width:206px" %)
1032		-|(% style="width:171px" %)None|(% style="width:232px" %)Process|(% style="width:206px" %)Process Step
1033		-|(% style="width:171px" %)None|(% style="width:232px" %)Structure Set|(% style="width:206px" %)(((
	1161	+| |(% colspan="2" %)Structure Usage|(% colspan="2" %)Dataflow Definition|(% colspan="2" %)
	1162	+| |(% colspan="2" %) |(% colspan="2" %)Metadataflow Definition|(% colspan="2" %)
	1163	+| |(% colspan="2" %)None|(% colspan="2" %)Process|(% colspan="2" %)Process Step
	1164	+| |(% colspan="2" %)None|(% colspan="2" %)Structure Set|(% colspan="2" %)(((
1034	1034	Component Map
	1166	+
1035	1035	Concept Scheme Map
	1168	+
1036	1036	Codelist Map
	1170	+
1037	1037	Category Scheme Map
	1172	+
1038	1038	Reporting Taxonomy Map
	1174	+
1039	1039	Organisation Scheme Map
	1176	+
1040	1040	Concept Map
	1178	+
1041	1041	Code Map
	1180	+
1042	1042	Category Map
	1182	+
1043	1043	Organisation Map
	1184	+
1044	1044	Reporting Category Map
	1186	+
1045	1045	Hybrid Codelist Map
	1188	+
1046	1046	Hybrid Code Map
1047	1047	)))
1048		-|(% style="width:171px" %)None|(% style="width:232px" %)Provision Agreement|(% style="width:206px" %)
1049		-|(% style="width:171px" %)None|(% style="width:232px" %)Hierarchical Codelist|(% style="width:206px" %)(((
	1191	+| |(% colspan="2" %)None|(% colspan="2" %)Provision Agreement|(% colspan="2" %)
	1192	+| |(% colspan="2" %)None|(% colspan="2" %)Hierarchical Codelist|(% colspan="2" %)(((
1050	1050	Hierarchy
	1194	+
1051	1051	Hierarchical Code
1052	1052	)))
	1197	+| | | | | | |
1053	1053
1054		-**able 4: Table of Maintainable Artefacts for Structural Definition Metadata**
	1199	+**Table 4: Table of Maintainable Artefacts for Structural Definition Metadata**
1055	1055
1056	1056	=== 7.1.2 Item Scheme, Structure ===
1057	1057
...	...	@@ -1058,7 +1058,10 @@
1058	1058	The artefacts included in the structural definitions are:
1059	1059
1060	1060	* All types of Item Scheme (Codelist, Concept Scheme, Category Scheme, Organisation Scheme - Agency Scheme, Data Provider Scheme, Data Consumer Scheme, Organisation Unit Scheme)
1061		-* All types of Structure (Data Structure Definition, Metadata Structure Definition)
	1206	+* All types of Structure (Data Structure Definition, Metadata Structure
	1207	+
	1208	+Definition)
	1209	+
1062	1062	* All types of Structure Usage (Dataflow Definition, Metadataflow Definition)
1063	1063
1064	1064	=== 7.1.3 Structure Usage ===
...	...	@@ -1077,8 +1077,6 @@
1077	1077
1078	1078	==== 7.1.3.3 Structure Usage Model ====
1079	1079
1080		-[[image:1747829078194-749.png]]
1081		-
1082	1082	**Figure 10: SDMX-IM of links from Structure Usage to Category**
1083	1083
1084	1084	In addition to the maintenance of the Dataflow Definition and the Metadataflow Definition the following links must be maintained in the registry:
...	...	@@ -1105,10 +1105,10 @@
1105	1105
1106	1106	An organisation which publishes statistical data or reference metadata and wishes to make it available to an SDMX enabled community is called a Data Provider. In terms of the SDMX Information Model, the Data Provider is maintained in a Data Provider Scheme.
1107	1107
1108		-[[image:1747829109466-595.png]]
1109	1109
1110	1110	**Figure 11: SDMX-IM of the Data Provider**
1111	1111
	1257	+
1112	1112	Note that the Data Provider does not inherit the hierarchy association. The diagram below shows a logical schematic of the data model classes required to maintain provision agreements
1113	1113
1114	1114	[[image:1747824123019-181.jpeg]]
...	...	@@ -1117,10 +1117,8 @@
1117	1117
1118	1118	The diagram below is a logical representation of the data required in order to maintain Provision Agreements.
1119	1119
1120		-[[image:1747829139951-378.png]]
1121	1121
1122		-(% class="wikigeneratedid" id="HFigure13:LogicalclassdiagramoftheinformationcontainedintheProvisionAgreement" %)
1123		-**Figure 13: Logical class diagram of the information contained in the Provision Agreement**
	1267	+==== Figure 13: Logical class diagram of the information contained in the Provision Agreement ====
1124	1124
1125	1125	A Provision Agreement is structural metadata. Each Provision Agreement must reference a Data Provider and a Dataflow or Metadataflow Definition. The Data Provider and the Dataflow/Metadataflow Definition must exist already in order to set up a Provision Agreement.
1126	1126
...	...	@@ -1148,12 +1148,13 @@
1148	1148
1149	1149	=== 7.3.3 Data and Metadata Constraints: Model ===
1150	1150
1151		-[[image:1747829204737-370.png]]
1152	1152
1153		-**Figure 15: Logical class diagram showing inheritance between and reference to constrainable artifacts**
1154	1154
1155		-The class diagram above shows that DataProvider, DataflowDefinition, MetadataflowDefinition, ProvisionAgreement, DataStructureDefinition, MetadataStructureDefinition, SimpleDatasource and QueryDatasource are all concrete sub-classes of ConstrainableArtefact and can therefore have Constraints specified. Note that the actual Constraint as submitted is associated to the reference classes which inherit from ConstrainableRef: these are used to refer to the classes to which the Constraint applies.
	1297	+==== Figure 15: Logical class diagram showing inheritance between and reference to constrainable artifacts ====
1156	1156
	1299	+The class diagram above shows that DataProvider, DataflowDefinition, MetadataflowDefinition, ProvisionAgreement, DataStructureDefinition, MetadataStructureDefinition, SimpleDatasource and QueryDatasource are all concrete sub-classes of ConstrainableArtefact and can therefore have Constraints specified. Note that the actual Constraint as submitted is associated to the reference classes which inherit from ConstrainableRef: these are used to refer to the classes to which the Constraint applies.
	1300	+
	1301	+
1157	1157	The content of the Constraint can be found in the SDMX Information Model document.
1158	1158
1159	1159	== 7.4 Data and Metadata Registration ==
...	...	@@ -1188,14 +1188,11 @@
1188	1188
1189	1189	The Registration has an action attribute which takes one of the following values:
1190	1190
1191		-(% style="width:970.294px" %)
1192		-|(% style="width:212px" %)**Action Attribute Value**|(% style="width:756px" %)**Behaviour**
1193		-|(% style="width:212px" %)Append|(% style="width:756px" %)Add this Registration to the registry
1194		-|(% style="width:212px" %)Replace|(% style="width:756px" %)Replace the existing Registration with identified by the id in the Registration of the Submit Registration Request
1195		-|(% style="width:212px" %)Delete|(% style="width:756px" %)Delete the existing Registration identified by the id in the Registration of the Submit Registration Request
	1336	+|**Action Attribute Value**|**Behaviour**
	1337	+|Append|Add this Registration to the registry
	1338	+|Replace|Replace the existing Registration with identified by the id in the Registration of the Submit Registration Request
	1339	+|Delete|Delete the existing Registration identified by the id in the Registration of the Submit Registration Request
1196	1196
1197		-[[image:1747829290890-122.png]]
1198		-
1199	1199	**Figure 17: Logical Class Diagram of Registration of Data and Metadata**
1200	1200
1201	1201	The Query Datasource is an abstract class that represents a data source which can understand an SDMX-ML query (SOAPDatasource) or RESTful query
...	...	@@ -1210,19 +1210,25 @@
1210	1210
1211	1211	Information in the data or metadata set is extracted and placed in one or more Content Constraints (see the Constraints model in the SDMX Information Model – Section 2 of the SDMX Standards). The information to be extracted is indicated by the Boolean values set on the Provision Agreement as shown in the table below.
1212	1212
1213		-|(% style="width:185px" %)**Indexing Required**|(% style="width:1686px" %)**Registration Process Activity**
1214		-|(% style="width:185px" %)indexTimeSeries|(% style="width:1686px" %)Extract all the series keys and create a KeySet(s) Constraint.
1215		-|(% style="width:185px" %)indexDataSet|(% style="width:1686px" %)(((
1216		-Extract all the codes and other content of the Key value of the Series Key in a Data Set and create one or more Cube Regions containing Member Selections of Dimension Components of the Constraints model in the SDMX-IM, and the associated Selection Value.
	1355	+|**Indexing Required**|**Registration Process Activity**
	1356	+|indexTimeSeries|Extract all the series keys and create a KeySet(s) Constraint.
	1357	+|indexDataSet|(((
	1358	+Extract all the codes and other content of the Key value of the Series Key in a Data Set and create one or more Cube
	1359	+
	1360	+Regions containing Member Selections of Dimension Components of the Constraints model in the SDMX-IM, and the associated Selection Value.
1217	1217	)))
1218		-|(% style="width:185px" %)indexReportingPeriod|(% style="width:1686px" %)(((
	1362	+|indexReportingPeriod|(((
1219	1219	This applies only to a registered dataset.
	1364	+
1220	1220	Extract the Reporting Begin and Reporting End from the Header of the Message containing the data set, and create a Reference Period constraint.
1221	1221	)))
1222		-|(% style="width:185px" %)indexAttributes|(% style="width:1686px" %)(((
	1367	+|indexAttributes|(((
1223	1223	**Data Set**
	1369	+
1224	1224	Extract the content of the Attribute Values in a Data Set and create one or more Cube Regions containing Member Selections of Data Attribute Components of the Constraints model in the SDMXIM, and the associated Selection Value
	1371	+
1225	1225	**Metadata Set**
	1373	+
1226	1226	Indicate the presence of a Reported Attribute by creating one or more Cube Regions containing Member Selections of Metadata Attribute Components of the Constraints model in the SDMX-IM. Note that the content is not stored in the Selection Value.
1227	1227	)))
1228	1228
...	...	@@ -1232,13 +1232,14 @@
1232	1232
1233	1233	=== 7.4.3 Registration Response ===
1234	1234
1235		-After a registration request has been submitted to the registry, a response is returned to the submitter indicating success or failure. Given that a registration request can hold many Registrations, then there must be a registration status for each Registration. The Submit Registration class has a status field which is either set to “Success”, “Warning” or “Failure”.
	1383	+After a registration request has been submitted to the registry, a response is returned to the submitter indicating success or failure. Given that a registration request can hold many Registrations, then there must be a registration status for each Registration. The Submit Registration class has a status field which is either set to
1236	1236
	1385	+“Success”, “Warning” or “Failure”.
	1386	+
1237	1237	If the registration has succeeded, a Registration will be returned - this holds the Registry-allocated Id of the newly registered Datasource plus a Datasource holding the URL to access the dataset, metadataset, or query service.
1238	1238
1239	1239	The Registration Response returns set of registration status (one for each registration submitted) in terms of a Status Message (this is common to all Registry Responses) that indicates success or failure. In the event of registration failure, a set of Message Text are returned, giving the error messages that occurred during registration. It is entirely possible when registering a batch of datasets, that the response will contain some successful and some failed statuses. The logical model for the Registration Response is shown below:
1240	1240
1241		-[[image:1747829477882-750.png]]
1242	1242
1243	1243	**Figure 18: Logical class diagram showing the registration response**
1244	1244

1747824504225-229.png

Author

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

Size

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

Content

1747829078194-749.png

Author

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

Size

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

Content

1747829109466-595.png

Author

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

Size

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

Content

1747829139951-378.png

Author

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

Size

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

Content

1747829204737-370.png

Author

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

Size

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

Content

1747829290890-122.png

Author

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

Size

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

Content

1747829477882-750.png

Author

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

Size

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

Content