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

[Best Practices] Context document - modifying and versioning

From: ☮ elf Pavlik ☮ <perpetual-tripper@wwelves.org>
Date: Sun, 08 Jun 2014 12:15:39 +0200
Message-ID: <539437CB.7020000@wwelves.org>
To: Linked JSON <public-linked-json@w3.org>
Howdy,

I see a pattern with versioned contexts like many Web Payments specs:
https://web-payments.org/specs/source/identity-credentials/#a-typical-identity

And also context without version, like Hydra Core
http://hydra-cg.com/spec/latest/core/#documenting-a-web-api

AFAIK one for schema.org will also have no version information.

I see it somehow relevant to this issue: "JSON-LD Context security
considerations" https://github.com/web-payments/web-payments.org/issues/21

Since changing content of the context document can completely change
meaning of data, maybe creating some kind of JSON-LD Context Best
Practices document could help many people with playing safe when
altering contexts used in data already out(in) there?

o/
Received on Sunday, 8 June 2014 10:18:00 UTC

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