- From: John Arwe <johnarwe@us.ibm.com>
- Date: Fri, 31 May 2013 12:43:40 -0400
- To: Linked Data Platform (LDP) Working Group <public-ldp-wg@w3.org>
Received on Friday, 31 May 2013 16:44:10 UTC
> Here the members of the container are not listed. So one has to do an HTTP > GET on another resource to find the content of this one. And when one receives > the content from <http://example.org/app/BugTracker> one has to merge those > two graphs, and then apply the rule above to get the rdf:member relations > of the Container one is looking at. > Would it not be simpler ... Simplicity varies by assumption. If you look at Steve's thinking that shows his thinking on how we'd re-use existing vocabularies by additively exposing containers on their existing 'value sets', we exploited hash URIs to remove the extra GET and resulting merge. It is useful to look at this under more general assumptions too as the WG doing. The more eyes the better. Best Regards, John Voice US 845-435-9470 BluePages Tivoli OSLC Lead - Show me the Scenario
Received on Friday, 31 May 2013 16:44:10 UTC