- From: Kingsley Idehen <kidehen@openlinksw.com>
- Date: Mon, 10 Jun 2013 10:09:36 -0400
- To: public-ldp-wg@w3.org
- Message-ID: <51B5DE20.4050600@openlinksw.com>
On 6/10/13 9:54 AM, Ted Thibodeau Jr wrote: > On Jun 4, 2013, at 05:26 PM, Kingsley Idehen wrote: > >> On 6/4/13 4:36 PM, Henry Story wrote: >>>> on a related note, just today the W3C published a FPWD of a "URLs in Data Primer http://www.w3.org/TR/2013/WD-urls-in-data-20130604/ ; essentially what it says is that instead of using the funky httpRange-14 dance, what you should do instead is at the model level clearly distinguish and expose different URIs to documents about things and things themselves, if it matters to what you're doing. >>> yes that's a nice find Erik. Thanks. >>> Except that they should really have big warning signs on 303s and tell people that it requires one more redirect and is so not the favored method. The #URL method is the efficient way to do things, and the one that is certainly correct. 303s are there to help cover erros. I'll leave them a note on that. >>> >>> Perhaps that will help Alexandre Bertails. >>> >> Note that the 303 heuristic is now just an option. You can now do a 200 OK on a hashless URI and then use "Content-Location: " header to aid disambiguation i.e., the Content-Location: header is the final arbiter for hashless URI disambiguation. Thus, <http://dbpedia.org/resource/Linked_data> can now result in a 200 OK with <http://dbpedia.org/page/Linked_data> returned in the "Content-Type" response header. > I think that last should be `returned in the "Content-Location" response header.`\ Correct. Too much talk about media types leads me to typing Content-Type: when I mean Content-Location: Thanks for spotting that critical typo! Kingsley > > Regards, > > Ted > > >> I also posted this to the LOD forum encouraging adoption of this new heuristic as yet another option for URI disambiguation. Naturally, we will incorporate this into DBpedia once we are clear it won't trip up existing LOD consumers and we arrive at consensus with other project members. >> >> Links: >> >> 1. http://lists.w3.org/Archives/Public/public-lod/2013Mar/0133.html -- thread about recent HTTP changes addressing the 303 concern >> >> -- >> >> Regards, >> >> Kingsley Idehen >> Founder & CEO >> OpenLink Software >> Company Web: http://www.openlinksw.com >> Personal Weblog: http://www.openlinksw.com/blog/~kidehen >> Twitter/Identi.ca handle: @kidehen >> Google+ Profile: https://plus.google.com/112399767740508618350/about >> LinkedIn Profile: http://www.linkedin.com/in/kidehen >> >> >> >> >> > -- > A: Yes. http://www.guckes.net/faq/attribution.html > | Q: Are you sure? > | | A: Because it reverses the logical flow of conversation. > | | | Q: Why is top posting frowned upon? > > Ted Thibodeau, Jr. // voice +1-781-273-0900 x32 > Senior Support & Evangelism // mailto:tthibodeau@openlinksw.com > // http://twitter.com/TallTed > OpenLink Software, Inc. // http://www.openlinksw.com/ > 10 Burlington Mall Road, Suite 265, Burlington MA 01803 > Weblog -- http://www.openlinksw.com/blogs/ > LinkedIn -- http://www.linkedin.com/company/openlink-software/ > Twitter -- http://twitter.com/OpenLink > Google+ -- http://plus.google.com/100570109519069333827/ > Facebook -- http://www.facebook.com/OpenLinkSoftware > Universal Data Access, Integration, and Management Technology Providers > > > > > > > -- Regards, Kingsley Idehen Founder & CEO OpenLink Software Company Web: http://www.openlinksw.com Personal Weblog: http://www.openlinksw.com/blog/~kidehen Twitter/Identi.ca handle: @kidehen Google+ Profile: https://plus.google.com/112399767740508618350/about LinkedIn Profile: http://www.linkedin.com/in/kidehen
Attachments
- application/pkcs7-signature attachment: S/MIME Cryptographic Signature
Received on Monday, 10 June 2013 14:10:00 UTC