XML Editor - Download a Free Trial >
See What's New >
Buy Now >

[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: The Goals of XML at 25, and the one thing that XML now nee

  • From: Rick Jelliffe <rjelliffe@allette.com.au>
  • To: xml-dev <xml-dev@lists.xml.org>
  • Date: Tue, 20 Jul 2021 16:43:59 +1000
Re: The Goals of XML at 25
Play the video
Let the dead bury the dead! 

Another adage is that anything that does not grow dies. I think XML has reached that stage.  It continues to be fine for what it does, but it is not now a technology that opens new doors or promotes new efficiencies. Which is just not a necessary or desirable fate. 

XML is now at a much worse stage than where SGML was in 1995:  standardized, adopted, stable, fit for purpose, but essentially solving the problems of the 1980s in a 1970s kind of way. And with a weeny technology  (HTML)  that could not possibly be considered a competitor or alternative because of its features, but sure was being adopted in that spirit. 

XML was a really great subset of the SGML idea for Web backends, meeting its goals well. It is possible to make different offspring from the SGML wellspring that meet other goals.  IMHO, parallel-parseability is meets a constant demand and is a good goal, and inplace parsing is a low-hanging fruit on this.

 By parallel-parseability I suppose I mean non-modal or random-access parsing: that you should be able start at any point in a document and figure out whether you are in tagging or data by parsing forward until the next milestone delimiter (i.e. > or ;) which then tells you what you started in.  When get this by not allowing modes, or allowing delimiter strings to serve double duty. So you can sick any number of threads onto different locations in the document and they will be able make sense of it without needing to know what went on before.

Cheers
Rick

Cheers
Rick


On Tue, Jul 20, 2021 at 4:07 PM Ihe Onwuka <ihe.onwuka@gmail.com> wrote:

On Mon, Jul 19, 2021 at 11:04 PM Rick Jelliffe <rjelliffe@a...> wrote:
.....

(Now, I am not saying that for data JSON is always the best, nor that XML doesn't have other features that may make it best to provide feeds in both JSON and XML, nor that if you currently have a good XML infrastructure you should rip it up and not take advantage of it.)

 You may not be saying that but that's the sentiment behind JSON for enterprise integration, we killed XML or JSON ate it's lunch. So NIEM, FPML and god knows who else end up having to put out a JSON spec even though JSON is not capable of representing the semantics in those data models. 

 
[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!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
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.

XML Editor - Download a 15 Day Free Trial Now >
See What's New in Stylus Studio >
Buy Stylus Studio - XML Editor - Now >
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.