The 1.7.0 release contained #166 / #181 feature that allowed defining schema files with descriptive elements (title, description, etc) in different languages. This allowed collections/(collection)/schema resource to support lang param or Accept-Language header when showing schema.
When documenting OGC API Features service in a developer portal that support multiple languages, it might be nice, if such portal documentation could link to different language versions of landing page, collections list, etc. HTML pages that the service provides.
This might mean possibility to add i18n support on Hakunapi properties like api.title, api.description, etc. and documenting how basic text resources (used by Hakunapi server) are configured.
The 1.7.0 release contained #166 / #181 feature that allowed defining schema files with descriptive elements (title, description, etc) in different languages. This allowed
collections/(collection)/schemaresource to support lang param or Accept-Language header when showing schema.When documenting OGC API Features service in a developer portal that support multiple languages, it might be nice, if such portal documentation could link to different language versions of landing page, collections list, etc. HTML pages that the service provides.
This might mean possibility to add i18n support on Hakunapi properties like
api.title,api.description, etc. and documenting how basic text resources (used by Hakunapi server) are configured.