Json format proposal for CategoryScheme and Categories

[OECD-BBAZART]

In this issue I would suggest a Json format for CategoryScheme and Categories:

Like AgencyScheme or Categorisation: CategoryScheme and Categories will be added to the "references" object.

Compared to the xml format: having the hierarchy of Categories represented nested I suggest a flat representation with a 'parent' link to establish the relationship between categories.

Here is an example of the parent relationship inside a Category:

"urn:sdmx:org.sdmx.infomodel.categoryscheme.Category=ESTAT:ESTAT_DATAFLOWS_SCHEME(1.2).14.14200": {
"id": "14200",
"name": "Normalisation of information systems",
"urn": "urn:sdmx:org.sdmx.infomodel.categoryscheme.Category=ESTAT:ESTAT_DATAFLOWS_SCHEME(1.2).14.14200",
"parent": {
"urn": "urn:sdmx:org.sdmx.infomodel.categoryscheme.Category=ESTAT:ESTAT_DATAFLOWS_SCHEME(1.2).14"
}
}

Full example:
From the source file: CATEGORY_SCHEME_ESTAT_DATAFLOWS_SCHEME_annotations.xml.txt
We will get: CATEGORY_SCHEME_ESTAT_DATAFLOWS_SCHEME_annotations.xml-output.json.txt

[OECD-BBAZART]

The downside with a flat representation of hierarchy is that the consistency of a document is not guaranteed. Furthermore the items must be correctly sorted, for ex: The parent Category A of Category B should be defined prior to Category B.
This should be the same reasoning for Codes in Code Lists, Concepts in Concept Schemes.

[OECD-BBAZART]

Thanks @sosna for the recent change on step1.json

Based on your model I suggest a complement for representing hierarchy of Categories:
CategoryScheme with hierarchy of Categories.txt

[sosna]

Thanks @OECD-BBAZART! The proposal is indeed what we had in mind, i.e. any Item/Item Scheme can hold an array of items. I will update the samples as soon as time allows but else feel free to fork the repo and send a pull request, if you want and have time.

[dosse]

#42