Join from PC, Mac, Linux, iOS or Android: https://duraspace.zoom.us/j/952326581
Or iPhone one-tap :
US: +16468769923,,952326581# or +16699006833,,952326581#
Dial(for higher quality, dial a number based on your current location):
US: +1 646 876 9923 or +1 669 900 6833 or +1 408 638 0968
Meeting ID: 952 326 581
International numbers available: https://duraspace.zoom.us/zoomconference?m=UwwKqz4RbGAsBAZgCE9XMorMuL0CeV4Q
more details» copy to my calendar
Ontology Interest Group Google Folder https://drive.google.com/drive/u/0/folders/1RGBh4fDZdzpJdwyiUMO8OPWwkcmVYrI0
Google doc for notes: http://bit.ly/2Jud40G
Mike will reach out to Melissa and suggest a few possible times to discuss. Then Mike will be on the road for 12 days after the end of next week.
Mike: Anabin in Germany maps between equivalent degrees from different countries. Not good coverage for the U.S.: only 22 degrees.
Mike: Tatiana made a comment on the academic degree document: points out that there is no StudentRole in VIVO currently, and one of the ontologies we’re considering reusing -- ERO -- does have a StudentRole.
Deeper issue of domain orthogonality: ERO is a resource ontology; not clear why it has a StudentRole. IAO, however, seems cleanly orthogonal. Things related to scholarship should be in the VIVO ontology; shouldn’t necessarily reuse everything, especially when entities are defined in ontologies where they don’t belong to the domain.
Marijane notes that Eagle-i doesn’t even seem to be using roles: why are they in there?
https://search.eagle-i.net/model/ (ontology browser)
https://search.eagle-i.net/model/#q=Matriculation%20Status&t=http://purl.obolibrary.org/obo/ERO_0000783&of=score (Student role, which is relabeled as Matriculation Status)
Also note -- it’s being used as a “referenced taxonomy”, not in the BFO sense of a role.
Javed: My understanding was that VIVO 2.0 would be entirely under its own namespace: was that not correct?
Mike: I’ve softened on that position. We could include ontologies that are either required by general ontology practice (e.g. RDF terms, DC metadata) or the upper-level ontology (BFO). We’re in good contact with BFO, IAO, and ERO. Feel comfortable collaborating with them, and they’re OBO compliant and actively maintained.
Mike made notes for each ontology about the license, whether it is actively maintained, and whether it is OBO compliant. Software ontology meets all the criteria. Could we work with them? Probably could.
Mike: Some ontologies, including ours, have vocabularies that could be maintained separately from the ontology itself (e.g. list of academic degrees).
Concept vocabularies (GEMET, AGROVOC): clearly, the maintenance is not in our domain. Can effectively “outsource” certain subdomains.
Academic degrees are a good example: we’re not in this business, but would be very useful to us. See Anabin (1-b-i) .
Worked with Digital Science to create 90K organizations for OpenVIVO. Could think about an automatically-maintained ontology from Digital Science data.
Journals: have a large list (44K) thanks to Violeta’s work. ISNI list (65K) is proprietary.
Can do a query in Dimensions to get a list.
Mike: Awards and honors and academic degrees end up with a very similar structure: rewarding to see those patterns emerging.
Javed: Poster or presentation?
Mike: Maybe both? Maybe a workshop? For people who are new to ontology, or to the idea of a version 2 ontology, a workshop might make them more accepting and less fearful of what initially sounds like a radical idea.
Javed: If we go with a workshop, we could divide into four one-hour sessions:
What is ontology? (General principles of using vocabularies, etc., could be here instead of strictly linked to VIVO 2.0)
Current VIVO ontology
Current interaction with the application
Way too early to talk in detail about VIVO 2.0
Mike: might have quite a bit more in six months.
Mike will reach out to invited speakers to see if they want to participate in a workshop.