- From: Michael Smethurst <michael.smethurst@bbc.co.uk>
- Date: Wed, 23 Jul 2014 21:15:34 +0000
- To: Kingsley Idehen <kidehen@openlinksw.com>, "public-lod@w3.org" <public-lod@w3.org>
On 23/07/2014 21:49, "Kingsley Idehen" <kidehen@openlinksw.com> wrote: >On 7/23/14 3:40 PM, Michael Smethurst wrote: >> Hi Kingsley >> >> Very definitely starting to feel like deja vu... >> >> On 23/07/2014 20:18, "Kingsley Idehen"<kidehen@openlinksw.com> wrote: >> >>> >On 7/23/14 2:05 PM, Michael Smethurst wrote: >>>> >>For internal usage it's all probably fine. But I still think it's a >>>> >>pattern that shouldn't be generally encouraged. >>> > >>> >Its a "horses for courses" matter:-) >>> > >>> >If you choose to use hashless HTTP URIs in regards to entity >>>denotation, >>> >you have to make the extra investment required (via 303 heuristics) >>>for >>> >entity disambiguation [1]. >> My only point is: if you don't conflate "I can't send that" (303) with >> "what flavour would you like" (conneg) you don't have to invest in more >> servers >> >>> > >>> >Note, there are changes to HTTP that also reduce some of the confusion >>> >in this realm. For instance the use "Content-Location:" response >>>headers >>> >to aid disambiguation [2]. >> We do use content location for the (information) resource / >>representation >> split but that's REST not 303 semantics >> >> michael > >There is only one kind of relation semantics in play here, and its the >semantics of denotation and connotation [1][2]. Tho derrida didn't have to pay for servers :-/ > HTTP URIs denote things. Which can't be served (303) > >HTTP URLs denote documents comprised of connotation bearing content. Which can be served in assorted representations (conneg (+ content location)) Think the last time we had this conversation we broke the twitter scroll bar and agreed to disagree. Or at worst misunderstand :-) michael > >In regards, to the current BBC programmes URIs, if you incorporate RDFa, ><link/>, or "Link:" based relations, disambiguation without 303's or >content negotiation is possible. RDF user agents (for example) will be >able to make sense of the relations that that collective describe >documents about programmes and actual programmes. > >Links: > >[1] http://bit.ly/what-does-this-bbc-programmes-uri-denote -- Vapour >using RDF semantics discern what ><http://www.bbc.co.uk/programmes/b006mw1h> denotes and connotes > >[2] http://bit.ly/what-does-this-bbc-programmes-doc-url-denote -- ditto >but targeting <http://www.bbc.co.uk/programmes/b006mw1h.rdf> . > >-- >Regards, > >Kingsley Idehen >Founder & CEO >OpenLink Software >Company Web: http://www.openlinksw.com >Personal Weblog 1: http://kidehen.blogspot.com >Personal Weblog 2: http://www.openlinksw.com/blog/~kidehen >Twitter Profile: https://twitter.com/kidehen >Google+ Profile: https://plus.google.com/+KingsleyIdehen/about >LinkedIn Profile: http://www.linkedin.com/in/kidehen >Personal WebID: http://kingsley.idehen.net/dataspace/person/kidehen#this > >
Received on Wednesday, 23 July 2014 21:16:06 UTC