Versions Compared

Old Version 2

changes.mady.by.user Christian Hauschke

Saved on

compared with

New Version Current

changes.mady.by.user Christian Hauschke

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Page properties
idontology-calls


Meeting date

 Attendees

Topics

 

  • Please add yourself to the list of attendees.


  • Release of VIVO Ontology 1.7.0
  • Documentation of the release process
  • Review process in vivo-ontologies

 

  • Ontology Release Management
    • Please add your topics



    Agenda & Notes

    Ideas for future meetings

    • ...

    To Do

    •  Enter tasks here, use "@" to assign a user, and "//", to add a deadline.
      • 0 has been released on  
    • Documentation of the release process:
      Image Added
        • Click on Release a version 
        • Release title: ontology-title-version, example: vivo-ontology-1.7.0
        • Choose a tag, example vivo-ontology-1.7.0
        • Add release notes
        • Publish release
      • Notes: "Generate release notes" has to be investigated. 
    • Review process in vivo-ontologies
      • values in different natural languages are treated equally for the review process 
      • Simplified version of the software review process
        • regular PRs require 2 people to review
          • all changes that might have impact on reasoning: e.g. changes on axioms
          • updating imports 
          • deprecations
          • changes of primary labels
          • adding, updating or removing individuals
          • changes in types (integer, float etc.)
        • minor PRs require only 1 person to review
          • all changes that have no impact on reasoning (except for primary labels, as mentioned above)
          • typos etc.
      • A PR template for github is needed.
      • Decision: This is accepted for the beginning. It will be documented in the wiki. In the beginning, PRs should be discussed in the Ontology IG before merging.
    • Alignment of VIVO ontology development with VIVO software development 
      • Q: Mechanisms to track changes / dependencies on the ontology are missing in the software. How can we update the ontology if we do not know what will break.
      • Discussion: Do we need VIVO-internal mechanisms to check for dependencies with the ontology.
        • Define import configurations
        • Ontology validation in VIVO: 
          • consistency with other existing ontologies
          • implementation dependencies on ontologies
        • Functionality to update already existing ontologies in VIVO runtime
          • Manually uploading new ontology version
          • With lookups to ontology providers
        • Improve current VIVO ontology editor

    Ideas for future meetings

    • Instances in the VIVO Ontology
    • Countries (FAO)


    To Do

    •  create issue for updating language tags in the ontology