Resources

• Ontology Interest Group Google Folder https://drive.google.com/drive/u/0/folders/1RGBh4fDZdzpJdwyiUMO8OPWwkcmVYrI0
• VIVO Ontologies on Github:  https://github/vivo-ontolgy
• OBO Slack https://join.slack.com/t/obo-communitygroup/shared_invite/zt-kpkvg7x3-kz7DeGoYKiY~VGWKO0voQg

Attendees

Please add yourself to the list of attendees.

• Melanie Wacker 
• Tatiana Walther 
• Brian Lowe 
• Christian Hauschke 

Agenda & Notes

• https://github.com/mconlon17/identifier-ontology/ is how it should be done ontology-wise, but might be to complicated for software developers to implement. The Ontology IG suggest to make it possible to use this ontology with some slight modifications.

• A direct data property to refer to identifiers is what is needed for most use cases. competency questions “Does a specific organization has a ROR identifier?” or “Is a publication with a certain DOI in our VIVO?”
• More sophisticated use cases might require a more complex model where it is possible to attach properties to an identifier object. The IDO should be enriched with properties to enable these use cases. Ideas are isValid (Boolean?), hasSource
• Possible fields of action: Displays, Entry Forms, Queries
• A transition phase could be set up that allows the current way to express identifiers. A deprecation process has to be designed. Idea: 2 or 3 versions which support both versions with marking the current way as deprecated before fading it out.
• Suggestion: Drafting and publishing a RFC proposal.