RE: Are MGET descriptions workable/necessary?

Joshua Allen writes:
 > 
 > > > author to maintain a web service describing all his/her terms *at
 > the
 > > > url it was defined at*.
 > 
 > 
 > > of the resource denoted by that URI, you ask an HTTP server hosted at
 > > example.com (which is presumed to exist) and usually, you'd GET back a
 > > representation.
 > 
 > Am I missing something?  I thought the idea of MGET would easily support
 > something like:
 > 
 > #telnet rdf.mymetadatarepository.com 80
 > Connected to .....
 > MGET http://www.ibm.com
 > ... returns all metadata about ibm.com known to server
 > mymetadatarepository ...
 > 

Doh! - I've just reread http://sw.nokia.com/uriqa/URIQA.html and
you're right.
I was assuming it would work like GET - i.e.:

#telnet www.ibm.com 80
 > Connected to .....
 > MGET / HTTP/1.1
 > ... returns all metadata about http://www.ibm.com/


#telnet www.ibm.com 80
 > Connected to .....
 > MGET /terms/foobah HTTP/1.1
 > ... returns all metadata about http://www.ibm.com/foobah


So I was missing something. That would imply that you can ask other
rdf repositories about terms that aren't in their dns. 

Apologies Patrick - I did have the wrong end of the stick after all.

Cheers,

Phil