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 bet many other applications will have to deal with a variety of content types, like hcard, vcard, portable contacts, and others that might use something else.
Paul -------- Original Message -------- From: SM <s...@resistor.net> Sent: Sat Apr 21 16:03:53 EDT 2012 To: "Paul E. Jones" <pau...@packetizer.com> Cc: oauth@ietf.org, apps-disc...@ietf.org Subject: Re: [apps-discuss] [OAUTH-WG] Web Finger vs. Simple Web Discovery (SWD) 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 a choice. Encouraging such a polygamous relationship can only end up badly. RFC 6415 was published in October 2011. Switching preferences in less than a year raises some issues about the nature of relationships. Anyway, whether someone break something is not as important as picking one option. Regards, -sm
_______________________________________________ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth
