Date: Fri, 29 Mar 2024 10:26:41 -0400 (EDT) Message-ID: <510130308.147.1711722401231@lyrasis1-roc-mp1> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_146_1626730801.1711722401231" ------=_Part_146_1626730801.1711722401231 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Join from PC, Mac, Linux, iOS or Andro=
id: https://duraspace.zoom.us/j/952326581
Or iPhone one-tap :
US: +16468769923,,952326581# or +16699006833,,95232658=
1#
Or Telephone:
Dial(for higher quality, dial a number based on your current=
location):
US: +1 646 876 9923 or +1 669 900 6833&n=
bsp; or +1 408 638 0968
Meeting ID: 952 326 581
International numbers available: https://duraspace.zoom.us/zoomconfer=
ence?m=3DUwwKqz4RbGAsBAZgCE9XMorMuL0CeV4Q
more details=C2=BB copy to my ca=
lendar
Google Doc: http://bit.ly/2DgHUDK
Since we are an IG now, we sh= ould no longer take notes in the OpenRIF GitHub wiki.
VoCol test (see http://vocol= .kbs.uni-hannover.de:8087/documentation)
exchange the ontology file (C= H)
Mike will give it a try and r= eply with comments
Perhaps we could set it up wi= th ontology from VIVO 1.10 distribution so we have a common base ontology (= Christian updated after the meeting)
It started out as a PhD proje= ct (by some of S=C3=B6ren Auer=E2=80=99s PhDs back at Bonn, at his previous= affiliation)
We=E2=80=99d like it to be us= eful, so it needs to be used -- with a real project and experienced people<= /span>
Bugs in Vocol can be reported= here: https:= //github.com/vocol/vocol/issues
Mike showed a simple list of the en= tities in the VIVO ontology. http://mconlon17.github.= io/table.html 870 entities (annotation properties, object pr= operties, datatype properties and classes). Perhaps a new ontology co= vering the same domain would need about 400 entities once duplicates and en= tities outside the domain are removed.
The scope of the VIVO ontolog= y has to be evaluated and newly defined
A lot of entities in the VIVO= ontology are not from the VIVO domain. See the VIVO ontology domain definition=
Examples: vCard stuff, geopol= itical ontology
A lot of the URIs are not res= olving, because the ontologies are broken
Mike started the discussion t= hat the ontology will eventually change
Two primary questions: how? W= hy?
Ontological perspective: The = ontology we have is not a good one, and we run into barriers when changing = the ontology. VIVO is used in the real world, it=E2=80=99s not a PhD projec= t. We have different ownerships in the VIVO world - devs, ontologists, etc.=
The vivo ontology should be f= ree to be a good ontology
Currently we have a working o= ntology, so what more do we need to represent, why would we change it?
Much of scholarship can not b= e represented using the current VIVO ontology. Some things could be a= dded to the existing ontology, but many things need refactoring so that we = have a firm foundation.
Furniture and house analogy -= -- we are building a new house with new furniture. We=E2=80=99ll fix = things in the house currently own. People need to be comfortable in the new= house. Will take time and communication.
How to write. We have p= ent up ideas to remodel parts of the ontology =E2=80=93 people, orgs, = papers. We have the general notion of using more roles and less types= . We need to review local ontologies to see what extensions people ha= ve made. We need to review other ontologies in domains similar to VIV= O such as IAO, FABIO, EuroCRIS, SPAR and many others. Where are the e= dges of the domain, for example, where does research end and research admin= istration begin? VIVO has been focused on research and scholarship.= span>
How to convert: 1) build a ne= w ontology, 2) review/test/prove out the new ontology =E2=80=93 this i= nvolves representing data using the new ontology, querying. 3) Train and to= ol around the new ontology. Architects and developers are considering= how best to accommodate the need for a new ontology. All these take = significant time. Three years? How to convert: Time, tools, tra= ining.