Menu
▾
▴
Re: [Oae-devel] [obo-admin] Request the addition of Adverse Event Ontology (AEO) into OBO foundry library
|
From: Xiang, A. <zx...@me...> - 2011-11-17 21:23:01
|
Hi, Due name conflict, we are switch to new name space OAE now. The following are the new sites/settings. Sourceforge: http://sourceforge.net/projects/oae/ Maillist: oae...@li...<mailto:oae...@li...> SVN: svn+ssh:// vn.code.sf.net/p/oae/code/trunk. SVN(https): https://svn.code.sf.net/p/oae/code/trunk Website: http://www.oae-ontology.org/ Before submit any changes to the new SVN repository, please make sure check out a fresh copy from the repository. Please check out to a different local folder other than your original AEO folder. Thanks, Allen From: He, Yongqun Sent: Wednesday, November 16, 2011 12:56 PM To: 'Chris Mungall' Cc: 'obo...@li...'; 'obo-admin'; 'OBO Coordinators'; Xiang, Allen Subject: RE: [obo-admin] Request the addition of Adverse Event Ontology (AEO) into OBO foundry library Dear Chris and OBO foundry, No problem. Thanks for reserving the OAE for us. I will provide you the required metadata for OAE soon. Best, Oliver From: Chris Mungall [mailto:cjm...@lb...]<mailto:[mailto:cjm...@lb...]> Sent: Wednesday, November 16, 2011 1:14 PM To: He, Yongqun Cc: 'obo...@li...'; 'obo-admin'; 'OBO Coordinators'; Xiang, Allen Subject: Re: [obo-admin] Request the addition of Adverse Event Ontology (AEO) into OBO foundry library Thanks for being accommodating Oliver I had asked Jonathan, he has already submitted an AEO publication. OAE is yours. If you can provide the required metadata we'll add it to the page On Nov 14, 2011, at 2:47 PM, He, Yongqun wrote: Hi Chris and OBO foundry, I don't know if you have considered my options. After second thoughts, we think the easiest way for us to do is to take the name space of "OAE", representing "Ontology of Adverse Events". Please consider this as our final proposal of solving this conflicts. I hope that you can confirm this option for us soon. Once confirmed, we will make changes on our website domain name, sourceforge SVN, and NCBO Bioportal. I look forward to hearing from you soon. Thanks, Oliver Yongqun "Oliver" He, DVM, PhD Associate Professor Unit for Laboratory Animal Medicine Department of Microbiology and Immunology and Center for Computational Medicine and Bioinformatics University of Michigan Medical School Ann Arbor, MI 48109 Email: yon...@me...<mailto:yon...@me...> Tel: 734-615-8231 (O) http://www.hegroup.org/ From: He, Yongqun Sent: Saturday, November 05, 2011 3:18 PM To: 'Chris Mungall' Cc: obo...@li...<mailto:obo...@li...>; obo-admin; OBO Coordinators Subject: RE: [obo-admin] Request the addition of Adverse Event Ontology (AEO) into OBO foundry library Hi Chris, Thanks for your prompt reply. For this conflict, a few options to consider here: (1) Use another name space, for example, OAE for "Ontology of Adverse Event(s)". (2) Stick with the AEO name space, but use the prefix of http://purl.bioontology.org/ontology instead of http://purl.bioontology.org/ontology/AEO . (3) Share IDs with AERO as you suggested. (4) Try to stick with AEO and continue to negotiate with OBO and the Anatomical Entity Ontology development team. I think it is very difficult to use the third strategy for the time being. Although we envision we will be more integrated in the future, we are now developing AEO and AERO in two separate and independent groups, have different focuses, and often try different strategies. The second option is a feasible but probably tentative strategy. We would eventually like to be part of OBO foundry, so we would like to get us registered as soon as we can. The first option is a good option. However, we have got our first AEO paper published, our AEO sourceforge and SVN generated, and our AEO website established (http://www.aeo-ontology.org/). It is much harder for us to make the change. If the Anatomical Entity Ontology (AEO) is going to stay, is that possible for you/OBO to negotiate with them and ask them/Jonathan to use another namespace like OAE for "Ontology of Anatomic Entities"? I notice that in OBO library, there is an ontology OMRSE, for "Ontology of Medically Related Social Entities". Therefore, it may not be a bad idea to have OAE for "Ontology of Anatomic Entities". If you think it is appropriate, I am happy to contact Jonathan by myself and negotiate this with him. By the way, once I submitted our Brucellosis Ontology to OBO and propose to use "BO" as the name space. I was suggested to keep it for other ontologies. I thought it was reasonable and so have agreed. Now we have the name IDOBRU. The IDOBRU paper was just accepted and published. I am wondering if I need to request to reserve the name "IDOBRU" for Brucellosis Ontology in OBO library. Thank you for your consideration! Oliver From: Chris Mungall [mailto:cjm...@lb...]<mailto:[mailto:cjm...@lb...]> Sent: Saturday, November 05, 2011 2:16 PM To: He, Yongqun Cc: obo...@li...<mailto:obo...@li...>; obo-admin; OBO Coordinators Subject: Re: [obo-admin] Request the addition of Adverse Event Ontology (AEO) into OBO foundry library Hi Oliver One possible issue is about the AEO acronym. It appears that the "AEO" acronym is now taken by Anatomical Entity Ontology, which is an ontology of anatomical structures that expands CARO, the Common Anatomy Reference Ontology. I am sorry that I did not apply for the AEO acronym before. But when we generated this "AEO" acronym for Adverse Event Ontology, the CARO-derived AEO was not in the obofoundry.org<http://obofoundry.org/> list yet. What I did before was to take an easy way -- submitted our AEO to NCBO BioPortal. Our AEO acronym in NCBO Bioportal was the first: http://bioportal.bioontology.org/ontologies/1489 http://purl.bioontology.org/ontology/AEO I'm afraid AEO was first in the OBO registry - people can put what they like in BioPortal, it doesn't affect the purl.obolibrary.org/obo<http://purl.obolibrary.org/obo> set of URLs. AEO has become more established since July, it's been linked to from other ontologies such as Uberon and EHDAA2. Is it not possible to share IDs in the AERO space? On Nov 5, 2011, at 1:53 PM, He, Yongqun wrote: Dear Chris and OBO admin/coordinators, I am wondering if you have asked Jonathan on it or not. We would like to solve the AEO name space conflict soon. This conflict makes many difficulties for our development. One note is that we have talked Melanie and Alan and solved a potential conflict between our Adverse Event Ontology (AEO) and the Adverse Event Reporting Ontology (AERO) generated by Melanie and Alan. We have all agreed to complement our work rather than compete with each other. As a result, AERO will use the AEO 'adverse event' definition and import (MIREOT) the AEO 'adverse event' term. As discussed and agreed by AEO and AERO and collaborators (including OGMS), the updated AEO 'adverse event' is defined as adverse event = def. "a pathological bodily process that occurs after a medical intervention" AEO and AERO will have different focuses. Briefly, AERO will focus on adverse event reporting, and AEO will focus on adverse event knowledge representation. More information about AEO can be found in our AEO website: http://www.aeo-ontology.org/ Here you can see the team of the AEO developers: http://www.aeo-ontology.org/dev_team.php Thanks for your consideration! Oliver Yongqun "Oliver" He, DVM, PhD Associate Professor Unit for Laboratory Animal Medicine Department of Microbiology and Immunology and Center for Computational Medicine and Bioinformatics University of Michigan Medical School Ann Arbor, MI 48109 Email: yon...@me...<mailto:yon...@me...> Tel: 734-615-8231 (O) http://www.hegroup.org/ ________________________________ From: He, Yongqun Sent: Thursday, July 28, 2011 4:45 PM To: Chris Mungall; obo...@li...<mailto:obo...@li...> Cc: obo-admin; OBO Coordinators Subject: RE: [obo-admin] Request the addition of Adverse Event Ontology (AEO) into OBO foundry library Hi Chris, Thanks for your prompt reply. Yes. It would be great if you could ask Jonathan. Thanks!! Oliver ________________________________ From: Chris Mungall [cjm...@lb...] Sent: Thursday, July 28, 2011 3:47 PM To: obo...@li...<mailto:obo...@li...> Cc: obo-admin; He, Yongqun; OBO Coordinators Subject: Re: [obo-admin] Request the addition of Adverse Event Ontology (AEO) into OBO foundry library Hi Oliver I'm afraid AEO is already taken (see obofoundry.org<http://obofoundry.org> for a complete list). I will ask Jonathan if he intends to keep his ID space, as his may be merged into CARO. On Jul 28, 2011, at 2:54 PM, He, Yongqun wrote: Dear OBO foundry, I would like to request the addition of the Adverse Event Ontology (AEO) into OBO foundry library. The AEO aligns with BFO and RO and follows the OBO foundry principles. The updated AEO is always available on page: http://sourceforge.net/projects/aeo/ specifically here: http://aeo.svn.sourceforge.net/viewvc/aeo/trunk/src/ontology/ The AEO website is here: http://www.aeo-ontology.org/ We just had an Adverse Event Representation workshop in ICBO: http://icbo.buffalo.edu/2011/WorkshopA.pdf In the workshop I presented the AEO and have received a lot of positive feedback, suggestions and comments. Attached is the AEO paper for the ICBO workshop. The adverse event community is large and covers vaccine adverse events, drug adverse events, medical device adverse events, nutritional product adverse event, surgery adverse events, etc. I see that the Adverse Event Reporting Ontology (AERO) is now listed in OBO library: http://www.obofoundry.org/ The AERO is focused on adverse event reporting. AEO is different from AERO in different ways, for example, AEO is focused on development of adverse event knowledge base. Barry Smith was in the workshop and knows the difference between these two very well. We also have two full length papers in the ICBO proceedings that discuss these two ontologies. One possible issue is about the AEO acronym. It appears that the "AEO" acronym is now taken by Anatomical Entity Ontology, which is an ontology of anatomical structures that expands CARO, the Common Anatomy Reference Ontology. I am sorry that I did not apply for the AEO acronym before. But when we generated this "AEO" acronym for Adverse Event Ontology, the CARO-derived AEO was not in the obofoundry.org<http://obofoundry.org> list yet. What I did before was to take an easy way -- submitted our AEO to NCBO BioPortal. Our AEO acronym in NCBO Bioportal was the first: http://bioportal.bioontology.org/ontologies/1489 http://purl.bioontology.org/ontology/AEO The CARO is NCBO BioPortal is still labeled as CARO (not AEO): http://bioportal.bioontology.org/ontologies/1063 http://purl.bioontology.org/ontology/CARO it appears that the CARO-derived Anatomical Entity Ontology does not exist in NCBO BioPortal now (I know it was listed in NCBO Bioportal before, but not now. I don't know why). So I hope that the OBO foundry can consider our request of using the AEO as the official acronym for the Adverse Event Ontology after discussing the current CARO/Anatomical Entity Ontology developers, and list our AEO in the OBO library. Your consideration is sincerely appreciated! Thanks! Oliver Yongqun "Oliver" He, DVM, PhD Assistant Professor Unit for Laboratory Animal Medicine Department of Microbiology and Immunology and Center for Computational Medicine and Bioinformatics University of Michigan Medical School Ann Arbor, MI 48109 Email: yon...@me...<mailto:yon...@me...> Tel: 734-615-8231 (O) http://www.hegroup.org/ ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues <AEO_camera_ready_submit.pdf> ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues |
