...
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
- vivo.owl and applicationConfiguration.owl – current state and next steps
- ApplicationConfiguration ontology terms https://goo.gl/yavY9D
- Namespaces referenced in VIVO and Vitro https://goo.gl/GPjmUa
- JIRA here:
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1447
- 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