> From: Richard Cyganiak > [ . . . ] > Let's say I have > > /resource (generic information resource with HTML and JSON > variants) > /resource.html (a HTML specific URI) > /resource.json (a JSON specific URI) > > Now let's say I request /resource.json with an Accept header of > "Accept: text/html". What should happen? > > One opinion is that the JSON should be served anyway, because the URI > identifies a specific variant. I think serving the JSON is the best option. Serving HTML from /resource.json would defeat the purpose of having a JSON-specific URI. It is quite likely that the user pasted the JSON URI into a browser to test it, and *wants* to see the JSON that is returned. Everyone knows how to paste a URI into a browser; few know how to configure their browsers to specify their desired MIME types. David Booth, Ph.D. HP Software +1 617 629 8881 office | dbooth@hp.com http://www.hp.com/go/software Statements made herein represent the views of the author and do not necessarily represent the official views of HP unless explicitly so stated.Received on Thursday, 31 July 2008 17:25:29 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:56:18 GMT