In order to provide contextual error messages, and otherwise plan ahead to facilitate UI building, request validation, and so on, we need a more explicit mechanism to allow schema types to declare themselves, other than the existence of a collection of normalizer services.
In #2868562: Better error messages → I explored this via a plugin mechanism, though in practice it could be that a service collector is just as effective. Either way, the primary need right now is in metadata entries rather than per schema type logic.
As a nice-to-have, it would be possible for a schema type to declare an associated MIME-Type, and have SchemataServiceProvider register that content type header for the serialization format. Doing this is a future scope thing, but will have to be researched a bit to identify if it's possible and how to see how that influences the implementation here.
None.
Additions.
None.
Needs review
1.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.