- From: Andy Seaborne <andy@apache.org>
- Date: Tue, 11 Jun 2013 11:12:09 +0100
- To: public-ldp-wg@w3.org
On 10/06/13 16:18, Arnaud Le Hors wrote: > Hi, > > We all agree that somehow a client needs to be able to figure out it is > dealing with an LDP server. The argument seems to be about how the > client makes that determination. From what I've seen we have two groups > of people. > > One group thinks that RDF provides all the client needs. The RDF typing > a la ldp:Container is the indicator. I believe this would mean that an > LDPR must also be typed with something LDP specific but I'll leave that > out for now. > > The other group argues that this is something the client should be able > to figure out just from the information contained in the HTTP layer. > Using a new mediatype would be one way to do that. It could be a new > mediatype entirely or one derived from existing mediatypes using the > profile mechanism. Would the following be an LDP server? A vanilla web server that provides GET, POST, PUT, DELETE, HEAD and eTags. In what way is not an LDP-R -only server? (no -C's) Andy
Received on Tuesday, 11 June 2013 10:12:40 UTC