Meeting Details

• Date and time: 29/05/2024, 2:00pm – 4:00pm AEST
• Location: Microsoft Teams Click here to join the meeting
• Dial-in details:
  • Meeting ID: 465 176 022 288
  • Passcode: gWgzgd
  • Dial In Number: +61 2 6188 4842
  • Phone Conference ID: 193 570 554#
• Chair: Elizabeth Arnold, DSB
• MI Solution Architect: Hemang Rathod, DSB
• Maintenance overview: Further information
• Maintenance issues: See here
• Maintenance project board: See here
• Maintenance Iteration Decision Proposal: Consultation on Decision Proposal 347 - Maintenance Iteration 19
• Maintenance Iteration meeting Plan and Minutes: See here

Housekeeping

Recording

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.

Acknowledgement of Country

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 and present and recognise and celebrate the diversity of Aboriginal peoples and their ongoing cultures and connections to the lands and waters of Australia.

Agenda

• Introductions
• Release Plan
• Requirements Analysis
• Maintenance Iteration 19 Candidates
• Any other business

Introductions

The purpose of this meeting is to confirm requirements for Maintenance Iteration 19 candidates are mature enough for a proposal to be made. If requirements are insufficient, the candidate will be moved to the next iteration.

Release Plan

• The outcome of Maintenance Iteration 19 will likely be published in v1.31.0.

Requirements analysis

Domain	#	Issue	Comments
Common	610	Addition of an (18 or over) Age Verification Flag	See this comment for an update
Security	628	Addition of a DH-side endpoint for querying the status of a consent establishment flow	DSB to share findings
Banking	636	Remove BankingTransactionDetail and incorporate extendedData into BankingTransaction ACTION: Josh to post data shared in the chat on the thread for broader visibility. DONE see this comment ACTION: Dima to request Australian Payments investigate to provide an opinion.	In progress

Maintenance Iteration 19 Candidates

Domain	#	Issue	Change Type
MI19	638	Maintenance Iteration 19 Holistic Feedback	Candidate
CX	633	Collection Consents - Authorisation Amendment ACTION: Data Holders are required to indicate a preference for Option 1, 2 or 3 and confirm it is a non-breaking change.	To be determined
Energy	640	Retirement date for Get Generic Plan Detail v2 and Get Energy Account Detail v3 ACTION: Energy retailers requested to comment on the thread to determine appropriate retirement date	Candidate
Documentation	362	Security Profile: Request Object - Inconsistency in example for sharing_duration and cdr_arrangement_id ACTION: Request for participants to comment on the ticket to clarify requirements.	Candidate
Documentation	415	Disambiguation of the claims for a response from the introspection endpoint ACTION: DSB to propose a way to address this issue.	Candidate
Documentation	573	Clarification on handling of standard claims in request object ACTION: Request for participants to comment on the ticket as to whether more guidance is required or a standards change is necessary.	Candidate
Documentation	615	Plan Obligation Milestones for 2025 NOTE: This issue was discussed in Meeting #2 but missed in Meeting #3, given it's a documentation issue we'd like to continue discussion on this item.	Candidate

Any other business

Participants are invited to raise topics related to the Consumer Data Standards that would benefit from the groups' consideration.