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

RE: What does "being a member" mean?

From: Steve Battle <steve.battle@sysemia.co.uk>
Date: Mon, 11 Nov 2013 17:36:15 -0000
Message-ID: <feff0eaced41838fcebae5c47ffcbbb5@mail.gmail.com>
To: Alexandre Bertails <bertails@w3.org>, Linked Data Platform WG <public-ldp-wg@w3.org>
I thought that "being an LDPR" meant "being a member of an LDPC".

Questions about Barbers and people who don't shave themselves
notwithstanding, there's at least one LDPC, and hence an LDPR by
implication, that is not a member of a LDPC.

Steve.

-----Original Message-----
From: Alexandre Bertails [mailto:bertails@w3.org]
Sent: 11 November 2013 16:49
To: Linked Data Platform WG
Subject: What does "being a member" mean?

Guys,

I think we have a problem with semantics :-)

Can somebody tell me what "being a member" means?

I thought that "being an LDPR" meant "being a member of an LDPC".

How is that different from "being managed by an LDPC"? And from
"ldp:created"?

Are the LDP interactions driven by "being a member" or by "being an
LDPC/LDPR"?

Is the notion of membership achieved through membershipXXX? If not, what's
the name for the feature captured by the membershipXXX relations?

If a POST succeed, does it mean that the new resource is created, or
managed, or a member of the LDPC? What about a binary resource then, as
it's currently not considered as an LDPC?

Sorry if those are obvious questions, but when I hear the conversations we
have in the meetings, it looks pretty confused :-/

Alexandre.
Received on Monday, 11 November 2013 17:36:44 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:17:46 UTC