Another look at namespaces

Ann Navarro ann at
Thu Sep 16 18:47:44 BST 1999

At 12:42 PM 9/16/99 -0400, Simon St.Laurent wrote:
>At 12:27 PM 9/16/99 -0400, Ann Navarro wrote:

>>Nothing in the current proposals being debated sets functionality. Instead,
>>it provides granularity in namespaces making a nod toward the possibility
>>of additional functionality. 
>>It may turn out to be unnecessary, but as I've said before, I believe it
>>easier to remove that granularity later (or simply ignore it), than it will
>>be to put it back in at some later date. 
>I still find this argument unconvincing.  One schema per namespace appears
>to be what you're arguing for here


I'm arguing that each flavor of XHTML is sufficiently different (idiom,
dialect, what have you) that it deserves a different namespace. 

Information about those namespaces may, if the W3C chooses to follow this
path, be obtained from a schema, DTD, or other data source at the end of
that URI. 

>It may be that the tools we have are inadequate. I don't think, however,
>that we've yet reached the conclusion that three namespaces will let us do
>better with either the tools we have today or the tools we may have tomorrow.

Nor have we reached the conclusion that they won't. I'd rather provide the
ability now than have to try and add it back in. 

It should also be noted that these is not the *only* use case being
considered (see Steven's summary). 


Author of Effective Web Design: Master the Essentials
Coming in September --- Mastering XML

Founder, WebGeek Communications  
Vice President-Finance, HTML Writers Guild
Director, HWG Online Education   

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at
Archived as: and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:majordomo at the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo at the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at

More information about the Xml-dev mailing list