W3C home > Mailing lists > Public > public-ldp-wg@w3.org > June 2013

LDP-Server - Issue-58

From: Henry Story <henry.story@bblfish.net>
Date: Wed, 12 Jun 2013 16:50:31 +0200
Message-Id: <43AEA952-702A-45DC-A9CE-4A34670A2733@bblfish.net>
To: public-ldp-wg@w3.org
The spec says in Section-3

[[
A conforming LDP Server is an application program that processes HTTP requests and generates HTTP responses that conform to the rules defined in sections onLDPRs and LDPCs
]]

Does this notion really make sense? It seems to lead straight to question of ISSUE-58

 "How can a client determine that it is in communication with an LDP server?"

Do we speak of an Form Server, because a Web Server can deal with HTML forms?
Or do we speak of a jpg server because a web server can deal with jpg images?
Or do we speak of a shopping cart server because a server contains a shopping cart functionality?

One can see how speaking in those ways would soon raise similar questions:

  - How can a client determine that it is in communication with a form server?
  - How can a client determine that it is in communication with a jpg server?
  - How can a client determine that it is in communication with a shopping cart server?
 
Clearly all those questions are silly. There is no such thing as a shopping cart server.
There are just resources that can receive shopping cart type requests: such as adding
items, etc... ( not so unlike an LDPC ). A request with a jpg mime type on a particular
image will return that image. etc...

The same is true then with an LDP Server.  It is not clear that one needs
anything more than the notion of an LDPC and LDPR resource. These would be
such that they behave the way the spec defines them to behave. They are of
course HTTP resources.

An LDP Server is then just a loose hand way of saying

[[
A conforming LDP Server is an HTTP Server that contains one or more LDPC resources that conform
to the rules defined in this spec.
]]

Social Web Architect
http://bblfish.net/
Received on Wednesday, 12 June 2013 14:51:04 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:11:51 UTC