Last modified by Helena on 2025/09/10 11:19
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 10 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -SDMX 2.1 Standards. Section .5. Registry Specification – Logical Interfaces1 +SDMX 2.1 Standards. Section 5. Registry Specification – Logical Interfaces - Content
-
... ... @@ -4,10 +4,11 @@ 4 4 5 5 **Revision History** 6 6 7 -|**Revision**|**Date**|**Contents** 8 -| |April 2011|Initial release 9 -|1.0|July 2011|Rectification of problems of the specifications dated April 2011 10 -|2.0|July 2020|Addition of VTL (Validation and Transformation Language) package, maintainable artefacts, nameable artefacts to 5.2.3, 6.2.2, 6.2.3, 6.2.4, 7.1.1 7 +(% style="width:833.294px" %) 8 +|(% style="width:122px" %)**Revision**|(% style="width:126px" %)**Date**|(% style="width:581px" %)**Contents** 9 +|(% style="width:122px" %) |(% style="width:126px" %)April 2011|(% style="width:581px" %)Initial release 10 +|(% style="width:122px" %)1.0|(% style="width:126px" %)July 2011|(% style="width:581px" %)Rectification of problems of the specifications dated April 2011 11 +|(% style="width:122px" %)2.0|(% style="width:126px" %)July 2020|(% style="width:581px" %)Addition of VTL (Validation and Transformation Language) package, maintainable artefacts, nameable artefacts to 5.2.3, 6.2.2, 6.2.3, 6.2.4, 7.1.1 11 11 12 12 **Corrigendum** 13 13 ... ... @@ -288,27 +288,22 @@ 288 288 * that a queryable data source exists - this would necessitate the registration service querying the service to determine its existence 289 289 * that a simple data source exists (i.e. a file accessible at a URL) 290 290 * that the correct Data Structure Definition or Metadata Structure Definition is used by the registered data that the components (Dimensions, Attributes, Measures, Identifier Components etc.) are consistent with the Data Structure Definition or Metadata Structure Definition 291 -* that the valid representations of the concepts to which these components382correspond conform to the definition in the Data Structure Definition or Metadata Structure Definition292 +* 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 292 292 293 - 3The Registration has an action attribute which takes one of the following values:294 +The Registration has an action attribute which takes one of the following values: 294 294 295 -|(% style="width:249px" %)((( 296 -**Action Attribute Value** 297 -)))|(% style="width:1622px" %)**Behaviour** 298 -|(% style="width:249px" %)Append|(% style="width:1622px" %)Add this registration to the registry 299 -|(% style="width:249px" %)Replace|(% style="width:1622px" %)Replace the existing Registration with this Registration identified by the id in the Registration of the Submit Registration Request 300 -|(% style="width:249px" %)Delete|(% style="width:1622px" %)Delete the existing Registration identified by the id in the Registration of the Submit Registration Request 296 +|(% style="width:219px" %)**Action Attribute Value**|(% style="width:1652px" %)**Behaviour** 297 +|(% style="width:219px" %)Append|(% style="width:1652px" %)Add this registration to the registry 298 +|(% style="width:219px" %)Replace|(% style="width:1652px" %)Replace the existing Registration with this Registration identified by the id in the Registration of the Submit Registration Request 299 +|(% style="width:219px" %)Delete|(% style="width:1652px" %)Delete the existing Registration identified by the id in the Registration of the Submit Registration Request 301 301 302 302 The Registration has three Boolean attributes which may be present to determine how an SDMX compliant Dataset or Metadata Set indexing application must index the Datasets or Metadata Set upon registration. The indexing application behaviour is as follows: 303 303 304 -|**Boolean Attribute**|**Behaviour if Value is “true”** 305 -|indexTimeSeries|A compliant indexing application must index all the time series keys (for a Dataset registration) or metadata target values (for a Metadata Set registration) 306 -|indexDataSet|((( 307 -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. 308 - 303 +|(% style="width:228px" %)**Boolean Attribute**|(% style="width:1644px" %)**Behaviour if Value is “true”** 304 +|(% style="width:228px" %)indexTimeSeries|(% style="width:1644px" %)A compliant indexing application must index all the time series keys (for a Dataset registration) or metadata target values (for a Metadata Set registration) 305 +|(% style="width:228px" %)indexDataSet|(% style="width:1644px" %)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. 309 309 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 310 -))) 311 -|indexReportingPeriod|A compliant indexing application must index the time period range(s) for which data are present in the Dataset or Metadata Set 307 +|(% style="width:228px" %)indexReportingPeriod|(% style="width:1644px" %)A compliant indexing application must index the time period range(s) for which data are present in the Dataset or Metadata Set 312 312 313 313 === 5.2.5 Data and Reference Metadata Discovery === 314 314 ... ... @@ -330,7 +330,7 @@ 330 330 Subscription management involves a user submitting a subscription request which contains: 331 331 332 332 * 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). 333 -* 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) 334 334 * request for a list of submitted subscriptions 335 335 * deletion of a subscription 336 336 ... ... @@ -340,8 +340,8 @@ 340 340 341 341 The following table defines the behaviour of the SDMX Registry for the various Registry Interface messages. 342 342 343 -|(% style="width: 143px" %)**Interface**|(% style="width:1729px" %)**Behaviour**344 -|(% style="width: 143px" %)All|(% style="width:1729px" %)(((339 +|(% style="width:227px" %)**Interface**|(% style="width:1644px" %)**Behaviour** 340 +|(% style="width:227px" %)All|(% style="width:1644px" %)((( 345 345 1) If the action is set to “replace” then the entire contents of the existing maintainable object in the Registry MUST be replaced by the object submitted, unless the final attribute is set to “true” in which case the only changes that are allowed are to the following constructs: 346 346 347 347 * Name – this applies to the Maintainable object and its contained elements, such a Code in a Code list. ... ... @@ -355,7 +355,6 @@ 355 355 * isExternalReference 356 356 357 357 2) 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. 358 - 359 359 3) If the action is set to “delete” then the Registry MUST verify that the object can deleted. In order to qualify for deletion the object must: 360 360 361 361 а) Not have the final attribute set to “true” ... ... @@ -362,14 +362,12 @@ 362 362 b) Not be referenced from any other object in the Registry. 363 363 364 364 4) The version rules in the SDMX Schema documentation MUST be obeyed. 365 - 366 366 5) The specific rules for the elements and attributes documented in the SDMX Schema MUST be obeyed. 367 367 ))) 368 -|(% style="width: 143px" %)SubmitStructureRequest|(% style="width:1729px" %)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.369 -|(% style="width: 143px" %)SubmitProvisioningRequest|(% style="width:1729px" %)No additional behaviour.370 -|(% style="width: 143px" %)Submit Registration Request|(% style="width:1729px" %)(((362 +|(% style="width:227px" %)SubmitStructureRequest|(% style="width:1644px" %)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. 363 +|(% style="width:227px" %)SubmitProvisioningRequest|(% style="width:1644px" %)No additional behaviour. 364 +|(% style="width:227px" %)Submit Registration Request|(% style="width:1644px" %)((( 371 371 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. 372 - 373 373 For a queryable datasource the Registry MAY validate that the source exists and can accept an SDMX-ML data query. 374 374 ))) 375 375 ... ... @@ -386,6 +386,8 @@ 386 386 387 387 === 6.1.1 Identification, Naming, Versioning, and Maintenance Model === 388 388 382 +[[image:1747824504225-229.png]] 383 + 389 389 **Figure 5: Class diagram of fundamental artefacts in the SDMX-IM** 390 390 391 391 The table below shows the identification and related data attributes to be stored in a registry for objects that are one of: ... ... @@ -396,38 +396,34 @@ 396 396 * Versionable 397 397 * Maintainable 398 398 399 -|**Object Type**|**Data Attributes**|**Status**|**Data type**|**Notes** 400 -|Annotable|AnnotationTitle|C|string| 401 -| |AnnotationType|C|string| 402 -| |AnnotationURN|C|string| 403 -| |((( 404 -AnnotationText in the form of 394 +(% style="width:935.294px" %) 395 +|**Object Type**|(% style="width:244px" %)**Data Attributes**|(% style="width:99px" %)**Status**|**Data type**|(% style="width:389px" %)**Notes** 396 +|Annotable|(% style="width:244px" %)AnnotationTitle|(% style="width:99px" %)C|string|(% style="width:389px" %) 397 +| |(% style="width:244px" %)AnnotationType|(% style="width:99px" %)C|string|(% style="width:389px" %) 398 +| |(% style="width:244px" %)AnnotationURN|(% style="width:99px" %)C|string|(% style="width:389px" %) 399 +| |(% style="width:244px" %)((( 400 +AnnotationText in the form of International String 401 +)))|(% style="width:99px" %)C| |(% style="width:389px" %)This can have languagespecific variants. 402 +|Identifiable|(% style="width:244px" %)all content as for Annotable plus|(% style="width:99px" %) | |(% style="width:389px" %) 403 +| |(% style="width:244px" %)id|(% style="width:99px" %)M|string|(% style="width:389px" %) 404 +| |(% style="width:244px" %)uri|(% style="width:99px" %)C|string|(% style="width:389px" %) 405 +| |(% style="width:244px" %)urn|(% style="width:99px" %)C|string|(% style="width:389px" %)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. 406 +|Nameable|(% style="width:244px" %)all content as for Identifiable plus|(% style="width:99px" %) | |(% style="width:389px" %) 407 +| |(% style="width:244px" %)Name in the form of International String|(% style="width:99px" %)M|string|(% style="width:389px" %)This can have languagespecific variants. 408 +| |(% style="width:244px" %)((( 409 +Description in the form of International String 410 +)))|(% style="width:99px" %)C|string|(% style="width:389px" %)This can have languagespecific variants. 411 +|Versionable|(% style="width:244px" %)All content as for Identifiable plus|(% style="width:99px" %) | |(% style="width:389px" %) 412 +| |(% style="width:244px" %)version|(% style="width:99px" %)C|string|(% style="width:389px" %)This is the version number. If not present the default is 1.0 413 +| |(% style="width:244px" %)validFrom|(% style="width:99px" %)C|Date/time|(% style="width:389px" %) 414 +| |(% style="width:244px" %)validTo|(% style="width:99px" %)C|Date/time|(% style="width:389px" %) 415 +|Maintainable|(% style="width:244px" %)All content as for Versionable plus|(% style="width:99px" %) | |(% style="width:389px" %) 416 +| |(% style="width:244px" %)final|(% style="width:99px" %) |boolean|(% style="width:389px" %)Value of “true” indicates that this is a final specification and it cannot be changed except as a new version. Note that providing a “final’ object is not referenced from another object then it may be deleted. 417 +| |(% style="width:244px" %)isExternalReference|(% style="width:99px" %)C|boolean|(% style="width:389px" %)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 structureURI, each of which must return a valid SDMX-ML file. 418 +| |(% style="width:244px" %)serviceURL|(% style="width:99px" %)C|string|(% style="width:389px" %)The url of the service that can be queried for this resource 419 +| |(% style="width:244px" %)structureURL|(% style="width:99px" %)C|string|(% style="width:389px" %)The url of the resource. 420 +| |(% style="width:244px" %)(Maintenance) agencyId|(% style="width:99px" %)M|string|(% style="width:389px" %)The object must be linked to a maintenance agency. 405 405 406 -International String 407 -)))|C| |This can have languagespecific variants. 408 -| | | | | 409 -|Identifiable|all content as for Annotable plus| | | 410 -| |id|M|string| 411 -| |uri|C|string| 412 -| |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. 413 -|Nameable|all content as for Identifiable plus| | | 414 -| |Name in the form of International String|M|string|This can have languagespecific variants. 415 -| |((( 416 -Description in the form of International 417 - 418 -String 419 -)))|C|string|This can have languagespecific variants. 420 -|Versionable|All content as for Identifiable plus| | | 421 -| |version|C|string|This is the version number. If not present the default is 1.0 422 -| |validFrom|C|Date/time| 423 -| |validTo|C|Date/time| 424 -|Maintainable|All content as for Versionable plus| | | 425 -| |final| |boolean|Value of “true” indicates that this is a final specification and it cannot be changed except as a new version. Note that providing a “final’ object is not referenced from another object then it may be deleted. 426 -| |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 structureURI, each of which must return a valid SDMX-ML file. 427 -| |serviceURL|C|string|The url of the service that can be queried for this resource 428 -| |structureURL|C|string|The url of the resource. 429 -| |(Maintenance) agencyId|M|string|The object must be linked to a maintenance agency. 430 - 431 431 **Table 1: Common Attributes of Object Types** 432 432 433 433 == 6.2 Unique identification of SDMX objects == ... ... @@ -457,7 +457,8 @@ 457 457 458 458 [[image:1747824123012-527.jpeg]] 459 459 460 -==== Figure 7: Example of Hierarchic Structure of Agencies ==== 451 +* 452 +** Figure 7: Example of Hierarchic Structure of Agencies 461 461 462 462 The following organizations maintain an Agency Scheme. 463 463 ... ... @@ -472,11 +472,10 @@ 472 472 473 473 An example of this is shown in the XML snippet below. 474 474 467 +[[image:1747832400104-286.png]] 475 475 476 - [[image:1747824123013-196.jpeg]]469 +**Figure 8: Example Showing Use of Agency Identifiers** 477 477 478 -==== Figure 8: Example Showing Use of Agency Identifiers ==== 479 - 480 480 Each of these maintenance agencies has an identical Code list with the Id CL_BOP. However, each is uniquely identified by means of the hierarchic agency structure. 481 481 482 482 === 6.2.2 Universal Resource Name (URN) === ... ... @@ -487,13 +487,14 @@ 487 487 488 488 ==== 6.2.2.2 URN Structure ==== 489 489 490 -===== //Case Rules for URN// ===== 481 +(% class="wikigeneratedid" id="HCaseRulesforURN" %) 482 +//Case Rules for URN// 491 491 492 492 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. 493 493 494 494 The generic structure of the URN is as follows: 495 495 496 -SDMXprefix.SDMX-IM-package-name.class-name=agencyid:maintainedobject-id(maintainedobject-version).*containerobject-id.object-id 488 +>SDMXprefix.SDMX-IM-package-name.class-name=agencyid:maintainedobject-id(maintainedobject-version).*containerobject-id.object-id 497 497 498 498 ~* this can repeat and may not be present (see explanation below) 499 499 ... ... @@ -505,7 +505,7 @@ 505 505 506 506 In the explanation below the actual object that is the target of the URN is called the **//actual object//**. 507 507 508 -**SDMXPrefix:** urn:sdmx:org. 500 +**SDMXPrefix:** urn:sdmx:org. 509 509 510 510 **SDMX-IM package name:** sdmx.infomodel.package= 511 511 ... ... @@ -515,10 +515,8 @@ 515 515 516 516 **(maintainable-object-version)** is the version of the maintainable object and is enclosed in round brackets (). It will always be present. 517 517 518 -**container-object-id** is the identifier of an intermediary object that contains the actual object which the URN is identifying. It is not mandatory as many actual objects do not have an intermediary container object. For instance, a Code is in a maintained object (Code List) and has no intermediary container object, whereas a Metadata Attribute has an intermediary container object (Report Structure) and may have an intermediary container object which is its parent Metadata Attribute. For this reason the container object id may repeat, with each repetition identifying the object at the next-lower level in its hierarchy. Note that if there is only a single containing object in the model then it is NOT included in the URN structure. This applies to Attribute Descriptor, Dimension Descriptor, and Measure Descriptor where there can be only one such object and this object has a fixed id. Therefore, whilst each of these has a 510 +**container-object-id** is the identifier of an intermediary object that contains the actual object which the URN is identifying. It is not mandatory as many actual objects do not have an intermediary container object. For instance, a Code is in a maintained object (Code List) and has no intermediary container object, whereas a Metadata Attribute has an intermediary container object (Report Structure) and may have an intermediary container object which is its parent Metadata Attribute. For this reason the container object id may repeat, with each repetition identifying the object at the next-lower level in its hierarchy. Note that if there is only a single containing object in the model then it is NOT included in the URN structure. This applies to Attribute Descriptor, Dimension Descriptor, and Measure Descriptor where there can be only one such object and this object has a fixed id. Therefore, whilst each of these has a URN, the id of the Attribute Descriptor, Dimension Descriptor, and Measure Descriptor is not included when the actual object is a Data Attribute or a Dimension/Measure Dimension/ Time Dimension, or a Measure. 519 519 520 -URN, the id of the Attribute Descriptor, Dimension Descriptor, and Measure Descriptor is not included when the actual object is a Data Attribute or a Dimension/Measure Dimension/ Time Dimension, or a Measure. 521 - 522 522 Note that although a Code can have a parent Code and a Concept can have a parent Concept these are maintained in a flat structure and therefore do not have a container-object-id. 523 523 524 524 For example the sequence is agency:DSDid(version).DimensionId and not agency:DSDid(version).DimensionDescriptorId.DimensionId. ... ... @@ -525,58 +525,57 @@ 525 525 526 526 **object-id** is the identifier of the actual object unless the actual object is a maintainable object. If present it is always the last id and is not followed by any other character. 527 527 528 -===== //Generic Examples of the URN Structure// ===== 518 +===== __**//Generic Examples of the URN Structure//**__ ===== 529 529 520 +__Actual object is a maintainable__ 530 530 531 - Actualobject isable522 +> SDMXPrefix.SDMX-IM package name.classname=agency id:maintained-object-id(version) 532 532 533 - SDMXPrefix.SDMX-IM packagename.classname=agencyid:maintained-object-id(version)524 +__Actual object is contained in a maintained object with no intermediate containing object__ 534 534 535 - Actualobjectiscontained inamaintainedwith no intermediate containingobject526 +> SDMXPrefix.SDMX-IM package name.classname=agency id:maintained-object-id(version).object-id 536 536 537 - SDMXPrefix.SDMX-IM packagename.classname=agencyid:maintained-object-id(version).object-id528 +__Actual object is contained in a maintained object with an intermediate containing object__ 538 538 539 - Actualobjectiscontainedinaintained object withanintermediate containingobject530 +> SDMXPrefix.SDMX-IM package name.classname=agency 540 540 541 -SDMXPrefix.SDMX-IM package name.classname=agency 542 - 543 543 id:maintained-object-id(version).contained-object-id.object-id 544 544 545 -Actual object is contained in a maintained object with no intermediate containing object but the object type itself is hierarchical 534 +__Actual object is contained in a maintained object with no intermediate containing object but the object type itself is hierarchical__ 546 546 547 547 In this case the object id may not be unique in itself but only within the context of the hierarchy. In the general syntax of the URN all intermediary objects in the structure (with the exception, of course, of the maintained object) are shown as a contained object. An example here would be a Category in a Category Scheme. The Category is hierarchical and all intermediate Categories are shown as a contained object. The example below shows the generic structure for Category Scheme/Category/Category 548 548 549 -SDMXPrefix.SDMX-IM package name.classname=agency id:maintained-object-id(version).contained-object-id.object-id 538 +> SDMXPrefix.SDMX-IM package name.classname=agency id:maintained-object-id(version).contained-object-id.object-id 550 550 551 -Actual object is contained in a maintained object with an intermediate containing object and the object type itself is hierarchical 540 +__Actual object is contained in a maintained object with an intermediate containing object and the object type itself is hierarchical__ 552 552 553 553 In this case the generic syntax is the same as for the example above as the parent object is regarded as a containing object, even if it is of the same type. An example here is a Metadata Attribute where the contained objects are Report Structure (first contained object id) and Metadata Attribute (subsequent contained object Ids). The example below shows the generic structure for MSD/Report Structure/Metadata Attribute/Metadata Attribute 554 554 555 -SDMXPrefix.SDMX-IM package name.classname=agency id:maintained-object-id(version).contained-object-id. contained-object-id contained-object-id.object-id 544 +> SDMXPrefix.SDMX-IM package name.classname=agency id:maintained-object-id(version).contained-object-id. contained-object-id contained-object-id.object-id 556 556 557 -===== //Concrete Examples of the URN Structure// ===== 546 +===== __**//Concrete Examples of the URN Structure//**__ ===== 558 558 559 559 The Data Structure Definition CRED_EXT_DEBT version 1.0 maintained by the top level Agency TFFS would have the URN: 560 560 561 -urn:sdmx:org.sdmx.infomodel.datastructure.DataStucture=TFFS:CRED_EXT_ DEBT(1.0) 550 +> urn:sdmx:org.sdmx.infomodel.datastructure.DataStucture=TFFS:CRED_EXT_ DEBT(1.0) 562 562 563 563 The URN for a code for Argentina maintained by ISO in the code list CL_3166A2 version 1.0 would be: 564 564 565 -urn:sdmx:org.sdmx.infomodel.codelist.Code=ISO:CL_3166A2(1.0).AR 554 +> urn:sdmx:org.sdmx.infomodel.codelist.Code=ISO:CL_3166A2(1.0).AR 566 566 567 567 The URN for a category (id of 1) which has parent category (id of 2) maintained by SDMX in the category scheme SUBJECT_MATTER_DOMAINS version 1.0 would be: 568 568 569 -urn:sdmx:org.sdmx.infomodel.categoryscheme.Category=SDMX:SUBJE CT_MATTER_DOMAINS(1.0).1.2 558 +> urn:sdmx:org.sdmx.infomodel.categoryscheme.Category=SDMX:SUBJE CT_MATTER_DOMAINS(1.0).1.2 570 570 571 571 The URN for a Metadata Attribute maintained by SDMX in the MSD CONTACT_METADATA version 1.0 in the Report Structure CONTACT_REPORT where the hierarchy of the Metadata Attribute is 572 572 573 573 CONTACT_DETAILS/CONTACT_NAME would be: 574 574 575 -urn:sdmx:org.sdmx.infomodel.metadatastructure.MetadataAttribut e=SDMX:CONTACT_METADATA(1.0).CONTACT_REPORT.CONTACT_DETAILS.CO NTACT_NAME 564 +> urn:sdmx:org.sdmx.infomodel.metadatastructure.MetadataAttribut e=SDMX:CONTACT_METADATA(1.0).CONTACT_REPORT.CONTACT_DETAILS.CO NTACT_NAME 576 576 577 577 The TFFS defines ABC as a sub Agency of TFFS then the URN of a Dataflow maintained by ABC and identified as EXTERNAL_DEBT version 1.0 would be: 578 578 579 -urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=TFFS.ABC:EX 568 +> urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=TFFS.ABC:EX 580 580 581 581 TERNAL_DEBT(1.0) 582 582 ... ... @@ -591,112 +591,94 @@ 591 591 592 592 The table below lists all of the packages in the SDMX-IM together with the concrete classes that are in these packages and whose objects have a URN. 593 593 594 -|**Package**|((( 595 -**URN Classname (model classname** 596 - 597 -**where this is different)** 583 +|(% style="width:127px" %)**Package**|(% style="width:1745px" %)((( 584 +**URN Classname (model classname where this is different)** 598 598 ))) 599 -|base|Agency 600 -| |OrganisationUnitScheme 601 -| |AgencyScheme 602 -| |DataProviderScheme 603 -| |DataConsumerScheme 604 -| |OrganisationUnit 605 -| |DataProvider 606 -| |DataConsumer 607 -| | 608 -|datastructure|DataStructure (DataStructureDefinition) 609 -| |AttributeDescriptor 610 -| |DataAttribute 611 -| |GroupDimensionDescriptor 612 -| |DimensionDescriptor 613 -| |Dimension 614 -| |MeasureDimension 615 -| |TimeDimension 616 -| |MeasureDescriptor 617 -| |PrimaryMeasure 618 -| |Dataflow (DataflowDefinition) 619 -| | 620 -|metadatastructure|MetadataTarget 621 -| |DimensionDescriptorValueTarget 622 -| |IdentifiableObjectTarget 623 -| |ReportPeriodTarget 624 -| |DataSetTarget 625 -| |ReportStructure 626 -| |MetadataAttribute 627 -| |((( 586 +|(% style="width:127px" %)base|(% style="width:45px" %)Agency 587 +|(% style="width:127px" %) |(% style="width:45px" %)OrganisationUnitScheme 588 +|(% style="width:127px" %) |(% style="width:45px" %)AgencyScheme 589 +|(% style="width:127px" %) |(% style="width:45px" %)DataProviderScheme 590 +|(% style="width:127px" %) |(% style="width:45px" %)DataConsumerScheme 591 +|(% style="width:127px" %) |(% style="width:45px" %)OrganisationUnit 592 +|(% style="width:127px" %) |(% style="width:45px" %)DataProvider 593 +|(% style="width:127px" %) |(% style="width:45px" %)DataConsumer 594 +|(% style="width:127px" %)datastructure|(% style="width:45px" %)DataStructure (DataStructureDefinition) 595 +|(% style="width:127px" %) |(% style="width:45px" %)AttributeDescriptor 596 +|(% style="width:127px" %) |(% style="width:45px" %)DataAttribute 597 +|(% style="width:127px" %) |(% style="width:45px" %)GroupDimensionDescriptor 598 +|(% style="width:127px" %) |(% style="width:45px" %)DimensionDescriptor 599 +|(% style="width:127px" %) |(% style="width:45px" %)Dimension 600 +|(% style="width:127px" %) |(% style="width:45px" %)MeasureDimension 601 +|(% style="width:127px" %) |(% style="width:45px" %)TimeDimension 602 +|(% style="width:127px" %) |(% style="width:45px" %)MeasureDescriptor 603 +|(% style="width:127px" %) |(% style="width:45px" %)PrimaryMeasure 604 +|(% style="width:127px" %) |(% style="width:45px" %)Dataflow (DataflowDefinition) 605 +|(% style="width:127px" %)metadatastructure|(% style="width:45px" %)MetadataTarget 606 +|(% style="width:127px" %) |(% style="width:45px" %)DimensionDescriptorValueTarget 607 +|(% style="width:127px" %) |(% style="width:45px" %)IdentifiableObjectTarget 608 +|(% style="width:127px" %) |(% style="width:45px" %)ReportPeriodTarget 609 +|(% style="width:127px" %) |(% style="width:45px" %)DataSetTarget 610 +|(% style="width:127px" %) |(% style="width:45px" %)ReportStructure 611 +|(% style="width:127px" %) |(% style="width:45px" %)MetadataAttribute 612 +|(% style="width:127px" %) |(% style="width:45px" %)((( 628 628 MetadataStructure 629 629 630 630 (MetadataStructureDefinition) 631 631 ))) 632 -| |Metadataflow (MetadataflowDefinition) 633 -| | 634 -|process|Process 635 -| |ProcessStep 636 -| |Transition 637 -| | 638 -|registry|ProvisionAgreement 639 -| |AttachmentConstraint 640 -| |ContentConstraint 641 -| |Subscription 642 -| | 643 -|mapping|StructureMap 644 -| |StructureSet 645 -| |ComponentMap 646 -|**Package**|((( 647 -**URN Classname (model classname** 617 +|(% style="width:127px" %) |(% style="width:45px" %)Metadataflow (MetadataflowDefinition) 618 +|(% style="width:127px" %)process|(% style="width:45px" %)Process 619 +|(% style="width:127px" %) |(% style="width:45px" %)ProcessStep 620 +|(% style="width:127px" %) |(% style="width:45px" %)Transition 621 +|(% style="width:127px" %)registry|(% style="width:45px" %)ProvisionAgreement 622 +|(% style="width:127px" %) |(% style="width:45px" %)AttachmentConstraint 623 +|(% style="width:127px" %) |(% style="width:45px" %)ContentConstraint 624 +|(% style="width:127px" %) |(% style="width:45px" %)Subscription 625 +|(% style="width:127px" %)mapping|(% style="width:45px" %)StructureMap 626 +|(% style="width:127px" %) |(% style="width:45px" %)StructureSet 627 +|(% style="width:127px" %) |(% style="width:45px" %)ComponentMap 628 +|(% style="width:127px" %) |(% style="width:1745px" %)ConceptSchemeMap 629 +|(% style="width:127px" %) |(% style="width:1745px" %)OrganisationSchemeMap 630 +|(% style="width:127px" %) |(% style="width:1745px" %)CodelistMap 631 +|(% style="width:127px" %) |(% style="width:1745px" %)CategorySchemeMap 632 +|(% style="width:127px" %) |(% style="width:1745px" %)ReportingTaxonomyMap 633 +|(% style="width:127px" %) |(% style="width:1745px" %)ConceptMap 634 +|(% style="width:127px" %) |(% style="width:1745px" %)OrganisationMap 635 +|(% style="width:127px" %) |(% style="width:1745px" %)CodeMap 636 +|(% style="width:127px" %) |(% style="width:1745px" %)HybridCodelistMap 637 +|(% style="width:127px" %) |(% style="width:1745px" %)CategoryMap 638 +|(% style="width:127px" %) |(% style="width:1745px" %)HybridCodeMap 639 +|(% style="width:127px" %) |(% style="width:1745px" %)ReportingCategoryMap 640 +|(% style="width:127px" %)codelist|(% style="width:1745px" %)Codelist 641 +|(% style="width:127px" %) |(% style="width:1745px" %)HierarchicalCodelist 642 +|(% style="width:127px" %) |(% style="width:1745px" %)Hierarchy 643 +|(% style="width:127px" %) |(% style="width:1745px" %)Hierarchy 644 +|(% style="width:127px" %) |(% style="width:1745px" %)Code 645 +|(% style="width:127px" %) |(% style="width:1745px" %)HierarchicalCode 646 +|(% style="width:127px" %) |(% style="width:1745px" %)Level 647 +|(% style="width:127px" %)categoryscheme|(% style="width:1745px" %)CategoryScheme 648 +|(% style="width:127px" %) |(% style="width:1745px" %)Category 649 +|(% style="width:127px" %) |(% style="width:1745px" %)Categorisation 650 +|(% style="width:127px" %) |(% style="width:1745px" %)ReportingTaxonomy 651 +|(% style="width:127px" %) |(% style="width:1745px" %)ReportingCategory 652 +|(% style="width:127px" %)conceptscheme|(% style="width:1745px" %)ConceptScheme 653 +|(% style="width:127px" %) |(% style="width:1745px" %)Concept 654 +|(% style="width:127px" %)transformation|(% style="width:1745px" %)TransformationScheme 655 +|(% style="width:127px" %) |(% style="width:1745px" %)Transformation 656 +|(% style="width:127px" %) |(% style="width:1745px" %)CustomTypeScheme 657 +|(% style="width:127px" %) |(% style="width:1745px" %)CustomType 658 +|(% style="width:127px" %) |(% style="width:1745px" %)NamePersonalisationScheme 659 +|(% style="width:127px" %) |(% style="width:1745px" %)NamePersonalisation 660 +|(% style="width:127px" %) |(% style="width:1745px" %)VtlCodelistMapping 661 +|(% style="width:127px" %) |(% style="width:1745px" %)VtlConceptMapping 662 +|(% style="width:127px" %) |(% style="width:1745px" %)VtlDataflowMapping 663 +|(% style="width:127px" %) |(% style="width:1745px" %)VtlConceptSchemeMapping 664 +|(% style="width:127px" %) |(% style="width:1745px" %)RulesetScheme 665 +|(% style="width:127px" %) |(% style="width:1745px" %)Ruleset 666 +|(% style="width:127px" %) |(% style="width:1745px" %)UserDefinedOperatorScheme 667 +|(% style="width:127px" %) |(% style="width:1745px" %)UserDefinedOperator 648 648 649 -**where this is different)** 650 -))) 651 -| |ConceptSchemeMap 652 -| |OrganisationSchemeMap 653 -| |CodelistMap 654 -| |CategorySchemeMap 655 -| |ReportingTaxonomyMap 656 -| |ConceptMap 657 -| |OrganisationMap 658 -| |CodeMap 659 -| |HybridCodelistMap 660 -| |CategoryMap 661 -| |HybridCodeMap 662 -| |ReportingCategoryMap 663 -| | 664 -|codelist|Codelist 665 -| |HierarchicalCodelist 666 -| |Hierarchy 667 -| |Hierarchy 668 -| |Code 669 -| |HierarchicalCode 670 -| |Level 671 -| | 672 -|categoryscheme|CategoryScheme 673 -| |Category 674 -| |Categorisation 675 -| |ReportingTaxonomy 676 -| |ReportingCategory 677 -| | 678 -|conceptscheme|ConceptScheme 679 -| |Concept 680 -| | 681 -|transformation|TransformationScheme 682 -| |Transformation 683 -| |CustomTypeScheme 684 -| |CustomType 685 -| |NamePersonalisationScheme 686 -| |NamePersonalisation 687 -| |VtlCodelistMapping 688 -| |VtlConceptMapping 689 -| |VtlDataflowMapping 690 -| |VtlConceptSchemeMapping 691 -| |RulesetScheme 692 -| |Ruleset 693 -| |UserDefinedOperatorScheme 694 -| |UserDefinedOperator 695 -| | 696 - 697 697 **Table 2: SDMX-IM Packages and Contained Classes** 698 698 699 - 700 700 === 6.2.4 URN Identification components of SDMX objects === 701 701 702 702 The table below describes the identification components for all SDMX object types that have identification. Note the actual attributes are all Id, but have been prefixed by their class name or multiple class names to show navigation, e.g. conceptSchemeAgencyId is really the Id attribute of the Agency class that is associated to the ConceptScheme. ... ... @@ -705,78 +705,50 @@ 705 705 706 706 Note that for brevity the URN examples omit the prefix. All URNs have the prefix 707 707 708 -urn:sdmx.org.sdmx.infomodel.{package}.{classname}= 679 +> urn:sdmx.org.sdmx.infomodel.{package}.{classname}= 709 709 710 - 711 -|**SDMX Class**|**Key attribute(s)**|**Example of URN** 712 -|Agency|The URN for an Agency is shown later in this table. The identification of an Agency in the URN structure for the maintainable object is by means of the agencyId. The AgencyScheme is not identified as SDMX has a mechanism for identifying an Agency uniquely by its Id. Note that this Id may be hierarchical.|((( 681 +(% style="width:1091.29px" %) 682 +|(% style="width:250px" %)**SDMX Class**|(% style="width:444px" %)**Key attribute(s)**|(% style="width:396px" %)**Example of URN** 683 +|(% style="width:250px" %)Agency|(% style="width:444px" %)The URN for an Agency is shown later in this table. The identification of an Agency in the URN structure for the maintainable object is by means of the agencyId. The AgencyScheme is not identified as SDMX has a mechanism for identifying an Agency uniquely by its Id. Note that this Id may be hierarchical.|(% style="width:396px" %)((( 713 713 IMF 714 - 715 - 716 716 Sub agency in the IMF AGENCIES 717 - 718 - 719 719 IMF.SubAgency1 720 720 ))) 721 -|*ConceptScheme|conceptSchemeAgencyId:conceptSchemeId(ve rsion)|SDMX:CROSS_DOMAIN_CONCEPTS(1.0) 722 -|Concept|((( 723 -conceptSchemeAgencyId: 724 - 725 -conceptSchemeId(version).conceptId 726 -)))|SDMX:CROSS_DOMAIN_CONCEPTS(1.0).FREQ 727 -|*Codelist|codeListAgencyId:codeListId(version)|SDMX:CL_FREQ(1.0) 728 -|Code|codeListAgencyId:codelistId(version).codeId|((( 729 -SDMX:CL_FREQ(1.0).Q 730 - 731 - 688 +|(% style="width:250px" %)*ConceptScheme|(% style="width:444px" %)conceptSchemeAgencyId:conceptSchemeId(ve rsion)|(% style="width:396px" %)SDMX:CROSS_DOMAIN_CONCEPTS(1.0) 689 +|(% style="width:250px" %)Concept|(% style="width:444px" %)conceptSchemeAgencyId: 690 +conceptSchemeId(version).conceptId|(% style="width:396px" %)SDMX:CROSS_DOMAIN_CONCEPTS(1.0).FREQ 691 +|(% style="width:250px" %)*Codelist|(% style="width:444px" %)codeListAgencyId:codeListId(version)|(% style="width:396px" %)SDMX:CL_FREQ(1.0) 692 +|(% style="width:250px" %)Code|(% style="width:444px" %)codeListAgencyId:codelistId(version).codeId|(% style="width:396px" %)SDMX:CL_FREQ(1.0).Q 693 +|(% style="width:250px" %)((( 694 +*Hierarchical Codelist 695 +)))|(% style="width:444px" %)hierachicalCodelistAgencyId: hierarchicalCodelistId(version)|(% style="width:396px" %)((( 696 +UNESCO:CL_EXP_SOURCE(1.0(% style="background-color:transparent" %)) 732 732 ))) 733 - 734 - 735 - 736 -|((( 737 -*Hierarchical 738 - 739 -Codelist 740 -)))|hierachicalCodelistAgencyId: hierarchicalCodelistId(version)|((( 741 -UNESCO:CL_EXP_SOURCE(1.0) 742 - 743 - 744 -))) 745 -|Hierarchy|((( 698 +|(% style="width:250px" %)Hierarchy|(% style="width:444px" %)((( 746 746 hierachicalcodeListAgencyId: 747 - 748 748 hierarchicalcodelistId(version).Hierarchy 749 -)))|UNESCO:CL_EXP_SOURCE(1.0). H-C-GOV 750 -|Level|((( 701 +)))|(% style="width:396px" %)UNESCO:CL_EXP_SOURCE(1.0). 702 +H-C-GOV 703 +|(% style="width:250px" %)Level|(% style="width:444px" %)((( 751 751 hierachicalcodeListAgencyId: 752 - 753 753 hierarchicalcodelistId(version).Hierarchy.Level 754 -)))|((( 706 +)))|(% style="width:396px" %)((( 755 755 ESTAT:HCL_REGION(1.0).H_1.COUNTRY 756 - 757 - 758 758 ))) 759 -|HierarchicalCode|hierachicalCodeListAgencyId: hierarchicalcodelistId(version).hierarchy.hierarc hicalCode|UNESCO:CL_EXP_SOURCE(1.0). H-C-GOV.GOV_CODE1 760 -|*DataStructure|dataStructureDefintitionAgencyId: dataStructureDefintitionId(version)|TFFS:EXT_DEBT(1.0) 761 -|((( 709 +|(% style="width:250px" %)HierarchicalCode|(% style="width:444px" %)hierachicalCodeListAgencyId: hierarchicalcodelistId(version).hierarchy.hierarc hicalCode|(% style="width:396px" %)UNESCO:CL_EXP_SOURCE(1.0). H-C-GOV.GOV_CODE1 710 +|(% style="width:250px" %)*DataStructure|(% style="width:444px" %)dataStructureDefintitionAgencyId: dataStructureDefintitionId(version)|(% style="width:396px" %)TFFS:EXT_DEBT(1.0) 711 +|(% style="width:250px" %)((( 762 762 Dimension 763 - 764 764 Descriptor 765 - 766 766 Measure 767 - 768 768 Descriptor 769 - 770 770 Attribute 771 - 772 772 Descriptor 773 -)))|((( 718 +)))|(% style="width:444px" %)((( 774 774 dataStructureDefinitionAgencyId: dataStructureDefinitionId(version). 775 - 776 776 componentListId 777 - 778 778 where the componentListId is the name of the class (there is only one occurrence of each in the Data Structure Definition) 779 -)))|((( 722 +)))|(% style="width:396px" %)((( 780 780 TFFS:EXT_DEBT(1.0).DimensionDescriptor 781 781 782 782 TFFS:EXT_DEBT(1.0).MeasureDescriptor ... ... @@ -783,181 +783,124 @@ 783 783 784 784 TFFS:EXT_DEBT(1.0).AttributeDescriptor 785 785 ))) 786 -|((( 729 +|(% style="width:250px" %)((( 787 787 GroupDimension 788 - 789 789 Descriptor 790 -)))|((( 732 +)))|(% style="width:444px" %)((( 791 791 dataStructureDefinitionAgencyId: dataStructureDefinitionId(version). 792 - 793 793 groupDimensionDescriptorId 794 -)))|TFFS:EXT_DEBT(1.0).SIBLING 795 -|Dimension|((( 735 +)))|(% style="width:396px" %)TFFS:EXT_DEBT(1.0).SIBLING 736 +|(% style="width:250px" %)Dimension|(% style="width:444px" %)((( 796 796 dataStructureDefinitionAgencyId: dataStructureDefinition (version). 797 - 798 798 dimensionId 799 -)))|TFFS:EXT_DEBT(1.0).FREQ 800 -|TimeDimension|((( 739 +)))|(% style="width:396px" %)TFFS:EXT_DEBT(1.0).FREQ 740 +|(% style="width:250px" %)TimeDimension|(% style="width:444px" %)((( 801 801 dataStructureDefinitionAgencyId: dataStructureDefinition (version). 802 - 803 803 timeDimensionId 804 -)))|TFFS:EXT_DEBT(1.0).TIME_PERIOD 805 -|Measure Dimension|dataStructureDefinitionAgencyId: dataStructureDefinition (version).|TFFS:EXT_DEBT(1.0).STOCK_FLOW 806 - 807 - 808 - 809 -| |measureDimensionId| 810 -|DataAttrribute|dataStructureDefinitionAgencyId: dataStructureDefinition (version). dataAttributeId|TFFS:EXT_DEBT(1.0).OBS_STATUS 811 -|PrimaryMeasure|((( 743 +)))|(% style="width:396px" %)TFFS:EXT_DEBT(1.0).TIME_PERIOD 744 +|(% style="width:250px" %)Measure Dimension|(% style="width:444px" %)dataStructureDefinitionAgencyId: dataStructureDefinition (version). 745 +measureDimensionId|(% style="width:396px" %)TFFS:EXT_DEBT(1.0).STOCK_FLOW 746 +|(% style="width:250px" %)DataAttrribute|(% style="width:444px" %)dataStructureDefinitionAgencyId: dataStructureDefinition (version). dataAttributeId|(% style="width:396px" %)TFFS:EXT_DEBT(1.0).OBS_STATUS 747 +|(% style="width:250px" %)PrimaryMeasure|(% style="width:444px" %)((( 812 812 dataStructureDefinitionAgencyId: dataStructureDefinition (version). 813 - 814 814 primaryMeasureId 815 -)))|TFFS:EXT_DEBT(1.0).OBS_VALUE 816 -|((( 817 -*Category 818 - 819 -Scheme 820 -)))|categorySchemeAgencyId: categorySchemeId(version)|IMF:SDDS(1.0) 821 -|Category|categorySchemeAgencyId: categorySchemeId(version). categoryId.categoryId categoryId.categoryId etc.|((( 750 +)))|(% style="width:396px" %)TFFS:EXT_DEBT(1.0).OBS_VALUE 751 +|(% style="width:250px" %)((( 752 +*Category Scheme 753 +)))|(% style="width:444px" %)categorySchemeAgencyId: 754 +categorySchemeId(version)|(% style="width:396px" %)IMF:SDDS(1.0) 755 +|(% style="width:250px" %)Category|(% style="width:444px" %)categorySchemeAgencyId: 756 +categorySchemeId(version). 757 +categoryId.categoryId categoryId.categoryId etc.|(% style="width:396px" %)((( 822 822 IMF:SDDS(1.0): 823 - 824 824 level_1_category.level_2_category … 825 825 ))) 826 -|((( 827 -*Reporting 828 - 829 -Taxonomy 830 -)))|reportingTaxonomyAgencyId: reportingTaxonomyId(version)| IMF:REP_1(1.0) 831 -|ReportingCategory|reportingTaxonomyAgencyId: reportingTaxonomyId(version) reportingcategoryId.reportingcategoryId|((( 761 +|(% style="width:250px" %)((( 762 +*Reporting Taxonomy 763 +)))|(% style="width:444px" %)reportingTaxonomyAgencyId: reportingTaxonomyId(version)|(% style="width:396px" %) IMF:REP_1(1.0) 764 +|(% style="width:250px" %)ReportingCategory|(% style="width:444px" %)reportingTaxonomyAgencyId: reportingTaxonomyId(version) reportingcategoryId.reportingcategoryId|(% style="width:396px" %)((( 832 832 IMF:REP_1(1.0): 833 - 834 834 level_1_repcategory.level_2_repcategory … 835 835 ))) 836 -|*Categorisation|categorisationAgencyId: categorisationId(version)|IMF:cat001(1.0) 837 -|((( 838 -*Organisation 768 +|(% style="width:250px" %)*Categorisation|(% style="width:444px" %)categorisationAgencyId: categorisationId(version)|(% style="width:396px" %)IMF:cat001(1.0) 769 +|(% style="width:250px" %)((( 770 +*Organisation Unit Scheme 771 +)))|(% style="width:444px" %)organisationUnitSchemeAgencyId: organisationUnitSchemeId(version)|(% style="width:396px" %)ECB:ORGANISATIONS(1.0) 772 +|(% style="width:250px" %)Organisation Unit|(% style="width:444px" %)organisationUnitSchemeAgencyId: organisationUnitSchemeId(version). organisationUnitId|(% style="width:396px" %)ECB:ORGANISATIONS(1.0).1F 773 +|(% style="width:250px" %)*AgencyScheme|(% style="width:444px" %)agencySchemeAgencyId: agencySchemeId(version)|(% style="width:396px" %)ECB:AGENCIES(1.0) 839 839 840 -Unit Scheme 841 -)))|organisationUnitSchemeAgencyId: organisationUnitSchemeId(version)|ECB:ORGANISATIONS(1.0) 842 -|Organisation Unit|organisationUnitSchemeAgencyId: organisationUnitSchemeId(version). organisationUnitId|ECB:ORGANISATIONS(1.0).1F 843 -|*AgencyScheme|agencySchemeAgencyId: agencySchemeId(version)|ECB:AGENCIES(1.0) 844 - 845 - 846 - 847 -|Agency|agencySchemeAgencyId: agencySchemeId(version). agencyId|ECB:AGENCY(1.0).AA 848 -|((( 849 -*DataProvider 850 - 851 -Scheme 852 -)))|dataProviderSchemeAgencyId: dataProviderSchemeId(version)|SDMX:DATA_PROVIDERS(1.0) 853 -|DataProvider|dataProviderSchemeAgencyId: dataProviderSchemeId(version) dataProviderId|SDMX:DATA_PROVIDERS(1.0).PROVIDER_1 854 -|((( 855 -*DataConsumer 856 - 857 -Scheme 858 -)))|dataConsumerSchemeAgencyId: dataConsumerSchemeId(version)|SDMX:DATA_CONSUMERS(1.0) 859 -|Data Consumer|dataConsumerSchemeAgencyId: dataConsumerSchemeId(version) dataConsumerId|SDMX:DATA_CONSUMERS(1.0).CONSUMER_1 860 -|((( 861 -*Metadata 862 - 863 -Structure 864 -)))|MSDAgencyId:MSDId(version)|IMF:SDDS_MSD(1.0) 865 -|MetadataTarget|((( 775 +|(% style="width:262px" %)Agency|(% style="width:369px" %)agencySchemeAgencyId: agencySchemeId(version). agencyId|(% style="width:1262px" %)ECB:AGENCY(1.0).AA 776 +|(% style="width:262px" %)((( 777 +*DataProvider Scheme 778 +)))|(% style="width:369px" %)dataProviderSchemeAgencyId: dataProviderSchemeId(version)|(% style="width:1262px" %)SDMX:DATA_PROVIDERS(1.0) 779 +|(% style="width:262px" %)DataProvider|(% style="width:369px" %)dataProviderSchemeAgencyId: dataProviderSchemeId(version) dataProviderId|(% style="width:1262px" %)SDMX:DATA_PROVIDERS(1.0).PROVIDER_1 780 +|(% style="width:262px" %)((( 781 +*DataConsumer Scheme 782 +)))|(% style="width:369px" %)dataConsumerSchemeAgencyId: dataConsumerSchemeId(version)|(% style="width:1262px" %)SDMX:DATA_CONSUMERS(1.0) 783 +|(% style="width:262px" %)Data Consumer|(% style="width:369px" %)dataConsumerSchemeAgencyId: dataConsumerSchemeId(version) dataConsumerId|(% style="width:1262px" %)SDMX:DATA_CONSUMERS(1.0).CONSUMER_1 784 +|(% style="width:262px" %)((( 785 +*Metadata Structure 786 +)))|(% style="width:369px" %)MSDAgencyId:MSDId(version)|(% style="width:1262px" %)IMF:SDDS_MSD(1.0) 787 +|(% style="width:262px" %)MetadataTarget|(% style="width:369px" %)((( 866 866 MSDAgencyId: 867 - 868 868 MSDId(version).metadataTargetId 869 -)))|IMF:SDDS_MSD(1.0).AGENCY 870 -|((( 790 +)))|(% style="width:1262px" %)IMF:SDDS_MSD(1.0).AGENCY 791 +|(% style="width:262px" %)((( 871 871 Dimension 872 - 873 873 DescriptorValues 874 - 875 875 Target 876 -)))|((( 795 +)))|(% style="width:369px" %)((( 877 877 MSDAgencyId: MSDId(version). 878 - 879 879 metadataTargetId.keyDescriptorValueTargetId 880 -)))|IMF:SDDS_MSD(1.0).AGENCY.KEY 881 -|Identifiable ObjectTarget|((( 798 +)))|(% style="width:1262px" %)IMF:SDDS_MSD(1.0).AGENCY.KEY 799 +|(% style="width:262px" %)Identifiable Object Target|(% style="width:369px" %)((( 800 +MSDAgencyId: MSDId(version).metadataTargetId.identifiableObjectTargetId 801 +)))|(% style="width:1262px" %)IMF:SDDS_MSD(1.0).AGENCY.STR-OBJECT 802 +|(% style="width:262px" %)DataSetTarget|(% style="width:369px" %)((( 882 882 MSDAgencyId: 804 +MSDId(version).metadataTargetId.dataSetTargetId 805 +)))|(% style="width:1262px" %)IMF:SDDS_MSD(1.0).AGENCY.D1101 806 +|(% style="width:262px" %)PeportPeriod Target|(% style="width:369px" %)((( 807 +MSDAgencyId: MSDId(version).metadataTargetId.reportPeriodTargetId 808 +)))|(% style="width:1262px" %)IMF:SDDS_MSD(1.0).AGENCY.REP_PER 883 883 884 -MSDId(version).metadataTargetId.identifiable 885 - 886 -ObjectTargetId 887 -)))|IMF:SDDS_MSD(1.0).AGENCY.STR-OBJECT 888 -|DataSetTarget|((( 889 -MSDAgencyId: 890 - 891 -MSDId(version).metadataTargetId.dataSet 892 - 893 -TargetId 894 -)))|IMF:SDDS_MSD(1.0).AGENCY.D1101 895 -|PeportPeriod Target|((( 896 -MSDAgencyId: 897 - 898 -MSDId(version).metadataTargetId.reportPeriod 899 - 900 -TargetId 901 -)))|IMF:SDDS_MSD(1.0).AGENCY.REP_PER 902 - 903 - 904 - 905 -|((( 810 +|(% style="width:251px" %)((( 906 906 ReportStructure 907 - 908 - 909 -)))|((( 910 -MSDAgencyId: 911 - 912 -MSDId(version).reportStructureId 913 -)))|IMF:SDDS_MSD(1.0).AGENCY_REPORT 914 -|((( 915 -Metadata 916 - 917 -Attribute 918 -)))|((( 919 -MSDAgencyId: 920 - 921 -MSDId(version).reportStructureId.metadataattri buteID 922 -)))|IMF:SDDS_MSD(1.0).AGENCY_REPORT.COMPILATION 923 -|*Dataflow|dataflowAgencyId: dataflowId(version)|TFFS:CRED_EXT_DEBT(1.0) 924 -|*Provision Agreement|((( 812 +)))|(% style="width:442px" %)((( 813 +MSDAgencyId: MSDId(version).reportStructureId 814 +)))|(% style="width:1178px" %)IMF:SDDS_MSD(1.0).AGENCY_REPORT 815 +|(% style="width:251px" %)((( 816 +Metadata Attribute 817 +)))|(% style="width:442px" %)((( 818 +MSDAgencyId: MSDId(version).reportStructureId.metadataattri buteID 819 +)))|(% style="width:1178px" %)IMF:SDDS_MSD(1.0).AGENCY_REPORT.COMPILATION 820 +|(% style="width:251px" %)*Dataflow|(% style="width:442px" %)dataflowAgencyId: dataflowId(version)|(% style="width:1178px" %)TFFS:CRED_EXT_DEBT(1.0) 821 +|(% style="width:251px" %)*Provision Agreement|(% style="width:442px" %)((( 925 925 provisionAgreementAgencyId:provisionAgreem entId(version) 926 - 927 - 928 -)))|((( 823 +)))|(% style="width:1178px" %)((( 929 929 TFFS:CRED_EXT_DEBT_AB(1.0) 930 - 931 - 932 - 933 933 ))) 934 -|((( 935 -*Content 936 - 937 -Constraint 938 -)))|constraintAgencyId:ContentConstraintId(versio n)|TFFS:CREDITOR_DATA_CONTENT(1.0) 939 -|((( 940 -*Attachment 941 - 942 -Constraint 943 -)))|((( 826 +|(% style="width:251px" %)((( 827 +*Content Constraint 828 +)))|(% style="width:442px" %)constraintAgencyId:ContentConstraintId(versio n)|(% style="width:1178px" %)TFFS:CREDITOR_DATA_CONTENT(1.0) 829 +|(% style="width:251px" %)((( 830 +*Attachment Constraint 831 +)))|(% style="width:442px" %)((( 944 944 constraintAgencyId: 945 945 946 946 attachmentConstraintId(version) 947 -)))|TFFS:CREDITOR_DATA_ATTACHMENT_CONSTRAINT_ONE(1.0) 948 -|*Metadataflow|metadataflowAgencyId: metadataflowId(version)|IMF:SDDS_FLOW(1.0) 949 -|*StructureSet|structureSetAgencyId: structureSetId(version)|SDMX:BOP_STRUCTURES(1.0) 950 -|StructureMap|structureSetAgencyId: structureSetId(version). structureMapId|SDMX:BOP_STRUCTURES(1.0).TABLE1_TABLE2 951 -|Component Map|((( 835 +)))|(% style="width:1178px" %)TFFS:CREDITOR_DATA_ATTACHMENT_CONSTRAINT_ONE(1.0) 836 +|(% style="width:251px" %)*Metadataflow|(% style="width:442px" %)metadataflowAgencyId: metadataflowId(version)|(% style="width:1178px" %)IMF:SDDS_FLOW(1.0) 837 +|(% style="width:251px" %)*StructureSet|(% style="width:442px" %)structureSetAgencyId: structureSetId(version)|(% style="width:1178px" %)SDMX:BOP_STRUCTURES(1.0) 838 +|(% style="width:251px" %)StructureMap|(% style="width:442px" %)structureSetAgencyId: structureSetId(version). structureMapId|(% style="width:1178px" %)SDMX:BOP_STRUCTURES(1.0).TABLE1_TABLE2 839 +|(% style="width:251px" %)Component Map|(% style="width:442px" %)((( 952 952 structureSetAgencyId: structureSetId(version). 953 953 954 954 structureMapId. componentMapId 955 -)))|SDMX:BOP_STRUCTURES(1.0).TABLE1_TABLE2. REFAREA_REPCOUNTRY 956 -|CodelistMap|structureSetAgencyId: structureSetId(version). codelistMapId|SDMX:BOP_STRUCTURES(1.0).CLREFAREA_CLREPCOUNTRY 957 -|CodeMap|structureSetAgencyId: structureSetId(version).|SDMX:BOP_STRUCTURES(1.0).CLREFAREA_CLREPCOUNTRY. DE_GER 843 +)))|(% style="width:1178px" %)SDMX:BOP_STRUCTURES(1.0).TABLE1_TABLE2. REFAREA_REPCOUNTRY 844 +|(% style="width:251px" %)CodelistMap|(% style="width:442px" %)structureSetAgencyId: structureSetId(version). codelistMapId|(% style="width:1178px" %)SDMX:BOP_STRUCTURES(1.0).CLREFAREA_CLREPCOUNTRY 845 +|(% style="width:251px" %)CodeMap|(% style="width:442px" %)structureSetAgencyId: structureSetId(version).|(% style="width:1178px" %)SDMX:BOP_STRUCTURES(1.0).CLREFAREA_CLREPCOUNTRY. DE_GER 958 958 959 - 960 - 961 961 | |((( 962 962 codeListMapId. 963 963 ... ... @@ -964,9 +964,7 @@ 964 964 codeMapId 965 965 )))| 966 966 |((( 967 -Category 968 - 969 -SchemeMap 853 +CategorySchemeMap 970 970 )))|structureSetAgencyId: structureSetId(version). categorySchemeMapId|SDMX:BOP_STRUCTURES(1.0).SDMX_EUROSTAT 971 971 |CategoryMap|structureSetAgencyId: structureSetId(version). categorySchemeMapId. categoryMapId|SDMX:BOP_STRUCTURES(1.0).SDMX_EUROSTAT.TOURISM_M AP 972 972 |Organisation SchemeMap|structureSetAgencyId: structureSetId(version). organisationSchemeMapId|SDMX:BOP_STRUCTURES(1.0).DATA_PROVIDER_MAP ... ... @@ -980,71 +980,53 @@ 980 980 structureSetAgencyId: structureSetId(version). conceptSchemeMapId. 981 981 982 982 conceptMapId 983 - 984 984 985 985 )))|SDMX:BOP_STRUCTURES(1.0).SDMX_OECD.COVERAGE_AVAI LABILITY 986 986 |((( 987 -Reporting 988 - 989 -TaxonomyMap 870 +ReportingTaxonomyMap 990 990 )))|structureSetAgencyId: structureSetId(version). reportingTaxonomyMapId|SDMX:BOP_STRUCTURES(1.0).TAXMAP 991 991 |((( 992 -Reporting 993 - 994 -CategoryMap 873 +ReportingCategoryMap 995 995 )))|((( 996 996 structureSetAgencyId: structureSetId(version). 997 - 998 998 reportngCategoryId 999 999 )))|SDMX:BOP_STRUCTURES(1.0).TAXMAP.TOPCAT 1000 1000 1001 - 1002 - 1003 1003 |((( 1004 -HybridCodelist 1005 - 1006 -Map 1007 -)))|structureSetAgencyId: structureSetId(version). hybridCodelistMapId.|SDMX:BOP_STRUCTURES(1.0).COUNTRY_HIERARCHYMAP 880 +HybridCodelistMap 881 +)))|structureSetAgencyId: structureSetId(version). 882 +hybridCodelistMapId.|SDMX:BOP_STRUCTURES(1.0).COUNTRY_HIERARCHYMAP 1008 1008 |HybridCodeMap|structureSetAgencyId: structureSetId(version). hybridCodelistMapId. hybridCodeMapId|SDMX:BOP_STRUCTURES(1.0).COUNTRY_HIERARCHYMAP.CO DEMAP1 1009 1009 |*Process|processAgencyId: processId{version]|BIS:PROCESS1(1.0) 1010 1010 |ProcessStep|((( 1011 1011 processAgencyId: processId(version). 1012 - 1013 1013 processStepId 1014 1014 )))|BIS:PROCESS1(1.0).STEP1 1015 1015 |Transition|((( 1016 1016 processAgencyId: processId(version). 1017 - 1018 1018 processStepId transitionId 1019 1019 )))|BIS:PROCESS1(1.0).STEP1.TRANSITION1 1020 1020 |Subscription|The Subscription is not itself an Identifiable Artefact and therefore it does not follow the rules for URN structure, The name of the URN is registryURN There is no pre-determined format.|This cannot be generated by a common mechanism as subscriptions, although maintainable in the sense that they can be submitted and deleted, are not mandated to be created by a maintenance agency, and have no versioning mechanism. It is therefore the responsibility of the target registry to generate a unique Id for the Subscription, and for the application creating the subscription to store the registryURN that is returned from the registry in the subscription response message. 1021 1021 |((( 1022 -*Transformation 1023 - 1024 -Scheme 895 +*Transformation Scheme 1025 1025 )))|transformationSchemeAgencyId transformationSchemeId(version)|ECB: TRANSFORMATION_SCHEME(1.0) 1026 1026 |Transformation|((( 1027 1027 transformationSchemeAgencyId transformationSchemeId(version) 1028 - 1029 1029 transformationId 1030 1030 )))|ECB:TRANSFORMATION_SCHEME(1.0).TRANS_1 1031 1031 |CustomType Scheme|customTypeSchemeAgencyId customTypeSchemeId(version)|ECB:CUSTOM_TYPE_SCHEME(1.0) 1032 1032 1033 - 1034 - 1035 1035 |CustomType|customTypeSchemeAgencyId customTypeSchemeId(version) customTypeId|ECB: CUSTOM_TYPE_SCHEME(1.0).CUSTOM_TYPE_1 1036 1036 |((( 1037 1037 Name 1038 - 1039 1039 Personalisation 1040 - 1041 1041 Scheme 1042 1042 )))|namePersonalisationSchemeAgencyId namePersonalisationSchemeId(version)|ECB:PSN_SCHEME(1.0) 1043 1043 |((( 1044 1044 Name 1045 - 1046 1046 Personalisation 1047 -)))|namePersonalisationSchemeAgencyId namePersonalisationSchemeId(version) namePersonalisationId|ECB:PSN_SCHEME(1.0).PSN1234 912 +)))|namePersonalisationSchemeAgencyId namePersonalisationSchemeId(version) 913 +namePersonalisationId|ECB:PSN_SCHEME(1.0).PSN1234 1048 1048 |VtlMapping Scheme|vtlMappingSchemeAgencyId VtlMappingSchemeId(version)|ECB:CLIST_MP(2.0) 1049 1049 |VtlCodelist Mapping|vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlCodelistMappingId|ECB:CLIST_MP(2.0).ABZ 1050 1050 |VtlConcept Mapping|vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlConceptMappingId|ECB:CLIST_MP(1.0).XYA ... ... @@ -1057,15 +1057,12 @@ 1057 1057 |RulesetScheme|rulesetSchemeAgencyId rulesetSchemeId(version)|ECB:RULESET_23(1.0) 1058 1058 |Ruleset|rulesetSchemeAgencyId rulesetSchemeId(version) rulesetId|ECB:RULESET_23(1.0).SET111 1059 1059 |((( 1060 -UserDefined 1061 - 1062 -OperatorScheme 926 +UserDefinedOperatorScheme 1063 1063 )))|userDefinedOperatorSchemeAgencyId userDefinedOperatorSchemeId(version)|ECB:OS_CALC(1.2) 1064 1064 |UserDefined Operator|userDefinedOperatorSchemeAgencyId userDefinedOperatorSchemeId(version) usserDefinedOperatorId|ECB:OS_CALC(1.2).OS267 1065 1065 1066 - 7**Table 3: Table of identification components for SDMX Identifiable Artefacts**930 +**Table 3: Table of identification components for SDMX Identifiable Artefacts** 1067 1067 1068 - 1069 1069 = 7 Implementation Notes = 1070 1070 1071 1071 == 7.1 Structural Definition Metadata == ... ... @@ -1086,109 +1086,72 @@ 1086 1086 1087 1087 The following table lists the Maintainable Artefacts. 1088 1088 1089 -|(% colspan="4" %)**Maintainable Artefacts**|(% colspan="2" %)**Content**| 1090 -|(% colspan="2" %)**Abstract Class**|(% colspan="2" %)**Concrete Class**|(% colspan="2" %) | 1091 -|(% colspan="2" %)Item Scheme|(% colspan="2" %)Codelist|(% colspan="2" %)Code| 1092 -|(% colspan="2" %) |(% colspan="2" %)Concept Scheme|(% colspan="2" %)Concept| 1093 -|(% colspan="2" %) |(% colspan="2" %)Category Scheme|(% colspan="2" %)Category| 1094 -|(% colspan="2" %) |(% colspan="2" %)Organisation Unit Scheme|(% colspan="2" %)Organisation Unit| 1095 -|(% colspan="2" %) |(% colspan="2" %)Agency Scheme|(% colspan="2" %)Agency| 1096 -|(% colspan="2" %) |(% colspan="2" %)Data Provider Scheme|(% colspan="2" %)Data Provider| 1097 -|(% colspan="2" %) |(% colspan="2" %)Data Consumer Scheme|(% colspan="2" %)Data Consumer| 1098 -|(% colspan="2" %) |(% colspan="2" %)Reporting Taxonomy|(% colspan="2" %)Reporting Category| 1099 -|(% colspan="2" %) |(% colspan="2" %)Transformation Scheme|(% colspan="2" %)Transformation| 1100 -|(% colspan="2" %) |(% colspan="2" %)Custom Type Scheme|(% colspan="2" %)Custom Type| 1101 -| |(% colspan="4" %)**Maintainable Artefacts**|(% colspan="2" %)**Content** 1102 -| |(% colspan="2" %)**Abstract Class**|(% colspan="2" %)**Concrete Class**|(% colspan="2" %) 1103 -| |(% colspan="2" %) |(% colspan="2" %)Name Personalisation Scheme|(% colspan="2" %)Name Personalisation 1104 -| |(% colspan="2" %) |(% colspan="2" %)Vtl Mapping Scheme|(% colspan="2" %)Vtl Codelist Mapping 1105 -| |(% colspan="2" %) |(% colspan="2" %) |(% colspan="2" %)Vtl Concept Mapping 1106 -| |(% colspan="2" %) |(% colspan="2" %) |(% colspan="2" %)Vtl Dataflow Mapping 1107 -| |(% colspan="2" %) |(% colspan="2" %) |(% colspan="2" %)((( 1108 -Vtl Concept Scheme 1109 - 1110 -Mapping 1111 -))) 1112 -| |(% colspan="2" %) |(% colspan="2" %)Ruleset Scheme|(% colspan="2" %)Ruleset 1113 -| |(% colspan="2" %) |(% colspan="2" %)User Defined Operator Scheme|(% colspan="2" %)User Defined Operator 1114 -| |(% colspan="2" %) |(% colspan="2" %) |(% colspan="2" %) 1115 -| |(% colspan="2" %)Structure|(% colspan="2" %)Data Structure Definition|(% colspan="2" %)((( 952 +(% style="width:640.294px" %) 953 +|(% colspan="2" rowspan="1" style="width:186px" %)**Maintainable Artefacts**|(% style="width:206px" %)**Content** 954 +|(% style="width:171px" %)**Abstract Class**|(% style="width:232px" %)**Concrete Class**|(% style="width:206px" %) 955 +|(% style="width:171px" %)Item Scheme|(% style="width:232px" %)Codelist|(% style="width:206px" %)Code 956 +|(% style="width:171px" %) |(% style="width:232px" %)Concept Scheme|(% style="width:206px" %)Concept 957 +|(% style="width:171px" %) |(% style="width:232px" %)Category Scheme|(% style="width:206px" %)Category 958 +|(% style="width:171px" %) |(% style="width:232px" %)Organisation Unit Scheme|(% style="width:206px" %)Organisation Unit 959 +|(% style="width:171px" %) |(% style="width:232px" %)Agency Scheme|(% style="width:206px" %)Agency 960 +|(% style="width:171px" %) |(% style="width:232px" %)Data Provider Scheme|(% style="width:206px" %)Data Provider 961 +|(% style="width:171px" %) |(% style="width:232px" %)Data Consumer Scheme|(% style="width:206px" %)Data Consumer 962 +|(% style="width:171px" %) |(% style="width:232px" %)Reporting Taxonomy|(% style="width:206px" %)Reporting Category 963 +|(% style="width:171px" %) |(% style="width:232px" %)Transformation Scheme|(% style="width:206px" %)Transformation 964 +|(% style="width:171px" %) |(% style="width:232px" %)Custom Type Scheme|(% style="width:206px" %)Custom Type 965 +|(% style="width:171px" %) |(% style="width:232px" %)Name Personalisation Scheme|(% style="width:206px" %)Name Personalisation 966 +|(% style="width:171px" %) |(% style="width:232px" %)Vtl Mapping Scheme|(% style="width:206px" %)Vtl Codelist Mapping 967 +|(% style="width:171px" %) |(% style="width:232px" %) |(% style="width:206px" %)Vtl Dataflow Mapping 968 +|(% style="width:171px" %) |(% style="width:232px" %) |(% style="width:206px" %)Vtl Concept Scheme Mapping 969 +|(% style="width:171px" %) |(% style="width:232px" %)Ruleset Scheme|(% style="width:206px" %)Ruleset 970 +|(% style="width:171px" %) |(% style="width:232px" %)User Defined Operator Scheme|(% style="width:206px" %)User Defined Operator 971 +|(% style="width:171px" %) |(% style="width:232px" %) |(% style="width:206px" %)User Defined Operator 972 +|(% style="width:171px" %)Structure|(% style="width:232px" %)Data Structure Definition|(% style="width:206px" %)((( 1116 1116 Dimension Descriptor 1117 - 1118 1118 Group Dimension 1119 - 1120 1120 Descriptor 1121 - 1122 1122 Dimension 1123 - 1124 1124 Measure Dimension 1125 - 1126 1126 Time Dimension 1127 - 1128 1128 Attribute Descriptor 1129 - 1130 1130 Data Attribute 1131 - 1132 1132 Measure Descriptor 1133 - 1134 1134 Primary Measure 1135 1135 ))) 1136 -| |(% colspan="2" %) |(% colspan="2" %)Metadata Structure Definition|(% colspan="2" %)((( 1137 -Metadata Target, 1138 - 1139 -Dimension Descriptor 1140 - 984 +|(% style="width:171px" %) |(% style="width:232px" %)Metadata Structure Definition|(% style="width:206px" %)((( 985 +Metadata Target, Dimension Descriptor 1141 1141 Values Target Identifiable 1142 - 1143 1143 Object Target 1144 - 1145 1145 Report Period Target 1146 - 1147 1147 Data SetTarget 1148 - 1149 1149 Report Structure 1150 - 1151 1151 Metadata Attribute 1152 1152 ))) 1153 -| |(%colspan="2" %)Structure Usage|(%colspan="2" %)Dataflow Definition|(%colspan="2" %)1154 -| |(%colspan="2" %) |(%colspan="2" %)Metadataflow Definition|(%colspan="2" %)1155 -| |(%colspan="2" %)None|(%colspan="2" %)Process|(%colspan="2" %)Process Step1156 -| |(%colspan="2" %)None|(%colspan="2" %)Structure Set|(%colspan="2" %)(((993 +|(% style="width:171px" %)Structure Usage|(% style="width:232px" %)Dataflow Definition|(% style="width:206px" %) 994 +|(% style="width:171px" %) |(% style="width:232px" %)Metadataflow Definition|(% style="width:206px" %) 995 +|(% style="width:171px" %)None|(% style="width:232px" %)Process|(% style="width:206px" %)Process Step 996 +|(% style="width:171px" %)None|(% style="width:232px" %)Structure Set|(% style="width:206px" %)((( 1157 1157 Component Map 1158 - 1159 1159 Concept Scheme Map 1160 - 1161 1161 Codelist Map 1162 - 1163 1163 Category Scheme Map 1164 - 1165 1165 Reporting Taxonomy Map 1166 - 1167 1167 Organisation Scheme Map 1168 - 1169 1169 Concept Map 1170 - 1171 1171 Code Map 1172 - 1173 1173 Category Map 1174 - 1175 1175 Organisation Map 1176 - 1177 1177 Reporting Category Map 1178 - 1179 1179 Hybrid Codelist Map 1180 - 1181 1181 Hybrid Code Map 1182 1182 ))) 1183 -| |(%colspan="2" %)None|(%colspan="2" %)Provision Agreement|(%colspan="2" %)1184 -| |(%colspan="2" %)None|(%colspan="2" %)Hierarchical Codelist|(%colspan="2" %)(((1011 +|(% style="width:171px" %)None|(% style="width:232px" %)Provision Agreement|(% style="width:206px" %) 1012 +|(% style="width:171px" %)None|(% style="width:232px" %)Hierarchical Codelist|(% style="width:206px" %)((( 1185 1185 Hierarchy 1186 - 1187 1187 Hierarchical Code 1188 1188 ))) 1189 -| | | | | | | 1190 1190 1191 -** Table 4: Table of Maintainable Artefacts for Structural Definition Metadata**1017 +**able 4: Table of Maintainable Artefacts for Structural Definition Metadata** 1192 1192 1193 1193 === 7.1.2 Item Scheme, Structure === 1194 1194 ... ... @@ -1195,10 +1195,7 @@ 1195 1195 The artefacts included in the structural definitions are: 1196 1196 1197 1197 * All types of Item Scheme (Codelist, Concept Scheme, Category Scheme, Organisation Scheme - Agency Scheme, Data Provider Scheme, Data Consumer Scheme, Organisation Unit Scheme) 1198 -* All types of Structure (Data Structure Definition, Metadata Structure 1199 - 1200 -Definition) 1201 - 1024 +* All types of Structure (Data Structure Definition, Metadata Structure Definition) 1202 1202 * All types of Structure Usage (Dataflow Definition, Metadataflow Definition) 1203 1203 1204 1204 === 7.1.3 Structure Usage === ... ... @@ -1217,6 +1217,8 @@ 1217 1217 1218 1218 ==== 7.1.3.3 Structure Usage Model ==== 1219 1219 1043 +[[image:1747829078194-749.png]] 1044 + 1220 1220 **Figure 10: SDMX-IM of links from Structure Usage to Category** 1221 1221 1222 1222 In addition to the maintenance of the Dataflow Definition and the Metadataflow Definition the following links must be maintained in the registry: ... ... @@ -1243,10 +1243,10 @@ 1243 1243 1244 1244 An organisation which publishes statistical data or reference metadata and wishes to make it available to an SDMX enabled community is called a Data Provider. In terms of the SDMX Information Model, the Data Provider is maintained in a Data Provider Scheme. 1245 1245 1071 +[[image:1747829109466-595.png]] 1246 1246 1247 1247 **Figure 11: SDMX-IM of the Data Provider** 1248 1248 1249 - 1250 1250 Note that the Data Provider does not inherit the hierarchy association. The diagram below shows a logical schematic of the data model classes required to maintain provision agreements 1251 1251 1252 1252 [[image:1747824123019-181.jpeg]] ... ... @@ -1255,8 +1255,10 @@ 1255 1255 1256 1256 The diagram below is a logical representation of the data required in order to maintain Provision Agreements. 1257 1257 1083 +[[image:1747829139951-378.png]] 1258 1258 1259 -==== Figure 13: Logical class diagram of the information contained in the Provision Agreement ==== 1085 +(% class="wikigeneratedid" id="HFigure13:LogicalclassdiagramoftheinformationcontainedintheProvisionAgreement" %) 1086 +**Figure 13: Logical class diagram of the information contained in the Provision Agreement** 1260 1260 1261 1261 A Provision Agreement is structural metadata. Each Provision Agreement must reference a Data Provider and a Dataflow or Metadataflow Definition. The Data Provider and the Dataflow/Metadataflow Definition must exist already in order to set up a Provision Agreement. 1262 1262 ... ... @@ -1284,13 +1284,12 @@ 1284 1284 1285 1285 === 7.3.3 Data and Metadata Constraints: Model === 1286 1286 1114 +[[image:1747829204737-370.png]] 1287 1287 1116 +**Figure 15: Logical class diagram showing inheritance between and reference to constrainable artifacts** 1288 1288 1289 - ==== Figure15: Logicalclass diagram showing inheritancebetween and reference to constrainable artifacts====1118 +The class diagram above shows that DataProvider, DataflowDefinition, MetadataflowDefinition, ProvisionAgreement, DataStructureDefinition, MetadataStructureDefinition, SimpleDatasource and QueryDatasource are all concrete sub-classes of ConstrainableArtefact and can therefore have Constraints specified. Note that the actual Constraint as submitted is associated to the reference classes which inherit from ConstrainableRef: these are used to refer to the classes to which the Constraint applies. 1290 1290 1291 -The class diagram above shows that DataProvider, DataflowDefinition, MetadataflowDefinition, ProvisionAgreement, DataStructureDefinition, MetadataStructureDefinition, SimpleDatasource and QueryDatasource are all concrete sub-classes of ConstrainableArtefact and can therefore have Constraints specified. Note that the actual Constraint as submitted is associated to the reference classes which inherit from ConstrainableRef: these are used to refer to the classes to which the Constraint applies. 1292 - 1293 - 1294 1294 The content of the Constraint can be found in the SDMX Information Model document. 1295 1295 1296 1296 == 7.4 Data and Metadata Registration == ... ... @@ -1311,7 +1311,7 @@ 1311 1311 1312 1312 [[image:1747824123025-411.jpeg]] 1313 1313 1314 - 1140 +**Figure 16: Schematic of the Objects Concerned with Registration** 1315 1315 1316 1316 ==== 7.4.2.2 Registration Request Model ==== 1317 1317 ... ... @@ -1325,11 +1325,14 @@ 1325 1325 1326 1326 The Registration has an action attribute which takes one of the following values: 1327 1327 1328 -|**Action Attribute Value**|**Behaviour** 1329 -|Append|Add this Registration to the registry 1330 -|Replace|Replace the existing Registration with identified by the id in the Registration of the Submit Registration Request 1331 -|Delete|Delete the existing Registration identified by the id in the Registration of the Submit Registration Request 1154 +(% style="width:970.294px" %) 1155 +|(% style="width:212px" %)**Action Attribute Value**|(% style="width:756px" %)**Behaviour** 1156 +|(% style="width:212px" %)Append|(% style="width:756px" %)Add this Registration to the registry 1157 +|(% style="width:212px" %)Replace|(% style="width:756px" %)Replace the existing Registration with identified by the id in the Registration of the Submit Registration Request 1158 +|(% style="width:212px" %)Delete|(% style="width:756px" %)Delete the existing Registration identified by the id in the Registration of the Submit Registration Request 1332 1332 1160 +[[image:1747829290890-122.png]] 1161 + 1333 1333 **Figure 17: Logical Class Diagram of Registration of Data and Metadata** 1334 1334 1335 1335 The Query Datasource is an abstract class that represents a data source which can understand an SDMX-ML query (SOAPDatasource) or RESTful query ... ... @@ -1344,25 +1344,19 @@ 1344 1344 1345 1345 Information in the data or metadata set is extracted and placed in one or more Content Constraints (see the Constraints model in the SDMX Information Model – Section 2 of the SDMX Standards). The information to be extracted is indicated by the Boolean values set on the Provision Agreement as shown in the table below. 1346 1346 1347 -|**Indexing Required**|**Registration Process Activity** 1348 -|indexTimeSeries|Extract all the series keys and create a KeySet(s) Constraint. 1349 -|indexDataSet|((( 1350 -Extract all the codes and other content of the Key value of the Series Key in a Data Set and create one or more Cube 1351 - 1352 -Regions containing Member Selections of Dimension Components of the Constraints model in the SDMX-IM, and the associated Selection Value. 1176 +|(% style="width:185px" %)**Indexing Required**|(% style="width:1686px" %)**Registration Process Activity** 1177 +|(% style="width:185px" %)indexTimeSeries|(% style="width:1686px" %)Extract all the series keys and create a KeySet(s) Constraint. 1178 +|(% style="width:185px" %)indexDataSet|(% style="width:1686px" %)((( 1179 +Extract all the codes and other content of the Key value of the Series Key in a Data Set and create one or more Cube Regions containing Member Selections of Dimension Components of the Constraints model in the SDMX-IM, and the associated Selection Value. 1353 1353 ))) 1354 -|indexReportingPeriod|((( 1181 +|(% style="width:185px" %)indexReportingPeriod|(% style="width:1686px" %)((( 1355 1355 This applies only to a registered dataset. 1356 - 1357 1357 Extract the Reporting Begin and Reporting End from the Header of the Message containing the data set, and create a Reference Period constraint. 1358 1358 ))) 1359 -|indexAttributes|((( 1185 +|(% style="width:185px" %)indexAttributes|(% style="width:1686px" %)((( 1360 1360 **Data Set** 1361 - 1362 1362 Extract the content of the Attribute Values in a Data Set and create one or more Cube Regions containing Member Selections of Data Attribute Components of the Constraints model in the SDMXIM, and the associated Selection Value 1363 - 1364 1364 **Metadata Set** 1365 - 1366 1366 Indicate the presence of a Reported Attribute by creating one or more Cube Regions containing Member Selections of Metadata Attribute Components of the Constraints model in the SDMX-IM. Note that the content is not stored in the Selection Value. 1367 1367 ))) 1368 1368 ... ... @@ -1372,14 +1372,13 @@ 1372 1372 1373 1373 === 7.4.3 Registration Response === 1374 1374 1375 -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 Submit Registration class has a status field which is either set to 1198 +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 Submit Registration class has a status field which is either set to “Success”, “Warning” or “Failure”. 1376 1376 1377 -“Success”, “Warning” or “Failure”. 1378 - 1379 1379 If the registration has succeeded, a Registration will be returned - this holds the Registry-allocated Id of the newly registered Datasource plus a Datasource holding the URL to access the dataset, metadataset, or query service. 1380 1380 1381 1381 The Registration Response returns set of registration status (one for each registration submitted) in terms of a Status Message (this is common to all Registry Responses) that indicates success or failure. In the event of registration failure, a set of Message Text are returned, giving the error messages that occurred during registration. It is entirely possible when registering a batch of datasets, that the response will contain some successful and some failed statuses. The logical model for the Registration Response is shown below: 1382 1382 1204 +[[image:1747829477882-750.png]] 1383 1383 1384 1384 **Figure 18: Logical class diagram showing the registration response** 1385 1385 ... ... @@ -1389,15 +1389,12 @@ 1389 1389 1390 1390 A user can submit a subscription in the registry that defines which events are of interest, and either an email and/or an HTTP address to which a notification of qualifying events will be delivered. The subscription will be identified in the registry by a URN which is returned to the user when the subscription is created. If the user wants to delete the subscription at a later point, the subscription URN is used as identification. Subscriptions have a validity period expressed as a date range (startDate, endDate) and the registry may delete any expired subscriptions, and will notify the subscriber on expiry. 1391 1391 1392 -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 1214 +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”. 1393 1393 1394 - “notification”.1216 +=== 7.5.1Subscription Logical Class Diagram === 1395 1395 1396 - .5.1SubscriptionLogical Class Diagram1218 +[[image:1747829554603-150.png]] 1397 1397 1398 - 1399 -[[image:1747824123028-257.png]] 1400 - 1401 1401 **Figure 19: Logical Class Diagram of the Subscription** 1402 1402 1403 1403 === 7.5.2 Subscription Information === ... ... @@ -1404,73 +1404,58 @@ 1404 1404 1405 1405 Regardless of the type of registry/repository events being observed, a subscription always contains: 1406 1406 1407 -~1. A set of URIs describing the end-points to which notifications must be sent if the subscription is activated. The URIs can be either mailto~: or http: protocol. In the former case an email notification is sent; in the latter an HTTP POST notification is sent. 1226 +1. A set of URIs describing the end-points to which notifications must be sent if the subscription is activated. The URIs can be either mailto~: or http: protocol. In the former case an email notification is sent; in the latter an HTTP POST notification is sent. 1227 +1. A user-defined identifier which is returned in the response to the subscription request. This helps with asynchronous processing and is NOT stored in the Registry. 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 +1. A selector which specifies which type of events are of interest. The set of event types is: 1408 1408 1409 -2. A user-defined identifier which is returned in the response to the subscription request. This helps with asynchronous processing and is NOT stored in the Registry. 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 1410 1410 1411 -3. 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. 1412 - 1413 -4. A selector which specifies which type of events are of interest. The set of event types is: 1414 - 1415 -|**Event Type**|**Comment** 1416 -|STRUCTURAL_REPOSITORY_EVENTS|Life-cycle changes to Maintainable Artefacts in the structural metadata repository. 1417 -|DATA_REGISTRATION_EVENTS|Whenever a published dataset is registered. This can be either a SDMXML data file or an SDMX conformant database. 1418 -|METADATA_REGISTRATION_EVENTS|Whenever a published metadataset is registered. This can be either a SDMXML reference metadata file or an SDMX conformant database. 1419 -|ALL_EVENTS|All events of the specified EventType 1420 - 1421 1421 === 7.5.3 Wildcard Facility === 1422 1422 1423 1423 Subscription notification supports wildcarded identifier components URNs, which are identiiers which have some or all of their component parts replaced by the wildcard character `%`. Identifier components comprise: 1424 1424 1425 - agencyID 1241 +* agencyID 1242 +* id 1243 +* version 1426 1426 1427 - id 1428 - 1429 - version 1430 - 1431 1431 Examples of wildcarded identifier components for an identified object type of Codelist are shown below. 1432 1432 1433 -AgencyID = % 1434 - 1247 +//AgencyID = % 1435 1435 Id = % 1249 +Version = %// 1436 1436 1437 -Version = % 1438 - 1439 1439 This subscribes to all Codelists of all versions for all agencies. 1440 1440 1441 -AgencyID = AGENCY1 1442 - 1253 +//AgencyID = AGENCY1 1443 1443 Id = CODELIST1 1255 +Version = %// 1444 1444 1445 -Version = % 1446 - 1447 1447 This subscribes to all versions of Codelist CODELIST1 maintained by the agency 1448 1448 1449 -AGENCY1 1450 - 1259 +//AGENCY1 1451 1451 AgencyID = AGENCY1 1452 - 1453 1453 Id = % 1262 +Version = %// 1454 1454 1455 -Version = % 1456 - 1457 1457 This subscribes to all versions of all Codelist objects maintained by the agency 1458 1458 1459 -AGENCY1 1460 - 1266 +//AGENCY1 1461 1461 AgencyID = % 1462 - 1463 1463 Id = CODELIST1 1269 +Version = %// 1464 1464 1465 -Version = % 1466 - 1467 1467 This subscribes to all versions of Codelist CODELIST1 maintained by the agency 1468 1468 1469 -AGENCY1 1273 +//AGENCY1// 1470 1470 1471 1471 Note that if the subscription is to the latest version then this can be achieved by the * character 1472 1472 1473 -i.e. Version = * 1277 +//i.e. Version = *// 1474 1474 1475 1475 Note that a subscription using the URN mechanism cannot use wildcard characters. 1476 1476 ... ... @@ -1482,16 +1482,15 @@ 1482 1482 1483 1483 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: 1484 1484 1289 +|(% style="width:405px" %)**Selector**|(% style="width:1467px" %)**Comment** 1290 +|(% style="width:405px" %)DataProvider|(% style="width:1467px" %)Any datasets or metadata sets registered by the specified data provider will activate the notification. 1291 +|(% style="width:405px" %)ProvisionAgreement|(% style="width:1467px" %)Any datasets or metadata sets registered for the provision agreement will activate the notification. 1292 +|(% style="width:405px" %)Dataflow (&Metadataflow)|(% style="width:1467px" %)Any datasets or metadata sets registered for the specified dataflow (or metadataflow) will activate the notification. 1293 +|(% style="width:405px" %)DataStructureDefinition & MetadataStructureDefinition|(% style="width:1467px" %)Any datasets or metadata sets registered for those dataflows (or metadataflows) that are based on the specified Data Structure Definition will 1294 +|(% style="width:405px" %)**Selector**|(% style="width:1467px" %)**Comment** 1295 +|(% style="width:405px" %) |(% style="width:1467px" %)activate the notification. 1296 +|(% style="width:405px" %)Category|(% style="width:1467px" %)Any datasets or metadata sets registered for those dataflows, metadataflows, provision agreements that are categorised by the category. 1485 1485 1486 -|**Selector**|**Comment** 1487 -|DataProvider|Any datasets or metadata sets registered by the specified data provider will activate the notification. 1488 -|ProvisionAgreement|Any datasets or metadata sets registered for the provision agreement will activate the notification. 1489 -|Dataflow (&Metadataflow)|Any datasets or metadata sets registered for the specified dataflow (or metadataflow) will activate the notification. 1490 -|DataStructureDefinition & MetadataStructureDefinition|Any datasets or metadata sets registered for those dataflows (or metadataflows) that are based on the specified Data Structure Definition will 1491 -|**Selector**|**Comment** 1492 -| |activate the notification. 1493 -|Category|Any datasets or metadata sets registered for those dataflows, metadataflows, provision agreements that are categorised by the category. 1494 - 1495 1495 The event will also capture the semantic of the registration: deletion or replacement of an existing registration or a new registration. 1496 1496 1497 1497 == 7.6 Notification == ... ... @@ -1498,8 +1498,10 @@ 1498 1498 1499 1499 === 7.6.1 Logical Class Diagram === 1500 1500 1304 +[[image:1747829675568-610.png]] 1501 1501 1502 -==== Figure 20: Logical Class Diagram of the Notification ==== 1306 +(% class="wikigeneratedid" id="HFigure20:LogicalClassDiagramoftheNotification" %) 1307 +**Figure 20: Logical Class Diagram of the Notification** 1503 1503 1504 1504 A notification is an XML document that is sent to a user via email or http POST whenever a subscription is activated. It is an asynchronous one-way message. 1505 1505 ... ... @@ -1519,5 +1519,3 @@ 1519 1519 === 7.6.3 Registration Event Component === 1520 1520 1521 1521 The notification will contain the Registration. 1522 - 1523 -
- 1747824504225-229.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +xwiki:XWiki.helena - Size
-
... ... @@ -1,0 +1,1 @@ 1 +52.8 KB - Content
- 1747829078194-749.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +xwiki:XWiki.helena - Size
-
... ... @@ -1,0 +1,1 @@ 1 +40.4 KB - Content
- 1747829109466-595.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +xwiki:XWiki.helena - Size
-
... ... @@ -1,0 +1,1 @@ 1 +30.4 KB - Content
- 1747829139951-378.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +xwiki:XWiki.helena - Size
-
... ... @@ -1,0 +1,1 @@ 1 +21.1 KB - Content
- 1747829204737-370.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +xwiki:XWiki.helena - Size
-
... ... @@ -1,0 +1,1 @@ 1 +55.8 KB - Content
- 1747829290890-122.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +xwiki:XWiki.helena - Size
-
... ... @@ -1,0 +1,1 @@ 1 +41.4 KB - Content
- 1747829477882-750.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +xwiki:XWiki.helena - Size
-
... ... @@ -1,0 +1,1 @@ 1 +24.6 KB - Content
- 1747829554603-150.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +xwiki:XWiki.helena - Size
-
... ... @@ -1,0 +1,1 @@ 1 +99.1 KB - Content
- 1747829675568-610.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +xwiki:XWiki.helena - Size
-
... ... @@ -1,0 +1,1 @@ 1 +31.1 KB - Content
- 1747832400104-286.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +xwiki:XWiki.helena - Size
-
... ... @@ -1,0 +1,1 @@ 1 +172.3 KB - Content