Geoservices REST API
This wiki page aims to collate community concerns related to the proposed acceptance of the "Geoservices REST API" becoming an OGC standard.
Open Letter to OGC and voting members
Please don't edit this "Open Letter" statement, comments and discussion should go below.
We, the undersigned, have concerns that approving the "Geoservices REST API" as an OGC standard, would have detrimental impacts on interoperability within the spatial industry.
We strongly urge that the proposed "Geoservices REST API", as it stands in May 2013, be rejected as an OGC standard.
People have listed different reasons for concern. They are described below.
Please add your name here if you agree with the above statement. Include name, work title (if appropriate), very brief title/involvement in OSGeo if appropriate. (Link to OSGeo profile if appropriate). You may sign as a group, such as the Project Steering Committee of XXX project if you wish, or as Your Name on behalf of YYY company.
- Cameron Shorter, Geospatial Solutions Director at LISAsoft, core contributor & coordinator of OSGeo-Live
- Stephen Woodbridge, Director of iMaptools.com, Contributor and/or PSC of Mapserver, pgRouting, PAGC, and PostGIS
- Even Rouault, Geospatial developer, OSGeo Charter Member, core contributor and PSC member of GDAL/OGR, contributor of Mapserver, PROJ.4, libgeotiff, shapelib, libtiff
- Gerhard Triebnig, Managing Director at EOX IT Services GmbH and Stephan Meissl, CTO at EOX IT Services GmbH, contributor of Mapserver, PSC chair of EOxServer
- Jeroen Ticheler, Director of GeoCat, project founder and PSC chair of GeoNetwork opensource
--- DRAFT ____
Please add concerns as bullet points below. Try to be concise. Where appropriate, link to external web pages (such as email achieves)
As at May 2013, OGC members have been asked to decide whether to accept the "GeoServices REST API" as an OGC standard. This is a contentious issue, with many people arguing that introduction of the “GeoServices REST API” will have costly, far reaching, negative impacts on interoperability, and significantly tarnish the OGC's reputation as a champion of interoperability.
The key points of contention revolve around the fact that the proposed “GeoServices REST API does not build upon or extend existing OGC standards, but rather addresses similar requirements using an alternative API. In particular, the overlap and/or duplication of existing standards is widespread: OGC's core standards of WMS, WMTS, WFS, SE/SLD, WCS, CS/W are all duplicated to a significant extent. This defeats the purpose of having standards in the first place.
Duplication of standards will likely result in a combination of the following:
- The cost to application developers, systems integrators, testers and sponsors to support all relevant OGC standards will be substantially increased.
- Consequently, organisations and/or applications may choose to only support one standard, or only support one standard fully.
- Sponsors (such as governments) who require compliance with OGC standards will discover that applications don't communicate together, due to applications supporting different OGC standards that essentially do the same thing.
- This will result in a diminished importance of OGC, as the "OGC standards" stamp of approval will not equate interoperability.
- After a while, in order to solve interoperability issues, a respected international organisation or program will likely take the initiative to mandate one standard as the preferred standard for all agencies to follow. To date, the OGC has provided this leadership.
- One standard taking prominance over the other will likely lead to the other being neglected or deprecated, resulting in many OGC compliant systems becoming legacy systems in the process. This should be considered an undesirable outcome for a standards organisation. Backward compatibility to the existing WxS standards is important in this respect.
- Adopting the standard will expose the OGC to a strong suspicion of acting as a rubber stamp organization under ESRI weight, and will be detrimental to its recognized position as a reference organization for geospatial standards.
- It is a dubious practice that a standardization organisation promotes competing standards, without explicitely obsoleting (or at least recommending) some of them. How is a new comer to the industry supposed to select the appropriate standard if several ones share the same scope : WFS or GeoServices REST API Feature Service, WMS or GeoServices REST API Map Service, etc. ?
- Promoting standards from an existing implementation made by a single vendor leads to an obvious bias in competition.
- Supporting multiple overlapping standards greatly reduces usability while it increases complexity and cost of development and maintenance.
- Many SME's have invested in supporting existing OGC standards in their products. They will be forced to choose the standards they support (and can explain), resulting in decreased interoperability, confusion and frustration for clients.
- Confusing customers with new, overlapping OGC standards will lower the credibility of companies and of OGC, reducing business opportunities.
- The Geoservices REST API overlaps in large proportion with existing OGC standards such as WMS, WCS, WFS, WMTS, CSW, with no effort made to reconcile with those standards.
- The standardization of WKT for Spatial reference systems is unfortunately currently quite weak in OGC standards. Geoservices REST API is tied with ESRI's version of WKT, which is not properly specified in the Geoservices REST API documents, and is known to be incompatible with other OGC documents, which will lead to a larger confusion. See the following [comment] for more details on this issue.
- No public response (nor private to the authors of the comments) has been made to the various comments sent on the OGC Requests mailing list in [July 2012] and [August 2012] during the 30 day public comments period.
- The Geoservices REST API can not be amended (other than editorial changes in the specification document), because of a requirement of backward compatibility with ESRI implementation. Consequently, the standard is unlikely to improve, or its evolution will be only lead by ESRI.
Todo: please expand
- Explain how this standard came to be
- Based on Arc GIS Server API
- Attempted but failed to go through OGC fast track process
- Recent voting history: refer to: http://lists.osgeo.org/pipermail/discuss/2013-May/011602.html
Todo: Link to key external docs, such as the proposed standards