Open alexrobin opened 1 year ago
Right now we have separate conformance classes for encodings, e.g. GeoJSON, SensorML JSON, etc.
And then we have a conformance class for Create/Replace/Delete operations.
But how can an endpoint advertise that it supports resource creation but only for certain encodings (while it may support all encodings for reading).
One place we can advertise this is in the OpenAPI document but do we also need conformance classes for every possible combination?
Right now we have separate conformance classes for encodings, e.g. GeoJSON, SensorML JSON, etc.
And then we have a conformance class for Create/Replace/Delete operations.
But how can an endpoint advertise that it supports resource creation but only for certain encodings (while it may support all encodings for reading).
One place we can advertise this is in the OpenAPI document but do we also need conformance classes for every possible combination?