- From: Raphaël Troncy <raphael.troncy@eurecom.fr>
- Date: Fri, 03 Jan 2014 11:24:12 +0100
- To: Andrea Perego <andrea.perego@jrc.ec.europa.eu>, LocAdd W3C CG Public Mailing list <public-locadd@w3.org>
Dear Andrea, > *Proposed resolution* > Add to the LOCN voc an optional property to specify the CRS of a > geometry. The range of such property can be either a literal (e.g., > EPSG:4326), a URN (e.g., urn:ogc:def:EPSG::4326) or an HTTP URI > reference (e.g., http://www.opengis.net/def/crs/EPSG/0/4326). +1 for such a property. The domain and range of such a property needs to be further thought though. I would prefer we constrain the values to be HTTP URI (and not literal or URN except if this is for strong legacy reason but I understand that OGC has explicitly deprecated the usage of URN and literals). Regarding the domain, we need to make sure that the CRS information is interpreted alongside a set of coordinates, which may require to have an intermediary blank node. > 2. Should we recommend a specific CRS URI register? I think Raj Singh has proposed that http://www.opengeospatial.org/projects/groups/ogcnasc should be recommended. I have read the guidelines for editors [1] who wish to submit URIs but I don't find the instructions that clear. I suggest that this document should be enhanced with an example such as: organization/authority X wants to submit a URI u identifying a new CRS (e.g. Lambert93) for review by OGC-NA ... what is the procedure? Furthermore, it is unclear who is allowed to make such a submission: anyone?, only OGC members? Best regards. Raphaël -- Raphaël Troncy EURECOM, Campus SophiaTech Multimedia Communications Department 450 route des Chappes, 06410 Biot, France. e-mail: raphael.troncy@eurecom.fr & raphael.troncy@gmail.com Tel: +33 (0)4 - 9300 8242 Fax: +33 (0)4 - 9000 8200 Web: http://www.eurecom.fr/~troncy/
Received on Friday, 3 January 2014 10:24:40 UTC