Skip to Content
Last modified by Helena on 2025/09/10 11:19
From version 9.1
edited by Helena
on 2025/05/23 01:07
Change comment: There is no comment for this version
To version 3.6
edited by Helena
on 2025/05/21 15:49
Change comment: There is no comment for this version

Summary

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
Content
... ... @@ -326,7 +326,7 @@
326 326  Subscription management involves a user submitting a subscription request which contains:
327 327  
328 328  * 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).
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)
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)
330 330  * request for a list of submitted subscriptions
331 331  * deletion of a subscription
332 332  
... ... @@ -448,7 +448,7 @@
448 448  
449 449  [[image:1747824123012-527.jpeg]]
450 450  
451 -*
451 +*
452 452  ** Figure 7: Example of Hierarchic Structure of Agencies
453 453  
454 454  The following organizations maintain an Agency Scheme.
... ... @@ -464,7 +464,7 @@
464 464  
465 465  An example of this is shown in the XML snippet below.
466 466  
467 -[[image:1747832400104-286.png]]
467 +[[image:1747824123013-196.jpeg||height="309" width="446"]]
468 468  
469 469  **Figure 8: Example Showing Use of Agency Identifiers**
470 470  
... ... @@ -478,8 +478,7 @@
478 478  
479 479  ==== 6.2.2.2 URN Structure ====
480 480  
481 -(% class="wikigeneratedid" id="HCaseRulesforURN" %)
482 -//Case Rules for URN//
481 +===== //Case Rules for URN// =====
483 483  
484 484  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.
485 485  
... ... @@ -870,7 +870,9 @@
870 870  ReportingTaxonomyMap
871 871  )))|structureSetAgencyId: structureSetId(version). reportingTaxonomyMapId|SDMX:BOP_STRUCTURES(1.0).TAXMAP
872 872  |(((
873 -ReportingCategoryMap
872 +Reporting
873 +
874 +CategoryMap
874 874  )))|(((
875 875  structureSetAgencyId: structureSetId(version).
876 876  reportngCategoryId
... ... @@ -923,11 +923,13 @@
923 923  |RulesetScheme|rulesetSchemeAgencyId rulesetSchemeId(version)|ECB:RULESET_23(1.0)
924 924  |Ruleset|rulesetSchemeAgencyId rulesetSchemeId(version) rulesetId|ECB:RULESET_23(1.0).SET111
925 925  |(((
926 -UserDefinedOperatorScheme
927 +UserDefined
928 +
929 +OperatorScheme
927 927  )))|userDefinedOperatorSchemeAgencyId userDefinedOperatorSchemeId(version)|ECB:OS_CALC(1.2)
928 928  |UserDefined Operator|userDefinedOperatorSchemeAgencyId userDefinedOperatorSchemeId(version) usserDefinedOperatorId|ECB:OS_CALC(1.2).OS267
929 929  
930 -**Table 3: Table of identification components for SDMX Identifiable Artefacts**
933 +7**Table 3: Table of identification components for SDMX Identifiable Artefacts**
931 931  
932 932  = 7 Implementation Notes =
933 933  
... ... @@ -1228,11 +1228,11 @@
1228 1228  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.
1229 1229  1. A selector which specifies which type of events are of interest. The set of event types is:
1230 1230  
1231 -|(% style="width:319px" %)**Event Type**|(% style="width:1553px" %)**Comment**
1232 -|(% style="width:319px" %)STRUCTURAL_REPOSITORY_EVENTS|(% style="width:1553px" %)Life-cycle changes to Maintainable Artefacts in the structural metadata repository.
1233 -|(% style="width:319px" %)DATA_REGISTRATION_EVENTS|(% style="width:1553px" %)Whenever a published dataset is registered. This can be either a SDMXML data file or an SDMX conformant database.
1234 -|(% style="width:319px" %)METADATA_REGISTRATION_EVENTS|(% style="width:1553px" %)Whenever a published metadataset is registered. This can be either a SDMXML reference metadata file or an SDMX conformant database.
1235 -|(% style="width:319px" %)ALL_EVENTS|(% style="width:1553px" %)All events of the specified EventType
1234 +|(% style="width:327px" %)**Event Type**|(% style="width:1545px" %)**Comment**
1235 +|(% style="width:327px" %)STRUCTURAL_REPOSITORY_EVENTS|(% style="width:1545px" %)Life-cycle changes to Maintainable Artefacts in the structural metadata repository.
1236 +|(% style="width:327px" %)DATA_REGISTRATION_EVENTS|(% style="width:1545px" %)Whenever a published dataset is registered. This can be either a SDMXML data file or an SDMX conformant database.
1237 +|(% style="width:327px" %)METADATA_REGISTRATION_EVENTS|(% style="width:1545px" %)Whenever a published metadataset is registered. This can be either a SDMXML reference metadata file or an SDMX conformant database.
1238 +|(% style="width:327px" %)ALL_EVENTS|(% style="width:1545px" %)All events of the specified EventType
1236 1236  
1237 1237  === 7.5.3 Wildcard Facility ===
1238 1238  
1747832400104-286.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -172.3 KB
Content