DSB Maintenance Iteration 8: Agenda & Meeting Notes (25 August 2021) - ConsumerDataStandardsAustralia/standards GitHub Wiki

DSB Maintenance Iteration 8 - Agenda & Meeting Notes (2021-08-25)

Date and time: 25/08/2021, 2pm - 3pm AEST
Location: WebEx
Dial-in details:

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 202

Agenda

Meeting notes

Introductions

This week is the fourth and final call of the 8th maintenance iteration. The purpose of the meeting is to review resolved change requests and finalise change scope.

  • Allow 5 min for participants to join
  • Housekeeping
  • Overview, purpose and intended outcomes of the meeting

Actions

  • DSB to confirm designation of Digital Wallets
  • DSB to update Issue #240 with the outcome of discussions with the Treasury Rules team

Release plan

  • v1.11.0 was published on June 30th 2021 incorporating CX standards changes and the approved change requests from the 7th maintenance iteration
  • v1.11.1: Planned for release this week (beginning 23/08/2021). This release contains minor documentation errata
  • v1.12.0+: There is not v1.12.0 currently planned.

Open / Active Decision Proposals

The following decision proposals are open for community feedback

DP # Closing date DP
207 Closed [Noting Paper 207 - Draft v3 Rules Analysis
208 10/09/2021 Decision Proposal 208 - Binding NFRs
206 10/09/2021 Decision Proposal 206 - Register Standards
203 No closing date Normative Standards Review (2021)
200 No closing date Noting Paper 200 - Action Initiation Framework
183 Closed Decision Proposal 183 - Purpose Based Consents
182 Decision published Decision Proposal 182 - InfoSec Uplift for Write
158 Closed Decision Proposal 158 - Participant capability discovery

Future Plan

Review of Q3 and new changes: https://github.com/ConsumerDataStandardsAustralia/future-plan/projects/1

Iteration 8 Change Requests

All open change requests can be found here: Standards Maintenance Issues.

Open change requests:

Issue 396: Define new Digital Wallet Payee Type to relevant schemas

https://github.com/ConsumerDataStandardsAustralia/standards-maintenance/issues/396

291 - Credit card loyalty program data: significant gaps and lack of structure

https://github.com/ConsumerDataStandardsAustralia/standards-maintenance/issues/291

292 - Credit card balance plans and payment hierarchy: inadequate information within the CDS

https://github.com/ConsumerDataStandardsAustralia/standards-maintenance/issues/292

Change requests consulted

Issue No. Issue Title Current status
240 'SHOULD' for access token revocation No change
150 A loan may have no end date but loanEndDate is mandatory Limited feedback received, currently default to Option 4
394 Adding support for given names Documentation to be clarified. No change to standards
373 Confusing use of the term 'base path' In staging

Normative Standards Review

Any other business

Address any other business arising from the community





Meeting Minutes

Notes

  • Discussed change requests where a decision had been made
  • Limited supporting feedback provided to change request 150.
  • Change Request 394
    • Documentation will be updated to be clear DHs are permitted to return a single string value in the first_name field when they cannot separate into component given names

Other business

  • Access Token revocation

    • Discussed the InfoSec profile stating ADRs SHOULD revoke access tokens after collection of data and when deemed required in a security event identified by the ADR to minimise risk of malicious sharing of data
    • Westpac will create a change request
  • Pagination support - the standards require changes to better support cursors for returning large result sets.

    • ANZ will create a change request
  • 'profile' scope - the InfoSec standards permit the authorisation of the profile scope that shares some customer data. There are no corresponding CX data language standards to support this for ADR consent and DH authorisation

    • Cuscal will create a change request

Next Steps

⚠️ **GitHub.com Fallback** ⚠️