RE: TB16 Re: Comments on arch doc draft

Providing documentation is certainly my goal with the namespace issue.  

I'm not sure what a URL "for the namespace" identifies.  The question
becomes "what is a namespace, and thence what is the representation that is
retrieved from such an identifier".  

Again, providing documentation solves some very real problems without going
into that rathole.  Though I will point out there is vigorous debate on what
kinds of documentation can or should be present, such as XML Schemas, RDDL
documents, etc.

Cheers,
Dave

> -----Original Message-----
> From: www-tag-request@w3.org 
> [mailto:www-tag-request@w3.org]On Behalf Of
> Joshua Allen
> Sent: Wednesday, July 03, 2002 10:25 AM
> To: Paul Prescod
> Cc: Jonathan Borden; Patrick Stickler; ext Tim Bray; WWW TAG
> Subject: RE: TB16 Re: Comments on arch doc draft
> 
> 
> 
> > Your use of the word "overloading" "begs the question". 
> Using HTTP to
> > serve up documentation for a namespace is not overloading 
> anything. It
> 
> We agree 100%.  As long as you are clear that the URL is for the
> "documentation for a namespace" and not "the namespace", you are not
> overloading anything.
> 
> 
>