DSB Maintenance Iteration Agenda (2 April 2025) - ConsumerDataStandardsAustralia/standards GitHub Wiki

Meeting Details

Housekeeping

Recording

Maintenance Iteration Calls are recorded for note taking purposes only. Recordings and transcripts are kept securely. Unless agreed in the call, no identifying material is provided without the participant's consent. Participants may email [email protected] with any questions or a request to have 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

The purpose of this meeting is to confirm the candidates that will be proposed in MI22. Actions and relevant CR's will be carried over to the next MI where necessary. The Decision Document with approved candidates will be drafted and sent to the Chair for approval.

The order of discussion is:

  • Breaking changes
  • Non-breaking changes
  • CR's with no changes
  • Completed CR's
  • CR's being carried over to next MI

Release Plan

  • Current version is 1.34 incorporating decision 338 for Banking and Decision 361 LCCD for Energy
  • An 1.34.1 patch release is planned to align the NBL Candidate Standards with the current banking changes
  • Changes resulting from this MI will be published in version 1.35.0 or later.

MI22 Candidates

Note: To focus on the detail of unresolved issues in standards maintenance consultation, the DSB assumes proposed solutions can be taken forward in a Decision Document for the Chair; unless there are opposing views raised before the final call of the iteration. The DSB encourages participants to post their views on issues as early as possible.

Domain # Issue Comments
Security 650 Weaken JARM Encryption Requirements for ADRs
OUTSTANDING ACTION Data Holders to raise any concerns with the removal of the 'MAY' statement.		 Breaking change
MI22 683 Maintenance Iteration 22 Holistic Feedback Non-breaking change
Security / Register 682 Spec alignment - OpenID Provider Configuration and issuer value
ACTION ACCC to advise anticipated implementation dates. 		Non-breaking change
Register 671 Remove deprecated Register scope detail Non-breaking change
Energy 677 Energy transaction fields should be conditional Non-breaking change
Banking 656 A status of POSTED should indicate the final update for a transaction
ACTION ANZ supportive of proposed solution and will comment on the issue.		 Non-breaking change
Banking 681 Retirement date for Get Transaction Detail V1 Non-breaking change
Energy 680 Jurisdiction Code of ISO No change
Energy 662 Extend Get Generic Plan Detail to include a new field: tariffCode No change
Banking 678 New Error Code for Product Data Requests where the Data Holder does not hold the required Product Reference Data No change
Banking 642 Update guidance for Banking account rate detail No change, guidance will be updated.
CX 674 CX Guidelines - Updates stemming from 2024 Consent Review changes Completed - Guidance updated
CX 684 CX Guidelines - ADI or NBL to hold CDR data as a DH Carry over to next MI
Register 679 Update SSA specification
ACTION Data Holders to raise any concerns with making some SSA fields modifiable to support ADR updates.		 Carry over to next MI
NFR 660 Revise the Availability Requirements NFRs
ACTION DSB will post more detail on Options 1 - 3 including the addition of a consumer notification channel for specific outage types.		 Carry over to next MI
Banking 687 Bank account balance calculation time is indeterminate
ACTION CBA anticipating to post comments on the issue.
ACTION DSB to provide an update on interpretation of rules for data holders to include time for balances.		 Carry over to next MI
Banking TBA Potential new issue relating to 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.		 Carry over to next MI as new issue, discuss comment.
Banking TBA Potential new issue relating to banking issues included, but deferred in Decision 338
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.		 Carry over to next MI as new issue

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
⚠️ **GitHub.com Fallback** ⚠️