Meeting Minutes

Release Plan

Standards version for this iteration is TBC, considering the Data Standards Chair approved Decision Proposal 322 - Update Get Metrics Endpoint Schedule to be considered as an urgent change. The urgent change release may include documentation and other minor changes not requiring a decision of the Chair.

Maintenance Iteration 16 Candidates

The issues listed below have been proposed for consultation in this iteration or 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 ⚡

CX:

• None proposed

Security:

• None proposed

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 will review the issue, no comments as yet.

Banking:

• #229 – Service field in the Get Transaction Details API
  • Confirmed as a candidate for MI16 and expected to be a breaking change
  • DSB to review and propose a solution ⚡
• #593 – Interest paid at maturity guidance for applicationFrequency in BankingProductDepositRate
  • DSB to update thread with discussion outcome and consider circumstances where a new field, and therefore Change Request, is required ⚡
• #595 – Use of additionalValue field in Product Eligibility Types
  • Accommodating this change will require a new endpoint version which could be incorporated with future changes, potentially arising from DP 306.
• #596 - Add Swift BIC Code to Get Payees and Get Scheduled Payments API
  • Clarification provided on the use of international structure for domestic payments. Issue appears resolved and may be closed if no further comments.

Energy:

• None proposed

Common:

• #376 - Include FAX as CommonPhoneNumber purpose
  • Suggestion that this issue be removed item from MI16.

Schema:

• #469 – Add isQueryParamUnsupported to MetaPaginated for schema validation
  • Confirmed as a candidate for MI16 and will be treated as a non-breaking change.

Errors:

• #412 – Proposal to change specific error codes from MUSTs to SHOULDs
  • Participants requested to comment on the issue to assist DSB in determining the nature of change ⚡

NFRs:

• #605 - Metrics: Performance threshold including SDH
  • Confirmed as a candidate for MI16. Non/Breaking Change TBC ⚡
• #602 - NFR: Secondary Data Holder unable to determine Customer Present
  • Issue will be discussed in upcoming NFR workshops ⚡
  • AEMO to update CDR page with business rules on when they treat CDR API requests as customer present.
• #603 - NFR: Policing of Data Recipient Low Velocity Data Sets Thresholds
  • AEMO confirmed a change to control thresholds, if required, could be implemented
  • Issue will be discussed in upcoming NFR workshops ⚡
• #604 - NFR: Arrangements with large numbers (500+) of accounts
  • DSB to consider short term relief by reducing maximum number of accounts in a request ⚡
  • Issue will be discussed in upcoming NFR workshops ⚡

Operational:

• None proposed

Documentation:

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

Other business

None

Next Steps

• DSB will monitor candidates for comments with the view to proposing a solution for discussion in the next meeting.