Re: Migrating to @id and @type for legacy JSON specifications

On 07/16/2014 06:08 PM, Dave Longley 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.
I aliased it in the same way to render data more easily to RDFa using
http://handlebarsjs.com/

BTW I hope to at some point pull out JSON-LD -> RDFa templating from
http://viejs.org/

Received on Tuesday, 22 July 2014 11:36:19 UTC