Skip to Content
Last modified by Helena on 2025/09/10 11:19
From version 3.6
edited by Helena
on 2025/05/21 15:49
Change comment: There is no comment for this version
To version 9.3
edited by Helena
on 2025/05/23 13:00
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  
... ... @@ -427,6 +427,8 @@
427 427  
428 428  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.
429 429  
430 +[[image:1747994320263-112.png]]
431 +
430 430  **Figure 6: Agency Scheme Model**
431 431  
432 432  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.
... ... @@ -448,8 +448,7 @@
448 448  
449 449  [[image:1747824123012-527.jpeg]]
450 450  
451 -*
452 -** Figure 7: Example of Hierarchic Structure of Agencies
453 +**Figure 7: Example of Hierarchic Structure of Agencies**
453 453  
454 454  The following organizations maintain an Agency Scheme.
455 455  
... ... @@ -464,7 +464,7 @@
464 464  
465 465  An example of this is shown in the XML snippet below.
466 466  
467 -[[image:1747824123013-196.jpeg||height="309" width="446"]]
468 +[[image:1747832400104-286.png]]
468 468  
469 469  **Figure 8: Example Showing Use of Agency Identifiers**
470 470  
... ... @@ -478,7 +478,8 @@
478 478  
479 479  ==== 6.2.2.2 URN Structure ====
480 480  
481 -===== //Case Rules for URN// =====
482 +(% class="wikigeneratedid" id="HCaseRulesforURN" %)
483 +//Case Rules for URN//
482 482  
483 483  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.
484 484  
... ... @@ -869,9 +869,7 @@
869 869  ReportingTaxonomyMap
870 870  )))|structureSetAgencyId: structureSetId(version). reportingTaxonomyMapId|SDMX:BOP_STRUCTURES(1.0).TAXMAP
871 871  |(((
872 -Reporting
873 -
874 -CategoryMap
874 +ReportingCategoryMap
875 875  )))|(((
876 876  structureSetAgencyId: structureSetId(version).
877 877  reportngCategoryId
... ... @@ -924,13 +924,11 @@
924 924  |RulesetScheme|rulesetSchemeAgencyId rulesetSchemeId(version)|ECB:RULESET_23(1.0)
925 925  |Ruleset|rulesetSchemeAgencyId rulesetSchemeId(version) rulesetId|ECB:RULESET_23(1.0).SET111
926 926  |(((
927 -UserDefined
928 -
929 -OperatorScheme
927 +UserDefinedOperatorScheme
930 930  )))|userDefinedOperatorSchemeAgencyId userDefinedOperatorSchemeId(version)|ECB:OS_CALC(1.2)
931 931  |UserDefined Operator|userDefinedOperatorSchemeAgencyId userDefinedOperatorSchemeId(version) usserDefinedOperatorId|ECB:OS_CALC(1.2).OS267
932 932  
933 -7**Table 3: Table of identification components for SDMX Identifiable Artefacts**
931 +**Table 3: Table of identification components for SDMX Identifiable Artefacts**
934 934  
935 935  = 7 Implementation Notes =
936 936  
... ... @@ -1231,11 +1231,11 @@
1231 1231  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.
1232 1232  1. A selector which specifies which type of events are of interest. The set of event types is:
1233 1233  
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
1232 +|(% style="width:319px" %)**Event Type**|(% style="width:1553px" %)**Comment**
1233 +|(% style="width:319px" %)STRUCTURAL_REPOSITORY_EVENTS|(% style="width:1553px" %)Life-cycle changes to Maintainable Artefacts in the structural metadata repository.
1234 +|(% 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.
1235 +|(% 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.
1236 +|(% style="width:319px" %)ALL_EVENTS|(% style="width:1553px" %)All events of the specified EventType
1239 1239  
1240 1240  === 7.5.3 Wildcard Facility ===
1241 1241  
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