Page Comparison

Minutes approved.

• Financial Objects has an initial set of approved (reference) objects, such as Instrument, Contact, Organization, etc. There is ongoing work within the FO WG to provide additional structure and validation around these.
• Where the context data WG identifies new required objects they can propose these to the FO WG for review and ratification. 
• FINOS is working with the FO WG on how these objects are presented, see https://fo.finos.org/docs/fo-library and https://github.com/finos-fo/finos-fo. These JIRAs were also referenced https://finosfoundation.atlassian.net/browse/ODP-62, https://finosfoundation.atlassian.net/browse/ODP-77 and help/input is welcome.
• There was some discussion around the best tooling/languages/formats (JSON, TypeScript, QuickType) for this.
• Group agreed that post FDC3 standards launch it would be good to have a call between FDC3 and DOFO.

Confirmed that the launch date currently being discussed is March 19. Reference implementations are not required before launch but there is still work to be done on the Wiki, iconography, versioning, licensing, etc. 

• All repos have been consolidated to the single repo
• Issues are being transferred to the combined repo and GitHub labels are used to tag particular areas

The group discussed issue # 22 (id field should be renamed or have its keys moved to the body of the object) including ID as a dictionary, ID map, ID as an array, single ID of which there could be multiple version. It was raised that if this was going to change it probably needed to be done before the V1.0 public launch. Agreed to use email to continue this discussion.

Discussed:

• using JSON schema to represent type definitions (and ability to use this for creating definitions for other languages)
• start defining types for FDC3 objects - V1 of the spec covers the context envelope but the group needs to start solidifying the mechanisms for which they communicate the objects and having a set of defined types to pass context from one app to another
• look at type registry (in conjunction with other groups as necessary)