Agenda & Notes

• Pull requests and issues
  • Merged PRs:
    
    • https://github.com/vivo-ontologies/vivo-ontology/pull/1#event-13100076907 Added rdfs:comment for bibo:issue - reviewed and merged
    • fixed typo "tye" to type - reviewed and merged
      
      • how do we deal with these trivial kind of PRs? 
      • 4 eye principle. Submitter of PR is one person, review and merge should be done by a different person.
    • Removed domain statement from bibo:doi - reviewed and merged
  • open PRs:
    • Improved metadata for vivo.owl - reviewer wanted
    • Readme release information - reviewer wanted
  • a couple Software related issues - Dragan Ivanovic will create a draft PR
    • https://github.com/vivo-ontologies/vivo-ontology/issues/27
      • 2 approaches
        • using the approach for patents, with a direct data property for the date
        • creating an object
    • https://github.com/vivo-ontologies/vivo-ontology/issues/28 - Add relationships for other contribution types 
      • Christian asked a colleague if he can provide contributor roles for (research) software
    • https://github.com/vivo-ontologies/vivo-ontology/issues/29
      • idea: deprecating informationResourceSupportedBy, and using vivo:SupportedBy instead for all kinds of support
    • Context for those PRs is to consider alignment of VIVO with codemeta - https://github.com/codemeta/codemeta/blob/master/crosswalk.csv
    • Potential identifiers
      • Github, Gitlab, Codeberg for persons
      • https://docs.softwareheritage.org/devel/swh-model/persistent-identifiers.html for software
  • Unknown provenance of property  <http://purl.obolibrary.org/obo/ARG_2000028>
    Example of usage for https://forschungsatlas.fid-bau.de/individual/Bb4e7d03-0d7f-4a8b-a3e5-024b7c1aa247: 
    

    | <http://purl.obolibrary.org/obo/ARG_2000028> | <https://forschungsatlas.fid-bau.de/individual/vcard_Bb4e7d03-0d7f-4a8b-a3e5-024b7c1aa247> | <http://vitro.mannlib.cornell.edu/default/vitro-kb-inf> |
    
    

Ideas for future meetings

• ...

To Do

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