Skip to content

DSB Maintenance Iteration 22: Agenda (5 March 2025)

Jump to bottom
CDR API Stream edited this page Mar 4, 2025 · 2 revisions

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
  • 100 min
    • Candidate Discussion
  • 5 min
    • Any other business

Introductions

Today we're proposing discussion on four of the 16 confirmed candidates in MI22, (identified with a 💡 on the agenda) plus four issues with outstanding actions. The remaining issues won't be discussed unless attendees have something to contribute.

The order for discussion on each domain is:

  • CX
  • Security
  • Register
  • Energy
  • NFR
  • Banking

Release Plan

  • Current version is 1.33.0
  • Changes arising from the Chair's decision on DP 338 for Banking and DP 361 LCCD for Energy will be published in v1.34.0
  • Changes resulting from this MI will be published in version 1.35.0 or later

MI22 Candidates

Domain # Issue Comments
MI22 683 Maintenance Iteration 22 Holistic Feedback
CX 674 CX Guidelines - Updates stemming from 2024 Consent Review changes Refer to latest comments on the issue for updates.
CX 684 CX Guidelines - ADI or NBL to hold CDR data as a DH Refer to latest comments on the issue for updates.
Security 650 Weaken JARM Encryption Requirements for ADRs
ACTION Data Holders to raise any concerns with the removal of the 'MAY' statement.		 Outcome would be that Data Holders cannot require authorization response encryption.
Security / Register 682 Spec alignment - OpenID Provider Configuration and issuer value
Register 679 Update SSA specification
ACTION Data Holders to raise any concerns with making some SSA fields modifiable to support ADR updates.
Register 671 Remove deprecated Register scope detail Deprecated sector-specific scope detail will be removed.
Energy 680 Jurisdiction Code of ISO Proposing to close this issue, value not expected to be shared.
Energy 677 Energy transaction fields should be conditional Support for a non-breaking change noted.
Energy 662 Extend Get Generic Plan Detail to include a new field: tariffCode 💡 For discussion
NFR 660 Revise the Availability Requirements NFRs
ACTION Participants to review options and provide comment.		 💡 For discussion
Banking 656 A status of POSTED should indicate the final update for a transaction 💡 For discussion. See proposed change
Banking 553 Running balance available under transaction detail
ACTION Participants to provide views on wording that provides the clearest interpretation		 💡 For discussion
Banking 681 Retirement date for Get Transaction Detail V1 Proposed as 10th November 2025.
Banking 678 New Error Code for Product Data Requests where the Data Holder does not hold the required Product Reference Data Discussion and comments appear to show lack of support for this change. #561 - Update Register API to return separate PRD and status/outage endpoint deals with a similar scenario.
Banking 642 Update guidance for Banking account rate detail Change to guidance regarding provision of rate fields.
Banking TBA Additional credit card fields
ACTION SISS Data Systems to create a more specific CR to be considered as a candidate in this (or future) MI.
Banking TBA ACTION Frollo to summarise of key aspects from issues #283, #284, #567 and #569 in a new CR to be considered as a candidate in this (or future) MI. Further discussion with DSB may be required.

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

Getting Started

Meetings

Maintenance Iterations

CDR Implementation Call

Clone this wiki locally