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

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

From: Markus Lanthaler <markus.lanthaler@gmx.net>
Date: Wed, 16 Jul 2014 16:24:08 +0200
To: <public-linked-json@w3.org>
Message-ID: <02c401cfa101$9c116a60$d4343f20$@gmx.net>
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.

> 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?

If it helps to keep old clients working, yes. If the values are exactly the same though and the semantics match, it doesn't make a lot of sense to include both.


> (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.)

Which format is it?


--
Markus Lanthaler
@markuslanthaler
Received on Wednesday, 16 July 2014 14:24:37 UTC

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