search

opengeospatial / ogcapi-discrete-global-grid-systems

https://ogcapi.ogc.org/dggs
Other
20 stars 8 forks source link

Decision needed on nomenclature for "Zonal Identifier" in the OGC API DGGS Specification. #57

Open geofizzydrink opened 2 years ago

geofizzydrink commented 2 years ago

Hi All,

Here's another issue I would like us to vote on (similar to the dggsRSID vs dggsID decision we need to make).

OGC Abstract Spec Topic 21 (ISO 19170-1:2021) describes "cell" identifiers as "zonal" identifiers, recognising that a more appropriate naming convention for a 2D cell in a multi-dimensional (spatio-temporal) infrastructure such as a DGGS is "zone", and when referring to a collection of one or more "zones" it is appropriate to use the term "zonal".

However, in terms of the naming conventions for resource elements of OGC APIs, using the term {zonalID} to access the description (or data holdings of) an individual DGGS Zone (e.g. /dggs/{dggsID}/zones/{zonalID}) appears both cumbersome and presents a possible risk of someone miss reading the OGC API DGGS specification depending on the font used to publish the specification (i.e. it is possible in a number of fonts to missread lowercase "l" and uppercase "I"). In this context it might be better to use the term "zoneID" instead of zonalID.

So, I would like to ask the question, which naming convention to we want to enshrine in the OGC API DGGS Specification:

  1. {zoneID}
    • following a very similar naming convention to that of the other OGC APIs
    • simpler and less prone to missreading due to font representations; or,
  2. {zonalID}
    • following the explicit naming convention defined in OGC Abstract Spec Topic 21 (ISO 19170-1:2021).

As the the dggsRSID vs dggsID question, I'd like us to hold a SWG vote on this during the next telecon if we have quorum.

AkexStar commented 1 year ago

Prefer to {zoneID} and {dggsID} It's important for endPoints to be simpler and shorter.