Confusion about the API definition requirement

[tschaub]

Section 12.2 says that

Every API implementation should provide an API Definition resource that describes the capabilities provided by that API.

The /req/landing-page/root-success requirement in 12.1.2 says that

The content of that response SHALL [...] include links to the [...] API Definition

I'm guessing that the intention is that implementations of the core conformance class (http://www.opengis.net/spec/ogcapi-common-1/1.0/conf/core) are required to have an API definition. The mix of "should" and "SHALL" above make me a little uncertain about this though.

[jerstlouis]

@tschaub My understanding is that the "Core" requirements class does not require landing page, conformance declaration or API definition. Only the landing-page conformance class requires that.

The should is a recommendation that OGC API implementations also support the landing-page conformance class.

I think some of the dependencies in Tiles, Maps, Coverages, DGGS regarding "dataset / API" origins should be to the "landing-page" rather than the "core" of Common-1 as they are incorrectly right now.