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...") |
|||
Line 9: | Line 9: | ||
Additional Characteristics: | Additional Characteristics: | ||
− | * Maintainable artefacts can be uniquely referenced by a URN, for instance: urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=WB:LABOR_FORCE(1.0) | + | * Maintainable artefacts can be uniquely referenced by a URN, for instance: <nowiki>urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=WB:LABOR_FORCE(1.0)</nowiki> |
− | * | + | * Optionally have annotations |
+ | |||
+ | Codes and Concepts, for instance, are not maintainable artefacts because they cannot exist outside of their containers - in this case Codelists and Concept Schemes. | ||
=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 formal SDMX standard: | ||
+ | * Validation Schemes |
Revision as of 01:38, 21 January 2020
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)
Additional Characteristics:
- Maintainable artefacts can be uniquely referenced by a URN, for instance: urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=WB:LABOR_FORCE(1.0)
- Optionally have annotations
Codes and Concepts, for instance, are not maintainable artefacts because they cannot exist outside of their containers - in this case Codelists and Concept Schemes.
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 formal SDMX standard:
- Validation Schemes