- From: Roger Menday <roger.menday@uk.fujitsu.com>
- Date: Mon, 13 Jan 2014 16:03:24 +0000
- To: John Arwe <johnarwe@us.ibm.com>
- CC: "public-ldp-wg@w3.org" <public-ldp-wg@w3.org>
- Message-ID: <6AC9ACA7-8E9C-47C4-A070-A5D53FF19023@uk.fujitsu.com>
On 13 Jan 2014, at 15:40, John Arwe wrote: > > > For me, I am happy that the Documents are navigable from the > > response, and then "real world resources" are inside the membership data > > I'm not clear what that means. Short example? > > > > I am using "Documents" to mean Informational resources, and "real > > world resources" to mean Non-Informational resources. So by "real > > world resources inside the membership data", I mean a > > membershiptriple which is something like <networth1> <has_asset> > > <asset1>, and where <networth1> != <networth1Document>. > > "the response" meaning "the 201-created response"? Yes. (actually I wondered if the Location: header can point to a Non-informational resource - I guess so ... but anyway, I am referring to a pointer to a Document) > Alexandre et al. earlier felt that (since only the creator would have this information) that was insufficient. I.e. all clients should be able to find those documents. > > I also recall that argument. If the application is the 'filesystem' application, then the membershipPredicate might be ldpx:containsLikeAFileSystem. It is inserted by the server. It is understood that for this application this specific predicate links Documents to Documents. Roger > > Best Regards, John > > Voice US 845-435-9470 BluePages > Tivoli OSLC Lead - Show me the Scenario > > >
Attachments
- application/pkcs7-signature attachment: smime.p7s
Received on Monday, 13 January 2014 16:03:42 UTC