- From: Roger Menday <Roger.Menday@uk.fujitsu.com>
- Date: Fri, 28 Feb 2014 13:53:27 +0000
- To: "public-ldp-wg@w3.org Group" <public-ldp-wg@w3.org>
- Message-ID: <44F87334-2563-4598-931A-AD84F382851E@uk.fujitsu.com>
hello I did some experimenting with JSON-LD. With using the @reverse attribute, I can write LDP RDF in an appealing way which has a nice follow-your-nose style (and makes things pretty clear - IMO). { "@type": "o:Networth", "@id": "http://example/nw1", "asset" : [ "assets/a1", "assets/a2" ], "createAndLink": { "createsType" : "o:Asset", "linkedWith" : "asset", "@id" : "http://example/nw1/assets" } } It shows a Networth which is already linked to 2 Assets. It also advertises its capability to createAndLink new Asset resources. It says that newly created resources will be linked with the 'asset' property from the Networth. The createsType attribute is optional. It will be important to have a shape/constraints language guiding contents of the POSTed body. With a @context added, the JSON-LD above is same as valid LDP triples - see the JSON above in the JSON-LD playground at http://goo.gl/lXDIXx Extending to cover the case of the Networth directing the case of creating liabilities as well .. { "@type": "o:Networth", "@id": "http://example/nw1", "asset": ["assets/a1", "assets/a2"], "liability": ["liabilities/l5"], "createAndLink": [{ "createsType": "o:Asset", "linkedWith": "asset", "@id": "http://example/nw1/assets" },{ "linkedWith": "liability", "@id": "http://example/nw1/liabilities" }] } at http://goo.gl/OgzRcc Thought it might be of interest. Roger
Attachments
- application/pkcs7-signature attachment: smime.p7s
Received on Friday, 28 February 2014 13:54:00 UTC