Skip to content

DSB Maintenance Iteration 22: Agenda (5 February 2025)

CDR API Stream edited this page Feb 5, 2025 · 1 revision

Meeting Details

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.

Time management of Maintenance Iteration Meetings (if required)

  • After the first meeting to groom the backlog, if the number of candidates and the anticipated complexity of them indicates timeboxing discussions is required, these time management practices will be put in place:
    • 5 minute delay will be removed. Meetings will commence at 2:00PM AEST.
    • Each discussion will be timed, if the discussion is not concluded within the allotted time, the discussion will be taken offline.
      • Allotted time will be determined based on the number of candidates in the iteration.
      • If the discussion on all issues has concluded and time remains, any issues scheduled for offline discussion can be revisited.
    • Start times will be estimated for each Domain and advertised when the Agenda is published.

Agenda

  • 15 min
    • Introductions
    • Release Plan
    • Update
  • 100 min
    • Candidate Selection
  • 5 min
    • Any other business

Introductions

The purpose of this meeting is to identify candidates for MI22.

Release Plan

  • Current version is 1.33.0
  • Changes resulting from this MI will be published in version 1.34.0 or later

Updates

  • Information Security and Non Functional Requirement Consultative Groups
  • Outages and drop offs
  • BCP195 FDO

Candidate selection

Domain # Issue Comments
MI22 683 Maintenance Iteration 22 Holistic Feedback Non-breaking
CX 674 CX Guidelines - Updates stemming from 2024 Consent Review changes
CX 684 CX Guidelines - ADI or NBL to hold CDR data as a DH
Security 650 Weaken JARM Encryption Requirements for ADRs
Waiting on information about data holders who require encryption on JARM responses.
Banking 656 A status of POSTED should indicate the final update for a transaction
ACTION Data Holders to investigate and provide a response if the proposed changes would have any implementation considerations adopting the proposal.
ACTION Data Holders to investigate and provide a response whether the lifecycle of transactions results in changes to posted transactions and what occurs in reversal scenarios - does this result in a change to the same transaction, or creation of a new transaction?
Banking 553 Running balance available under transaction detail
NFR 660 Revise the Availability Requirements NFRs

NOTE: Issues Addition of a DH-side endpoint for querying the status of a consent establishment flow #628 and Inconsistent JARM error responses #649 have been moved to the backlog as they will be addressed through work occurring in the Information Security Consultative Group.

Any other business

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

Useful Links

View a number of informative and useful links in the Consumer Data Standards Guide on Information Links.

Data Standards Body Consumer Data Right Digital ID Contact & Media
Chair Standards Accreditation Standards Website
News Maintenance Iteration AGDIS Standards Email
Advisory Committee CX Guidelines Calendar
Support Portal LinkedIn
YouTube
GitHub
Newsletter
Clone this wiki locally