-
Notifications
You must be signed in to change notification settings - Fork 4
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
Proposal: reuse upper level OBI classes #30
Comments
Looking at OBI, there are some relevant terms under 'assay', including imaging assay, hematology assay, and imaging assay (to name a few). Biopsy isn't in the ontology as a procedure, but only the resultant, "pre-mortem specimen". This might be helpful in describing the biopsy but is not the biopsy itself. I suppose we could request to add these terms? There isn't much hierarchy there, either. Would it be better xref? |
I think it would be good to reuse classes. You can request new upper
classes from them. Be good to align terminology. If you think the term
biopsy indicates a material and not a process then you can bring this up on
the obi tracker
…On Mon, Apr 29, 2019, 10:39 Leigh Carmody ***@***.***> wrote:
Looking at OBI, there are some relevant terms under 'assay', including
imaging assay, hematology assay, and imaging assay (to name a few).
Biopsy isn't in the ontology as a procedure, but only the resultant,
"pre-mortem specimen". This might be helpful in describing the biopsy but
is not the biopsy itself. I suppose we could request to add these terms?
There isn't much hierarchy there, either. Would it be better xref?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#30 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAMMOL34EWE6MJZKVMUR2DPS4XDHANCNFSM4HJETYDQ>
.
|
Usually I am 100% with you @cmungall on re-using stuff; in this case I would be more inclined however to create a separate alignment. @LCCarmody has done some good work to convince me that the hierarchies of the ontologies she wants to pull together, including NCIt and OBI, do not reflect the clean groupings we are looking for now with MAXO. They are not UBERONs either where we can just go and fix stuff when we need to. I think Leigh will, in her engineering practice, carefully document alignments with other ontologies. But the Medical actions space is a similar chaos to the disease space, and, at least for the first 3 levels of the hierarchy, I would prefer we were independent and drive integration with bridges ala UBERON. |
This seems sensible, it would just be good to articulate some of the reasons not to reuse - and feed it back. In theory OBI and other OBOs should be open to change. It would be very useful for me to know areas in which these OBOs don't work. As it happens I have been looking at OBI "specimen" class lately and I had some questions/concerns about it. By all means let's start with some equivalence axioms between the named classes (or xrefs if you must..) |
This ticket makes it pretty clear that MAxO has no intention of conforming with OBO foundry principles; why are you applying for a purl then? |
On our call today we discussed "biopsy" that Chris raised in (obi-ontology/obi#1072), and see that it would be a specimen collection process. It currently is listed under ERO, so I am following up with ERO to see about importing it and its subclasses into OBI. I'll just add that it is incumbent on us at OBI to understand any class structure issues that make MAXO curators shy of integrating ... we would appreciate knowing what barriers to adoption you see in particular. |
Hey @ddooley we are happy to align on biopsy. Please see: obi-ontology/obi#1072 (comment) |
Add Collecting with a swab: use for swab collection pattern http://purl.obolibrary.org/obo/OBI_0002600 |
OBI has classes for Assay (test), biopsy, etc. These could be used in dosdp files and used as upper level classes in MAXO
The text was updated successfully, but these errors were encountered: