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

 


Help: OASIS Mailing Lists Help | MarkMail Help

 


 

   Motivations for namespaces (sorry)

[ Lists Home | Date Index | Thread Index ]

Got some inspiration from the "Looking for an example of a name collission"
thread. It's funny that no one seem to be able to present a *good* working
example of how namespaces solves name conflicts. I'm not opposing
namespaces myself, but I still try to find the right place for them.

Namespaces doesn't seem to contribute much to data processing. I've found
them more useful when mixing tags from document schemas, where tags are
more likely to have the same generic names like <paragraph>, <list>,
<table> and so on. It's much harder to find examples when working with
data, because homonyms where both words are nouns (assuming element names
are always nouns) are rare. Title and table...what more examples are there?

So, assuming that you limit their use to solving name conflicts, is it
right to say that namespaces are more useful for document processing?

In actual use however, namespaces are not limited to solve name conflicts.
It seems they are used more as a way to tell which parts of the document
should be processed by which application. Still the specification seem to
be all about how to solve name conflicts. Perhaps it would have been better
if namespaces had been presented as a way to tie groups of element names to
a certain processing enviroment, instead of merely solving name conflicts?

Gustaf





 

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

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