Meeting scheduling update

• Cadence of General Meeting will change to quarterly

Productization/Documentation Updates

• https://fdc3.finos.org/
• Checklist: https://github.com/FDC3/FDC3/issues/32

Proposed Roadmap

• Expand the broadcast API or introduce a new channels API to support the context setting use case. 
• Publish npm package with FDC3 API definitions.

• Unify object representations of intents and applications.
• Formalize the addressing of apps specific to platform domains.

• Pivot to JSON schema for representing type definitions. We have found that TypeScript is too implementation-specific and too restrictive in practice.
• Use https://quicktype.io/ to generate type definitions from JSON schema for multi-language support.
• Formalise current example types into official fdc3 types for contact, organisation, instrument etc.

• Add detailed documentation to each intent - linking to use cases
• Align closer with Context Data WG
• Evaluate real use cases, given that we have input from early adapters
• Extend with new intents, based on above + accepted use cases

Use Cases

• Continue to process new and existing FDC3 Use Cases

• Define the next set of FDC3 Context Data types in conjunction with/based on Financial Objects working group work.
• Work with Financial Objects and other FINOS programs to reach consensus on how to make standardized taxonomies available for consumption, both for viewing/editing and programmatically e.g. for validation. 
• Create comprehensive examples of use cases that show how to use the various FDC3 standards together to enable interoperability.