Skip to content

ACCC & DSB | CDR Implementation Call Agenda & Meeting Notes | 11th of April 2024

CDR-Engagement-Stream edited this page Apr 11, 2024 · 9 revisions

CDR Implementation Call Banner

Agenda & Meeting Notes

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
teams@vc.treasury.gov.au
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


Agenda

  1. Introductions
  2. House Keeping
  3. Updates
  4. CDR Stream updates
  5. Presentation
  6. Q&A
  7. Any other business

Introductions

1ImpCallHeaders

  • 5 min will be al lowed for participants to join the call.

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, 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.

House Keeping

2ImpCallHeaders

Recording

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 contact@consumerdatastandards.gov.au should they have any further questions or wish to have any material redacted from the record.

Community Guidelines

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.

Updates

3ImpCallHeaders ⭐ indicates change from last week.

Type Topic Update
Standards Version 1.29.1 Published: 28th of February 2024
Change log
Standards Version 1.30.0 is being staged for release Standards Staging
Maintenance ⭐ Maintenance Iteration 18 complete MI 18 Agendas
Maintenance ⭐ Iteration 19 to commence on the 17th of April 2024 Invitations to all current members have been sent out to our new sign-up platform; Trumba. You can sign-up here
DSB Newsletter To subscribe to DSB Newsletter Link here
DSB Newsletter ⭐ 5th of April 2024 View in browser here
Consultation Decision Proposal 229 - CDR Participant Representation Placeholder: no close date
Link to consultation
Consultation Noting Paper 279 - Accessibility Improvement Plan No Close Date
Link to consultation
Consultation Noting Paper 323 - NFR Workshops Link to consultation
Consultation Noting Paper 330 - UNSW Reports Link to consultation
Consultation Decision Proposal 340 - Maintenance Iteration 18 Link to consultation
Consultation Noting Paper 342 - Information Security Working Group Link to consultation
Consultation Noting Paper 345 - Data Standards Body Capability, Consultation Processes and Operating Mode Link to consultation
Energy Guide AEMO has developed a guide to understanding AEMO Standing, Usage and DER data so that ADRs might be better informed how to interpret the data they receive, to understand its complexities and its limitations. Guide to understanding AEMO data for ADRs
Events Data Standards Body new calendar
Self manage the Maintenance Iterations, CDR Implementation Calls, Workshops and consultations from here.
Data Standards Body Calendar
Consumer Experience New and updated wireframe flows, open source design assets, annotations and CX Checklist for Consent Management (Data holder): Authorisations to reflect July 2023 rules amendments, Decision 334, Change Request 557 and a UI uplift. Consumer Experience Guidelines
ANZAC Day The CDR Implementation Call for the 25th of April 2024 will be cancelled. Cancellations sent.

CDR Stream Updates

4ImpCallHeaders Provides a weekly update on the activities of each CDR stream and their work.

Organisation Stream Member
ACCC Register and Accreditation Application Platform, Conformance Test Suite & Participant Tooling Christian
DSB Consumer Experience Michael
DSB Energy Hemang
DSB Information Security Mark

Presentation

5ImpCallHeaders None this week.

Q&A

6ImpCallHeaders Questions on Notice

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.

Answer provided

Ticket # Question Answer
2189 i refer to the figma diagram from the DP334 .
From the diagram attached in my screenshot, the angular icons seem to suggest that the consent history would progress further on to another page (assuming it's to list out previous details screen).
Can i seek confirmation that there are no such requirement that would enforce the DH to provide the full details to that level? i.e. to meet CDR v5 dashboard rule in 1.15(3)(h), and the DP334 requirement, if we are to just display the amended changes (similar to those one liner that you see on the suggested screen), would that be enough to meet the rules and DP?
We apologise for the delayed response. We have been working closely with other CDR agencies in drafting guidance relating to the requirement for data holders to display details of amendments on the dashboard. This guidance has now been finalised and is published on the CX Guidelines website at Consent Management (Data holder): Authorisations, Amended Authorisations.
We hope this guidance addresses your questions. If you have any further questions, please don't hesitate to contact us via the support portal.
2190 Part 1 Can i find out if those text displayed (per my attached image). Is it a requirement to always have those? or can we just expose the past historical shared detail pages to customers instead? We apologise for the delayed response. As noted in your other ticket, we've just published guidance on the CX Guidelines website at Consent Management (Data holder): Authorisations, Amended Authorisations, which should help address your questions.
2190 Part 2 the text I've highlighted in green ("Duration extended, data changed, accounts changed." and "Duration extended" and "Data Sharing started") are not part of any mandatory information that we MUST provide right?
Seems like those text that i've highlighted are more of "change attributes" would you agree?
The rules and standards require that data holders display details of each amendment to a sharing arrangement on their consumer dashboard. However, the rules and standards don't prescribe how data holders achieve this. The guidance provided on Consent Management (Data holder): Authorisations, Amended Authorisations were developed in collaboration with other CDR agencies and are an example of a compliant implementation. The level of detail displayed in these CX Guidelines reflects these views.
Unfortunately, the DSB can't offer personalised or specific compliance advice to CDR participants. We recommend carefully reviewing our wireframes and annotations, and conducting your own due diligence to assess whether any potential variances would result in non-compliance.
2270 Pl let me know when will the CX guidelines be updated.
The existing CX shows a screen capturing consent history including amendments and we wanted to confirm if it’s a mandatory screen.
When a customer amends a consent, our solution update the customer consent dashboard to show the revised duration, scopes, etc.
However, based on the CDR CX design, is there an expectation to show the history of consent including amendments on a screen?
We apologise for the delayed response. We have been working closely with other CDR agencies in drafting guidance relating to the requirement for data holders to display details of amendments on the dashboard. This guidance has now been finalised and is published on the CX Guidelines website at Consent Management (Data holder): Authorisations, Amended Authorisations.
We hope this guidance addresses your questions. If you have any further questions, please don't hesitate to contact us via the support portal.

Any Other Business

7ImpCallHeaders Attendees are invited to raise topics related to the Consumer Data Right that would benefit from the DSB and ACCCs' consideration.

Useful Links

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

Check out our guides, browse through our FAQs, and post your own questions for Support. The official Consumer Data Standards website This repository contains the binding API Standards and Information Security profile created in response to the Consumer Data Right legislation and the subsequent regulatory rules. A demonstration of Product Reference data from the Banking Sector.
Consumber Data Standards on GitHub Data Standards Body video channel on YouTube Helping organisations provide consumers with intuitive, informed, and trustworthy data sharing experiences. A Postman collection with a set of unit tests. It can be used as a development testing tool for Data Holders developing a DSB compliant API.
Follow Data Standards Body on LinkedIn for updates and announcements Digital Resources Repository on DSB's GitHub website The glossary of CDR CX terminology Data Holder server reference implementation and associated tools.
  A repository of DSB Newsletters/Blog posts since 2019 This repository is the staging repository for the Consumer Data Standards. Java Artefacts Data Holder server reference implementation
  This glossary lists terms and their definitions in the context of the Consumer Data Right and Consumer Data Standards. This repository is used to contain discussions and contributions from the community of participants and other interested parties in the Australian Consumer Data Right regime. Java Artefacts Data Holder server reference implementation
Clone this wiki locally