DSB Maintenance Iteration 7: Agenda & Meeting Notes (23rd June 2021)
Date and time: 23/06/2021, 2pm - 3pm AEST
Location: WebEx
Dial-in details:
- https://csiro.webex.com/csiro/j.php?MTID=m64ff82797cdd2fb0779c845915fffcea
- Dial In Number: +61 2 6246 4433
- Dial In Access Code: 154 143 2512
- Quick Dial: +61262464433,1541432512%23%23
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 178
-
Release plan: schedule of forwards looking standards releases
-
Open Decision Proposals: key consultation dates
-
Iteration 7 Issues: Change requests for review
-
Normative standards review process
-
Any other business
Meeting notes
The purpose of the call this week is to review the in flight change requests and conclude the maintenance iteration. The meeting will also review the process for consulting on the Future Plan's Normative Standards Review issue.
- Allow 5 min for participants to join
- Housekeeping
- Overview, purpose and intended outcomes of the meeting
- DSB to raise a Decision Proposal cover the Normative References Review item in the DSB's Future Plan.
The following release plan provides an upcoming view of the changes to be released:
-
v1.10.0 was release June 1st.
-
v1.11.0 Changes arising from DP160 and DP187, targeting pre-July
- DP160 (consultation closed)
- Updates to unavailable account standard for non-individuals, partnerships, secondary users
- Secondary user instruction withdrawal standard
- DP187 (consultation closing 18 June)
- Disclosure consent standard
- Update to ADR consent standard
- Disclosure consent withdrawal standard
- DP160 (consultation closed)
-
v1.11.0+: Adopted Maintenance Iteration changes
The following decision proposals are open for community feedback
| DP # | Closing date | DP |
|---|---|---|
| 186 | 02/07/2021 | Decision Proposal 186 - Engineering Support |
| 182 | 09/07/2021 | Decision Proposal 182 - InfoSec Uplift for Write |
| 183 | Pending | Decision Proposal 183 - Purpose Based Consents |
The following changes have been staged for review:
| Change Request | Recommendation | Impact | Details |
|---|---|---|---|
| transactionId conditional documentation | Adopt change. | No breaking changes. Documentation clarification. |
Change Request: Update the description for transactionId to include "Mandatory if isDetailAvailable is set to true". Context: This makes the implied requirement explicit and clear. It doesn't change or affect existing implementations. |
| financialInstitution should be marked as conditionally required | Don't adopt, but correct documentation bug. | Non breaking change |
Change Request: Introduce a new data field to denote when financialInstitution is not populated due to card scheme payment Context: Feedback during the iteration calls suggested improvements by Visa and other card schemes may make it possible to populate the financialInstitution in future. |
| Clarify alignment of lastUpdateTime in CommonPerson schema and updated_at claim | No change | No impacts |
Change Request: Make lastUpdateTime mandatory Context: The standards are correct as published |
| Remove redundant future dated obligations | Adopt change | Non breaking changes. Documentation clarification. |
Change Request: Remove references in the standards to obligations in the past Context: Removes legacy obligation statements more than 3 months older than the current release of the standards. |
| Typos in HTTP Headers documentation | Adopt | Non breaking change | Documentation fix |
| Fix typos in CX Standards | Adopt | Non breaking change | Documentation fix |
| Levels of Assurance (LoAs) navigation bug | Adopt | Non breaking change | Documentation fix |
| Documentation bug: 422 error codes - description should refer to request body not URI | Adopt | Non breaking change | Documentation fix |
| Minor typo in Product Fee Types documentation | Adopt | Non breaking change | Documentation fix |
| Error Response Structure - Does it contain "description" or "detail"? | Adopt | Non breaking change | Documentation fix |
The following changes did not have sufficient feedback:
-
Addition of enums for extensionUType and service in extendedData - BankingTransactionDetail
- https://github.com/ConsumerDataStandardsAustralia/standards-maintenance/issues/181
- https://github.com/ConsumerDataStandardsAustralia/standards-maintenance/issues/229
- Change Request: Add support for other NPP service overlays such as X2P2 and X2P3
- Recommendation: No change.
- Impact: No impacts.
- Context: NPPA have advised that X2P2 and X2P3 are not yet defines as the NPP's Mandated Payment Service was priorities. No banks provided further details to the contrary.
- There has been other discussion around providing better representation of existing payment schemes for instance, expanding transaction detail to clearly differentiate the payment schemes. Should this work be progressed instead?:
- BPay: BPAY reference id
- Traditional payments: BSB, Account Number etc
- International payments: Routing codes, payment instructions, intermediaries etc.
- NPP payments distinguished by service name and service version
- Internal Transfers: Source/Destination account
- Card payments
The following changes were not addressed:
Link to the normative standards review can be found here: https://github.com/ConsumerDataStandardsAustralia/standards-maintenance/tree/master/reviews.
FAPI 1.0 Part 1 analysis is now available.
Address any other business arising from the community
- Reviewed changes proposed to the data standards. No changes opposed.
- Reviewed FAPI 1.0 Part 1 analysis
- No other business
- DSB to raise the change requests for upstream spec analysis