- From: Benjamin Nowack <bnowack@appmosphere.com>
- Date: Tue, 22 Mar 2005 09:29:43 +0100
- To: "Miles, AJ \(Alistair\)" <A.J.Miles@rl.ac.uk>
- Cc: public-esw-thes@w3.org
On 21.03.2005 19:17:38, Miles, AJ \(Alistair\) wrote: >Hi all, > > >I have a suggestion: we make the resource http://www.w3.org/2004/02/skos/core >content negotiable. If a client asks for 'text/html' then the resource serves >up some html that carries the title 'SKOS Core Vocabulary Namespace Document'. >If the client asks for 'application/rdf+xml' then they get what they currently >get, which some RDF/XML. I'm not sure. I'd try to avoid (directly) serving two different representations at a single URI. AFAIK this type of URI overloading is still considered bad practice (VM TF again?). maybe using a linked stylesheet to provide an htmly view in a browser could be an option to only have a single document at that URI. Or redirecting to another URI, based on the accept headers sent, but I'm not sure if there's a recommendation how to implement the latter option already.. regards, benjamin -- Benjamin Nowack Kruppstr. 100 45145 Essen, Germany http://www.bnode.org/ > >Cheers, > >Al. > >[3] http://www.w3.org/2004/02/skos/core/spec/2005-03-11 > > >--- >Alistair Miles >Research Associate >CCLRC - Rutherford Appleton Laboratory >Building R1 Room 1.60 >Fermi Avenue >Chilton >Didcot >Oxfordshire OX11 0QX >United Kingdom >Email: a.j.miles@rl.ac.uk >Tel: +44 (0)1235 445440
Received on Tuesday, 22 March 2005 08:29:42 UTC