2017-07-20 Meeting notes
- Aaron Williamson
Table of Contents
Date
Agenda
| Time | Item | Who | Notes |
|---|---|---|---|
| 5 min | Convene & roll call | ||
| 10 min | Review action items from previous meetings | See below | |
| 15 min | Update: Symphony Java Client 1.46 support | Former user (Deleted) | |
| 10 min | Poll: interest in defining RESTful API Design Guidelines | Aaron Williamson | BNY Mellon contributed its RESTful API Design Guidelines to the WG. Are members interested in collaborating on consensus guidelines based on these to "to inform, guide and validate the way future APIs should be published," per the charter? |
| 15 min | Review use cases | Johan Sandersson | |
| 5 min | AOB & adjourn |
New action items
- Former user (Deleted)/anyone: add to Standard Test Cases: attachments (plus hash validation), PresentationML validity, tag limit validation(?)
- Former user (Deleted)Former user (Deleted): set API client maintainers up with early access to new API versions for testing
- Dan Nathanson (Deactivated) / Former user (Deleted) / Matt Joyce (Deactivated): if there is any change in how attachments work, update the RESTful API Design Guidelines to reflect the recommended practice
- All: add your comments and questions to the RESTful API Design Guidelines
Standing action items
- Capture API use cases relevant to your organization
- Identify high-priority use cases in Confluence or to Former user (Deleted)
- Tell Former user (Deleted) about API errors & exceptions that need work
- Define Standard Test Cases for API clients
Actions items from previous meetings
Language Bindings
- Former user (Deleted): create API definitions based on SJC abstracted binding layer and generate a YAML Swagger specification from it
- Former user (Deleted), Former user (Deleted), Matt Joyce (Deactivated):
- Start a list of the basic functionality bindings should have test for before being considered active. (Possibly Former user (Deleted) too.)
- Draft list of API endpoints that should be supported by active language bindings.
Use Cases
- Former user (Deleted): review API use cases with LLC team before the next meeting to determine/document whether they're supported by the existing API.
- All: review the job story format and consider whether to use this format for use cases.
Consuming the Symphony API
- All: If you are aware of an open source project that provides a good API for creating bots, tell Former user (Deleted).
Attendees
| Name | Organisation | Present? |
|---|---|---|
Former user (Deleted) (Chair) | BNY Mellon | |
Former user (Deleted) (Co-chair) | Symphony LLC | |
| Dhilip Buddha | BlackRock | |
| Kashik Chaubal | BlackRock | |
| Symphony LLC | ||
| David Deng | Citi | |
| At-Large Member | ||
| BlackRock | ||
| Symphony LLC | Y | |
| Morgan Stanley | Y | |
| Anton Kozyr | BlackRock | |
| BNY Mellon | ||
| JP Morgan | ||
| Symphony LLC | Y | |
| Barun Patnayak | Citi | |
| JP Morgan | ||
| FactSet | ||
| FactSet | ||
| Tick42 | Y | |
| IHS Markit | Y | |
| Symphony Software Foundation | Y | |
| Symphony Software Foundation | Y |
Meeting notes
Former user (Deleted) gave an update on the new version of the Symphony Java Client, which supports Symphony's 1.46 API. A complete summary of his changes was posted on the Symphony developers mailing list.
Matt Joyce (Deactivated) gave an update on the development of the Python API client.
The members discussed the Standard Test Cases for API client development proposed by Former user (Deleted) and what additions should be made.
The members discussed the provisioning of bots via the Symphony Java Client. Former user (Deleted) proposed integrating SJC with BotMill or a similar tool to make this easy.
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.