Hi Sofia,
Yes, as it happens, there was an entire course on building anatomy
ontologies, run by Melissa Haendel
https://academy.nescent.org/wiki/Ontologies_for_evolutionary_biology
(Hilmar - this is hosted on the Nescent wiki - are there plans to
migrate the wiki after Nescent goes away?)
We also ran a course for the GO editors
http://wiki.geneontology.org/index.php/Hinxton_OBO-Edit/Protege_4_workshop_Jan_2012
All of the course material is here (oops, google code):
http://oboformat.googlecode.com/svn/docs/tutorial/
Some basic tips before you get started:
No offence to Wao, but cloning it and making modifications is probably
not the way to go. Others have gone this route with other ontologies in
the past and can share their experience. Raymond may have suggestions
too.
Before going any further I'd stop and write down what some of the short
and long term goals of the ontology are. If you just need a semi-flat
list of terms for doing some image annotation then just dive in with
obo-edit and learn as you go along as most people do. However, if the
ontology is to have a more central role in your research, is likely to
be around a while, or have multiple users, or be integrated with
ontologies of either closely or distantly related organisms, modeling
neural networks, etc I'd really recommend dedicating some time upfront
to learning some modern OWL-based ontology development practices,
planning things out strategically, as this will all pay off in the
longer term. Everything will be more maintainable, amenable to automated
tooling, etc. I'll admit upfront that this can seem a bit daunting and
the tools are far from perfect.
Whichever route you take, what I'd really recommend is starting out with
a github project. It can be empty at first and just have a few files or
notes in the wiki sketching out some ideas and requirements. I know
you're familiar with github and you might be pleasantly surprised about
how much of your way of thinking for coding and bioinformatics
translates to ontology development - for example using our tools you can
set up a travis job to auto-check every commit on your repo, or pull
requests. I wrote this on setting up your gh project, but it's a bit out
of date now:
http://douroucouli.wordpress.com/2014/01/08/creating-an-ontology-project/
- after you set it up others here who are interested can follow tickets
etc.
Not really related to your question but you may want to look into some
of the work done by Daniel Lobo on planaria modeling?
> ------------------------------------------------------------------------------
> _______________________________________________
> Obo-anatomy mailing list
>
Obo-a...@lists.sourceforge.net
>
https://lists.sourceforge.net/lists/listinfo/obo-anatomy
------------------------------------------------------------------------------
_______________________________________________
Obo-anatomy mailing list
Obo-a...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/obo-anatomy