Re: opaque uris and self-describing resources

Sandro Hawke said:
> > so i assume to discover the non-http nature of the resource 
> > identified by u1, there must be some content within the returned 
> > resource that makes that statement. logically, i see three ways how the 
> > non-httpness of the identified resource could be established:
> > 
> > 1. string matching with a magic prefix
> > 
> > 2. the 303 returned when dereferencing the uri
> > 
> > 3. embedded metadata in the returned resource

> The TAG reached consensus on 15 Jun 2005 to use option 2.

How does this work when I'm not online? How does my software discover that
there's something special about this URL?

-- 
Clive D.W. Feather  | Work:  <clive@demon.net>   | Tel:    +44 20 8495 6138
Internet Expert     | Home:  <clive@davros.org>  | Fax:    +44 870 051 9937
Demon Internet      | WWW: http://www.davros.org | Mobile: +44 7973 377646
THUS plc            |                            |

Received on Friday, 18 January 2008 13:01:56 UTC