- From: Andreas Wagner <wagner@lhlt.mpg.de>
- Date: Fri, 15 Dec 2023 08:47:24 +0100
- To: <public-reconciliation@w3.org>
- Message-ID: <619FE83E-BA09-44D7-9D30-E3738F90320C@lhlt.mpg.de>
Hello Antonin, hello all, when is this blog post meant to be published? I have worked a bit on the reconciliation connector for TEI Publisher but ran out of time when the pull request(s) got stuck. No serious problems, though, and I suppose I could get it merged until early January... https://github.com/eeditiones/tei-publisher-app/pull/204 https://github.com/eeditiones/tei-publisher-components/pull/168 Best wishes, Andreas Am 14. Dezember 2023 16:59:38 MEZ schrieb Antonin Delpeuch <antonin@delpeuch.eu>: >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 > > -- Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.
Received on Friday, 15 December 2023 08:48:39 UTC