On Tue, Sep 16, 2014 at 8:35 AM, John Bradley <[email protected]> wrote:
> > > > As Tim stated in a later message most of them don't reject or report > duplicate keys. > > He is proposing a new JSON profile I-JSON that changes that. > Actually, the JSON working group is under no illusion that shipping I-JSON as an RFC is going to magically cause existing JSON software to fix this issue (although I’m optimistic that implementations will pop up pretty quickly, because it’s not hard). The value of I-JSON is that it takes all the things that we’ve observed to cause interop problems in practical JSON, that in some cases have had to be explicitly argued-over in other contexts (like we’re doing here), and in a short simple document says “don’t do any of these things”. So it’ll be handy as a spec-writer’s tool even before the software catches up.
_______________________________________________ jose mailing list [email protected] https://www.ietf.org/mailman/listinfo/jose
