Table of Contents
Date/Time
Attendees
| Name | Organisation | Role |
|---|---|---|
| Refinitiv | Chair | |
| Refinitiv | ||
| Espen Overbye | OpenFin | |
| Johan Sandersson | FactSet | |
| Ben Gold | Wellington | |
| Rob Underwood (Deactivated) | FINOS | |
| Tosha Ellison | FINOS | |
Action Items
Tasks Identified and Assigned
- Use case owners should move "Accepted" use cases to the GitHub repository.
- Jonathan Teper add agenda item for next meeting to discuss management of use cases not in "Accepted" status.
- Former user (Deleted) to set up an "in person" meeting in London to progress some Use Case work (geared towards those already in London)
Task Report from Last Meeting
(In the task report select the meetings notes from the LAST meeting in the 'Space(s) and page(s)' field to auto-populate this table– remove this note before publishing)
Task report
Looking good, no incomplete tasks.
Decisions Made
- The group agreed to use the Use Cases GitHub repo to house use cases in "Accepted" status
Agenda and Discussion items
| Time | Item | Who | Notes |
|---|---|---|---|
| 1 min | Select Scribe for meeting | Tosha Ellison from FINOS to scribe. | |
| 2 min | Ratification of previous minutes | group | Minutes from the previous meeting were approved by the group. |
| 2 min | Roll call | group | Not Required |
| 10 min | OSSF Update | Kat | On the 2nd day of OSSF there was a dedicated program on FDC3 and Kat led the attendees (representatives from multiple working groups.) in a review and discussion of two use cases. They worked through the workflows to identify where there were requirements for the standards being written by the other groups (API, Intents, Context Data, App Directory). There was also significant discussion around context data and it was particularly useful to have use cases to focus the conversation to understand what works and where there are gaps. Also, key to keep the task at hand manageable rather than more theoretical conversations. Saori noted that she is slightly concerned that there are too many use cases and that this may cause issues over priority. She asked if there was a need for this working group to prioritize use cases. Kat noted that some of the workflows in the use cases were repetitive in terms of functional requirements. There hasn’t been an immediate request to prioritize the use cases but the group will focus on prioritising the business use cases that cover a superset of functional workflows. Kat raised other items that were discussed:
|
| 20 min | Use Cases Clean Up (based on feedback from other working groups) GitHub Demo | Kat noted that when going through the use cases with the other working groups there was still some ambiguity on what the workflow was actually trying to achieve. Kat showed an example, in GitHub, of how she has clarified this in one of the workflows. The group discussed what is meant by functional workflows, which Kat clarified to be akin to the technical steps that are required to meet the use case workflow, e.g. how an application launches another application, what context is required, etc. The group also discussed the mapping between use cases, functional workflows in the use cases, and the standards (and perhaps specific elements of the standards) that would be needed/exercised to execute the workflows/use cases. Rob and Kat will work together to clarify the required documentation around use cases as part of the overall FDC3 documentation work. | |
| 10 min | London Meeting in December | Feedback has been provided that recent in-person meetings have been extremely useful and that there is a desire to do more of this, even if in small groups. This needs to be balanced with the necessity of having a global community that can work remotely. The group agreed that in-person meetings can be helpful to do some of the “heavy lifting” before then reporting back to the group. Kat will send an email to organize some of these (small in-person meetings) in London in the near future. | |
| 10 min | Use Cases as pan-FINOS program (not just FDC3) | Rob noted that next week the Foundation team will review the suggestion of having a cross-program Use Cases WG and provide guidance from an overall Foundation point of view in a future meeting. | |
| 5 min | AOB | group | No other business |
