I think the property should be optional. Values cannot be provided in the attributes=msd case, and the information is only advisory anyway (when importing data from a SDMX-JSON data message, there does not seem a point in evaluating them and then wondering what to do if the relationships in the data message are different from those in the DSD). (I do not mind if REST API implementations are required to generate the property, when possible, but a data message should not become invalid due to the absence of the property).
(In doubt, please handle this as a public review comment on SDMX 3.1 once the comment period begins.)
Using https://github.com/sdmx-twg/sdmx-rest/blob/99e92fd7a7f2c1a0c5dcfb2776f2fdae3cf2458e/doc/data.md
attributes=msda SDMX-JSON data message would include metadata structure attributes as if they were datastructure attributes. MSD attributes do not define attribute relationships, but theattributeRelationshipproperty is currently required for all attributes.I think the property should be optional. Values cannot be provided in the
attributes=msdcase, and the information is only advisory anyway (when importing data from a SDMX-JSON data message, there does not seem a point in evaluating them and then wondering what to do if the relationships in the data message are different from those in the DSD). (I do not mind if REST API implementations are required to generate the property, when possible, but a data message should not become invalid due to the absence of the property).(In doubt, please handle this as a public review comment on SDMX 3.1 once the comment period begins.)