RE: referendum on httpRange-14

> -----Original Message-----
> From: www-tag-request@w3.org 
> [mailto:www-tag-request@w3.org]On Behalf Of
> ext Sandro Hawke
> Sent: 18 October, 2004 22:02
> To: Norman Walsh
> Cc: www-tag@w3.org
> Subject: Re: referendum on httpRange-14 
> 
> 
> 
> 
> > | Seriously, I'm writing this while procrastinating about 
> answering this
> > | for myself in Ontaria.  I need a tab on which to display 
> information
> > | about any resource for which dereference worked, and I'm 
> not sure what
> > | users are going to want to see on that tab.  I'm also not 
> sure what to
> > | call it (ie what the class name is), but I'm leaning 
> towards "Document".
> > 
> > How about 'Response Headers' :-)
> 
> Yeah, but that's not the class name.  I need to name some class which
> is a subclass of Resource for which dereference makes sense.  I could
> call it Dereferenceable, but I want this to be comfortable to Joe
> Random User.  Google mostly avoids any term, but sometimes calls them
> Documents; Yahoo calls them Sites.

Well, I've proposed "Web Resource", which is the subclass of Resources
which have web accessible representations.

So, if for a given URI you GET a "200 OK" response, it is a "web resource".

But what real utility does that provide the user? Why the need for any
name at all? Or why the need for a subclass of Resource?

Patrick

Received on Tuesday, 19 October 2004 07:56:16 UTC