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
Metaschema processor was built on top of a self-described import model, where files point to other files in the repository space.
With our recent build restructure, this has proven to be burdensome, requiring brittle, repo-specific path management.
It would be useful to have each repository create a simple index of import source-file names -> filepaths relative to the index, that GMP could load. Imports and $refCuries alike would be configurable as linked entries.
It would also be cool to use the python-jsonschema/referencing library to support online ref-retrieval, once the GKS specs are a little more stable and we have ref resolution set up through w3id.
The text was updated successfully, but these errors were encountered:
ahwagner
changed the title
Metaschema processing config
Metaschema processing index
Mar 5, 2024
Metaschema processor was built on top of a self-described import model, where files point to other files in the repository space.
With our recent build restructure, this has proven to be burdensome, requiring brittle, repo-specific path management.
It would be useful to have each repository create a simple index of import source-file names -> filepaths relative to the index, that GMP could load. Imports and $refCuries alike would be configurable as linked entries.
It would also be cool to use the python-jsonschema/referencing library to support online ref-retrieval, once the GKS specs are a little more stable and we have ref resolution set up through w3id.
The text was updated successfully, but these errors were encountered: