DSB Maintenance Iteration 16: Agenda (9 August 2023)

Meeting Details

• Date and time: 09/08/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: Brian Kirkpatrick, DSB
• 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 [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
• Open Consultations
• Future Work Plan
• Maintenance Iteration 16 candidates
• New Issues
• Any other business

Introductions

The purpose of this meeting is to:

• Consult on iteration candidates for Maintenance Iteration 16 and check for new issues that may affect the iteration.

Release plan

• Current version of the standards is 1.25.0 published on 8 July 2023, refer to the release notes for details.
• Decision Proposal 322 - Update Get Metrics Endpoint Schedule has been approved as an urgent change and is therefore currently undergoing a truncated consultation period. It is likely it will be released as v1.26.0.

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.

Maintenance Iteration 16 Candidates

The following issues have been identified as candidates. Note: Actions are indicated with a ⚡ and will be included in the discussion for the relevant issue.

Domain	#	Issue	Status
MI 16	599	Maintenance Iteration 16 Holistic Feedback
Banking	229	Service field in the Get Transaction Details API	DSB to review
Banking	593	Interest paid at maturity guidance for applicationFrequency in BankingProductDepositRate	Breaking change: Update to description, consider with DP306
Banking	595	Use of additionalValue field in Product Eligibility Types	Non-breaking change: Update descriptions. Change staged
Common	376	Include FAX as CommonPhoneNumber purpose	Requires participant feedback. If none received, this will be removed from this MI ⚡
Schema	469	Add isQueryParamUnsupported to MetaPaginated for schema validation
Errors	412	Proposal to change specific error codes from MUSTs to SHOULDs	DSB to review

New Issues

• issue 596 and use of DOMESTIC type for Payees that have details in an international format.
  • Participant was requested to review the INTERNATIONAL schema as an alternative. ⚡
• 'Customer Present' and Performance Requirements of secondary data holders
  • For customer present calls the x-fapi-customer-ip-address is not passed to the secondary data holder however the response time for those calls includes the secondary data holder which is consistently above 1.5 seconds.
  • It was not DSBs intention to include the secondary data holder response times in Get Metrics for primary data holders.
  • Change Requests #602 and #605 have been raised and will be considered during this MI, raised with AEMO, and added to the agenda for NFR Workshops scheduled in August. ⚡
• Expected behaviour for calls with large numbers of accounts
  • e.g. 1,000, particularly C&I customers
  • DSB did not anticipate large numbers in these calls
  • Potential solution is to change the pagination limit for the API
  • Change Request #604 has been raised and will be considered for this MI, raised with AEMO, and added to the agenda for NFR Workshops scheduled in August. ⚡
• Are primary data holders are expected to enforce thresholds for the secondary data holder?
  • The secondary data holders have no visibility of consent, start time of session etc so are unable to manage this.
  • Change request #603 has been raised and AEMO has been asked to investigate and advise on whether they can enforce the NFRs. ⚡

Any other business

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