[OSGeo-Standards] JSON in OGC standards (REST API Candidate Standard)

Tue Jul 24 15:51:44 PDT 2012

OGC,
As an OGC member (from LISAsoft), I would like to second Volker's 
comment's below regarding GeoJSON.

I would also like to ask:
* Has the REST API standard been tested amongst multiple client and 
server applications, as is usually done in OGC Open Web Services Testbeds?

* Is there an Open Source reference implementation of the REST API 
standard, as has been the case for most (all?) OGC standards to date.

I'm nervous that the proposed REST API standard may be supported by one 
vendor, but has not been given the attention required to be adopted 
broadly by other applications.

On 24/07/2012 7:57 PM, Volker Mische wrote:
> Hi all,
>
> I've just discovered that the upcoming GeoServices REST API [1] standard
> doesn't make use of GeoJSON, but has it's own JSON format for geometries.
>
> I'm well aware that GeoJSON is not an OGC standard, but no one can argue
> that it's not widely used. The objective of the GeoServices REST API is
> to be backwards compatible to the ESRI implementation. This of course
> makes sense for ESRI, but is it really what the OGC wants/is about?
>
> Does the OGC really want to have a standard with JSON encoded geometries
> which are not compatible to an already existing specification?
>
> "Widely used" is hard to put into numbers, but I think it this case, we
> could just count how many GeoJSON parsers out there, and how many
> GeoServices REST API JSON encoded geometry parsers are out there.
>
> Would it make sense to file an official change request? Or is it not
> worth the hassle as it would be taken down immediately, as it is a
> backwards incompatible change?
>
> [1] http://www.opengeospatial.org/standards/requests/89
>
> Cheers,
>    Volker
> _______________________________________________
> Standards mailing list
> Standards at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/standards

On 20/07/2012 4:31 AM, announce at opengeospatial.org wrote:
>
> OGC <http://www.opengeospatial.org/>
>
> ------------------------------------------------------------------------
>
> FOR IMMEDIATE RELEASE
>
> Contact:  info at opengeospatial.org
>
>
> OGC Seeks Comments on GeoServices REST API Candidate Standard
>
> 19 July 2012. The Open Geospatial Consortium (OGC®) seeks public 
> comment on the candidate OGC GeoServices REST API standard. The 
> GeoServices REST Application Programming Interface (API) provides a 
> standard way for web clients to communicate with geospatial 
> technologies, such as Geographic Information System (GIS) servers, 
> based on Representational State Transfer (REST) principles.
>
> Using this API, clients, such as a web browser application, issue 
> requests to resources on the server identified by structured Uniform 
> Resource Locators (URLs). The server responds with map images, 
> text-based location details or other representations of geospatial 
> information.  From a services perspective the API offers a mechanism 
> to interact with map, image and feature services and perform 
> geospatial analysis. This JavaScript Object Notation (JSON)-based, 
> RESTful API is intended to make implementing servers instantly usable 
> by developers working with widely used REST-based scripting and 
> programming languages, as well as mobile platforms. End users can then 
> use these developers' Web applications to discover and access the 
> services and use them in their workflows.
>
> In early 2011, Esri contacted the Open Geospatial Consortium about 
> submitting the GeoServices Rest API as a candidate OGC standard. This 
> submission was approved through the OGC process and then a Standards 
> Working Group (SWG), composed of many OGC members, performed a 
> detailed review and rewrote the API as an OGC interface standard, 
> removing Esri-specific software references. The OGC's adoption of this 
> candidate standard will provide the wider Web developer community with 
> additional standards-based choices for leveraging geospatial information.
>
> The candidate OGC GeoServices REST API standard documents are 
> available for review and comment at 
> http://www.opengeospatial.org/standards/requests/89.
>
> The closing date for comments will be 18 August 2012.
>
> The OGC is an international consortium of more than 445 companies, 
> government agencies, research organizations, and universities 
> participating in a consensus process to develop publicly available 
> geospatial standards. OGC Standards support interoperable solutions 
> that "geo-enable" the Web, wireless and location-based services, and 
> mainstream IT. OGC Standards empower technology developers to make 
> geospatial information and services accessible and useful with any 
> application that needs to be geospatially enabled. Visit the OGC 
> website at http://www.opengeospatial.org/contact.
>
> ------------------------------------------------------------------------
>
> Join on LinkedIn 
> <http://www.linkedin.com/groups?mostPopular=&gid=55322> Follow on 
> Twitter <https://twitter.com/opengeospatial> OGC Youtube Channel 
> <http://www.youtube.com/user/ogcvideo>
>
>
> --
>
> If you do not want to receive any more messages, please visit this 
> link 
> <http://lists.opengeospatial.org/lists/?p=unsubscribe&uid=fc172449de56bd8945a043139bc9388d>
> To update your preferences and to unsubscribe visit this link 
> <http://lists.opengeospatial.org/lists/?p=preferences&uid=fc172449de56bd8945a043139bc9388d>
> To forward a message to someone you may use this link 
> <http://lists.opengeospatial.org/lists/?p=forward&uid=fc172449de56bd8945a043139bc9388d&mid=101>

-- 
Cameron Shorter
Geospatial Solutions Manager
Tel: +61 (0)2 8570 5050
Mob: +61 (0)419 142 254

Think Globally, Fix Locally
Geospatial Solutions enhanced with Open Standards and Open Source
http://www.lisasoft.com

-- 
Cameron Shorter
Geospatial Solutions Manager
Tel: +61 (0)2 8570 5050
Mob: +61 (0)419 142 254

Think Globally, Fix Locally
Geospatial Solutions enhanced with Open Standards and Open Source
http://www.lisasoft.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/standards/attachments/20120725/1b1ed243/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 6628 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/standards/attachments/20120725/1b1ed243/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 6279 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/standards/attachments/20120725/1b1ed243/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 6132 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/standards/attachments/20120725/1b1ed243/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 1621 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/standards/attachments/20120725/1b1ed243/attachment-0007.png>