Part 4: application/json as media type?

[m-mohr]

Chapter 10 in Part 4 lists some media types for GeoJSON Features that are submitted through the CRUD endpoints:

The media types for the CREATE, REPLACE and UPDATE requests as well as for the schema documents depend on the representations of the resources.

For GeoJSON features,

• CREATE and REPLACE operations will use application/geo+json,
• UPDATE operations will use application/merge-patch+json,

What happens if I submit the more generic application/json instead?
I'm asking because most STAC tooling actually seems to just use application/json right now.
Is that valid? Is that getting rejected? ...

Also:

• schema documents will use application/schema+json.

How is this relevant here? I didn't see any endpoints that were meant to update schema documents?!

[cportele]

Meeting 2024-08-26: In the standard, the proper media types will be used. Implementations can be more lenient and accept application/json, too. The current requirements do not prohibit that application/json is used / supported, if the server wants to be more flexible.

Regarding the question regarding the schema media type, this has to be mentioned in the media type section, because schemas are relevant to understand the resource schema to construct create/replace/update requests.