Tim,
When I talk about existing software I'm referring to generic JSON
parsers such as are included in the basic library set of every
programming language now, and which are unfortunately idiosyncratic
and inconsistent in their handling of dupe keys, but in almost no
cases actually inform the calling software whether or not dupe keys
were encountered.
Thanks for the clarifying comments. I am still a bit puzzled, though. I
thought JWK was
a proposal to establish JSON formats for key transport. Are you saying
that the formats we are
about to standardize have been in use in JSON for a while and that's why
parsers are not
prepared to reject dupe keys? Or is this a lower layer, JS issue re
partsing?
Steve
_______________________________________________
jose mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/jose
