Time | Item | Who | Notes from the Meeting |
---|
5 min | Convene & roll call | Tim Kolecke |
|
5 min | Update from WG Chair | Tim | PMC approved the context data as a standard along with AppD. The only change was exclusion of $ from the type. No concerns raised. |
5 min | Review minutes |
|
|
15 min | Review action items from previous meetings (see above) | | |
15 min | OSSF Recap | Tim Kolecke Espen Overbye Johan Sandersson Riko Eksteen | - Good cross-working group conversations on the 2nd day.
- There are ratified standards across all the working groups
- Walked through the approved use cases and applied the standards.
- Key takeaways included:
- Need to have a reference implementation
- Also need to productize, i.e. make the standards more easily consumable, even if new to FDC3. This is work to be done across FDC3 and with FINOS help.
- There was also a cross-program discussion with Financial Objects including:
- Discussion about what data belongs in FO vs. in FDC3.
- Last Thursday Johan presented some of the FDC3 context data that has crossover with Financial Objects, using real examples to help clarify whether the existing objects work, need to be modified or new objects need to be added.
- Within FO initial focus on was the basic trade attributes required for an IRSwap RFQ. They are now looking to expand this.
- Tim added that they have basic building blocks like context, instrument, portfolios and positions etc. and asked if we need a use case reference implementation of this. These could potentially be discoverable objects in AppD.
- General agreement that it's important to stay small/focused with required fields on objects (classes / types) - if you make something mandatory harder to take it away later without breaking integrations.
|
15 min | Financial Objects Contributions | Tim Kolecke Johan Sandersson | See notes above. |
5 min | AOB & adjourn | | For next steps, agreed to start with definition of contact. Can be in GitHub or in Wiki pages for comments to start coming in. Group agreed to move to a mtg frequency of two weeks, with next meeting in December. And then meet again in January on the 14th. - Request for Mao look into the PR in Context Data that is outstanding with a CCLA error.
|