...

• Ontology Interest Group Google Folder https://drive.google.com/drive/u/0/folders/1RGBh4fDZdzpJdwyiUMO8OPWwkcmVYrI0
• VIVO Ontologies on Github:  https://github/vivo-ontolgy
• OBO Slack https://join.slack.com/t/obo-communitygroup/shared_invite/zt-kpkvg7x3-kz7DeGoYKiY~VGWKO0voQg

Attendees

...

• .

...

• ...

Agenda & Notes

• Projects in the VIVO / Hercules Ontology?
  
  • ...
• Ontology improvement priorities, and release planning
  • Issues: https://docs.google.com/document/d/10Y5j8K_LKa-lAU-Z_p4q1ZnpuuKXEqqTTUb9F-4cFBE/edit#heading=h.zhzo0gde3z5i 
    • https://docs.google.com/spreadsheets/d/1WGEwIlE0PinXsFqT7JJtgT4s7UJJVGtXVzq18inqs1E/edit?usp=drive_web&ouid=115121480014248002761
  • Update:
• CERIF2VIVO
  • https://docs.google.com/spreadsheets/d/19vmYxsyawNi3W0JkToCc7CDUvjTSluoULPBsAgb-nEU/edit#gid=0
    
  • Update:
• KDSF
  
  • Update: 
• Application-specific ontologies
  • Vitro search - where to put the ontology?
  • Options:
  • https://github.com/vivo-ontologies
    • Should me mix software-oriented ontologies with domain-oriented ontologies in https://github.com/vivo-ontologies?
    • not preferred situation, reusability does not seem high
  • https://github.com/vivo-community/
    • only for additions, not things that VIVO relies upon
  • https://github.com/vivo-project/
    • should contain essential pieces for VIVO.
  • if it stored outside vivo-project it would have consequences for the build process, it should be copied into vivo-project.
  • Vitro search ontology and ABAC ontology and any application oriented ontology will be put into the VIVO code-base for now. This decision will be re-assessed later. At the moment it's built for the needs for the VIVO project