Roadmap

v.Next (Postponed)

Postponed Issues

0%

0 closed (0%)   22 open (100%)

Related issues
Feature #4: A need to document profiles for different typical data exchanges
Feature #6: More documentation details needed on Operands
Feature #15: Security of SDMX-HD messages
Feature #16: Inheritance
Feature #17: Multiple DataSets
Feature #19: Common list of Disaggregation can use CubRegion Constraints.
Feature #20: Disease should be renamed as “Condition”
Feature #28: SDMX xsd copyright question
Feature #31: Ranges
Feature #79: Schematron rule needed to check for mutiples.

v1.0

SDMX-HD Standard version 1.0

72%

42 closed (72%)   16 open (28%)

Related issues
Feature #1: Additional business rules declared/expressed to further validate SDMX-HD rules.
Feature #3: Relative paths outside of the SDMX-HD folder
Feature #7: SenderId should be the system that generated the data
Feature #9: Program should NOT be a "Mandatory" Dimension attribute
Feature #10: SDMX-HD Normative Document Needed
Feature #11: Valid SDMX HD messages shall in all cases conform to valid SDMX messages
Feature #12: CDS namespace rule
Feature #13: How should we Identify Common or Custom code-lists
Feature #14: What is the definition of a Common Code-list
Feature #18: What should be transferred in SDMX-HD
Feature #21: Minimum dimensions
Feature #22: What is the Organization definition exactly
Feature #23: COMMON Concept Review Reqiured
Feature #24: Time Period - Time Dimension
Feature #25: Attributes attached to Group they need a Group ID
Feature #26: REPEATS="0" MANDATORY="1" should be removed
Feature #29: SDMX-HD Zip File Standard
Feature #32: Special Concepts will have custom code-lists