tags:

views:

23

answers:

2

Is there a way of - inside an RDF document - specifying a physical URL for URI references? That is, something that does the same job as xsi:schemaLocation in XML schema documents?

I understand that the "correct" way to do it is with the URI doing a 303 redirect with content negotiation, but if setting up redirects is a hassle, can my RDF document itself explain that

http://foo.bar.com/voc/SpecialSettings

is to be fetched from the physical location

http://server1.bar.com/prod/app3/SpecialSettings.owl

?


Update: we resolved this by explaining to the server that it needed to send redirects. See http://biodiversity.org.au/voc/ibis/IBIS

+3  A: 

This is not possible with standard RDF. AFAIR, this additional complexity was deliberately avoided.

You could cheat and say in an ontology that http://foo.bar.com/voc/SpecialSettings is owl:sameAs http://server1.bar.com/prod/app3/SpecialSettings.owl. Then a program that understands owl:sameAs might try both URLs and combine the information it gets from both, which in that case would be nothing from the first one and everything from the second one. But not many programs and libraries will do this automatically. It's also fishy from an ontological perspective. You, as the data provider, should provide one canonical URL for your resources.

For this kind of question, my first reference is How to Publish Linked Data on the Web.

Thomas Kappler
Drat. Thanks anyway. Looks like I'll be asking the DMZ team to please put in some 303s for my vocabulary files.
paulmurray
A: 

I'm not sure if it's relevant, but ontologies are served up as vanilla (or physical) web documents. Take OWL itself for example:

@rorty:~/tmp$ curl -I http://www.w3.org/2002/07/owl
HTTP/1.1 200 OK
Date: Fri, 15 Oct 2010 14:34:23 GMT
Server: Apache/2
Content-Location: owl.rdf
Vary: negotiate,accept
TCN: choice
Last-Modified: Sun, 15 Nov 2009 10:54:12 GMT
ETag: "7c75-47866b6941d00;47803990f62c0"
Accept-Ranges: bytes
Cache-Control: max-age=21600
Expires: Fri, 15 Oct 2010 20:34:23 GMT
P3P: policyref="http://www.w3.org/2001/05/P3P/p3p.xml"
Content-Type: application/rdf+xml; qs=0.9
Content-Length: 31861
Connection: Keep-Alive
Ed Summers