DSB Maintenance Iteration 16: Agenda (26 July 2023)

Meeting Details

• Date and time: 25/07/2023, 2:00pm – 4:00pm AEST
• Location: Microsoft Teams Click here to join the meeting
• Dial-in details:
  • Meeting ID: 477 437 866 801
  • Passcode: cJ5evt
  • Dial In Number: +61 2 9161 1229
  • Phone Conference ID: 856 119 656#
• Chair: Nils Berge, DSB
• MI Solution Architect: TBA
• Maintenance overview: Further information
• Maintenance issues: See here
• Maintenance project board: See here
• Maintenance Iteration Decision Proposal: Consultation on Decision Proposal 313 - Maintenance Iteration 16
• 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 contact@consumerdatastandards.gov.au 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
• Open Consultations
• Future Work Plan
• Outstanding actions
• Maintenance Iteration 16 candidates
• Any other business

Introductions

The purpose of this meeting is to:

• Review the backlog and discuss iteration candidates for Maintenance Iteration 16.

Release plan

• Current version of the standards is 1.25.0 published on 8 July 2023, refer to the release notes for details

Open consultations

The following consultations are open for community feedback: See issues open for feedback.

Future Work Plan

Review of July-September Quarter and new changes: See DSB Future Work Plan Project board.

Outstanding actions

NOTE: Where a 💡 appears it indicates the Action will be discussed later in the Agenda under Maintenance Iteration 16 Candidates.

InfoSec

• DSB to seek legal advice on the enforceability or the binding status of the standards versus an implementation guide with regard to Issue #522 OpenID Provider Configuration End Point parameter requirements.
  • Issue 522 was incorporated into Standards v1.25.0, under Security Endpoints
  • This action has been closed, but any further guidance will be provided when available.

Maintenance Iteration 16 Candidates

The DSB invites participants to propose items for consideration and prioritisation. You can do this by posting a comment on Decision Proposal 313 and attending the meeting to provide context and detail on your requirements in support of your request.

Domain	#	Issue	Proposal Status	Change Proposed	Standards Staging link
MI 16	599	Maintenance Iteration 16 Holistic Feedback
Banking	593	Interest paid at maturity guidance for applicationFrequency in BankingProductDepositRate
Banking	595	Use of additionalValue field in Product Eligibility Types
Common	376	Include FAX as CommonPhoneNumber purpose
Schema	469	Add isQueryParamUnsupported to MetaPaginated for schema validation

Other issues

Register:

• It was noted that issue #480 - 1.13.0 appears to have broken pseudonymity of Pairwise Identifiers had been suggested for consideration as a Decision Proposal.
  • DSB is reviewing the issue.

Banking:

• #229 – Service field in the Get Transaction Details API
  • The DSB is seeking feedback on whether this item should be prioritised for this iteration and/or made urgent. If an urgent change is requested, this would mean the DSB would need to seek approval from the Data Standards Chair to make the change as soon as possible. If not urgent, this will be incorporated with other changes at the end of iteration 16.
• #584 - Flag for account(s) not shared
  • Transferred to a Decision Proposal placeholder, see: Ability for ADR to request all accounts or identify missing accounts #130

Errors:

• #412 - Proposal to change specific error codes from MUSTs to SHOULDs
  • Although changes to errors have been raised in the MI16 holistic issue, issue #412 may require further discussion or participant support for prioritisation. Please review and add any comments.

Any other business

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