Re: Reconciliation CG kick-off

I agree on documenting the current ecosystem of tools/clients/software that
use Reconciliation API (or a derivative of it).

I think setting up a Github repo (which can include Issues, Wiki, etc)
would be helpful to begin that documentation.
(CURRENTLY: A lot of the Reconciliation API is documented here -
https://github.com/OpenRefine/OpenRefine/wiki/Reconciliation-Service-API)

But since this is not about OpenRefine's historical usage of Reconciliation
API, but instead about describing and furthering and promoting a standard
so that tools/clients/software can allow Reconciliation as a Service
(RaaS), more or less, and a greater ecosystem.  So, I think a Github repo
with all it's bells and whistles gives us a lot of what we need to start
with.  Github has worked well for us in Schema.org and Open Mobile Alliance
while still keeping W3C community group as a way for official communication
and voting within the community.

As far as promoting a Reconciliation standard, I have mixed feelings about
drafting within W3C, but at the same time, many vendors look towards a
community process and standards output and ratified from that process as a
signal for them to begin adoption in their tools/clients/software and even
still fewer adopt any standards built outside of a collaborative community
process like we have (ISO, W3C, Apache, Oasis, etc.)

Administratively, I think the CGCharter template is fine.  I withhold
opinion and defer on any chair appointments towards myself. No interest in
chairing  :-)

Thad
https://www.linkedin.com/in/thadguidry/