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


Help: OASIS Mailing Lists Help | MarkMail Help



   RE: power uses of XML vs. simple uses of XML

[ Lists Home | Date Index | Thread Index ]
  • From: "Gavin Thomas Nicol" <gtn@ebt.com>
  • To: "XML-Dev Mailing list" <xml-dev@xml.org>
  • Date: Mon, 10 Jul 2000 10:33:38 -0700

> > I'm not sure about that. If you control the application in a given
> > domain, then you control the semantics of the encoded data, and in
> > such cases, even if you are embedding XHTML in your content, you
> > don't need namespaces to tell you that.
> I think maybe you missed my point about "a variety of ways". If you're
> only using XML in one domain and you don't need namespaces then there's
> no need to gratuitously implement them. But work in different
> areas/domains and with different technologies and eventually you're going
> to run into a need for namespaces, unless you expand your tagset/DTD
> beyond all sensibility.

Well, I haven't seen too many applications where XML is used "in a variety
of ways". That may be the future, but typically, vocabularies/tagsets
are controlled quite tightly.

Think of it this way: if your application knows nothing about XHTML, and
someone randomly embeds <xhtml:p> in the data, what will it do with it?
I think this is the normal case: at best the application can embed a
typically, it will ignore it, and in the worste case, it will cause the
app to fail.

This is xml-dev, the mailing list for XML developers.
To unsubscribe, mailto:majordomo@xml.org&BODY=unsubscribe%20xml-dev
List archives are available at http://xml.org/archives/xml-dev/


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

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