specVersion clarification

[daenney]

I've been implementing the 1.1 spec and am now at a stage where I'm running the expansion tests.

Test t0024 fails for me, which has a context of

  "@context": {
    "http://www.w3.org/1999/02/22-rdf-syntax-ns#type": {"@id": "@type", "@type": "@id"}
  }

It fails in 14.2.4.2 of Create Term in my case, though this might just be a bug on my side.

However, I noticed that the specVersion for that test is set to 1.0. Does that mean that this test is not expected to pass, or be run, by a 1.1 implementation, even in 1.0 processing mode?

[gkellogg]

However, I noticed that the specVersion for that test is set to 1.0. Does that mean that this test is not expected to pass, or be run, by a 1.1 implementation, even in 1.0 processing mode?

Yes, this is described in the test vocabulary document https://w3c.github.io/json-ld-api/tests/vocab and in README.md:

Unless processingMode is set explicitly in a test entry, processingMode is compatible with both json-ld-1.0 and json-ld-1.1.

It is intended allow 1.0-conforming processors to continue to work for 1.0-conforming tests.

We might add more to that statement above, if it's not sufficiently clear.

[daenney]

I understood the processingMode one, but how it interacted with specVersion wasn't clear to me.

The concept that was missing for me is that when specVersion is explicitly set, only a processor implemented according to that version of the spec should run it. So when specVersion: 1.0 is set, behaviour between 1.0 and 1.1 has changed in a backwards incompatible way.

My brain sort of sees 1.1 as an evolution of 1.0, so it felt like even without processingMode specified, a specVersion of 1.0 implied processingMode: 1.0 even for a 1.1 implementation.