-
Notifications
You must be signed in to change notification settings - Fork 2
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
Integrate taxonomy with semantic enumerations #11
base: main
Are you sure you want to change the base?
Conversation
Here is the Unfortunately, it looks like the |
7aa2ab1
to
02eb62e
Compare
Deploying regen-data-standards with Cloudflare Pages
|
a3faeb8
to
1d1eac9
Compare
The current generated docs are out of date with the most recently committed schemas.
1d1eac9
to
7bd6a2f
Compare
I've rebased this on main and added a few follow up commits to make this consistent with changes since I first opened this PR |
This PR integrates framework taxonomy terms into the schemas using semantic enumerations.
This works by using a simple python script to populate a new
taxonomy.yaml
schema file with enum values from the curated list of taxonomy terms. This was easy to do since Linkml provides a python API for interacting with schemas, SchemaView. I also considered manipulating thetaxonomy.yaml
file more manually but got this working so didn't explore that any further.I added simple
activity
,impact
andenvironmentType
slots to the Project class just so these terms get pulled into the documentation in a meaningful way... I imagine we might want to reference these enums via different or even multiple slots? I left some related comments in #8