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

Summary

• Page properties (3 modified, 0 added, 0 removed)
• Attachments (0 modified, 9 added, 0 removed)
  • 1747829109466-595.png
  • 1747829139951-378.png
  • 1747829204737-370.png
  • 1747829290890-122.png
  • 1747829477882-750.png
  • 1747829554603-150.png
  • 1747829675568-610.png
  • 1747832400104-286.png
  • 1747994320263-112.png
• Objects (0 modified, 1 added, 0 removed)
  • SKMS.Methodology.Code.MethodologyClass[0]

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-SDMX 2.1 Standards. Section. 5. Registry Specification – Logical Interfaces
	1	+SDMX 2.1 Standards. Section 5. Registry Specification: Logical Interfaces

Author

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

Content

...	...	@@ -4,10 +4,11 @@
4	4
5	5	**Revision History**
6	6
7		-|**Revision**|**Date**|**Contents**
8		-| |April 2011|Initial release
9		-|1.0|July 2011|Rectification of problems of the specifications dated April 2011
10		-|2.0|July 2020|Addition of VTL (Validation and Transformation Language) package, maintainable artefacts, nameable artefacts to 5.2.3, 6.2.2, 6.2.3, 6.2.4, 7.1.1
	7	+(% style="width:833.294px" %)
	8	+|(% style="width:122px" %)**Revision**|(% style="width:126px" %)**Date**|(% style="width:581px" %)**Contents**
	9	+|(% style="width:122px" %) |(% style="width:126px" %)April 2011|(% style="width:581px" %)Initial release
	10	+|(% style="width:122px" %)1.0|(% style="width:126px" %)July 2011|(% style="width:581px" %)Rectification of problems of the specifications dated April 2011
	11	+|(% style="width:122px" %)2.0|(% style="width:126px" %)July 2020|(% style="width:581px" %)Addition of VTL (Validation and Transformation Language) package, maintainable artefacts, nameable artefacts to 5.2.3, 6.2.2, 6.2.3, 6.2.4, 7.1.1
11	11
12	12	**Corrigendum**
13	13
...	...	@@ -288,27 +288,22 @@
288	288	* that a queryable data source exists - this would necessitate the registration service querying the service to determine its existence
289	289	* that a simple data source exists (i.e. a file accessible at a URL)
290	290	* that the correct Data Structure Definition or Metadata Structure Definition is used by the registered data that the components (Dimensions, Attributes, Measures, Identifier Components etc.) are consistent with the Data Structure Definition or Metadata Structure Definition
291		-*  that the valid representations of the concepts to which these components 382 correspond conform to the definition in the Data Structure Definition or Metadata Structure Definition
	292	+* that the valid representations of the concepts to which these components correspond conform to the definition in the Data Structure Definition or Metadata Structure Definition
292	292
293		-3The Registration has an action attribute which takes one of the following values:
	294	+The 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
	296	+|(% style="width:219px" %)**Action Attribute Value**|(% style="width:1652px" %)**Behaviour**
	297	+|(% style="width:219px" %)Append|(% style="width:1652px" %)Add this registration to the registry
	298	+|(% style="width:219px" %)Replace|(% style="width:1652px" %)Replace the existing Registration with this Registration identified by the id in the Registration of the Submit Registration Request
	299	+|(% style="width:219px" %)Delete|(% style="width:1652px" %)Delete the existing Registration identified by the id in the Registration of the Submit Registration Request
301	301
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		-|**Boolean Attribute**|**Behaviour if Value is “true”**
305		-|indexTimeSeries|A compliant indexing application must index all the time series keys (for a Dataset registration) or metadata target values (for a Metadata Set registration)
306		-|indexDataSet|(((
307		-A compliant indexing application must index the range of actual (present) values for each dimension of the Dataset (for a Dataset registration) or the range of actual (present) values for each Metadata Attribute which takes an enumerated value.
308		-
	303	+|(% style="width:228px" %)**Boolean Attribute**|(% style="width:1644px" %)**Behaviour if Value is “true”**
	304	+|(% style="width:228px" %)indexTimeSeries|(% style="width:1644px" %)A compliant indexing application must index all the time series keys (for a Dataset registration) or metadata target values (for a Metadata Set registration)
	305	+|(% style="width:228px" %)indexDataSet|(% style="width:1644px" %)A compliant indexing application must index the range of actual (present) values for each dimension of the Dataset (for a Dataset registration) or the range of actual (present) values for each Metadata Attribute which takes an enumerated value.
309	309	Note that for data this requires much less storage than full key indexing, but this method cannot guarantee that a specific combination of Dimension values (the Key) is actually present in the Dataset
310		-)))
311		-|indexReportingPeriod|A compliant indexing application must index the time period range(s) for which data are present in the Dataset or Metadata Set
	307	+|(% style="width:228px" %)indexReportingPeriod|(% style="width:1644px" %)A compliant indexing application must index the time period range(s) for which data are present in the Dataset or Metadata Set
312	312
313	313	=== 5.2.5 Data and Reference Metadata Discovery ===
314	314
...	...	@@ -330,7 +330,7 @@
330	330	Subscription management involves a user submitting a subscription request which contains:
331	331
332	332	* a query or constraint expression in terms of a filter which defines the events for which the user is interested (e.g. new data for a specific dataflow, or for a domain category, or changes to a Data Structure Definition).
333		-* a list of URIs or end-points to which an XML notification message can be sent. Supported end-point types will be email (mailto~:) and HTTP POST (a normal http:~/~/ address)
	329	+* a list of URIs or end-points to which an XML notification message can be sent. Supported end-point types will be email (mailto : ) and HTTP POST (a normal http:~/~/ address)
