- From: Anders Rundgren <anders.rundgren.net@gmail.com>
- Date: Mon, 28 Nov 2022 07:16:40 +0100
- To: Christopher Allen <ChristopherA@lifewithalacrity.com>, "Michael Herman (Trusted Digital Web)" <mwherman@parallelspace.net>
- Cc: "public-credentials (public-credentials@w3.org)" <public-credentials@w3.org>
On 2022-11-27 17:59, Christopher Allen wrote: > On Sat, Nov 26, 2022 at 11:33 PM Michael Herman (Trusted Digital Web) <mwherman@parallelspace.net <mailto: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. https://github.com/BlockchainCommons/BCSwiftSecureComponents/blob/master/Docs/02-ENVELOPE.md CBOR + Deterministic serialization! This is the s**t, finally get rid of Base64 (JOSE) or putting everything crypto-ish in "bstr" (COSE). Trivial to do, works like charm, and makes ASN.1 DER look like rocket science. Anders https://github.com/cyberphone/D-CBOR > > See intro: https://www.blockchaincommons.com/introduction/Envelope-Intro/ <https://www.blockchaincommons.com/introduction/Envelope-Intro/> > > A use case: https://github.com/BlockchainCommons/Gordian/blob/master/Docs/Envelope-Use-Cases-Educational.md <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 <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 Monday, 28 November 2022 06:16:53 UTC