Skip to Content
Last modified by Helena on 2025/09/10 11:19
From version 5.1
edited by Helena
on 2025/05/21 15:57
Change comment: There is no comment for this version
To version 9.2
edited by Helena
on 2025/05/23 12:58
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.
... ... @@ -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"]]
469 +[[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// =====
483 +(% class="wikigeneratedid" id="HCaseRulesforURN" %)
484 +//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  
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