new OBI request

[Melissa Haendel]

Hi all,

As a first step, I made an OBI request today to include a few classes from BRO in OBI. They are BRO:instruments, but probably fall into different parts of the OBI:processed material branch as indicated in the request.

The term request is here:

https://sourceforge.net/tracker/?func=detail&aid=2921944&group_id=177891&atid=886178

It may be that we will want to work with whomever this is assigned to, to get these classes defined.

Cheers,

Melissa

Dr. Melissa Haendel

Lead Curator 
eagle-i Networking Research Resources
Oregon Health & Science University
hae...@ohsu.edu
skype: melissa.haendel

503-407-5970

[whetzel]

Hi Melissa,

I just realized that this term proposal was for another set of BRO
terms, ie not the ones with multiple inheritance from the earlier
email that Alan then fowarded to the obi-devel list to suggest that
they be added to OBI. Does the eagle-i project gain value from having
BRO terms located in OBI? The BRO developers will be discussing
possible interactions with OBI at our call this Friday and it would be
great to get your feedback.

Thanks,
Trish

On Dec 27 2009, 10:57 am, Melissa Haendel <haen...@ohsu.edu> wrote:
> Hi all,
>
> As a first step, I made an OBI request today to include a few classes from BRO in OBI. They are BRO:instruments, but probably fall into different parts of the OBI:processed material branch as indicated in the request.
>

> The term request is here:https://sourceforge.net/tracker/?func=detail&aid=2921944&group_id=177...

>
> It may be that we will want to work with whomever this is assigned to, to get these classes defined.
>
> Cheers,
> Melissa
>
> Dr. Melissa Haendel
>
> Lead Curator
> eagle-i Networking Research Resources
> Oregon Health & Science University

> haen...@ohsu.edu<mailto:haen...@ohsu.edu>
> skype: melissa.haendel
> 503-407-5970

[Melissa Haendel]

Hi Trish,

In this case it was that OBI has a fairly extensive set of instruments and devices that are defined (albeit without a good parent). There were a few in BRO that overlap, and a few in BRO that are missing from OBI. The eagle-i project will be using this branch of OBI and will add new classes as needed. I think it would be great if BRO could coordinate definitions for these classes, but eagle-i does not depend on it. We would like to be able to export in biositemap RDF, but we can always create a mapping to BRO terms to do this if they don't inherently exist already. 

hope this helps clarify,

cheers

melissa

hae...@ohsu.edu
skype: melissa.haendel

503-407-5970