Resources
- 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
Please add yourself to the list of attendees.
Agenda & Notes
- VIVO Meetup at SWIB 2023 in Berlin
- Update:
- 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
- Update:
- NOTES: Georgy and Brian discussed the implications of the first row in the spreadsheet: moving Relationship from Continuant to Occurrent
- Brian mentioned history of why the difference was introduced in the ISF in 2013 (relationships are "assigned" and may differ from processes where actual work was done; listing of a person as an author in an Authorship doesn't necessarily imply an AuthorRole in the process that produced the work, etc.).
- It would be nice to be able to use only standard OBO predicates like participant/participatesIn instead of the problematic relates/relatedBy.
- Making this change would have far-reaching implications for existing implementers
- Want to avoid problems of original ISF transition (built-in VIVO triple store upgrade worked well but outboard ingest scripting changes were hard for implementing sites).
- Good use case for the developing deprecation process. Would need to allow time for people to adapt.
- Georgy discussed the value of encapsulating these ontology structures in Dynamic API components so that we can introduce new components and users won't have to change their code that calls those components.
- NOTES: Georgy and Brian discussed the implications of the first row in the spreadsheet: moving Relationship from Continuant to Occurrent
- CERIF2VIVO
- KDSF
- Update:
