RE: Status of w3c-ccg/rdf-dataset-canonicalization repo

Agreed, thanks for bringing this up, Gregg.

@PA - this is something we'll need your help with I think.

It's not just about having to keep an eye on multiple issue trackers, it's about the intellectual property now that the spec is on Rec track, so it's important that, yes, the CCG repo is archived and people interested focus on the WG's repo.

Phil



Phil Archer
Web Solutions Director, GS1
https://www.gs1.org


Meet GS1 Digital Link Developers at
https://groups.google.com/forum/#!forum/gs1-digital-link-developers


https://philarcher.org

+44 (0)7887 767755
@philarcher1
Skype: philarcher

-----Original Message-----
From: Gregg Kellogg <gregg@greggkellogg.net>
Sent: 02 December 2022 23:46
To: W3C Credentials CG <public-credentials@w3.org>
Cc: RDF Dataset Canonicalization and Hash (RCH) WG <public-rch-wg@w3.org>
Subject: Status of w3c-ccg/rdf-dataset-canonicalization repo

Issues are coming in, which should go to the WG repo. Also, issues in the CCG repo should probably be moved to, or merged with those in the WG. When this is done, I think locking down that repo to prevent further changes, and more explicitly redirect people to the RCH repo would save everyone a lot of time going forward.

Gregg Kellogg
gregg@greggkellogg.net

CONFIDENTIALITY / DISCLAIMER: The contents of this e-mail are  confidential and are not to be regarded as a contractual offer or acceptance from GS1 (registered in Belgium). 
If you are not the addressee, or if this has been copied or sent to you in error, you must not use data herein for any purpose, you must delete it, and should inform the sender. 
GS1 disclaims liability for accuracy or completeness, and opinions expressed are those of the author alone. 
GS1 may monitor communications. 
Third party rights acknowledged. 
(c) 2020.

Received on Sunday, 4 December 2022 11:26:59 UTC