- From: Kingsley Idehen <kidehen@openlinksw.com>
- Date: Tue, 22 Jan 2013 11:33:06 -0500
- To: public-ldp-wg@w3.org
- Message-ID: <50FEBF42.5060006@openlinksw.com>
On 1/22/13 11:23 AM, Wilde, Erik wrote: > On 2013-01-22 15:25 , "Roger Menday" <roger.menday@uk.fujitsu.com> wrote: >>>> Erik's solution will work. >>>> You either POST to a collection which will create the LDPR >>> You POST a Graph or a binary to a collection, right? Those are pretty >>> much complementary >>> classes of things. >>> >>> >>>> or you do a POST which will create a link to an already existing LDPR. >>>> >>> You would POST what to the collection? >> maybe : >> <> ldp:link <http://www.someremoteserver.com/Tracker/1/Bug/1> . >> Roger > a little more than that, because we need whatever LDP says LDP clients > MUST supply as metadata for entries, maybe a title and a creation date or > whatever. and rather than using a nondescript link, i'd prefer ldp:content > or something along these lines. > > cheers, > > dret. > > > > Is ldp:content defined anywhere? If not, then its as meaningful or meaningless as ldp:link . BTW -- I see nothing at: http://www.w3.org/ns/ldp# . -- Regards, Kingsley Idehen Founder & CEO OpenLink Software Company Web: http://www.openlinksw.com Personal Weblog: http://www.openlinksw.com/blog/~kidehen Twitter/Identi.ca handle: @kidehen Google+ Profile: https://plus.google.com/112399767740508618350/about LinkedIn Profile: http://www.linkedin.com/in/kidehen
Attachments
- application/pkcs7-signature attachment: S/MIME Cryptographic Signature
Received on Tuesday, 22 January 2013 16:33:33 UTC