DSB Maintenance Iteration 12: Agenda & Minutes (14 September 2022) - ConsumerDataStandardsAustralia/standards GitHub Wiki
Date and time: 14/09/2022, 2:00pm – 4:00pm AEST
Location: Microsoft Teams Meeting
Dial-in details:
- https://teams.microsoft.com/l/meetup-join/19%3ameeting_MjAyMzg2M2EtNTE2Zi00YmJiLWI1NWYtYjg3ZWFiYTI0MWM2%40thread.v2/0?context=%7b%22Tid%22%3a%22214f1646-2021-47cc-8397-e3d3a7ba7d9d%22%2c%22Oid%22%3a%2257cd8c59-9b50-4670-bc85-25281a11ec8d%22%7d
- Dial In Number: +61 2 9161 1229
- Phone Conference ID: 222 556 244#
- Quick Dial: +61291611229,,222556244#,,(tel:+61291611229,,222556244#) Australia, Sydney
Chair: Mark Verstege, DSB
Maintenance overview: Further information
Maintenance project board: See here
Decision Proposal: This maintenance iteration is being consulted on under Decision Proposal 259: Maintenance Iteration 12
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
- Maintenance Iteration 12 Issues
- Any other business
- Next Steps
Meeting notes
Introductions
This meeting is the fourth and final in the series for Maintenance Iteration 12. The purpose is to provide a summary of the decision proposals and progress to agreement on any relevant future dated obligations where applicable. Any changes that are not finalised will be moved to iteration candidates in the next maintenance iteration.
Outstanding Actions
Energy
- DSB/AEMO Issue #477 Provide an update on delivery date for Get Status and Get Outages APIs Issue 477.
- Retailers to raise a ticket on energy usage data covering multiple FRMPs. DSB to table this in their discussions with AEMO.
- Analysis ongoing
- DSB will progress "Issue #520 - Stepped solar feed in tariffs in Energy" and propose options for consultation
- Consensus from Energy Retailers is required to mark Issue #506 - Energy error codes for issues in data received by DH from SDH as urgent.
- Note - Consensus no longer required as proposed solution is non breaking
- Consensus from Energy Retailers is required to mark Issue #524 - EnergyDerRecord - mandatory values not available in AEMO's DER register as urgent.
- Note - Consensus no longer required as proposed solution is non breaking
- Consensus from Energy Retailers is required to mark Issue #526 - Get DER for Service Point - allow for no data as urgent.
- Note - Consensus no longer required as proposed solution is non breaking
InfoSec
- No new actions
CX
- Consensus from Energy Retailers is required to mark Issue #529 - CX - Energy Data Language Standards - NMI and Scheduled Payments as urgent.
Other
- MI11 RETRO: DSB to consider the adoption of a feedback loop from community to assist in the prioritisation of maintenance iteration candidates and advise.
Release plan
- Release 1.19.0 incorporating Decision Proposal 260 and Standards Maintenance Issue #529 has been published on 13/09/2022.
Open / Active Decision Proposals
The following decision proposals are open for community feedback
DP # | Decision Proposal | Closing date |
---|---|---|
Consultation | Decision Proposal 229 - CDR Participant Representation | Placeholder: no close date Link to consultation |
Noting Paper | Noting Paper 255 - Approach to Telco Sector Standards | Link to consultation |
Noting Paper | Noting Paper 258 - Independent Information Security Review | Link to consultation |
Consultation | Decision Proposal 260 - Energy Closed Accounts Feedback extended, now closes: 30th of August 2022 | Link to consultation |
Consultation | Decision Proposal 263 - Telco Accounts Payloads Feedback closes: 16th of September 2022 | Link to consultation |
Consultation | Decision Proposal 264 - Telco Invoice Payloads PLACEHOLDER | Link to consultation |
Consultation | Decision Proposal 265 - Telco Billing Transactions Payloads PLACEHOLDER | Link to consultation |
Consultation | Decision Proposal 266 - Telco Balance and Usage Payloads PLACEHOLDER | Link to consultation |
Consultation | Decision Proposal 267 - Telco Data Language Feedback closes: 15th of September 2022 | Link to consultation |
Future Plan
Review of July-September Quarter and new changes: https://github.com/ConsumerDataStandardsAustralia/future-plan/projects/1
Known Issues
open-status
is incorrectly specified as a query parameter forGet Energy Account Detail
API in version 1.19.0 of the standards.
Maintenance Iteration 12 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 discussed during this iteration are:
Domain | Issue # | Issue | Proposal Status | Change Proposed | Standards Staging link |
---|---|---|---|---|---|
MI 12 | Issue #530 | Iteration 12 Holistic Feedback | N/A | ||
CX | Issue #529 | CX - Energy Data Language Standards - NMI and Scheduled Payments | Breaking change - 15 Nov 2022 | This change has been approved by the Chair and will be incorporated into v1.19.0 | |
Register | Issue #409 | Dynamic Client Registration Response Time NFR | No Decision Taken | Convert to Decision Proposal: Look at this within the context of the uplift of all Register APIs | N/A |
Register | Issue #525 | softwareProductDescription should be marked as mandatory | Non-breaking change | Change the swagger to mark softwareProductDescription as mandatory | Staged |
InfoSec | Issue #411 | Clarification of x-fapi-interaction-id header | Non-breaking change | Clarify that the header is not to be used for unauthenticated APIs | Staged |
InfoSec | Issue #435 | Nominated representative end user for non-individual consumers | No Decision Taken | Carry over to Maintenance Iteration 13 | N/A |
InfoSec | Issue #447 | CORS typos in CDR | Non-breaking change | Fix documentation error | Staged |
InfoSec | Issue #458 | FAPI 1.0 Non Normative Examples | Non-breaking change | Add FAPI 1.0 aligned non-normative examples including for Authorization Code Flow | |
InfoSec | Issue #479 | Clarification on Minimum Algorithm Required for JARM | Options Presented | ||
InfoSec | Issue #522 | OpenID Provider Configuration End Point parameter requirements | No Decision Taken | Carry over to Maintenance Iteration 13 | |
InfoSec | Issue #533 | PKCE + PAR support for 16th September 2022 | Non Breaking Change | The proposal made is no change to the standards in support of Option 1 | N/A |
Banking | Issue #414 | Properties in BankingTransactionDetail objects | Non-breaking change | Swagger documentation fix | Staged |
Banking | Issue #462 | Make additional account attributes available in bulk | No Decision Taken | Convert to Decision Proposal: Look at the threshold and criteria for introducing new APIs | N/A |
Energy | Issue #477 | Secondary Data Holder Planned Outages and Status | Non Breaking Change | AEMO to host public Get Status and Get Outage endpoints. DH may choose to expose them if they wish |
N/A |
Energy | Issue #506 | Energy error codes for issues in data received by DH from SDH | TBC | Optional isSecondaryDataHolderError flag to be added to Error structure. Data Holders MAY implement this field on November 15 2022. Affected Data Holders MUST implement this field by April 7th 2023 |
|
Energy | Issue #524 | EnergyDerRecord - mandatory values not available in AEMO's DER register | Non Breaking Change | AEMO to provide default of 0 where value not available for nominalRatedCapacity and nominalStorageCapacity |
|
Energy | Issue #526 | Get DER for Service Point - allow for no data | Non Breaking Change | Define default values for mandatory fields in EnergyDerRecord structure allowing schema compliant response when DER record is not available |
|
Energy | Issue #475 | Representation of Spot price based contracts for C&I customers | No Decision Taken | Carry over to Maintenance Iteration 13 | |
Energy | Issue #520 | Stepped solar feed in tariffs in Energy | No Decision Taken | Carry over to Maintenance Iteration 13 |
Any Other Business
Meeting Minutes
Release management
Discussed the release of 1.19.0.
MI12 changes will be targetted for v1.20.0
Change Requests
The list of change requests that were consulted on this maintenance iteration were discussed with their current proposals and status summarised.
-
Issue #530: Iteration 12 Holistic Feedback
- Discussed that minor documentation defects will be staged over the next week
- Changes supported by participants
-
Issue #529: CX - Energy Data Language Standards - NMI and Scheduled Payments
- Incorporated into v1.19.0
-
Issue #409: Dynamic Client Registration Response Time NFR
- Re-iterated this will be dealt with as a future Decision Proposal
-
Issue #525: softwareProductDescription should be marked as mandatory
- Staged change is published for review
- Change supported by participants
-
Issue #411: Clarification of x-fapi-interaction-id header
- Staged change is published for review
- Change supported by participants
-
Issue #435: Nominated representative end user for non-individual consumers
- Carried over to MI 13 and a Decision Proposal will be created for introducing an Agent API
-
- Staged change is published for review
- Only adopted core change, not additional documentation comments
- Change supported by participants
-
Issue #458: FAPI 1.0 Non Normative Examples
- DSB to stage non-normative examples for review
- ANZ raised a request to raise a new Change Request to deal with new OIDD metadata parameters and DCR changes
- DSB to raise new change request to support OIDD / DCR changes
- This is a dependency for FAPI 1.0 Phase 3 go live
-
Issue #479: Clarification on Minimum Algorithm Required for JARM
- Participants supported definining a minimum set of signing algorithms: PS256, ES256 and EdDSA (see https://openid.bitbucket.io/fapi/fapi-2_0-security.html#section-4.4-1.1.2.2.1)
- Participants supported retaining support for JARM encryption but leave this to the discretion of DHs for now
- Partipants supported defining a minumum set of encryption algorithms but did not recommend a minimum set
- DSB to propose a minumum set of encryption algorithms for approval
-
Issue #522: OpenID Provider Configuration End Point parameter requirements
- No current consensus. This issue will carry over to MI 13
-
Issue #533: PKCE + PAR support for 16th September 2022
- Option 1 - cutover on Friday 16th September is recommended
- Change supported by participants
-
Issue #414: Properties in BankingTransactionDetail objects
- Staged change is published for review
- Change supported by participants
-
Issue #462: Make additional account attributes available in bulk
- Re-iterated this will be dealt with as a future Decision Proposal
-
Issue #475: Representation of Spot price based contracts for C&I customers
- This issue will be carried over to the next MI as no feedback was provided
-
Issue #477: Secondary Data Holder Planned Outages and Status
- AEMO is targeting a go-live next year. Most likely in line with tranche 2 (C&I) obligation dates
- Retailers currently aren't required to expose the secondary data holder outages but they may do so if they want to
- No change is required to the standards and the CR will be closed with no action taken if no further feedback is provided
-
Issue #506: Energy error codes for issues in data received by DH from SDH
- The proposed change which was defined in the last MI call was discussed. No further comments were made during the call.
- If no further feedback is receive the proposed changes be recommended to the Chair
-
Issue #520: Stepped solar feed in tariffs in Energy
- This issue will be carried over to MI 13 as no feedback was provided
-
Issue #524: EnergyDerRecord - mandatory values not available in AEMO's DER register
- AEMO raised that invertorDeviceCapacity also has the same issue and requires a default value to '0'
- DSB requested AEMO to comment against the ticket, which they have done
- If no further feedback is receive the proposed changes of defining default values where data is not available will be recommended to the Chair
-
Issue #526: Get DER for Service Point - allow for no data
- The proposed change, which was discussed and agreed by participants in last MI call, was revisited. No further comments were made during the call
- If no further feedback is receive the proposed changes be recommended to the Chair