Skip to content

DSB Maintenance Iteration 14: Agenda & Minutes (8 February 2023)

Jump to bottom
CDR API Stream edited this page Feb 15, 2023 · 18 revisions

Date and time: 08/02/2023, 2:00pm – 4:00pm AEDT

Location: Microsoft Teams Meeting

Dial-in details:

Chair: Hemang Rathod, DSB

Maintenance overview: Further information

Maintenance project board: See here

Decision Proposal: This maintenance iteration is being consulted on under Decision Proposal 281: Maintenance Iteration 14

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 contact@consumerdatastandards.gov.au 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, present and emerging, and recognise and celebrate the diversity of Aboriginal peoples and their ongoing cultures and connections to the lands and waters of Australia.

Agenda

  • Introductions
  • Outstanding Actions
  • Release plan
  • Open Consultations
  • Future Plan
  • Maintenance Iteration 13 Retrospective
  • Maintenance Iteration 14 Issues
  • Any other business

Meeting notes

Introductions

The purpose of this meeting is to

  • Run a Retrospective on Maintenance Iteration 13.
  • Groom the backlog to discuss iteration candidates for Maintenance Iteration 14

Outstanding Actions

Energy

  • Retailers to raise a ticket on energy usage data covering multiple FRMPs. DSB to table this in their discussions with AEMO.
    • Analysis ongoing. Note Recommend to close this action. If the outcome of analysis is presented, appropriate CR/DP can be raised to consult on any issues.

InfoSec

None

CX

None

Release plan

  • Latest/current version of standards is 1.22.0 which incorporates changes from MI13

Open Consultations

The following decision proposals are open for community feedback

DP # Consultation Closing date
Consultation Decision Proposal 229 - CDR Participant Representation Placeholder: no close date
Link to consultation
Consultation Decision Proposal 267 - Telco Data Language TBD
Link to consultation
Consultation Decision Proposal 275 - Holistic Feedback on Telco Standards TBD
Link to consultation
Consultation Noting Paper 276 - Proposed V5 Rules: Standards Impacts TBD
Link to consultation
Consultation Noting Paper 280 - The CX of Authentication Uplift 10 February 2023
Link to consultation
Consultation Decision Proposal 287 - Energy C&I Consumers 17th February 2023
Link to consultation
Consultation Noting Paper 291 - Workshop for simple Payments Initiation
 Workshop on 7 March 2023
Link to consultation

Future Plan

Review of January-March Quarter and new changes: https://github.com/ConsumerDataStandardsAustralia/future-plan/projects/1

Maintenance Iteration 13 Retrospective

Miro board is available here https://miro.com/app/board/uXjVPz3dNPo=/

Maintenance Iteration 14 Issues

All open change requests can be found here: Standards Maintenance Issues.

The standards maintenance backlog can be found here: Data Standards Maintenance

The change requests proposed for this iteration are:

Iteration 14 Holistic Feedback

Any Other Business

Meeting Minutes

Notes

Outstanding Actions

Energy

  • Retailers to raise a ticket on energy usage data covering multiple FRMPs. DSB to table this in their discussions with AEMO.
    • Closing this Action.
    • While analysis is ongoing there's no benefit in tracking it because retailers will be required to raise a CR if the outcome warrants a change.

Maintenance Iteration 13 Retrospective

image

Start

Tickets:

  1. "Be clearer about what will be discussed"
    • The participant who raised the ticket elaborated as being clear about the issues that would be discussed in a given MI. The DSB explained the process (noted below) which address the issue:
      • The first session for each MI is to groom the backlog to identify candidates based on participant recommendations, DSB capacity and priorities as directed by the DSB Chair and the Data Standards Advisory Committee.
      • Following the first session change requests are prioritised for the iteration and items may include related activities (e.g. compliance) that are monitored within the iteration out of interest but will not result in a change to the standards.
      • The agenda for each subsequent meeting in the iteration lists the candidates that will be discussed and DSB posts this information on the relevant Decision Proposal with links to agendas and relevant issues as required.

Stop

Tickets:

  1. "Stop adding non binded standards to the standards"
  • This ticket was in relation to introducing non-binding standards in the CDS. The specific example of introducing non-binding Telco APIs in the CDS was used as it may complicate interpretation of binding and non binding standards despite messaging to confirm they're not binding.
    • DSB acknowledges the concern as it was encountered with Energy where a separate site was established which presented a different set of challenges. Sector specific APIs need to be interpreted in the context of the Consumer Data Standards as a whole (for e.g. CX and InfoSec) and therefore separating them out is not helpful.
    • Providing information on the 'delta' between versions and features that enable API versions to be displayed based on a compliance date is an option.
    • It was noted that international standards used RFCs however that would mean the standards would need to be broken down into individual parts to enable that.
    • The DSB will continue to explore options that enable clearer presentation and consumption of binding and non binding standards at a given point in time.
  1. "Posting consultation for binding separate from other consultations"
  • DSB addressed this concern at the time it was raised by extending the consultation period and creating a GitHub entry to redirect interested parties to the non-technical consultation.
  • A similar process will be used should any non-technical consultations be required in the future.

Continue

Tickets:

  1. "Keep forecasting FDOs with sufficient notice"
  • Challenges present for implementers who plan on a 90 cycle, if changes to FDOs are made within that time frame the obligation may have already been shipped making amendments to them difficult.
    • DSB acknowledges this and encourages participants involved in discussions on a Change Request to also consider the date the changes can be made so the FDO is set accordingly during consultation.

Maintenance Iteration 14 Issues

The following candidates were proposed:

CX

InfoSec

Energy

Banking

Register

Documentation

Watching Brief

The following change requests are not related to DSBs remit to change the Standards however they are of significant interest to the community from a standards perspective. A watching brief will be kept on them throughout this iteration.

Other Business

None.

New Actions

Banking

  • DSB to review all Banking change requests to determine if there are related items that could be addressed at the same time as #567 and #569.

Next Steps

Community to review the list of proposed candidates and post comments as needed in preparation for the next meeting on 22 February 2023.

Getting Started

Meetings

Maintenance Iterations

CDR Implementation Call

Clone this wiki locally