Hi All,

I've noticed that when you request data from dbpedia, content
negotiation is implemented (afaik) but the Content-Location header isn't
implemented.

surely if http://dbpedia.org/data/London defaults to application/rdf+xml
and the same representation is available at
http://dbpedia.org/data/London.rdf then that should be the content location?

Also, how does this affect cacheing and memento; are extra versions of
each resource being stored for no reason?

and finally - should last-modified and ETags be on there to enable
cache's down the line (I'm aware there are multiple representations, but
a weak ETag could be used).

Many Regards,

Nathan

Reply via email to