[XML-DEV Mailing List Archive Home]
[By Thread]
[By Date]
[Recent Entries]
[Reply To This Message]
Re: Re: How long before services sending/receiving XMLmight ne
- From: Stephen D Green <stephengreenubl@gmail.com>
- To: Jim DeLaHunt <list+xml-dev@jdlh.com>, XML Developers List <xml-dev@l...>
- Date: Sat, 13 Nov 2021 08:50:11 +0000
Hi Jim
Isn’t that on an assumption that the data is persisted in the format it was exchanged? Wouldn’t it be more likely that the exchange format will be transient, deleted immediately it has been deserialised?
Regards Stephen Green
Stephen:
Your question below frames the choice as about serialisation
options ("is there more reason to serialize it as XML or as
another format"). I would instead frame the choice as about what
kind of information artifact do you want to have: a pile of
information encoded using XML, or using CSV, or using JSON? I
would make that choice in part with an eye to how long will that
pile of information persist, and what someone might want to do
with it 20 or 30 years in the future.
What I take from the conversation on this list is that if the
information is encoded using the right XML language (and schema
etc.) then it will be a more comprehensible, re-usable, and thus
more valuable asset in future decades with future systems, than
will be the same information encoded as CSV, or worse yet, JSON. I
could be wrong about that. I'm not an expert.
But I do think that it matters how you frame the choice.
—Jim DeLaHunt
On 2021-11-12 04:58, Stephen D Green
wrote:
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?
Hi
XML Dev’ers,
Do you have any opinion on how long software
systems communicating with each other (one-way or two-way)
using XML might be able to continue to use XML this way?
If, say, governments currently require data or documents
to be sent to them in XML format, what professional advice
would you suggest about how long would be reasonable
before this use of XML should be replaced? Or do you think
such uses of XML could reasonably be perpetual?
Many thanks for your consideration.
Stephen 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
RSS 2.0 |
 |
Atom 0.3 |
 |
|
Stylus Studio has published XML-DEV in RSS and ATOM formats,
enabling users to easily subcribe to the list from their preferred news reader application.
|
Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website.
they were not included by the author in the initial post. To view the content without the Sponsor Links please
click here.
|
|