DSB Maintenance Iteration 12: Agenda & Minutes (3 August 2022) - ConsumerDataStandardsAustralia/standards GitHub Wiki
Date and time: 03/08/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: James Bligh, 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 second in the series for Maintenance Iteration 12. The purpose is to discuss each change request proposed for the iteration to agree on the candidates that will be consulted on.
Outstanding Actions
Energy
- DSB/AEMO Issue #477 DSB and AEMO to meet offline and agreed on an FDO for Issue 477.
- Consider in MI12
- Retailers to raise a ticket on energy usage data covering multiple FRMPs. DSB to table this in their discussions with AEMO.
- Analysis ongoing
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.
- Waiting on advice
- CBA to raise a change request to drop encryption for the JARM token response. Issue #458
- Waiting on advice
Register
- ACCC and DSB to post a response on issue #486 that describes default behaviour on how versioning will work.
- DSB to include v1 of Get Software Statement Assertion (SSA) in the Endpoint Version Schedule as a deprecation date has not been set for this version to facilitate changes associated to #486.
- DSB to investigate original proposals in Issue #427 to consider how to progress issue #480
- Consider in MI12
Other
- DSB to list CRs proposed for MI12 and once confirmed post on DP259 for the community to comment.
- MI11 RETRO: DSB to consider the adoption of a feedback loop from community to assist in the prioritisation of maintenance iteration candidates and advise.
- MI11 RETRO: DSB to consider a process to summarise the current position on a change request as it is iterated on to avoid confusion and advise.
- MI11 RETRO: Chair will monitor the MI12 holistic thread to determine value for future MIs and extract any contributions that warrant being considered under a separate CR.
- Issue #530 has been raised for this iteration
Release plan
- Decision Proposal 249: Maintenance Iteration 11 has been sent to DSAC for review. The team is working on staging the change requests for community review. Version 1.18.0 of the standards will be published following the Chair's approval.
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 |
Consultation | Decision Proposal 256 - Telco Endpoints Feedback closes: 5th of August 2022 | Link to consultation |
Consultation | Decision Proposal 257 - Customer Data Payloads for Telco Feedback closes: 5th of August 2022 | Link to consultation |
Noting Paper | Noting Paper 258 - Independent Information Security Review | Link to consultation |
Consultation | Decision Proposal 260 - Energy Closed Accounts Feedback closes: 18th of August 2022 | Link to consultation |
Consultation | Decision Proposal 262 - Telco Product Reference Payloads PLACEHOLDER | Link to consultation |
Consultation | Decision Proposal 263 - Telco Accounts Payloads PLACEHOLDER | 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 |
Future Plan
Review of July-September Quarter and new changes: https://github.com/ConsumerDataStandardsAustralia/future-plan/projects/1
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 proposed for this iteration are:
- Issue #414 - Properties in BankingTransactionDetail objects
- Issue #525 - softwareProductDescription should be marked as mandatory
- Issue #526 - Get DER for Service Point - allow for no data
- Issue #524 - EnergyDerRecord - mandatory values not available in AEMO's DER register
- Issue #506 - Energy error codes for issues in data received by DH from SDH
- Issue #477 - Secondary Data Holder Planned Outages and Status
- Issue #480 - 1.13.0 appears to have broken pseudonymity of Pairwise Identifiers
- Issue #484 - 1.13.0 Appears to have introduced new SSA error behaviours
- Issue #529 - CX - Energy Data Language Standards - NMI and Scheduled Payments
- Issue #409 - Dynamic Client Registration Response Time NFR
- Issue #411 - Clarification of x-fapi-interaction-id header
- Issue #447 - CORS typos in CDR
- Issue #458 - FAPI 1.0 Non Normative Examples
- Issue #475 - Energy - Representation of Spot price based contracts for C&I customers
- Issue #520 - Stepped solar feed in tariffs in Energy
- Issue #435 - Nominated representative end user for non-individual consumers
- Issue #462 - Make additional account attributes available in bulk
- Issue #530 - Iteration 12 Holistic Feedback
Any Other Business
Meeting Minutes
Notes
Maintenance Iteration 12 Issues
Scope
- DSB provided an overview of all issues selected as candidates for MI12 consideration
- ANZ requested Issues #479 and #522 be included in scope
- Overlap to Issue #458 - FAPI 1.0 Non Normative Examples
- This was accepted - the items will be incorporated into MI 12 scope
- All other items were agreed for consultation
Issues discussed
-
Issue #529 - CX - Energy Data Language Standards - NMI and Scheduled Payments
- Has impact to consumer comprehension of consent
- This means there is impacts to consider for November 15 2022 scope
- DSB raised two options:
- (1) Assign a future FDO to the change of data language and go-live with reduced consumer comprehension
- (2) Accept the data language changes for implementation in November to improve consumer comprehension. (2) was preferred subject to industry feedback
- Feedback is also invited on the language being proposed for the change
-
Issue #526 - Get DER for Service Point - allow for no data
- Up to 80% of Service Point IDs do not have a DER record.
- As such there is critical impact to November go-live for energy
- Clarity required on the error handling where no DER record is available for a given servicePointId
- Considered an urgent change to clarify for November
- 200 OK is not possible because a schema compliant response cannot be constructed
- Discussed 404 Not Found as a response code. This would be appropriate given the requested resource (the DER) is not available for the requested servicePointId.
- A new CDR Error Code would need to be defined
- Alternative error response floated was 204 No Content
-
Issue #524 - EnergyDerRecord - mandatory values not available in AEMO's DER register
- A small proportion of DERs do not have a
nominalRatedCapacity
and/ornominalStorageCapacity
- From an energy-sector perspective capacity must be a number > 0
- From a data standards perspective, a schema compliant response is a "number" hence a value of "0" could be given
- Discussed what to do where the capacity is not available. Currently this is a mandatory field
- Three options: (1) don't return a record at all, (2) Return a default of "0" with defined meaning, (3) Change the mandatory requirement to be conditional
- (3) loses meaning (it is unknown why the value is omitted)
- (2) would require a definition change to describe the allowance for a "0" value and the specific meaning attached. This would be the least impact change. Currently a "0" value would be schema compliant
- (1) would be least desirable because the entire record would not be available.
- A small proportion of DERs do not have a
-
Issue #506 - Energy error codes for issues in data received by DH from SDH
- No candidates yet identified
- CR will remain open for industry to propose any relevant error scenarios requiring specific error handling
-
Issue #477 - Secondary Data Holder Planned Outages and Status
- Discussed the issue and requested feedback from secondary DHs
-
Issue #475 - Energy - Representation of Spot price based contracts for C&I customers
- Some participants suggested de-scoping the issue
- DSB clarified that C&I data is included in Phase 2 data sharing for May 2023. De-scoping this issue would reduce implementation timeframes but it would not change the obligation for data holders that is set out in the rules. Not addressing the change in MI 12 would only increase risk to DHs of being non-compliant in May 2023
- Because contracts for C&I customers can be based on the energy spot price, options to deal with this within the data standards are being considered.
- DSB stated they would need industry input to understand how spot price based contracts are structured to help identify solution options
- DSB will raise this at the energy AEC meeting
-
Issue #520 - Stepped solar feed in tariffs in Energy
- DSB will progress this issue and propose options for consultation
Other Business
- No other business was identified
New Actions
- DSB to raise "Issue #475 - Energy - Representation of Spot price based contracts for C&I customers" at the next AEC meeting
-
DSB to propose options to "Issue #475 - Energy - Representation of Spot price based contracts for C&I customers" - DSB will progress "Issue #520 - Stepped solar feed in tariffs in Energy" and propose options for consultation
Next Steps
Not applicable.