Ticket #248 (new enhancement)

Opened 3 months ago

Last modified 3 months ago

Implement Content-Type negotiation for RDF output (aka Nicer URIs)

Reported by: earle Assigned to: Nobody
Priority: low Milestone:
Component: openguides Version: svn
Severity: normal Keywords:
Cc:

Description

Context: 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>

Change History

06/11/08 02:57:06 changed by earle

The final code snippet in the ticket is incorrect. It should read: 

<rdf:Description rdf:about="http://openguides.example.org/rdf/Somewhere">
  <!-- everything else here -->
</rdf:Description>

I also forgot to mention that this will also finally dispense with the awkward "#obj" notation that I was forced to invent for the original design of the RDF output.

The second half of the RDF output for a typical page, which currently looks like: 

<geo:SpatialThing rdf:ID="obj">

will become: 

<geo:SpatialThing rdf:about="http://openguides.example.org/Somewhere">