- From: Simon Cox via GitHub <sysbot+gh@w3.org>
- Date: Sun, 12 Aug 2018 23:20:55 +0000
- To: public-dxwg-wg@w3.org
@larsgsvensson wrote
> geospatial data has too many dimensions so that it's not possible to put all of it into a single profile, since a profile can only cater for a single value in each dimension (e. g. crs=CRS84 and scale=1:100,000 or crs=CRS84 and scale=1:50,000) -- CRS and scale being orthogonal -- whereas it might be more convenient to have different Accept-headers for those two dimensions.
Yes - I think this is the case. CRS in particular is independent of all other representation concerns, so is highly suitable for HTTP conneg.
However, there are representation standards ('profiles') that constrain the CRS - for example, GeoJSON specifies that the only acceptable CRS is WGS84 lon-lat. So the outstanding issue is what to expect when the value for `Accept-CRS` is different to the value specified within a standard indicated in `Accept-Profile` or `dct:conformsTo`.
--
GitHub Notification of comment by dr-shorthair
Please view or discuss this issue at https://github.com/w3c/dxwg/issues/311#issuecomment-412378759 using your GitHub account
Received on Sunday, 12 August 2018 23:20:58 UTC