Gregg Kellogg

> @gkellogg there's an ongoing discussion on YAML fragids here [ietf-wg-httpapi/mediatypes#50](https://github.com/ietf-wg-httpapi/mediatypes/issues/50) > > There's a proposal for applying to all xxx+yaml the fragid defined for yaml. Please have a look...

I agree that these are not specific to YAML-LD, and it is the author who chooses to use a context, not typically the end user (except for the case of...

Given a new push towards creating a YAML-LD Best Practices as a separate document, I suggest we create a new repository: https://github.com/json-ld/yaml-ld-bp which we can set up with PR-preview, which...

[Discussed at TPAC F2F](https://json-ld.org/minutes/2022-09-12/#171). Generally consensus that this is not really a good idea, in spite of the fact that it keeps coming up. In any case, the issue is...

JSON-LD does not say anything about the specifics of JSON encoding, other than ordering. Particularly, the treatment of whitespace. IMO, as an RDF serialization, two documents are equivalent if they...

> A YAML-LD Frame, together with the context, defines the serialization of some RDF data to YAML-LD. It should include: > > * same as YAML-LD frame JSON-LD frame? >...

The only use for YAML C14N I can see would be for a hypothetical YAML Literal (similar to JSON Literal). And as such, that would seem to be a spec...

> @gkellogg > > > The only use for YAML C14N I can see would be for a hypothetical YAML Literal > > The main use of JSON-LD c14n is...

Note, sadly no PR-preview on the UCR document.

This PR was discussed in the [2022-07-06 meeting](https://json-ld.org/minutes/2022-07-06/), and it was decided to not merge now, and wait until more use cases have been identified and reconciled.