[Openid-specs-fapi] Fwd: New deterministic CBOR Libraries (Rust & Swift) from Blockchain Commons

[Anders Rundgren]

It seems that my idea to exploit deterministic CBOR certainly was not "mine" :)
The future format for financial messaging may very well be CBOR: https://fido-web-pay.github.io/
With the coming URL object identifier RFC, deterministic CBOR beats XML and JSON hands down.
Anders
https://github.com/cyberphone/cbor-everywhere



-------- Forwarded Message --------
Subject: 	New deterministic CBOR Libraries (Rust & Swift) from Blockchain Commons
Resent-Date: 	Thu, 16 Feb 2023 01:00:25 +0000
Resent-From: 	public-vc-wg at w3.org
Date: 	Wed, 15 Feb 2023 16:59:31 -0800
From: 	Christopher Allen <ChristopherA at lifewithalacrity.com>
To: 	Credentials Community Group <public-credentials at w3.org>, W3C Verifiable Credentials WG <public-vc-wg at w3.org>
CC: 	Wolf McNally <wolf at wolfmcnally.com>, Shannon Appelcline <shannon.appelcline at gmail.com>



Since I know that many projects in the broader Credentials Community already use CBOR, I'd like to announce Blockchain Commons' release of dCBOR libraries for Rust and Swift. In particular, these two languages demonstrate our support of use cases for dCBOR for mobile in Android and iOS:

  * *dCBOR Codec for Rust:* https://github.com/BlockchainCommons/bc-dcbor-rust
  * *dCBOR Codec for Swift:* https://github.com/BlockchainCommons/BCSwiftDCBOR

We've also produced a CLI app using our Rust library, which can be used to test parsing and validation:

  * *dCBOR CLI:* https://github.com/BlockchainCommons/dcbor-cli

We focused on the deterministic flavor of CBOR per §4.2 of RFC-8949 <https://www.rfc-editor.org/rfc/rfc8949.html#name-deterministically-encoded-c>because of our specific need to produce deterministically repeatable hashes in the Merkle Tree underlying our Gordian Envelope <https://www.blockchaincommons.com/introduction/Envelope-Intro/> data format. We suspect that there will be others with similar needs and hope these dCBOR libraries will prove useful for other specs & standards using CBOR!

I'd love to get any advice, comments, or thoughts you have on our dCBOR libraries, as well as any requirements that the libraries may need to meet. I'd also appreciate to get any CCG-related CBOR test examples that we can use in documents and examples, such as mDL and COSE tests.

I'm also happy to discuss why we picked CBOR <https://www.blockchaincommons.com/introduction/Why-CBOR/> as a data format and why dCBOR is particularly advantageous, either here or in our discussion forums at GitHub <https://github.com/orgs/BlockchainCommons/discussions/184>.

Thanks!

-- Christopher Allen
    Blockchain Commons
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-fapi/attachments/20230216/6b10a9f9/attachment.html>