[Home] [By Thread] [By Date] [Recent Entries]

  • From: Ihe Onwuka <ihe.onwuka@g...>
  • To: Rick Jelliffe <rjelliffe@a...>
  • Date: Sun, 18 Jul 2021 14:15:30 -0400

Just want to comment on the terseness angle.

In other domains the need for a data preparation step to tame obnoxiously formatted data before it is used is generally accepted and not controversial. When it concerns XML however no such step is contemplated and instead we get specious interminable whining about  bloat and verbosity. 
Here is an past example of 324k JSON data naively converted to 1.16MB of XML which reduced to 350K of XML after some 'data prep'.


I believe it's generally the case that with such a step the size of "equivalent" JSON and XML is within about 10% of each other.




On Sun, Jul 18, 2021 at 4:37 AM Rick Jelliffe <rjelliffe@a...> wrote:
While in lock-down, I took the time to write down a little post for Schematron.com called "The Goals of XML at 25: and the one change that XML really now needs"  which people interested in the past and future of XML may find familiar but not irrelevant.

Key passage, or twist:

"For several decades I have dabbled with methods to speed up parsing UTF-8 and XML using SIMD and parallel parsing: my conclusion is that the approach I am suggesting here is the only feasible way for XML to not be sidelined as slow and complex. I think the lack of papers and experience demonstrating otherwise indicates it too.)"

Regards
Rick

(Here in Sydney we are in lockdown again, after an exiled year of almost no cases, Delta broke through, and we are trying to eliminate it. Taiwan successfully eliminated it this month, so maybe we will: elimination is a feasible strategy on islands, rather than just suppression. I get my 2nd vaccine tomorrow.)



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]


Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member