Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Attribute relationship vs attachment level #155

Open
hoehrmann opened this issue Apr 20, 2024 · 0 comments
Open

Attribute relationship vs attachment level #155

hoehrmann opened this issue Apr 20, 2024 · 0 comments

Comments

@hoehrmann
Copy link

https://github.com/sdmx-twg/sdmx-json/blob/71fe5eaa9fcd29e3c15f2f0216a19b9b650b1dbd/data-message/docs/1-sdmx-json-field-guide.md#component says »Depending on the message context (especially the data query) an attribute value can however be attached physically in the message at a different level.«

But https://github.com/sdmx-twg/sdmx-json/blob/71fe5eaa9fcd29e3c15f2f0216a19b9b650b1dbd/structure-message/docs/1-sdmx-json-field-guide.md#attributeRelationship says »An attribute with this relationship will its values always have presented at observation level.«

This seems contradictory, and the latter statement seems mistaken. Suppose the attribute is only there to be able to encode extremely unlikely cases should they ever occur. If there is no such case in the data, why shouldn't the value be attached to the data set? It also seems an unnecessary burden to generate an error or ignore the attribute if specified on the dataset level just because the DSD says different values per observation are possible.

(In doubt, please handle this as a public review comment on SDMX 3.1 once the comment period begins.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant