- From: John Arwe <johnarwe@us.ibm.com>
- Date: Wed, 29 May 2013 09:08:06 -0400
- To: Linked Data Platform (LDP) Working Group <public-ldp-wg@w3.org>
Received on Wednesday, 29 May 2013 13:08:46 UTC
> yes. the language would need to be tuned. I was just trying to make "tuned"?? it completely changes the meaning for Pete's sake. The spec already requires all members to be listed - that is the intent and purpose of membership triples. The proposal as written says the container must list all members it created via rdfs:member ... which is (the created-only part at least) is not something the spec exactly covers today, so that's a reasonable point of discussion. Today's spec covers a superset (created by the container + those added via other means). The "tuned" version then nets out to "remove ldp:membershipPredicate and force the use of rdfs:member", correct? Just so we're clear about what we're talking about, rather than hiding it in a list of pro's. Best Regards, John Voice US 845-435-9470 BluePages Tivoli OSLC Lead - Show me the Scenario
Received on Wednesday, 29 May 2013 13:08:46 UTC