On Sat, Nov 26, 2022 at 11:33 PM Michael Herman (Trusted Digital Web) < mwherman@parallelspace.net> wrote: > I hope people are following this thread on LinkedIn and elsewhere... > Our Envelope spec offers an alternative VC/DID binary CBOR format, that also doesn’t require context and focuses on agency about privacy through supports of encryption, redaction & inclusion proofs from the bottom for all parties, in particular holders. See intro: https://www.blockchaincommons.com/introduction/Envelope-Intro/ A use case: https://github.com/BlockchainCommons/Gordian/blob/master/Docs/Envelope-Use-Cases-Educational.md We plan to submit this spec as an IETF Internet-Draft by end of this week. https://blockchaincommons.github.io/WIPs-IETF-draft-envelope/draft-mcnally-envelope.html ABSTRACT: The envelope protocol specifies a format for hierarchical binary data built on CBOR. Envelopes are designed with "smart documents" in mind, and have a number of unique features including easy representation of semantic structures like triples, built-in normalization, a built-in Merkle-like digest tree, and the ability for the holder of a document to selectively encrypt or elide specific parts of a document without invalidating the digest tree or cryptographic signatures that rely on it. — Christopher Allen >
Received on Sunday, 27 November 2022 16:59:30 UTC