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

Migrating to @id and @type for legacy JSON specifications

From: Andreas Kuckartz <a.kuckartz@ping.de>
Date: 11 Jul 2014 07:25:37 +0200
Message-ID: <53BF7551.4060808@ping.de>
To: public-linked-json@w3.org
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?

In particular: how could a migration path look like?

Would it be reasonable to use both, the new and the old property, during
a transition?

(The background of the question is a JSON format which has been existing
for several years, is moving to use JSON-LD and will be further
developed within a W3C WG.)

Received on Friday, 11 July 2014 05:26:04 UTC

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