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

• https://treasuryau.webex.com/treasuryau/j.php?MTID=md2844e32bbac294d42779fead7663f79
• Dial In Number: +61 2 9338 2221
• Dial In Access Code: 165 569 9964
• Quick Dial: +61293382221,,1655699964%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 202

• Introductions

• Outstanding Actions

• Release plan: schedule of forwards looking standards releases

• Open Decision Proposals: key consultation dates

• Standards Release Process

• Iteration 8 Change Requests

• Normative standards review

• Any other business

Meeting notes

• Meeting Notes
• Next steps

This week is the second call of the 8th maintenance iteration. The purpose of the meeting is to review the open change requests and solution options.

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

• DSB to add Issue 396 to the agenda

• v1.11.0 was published on June 30th 2021 incorporating CX standards changes and the approved change requests from the 7th maintenance iteration
• v1.12.0+: There is not v1.12.0 currently planned.

The following decision proposals are open for community feedback

DP #	Closing date	DP
207	24/08/2021	[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	Closed	Decision Proposal 182 - InfoSec Uplift for Write
158	Closed	Decision Proposal 158 - Participant capability discovery

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

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

For discussion in this call:

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

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

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

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

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

• FAPI 1.0 Part 1
• FAPI 1.0 Part 2
• PAR Draft 09

Address any other business arising from the community

---

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

  • Represents a different payee type for digital wallet payments
  • The payee may be an individual, business or sole trader
  • The payee may be a domestic or international payee
  • The change request only represents PayPal digital wallet payees, but other digital wallet schemes are possible.
  • Representing the wallet type would make this applicable beyond just PayPal digital wallets
  • Similar in representation to the BankingDomesticPayeePayId
  • DigitalWalletPayeeAccountID is unique to the "customer" of the data holder (where customer is defined under the CDR Federation section of the standards)
  • A customer can have only one digital wallet
  • A digital wallet can be owned by only one customer
  • A digital wallet may have multiple bank accounts attached to it
  • DSB to check the Rules and CDR designation to determine whether digital wallets can be fully represented in this way

• Issue #291: Credit card loyalty program data: significant gaps and lack of structure

  • Carried over to the next at the request of the original poster because they were unable to present

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

  • Carried over to the next at the request of the original poster because they were unable to present

• Issue #240 - 'SHOULD' for access token revocation

  • DSB is meeting with the Treasury Rules team end of this week to follow up on the outstanding action regarding legal/liability questions
  • A follow up will be provided by the DSB team to progress the change request

• Issue #150: A loan may have no end date but loanEndDate is mandatory

  • No further issues raised
  • Requires feedback from data holders to progress to a decision

• Issue #394: Adding support for given names

  • If no data standards change is recommended, WBC would support additional clarification in the description field for the firstName and middleName elements where the DH holds all given names as a single string and decomposition into component names cannot be determined (example C3). DSB will create a ZenDesk support article articulating the examples and interpretation of the standards pending the outcome of the change request

• Issue #373: Confusing use of the term 'base path'

  • No issues raised with the change presented
  • Next step is to progress to standards staging

• Issue #388: Typo in TRADE FINANCE enum in Product Categories table

  • New issue was raised and brought into the iteration candidates - documentation defect

• No other business

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