DSB Maintenance Iteration 16: Minutes (6 September 2023)

Meeting Minutes

Release Plan

• Current version of the standards is 1.26.0.
• Publishing v 1.27.0, anticipated to arise from DP 313 for MI 16, will be delayed until later in September to align with ACCCs planned deprecation of a range of Register APIs where x-v headers will become mandatory.

Maintenance Iteration 16 Candidates

The issues listed below have been consulted on in this iteration or proposed for further review by DSB. The DSB encourages participants to review these and post comments for consideration in developing solution proposals.

NOTE: New actions from this call, plus outstanding actions, are marked with ⚡

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.
  • Under DSB review, not discussed.

Banking:

• #229 – Service field in the Get Transaction Details API
  • a place holder for the Decision Proposal has been raised, refer to #324
• #593 – Interest paid at maturity guidance for applicationFrequency in BankingProductDepositRate
  • Support for this breaking change to be incorporated with future changes.
• #595 – Use of additionalValue field in Product Eligibility Types
  • Support for this breaking change to be incorporated with future changes.
• #596 - Add Swift BIC Code to Get Payees and Get Scheduled Payments API
  • Issue closed.

Energy:

• see NFRs
• #611 - Clarification of Energy PRD Obligations
  • Agreement to include a statement clarifying Energy DH obligations in the standards. Careful consideration of the wording is required to ensure the statement aligns with the rules.

Common:

• #376 - Include FAX as CommonPhoneNumber purpose
  • Removed from MI16.

Schema:

• #469 – Add isQueryParamUnsupported to MetaPaginated for schema validation
  • Non-breaking change.

Errors:

• #412 – Proposal to change specific error codes from MUSTs to SHOULDs
  • Waiting on advice from ACCC⚡

NFRs:

• #605 - Metrics: Performance threshold including SDH
  • Non-breaking Change
• #602 - NFR: Secondary Data Holder unable to determine Customer Present
  • Issue will be moved to the backlog for the NFR Working Group, see Other business
• #603 - NFR: Policing of Data Recipient Low Velocity Data Sets Thresholds,
  • Issue will be moved to the backlog for the NFR Working Group, see Other business
• #604 - NFR: Arrangements with large numbers (500+) of accounts
  • Issue will be moved to the backlog for the NFR Working Group, see Other business

Documentation:

• See #599 – Maintenance Iteration 16 Holistic Feedback for minor documentation updates and other amendments.
  • A proposal for each comment was discussed with no objections.

Other business

NFR workshops

• A clear outcome of the NFR Workshops was agreement to establish an NFR Working Group to advise the DSB on requirements with reporting responsibility to DSAC.

Next Steps

• DSB will continue staging changes for review and draft the Decision Proposal for the Chair's approval.