DSB Maintenance Iteration Agenda & Meeting Notes (2020 03 12)

DSB Maintenance Iteration Agenda & Meeting Notes (2020-02-13)

Date and time: 12/03/2020, 2pm - 3pm AEDT (1pm - 2pm AEST) Location: WebEx

• https://csiro.webex.com/csiro/j.php?MTID=mc79426491aed32ee54e2121dcdb32d0a
• Dial In Number: +61 2 6246 4433
• Dial In Access Code: 780 996 986
• Quick Dial: +61262464433,780996986%23%23

Chair: Mark Verstege, DSB
Maintenance overview: Further information
Maintenance project board: See here

Agenda

• Introductions
• Roll call
• Outstanding actions
• Update on Decision Proposals
• Update on iteration Change Requests
• For discussion: Community input on scope for next iteration
• Any other business

Meeting notes

• Meeting Notes
• Next steps

Introductions

• The primary objective this iteration is to resolve change requests for Product Reference Data (PRD) and Banking endpoints.

Actions

• No outstanding actions

Decision Proposals

The following decision proposals were socialised for consultation this iteration. The feedback is currently under review and updated decision records are being developed.

Note: initial feedback closed at the end of February.

Decision #	Decision
#89	Decision Proposal 089 - Direct Consumer Access
#97	Decision Proposal 097 - Principles Review
#99	Decision Proposal 099 - Concurrent Consent Target State

Issues

The list of change requests addressed in this iteration for discussion:

Issue #	Issue	Proposal	Comments
#30	APCA Number is specified as String but is a Number	No change	Supported
#48	Inclusion of repaymentType in the Product detail API	Change - spec	Supported
#55	Specify the type of sharing_duration claim as a number in the normative standards	No change	Supported - this is already addressed in v1.2.0
#58	Further specify ID Token encryption algorithms	Change - doc	Supported
#64	Support URI Encoded Images in Payloads	No change	Supported
#65	V1.1.0: RateString bounding	No change	Supported
#66	V1.1.0: lastWeekDay change is a new version	No change	Supported
#79	New constraint type for product detailed and account detailed endpoints	No change	Further discussion required
#86	BankingTermDepositAccount maturityInstructions described as String when Enum	No change	Supported
#102	Missing x-cds-client-headers in Get Transactions For Account definition	Change - doc	Supported
#103	Remove ProductRateTier.subTier object used in Get Product Detail	Change - spec	Supported with future dated obligation post-July
#107	Add additionalInfo and additionalUri properties to ProductRateTier	Change - spec	Supported
#137	x-fapi-interaction-id usage	Change - doc	Supported

Notes

Iteration scope review

• Issue #103 is supported to remove subTier however it is noted that some banks are currently relying on subTier as part of their Product Reference Data (PRD) implementations. Instead of making this change applicable for the Get Product v2 obligations for July 2020, the preference is to make this a versioned change to PRD beyond v2 and have a future dated obligation later than July
• CBA is currently drafting a response for Issue #79. A request was made to defer this change request to the next iteration to allow CBA to provide a response. This has been accepted and the change request will remain open and roll over into the next maintenance iteration.

Scope for next maintenance iteration

• Request was made to prioritise the creation of a Decision Proposal for Tiered fees in Product Reference data. This will be considered as part of backlog grooming for the next iteration

Other business

• A new DSB-led Data Holder series will be established from Thu March 19th. This will replace the ABA led meetings and is open to all interested parties but specifically it is a forum for Data Holders to raise questions and receive updates - invitations will be issued in the coming days
• A Data Recipient series will be established shortly after the Data Holder series

Next Steps

• A solution for concurrent consent arising from Decision Proposal 99 consultation is underway. This will also cover questions raised in Issue #57. Expectation is that community consultation on this solution will commence within 1-2 weeks
• The scope for Maintenance Iteration #2 was well supported - the next week is the documentation of the scope for Data Standards Chair approval within a Decision Proposal
• Subsequently implementation of the approved scope into the data standards will be conducted within the next fortnight