DSB Maintenance Iteration 10: Agenda & Meeting Notes (6 April 2022)
Date and time: 04/04/2022, 2:00pm – 4:00pm AEST
Location: WebEx
Dial-in details:
- https://treasuryau.webex.com/treasuryau/j.php?MTID=mf148de6a206fb95e1d25055ee9b7c90d
- Dial In Number: +61 2 9338 2221
- Dial In Access Code: 2653 293 7148
- Quick Dial: +61-2-9338-2221,,26532937148## Australia Toll
Chair: Ivan Hosgood, DSB
Maintenance overview: Further information
Maintenance project board: See here
Decision Proposal: This maintenance iteration is being consulted on under Decision Proposal 237
The Maintenance Iteration Calls are recorded for note taking purposes only. All recordings are kept securely, as are the transcripts which may be made from them. No identifying material will be provided without the participant's consent. Participants may email [email protected] should they have any further questions or wish to have any material redacted from the record.
We acknowledge the Traditional Custodians of the various lands on which we work today and the Aboriginal and Torres Strait Islander people participating in this call.
We pay our respects to Elders past, present and emerging, and recognise and celebrate the diversity of Aboriginal peoples and their ongoing cultures and connections to the lands and waters of Australia.
- Housekeeping
- Introductions
- Iteration 10 issues not discussed on 30 March 2022
- Any other business
Meeting notes
This week is an additional call, the fifth, for the 10th Maintenance Iteration.
The purpose of the meeting is to discuss 6 issues on the Agenda for Meeting 4 that were not discussed.
- Overview, purpose and intended outcomes of the meeting
The full agenda for Meeting 4 is available here https://github.com/ConsumerDataStandardsAustralia/standards/wiki/DSB-Maintenance-Iteration-10:-Agenda-&-Meeting-Notes-(30-March-2022)
All open change requests can be found here: Standards Maintenance Issues.
The standards maintenance backlog can be found here: Data Standards Maintenance
Discussion in today's meeting is limited to the following change requests which are currently in the design stage for this iteration:
| Issue # | Sector | Change Request | Decision | Change Status | Future Dated Obligation (FD) |
Affected Schema (if applicable) |
Affected Endpoint (if applicable) |
Recommendation |
|---|---|---|---|---|---|---|---|---|
| 488 | Register | Data holder behaviour clarification required when receiving registrations with unsupported authorisation scopes | Change Recommended | Breaking change | 15/11/2022 | N/A | Register Data Recipient oAuth Client, Update Data Recipient Registration | Data Holder Brands should ignore unsupported authorisation scopes presented in the SSA for the creation and update of Client Registrations. |
| 486 | Register | Allow ADRs to specify scopes for a Software Statement Assertion (SSA) to support cross industry software products | Continue consultation through DP245 | N/A | N/A | N/A | N/A | This topic is complex and requires dedicated consultation. DP 245 has been raised to continue this work |
| 443 | Register | SSA definition: Deprecation of revocation_uri | Change Recommended | Get Software Statement Assertion (SSA) | This work contributes to the delivery of #444 | |||
| 498 | Register | New Register Authenticated APIs versions require multiple authorisation scopes #498 | In Progress | |||||
| 435 | Infosec | Nominated representative end user for non-individual consumers | ||||||
| 482 | Infosec | JWT signing non-normative examples use unsupported signing algorithm | Change Recommended | Non-breaking change | Non-normative example update |