w3c / json-ld-framing

JSON-LD 1.1 Framing Specification
https://w3c.github.io/json-ld-framing/
Other
25 stars 20 forks source link

Should tests for `@embed`: `@last` be restricted to JSON-LD 1.0? #110

Closed kal closed 1 year ago

kal commented 4 years ago

The test t0059 tests handling of @last as a value of @embed with a specVersion of 1.1, but the 1.1 spec says that this is an invalid @embed value. Should the specVersion option for this test be json-ld-1.0 rather than 1.1?

gkellogg commented 4 years ago

It is supported as processingMode is set to json-ld-1.0. Even though framing was not a 1.0 recommendation, but a community spec, it was widely implemented, and @last was, in fact, the default value in the previous version.

As other places in the spec mention things to do for json-ld-1.0 processing mode, it might be worth a future editorial update to add these things, but it would mean placing emphasis on some specifically outdated mechanisms.

kal commented 4 years ago

Thanks Greg. I agree that an editorial update would be very useful. If the intention is that a JSON-LD 1.1 Framing conformant processor should implement support for @first and @last then those values and the intended semantics that should ideally be included in the specification, and at a minimum the definition for the allowed values of @embed should include those values and note that support for them is expected.

gkellogg commented 4 years ago

It should also probably be clear that operating in json-ld-1.0 mode is not required for conformance. It's intended for backwards compatibility.

gkellogg commented 1 year ago

Removing the ErratumRaised flag, as this does not affect the specification, itself.