- From: Thad Guidry <thadguidry@gmail.com>
- Date: Fri, 15 Dec 2023 06:36:02 +0800
- To: Antonin Delpeuch <antonin@delpeuch.eu>
- Cc: "public-reconciliation@w3.org" <public-reconciliation@w3.org>
- Message-ID: <CAChbWaOyFU8P4Z9UP12mY45_DaPWo7hgavjzahu+1j-Mh9w9qA@mail.gmail.com>
Maybe any manifest changes? Thad https://www.linkedin.com/in/thadguidry/ https://calendly.com/thadguidry/ On Fri, Dec 15, 2023 at 12:00 AM Antonin Delpeuch <antonin@delpeuch.eu> wrote: > Hello all, > > I noticed we haven't published a blog post on > https://www.w3.org/community/reconciliation/ for a while. I thought > about writing one, highlighting a few things which have been happening > around the reconciliation protocol over the past year. > > I need your help to collect those things! So far, I could come up with > the following (which I would develop in paragraphs for a blog post): > > - our group was active this year, continuing our improvements of the > specifications on various fronts (including publishing final specs for > the 0.1 and 0.2 versions of the protocol) > > - a new Global Names reconciliation service was published. See > https://github.com/gnames/gnverifier/wiki/OpenRefine-readme > > - a reconciliation service for the RĂ©pertoire International des Sources > Musicales (RISM) was created. See > https://rism.online/docs/reconciliation/introduction/ > > - thanks to a grant from the NFDI4Culture consortium, OpenRefine > improved the user experience of its reconciliation feature (to be > released in the upcoming 3.8 version). > > Anything else we should mention? Even small improvements in existing > clients or reconciliation services are worth sharing. > > Cheers, > > Antonin > > >
Received on Thursday, 14 December 2023 22:36:20 UTC