search

INSPIRE-MIF / gp-ogc-api-features

Good Practice document for INSPIRE download services based on OGC API - Features
13 stars 12 forks source link

Abbreviation "OAPIF" offers potential for confusion #24

Open jsaligoe opened 4 years ago

jsaligoe commented 4 years ago

The need for a shortened name for “OGC API Features” is apparent, and in the draft document “OAPIF” is used. However, this abbreviation is already used as the short name for the OGC API Features GDAL Driver https://gdal.org/drivers/vector/oapif.html and therefore could be confusing from a technical perspective to call it the same thing. Note also the discussion on naming convention provided in the implementation standard Abstract "That is, the title of this document in OGC is "OGC API - Features - Part 1:Core" and the title in ISO is "Geographic Information - Geospatial API for Features - Part 1: Core.""

For consideration, use a different abbreviation, such as "OGCAPI-F" or "GeoAPI-F".

alexanderkotsev commented 4 years ago

Indeed, the name (OAPIF) that we use is not ideal. We would like to rely on the OGC for a shorter name and not introduce a new one ourselves. Proposals for OGC API names are already discussed in https://github.com/opengeospatial/oapi_common/issues/35. Once the short names are officially confirmed by the OGC, we can go ahead and modify our document accordingly.

heidivanparys commented 4 years ago

Still no resolution at OGC on the short names as far as I know. What we could do is spell the name out in the specification, or use the OGC document numbers as a reference (OGC 17-069r4, OGC 18-058, etc.). The use of OAPIF in the URIs is more tricky though.