- From: Sandro Hawke <sandro@w3.org>
- Date: Wed, 19 Feb 2014 12:18:54 -0500
- To: Linked Data Platform WG <public-ldp-wg@w3.org>
Received on Wednesday, 19 February 2014 17:19:01 UTC
As I read the spec, it seems to me that normally a container contains exactly the same resources it has as members. The one circumstance I can see where this would not be true is when ldp:insertedContentRelation is used. I think this is reasonable, but I'm not at all sure I'm reading things right. Is there some other circumstance where it's possible to have a resource that is a member but is not contained, or is contained but is not a member? (I guess the current spec doesn't rule out the server making these sets different for its own reasons, but I think the clients can't make it happen, so I'm not too worried about it. It would probably be best if servers were forbidden from doing it, too.) BTW, I have an alternative proposal for ldp:insertedContentRelation (which I think has some problems), but I want to make sure I understand the context before I get into that. -- Sandro ||||| |
Received on Wednesday, 19 February 2014 17:19:01 UTC