Difference between revisions of "Geoservices REST API"
Jump to navigation
Jump to search
| Line 25: | Line 25: | ||
= Technical Concerns = | = Technical Concerns = | ||
| + | |||
| + | = History = | ||
| + | |||
| + | 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 | ||
[[Category: OGC]] | [[Category: OGC]] | ||
[[Category: Standards]] | [[Category: Standards]] | ||
Revision as of 02:11, 7 May 2013
This wiki page aims to collate community concerns related to the proposed acceptance of the "Geoservices REST API" becoming an OGC standard.
May 2013
___ DRAFT ____
Open Letter to OGC and voting members
We, the undersigned have serious concerns related to the proposed approval of the "Geoservices REST API" as an OGC standard. If approved, we believe it will have costly, far reaching, negative impacts on interoperability, and significantly tarnish the OGC’s reputation as a champion of interoperability.
Some of the reasons for our concern include some of the following:
...
Signed
- Cameron Shorter, Geospatial Solutions Director at LISAsoft, core contributor & coordinator of OSGeo-Live
Executive Summary
Political Concerns
Commercial Concerns
Technical Concerns
History
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