DSB Maintenance Iteration 21: Agenda (13 November 2024) - ConsumerDataStandardsAustralia/standards GitHub Wiki
- Date and time: 13/11/2024, 2:00pm – 4:00pm AEDT
- Location: Microsoft Teams Click here to join the meeting
-
Dial-in details:
- Meeting ID: 464 316 549 421
- Passcode: NiYjec
- Dial In Number: +61 2 6188 4842
- Phone Conference ID: 969 637 712#
- Chair: Mark Verstege, DSB
- MI Solution Architect: Hemang Rathod
- Maintenance overview: Further information
- Maintenance issues: See here
- Maintenance project board: See here
- Maintenance Iteration Decision Proposal: Consultation on Decision Proposal 356 - Maintenance Iteration 21
- Maintenance Iteration Meeting Schedule, Agenda and Meeting Notes: See here
The Maintenance Iteration Calls are recorded for note taking purposes only. All recordings are kept securely, as are the transcripts which may be made from them. No identifying material will be provided without the participant's consent. Participants may email [email protected] 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 and present and recognise and celebrate the diversity of Aboriginal peoples and their ongoing cultures and connections to the lands and waters of Australia.
- After the first meeting to groom the backlog, if the number of candidates and the anticipated complexity of them indicates timeboxing discussions is required, these time management practices will be put in place:
- 5 minute delay will be removed. Meetings will commence at 2:00PM AEST.
- Each discussion will be timed, if the discussion is not concluded within the allotted time, the discussion will be taken offline.
- Allotted time will be determined based on the number of candidates in the iteration.
- If the discussion on all issues has concluded and time remains, any issues scheduled for offline discussion can be revisited.
- Start times will be estimated for each Domain and advertised when the Agenda is published.
- 15 min
- Introductions
- Release Plan
- Actions
- 100 min
- Candidate Finalisation
- 5 min
- Any other business
The purpose of this meeting is to confirm the candidates that will be proposed in MI21. Actions will be carried over to MI21 where necessary. The Decision Document with approved candidates will be drafted and sent to the Chair for approval.
- Current version is 1.32.0 released on 21 October 2024.
- Changes resulting from this MI will be incorporated in a new standards version (e.g. 1.33.0)
- The next future release is not currently planned
- DSB to provide use cases and expected outcomes for authorisations based on account removal scenarios ✔️
- Scenarios outlined in #669 - Guidance for accounts becoming unavailable
- 519: Billing API Change: DSB to assess whether this change has been resolved ✔️
- 508: Provide APIs to automate onboarding of software products and provisioning of certificates: DSB shall follow up with ACCC to ascertain current support ✔️
- 518: Deliver V2 of the GetDataHolderBrandsSummary API: DSB to refer the change back to ACCC ✔️
- 659 - Enhancing CDR Adoption: Streamlining Account Selection and Improving Data Transparency: The community to provide views on a mandatory 'select all' functionality in account selection
-
656 - A status of POSTED should indicate the final update for a transaction
- Data Holders to investigate and provide a response if the proposed changes would have any implementation considerations adopting the proposal.
- Data Holders to investigate and provide a response whether the lifecycle of transactions results in changes to posted transactions and what occurs in reversal scenarios - does this result in a change to the same transaction, or creation of a new transaction?
-
660 - Revise the Availability Requirements NFRs: DSB to draft the options for consideration ✔️
- Option 1: Detailed technical outage information via Get Outages (including technical explanation, list of affected endpoints, list of affected data clusters, list of affected products or product categories, coded list of Data Quality and PS11 impacts)
- Option 2: Allow DHs to deny data sharing at the account level via a Temporarily Unavailable error that is updated to include PS11 data latency issues
- Option 3: Provide additional detail in the meta{} object for transactions and accounts where data latency is an issue
- Option 4: Provide additional consumer notifications via the ADR, DH or both
Participants are invited to raise topics related to the Data Standards that would benefit from the groups' consideration.