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

Summary

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

Details

Page properties

Content

...	...	@@ -992,7 +992,7 @@
992	992
993	993	The Registration must reference the ProvisionAgreement to which it relates.
994	994
995		-=== 7.4.3 Registration Response ===
	995	+===== {{id name="_Toc90825"/}}7.4.3 Registration Response =====
996	996
997	997	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”.
998	998
...	...	@@ -1004,7 +1004,7 @@
1004	1004
1005	1005	**Figure 18: Logical class diagram showing the registration response**
1006	1006
1007		-== 7.5 Subscription and Notification Service ==
	1007	+=== {{id name="_Toc90826"/}}7.5 Subscription and Notification Service ===
1008	1008
1009	1009	The contents of the SDMX Registry/Repository will change regularly: new code lists and key families will be published and new datasets and metadata-sets will be registered. To obviate the need for users to repeatedly query the registry to see when new information is available, a mechanism is provided to allow users to be notified when these events happen.
1010	1010
...	...	@@ -1012,13 +1012,13 @@
1012	1012
1013	1013	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”.
1014	1014
1015		-=== 7.5.1 Subscription Logical Class Diagram ===
	1015	+===== {{id name="_Toc90827"/}}7.5.1 Subscription Logical Class Diagram =====
1016	1016
1017	1017	[[image:SDMX 3.1 Section 5_en_1433df5d.jpg||height="680" width="587"]]
1018	1018
1019	1019	**Figure 19: Logical Class Diagram of the Subscription**
1020	1020
1021		-=== 7.5.2 Subscription Information ===
	1021	+===== {{id name="_Toc90828"/}}7.5.2 Subscription Information =====
1022	1022
1023	1023	Regardless of the type of registry/repository events being observed, a subscription always contains:
1024	1024
...	...	@@ -1027,16 +1027,18 @@
1027	1027	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.
1028	1028	1. A selector which specifies which type of events are of interest. The set of event types is:
1029	1029
	1030	+:
	1031	+::
	1032	+
1030	1030	(((
1031		-(% style="width:1061.83px" %)
1032		-|**Event Type**|(% style="width:660px" %)**Comment**
1033		-|STRUCTURAL_REPOSITORY_EVENTS|(% style="width:660px" %)Life-cycle changes to Maintainable Artefacts in the structural metadata repository.
1034		-|DATA_REGISTRATION_EVENTS|(% style="width:660px" %)Whenever a published dataset is registered. This can be either a SDMXML data file or an SDMX conformant database.
1035		-|METADATA_REGISTRATION_EVENTS|(% style="width:660px" %)Whenever a published metadataset is registered. This can be either a SDMXML reference metadata file or an SDMX conformant database.
1036		-|ALL_EVENTS|(% style="width:660px" %)All events of the specified EventType
	1034	+|**Event Type**|**Comment**
	1035	+|STRUCTURAL_REPOSITORY_EVENTS|Life-cycle changes to Maintainable Artefacts in the structural metadata repository.
	1036	+|DATA_REGISTRATION_EVENTS|Whenever a published dataset is registered. This can be either a SDMXML data file or an SDMX conformant database.
	1037	+|METADATA_REGISTRATION_EVENTS|Whenever a published metadataset is registered. This can be either a SDMXML reference metadata file or an SDMX conformant database.
	1038	+|ALL_EVENTS|All events of the specified EventType
1037	1037	)))
1038	1038
1039		-=== 7.5.3 Wildcard Facility ===
	1041	+===== {{id name="_Toc90829"/}}7.5.3 Wildcard Facility =====
1040	1040
1041	1041	Subscription notification supports wildcarded identifier components URNs, which are identifiers which have some or all of their component parts replaced by the wildcard character `*`. Identifier components comprise:
1042	1042
...	...	@@ -1092,29 +1092,30 @@
1092	1092
1093	1093	The complete SDMX versioning syntax can be found in the SDMX Standards Section 6 “Technical Notes”, paragraph “4.3 Versioning”.
1094	1094
1095		-=== 7.5.4 Structural Repository Events ===
	1097	+===== {{id name="_Toc90830"/}}7.5.4 Structural Repository Events =====
1096	1096
1097	1097	Whenever a maintainable artefact (data structure definition, concept scheme, codelist, metadata structure definition, category scheme, etc.) is added to, deleted from, or modified in the structural metadata repository, a structural metadata event is triggered. Subscriptions may be set up to monitor all such events, or focus on specific artefacts such as a Data Structure Definition.
1098	1098
1099		-=== 7.5.5 Registration Events ===
	1101	+===== {{id name="_Toc90831"/}}7.5.5 Registration Events =====
1100	1100
1101	1101	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:
1102	1102
	1105	+:
	1106	+
1103	1103	(((
1104		-(% style="width:1082.83px" %)
1105		-|(% style="width:230px" %)**Selector**|(% style="width:850px" %)**Comment**
1106		-|(% style="width:230px" %)DataProvider|(% style="width:850px" %)Any datasets registered by the specified dataprovider will activate the notification.
1107		-|(% style="width:230px" %)ProvisionAgreement|(% style="width:850px" %)Any datasets for the agreement will activate the notification.
1108		-|(% style="width:230px" %)Dataflow|(% style="width:850px" %)Any datasets for the specified dataflow will activate the notification.
1109		-|(% style="width:230px" %)DataStructureDefinition|(% style="width:850px" %)Any datasets for those dataflows that are based on the specified Data Structure Definition will activate the notification
1110		-|(% style="width:230px" %)Category|(% style="width:850px" %)Any datasets registered for those dataflows, provision agreements that are categorised by the category.
	1108	+|**Selector**|**Comment**
	1109	+|DataProvider|Any datasets registered by the specified dataprovider will activate the notification.
	1110	+|ProvisionAgreement|Any datasets for the agreement will activate the notification.
	1111	+|Dataflow|Any datasets for the specified dataflow will activate the notification.
	1112	+|DataStructureDefinition|Any datasets for those dataflows that are based on the specified Data Structure Definition will activate the notification
	1113	+|Category|Any datasets registered for those dataflows, provision agreements that are categorised by the category.
1111	1111	)))
1112	1112
1113	1113	The event will also capture the semantic of the registration: deletion or replacement of an existing registration or a new registration.
1114	1114
1115		-== 7.6 Notification ==
	1118	+== {{id name="_Toc90832"/}}7.6 Notification ==
1116	1116
1117		-=== 7.6.1 Logical Class Diagram ===
	1120	+==== {{id name="_Toc90833"/}}7.6.1 Logical Class Diagram ====
1118	1118
1119	1119	[[image:SDMX 3.1 Section 5_en_8bc1b889.jpg||height="379" width="579"]]
1120	1120
...	...	@@ -1131,11 +1131,11 @@
1131	1131
1132	1132	Additionally, supplementary information may be contained in the notification as detailed below.
1133	1133
1134		-=== 7.6.2 Structural Event Component ===
	1137	+==== {{id name="_Toc90834"/}}7.6.2 Structural Event Component ====
1135	1135
1136	1136	The notification will contain the MaintainableArtefact that triggered the event in a form similar to the SDMX-ML structural message (using elements from that namespace).
1137	1137
1138		-=== 7.6.3 Registration Event Component ===
	1141	+==== {{id name="_Toc90835"/}}7.6.3 Registration Event Component ====
1139	1139
1140	1140	The notification will contain the Registration.
1141	1141