- From: Stian Soiland-Reyes <soiland-reyes@cs.manchester.ac.uk>
- Date: Tue, 22 Jul 2014 11:05:19 +0100
- To: Dave Longley <dlongley@digitalbazaar.com>
- Cc: Linked JSON <public-linked-json@w3.org>
One problem I found is that, if data is coming from RDF and going out as JSON-LD, it is hard to generate aliased terms for '@id' and '@type' with JSON-LD Framing - but perhaps someone know a nice trick with one of the libraries? (Search/replace does not count :) ) On 16 July 2014 17:08, Dave Longley <dlongley@digitalbazaar.com> wrote: > On 07/16/2014 10:24 AM, Markus Lanthaler wrote: >> On 11 Jul 2014 at 07:25, Andreas Kuckartz wrote: >>> Are there any best practices on how to deal with the use of different >>> property names than "@id" (such as "id" or "identifier") and "@type" >>> (such as "objectType") in addition to not changing them and using >>> @context for name mapping? >> >> Not really, no. > > My only comment is that we, at Digital Bazaar, prefer to alias @id and > @type to "id" and "type", respectively, because they can be more > easily/naturally accessed in JavaScript by using dot-notation. > > > -- > Dave Longley > CTO > Digital Bazaar, Inc. > -- Stian Soiland-Reyes, myGrid team School of Computer Science The University of Manchester http://soiland-reyes.com/stian/work/ http://orcid.org/0000-0001-9842-9718
Received on Tuesday, 22 July 2014 10:06:07 UTC