DSB Maintenance Iteration 20: Agenda (4 September 2024) - ConsumerDataStandardsAustralia/standards GitHub Wiki
Meeting Details
- Date and time: 4/09/2024, 2:00pm – 4:00pm AEST
- Location: Microsoft Teams Click here to join the meeting
- Dial-in details:
- Meeting ID: 494 389 362 467
- Passcode: PZFPkd
- Dial In Number: +61 2 6188 4842
- Phone Conference ID: 779 012 902#
- Chair: Elizabeth Arnold, DSB
- MI Solution Architect: Nils Berge
- Maintenance overview: Further information
- Maintenance issues: See here
- Maintenance project board: See here
- Maintenance Iteration Decision Proposal: Consultation on Decision Proposal 353 - Maintenance Iteration 20
- Maintenance Iteration Meeting Schedule, Agenda and Meeting Notes: See here
Housekeeping
Recording
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.
Acknowledgement of Country
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.
Time management of Maintenance Iteration Meetings (if required)
- 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.
Agenda
- Introductions
- Release Plan
- Maintenance Iteration 20 Candidates
- Requirements Analysis
- Other business
Introductions
The purpose of this meeting is to confirm the candidates that will be approved in MI20. Requirements analysis issues will be carried over to MI21 where necessary. The Decision Document has been drafted and once all changes have been staged and reviewed it will be sent to the Chair for approval.
Release Plan
- Current version is 1.31.0.
- The outcome of Maintenance Iteration 20 will likely be published in v1.32.0.
Maintenance Iteration 20 Candidates
| Domain | # | Issue | Change Type |
|---|---|---|---|
| MI20 | 647 | Maintenance Iteration 20 Holistic Feedback | Non-breaking |
| CX | 646 | Clarify selection of Trusted Adviser in the CX Guidelines | Non-breaking change |
| Security | 648 | Adopt BCP 195 for TLS ciphers ACTION: DSB to stage the change. | Will be treated as a Breaking change |
| Security | 650 | Weaken JARM Encryption Requirements for ADRs Waiting on information about data holders who require encryption on JARM responses. | Carry over to MI21 |
| Banking | 641 | Update CDS documentation to clarify expected rate value 'sign' (+/-) for each RateType | Non-breaking change |
| Energy | 644 | AmountString field type impractical for energy tariffs | No change |
| Energy | 652 | Specify units of currency to be used for the AmountString field type | Non-breaking change |
| Energy | 653 | EnergyPlanTariffPeriod - cater for plans with no dailySupplyCharge ACTION: Participants impacted by this change are asked to consider the proposal and advise if treating the change as errata can be accommodated. | Non-breaking change |
Requirements Analysis
| Domain | # | Issue | Comments |
|---|---|---|---|
| Common | 610 | Addition of an (18 or over) Age Verification Flag OUTSTANDING ACTION: Participants to provide examples of use cases. | DSB recommends closing this issue |
| Banking | 553 | Running balance available under transaction detail OUTSTANDING ACTION: ADR to clarify requirements in options proposed in original post. OUTSTANDING ACTION: ADR to clarify requirements in options proposed in original post. OUTSTANDING ACTION: ADRs to investigate whether information exists on differences between data holders that illustrate the problems with calculated balances. OUTSTANDING ACTION: DHs to provide clarification on the difference between 'current' and 'available' balances. OUTSTANDING ACTION: DHs to provide details on how balances are calculated. | To remain open |
| Banking | 636 | Remove BankingTransactionDetail and incorporate extendedData into BankingTransaction OUTSTANDING ACTION: DSB to following up with NPP. In progress OUTSTANDING ACTION: DSB to schedule offline discussion with SISS (Josh) on data quality analysis. In progress OUTSTANDING ACTION: Participants to provide feedback on summary of earlier discussions in comment. | Refer to NFR CG for async pattern |
| Energy | 651 | Supporting HTTP Status 429 passthrough from Secondary Data Holder ACTION: DSB to update issue as the details of the become available. | Trial planning is in progress |
| Security | 628 | Addition of a DH-side endpoint for querying the status of a consent establishment flow | To remain open |
| Security | 649 | Inconsistent JARM error codes | For discussion |
Any other business
Participants are invited to raise topics related to the Data Standards that would benefit from the groups' consideration.