Draft Charter Update(s)

Owned by Former user (Deleted)
Last updated: Jul 04, 2017 by Former user (Deleted)
2 min read

As per discussions in January and February of 2017, a new charter is in preparation as per below

1. The group will seek to define and standardize APIs required to integrate the Symphony HTML5 application into a desktop container, with a specific goal such that the application can be hosted in different desktop wrappers (aka desktop containers).

2. The group will seek to define and standardize APIs to enable any HTML5 application to run in a compatible desktop wrapper and take advantage of the standardized desktop integration features.

3. Enable and expand the capabilities of the Symphony Desktop Container project(s) by direct contributions from the Foundation members and collaboration with Symphony LLC, in order to influence the direction of the project to meet the requirements of the Foundation members.

4. The group will seek to influence and standardize the integration APIs used to both interact with the Symphony Desktop application and for more general desktop application interoperability. This influence will happen through working with Symphony LLC and direct contributions from the Foundation members.


NOTES:

The Symphony HTML5 application is the javascript code that runs in the browser, the Minuet wrapper (container) and the Symphony Electron wrapper (container)

The Symphony desktop application is (July 2017) the deployed Minuet wrapper along with the Symphony HTML5 application.

Activities to support the goals above may take the form of

  • Identifying the relevant standards (i.e. W3C standards)
  • Authoring new standards as relevant / required
  • Providing a reference implementation of the standards
  • Implementing a compatibility layer (shim) to enable the Symphony HTML5 application to run without code changes with a compatibility layer
  • Developing and delivering Launchers and other code to enable a particular wrapper (container) to act similarly to the Symphony LLC provided container
  • Developing and delivering a test suite to enable wrapper (container) providers to test compatibility
  • Other activities as discussed and agreed on the Working Group call


CHANGELOG / UPDATES:

  • ESCO has seen the charter and had no major objections (Feb 2017)
  • Wording of 2 updated for clarity - overall intent should be the same
  • 3 July 2017
    • As per discussions, Goal 1 and 2 broken out to explicitly state that Symphony running in multiple wrappers / containers is goal 1
    • Added explanatory notes



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.