You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The spec needs to be using a vendor prefix, or register the media type with the IANA. The x- prefix isn't a vendor prefix and still requires registration.
If the registration process seems complicated, well, the whole point of having a specification is to do all the heavy lifting of examining how it interoperates with other specifications, so that developers don't have to. It's not something to skimp out on.
Aside, an RFC is probably one of the easiest kinds of technical documents to publish.
This doesn't seem like a fun thing to do. But it would be nice to get
application/ndjson
approved instead of usingapplication/x-ndjson
.Here is a form for that http://www.iana.org/form/media-types, but it required all kinds of considerations.
The text was updated successfully, but these errors were encountered: