DSB Maintenance Iteration 20: Agenda (24 July 2024) - ConsumerDataStandardsAustralia/standards GitHub Wiki
Meeting Details
- Date and time: 24/07/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 Capacity
- Maintenance Iteration 20 Candidates
- Prioritisation
- Candidate discussion
- Requirements Analysis
- Any other business
Introductions
The purpose of this meeting is to prioritise items proposed as candidates in the kick off meeting on 10 July.
DSB had anticipated continuing Requirements Analysis on a number of items carried over from Maintenance Iteration 19 (#573, #628 and #636), however given the number of items falling into this category, we will prioritise these with the community before proceeding.
Release Plan
- Current version is 1.31.0.
- The outcome of Maintenance Iteration 20 will likely be published in v1.32.0.
Maintenance Iteration Capacity
In the first meeting of Maintenance Iteration 20, 14 issues proposed either as a Candidate for MI20 or requiring further analysis and discussion. A further two issues were proposed on Decision Proposal 353 - Maintenance Iteration 20.
These candidates have been grouped into confirmed candidates and issues requiring further analysis.
The Maintenance Iteration has capacity to add two of the issues requiring further analysis. We're asking the Community to provide input on how these issues should be prioritised.
Maintenance Iteration 20 Candidates
Confirmed candidates
- #647 Maintenance Iteration 20 Holistic Feedback
- #646 Clarify selection of Trusted Adviser in the CX Guidelines
- #648 Adopt BCP 195 for TLS ciphers
- #650 Weaken JARM Encryption Requirements for ADRs
- #641 Update CDS documentation to clarify expected rate value 'sign' (+/-) for each RateType
- #644 AmountString field type impractical for energy tariffs
- #652 Specify units of currency to be used for the AmountString field type
Issues requiring further analysis
- #628 Addition of a DH-side endpoint for querying the status of a consent establishment flow
- #636 Remove BankingTransactionDetail and incorporate extendedData into BankingTransaction
- #573 Clarification on handling of standard claims in request object
- #649 Inconsistent JARM error responses
- #651 Supporting HTTP Status 429 passthrough from Secondary Data Holder
- #TBA Extensibility of standards (no issue raised yet)
- #610 Addition of an (18 or over) Age Verification Flag
- #553 Running balance available under transaction detail
- #245 Decision Proposal 245 - Enhancing Data Recipient Accreditation Negotiation
- #627 EnergyPlanTariffPeriod - Change to daily supply charge
Prioritisation
Using this Miro Board we will run a short exercise to Prioritise the issues requiring further analysis.
Candidate discussion
| Domain | # | Issue |
|---|---|---|
| MI20 | 647 | Maintenance Iteration 20 Holistic Feedback |
| CX | 646 | Clarify selection of Trusted Adviser in the CX Guidelines |
| Security | 648 | Adopt BCP 195 for TLS ciphers |
| Security | 650 | Weaken JARM Encryption Requirements for ADRs |
| Banking | 641 | Update CDS documentation to clarify expected rate value 'sign' (+/-) for each RateType |
| Energy | 644 | AmountString field type impractical for energy tariffs |
| Energy | 652 | Specify units of currency to be used for the AmountString field type |
Requirements Analysis
Discussion on the two issue prioritised for Maintenance Iteration 20.
| Domain | # | Issue |
|---|---|---|
| TBA | issue selected from prioritisation session | |
| TBA | issue selected from prioritisation session |
Any other business
Participants are invited to raise topics related to the Data Standards that would benefit from the groups' consideration.