DSB Maintenance Iteration 20: Meeting Notes (4 September 2024) - ConsumerDataStandardsAustralia/standards GitHub Wiki

Meeting Notes

Release Plan

  • Current version is v1.31.0.
  • The outcome of Maintenance Iteration 20 will be published in v1.32.0.

Maintenance Iteration 20 Candidates

Holistic Changes

CX

  • #646 Clarify selection of Trusted Adviser in the CX Guidelines
    • A visual example of the changes proposed in this comment have been provided in a Figma file to explain how they will be applied to the CX guidelines.
    • Unless further comments are made, the proposed changes will be finalised and published on the CX Guidelines website.
      • ACTION: Participants are invited to respond on the proposed changes.
      • No FDO applies.

InfoSec

Banking

Energy

Requirements Analysis

Common

Banking

  • #553 - Running balance available under transaction detail

    • The outcome of discussions on this issue has been summarised in this comment.
    • The outstanding actions listed below still apply in the context of participants providing further insight on an appropriate course of action to resolve the problems experienced by ADRs with regard to account balances.
      • OUTSTANDING ACTION: ADR to clarify requirements in options proposed in original post.
      • OUTSTANDING ACTION: ADRs to investigate whether information exists on differences between data holders that illustrate the problems with calculated balances.
      • OUTSTANDING ACTION: DHs to provide clarification on the difference between 'current' and 'available' balances.
      • OUTSTANDING ACTION: DHs to provide details on how balances are calculated.

  • #636 - Remove BankingTransactionDetail and incorporate extendedData into BankingTransaction

    • This issue has been referred to the NFR Consultative Group for consideration of an asynchronous pattern. Compliance issues have also been escalated to ACCC.
      • OUTSTANDING ACTION: DSB to following up with NPP. In progress
      • OUTSTANDING ACTION: Participants to provide feedback on summary of earlier discussions in comment

Energy

  • #651 Supporting HTTP Status 429 passthrough from Secondary Data Holder
  • Planning on the trial to test use of error 429 is underway, see comment, it is anticipated to commence in November.
  • The intention of the trial is to test use, and performance, of the 429 passthrough pattern:
    • used when a DH needs to respond to a request with a very large payload
    • when a request for a large payload is received the DH responds with a 429 message inserting the amount of time required to fulfil the request in seconds, e.g. 60 seconds
    • ADR acknowledges the retry time and follows up with a subsequent request at the specified time
    • within that timeframe DH prepares the data to respond when the retry request is received
    • this pattern is also being discussed in the NFR Consultative Group, a copy of the minutes from these meetings are available here: https://consumerdatastandards.gov.au/non-functional-requirements-consultative-group.

Security

Other business

  • #655 - Get Metrics V5 error metrics documentation

    • In reviewing Get Metrics data, it appeared some Data Holders are only providing the 500 error code which aligned with the previous versions of the Get Metrics endpoint. The structure was updated in v5 to require all 4xx and 5xx series error codes.
    • Many participants have implemented correctly, but noted the additionalProperties field had been a source of confusion.
    • DSB is proposing to clarify that all 4xx and 5xx error codes are required.
    • Potential candidate for MI21.

  • #657 - Addition of LVR in the enumerated values list for constraintType

    • In addition to new constraint types being considered in DP338 another constraint for Max LVR has been proposed and would likely be a minor change worth considering in MI21.

  • Abandonment metrics

    • Recent guidance updated by ACCC on Abandonments clarifies synthetic requests to PAR endpoint should not be included in statistics.
    • Mentioned to raise visibility of this change.

Next Steps

DSB will finalise the outcome of MI20 in the Decision Document for the Chair's approval and publish v1.32.0 as soon as possible.