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

Obligation milestones for 2026 and 2027 #661

Closed
nils-work opened this issue Sep 3, 2024 · 1 comment
Closed

Obligation milestones for 2026 and 2027 #661

nils-work opened this issue Sep 3, 2024 · 1 comment
Assignees
Labels
Documentation Improvements, additions or queries related to documentation Non-breaking change A change that is not expected to result in a new endpoint version. Proposal made The DSB has proposed a specific change to the standards to address the change request
Milestone

Comments

@nils-work
Copy link
Member

nils-work commented Sep 3, 2024

Description

The Milestone Dates in the Obligation Dates Schedule currently extend to 10/11/2025.
Dates beyond this will be required as new requirements and obligations develop.

Intention and Value of Change

To determine an agreed set of future milestone dates to refer to when an obligation date is required.

Area Affected

Obligation Dates Schedule

Change Proposed

To incorporate the below dates proposed for 2026 and 2027.
These dates aim for the second Monday of the month (holidays permitting) every two months (excluding Dec.-Jan.)

Obligation Milestone Milestone Date
Y26 #⁠1 16/03/2026
Y26 #⁠2 11/05/2026
Y26 #⁠3 13/07/2026
Y26 #⁠4 14/09/2026
Y26 #⁠5 09/11/2026
Y27 #⁠1 15/03/2027
Y27 #⁠2 10/05/2027
Y27 #⁠3 12/07/2027
Y27 #⁠4 13/09/2027
Y27 #⁠5 08/11/2027

DSB Proposed Solution

The current DSB proposal for this issue is in #661 (comment) (above)

@nils-work nils-work added the Documentation Improvements, additions or queries related to documentation label Sep 3, 2024
@nils-work nils-work moved this from Full Backlog to Iteration Candidates in Data Standards Maintenance Oct 31, 2024
@nils-work nils-work added this to the v1.33.0 milestone Oct 31, 2024
@nils-work nils-work self-assigned this Nov 15, 2024
nils-work added a commit to ConsumerDataStandardsAustralia/standards-staging that referenced this issue Nov 15, 2024
@nils-work
Copy link
Member Author

@nils-work nils-work added Non-breaking change A change that is not expected to result in a new endpoint version. Proposal made The DSB has proposed a specific change to the standards to address the change request labels Nov 19, 2024
nils-work added a commit to ConsumerDataStandardsAustralia/standards that referenced this issue Dec 18, 2024
* Created 1.32.0 branch base

* Staging #429 - Refactor Banking API spec

Addresses: ConsumerDataStandardsAustralia/standards-staging#429

* Create 1.33.0 branch base

* Updated refresh token expiry requirements related to Standards Maintenance issue #667

* Made links relative to avoid page refresh

Addresses: ConsumerDataStandardsAustralia/standards-staging#435 (comment)

* Added and updated servers in specs and examples

Addresses: ConsumerDataStandardsAustralia/standards-maintenance#663 (comment)

* Link to specific comment

* Remove scheme from host field

* Clarified 'CDR Arrangement JWT method' details

Addresses: ConsumerDataStandardsAustralia/standards-maintenance#663 (comment)

* Updated Reporting Requirements section

Addresses: ConsumerDataStandardsAustralia/standards-maintenance#663 (comment)

* Replaced 'must' with 'MUST' in some headers

Addresses: ConsumerDataStandardsAustralia/standards-maintenance#473 (comment)

* Applied consistent styling

Addresses: ConsumerDataStandardsAustralia/standards-staging#442

* Key word styling

Addresses: ConsumerDataStandardsAustralia/standards-staging#443

* Move note to correct section

* Corrected typos, updated styling

Addresses: ConsumerDataStandardsAustralia/standards-staging#431

* Staging #429 - Refactor Banking API spec

Addresses: ConsumerDataStandardsAustralia/standards-staging#429

* Update MTLS section 3 link

Addresses: ConsumerDataStandardsAustralia/standards-maintenance#663 (comment)

* Clarify retirement date statements

Addresses: ConsumerDataStandardsAustralia/standards-maintenance#663 (comment)

* Updated Obligation Date Schedule

Addresses: ConsumerDataStandardsAustralia/standards-maintenance#661

* Clarified transaction security requirements

Addresses: ConsumerDataStandardsAustralia/standards-maintenance#654

* Updated field descriptions

Addresses: ConsumerDataStandardsAustralia/standards-maintenance#655

* Updated CX Standards

Addresses: #350

* Updated Normative References

Addresses: ConsumerDataStandardsAustralia/standards-maintenance#675

* Tidied table formatting

* Get Product Detail v5 with LVR constraints

Addresses: ConsumerDataStandardsAustralia/standards-maintenance#657

* Rename file to prevent generated version

Addresses: ConsumerDataStandardsAustralia/standards-staging#463

* Adjusted values to align format

* Corrected Date Schedule

* Standards Maintenance 664: Support for additional NPP service overlays and all versions

* Added diff for FDO table

* Change CDS links to DSB

Addresses: ConsumerDataStandardsAustralia/standards-staging#468

* Closed list items in unordered list

* Minor corrections

* Updates

* Minor updates

- customer > consumer
- obligation sequence

* Deprecated OiDC Hybrid Flow with retirement date set for May 12th 2025

* Add condition

* Updated diff comment for OIDC hybrid flow to indicate it is deprecated

* Update get-transaction-detail-v1.html.md

* Apply dates, logo and correct merge differences

* Rebuild

* Rebuild specs

* Minor corrections

* Update obligation table

---------

Co-authored-by: Mark Verstege <[email protected]>
@nils-work nils-work moved this from In Progress: Staging to Awaiting Chair Approval in Data Standards Maintenance Dec 18, 2024
@nils-work nils-work moved this from Awaiting Chair Approval to Done in Data Standards Maintenance Dec 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Documentation Improvements, additions or queries related to documentation Non-breaking change A change that is not expected to result in a new endpoint version. Proposal made The DSB has proposed a specific change to the standards to address the change request
Projects
Status: Done
Development

No branches or pull requests

1 participant