| Topic | Notes |
|---|
|
|
| |
- Corporate commitment
- Openly sharing use cases
- Delivery of use case implementations as standards are ready
- Right audience in working group
| - All present understand
- All present will commit to implementations - as relevant to their needs
- Most members are the right audi, need wider representation from FDC3, "audience" does not mean people who attend meeting, but who contribute to documents as well.
- All to encourage others to contribute
|
- Quick look at DRAFT use cases
| - Use Case 1
- More details
- Add FDC3 compliance status
- In addition to the technical detail (good), use language that is how the user sees it (e.g. trader does not say 'i want menu options' but more like 'i want to get more in depth info about a stock').
- Use Case 2
- Good to have mobile, even if FDC3 is desktop interop focused.
- Some implementations may solve Workflows and not entire Use Cases
|
- Logistics
- Meeting cadence
- Documentation and Edits
- Ratification
- Impact/Link to other FDC3 working groups
- Email distribution
| - All good with meeting cadence for now - bi-weekly
- All OK with anyone creating docs.
- If you don't have access to wiki email help@finos.org
- All to think about what this means for next call
- How do we inform other working groups of the use cases? Start with email.
- Check with FDC3 PMC on how inter wg synchronization happens - via API working group?
- All agree to use google group email distribution - the best way to communicate (get added to email group)
- Need to set it up and add today's participants
|
| |