Remove the path to items and its definition

[joanma747]

This issue has been created as part of the public review and is based on document 19-072. See in particular section 9.2.3.

Not all geospatial data is structured in "items". "/collections/{collectionsId}/items" is defined by "OGC API features" because they need it. OGC API coverages are planning to use /collections/{collectionsId} but they will never use "items". EDR are also using collections but they are not using items so far. The only other proposed OGC API candidate that I know is that proposes the use of "items" is OGC API records and it is still under discussion if this is convenient.

(the discussion on the convenience of the word "collections" versus "geodata" or similar is not part of the scope of this CR).

OGC API Common should NOT define "items". Please remove.

In addition also remove any reference to itemsType

[jeffharrison]

+1

[dblodgett-usgs]

This needs a motion at the next API Common meeting. Highly related to #107.

Motion: Remove items and itemType from OGC-API Common Part 2.

[cmheazel]

API-Common Part 2 has been rewritten so that /items is optional. The decision of whether or not to include /items will lie with the SWGs developing API Standards which build on Part 2.
This is an uncomfortable solution. /items is too useful to not make common, not universal so it cannot be mandatory, and too small to make its' own conformance class.

[bradh]

Maybe Common should provide a set of guidance / recommendations. Perhaps a pattern approach of describing the concept, showing an implementation, and noting benefits and (potential) downsides.

[cmheazel]

@bradh This material should be captured in the Users Guide, not the Standard. If someone were to contribute content for the Users Guide, then we can point to it from the Standard.

[cmheazel]

#221 removes the /items endpoint. That makes this issue OBE.