Skip to content

DSB Maintenance Iteration 5: Final Checkpoint: Agenda & Meeting Notes (12th November 2020)

Jump to bottom
CDR API Stream edited this page Nov 17, 2020 · 7 revisions

Date and time: 12/11/2020, 1pm - 2.00pm AEST (2pm - 3.00pm AEDT)
Location: WebEx

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

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
  • (Done) ADR/DHs to confirm request for urgent treatment of Issue #325
  • (Done) CBA to provide options for dealing with #315 - Obligation based standards
  • (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
  • 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

General updates

NPP update

  • DSB / NPPA NDA complete
  • DSB access to NPPA technical documentation pending

Audience Claim Issue 325

  • Consultation on DP325 closes COB Monday 16/11/20
  • Current plan is to create v1.6.0 of the data standards to address this urgent change, only.

Change Requests For Discussion

  1. #315: Obligation date-based standards
    • For discussion
      • InfoSec versioning - profile level or section?
      • Future dated obligation table changes
      • Draft implementation branches and public staging repository
  2. #300: Alternate implementations for one-time consent
    • Proposal: Adopt maximum 24 hour sharing duration to be allowed for one-time consent for separation of collection and use
    • For Discussion:
      • Intent is to make it clear what one-time collection is but this doesn't preclude ongoing data sharing use cases having overlapping sharing durations
      • Is there a better way to describe in the standards the distinction between consent, collection and use. e.g. one-time consent to collect vs ongoing consent to collect?
    • Assumption: This is a non breaking change
  3. #325: Future dated obligation for change to how audience is set for Data Recipients calling Data Holders
    • Proposal: Decision Proposal posted to #325. For walkthrough and discussion
  4. #301: Consider changing BankingScheduledPayment to allow the capture of multiple nicknames and payeeReferences
  5. #318: [1.5.0] Missing Changelog Item: (Nearly) All Enumerations Reordered
    • Proposal: strictly order all enums by natural sort order
  6. #219: Allow retrieval of current refresh_token by arrangement ID
  7. #320: [1.5.0] BPAY crnType introduced as mandatory and backported into existing version

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" Documentation change 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
#312 Implement Redirects for old Consumer Data Standards links URL redirection has been fixed Change adopted https://github.com/ConsumerDataStandardsAustralia/standards-maintenance/issues/312

#301 Consider changing BankingScheduledPayment to allow the capture of multiple nicknames and payeeReferences

See GitHub Standards-Maintenance issue #301

#320 BPAY crnType introduced as mandatory and backported into existing version

See GitHub Standards-Maintenance issue #320

Any other business

For discussion

Open Change Requests

The following change requests have been proposed for this iteration:

  1. #152: CRN in BankingBillerPayee should be optional
  2. #320: [1.5.0] BPAY crnType introduced as mandatory and backported into existing version
  3. #229: Service field in the Get Transaction Details API / #181
  4. #300: Alternate implementations for one-time consent
  5. #175: Premature Completion of Consent (Hybrid) Flow
  6. #219: Allow retrieval of current refresh_token by arrangement ID
  7. #240: 'SHOULD' for access token revocation
  8. #325: Future dated obligation for change to how audience is set for Data Recipients calling Data Holders
  9. #307: Make Metrics brand aware
  10. #315: Obligation based standards
  11. #150: A loan may have no end date but loanEndDate is mandatory
  12. #301: Consider changing BankingScheduledPayment to allow the capture of multiple nicknames and payeeReferences
  13. #309: paymentsRemaining cannot currently be 0
  14. #310: [1.4.0] BankingProductFee feeType adds Variable which is a new payload version
  15. #318: [1.5.0] Missing Changelog Item: (Nearly) All Enumerations Reordered
  16. #319: [1.5.0] Missing Changelog Item: Maturity Instructions
  17. #321: [1.5.0] Clarification of future obligation dates
  18. #247: ADR Revocation Endpoint

Meeting Minutes

Notes

TBA

Other business

TBA

Next Steps

Actions

TBA

Getting Started

Meetings

Maintenance Iterations

CDR Implementation Call

Clone this wiki locally