Skip to content

Modify materialize subclass inferences script to support versioning implementation #984

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

Closed
rjyounes opened this issue Oct 12, 2023 · 2 comments
Assignees

Comments

@rjyounes
Copy link
Collaborator

See #979

@rjyounes
Copy link
Collaborator Author

rjyounes commented Oct 13, 2023

@dylan-sa I see two options here - you might have other ideas:

  1. Simplest: don't include an ontology header in the subclass ontology
  2. Move the ontology header triples out into a separate file, and read those into the output graph. That way the script can stay the same but be extended to other projects, where each one would have its own metadata file. In that case the script has to accept an argument indicating the location of the header file.

@coltonglasgow @Jamie-SA I'm thinking we can put this generalized Python script into the sub-module. Using option 1, that would be it. Using option 2, the script would be in the sub-module but each repo would store its own header triples.

@rjyounes rjyounes moved this to To do (typically assigned) in gist Version 12.1.0 Nov 19, 2023
@rjyounes rjyounes removed their assignment Jan 25, 2024
@rjyounes
Copy link
Collaborator Author

Can't figure out what the issue is. Closing.

@rjyounes rjyounes closed this as not planned Won't fix, can't repro, duplicate, stale Jan 25, 2024
@github-project-automation github-project-automation bot moved this from To Do (typically assigned) to Done in gist Version 12.1.0 Jan 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants