Re: Review of the OGC Architecture Board's API guidelines

I’ve also reviewed them, and have forwarded them to a few others who I know will have feedback.

There are issues already created that cover the concerns I have, largely related to pagination, 300 series http codes, and http methods.

Sent from my iPhone

On 11 Feb 2019, at 10:44 pm, Rob Smith <rob.smith@awayteam.co.uk<mailto:rob.smith@awayteam.co.uk>> wrote:

Linda,

As promised in the SDWIG telecon on 16th January, I’ve now had time to review the OGC Web API guidelines [1] and can report that they're clear and sensible. However, I can’t provide any feedback with respect to the Javascript library client API I’m currently designing for WebVMT, as the guidelines are specifically aimed at an HTTP server API and its syntax. Apologies.

I may be able to provide more comments in the future when the proposed WebVMT search experiment work [2, 3] progresses in OGC Ideas.

Rob Smith

Away Team
www.awayteam.co.uk<http://www.awayteam.co.uk>

[1] https://github.com/opengeospatial/OGC-Web-API-Guidelines

[2] https://github.com/opengeospatial/ideas/issues/91

[3] https://github.com/opengeospatial/ideas/issues/92


On 30 Jan 2019, at 13:22, Bill Roberts <bill@swirrl.com<mailto:bill@swirrl.com>> wrote:

Thanks Linda. I’ll take a look

On 30 Jan 2019, at 13:00, Linda van den Brink <l.vandenbrink@geonovum.nl<mailto:l.vandenbrink@geonovum.nl>> wrote:

Hi all,

I read the OGC API guidelines draft. If you were planning to review it, I can tell you the document is a short and good read, so reviewing it should not take much of your time!

For each topic in the guidelines doc they have already created an issue for the purpose of collecting comments about that topic. I left a few comments there.

The document is at https://github.com/opengeospatial/OGC-Web-API-Guidelines (don’t click the HTML and PDF links, they don’t work – just scroll to read the text directly from the readme.md)

Linda