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
JSON Schema has no concept of inheritance. This makes it difficult to write schemas for type hierarchies, which have been pretty common in the ASDF use cases we've seen so far. The result ends up being a lot of duplicated attributes throughout the schema hierarchy, which becomes quite difficult to maintain.
I've recently been wondering whether we could incorporate some way to express inheritance and type hierarchies into the existing ASDF metaschema. This wouldn't actually be a part of the JSON Schema validation, but instead would indicate some preprocessing steps that would be taken when parsing schemas before they were used for validation.
This seems like a pretty proposal, but I haven't thought through many of the details yet of how exactly it would be expressed in the schema.
It would be important to allow for the ability to override the definition of certain fields inherited from a parent in a child schema.
cc-ing @jdavies-st since this could potentially replace a lot of custom logic in JWST data models.
The text was updated successfully, but these errors were encountered:
JSON Schema has no concept of inheritance. This makes it difficult to write schemas for type hierarchies, which have been pretty common in the ASDF use cases we've seen so far. The result ends up being a lot of duplicated attributes throughout the schema hierarchy, which becomes quite difficult to maintain.
I've recently been wondering whether we could incorporate some way to express inheritance and type hierarchies into the existing ASDF metaschema. This wouldn't actually be a part of the JSON Schema validation, but instead would indicate some preprocessing steps that would be taken when parsing schemas before they were used for validation.
This seems like a pretty proposal, but I haven't thought through many of the details yet of how exactly it would be expressed in the schema.
It would be important to allow for the ability to override the definition of certain fields inherited from a parent in a child schema.
cc-ing @jdavies-st since this could potentially replace a lot of custom logic in JWST data models.
The text was updated successfully, but these errors were encountered: