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

Re: What does "being a member" mean?

From: Arnaud Le Hors <lehors@us.ibm.com>
Date: Tue, 12 Nov 2013 07:01:05 -0800
To: Henry Story <henry.story@bblfish.net>
Cc: Linked Data Platform WG <public-ldp-wg@w3.org>
Message-ID: <OFF0BDF6D8.353C5C83-ON88257C21.00519D2D-88257C21.00527F93@us.ibm.com>
Henry Story <henry.story@bblfish.net> wrote on 11/12/2013 02:04:18 AM:

> On 11 Nov 2013, at 23:20, Arnaud Le Hors <lehors@us.ibm.com> wrote:
> 
> > We've heard, repeatedly, that the notion of membership is not 
> bound to whether a resource is created by POSTing to an LDPC. Steve 
> Speicher said it again today on the call: 
> > "there are a number of existing data structures that, when I bring
> them online [in LDP], I didn't create anything " 
> > 
> > John added: 
> > "I thought that "membership triples" today were there to tell 
> clients how to enumerate members of the container; does not matter 
> how they came to be members (post, put,... , out of band)." 
> > 
> > I don't think ignoring that is helpful. 
> 
> I am not at all ignoring that. My definition contains 
> an "or": 
>  - either an LDPR is created through a POST
>  - or if an LDPR is DELETEd the LDPC needs to remove the membership 
triples
> 
> (see http://www.w3.org/2012/ldp/wiki/Member )

My bad. I had read it as an and somehow.
--
Arnaud  Le Hors - Software Standards Architect - IBM Software Group
Received on Tuesday, 12 November 2013 15:24:46 UTC

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