Re: ungetable http URIs

Seaborne, Andy wrote:

>Mark wrote:
>  
>
>>In the Artstor dataset at least we are also currently using URLs for a
>>number of things:
>>
>>1. vocabularies
>>2. controlled terms
>>3. metadata instances
>>
>>    
>>
>I would suggest putting something appropriate at the URLs for each of these:
>
>1/ The vocabulary
>2/ A defintion of the controlled term (it's a web resource so the return
>from GET is a representation of that resource - could be RDF - just
>rdfs:label would help).
>
>    <> rdf:label "Portrait" .
>
>(<> is a "this" resource reference in N3)
>
>  
>
If we know where the Joseki server is located that will be hosting this 
service, then the URL's provided could be self-referential -- they could 
be the same fetch request as would be used to retrieve the actual node 
in question.

-- 
========================================================
   Kevin Smathers                kevin.smathers@hp.com    
   Hewlett-Packard               kevin@ank.com            
   Palo Alto Research Lab                                 
   1501 Page Mill Rd.            650-857-4477 work        
   M/S 1135                      650-852-8186 fax         
   Palo Alto, CA 94304           510-247-1031 home        
========================================================
use "Standard::Disclaimer";
carp("This message was printed on 100% recycled bits.");