practical question on naming graphs

Has the W3c or anyone put together a practical guide on how to name graphs yet?

What should the graph names of some well known ontologies be? Assuming to start off
with that we don't want to explore issues of temporal graph names or names of graphs
where the idenity of the requestor has been made available.


For foaf should it be:

 +  http://xmlns.com/foaf/0.1/ 
 +  http://xmlns.com/foaf/spec/ <- all foaf terms are redirected here with 303
 +  http://xmlns.com/foaf/0.1/knows -> redirects with 303 to spec

Should owl be:

 + http://www.w3.org/2002/07/owl
 + http://www.w3.org/2002/07/owl.rdf <- Content-Location but 200

Sould DC be:
  
  + http://purl.org/dc/elements/1.1/
  + http://dublincore.org/2010/10/11/dcelements.rdf <- 302 Moved Temporarily

One answer may simply be both! That is in a SPARQL query

SELECT ?clazz
FROM <http://xmlns.com/foaf/0.1/>
WHERE { ?class a owl:Class }

SELECT ?clazz
FROM <http://xmlns.com/foaf/spec/>
WHERE { ?class a owl:Class }

should both return the same answers. The server serving the answers should do a GET or look up the information in a database that keeps track of redirects.

Note: for foaf type naming systems I suppose that means that it will take quite a few partial GETs one for each relation or class type, to GET all the initial 303 redirects before one really captures all the named graphs foaf can have.

Sorry to bring this up. I am sure it's been debated for ever already. If it has please just point me to the answer. :-)

Thanks, 

Henry

Social Web Architect
http://bblfish.net/

Received on Sunday, 15 May 2011 18:54:05 UTC