W3C home > Mailing lists > Public > public-rdf-ruby@w3.org > March 2014

Re: extension for MIME type in rack-linkeddata

From: cr <_@whats-your.name>
Date: Fri, 14 Mar 2014 04:32:40 +0000
To: public-rdf-ruby@w3.org
Message-ID: <20140314043240.GA9054@p.hsd1.ma.comcast.net>
unsure how useful extension shortcuts are as data-browsers + conneg-aware tools eliminate the need to turn opaque URIs into something with embedded magic - probably not worth introducing any complexity/fragility to the middleware which currently does what it says on the tin. 

> Doing extension-based content negotiation in Rack::LinkedData::ContentNegotiation would be reasonable

ContentLocation could be a seperate middleware run first

should it encounter an extension, and a suitable Writer class exists, it could modify the Accept header, then the next middleware runs unchanged

GET /resource.n3 Accept: */* ->  GET /resource Accept: text/n3 

on the way out, it could append Content-Location to the specific variant's URI:

http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-26#section-3.1.4.2
Received on Friday, 14 March 2014 04:33:09 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:53:42 UTC