API Views

[cmheazel]

Return to the issue of Views as discussed in Part 2. How should we formalize this concept?

[jerstlouis]

A collection of data may offer support for one or more OGC API specifications providing access to the data.
(e.g. Features and Tiles; Maps and Coverages; Features and Coverages...).

[cmheazel]

I believe this is addressed by allowing different collection paths to represent the data using different specifications. Since this requirement has already been addressed, we can close this issue.

[jerstlouis]

addressed by allowing different collection paths to represent the data using different specifications.

Possibly here @cmheazel meant collection sub-resources paths ?

It also requires different link relation types to link from the collection description document at /collections/{collectionId}, unless talking only about different representation based on a distinct media type.
Do we need to add clarification about this?

This is also the resolution of the big Collections Discussion ( #140 ).