W3C home > Mailing lists > Public > public-ldp@w3.org > February 2014

Re: lossless paging & volunteering for the army

From: <henry.story@bblfish.net>
Date: Mon, 24 Feb 2014 10:04:47 +0100
Cc: Sandro Hawke <sandro@w3.org>, Steve K Speicher <sspeiche@gmail.com>, public-ldp <public-ldp@w3.org>
Message-Id: <3FE1BD25-F44F-4A55-BAE6-6BEDED83EBAC@bblfish.net>
To: Mark Baker <distobj@acm.org>

On 24 Feb 2014, at 02:05, Mark Baker <distobj@acm.org> wrote:

> On Fri, Feb 21, 2014 at 11:33 AM, henry.story@bblfish.net
> <henry.story@bblfish.net> wrote:
>>> AIUI, the POST to a container modifies it's membership.
>> The POST to container creates a new information resource ( a RDF1.1 Source),
>> that is in ldp:contains relation to the LDPC. But it can also create other
>> relations, called the "Membership triples".
> Ah, there seems to be significant changes since I last looked. I'll
> just leave it at this; I consider the design overly complex, tightly
> coupled (and therefore unRESTful). But they're consistent with the
> general tightly-coupled nature of LDP, so on the upside, shouldn't
> make things any worse.

the membership triples have been there since the beginning, but they 
were so unintuitive to understand that they were easy to miss.

I think the design is very simple. You can post graphs to Containers.
When you do you 

 (1) create a new resource that is managed by the container.
 (2) for non Simple LDPCs, you create what I'd like to call a "binding relation"
     ( and which is currently called a "membership triple" )

When POSTing a normal form one can see something like the same thing happening:
  (1a) one creates a new resource
  (2a) one sometimes binds oneself by the act of POSTing - for example one binds oneself to buying a car

how one binds oneself in (2a) is normally specified by the text on the html page. In LDP this is
specified by the membershipResource, hasMemberRelation and insertedContentRelation .

I am not sure why one is limited to only one binding relation. I had proposed something like

<> a ldp:Container;
   ldp:binding [ membershipResource <#grp>;
                 hasMemberRelation foaf:member;
                 insertedContentRelation foaf:primaryTopic ];
   ldp:binding [ membershipResource ...
               ] .

But I can't think of a good example right now for the second binding.

> Mark.

Social Web Architect
Received on Monday, 24 February 2014 09:05:55 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:03:11 UTC