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

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -243,23 +243,22 @@
243	243	* that the components (Dimensions, Attributes, Measures, Metadata Attributes, etc.) are consistent with the Data Structure Definition or Metadata Structure Definition;
244	244	* 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. The Registration has an action attribute which takes one of the following values:
245	245
246		-|**Action Attribute Value**|**Behaviour**
247		-|Append|Add this registration to the registry
248		-|Replace|Replace the existing Registration with this Registration identified by the id in the Registration of the Submit Registration Request
249		-|Delete|Delete the existing Registration identified by the id in the Registration of the Submit Registration Request
	246	+(% style="width:755.294px" %)
	247	+|(% style="width:187px" %)**Action Attribute Value**|(% style="width:566px" %)**Behaviour**
	248	+|(% style="width:187px" %)Append|(% style="width:566px" %)Add this registration to the registry
	249	+|(% style="width:187px" %)Replace|(% style="width:566px" %)Replace the existing Registration with this Registration identified by the id in the Registration of the Submit Registration Request
	250	+|(% style="width:187px" %)Delete|(% style="width:566px" %)Delete the existing Registration identified by the id in the Registration of the Submit Registration Request
250	250
251	251	The Registration has three Boolean attributes which may be present to determine how an SDMX compliant dataset or metadataset indexing application must index the datasets or metadatasets upon registration. The indexing application behaviour is as follows:
252	252
253		-|**Boolean Attribute**|**Behaviour if Value is “true”**
254		-|indexTimeSeries|A compliant indexing application must index all the time series keys (for a Dataset registration) or metadata target values (for a Metadataset registration)
255		-|indexDataSet|(((
256		-A compliant indexing application must index the range of actual
257		-
258		-(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.
259		-
	254	+(% style="width:759.294px" %)
	255	+|(% style="width:191px" %)**Boolean Attribute**|(% style="width:565px" %)**Behaviour if Value is “true”**
	256	+|(% style="width:191px" %)indexTimeSeries|(% style="width:565px" %)A compliant indexing application must index all the time series keys (for a Dataset registration) or metadata target values (for a Metadataset registration)
	257	+|(% style="width:191px" %)indexDataSet|(% style="width:565px" %)(((
	258	+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.
260	260	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
261	261	)))
262		-|indexReportingPeriod|A compliant indexing application must index the time period range(s) for which data are present in the Dataset. The validity period of the Metadatasets may also be indexed.
	261	+|(% style="width:191px" %)indexReportingPeriod|(% style="width:565px" %)A compliant indexing application must index the time period range(s) for which data are present in the Dataset. The validity period of the Metadatasets may also be indexed.
263	263
264	264	=== {{id name="_Toc93850"/}}5.2.5 Data and Reference Metadata Discovery ===
265	265
...	...	@@ -293,8 +293,9 @@
293	293
294	294	Given the above, the behaviour described in the following table concerns either draft Artefacts using semantic versioning or any Artefacts using the old versioning scheme. Nevertheless, in the case of semantic versioning the registry must respect the versioning rules when performing the actions below. For example, it is not possible to replace a non-draft Artefact that follows semantic versioning, unless a newer version is introduced according to the semantic versioning rules. Furthermore, even when draft Artefacts are submitted, the registry has to verify semantic versioning is respected against the previous non-draft versions. It is worth noting that the rules for semantic versioning and replacing or maintaining semantically versioned Artefacts applies to externally shared Artefacts. This means that any system may internally perform any change within a version of an Artefact, until the latter is shared outside of that system or becomes public. Then (as also explained in the SDMX Standards Section 6 “Technical Notes”) the Artefacts must adhere to the Semantic Versioning rules.
295	295
296		-|**Interface**|**Behaviour**
297		-|All|(((
	295	+(% style="width:757.294px" %)
	296	+|(% style="width:188px" %)**Interface**|(% style="width:542px" %)**Behaviour**
	297	+|(% style="width:188px" %)All|(% style="width:542px" %)(((
298	298	1. If the action is set to “replace” (or a maintainable Artefact is PUT or POSTed) then the entire contents of the existing maintainable object in the Registry MUST be replaced by the object submitted.
299	299	1. Cross referenced structures MUST exist in either the submitted document (in Structures or Structure Location) or in the registry to which the request is submitted.
300	300	1. If the action is set to “delete” (or a maintainable Artefact is DELETEd) then the Registry MUST verify that the object can be deleted. In order to qualify for deletion, the object must:
...	...	@@ -301,14 +301,14 @@
301	301
302	302	a) Be a draft version.
303	303	)))
304		-|**Interface**|**Behaviour**
305		-| |(((
306		-b) Not be explicitly^^[[(% class="wikiinternallink wikiinternallink" %)^^1^^>>path:#sdfootnote1sym||name="sdfootnote1anc"]](%%)^^ referenced from any other object in the Registry.
	304	+|(% style="width:188px" %)**Interface**|(% style="width:542px" %)**Behaviour**
	305	+|(% style="width:188px" %) |(% style="width:542px" %)(((
	306	+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	307
308	308	4) The semantic versioning rules in the SDMX documentation MUST be obeyed.
309	309	)))
310		-|Structure submission|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.
311		-|SubmitRegistrationRequest|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. For a queryable datasource the Registry MAY validate that the source exists and can accept an SDMX data query.
	310	+|(% 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.
	311	+|(% style="width:188px" %)SubmitRegistrationRequest|(% style="width:542px" %)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. For a queryable datasource the Registry MAY validate that the source exists and can accept an SDMX data query.
312	312
313	313	= {{id name="_Toc93853"/}}6 Identification of SDMX Objects =
314	314
...	...	@@ -338,27 +338,28 @@
338	338	:
339	339
340	340	(((
341		-|**Object Type**|**Data Attributes**|**Status**|**Data type**|**Notes**
342		-|(% rowspan="4" %)//Annotable//|AnnotationTitle|C|string|
343		-|AnnotationType|C|string|
344		-|AnnotationURN|C|string|
345		-|AnnotationText in the form of InternationalString|C| |This can have languagespecific variants
346		-|(% rowspan="4" %)//Identifiable//|All content as for //Annotable// plus| | |
347		-|id|M|string|
348		-|uri|C|string|
349		-|urn|C|string|Although the urn is computable and therefore may not be submitted or stored physically, the Registry must return the urn for each object, and must be able to service a query on an object referenced solely by its urn.
350		-|(% rowspan="3" %)//Nameable//|All content as for //Identifiable// plus| | |
351		-|Name in the form of InternationalString|M|string|This can have language specific variants.
352		-|Description in the form of InternationalString|C|string|This can have language specific variants.
353		-|(% rowspan="4" %)//Versionable//|All content as for //Identifiable// plus| | |
354		-|version|M|string|This is the version number according to SDMX versioning rules.
355		-|validFrom|C|Date/time|
356		-|validTo|C|Date/time|
357		-|//Maintainable//|All content as for //Versionable// plus| | |
358		-| |isExternalReference|C|boolean|Value of “true” indicates that the actual resource is held outside of this registry. The actual reference is given in the registry URI or the structureURL, each of which must return a valid SDMX-ML file.
359		-| |serviceURL|C|string|The url of the service that can be queried for this resource.
360		-| |structureURL|C|string|The url of the resource.
361		-| |(Maintenance) organisationId|M|string|The object must be linked to a maintenance organisation, i.e., Agency or Metadata Provider.
	341	+(% style="width:1052.29px" %)
	342	+|**Object Type**|(% style="width:241px" %)**Data Attributes**|(% style="width:156px" %)**Status**|**Data type**|(% style="width:457px" %)**Notes**
	343	+|(% rowspan="4" %)//Annotable//|(% style="width:241px" %)AnnotationTitle|(% style="width:156px" %)C|string|(% style="width:457px" %)
	344	+|(% style="width:241px" %)AnnotationType|(% style="width:156px" %)C|string|(% style="width:457px" %)
	345	+|(% style="width:241px" %)AnnotationURN|(% style="width:156px" %)C|string|(% style="width:457px" %)
	346	+|(% style="width:241px" %)AnnotationText in the form of InternationalString|(% style="width:156px" %)C| |(% style="width:457px" %)This can have languagespecific variants
	347	+|(% rowspan="4" %)//Identifiable//|(% style="width:241px" %)All content as for //Annotable// plus|(% style="width:156px" %) | |(% style="width:457px" %)
	348	+|(% style="width:241px" %)id|(% style="width:156px" %)M|string|(% style="width:457px" %)
	349	+|(% style="width:241px" %)uri|(% style="width:156px" %)C|string|(% style="width:457px" %)
	350	+|(% style="width:241px" %)urn|(% style="width:156px" %)C|string|(% style="width:457px" %)Although the urn is computable and therefore may not be submitted or stored physically, the Registry must return the urn for each object, and must be able to service a query on an object referenced solely by its urn.
	351	+|(% rowspan="3" %)//Nameable//|(% style="width:241px" %)All content as for //Identifiable// plus|(% style="width:156px" %) | |(% style="width:457px" %)
	352	+|(% style="width:241px" %)Name in the form of InternationalString|(% style="width:156px" %)M|string|(% style="width:457px" %)This can have language specific variants.
	353	+|(% style="width:241px" %)Description in the form of InternationalString|(% style="width:156px" %)C|string|(% style="width:457px" %)This can have language specific variants.
	354	+|(% rowspan="4" %)//Versionable//|(% style="width:241px" %)All content as for //Identifiable// plus|(% style="width:156px" %) | |(% style="width:457px" %)
	355	+|(% style="width:241px" %)version|(% style="width:156px" %)M|string|(% style="width:457px" %)This is the version number according to SDMX versioning rules.
	356	+|(% style="width:241px" %)validFrom|(% style="width:156px" %)C|Date/time|(% style="width:457px" %)
	357	+|(% style="width:241px" %)validTo|(% style="width:156px" %)C|Date/time|(% style="width:457px" %)
	358	+|//Maintainable//|(% style="width:241px" %)All content as for //Versionable// plus|(% style="width:156px" %) | |(% style="width:457px" %)
	359	+| |(% style="width:241px" %)isExternalReference|(% style="width:156px" %)C|boolean|(% style="width:457px" %)Value of “true” indicates that the actual resource is held outside of this registry. The actual reference is given in the registry URI or the structureURL, each of which must return a valid SDMX-ML file.
	360	+| |(% style="width:241px" %)serviceURL|(% style="width:156px" %)C|string|(% style="width:457px" %)The url of the service that can be queried for this resource.
	361	+| |(% style="width:241px" %)structureURL|(% style="width:156px" %)C|string|(% style="width:457px" %)The url of the resource.
	362	+| |(% style="width:241px" %)(Maintenance) organisationId|(% style="width:156px" %)M|string|(% style="width:457px" %)The object must be linked to a maintenance organisation, i.e., Agency or Metadata Provider.
362	362	)))
363	363
364	364	**Table 1: Common Attributes of Object Types**
...	...	@@ -439,13 +439,13 @@
439	439
440	440	Following the same principles, the Metadata Provider is the maintenance organisation for a special subset of Maintainable Artefacts, i.e., the Metadatasets; the latter are the containers of reference metadata combined with a target that those metadata refer to.
441	441
442		-===== {{id name="_Toc93858"/}}6.2.2 Universal Resource Name (URN) =====
	443	+=== {{id name="_Toc93858"/}}6.2.2 Universal Resource Name (URN) ===
443	443
444		-**6.2.2.1 Introduction**
	445	+==== 6.2.2.1 Introduction ====
445	445
446	446	To provide interoperability between SDMX Registry/Repositories in a distributed network environment, it is important to have a scheme for uniquely identifying (and thus accessing) all first-class (Identifiable) SDMX-IM objects. Most of these unique identifiers are composite (containing maintenance agency, or parent object identifiers), and there is a need to be able to construct a unique reference as a single string. This is achieved by having a globally unique identifier called a universal resource name (URN) which is generated from the actual identification components in the SDMX-RR APIs. In other words, the URN for any Identifiable Artefact is constructed from its component identifiers (agency, id, version etc.).
447	447
448		-**6.2.2.2 URN Structure //__Case Rules for URN__//**// //
	449	+==== 6.2.2.2 URN Structure //__Case Rules for URN__ // ====
449	449
450	450	For the URN, all parts of the string are case sensitive. The generic structure of the URN is as follows:
451	451
...	...	@@ -623,7 +623,7 @@
623	623	urn:sdmx.org.sdmx.infomodel.{package}.{classname}=
624	624
625	625	|**Classname**|**Ending URN pattern**|**Example**
626		-|Agency^^[[(% class="wikiinternallink wikiinternallink" %)^^2^^>>path:#sdfootnote2sym||name="sdfootnote2anc"]](%%)^^|agencySchemeAgencyId:**AGENCIES**(**1.0**).agencyId|ECB:**AGENCIES**(**1.0**).AA
	627	+|Agency^^[[(% class="wikiinternallink wikiinternallink wikiinternallink" %)^^2^^>>path:#sdfootnote2sym||name="sdfootnote2anc"]](%%)^^|agencySchemeAgencyId:**AGENCIES**(**1.0**).agencyId|ECB:**AGENCIES**(**1.0**).AA
627	627	|//AgencyScheme//|agencySchemeAgencyId:**AGENCIES**(**1.0**)|ECB:**AGENCIES**(**1.0**)
628	628	|//Categorisation//|categorisationAgencyId:categorisationId(version)|IMF:cat001(1.0.0)
629	629	|Category|categorySchemeAgencyId:categorySchemeId(versi on).categoryId.categoryId.categoryId etc.|IMF:SDDS(1.0.0):level_1_category.level_2_category …
...	...	@@ -840,7 +840,7 @@
840	840
841	841	• All types of Item Scheme (Codelist, Concept Scheme, Category Scheme, Organisation Scheme, Agency Scheme, Data Provider Scheme, Metadata Provider Scheme, Data Consumer Scheme, Organisation Unit Scheme, Transformation Scheme, Name Personalisation Scheme, Custom Type Scheme, Vtl Mapping Scheme, Ruleset Scheme, User Defined Operator Scheme)
842	842
843		-• All types of Enumerated List (ValueList)^^[[(% class="wikiinternallink wikiinternallink" %)^^3^^>>path:#sdfootnote3sym||name="sdfootnote3anc"]](%%)^^
	844	+• All types of Enumerated List (ValueList)^^[[(% class="wikiinternallink wikiinternallink wikiinternallink" %)^^3^^>>path:#sdfootnote3sym||name="sdfootnote3anc"]](%%)^^
844	844
845	845	• All types of Structure (Data Structure Definition, Metadata Structure Definition)
846	846
...	...	@@ -1185,3 +1185,5 @@
1185	1185	IMF.SubAgency1
1186	1186
1187	1187	[[3>>path:#sdfootnote3anc||name="sdfootnote3sym"]] Note that Codelist is also an EnumeratedList.
	1189	+
	1190	+{{putFootnotes/}}