Re: Geographic metadata in Spatial Data on the Web Best Practices

Hello Jeremy

The changes look good. Thanks!

    Regards,

        Martin


Le 04/05/2017 à 16:36, Jeremy Tandy a écrit :
> Hi Martin - I've incorporated your suggestions and modified the
> references that were pointing to epsg.io <http://epsg.io> to point to
> epsg-registry.org <http://epsg-registry.org>.
>
> I see that this supersedes your previous email [1] which made more or
> less the same suggestions. Oh- and we don't point to the Apache SIS
> project staging area anymore either.
>
> Can you confirm that you're content with the changes I've made -
> latest version is the editor's draft [2]? See Pull Request #791 [3]
> for details.
>
> Jeremy
>
> [1]: https://lists.w3.org/Archives/Public/public-sdw-comments/2016Nov/0000.html
> [2]: http://w3c.github.io/sdw/bp/ 
> [3]: https://github.com/w3c/sdw/pull/791 
>
> On Tue, 4 Apr 2017 at 21:46 Ed Parsons <eparsons@google.com
> <mailto:eparsons@google.com>> wrote:
>
>     Thanks Martin, I have fwd'd to the editors.
>
>     Ed
>
>
>     On Tue, 4 Apr 2017 at 17:04 Martin Desruisseaux
>     <martin.desruisseaux@geomatys.com
>     <mailto:martin.desruisseaux@geomatys.com>> wrote:
>
>         Hello Ed
>
>         For EPSG codes, the best practice documents links to
>         http://epsg.io in many places. Would it be possible to replace
>         http://epsg.io links by http://epsg-registry.org links? The
>         later is the only official source of EPSG definitions, and
>         those two sources differ in axis order and other aspects.
>         There is unfortunately a lot of confusion about axis order and
>         (to lesser extend) units of measurement of CRS defined by EPSG
>         codes, so I worry that having W3C referencing a site
>         publishing non-compliant EPSG definitions may contribute to
>         the confusion. For example the document has some sentences
>         accurately describing WGS 84 as (Lat/Long), but the link to
>         http://epsg.io/4326 describes a (Long/Lat) system (except in
>         their GML definitions).
>
>         The proposed replacements are:
>
>           * http://epsg.io/28992 ->
>             http://epsg-registry.org/?display=entity&urn=urn:ogc:def:crs:EPSG::28992
>           * http://epsg.io/27700 ->
>             http://epsg-registry.org/?display=entity&urn=urn:ogc:def:crs:EPSG::27700
>           * /etc./ for all EPSG codes (a search in the HTML source
>             code shows 22 occurrences).
>
>         I suggest to also replace the following sentence in chapter 8:
>
>             Definitions of coordinate reference systems are available
>             from the Open Geospatial Consortium CRS Register, Spatial
>             Reference and EPSG.io (an open-source web service which
>             simplifies discovery of coordinate reference systems
>             utilized worldwide).
>
>         By
>
>             Definitions of coordinate reference systems are available
>             from the Open Geospatial Consortium CRS Register
>             <http://www.opengis.net/def/crs/> and EPSG registry
>             <http://epsg-registry.org/> (the official source of EPSG
>             definitions). Other web services like Spatial Reference
>             <http://spatialreference.org/> and EPSG.io
>             <http://epsg.io> also provide definitions as used in
>             popular software, but those definitions — especially the
>             ones published in Well Known Text (WKT) version 1 format —
>             sometime differ from official EPSG definitions in axis
>             order and units of measurement.
>
>         Regards,
>
>             Martin
>