| Dear all,
With this email I would like to raise your awareness of the API Ad-Hoc at the upcoming OGC Nottingham TC meeting.
What started as an innocent discussion at the Barcelona TC, raised an interesting discussion (how to call the various available API’s, how are they created, best practices, ...) and continued in the Boulder PC meeting with an action to create a paper about API’s and the OGC. We would like to continue the discussion with a wider group at he Nottingham TC in an Ad-Hoc meeting (Tuesday, 15 September at 17:15 - 19:00).
Here are the topics for the Ad-Hoc that came up in previous discussion and meetings: - API’s and the OGC (OGC defines interfaces that enable interoperability of geospatial applications and API’s are a popular method to define interfaces for accessing spatial data in a web browser)
- Agreement on terms, What is an API and what sort of API's do we know ()
- REST, Web API’s
- WebIDL, OGC GeoAPI, ...
- API, SDK, Libraries (Library API’s), toolkits, ...
- OGC geospatial API’s are implementation independant
- use of W3C IDL, other
- what about API that are not implementation independent? (OpenLayers, CMAPI, Leaflet, …)
- Agreement on OGC specifying reusable constructs for RESTful Web APIs
- Use of small bits of OGC for web api providers (WKT, WMTS, CQL/Filter, geoPackage, …)
- API's as defining key geospatial constructs and functionality
- brokering/transformations between the various API’s and representations
- Moving forward
- convergence of Library APIs?
Knowing ourselves, we can spend an entire week on these topics - so we will carefully time manage the meeting so that all topics can be discussed. If need be, we can continue in follow-up calls and meetings.
Overall purpose of the Ad-Hoc is to make sure we agree on terms and start to form ideas on how the OGC should be dealing with API’s in the future.
I look forward to a spirited Ad-Hoc Bart
The calendar invite: |
