You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To create a sane looking upper level for phenio, independent of the upper level alignment of the source ontologies, we likely have to iterate.
Upper-level alignment and metaclasses are somewhat similar here, and I feel inclined to keep the metaclasses (bl:has_category bl:Gene) while aligning the upper level manually at the same time. As a first pass, I would:
Document all the main categories we need for Monarch, and identify the top level classes (UBERON, MONDO, CL, GO, etc)
Document these top-level classes carefully in a documentation page
At release time, remove all their parents. This will, in particular, remove basically all of BFO.
The text was updated successfully, but these errors were encountered:
To create a sane looking upper level for phenio, independent of the upper level alignment of the source ontologies, we likely have to iterate.
Upper-level alignment and metaclasses are somewhat similar here, and I feel inclined to keep the metaclasses (bl:has_category bl:Gene) while aligning the upper level manually at the same time. As a first pass, I would:
The text was updated successfully, but these errors were encountered: