Agenda

• Review process
• Open issues and PRs
• Creating/assigning new issues (possibly with items from https://docs.google.com/document/d/10Y5j8K_LKa-lAU-Z_p4q1ZnpuuKXEqqTTUb9F-4cFBE/edit#heading=h.zhzo0gde3z5i)

Notes

• Initial GitHub release is available, but we still need to create Maven artifact.
  • Is an artifact with only the combined vivo.owl sufficient?
  • Should axioms from imported ontologies be separated into files to make it easier for software projects to update the imports independently?
  • Should the Maven artifact be scoped to the needs of VIVO, or might there be a use case for a generic dependency that other Java projects might decide to use?
• New issue templates
  • Edited the default text for GitHub's bug report and feature request templates and created two new issues with PRs:  https://github.com/vivo-ontologies/vivo-ontology/issues/14 and https://github.com/vivo-ontologies/vivo-ontology/issues/15
• Ontologies outside the core VIVO domain
  • Generalized solution for ordered trees (e.g. tables of contents, site navigation) would be useful in Vitro/VIVO and possibly other software.  Should these types of ontologies be included under the vivo-ontologies GitHub organization?

Ideas for future meetings

• Instances in the VIVO Ontology
• Countries (FAO)

To Do

• Enter tasks here, use "@" to assign a user, and "//", to add a deadline.