DSB Maintenance Iteration 16: Minutes (23 August 2023)

Meeting Minutes

As at COB on 23 August 2023

Release Plan

Decision Proposal 322 - Update Get Metrics Endpoint Schedule has been staged in v1.26.0. It will be published in the coming days.

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 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
  • Following a DSB meeting with AP+ (formerly NPP) a holistic review of schemas is suggested to consider all changes made since the CDR Banking APIs were developed. The consensus among attendees was to move this issue into a Decision Proposal to accommodate a broader approach.
  • DSB to create a Decision Proposal at which time this issue will be closed ⚡
  • NOTE a place holder for this Decision Proposal has been created, refer to #324
• #593 – Interest paid at maturity guidance for applicationFrequency in BankingProductDepositRate
  • Support for this breaking change to be incorporated with other future changes. Participant indicated they would add a comment in support of this ⚡
• #595 – Use of additionalValue field in Product Eligibility Types
  • Support for this breaking change to be incorporated with other future changes.
• #596 - Add Swift BIC Code to Get Payees and Get Scheduled Payments API
  • Issue will be closed.

Energy:

• see NFRs

Common:

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

Schema:

• #469 – Add isQueryParamUnsupported to MetaPaginated for schema validation
  • Documentation error to be treated as a non-breaking change.

Errors:

• #412 – Proposal to change specific error codes from MUSTs to SHOULDs
  • Counter comments from both Data Holders and Accredited Data Recipients to be posted on the issue. Concerns relaxing the rigor around supplying specific error codes could be abused and doesn't assist with troubleshooting errors when they arise.
  • Advice from the regulator required to determine how the issue could be interpreted from a compliance and enforcement perspective. ACCC to advise ⚡

NFRs:

• #605 - Metrics: Performance threshold including SDH
  • Consensus on the clarification to exclude the Secondary Data holder from performance metrics calculations should be treated as a Non-breaking Change
  • Changes can be made based on this advice and will be published along with all other MI16 changes
• #602 - NFR: Secondary Data Holder unable to determine Customer Present
  • Issue will be discussed in upcoming NFR workshops ⚡
• #603 - NFR: Policing of Data Recipient Low Velocity Data Sets Thresholds,
  • Issue will be discussed in upcoming NFR workshops ⚡
• #604 - NFR: Arrangements with large numbers (500+) of accounts
  • Issue will be discussed in upcoming NFR workshops ⚡

Documentation:

• See #599 – Maintenance Iteration 16 Holistic Feedback for minor documentation updates and other amendments.

Other business

NFR workshops

• First workshop in Sydney was very productive, there are spaces available in Melbourne. Participants are encouraged to attend.

Retirement of Register APIs

• Specific details regarding the Register API versions that will be retired can be found at https://consumerdataright.atlassian.net/wiki/spaces/DP/pages/30081043/Delivery+Dates#Definitions and https://github.com/ConsumerDataStandardsAustralia/standards-maintenance/issues/544#issuecomment-1331610730

• the ACCC will post a request on the holistic thread for the xv header to be made mandatory ⚡

v1.26.0 Staged

• DSB encourages participants to review the staged version of the standards before they're published. See https://consumerdatastandardsaustralia.github.io/standards-staging/#introduction

Next Steps

• DSB will stage the changes and present solutions for each of the candidates in the final meeting of the iteration on 6 September.