Re: CBOR-LD Codecs and JSON-LD in general

I don’t recall that we finalized CBOR-LD, did we?  It really isn’t the same as the others, as it was more focused on the compression/optimization options that BC Commons is trying to introduce - though I wish they would have done it in a formal standards body instead of going their own way ☹️.

Leonard

From: Christoph <christoph@christophdorn.com>
Date: Wednesday, February 25, 2026 at 2:02 PM
To: JSON-LD Working Group <public-json-ld-wg@w3.org>
Subject: CBOR-LD Codecs and JSON-LD in general


EXTERNAL: Use caution when clicking on links or opening attachments.


Hi All!

I am interested in CBOR-LD Codecs and JSON-LD in general.

I am building a JS/TS stack. I have played with third party JSON-LD resolvers and related libs but am leaning towards implementing my own. To make that safer, I am looking for implementations to validate against.

  1.  Which JSON-LD implementations (JS preferred but other languages ok) should I make sure I am compatible with to ensure my library fits into the ecosystem?
     *   Is there a good set of tests including json-ld test documents somewhere that I can use to compare my library behaviour?
     *   Are there known experimental additions to JSON-LD that seem to make sense to explore?
  2.  Is there an implementation for CBOR-LD Codecs I can look at?
     *   I am building towards Gordian Envelopes [1] so I am also curious if dCBOR [2] poses any problems to CBOR-LD Codecs?

Thanks!
Christoph

[1] - https://developer.blockchaincommons.com/envelope/

[2] - https://datatracker.ietf.org/doc/draft-mcnally-deterministic-cbor/