- From: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
- Date: Mon, 10 Jun 2013 09:57:50 -0400
- To: Arnaud Le Hors <lehors@us.ibm.com>
- Cc: public-ldp-wg@w3.org
- Message-Id: <E86252CB-26C4-4FE5-A722-83D976D12CFF@openlinksw.com>
On Jun 6, 2013, at 04:11 PM, Arnaud Le Hors wrote: > There is no magic. In one way or another the client needs to figure out that it is dealing with an LDP server. This can be done at the HTTP level, at the RDF level, or possibly both. In other words... LDP requires a discovery mechanism. We've skirted this issue before, in questions about how to know what functionality a server has implemented, and in "implementation specific" functionality, about *how* it has been implemented. I don't recall any decisions that deliver such discovery mechanism (and think I remember some decisions *not* to do so), but the length of this thread seems a clear justification for such delivery. Ted -- 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
Attachments
- application/pkcs7-signature attachment: smime.p7s
Received on Monday, 10 June 2013 13:58:16 UTC