Extend the Maps API metadata model to include a 'rel' to a map

[ghobona]

Maps API should extend the metadata model for the styles to include a 'rel' to a map.

[jerstlouis]

Is the issue title right? Is this talking about the Styles metadata model ? (e.g. /styles/{styleId}/metadata) or the map metadata (a /map/metadata which is not yet defined and which may not be necessary after all based on recent discussions).

[pomakis]

If a client wants to get a map of a collection without concerning itself with styles, it goes to collections/{collectionId} and sniffs out the "map" link. However, if it wants a map of a particular style, no such link exists in the collections/{collectionId} document (nor, I would argue, should it). The natural thing for a client to do would be to go to collections/{collectionId}/styles/{styleId} and sniff out the "map" link there. So either the "OGC API - Maps" standard or the "OGC API - Styles" standard (I'm not sure which) needs to indicate that the proper place for style-specific "map" links to go is in the collections/{collectionId}/styles/{styleId} resource.

[jerstlouis]

@pomakis correct a rel: "map" link should be included at collections/{collectionId}/styles/{styleId}.
Maps should define the relation type to use (http://www.opengis.net/def/rel/ogc/1.0/map) and Styles defines that links can be included. I'm not sure if we should have any normative reference to Styles in Maps though, but there could certainly be informative text to that effect.

Right now there are "Dataset map" and "Geospatial data map" conformance classes, but no "Style map" conformance class.

Actually Permission 2 B (in GeoData map conformance class) already says:

the dataset that is modified or complemented by the /styles/{styleId} path fragment can be considered modified dataset resources that can be exposed as a map. The link to the map resource will be added to the /styles GET response

so that seems covered for "Geospatial data map". There doesn't seem to be a separate permission for "Dataset map", but Permission 2 already talks about a dataset.

[jerstlouis]

I believe that we settled on how this should work, and only need to update the specification to reflect it.
(The title of the issue is confusing though, as this does not really concerns map metadata anymore).

[jerstlouis]

Requirement 21 already includes the http://www.opengis.net/def/rel/ogc/1.0/map link relation, but also includes map-meta which may be obsolete. Can we get rid of this map-meta?

[jerstlouis]

It seems that map-meta is gone already. Can we close this issue?