Part 4/CRUD: PATCH using JSON Merge Patch #1023
Description
The current draft requires that the PATCH payload is in JSON, but not on the basis that the JSON representation of the feature is GeoJSON. This is confusing.
When a client sends a POST or PUT with a feature in JSON, it will in almost all APIs be represented in GeoJSON (with or without the JSON-FG extensions). When a client wants to patch the same feature, the client currently has to use a different JSON representation of the feature.
It would be more consistent and intuitive to apply the JSON Merge Patch payload against the GeoJSON representation of the feature, if the API accepts GeoJSON as the payload of a POST/PUT request.