CBOR-LD w/o JSON-LD?

Thanks for pointing out that CBOR-LD is still under development and I just read the latest version (Feb 2026, https://w3c.github.io/cbor-ld/).

The one thing that struck me as problematic with the proposal is that it is written assuming that someone using it MUST be using it for the purposes of going between JSON-LD <-> CBOR-LD.  All sections talk about that workflow, but not about the general case of simply working with CBOR-LD natively.

For example, we’ve been hoping to adopt CBOR-LD as part of the Content Credentials specification (https://c2pa.org/specifications/specifications/2.3/specs/C2PA_Specification.html) which uses CBOR natively - with no JSON(-LD) processing.  But as currently written, none of the sections in the CBOR-LD spec apply since they all talk about their use when converting between the LD formats.

Can we see about revamping all of that to simply talk about using CBOR-LD in the general case with conversion as a secondary case?

Leonard