Anatomy Ontology Conf calls

Weekly anatomy ontology calls are held on Mondays, 11:00 am-12:00 pm EDT.

Next call: Aug 8, 2011

Attending:

Agenda

Review Obo-Edit Synchronization Tool Download Synch tool plugin

July 18, 2011

Attending: Terry, Christina, VG, Paula, Chris, Dave, Erik, Wasila

Agenda

Discuss strategies for cross-species ontology synchronization

• multispecies ontologies and import vs. MIREOT
  • tool support for import/mireot in Obo-Edit
• species specific ontologies and macro x-refs
  • XAO/AAO plan
  • tool support for synchronization (Obo-edit; GO diff tool)

Minutes

Multispecies ontologies and import vs. MIREOT

• MIREOT lets you import a part of an ontology (e.g. so that we don’t get ‘tibia’ in the teleost ontology)
  • Mireot only developed in owl; applied mainly in cell ontology to date; easier than working with imports because can extract a submodule as basis for the import; variation of it in obo-edit where you save only the relevant terms (save is_a closure)
  • develop a subset file - need external script to keep subset synchronized
  • WD: Plans to develop a mireot module for obo? Roundtripping tool being developed for OWL
• another option: use ‘never in taxon’ designation instead of mireot; Put taxon info in VAO with never_in_taxon links; TAO/VAO e.g. –want to import only teleost specific;
  • never_in_taxon will be difficult for e.g., structures lost repeatedly in a clade
• Homology discussion
  • Don't add terms to VAO that are not required [incomplete notes here...]
• For now: just import/mireot the whole thing
• Better tool support needed

Species specific ontologies and macro x-refs

• XAO/AAO plan originally involved merging AAO into XAO, with AAO terms being alt-ids ot XAO terms. But messy to deal with alt-ids and obsoleting terms in XAO
• New plan for AAO/XAO alignment using xrefs
  • At end of year 1 would clone out AAO (keeping original AAO ids) terms not in Xenopus added back to AAO
  • OK to add VAO xrefs (with David) to AAO now and then
  • XAO would preferentially xref VAO terms where they are available
  • Primary location of xrefs would be in XAO now; the ssAOs hold xrefs to multispecies
• Another issue: where XAO to get non-skel terms; not ideal to xref ZFA
  • Uberon xrefs AAO; easier to do from purpose of synchronization
  • currently XAO xrefs ZFA - should they be maintained? Keep as historical record and leave as xrefs without defined semantics; don't rush to get rid of

WD: should AAO hold xrefs to Uberon or Uberon to AAO? CM: doesn't matter which file it lives in - need a bridging file which contains axioms for xrefs

• XAO workflow: if XAO need a new term, where to get them? Better to get term from higher level
  • in order of preference for a new term: AAO, VAO, Uberon, ZFA, create new term (no xref needed)
  • if AAO xrefs VAO, then VAO ID should be used preferentially over AAO id
  • non-skel terms not added to AAO until cloning

• Should terms be directlly requested from Uberon? Could do that or on the other hand, UBeron will pick up new terms when it gets updated
• When pulling terms from above and definition is terrible, then start an external dialogue to fix it.

July 11, 2011

Attending: Judy, Terry, Monte, Aaron, Christina, VG, Wasila

Agenda

1. Review anatomy ontology development plans

2. Alternative formalisms for inter-ontology links. From Chris email, 7/8/2011:

• equivalence (e.g. VAO:ligament equivalentTo Uberon:skeletal_ligament)
• subclass_of (e.g. EMAPA:islets_of_langerhans SubClassOf Uberon:islets_of_langerhans) note that EMAPA includes several classes called "islet of langerhans" and no single generic class, so we're forced to use subclass here
• equivalence given a taxon (e.g. MA:ligament EquivalentTo Uberon:ligament and partOf some NCBITaxon:10090)

3. Discuss use of vertebrate anatomy term tracker and mailing lists

4. Issues raised by Chris:

1. 1. alternate project meetings with calls where we invite other members of the obo-anatomy list?
   2. make the agenda pages on the wiki publicly readable?

Minutes

1. Reviewed ontology development plan for year 1:

• multispecies ontologies (TAO, AAO, AMAO) will import VAO; cross references in VAO, TAO, AAO, AMAO to upperlevel ontologies unnecessary
  • Action item: Chris and Jim to discuss handling of imports in OWL version of ontologies
