Gregg Kellogg

Good call, not sure why this was not considered originally.

This should be read as if the result contains `@value` or `@list`, as it could indeed have both `@value` and `@type` or `@language`, and could also have `@index`. This could...

Summary: Step 19.1 of the [Expansion Algorithm](https://www.w3.org/TR/json-ld11-api/#algorithm-3) should be changed to the following: > 19.1) If result is a [map](https://infra.spec.whatwg.org/#ordered-map) which is empty, or contains only the [entries](https://infra.spec.whatwg.org/#map-entry) `@value` or...

@pchampin It's questionable if this is really a normative change, as we've long held that the test results are what matters, and they remain unchanged. If considered editorial, we can...

@pchampin This came up in https://github.com/w3c/json-ld-api/issues/518#issuecomment-748567302 where @iherman made the case that such changes are, indeed, normative. I'll keep it as is.

That is definitely not an expected result, and will require more investigation and addition tests. Thanks for reporting.

@tchoutri great that you're working on an implementation! At some point, we should add you to the list on json-ld.org. Regarding this issue, it is considered an Erratum, which when...

It is certainly interesting, I’m not sure we’d want to apply it to every embedded `` element in a large algorithm, but it could make the algorithm easier to take...

> Can we have this reviewed for accessibility? With the appropriate CSS media query, these could default to open. According to [this article](https://www.hassellinclusion.com/blog/accessible-accordions-part-2-using-details-summary/), summary is taxable, and the opened using...

(I believe 5.1.1 is the step you meant). I think 5.1.1 should check _result_ instead of _active context_, so the paragraph could read as follows: | If _override protected_ is...