Difference between revisions of "Geoservices REST API"
| Line 8: | Line 8: | ||
= Open Letter to OGC and voting members = | = Open Letter to OGC and voting members = | ||
| − | + | May 2013 | |
| − | + | 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 standard be rejected in its current form. |
| + | |||
| + | People have listed different reasons for concern. They are expanded upon below. | ||
== Signed == | == Signed == | ||
| + | Please include name, work title (if appropriate), very brief title/involvement in OSGeo if appropriate. Eg: developer on X and Y. (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. | ||
| + | |||
* [[User:camerons|Cameron Shorter]], Geospatial Solutions Director at LISAsoft, core contributor & coordinator of [http://live.osgeo.org OSGeo-Live] | * [[User:camerons|Cameron Shorter]], Geospatial Solutions Director at LISAsoft, core contributor & coordinator of [http://live.osgeo.org OSGeo-Live] | ||
| − | * | + | * |
= Executive Summary = | = Executive Summary = | ||
Revision as of 14:34, 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
May 2013
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 standard be rejected in its current form.
People have listed different reasons for concern. They are expanded upon below.
Signed
Please include name, work title (if appropriate), very brief title/involvement in OSGeo if appropriate. Eg: developer on X and Y. (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
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