- From: Dimitri van Hees via GitHub <sysbot+gh@w3.org>
- Date: Wed, 01 Aug 2018 07:59:37 +0000
- To: public-sdwig@w3.org
Hi. @lvdbrink pointed me here because I don't know much about MapML but I'm interested in standardising CRS negotiation ;) Using our REST APIs, a client can send geometries in a specific CRS and a server can reply geometries in a specific CRS. Using response headers, we could use the `Link` approach mentioned here to tell the client which CRS is used in the response, but then we'd still have to find a proper way to do this in a request. We chose to introduce an `Accept-Crs` request header to let the client negotiate a preferred CRS and a `Content-Crs` header to identify the CRS used in both the payload of the request as the payload of the response. How is this compared to the MapML usecase? -- GitHub Notification of comment by dvh Please view or discuss this issue at https://github.com/w3c/sdw/issues/1058#issuecomment-409486161 using your GitHub account
Received on Wednesday, 1 August 2018 07:59:41 UTC