- From: Wilde, Erik <Erik.Wilde@emc.com>
- Date: Fri, 1 Feb 2013 05:08:42 -0500
- To: Arnaud Le Hors <lehors@us.ibm.com>, "public-ldp-wg@w3.org" <public-ldp-wg@w3.org>
hello all. On 2013-01-31 20:54 , "Arnaud Le Hors" <lehors@us.ibm.com> wrote: >One argument against introducing ldp:contains or any such new predicate >is that we want to encourage reuse and this doesn't. >I'm not really sure this is independent of ISSUE-37. As the draft stands >it only supports composition and if that's all we end up with there won't >be any confusion about what rdfs:member is about, will there? to avoid confusion, what's the problem of using rdfs:member to always represent membership, ldp:content to always represent member content, and then to distinguish between containment and aggregation simply by letting the user decide whether they embed the content or not when creating new members? as i've pointed out before, this would also simply deletion semantics and generally make the model simpler, and more consistent. cheers, dret.
Received on Friday, 1 February 2013 10:09:39 UTC