Next Wednesday, the OSGeo Board will deliver an Open Letter to the OGC and OGC voting members, with multiple signatures, demonstrating the large number of people concerned about the negative consequences associated with making the "Geoservices REST API" an OGC standard.
In what has become the OGC’s most contentious vote to date, OGC members are being asked whether the proposed "Geoservices REST API" should be accepted as an OGC standard. A summary of concerns are listed in an Open Letter from the Open Source Geospatial Foundation (OSGeo) to the OGC. However, the crux of contentions hinge around the definition of an Open Standard and whether the "Geoservices REST API" qualifies as one.
This page aims to collate community concerns related to the adoption of the "Geoservices REST API" document as a standard of the Open Geospatial Consortium (OGC). The page has been collaboratively edited, and delivered by the board of the OSGeo Foundation (OSGeo) to the OGC and OGC voting members on Friday 17 May 2013.
We are starting the build cycle for the 7.0 OSGeo-Live DVD/USB/VM which will be released in September 2013, ready for the
The UK Government have defined excellent design principles for deploying digital services, which is broadly applicable, and should be considered, by anyone developing applications for the web. They are summarised below:
A productive virtual meeting of the OSGeo Board resulted in general consensus over OSGeo's priorities, which in turn should help the OSGeo Board and OSGeo committees when guiding OSGeo into the future.
These principles are:
Increased quality
As we are wrapping up the OSGeo-Live 6.5 release, it is worth taking stock of the progress made during our recent OSGeo-Live Quickstart Hackaton. This was kicked off by a 48 hour intensive hackathon, followed up by a couple of weeks, addressing issues found.
