Skip to content

DSB Maintenance Iteration 11: Agenda & Meeting Notes (27 April 2022)

Jump to bottom
CDR API Stream edited this page May 2, 2022 · 7 revisions

Date and time: 27/04/2022, 2:00pm – 4:00pm AEST

Location: WebEx

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 249

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 Decision Proposals: key consultation dates
  • Future Plan
  • Retrospective on Iteration 10
  • Iteration 11 backlog
  • Any other business
  • Next Steps

Meeting notes

Introductions

This week is the first call of the 11th maintenance iteration.

The purpose of the meeting is to perform a retrospective of the 10th maintenance iteration and to identify iteration candidates for the 11th maintenance iteration.

  • Housekeeping
  • Overview, purpose and intended outcomes of the meeting

Outstanding Actions

  • Issue #464 DSB will work through the issue to determine opportunities for improvement to address MI9 Retrospective. IN PROGRESS
  • Issue #435 DSB will follow up with the CDR Rules team and the OAIC regarding privacy considerations with sharing a second-party's details under the primary consumer's consent
  • Issue #458 DSB to include examples to describe the transition to FAPI 1.0
  • Issue #488 DSB to discuss internally what evidence can be presented to determine whether DHs will be non-compliant when scopes grow
  • Issue #453 ACCC to investigate operational issues with CTS to resolve discrepancies in Register behaviour.
  • Issue #435 DSB to update the community on progress of this issue in the next maintenance iteration meeting on the 13th of April.
  • Issue #458 DSB will discuss the issue of potential documentation changes to accommodate upstream changes to JARM when FAPI moves from optional to mandatory offline and update the community on progress of this issue in the next maintenance iteration meeting on the 13th of April. Considerations will need to be made on whether the Discovery Configuration Endpoint and DCR documentation should be updated to defer to the upstream standards or explicitly document the fields required to enable JARM support.
  • Issue #486 ACCC to provide feedback on the proposal and comment on the feasibility of FDO.
  • DSB to correct reference to Decision Proposal 245; it has now been published
  • Issue #444 DSB to work with ACCC to resolve API design and determine whether it can be included in this MI or deferred to MI11.
  • Issue #465 DSB will take this offline to get advice from the team on how this situation should be managed.
  • Issue #501 DSB to work with ACCC to determine the best course of action to resolve correct versions for each of the Register APIs Issue 501
  • Issue #488 DSB to update proposal considering whether the change of the obligation date will be considered.
  • Issue #472 DSB to raise a change request to consider standardising time in EnergyPlanContract schema. Issue 505 raised.
  • Issue #476 DSB to correct RateString on Issue 476.
  • Issue #477 DSB and AEMO to meet offline and agreed on an FDO for Issue 477.
  • Issue #478 DSB to raise a change request to help define any new specific error codes required for dealing with issues in data received by DH from SDH. Issue 506 raised.
  • DSB to add a new change request for Profile scope data language fix. See https://github.com/ConsumerDataStandardsAustralia/standards-maintenance/issues/504

Release plan

  • v1.17.0: Released TBC incorporating DP 237 and addressing defects from 1.16.1
  • Future release dates yet to be confirmed

Open / Active Decision Proposals

The following decision proposals are open for community feedback

DP # Closing date DP
229 Placeholder Decision Proposal 229 - CDR Participant Representation
240 27 May 2022 Decision Proposal 240 - ADR Metrics
245 27 May 2022 Decision Proposal 245 - Enhancing Data Recipient Accreditation Negotiation
248 No closing date Noting Paper 248 - Energy PRD

Future Plan

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

Iteration 10 Retrospective

The community can provide feedback on the Iteration 10 process here

Iteration 11 Backlog

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

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

Iteration 11 Candidates

The following changes have been carried over from Iteration #10

# Sector/Domain Change Request
Issue 435 InfoSec Nominated representative end user for non-individual consumers
Issue 458 InfoSec FAPI 1.0 Non Normative Examples
Issue 229 Banking Service field in the Get Transaction Details API
Issue 486 Register Allow ADRs to specify scopes for a Software Statement Assertion (SSA) to support cross industry software products
Issue 431 Register Register participant statuses do not detail data holder behaviour when ADR is revoked and SP inactive
Issue 480 Register 1.13.0 appears to have broken pseudonymity of Pairwise Identifiers
Issue 484 Register 1.13.0 Appears to have introduced new SSA error behaviours
Issue 487 Infosec DCR APIs non-normative examples would benefit from clarification
Issue 472 Energy Modify Energy Plans structure to allow Time of Use based Controlled Load rates

Meeting Minutes

Notes

Outstanding Actions

  • Issue 464 DSB will work through the issue to determine opportunities for improvement to address MI9 Retrospective.

    • V1.17.0 will incorporate enhancements to the usability of the standards; refer comment.        

  • Issue 435 DSB will follow up with the CDR Rules team and the OAIC regarding privacy considerations with sharing a second-party's details under the primary consumer's consent

    • To be covered off in MI 11  

  • Issue 435 DSB to update the community on progress of this issue in the next maintenance iteration meeting on the 13th of April.

    • DSB to carry this over to MI 11.

  • Issue 458 DSB to include examples to describe the transition to FAPI 1.0

    • Working through this at the moment.

  • Issue 488 DSB to discuss internally what evidence can be presented to determine whether DHs will be non-compliant when scopes grow

    • Marking as complete. The risk assessment is being discussed via Issue 486

  • Issue 453 ACCC to investigate operational issues with CTS to resolve discrepancies in Register behaviour.

    • ACCC has undertaken preliminary analysis. ACCC to reach out to Biza to get specific details on the issues being encountered

  • Issue 458 DSB will discuss the issue of potential documentation changes to accommodate upstream changes to JARM when FAPI moves from optional to mandatory offline and update the community on progress of this issue in the next maintenance iteration meeting on the 13th of April. Considerations will need to be made on whether the Discovery Configuration Endpoint and DCR documentation should be updated to defer to the upstream standards or explicitly document the fields required to enable JARM support.

    • In progress to be completed this MI. DSB will walk through this with the community and get feedback from this MI and take this to conclusion

  • Issue 486 ACCC to provide feedback on the proposal and comment on the feasibility of FDO.

    • Validity of the technical control is in discussion but there is a need for comment on the operational risk to the ecosystem
    • DSB to correct reference to Decision Proposal 245; it has now been published.  

  • Issue 444 DSB to work with ACCC to resolve API design and determine whether it can be included in this MI or deferred to MI11.

    • Issue 444 DSB proposal will be presented to the chair in its current form via the MI DP 237. Feedback from the ACCC request to defer to MI 11 will not be included in this proposal as analysis of a solution which meets industry expectation has been met. If further analysis is deemed necessary, a new CR can be raised and considered for MI 11.

  • Issue 465 DSB will take this offline to get advice from the team on how this situation should be managed.

    • Default version to return per API will be analysed via a separate CR, and the current Issue #465 proposal will be proposed to the chair.
    • DSB to raise separate CR to determine default version to return per API

  • Issue 501 DSB to work with ACCC to determine the best course of action to resolve correct versions for each of the Register APIs Issue 501

  • Issue 488 DSB to update proposal considering whether the change of the obligation date will be considered.

    • Proposal has not included ACCC’s request to move the obligation date earlier. This will be treated as new CR in MI 11.
    • DSB to raise new CR to cover moving obligation date.

  • Issue 472 DSB to raise a change request to consider standardising time in EnergyPlanContract schema. 

  • Issue 476 DSB to correct RateString on Issue 476.

    • Will be completed as changes incorporated in MI 10  

  • Issue 477 DSB and AEMO to meet offline and agreed on an FDO for Issue 477.

    • DSB to work through with AEMO this MI

  • Issue 478 DSB to raise a change request to help define any new specific error codes required for dealing with issues in data received by DH from SDH. 

 

Release Plan

  • Decision Proposal 237 for MI 10 will be proposed to the chair soon.
  • V1.17.0 Will be published after approval of the chair.

Iteration 10 Retrospective

  • Publishing proposals hours before meetings: Perhaps a cut-off date on proposals so there is dedicated time to review. Perhaps DSB can hold off on discussing proposals which have not been published in time for cut-off.

  • Assuming implementers have already reviewed the Standards – Very few implementers have reviewed the energy standards. Banking is settled but Energy is declared final with an FDO however there are a large number of things implementers are now discovering.

  • The flip-side of this problem is that significant consultation has occurred with the key retailers but whether architecture teams were involved will have depended on the retailer.

  • ACCC to provide feedback to the community on what their release schedule will look like.

  • DSB to work with ACCC to explore opportunities to reconcile actions raised during the Maintenance Iteration.

Iteration Candidates

  InfoSec  

  • Issue 458 FAPI 1.0 Non Normative Examples  
  • Issue 229 Service field in the Get Transaction Details API  
  • Issue 487 DCR APIs non-normative examples would benefit from clarification  

Register  

  • Issue 486 Allow ADRs to specify scopes for a Software Statement Assertion (SSA) to support cross industry software products Further work is required to determine the risk to the ecosystem with this issue and whether a technical control defined in the standards is required. ACCC need to provide input for this issue to be addressed. Once we have determined the need, we can consider specifying the technical solution.  

  • Issue 431 Register participant statuses do not detail data holder behaviour when ADR is revoked and SP inactive This was deferred in MI 10 as part of ACCC's request. This is now being resurfaced in MI 11 and the ACCC will need to provide comment on when it is appropriate to address this issue.  

  • Issue 480 1.13.0 appears to have broken pseudonymity of Pairwise Identifiers Raised during implementation call so has been short-listed accordingly

  • Issue 484 1.13.0 Appears to have introduced new SSA error behaviours Raised during implementation call so has been short-listed accordingly 

  • Issue 488 Data holder behaviour clarification required when receiving registrations with unsupported authorisation scopes The specification change in the standards has been addressed however the request by ACCC to consider a shorter FDO has not.

    • DSB to raise an additional CR to address the FDO request by ACCC in MI 11.

Energy  

  • Issue 472 Modify Energy Plans structure to allow Time of Use based Controlled Load rates  

Backlog Grooming:

 

  • Issue 470 - Overloading of banking language for scopes / data clusters  

  • Issue 495 – Requested to bring into the iteration  

  • Issue 471 - Additional fields that could be considered.  

  • Issue 427 - Presentation layer on the sponsored accreditation. Management via API (topic 1) Sponsored accreditation presentation (topic 2)  

    • DSB to break this CR into two topics and invite community to comment to help drive priority  

  • Issue 418 – Is this to be considered? DP 245 does highlight this usecase and contributions should be made there. If there is urgency on this topic, the DSB invites feedback.

    • As part of the grooming process, DSB will propose on what will be included in the MI due to limited capacity.  

  • Usage data from AEMO. It was mentioned that in some cases there could be more than one Financially Responsible Market Participant (FRMP) per retailer under the cover for a single consumer. Therefore, usage data over 24 months for a retailer is composed from multiple FRMPs. Clarification is required on how this will work.

    • Biza to raise a ticket and DSB to table this in their discussions with AEMO.

  • Energy PRD – Noting Paper 248 provides clarity that energy retailers will require build to expose PRD endpoints. The standards currently do not specify the patterns and do not intend to. The noting paper provides technical patterns to consider.

    • A question has been raised on the obligations dictated by the rules. The standards maintenance consultation is not the forum to address this ambiguity.
    • Technical implementation will pose challenges for NFR requirements. Unless the retailer self-hosts, the retailer is not obligated to meet the NFRs for those APIs.
    • Also not obligated to report metrics, unless you self-host.
    • DSB to update noting paper to clarify PRD hosting obligations.

  • Issue 435 - Nominated representative end user for non-individual consumers

  • Issue 502 - Review ENUM values for representation of days in Energy Standards

  • Issue 481 - Provide timeline of when multiple sectors per data holder brand will be supported

  • Issue 485 - Common Data Clusters altered for Energy Data Language

New Actions

  • ACCC to provide feedback to the community on what their release schedule will look like.
  • DSB to work with ACCC to explore opportunities to reconcile actions raised during the Maintenance Iteration.
  • DSB to raise an additional CR to address the FDO request by ACCC in MI 11 Issue 488.
  • DSB to break this CR into two topics and invite community to comment to help drive priority Issue 427.
  • As part of the grooming process for MI11, DSB will propose on what can be included in the MI to address Issue 418 due to limited capacity.
  • Biza to raise a ticket on energy usage and DSB to table this in their discussions with AEMO.
  • DSB to update Noting Paper 248 to clarify PRD hosting obligations.

Any other business

  • None

Next Steps

  • Preparation for Maintenance Iteration Meeting on 11 May 2022.

Getting Started

Meetings

Maintenance Iterations

CDR Implementation Call

Clone this wiki locally