Skip to content

DSB Maintenance Iteration 20: Agenda (7 August 2024)

Jump to bottom
CDR API Stream edited this page Aug 6, 2024 · 2 revisions

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 this meeting is to check whether any new issues relate to the candidates selected for Maintenance Iteration 20 and to continue discussion on the candidates to work toward a proposal for the community to consider.

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 is requesting input from the community on this change.		 To be determined
Security 648 Adopt BCP 195 for TLS ciphers
ACTION: participants are requested to consider whether the change from a specific suite of ciphers to those listed in BCP 195 would result in a breaking change and advise on a suitable Future Dated Obligation.		 To be determined
Security 650 Weaken JARM Encryption Requirements for ADRs
Discuss if information on 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 is requesting feedback from the community on the proposed solution in this comment 		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 review proposed description and advise of any amendments.		 To be determined, likely Non-breaking
Energy 653 EnergyPlanTariffPeriod - cater for plans with no dailySupplyCharge
ACTION: DSB to explore options to resolve this issue.		 To be determined

Requirements Analysis

Domain # Issue Comments
Common 610 Addition of an (18 or over) Age Verification Flag
ACTION: Participants to provide examples of use cases.		 In progress
Banking 553 Running balance available under transaction detail
ACTION: ADR to clarify requirements in options proposed in original post.
ACTION: ADRs to investigate whether information exists on differences between data holders that illustrate the problems with calculated balances.
ACTION: DHs to provide clarification on the difference between 'current' and 'available' balances.
ACTION: DHs to provide details on how balances are calculated.		 In progress
Banking 636 Remove BankingTransactionDetail and incorporate extendedData into BankingTransaction
OUTSTANDING ACTION: DSB to follow up with Dima on NPP opinion.
OUTSTANDING ACTION: DSB to schedule offline discussion with SISS (Josh) on data quality analysis.
ACTION: Participants to provide feedback on summary of earlier discussions in comment.		 In progress
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 coordinate communications with ACCC.		 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.

Getting Started

Meetings

Maintenance Iterations

CDR Implementation Call

Clone this wiki locally