...
Attendees
- Damaris Murry
- Dong Joon (DJ) Lee
- Muhammad Javed
- Juliane Schneider
- Marijane White
- Tenille Johnson
- Violeta Ilik
Goals
- Create a domain definition for the VIVO ontology
- Make an ontology change - that is expected to be no / low impact; e.g. spelling correction, additional class; doesn't involve a change in the VIVO software
- Make an ontology change where there is a software change (preferably a small change)
.
Discussion items
Time | Item | Who | Notes |
---|
What is the domain of the VIVO ontologies?
Notes
- What is the domain of the VIVO ontologies
- VIVO wants to be brand when it thinks about scholarship
- Original development - not particularly strong in the arts
- Modular ontology would allow people to turn on / off the modules that they are interested in
- Modules should be concepts - may be concepts that are only applicable in a local domain
- When we say scholarship, do we also include museums? - yes
- OpenRIF, when discussing is "scholarship" exclusionary, settled on the word "expertise"
- Should it be broadened to experts such as IT personnel, who are working in a scholarly centre, but not doing research?
- Do we care about whether a publication was part of a grant, project, etc.?
- Can there be an ontology around research funding? CASRAI has a lot of terms in the vocabulary that aren't suitable for VIVO.
EuroCRIS has a model for research funding See http://www.sparontologies.net/ontologies/frapo/source.html#d4e3103)
- Some ontological errors
https://www.dropbox.com/s/976depqlqrnah65/ontologyErrors.docx?dl=0
- Ontological change
- Little to no impact vs significant community impact
- Little to no impact
- Inclusion of new class
- Changing labels
- Metadata about the ontology - e.g. attribution of ontology
- "Rare" ontology items - things that aren't used commonly. Can we be certain?
- Structural vs non-structural
- Adding relationships is a semantic change
- When can we add hierarchical assertions - a parent that we didn't have before?
- What if something is no longer a skos:Concept and becomes a BFO class?
- Moving vcards to people? Inconsistency in how these are handled across systems.
- Touching the author list is a high impact change!
- Name changes aren't handled at all in VIVO.
- vcards relate to relationships, not meant to be a replacement for authors.
- Do a survey to see what is used?
Links:
https://vivo.tib.eu/fis/display/publ201638668543
Spin off companies: http://www.sparontologies.net/ontologies/frapo/source.html#d4e3103)
Notes
Marijane: We have some to-dos from last time
- Copy of the Eagle-I ontology that does not import the NCBI taxonomy
- Ontology build tools - Melissa believes that eagle-i should transition over to robot (impacts comparing approaches for VIVO and Eagle-I)
Javed: what is robot?
Marijane: maintained by OBO community
https://github.com/ontodev/robot
Idea; Inviting someone from the robot developers to a ontology development call.
Javed compared the ontology owl file with the ontology used in VIVO.
http://purl.obolibrary.org/obo/OBI_0000571 didn't find in OWL file.
http://purl.obolibrary.org/obo/OBI_0000066 didn't find in OWL file.
http://purl.obolibrary.org/obo/OBI_0000086 didn't find in OWL file.
http://purl.obolibrary.org/obo/OBI_0000094 didn't find in OWL file.
Marijane: We need one place with the most important information about the ontology (names, definitions, where to file issues etc.).
Links:
Robot: https://github.com/ontodev/robot
https://open.med.harvard.edu/wiki/display/eaglei/eagle-i+Application+OntologiesMarijane's notes: https://github.com/openrif/vivo-isf-ontology/wiki/20170327-Ontology-Change-Improvement-Call