Note that requiring both would only be on the server side. While JSON might be
the new hip format, I suspect some will use XML for some time. And there are
some link relations that might point to XML content. For certain applications
like OpenID Connect, they could get by with JSON only, but I b
Hi Paul,
At 20:34 20-04-2012, Paul E. Jones wrote:
My preference has been MUST for XML and JSON since 1) XML is already a MUST
in RFC 6415 and we'd have to "break" what is there now to remove the MUST
and 2) people are clearly demanding JSON.
MUST for XML and JSON offers choice but it does make
That might have happened had there been some free high-quality ASN.1
software, instead of slow buggy parsers that cost $50K to license.
It’s always seemed to me that one reason XML took off so fast is that
there were fast robust open-source parsers in C and Java before the
spec was even finalized.
