On Sat 16/May/2020 19:48:25 +0200 Hector Santos wrote: > > One can suggest XML is also complex to get right. The direction has been with > JSON for a number of years, especially with the JavaScript developers using > established tools and platforms based JSON. The APIs are readily available.
Yet, XML has style sheets, XSLT, that JSON seems to be still missing. A noticeable amount of web stuff uses XML and XHTML. Dropping those languages entirely is a harsh decision for an online entity. > Just consider, when the spec has XML-only, then for those who use a solid JSON > I/O system, they are now going to be required to add XML. So for them, its > additional development complexity. Everything they probably do JSON related. > The exception would be DMARC using XML. This alone can delay or push aside > DMARC Reporting implementation. So you intend to ease report producers... How about consumers? I figure producing reports is quite easier than receiving them, once you have the relevant data structures. You don't need an API to write the data, you need it to parse. Since receivers have to verify report correctness and trustworthiness, /they/ deserve the right to decide what language they want reports to be written in. That is the kind of approach taken for failure reporting, where receivers can specify by rf= "a list of one or more report formats as requested by the Domain Owner". Disabled developers who are unable to produce XML reports can still resort to automatic translation by json2xml. Best Ale -- _______________________________________________ dmarc mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmarc
