Prepare gnverifier to v1.0.0 release about gnverifier HOT 5 CLOSED

@abubelinha I was trying to stabilize API for a few months, and your feedback played an important role in that process. Moving to v1.0.0 would indicate that API is considered stable, and its parameters and schema will stop changing, only new parameters will be added. So movement to v1.0.0 only included changing URLs and version numbers. Other than that it is the same as the previous v1.0.0-RC1.

Of course nothing prevents me to find out that I made some huge mistake and API must become backward incompatible. However in such case a change should really be important, and this time v1 will continue to be served. In addition v2.0.0 will be also served in parallel.

Sorry for the troubles of this transition, but I think it was important to promise stability. For example gnparser reached v1.0.0 (a stable version) one year and seven months ago and its API and schema were stable since then.

from gnverifier.

Hi @dimus
Not sure if this is related but my scripts based on this url are failing:
https://verifier.globalnames.org/api/v0/verifications/

As mentioned in #68, #82 and #90, I understood that "v0" was the suggested api access to rely on.

Have you made any changes that we need to be aware of?
(I hope this fail only means we just need to change v0 to v1 in our urls from now on)

Thanks!

from gnverifier.

@abubelinha yes, it is related, you can change v0 to v1 and it should work again.

Also I did cheat here. According to rules I supposed to change /api/v0 to /api/v2 because I did have /api/v1 already. However I knew that almost nobody used /api/v1, and I wanted to have application version (v1.0.0) to match API version to avoid confution. So old /api/v1 is now gone, and /api/v0 became /api/v1. When/if I will start working on backward incompatible v2.x.x, I will again make /api/v0 until the release of v2.0.0, Then /api/v0 will become /api/v2 and /api/v1 will continue to be around and functional.

from gnverifier.

I am thinking if I should make a redirect of /api/v0 to /api/v1, until there is again a developing version in place, however it would just postpone this problem to some random time.

from gnverifier.

Thanks for your confirmation.
I updated the url and made a simple test: my scripts seem to be working again.

But just in case I am missing some advanced options, I prefer to ask:
Are there any request/response API parameters that might have been modified during the last weeks?

Thanks a lot in advance

from gnverifier.