ACCC & DSB | CDR Implementation Call Agenda & Meeting Notes | 19th of August 2021
When: Weekly every Thursday at 3pm-4.30pm AEST
Location: WebEx, quick dial +61-2-9338-2221,,1650705270##
Meeting Details:
Desktop or Mobile Devices
https://treasuryau.webex.com/treasuryau/j.php?MTID=m9614a7c6166155d3d950a8999e437f9f
Once connected to your meeting remember to start your audio and video
Please mute when you are not speaking.
Video Conferencing (VC) Rooms
Use the remote control or touch panel and dial the number indicated below:
External VC Room: 1650705270@webex.com
Phones - AUDIO ONLY
- Primary Australia: +61-2-9338-2221
- Quick Dial: +61-2-9338-2221,,1650705270##
- Other Global Numbers: https://treasuryau.webex.com/cmp3300/webcomponents/widget/globalcallin/globalcallin.do?MTID=m311f46c87a3ab9ae5335a6c0ea431da4&MTID=m311f46c87a3ab9ae5335a6c0ea431da4&MTID=m311f46c87a3ab9ae5335a6c0ea431da4&MTID=m311f46c87a3ab9ae5335a6c0ea431da4&serviceType=MC&serviceType=MC&serviceType=MC&siteurl=treasuryau&siteurl=treasuryau&siteurl=treasuryau&apiname=globalcallin.php&apiname=globalcallin.php&apiname=globalcallin.php&rnd=6124483603&rnd=6124483603&rnd=6124483603&tollFree=0&tollFree=0&tollFree=0&ED=1403111402&ED=1403111402&ED=1403111402&needFilter=false&needFilter=false&needFilter=false&actappname=cmp3300&actappname=cmp3300&actname=/webcomponents/widget/globalcallin/gcnredirector.do&actname=/webcomponents/widget/globalcallin/gcnredirector.do&renewticket=0
- Meeting Number/Access Code: 165 070 5270
- Introductions
- Actions
- CDR Stream updates
- Presentation
- Q&A
- Any other business
- 5 min will be allowed for participants to join the call.
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.
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.
| Type | Topic | Update |
|---|---|---|
| Standards | Version 1.11.0 Published | Link to change log here |
| Standards | Version 1.11.1 Drafted |
Standard-staging Version 1.11.1 Change log for Version 1.11.1 |
| Maintenance | 8th Maintenance Iteration Commenced | Agenda from the 11th of August 2021 meet |
| Maintenance | Decision Proposal 202 - Banking Maintenance Iteration 8 | Link to consultation |
| DSB Newsletter | To subscribe to DSB Newsletter | Link here |
| TSY Newsletter | To subscribe to TSY Newsletter | Link here |
| TSY Newsletter | 18th of August 2021 | View in browser here |
| DSB Newsletter | 13th of August 2021 | View in browser here |
| Consultation | Decision Proposal 180 - Energy Draft Feedback Cycle 3 | Link to consultation |
| Consultation | Decision Proposal 193 - Energy Non-functional Requirements | Link to consultation |
| Consultation | Decision Proposal 194 - Candidate NMI Standing Data End Points | Link to consultation |
| Consultation | Decision Proposal 200 - Action Initiation Framework | Link to consultation |
| Consultation | Normative Standards Review (2021) | Link to consultation |
| Consultation | Decision Proposal 206 - Register Standards | Link to consultation |
| Consultation | Decision Proposal 207 - Draft v3 Rules Analysis - Anticipated Data Standards | Link to consultation |
| Consultation | Decision Proposal 208 - Binding NFRs | Link to consultation |
| Event | Introduction to the Consumer Data Right | Link to register |
| Community | Survey from Regional Australia Bank: Measuring CDR Success - Short Survey | Link to the Survey |
| Blog | The 'why' behind our Decision Proposals. |
Decision Proposal 194 Decision Proposal 206 Decision Proposal 208 |
Provides a weekly update on the activities of each of the CDR streams and their workplaces
| Organisation | Stream | Member |
|---|---|---|
| ACCC | CDR Register (Technical) | Ivan Hosgood (Away) |
| ACCC | CTS | Andrea Gibney |
| ACCC | Onboarding | Christine Atkins |
| DSB | CX Standards | Michael Palmyre |
| DSB | Technical Standards - Banking | Mark Verstege |
| DSB | Technical Standards - Energy & Engineering | James Bligh (Away) |
None this week.
Questions will be received by the community via WebEx chat before the questions are opened to the floor. Participants can pre-submit questions to the DSB mailing box.
We are trialling Sli.do for Question and Answer. Join our Q&A live here: https://www.sli.do/ Code: #169517
| Ticket # | Question | Answer |
|---|---|---|
| 982 | We have a question in relation to Scheduled Payments and the BankingScheduledPaymentInterval objects 'interval' and 'dayInInterval'. If an account has a schedule payment to occur every 14 days, first payment on 17/08/2021 our understanding is that 'interval' = P14D, however, what should be returned in the 'dayInInterval'? Should it be '31' (next payment 31/08/2021)? |
The day in the interval, determines the date within the interval the payment is made. It is defined as: the ordinal day within the interval defined by the interval field on which the payment occurs. If the resulting duration is 0 days in length or larger than the number of days in the interval then the payment will occur on the last day of the interval. A duration of 1 day indicates the first day of the interval. If absent the assumed value is P1D. Formatted according to ISO 8601 Durations (excludes recurrence syntax) with components less than a day in length ignored. The first day of a week is considered to be Monday. In your example, if the payment is made on the last day of the interval, dayInInterval would be P14D |
| 984 | Do we need to respond with page-size, in the following scenarios; 1. In the ADR request, if we receive only 'Page' without 'page-size': In the response records more than default page size (default 25 records) then in the "Self" link do we need to add page & page-size? 2. in the request if we receive Page and Page-size then in the response "Self" links do we need to add Page & Page-size? |
Question 1. In the ADR request, if we receive only 'Page' without 'page-size': In the response records more than default page size (default 25 records) then in the "Self" link do we need to add page & page-size? Answer 1: Yes. If you have more results than were returned in the response you must provide the page and page-size in the link references. Question 2. In the request if we receive Page and Page-size then in the response "Self" links do we need to add Page & Page-size? Answer 2: Yes. This would be the fully qualified URI to the response provided. Similarly, page and page-size are required to describe the first, last, previous and next links |
| 996 | While developing direct debits and scheduled payments as a Data Holder. Can we implement a default page-size of 20, what ever the client requests can we return page-size 20 in paginations. This is because as we are fetching those data from an internal API which keeps a constraint that can return only 20 records at a time. Please help me with this, how we can implement this? |
Question: Can we implement a default page-size of 20, what ever the client requests can we return page-size 20 in paginations. Answer: No. If the client does not provide a value for page-size, the data standards stipulate that a default of 25 will be assumed. If the client does provide a page-size it must be used up to a maximum page-size of 1000. |
View a number of informative and useful links in the Consumer Data Standards Implementation Guide on Information Links.
- Overview
- 2nd of May 2024
- 25th of April 2024 - Cancelled (ANZAC Day)
- 18th of April 2024
- 11th of April 2024
- 4th of April 2024
- March 2024 Agendas
- February 2024 Agendas
- January 2024 Agendas
- 2023 Agendas