- From: Anders Rundgren <anders.rundgren.net@gmail.com>
- Date: Sun, 9 Jul 2023 07:28:18 +0200
- To: Harrison <harrison@spokeo.com>
- Cc: "W3C Credentials CG (Public List)" <public-credentials@w3.org>, Mike Prorock <mprorock@mesur.io>, Kimberly Linson <kimberly.linson@randasolutions.com>, Henk Birkholz <henk.birkholz@sit.fraunhofer.de>
Hi Harrison, Currently several VC-related drafts depend on canonicalization methods that have been *dismissed* by the IETF. Deterministic CBOR Encoding is a very simple concept that unlike JSON canonicalization, has a good chance becoming a true standard, potentially being an intrinsic part of future iterations of mainstream computing platforms. The latter is currently out of scope for the IETF so my plan is to establish this through TC39; essentially following the tracks of JSON. Anders On 2023-07-09 0:18, Harrison wrote: > Thanks for your comment, Anders. I think we can go over this "Deterministic Encoding" issue if we have time, or we can hold a more in-depth discussion at a later date. The primary goal of this coming Tuesday's discussion is for our community to get a detailed and accurate understanding of CBOR in general since it has been brought up several times in prior discussion threads. > > Hope you and everyone else can join us this coming Tuesday 7/11 ! > > Sincerely, > Harrison > > On Sat, Jul 8, 2023 at 2:09 AM Anders Rundgren <anders.rundgren.net@gmail.com <mailto:anders.rundgren.net@gmail.com>> wrote: > > On 2023-07-05 20:06, Harrison wrote: > > *Main Agenda: CBOR - Concise Binary Object Representation * > > > > We are excited to have Henk Birkholz <https://de.linkedin.com/in/iot-ng <https://de.linkedin.com/in/iot-ng>>present "CBOR - Concise Binary Object Representation" at our W3C CCG meeting next Tuesday. Henk is a CBOR and standards expert, and he can help answer questions like where and how to use CBOR. > > Unfortunately the CBOR WG have not made up their mind about "Deterministic Encoding", a feature that could prove to be paramount for future, crypto-using applications like credentials and digital wallets. > > Although my "brain-child" JCS (RFC 8785) indeed have gotten some traction, I believe using deterministically encoded CBOR (as *default*), is way better idea, particularly when augmented with bi-directional "Diagnostic Notation". > > Anders > > Proposal: https://cyberphone.github.io/android-cbor/distribution/apidoc/org/webpki/cbor/package-summary.html#deterministic-encoding <https://cyberphone.github.io/android-cbor/distribution/apidoc/org/webpki/cbor/package-summary.html#deterministic-encoding> > > WIP: https://github.com/cyberphone/CBOR.js#cborjs <https://github.com/cyberphone/CBOR.js#cborjs> > Shipping: https://github.com/cyberphone/android-cbor#cbor-for-android <https://github.com/cyberphone/android-cbor#cbor-for-android> > > > > > -- > > > > Time: Tuesday 2023-06-20 at 9am PT, 12pm noon ET, 5pm GMT, 6pm CET**Time for 55 min. https://www.timeanddate.com/worldclock/converter.html?iso=20220215T170000&p1=tz_pt&p2=tz_et&p3=tz_cet&p4=tz_gmt&p5=tz_nzdt&p6=tz_nzst <https://www.timeanddate.com/worldclock/converter.html?iso=20220215T170000&p1=tz_pt&p2=tz_et&p3=tz_cet&p4=tz_gmt&p5=tz_nzdt&p6=tz_nzst> <https://www.timeanddate.com/worldclock/converter.html?iso=20220215T170000&p1=tz_pt&p2=tz_et&p3=tz_cet&p4=tz_gmt&p5=tz_nzdt&p6=tz_nzst <https://www.timeanddate.com/worldclock/converter.html?iso=20220215T170000&p1=tz_pt&p2=tz_et&p3=tz_cet&p4=tz_gmt&p5=tz_nzdt&p6=tz_nzst>> > > > > Jitsi Teleconf: > > https://meet.w3c-ccg.org/weekly <https://meet.w3c-ccg.org/weekly> <https://meet.w3c-ccg.org/weekly <https://meet.w3c-ccg.org/weekly>> > > > > Text Chat: > > http://irc.w3.org/?channels=ccg <http://irc.w3.org/?channels=ccg> <http://irc.w3.org/?channels=ccg <http://irc.w3.org/?channels=ccg>> > > irc://irc.w3.org:6665/#ccg <http://irc.w3.org:6665/#ccg> <http://irc.w3.org:6665/#ccg <http://irc.w3.org:6665/#ccg>> > > > > Voice: > > US phone: tel:+1.602.932.2243;1 > > > > Agenda: > > 1. Code of Ethics & Professional Conduct Reminder: https://www.w3.org/Consortium/cepc/ <https://www.w3.org/Consortium/cepc/> <https://www.w3.org/Consortium/cepc/ <https://www.w3.org/Consortium/cepc/>> > > 2. IP Note: > > a. Anyone can participate in these calls. However, all substantive contributors to any CCG Work Items must be members of the CCG with full IPR agreements signed. https://www.w3.org/community/credentials/join <https://www.w3.org/community/credentials/join> <https://www.w3.org/community/credentials/join <https://www.w3.org/community/credentials/join>> > > b. Ensure you have a W3 account: https://www.w3.org/accounts/request <https://www.w3.org/accounts/request> <https://www.w3.org/accounts/request <https://www.w3.org/accounts/request>> > > c. W3C Community Contributor License Agreement (CLA): > > https://www.w3.org/community/about/agreements/cla/ <https://www.w3.org/community/about/agreements/cla/> <https://www.w3.org/community/about/agreements/cla/ <https://www.w3.org/community/about/agreements/cla/>> > > 3. Call Notes: > > a. Meeting minutes and audio recordings: https://w3c-ccg.github.io/meetings/ <https://w3c-ccg.github.io/meetings/> <https://w3c-ccg.github.io/meetings/ <https://w3c-ccg.github.io/meetings/>> > > b. We use Jitsi chat (linked with IRC at http://irc.w3.org/?channels=ccg <http://irc.w3.org/?channels=ccg> <http://irc.w3.org/?channels=ccg <http://irc.w3.org/?channels=ccg>> or http://irc.w3.org:6665/#ccg <http://irc.w3.org:6665/#ccg> <http://irc.w3.org:6665/#ccg <http://irc.w3.org:6665/#ccg>>) to queue speakers during the call as well as to take minutes. > > c. In IRC type “q+” to add yourself to the queue, with an optional reminder, e.g., “q+ to mention something”. The “to” is required. > > 4. Introductions & Reintroductions > > 5. Announcements & Reminders: https://w3c-ccg.github.io/announcements/ <https://w3c-ccg.github.io/announcements/> <https://w3c-ccg.github.io/announcements/ <https://w3c-ccg.github.io/announcements/>> > > 6. Work Items: > > https://github.com/w3c-ccg/community/issues?q=is%3Aopen+is%3Aissue+label%3A%22action%3A+review+next%22 <https://github.com/w3c-ccg/community/issues?q=is%3Aopen+is%3Aissue+label%3A%22action%3A+review+next%22> <https://github.com/w3c-ccg/community/issues?q=is%3Aopen+is%3Aissue+label%3A%22action%3A+review+next%22 <https://github.com/w3c-ccg/community/issues?q=is%3Aopen+is%3Aissue+label%3A%22action%3A+review+next%22>> > > 7. Main Agenda > > 8. Discussions > > > > Upcoming Meetings: https://www.w3.org/groups/cg/credentials/calendar <https://www.w3.org/groups/cg/credentials/calendar> <https://www.w3.org/groups/cg/credentials/calendar <https://www.w3.org/groups/cg/credentials/calendar>> > > > > Thanks, > > > > -- > > > > *Harrison Tang* > > CEO > > <https://www.linkedin.com/in/theceodad/ <https://www.linkedin.com/in/theceodad/>>LinkedIn <https://www.linkedin.com/in/tangtalks/ <https://www.linkedin.com/in/tangtalks/>><https://www.linkedin.com/in/theceodad/ <https://www.linkedin.com/in/theceodad/>> • <https://twitter.com/TheCEODad <https://twitter.com/TheCEODad>>Twitter <https://twitter.com/tang_talks <https://twitter.com/tang_talks>> • <https://www.tiktok.com/@tang_toks <https://www.tiktok.com/@tang_toks>> Tiktok <https://www.tiktok.com/@tang_toks <https://www.tiktok.com/@tang_toks>> • <https://www.facebook.com/TheCEODad <https://www.facebook.com/TheCEODad>> Facebook <https://www.facebook.com/tangtalks/ <https://www.facebook.com/tangtalks/>> > > > > > > -- > > *Harrison Tang* > CEO > <https://www.linkedin.com/in/theceodad/>LinkedIn <https://www.linkedin.com/in/tangtalks/><https://www.linkedin.com/in/theceodad/> • <https://twitter.com/TheCEODad>Twitter <https://twitter.com/tang_talks> • <https://www.tiktok.com/@tang_toks> Tiktok <https://www.tiktok.com/@tang_toks> • <https://www.facebook.com/TheCEODad> Facebook <https://www.facebook.com/tangtalks/> >
Received on Sunday, 9 July 2023 05:28:27 UTC