sdmx-json
sdmx-json copied to clipboard
Issues in json formats
- It must be possible to omit the attachment
relationship
of referential metadata attributes defined in the dsd, as those cannot always be fixed to either the dataflow, a fixed dimension group or observation level. Often more flexibility is required when attaching individual referential metadata values at runtime to whatever is required. - It must be possible to omit all dimension indexes of a key in the
dimensionGroupAttributes
object in data messages, e.g. "::::" as writers cannot always easily upgrade such attributes to thedataSet
. - It must now be possible to omit dimension values in data messages if those transport only attribute or referential metadata values at dataflow level or partial key level, e.g. with parameters
measures=none
. - data message line 719: The definitions of dimension, attribute and measure values must be "anyOf" instead of current "oneOf":
"value": { "oneOf": [ {"type": "integer"}, {"type": "number"}, {"type": "boolean"}, {"type": "string"}, {"$ref": "#/definitions/localisedText"} ] },
otherwise with e.g. the value = 6 (an integer but also a number) the validation fails."value": { "oneOf": [ {"type": "integer"}, {"type": "number"}, {"type": "boolean"}, {"type": "string"} ] },