Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Schema definition - Data Model #139

Closed
romulocintra opened this issue Dec 15, 2020 · 1 comment
Closed

Schema definition - Data Model #139

romulocintra opened this issue Dec 15, 2020 · 1 comment
Labels
design Design principles, decisions

Comments

@romulocintra
Copy link
Collaborator

Is your feature request related to a problem? Please describe.
As a group we want an easy way to express a schema that helps creating examples, definitions , documentation and possibly tests for all definitions and future implementations of MF.

During the #134 Meeting we agree that we should try different formats , syntax or languages for this definition.

The solution or part of the solution would be experiment transposing the already created data model proposals to "types(Typescript)" and see how easy and flexible it could be for our needs.

Other languages or formats where mentioned yaml and edn - extensible data notation , please feel free to try and test all of those.

This was referenced Jan 14, 2021
@romulocintra romulocintra added the design Design principles, decisions label Jan 18, 2021
@romulocintra
Copy link
Collaborator Author

At moment Typescript was the selected and used by the actual data models

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
design Design principles, decisions
Projects
None yet
Development

No branches or pull requests

1 participant