morphir 26th January 2023 - Morphir Project Meeting

Date

Thursday 26th January 2023 - 11am ET / 4pm UK

Untracked attendees

Name	Firm	Comment

Meeting notices

FINOS Project leads are responsible for observing the FINOS guidelines for running project meetings. Project maintainers can find additional resources in the FINOS Maintainers Cheatsheet.
All participants in FINOS project meetings are subject to the LF Antitrust Policy, the FINOS Community Code of Conduct and all other FINOS policies.
FINOS meetings involve participation by industry competitors, and it is the intention of FINOS and the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. Please contact [email protected] with any questions.
FINOS project meetings may be recorded for use solely by the FINOS team for administration purposes. In very limited instances, and with explicit approval, recordings may be made more widely available.

Agenda

[ ] Status
[ ] Type Precision
[ ] IR JSON serialization for named unions
[ ] Decorations
[ ] Functional / relational mapping

Discussion

Status

Decorations proposal in progress
JSON Schema for Scala Backend in progress
Language interop - working on TypeScript version of Morphir SDK
Cross-language tests generated from Morphir tests in progress
Spark implementation is being refactored to be more generic to support similar technologies.
Morphir Scala frontend work still in progress.

Decorations

Reviewed the need for requirements and proposal. Started requirements discussion at Morphir Discussions 136.

JSON IR serialization

The main point revolves around tagged unions. A discussions has been started at Morphir Discussions 135.

Type Precision

We identified to use cases requiring type precision:

For performance in the backends.
At the edges of the model during hand-off from the host platform.

For performance, currently Morphir assumes variable precision as the default since this is Finance. Performance is strictly a runtime concern and is not a business logic authoring concern. It was noted that certain target platforms handle this adequately. Java is not one of those. Squire was raised as a Scala option. An alternative proposal was to default everything to the largest fixed size. This is a common runtime strategy. It runs the risk of overflow errors. A proposal was to let users choose either performance or precision by adding the option as a backend flag in code generators.

For conversion at the edges, that conversion seems best left to the hosting technologies. For example, calling a Morphir generated Scala library from Scala, the precision conversions should be done in Scala. Morphir actually does provide sized integer options, but they have no capabilities other than formalizing the conversion choices when converting to Morphir native numbers. All-in-all, precision is best left out of business logic.

Project Management

Question of how to follow progress of active feature development. GitHub projects was raised as a solution.
Optimizing meeting time: We will split the meeting into sections and publish times beforehand.

Decisions Made

Morgan Stanley to write Decorations discussion
Morgan Stanley to write IR JSON discussion
Capital One to propose alternate IR JSON format
Precision will be handled by a combination of backend flags, decorations, and limited capability sized Morphir types.