[foaf-dev] Strange HTTP behaviour for some FOAF classes

[Richard Cyganiak]

foaf:Agent
foaf:Group
foaf:PersonalProfileDocument

These three classes act a bit weird when their URIs are requested via  
HTTP GET.

Request with text/html Accept header
=> 303 to http://xmlns.com/foaf/spec/
  (this seems fine)

Request without Accept header
=> 404
  (this is strange)

Request with application/rdf+xml Accept header
=> 200 with contents of index.rdf
  (this is strange)

In fact, this is the same behaviour as for non-existing terms such as  
foaf:asdfasdf. Perhaps the classes have been forgotten from some  
administrative script?

I'm also not sure that the current behaviour for non-existing  
properties makes any sense, with 303, 404 or 200 depending on the  
content type. It should either always be 404, or always 303 to the spec.

Best,
Richard