-
Notifications
You must be signed in to change notification settings - Fork 56
Maintenance Iteration Meeting Agenda & Notes 2020_02_13
CDR API Stream edited this page Feb 17, 2020
·
1 revision
Date and time: 13/02/2020, 2pm-3pm AEDT
Location: WebEx
- https://csiro.webex.com/csiro/j.php?MTID=m1271d08eb37e3d4380bbcc546b42f80a
- Dial In Number: +61 2 6246 4433
- Dial In Access Code: 785 851 394
- Quick Dial: +61262464433,785851394%23%23
Chair: Mark Verstege, DSB
Maintenance overview: Further information
Maintenance project board: See here
- Introductions
- Roll call
- Outstanding actions
- Review issues candidates
- For discussion: consideration of Adoption of JARM and Adoption of detached signatures
- Community request for any other candidates
- Any other business
- Primary objective this iteration is to resolve change requests for Product Reference Data (PRD) and Banking endpoints.
- Request for review of Standards Decision Proposals (close end of February)
| Decision # | Decision |
|---|---|
| #99 | Decision Proposal 099 - Concurrent Consent Target State |
| #97 | Decision Proposal 097 - Principles Review |
| #89 | Decision Proposal 089 - Direct Consumer Access |
The provisional list of iteration change request candidates for discussion:
Two InfoSec issues are under consideration and feedback from the community is welcomed on their inclusion in this iteration.
| Issue # | Issue |
|---|---|
| #7 | Adoption of JARM |
| #8 | Adoption of detached signatures |
- There were requests from WBC to prioritise Issues #55 and #51. Mark to confirm if these have already been covered under the v1.2.0 release and can be closed
- Rabobank asked for clarification on #94 Clarification of rate presentation and use of subTier. At present, there are two ways that tiering can be modelled. Sub-tiering was added originally to support parent/child relationship for tiering. The big 4 have preferred to go with a flat structure response to tiering. We advised Rabobank to look at existing implementations and go with the preference for flat representation. Given that subTiering is optional, this is not a material change in future iterations. Nevertheless I will review the associated CR in issue #103 to see if it makes sense for inclusion in the iteration.
- There was discussion about Error Handling. Request from the community is welcomed - the current position which is supported by WBC is to wait and see how holders implement. Everyone on the call recognises the need for comprehensive error handling documentation however the rationale is to wait and see what issues are faced during implementation, especially as the non-majors start to look at implementation. It would be premature to define error scenarios until we see the specific use cases for error handling in production and ability to confer with the non-majors because error handling tends to be different based on perspective and existing API conventions
- Community asked for feedback on the inclusion of two InfoSec issues #7 Adoption of JARM and #8 Adoption of detached signatures. Both of these were recommendations from the Fortian review of the CDS. The feedback was these are important but would impact current delivery and the preference is to defer to a future iteration after go-live. This is supported by the DSB. It will allow us to review the position, provide options and consult with the community to define a future change to the standards.
- WBC requested prioritisation of Issue #101 (Changes to align to FAPI and OIDF Specifications Round 2) but after go-live.
- Three Decision Proposals (Concurrent Consent; Principles Review; Direct to Consumer Requests) are open for consultation on the standards repository
- Iteration candidates will remain open for consultation until Thursday 27/02/2020
- Next meeting 12/03/2020