Part 4/CRUD: Co-branding as Common Part 5

[cportele]

Following the proposal to co-brand "Schemas" as both OGC API Features Part 5 as well as OGC API Common Part 3, it should be considered to co-brand also "Create, Replace, Update and Delete" as both OGC API Features Part 4 as well as OGC API Common Part 5.

All requirements classes should use ogcapi-common-5 in the URIs except for the requirements/conformance classes "Features", which should use ogcapi-features-4 in the URIs.

[cportele]

Meeting 2025-10-06: Propose this to the OGC API Common SWG (@jerstlouis and Joan Maso).

[jerstlouis]

@cportele The one difference with Schemas with CRUD is that while Schemas define a specific resource / path, the CRUD requirements are kind of abstract and still need to be tied with a particular resource.

So while we could write an ATS for them, it is difficult to write an ETS.

There's also some specific language that could perhaps be generalized e.g.,

A server that implements this requirements class provides the ability to add, replace and/or remove individual resources from a collection.

Since we're using collection with a very specific meaning of data in OGC APIs, that should probably be generalized so that it could be applied to e.g. Styles and Processes.

[cportele]

Meeting 2025-10-06: Review the generic requirements classes for the language that should be generalized. Maybe also move CRS handling to a separate generic requirements class (and maybe other aspects from the "Features" requirements class).