ACCC & DSB | CDR Implementation Call Agenda & Meeting Notes | 24th of November 2022
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.20.0 Published on 3rd of November 2022 | Link to change log here |
| Maintenance | Maintenance Iteration 13 underway | Met 23rd of November 2022 and the agenda for the meet is here |
| Maintenance | Decision Proposal 272 - Maintenance Iteration 13 | Changes, meeting notes and updates for the iteration can be found here |
| TSY Newsletter | To subscribe to TSY Newsletter | Link here |
| DSB Newsletter | To subscribe to DSB Newsletter | Link here |
| TSY Newsletter | 3rd of November 2022 | View in browser here |
| DSB Newsletter | 18th of November 2022 | View in browser here |
| Consultation | Normative Standards Review (2021) | No Close Date Link to consultation |
| Consultation | Decision Proposal 229 - CDR Participant Representation | Placeholder: no close date Link to consultation |
| Noting Paper | Noting Paper 255 - Approach to Telco Sector Standards | Link to consultation |
| Noting Paper | Noting Paper 258 - Independent Information Security Review | Link to consultation |
| Consultation | Decision Proposal 267- CX Standards Telco Data Language Feedback closed: 15th of September 2022 Thanks to those who provided feedback on DP267 by 15th September. With the v5 rules out for consultation, the DSB will leave this issue open for comments while considering existing feedback and developing version 2 of DP267, which is expected to be published for consultation in October. |
Link to consultation |
| Consultation | Noting Paper 273 - Consent Review |
Feedback closes: 9th of December 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 |
| Survey | The Data Standards Body invite the CDR Community to provide feedback on the different Engineering Tools and platforms. | Link to survey |
| End of the Year | Last CDR Implementation Call for 2022 is 15th of December 2022 | Calendar invitations for 2022 will be updated early next week |
| 2023 | CDR Implementation Call will recommence on the 19th of January 2023 | Calendar invitations for 2023 will be issued late 2022 |
| Presentation | Next week the Data Standards Body will be presenting a new tool the team have put together | Updates via the DSB Newsletter channel will be sent out |
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 - Energy | Hemang Rathod |
| DSB | Technical Standards - Telecommunications | Brian Kirkpatrick |
| DSB | Engineering | Sumaya Hasan |
No planned presentation this week.
Questions will be received by the community via WebEx 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 |
|---|---|---|
| 1803 | I recently noticed that the brands/summary endpoint is now returning a different publicBaseUri for Origin and AGL; it seems to have changed on Nov 8th alongside those two retailers opening up. The new publicBaseUri's are: https://public.mydata.cdr.originenergy.com.au/ https://public.cdr.agl.com.au/ Also, note Origin has "mydata" in the path while AGL doesn't. Trying to use these publicBaseUri's for the energy/plans and energy/plans/[planID] endpoints for both Origin and AGL now returns a 404 message when trying to get energy plans. Has the formatting for publicBaseUri changed? Should I adjust the Get requests for the other endpoints to accommodate this new format? If so, what changes should I make? If I still use the old publicBaseUri for Origin and AGL before Nov 8th: https://cdr.energymadeeasy.gov.au/agl https://cdr.energymadeeasy.gov.au/origin I can retrieve the data from the unauthenticated endpoints without a problem, though now I am hesitant to think this old publicBaseUri is being maintained if it's been replaced. Can you provide any info to help clear this up, or perhaps I messed up my Uri path when using this new publicBaseUri? Also, if you suggest I reach out to ACCC, I could do; I do have a few other questions about this endpoint. |
What you have identified is a known issue with energy PRD. I will try to summarise it below along with the available tactical solutions. As you may already know, the base URIs for energy PRD are available via the Get data holder brand summary API - https://api.cdr.gov.au/cdr-register/v1/energy/data-holders/brands/summary (will need to provide appropriate headers, refer to standards for details). As per the rules, the designated data holder for energy PRD is AER and the Victorian agency (DELWP)(refer to the note in Subrule 2.3(1) of the rules). Consequently, all the PRD data and APIs are developed, published and maintained by AER and the information for energy base URIs provided by them. However, there is a known limitation for the base URI's for energy DH available via this API. Specifically, a data holder (DH) can only have one public base URI. The public base URI is used for the PRD endpoints (i.e. Get Generic Plans and Get Generic Plan Detail) as well as the DH's Status and Outage APIs. The base URIs for energy PRD would continue to point to AER/EME until the time an energy retailer is onboarded onto the register to go live with CDR consumer data sharing. This would result in the AER/EME's public base URI for that retailer being replaced by the retailers own (e.g. https://cdr.energymadeeasy.gov.au/agl/ being replaced by https://public.cdr.agl.com.au/). The rules team are working on amendments to resolve this by requiring a proxy or redirect to be implemented by the energy DHs. You can read about it more in the noting paper available here - https://github.com/ConsumerDataStandardsAustralia/standards/issues/248 As a tactical solution, the following two alternative sources have been defined while the rules are being amended: Option 1 (tactical): Energy PRD Base URI list published AER's website - https://www.aer.gov.au/consumers/energy-product-reference-data Option 2 (tactical): datasources.json file of the product comparator demo/tool |
| 1798 | Rule 4a.11 "For the purposes of paragraph 4a.10(4)(b), the data holder must, through its ordinary means of contacting each relevant account holder..." Other than a message on our JA management dashboard in IB, an email is also sent out to each relevant account holder. In the event that a valid email does not exist or if an email has not been provided, an email will not reach the account holder. Please could you advise if we would need to do anything further in this scenario? many thanks |
Where the co-approval option applies to a joint account and a joint account holder has authorised the disclosure of CDR data for the account, the data holder must seek the other account holders’ approval before disclosing data from the account. We have previously provided guidance in relation to a similar issue: https://cdr-support.zendesk.com/hc/en-us/articles/4596098813967. Generally we generally consider the data holder's obligation to be satisfied where the data holder has provided the notification, rather than where the notification has been received by the account holder. However, we expect data holders to take reasonable steps to ensure they maintain up to date contact details where they become aware that these details are no longer correct. |
| 1799 | Content within the v2 Joint Account Rules Support Portal article (https://cdr-support.zendesk.com/hc/en-us/articles/900004342366-v2-Joint-Account-Rules) confirms that: "Where a disclosure option is not already in place, clause 4.10 requires data holders to ask consumers to indicate a disclosure option as part of the authorisation flow (commonly referred to as the ‘in flow election’)" However, the CDR clause 4A.10 does not specifically state this requirement. Under v3, as the pre-approval disclosure option applies by default, do data holders have to ask consumers to indicate a disclosure option as part of the authorisation flow when a joint account does not have a selected option? |
We have published Joint Account Implementation Guidance which should address your question. At para 6.6 and 6.7 the guidance notes that: The pre-approval option will apply by default to new joint accounts that are established while a data holder is complying with the version 3 joint account provisions. While it is not a requirement in the rules, to promote transparency we encourage data holders to notify relevant consumers that the pre-approval option will apply by default to their joint account. This notification could also include an explanation of what this means, and instructions for how to change the disclosure option. Therefore, data holders do not have to ask consumers to indicate a disclosure option though we do consider it may be optimal to notify consumers of the option that applies by default. In addition, the DSB have also provided an example of an authorisation flow in the CX guidelines where a pre-approval option applies which may assist you. |
View a number of informative and useful links in the Consumer Data Standards Guide on Information Links.
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
|
 |
 |