search

RDFLib / pyLDAPI

A very small module to add Linked Data API functionality to a Python Flask installation
BSD 3-Clause "New" or "Revised" License
41 stars 11 forks source link

Implement conneg by CRS #4

Open nicholascar opened 5 years ago

nicholascar commented 5 years ago

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

Motivation: w3c/dxwg#311

nicholascar commented 5 years ago

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 commented 5 years ago

Ref original issue: https://github.com/CSIRO-enviro-informatics/pyldapi/issues/10

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

nicholascar commented 5 years ago

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.