ACCC & DSB | CDR Implementation Call Agenda & Meeting Notes | 16th of February 2023
When: Weekly every Thursday at 3pm-4:30pm AEDT
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
- Introductions
- Actions
- CDR Stream updates
- Presentation
- Q&A
- Any other business
- 5 min will be allowed for participants to join the call.
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, present and emerging, and recognise and celebrate the diversity of Aboriginal peoples and their ongoing cultures and connections to the lands and waters of Australia.
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.
| Type | Topic | Update |
|---|---|---|
| Standards | Version 1.22.0 published 23rd of December 2022 |
Version 1.22.0 Change Log Release video 1.22.0 |
| Maintenance | Iteration 14 has commenced! | Check out the agenda here Meeting Minute have been published in link above. |
| TSY Newsletter | To subscribe to TSY Newsletter | Link here |
| DSB Newsletter | To subscribe to DSB Newsletter | Link here |
| TSY Newsletter | 13th of February 2023 | View in browser here |
| DSB Newsletter | 3rd of February 2023 | View in browser here |
| Consultation | Decision Proposal 229 - CDR Participant Representation | Placeholder: no close date Link to consultation |
| Consultation | Decision Proposal 267- CX Standards Telco Data Language |
Feedback extended with an end date to be determined pending the making of the telco rules. Link to consultation |
| Consultation | Decision Proposal 275 - Holistic Feedback on Telco Standards | No Close Date Link to consultation |
| Consultation | Noting Paper 276 - Proposed v5 Rules & Standards Impacts | No Close Date Link to consultation |
| Design Paper | Design Paper: Consumer Data Right Rules and Standards for the Non-Bank Lending Sector |
Feedback closed Link to consultation |
| Consultation | Noting Paper 279 - Accessibility Improvement Plan | No Close Date Link to consultation |
| Consultation | Decision Proposal 287 - Energy C&I Consumers |
Feedback closes: 17th of February 2023 Link to consultation |
| Workshop | 7th of March 2023 Action Initiation Workshop 01 |
Registration for Workshop |
| Tools | Java Artefacts 1.22.0 | Latest release |
Provides a weekly update on the activities of each of the CDR streams and their stream of work
| Organisation | Stream | Member |
|---|---|---|
| ACCC | CDR Register | Emma Harvey |
| ACCC | CTS | Andrea Gibney |
| DSB | CX Standards | Michael Palmyre |
| DSB | Technical Standards - Banking & Infosec | Mark Verstege |
| DSB | Technical Standards - Telecommunications | Brian Kirkpatrick |
| DSB | Technical Standards - Register | James Bligh |
| DSB | Engineering | Sumaya Hasan |
Topic: DSB Quarterly Plan
Presenter: James Bligh
Link: https://github.com/ConsumerDataStandardsAustralia/future-plan
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 |
|---|---|---|
| 1858 | We noticed there are couple of Software Products with missing mandatory field (LogoURI) when DH call the Get DataRecipient API. https://cdr-support.zendesk.com/hc/en-us/articles/900004767863-July2020-10-Register-APIs-API-Response-Validation Questions: 1. In the above scenario, if DH notices a Software Product A with missing mandatory properties (e.g., LogoURI) shall we skip that Software Product A and continue entering/updating the remaining Software Product Names in our Metadata? 2. Suppose if this Software Product A updates the mandatory properties in the CDR registry and a user at that moment request for consent authorisation. As a DH we may not have updated our metadata considering cache update period of 2-3 mins and we may reject this consent authorisation request. Is this the right response as a DH? Appreciate your earliest response |
If I understand it correctly, I think you may be looking for a details such as below - Under the Participant Statuses > Data Holder Responsibilities section it states - If Data Holders do not receive a status for a Data Recipient or Data Recipient Software Product, or receives a status that is not recognised, Data Holders SHOULD ignore the value and use the previous status value retrieved from the CDR Register. Data Holders SHOULD continue to use the previous status value until a valid value is returned by the CDR Register or the ACCC informs the Data Holder using an alternative mechanism. There is no upper bound for how long previous status values should remain trusted. If you therefore receive a schema- non-compliant response, you should continue to provide services based on a previously cached version. The values in your Status cache may provide three different outcomes - If your cached version indicated the Software Product was last known to be ACTIVE, data could be shared. If your cached version indicated the Software Product was not last known to be ACTIVE, data must not be shared. If you did not have a cached version for a particular software product and the CDR Register response was not schema compliant at the time of request, data must not be shared as the status could not be determined. If the Register APIs were providing invalid responses (and I don't believe they are currently), it may be helpful to make the ACCC aware of that fact so they could rectify the issue as soon as possible. |
| 1855 | when can we expect rules v 5? | Unfortunately we do not have an exact timeframe for when the v5 rules amendments will be released, but they are currently being progressed by Treasury. In the meantime, you can find the most recent exposure draft rules here: https://treasury.gov.au/consultation/c2022-315575 |
View a number of informative and useful links in the Consumer Data Standards Guide on Information Links.
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
|
 |
 |
 |