DSB Maintenance Iteration 20: Agenda (21 August 2024) - ConsumerDataStandardsAustralia/standards GitHub Wiki

Meeting Details

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
  • Any other business

Introductions

The purpose of today's meeting is to:

  • review proposed solutions and staged changes for maintenance iteration candidates;
  • continue discussion on candidates that do not have a proposed solution; and
  • continue Requirements Analysis on prioritised issues.

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 ACTION Participants are requested to review the comments posted on this issue for details and advise of any concerns. Non-breaking
CX 646 Clarify selection of Trusted Adviser in the CX Guidelines ACTION DSB CX to post comments from CDR Agencies in response to discussion once analysed.. To be determined
Security 648 Adopt BCP 195 for TLS ciphers ACTION DSB to stage the change. To be determined
Security 650 Weaken JARM Encryption Requirements for ADRs Discuss if information on data holders who require encryption on JARM responses is available. To be determined
Banking 641 Update CDS documentation to clarify expected rate value 'sign' (+/-) for each RateType ACTION: DSB to consider the changes needed and post on the issue To be determined
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 ACTION: Participants to comment on the issue to indicate preferred wording change. ACTION: DSB to incorporate the outcomes from the last meeting and feedback provided in related posts to provide an updated description. To be determined, likely Non-breaking
Energy 653 EnergyPlanTariffPeriod - cater for plans with no dailySupplyCharge ACTION: DSB to update proposed solution on the Issue. ACTION: DSB is interested in feedback on use of the field from ADRs. To be determined

Requirements Analysis

Domain # Issue Comments
Energy 651 Supporting HTTP Status 429 passthrough from Secondary Data Holder ACTION DSB to review scope of trial, including timing of change with AEMO and other impacted participants and ACCC. In progress
Common 610 Addition of an (18 or over) Age Verification Flag OUTSTANDING ACTION: Participants to provide examples of use cases. In progress
Banking 553 Running balance available under transaction detail 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. ACTION DSB to escalate issue 553 to the Regulator. In progress
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. In progress

NOTE: Issue #628 - Addition of a DH-side endpoint for querying the status of a consent establishment flow may be discussed if time permits.

Any other business

Participants are invited to raise topics related to the Data Standards that would benefit from the groups' consideration.