334	334	* request for a list of submitted subscriptions
335	335	* deletion of a subscription
336	336
...	...	@@ -340,8 +340,8 @@
340	340
341	341	The following table defines the behaviour of the SDMX Registry for the various Registry Interface messages.
342	342
343		-|(% style="width:244px" %)**Interface**|**Behaviour**
344		-|(% style="width:244px" %)All|(((
	339	+|(% style="width:227px" %)**Interface**|(% style="width:1644px" %)**Behaviour**
	340	+|(% style="width:227px" %)All|(% style="width:1644px" %)(((
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.
...	...	@@ -355,7 +355,6 @@
355	355	* isExternalReference
356	356
357	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.
358		-
359	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:
360	360
361	361	а) Not have the final attribute set to “true”
...	...	@@ -362,12 +362,11 @@
362	362	b) Not be referenced from any other object in the Registry.
363	363
364	364	4) The version rules in the SDMX Schema documentation MUST be obeyed.
365		-
366	366	5) The specific rules for the elements and attributes documented in the SDMX Schema MUST be obeyed.
367	367	)))
368		-|(% style="width: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|(((
	362	+|(% style="width:227px" %)SubmitStructureRequest|(% style="width:1644px" %)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.
	363	+|(% style="width:227px" %)SubmitProvisioningRequest|(% style="width:1644px" %)No additional behaviour.
	364	+|(% style="width:227px" %)Submit Registration Request|(% style="width:1644px" %)(((
371	371	If the datasource is a file (simple datasource) then the file MAY be retrieved and indexed according to the Boolean attributes set in the Registration.
372	372	For a queryable datasource the Registry MAY validate that the source exists and can accept an SDMX-ML data query.
373	373	)))
...	...	@@ -433,6 +433,8 @@
433	433
434	434	The Maintenance Agency in SDMX is maintained in an Agency Scheme which itself is a sub class of Organisation Scheme – this is shown in the class diagram below.
435	435
	430	+[[image:1747994320263-112.png]]
	431	+
436	436	**Figure 6: Agency Scheme Model**
437	437
438	438	The Agency in SDMX is extremely important. The Agency Id system used in SDMX is an n-level structure. The top level of this structure is maintained by SDMX. Any Agency in this top level can declare sub agencies and any sub agency can also declare sub agencies. The Agency Scheme has a fixed id and version and is never declared explicitly in the SDMX object identification mechanism.
...	...	@@ -454,7 +454,7 @@
454	454
455	455	[[image:1747824123012-527.jpeg]]
456	456
457		-==== Figure 7: Example of Hierarchic Structure of Agencies ====
	453	+**Figure 7: Example of Hierarchic Structure of Agencies**
458	458
459	459	The following organizations maintain an Agency Scheme.
460	460
...	...	@@ -469,9 +469,8 @@
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"]]
	468	+[[image:1747832400104-286.png]]
473	473
474		-(% class="wikigeneratedid" id="HFigure8:ExampleShowingUseofAgencyIdentifiers" %)
475	475	**Figure 8: Example Showing Use of Agency Identifiers**
476	476
477	477	Each of these maintenance agencies has an identical Code list with the Id CL_BOP. However, each is uniquely identified by means of the hierarchic agency structure.
...	...	@@ -484,13 +484,14 @@
484	484
485	485	==== 6.2.2.2 URN Structure ====
486	486
487		-===== //Case Rules for URN// =====
	482	+(% class="wikigeneratedid" id="HCaseRulesforURN" %)
	483	+//Case Rules for URN//
488	488
489	489	For the URN, all parts of the string are case sensitive. The Id of any object must be UPPER CASE. Therefore, CRED_ext_Debt is invalid and it should be CRED_EXT_DEBT.
490	490
491	491	The generic structure of the URN is as follows:
492	492
493		-SDMXprefix.SDMX-IM-package-name.class-name=agencyid:maintainedobject-id(maintainedobject-version).*containerobject-id.object-id
	489	+>SDMXprefix.SDMX-IM-package-name.class-name=agencyid:maintainedobject-id(maintainedobject-version).*containerobject-id.object-id
494	494
495	495	~* this can repeat and may not be present (see explanation below)
496	496
...	...	@@ -502,7 +502,7 @@
502	502
503	503	In the explanation below the actual object that is the target of the URN is called the **//actual object//**.
504	504
505		-**SDMXPrefix:** urn:sdmx:org.
	501	+**SDMXPrefix:** urn:sdmx:org.
506	506
507	507	**SDMX-IM package name:** sdmx.infomodel.package=
508	508
...	...	@@ -585,91 +585,92 @@
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" %)(((
	584	+(% style="width:644.294px" %)
	585	+|(% style="width:127px" %)**Package**|(% style="width:494px" %)(((
589	589	**URN Classname (model classname 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" %)(((
	588	+|(% style="width:127px" %)base|(% style="width:494px" %)Agency
	589	+|(% style="width:127px" %) |(% style="width:494px" %)OrganisationUnitScheme
	590	+|(% style="width:127px" %) |(% style="width:494px" %)AgencyScheme
	591	+|(% style="width:127px" %) |(% style="width:494px" %)DataProviderScheme
	592	+|(% style="width:127px" %) |(% style="width:494px" %)DataConsumerScheme
	593	+|(% style="width:127px" %) |(% style="width:494px" %)OrganisationUnit
	594	+|(% style="width:127px" %) |(% style="width:494px" %)DataProvider
	595	+|(% style="width:127px" %) |(% style="width:494px" %)DataConsumer
	596	+|(% style="width:127px" %)datastructure|(% style="width:494px" %)DataStructure (DataStructureDefinition)
	597	+|(% style="width:127px" %) |(% style="width:494px" %)AttributeDescriptor
	598	+|(% style="width:127px" %) |(% style="width:494px" %)DataAttribute
	599	+|(% style="width:127px" %) |(% style="width:494px" %)GroupDimensionDescriptor
	600	+|(% style="width:127px" %) |(% style="width:494px" %)DimensionDescriptor
	601	+|(% style="width:127px" %) |(% style="width:494px" %)Dimension
	602	+|(% style="width:127px" %) |(% style="width:494px" %)MeasureDimension
	603	+|(% style="width:127px" %) |(% style="width:494px" %)TimeDimension
	604	+|(% style="width:127px" %) |(% style="width:494px" %)MeasureDescriptor
	605	+|(% style="width:127px" %) |(% style="width:494px" %)PrimaryMeasure
	606	+|(% style="width:127px" %) |(% style="width:494px" %)Dataflow (DataflowDefinition)
	607	+|(% style="width:127px" %)metadatastructure|(% style="width:494px" %)MetadataTarget
	608	+|(% style="width:127px" %) |(% style="width:494px" %)DimensionDescriptorValueTarget
	609	+|(% style="width:127px" %) |(% style="width:494px" %)IdentifiableObjectTarget
	610	+|(% style="width:127px" %) |(% style="width:494px" %)ReportPeriodTarget
	611	+|(% style="width:127px" %) |(% style="width:494px" %)DataSetTarget
	612	+|(% style="width:127px" %) |(% style="width:494px" %)ReportStructure
	613	+|(% style="width:127px" %) |(% style="width:494px" %)MetadataAttribute
	614	+|(% style="width:127px" %) |(% style="width:494px" %)(((
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
	619	+|(% style="width:127px" %) |(% style="width:494px" %)Metadataflow (MetadataflowDefinition)
	620	+|(% style="width:127px" %)process|(% style="width:494px" %)Process
	621	+|(% style="width:127px" %) |(% style="width:494px" %)ProcessStep
	622	+|(% style="width:127px" %) |(% style="width:494px" %)Transition
	623	+|(% style="width:127px" %)registry|(% style="width:494px" %)ProvisionAgreement
	624	+|(% style="width:127px" %) |(% style="width:494px" %)AttachmentConstraint
	625	+|(% style="width:127px" %) |(% style="width:494px" %)ContentConstraint
	626	+|(% style="width:127px" %) |(% style="width:494px" %)Subscription
	627	+|(% style="width:127px" %)mapping|(% style="width:494px" %)StructureMap
	628	+|(% style="width:127px" %) |(% style="width:494px" %)StructureSet
	629	+|(% style="width:127px" %) |(% style="width:494px" %)ComponentMap
	630	+|(% style="width:127px" %) |(% style="width:494px" %)ConceptSchemeMap
	631	+|(% style="width:127px" %) |(% style="width:494px" %)OrganisationSchemeMap
	632	+|(% style="width:127px" %) |(% style="width:494px" %)CodelistMap
	633	+|(% style="width:127px" %) |(% style="width:494px" %)CategorySchemeMap
	634	+|(% style="width:127px" %) |(% style="width:494px" %)ReportingTaxonomyMap
	635	+|(% style="width:127px" %) |(% style="width:494px" %)ConceptMap
	636	+|(% style="width:127px" %) |(% style="width:494px" %)OrganisationMap
	637	+|(% style="width:127px" %) |(% style="width:494px" %)CodeMap
	638	+|(% style="width:127px" %) |(% style="width:494px" %)HybridCodelistMap
	639	+|(% style="width:127px" %) |(% style="width:494px" %)CategoryMap
	640	+|(% style="width:127px" %) |(% style="width:494px" %)HybridCodeMap
	641	+|(% style="width:127px" %) |(% style="width:494px" %)ReportingCategoryMap
	642	+|(% style="width:127px" %)codelist|(% style="width:494px" %)Codelist
	643	+|(% style="width:127px" %) |(% style="width:494px" %)HierarchicalCodelist
	644	+|(% style="width:127px" %) |(% style="width:494px" %)Hierarchy
	645	+|(% style="width:127px" %) |(% style="width:494px" %)Hierarchy
	646	+|(% style="width:127px" %) |(% style="width:494px" %)Code
	647	+|(% style="width:127px" %) |(% style="width:494px" %)HierarchicalCode
	648	+|(% style="width:127px" %) |(% style="width:494px" %)Level
	649	+|(% style="width:127px" %)categoryscheme|(% style="width:494px" %)CategoryScheme
	650	+|(% style="width:127px" %) |(% style="width:494px" %)Category
	651	+|(% style="width:127px" %) |(% style="width:494px" %)Categorisation
	652	+|(% style="width:127px" %) |(% style="width:494px" %)ReportingTaxonomy
	653	+|(% style="width:127px" %) |(% style="width:494px" %)ReportingCategory
	654	+|(% style="width:127px" %)conceptscheme|(% style="width:494px" %)ConceptScheme
	655	+|(% style="width:127px" %) |(% style="width:494px" %)Concept
	656	+|(% style="width:127px" %)transformation|(% style="width:494px" %)TransformationScheme
	657	+|(% style="width:127px" %) |(% style="width:494px" %)Transformation
	658	+|(% style="width:127px" %) |(% style="width:494px" %)CustomTypeScheme
	659	+|(% style="width:127px" %) |(% style="width:494px" %)CustomType
	660	+|(% style="width:127px" %) |(% style="width:494px" %)NamePersonalisationScheme
	661	+|(% style="width:127px" %) |(% style="width:494px" %)NamePersonalisation
	662	+|(% style="width:127px" %) |(% style="width:494px" %)VtlCodelistMapping
	663	+|(% style="width:127px" %) |(% style="width:494px" %)VtlConceptMapping
	664	+|(% style="width:127px" %) |(% style="width:494px" %)VtlDataflowMapping
	665	+|(% style="width:127px" %) |(% style="width:494px" %)VtlConceptSchemeMapping
	666	+|(% style="width:127px" %) |(% style="width:494px" %)RulesetScheme
	667	+|(% style="width:127px" %) |(% style="width:494px" %)Ruleset
	668	+|(% style="width:127px" %) |(% style="width:494px" %)UserDefinedOperatorScheme
	669	+|(% style="width:127px" %) |(% style="width:494px" %)UserDefinedOperator
673	673
674	674	**Table 2: SDMX-IM Packages and Contained Classes**
675	675
...	...	@@ -683,39 +683,38 @@
683	683
684	684	> 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" %)(((
	683	+(% style="width:1277.29px" %)
	684	+|(% style="width:269px" %)**SDMX Class**|(% style="width:453px" %)**Key attribute(s)**|(% style="width:550px" %)**Example of URN**
	685	+|(% style="width:269px" %)Agency|(% style="width:453px" %)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:550px" %)(((
689	689	IMF
690	690	Sub agency in the IMF AGENCIES
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" %)(((
	690	+|(% style="width:269px" %)*ConceptScheme|(% style="width:453px" %)conceptSchemeAgencyId:conceptSchemeId(ve rsion)|(% style="width:550px" %)SDMX:CROSS_DOMAIN_CONCEPTS(1.0)
	691	+|(% style="width:269px" %)Concept|(% style="width:453px" %)conceptSchemeAgencyId:
	692	+conceptSchemeId(version).conceptId|(% style="width:550px" %)SDMX:CROSS_DOMAIN_CONCEPTS(1.0).FREQ
	693	+|(% style="width:269px" %)*Codelist|(% style="width:453px" %)codeListAgencyId:codeListId(version)|(% style="width:550px" %)SDMX:CL_FREQ(1.0)
	694	+|(% style="width:269px" %)Code|(% style="width:453px" %)codeListAgencyId:codelistId(version).codeId|(% style="width:550px" %)SDMX:CL_FREQ(1.0).Q
	695	+|(% style="width:269px" %)(((
699	699	*Hierarchical Codelist
700		-)))|(% style="width:444px" %)hierachicalCodelistAgencyId: hierarchicalCodelistId(version)|(% style="width:396px" %)(((
	697	+)))|(% style="width:453px" %)hierachicalCodelistAgencyId:
	698	+hierarchicalCodelistId(version)|(% style="width:550px" %)(((
701	701	UNESCO:CL_EXP_SOURCE(1.0(% style="background-color:transparent" %))
702	702	)))
703		-|(% style="width:250px" %)Hierarchy|(% style="width:444px" %)(((
	701	+|(% style="width:269px" %)Hierarchy|(% style="width:453px" %)(((
704	704	hierachicalcodeListAgencyId:
705	705	hierarchicalcodelistId(version).Hierarchy
706		-)))|(% style="width:396px" %)UNESCO:CL_EXP_SOURCE(1.0).
	704	+)))|(% style="width:550px" %)UNESCO:CL_EXP_SOURCE(1.0).
707	707	H-C-GOV
708		-|(% style="width:250px" %)Level|(% style="width:444px" %)(((
	706	+|(% style="width:269px" %)Level|(% style="width:453px" %)(((
709	709	hierachicalcodeListAgencyId:
710	710	hierarchicalcodelistId(version).Hierarchy.Level
711		-)))|(% style="width:396px" %)(((
	709	+)))|(% style="width:550px" %)(((
712	712	ESTAT:HCL_REGION(1.0).H_1.COUNTRY
713		-
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" %)(((
	712	+|(% style="width:269px" %)HierarchicalCode|(% style="width:453px" %)hierachicalCodeListAgencyId: hierarchicalcodelistId(version).hierarchy.hierarc hicalCode|(% style="width:550px" %)UNESCO:CL_EXP_SOURCE(1.0). H-C-GOV.GOV_CODE1
	713	+|(% style="width:269px" %)*DataStructure|(% style="width:453px" %)dataStructureDefintitionAgencyId: dataStructureDefintitionId(version)|(% style="width:550px" %)TFFS:EXT_DEBT(1.0)
	714	+|(% style="width:269px" %)(((
719	719	Dimension
720	720	Descriptor
721	721	Measure
...	...	@@ -722,11 +722,11 @@
722	722	Descriptor
723	723	Attribute
724	724	Descriptor
725		-)))|(% style="width:444px" %)(((
	721	+)))|(% style="width:453px" %)(((
726	726	dataStructureDefinitionAgencyId: dataStructureDefinitionId(version).
727	727	componentListId
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" %)(((
	725	+)))|(% style="width:550px" %)(((
730	730	TFFS:EXT_DEBT(1.0).DimensionDescriptor
731	731
732	732	TFFS:EXT_DEBT(1.0).MeasureDescriptor
...	...	@@ -733,68 +733,69 @@
733	733
734	734	TFFS:EXT_DEBT(1.0).AttributeDescriptor
735	735	)))
736		-|(% style="width:250px" %)(((
	732	+|(% style="width:269px" %)(((
737	737	GroupDimension
738	738	Descriptor
739		-)))|(% style="width:444px" %)(((
	735	+)))|(% style="width:453px" %)(((
740	740	dataStructureDefinitionAgencyId: dataStructureDefinitionId(version).
741	741	groupDimensionDescriptorId
742		-)))|(% style="width:396px" %)TFFS:EXT_DEBT(1.0).SIBLING
743		-|(% style="width:250px" %)Dimension|(% style="width:444px" %)(((
	738	+)))|(% style="width:550px" %)TFFS:EXT_DEBT(1.0).SIBLING
	739	+|(% style="width:269px" %)Dimension|(% style="width:453px" %)(((
744	744	dataStructureDefinitionAgencyId: dataStructureDefinition (version).
745	745	dimensionId
746		-)))|(% style="width:396px" %)TFFS:EXT_DEBT(1.0).FREQ
747		-|(% style="width:250px" %)TimeDimension|(% style="width:444px" %)(((
	742	+)))|(% style="width:550px" %)TFFS:EXT_DEBT(1.0).FREQ
	743	+|(% style="width:269px" %)TimeDimension|(% style="width:453px" %)(((
748	748	dataStructureDefinitionAgencyId: dataStructureDefinition (version).
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" %)(((
	746	+)))|(% style="width:550px" %)TFFS:EXT_DEBT(1.0).TIME_PERIOD
	747	+|(% style="width:269px" %)Measure Dimension|(% style="width:453px" %)dataStructureDefinitionAgencyId: dataStructureDefinition (version).
	748	+measureDimensionId|(% style="width:550px" %)TFFS:EXT_DEBT(1.0).STOCK_FLOW
	749	+|(% style="width:269px" %)DataAttrribute|(% style="width:453px" %)dataStructureDefinitionAgencyId: dataStructureDefinition (version). dataAttributeId|(% style="width:550px" %)TFFS:EXT_DEBT(1.0).OBS_STATUS
	750	+|(% style="width:269px" %)PrimaryMeasure|(% style="width:453px" %)(((
755	755	dataStructureDefinitionAgencyId: dataStructureDefinition (version).
756	756	primaryMeasureId
757		-)))|(% style="width:396px" %)TFFS:EXT_DEBT(1.0).OBS_VALUE
758		-|(% style="width:250px" %)(((
	753	+)))|(% style="width:550px" %)TFFS:EXT_DEBT(1.0).OBS_VALUE
	754	+|(% style="width:269px" %)(((
759	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:
	756	+)))|(% style="width:453px" %)categorySchemeAgencyId:
	757	+categorySchemeId(version)|(% style="width:550px" %)IMF:SDDS(1.0)
	758	+|(% style="width:269px" %)Category|(% style="width:453px" %)categorySchemeAgencyId:
763	763	categorySchemeId(version).
764		-categoryId.categoryId categoryId.categoryId etc.|(% style="width:396px" %)(((
	760	+categoryId.categoryId categoryId.categoryId etc.|(% style="width:550px" %)(((
765	765	IMF:SDDS(1.0):
766	766	level_1_category.level_2_category …
767	767	)))
768		-|(% style="width:250px" %)(((
	764	+|(% style="width:269px" %)(((
769	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" %)(((
	766	+)))|(% style="width:453px" %)reportingTaxonomyAgencyId: reportingTaxonomyId(version)|(% style="width:550px" %) IMF:REP_1(1.0)
	767	+|(% style="width:269px" %)ReportingCategory|(% style="width:453px" %)reportingTaxonomyAgencyId: reportingTaxonomyId(version) reportingcategoryId.reportingcategoryId|(% style="width:550px" %)(((
772	772	IMF:REP_1(1.0):
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" %)(((
	771	+|(% style="width:269px" %)*Categorisation|(% style="width:453px" %)categorisationAgencyId: categorisationId(version)|(% style="width:550px" %)IMF:cat001(1.0)
	772	+|(% style="width:269px" %)(((
777	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)
	774	+)))|(% style="width:453px" %)organisationUnitSchemeAgencyId: organisationUnitSchemeId(version)|(% style="width:550px" %)ECB:ORGANISATIONS(1.0)
	775	+|(% style="width:269px" %)Organisation Unit|(% style="width:453px" %)organisationUnitSchemeAgencyId: organisationUnitSchemeId(version). organisationUnitId|(% style="width:550px" %)ECB:ORGANISATIONS(1.0).1F
	776	+|(% style="width:269px" %)*AgencyScheme|(% style="width:453px" %)agencySchemeAgencyId: agencySchemeId(version)|(% style="width:550px" %)ECB:AGENCIES(1.0)
781	781
782		-|(% style="width:262px" %)Agency|(% style="width:369px" %)agencySchemeAgencyId: agencySchemeId(version). agencyId|(% style="width:1262px" %)ECB:AGENCY(1.0).AA
	778	+(% style="width:1274.29px" %)
	779	+|(% style="width:262px" %)Agency|(% style="width:369px" %)agencySchemeAgencyId: agencySchemeId(version). agencyId|(% style="width:535px" %)ECB:AGENCY(1.0).AA
783	783	|(% style="width:262px" %)(((
784	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
	782	+)))|(% style="width:369px" %)dataProviderSchemeAgencyId: dataProviderSchemeId(version)|(% style="width:535px" %)SDMX:DATA_PROVIDERS(1.0)
	783	+|(% style="width:262px" %)DataProvider|(% style="width:369px" %)dataProviderSchemeAgencyId: dataProviderSchemeId(version) dataProviderId|(% style="width:535px" %)SDMX:DATA_PROVIDERS(1.0).PROVIDER_1
787	787	|(% style="width:262px" %)(((
788	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
	786	+)))|(% style="width:369px" %)dataConsumerSchemeAgencyId: dataConsumerSchemeId(version)|(% style="width:535px" %)SDMX:DATA_CONSUMERS(1.0)
	787	+|(% style="width:262px" %)Data Consumer|(% style="width:369px" %)dataConsumerSchemeAgencyId: dataConsumerSchemeId(version) dataConsumerId|(% style="width:535px" %)SDMX:DATA_CONSUMERS(1.0).CONSUMER_1
791	791	|(% style="width:262px" %)(((
792	792	*Metadata Structure
793		-)))|(% style="width:369px" %)MSDAgencyId:MSDId(version)|(% style="width:1262px" %)IMF:SDDS_MSD(1.0)
	790	+)))|(% style="width:369px" %)MSDAgencyId:MSDId(version)|(% style="width:535px" %)IMF:SDDS_MSD(1.0)
794	794	|(% style="width:262px" %)MetadataTarget|(% style="width:369px" %)(((
795	795	MSDAgencyId:
796	796	MSDId(version).metadataTargetId
797		-)))|(% style="width:1262px" %)IMF:SDDS_MSD(1.0).AGENCY
	794	+)))|(% style="width:535px" %)IMF:SDDS_MSD(1.0).AGENCY
798	798	|(% style="width:262px" %)(((
799	799	Dimension
800	800	DescriptorValues
...	...	@@ -802,170 +802,139 @@
802	802	)))|(% style="width:369px" %)(((
803	803	MSDAgencyId: MSDId(version).
804	804	metadataTargetId.keyDescriptorValueTargetId
805		-)))|(% style="width:1262px" %)IMF:SDDS_MSD(1.0).AGENCY.KEY
	802	+)))|(% style="width:535px" %)IMF:SDDS_MSD(1.0).AGENCY.KEY
806	806	|(% style="width:262px" %)Identifiable Object Target|(% style="width:369px" %)(((
807	807	MSDAgencyId: MSDId(version).metadataTargetId.identifiableObjectTargetId
808		-)))|(% style="width:1262px" %)IMF:SDDS_MSD(1.0).AGENCY.STR-OBJECT
	805	+)))|(% style="width:535px" %)IMF:SDDS_MSD(1.0).AGENCY.STR-OBJECT
809	809	|(% style="width:262px" %)DataSetTarget|(% style="width:369px" %)(((
810	810	MSDAgencyId:
811	811	MSDId(version).metadataTargetId.dataSetTargetId
812		-)))|(% style="width:1262px" %)IMF:SDDS_MSD(1.0).AGENCY.D1101
	809	+)))|(% style="width:535px" %)IMF:SDDS_MSD(1.0).AGENCY.D1101
813	813	|(% style="width:262px" %)PeportPeriod Target|(% style="width:369px" %)(((
814	814	MSDAgencyId: MSDId(version).metadataTargetId.reportPeriodTargetId
815		-)))|(% style="width:1262px" %)IMF:SDDS_MSD(1.0).AGENCY.REP_PER
	812	+)))|(% style="width:535px" %)IMF:SDDS_MSD(1.0).AGENCY.REP_PER
816	816
817		-|(% style="width:251px" %)(((
	814	+(% style="width:1277.29px" %)
	815	+|(% style="width:270px" %)(((
818	818	ReportStructure
819		-
820		-
821		-)))|(% style="width:442px" %)(((
	817	+)))|(% style="width:454px" %)(((
822	822	MSDAgencyId: MSDId(version).reportStructureId
823		-)))|(% style="width:1178px" %)IMF:SDDS_MSD(1.0).AGENCY_REPORT
824		-|(% style="width:251px" %)(((
825		-Metadata
826		-
827		-Attribute
828		-)))|(% style="width:442px" %)(((
	819	+)))|(% style="width:549px" %)IMF:SDDS_MSD(1.0).AGENCY_REPORT
	820	+|(% style="width:270px" %)(((
	821	+Metadata Attribute
	822	+)))|(% style="width:454px" %)(((
829	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" %)(((
	824	+)))|(% style="width:549px" %)IMF:SDDS_MSD(1.0).AGENCY_REPORT.COMPILATION
	825	+|(% style="width:270px" %)*Dataflow|(% style="width:454px" %)dataflowAgencyId: dataflowId(version)|(% style="width:549px" %)TFFS:CRED_EXT_DEBT(1.0)
	826	+|(% style="width:270px" %)*Provision Agreement|(% style="width:454px" %)(((
833	833	provisionAgreementAgencyId:provisionAgreem entId(version)
834		-)))|(% style="width:1178px" %)(((
	828	+)))|(% style="width:549px" %)(((
835	835	TFFS:CRED_EXT_DEBT_AB(1.0)
836	836	)))
837		-|(% style="width:251px" %)(((
838		-*Content
839		-
840		-Constraint
841		-)))|(% style="width:442px" %)constraintAgencyId:ContentConstraintId(versio n)|(% style="width:1178px" %)TFFS:CREDITOR_DATA_CONTENT(1.0)
842		-|(% style="width:251px" %)(((
843		-*Attachment
844		-
845		-Constraint
846		-)))|(% style="width:442px" %)(((
	831	+|(% style="width:270px" %)(((
	832	+*Content Constraint
	833	+)))|(% style="width:454px" %)constraintAgencyId:ContentConstraintId(versio n)|(% style="width:549px" %)TFFS:CREDITOR_DATA_CONTENT(1.0)
	834	+|(% style="width:270px" %)(((
	835	+*Attachment Constraint
	836	+)))|(% style="width:454px" %)(((
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" %)(((
	840	+)))|(% style="width:549px" %)TFFS:CREDITOR_DATA_ATTACHMENT_CONSTRAINT_ONE(1.0)
	841	+|(% style="width:270px" %)*Metadataflow|(% style="width:454px" %)metadataflowAgencyId: metadataflowId(version)|(% style="width:549px" %)IMF:SDDS_FLOW(1.0)
	842	+|(% style="width:270px" %)*StructureSet|(% style="width:454px" %)structureSetAgencyId: structureSetId(version)|(% style="width:549px" %)SDMX:BOP_STRUCTURES(1.0)
	843	+|(% style="width:270px" %)StructureMap|(% style="width:454px" %)structureSetAgencyId: structureSetId(version). structureMapId|(% style="width:549px" %)SDMX:BOP_STRUCTURES(1.0).TABLE1_TABLE2
	844	+|(% style="width:270px" %)Component Map|(% style="width:454px" %)(((
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
861		-
862		-| |(((
	848	+)))|(% style="width:549px" %)SDMX:BOP_STRUCTURES(1.0).TABLE1_TABLE2. REFAREA_REPCOUNTRY
	849	+|(% style="width:270px" %)CodelistMap|(% style="width:454px" %)structureSetAgencyId: structureSetId(version). codelistMapId|(% style="width:549px" %)SDMX:BOP_STRUCTURES(1.0).CLREFAREA_CLREPCOUNTRY
	850	+|(% style="width:270px" %)CodeMap|(% style="width:454px" %)structureSetAgencyId: structureSetId(version).
863	863	codeListMapId.
	852	+codeMapId|(% style="width:549px" %)SDMX:BOP_STRUCTURES(1.0).CLREFAREA_CLREPCOUNTRY. DE_GER
864	864
865		-codeMapId
866		-)))|
867		-|(((
868		-Category
869		-
870		-SchemeMap
871		-)))|structureSetAgencyId: structureSetId(version). categorySchemeMapId|SDMX:BOP_STRUCTURES(1.0).SDMX_EUROSTAT
872		-|CategoryMap|structureSetAgencyId: structureSetId(version). categorySchemeMapId. categoryMapId|SDMX:BOP_STRUCTURES(1.0).SDMX_EUROSTAT.TOURISM_M AP
873		-|Organisation SchemeMap|structureSetAgencyId: structureSetId(version). organisationSchemeMapId|SDMX:BOP_STRUCTURES(1.0).DATA_PROVIDER_MAP
874		-|Organisation Map|structureSetAgencyId: structureSetId(version). organisationSchemeMapId. organisationMapId|SDMX:BOP_STRUCTURES(1.0).DATA_PROVIDER_MAP.IMF_1C0
875		-|(((
	854	+(% style="width:1279.29px" %)
	855	+|(% style="width:271px" %)(((
	856	+CategorySchemeMap
	857	+)))|(% style="width:453px" %)structureSetAgencyId: structureSetId(version). categorySchemeMapId|(% style="width:551px" %)SDMX:BOP_STRUCTURES(1.0).SDMX_EUROSTAT
	858	+|(% style="width:271px" %)CategoryMap|(% style="width:453px" %)structureSetAgencyId: structureSetId(version). categorySchemeMapId. categoryMapId|(% style="width:551px" %)SDMX:BOP_STRUCTURES(1.0).SDMX_EUROSTAT.TOURISM_MAP
	859	+|(% style="width:271px" %)Organisation SchemeMap|(% style="width:453px" %)structureSetAgencyId: structureSetId(version). organisationSchemeMapId|(% style="width:551px" %)SDMX:BOP_STRUCTURES(1.0).DATA_PROVIDER_MAP
	860	+|(% style="width:271px" %)Organisation Map|(% style="width:453px" %)structureSetAgencyId: structureSetId(version). organisationSchemeMapId. organisationMapId|(% style="width:551px" %)SDMX:BOP_STRUCTURES(1.0).DATA_PROVIDER_MAP.IMF_1C0
	861	+|(% style="width:271px" %)(((
876	876	Concept
877	877
878	878	SchemeMap
879		-)))|structureSetAgencyId: structureSetId(version). conceptSchemeMapId|SDMX:BOP_STRUCTURES(1.0).SDMX_OECD
880		-|ConceptMap|(((
	865	+)))|(% style="width:453px" %)structureSetAgencyId: structureSetId(version). conceptSchemeMapId|(% style="width:551px" %)SDMX:BOP_STRUCTURES(1.0).SDMX_OECD
	866	+|(% style="width:271px" %)ConceptMap|(% style="width:453px" %)(((
881	881	structureSetAgencyId: structureSetId(version). conceptSchemeMapId.
882		-
883	883	conceptMapId
884		-
885		-
886		-)))|SDMX:BOP_STRUCTURES(1.0).SDMX_OECD.COVERAGE_AVAI LABILITY
887		-|(((
888		-Reporting
889		-
890		-TaxonomyMap
891		-)))|structureSetAgencyId: structureSetId(version). reportingTaxonomyMapId|SDMX:BOP_STRUCTURES(1.0).TAXMAP
892		-|(((
893		-Reporting
894		-
895		-CategoryMap
896		-)))|(((
	869	+)))|(% style="width:551px" %)SDMX:BOP_STRUCTURES(1.0).SDMX_OECD.COVERAGE_AVAI LABILITY
	870	+|(% style="width:271px" %)(((
	871	+ReportingTaxonomyMap
	872	+)))|(% style="width:453px" %)structureSetAgencyId: structureSetId(version). reportingTaxonomyMapId|(% style="width:551px" %)SDMX:BOP_STRUCTURES(1.0).TAXMAP
	873	+|(% style="width:271px" %)(((
	874	+ReportingCategoryMap
	875	+)))|(% style="width:453px" %)(((
897	897	structureSetAgencyId: structureSetId(version).
898		-
899	899	reportngCategoryId
900		-)))|SDMX:BOP_STRUCTURES(1.0).TAXMAP.TOPCAT
	878	+)))|(% style="width:551px" %)SDMX:BOP_STRUCTURES(1.0).TAXMAP.TOPCAT
901	901
902		-
903		-
904		-|(((
905		-HybridCodelist
906		-
907		-Map
908		-)))|structureSetAgencyId: structureSetId(version). hybridCodelistMapId.|SDMX:BOP_STRUCTURES(1.0).COUNTRY_HIERARCHYMAP
909		-|HybridCodeMap|structureSetAgencyId: structureSetId(version). hybridCodelistMapId. hybridCodeMapId|SDMX:BOP_STRUCTURES(1.0).COUNTRY_HIERARCHYMAP.CO DEMAP1
910		-|*Process|processAgencyId: processId{version]|BIS:PROCESS1(1.0)
911		-|ProcessStep|(((
	880	+(% style="width:1282.29px" %)
	881	+|(% style="width:272px" %)(((
	882	+HybridCodelistMap
	883	+)))|(% style="width:450px" %)structureSetAgencyId: structureSetId(version).
	884	+hybridCodelistMapId.|(% style="width:557px" %)SDMX:BOP_STRUCTURES(1.0).COUNTRY_HIERARCHYMAP
	885	+|(% style="width:272px" %)HybridCodeMap|(% style="width:450px" %)structureSetAgencyId: structureSetId(version). hybridCodelistMapId. hybridCodeMapId|(% style="width:557px" %)SDMX:BOP_STRUCTURES(1.0).COUNTRY_HIERARCHYMAP.CO DEMAP1
	886	+|(% style="width:272px" %)*Process|(% style="width:450px" %)processAgencyId: processId{version]|(% style="width:557px" %)BIS:PROCESS1(1.0)
	887	+|(% style="width:272px" %)ProcessStep|(% style="width:450px" %)(((
912	912	processAgencyId: processId(version).
913		-
914	914	processStepId
915		-)))|BIS:PROCESS1(1.0).STEP1
916		-|Transition|(((
	890	+)))|(% style="width:557px" %)BIS:PROCESS1(1.0).STEP1
	891	+|(% style="width:272px" %)Transition|(% style="width:450px" %)(((
917	917	processAgencyId: processId(version).
918		-
919	919	processStepId transitionId
920		-)))|BIS:PROCESS1(1.0).STEP1.TRANSITION1
921		-|Subscription|The Subscription is not itself an Identifiable Artefact and therefore it does not follow the rules for URN structure, The name of the URN is registryURN There is no pre-determined format.|This cannot be generated by a common mechanism as subscriptions, although maintainable in the sense that they can be submitted and deleted, are not mandated to be created by a maintenance agency, and have no versioning mechanism. It is therefore the responsibility of the target registry to generate a unique Id for the Subscription, and for the application creating the subscription to store the registryURN that is returned from the registry in the subscription response message.
922		-|(((
923		-*Transformation
924		-
925		-Scheme
926		-)))|transformationSchemeAgencyId transformationSchemeId(version)|ECB: TRANSFORMATION_SCHEME(1.0)
927		-|Transformation|(((
	894	+)))|(% style="width:557px" %)BIS:PROCESS1(1.0).STEP1.TRANSITION1
	895	+|(% style="width:272px" %)Subscription|(% style="width:450px" %)The Subscription is not itself an Identifiable Artefact and therefore it does not follow the rules for URN structure, The name of the URN is registryURN There is no pre-determined format.|(% style="width:557px" %)This cannot be generated by a common mechanism as subscriptions, although maintainable in the sense that they can be submitted and deleted, are not mandated to be created by a maintenance agency, and have no versioning mechanism. It is therefore the responsibility of the target registry to generate a unique Id for the Subscription, and for the application creating the subscription to store the registryURN that is returned from the registry in the subscription response message.
	896	+|(% style="width:272px" %)(((
	897	+*Transformation Scheme
	898	+)))|(% style="width:450px" %)transformationSchemeAgencyId transformationSchemeId(version)|(% style="width:557px" %)ECB: TRANSFORMATION_SCHEME(1.0)
	899	+|(% style="width:272px" %)Transformation|(% style="width:450px" %)(((
928	928	transformationSchemeAgencyId transformationSchemeId(version)
929		-
930	930	transformationId
931		-)))|ECB:TRANSFORMATION_SCHEME(1.0).TRANS_1
932		-|CustomType Scheme|customTypeSchemeAgencyId customTypeSchemeId(version)|ECB:CUSTOM_TYPE_SCHEME(1.0)
	902	+)))|(% style="width:557px" %)ECB:TRANSFORMATION_SCHEME(1.0).TRANS_1
	903	+|(% style="width:272px" %)CustomType Scheme|(% style="width:450px" %)customTypeSchemeAgencyId customTypeSchemeId(version)|(% style="width:557px" %)ECB:CUSTOM_TYPE_SCHEME(1.0)
933	933
934		-
935		-
936		-|CustomType|customTypeSchemeAgencyId customTypeSchemeId(version) customTypeId|ECB: CUSTOM_TYPE_SCHEME(1.0).CUSTOM_TYPE_1
937		-|(((
	905	+(% style="width:1281.29px" %)
	906	+|(% style="width:275px" %)CustomType|(% style="width:450px" %)customTypeSchemeAgencyId customTypeSchemeId(version) customTypeId|(% style="width:552px" %)ECB: CUSTOM_TYPE_SCHEME(1.0).CUSTOM_TYPE_1
	907	+|(% style="width:275px" %)(((
938	938	Name
939		-
940	940	Personalisation
941		-
942	942	Scheme
943		-)))|namePersonalisationSchemeAgencyId namePersonalisationSchemeId(version)|ECB:PSN_SCHEME(1.0)
944		-|(((
	911	+)))|(% style="width:450px" %)namePersonalisationSchemeAgencyId namePersonalisationSchemeId(version)|(% style="width:552px" %)ECB:PSN_SCHEME(1.0)
	912	+|(% style="width:275px" %)(((
945	945	Name
946		-
947	947	Personalisation
948		-)))|namePersonalisationSchemeAgencyId namePersonalisationSchemeId(version) namePersonalisationId|ECB:PSN_SCHEME(1.0).PSN1234
949		-|VtlMapping Scheme|vtlMappingSchemeAgencyId VtlMappingSchemeId(version)|ECB:CLIST_MP(2.0)
950		-|VtlCodelist Mapping|vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlCodelistMappingId|ECB:CLIST_MP(2.0).ABZ
951		-|VtlConcept Mapping|vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlConceptMappingId|ECB:CLIST_MP(1.0).XYA
952		-|VtlDataflow Mapping|vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlDataflowMappingId|ECB:CLIST_MP(1.0).MOQ
953		-|(((
	915	+)))|(% style="width:450px" %)namePersonalisationSchemeAgencyId namePersonalisationSchemeId(version)
	916	+namePersonalisationId|(% style="width:552px" %)ECB:PSN_SCHEME(1.0).PSN1234
	917	+|(% style="width:275px" %)VtlMapping Scheme|(% style="width:450px" %)vtlMappingSchemeAgencyId VtlMappingSchemeId(version)|(% style="width:552px" %)ECB:CLIST_MP(2.0)
	918	+|(% style="width:275px" %)VtlCodelist Mapping|(% style="width:450px" %)vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlCodelistMappingId|(% style="width:552px" %)ECB:CLIST_MP(2.0).ABZ
	919	+|(% style="width:275px" %)VtlConcept Mapping|(% style="width:450px" %)vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlConceptMappingId|(% style="width:552px" %)ECB:CLIST_MP(1.0).XYA
	920	+|(% style="width:275px" %)VtlDataflow Mapping|(% style="width:450px" %)vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlDataflowMappingId|(% style="width:552px" %)ECB:CLIST_MP(1.0).MOQ
	921	+|(% style="width:275px" %)(((
954	954	VtlConcept
955	955
956	956	SchemeMapping
957		-)))|vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlConceptSchemeId|ECB:CLIST_MP(1.0).Z11
958		-|RulesetScheme|rulesetSchemeAgencyId rulesetSchemeId(version)|ECB:RULESET_23(1.0)
959		-|Ruleset|rulesetSchemeAgencyId rulesetSchemeId(version) rulesetId|ECB:RULESET_23(1.0).SET111
960		-|(((
961		-UserDefined
	925	+)))|(% style="width:450px" %)vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlConceptSchemeId|(% style="width:552px" %)ECB:CLIST_MP(1.0).Z11
	926	+|(% style="width:275px" %)RulesetScheme|(% style="width:450px" %)rulesetSchemeAgencyId rulesetSchemeId(version)|(% style="width:552px" %)ECB:RULESET_23(1.0)
	927	+|(% style="width:275px" %)Ruleset|(% style="width:450px" %)rulesetSchemeAgencyId rulesetSchemeId(version) rulesetId|(% style="width:552px" %)ECB:RULESET_23(1.0).SET111
	928	+|(% style="width:275px" %)(((
	929	+UserDefinedOperatorScheme
	930	+)))|(% style="width:450px" %)userDefinedOperatorSchemeAgencyId userDefinedOperatorSchemeId(version)|(% style="width:552px" %)ECB:OS_CALC(1.2)
	931	+|(% style="width:275px" %)UserDefined Operator|(% style="width:450px" %)userDefinedOperatorSchemeAgencyId userDefinedOperatorSchemeId(version) usserDefinedOperatorId|(% style="width:552px" %)ECB:OS_CALC(1.2).OS267
962	962
963		-OperatorScheme
964		-)))|userDefinedOperatorSchemeAgencyId userDefinedOperatorSchemeId(version)|ECB:OS_CALC(1.2)
965		-|UserDefined Operator|userDefinedOperatorSchemeAgencyId userDefinedOperatorSchemeId(version) usserDefinedOperatorId|ECB:OS_CALC(1.2).OS267
	933	+**Table 3: Table of identification components for SDMX Identifiable Artefacts**
966	966
967		-7**Table 3: Table of identification components for SDMX Identifiable Artefacts**
968		-
969	969	= 7 Implementation Notes =
970	970
971	971	== 7.1 Structural Definition Metadata ==
...	...	@@ -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
	1074	+[[image:1747829109466-595.png]]
1108	1108
1109	1109	**Figure 11: SDMX-IM of the Data Provider**
1110	1110
1111		-
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,8 +1117,10 @@
1117	1117
1118	1118	The diagram below is a logical representation of the data required in order to maintain Provision Agreements.
1119	1119
	1086	+[[image:1747829139951-378.png]]
1120	1120
1121		-==== Figure 13: Logical class diagram of the information contained in the Provision Agreement ====
	1088	+(% class="wikigeneratedid" id="HFigure13:LogicalclassdiagramoftheinformationcontainedintheProvisionAgreement" %)
	1089	+**Figure 13: Logical class diagram of the information contained in the Provision Agreement**
1122	1122
1123	1123	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.
1124	1124
...	...	@@ -1146,13 +1146,12 @@
1146	1146
1147	1147	=== 7.3.3 Data and Metadata Constraints: Model ===
1148	1148
	1117	+[[image:1747829204737-370.png]]
1149	1149
	1119	+**Figure 15: Logical class diagram showing inheritance between and reference to constrainable artifacts**
1150	1150
1151		-==== Figure 15: Logical class diagram showing inheritance between and reference to constrainable artifacts ====
	1121	+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.
1152	1152
1153		-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.
1154		-
1155		-
1156	1156	The content of the Constraint can be found in the SDMX Information Model document.
1157	1157
1158	1158	== 7.4 Data and Metadata Registration ==
...	...	@@ -1173,7 +1173,7 @@
1173	1173
1174	1174	[[image:1747824123025-411.jpeg]]
1175	1175
1176		- **Figure 16: Schematic of the Objects Concerned with Registration**
	1143	+**Figure 16: Schematic of the Objects Concerned with Registration**
1177	1177
1178	1178	==== 7.4.2.2 Registration Request Model ====
1179	1179
...	...	@@ -1187,11 +1187,14 @@
1187	1187
1188	1188	The Registration has an action attribute which takes one of the following values:
1189	1189
1190		-|**Action Attribute Value**|**Behaviour**
1191		-|Append|Add this Registration to the registry
1192		-|Replace|Replace the existing Registration with identified by the id in the Registration of the Submit Registration Request
1193		-|Delete|Delete the existing Registration identified by the id in the Registration of the Submit Registration Request
	1157	+(% style="width:798.294px" %)
	1158	+|(% style="width:212px" %)**Action Attribute Value**|(% style="width:582px" %)**Behaviour**
	1159	+|(% style="width:212px" %)Append|(% style="width:582px" %)Add this Registration to the registry
	1160	+|(% style="width:212px" %)Replace|(% style="width:582px" %)Replace the existing Registration with identified by the id in the Registration of the Submit Registration Request
	1161	+|(% style="width:212px" %)Delete|(% style="width:582px" %)Delete the existing Registration identified by the id in the Registration of the Submit Registration Request
1194	1194
	1163	+[[image:1747829290890-122.png]]
	1164	+
1195	1195	**Figure 17: Logical Class Diagram of Registration of Data and Metadata**
1196	1196
1197	1197	The Query Datasource is an abstract class that represents a data source which can understand an SDMX-ML query (SOAPDatasource) or RESTful query
...	...	@@ -1206,25 +1206,20 @@
1206	1206
1207	1207	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.
1208	1208
1209		-|**Indexing Required**|**Registration Process Activity**
1210		-|indexTimeSeries|Extract all the series keys and create a KeySet(s) Constraint.
1211		-|indexDataSet|(((
1212		-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
1213		-
1214		-Regions containing Member Selections of Dimension Components of the Constraints model in the SDMX-IM, and the associated Selection Value.
	1179	+(% style="width:860.294px" %)
	1180	+|(% style="width:185px" %)**Indexing Required**|(% style="width:672px" %)**Registration Process Activity**
	1181	+|(% style="width:185px" %)indexTimeSeries|(% style="width:672px" %)Extract all the series keys and create a KeySet(s) Constraint.
	1182	+|(% style="width:185px" %)indexDataSet|(% style="width:672px" %)(((
	1183	+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.
1215	1215	)))
1216		-|indexReportingPeriod|(((
	1185	+|(% style="width:185px" %)indexReportingPeriod|(% style="width:672px" %)(((
1217	1217	This applies only to a registered dataset.
1218		-
1219	1219	Extract the Reporting Begin and Reporting End from the Header of the Message containing the data set, and create a Reference Period constraint.
1220	1220	)))
1221		-|indexAttributes|(((
	1189	+|(% style="width:185px" %)indexAttributes|(% style="width:672px" %)(((
1222	1222	**Data Set**
1223		-
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
1225		-
1226	1226	**Metadata Set**
1227		-
1228	1228	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.
1229	1229	)))
1230	1230
...	...	@@ -1234,14 +1234,13 @@
1234	1234
1235	1235	=== 7.4.3 Registration Response ===
1236	1236
1237		-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
	1202	+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”.
1238	1238
1239		-“Success”, “Warning” or “Failure”.
1240		-
1241	1241	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.
1242	1242
1243	1243	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:
1244	1244
	1208	+[[image:1747829477882-750.png]]
1245	1245
1246	1246	**Figure 18: Logical class diagram showing the registration response**
1247	1247
...	...	@@ -1251,15 +1251,12 @@
1251	1251
1252	1252	A user can submit a subscription in the registry that defines which events are of interest, and either an email and/or an HTTP address to which a notification of qualifying events will be delivered. The subscription will be identified in the registry by a URN which is returned to the user when the subscription is created. If the user wants to delete the subscription at a later point, the subscription URN is used as identification. Subscriptions have a validity period expressed as a date range (startDate, endDate) and the registry may delete any expired subscriptions, and will notify the subscriber on expiry.
1253	1253
1254		-When a registry/repository artefact is modified, any subscriptions which are observing the object are activated, and either an email or HTTP POST is instigated to report details of the changes to the user specified in the subscription. This is called a
	1218	+When a registry/repository artefact is modified, any subscriptions which are observing the object are activated, and either an email or HTTP POST is instigated to report details of the changes to the user specified in the subscription. This is called a “notification”.
1255	1255
1256		-“notification”.
	1220	+=== 7.5.1Subscription Logical Class Diagram ===
1257	1257
1258		- 7.5.1Subscription Logical Class Diagram
	1222	+[[image:1747829554603-150.png]]
1259	1259
1260		-
1261		-[[image:1747824123028-257.png]]
1262		-
1263	1263	**Figure 19: Logical Class Diagram of the Subscription**
1264	1264
1265	1265	=== 7.5.2 Subscription Information ===
...	...	@@ -1266,73 +1266,59 @@
1266	1266
1267	1267	Regardless of the type of registry/repository events being observed, a subscription always contains:
1268	1268
1269		-~1. A set of URIs describing the end-points to which notifications must be sent if the subscription is activated. The URIs can be either mailto~: or http: protocol. In the former case an email notification is sent; in the latter an HTTP POST notification is sent.
	1230	+1. A set of URIs describing the end-points to which notifications must be sent if the subscription is activated. The URIs can be either mailto~: or http: protocol. In the former case an email notification is sent; in the latter an HTTP POST notification is sent.
	1231	+1. A user-defined identifier which is returned in the response to the subscription request. This helps with asynchronous processing and is NOT stored in the Registry.
	1232	+1. A validity period which defines both when the subscription becomes active and expires. The subscriber may be sent a notification on expiration of the subscription.
	1233	+1. A selector which specifies which type of events are of interest. The set of event types is:
1270	1270
1271		-2. A user-defined identifier which is returned in the response to the subscription request. This helps with asynchronous processing and is NOT stored in the Registry.
	1235	+(% style="width:1031.29px" %)
	1236	+|(% style="width:319px" %)**Event Type**|(% style="width:678px" %)**Comment**
	1237	+|(% style="width:319px" %)STRUCTURAL_REPOSITORY_EVENTS|(% style="width:678px" %)Life-cycle changes to Maintainable Artefacts in the structural metadata repository.
	1238	+|(% style="width:319px" %)DATA_REGISTRATION_EVENTS|(% style="width:678px" %)Whenever a published dataset is registered. This can be either a SDMXML data file or an SDMX conformant database.
	1239	+|(% style="width:319px" %)METADATA_REGISTRATION_EVENTS|(% style="width:678px" %)Whenever a published metadataset is registered. This can be either a SDMXML reference metadata file or an SDMX conformant database.
	1240	+|(% style="width:319px" %)ALL_EVENTS|(% style="width:678px" %)All events of the specified EventType
1272	1272
1273		-3. A validity period which defines both when the subscription becomes active and expires. The subscriber may be sent a notification on expiration of the subscription.
1274		-
1275		-4. A selector which specifies which type of events are of interest. The set of event types is:
1276		-
1277		-|**Event Type**|**Comment**
1278		-|STRUCTURAL_REPOSITORY_EVENTS|Life-cycle changes to Maintainable Artefacts in the structural metadata repository.
1279		-|DATA_REGISTRATION_EVENTS|Whenever a published dataset is registered. This can be either a SDMXML data file or an SDMX conformant database.
1280		-|METADATA_REGISTRATION_EVENTS|Whenever a published metadataset is registered. This can be either a SDMXML reference metadata file or an SDMX conformant database.
1281		-|ALL_EVENTS|All events of the specified EventType
1282		-
1283	1283	=== 7.5.3 Wildcard Facility ===
1284	1284
1285	1285	Subscription notification supports wildcarded identifier components URNs, which are identiiers which have some or all of their component parts replaced by the wildcard character `%`. Identifier components comprise:
1286	1286
1287		- agencyID
	1246	+* agencyID
	1247	+* id
	1248	+* version
1288	1288
1289		- id
1290		-
1291		- version
1292		-
1293	1293	Examples of wildcarded identifier components for an identified object type of Codelist are shown below.
1294	1294
1295		-AgencyID = %
1296		-
	1252	+//AgencyID = %
1297	1297	Id = %
	1254	+Version = %//
1298	1298
1299		-Version = %
1300		-
1301	1301	This subscribes to all Codelists of all versions for all agencies.
1302	1302
1303		-AgencyID = AGENCY1
1304		-
	1258	+//AgencyID = AGENCY1
1305	1305	Id = CODELIST1
	1260	+Version = %//
1306	1306
1307		-Version = %
1308		-
1309	1309	This subscribes to all versions of Codelist CODELIST1 maintained by the agency
1310	1310
1311		-AGENCY1
1312		-
	1264	+//AGENCY1
1313	1313	AgencyID = AGENCY1
1314		-
1315	1315	Id = %
	1267	+Version = %//
1316	1316
1317		-Version = %
1318		-
1319	1319	This subscribes to all versions of all Codelist objects maintained by the agency
1320	1320
1321		-AGENCY1
1322		-
	1271	+//AGENCY1
1323	1323	AgencyID = %
1324		-
1325	1325	Id = CODELIST1
	1274	+Version = %//
1326	1326
1327		-Version = %
1328		-
1329	1329	This subscribes to all versions of Codelist CODELIST1 maintained by the agency
1330	1330
1331		-AGENCY1
	1278	+//AGENCY1//
1332	1332
1333	1333	Note that if the subscription is to the latest version then this can be achieved by the * character
1334	1334
1335		-i.e. Version = *
	1282	+//i.e. Version = *//
1336	1336
1337	1337	Note that a subscription using the URN mechanism cannot use wildcard characters.
1338	1338
...	...	@@ -1344,16 +1344,14 @@
1344	1344
1345	1345	Whenever a dataset or metadata-set is registered a registration event is created. A subscription may be observing all data or metadata registrations, or it may focus on specific registrations as shown in the table below:
1346	1346
	1294	+(% style="width:974.294px" %)
	1295	+|(% style="width:295px" %)**Selector**|(% style="width:677px" %)**Comment**
	1296	+|(% style="width:295px" %)DataProvider|(% style="width:677px" %)Any datasets or metadata sets registered by the specified data provider will activate the notification.
	1297	+|(% style="width:295px" %)ProvisionAgreement|(% style="width:677px" %)Any datasets or metadata sets registered for the provision agreement will activate the notification.
	1298	+|(% style="width:295px" %)Dataflow (&Metadataflow)|(% style="width:677px" %)Any datasets or metadata sets registered for the specified dataflow (or metadataflow) will activate the notification.
	1299	+|(% style="width:295px" %)DataStructureDefinition & MetadataStructureDefinition|(% style="width:677px" %)Any datasets or metadata sets registered for those dataflows (or metadataflows) that are based on the specified Data Structure Definition will activate the notification.
	1300	+|(% style="width:295px" %)Category|(% style="width:677px" %)Any datasets or metadata sets registered for those dataflows, metadataflows, provision agreements that are categorised by the category.
1347	1347
1348		-|**Selector**|**Comment**
1349		-|DataProvider|Any datasets or metadata sets registered by the specified data provider will activate the notification.
1350		-|ProvisionAgreement|Any datasets or metadata sets registered for the provision agreement will activate the notification.
1351		-|Dataflow (&Metadataflow)|Any datasets or metadata sets registered for the specified dataflow (or metadataflow) will activate the notification.
1352		-|DataStructureDefinition & MetadataStructureDefinition|Any datasets or metadata sets registered for those dataflows (or metadataflows) that are based on the specified Data Structure Definition will
1353		-|**Selector**|**Comment**
1354		-| |activate the notification.
1355		-|Category|Any datasets or metadata sets registered for those dataflows, metadataflows, provision agreements that are categorised by the category.
1356		-
1357	1357	The event will also capture the semantic of the registration: deletion or replacement of an existing registration or a new registration.
1358	1358
1359	1359	== 7.6 Notification ==
...	...	@@ -1360,8 +1360,10 @@
1360	1360
1361	1361	=== 7.6.1 Logical Class Diagram ===
1362	1362
	1308	+[[image:1747829675568-610.png]]
1363	1363
1364		-==== Figure 20: Logical Class Diagram of the Notification ====
	1310	+(% class="wikigeneratedid" id="HFigure20:LogicalClassDiagramoftheNotification" %)
	1311	+**Figure 20: Logical Class Diagram of the Notification**
1365	1365
1366	1366	A notification is an XML document that is sent to a user via email or http POST whenever a subscription is activated. It is an asynchronous one-way message.
1367	1367
...	...	@@ -1381,5 +1381,3 @@
1381	1381	=== 7.6.3 Registration Event Component ===
1382	1382
1383	1383	The notification will contain the Registration.
1384		-
1385		-

1747829109466-595.png

Author

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

Size

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

Content

1747829139951-378.png

Author

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

Size

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

Content

1747829204737-370.png

Author

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

Size

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

Content

1747829290890-122.png

Author

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

Size

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

Content

1747829477882-750.png

Author

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

Size

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

Content

1747829554603-150.png

Author

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

Size

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

Content

1747829675568-610.png

Author

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

Size

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

Content

1747832400104-286.png

Author

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

Size

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

Content

1747994320263-112.png

Author

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

Size

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

Content

SKMS.Methodology.Code.MethodologyClass[0]