Michael, > > am NOT okay with making it the only one, and I am even less okay with > > mandating it is the ONLY one. I would say MUST JSON, MUST (or > > possibly SHOULD -- you can convince me either way) XML, and MAY for > > anything else that people feel stronly about (although I feel in 2012 > > XML and JSON are the two best). I also feel it is okay to say that a > > client MUST implement one of JSON or XML, and MAY implement more. > > > > > > Why not MUST ASN.1 while you're at it? JSON has won in case you'all > haven't noticed it.
"Won"? Data formats are not popularity contests. This is the Internet Engineering Task Force, not the Internet Entertainment Task Force. (That said, a few recent message have been entertaining.) We should be building and designing systems for longevity. XML was absolutely *the* thing just a few years ago and now JSON is all the rage. How long will that last before "the next great thing" comes along? There are many people who value XML still, in spite a growth in the use of JSON. Paul _______________________________________________ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth
