Gregg Kellogg

One stated goal is to be able to use something like `YAML.dump` of the parsed JSON/YAML, which will likely not allow defining how data is serialized in these cases. This...

It’s probably a more a more philosophical question: Must a JSON Literal necessarily have the form of JSON?

The JSON-LD Literal definition is written to allow a variation in representation. The JCS C14N considerations only come into play when describing the representation within RDF Triples. Similar to `rdf:XMLLiteral`...

@VladimirAlexiev said: > 1. When converting to RDF, a `@json` literal should be treated as opaque and left alone, see https://w3c.github.io/json-ld-syntax/#the-rdf-json-datatype. I have more examples of such needs: Then converting...

> @VladimirAlexiev Afaik JSON grammar allows duplicate keys. No, I believe this has been addressed by [RFC8259](https://www.rfc-editor.org/rfc/rfc8259): > The names within an object SHOULD be unique. Not a MUST, but...

With regard to JSON Literals, the spec uses JCS. IIRC, the spec is silent on duplicate keys, and as noted in the RFCs, May have different behaviors. This is at...

> What do you mean with "JSON subset"? If you mean something like the "internal representation" than its feasible. Otherwise I think that we can only check that the representation...

This issue was discussed on the [Aug 03](https://json-ld.org/minutes/2022-08-03/) meeting.

> @ioggstream -- Please edit your [#36 (comment)](https://github.com/json-ld/yaml-ld/issues/36#issuecomment-1174751556) and wrap code fences (either single or triple backticks) around all `@`terms that aren't meant to link to GitHub users (e.g., ``...

I propose closing this saying that YAML-LD has no specific encoding requirements for `@json` value objects as long as round-tripping YAML to JSON reproduces an equivalent structure.