[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: How long before services sending/receiving XML might need replacemen
Given that systems typically hold data in some kind of code model before it is serialized to a final character encoded format required by the government such as XML, CSV (yes, right) or JSON, is there more reason to serialize it as XML or as another format such as CSV or JSON? Or is serialization to JSON so commonplace that there is little reason to look any further if given the choice? I could understand it if serialization to JSON poses a problem when the government puts necessary constraints on that JSON. Is the understanding of the practicalities of the possibilities for constraining the final, transferred data/document a reason to stick with XML? UTF-*, escaping, choices of alternatives in the text syntax, etcetera? On Tue, 9 Nov 2021 at 16:30, Stephen D Green <stephengreenubl@gmail.com> wrote: Hi XML Dev’ers, ---- Stephen D Green
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] |
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|