Unclear source of min/maxOccurs property present in JSON schema of ConceptRepresentationType about sdmx-json

[dosse]

In general, the SDMX-ML schema is meant to be a "master" IM implementation. In many aspects, it is more precise. However, each issue need to be looked at separately, as bugs could also happen here.

[dosse]

Hello @buhaiovos, thanks for reporting this. It highlights an inconsistency in the documentation between the IM and the message format implementations (SDMX-ML and SDMX-JSON). Indeed, when constructing the message formats, sometimes some changes are made to generalise the approach and make it more coherent. Certain aspects may not have been seen when writing the IM document. The SDMX-JSON represents a translation of structures in SDMX-ML,.
You can see here how the maxOccurs and minOccurs parameters were moved from the component definitions into the RepresentationType, thus into CoreRepresentation (inside concepts) and LocalRepresentation (inside the component definitions in the DSD). The same was done in SDMX-JSON.
In conclusion, it would seem to me that this feedback should be addressed by updating the IM document. I opened sdmx-twg/sdmx-im#27 for this.

[buhaiovos]

@dosse, thanks for the response.
So, basically, if we're dealing with such kind of issues (when something between infomodel and XML(JSON) doesn't match) - we consider message formats more relevant?