4 ms·
It depends. JSON is very fragile. You lose a tweet or two here or there, not a big issue. JSON will do it just fine. Your bank on the other hand will prefer X
by CCs 15y ago
It depends. JSON is very fragile.
You lose a tweet or two here or there, not a big issue. JSON will do it just fine.
Your bank on the other hand will prefer XML that can be validated with XSD and you don't lose your car payment. Or your salary deposit.
It's not academic, it's a matter of use case.
- drawkbox 15y agoThe example was largely web apis used for general consumption not private apis. But yes, in terms of financial/gov't there can be other requirements. Lots of those systems are more enterprisy and may need that. However the same things can be done no matter the format, it still happens in EDI for instance over EDIHTTP/AS2 for POs and Invoices to Wal-mart everyday, it is not locked to XML and validated schemas only. JSON can be used there as well such as stripe.com does. The messaging is independent from a solid system really, I am just talking what is easier for large web consumption.