DSB Maintenance Iteration 5: Iteration Checkpoint: Agenda & Meeting Notes (28th October 2020) - ConsumerDataStandardsAustralia/standards GitHub Wiki
Date and time: 28/10/2020, 1pm - 2.00pm AEST (2pm - 3.00pm AEDT)
Location: WebEx
- https://csiro.webex.com/csiro/j.php?MTID=md498fcab7a2000cbb4b0072b4b266111
- Dial In Number: +61 2 6246 4433
- Dial In Access Code: 165 106 9550
- Quick Dial: +61262464433,1651069550%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 138
Agenda
- Introductions
- Outstanding Actions
- Change Requests For Discussion: change requests and decision proposals for discussion
- Any other business
Meeting notes
Introductions
- Allow for participants to join
- Housekeeping
- Overview, purpose and intended outcomes of the meeting
Actions
- (Done) DSB to seek request for urgent treatment of Issue #325
- (In Progress) ADR/DHs to confirm request for urgent treatment of Issue #325
- (In Progress) DSB to follow up with the ACCC regarding legal liabilities regarding access token revocation if this was changed to a SHOULD for Issue #240
- (In Progress) DSB to follow up with ADRs to get volume/frequency metrics for loss of refresh token issues regarding Issue #219
- (In Progress)DHs to provide implementation impact analysis for Issue #325
- (In Progress) DSB to publish consent lifecycle for input into Issue #175
- CBA to provide options for dealing with #315 - Obligation based standards
- DSB to request that the second concern in Issue #247 of an adjacent polling method be raised as a separate change request
- DSB to publish recent clarifications of going-forwards position on payload and end point versioning to Issue #311
For discussion
NPP update
- DSB / NPPA NDA in progress
- DSB access to NPPA technical documentation pending
Change Requests For Discussion
- #325: Future dated obligation for change to how audience is set for Data Recipients calling Data Holders
- #150: A loan may have no end date but loanEndDate is mandatory
- #219: Allow retrieval of current refresh_token by arrangement ID
- #320: [1.5.0] BPAY crnType introduced as mandatory and backported into existing version
- #315: Obligation date-based standards
Resolved Change Requests
CR # | Issue Title | Outcome | Status | Issue Link |
---|---|---|---|---|
#321 | DepositRateType - Valid list of enumerations | Clarification provided. Standards documentation to be updated to include clearer requirement | Documentation change | https://github.com/ConsumerDataStandardsAustralia/standards-maintenance/issues/321 |
#309 | paymentsRemaining cannot currently be 0 | Non-normative example to be fixed to show value of "1" | https://github.com/ConsumerDataStandardsAustralia/standards-maintenance/issues/309 | |
#300 | Alternate implementations for one-time consent | Standards documentation to be updated to support one-time collection and ongoing use | Change Supported | https://github.com/ConsumerDataStandardsAustralia/standards-maintenance/issues/300 |
#307 | Make Metrics API Brand Aware | CR closed by creator | No Change | https://github.com/ConsumerDataStandardsAustralia/standards-maintenance/issues/307 |
Error URN structure
- Update on progress
- Approach and timeframes
Discovery Service
- Request for requirements elicitation
- Key business problems to solve
Open Change Requests For Consultation
This is the list of change requests and Decision Proposals under consultation through this iteration
Decision Proposals
- Enhanced Error Handling: #119, #120, #121, #122 and #127
- Discovery Service (see DP #135) - DP TBA
- Metrics and Reporting roadmap + Metric API v2 - DP TBA
Any other business
For discussion
Change Requests
The following change requests have been proposed for this iteration:
- #152: CRN in BankingBillerPayee should be optional
- #320: [1.5.0] BPAY crnType introduced as mandatory and backported into existing version
- #229: Service field in the Get Transaction Details API / #181
- #300: Alternate implementations for one-time consent
- #175: Premature Completion of Consent (Hybrid) Flow
- #219: Allow retrieval of current refresh_token by arrangement ID
- #240: 'SHOULD' for access token revocation
- #325: Future dated obligation for change to how audience is set for Data Recipients calling Data Holders
- #307: Make Metrics brand aware
- #315: Obligation based standards
- #150: A loan may have no end date but loanEndDate is mandatory
- #301: Consider changing BankingScheduledPayment to allow the capture of multiple nicknames and payeeReferences
- #309: paymentsRemaining cannot currently be 0
- #310: [1.4.0] BankingProductFee feeType adds Variable which is a new payload version
- #318: [1.5.0] Missing Changelog Item: (Nearly) All Enumerations Reordered
- #319: [1.5.0] Missing Changelog Item: Maturity Instructions
- #321: [1.5.0] Clarification of future obligation dates
- #247: ADR Revocation Endpoint
Meeting Minutes
Notes
TBA
Other business
TBA
Next Steps
Actions
TBA