ACCC & DSB | CDR Implementation Call Agenda & Meeting Notes | 6 February 2025 - ConsumerDataStandardsAustralia/standards GitHub Wiki
When: Weekly every Thursday at 3pm-4:30pm AEST
Location: Microsoft Teams
Meeting Details: Join on your computer, mobile app or room device Click here to join the meeting
Meeting ID: 446 019 435 001
Passcode: BU6uFg
Download Teams | Join on the web
Join with a video conferencing device
[email protected]
Video Conference ID: 133 133 341 4
Alternate VTC instructions
Or call in (audio only)
+61 2 9161 1229,,715805177# Australia, Sydney
Phone Conference ID: 715 805 177#
Find a local number | Reset PIN
Learn More | Meeting options
- 5 min will be allowed for participants to join the call.
- This call is jointly facilitated by the ACCC and the DSB, and we welcome observers from APRA, OAIC and the Treasury.
The Consumer Data Right Implementation Calls are recorded for note taking purposes. All recordings are kept securely, as are the transcripts which may be made from them. No identifying material shall be provided without the participant's consent. Participants may [email protected] should they have any further questions or wish to have any material redacted from the record.
By participating in the Consumer Data Right Implementation Call you agree to the Community Guidelines. These guidelines intend to provide a safe and constructive space for members to discuss implementation topics with other participants and members of the ACCC and Data Standards Body.
⭐ indicates change from last week.
| Type | Updated | Links |
|---|---|---|
| Standards | Version 1.33.0 | Published: 18th of December 2024 Change log |
| Maintenance ⭐ | Iteration 22 runs fortnightly through to April Decision Proposal 364 - Maintenance Iteration 22 |
Link to consultation |
| DSB Newsletter ⭐ | 31 January 2025 | View in browser here |
| Consultation ⭐ |
(Closing date extended) Decision Proposal 361 - Energy LCCD Phase 2 |
Feedback closes: 7 February 2025 Link to consultation |
| Consultation | Noting Paper 363 - Applicability of Authentication Frameworks | Link to consultation |
| Feedback | Request for Community Feedback on Issue 674 Note: this is pertinent for Accredited Data Recipients |
Standards Maintenance Issue 674 |
| Guidance | Guidance on introducing a new software product The ACCC has published a new article that provides guidance to ADRs considering whether to introduce a new software product to collect a CDR consumer’s CDR data. The article is available on the CDR Support Portal |
CDR Support Portal |
| Guidance ⭐ | Revised guidance The ACCC is continuing to update guidance to reflect changes made by the v7 CDR Rules package. Revised versions of the guidance (right) were published on the CDR website on Tuesday. |
- Joint account implementation guidance - Secondary users in the banking sector fact sheet - Secondary users in the energy sector fact sheet - Quick reference guide to finding documents in the CDR legislative framework |
| Tooling | JSON schema tools: updated to align with the latest version of CDS (1.33.0) | Repository |
| Tooling | Type Definition Library: Updated to align with the latest CDS (1.33.0) | npm Package |
| Standards | Transaction Security Ciphers FDO. Ensure your systems support only BCP195 recommended ciphers to meet compliance requirements by March 17 2025. | Future Dated Obligations page |
| Video | 135: CDS 1.33.0 Release Walkthrough and Changes - with Jarryd Judd (02/01/2025) | DSB YouTube Video |
| Video | 136: Decision Proposal 361 - narrated by Jarryd Judd (08/01/2025) | DSB YouTube Video |
| Video | 137: Noting Paper 363 - narrated by Neale Morison (28/01/2025) | DSB YouTube Video |
Provides a weekly update on the activities of each CDR stream and their work.
| Organisation | Stream | Member |
|---|---|---|
| DSB | Consumer Experience | Michael |
None this week.
Questions will be received by the community via Microsoft Teams chat before the questions are opened to the floor. Participants can submit questions outside of the CDR Implementation Call to the CDR Support Portal.
In regards to topics for questions, we ask the participants on the call to consider the Community Guidelines when posing questions to the subject matter experts.
| Ticket # | Question | Answer |
|---|---|---|
| 2444 |
OpenAPI Specification as a requirement in the standards CDR APIs often have OpenAPI specification (OAS) files, and the principles for consumer data standards point to the use of open standards wherever possible and to ensure high level developer experience, but is there any requirement in the standards that APIs MUST or SHOULD include an API description in an OpenAPI Specification file format? |
There is not currently a statement in the Standards that says APIs must/should include an OAS, as they focus primarily on the technical aspects of sharing, rather than copyright or further usage. For more details about the CDR, including Rules for certain participant types, you may also want to refer to - https://www.cdr.gov.au/for-providers - https://www.cdr.gov.au/for-providers/become-accredited-data-recipient |
Attendees are invited to raise topics related to the Consumer Data Right that would benefit from the DSB and ACCCs' consideration.
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 | |
| Advisory Committee | CX Guidelines | Calendar | |
| Support Portal | |||
| YouTube | |||
| GitHub | |||
| Newsletter |