Dmitry Mozzherin

I decided to sunset API v0, sorry for the confusion @abubelinha, and I will try hard to keep backward compativility for API v1, at least for JSON output.

It is indeed a problem. And it is not only code, because database evolves as well, although, it mostly stays backward compatible sofar. However, nothing prevents a situation where an...

Usually I use formula: work/users_num I think it is something that everybody who publishes their results would need, so I think it is not so much work in the end....

for gndiff it should be easy, it has no remote dependencies, so just its version defines the result

Someone wanted to cite gnames, so I created Zenodo link for that purpose. Being lazy, I prefer to avoid unnecessary work, so I decided not to update these links, until...

I these tree/vx.x.x and vx.x.x mean the same. In case of github links I usually use something like https://github.com/gnames/gnverifier/releases/tag/v0.8.2

I wonder if they made updates to OTT, but did not publish it yet. It seems they still have OTT v3.2 from 2019 for download https://tree.opentreeoflife.org/about/taxonomy-version/ott3.2

I see, I think it is a bug. gnverify should return as the best result https://tree.opentreeoflife.org/taxonomy/browse?name=2485, because it was parsed clearly.

@abubelinha, first of all thanks a lot for reporting https://github.com/gnames/gnverifier/issues/83, it would be very hard to find without your spotting of the problem. Q1: Currently gnverifier database is rebuilt from...

Sometimes differences are, indeed, speed requirements, but in other cases are just playing with parameters. I will go through your examples, and analyze their behavior in gnverifier. For cases where...