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] What does it mean to say that XML was over-engineered?

On Tue, Sep 14, 2021 at 11:10 PM Michael Kay <mike@saxonica.com> wrote:
>
> By over-engineered I mean that it has more functionality than most applications require.
>
> Things like DTDs, namespaces, processing instructions, which add substantial complexity to applications and APIs whether you use them or not.
>

DTDs don't really bother me. Internal DTD subsets are where the
problems arise. If we had stuck to external DTDs that were only
optionally processed and predefined all the HTML entity references, a
lot of problems would go away. Also minimal parsers would be much
simpler and possibly faster.

Processing instructions maybe aren't needed but don't cause a huge
amount of problems.

Namespaces are necessary but almost certainly could have been done better.

-- 
Elliotte Rusty Harold
elharo@ibiblio.org


[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