Reformat the existing COR use cases into something more user-friendly #70
Description
It has been determined that the existing COR Use Cases and Requirements needs to be manifested into some document that users can easily contribute to.
Some comments from the 2020 summer meeting notes are as follows
It's really not clear what the use case(s) is that COR is intended to support? I’d like a resource to give me a controlled vocabulary for a particular property, what are the definitions of the term at this URI, what (SKOS, OWL...) vocabularies are there that are about ‘X’.
I’m wondering if there are use cases for beginners who are looking for appropriate ontologies to adopt.
Does COR intend to be like OBO Foundry with only orthogonal vocabularies? No (says John G). But if not, seeing multiple responses means you need to know which vocabulary to visit first.
really need to be clear about what COR is for? Store, find, USe terminology. What is ‘use terminology’. COR targeted to particular community. Aims at spectrum of users, not just semantic experts. “Easy for anyone to upload a vocabulary to COR; BioPortal requires some semantic knowledge”