- From: Gregg Kellogg <gregg@greggkellogg.net>
- Date: Wed, 11 Jan 2023 09:00:19 -0800
- To: Manu Sporny <msporny@digitalbazaar.com>
- Cc: Dan Yamamoto <dan@iij.ad.jp>, public-rch-wg@w3.org
> On Jan 11, 2023, at 7:36 AM, Manu Sporny <msporny@digitalbazaar.com> wrote: > >> On 2023/01/11 9:33, Pierre-Antoine Champin wrote: >>> I have just implemented the c14n algorithm in Rust [1]. It went quite > On Tue, Jan 10, 2023 at 7:54 PM Dan Yamamoto <dan@iij.ad.jp> wrote: >> Coincidentally, I have also developed a rough implementation of the >> rdf-canon specification by Rust. > > Guys, that's fantastic! Thank you! What wonderful news! > > I know this is premature, but what would we need to go to CR at this > point? We already have multiple implementations using the algorithm in > the spec... I'm sure there are some W3C Process timeline's we need to > wait for... and issues to process, of course, but what are the major > items needing to still be done to get to CR? A couple of things I can think of: * We need to describe serialization of the results, not just the canonicalization algorithm. This is from issue #4, which is up for discussion. * In addition to other open issues, the spec has a number of editor’s notes scattered throughout, which should be addressed in one way or another. * We depend on changes to N-Quads, which could potentially get an FPWD in the next month or so. IIRC, for us to get into CR, our normative dependencies need to be at least WD. Plus, of course, the issues Ivan mentioned. Gregg > -- manu > > -- > Manu Sporny - https://www.linkedin.com/in/manusporny/ > Founder/CEO - Digital Bazaar, Inc. > News: Digital Bazaar Announces New Case Studies (2021) > https://www.digitalbazaar.com/ >
Received on Wednesday, 11 January 2023 17:00:44 UTC