> > publishing it in a web style > > As soon as I can hijack a server that is accessible from the outside and > has enough free disk space :-) Ah, excellent. > We have a simple web application that allows resources to be retrieved > through addresses such as: > > /uniprot/P12345 <- text/html > /uniprot/P12345.rdf <- application/rdf+xml > /uniprot/?query=antigen > /uniprot/?query=antigen&format=rdf > /taxonomy/9606 > /taxonomy/9606.rdf > ... > > > > [1] http://www.pir.uniprot.org/start/faq.shtml#uniplink > > The original proposal was: > > http://uniprot.org/uniprot/P12345 > http://uniprot.org/uniref/UniRef_Q12345 > ... > > Unfortunately, after all cooks where done, resources from all namespaces > ended up in the same path: > > http://uniprot.org/entry/P12345 > http://uniprot.org/entry/UniRef_Q12345 > ... So where are you thinking you'll serve the RDF? http://uniprot.org/entry/P12345.rdf would be obvious, but including the ".rdf" in the URI for the protien itself doesn't seem right. Maybe http://uniprot.org/data/P12345 ? or http://uniprot.org/entry/P12345 but use some technique for serving HTML and RDF at the same location (such as HTTP Content Negotiation, or an HTML meta/link/profile technique)? -- sandroReceived on Wednesday, 21 July 2004 13:15:17 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:52:08 GMT