Tuesday, Feburary 20, 10 AM US Eastern Time

Connection Info

Please the connection information below.

Join from PC, Mac, Linux, iOS or Android: https://duraspace.zoom.us/j/500988888

Or iPhone one-tap :
    US: +14086380968,,500988888#  or +16468769923,,500988888# 
Or Telephone:
    Dial(for higher quality, dial a number based on your current location): 
        US: +1 408 638 0968  or +1 646 876 9923  or +1 669 900 6833 
    Meeting ID: 500 988 888
    International numbers available: https://duraspace.zoom.us/zoomconference?m=oXpqq6Aut6jUDAx3jNrE-q-bZNT-PM63

Attendees

• Mike Conlon
• Anna Kasprzik
• Brian Lowe
• Ralph O'Flinn
• Muhammad Javed
• Kitio Fofack
• Christian Hauschke
• Juliane Schneider
• Violeta Ilik
• Andrei Tudor

Agenda

1. vivo.owl and applicationConfiguration.owl – current state and next steps
   1. ApplicationConfiguration ontology terms https://goo.gl/yavY9D
   2. Namespaces referenced in VIVO and Vitro https://goo.gl/GPjmUa
   3. JIRA here:   Unable to locate Jira server for this macro. It may be due to Application Link configuration.
2. Your Item here

Notes

Mike

• was concerned that creating an application ontology file might disrupt the application, but that appears not to be the case.
• Javed had found a couple of annotation properties that were used in VIVO and Vitro and didn't appear to have definitions.
  • created a file to house the definitions
  • set off discussion of whether it was disruptive to the application
    • answer is no - application is just looking for triples, not ontology declarations
• went looking for things that are being used as part of the application configuration ontology
  • looking for references to the application configuration namespace in code, files
  • found 13 terms
    • 2 appear to be individuals; rest appear to be properties

Javed

• Should all 13 be defined in the same place?

Mike

• Would recommend not separating them out at this time, since that would imply that we should change the namespace and that would affect the code.