The chairs discussed with the AD, and we came up with the following action plan to drive this wg to a consensus on the json vs xml encoding: we'll collect an objections list for json and one for xml, listing what is seen wrong/problematic with that encoding. The chairs and the wg will go through that list and see if the objections are valid, then decide which encoding has more support and choose that one. If we end up with good objections list for both, we may choose to support both encodings, as that list will justify the decision once the document advances to the iesg.
I went through the emails and I found so far the following valid objections: xml: too verbose, may be a problem to be supported in embedded devices current trend for APIs in the browsers is towards json json: some data structures are encoded in xml, a json encoding for those would need to be defined (which is not impossible, but requires some extra work) If you have additional objections, send them to the list asap. - Gabor
_______________________________________________ paws mailing list [email protected] https://www.ietf.org/mailman/listinfo/paws
