DSB Maintenance Iteration 4: Iteration checkpoint: Agenda & Meeting Notes (5th August 2020) - ConsumerDataStandardsAustralia/standards GitHub Wiki
Date and time: 5/08/2020, 2pm - 3pm AEST Location: WebEx
- https://csiro.webex.com/csiro/j.php?MTID=m1a847c216c0578e19845184f08cdd878
- Dial In Number: +61 2 6246 4433
- Dial In Access Code: 165 673 5848
- Quick Dial: +61262464433,1656735848##
Chair: Mark Verstege, DSB
Maintenance overview: Further information
Maintenance project board: See here
- Introductions
- Outstanding Actions
- Release 1.4.0: progress update to v1.4.0 release
- Iteration Candidates: walkthrough review of issues for this iteration
- Any other business
Meeting notes
- Allow for participants to join
- Housekeeping
- Overview, purpose and intended outcomes of the meeting
- DONE NAB analysis of NPP changes required for https://github.com/ConsumerDataStandardsAustralia/standards-maintenance/issues/229
- WBC analysis of NPP changes for https://github.com/ConsumerDataStandardsAustralia/standards-maintenance/issues/229
Decision Record for Release 1.4.0 is available here. Scope includes:
- Maintenance Iteration 3
- Prioritised change requests to support July go-live
- Documentation fixes including non-normative examples
Open
Under Review
- Enhanced Error Handling, Payload Structure: Decision proposal 119
- Enhanced Error Handling, Identification of additional HTTP Status Codes: Decision proposal 122.
- Enhanced Error Handling, Application of HTTP Status Codes: Decision proposal 121.
- Enhanced Error Handling, Error Catalogue: Decision proposal 120.
Iteration Summary
- Iteration candidates were identified in the kickoff call.
- Project board: https://github.com/ConsumerDataStandardsAustralia/standards-maintenance/projects/3
- Feedback required on several CRs to understand supported options and considerations
- The prioritised list of iterations candidates was supported. The final scope for the iteration adopted is available here: https://github.com/ConsumerDataStandardsAustralia/standards-maintenance/projects/3
- Analysis of NPP change request is being considered by WBC and further analysis will be posted to #229 in the coming fortnight.
# | Change Request | Status | Recommendation |
---|---|---|---|
#42 | ANZSIC Code multiple version support | Pending | Discuss WBC & DSB feedback. |
#153 | Maturity instructions for a term deposit may not always be known | In principle support | Discuss WBC feedback. |
#150 | A loan may have no end date but loanEndDate is mandatory | Pending | Awaiting WBC feedback |
#151 | A payee may have no nickname provided by the customer | Supported | Keep mandatory and change description to be "determined by the Data Holder in line with existing digital banking channels" |
#152 | CRN in BankingBillerPayee should be optional | Pending | Discuss feedback. Is there an option to provide the type of CRN if ICRN of VCRN is known? Whilst conditional, an empty string would still satisfy the standards where an ADI allows BPAY payees to be saved by customers in a payee address book without a CRN. Do any banks support saving BPAY billers without a CRN? |
#176 | Update Query Parameter Transaction | Pending | Discuss community feedback. |
#177 | Negative Available Balance in Get Balances response | Pending | Further feedback required. Currently no support from other ADIs |
#229 | Service field in the Get Transaction Details API | Pending | Awaiting analysis and community feedback. Review NAB feedback. |
#271 | Update Get Metrics rejections counts and clarify affected APIs | Provisional | Option C - authenticated AND unauthenticated rejection counts. Recommend this treats the existing rejections as the authenticated rejection count so no breaking change is introduced to current implementations. unauthenticatedRejections is introduced for rejections on unauthenticated endpoints. Would require a future dated obligation |
#240 | 'SHOULD' for access token revocation | In Consultation | For discussion. Refer to https://tools.ietf.org/html/rfc7009#section-3 |
#273 | Update claims permitted in Token Introspection | In Consultation | For discussion |
#272 | Transition arrangements for November 2020 CDR Consent obligations | Pending | For discussion |
#266 | Decrement BankingProduct | Not supported | This change to increment BankingProduct was intentional to align with BankingProductDetail
|
#247 | ADR Revocation Endpoint | In Consultation | For discussion |
Issue #42: ANZSIC Code multiple version support
- Support for including a version enumeration as an optional parameter
- Agreed to clarify which version of each standard is considered the baseline rather than support all possible legacy versions
- No support for backwards compatibility of older versions
- Set baselined versions as ANZSCO_1220.0_V1.3 and ANZSIC_1292.0_V2.0 or ANZSCO_1220.0_V1.0 and ANZSIC_1292.0_V1.0
Issue #153: Maturity instructions for a term deposit may not always be known
- Support for maintaining maturityInstructions as mandatory
- Support for changing description to include default maturity instructions
- Support for extending the enumerated type to include "HOLD"
- Consultation will be requested if an optional
isMaturityInstructionsDefaulted
which itself defaults tofalse
should be included to differentiate between a bank's default instructions (if the customer has not explicitly provided maturity instructions) versus a customer's explicit instructions
Issue #150: A loan may have no end date but loanEndDate is mandatory
- WBC to provide further update to this change request
- Requires further detail before the CR can be progressed
Issue #151: A payee may have no nickname provided by the customer
- Updated description to support default values is supported
- Supported that this is a display name which is either the customer entered nickname or a display name derived by the bank for the purposes presenting payees in digital banking channels
Issue #152: CRN in BankingBillerPayee should be optional
- Further analysis required by banks. It was mentioned that at least one bank allows billers to be created in a payee address book without CRNs
- In this case, ICRN and VCRN may be better off represented as an enumerated type with conditional optionality for the CRN in only those situations
Issue #176: Update Query Parameter Transaction
- Some banks have said they are supporting text filtering including both majors and non-majors
- Discussed options. Option A - do nothing was supported: address this issue in future if/when additional conditional filtering is required in the future.
Issue #177: Negative Available Balance in Get Balances response
- Issue of negative available balances was discussed. Other than CBA, no other banks have provided support for negative available balances
- This change will not be supported. The description for available balance will be updated to make it clear that available balance should be zero or greater.
Issue #229: Service field in the Get Transaction Details API
- Still waiting for analysis from banks.
Issue #271: Update Get Metrics rejections counts and clarify affected APIs
- Option C is supported. This would introduce rejection counts for unauthenticated endpoints.
- Needs to consider future dated obligations
- DSB to propose representation options on GitHub
Issue #240: 'SHOULD' for access token revocation
- Previous guidance has been that access tokens must be able to be revoked in cases where an ADR, for security reasons, needs to invalidate an access token without revoking consent
Issue #273: Update claims permitted in Token Introspection
- Item raised for ongoing consultation
- No objections have currently been raised with the proposal
Issue #272: Transition arrangements for November 2020 CDR Consent obligations
- Item raised for ongoing consultation
Issue #266: Decrement BankingProduct
- Item raised for ongoing consultation
Issue #247: ADR Revocation Endpoint
- Item was not discussed
TBA
—