2015-06-25 14:14 GMT+02:00 Andrea Perego <andrea.perego@jrc.ec.europa.eu>: > > [snip] > > > > So the next proposal could be > > > > "There should be a best practice for referencing a CRS with a HTTP URI, > and > > to get useful information about the CRS when that URI is dereferenced."? > > Or simply: > > "CRSs should be referenced with HTTP URIs, resolving to useful > information about the CRS" > When put that way, I think the intention of the requirement is different on two important points: 1. We don't ask for a single best way of publishing CRS data 2. We mandate publication of CRS data instead of trying to make it possible or easy to do so Perhaps we are trying to solve two different problems with this requirement: A) the problem that there are lots of coordinate data out there that have no clear CRS, making them hard to use in some scenarios B) the problem that if someone want to publish or consume data about the CRS (associated with metadata or individual geometries) it is not clear how that should be done If there are multiple schools of thought on what we want to achieve with this requirement, perhaps we can split the requirement in two separate requirements? Regards, Frans > Andrea > -- Frans Knibbe Geodan President Kennedylaan 1 1079 MB Amsterdam (NL) T +31 (0)20 - 5711 347 E frans.knibbe@geodan.nl www.geodan.nl disclaimer <http://www.geodan.nl/disclaimer>
Received on Thursday, 25 June 2015 12:35:57 UTC