Re: comment on https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpr-5_4_13

hello steve.

On Jul 24, 2013, at 13:20, "Steve Speicher" <sspeiche@gmail.com<mailto:sspeiche@gmail.com>> wrote:
On Wed, Jul 24, 2013 at 5:14 AM, Wilde, Erik <Erik.Wilde@emc.com<mailto:Erik.Wilde@emc.com>> wrote:
it seems to me that
https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpr-5_4_13 should
start with "LDPC servers" and not with "LDPR servers".
personally, i think the whole notion of mentioning a "... server"
complicates the language unnecessarily: REST interactions are supported by
resources, and the fact that somewhere there's a server implementation
implementing that support really doesn't make any difference. but i guess
that it's too late to change this, and i also guess i am not the first one
making this suggestion... ;-)
I think it is too late for a change like this and not sure I even agree it should be done.  Someone needs to implement the end of the connection that receives a request, it is typical in spec to call these things servers (see RFC2616).  Then these servers need to comply to the request processing requirements.

i agree that it's too late. but look at examples like HTML or other media types: they don't talk about an "HTML server" or a "form processing server", they just talk about how to interact with a service that is exposing HTML as a representation. there may be examples where media type specs are using "server" language, but i would think (and hope) they are the minority.

thanks and cheers,

dret.