OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   Extensibility of a data language

[ Lists Home | Date Index | Thread Index ]
  • To: XML Developers List <xml-dev@lists.xml.org>
  • Subject: Extensibility of a data language
  • From: bryan rasmussen <rasmussen.bryan@gmail.com>
  • Date: Tue, 7 Feb 2006 11:44:51 +0100
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=oTLrRvD04mAMkjxwqNrbfTAKD9avCi8UWX1GgYSCRw8cJK7ofRQkfHT5BrjiPDr7Q9j2Z0P7+a3DPRdj3GKjEeQ8Odcy3rDdALXkDmn67g+9OW3BZGPG79cOqaJHKDmAwwhOjnowF5Ho79+WEKMve1L8M0NruuTHwubMD1v0OEM=

It seems that most successful examples of extension exist at the level
of protocol, display languages, and so forth, whereas I can't think of
any particularly successful data language where the language had the
possibility of extension of the language by users built in.

It often seems that Data heads feel that the kind of loose
extensibility that namespaces can be set to allow will create anarchy.
Any arguments against?

Bryan Rasmussen


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

Copyright 2001 XML.org. This site is hosted by OASIS