W3C home > Mailing lists > Public > public-linked-json@w3.org > February 2018

Re: release process for 1.1 libraries?

From: Dan Brickley <danbri@danbri.org>
Date: Thu, 8 Feb 2018 00:05:21 +0000
Message-ID: <CAFfrAFpHgStESJzLM_8sJvo5TZvMQEy1eLcdfDeJsGXXtQ_-1g@mail.gmail.com>
To: "David I. Lehn" <dil@lehn.org>
Cc: Linked JSON <public-linked-json@w3.org>
On 7 Feb 2018 18:48, "David I. Lehn" <dil@lehn.org> wrote:

Hi,
What do people think about releasing libraries with 1.1 draft spec support?


Are there test case files available?

Dan

  Gregg Kellogg has done some great work adding 1.1 support to jsonld.js
and pyld.  We'd like to release that code for people to use but I'm unsure
on how to best do it.  Once the code is out there people will start using
and depending on the features.  If changes need to be made before 1.1 is
final, it would be nice to be able to change anything as needed.

Libraries can use a semantic versioning scheme, and if the spec changes,
that will bump up the version.  But how do we deal with the JSON-LD data
itself?  We want to avoid needing tricky compatibility code for possible
old draft behavior.  Is this enough of a problem to even need a solution?
"@version": "1.1-draft-1" or similar might be nice, but that doesn't have
the 1.0 processor fail behavior.  "@version": [1.1, "draft-1"] could work,
and arrays would even allow a string "1.1" version, but maybe that's too
confusing.  Other schemes are possible too, for 1.1 processor to read other
flags, etc.  Thoughts?

The easiest thing to do is release the libs, and document that all 1.1
features are for draft specs and subject to change.  User beware.

-dave
Received on Thursday, 8 February 2018 00:05:49 UTC

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