• single species ontologies (MA, XAO, ZFA) will maintain species-specific versions of terms, and cross reference VAO and appropriate multispecies ontology
  • Cross references in single species ontologies are specified as "equivalent in taxon" links by having a line describing the meaning of the xref in the header of ontology file; for example, ZFA has the following lines in the header:

treat-xrefs-as-genus-differentia: CL part_of NCBITaxon:7955
treat-xrefs-as-genus-differentia: TAO part_of NCBITaxon:7955
treat-xrefs-as-genus-differentia: CARO part_of NCBITaxon:7955

• macro-xrefs tralsated into owl: ZFA term is the equivalent of the TAO term
• Beware if two terms xref a single term: indicates that there is a duplicate term (error)

Aaron: XAO will be adding upwards of several thousand terms, many embryological; will ref ZFA, VAO, CARO

• will be done manually, case by case basis, - are there tools for automating this?
• Action item: Chris and Jim to discuss tools for adding large chunks of ontologies to other ontologies - Paula suggests involving Jeff Bowes
• Chris: mapping issue here: don't xref at sibling level (e.g., XAO shouldn't xref ZFA), should inherit the term
• Long term goal for XAO is to follow import model;

Chris: need generic guidelines for when to subtype and when to merge

• when need to designate develops_from relationship that is not general, would create a subclass rather than add relationship at amphibian level
  • this is a shortterm solution; get latticy ontology, difficult to navigate

Wasila: way to handle taxonomically variable relationships as annotations? Chris: difficult to edit a separate data table, which would need extensions and way to view as ontology relationships

Terry: possible redundancy issue: Uberon has skeletal terms that VAO doesn't yet; what should be xrefed?

Wasila: VAO is musculo-skeletal so xrefs should be made to VAO; non-skeletal terms can be xrefed to Uberon

• Term addition to VAO is ongoing, but focus xref addition on limb/fin anatomy in first year

Decided to keep this time slot for project specific issues but there is interest in participating in a general call; also could revisit using this time slot after project work settles down

June 13, 2011

Attending: Monte Westerfield, Paula Mabee, Judy Blake, Aaron Zorn, Jeff Bowes, Wasila Dahdul, Jim Balhoff, Terry Hayamizu

Agenda

• Judy:
  • Discussion on how to initiate the Amniote Anatomy Ontology for terms outside skeletal system
  • Report on status of unified anatomy [emap + MA]
  • What exactly is abstract mouse?
  • Clone MA, UBERON, unified mouse [emap + MA], or abstract mouse?
• Monte:
  • Discussion on moving ZFA to GO like model; possibility of implementing VAO import (so that XAO can just clone this VAO chunk when they also clone the rest of ZFA)
• Aaron and Jeff:
  • Discussion on setting up modular ontology model and specifics of importing model species-specific information (like devo stage)

Action items resulting from call:

• Monte: Charge to the zfin group (from Monte) is to write up plan and potential problems
• Judy: Will send Jim contact for Amelia Ireland for diff
• All: short term goal to add xrefs to VAO to ZFA, XAO, MA
• Wasila: give VAO write access to other groups
• Wasila: find out how often UBERON gets updated -- done WD 6/25/2011
• Wasila: Schedule weekly meeting to sort out what is happening in these AOs, beginning in July -- done WD 6/25/2011

Minutes

• Wasila will demonstrate diffs between Uberon and MA using non-skeletal terms
  • e.g. 'naris' in mouse is 'part of nose'
  • e.g. 'naris' in uberon with lots of xrefs but missing relationship 'part of' olfactory apparatus
  • not sure how often Chris updates Uberon
