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

Re: LDP-Server - Issue-58

From: Arnaud Le Hors <lehors@us.ibm.com>
Date: Thu, 13 Jun 2013 08:00:56 -0700
To: Henry Story <henry.story@bblfish.net>
Cc: public-ldp-wg@w3.org
Message-ID: <OFC76ABCA4.3D1DBE65-ON88257B89.004E89F3-88257B89.00527B90@us.ibm.com>
Hey Henry,
Didn't you mean Issue-57 (How can a client determine that it is in 
communication with an LDP server) rather than issue-58 (membersInlined) 
here?

I must admit to be surprised by your question but I'm glad you asked 
because this is fundamental enough that if we don't all agree on this it's 
no wonder we have such a hard time talking through some of the issues.

>From my point of view, we're not just defining a vocabulary or ontology 
people can use with an existing triple store. We're also defining an 
interaction model in a the form of requirements that requires one to write 
code for in a server to be compliant.

LDP isn't only about RDF. It is also about REST, which clearly involves 
servers and clients. We're not only defining specific states but also how 
to transition from one state to another. How do you do that without 
talking about servers?

Regards.
--
Arnaud  Le Hors - Software Standards Architect - IBM Software Group


Henry Story <henry.story@bblfish.net> wrote on 06/12/2013 07:50:31 AM:

> From: Henry Story <henry.story@bblfish.net>
> To: public-ldp-wg@w3.org, 
> Date: 06/12/2013 07:57 AM
> Subject: LDP-Server - Issue-58
> 
> 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 Thursday, 13 June 2013 15:08:40 UTC

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