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

Implement conneg by CRS #4

Open
nicholascar opened this issue Sep 23, 2018 · 3 comments
Open

Implement conneg by CRS #4

nicholascar opened this issue Sep 23, 2018 · 3 comments
Labels
enhancement New feature or request

Comments

@nicholascar
Copy link
Member

Add a new conneg dimension: by CRS. Open-ended list of CRSes as URIs.

Motivation: w3c/dxwg#311

@nicholascar nicholascar added the enhancement New feature or request label Sep 23, 2018
@nicholascar
Copy link
Member Author

From @dr-shorthair: Note that OGC serves GML-conformant CRS descriptions from URI's like

https://www.opengis.net/def/crs/EPSG/0/4326

@ashleysommer
Copy link
Collaborator

Ref original issue:
CSIRO-enviro-informatics/pyldapi#10

@nicholascar has the WG decided on a mechanism for CRS negotiation yet? I read the discussion here w3c/dxwg#311 but I don't there there is any solid agreement on Accept-Crs vs using extensions on Accept-Profile.

@nicholascar
Copy link
Member Author

I think the feeling is that the WG should just ensure that, as per Requirement 1: Profile negotiation mechanisms must support or safely co-exist with negotiation over other dimensions of data organisation. So the UC indicates constraints on the Profile Negotiation but doesn't call on the WG to actually implement conneg by CRS.

Let's put supporting conneg by CRS within pyLDAPI on the back-burner. It might be something that LOC-I project wants but there's no requirement to support it directly for now.

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

No branches or pull requests

2 participants