Yes, there was a discussion on what representation/encoding we should use, JSON or XML. We took hums in the room to see preferences, and there was strong preference towards using JSON. One technical issue which came up: not all data structures we may want to reuse have a JSON representation, some only have XML. Can JSON include XML data structures, if yes, can someone point to a doc describing it? Otherwise we'll have to redefine them in JSON (this is what draft-das is actually doing).
Let me ask this: are there any objections to using JSON representation for the data format? Does anyone think that XML would be a better choice, and why? - Gabor -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of ext Teco Boot Sent: Friday, August 10, 2012 6:03 AM To: [email protected] Subject: [paws] XML schema versus JSON, vCard & iCal We had a discussion on XML vs. JSON. I prefer the one with most compact messages. On vCard and JSON: what is the status of "A JavaScript Object Notation (JSON) Representation for vCard"? http://tools.ietf.org/html/draft-bhat-vcarddav-json-00 On valid times: can we use same format as certificates? They have similar simple requirements: valid notBefore & notAfter. http://tools.ietf.org/html/rfc3280#section-4.1.2.5 Teco _______________________________________________ paws mailing list [email protected] https://www.ietf.org/mailman/listinfo/paws _______________________________________________ paws mailing list [email protected] https://www.ietf.org/mailman/listinfo/paws
