ACCC & DSB | CDR Implementation Call Agenda & Meeting Notes | 25th of July 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 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.
⭐ indicates change from last week.
| Type | Updated | Links |
|---|---|---|
| Standards | Version 1.31.0 | Published: 3rd of July 2024 Change log |
| Maintenance ⭐ | Iteration 20 Commenced 10th of July 2024 |
Sign-up and Register Data Standards Body Events |
| Maintenance ⭐ | Iteration 20 Schedule: 7/08/2024 Consultation and new issue checkpoint 21/08/2024 Proposal Checkpoint 4/09/2024 Approvals and Documentation |
MI20 Agendas and Minutes |
| DSB Newsletter | To subscribe to DSB Newsletter | Link here |
| DSB Newsletter ⭐ | 19th of July 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 351 - LCCD Risk workshop summary | No feedback sought Link to Noting Paper |
| Guidance ⭐ | CDR representative fact sheet – revised to include new section on how CDR representatives describe themselves to consumers, to assist CDR representatives avoid making false or misleading claims. | CDR.gov.au - CDR representative fact sheet |
| Guidance ⭐ | CDR business consumers fact sheet – minor revision to clarify that an individual without an ABN cannot be treated as a CDR business consumer. | CDR.gov.au - CDR business consumers fact sheet |
| DSB Calendar ⭐ | Added Future Dated Obligations (from the Standards) to the DSB Calendar. Note: still working through styling and interactions. |
DSB Calendar |
| Engineering ⭐ | JSON Schema Tools: Latest release includes updates that align the tool to CDS 1.31.0 | GitHub Repo |
Provides a weekly update on the activities of each CDR stream and their work.
| Organisation | Stream | Member |
|---|---|---|
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 |
|---|---|---|
| 2399 | The postingDateTime field in the standards for a Banking Transaction is defined as a DateTimeString. The standards further state that this field should be interpreted as follows - “As specified in [RFC3339] times MUST be offset relative to UTC”. We have identified at least one DH who doesn't store a time component for this field in their core banking system. As a result, they are doing the following 1. Taking the date from their core system 2. Appending a static "00:00:00" to the end 3. Not including any timezone/offset information For example - they are passing values such as "2024-07-22 00:00:00". Since there is no offset, we are interpreting this as a UTC value, and as such, when converting it to AEST it's being treated as "2024-07-22 10:00:00". We believe that this DH has incorrectly implemented the standards and require your guidance. |
If the dates are intended to be interpreted as at AEST, then they would be expected to be specified with an offset to that effect, such as: 2024-07-22T00:00:00+10:00 The Z suffix may also be used but the time must be specified as at that offset. i.e., 2024-07-21T14:00:00Z would be the same time as above. Let me know if those examples make sense. If you think the examples in the Standards could be improved let me know or add a comment on the maintenance holistic thread. |
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.
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |