Date
Attendees
Goals
- Create a domain definition for the VIVO ontology
- Make an ontology change - that is expected to be no / low impact; e.g. spelling correction, additional class; doesn't involve a change in the VIVO software
- Make an ontology change where there is a software change (preferably a small change)
.
Discussion items
| Time | Item | Who | Notes |
|---|---|---|---|
Notes
Marijane: We have some to-dos from last time
- Copy of the Eagle-I ontology that does not import the NCBI taxonomy
- Ontology build tools - Melissa believes that eagle-i should transition over to robot (impacts comparing approaches for VIVO and Eagle-I)
Javed: what is robot?
Marijane: maintained by OBO community
https://github.com/ontodev/robot
Idea; Inviting someone from the robot developers to a ontology development call.
Javed compared the ontology owl file with the ontology used in VIVO.
http://purl.obolibrary.org/obo/OBI_0000571 didn't find in OWL file.
http://purl.obolibrary.org/obo/OBI_0000066 didn't find in OWL file.
http://purl.obolibrary.org/obo/OBI_0000086 didn't find in OWL file.
http://purl.obolibrary.org/obo/OBI_0000094 didn't find in OWL file.
Marijane: We need one place with the most important information about the ontology (names, definitions, where to file issues etc.).
Links:
Robot: https://github.com/ontodev/robot
https://open.med.harvard.edu/wiki/display/eaglei/eagle-i+Application+Ontologies
