You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Those of us working on morphir-scala have arrived at a place where we need to prepare for a need to support multiple data formats (i.e. Avro, Parquet, Ion, OpenAPI, etc) by providing a Morphir frontend and backend for each.
This coupled with the pack that we've been working on a Morphir Evaluator which evaluates to data values only, has lead us to start exploring the creation of a Morphir specific data model, that can serve as both a superset of other data formats and serve as a way to deal with data use cases which do not directly involve logic.
I'm place this here as a place to centralize the discussion of this topic, but there is more to come, in this space.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Those of us working on morphir-scala have arrived at a place where we need to prepare for a need to support multiple data formats (i.e. Avro, Parquet, Ion, OpenAPI, etc) by providing a Morphir frontend and backend for each.
This coupled with the pack that we've been working on a Morphir Evaluator which evaluates to data values only, has lead us to start exploring the creation of a Morphir specific data model, that can serve as both a superset of other data formats and serve as a way to deal with data use cases which do not directly involve logic.
I'm place this here as a place to centralize the discussion of this topic, but there is more to come, in this space.
Beta Was this translation helpful? Give feedback.
All reactions