Consider making finer-grained conformance classes

[bradh]

Requirement class http://www.opengis.net/spec/ogcapi-movingfeatures-1/1.0/req/movingfeatures is fairly large, and potentially involves data types and functionality that not all implementations will need.

For example, where the OGC API for Moving Features is a facade over an existing system, it may not be desirable to allow anything other than "query" (i.e. GET). The create/replace/update/delete operations are required by the conformance class, but may not be desired (or implementable) on the system.

Even if there is support for making changes, the underlying data model may not be suited to DELETE of a single geometry on the MF.

(I'm still trying to get all of the operations clear, but it looks like support for MF Prism is also required, even though the underlying data might only be easily represented in Trajectory).

Suggest breaking out at least the simple "GET me a moving point" functionality, and ideally each logical block of functionality that can be meaningfully implemented on top of that.