[foaf-dev] foaf resources do not return correct representations

Dan Brickley danbri at danbri.org
Tue May 22 22:40:20 BST 2007

Richard Cyganiak wrote:
> On 7 May 2007, at 02:28, Henry Story wrote:
>> curl -I -H "Accept: application/rdf+xml" http://xmlns.com/foaf/0.1/knows
>> Does not return the rdf representation, or a pointer to the rdf 
>> representation. It returns a pointer to an html web page
> And this web page also lacks the <link rel="alternate"> header that 
> might still allow an agent to find the RDF version.
>> Please fix!
> +1
> I'd be happy to contribute some time if there's anything I could do to 
> make these fixes happen.

I'm trying to figure out what's up with the xmlns.com config, per 

There is an .htaccess in effect,

...in that it redirects http://xmlns.com/foaf/0.1/name to 
http://xmlns.com/foaf/0.1/ (and, sanity check, when the .htaccess is 
moved, it doesn't :)

curl -I -H "Accept: application/rdf+xml" http://xmlns.com/foaf/0.1/

...doesn't see the RDF flavour.

Here is the voodoo we used to use successfully, pre-Dreamhost hosting:

	RewriteCond %{HTTP_ACCEPT} application/rdf\+xml
	RewriteRule ^foaf/0.1/ /foaf/0.1/index.rdf [R=303]

I've tried adding "RewriteEngine on" before that too.
And some other voodoo. And googling around at this stuff plus 
"dreamhost". No joy yet. Dreamhost claim that mod rewrite is functional 
on their servers.

Current version I'm trying is:

	AddType  application/rdf+xml rdf
	RewriteEngine on
	RewriteBase /
	RewriteCond %{HTTP_ACCEPT} application/rdf\+xml
	RewriteRule ^foaf/0.1/ /foaf/0.1/index.rdf [R=303]

Suggestions/help welcomed!

I'll add the rel="alternate" too.

Regarding the "0.1" in the URL, I also suggest moving the HTML docs to 
live in /foaf/spec and redirecting there, leaving the 0.1/ only in the 
machine-readable URIs. Any objections to that?

First obstacle there is building a new Redland on the Dreamhost box, 
needed for specgen.py. Will be bugging Dave about that next...



More information about the foaf-dev mailing list