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

RE: XML, hypertext

• To: <xml-dev@l...>
• Subject: RE: XML, hypertext
• From: "Jelks Cabaniss" <jelks@j...>
• Date: Sun, 18 Aug 2002 17:12:40 -0400
• Importance: Normal
• In-reply-to: <2C61CCE8A870D211A523080009B94E430752B80F@HQ5>

Bullard, Claude L (Len) wrote:
 
...
> http://www.oasis-open.org/cover/newcombGroves19990908.html

Particularly relevant in the above (one might profitably substitute "the
DOM" with some other, uh, "technologies"):

<snip>
    I hope we're not facing a future in which the semantics of
    certain chosen vocabularies will be directly supported by
    future versions of the DOM.  Such support should "plug into"
    (and be unpluggable from) the DOM.  No vocabulary-specific
    support should become a required feature of all DOM
    implementations.  For example, making XLink a vocabulary is
    fine; making the DOM able to support XLink but no other
    linking vocabularies would be the start of a long nightmare
    with a bad ending.  To do that would significantly reduce
    the freedom of industries to design their own information
    architectures, and to evolve them according to their own
    perceived needs.  It would also destroy the DOM, which must
    stay simple in order to survive.  No API can do everything
    for everybody, and once you start putting support for DTD-
    specific (or namespace-specific) semantics into the DOM,
    where do you stop?  I've watched a couple of systems bloat
    uncontrollably and meet their demise in similar ways, and
    the stage is perfectly set for the same thing to happen to
    the DOM.
</snip>

Pretty prescient in 1999.  


/Jelks

• References:
  • RE: XML, hypertext
    • From: "Bullard, Claude L (Len)" <clbullar@i...>

• Prev by Date: RE: XHTML 2.0 and the death of XLink and XPointer?
• Next by Date: RE: linking, 80/20
• Previous by thread: RE: XML, hypertext
• Next by thread: RE: XML, hypertext
• Index(es):
  • Date
  • Thread