radiantearth
Templated Links
Templated links have been defined in OGC API - Records (see e.g. https://github.com/opengeospatial/ogcapi-records/issues/234 ).
What should we do in STAC about it? The web-map-links extension already provides templated links and we should probably add a framework in stac that extensions can use for templated links.
Related: https://github.com/stac-extensions/web-map-links/issues/15
Discussion happening at https://github.com/opengeospatial/ogcapi-common/issues/187
We prefer the linkTemplates approach as proposed in https://github.com/opengeospatial/ogcapi-records/pull/290 although we are slightly concerned about the camel case.
The issue will be discussed in the OGC Architecture DWG next week.
Please find below a link to a Doodle poll for scheduling a discussion on templated links. https://doodle.com/meeting/participate/id/epzwRgVb Please enter your availability by 09:00 AM EDT this Thursday 12th October .
Posted by @ghobona at https://github.com/opengeospatial/ogcapi-common/issues/187#issuecomment-1752826598
It looks like OGC will switch to using a property called "linkTemplates" based on https://ietf-wg-httpapi.github.io/link-template/draft-ietf-httpapi-link-template.html . I think this is the best solution we could get from this "conflicting" situation. I'd propose to make this an extension and not adopt it in core.
The only STAC-related thing that really needs a change would be Web-Map-Links extension, as far as I know. It also may need some work in the STAC API world.
So since this is to be an extension I think we can drop the 1.1 milestone here
