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

Should we develop this ontology as part of OBI directly? #1

Open
addiehl opened this issue Jun 15, 2021 · 0 comments
Open

Should we develop this ontology as part of OBI directly? #1

addiehl opened this issue Jun 15, 2021 · 0 comments

Comments

@addiehl
Copy link
Contributor

addiehl commented Jun 15, 2021

At the OBO Foundry call today there was a discussion about ontology modularity, scope, and orthogonality. I brought up MRIO as an example of an ontology that is being built as an extension of OBI, but Bjoern Peters (one of the prime movers of OBI) complained that we should simply be building it directly as part of OBI. I think MRI acquisition and analysis is important enough that perhaps it should be directly included in OBI. The advantage of this is that we would immediately get more visibility for our work. The challenge would be working through the OBI ontology development process, which could limit our speed in doing ontology development and latitude in how we chose to develop MRIO (though perhaps not so seriously).

In any case I proposed that we would present MRIO in its current state in an OBI developer call, which is typically held on Mondays, to get their opinion. This would not happen before sometime in July in any case, and we should continue to develop MRIO on own until we can discuss it with them.

Any comments from the immediate group?

@wdduncan wdduncan mentioned this issue Aug 28, 2021
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

1 participant