JSON-AD MIME type registration at IANA

[joepio]

Since the JSON-AD serialization format should have a mimetype for HTTP requests, it should officially be registered at IANA. That's why I've started an application procedure there to register it.

However, it seems like an RFC document is required (if you're not a standards organization, and if you're not willing to put vnd in the string). I'm not very excited on writing a lengthy, detailed, technical document that few will read, so this is unfortunately not something that I'm likely to do in the near future.

Some very notable standards such as TOML, phpm YAML, rust, typescript are completely absent in the official IANA list, sometimes leading to serious confusion.

I'll keep this issue posted on the process. There is a chance that application/ad+json will have to change to application/vnd.ad+json... Which is horrible.

[aschrijver]

The docs for JSON-AD mention the mime type and 'registration pending', but in the referenced issue above you say:

Ideally, we'd also register a MIME type (and the file extension) at IANA for hextuples. I've tried that [in this issue] but it was quite a bothersome process, so I never completed it.

Does that mean that it won't be registered?

(PS. This issue is not migrated to the other repo. Hence asking here)

[joepio]

Hi @aschrijver, no I'm not planning to! If someone else would like to do this I'd gladly help.