[Json] Media types, extensibility in draft-ietf-json-i-json-02

[Mark Baker <[e-mail]>]

Greetings,

There's no mention of which media type I-JSON content should use. A
quick check of the archives shows recent discussion about
application/xxx+i-json and application/i-json, but I don't know why it
isn't yet in the draft. I think it's essential to get this correct,
given the compatibility goals of the format.

FWIW, I agree that a non +json type is required, and also agree that
its short name should be usable as a suffix. So I'd personally go with
application/ijson and application/*+ijson as I expect many will find
the use of "-" confusing in suffix form.

The must-ignore/must-understand section also seems out of place here.
"must understand" has historically not referred to a lack of
extensibility, but to an inline declaration that some particular
extension cannot be safely ignored (see SOAP). Instead it's used here
as the opposite of "must ignore". And I also don't particularly care
for the characterization of the extensibility of a data format in
terms of implementation behaviour; the point is not that
implementations "must ignore" unknown extensions, it's that the format
is designed so it can be interpreted piecemeal[1], and that seems to
already be part of the assumed fabric of JSON (luckily, schema-think
hasn't yet taken over JSON-land) so doesn't seem worth mentioning. I'd
suggest removing this section.

 [1] http://www.w3.org/TR/1998/NOTE-webarch-extlang-19980210