- From: Antonin Delpeuch <antonin@delpeuch.eu>
- Date: Fri, 12 Jan 2024 13:52:31 +0100
- To: public-reconciliation@w3.org
- Message-ID: <b23e9c35-f2e1-4d50-8d68-bfaca8e6a5ea@delpeuch.eu>
Hi Daniel, That's amazing! I opened a PR [1] to add it to our census list of reconciliation clients [2]. Thanks also for opening these issues about clarifications to the specs. I hope we can address them all in the next version of the specs. Feel free to join the community group (which you can do in a personal capacity) if you feel like it. I would also be curious to know more about your use case: are you building an application on top of this library? Which reconciliation services are you primarily interested in using? Best, Antonin [1] : https://github.com/reconciliation-api/census/pull/26 [2] : https://reconciliation-api.github.io/census/clients/ On 12/01/2024 06:25, Daniel Erenrich wrote: > Just a small announcement that I've put together a new python library > wrapping the 0.2 version of the spec. > > You can find the library on github > <https://github.com/derenrich/py-reconciliation-service-api>/ pypi > <https://pypi.org/project/py-reconciliation-service-api/>. > Contributions welcome! > > I did find a few issues in the spec/common implementations when > writing this. For example the geonames > <https://fornpunkt.se/apis/reconciliation/geonames> implementation > returns identifiers as numbers instead of strings (as the spec > requires). And the encyclopedia of life > <https://eol.org/api/reconciliation> API seems to ignore the limit > query (it's not totally clear from the spec if ignoring the limit > param is compliant). > > Hope this is helpful to someone, > Daniel >
Received on Friday, 12 January 2024 12:52:35 UTC