Changes for page SDMX 3.0 Standards. Section 5. Registry Specification: Logical Functionality

Summary

• Page properties (2 modified, 0 added, 0 removed)
• Objects (0 modified, 0 added, 1 removed)
  • SUZ.Methodology.Code.MethodologyClass[0]

Details

Page properties

Content

...	...	@@ -183,11 +183,11 @@
183	183
184	184	=== {{id name="_Toc93847"/}}5.2.2 Structure Submission Service ===
185	185
186		-The registry must support a mechanism for submitting structural metadata. This mechanism can be the SDMX REST interface for structural metadata (this is defined in the corresponding GitHub project, dedicated to the SDMX REST API: [[__https:~~/~~/github.com/sdmx-twg/sdmx-rest__>>https://https:github.comsdmx-twgsdmx-rest]]). In order for the architecture to be scalable, the finest-grained piece of structural metadata that can be processed by the SDMX-RR is a MaintainableArtefact, with the exception of Item Schemes, where changes at an Item level is also possible (see next section on the SDMX Information Model).
	186	+The registry must support a mechanism for submitting structural metadata. This mechanism can be the SDMX REST interface for structural metadata (this is defined in the corresponding GitHub project, dedicated to the SDMX REST API: __[[https:~~/~~/github.com/sdmx>>url:https://github.com/sdmx-twg/sdmx-rest]][[->>url:https://github.com/sdmx-twg/sdmx-rest]][[twg/sdmx>>url:https://github.com/sdmx-twg/sdmx-rest]][[->>url:https://github.com/sdmx-twg/sdmx-rest]][[rest>>url:https://github.com/sdmx-twg/sdmx-rest]]__[[)>>url:https://github.com/sdmx-twg/sdmx-rest]]. In order for the architecture to be scalable, the finest-grained piece of structural metadata that can be processed by the SDMX-RR is a MaintainableArtefact, with the exception of Item Schemes, where changes at an Item level is also possible (see next section on the SDMX Information Model).
187	187
188	188	=== {{id name="_Toc93848"/}}5.2.3 Structure Query Service ===
189	189
190		-The registry must support a mechanism for querying for structural metadata. This mechanism can be the SDMX REST interface for structural metadata (this is defined in the corresponding GitHub project, dedicated to the SDMX REST API: [[__https:~~/~~/github.com/sdmx-twg/sdmx-rest__>>https://https:github.comsdmx-twgsdmx-rest]]). The registry response to this query mechanism is the SDMX Structure message, which has as its root node:
	190	+The registry must support a mechanism for querying for structural metadata. This mechanism can be the SDMX REST interface for structural metadata (this is defined in the corresponding GitHub project, dedicated to the SDMX REST API: __[[https:~~/~~/github.com/sdmx>>url:https://github.com/sdmx-twg/sdmx-rest]][[->>url:https://github.com/sdmx-twg/sdmx-rest]][[twg/sdmx>>url:https://github.com/sdmx-twg/sdmx-rest]][[->>url:https://github.com/sdmx-twg/sdmx-rest]][[rest>>url:https://github.com/sdmx-twg/sdmx-rest]]__ [[)>>url:https://github.com/sdmx-twg/sdmx-rest]]. The registry response to this query mechanism is the SDMX Structure message, which has as its root node:
191	191
192	192	* Structure
193	193
...	...	@@ -280,7 +280,7 @@
280	280	Subscription management involves a user submitting a subscription request which contains:
281	281
282	282	* 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).
283		-* a list of URIs or endpoints to which an XML notification message can be sent. Supported endpoint types will be email (mailto~: ) and HTTP POST (a normal http:~/~/ address);
	283	+* a list of URIs or endpoints to which an XML notification message can be sent. Supported endpoint types will be email (mailto~:) and HTTP POST (a normal http:~/~/ address);
284	284	* request for a list of submitted subscriptions;
285	285	* deletion of a subscription;
286	286
...	...	@@ -301,8 +301,10 @@
301	301
302	302	a) Be a draft version.
303	303	)))
	304	+|(% style="width:188px" %)**Interface**|(% style="width:542px" %)**Behaviour**
304	304	|(% style="width:188px" %) |(% style="width:542px" %)(((
305	305	b) Not be explicitly{{footnote}}With semantic versioning, it is allowed to reference a range of artefacts, e.g., a DSD referencing a Codelist with version 1.2.3+ means all patch versions greater than 1.2.3. This means that deleting 1.2.4-draft does not break integrity of the aforementioned DSD.{{/footnote}} referenced from any other object in the Registry.
	307	+
306	306	4) The semantic versioning rules in the SDMX documentation MUST be obeyed.
307	307	)))
308	308	|(% style="width:188px" %)Structure submission|(% style="width:542px" %)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.
...	...	@@ -327,12 +327,14 @@
327	327
328	328	The table below shows the identification and related data attributes to be stored in a registry for objects that are one of:
329	329
330		-* //nnotable//
	332	+* //Annotable//
331	331	* //Identifiable//
332	332	* //Nameable//
333	333	* //Versionable//
334	334	* //Maintainable//
335	335
	338	+:
	339	+
336	336	(((
337	337	(% style="width:1052.29px" %)
338	338	|**Object Type**|(% style="width:241px" %)**Data Attributes**|(% style="width:156px" %)**Status**|**Data type**|(% style="width:457px" %)**Notes**
...	...	@@ -360,9 +360,9 @@
360	360
361	361	**Table 1: Common Attributes of Object Types**
362	362
363		-== {{id name="_Toc93856"/}}6.2 Unique identification of SDMX objects ==
	367	+=== {{id name="_Toc93856"/}}6.2 Unique identification of SDMX objects ===
364	364
365		-=== {{id name="_Toc93857"/}}6.2.1 Agencies and Metadata Providers ===
	369	+===== {{id name="_Toc93857"/}}6.2.1 Agencies and Metadata Providers =====
366	366
367	367	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.
368	368
...	...	@@ -443,14 +443,23 @@
443	443	The packages are:
444	444
445	445	base
	450	+
446	446	codelist
	452	+
447	447	conceptscheme
	454	+
448	448	datastructure
	456	+
449	449	categoryscheme
	458	+
450	450	registry
	460	+
451	451	metadatastructure
	462	+
452	452	process
	464	+
453	453	structuremapping
	466	+
454	454	transformation
455	455
456	456	**maintainable-object-id** is the identifier of the maintainable object. This will always be present as all identifiable objects are either a maintainable object or contained in a maintainable object.
...	...	@@ -495,23 +495,23 @@
495	495
496	496	The Data Structure Definition CRED_EXT_DEBT of legacy version 2.1 maintained by the toplevel Agency TFFS would have the URN:
497	497
498		- urn:sdmx:org.sdmx.infomodel.datastructure.DataStucture=TFFS:CRED_EXT_ DEBT(2.1)
	511	+urn:sdmx:org.sdmx.infomodel.datastructure.DataStucture=TFFS:CRED_EXT_ DEBT(2.1)
499	499
500	500	The URN for a code for Argentina maintained by ISO in the code list CL_3166A2 of semantic version 1.0.0 would be:
501	501
502		- urn:sdmx:org.sdmx.infomodel.codelist.Code=ISO:CL_3166A2(1.0.0).AR
	515	+urn:sdmx:org.sdmx.infomodel.codelist.Code=ISO:CL_3166A2(1.0.0).AR
503	503
504	504	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 of the semantic extended version 1.0.0draft would be:
505	505
506		- urn:sdmx:org.sdmx.infomodel.categoryscheme.Category=SDMX:SUBJECT_MATT ER_DOMAINS(1.0.0-draft).1.2
	519	+urn:sdmx:org.sdmx.infomodel.categoryscheme.Category=SDMX:SUBJECT_MATT ER_DOMAINS(1.0.0-draft).1.2
507	507
508	508	The URN for a Metadata Attribute maintained by SDMX in the MSD CONTACT_METADATA of semantic version 1.0.0 where the hierarchy of the Metadata Attribute is CONTACT_DETAILS/CONTACT_NAME would be:
509	509
510		- urn:sdmx:org.sdmx.infomodel.metadatastructure.MetadataAttribute=SDMX: CONTACT_METADATA(1.0.0).CONTACT_DETAILS.CONTACT_NAME
	523	+urn:sdmx:org.sdmx.infomodel.metadatastructure.MetadataAttribute=SDMX: CONTACT_METADATA(1.0.0).CONTACT_DETAILS.CONTACT_NAME
511	511
512	512	The TFFS defines ABC as a sub-Agency of TFFS then the URN of a Dataflow maintained by ABC and identified as EXTERNAL_DEBT of semantic version 1.0.0 would be:
513	513
514		- urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=TFFS.ABC:EXTERNAL_ DEBT(1.0.0)
	527	+urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=TFFS.ABC:EXTERNAL_ DEBT(1.0.0)
515	515
516	516	The SDMX-RR MUST support this globally unique identification scheme. The SDMX-RR MUST be able to create the URN from the individual identification attributes submitted and to transform the URN to these identification attributes. The identification attributes are:
517	517
...	...	@@ -730,7 +730,7 @@
730	730
731	731	=== {{id name="_Toc93862"/}}7.1 Structural Definition Metadata ===
732	732
733		-=== {{id name="_Toc93863"/}}7.1.1 Introduction ===
	746	+===== {{id name="_Toc93863"/}}7.1.1 Introduction =====
734	734
735	735	The SDMX Registry must have the ability to support agencies in their role of defining and disseminating structural metadata artefacts. These artefacts include data structure definitions, code lists, concepts etc. and are fully defined in the SDMX-IM. An authenticated agency may submit valid structural metadata definitions which must be stored in the registry. Note that the term “structural metadata” refers as a general term to all structural components (Data Structure Definitions, Metadata Structure Definitions, Code Lists, Concept Schemes, etc.)
736	736
...	...	@@ -797,7 +797,7 @@
797	797
798	798	**Table 4: Table of Maintainable Artefacts for Structural Definition Metadata**
799	799
800		-=== {{id name="_Toc93864"/}}7.1.2 Item Scheme, Structure ===
	813	+===== {{id name="_Toc93864"/}}7.1.2 Item Scheme, Structure =====
801	801
802	802	The artefacts included in the structural definitions are:
803	803
...	...	@@ -806,19 +806,19 @@
806	806	* All types of Structure (Data Structure Definition, Metadata Structure Definition)
807	807	* All types of Structure Usage (Dataflow, Metadataflow)
808	808
809		-=== {{id name="_Toc93865"/}}7.1.3 Structure Usage ===
	822	+===== {{id name="_Toc93865"/}}7.1.3 Structure Usage =====
810	810
811		-==== 7.1.3.1 Structure Usage: Basic Concepts ====
	824	+**7.1.3.1 Structure Usage: Basic Concepts**
812	812
813	813	The Structure Usage defines, in its concrete classes of Dataflow and Metadataflow, which flows of data and metadata use which specific Structure, and importantly for the support of data and metadata discovery, the Structure Usage can be linked to one or more Category in one or more Category Scheme using the Categorisation mechanism. This gives the ability for an application to discover data and metadata by “drilling down” the Category Schemes.
814	814
815		-==== 7.1.3.2 Structure Usage Schematic ====
	828	+**7.1.3.2 Structure Usage Schematic**
816	816
817	817	[[image:SDMX 3-0-0 SECTION 5 FINAL-1.0_en_52097ab5.jpg||height="246" width="438"]]
818	818
819	819	**Figure 9: Schematic of Linking the Data and Metadata Flows to Categories and Structure Definitions**
820	820
821		-==== 7.1.3.3 Structure Usage Model ====
	834	+**7.1.3.3 Structure Usage Model**
822	822
823	823	[[image:SDMX 3-0-0 SECTION 5 FINAL-1.0_en_302cc1a2.jpg||height="548" width="578"]]
824	824
...	...	@@ -834,9 +834,9 @@
834	834	* Categorisation to Dataflow and Category
835	835	* Categorisation to Metadataflow and Category
836	836
837		-== {{id name="_Toc93866"/}}7.2 Data and Metadata Provisioning ==
	850	+=== {{id name="_Toc93866"/}}7.2 Data and Metadata Provisioning ===
838	838
839		-=== {{id name="_Toc93867"/}}7.2.1 Provisioning Agreement: Basic concepts ===
	852	+===== {{id name="_Toc93867"/}}7.2.1 Provisioning Agreement: Basic concepts =====
840	840
841	841	Data/Metadata provisioning defines a framework in which the provision of different types of statistical data and metadata by various data/metadata providers can be specified and controlled. This framework is the basis on which the existence of data can be made known to the SDMX-enabled community and hence the basis on which data can subsequently be discovered. Such a framework can be used to regulate the data content to facilitate the building of intelligent applications. It can also be used to facilitate the processing implied by service level agreements, or other provisioning agreements in those scenarios that are based on legal directives. Additionally, quality and timeliness metadata can be supported by this framework which makes it practical to implement information supply chain monitoring.
842	842
...	...	@@ -844,7 +844,7 @@
844	844
845	845	Although the Provision Agreement directly supports the data-sharing “pull” model, it is also useful in “push” exchanges (bilateral and gateway scenarios), or in a dissemination environment. It should be noted, too, that in any exchange scenario, the registry functions as a repository of structural metadata.
846	846
847		-=== {{id name="_Toc93868"/}}7.2.2 Provisioning Agreement Model – pull use case ===
	860	+===== {{id name="_Toc93868"/}}7.2.2 Provisioning Agreement Model – pull use case =====
848	848
849	849	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.
850	850
...	...	@@ -866,9 +866,9 @@
866	866
867	867	A Provision Agreement is structural metadata. Each Provision Agreement must reference a Data Provider or Metadata Provider and a Dataflow or Metadataflow Definition. The Data/Metadata Provider and the Dataflow/Metadataflow must exist already in order to set up a Metadata Provision or Provision Agreement.
868	868
869		-== {{id name="_Toc93869"/}}7.3 Data and Metadata Constraints ==
	882	+=== {{id name="_Toc93869"/}}7.3 Data and Metadata Constraints ===
870	870
871		-=== {{id name="_Toc93870"/}}7.3.1 Data and Metadata Constraints: Basic Concepts ===
	884	+===== {{id name="_Toc93870"/}}7.3.1 Data and Metadata Constraints: Basic Concepts =====
872	872
873	873	Constraints are, effectively, lists of the valid or actual content of data and metadata. Constraints can be used to specify a subset of the theoretical content of data set or metadata set which can be derived from the specification of the DSD or MSD. A Constraint can comprise a list of keys or a list of content (usually code values) of a specific component such as a dimension or attribute.
874	874
...	...	@@ -932,14 +932,17 @@
932	932
933	933	The Registration has an action attribute which takes one of the following values:
934	934
	948	+:
	949	+
935	935	(((
936		-(% style="width:761.294px" %)
937		-|(% style="width:196px" %)**Action Attribute Value**|(% style="width:561px" %)**Behaviour**
938		-|(% style="width:196px" %)Append|(% style="width:561px" %)Add this Registration to the registry
939		-|(% style="width:196px" %)Replace|(% style="width:561px" %)(((
940		-Replace the existing Registration with identified by the id in the Registration of the SubmitRegistrationRequest
	951	+|**Action Attribute Value**|**Behaviour**
	952	+|Append|Add this Registration to the registry
	953	+|Replace|(((
	954	+Replace the existing Registration with identified by the id in the
	955	+
	956	+Registration of the SubmitRegistrationRequest
941	941	)))
942		-|(% style="width:196px" %)Delete|(% style="width:561px" %)Delete the existing Registration identified by the id in the Registration of the SubmitRegistrationRequest
	958	+|Delete|Delete the existing Registration identified by the id in the Registration of the SubmitRegistrationRequest
943	943	)))
944	944
945	945	[[image:SDMX 3-0-0 SECTION 5 FINAL-1.0_en_bc1dcdec.jpg||height="575" width="579"]]
...	...	@@ -956,20 +956,27 @@
956	956
957	957	Information in the data or metadata set is extracted and placed in one or more //Constraint//s (see the //Constraint// 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 ProvisionAgreement or MetadataProvisionAgreement as shown in the table below.
958	958
	975	+:
	976	+
959	959	(((
960		-(% style="width:678.294px" %)
961		-|**Indexing Required**|(% style="width:504px" %)**Registration Process Activity**
962		-|indexTimeSeries|(% style="width:504px" %)Extract all the series keys and create a KeySet(s) Constraint.
963		-|indexDataSet|(% style="width:504px" %)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.
964		-|indexReportingPeriod|(% style="width:504px" %)(((
	978	+|**Indexing Required**|**Registration Process Activity**
	979	+|indexTimeSeries|Extract all the series keys and create a KeySet(s) Constraint.
	980	+|indexDataSet|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.
	981	+|indexReportingPeriod|(((
965	965	This applies only to a registered __dataset__.
	983	+
966	966	Extract the Reporting Begin and Reporting End from the Header of the Message containing the data set, and create a Reference Period constraint.
967	967	)))
968		-|**Indexing Required**|(% style="width:504px" %)**Registration Process Activity**
969		-|indexAttributes|(% style="width:504px" %)(((
	986	+|**Indexing Required**|**Registration Process Activity**
	987	+|indexAttributes|(((
970	970	**Data Set**
971		-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
	989	+
	990	+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
	991	+
	992	+SDMXIM, and the associated Selection Value
	993	+
972	972	**Metadata Set**
	995	+
973	973	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.
974	974	)))
975	975	)))
...	...	@@ -978,7 +978,7 @@
978	978
979	979	The Registration must reference the ProvisionAgreement or MetadataProvisionAgreement to which it relates.
980	980
981		-=== {{id name="_Toc93876"/}}7.4.3 Registration Response ===
	1004	+===== {{id name="_Toc93876"/}}7.4.3 Registration Response =====
982	982
983	983	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 SubmitRegistration class has a status field, which is either set to “Success”, “Warning” or “Failure”.
984	984
...	...	@@ -1008,18 +1008,20 @@
1008	1008
1009	1009	Regardless of the type of registry/repository events being observed, a subscription always contains:
1010	1010
1011		-1. 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.
	1034	+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.
1012	1012	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.
1013	1013	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.
1014	1014	1. A selector which specifies which type of events are of interest. The set of event types is:
1015	1015
	1039	+:
	1040	+::
	1041	+
1016	1016	(((
1017		-(% style="width:856.294px" %)
1018		-|(% style="width:320px" %)**Event Type**|(% style="width:532px" %)**Comment**
1019		-|(% style="width:320px" %)STRUCTURAL_REPOSITORY_EVENTS|(% style="width:532px" %)Life-cycle changes to Maintainable Artefacts in the structural metadata repository.
1020		-|(% style="width:320px" %)DATA_REGISTRATION_EVENTS|(% style="width:532px" %)Whenever a published dataset is registered. This can be either a SDMXML data file or an SDMX conformant database.
1021		-|(% style="width:320px" %)METADATA_REGISTRATION_EVENTS|(% style="width:532px" %)Whenever a published metadataset is registered. This can be either a SDMXML reference metadata file or an SDMX conformant database.
1022		-|(% style="width:320px" %)ALL_EVENTS|(% style="width:532px" %)All events of the specified EventType
	1043	+|**Event Type**|**Comment**
	1044	+|STRUCTURAL_REPOSITORY_EVENTS|Life-cycle changes to Maintainable Artefacts in the structural metadata repository.
	1045	+|DATA_REGISTRATION_EVENTS|Whenever a published dataset is registered. This can be either a SDMXML data file or an SDMX conformant database.
	1046	+|METADATA_REGISTRATION_EVENTS|Whenever a published metadataset is registered. This can be either a SDMXML reference metadata file or an SDMX conformant database.
	1047	+|ALL_EVENTS|All events of the specified EventType
1023	1023	)))
1024	1024
1025	1025	=== {{id name="_Toc93880"/}}7.5.3 Wildcard Facility ===
...	...	@@ -1086,14 +1086,15 @@
1086	1086
1087	1087	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:
1088	1088
	1114	+:
	1115	+
1089	1089	(((
1090		-(% style="width:1126.29px" %)
1091		-|(% style="width:382px" %)**Selector**|(% style="width:740px" %)**Comment**
1092		-|(% style="width:382px" %)DataProvider & MetadataProvider|(% style="width:740px" %)Any datasets or metadata sets registered by the specified data or metadata provider will activate the notification.
1093		-|(% style="width:382px" %)ProvisionAgreement & MetadataProvisionAgreement|(% style="width:740px" %)Any datasets or metadata sets registered for the agreement will activate the notification.
1094		-|(% style="width:382px" %)Dataflow & Metadataflow|(% style="width:740px" %)Any datasets or metadata sets registered for the specified dataflow (or metadataflow) will activate the notification.
1095		-|(% style="width:382px" %)DataStructureDefinition & MetadataStructureDefinition|(% style="width:740px" %)Any datasets or metadata sets registered for those dataflows (or metadataflows) that are based on the specified Data Structure Definition will activate the notification
1096		-|(% style="width:382px" %)Category|(% style="width:740px" %)Any datasets or metadata sets registered for those dataflows, metadataflows, provision agreements that are categorised by the category.
	1117	+|**Selector**|**Comment**
	1118	+|DataProvider & MetadataProvider|Any datasets or metadata sets registered by the specified data or metadata provider will activate the notification.
	1119	+|ProvisionAgreement & MetadataProvisionAgreement|Any datasets or metadata sets registered for the agreement will activate the notification.
	1120	+|Dataflow & Metadataflow|Any datasets or metadata sets registered for the specified dataflow (or metadataflow) will activate the notification.
	1121	+|DataStructureDefinition & MetadataStructureDefinition|Any datasets or metadata sets registered for those dataflows (or metadataflows) that are based on the specified Data Structure Definition will activate the notification
	1122	+|Category|Any datasets or metadata sets registered for those dataflows, metadataflows, provision agreements that are categorised by the category.
1097	1097	)))
1098	1098
1099	1099	The event will also capture the semantic of the registration: deletion or replacement of an existing registration or a new registration.
...	...	@@ -1125,6 +1125,12 @@
1125	1125
1126	1126	The notification will contain the Registration.
1127	1127
1128		-----
	1154	+[[1>>path:#sdfootnote1anc||name="sdfootnote1sym"]] With semantic versioning, it is allowed to reference a range of artefacts, e.g., a DSD referencing a Codelist with version 1.2.3+ means all patch versions greater than 1.2.3. This means that deleting 1.2.4draft does not break integrity of the aforementioned DSD.
1129	1129
	1156	+[[2>>path:#sdfootnote2anc||name="sdfootnote2sym"]] 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. For example, a sub-agency of IMF is referred like this:
	1157	+
	1158	+IMF.SubAgency1
	1159	+
	1160	+[[3>>path:#sdfootnote3anc||name="sdfootnote3sym"]] Note that Codelist is also an EnumeratedList.
	1161	+
1130	1130	{{putFootnotes/}}

SUZ.Methodology.Code.MethodologyClass[0]