-
Notifications
You must be signed in to change notification settings - Fork 56
DSB Maintenance Iteration 6: Agenda & Meeting Notes (15th April 2021)
Date and time: 15/04/2021, 2pm - 3pm AEST
Location: WebEx
Dial-in details:
- https://csiro.webex.com/csiro/j.php?MTID=mb6275e281ee11c0a310b1accec9aee37
- Dial In Number: +61 2 6246 4433
- Dial In Access Code: 165 089 2474
- Quick Dial: +61262464433,1650892474%23%23
Chair: Mark Verstege, DSB
Maintenance overview: Further information
Maintenance project board: See here
Decision Proposal: This maintenance iteration is being consulted on under Decision Proposal 161
-
Future Plan: Review of Q1 and new changes
-
Open Decision Proposals: key consultation dates
-
Finalising the iteration scope
- Iteration candidates that were not addressed
- Iterations candidates ready for release and a summary of future dated obligations
-
Review DP154/155/156 Enhanced Error Handling feedback and changes to be made
-
Any other business
Meeting notes
This week is the final call of the 6th maintenance iteration. The purpose of the meeting is to review the final change candidates and future dated obligations.
Further to this, the meeting will discuss the changes to be made for the Enhanced Error Handling decision proposals.
- Allow 5 min for participants to join
- Housekeeping
- Overview, purpose and intended outcomes of the meeting
- ACCC/DSB to clarify when the CDR Register will be updated to support the alternative methods of client authentication presented in Issue #360
- DSB to publish the PDF on error handling feedback - this will be responded to against the DP issue #s and request for feedback open for a short consultation
This has been provided inline to each of the DPs with feedback open until Wednesday next week - DSB to check correctness of changes to address #345. There may be additional changes to handle Rejection and Invocation metrics to make this clearer (e.g. should a '0' value always be responded on TPS for high priority if no high priority calls were made in the response period)
This has been confirmed to be correct. Additional changes have been acted upon and are available for review in the staging branch
The following decision proposals are open for community feedback
| DP # | Closing date | DP |
|---|---|---|
| 165 | 16/04/2021 | Decision Proposal 165 - Brand aware metrics |
| 168 | No closing date | Decision Proposal 168 - Separate Consents / Authorisation Withdrawal |
| 162 | No closing date | Decision Proposal 162 - CX Standards / Joint Accounts / Authorisation Flow |
| 160 | No closing date | Decision Proposal 160 - CX Standards / Non-individual Consumers / Business Partnerships / Secondary users |
Review of Q1 and new changes: https://github.com/ConsumerDataStandardsAustralia/future-plan/projects/1
https://github.com/ConsumerDataStandardsAustralia/standards-maintenance/issues/360
Summary: Data Holders may optionally support client registration of the CDR Register and private_key_jwt client authentication
Change impact: Non-breaking
Future dated obligation: Data Holders may implement from July 1st
https://github.com/ConsumerDataStandardsAustralia/standards-maintenance/issues/368
Summary: Defines the date with which v2 of the PRD endpoints can be retired by DHs. This will be added into the Future Dated Obligations section of the data standards.
Change impact: Non-breaking
Future dated obligation: If v2 is supported, Data Holders may retire the endpoint version from May 31st 2021.
Summary: Defines the date with which v1 of the Get Metrics endpoint can be retired by DHs. This will be added into the Future Dated Obligations section of the data standards.
Change impact: Non-breaking
Future dated obligation: If v1 is supported, Data Holders may retire the endpoint version from October 31st 2021.
https://github.com/ConsumerDataStandardsAustralia/standards-maintenance/issues/345
Summary: Documentation fixes to correctly treat all top-level metrics payload entities as mandatory (were conditional) whilst current/previous day metrics remain optional. Previously they were incorrectly labelled conditional but there was no condition under which they were optional to implement
Change impact: Non-breaking
Future dated obligation: Not applicable.
#369 - Remove historical audience claim requirements for Data Recipients calling Data Holders defined in the Client Authentication section
https://github.com/ConsumerDataStandardsAustralia/standards-maintenance/issues/369
Summary: Removes legacy documentation that supported pre/post Feb 2021 obligations. Now that February 2021 has passed only the post Feb 2021 text is required.
Change impact: Non-breaking
Future dated obligation: Not applicable.
Review feedback from the community and the summary of changes to be made
- https://github.com/ConsumerDataStandardsAustralia/standards/issues/154
- https://github.com/ConsumerDataStandardsAustralia/standards/issues/155
- https://github.com/ConsumerDataStandardsAustralia/standards/issues/156
A number of changes are approved or close to approval. The following release plan provides an upcoming view of the changes to be released:
- v1.8.0 will be released the mid April. Incorporates the DP144 changes only.
- v1.9.0 will be released with the Iteration 6 changes. Targeting late April.
- v1.10.0 will be released with Enhanced Error Handling changes pending final community feedback and Data Standards Chair approval. Targetting early May.
- Beyond v1.10.0: Priority changes for release will include enhanced NPP service overlay support and any changes to address the v2 rules changes. Targeting end of May / early June subject to consultation.
Address any other business arising from the community