- From: John Arwe <johnarwe@us.ibm.com>
- Date: Fri, 31 May 2013 16:30:27 -0400
- To: "public-ldp-wg@w3.org" <public-ldp-wg@w3.org>
Received on Friday, 31 May 2013 20:31:02 UTC
> By-reference is totally different! That is exactly what I want to > not have confused with ldp:contains. My gut reaction is: if a client listing a container's membership is limited to finding resources newly created by/through HTTP interactions with the container, then this spec applies to zero of my use cases. It completely ceases to be an interesting spec in anything aside from a purely academic exercise, and I don't get paid for those (oh that it were so! :-) It cannot even handle a simple query result from a db query. Now maybe there is something in all changes you've proposed that I've missed, if so by all means point it out. I have no problem with the notion that a container exposes that smaller member list, optionally. But limiting it to that, not AT ALL interested/ing. Best Regards, John Voice US 845-435-9470 BluePages Tivoli OSLC Lead - Show me the Scenario
Received on Friday, 31 May 2013 20:31:02 UTC