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

Unclear representation of geospatial artefacts #41

Open
hoehrmann opened this issue May 4, 2024 · 0 comments
Open

Unclear representation of geospatial artefacts #41

hoehrmann opened this issue May 4, 2024 · 0 comments

Comments

@hoehrmann
Copy link

As far as I can tell, geospatial artefacts have multiple representations allowed by the schema definitions, all of these paths seem valid:

/m:Structure/m:Structures/s:Codelists[n]/s:Codelist[n]/s:GeoFeatureSetCode[n]/@value
/m:Structure/m:Structures/s:GeographicCodelists[n]/s:GeographicCodelist[n]/s:GeoFeatureSetCode[n]/@value

/m:Structure/m:Structures/s:Codelists[n]/s:Codelist[n]/s:GeoGridCode[n]/s:GeoCell
/m:Structure/m:Structures/s:GeoGridCodelists[n]/s:GeoGridCodelist[n]/s:GeoGridCode[n]/s:GeoCell

The SDMX 3.0.0 Registry specification also does not define special URN prefixes for geospatial artefacts, suggesting they use codelist.Codelist which would suggest the representation under /m:Structure/m:Structures/s:Codelists[n]/ is the intended one, but the examples use the specialized representation, in which case using codelist.Codelist seems inconsistent and one would expect they use URN prefixes of codelist.GeographicCodelist and codelist.GeoGridCodelist.

(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