• Terry - developed adult Mouse Anatomy; working with Edinburgh group to update their ontology
  • 'unified mouse anatomy' not an official term, just a descriptor
  • Ed. developmental mouse anatomy developed 15 years ago in an effort to code mouse expressiondata. Built along lines of an atlas by kauffman and baird; partonomy; Used for expression annotation by ... for years now. Two parts: abstract mouse which is a time -inedpent collection of terms in a hierarhy not a dag; and from that extracted stage-dependent hierarchies. stage 28 is postnatal -- this is not developed at all. 8-10 years ago, a postnatal developed by jax. jax added is-a and expanded on stages. Examined all relevant ontologies in updating. Two entities (MA vs. developmental) not connected currently -- working to make it an anatomy ontology encompassing the whole of mouse development.
  • Q: re: timeline? Terry: within next two weeks could give clearer answer.
  • would like to work with rest of ao community to make it a resource that will best serve needs of community. It works for expression and for phenotype, but needs to work better for other communities. Have updated based on other working groups. Would like to work to update weak points.
  • Judy - Terry funded for small portion of time on issues relevant to project
  • Wasila - use mouse
  • Judy -- start with MA, great place to start. Talk with Chris to see where he last updated and worked with it.
  • Terry -- Uberon - made an effort to take into consideration only things that are shared - not less valuable for it; structurally less consistent than mouse; mouse is lacking becuase of roots in ed anatomy and purpose for expression -- so the high level structure is a partonomy; first level division into regions, then into organ systems, etc. Need to think about primary goals of new ontology. Where along tree does it no longer serve amniotes or chickens?
  • Some avian terms are already in uberon -- use mixed approach. Also uberon follows more of a is_a approach;
  • MA, Uberon, VAO, AmAO are all separate right now; good documentation of proposed changes;
• Judy: suggestion -- all work together on one aspect at a time - start with limb/fin
• Terry: Historically for MA, when significant changes made, to a section in response to some input; not a constant stream of changes; structurally and in terms of big picture, not changes often. Need to do in coordination.
• Wasila: Conclude -- need mixed approach

• Monte:
  • Need to improve ways of synchronizing zfish ontology with vao, uberon, etc. Met with db admins etc. to discuss future re: ontologies and new mechanism to stay in synch. Potential problem is that lead curator out on maternity leave, so people he discussed it with not necessarily in charge, but they understood basic issue. Charge to the zfin group (from Monte) is to write up plan and potential problems. Briefly -- problem how to grow two ontologies grow in synch. Big concern that curators have is if they become dependent on outside group such as Phenoscape, there could be changes made without consideration for the implications of zfin. Also, term request brokerage rights need to be grant to zfin. Need to work out sop for how updates are made.
  • Concern how we represent developmental staging. Start and stop times in same db table. If bringing in terms from outside resource, will break the devo and it will have to be moved to an outside table. This has implications for xao. If xao is dependent on zfin, this will take some time.
• Aaron: best way to go is to clone zfa. Have to develop ways to import VAO.
• Jeff: Inheritance structure?
• Wasila: Yes, direct links
• Jeff: inheritance from next highest ontology? correct?
• Wasila: Yes, go up to next higher level ontology.
• Jeff: Given current architecture, not hard to do. However concerns about changing higher level terms and effects on lower level terms.
• Monte: talked about how zfin does with go currently - via diffs list - not overly onerous - but have to have sop - can run checks on reasoning, but human will have to fix a couple of things
• Judy - -yes
• Aaron: VAO not complete for all organ systems....how does this work?
• Jeff: This is ok -- for terms that exist in VAO, we can show as inherited.
• Jeff: Development not taken into account in higher-level ontologies. Have to have a way to associate development with terms. Just show which terms are inherited and maintain just as we do now.
• Aaron: Will clone vao and zfa terms and keep xrefs. When we transition to other system, can track what we are importing.
  • In short term, clone vao terms into xao - ok?
• Short term goal: Add xrefs to VAO to ZFA, XAO, MA
• Judy: weekly meeting to sort out what is happening in these anatomies?
• Wasila: yes, it would be useful
• Aaron: jamboree approach --
• Judy: Even a 1/2 hour check up
• Wasila: Even a open weekly call
• Judy: open up wiki for agenda building and notes
• Aaron re: data jam: 22 Aug-26 Aug; Erik S for 5 days
• Paula: Most efficient way to add xrefs to VAO to zfa etc.?
• Monte: ZFA and XAO etc. need write access to VAO
• Paula: Jim -- how to get this diff file automatically generated?
• Judy: Will send Jim contact for Amelia Ireland for diff
• Wasila: Will give write access to VAO to other groups. Will be making lots of changes over next two months.
• Paula: How coordinated in GO?
• Judy: Webex every/most mornings by the GO development team, share screen and work together ---additions at leaves easy; others assigned to people; coordination - big branches worked on by whole group
• bowes@ucalgary.ca and terry to be added to email list; Wasila will send out notes