API Working Group (Archived)
The content on this page and all sub-pages is an archive from the legacy Symphony Software Foundation. It is preserved as a historical record only, and should not be considered relevant for any FINOS activities.
Current Focus
Language Bindings
Publish and maintain a clear list of language bindings to the Symphony LLC REST API and implementation of the Extension API. This is inclusive of endpoint coverage and UI module integration in the container.
SDK & Frameworks
Development kits and frameworks that support development and implement well defined use cases. This is inclusive of both application (bot) and UI module development in the container. Catalogue features between like solutions.
Use Cases and Benefits
Defined collaboration use cases through both design and example (bots, UI modules, workflows). Create a clear index of possible use cases to existing solutions that consumers can benefit from.
Extensions
Integration of external standard frameworks and services such as Lex, Google Assist, MS, Bot interfaces, and UI solutions.
Testing and Best Practices
Required tests to validate developed solutions. Can be based on specific workflows, use cases or individual feature.
Culture and Support
Foster a community of SME’s that can offer help on the implementation of solutions available that implement the Symphony LLC platform feature set.
Participants
Chair(s)
Name | Organization | Role |
|---|---|---|
Aaron Williamson | Symphony Software Foundation | Acting Chair |
Former user (Deleted) | IHS Markit / ESCO | Support |
Members
Name | Organization | Role |
|---|---|---|
Tim Christopher | BlackRock | Participant |
Symphony Communication Services LLC | Participant | |
Yuming Deng | Citi | Participant |
JT Dupuy | Wells Fargo | Participant |
Former user (Deleted) | BNY Mellon | Participant |
Matthew Gardner | BlackRock | Participant |
Matt Joyce | Symphony LLC | Participant |
Morgan Stanley | Participant | |
JP Morgan | Participant | |
Peter Leong | BNY Mellon | Participant |
JP Morgan | Participant | |
Joy Peacock | BNY Mellon | Participant |
Former user (Deleted) | JP Morgan | Participant |
Citi | Participant | |
FactSet | Participant | |
Symphony Communication Services LLC | Participant | |
Leslie Spiro | Tick42 | Participant |
Credit Suisse | Participant | |
Symphony Software Foundation | Observer | |
Symphony Software Foundation | Observer | |
Aaron Williamson | Symphony Software Foundation | Secretary |
Board Sponsor
Name | Organization | Role |
|---|---|---|
Brad Levy | IHS Markit | Board Sponsor |
Getting involved
If you're a member of the Symphony Software Foundation and would like to participate in this working group, please send an email to Aaron Williamson. We'll invite you to the next meeting and add you to the mailing list.
Charter
**Note: The current charter was based on the original discussion around both best practices using REST and integration of Symphony LLC APIs. The group has morphed into the focus items listed to the left. The original charter will be evaluated at a later date and is not critical to the success of the working group itself.
This working group focuses on the APIs of the Symphony platform, to enable server-side integrations with 3rd party technologies. See detailed charter.
The Working Group was ratified by the ESCo on December 9th, 2016.
The group chose to discontinue operations on April 20th, 2018.
Group information
| Info | Value | Comments |
|---|---|---|
Nature | Permanent | Manages the ongoing strategy, open source governance and technology choices of the Platform's APIs. |
| Occurrence | Fortnightly | To start with, might change moving forward. |
| Visibility | Public (R/O) | Certain firm material may be shared privately. |
| Mailing List | wg-api@symphony.foundation | Archives here (requires Foundation Login) |
| Meeting minutes | API WG Meeting Notes | Notes, actions and decisions of WG meetings. |
| Working Group Documents | API WG Documents | Input and deliverables documents from this WG. |
Activity Stream
Need help? Email help@finos.org we'll get back to you.
Content on this page is licensed under the CC BY 4.0 license.
Code on this page is licensed under the Apache 2.0 license.