XML.orgXML.org
FOCUS AREAS |XML-DEV |XML.org DAILY NEWSLINK |REGISTRY |RESOURCES |ABOUT
OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: [xml-dev] It's too late to improve XML ... lessons learned?

Isn't saying "the problem is that the SGML and XML designers never really imagined how popular XML would become for pure data interchange applications" really just a reformulation for "XML was repurposed for data interchange when it was just meant as a markup language for encoding text"?

While I don't find using XML for data exchange terrible, I see a lot of misconceptions stemming from this misuse. For example, the endless attributes-vs-elements usage discussion. Or, in fact, proposing to remove entities - a markup language without even text macros would be laughed out of the room as an authoring language. XML's sin facilitating XXE was to allow unbounded entity expansion (when it otherwise put severe restriction on entities) while SGML has CAPACITY ENTLVL.

Best,
M. Reichardt
sgml.io

> Am 29.12.2021 um 16:31 schrieb Michael Kay <mike@saxonica.com>:
> 
> the problem is that the SGML and XML designers never really imagined how popular XML would become for pure data interchange applications


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


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS