Meeting minutes status: Draft (pending approval)
Table of Contents
Date/Time
Thursday, January 13, 2020
Attendees
| Name | Organisation | Github ID (optional) |
|---|---|---|
| Riko Eksteen | Adaptive | rikoe |
| Nick Kolba | ||
| Johan Sandersson | FactSet | |
| Mark Valeiras | ChartIQ/Finsemble |
Outstanding Action Items
| Description | Due date | Assignee | Task appears on |
|---|---|---|---|
| Johan Sandersson | 2020-02-13 Meeting Notes | |
| Riko Eksteen | 2019-10-10 Meeting Notes |
Agenda
| Time | Item | Who | Notes from the Meeting |
|---|---|---|---|
| 5 min | Convene & roll call | Riko Eksteen | |
| 5 min | Approve previous minutes, and review actions for previous meetings | Everyone | |
| 15 mins | Review open GitHub issues: | Everyone | |
15 mins | Review pull requests: | Everyone | Investigate a common list type for contexts after 1.1 release. |
| 10 mins | Review remaining FDC3 1.1 release tasks:
| Everyone | Mark is going to help with filling out documentation. Johan - look at how we can link intents to use case in the docs. |
| 10 mins | Discuss potential post-1.1 context data and intents work
| Everyone | Expand intent universe (based on use cases) Collection types Returning context types for intents that return data (API + Context Data + App D) Should fdc3.open be an intent, or have an equivalent intent? Mark to create an issue on GH. Multi-asset Intents/types related to buy/sell instructions, orders, e.g. ExecuteTrade - Spans API, Use Cases, App D and Intents → Use case #4 |
| 5 mins | AOB & adjourn | Everyone | Include description to schema about differentiation between id lookups and other metadata properties. Add example of expanded context object, e.g. instrument - Mark Get discussions going on GitHub about RFQs |
Decisions Made
- Future roadmap for Context Data and Intents after 1.1 release:
- Common collection type for contexts (instead of numerous different typed ones)
- Intent + context data for Use Case #4 (executing an FX trade)
- Return data/type from raising an intent to provide trade confirmation/rejection/error for FX trade use case
- Multi-asset support (not just equities)
- Define use cases, intents and context types for Request for Quote (RFQ) workflows
Action Items
Capture any actions that were identified here, and make sure they are also captured on the group's task page during, or immediately after, the meeting
- Mark Valeiras to add a GitHub issue about fdc3.open API vs having an OpenApplication intent
- Mark Valeiras to help out with filling out context type and intent documentation on FDC3 website
- Johan Sandersson to look at how we can link between intents and use cases in FDC3 website documentation
- Mark Valeiras to add an example of an expanded context with use of additional metadata to Context Data Specification
- Riko Eksteen to add a description to context base schema to explain difference between id bag and other metadata properties