Skip to content

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

@addiehl

Description

@addiehl

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions