Agenda & Notes

• Ontology Release Management
  
• Maven artefact for use in the VIVO application
  • Suggestion: a git dependency could work, too.
  • This would mean that the ontology repo would not have to be cchanged, a maven artifact is maybe not needed. Future assessment will come to different outcomes. 
  • Decision: No maven artifact needed, no need for changes of the release management to include the ontology in the VIVO app repo.
• 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? 
  
  • The Philip approach
  • would mean that a software using the ontology can pick if it selects the imports or not.
  • Decision: Christian approaches Philip and asks for support/help
• Review policy in contributing.md
  • allows easier switch to another repo
  • Should be referenced in readme.md
  • Decision: Review policy should be in Readme directly, https://github.com/vivo-ontologies/vivo-ontology/pull/9 will be closed.

Ideas for future meetings

• Open Access Ontology Tatiana Walther - not on the 17th of April

To Do

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