[Dutch] Fwd: Would you be concerned if the "GeoServices REST API" became an OGC standard?

[Jeroen Ticheler]

Beste mensen,

Op OSGeo Discuss is een intensieve discussie gaande over een mogelijk nieuwe OGC specificatie genaamd GeoServices REST API. 

Lees hieronder, lees de hele conversatie op http://lists.osgeo.org/pipermail/discuss/2013-May/thread.html 

De discussie is belangrijk omdat de geloofwaardigheid van OGC als standaarden organisatie op het spel staat. Dus schroom niet en laat je horen.

Groet,
Jeroen
____________________________________________________
GeoCat introduces Bridge© 
An extension to ArcGIS© to instantly publish data and metadata on GeoServer and GeoNetwork.
See http://geocat.net for more details. 

Jeroen Ticheler
GeoCat bv
Veenderweg 13
6721 WD Bennekom
The Netherlands
Tel: +31 (0)6 81286572
http://geocat.net

Begin forwarded message:

> From: Cameron Shorter <cameron.shorter op gmail.com>
> Subject: [Board] Would you be concerned if the "GeoServices REST API" became an OGC standard?
> Date: 4 mei 2013 12:46:33 CEST
> To: OSGeo Discussions <discuss op lists.osgeo.org>
> Cc: standards op lists.osgeo.org, OSGeo-Board <board op lists.osgeo.org>
> 
> OSGeo Community,
> 
> Currently, voting OGC members are to decide whether to accept the "GeoServices REST API" as an OGC standard. This is already a contentious issue, with 13 votes for, and 10 votes against, 72 outstanding votes, with voting halted temporally, being reopened again in a few days, and closing 2 weeks after that. [1]
> 
> I'm wanting to hear whether people in the OSGeo community have strong opinions regarding this proposed standard, and whether we as a collective OSGeo community should make statements to the OGC, and voting OGC members, stressing our thoughts.
> 
> If there is sufficient interest, I'll raise this issue with the OSGeo Board, with the intent of drafting a statement on behalf of OSGeo.
> 
> As background:
> * "The API was initially developed by Esri and implemented on the ArcGIS for Server platform." [2]
> 
> * The proposed GeoServices REST API specification overlaps with most OGC standards already deployed, including: WMS, WMTS, WCS, WFS, SE/SLD, CS/W. This effectively means that for most use cases covered by the GeoServices REST API, applications would now have two standards to support. Also, spatial infrastructure programs will be impacted, as OGC compliance won't necessarily equate to interoperability.
> 
> * Most (all?) current OGC web service standards to date have an Open Source reference implementation, which was often (always?) part funded by OGC testbeds, and open source implementations were tested against proprietary implementations during OGC testbeds. As far as I'm aware, there has been very little up-take from the Open Source community of the "GeoServices REST API", and I'm unaware of any testing of non-ESRI applications during OGC testbeds. (Someone may be able to correct me here).
> 
> [1] https://portal.opengeospatial.org/?m=projects&a=view&project_id=82&tab=5&subtab=0
> (OGC member login required. Votes counted as at 4 May 2013)
> 
> [2] http://www.opengeospatial.org/standards/requests/89
> 
> -- 
> 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
> http://www.lisasoft.com
> 
> _______________________________________________
> Board mailing list
> Board op lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/board

------------- volgend deel ------------
Een HTML-bijlage is gescrubt...
URL: <http://lists.osgeo.org/pipermail/dutch/attachments/20130507/6e90a599/attachment.html>