<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">OGC,<br>
As an OGC member (from LISAsoft), I would like to second Volker's
comment's below regarding GeoJSON.<br>
<br>
I would also like to ask:<br>
* Has the REST API standard been tested amongst multiple client
and server applications, as is usually done in OGC Open Web
Services Testbeds?<br>
<br>
* Is there an Open Source reference implementation of the REST API
standard, as has been the case for most (all?) OGC standards to
date.<br>
<br>
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.<br>
<br>
On 24/07/2012 7:57 PM, Volker Mische wrote:<br>
</div>
<blockquote cite="mid:500E717E.7090808@gmail.com" type="cite">
<pre wrap="">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] <a class="moz-txt-link-freetext" href="http://www.opengeospatial.org/standards/requests/89">http://www.opengeospatial.org/standards/requests/89</a>
Cheers,
Volker
_______________________________________________
Standards mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Standards@lists.osgeo.org">Standards@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/standards">http://lists.osgeo.org/mailman/listinfo/standards</a>
</pre>
</blockquote>
<br>
<br>
<div class="moz-cite-prefix">On 20/07/2012 4:31 AM,
<a class="moz-txt-link-abbreviated" href="mailto:announce@opengeospatial.org">announce@opengeospatial.org</a> wrote:<br>
</div>
<blockquote
cite="mid:38a2f8f06dcaf34b60d1032705fe4dbb@lists.opengeospatial.org"
type="cite">
<p> <a moz-do-not-send="true"
href="http://www.opengeospatial.org/"><img alt="OGC"
src="cid:part1.03060201.05050204@lisasoft.com"></a></p>
<hr>
<p>FOR IMMEDIATE RELEASE <br>
<br>
Contact: <a class="moz-txt-link-abbreviated" href="mailto:info@opengeospatial.org">info@opengeospatial.org</a>
<br>
<br>
<br>
OGC Seeks Comments on GeoServices REST API Candidate
Standard<br>
<br>
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.<br>
<br>
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. <br>
<br>
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.<br>
<br>
The candidate OGC GeoServices REST API standard documents
are available for review and comment at
<a class="moz-txt-link-freetext" href="http://www.opengeospatial.org/standards/requests/89">http://www.opengeospatial.org/standards/requests/89</a>.<br>
<br>
The closing date for comments will be 18 August
2012.<br>
<br>
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
<a class="moz-txt-link-freetext" href="http://www.opengeospatial.org/contact">http://www.opengeospatial.org/contact</a>.</p>
<hr>
<p> </p>
<div class="icons"><a moz-do-not-send="true" title="Join on
LinkedIn"
href="http://www.linkedin.com/groups?mostPopular=&gid=55322"><img
alt="Join on LinkedIn"
src="cid:part3.07070207.05050900@lisasoft.com"></a> <a
moz-do-not-send="true" title="Follow on Twitter"
href="https://twitter.com/opengeospatial"><img alt="Follow
on Twitter" src="cid:part5.04010802.04000609@lisasoft.com"></a>
<a moz-do-not-send="true" title="OGC Youtube Channel"
href="http://www.youtube.com/user/ogcvideo"><img alt="OGC
Youtube Channel"
src="cid:part7.04040808.03010107@lisasoft.com"></a></div>
<br>
<br>
<div class="emailfooter">--<br>
<br>
If you do not want to receive any more messages, please
visit <a moz-do-not-send="true"
href="http://lists.opengeospatial.org/lists/?p=unsubscribe&uid=fc172449de56bd8945a043139bc9388d">this
link</a><br>
To update your preferences and to unsubscribe visit <a
moz-do-not-send="true"
href="http://lists.opengeospatial.org/lists/?p=preferences&uid=fc172449de56bd8945a043139bc9388d">this
link</a><br>
To forward a message to someone you may use <a
moz-do-not-send="true"
href="http://lists.opengeospatial.org/lists/?p=forward&uid=fc172449de56bd8945a043139bc9388d&mid=101">this
link</a></div>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
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
<a class="moz-txt-link-freetext" href="http://www.lisasoft.com">http://www.lisasoft.com</a>
</pre>
<br>
<pre class="moz-signature" cols="72">--
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
<a class="moz-txt-link-freetext" href="http://www.lisasoft.com">http://www.lisasoft.com</a>
</pre>
</body>
</html>