Difference between revisions of "Geoservices REST API"
Wiki-Woodbri (talk | contribs) (→Signed) |
(→Signed) |
||
| Line 16: | Line 16: | ||
''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.'' | ''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.'' | ||
| − | * [[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 [http://lisasoft.com LISAsoft], core contributor & coordinator of [http://live.osgeo.org OSGeo-Live] |
* [[User:Woodbri|Stephen Woodbridge]], Director of [http://imaptools.com iMaptools.com], Contributor and/or PSC of [http://mapserver.org Mapserver], [http://pgrouting.org/ pgRouting], [http://www.pagcgeo.org/ PAGC], and [http://www.postgis.org/ PostGIS] | * [[User:Woodbri|Stephen Woodbridge]], Director of [http://imaptools.com iMaptools.com], Contributor and/or PSC of [http://mapserver.org Mapserver], [http://pgrouting.org/ pgRouting], [http://www.pagcgeo.org/ PAGC], and [http://www.postgis.org/ PostGIS] | ||
* | * | ||
Revision as of 23:59, 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.
Open Letter to OGC and voting members
Please don't edit this "Open Letter" statement, comments and discussion should go below.
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 "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.
Signed
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
Concerns
--- DRAFT ____
Please add concerns as bullet points below. Try to be concise. Where appropriate, link to external web pages (such as email achieves)
Summary
To do: Add a brief 3 paragraphs or so summarising the issues.
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
References
Todo: Link to key external docs, such as the proposed standards