[OSGeo-Standards] [RESTful-Policy.SWG] Encodings and REST

Arnulf Christl arnulf.christl at metaspatial.net
Sat Oct 20 05:54:34 PDT 2012


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Folks,
I neither followed the discussion closely not the decision process of
the SWG. Can somebody summarize the rationale of the Geoservices REST
API group for not implementing GeoJSON but going down another route?

Somehow it seems like OGC is becoming just yet another party in the
general noise of format proliferation. We did better in other areas,
how come we cannot stay on top of this one?

This is pretty clear language, how are we going to address it?
https://twitter.com/vmx/status/259275792817741824

Apparently this comment by Volker Mische (who we know as supportive to
the OGC) is receiving a lot of positive support in the broader
geospatial IT crowd. Ignoring is not a solution.

Cheers,
Arnulf

On 10/20/2012 12:46 PM, Peter Schut wrote:
> The good thing about standards is that there are so many of them.
> The bad thing about standards....
> 
> Cheers, Peter.
> 
> 
> On Fri, Oct 19, 2012 at 11:49 AM, Jeff Harrison 
> <jharrison at thecarbonproject.com
> <mailto:jharrison at thecarbonproject.com>> wrote:
> 
> It's my understanding that the GeoServices REST group has rejected 
> integrating GeoJSON.  I suppose this means that if OGC passes 
> GeoServices REST with its current JSON, there will then be 'OGC
> GeoServices JSON'. Which means this could be added to OGC GML,
> GMLsf and OGC KML on the list of encodings vendors may need to
> support. Then there could be OGC GeoJSON if that angle moves
> forward.  Add to this the fact that there will likely be an OSM
> JSON API next year, as well potentially an OGC GeoPackage.
> 
> So the 2013 interoperability tech landscape, for geospatial
> features alone, could look like -> OGC GML, OGC GMLsf and OGC KML
> ... GeoServices JSON, GeoJSON, OSM JSON, ... GeoPackage
> 
> Is it just me, or is this a really long list?
> 
> Regards, Jeff
> 
> 
> 


- -- 
Arnulf Christl
http://metaspatial.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iEYEARECAAYFAlCCnwkACgkQXmFKW+BJ1b0XIwCaA4Yx4CwzDf3Ti2YTbhk+1MGE
TiEAn1mOMiraT+VAyYWgO9RtiFkKmqxq
=UFEF
-----END PGP SIGNATURE-----


More information about the Standards mailing list