/req/pre-defined/collection-naming

INSPIRE-MIF / gp-ogc-api-features

Good Practice document for INSPIRE download services based on OGC API - Features

13 stars 12 forks source link

/req/pre-defined/collection-naming #12

Closed cportele closed 4 years ago

cportele commented 4 years ago

... the name of the collection SHALL be the language-neutral name of the feature type as specified in the IRs for ISDSS

Then the examples need to be updated as they use buildings not Building or addresses not Address.

alexanderkotsev commented 4 years ago

@cportele - well spotted. Thanks. One additional issue to consider here would be case sensitivity. Maybe we can recommend, or explicitly ask url paths to be provided as lowercase. Additional details on that are provided in https://www.w3.org/TR/WD-html40-970708/htmlweb.html

heidivanparys commented 4 years ago

One additional issue to consider here would be case sensitivity. Maybe we can recommend, or explicitly ask url paths to be provided as lowercase.

Then we need to state very clear that the interpretation of IRs for ISDSS is that the case is not specified by these IRs, but will depend on the exact technology used and best practices for that technology.

alexanderkotsev commented 4 years ago

The issue of naming of collections is addressed in 9877944