OBI seems to be an important topic in the discussion of the ontology, keywords, and lexicons that are being proposed for NITRC, NCBC, BIRN, etc.

Bill Bug pointed us to the following OBI content:

Here's the OBI Wiki Branch development page:
https://wiki.cbil.upenn.edu/obiwiki/inde...

The wiki is for those developers contributing directly to the ontology. It used to be open to the public, but I'm not certain it still is based on some recent changes. Here's the public OBI site:
http://obi.sourceforge.net/

OBI's large scope has led to it breaking into branches - one of which focusses on digital artifacts - Digitial Entity and Non-realizable Information Entity

The current state of this branch in OBI may be quite nascent.

I'd recommend contacting the branch editor - Jennifer Fostel - directly.

I can do that if you like, as I interact with here on the development of several of the OBI branches.

Cheers,
Bill

It was also noted that the 'data transformation branch' seems interesting as well.

We should understand these developments, and how they relate to us, further.

Maryann and I went over the OBI content today. There is much content that has potential links to the resource and resource attributes that we are describing in NITRC & IATR. I (DNK) will review how the NITRC and NIF high-level resource descriptors match, and how these may best map into the OBI framework. I will also look again at how the tool function keywords we have been using map between the NCBC framework and the OBI.

Hi David,

A few quick notes re: OBI

1) OBI = the Ontology of Biomedical Investigation

2) Current public version
* OBI development underwent a major overhaul as of January's bi-annual meeting. This is where a further commitment to building on BFO (Basic Formal Ontology) and the OBO-RO (Open Bioontologies Relation Ontology) was made, as well as the commitment to break development into the branches (). Also at this meeting, we spent time building out each branch down 2 - 3 levels from the BFO superclass - which still is at a very course level of description - e.g., obi:data_normalization is a type of obi:data_transformation is a type of obi:protocol_application is a type of bfo:Process. In this particular case, we went 3 levels down from BFO, because data_normalization was already in the previous version of OBI. This is the current public file (http://obi.sourceforge.net/ontology/OBI....). Since then (January), a HUGE amount of effort has been invested in building out the branches, but these are still at the development stage and are not in the public release. The upcoming OBI meeting will likely lead to a release of some significant portion of this additional content. There has been considerable effort invested in working of how to develop OBI as a modular ontology (i.e., each branch is a distinct OWL file), so this has slowed things a bit. The current tools - Protege v3.x - are a bit idiosyncratic in how they support shared, community development of a modular ontology. For data transformation - and the variety of generically_dependent_entities likely to be relevant to a software ontology of use to NCBCs, to NIF, and to NITRC (see those under OBI:plan and OBI:digital_entity). Again - quite a bit of work has occurred since January to build out some of these branches - e.g., data_transformation (which has only that one sub-class in the current public file) and plan are two I know that have been getting a lot of attention.