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] Failed XML standards

On Sun, Nov 15, 2009 at 11:48 PM, Rick Jelliffe
<rjelliffe@allette.com.au> wrote:
> Elliotte Rusty Harold wrote:
> Let me put it like this: one of the original goals of XML was "The number of
> optional features in XML is to be kept to the absolute minimum, ideally
> zero." This was because the highly parameterized approach that SGML took was
> not appropriate, for various reasons: one of which was that if there were
> optional features, you could not be guaranteed that the recipient could
> handle your document.
> And so what happened after that?  A stream of piddly little standards for
> optional things: XBase, XInclude, xml:id.  And what is the result? It is
> impractical to rely on them: or, at least, they don't relieve the developer
> of any decision making or programming, since the developer has to enable
> them or program for them on a case-by-case basis.
So what's the alternative?  There are lots of things that people
sometimes want to do, but not always.  Having optional standards that
cover these areas is probably a good thing; at least developers can
pick up the standard and run with it (if they so choose) instead of
reinventing things from scratch.  The only thing I would ask is that
they be done in such a way that anyone that doesn't know about them
have things break when they encounter them.  For the most part things
like XInclude can be ignored if you don't care about them?

Peter Hunsberger

[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