Difference between revisions of "Maintainable artefact"
Jump to navigation
Jump to search
(Created page with "__NOTOC__ Category:Glossary An SDMX maintainable artefact is one that can be independently created and maintained by a maintenance agency.<br><br> Maintainable artefac...") |
|||
| (4 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
__NOTOC__ | __NOTOC__ | ||
[[Category:Glossary]] | [[Category:Glossary]] | ||
| + | [[Category:How_To]] | ||
An SDMX maintainable artefact is one that can be independently created and maintained by a [[maintenance agency]].<br><br> | An SDMX maintainable artefact is one that can be independently created and maintained by a [[maintenance agency]].<br><br> | ||
Maintainable artefacts have: | Maintainable artefacts have: | ||
| Line 7: | Line 8: | ||
* Name | * Name | ||
* Description (optional) | * Description (optional) | ||
| + | * Annotations (optional) | ||
| − | + | ||
| − | + | [[Item|Items]] such as Codes and Concepts, are not maintainable artefacts because they can only exist within their containers, in this case Codelists and Concept Schemes respectively. | |
| − | + | ||
| + | ==URN== | ||
| + | Maintainable artefacts can be uniquely referenced by a URN: | ||
| + | <code> | ||
| + | <nowiki>urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=WB:LABOR_FORCE(1.0)</nowiki> | ||
| + | </code> | ||
| + | |||
| + | The above example is the URN from a World Bank Labor Force Dataflow where: | ||
| + | {| class="wikitable" | ||
| + | |- | ||
| + | | Agency || WB (World Bank) | ||
| + | |- | ||
| + | | Dataflow ID || LABOR_FORCE | ||
| + | |- | ||
| + | | Version || 1.0 | ||
| + | |} | ||
=Examples= | =Examples= | ||
| + | The following SDMX structures are maintainable artefacts: | ||
| + | * Agency Schemes | ||
| + | * Attachment Constraints | ||
| + | * Category Schemes | ||
| + | * Codelists | ||
| + | * Concept Schemes | ||
| + | * Content Constraints | ||
| + | * Data Consumers | ||
| + | * Data Providers | ||
| + | * Data Structure Definitions | ||
| + | * Dataflows | ||
| + | * Hierarchical Codelists | ||
| + | * Metadata Structure Definitions | ||
| + | * Metadataflows | ||
| + | * Organisation Unit Schemes | ||
| + | * Processes | ||
| + | * Provision Agreements | ||
| + | * Reporting Taxonomies | ||
| + | * Structure Sets | ||
| + | * Metadata Reports | ||
| + | |||
| + | The following are additional maintainable artefacts supported by Fusion Registry that are not part of the published SDMX standard: | ||
| + | * Validation Schemes | ||
Latest revision as of 07:22, 4 September 2023
An SDMX maintainable artefact is one that can be independently created and maintained by a maintenance agency.
Maintainable artefacts have:
- ID
- Version
- Name
- Description (optional)
- Annotations (optional)
Items such as Codes and Concepts, are not maintainable artefacts because they can only exist within their containers, in this case Codelists and Concept Schemes respectively.
URN
Maintainable artefacts can be uniquely referenced by a URN:
urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=WB:LABOR_FORCE(1.0)
The above example is the URN from a World Bank Labor Force Dataflow where:
| Agency | WB (World Bank) |
| Dataflow ID | LABOR_FORCE |
| Version | 1.0 |
Examples
The following SDMX structures are maintainable artefacts:
- Agency Schemes
- Attachment Constraints
- Category Schemes
- Codelists
- Concept Schemes
- Content Constraints
- Data Consumers
- Data Providers
- Data Structure Definitions
- Dataflows
- Hierarchical Codelists
- Metadata Structure Definitions
- Metadataflows
- Organisation Unit Schemes
- Processes
- Provision Agreements
- Reporting Taxonomies
- Structure Sets
- Metadata Reports
The following are additional maintainable artefacts supported by Fusion Registry that are not part of the published SDMX standard:
- Validation Schemes
