W3C home > Mailing lists > Public > public-swd-wg@w3.org > February 2007


From: Dan Brickley <danbri@danbri.org>
Date: Mon, 26 Feb 2007 18:46:38 +0000
Message-ID: <45E32B0E.3080901@danbri.org>
To: Daniel Rubin <rubin@med.stanford.edu>
Cc: public-swd-wg@w3.org

Daniel Rubin wrote:
> Hi everyone,
> I got a message below from a user who is trying to use SKOS in a 
> project, but is getting tangled in a problem with the FOAF URL to define 
> the NS which is preventing use of SKOS. Any suggestions?
> Daniel

Thanks. It certainly ought to be the case that FOAF and SKOS work well 
together. If someone is having trouble, I would like to find out why.

That said, I am having trouble understanding the detail of the message.

http://xmlns.com/foaf/0.1/20050603.rdf is an archive-only snapshot of 
FOAF's RDF description, never intended for use as a namespace. Well, 
people are free to do so, but it would be excessively cautious usage, I 

It soulds like they are using some particular toolset. Do you have any 
more details?

For example, http://www.dasbistro.com/~sam/raptor.lisp seems to be 
fixing on that specific URI.

suggests that URI is being used in Protege circles.

Could you ask if http://xmlns.com/foaf/0.1/index.rdf works OK for them?

Perhaps the problem is with our content negotiation setup. That could 
well be the case. If you can find out what tool is being used, I could 
run some tests...



> _____________________________
> The old FOAF  & SKOS (which creates a FOAF namespace (NS)) URLs are no 
> longer any good.
> SKOS has a NEW URL which does appear to work:
> http://www.w3.org/2004/02/skos/core.rdf
> However, since SKOS defines a FOAF namespace, you must also have a 
> working FOAF URL to use SKOS.  The W3C FOAF page (which has been updated 
> a bit) does include a FOAF RDF file link:
> http://xmlns.com/foaf/0.1/20050603.rdf
> When you click on this, you get nothing, but when you use 'wget' on the 
> command line you get a nice FOAF RDF file.
> Unfortunately, the SKOS file uses the old FOAF URL - 
> http://xmlns.com/foaf/0.1/ - to define the FOAF NS.  This means unless 
> you download a copy of the SKOS file and hand edit the FOAF NS 
> description to a working FOAF URL, you can't open SKOS or any other RDF 
> or OWL file that either defines a SKOS NS or imports SKOS.
Received on Monday, 26 February 2007 18:47:17 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:07:49 UTC