Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Commissioning /decommissioning dates of the product APIs #202

Closed
C-Blatch opened this issue Apr 27, 2020 · 3 comments
Closed

Commissioning /decommissioning dates of the product APIs #202

C-Blatch opened this issue Apr 27, 2020 · 3 comments

Comments

@C-Blatch
Copy link

In the latest release of the standards (v1.3) it refers to the commissioning /decommissioning dates of the product APIs.
For both Get Products and Get Products Detail the Future Data Obligations table states that;

However if you follow through on the V2 link for either of the V2 of the APIs, you get the statement that

Which would mean V2 is to be decommissioned before V3 goes live, by 6 months. Please confirm if the above decommission date should be 29-Aug-2021.

@C-Blatch C-Blatch added the query label Apr 27, 2020
@Camios
Copy link

Camios commented Apr 27, 2020

When I first saw it, I assumed it was a copy and past from the v1 endpoint's obsolescence page. If it was a copy and paste mistake, then v2's decommission date may not be in August.

e.g. When V2 was created to replace V1, the overlap for both being available was only a month (V2 to be available by end July-2020 and V1 to be decommissioned by 29-Aug-2020).

If the same period applies for the V3 to V2 overlap, then V2 would be decommissioned one month after V3 became available. Interestingly V3 only specifies a month of availability: February 2021 (end of month)

Assuming for arguments sake it is the end of February, then V2's decommission date might be the end of March 2021.

Note Dates are pre-COVID extensions.

@CDR-API-Stream
Copy link
Collaborator

This is a known issue and will be fixed in v1.3.1 of the standards.

@CDR-API-Stream
Copy link
Collaborator

This change has been addressed in the data standards. This issue has been answered and it is being closed accordingly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants