Skip to content

DSB Maintenance Iteration 11: Agenda & Meeting Notes (22 June 2022)

CDR API Stream edited this page Jun 21, 2022 · 15 revisions

Date and time: 22/06/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 [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, 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 / Active Decision Proposals
  • Iteration 11 issues
  • CRs for discussion
  • Any other business
  • Next Steps

Meeting notes

Introductions

This week is the sixth and final call of the 11th maintenance iteration.

The purpose of the meeting is to review and close out the candidates that have been consulted on in the 11th maintenance iteration.

Outstanding Actions

Energy

  • DSB/AEMO Issue #477 DSB and AEMO to meet offline and agreed on an FDO for Issue 477.
  • Retailers to raise a ticket on energy usage data covering multiple FRMPs. DSB to table this in their discussions with AEMO.
  • This was discussed in recent meeting with AEMO, Biza and big 3 retailers. AEMO presented their analysis which indicated the scenario accounted for less than 1%. Retailers have taken action to conduct analysis on their own data. Pending outcome, ticket may be required.

InfoSec

  • DSB (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.
  • DSB to confirm PAR requirement for scope and client_id outside the request object through review of upstream specs. Issue #458 💡
  • DSB to raise a change request and stage a proof of concept minimising the OpenID Provider Configuration End Point section to strip out parameters already required by upstream specs so that the CDS doesn't redundantly repeat normative references. Issue #458 💡
  • CBA to raise a change request to drop encryption for the JARM token response. Issue #458 💡

Register

  • INDUSTRY to provide feedback to indicate when data holders with multiple sectors will need to be represented in the Register for Issue 481. 💡
  • ACCC to advise on what iteration issue #481 should be resolved in.
  • DSB to post early analysis on issue 484 to determine whether its covered in DP245 or whether there is further work outside of the Decision Proposal. 💡
  • ACCC to advise on whether MI12 is an appropriate iteration to resolve issue #431. 💡

Register / DCR

  • DSB to stage the change for Issue 491 and consider a patch release.

Other

  • DSB/ACCC: DSB to work with ACCC to explore opportunities to reconcile actions raised during the Maintenance Iteration.
  • ACCC to provide feedback to the community on what their release schedule will look like.

MI11 Holistic Feedback

Release plan

  • Decision Proposal 237 for MI 10 was approved by the Chair on 12 May 2022.
  • V1.17.0 of the standards is now published and live.

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
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 11 Issues

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

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

Iteration 11 Progress

The following change requests are proposed for this iteration.

CRs under consultation

Issue # Sector Change Request Proposed Outcome Change Type Future Dated
Obligation (FD)
Affected Schema
(if applicable)
Affected Endpoint
(if applicable)
Issue 472 Energy Modify Energy Plans structure to allow Time of Use based Controlled Load rates Change Recommended Non-Breaking 15 Nov 2022 EnergyPlanControlledLoad
Issue 495 Energy GetAgreedPaymentSchedule API - manualPayment section should have paymentFrequency instead of billFrequency field Under consultation Non-Breaking 15 Nov 2022
Issue 502 Energy Review ENUM values for representation of days in Energy Standards Change Recommended Change Recommended 15 Nov 2022
Issue 515 Energy Clarity around GET Metrics for AER, DELWP and AEMO Change Recommended Non-Breaking 15 Nov 2022
Issue 514 Energy Get Usage For ... Shared Responsibility APIs Payload size Change Recommended Non-Breaking 15 Nov 2022
Issue 512 Energy Distributor needed for EnergyPlan.geography object Change Recommended Non-Breaking 1 Oct 2022
Issue 505 Energy Representation of time within EnergyPlanDetail Schema Change Recommended Non-Breaking 15 Nov 2022
Issue 499 Energy Unknown field in Energy Secondary Data Holder OpenAPI spec Documentation fix Non-Breaking 15 Nov 2022
Issue 493 Energy Get Transaction Detail - Client Error documentation Documentation fix Non-Breaking 15 Nov 2022
Issue 461 Energy Documentation Improvement: EnergyPlanContract.variation Documentation fix Non-Breaking 15 Nov 2022
Issue 485 CX Common Data Clusters altered for Energy Data Language Under consultation Non-Breaking 15 Nov 2022
Issue 427 CX Standards & Guidelines regarding Sponsored Accreditation See latest post in Issue 427 for more detail about what will be addressed in DP229 and what has been covered by the CX Guidelines.
Issue 480 Register 1.13.0 appears to have broken pseudonymity of Pairwise Identifiers Under Consultation
Issue 484 Register 1.13.0 Appears to have introduced new SSA error behaviours Under Consultation
Issue 481 Register Provide timeline of when multiple sectors per data holder brand will be supported Change Recommended Non-breaking change
Issue 486 Register Allow ADRs to specify scopes for a Software Statement Assertion (SSA) to support cross industry software products Under Consultation
Issue 431 Register Register participant statuses do not detail data holder behaviour when ADR is revoked and SP inactive Defer Proposed
Issue 507 Register FDO for data holders ignoring unsupported authorisation scopes to be set earlier than energy release date Under Consultation
Issue 510 Register Register API error codes need to be aligned with the CDS standardised error codes Change Recommended Non-breaking change
Issue 491 Register / DCR ID Token algorithm support requirements are ambiguous Documentation fix Non-breaking change
Issue 435 InfoSec Nominated representative end user for non-individual consumers
Issue 458 InfoSec FAPI 1.0 Non Normative Examples
Issue 172 InfoSec Validation of client_id parameter in client authentication requests
Issue 200 InfoSec Documentation defect in the non-normative example - DH calling the DR Revocation Endpoint Close issue No change
Issue 500 InfoSec ADR should not initiate Authorisation Code Flow with PKCE if the Data Holder does not support this flow
Issue 447 InfoSec CORS typos in CDR
Issue 479 InfoSec Clarification on Minimum Algorithm Required for JARM Options presented To be determined
Issue 487 InfoSec DCR APIs non-normative examples would benefit from clarification Documentation fix Non-breaking change
Issue 489 InfoSec v1.15.0 More ambiguity into x-fapi-auth-date not less Documentation fix Non-breaking change
Issue 411 High Level Standards Clarification of x-fapi-interaction-id header Under Consultation
Issue 494 High Level Standards Response payload structure description error Documentation fix Non-breaking change
Issue 497 Common APIs CommonEmailAddress - address format documentation Documentation fix Non-breaking change
Issue 409 Non-Functional Requirements Dynamic Client Registration Response Time NFR Non-breaking change
Issue 490 Admin APIs Admin CDR OpenAPI specification missing error definitions Documentation fix Non-breaking change
Issue 492 Admin APIs Admin API Definitions Request Body Incorrectly Nested Documentation fix Non-breaking change

Closed CRs

Issue # Sector Change Request Outcome
Issue 78 High Level Standards HTTP Header to be returned in the case where the request is not entirely well formed and a large page size is requested Close issue - No change

CRs for discussion

InfoSec

(Urgent) #521 Transition of required parameters in the CDR Arrangement JWT

  • For discussion

Energy

#495 GetAgreedPaymentSchedule API - manualPayment section should have paymentFrequency instead of billFrequency field

  • Review feedback and agree on next steps
  • Summary of feedback
    • Placement of calculationType and paymentFrequencey
    • Inclusion of servicePointId
      • Included as part of addressing the feedback to cater for scenarios where multiple payment agreements, one per specific service/connection point, within a single account can exist.
      • For example a customer having direct debit setup for property/connection point A and manual payments for property/connection point B. In this scenario, servicePointId would be used to identify which connection point the agreement is related to.
      • If same payment agreement is used for all connection points within an account, servicePointId is not required.
    • Access to servicePointId

#512 Distributor needed for EnergyPlan.geography object

  • Review feedback and agree on next steps

CX

#485 Common Data Clusters altered for Energy Data Language

  • To discuss

Register

#486 Allow ADRs to specify scopes for a Software Statement Assertion (SSA) to support cross industry software products

  • Review proposal

#507 FDO for data holders ignoring unsupported authorisation scopes to be set earlier than energy release date

  • Discuss problem space and next steps

#480 1.13.0 appears to have broken pseudonymity of Pairwise Identifiers

  • Discuss problem space and next steps

#484 1.13.0 Appears to have introduced new SSA error behaviours

  • Discuss problem space and next steps

#431 Register participant statuses do not detail data holder behaviour when ADR is revoked and SP inactive

  • Review Deferral

#481 Provide timeline of when multiple sectors per data holder brand will be supported

  • Review Proposal

**#510 Register API error codes need to be aligned with the CDS standardised error codes

  • Review Proposal

MI11 Holistic Feedback

#511 Iteration 11 Holistic Feedback

  • Update on contributions to date

Any Other Business

Meeting Minutes

Notes

Progress on Outstanding Actions

Energy

InfoSec

Register

Other

CRs for discussion

CX

InfoSec

Register

Energy

MI11 Holistic Feedback

New Actions

Next Steps

Clone this wiki locally