W3C home > Mailing lists > Public > www-tag@w3.org > July 2002

RE: TB16 Re: Comments on arch doc draft

From: David Orchard <dorchard@bea.com>
Date: Wed, 3 Jul 2002 10:50:17 -0700
To: "'Joshua Allen'" <joshuaa@microsoft.com>, "'Paul Prescod'" <paul@prescod.net>
Cc: "'Jonathan Borden'" <jonathan@openhealth.org>, "'Patrick Stickler'" <patrick.stickler@nokia.com>, "'ext Tim Bray'" <tbray@textuality.com>, "'WWW TAG'" <www-tag@w3.org>
Message-ID: <02af01c222ba$1837d990$450ba8c0@beasys.com>
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.


> -----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.

Received on Wednesday, 3 July 2002 13:51:01 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:55:52 UTC