Thursday, June 25, 2020, 10 AM US Eastern Time

Connection Info

To join the online meeting:

• Go to: https://lyrasis.zoom.us/my/vivo1

• One tap mobile:

  • US: +16699006833,,9358074182# or +19292056099,,9358074182#

• Or Telephone:

  • US: +1 669 900 6833 or +1 929 205 6099 or 877 853 5257

  • Meeting ID: 935 807 4182

• International numbers available: https://zoom.us/u/aeANHanzED

Attendees

Resources

Ontology Interest Group Google Folder https://drive.google.com/drive/u/0/folders/1RGBh4fDZdzpJdwyiUMO8OPWwkcmVYrI0

Google Doc for meeting notes:

Attendees

• Brian Lowe
• Mike Conlon
• Philip Strömert
• Violeta Ilik
• Mathias Brochhausen
• Anna Kasprzik
• Christian Hauschke
• Ralph O’Flinn

Agenda

1. Updates
   1. ZDB presentation
2. Work in progress
   1. ADO
   2. ORG
   3. LANG
3. AEON
   1. Github: https://github.com/tibonto/aeon
   2. Slides of the AEON presentation at the VIVO conference: https://doi.org/10.5281/zenodo.3896516
4. Next Meeting, two weeks, July 9.

Notes

• Updates
• ZDB presentation
• Work in progress
• ADO
• ORG
• LANG  -- http://github.com/vivo-community/language-ontology.git 
• AEON
• Github: https://github.com/tibonto/aeon
• How will we coordinate the cooperation in the GitHub repo
• Probably needs a separate meeting
• Need to check the TIB policy on that
• http://ontology.tib.eu/aeon/ 
• Slides of the AEON presentation at the VIVO conference: https://doi.org/10.5281/zenodo.3896516
• Content Questions:
• In how far do we need to incorporate the research output, wil DOI (PID) be enough?
• How fine grained should the object properties (predicates) be?
• How to model blockchain certificates for attendees?
• Confident will focus on AEON.  SEO has several inconsistencies.  AEON has advantages with the VIVO community and ability to create a consistent ontology.  SEO is currently more comprehensive. http://kddste.sda.tech/SEOontology/Documentation/ 
• Discussion (Mathias): if a role ceases to exist if it is not fulfilled then this indicates that this should not be modeled as a role.  One sign that something is not a role is if it MUST be fulfilled.  Such things are not roles.  Roles are “realizable” optionally.  One would have roles that are never used
• Attendee role:
• must be realized as an actual activity in a part of the event.  So perhaps this is not a role.
• Is supposed to attend the event
• To count those attendees, we might have Person -> participates in -> Attendee Act -> part of -> Event
• Being the bearer is not enough.  Must be realized to “prove” attendee.  Attendee role qualifies one to receive materials and attend.  Sounds like Potential Attendee, or Registrant.
• Mathias can be reached by email
• Next meeting, two weeks, July 9.  Mike will present ADO

Action Items

• Mike will reach out to Andrew to set up a meeting regarding development practices
• Mike will prepare ADO ahead of time so that people can review.
• Philip will continue work on AEON