OGC API - Common

[cportele]

WFS has been the first group within OGC to work on a revision of an OGC Web Services standard as a Web API with OpenAPI support. By now, several other groups in OGC are working on similar revisions, too.

Common elements in OGC APIs have been discussed now for several months and the OWS Common SWG has agreed to

• work on the common API elements underlying all OGC APIs;
• do this in a public repository (https://github.com/opengeospatial/oapi_common);
• provide an initial draft based on what is currently in WFS 3.0 as the starting point for the discussion (March 2019);
• provide another draft release by the end of May 2019 as input to discussions at the OGC meeting in Leuven, June 24-28, 2019, where the goal is to resolve all remaining hard issues.

If this process is successful, the WFS standard would be updated in the future to reuse the relevant API elements specified in the OGC API - Core standard once it has been published.

[cportele]

An issue on the link object has been raised in the OGC API Common discussions.

See https://github.com/opengeospatial/oapi_common/issues/27.

[cmheazel]

The September-2019-re-syc branch of API-Common contains the latest proposed updates to the API-Common specification. These updates synchronize API-Common with the approved API-Features standard and address the recomendations from the API Hackathon. A partial review of this branch was performed by the SWG at the Banff TC, but there was insufficient time to complete the review. Telecons will be scheduled to complete the review, identified changes applied, and the branch merged into Master.