ACCC & DSB | CDR Implementation Call Agenda & Meeting Notes | 29th of February 2024
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
- 5 min will be al lowed 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.
⭐ indicates change from last week.
| Type | Topic | Update |
|---|---|---|
| Standards | Version 1.29.1 | Published: 28th February 2024 Change log |
| Maintenance | Maintenance Iteration 18 commenced on the 7th February 2024 Last met for candidate consultation on the 21st of February 2024 |
All MI18 Agendas Please reach out to [email protected] for an invitation |
| DSB Newsletter | To subscribe to DSB Newsletter | Link here |
| DSB Newsletter ⭐ | 23rd of February 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 |
| Survey | If you are a CDR stakeholder, we want to hear about your experience finding and using CDR guidance. The ACCC has released a survey for businesses and individuals who are holder or receivers of CDR data, or who provide services to these parties. This includes, for example, data holders, accredited persons, CDR representatives and third-party service providers. Your response will help us assess the effectiveness of CDR guidance and identify potential areas for improvement. | The survey is available on the ACCC website and will remain open until 25 March 2024. |
| JS Holder SDK | Fixed 2 Github issues (https://github.com/ConsumerDataStandardsAustralia/js-holder-sdk/issues/16 and https://github.com/ConsumerDataStandardsAustralia/js-holder-sdk/issues/15) | Latest Github Repository: https://github.com/ConsumerDataStandardsAustralia/js-holder-sdk The relevant NPM package: https://www.npmjs.com/package/@cds-au/holder-sdk |
| NodeJS Mock DH (i.e. Test data server) | Fixed 2 Github issues (https://github.com/ConsumerDataStandardsAustralia/dsb-test-data/issues/5 and https://github.com/ConsumerDataStandardsAustralia/dsb-test-data/issues/6). | Latest Github Repository: https://github.com/ConsumerDataStandardsAustralia/dsb-test-data |
| Announcement | Upcoming changes |
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 | Standards | James |
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 |
|---|---|---|
| 2215 | When a consumer amends an authorisation in accordance with rule 4.22A, which is linked to a cdr_arrangement_id supplied by the data recipient as per the amending authorisation standards, data holders MUST display the details of each authorisation’s amendment on the consumer’s dashboard. Note: this requirement gives effect to rule 1.15(3)(h) (h) details of each amendment (if any) that has been made to the authorisation |
As per comment on Decision Proposal 334 There are existing requirements for ADR and DH dashboards, which include specifying details relating to the status of the consent or authorisation, such as indicating where it has been withdrawn or, for DHs, where SUI or DOMS adjustments have occurred, among other things. These are separate to the requirements for displaying the details of an amendment to a consent or authorisation on a dashboard. As per the rules, an ADR may invite a consumer to amend their existing consent(s) when the conditions set out in 4.12B(3) are met. This could include an amendment to datasets, durations, consent types, or other details requiring consent as outlined in rule 4.11. As per rule 4.11(1), collection consents - which correspond to DH authorisations - can be amended to reflect new datasets and/or a new duration as per rule 4.11(1)(a)(i) and 4.11(1)(b), respectively. If a consumer chooses to amend a collection consent, then rule 4.18C specifies that the ADR must notify the DH, and that the DH must then invite the consumer to amend the corresponding authorisation, which would pertain to the dataset(s) and duration. The authorisation amendment details to be displayed on the DH dashboard would follow accordingly – that is, the dashboard would need to indicate what changes have been made to the dataset and/or duration authorised for sharing. This does not override or displace the need to display other details on the dashboard. As noted in our previous response, the DSB expects that DHs will treat a request as a separate and standalone authorisation where the ADR has not supplied a cdr_arrangement_id. This is on the basis that without this information it will not be possible for the DH to link the request to an existing authorisation. The CX standards establish this link for authorisation amendments where the ADR supplies a cdr_arrangement_id. The standards in DP334 also facilitate this link for the purposes of displaying the corresponding authorisation amendment details on the dashboard, as is now required by the July 2023 rules. |
| 2267 | We are remediating an issue with product bundling and the team raised the below scenario and what the API response should be. API: Get Account Detail Scenario: one account is linked to more than 1 bundle Issue: the bundleName field is an optional string type in the standard. We are not sure for the above scenario, what the API response should be. A few options were discussed: Option 1: list all the bundle names as an array within the bundleName field (e.g. bundle1, bundle2, bundle3) Option 2: list each bundle name in a separate bundleName field (e.g. BundleName: bundle1 BundleName: bundle2 BundleName: bundle3 Appreciate if you can provide some guidance or some alternative option. Note this is not our current production scenario but more like for future proofing. |
If you think there may be a need to specify more than one bundle for an account in Account Detail, you could raise a change request in Standards Maintenance. Changing the single field to an array may be a simple option to meet this need. |
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.
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
|
 |
 |
 |