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:2 44px" %)**Interface**|**Behaviour**344 -|(% style="width:2 44px" %)All|(((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,12 +362,11 @@ 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:2 44px" %)SubmitStructureRequest|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:2 44px" %)SubmitProvisioningRequest|No additional behaviour.370 -|(% style="width:2 44px" %)Submit Registration Request|(((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 372 For a queryable datasource the Registry MAY validate that the source exists and can accept an SDMX-ML data query. 373 373 ))) ... ... @@ -433,6 +433,8 @@ 433 433 434 434 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. 435 435 430 +[[image:1747994320263-112.png]] 431 + 436 436 **Figure 6: Agency Scheme Model** 437 437 438 438 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. ... ... @@ -454,7 +454,7 @@ 454 454 455 455 [[image:1747824123012-527.jpeg]] 456 456 457 - ====Figure 7: Example of Hierarchic Structure of Agencies====453 +**Figure 7: Example of Hierarchic Structure of Agencies** 458 458 459 459 The following organizations maintain an Agency Scheme. 460 460 ... ... @@ -469,9 +469,8 @@ 469 469 470 470 An example of this is shown in the XML snippet below. 471 471 472 -[[image:1747824 123013-196.jpeg||height="309" width="446"]]468 +[[image:1747832400104-286.png]] 473 473 474 -(% class="wikigeneratedid" id="HFigure8:ExampleShowingUseofAgencyIdentifiers" %) 475 475 **Figure 8: Example Showing Use of Agency Identifiers** 476 476 477 477 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. ... ... @@ -484,13 +484,14 @@ 484 484 485 485 ==== 6.2.2.2 URN Structure ==== 486 486 487 -===== //Case Rules for URN// ===== 482 +(% class="wikigeneratedid" id="HCaseRulesforURN" %) 483 +//Case Rules for URN// 488 488 489 489 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. 490 490 491 491 The generic structure of the URN is as follows: 492 492 493 -SDMXprefix.SDMX-IM-package-name.class-name=agencyid:maintainedobject-id(maintainedobject-version).*containerobject-id.object-id 489 +>SDMXprefix.SDMX-IM-package-name.class-name=agencyid:maintainedobject-id(maintainedobject-version).*containerobject-id.object-id 494 494 495 495 ~* this can repeat and may not be present (see explanation below) 496 496 ... ... @@ -502,7 +502,7 @@ 502 502 503 503 In the explanation below the actual object that is the target of the URN is called the **//actual object//**. 504 504 505 -**SDMXPrefix:** urn:sdmx:org. 501 +**SDMXPrefix:** urn:sdmx:org. 506 506 507 507 **SDMX-IM package name:** sdmx.infomodel.package= 508 508 ... ... @@ -585,91 +585,92 @@ 585 585 586 586 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. 587 587 588 -|(% style="width:127px" %)**Package**|(% style="width:1745px" %)((( 584 +(% style="width:644.294px" %) 585 +|(% style="width:127px" %)**Package**|(% style="width:494px" %)((( 589 589 **URN Classname (model classname where this is different)** 590 590 ))) 591 -|(% style="width:127px" %)base|(% style="width:4 5px" %)Agency592 -|(% style="width:127px" %) |(% style="width:4 5px" %)OrganisationUnitScheme593 -|(% style="width:127px" %) |(% style="width:4 5px" %)AgencyScheme594 -|(% style="width:127px" %) |(% style="width:4 5px" %)DataProviderScheme595 -|(% style="width:127px" %) |(% style="width:4 5px" %)DataConsumerScheme596 -|(% style="width:127px" %) |(% style="width:4 5px" %)OrganisationUnit597 -|(% style="width:127px" %) |(% style="width:4 5px" %)DataProvider598 -|(% style="width:127px" %) |(% style="width:4 5px" %)DataConsumer599 -|(% style="width:127px" %)datastructure|(% style="width:4 5px" %)DataStructure (DataStructureDefinition)600 -|(% style="width:127px" %) |(% style="width:4 5px" %)AttributeDescriptor601 -|(% style="width:127px" %) |(% style="width:4 5px" %)DataAttribute602 -|(% style="width:127px" %) |(% style="width:4 5px" %)GroupDimensionDescriptor603 -|(% style="width:127px" %) |(% style="width:4 5px" %)DimensionDescriptor604 -|(% style="width:127px" %) |(% style="width:4 5px" %)Dimension605 -|(% style="width:127px" %) |(% style="width:4 5px" %)MeasureDimension606 -|(% style="width:127px" %) |(% style="width:4 5px" %)TimeDimension607 -|(% style="width:127px" %) |(% style="width:4 5px" %)MeasureDescriptor608 -|(% style="width:127px" %) |(% style="width:4 5px" %)PrimaryMeasure609 -|(% style="width:127px" %) |(% style="width:4 5px" %)Dataflow (DataflowDefinition)610 -|(% style="width:127px" %)metadatastructure|(% style="width:4 5px" %)MetadataTarget611 -|(% style="width:127px" %) |(% style="width:4 5px" %)DimensionDescriptorValueTarget612 -|(% style="width:127px" %) |(% style="width:4 5px" %)IdentifiableObjectTarget613 -|(% style="width:127px" %) |(% style="width:4 5px" %)ReportPeriodTarget614 -|(% style="width:127px" %) |(% style="width:4 5px" %)DataSetTarget615 -|(% style="width:127px" %) |(% style="width:4 5px" %)ReportStructure616 -|(% style="width:127px" %) |(% style="width:4 5px" %)MetadataAttribute617 -|(% style="width:127px" %) |(% style="width:4 5px" %)(((588 +|(% style="width:127px" %)base|(% style="width:494px" %)Agency 589 +|(% style="width:127px" %) |(% style="width:494px" %)OrganisationUnitScheme 590 +|(% style="width:127px" %) |(% style="width:494px" %)AgencyScheme 591 +|(% style="width:127px" %) |(% style="width:494px" %)DataProviderScheme 592 +|(% style="width:127px" %) |(% style="width:494px" %)DataConsumerScheme 593 +|(% style="width:127px" %) |(% style="width:494px" %)OrganisationUnit 594 +|(% style="width:127px" %) |(% style="width:494px" %)DataProvider 595 +|(% style="width:127px" %) |(% style="width:494px" %)DataConsumer 596 +|(% style="width:127px" %)datastructure|(% style="width:494px" %)DataStructure (DataStructureDefinition) 597 +|(% style="width:127px" %) |(% style="width:494px" %)AttributeDescriptor 598 +|(% style="width:127px" %) |(% style="width:494px" %)DataAttribute 599 +|(% style="width:127px" %) |(% style="width:494px" %)GroupDimensionDescriptor 600 +|(% style="width:127px" %) |(% style="width:494px" %)DimensionDescriptor 601 +|(% style="width:127px" %) |(% style="width:494px" %)Dimension 602 +|(% style="width:127px" %) |(% style="width:494px" %)MeasureDimension 603 +|(% style="width:127px" %) |(% style="width:494px" %)TimeDimension 604 +|(% style="width:127px" %) |(% style="width:494px" %)MeasureDescriptor 605 +|(% style="width:127px" %) |(% style="width:494px" %)PrimaryMeasure 606 +|(% style="width:127px" %) |(% style="width:494px" %)Dataflow (DataflowDefinition) 607 +|(% style="width:127px" %)metadatastructure|(% style="width:494px" %)MetadataTarget 608 +|(% style="width:127px" %) |(% style="width:494px" %)DimensionDescriptorValueTarget 609 +|(% style="width:127px" %) |(% style="width:494px" %)IdentifiableObjectTarget 610 +|(% style="width:127px" %) |(% style="width:494px" %)ReportPeriodTarget 611 +|(% style="width:127px" %) |(% style="width:494px" %)DataSetTarget 612 +|(% style="width:127px" %) |(% style="width:494px" %)ReportStructure 613 +|(% style="width:127px" %) |(% style="width:494px" %)MetadataAttribute 614 +|(% style="width:127px" %) |(% style="width:494px" %)((( 618 618 MetadataStructure 619 619 620 620 (MetadataStructureDefinition) 621 621 ))) 622 -|(% style="width:127px" %) |(% style="width:4 5px" %)Metadataflow (MetadataflowDefinition)623 -|(% style="width:127px" %)process|(% style="width:4 5px" %)Process624 -|(% style="width:127px" %) |(% style="width:4 5px" %)ProcessStep625 -|(% style="width:127px" %) |(% style="width:4 5px" %)Transition626 -|(% style="width:127px" %)registry|(% style="width:4 5px" %)ProvisionAgreement627 -|(% style="width:127px" %) |(% style="width:4 5px" %)AttachmentConstraint628 -|(% style="width:127px" %) |(% style="width:4 5px" %)ContentConstraint629 -|(% style="width:127px" %) |(% style="width:4 5px" %)Subscription630 -|(% style="width:127px" %)mapping|(% style="width:4 5px" %)StructureMap631 -|(% style="width:127px" %) |(% style="width:4 5px" %)StructureSet632 -|(% style="width:127px" %) |(% style="width:4 5px" %)ComponentMap633 -|(% style="width:127px" %) |(% style="width: 1745px" %)ConceptSchemeMap634 -|(% style="width:127px" %) |(% style="width: 1745px" %)OrganisationSchemeMap635 -|(% style="width:127px" %) |(% style="width: 1745px" %)CodelistMap636 -|(% style="width:127px" %) |(% style="width: 1745px" %)CategorySchemeMap637 -|(% style="width:127px" %) |(% style="width: 1745px" %)ReportingTaxonomyMap638 -|(% style="width:127px" %) |(% style="width: 1745px" %)ConceptMap639 -|(% style="width:127px" %) |(% style="width: 1745px" %)OrganisationMap640 -|(% style="width:127px" %) |(% style="width: 1745px" %)CodeMap641 -|(% style="width:127px" %) |(% style="width: 1745px" %)HybridCodelistMap642 -|(% style="width:127px" %) |(% style="width: 1745px" %)CategoryMap643 -|(% style="width:127px" %) |(% style="width: 1745px" %)HybridCodeMap644 -|(% style="width:127px" %) |(% style="width: 1745px" %)ReportingCategoryMap645 -|(% style="width:127px" %)codelist|(% style="width: 1745px" %)Codelist646 -|(% style="width:127px" %) |(% style="width: 1745px" %)HierarchicalCodelist647 -|(% style="width:127px" %) |(% style="width: 1745px" %)Hierarchy648 -|(% style="width:127px" %) |(% style="width: 1745px" %)Hierarchy649 -|(% style="width:127px" %) |(% style="width: 1745px" %)Code650 -|(% style="width:127px" %) |(% style="width: 1745px" %)HierarchicalCode651 -|(% style="width:127px" %) |(% style="width: 1745px" %)Level652 -|(% style="width:127px" %)categoryscheme|(% style="width: 1745px" %)CategoryScheme653 -|(% style="width:127px" %) |(% style="width: 1745px" %)Category654 -|(% style="width:127px" %) |(% style="width: 1745px" %)Categorisation655 -|(% style="width:127px" %) |(% style="width: 1745px" %)ReportingTaxonomy656 -|(% style="width:127px" %) |(% style="width: 1745px" %)ReportingCategory657 -|(% style="width:127px" %)conceptscheme|(% style="width: 1745px" %)ConceptScheme658 -|(% style="width:127px" %) |(% style="width: 1745px" %)Concept659 -|(% style="width:127px" %)transformation|(% style="width: 1745px" %)TransformationScheme660 -|(% style="width:127px" %) |(% style="width: 1745px" %)Transformation661 -|(% style="width:127px" %) |(% style="width: 1745px" %)CustomTypeScheme662 -|(% style="width:127px" %) |(% style="width: 1745px" %)CustomType663 -|(% style="width:127px" %) |(% style="width: 1745px" %)NamePersonalisationScheme664 -|(% style="width:127px" %) |(% style="width: 1745px" %)NamePersonalisation665 -|(% style="width:127px" %) |(% style="width: 1745px" %)VtlCodelistMapping666 -|(% style="width:127px" %) |(% style="width: 1745px" %)VtlConceptMapping667 -|(% style="width:127px" %) |(% style="width: 1745px" %)VtlDataflowMapping668 -|(% style="width:127px" %) |(% style="width: 1745px" %)VtlConceptSchemeMapping669 -|(% style="width:127px" %) |(% style="width: 1745px" %)RulesetScheme670 -|(% style="width:127px" %) |(% style="width: 1745px" %)Ruleset671 -|(% style="width:127px" %) |(% style="width: 1745px" %)UserDefinedOperatorScheme672 -|(% style="width:127px" %) |(% style="width: 1745px" %)UserDefinedOperator619 +|(% style="width:127px" %) |(% style="width:494px" %)Metadataflow (MetadataflowDefinition) 620 +|(% style="width:127px" %)process|(% style="width:494px" %)Process 621 +|(% style="width:127px" %) |(% style="width:494px" %)ProcessStep 622 +|(% style="width:127px" %) |(% style="width:494px" %)Transition 623 +|(% style="width:127px" %)registry|(% style="width:494px" %)ProvisionAgreement 624 +|(% style="width:127px" %) |(% style="width:494px" %)AttachmentConstraint 625 +|(% style="width:127px" %) |(% style="width:494px" %)ContentConstraint 626 +|(% style="width:127px" %) |(% style="width:494px" %)Subscription 627 +|(% style="width:127px" %)mapping|(% style="width:494px" %)StructureMap 628 +|(% style="width:127px" %) |(% style="width:494px" %)StructureSet 629 +|(% style="width:127px" %) |(% style="width:494px" %)ComponentMap 630 +|(% style="width:127px" %) |(% style="width:494px" %)ConceptSchemeMap 631 +|(% style="width:127px" %) |(% style="width:494px" %)OrganisationSchemeMap 632 +|(% style="width:127px" %) |(% style="width:494px" %)CodelistMap 633 +|(% style="width:127px" %) |(% style="width:494px" %)CategorySchemeMap 634 +|(% style="width:127px" %) |(% style="width:494px" %)ReportingTaxonomyMap 635 +|(% style="width:127px" %) |(% style="width:494px" %)ConceptMap 636 +|(% style="width:127px" %) |(% style="width:494px" %)OrganisationMap 637 +|(% style="width:127px" %) |(% style="width:494px" %)CodeMap 638 +|(% style="width:127px" %) |(% style="width:494px" %)HybridCodelistMap 639 +|(% style="width:127px" %) |(% style="width:494px" %)CategoryMap 640 +|(% style="width:127px" %) |(% style="width:494px" %)HybridCodeMap 641 +|(% style="width:127px" %) |(% style="width:494px" %)ReportingCategoryMap 642 +|(% style="width:127px" %)codelist|(% style="width:494px" %)Codelist 643 +|(% style="width:127px" %) |(% style="width:494px" %)HierarchicalCodelist 644 +|(% style="width:127px" %) |(% style="width:494px" %)Hierarchy 645 +|(% style="width:127px" %) |(% style="width:494px" %)Hierarchy 646 +|(% style="width:127px" %) |(% style="width:494px" %)Code 647 +|(% style="width:127px" %) |(% style="width:494px" %)HierarchicalCode 648 +|(% style="width:127px" %) |(% style="width:494px" %)Level 649 +|(% style="width:127px" %)categoryscheme|(% style="width:494px" %)CategoryScheme 650 +|(% style="width:127px" %) |(% style="width:494px" %)Category 651 +|(% style="width:127px" %) |(% style="width:494px" %)Categorisation 652 +|(% style="width:127px" %) |(% style="width:494px" %)ReportingTaxonomy 653 +|(% style="width:127px" %) |(% style="width:494px" %)ReportingCategory 654 +|(% style="width:127px" %)conceptscheme|(% style="width:494px" %)ConceptScheme 655 +|(% style="width:127px" %) |(% style="width:494px" %)Concept 656 +|(% style="width:127px" %)transformation|(% style="width:494px" %)TransformationScheme 657 +|(% style="width:127px" %) |(% style="width:494px" %)Transformation 658 +|(% style="width:127px" %) |(% style="width:494px" %)CustomTypeScheme 659 +|(% style="width:127px" %) |(% style="width:494px" %)CustomType 660 +|(% style="width:127px" %) |(% style="width:494px" %)NamePersonalisationScheme 661 +|(% style="width:127px" %) |(% style="width:494px" %)NamePersonalisation 662 +|(% style="width:127px" %) |(% style="width:494px" %)VtlCodelistMapping 663 +|(% style="width:127px" %) |(% style="width:494px" %)VtlConceptMapping 664 +|(% style="width:127px" %) |(% style="width:494px" %)VtlDataflowMapping 665 +|(% style="width:127px" %) |(% style="width:494px" %)VtlConceptSchemeMapping 666 +|(% style="width:127px" %) |(% style="width:494px" %)RulesetScheme 667 +|(% style="width:127px" %) |(% style="width:494px" %)Ruleset 668 +|(% style="width:127px" %) |(% style="width:494px" %)UserDefinedOperatorScheme 669 +|(% style="width:127px" %) |(% style="width:494px" %)UserDefinedOperator 673 673 674 674 **Table 2: SDMX-IM Packages and Contained Classes** 675 675 ... ... @@ -683,58 +683,49 @@ 683 683 684 684 > urn:sdmx.org.sdmx.infomodel.{package}.{classname}= 685 685 686 -(% style="width:1 038.29px" %)687 -|(% style="width: 191px" %)**SDMX Class**|(% style="width:413px" %)**Key attribute(s)**|(% style="width:431px" %)**Example of URN**688 -|(% style="width: 191px" %)Agency|(% style="width:413px" %)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:431px" %)(((683 +(% style="width:1277.29px" %) 684 +|(% style="width:269px" %)**SDMX Class**|(% style="width:453px" %)**Key attribute(s)**|(% style="width:550px" %)**Example of URN** 685 +|(% style="width:269px" %)Agency|(% style="width:453px" %)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:550px" %)((( 689 689 IMF 690 - 691 -((( 692 -Sub agency in the IMF AGENCIES 693 - 687 +Sub agency in the IMF AGENCIES 694 694 IMF.SubAgency1 695 695 ))) 696 -))) 697 -|(% style="width:191px" %)*ConceptScheme|(% style="width:413px" %)conceptSchemeAgencyId:conceptSchemeId(ve rsion)|(% style="width:431px" %)SDMX:CROSS_DOMAIN_CONCEPTS(1.0) 698 -|(% style="width:191px" %)Concept|(% style="width:413px" %)conceptSchemeAgencyId: 699 -conceptSchemeId(version).conceptId|(% style="width:431px" %)SDMX:CROSS_DOMAIN_CONCEPTS(1.0).FREQ 700 -|(% style="width:191px" %)*Codelist|(% style="width:413px" %)codeListAgencyId:codeListId(version)|(% style="width:431px" %)SDMX:CL_FREQ(1.0) 701 -|(% style="width:191px" %)Code|(% style="width:413px" %)codeListAgencyId:codelistId(version).codeId|(% style="width:431px" %)SDMX:CL_FREQ(1.0).Q 702 -|(% style="width:191px" %)((( 690 +|(% style="width:269px" %)*ConceptScheme|(% style="width:453px" %)conceptSchemeAgencyId:conceptSchemeId(ve rsion)|(% style="width:550px" %)SDMX:CROSS_DOMAIN_CONCEPTS(1.0) 691 +|(% style="width:269px" %)Concept|(% style="width:453px" %)conceptSchemeAgencyId: 692 +conceptSchemeId(version).conceptId|(% style="width:550px" %)SDMX:CROSS_DOMAIN_CONCEPTS(1.0).FREQ 693 +|(% style="width:269px" %)*Codelist|(% style="width:453px" %)codeListAgencyId:codeListId(version)|(% style="width:550px" %)SDMX:CL_FREQ(1.0) 694 +|(% style="width:269px" %)Code|(% style="width:453px" %)codeListAgencyId:codelistId(version).codeId|(% style="width:550px" %)SDMX:CL_FREQ(1.0).Q 695 +|(% style="width:269px" %)((( 703 703 *Hierarchical Codelist 704 -)))|(% style="width:413px" %)hierachicalCodelistAgencyId: hierarchicalCodelistId(version)|(% style="width:431px" %)((( 697 +)))|(% style="width:453px" %)hierachicalCodelistAgencyId: 698 +hierarchicalCodelistId(version)|(% style="width:550px" %)((( 705 705 UNESCO:CL_EXP_SOURCE(1.0(% style="background-color:transparent" %)) 706 706 ))) 707 -|(% style="width: 191px" %)Hierarchy|(% style="width:413px" %)(((701 +|(% style="width:269px" %)Hierarchy|(% style="width:453px" %)((( 708 708 hierachicalcodeListAgencyId: 709 709 hierarchicalcodelistId(version).Hierarchy 710 -)))|(% style="width:431px" %)UNESCO:CL_EXP_SOURCE(1.0). H-C-GOV 711 -|(% style="width:191px" %)Level|(% style="width:413px" %)((( 704 +)))|(% style="width:550px" %)UNESCO:CL_EXP_SOURCE(1.0). 705 +H-C-GOV 706 +|(% style="width:269px" %)Level|(% style="width:453px" %)((( 712 712 hierachicalcodeListAgencyId: 713 713 hierarchicalcodelistId(version).Hierarchy.Level 714 -)))|(% style="width: 431px" %)(((709 +)))|(% style="width:550px" %)((( 715 715 ESTAT:HCL_REGION(1.0).H_1.COUNTRY 716 - 717 - 718 718 ))) 719 -|(% style="width: 191px" %)HierarchicalCode|(% style="width:413px" %)hierachicalCodeListAgencyId: hierarchicalcodelistId(version).hierarchy.hierarc hicalCode|(% style="width:431px" %)UNESCO:CL_EXP_SOURCE(1.0). H-C-GOV.GOV_CODE1720 -|(% style="width: 191px" %)*DataStructure|(% style="width:413px" %)dataStructureDefintitionAgencyId: dataStructureDefintitionId(version)|(% style="width:431px" %)TFFS:EXT_DEBT(1.0)721 -|(% style="width: 191px" %)(((712 +|(% style="width:269px" %)HierarchicalCode|(% style="width:453px" %)hierachicalCodeListAgencyId: hierarchicalcodelistId(version).hierarchy.hierarc hicalCode|(% style="width:550px" %)UNESCO:CL_EXP_SOURCE(1.0). H-C-GOV.GOV_CODE1 713 +|(% style="width:269px" %)*DataStructure|(% style="width:453px" %)dataStructureDefintitionAgencyId: dataStructureDefintitionId(version)|(% style="width:550px" %)TFFS:EXT_DEBT(1.0) 714 +|(% style="width:269px" %)((( 722 722 Dimension 723 - 724 724 Descriptor 725 - 726 726 Measure 727 - 728 728 Descriptor 729 - 730 730 Attribute 731 - 732 732 Descriptor 733 -)))|(% style="width:4 13px" %)(((721 +)))|(% style="width:453px" %)((( 734 734 dataStructureDefinitionAgencyId: dataStructureDefinitionId(version). 735 735 componentListId 736 736 where the componentListId is the name of the class (there is only one occurrence of each in the Data Structure Definition) 737 -)))|(% style="width: 431px" %)(((725 +)))|(% style="width:550px" %)((( 738 738 TFFS:EXT_DEBT(1.0).DimensionDescriptor 739 739 740 740 TFFS:EXT_DEBT(1.0).MeasureDescriptor ... ... @@ -741,284 +741,209 @@ 741 741 742 742 TFFS:EXT_DEBT(1.0).AttributeDescriptor 743 743 ))) 744 -|(% style="width: 191px" %)(((732 +|(% style="width:269px" %)((( 745 745 GroupDimension 746 - 747 747 Descriptor 748 -)))|(% style="width:4 13px" %)(((735 +)))|(% style="width:453px" %)((( 749 749 dataStructureDefinitionAgencyId: dataStructureDefinitionId(version). 750 750 groupDimensionDescriptorId 751 -)))|(% style="width: 431px" %)TFFS:EXT_DEBT(1.0).SIBLING752 -|(% style="width: 191px" %)Dimension|(% style="width:413px" %)(((738 +)))|(% style="width:550px" %)TFFS:EXT_DEBT(1.0).SIBLING 739 +|(% style="width:269px" %)Dimension|(% style="width:453px" %)((( 753 753 dataStructureDefinitionAgencyId: dataStructureDefinition (version). 754 754 dimensionId 755 -)))|(% style="width: 431px" %)TFFS:EXT_DEBT(1.0).FREQ756 -|(% style="width: 191px" %)TimeDimension|(% style="width:413px" %)(((742 +)))|(% style="width:550px" %)TFFS:EXT_DEBT(1.0).FREQ 743 +|(% style="width:269px" %)TimeDimension|(% style="width:453px" %)((( 757 757 dataStructureDefinitionAgencyId: dataStructureDefinition (version). 758 758 timeDimensionId 759 -)))|(% style="width:431px" %)TFFS:EXT_DEBT(1.0).TIME_PERIOD 760 -|(% style="width:191px" %)Measure Dimension|(% style="width:413px" %)dataStructureDefinitionAgencyId: dataStructureDefinition (version).|(% style="width:431px" %)TFFS:EXT_DEBT(1.0).STOCK_FLOW 761 - 762 -(% style="width:987.294px" %) 763 -|(% style="width:170px" %) |(% style="width:367px" %)measureDimensionId|(% style="width:446px" %) 764 -|(% style="width:170px" %)DataAttrribute|(% style="width:367px" %)dataStructureDefinitionAgencyId: dataStructureDefinition (version). dataAttributeId|(% style="width:446px" %)TFFS:EXT_DEBT(1.0).OBS_STATUS 765 -|(% style="width:170px" %)PrimaryMeasure|(% style="width:367px" %)((( 746 +)))|(% style="width:550px" %)TFFS:EXT_DEBT(1.0).TIME_PERIOD 747 +|(% style="width:269px" %)Measure Dimension|(% style="width:453px" %)dataStructureDefinitionAgencyId: dataStructureDefinition (version). 748 +measureDimensionId|(% style="width:550px" %)TFFS:EXT_DEBT(1.0).STOCK_FLOW 749 +|(% style="width:269px" %)DataAttrribute|(% style="width:453px" %)dataStructureDefinitionAgencyId: dataStructureDefinition (version). dataAttributeId|(% style="width:550px" %)TFFS:EXT_DEBT(1.0).OBS_STATUS 750 +|(% style="width:269px" %)PrimaryMeasure|(% style="width:453px" %)((( 766 766 dataStructureDefinitionAgencyId: dataStructureDefinition (version). 767 767 primaryMeasureId 768 -)))|(% style="width:446px" %)TFFS:EXT_DEBT(1.0).OBS_VALUE 769 -|(% style="width:170px" %)((( 770 -*Category 771 - 772 -Scheme 773 -)))|(% style="width:367px" %)categorySchemeAgencyId: categorySchemeId(version)|(% style="width:446px" %)IMF:SDDS(1.0) 774 -|(% style="width:170px" %)Category|(% style="width:367px" %)categorySchemeAgencyId: categorySchemeId(version). categoryId.categoryId categoryId.categoryId etc.|(% style="width:446px" %)((( 753 +)))|(% style="width:550px" %)TFFS:EXT_DEBT(1.0).OBS_VALUE 754 +|(% style="width:269px" %)((( 755 +*Category Scheme 756 +)))|(% style="width:453px" %)categorySchemeAgencyId: 757 +categorySchemeId(version)|(% style="width:550px" %)IMF:SDDS(1.0) 758 +|(% style="width:269px" %)Category|(% style="width:453px" %)categorySchemeAgencyId: 759 +categorySchemeId(version). 760 +categoryId.categoryId categoryId.categoryId etc.|(% style="width:550px" %)((( 775 775 IMF:SDDS(1.0): 776 - 777 777 level_1_category.level_2_category … 778 778 ))) 779 -|(% style="width:170px" %)((( 780 -*Reporting 781 - 782 -Taxonomy 783 -)))|(% style="width:367px" %)reportingTaxonomyAgencyId: reportingTaxonomyId(version)|(% style="width:446px" %) IMF:REP_1(1.0) 784 -|(% style="width:170px" %)ReportingCategory|(% style="width:367px" %)reportingTaxonomyAgencyId: reportingTaxonomyId(version) reportingcategoryId.reportingcategoryId|(% style="width:446px" %)((( 764 +|(% style="width:269px" %)((( 765 +*Reporting Taxonomy 766 +)))|(% style="width:453px" %)reportingTaxonomyAgencyId: reportingTaxonomyId(version)|(% style="width:550px" %) IMF:REP_1(1.0) 767 +|(% style="width:269px" %)ReportingCategory|(% style="width:453px" %)reportingTaxonomyAgencyId: reportingTaxonomyId(version) reportingcategoryId.reportingcategoryId|(% style="width:550px" %)((( 785 785 IMF:REP_1(1.0): 786 - 787 787 level_1_repcategory.level_2_repcategory … 788 788 ))) 789 -|(% style="width:170px" %)*Categorisation|(% style="width:367px" %)categorisationAgencyId: categorisationId(version)|(% style="width:446px" %)IMF:cat001(1.0) 790 -|(% style="width:170px" %)((( 791 -*Organisation 771 +|(% style="width:269px" %)*Categorisation|(% style="width:453px" %)categorisationAgencyId: categorisationId(version)|(% style="width:550px" %)IMF:cat001(1.0) 772 +|(% style="width:269px" %)((( 773 +*Organisation Unit Scheme 774 +)))|(% style="width:453px" %)organisationUnitSchemeAgencyId: organisationUnitSchemeId(version)|(% style="width:550px" %)ECB:ORGANISATIONS(1.0) 775 +|(% style="width:269px" %)Organisation Unit|(% style="width:453px" %)organisationUnitSchemeAgencyId: organisationUnitSchemeId(version). organisationUnitId|(% style="width:550px" %)ECB:ORGANISATIONS(1.0).1F 776 +|(% style="width:269px" %)*AgencyScheme|(% style="width:453px" %)agencySchemeAgencyId: agencySchemeId(version)|(% style="width:550px" %)ECB:AGENCIES(1.0) 792 792 793 -Unit Scheme 794 -)))|(% style="width:367px" %)organisationUnitSchemeAgencyId: organisationUnitSchemeId(version)|(% style="width:446px" %)ECB:ORGANISATIONS(1.0) 795 -|(% style="width:170px" %)Organisation Unit|(% style="width:367px" %)organisationUnitSchemeAgencyId: organisationUnitSchemeId(version). organisationUnitId|(% style="width:446px" %)ECB:ORGANISATIONS(1.0).1F 796 -|(% style="width:170px" %)*AgencyScheme|(% style="width:367px" %)agencySchemeAgencyId: agencySchemeId(version)|(% style="width:446px" %)ECB:AGENCIES(1.0) 797 - 798 - 799 - 800 -|Agency|agencySchemeAgencyId: agencySchemeId(version). agencyId|ECB:AGENCY(1.0).AA 801 -|((( 802 -*DataProvider 803 - 804 -Scheme 805 -)))|dataProviderSchemeAgencyId: dataProviderSchemeId(version)|SDMX:DATA_PROVIDERS(1.0) 806 -|DataProvider|dataProviderSchemeAgencyId: dataProviderSchemeId(version) dataProviderId|SDMX:DATA_PROVIDERS(1.0).PROVIDER_1 807 -|((( 808 -*DataConsumer 809 - 810 -Scheme 811 -)))|dataConsumerSchemeAgencyId: dataConsumerSchemeId(version)|SDMX:DATA_CONSUMERS(1.0) 812 -|Data Consumer|dataConsumerSchemeAgencyId: dataConsumerSchemeId(version) dataConsumerId|SDMX:DATA_CONSUMERS(1.0).CONSUMER_1 813 -|((( 814 -*Metadata 815 - 816 -Structure 817 -)))|MSDAgencyId:MSDId(version)|IMF:SDDS_MSD(1.0) 818 -|MetadataTarget|((( 778 +(% style="width:1274.29px" %) 779 +|(% style="width:262px" %)Agency|(% style="width:369px" %)agencySchemeAgencyId: agencySchemeId(version). agencyId|(% style="width:535px" %)ECB:AGENCY(1.0).AA 780 +|(% style="width:262px" %)((( 781 +*DataProvider Scheme 782 +)))|(% style="width:369px" %)dataProviderSchemeAgencyId: dataProviderSchemeId(version)|(% style="width:535px" %)SDMX:DATA_PROVIDERS(1.0) 783 +|(% style="width:262px" %)DataProvider|(% style="width:369px" %)dataProviderSchemeAgencyId: dataProviderSchemeId(version) dataProviderId|(% style="width:535px" %)SDMX:DATA_PROVIDERS(1.0).PROVIDER_1 784 +|(% style="width:262px" %)((( 785 +*DataConsumer Scheme 786 +)))|(% style="width:369px" %)dataConsumerSchemeAgencyId: dataConsumerSchemeId(version)|(% style="width:535px" %)SDMX:DATA_CONSUMERS(1.0) 787 +|(% style="width:262px" %)Data Consumer|(% style="width:369px" %)dataConsumerSchemeAgencyId: dataConsumerSchemeId(version) dataConsumerId|(% style="width:535px" %)SDMX:DATA_CONSUMERS(1.0).CONSUMER_1 788 +|(% style="width:262px" %)((( 789 +*Metadata Structure 790 +)))|(% style="width:369px" %)MSDAgencyId:MSDId(version)|(% style="width:535px" %)IMF:SDDS_MSD(1.0) 791 +|(% style="width:262px" %)MetadataTarget|(% style="width:369px" %)((( 819 819 MSDAgencyId: 820 - 821 821 MSDId(version).metadataTargetId 822 -)))|IMF:SDDS_MSD(1.0).AGENCY 823 -|((( 794 +)))|(% style="width:535px" %)IMF:SDDS_MSD(1.0).AGENCY 795 +|(% style="width:262px" %)((( 824 824 Dimension 825 - 826 826 DescriptorValues 827 - 828 828 Target 829 -)))|((( 799 +)))|(% style="width:369px" %)((( 830 830 MSDAgencyId: MSDId(version). 831 - 832 832 metadataTargetId.keyDescriptorValueTargetId 833 -)))|IMF:SDDS_MSD(1.0).AGENCY.KEY 834 -|Identifiable ObjectTarget|((( 802 +)))|(% style="width:535px" %)IMF:SDDS_MSD(1.0).AGENCY.KEY 803 +|(% style="width:262px" %)Identifiable Object Target|(% style="width:369px" %)((( 804 +MSDAgencyId: MSDId(version).metadataTargetId.identifiableObjectTargetId 805 +)))|(% style="width:535px" %)IMF:SDDS_MSD(1.0).AGENCY.STR-OBJECT 806 +|(% style="width:262px" %)DataSetTarget|(% style="width:369px" %)((( 835 835 MSDAgencyId: 808 +MSDId(version).metadataTargetId.dataSetTargetId 809 +)))|(% style="width:535px" %)IMF:SDDS_MSD(1.0).AGENCY.D1101 810 +|(% style="width:262px" %)PeportPeriod Target|(% style="width:369px" %)((( 811 +MSDAgencyId: MSDId(version).metadataTargetId.reportPeriodTargetId 812 +)))|(% style="width:535px" %)IMF:SDDS_MSD(1.0).AGENCY.REP_PER 836 836 837 -MSDId(version).metadataTargetId.identifiable 838 - 839 -ObjectTargetId 840 -)))|IMF:SDDS_MSD(1.0).AGENCY.STR-OBJECT 841 -|DataSetTarget|((( 842 -MSDAgencyId: 843 - 844 -MSDId(version).metadataTargetId.dataSet 845 - 846 -TargetId 847 -)))|IMF:SDDS_MSD(1.0).AGENCY.D1101 848 -|PeportPeriod Target|((( 849 -MSDAgencyId: 850 - 851 -MSDId(version).metadataTargetId.reportPeriod 852 - 853 -TargetId 854 -)))|IMF:SDDS_MSD(1.0).AGENCY.REP_PER 855 - 856 - 857 - 858 -|((( 814 +(% style="width:1277.29px" %) 815 +|(% style="width:270px" %)((( 859 859 ReportStructure 860 - 861 - 862 -)))|((( 863 -MSDAgencyId: 864 - 865 -MSDId(version).reportStructureId 866 -)))|IMF:SDDS_MSD(1.0).AGENCY_REPORT 867 -|((( 868 -Metadata 869 - 870 -Attribute 871 -)))|((( 872 -MSDAgencyId: 873 - 874 -MSDId(version).reportStructureId.metadataattri buteID 875 -)))|IMF:SDDS_MSD(1.0).AGENCY_REPORT.COMPILATION 876 -|*Dataflow|dataflowAgencyId: dataflowId(version)|TFFS:CRED_EXT_DEBT(1.0) 877 -|*Provision Agreement|((( 817 +)))|(% style="width:454px" %)((( 818 +MSDAgencyId: MSDId(version).reportStructureId 819 +)))|(% style="width:549px" %)IMF:SDDS_MSD(1.0).AGENCY_REPORT 820 +|(% style="width:270px" %)((( 821 +Metadata Attribute 822 +)))|(% style="width:454px" %)((( 823 +MSDAgencyId: MSDId(version).reportStructureId.metadataattri buteID 824 +)))|(% style="width:549px" %)IMF:SDDS_MSD(1.0).AGENCY_REPORT.COMPILATION 825 +|(% style="width:270px" %)*Dataflow|(% style="width:454px" %)dataflowAgencyId: dataflowId(version)|(% style="width:549px" %)TFFS:CRED_EXT_DEBT(1.0) 826 +|(% style="width:270px" %)*Provision Agreement|(% style="width:454px" %)((( 878 878 provisionAgreementAgencyId:provisionAgreem entId(version) 879 - 880 - 881 -)))|((( 828 +)))|(% style="width:549px" %)((( 882 882 TFFS:CRED_EXT_DEBT_AB(1.0) 883 - 884 - 885 - 886 886 ))) 887 -|((( 888 -*Content 889 - 890 -Constraint 891 -)))|constraintAgencyId:ContentConstraintId(versio n)|TFFS:CREDITOR_DATA_CONTENT(1.0) 892 -|((( 893 -*Attachment 894 - 895 -Constraint 896 -)))|((( 831 +|(% style="width:270px" %)((( 832 +*Content Constraint 833 +)))|(% style="width:454px" %)constraintAgencyId:ContentConstraintId(versio n)|(% style="width:549px" %)TFFS:CREDITOR_DATA_CONTENT(1.0) 834 +|(% style="width:270px" %)((( 835 +*Attachment Constraint 836 +)))|(% style="width:454px" %)((( 897 897 constraintAgencyId: 898 898 899 899 attachmentConstraintId(version) 900 -)))|TFFS:CREDITOR_DATA_ATTACHMENT_CONSTRAINT_ONE(1.0) 901 -|*Metadataflow|metadataflowAgencyId: metadataflowId(version)|IMF:SDDS_FLOW(1.0) 902 -|*StructureSet|structureSetAgencyId: structureSetId(version)|SDMX:BOP_STRUCTURES(1.0) 903 -|StructureMap|structureSetAgencyId: structureSetId(version). structureMapId|SDMX:BOP_STRUCTURES(1.0).TABLE1_TABLE2 904 -|Component Map|((( 840 +)))|(% style="width:549px" %)TFFS:CREDITOR_DATA_ATTACHMENT_CONSTRAINT_ONE(1.0) 841 +|(% style="width:270px" %)*Metadataflow|(% style="width:454px" %)metadataflowAgencyId: metadataflowId(version)|(% style="width:549px" %)IMF:SDDS_FLOW(1.0) 842 +|(% style="width:270px" %)*StructureSet|(% style="width:454px" %)structureSetAgencyId: structureSetId(version)|(% style="width:549px" %)SDMX:BOP_STRUCTURES(1.0) 843 +|(% style="width:270px" %)StructureMap|(% style="width:454px" %)structureSetAgencyId: structureSetId(version). structureMapId|(% style="width:549px" %)SDMX:BOP_STRUCTURES(1.0).TABLE1_TABLE2 844 +|(% style="width:270px" %)Component Map|(% style="width:454px" %)((( 905 905 structureSetAgencyId: structureSetId(version). 906 906 907 907 structureMapId. componentMapId 908 -)))|SDMX:BOP_STRUCTURES(1.0).TABLE1_TABLE2. REFAREA_REPCOUNTRY 909 -|CodelistMap|structureSetAgencyId: structureSetId(version). codelistMapId|SDMX:BOP_STRUCTURES(1.0).CLREFAREA_CLREPCOUNTRY 910 -|CodeMap|structureSetAgencyId: structureSetId(version).|SDMX:BOP_STRUCTURES(1.0).CLREFAREA_CLREPCOUNTRY. DE_GER 911 - 912 - 913 - 914 -| |((( 848 +)))|(% style="width:549px" %)SDMX:BOP_STRUCTURES(1.0).TABLE1_TABLE2. REFAREA_REPCOUNTRY 849 +|(% style="width:270px" %)CodelistMap|(% style="width:454px" %)structureSetAgencyId: structureSetId(version). codelistMapId|(% style="width:549px" %)SDMX:BOP_STRUCTURES(1.0).CLREFAREA_CLREPCOUNTRY 850 +|(% style="width:270px" %)CodeMap|(% style="width:454px" %)structureSetAgencyId: structureSetId(version). 915 915 codeListMapId. 852 +codeMapId|(% style="width:549px" %)SDMX:BOP_STRUCTURES(1.0).CLREFAREA_CLREPCOUNTRY. DE_GER 916 916 917 -codeMapId 918 -)))| 919 -|((( 920 -Category 921 - 922 -SchemeMap 923 -)))|structureSetAgencyId: structureSetId(version). categorySchemeMapId|SDMX:BOP_STRUCTURES(1.0).SDMX_EUROSTAT 924 -|CategoryMap|structureSetAgencyId: structureSetId(version). categorySchemeMapId. categoryMapId|SDMX:BOP_STRUCTURES(1.0).SDMX_EUROSTAT.TOURISM_M AP 925 -|Organisation SchemeMap|structureSetAgencyId: structureSetId(version). organisationSchemeMapId|SDMX:BOP_STRUCTURES(1.0).DATA_PROVIDER_MAP 926 -|Organisation Map|structureSetAgencyId: structureSetId(version). organisationSchemeMapId. organisationMapId|SDMX:BOP_STRUCTURES(1.0).DATA_PROVIDER_MAP.IMF_1C0 927 -|((( 854 +(% style="width:1279.29px" %) 855 +|(% style="width:271px" %)((( 856 +CategorySchemeMap 857 +)))|(% style="width:453px" %)structureSetAgencyId: structureSetId(version). categorySchemeMapId|(% style="width:551px" %)SDMX:BOP_STRUCTURES(1.0).SDMX_EUROSTAT 858 +|(% style="width:271px" %)CategoryMap|(% style="width:453px" %)structureSetAgencyId: structureSetId(version). categorySchemeMapId. categoryMapId|(% style="width:551px" %)SDMX:BOP_STRUCTURES(1.0).SDMX_EUROSTAT.TOURISM_MAP 859 +|(% style="width:271px" %)Organisation SchemeMap|(% style="width:453px" %)structureSetAgencyId: structureSetId(version). organisationSchemeMapId|(% style="width:551px" %)SDMX:BOP_STRUCTURES(1.0).DATA_PROVIDER_MAP 860 +|(% style="width:271px" %)Organisation Map|(% style="width:453px" %)structureSetAgencyId: structureSetId(version). organisationSchemeMapId. organisationMapId|(% style="width:551px" %)SDMX:BOP_STRUCTURES(1.0).DATA_PROVIDER_MAP.IMF_1C0 861 +|(% style="width:271px" %)((( 928 928 Concept 929 929 930 930 SchemeMap 931 -)))|structureSetAgencyId: structureSetId(version). conceptSchemeMapId|SDMX:BOP_STRUCTURES(1.0).SDMX_OECD 932 -|ConceptMap|((( 865 +)))|(% style="width:453px" %)structureSetAgencyId: structureSetId(version). conceptSchemeMapId|(% style="width:551px" %)SDMX:BOP_STRUCTURES(1.0).SDMX_OECD 866 +|(% style="width:271px" %)ConceptMap|(% style="width:453px" %)((( 933 933 structureSetAgencyId: structureSetId(version). conceptSchemeMapId. 934 - 935 935 conceptMapId 936 - 937 - 938 -)))|SDMX:BOP_STRUCTURES(1.0).SDMX_OECD.COVERAGE_AVAI LABILITY 939 -|((( 940 -Reporting 941 - 942 -TaxonomyMap 943 -)))|structureSetAgencyId: structureSetId(version). reportingTaxonomyMapId|SDMX:BOP_STRUCTURES(1.0).TAXMAP 944 -|((( 945 -Reporting 946 - 947 -CategoryMap 948 -)))|((( 869 +)))|(% style="width:551px" %)SDMX:BOP_STRUCTURES(1.0).SDMX_OECD.COVERAGE_AVAI LABILITY 870 +|(% style="width:271px" %)((( 871 +ReportingTaxonomyMap 872 +)))|(% style="width:453px" %)structureSetAgencyId: structureSetId(version). reportingTaxonomyMapId|(% style="width:551px" %)SDMX:BOP_STRUCTURES(1.0).TAXMAP 873 +|(% style="width:271px" %)((( 874 +ReportingCategoryMap 875 +)))|(% style="width:453px" %)((( 949 949 structureSetAgencyId: structureSetId(version). 950 - 951 951 reportngCategoryId 952 -)))|SDMX:BOP_STRUCTURES(1.0).TAXMAP.TOPCAT 878 +)))|(% style="width:551px" %)SDMX:BOP_STRUCTURES(1.0).TAXMAP.TOPCAT 953 953 954 - 955 - 956 -|((( 957 -HybridCodelist 958 - 959 -Map 960 -)))|structureSetAgencyId: structureSetId(version). hybridCodelistMapId.|SDMX:BOP_STRUCTURES(1.0).COUNTRY_HIERARCHYMAP 961 -|HybridCodeMap|structureSetAgencyId: structureSetId(version). hybridCodelistMapId. hybridCodeMapId|SDMX:BOP_STRUCTURES(1.0).COUNTRY_HIERARCHYMAP.CO DEMAP1 962 -|*Process|processAgencyId: processId{version]|BIS:PROCESS1(1.0) 963 -|ProcessStep|((( 880 +(% style="width:1282.29px" %) 881 +|(% style="width:272px" %)((( 882 +HybridCodelistMap 883 +)))|(% style="width:450px" %)structureSetAgencyId: structureSetId(version). 884 +hybridCodelistMapId.|(% style="width:557px" %)SDMX:BOP_STRUCTURES(1.0).COUNTRY_HIERARCHYMAP 885 +|(% style="width:272px" %)HybridCodeMap|(% style="width:450px" %)structureSetAgencyId: structureSetId(version). hybridCodelistMapId. hybridCodeMapId|(% style="width:557px" %)SDMX:BOP_STRUCTURES(1.0).COUNTRY_HIERARCHYMAP.CO DEMAP1 886 +|(% style="width:272px" %)*Process|(% style="width:450px" %)processAgencyId: processId{version]|(% style="width:557px" %)BIS:PROCESS1(1.0) 887 +|(% style="width:272px" %)ProcessStep|(% style="width:450px" %)((( 964 964 processAgencyId: processId(version). 965 - 966 966 processStepId 967 -)))|BIS:PROCESS1(1.0).STEP1 968 -|Transition|((( 890 +)))|(% style="width:557px" %)BIS:PROCESS1(1.0).STEP1 891 +|(% style="width:272px" %)Transition|(% style="width:450px" %)((( 969 969 processAgencyId: processId(version). 970 - 971 971 processStepId transitionId 972 -)))|BIS:PROCESS1(1.0).STEP1.TRANSITION1 973 -|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. 974 -|((( 975 -*Transformation 976 - 977 -Scheme 978 -)))|transformationSchemeAgencyId transformationSchemeId(version)|ECB: TRANSFORMATION_SCHEME(1.0) 979 -|Transformation|((( 894 +)))|(% style="width:557px" %)BIS:PROCESS1(1.0).STEP1.TRANSITION1 895 +|(% style="width:272px" %)Subscription|(% style="width:450px" %)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.|(% style="width:557px" %)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. 896 +|(% style="width:272px" %)((( 897 +*Transformation Scheme 898 +)))|(% style="width:450px" %)transformationSchemeAgencyId transformationSchemeId(version)|(% style="width:557px" %)ECB: TRANSFORMATION_SCHEME(1.0) 899 +|(% style="width:272px" %)Transformation|(% style="width:450px" %)((( 980 980 transformationSchemeAgencyId transformationSchemeId(version) 981 - 982 982 transformationId 983 -)))|ECB:TRANSFORMATION_SCHEME(1.0).TRANS_1 984 -|CustomType Scheme|customTypeSchemeAgencyId customTypeSchemeId(version)|ECB:CUSTOM_TYPE_SCHEME(1.0) 902 +)))|(% style="width:557px" %)ECB:TRANSFORMATION_SCHEME(1.0).TRANS_1 903 +|(% style="width:272px" %)CustomType Scheme|(% style="width:450px" %)customTypeSchemeAgencyId customTypeSchemeId(version)|(% style="width:557px" %)ECB:CUSTOM_TYPE_SCHEME(1.0) 985 985 986 - 987 - 988 -|CustomType|customTypeSchemeAgencyId customTypeSchemeId(version) customTypeId|ECB: CUSTOM_TYPE_SCHEME(1.0).CUSTOM_TYPE_1 989 -|((( 905 +(% style="width:1281.29px" %) 906 +|(% style="width:275px" %)CustomType|(% style="width:450px" %)customTypeSchemeAgencyId customTypeSchemeId(version) customTypeId|(% style="width:552px" %)ECB: CUSTOM_TYPE_SCHEME(1.0).CUSTOM_TYPE_1 907 +|(% style="width:275px" %)((( 990 990 Name 991 - 992 992 Personalisation 993 - 994 994 Scheme 995 -)))|namePersonalisationSchemeAgencyId namePersonalisationSchemeId(version)|ECB:PSN_SCHEME(1.0) 996 -|((( 911 +)))|(% style="width:450px" %)namePersonalisationSchemeAgencyId namePersonalisationSchemeId(version)|(% style="width:552px" %)ECB:PSN_SCHEME(1.0) 912 +|(% style="width:275px" %)((( 997 997 Name 998 - 999 999 Personalisation 1000 -)))|namePersonalisationSchemeAgencyId namePersonalisationSchemeId(version) namePersonalisationId|ECB:PSN_SCHEME(1.0).PSN1234 1001 -|VtlMapping Scheme|vtlMappingSchemeAgencyId VtlMappingSchemeId(version)|ECB:CLIST_MP(2.0) 1002 -|VtlCodelist Mapping|vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlCodelistMappingId|ECB:CLIST_MP(2.0).ABZ 1003 -|VtlConcept Mapping|vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlConceptMappingId|ECB:CLIST_MP(1.0).XYA 1004 -|VtlDataflow Mapping|vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlDataflowMappingId|ECB:CLIST_MP(1.0).MOQ 1005 -|((( 915 +)))|(% style="width:450px" %)namePersonalisationSchemeAgencyId namePersonalisationSchemeId(version) 916 +namePersonalisationId|(% style="width:552px" %)ECB:PSN_SCHEME(1.0).PSN1234 917 +|(% style="width:275px" %)VtlMapping Scheme|(% style="width:450px" %)vtlMappingSchemeAgencyId VtlMappingSchemeId(version)|(% style="width:552px" %)ECB:CLIST_MP(2.0) 918 +|(% style="width:275px" %)VtlCodelist Mapping|(% style="width:450px" %)vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlCodelistMappingId|(% style="width:552px" %)ECB:CLIST_MP(2.0).ABZ 919 +|(% style="width:275px" %)VtlConcept Mapping|(% style="width:450px" %)vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlConceptMappingId|(% style="width:552px" %)ECB:CLIST_MP(1.0).XYA 920 +|(% style="width:275px" %)VtlDataflow Mapping|(% style="width:450px" %)vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlDataflowMappingId|(% style="width:552px" %)ECB:CLIST_MP(1.0).MOQ 921 +|(% style="width:275px" %)((( 1006 1006 VtlConcept 1007 1007 1008 1008 SchemeMapping 1009 -)))|vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlConceptSchemeId|ECB:CLIST_MP(1.0).Z11 1010 -|RulesetScheme|rulesetSchemeAgencyId rulesetSchemeId(version)|ECB:RULESET_23(1.0) 1011 -|Ruleset|rulesetSchemeAgencyId rulesetSchemeId(version) rulesetId|ECB:RULESET_23(1.0).SET111 1012 -|((( 1013 -UserDefined 925 +)))|(% style="width:450px" %)vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlConceptSchemeId|(% style="width:552px" %)ECB:CLIST_MP(1.0).Z11 926 +|(% style="width:275px" %)RulesetScheme|(% style="width:450px" %)rulesetSchemeAgencyId rulesetSchemeId(version)|(% style="width:552px" %)ECB:RULESET_23(1.0) 927 +|(% style="width:275px" %)Ruleset|(% style="width:450px" %)rulesetSchemeAgencyId rulesetSchemeId(version) rulesetId|(% style="width:552px" %)ECB:RULESET_23(1.0).SET111 928 +|(% style="width:275px" %)((( 929 +UserDefinedOperatorScheme 930 +)))|(% style="width:450px" %)userDefinedOperatorSchemeAgencyId userDefinedOperatorSchemeId(version)|(% style="width:552px" %)ECB:OS_CALC(1.2) 931 +|(% style="width:275px" %)UserDefined Operator|(% style="width:450px" %)userDefinedOperatorSchemeAgencyId userDefinedOperatorSchemeId(version) usserDefinedOperatorId|(% style="width:552px" %)ECB:OS_CALC(1.2).OS267 1014 1014 1015 -OperatorScheme 1016 -)))|userDefinedOperatorSchemeAgencyId userDefinedOperatorSchemeId(version)|ECB:OS_CALC(1.2) 1017 -|UserDefined Operator|userDefinedOperatorSchemeAgencyId userDefinedOperatorSchemeId(version) usserDefinedOperatorId|ECB:OS_CALC(1.2).OS267 933 +**Table 3: Table of identification components for SDMX Identifiable Artefacts** 1018 1018 1019 -7**Table 3: Table of identification components for SDMX Identifiable Artefacts** 1020 - 1021 - 1022 1022 = 7 Implementation Notes = 1023 1023 1024 1024 == 7.1 Structural Definition Metadata == ... ... @@ -1039,109 +1039,72 @@ 1039 1039 1040 1040 The following table lists the Maintainable Artefacts. 1041 1041 1042 -|(% colspan="4" %)**Maintainable Artefacts**|(% colspan="2" %)**Content**| 1043 -|(% colspan="2" %)**Abstract Class**|(% colspan="2" %)**Concrete Class**|(% colspan="2" %) | 1044 -|(% colspan="2" %)Item Scheme|(% colspan="2" %)Codelist|(% colspan="2" %)Code| 1045 -|(% colspan="2" %) |(% colspan="2" %)Concept Scheme|(% colspan="2" %)Concept| 1046 -|(% colspan="2" %) |(% colspan="2" %)Category Scheme|(% colspan="2" %)Category| 1047 -|(% colspan="2" %) |(% colspan="2" %)Organisation Unit Scheme|(% colspan="2" %)Organisation Unit| 1048 -|(% colspan="2" %) |(% colspan="2" %)Agency Scheme|(% colspan="2" %)Agency| 1049 -|(% colspan="2" %) |(% colspan="2" %)Data Provider Scheme|(% colspan="2" %)Data Provider| 1050 -|(% colspan="2" %) |(% colspan="2" %)Data Consumer Scheme|(% colspan="2" %)Data Consumer| 1051 -|(% colspan="2" %) |(% colspan="2" %)Reporting Taxonomy|(% colspan="2" %)Reporting Category| 1052 -|(% colspan="2" %) |(% colspan="2" %)Transformation Scheme|(% colspan="2" %)Transformation| 1053 -|(% colspan="2" %) |(% colspan="2" %)Custom Type Scheme|(% colspan="2" %)Custom Type| 1054 -| |(% colspan="4" %)**Maintainable Artefacts**|(% colspan="2" %)**Content** 1055 -| |(% colspan="2" %)**Abstract Class**|(% colspan="2" %)**Concrete Class**|(% colspan="2" %) 1056 -| |(% colspan="2" %) |(% colspan="2" %)Name Personalisation Scheme|(% colspan="2" %)Name Personalisation 1057 -| |(% colspan="2" %) |(% colspan="2" %)Vtl Mapping Scheme|(% colspan="2" %)Vtl Codelist Mapping 1058 -| |(% colspan="2" %) |(% colspan="2" %) |(% colspan="2" %)Vtl Concept Mapping 1059 -| |(% colspan="2" %) |(% colspan="2" %) |(% colspan="2" %)Vtl Dataflow Mapping 1060 -| |(% colspan="2" %) |(% colspan="2" %) |(% colspan="2" %)((( 1061 -Vtl Concept Scheme 1062 - 1063 -Mapping 1064 -))) 1065 -| |(% colspan="2" %) |(% colspan="2" %)Ruleset Scheme|(% colspan="2" %)Ruleset 1066 -| |(% colspan="2" %) |(% colspan="2" %)User Defined Operator Scheme|(% colspan="2" %)User Defined Operator 1067 -| |(% colspan="2" %) |(% colspan="2" %) |(% colspan="2" %) 1068 -| |(% colspan="2" %)Structure|(% colspan="2" %)Data Structure Definition|(% colspan="2" %)((( 955 +(% style="width:640.294px" %) 956 +|(% colspan="2" rowspan="1" style="width:186px" %)**Maintainable Artefacts**|(% style="width:206px" %)**Content** 957 +|(% style="width:171px" %)**Abstract Class**|(% style="width:232px" %)**Concrete Class**|(% style="width:206px" %) 958 +|(% style="width:171px" %)Item Scheme|(% style="width:232px" %)Codelist|(% style="width:206px" %)Code 959 +|(% style="width:171px" %) |(% style="width:232px" %)Concept Scheme|(% style="width:206px" %)Concept 960 +|(% style="width:171px" %) |(% style="width:232px" %)Category Scheme|(% style="width:206px" %)Category 961 +|(% style="width:171px" %) |(% style="width:232px" %)Organisation Unit Scheme|(% style="width:206px" %)Organisation Unit 962 +|(% style="width:171px" %) |(% style="width:232px" %)Agency Scheme|(% style="width:206px" %)Agency 963 +|(% style="width:171px" %) |(% style="width:232px" %)Data Provider Scheme|(% style="width:206px" %)Data Provider 964 +|(% style="width:171px" %) |(% style="width:232px" %)Data Consumer Scheme|(% style="width:206px" %)Data Consumer 965 +|(% style="width:171px" %) |(% style="width:232px" %)Reporting Taxonomy|(% style="width:206px" %)Reporting Category 966 +|(% style="width:171px" %) |(% style="width:232px" %)Transformation Scheme|(% style="width:206px" %)Transformation 967 +|(% style="width:171px" %) |(% style="width:232px" %)Custom Type Scheme|(% style="width:206px" %)Custom Type 968 +|(% style="width:171px" %) |(% style="width:232px" %)Name Personalisation Scheme|(% style="width:206px" %)Name Personalisation 969 +|(% style="width:171px" %) |(% style="width:232px" %)Vtl Mapping Scheme|(% style="width:206px" %)Vtl Codelist Mapping 970 +|(% style="width:171px" %) |(% style="width:232px" %) |(% style="width:206px" %)Vtl Dataflow Mapping 971 +|(% style="width:171px" %) |(% style="width:232px" %) |(% style="width:206px" %)Vtl Concept Scheme Mapping 972 +|(% style="width:171px" %) |(% style="width:232px" %)Ruleset Scheme|(% style="width:206px" %)Ruleset 973 +|(% style="width:171px" %) |(% style="width:232px" %)User Defined Operator Scheme|(% style="width:206px" %)User Defined Operator 974 +|(% style="width:171px" %) |(% style="width:232px" %) |(% style="width:206px" %)User Defined Operator 975 +|(% style="width:171px" %)Structure|(% style="width:232px" %)Data Structure Definition|(% style="width:206px" %)((( 1069 1069 Dimension Descriptor 1070 - 1071 1071 Group Dimension 1072 - 1073 1073 Descriptor 1074 - 1075 1075 Dimension 1076 - 1077 1077 Measure Dimension 1078 - 1079 1079 Time Dimension 1080 - 1081 1081 Attribute Descriptor 1082 - 1083 1083 Data Attribute 1084 - 1085 1085 Measure Descriptor 1086 - 1087 1087 Primary Measure 1088 1088 ))) 1089 -| |(% colspan="2" %) |(% colspan="2" %)Metadata Structure Definition|(% colspan="2" %)((( 1090 -Metadata Target, 1091 - 1092 -Dimension Descriptor 1093 - 987 +|(% style="width:171px" %) |(% style="width:232px" %)Metadata Structure Definition|(% style="width:206px" %)((( 988 +Metadata Target, Dimension Descriptor 1094 1094 Values Target Identifiable 1095 - 1096 1096 Object Target 1097 - 1098 1098 Report Period Target 1099 - 1100 1100 Data SetTarget 1101 - 1102 1102 Report Structure 1103 - 1104 1104 Metadata Attribute 1105 1105 ))) 1106 -| |(%colspan="2" %)Structure Usage|(%colspan="2" %)Dataflow Definition|(%colspan="2" %)1107 -| |(%colspan="2" %) |(%colspan="2" %)Metadataflow Definition|(%colspan="2" %)1108 -| |(%colspan="2" %)None|(%colspan="2" %)Process|(%colspan="2" %)Process Step1109 -| |(%colspan="2" %)None|(%colspan="2" %)Structure Set|(%colspan="2" %)(((996 +|(% style="width:171px" %)Structure Usage|(% style="width:232px" %)Dataflow Definition|(% style="width:206px" %) 997 +|(% style="width:171px" %) |(% style="width:232px" %)Metadataflow Definition|(% style="width:206px" %) 998 +|(% style="width:171px" %)None|(% style="width:232px" %)Process|(% style="width:206px" %)Process Step 999 +|(% style="width:171px" %)None|(% style="width:232px" %)Structure Set|(% style="width:206px" %)((( 1110 1110 Component Map 1111 - 1112 1112 Concept Scheme Map 1113 - 1114 1114 Codelist Map 1115 - 1116 1116 Category Scheme Map 1117 - 1118 1118 Reporting Taxonomy Map 1119 - 1120 1120 Organisation Scheme Map 1121 - 1122 1122 Concept Map 1123 - 1124 1124 Code Map 1125 - 1126 1126 Category Map 1127 - 1128 1128 Organisation Map 1129 - 1130 1130 Reporting Category Map 1131 - 1132 1132 Hybrid Codelist Map 1133 - 1134 1134 Hybrid Code Map 1135 1135 ))) 1136 -| |(%colspan="2" %)None|(%colspan="2" %)Provision Agreement|(%colspan="2" %)1137 -| |(%colspan="2" %)None|(%colspan="2" %)Hierarchical Codelist|(%colspan="2" %)(((1014 +|(% style="width:171px" %)None|(% style="width:232px" %)Provision Agreement|(% style="width:206px" %) 1015 +|(% style="width:171px" %)None|(% style="width:232px" %)Hierarchical Codelist|(% style="width:206px" %)((( 1138 1138 Hierarchy 1139 - 1140 1140 Hierarchical Code 1141 1141 ))) 1142 -| | | | | | | 1143 1143 1144 -** Table 4: Table of Maintainable Artefacts for Structural Definition Metadata**1020 +**able 4: Table of Maintainable Artefacts for Structural Definition Metadata** 1145 1145 1146 1146 === 7.1.2 Item Scheme, Structure === 1147 1147 ... ... @@ -1148,10 +1148,7 @@ 1148 1148 The artefacts included in the structural definitions are: 1149 1149 1150 1150 * All types of Item Scheme (Codelist, Concept Scheme, Category Scheme, Organisation Scheme - Agency Scheme, Data Provider Scheme, Data Consumer Scheme, Organisation Unit Scheme) 1151 -* All types of Structure (Data Structure Definition, Metadata Structure 1152 - 1153 -Definition) 1154 - 1027 +* All types of Structure (Data Structure Definition, Metadata Structure Definition) 1155 1155 * All types of Structure Usage (Dataflow Definition, Metadataflow Definition) 1156 1156 1157 1157 === 7.1.3 Structure Usage === ... ... @@ -1170,6 +1170,8 @@ 1170 1170 1171 1171 ==== 7.1.3.3 Structure Usage Model ==== 1172 1172 1046 +[[image:1747829078194-749.png]] 1047 + 1173 1173 **Figure 10: SDMX-IM of links from Structure Usage to Category** 1174 1174 1175 1175 In addition to the maintenance of the Dataflow Definition and the Metadataflow Definition the following links must be maintained in the registry: ... ... @@ -1196,10 +1196,10 @@ 1196 1196 1197 1197 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. 1198 1198 1074 +[[image:1747829109466-595.png]] 1199 1199 1200 1200 **Figure 11: SDMX-IM of the Data Provider** 1201 1201 1202 - 1203 1203 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 1204 1204 1205 1205 [[image:1747824123019-181.jpeg]] ... ... @@ -1208,8 +1208,10 @@ 1208 1208 1209 1209 The diagram below is a logical representation of the data required in order to maintain Provision Agreements. 1210 1210 1086 +[[image:1747829139951-378.png]] 1211 1211 1212 -==== Figure 13: Logical class diagram of the information contained in the Provision Agreement ==== 1088 +(% class="wikigeneratedid" id="HFigure13:LogicalclassdiagramoftheinformationcontainedintheProvisionAgreement" %) 1089 +**Figure 13: Logical class diagram of the information contained in the Provision Agreement** 1213 1213 1214 1214 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. 1215 1215 ... ... @@ -1237,13 +1237,12 @@ 1237 1237 1238 1238 === 7.3.3 Data and Metadata Constraints: Model === 1239 1239 1117 +[[image:1747829204737-370.png]] 1240 1240 1119 +**Figure 15: Logical class diagram showing inheritance between and reference to constrainable artifacts** 1241 1241 1242 - ==== Figure15: Logicalclass diagram showing inheritancebetween and reference to constrainable artifacts====1121 +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. 1243 1243 1244 -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. 1245 - 1246 - 1247 1247 The content of the Constraint can be found in the SDMX Information Model document. 1248 1248 1249 1249 == 7.4 Data and Metadata Registration == ... ... @@ -1264,7 +1264,7 @@ 1264 1264 1265 1265 [[image:1747824123025-411.jpeg]] 1266 1266 1267 - 1143 +**Figure 16: Schematic of the Objects Concerned with Registration** 1268 1268 1269 1269 ==== 7.4.2.2 Registration Request Model ==== 1270 1270 ... ... @@ -1278,11 +1278,14 @@ 1278 1278 1279 1279 The Registration has an action attribute which takes one of the following values: 1280 1280 1281 -|**Action Attribute Value**|**Behaviour** 1282 -|Append|Add this Registration to the registry 1283 -|Replace|Replace the existing Registration with identified by the id in the Registration of the Submit Registration Request 1284 -|Delete|Delete the existing Registration identified by the id in the Registration of the Submit Registration Request 1157 +(% style="width:798.294px" %) 1158 +|(% style="width:212px" %)**Action Attribute Value**|(% style="width:582px" %)**Behaviour** 1159 +|(% style="width:212px" %)Append|(% style="width:582px" %)Add this Registration to the registry 1160 +|(% style="width:212px" %)Replace|(% style="width:582px" %)Replace the existing Registration with identified by the id in the Registration of the Submit Registration Request 1161 +|(% style="width:212px" %)Delete|(% style="width:582px" %)Delete the existing Registration identified by the id in the Registration of the Submit Registration Request 1285 1285 1163 +[[image:1747829290890-122.png]] 1164 + 1286 1286 **Figure 17: Logical Class Diagram of Registration of Data and Metadata** 1287 1287 1288 1288 The Query Datasource is an abstract class that represents a data source which can understand an SDMX-ML query (SOAPDatasource) or RESTful query ... ... @@ -1297,25 +1297,20 @@ 1297 1297 1298 1298 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. 1299 1299 1300 -|**Indexing Required**|**Registration Process Activity** 1301 -|indexTimeSeries|Extract all the series keys and create a KeySet(s) Constraint. 1302 -|indexDataSet|((( 1303 -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 1304 - 1305 -Regions containing Member Selections of Dimension Components of the Constraints model in the SDMX-IM, and the associated Selection Value. 1179 +(% style="width:860.294px" %) 1180 +|(% style="width:185px" %)**Indexing Required**|(% style="width:672px" %)**Registration Process Activity** 1181 +|(% style="width:185px" %)indexTimeSeries|(% style="width:672px" %)Extract all the series keys and create a KeySet(s) Constraint. 1182 +|(% style="width:185px" %)indexDataSet|(% style="width:672px" %)((( 1183 +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. 1306 1306 ))) 1307 -|indexReportingPeriod|((( 1185 +|(% style="width:185px" %)indexReportingPeriod|(% style="width:672px" %)((( 1308 1308 This applies only to a registered dataset. 1309 - 1310 1310 Extract the Reporting Begin and Reporting End from the Header of the Message containing the data set, and create a Reference Period constraint. 1311 1311 ))) 1312 -|indexAttributes|((( 1189 +|(% style="width:185px" %)indexAttributes|(% style="width:672px" %)((( 1313 1313 **Data Set** 1314 - 1315 1315 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 1316 - 1317 1317 **Metadata Set** 1318 - 1319 1319 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. 1320 1320 ))) 1321 1321 ... ... @@ -1325,14 +1325,13 @@ 1325 1325 1326 1326 === 7.4.3 Registration Response === 1327 1327 1328 -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 1202 +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”. 1329 1329 1330 -“Success”, “Warning” or “Failure”. 1331 - 1332 1332 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. 1333 1333 1334 1334 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: 1335 1335 1208 +[[image:1747829477882-750.png]] 1336 1336 1337 1337 **Figure 18: Logical class diagram showing the registration response** 1338 1338 ... ... @@ -1342,15 +1342,12 @@ 1342 1342 1343 1343 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. 1344 1344 1345 -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 1218 +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”. 1346 1346 1347 - “notification”.1220 +=== 7.5.1Subscription Logical Class Diagram === 1348 1348 1349 - .5.1SubscriptionLogical Class Diagram1222 +[[image:1747829554603-150.png]] 1350 1350 1351 - 1352 -[[image:1747824123028-257.png]] 1353 - 1354 1354 **Figure 19: Logical Class Diagram of the Subscription** 1355 1355 1356 1356 === 7.5.2 Subscription Information === ... ... @@ -1357,73 +1357,59 @@ 1357 1357 1358 1358 Regardless of the type of registry/repository events being observed, a subscription always contains: 1359 1359 1360 -~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. 1230 +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. 1231 +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. 1232 +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. 1233 +1. A selector which specifies which type of events are of interest. The set of event types is: 1361 1361 1362 -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. 1235 +(% style="width:1031.29px" %) 1236 +|(% style="width:319px" %)**Event Type**|(% style="width:678px" %)**Comment** 1237 +|(% style="width:319px" %)STRUCTURAL_REPOSITORY_EVENTS|(% style="width:678px" %)Life-cycle changes to Maintainable Artefacts in the structural metadata repository. 1238 +|(% style="width:319px" %)DATA_REGISTRATION_EVENTS|(% style="width:678px" %)Whenever a published dataset is registered. This can be either a SDMXML data file or an SDMX conformant database. 1239 +|(% style="width:319px" %)METADATA_REGISTRATION_EVENTS|(% style="width:678px" %)Whenever a published metadataset is registered. This can be either a SDMXML reference metadata file or an SDMX conformant database. 1240 +|(% style="width:319px" %)ALL_EVENTS|(% style="width:678px" %)All events of the specified EventType 1363 1363 1364 -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. 1365 - 1366 -4. A selector which specifies which type of events are of interest. The set of event types is: 1367 - 1368 -|**Event Type**|**Comment** 1369 -|STRUCTURAL_REPOSITORY_EVENTS|Life-cycle changes to Maintainable Artefacts in the structural metadata repository. 1370 -|DATA_REGISTRATION_EVENTS|Whenever a published dataset is registered. This can be either a SDMXML data file or an SDMX conformant database. 1371 -|METADATA_REGISTRATION_EVENTS|Whenever a published metadataset is registered. This can be either a SDMXML reference metadata file or an SDMX conformant database. 1372 -|ALL_EVENTS|All events of the specified EventType 1373 - 1374 1374 === 7.5.3 Wildcard Facility === 1375 1375 1376 1376 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: 1377 1377 1378 - agencyID 1246 +* agencyID 1247 +* id 1248 +* version 1379 1379 1380 - id 1381 - 1382 - version 1383 - 1384 1384 Examples of wildcarded identifier components for an identified object type of Codelist are shown below. 1385 1385 1386 -AgencyID = % 1387 - 1252 +//AgencyID = % 1388 1388 Id = % 1254 +Version = %// 1389 1389 1390 -Version = % 1391 - 1392 1392 This subscribes to all Codelists of all versions for all agencies. 1393 1393 1394 -AgencyID = AGENCY1 1395 - 1258 +//AgencyID = AGENCY1 1396 1396 Id = CODELIST1 1260 +Version = %// 1397 1397 1398 -Version = % 1399 - 1400 1400 This subscribes to all versions of Codelist CODELIST1 maintained by the agency 1401 1401 1402 -AGENCY1 1403 - 1264 +//AGENCY1 1404 1404 AgencyID = AGENCY1 1405 - 1406 1406 Id = % 1267 +Version = %// 1407 1407 1408 -Version = % 1409 - 1410 1410 This subscribes to all versions of all Codelist objects maintained by the agency 1411 1411 1412 -AGENCY1 1413 - 1271 +//AGENCY1 1414 1414 AgencyID = % 1415 - 1416 1416 Id = CODELIST1 1274 +Version = %// 1417 1417 1418 -Version = % 1419 - 1420 1420 This subscribes to all versions of Codelist CODELIST1 maintained by the agency 1421 1421 1422 -AGENCY1 1278 +//AGENCY1// 1423 1423 1424 1424 Note that if the subscription is to the latest version then this can be achieved by the * character 1425 1425 1426 -i.e. Version = * 1282 +//i.e. Version = *// 1427 1427 1428 1428 Note that a subscription using the URN mechanism cannot use wildcard characters. 1429 1429 ... ... @@ -1435,16 +1435,14 @@ 1435 1435 1436 1436 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: 1437 1437 1294 +(% style="width:974.294px" %) 1295 +|(% style="width:295px" %)**Selector**|(% style="width:677px" %)**Comment** 1296 +|(% style="width:295px" %)DataProvider|(% style="width:677px" %)Any datasets or metadata sets registered by the specified data provider will activate the notification. 1297 +|(% style="width:295px" %)ProvisionAgreement|(% style="width:677px" %)Any datasets or metadata sets registered for the provision agreement will activate the notification. 1298 +|(% style="width:295px" %)Dataflow (&Metadataflow)|(% style="width:677px" %)Any datasets or metadata sets registered for the specified dataflow (or metadataflow) will activate the notification. 1299 +|(% style="width:295px" %)DataStructureDefinition & MetadataStructureDefinition|(% style="width:677px" %)Any datasets or metadata sets registered for those dataflows (or metadataflows) that are based on the specified Data Structure Definition will activate the notification. 1300 +|(% style="width:295px" %)Category|(% style="width:677px" %)Any datasets or metadata sets registered for those dataflows, metadataflows, provision agreements that are categorised by the category. 1438 1438 1439 -|**Selector**|**Comment** 1440 -|DataProvider|Any datasets or metadata sets registered by the specified data provider will activate the notification. 1441 -|ProvisionAgreement|Any datasets or metadata sets registered for the provision agreement will activate the notification. 1442 -|Dataflow (&Metadataflow)|Any datasets or metadata sets registered for the specified dataflow (or metadataflow) will activate the notification. 1443 -|DataStructureDefinition & MetadataStructureDefinition|Any datasets or metadata sets registered for those dataflows (or metadataflows) that are based on the specified Data Structure Definition will 1444 -|**Selector**|**Comment** 1445 -| |activate the notification. 1446 -|Category|Any datasets or metadata sets registered for those dataflows, metadataflows, provision agreements that are categorised by the category. 1447 - 1448 1448 The event will also capture the semantic of the registration: deletion or replacement of an existing registration or a new registration. 1449 1449 1450 1450 == 7.6 Notification == ... ... @@ -1451,8 +1451,10 @@ 1451 1451 1452 1452 === 7.6.1 Logical Class Diagram === 1453 1453 1308 +[[image:1747829675568-610.png]] 1454 1454 1455 -==== Figure 20: Logical Class Diagram of the Notification ==== 1310 +(% class="wikigeneratedid" id="HFigure20:LogicalClassDiagramoftheNotification" %) 1311 +**Figure 20: Logical Class Diagram of the Notification** 1456 1456 1457 1457 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. 1458 1458 ... ... @@ -1472,5 +1472,3 @@ 1472 1472 === 7.6.3 Registration Event Component === 1473 1473 1474 1474 The notification will contain the Registration. 1475 - 1476 -
- 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
- 1747994320263-112.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +xwiki:XWiki.helena - Size
-
... ... @@ -1,0 +1,1 @@ 1 +13.9 KB - Content