DSB Maintenance Iteration 18: Agenda (6 March 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.

Agenda

  • Introductions
  • Release Plan
  • Open Consultations and Pending Proposals
  • Future Work Plan
  • Maintenance Iteration Review Outcomes
  • Requirements analysis
  • Maintenance Iteration 18 Candidates
  • Any other business

Introductions

The purpose of this meeting is to:

  • Provide feedback on Maintenance Iteration Review outcomes; and
  • Finalise candidates for Maintenance Iteration 18 and continue discussion on requirements to develop proposals.

Release Plan

Open Consultations and Pending Proposals

A number of consultations are open for community feedback: See issues open for feedback.

Future Work Plan

Review of January-March Quarter and new changes: See DSB Future Work Plan Project board.

Maintenance Iteration Review Outcomes

The DSBs planned actions on the outcome of the MI Review are:

  • Requirements for Change & Decision Making

    • Update the CR Template to include a section on 'Intent and Value of Change' to support prioritisation, sequencing and the Chair's decision-making process in understanding the drivers for change in the ecosystem. This will also assist with drafting Decision Proposals.
    • Increase descriptiveness of Standards wherever possible while avoiding being overly prescriptive.
    • Continue development of Test Artefacts to assist with interpretation of the Standards.
    • Consider incorporating Guidance when making each change to include Usage and Interpretation.
    • Support the DSB Chair in developing a Scorecard and Prioritisation Framework.

  • Obligation Dates and Standards Releases

    • Consider Rules obligation dates when MI changes are assigned to a release date to avoid overloading delivery schedules.
    • Consider code freezes where necessary to prevent overloading.

  • Communication, Collaboration and Participation

    • Encourage participant involvement in MIs to support their understanding of forthcoming changes before new versions of the standards are made. To facilitate this more information on Maintenance Iteration candidates and progress will be shared in the Implementation Call to ensure a broader audience is aware of change and can communicate to colleagues.
    • More active commentary on each issue to push out notifications during an MI.
    • Drafting proposals and staging changes earlier in the MI to give participants more time to consider the impact of a change.
    • Continue with a single cross sectoral MI call but schedule offline meetings for specific detailed issues. Time box the discussion on each issue and request continued discussion on GitHub.
    • To improve efficiency of MI calls, consider changing the order of issues on the agenda to address cross sectoral issues first, then domain specific issues depending on number of items.
    • In Decision Proposals and Decision Documents, better articulate context of the change for CDR Participants and incorporate an Executive Summary.

The original feedback and DSB's synthesis are available on this board: https://miro.com/app/board/uXjVNzxv1Pk=/.

Requirements analysis

Domain # Issue Comments
Common 610 Addition of an (18 or over) Age Verification Flag In progress, no update
Errors 412 Proposal to change specific error codes from MUSTs to SHOULDs May be withdrawn, ANZ to update

Maintenance Iteration 18 Candidates

Domain # Issue Status
MI 18 629 Maintenance Iteration 18 Holistic Feedback Candidate
CX 557 Withdrawal of a SUI by an Account Holder leaving an "Empty" Authorisation Candidate
CX 633 Collection Consents - Authorisation Amendment Candidate
Security 543 refresh_token_expires_at and sharing_expires_at claims listed as MUST be supported Proposed as new candidate
Security 628 Addition of a DH-side endpoint for querying the status of a consent establishment flow Candidate
Security 631 Updates to 'Revoking consent' Standards Candidate
Security 632 Concurrent consent support and cdr_arrangement_id Proposed as new candidate
Admin 626 AuthorisationMetricsV2 abandonmentsByStage property descriptions and CDS Guide Candidate
Energy 623 Add new pricing models to EnergyPlanContractV2 Candidate
Energy 624 Improved structure for Solar Time Varying Tariffs Candidate
Energy 625 Additional field to support Step Tariff calculations Candidate
Energy 627 EnergyPlanTariffPeriod - Change to daily supply charge Candidate

Any other business

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