<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body text="#000000" bgcolor="#FFFFFF">
OSGeo education leaders:<br>
<br>
I'm hopeful that you all will add your weight to this Open Letter,
and will forward on to your respective networks.<br>
<div class="moz-forward-container"><br>
<br>
-------- Original Message --------
<table class="moz-email-headers-table" border="0" cellpadding="0"
cellspacing="0">
<tbody>
<tr>
<th nowrap="nowrap" valign="BASELINE" align="RIGHT">Subject:
</th>
<td>Last chance to reject "Geoservices REST API" standard</td>
</tr>
<tr>
<th nowrap="nowrap" valign="BASELINE" align="RIGHT">Date: </th>
<td>Mon, 13 May 2013 10:33:01 +1000</td>
</tr>
<tr>
<th nowrap="nowrap" valign="BASELINE" align="RIGHT">From: </th>
<td>Cameron Shorter <a class="moz-txt-link-rfc2396E" href="mailto:cameron.shorter@gmail.com"><cameron.shorter@gmail.com></a></td>
</tr>
<tr>
<th nowrap="nowrap" valign="BASELINE" align="RIGHT">To: </th>
<td>OSGeo Discussions <a class="moz-txt-link-rfc2396E" href="mailto:discuss@lists.osgeo.org"><discuss@lists.osgeo.org></a>,
<a class="moz-txt-link-rfc2396E" href="mailto:standards@lists.osgeo.org">"standards@lists.osgeo.org"</a>
<a class="moz-txt-link-rfc2396E" href="mailto:standards@lists.osgeo.org"><standards@lists.osgeo.org></a></td>
</tr>
</tbody>
</table>
<br>
<br>
<pre>Next Wednesday, the OSGeo Board will deliver an Open Letter to the OGC
and OGC voting members, with multiple signatures, demonstrating the
large number of people concerned about the negative consequences
associated with making the "Geoservices REST API" an OGC standard.
The "GeoServices REST API" was initially developed by ESRI and
implemented on the ArcGIS Server platform before going through the OGC
process. It significantly overlaps with OGC's existing W*S services, but
isn't based upon these existing standards. Consequently, we have grave
concerns that the two competing sets of standards, which essentially
cover the same use cases, will have far reaching, detrimental impacts on
interoperability, complexity, and costs within the spatial industry,
including being bad for Geospatial Open Source software.
Many people, including leaders of OSGeo and related communities, have
already signed this letter. Thankyou. If you agree that "Geoservices
REST API" will be bad for OSGeo and/or the greater spatial community,
then please help us deliver this concern to OGC voters before they vote.
Add your signature to the Open Letter [1] before we deliver it on
Wednesday 15 May 2013, and forward this message onto other OSGeo
communities. (I notice that messages from this thread are being
forwarded to the Spanish OSGeo email list. Thankyou.)
If you are looking for a deep analysis of the issues, I suggest reading
the open letter which is now draft complete [1].
[1] <a class="moz-txt-link-freetext" href="http://wiki.osgeo.org/wiki/Geoservices_REST_API">http://wiki.osgeo.org/wiki/Geoservices_REST_API</a>
--
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>
</div>
<br>
</body>
</html>