SDMX 3.0: implement "feature 029 Improving API data queries" for SDMX-CSV messages

[dosse]

In order to support the new requirement, it is proposed to:

structure message changes: No impact.

data message changes:

• Add support for multiple keys
  No impact. Note: Each line can already have its own structure reference. If different DSD versions are used then the components might be different. In this case, non-common and non-used components (columns) would be left empty.

• Extend the context of data retrieval
  The first keyword in the CSV data message is extended to be one of the following:

  • DATAFLOW
  • DATASTRUCTURE
  • DATAPROVISIONAGREEMENT

  Examples:

  
  DATAFLOW,DIM1,DIM2,DIM3,ATTR1,ATTR2,ATTR3,ATTR4
  ESTAT:NA_MAIN(1.6),A,B,C,AA,BB,CC,DD

DATASTRUCTURE,DIM1,DIM2,DIM3,ATTR1,ATTR2,ATTR3,ATTR4 ESTAT:DSD_NA_MAIN(1.0),A,B,C,AA,BB,CC,DD

DATAPROVISIONAGREEMENT,DIM1,DIM2,DIM3,ATTR1,ATTR2,ATTR3,ATTR4 ESTAT:DPA_NA_MAIN(2.0),A,B,C,AA,BB,CC,DD

- Add a “cube-based” data retrieval, in addition to the current “key-based” one
  No impact.
- Harmonizing separators
  No impact.

[dosse]

Released