W3C home > Mailing lists > Public > public-linked-json@w3.org > July 2014

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

From: Dave Longley <dlongley@digitalbazaar.com>
Date: Wed, 16 Jul 2014 12:08:47 -0400
Message-ID: <53C6A38F.80007@digitalbazaar.com>
To: public-linked-json@w3.org
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.
Received on Wednesday, 16 July 2014 16:09:10 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:18:42 UTC