#248: Implement Content-Type negotiation for RDF output (aka Nicer URIs)
-------------------------+--------------------------------------------------
Reporter: earle | Owner: Nobody
Type: enhancement | Status: new
Priority: low | Milestone:
Component: openguides | Version: svn
Severity: normal | Keywords:
-------------------------+--------------------------------------------------
Context: [
http://norman.walsh.name/2005/06/19/httpRange-14 Norman Walsh
explains "httpRange-14"]
If a URI is requested of us, we should negotiate with the client
application using whatever Accept: header it offers. Example:
Request URI:
http://openguides.example.org/Somewhere
If the client requests Text/HTML (ie, a human using a browser), we should
303 (See Other) redirect to
http://openguides.example.org/page/Somewhere
If the client requests Application/RDF+XML, we should 303 (See Other)
redirect to
http://openguides.example.org/rdf/Somewhere
The RDF output's rdf:about value will need to have the URI inserted thus:
{{{
<rdf:Description
rdf:about="http://openguides.example.org/Somewhere">
<!-- everything else here -->
</rdf:Description>
}}}
--
Ticket URL: <http://dev.openguides.org/ticket/248>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project