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

Improve schema modularity #52

Open
jonssonchristian opened this issue Apr 12, 2024 · 0 comments
Open

Improve schema modularity #52

jonssonchristian opened this issue Apr 12, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@jonssonchristian
Copy link
Collaborator

We have discussed on several occcasions that data for different parts of the data model may be generated by different software tools. It would therefore be useful to publish the JSON Schema in a modular form, so that a tool producing only one part of the EYA DEF can access a JSON Schema for that part only. The Pydantic data models are already modular in that way, and with the current approach of generating the JSON Schema from the Pydantic model, we could easily generate separate schemas for different components. The first task should be to identify the components we think make sense to publish separate JSON Schema for.

A question in relation to this is whether we still want to publish the full data model in a single JSON Schema, or if the top-level JSON Schema can include references to the component schemas.

@jonssonchristian jonssonchristian added the enhancement New feature or request label Apr 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant