Re: release process for 1.1 libraries?

On Feb 7, 2018, at 4:05 PM, Dan Brickley <danbri@danbri.org> wrote:
> 
> 
> 
> 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?

Tests are mixed with the main test suite at json-ld.org/test-suite and marked with a combination of “specVersion” and “processingMode” options.

At this point, My Ruby gem json-ld, and Digital Bazaar’s jsonld.js pass them all, with the Python pyld library almost complete (just framing to go).

Gregg

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