data2health/research-outputs-ontology

This ontology provides scholarly research outputs, for use in crediting persons or organizations.

research-outputs-ontology's Issues

Research objects vs. research outputs.

Would it be possible to rename repo as research objects ontology? This will allow us to be more inclusive of objects that might not necessarily be outputs. Thoughts? Thanks.

Create and document selection criteria for inclusion in the ontology

We should have a modular strategy for inclusion of ontology content. What we don't want is a random smattering of content from numerous resources as these will not have good semantic interoperability. We want to be able to do analytics on these data, not just link them.

My understanding is that the goal here is purely as an application ontology for our discovery tools. As such we should not need any new content.

Some considerations:
For library related document types we should use whatever is standard in the LinkedData4Libraries project or in MARC. @eichmann please inform this.

There could be a priority order - such as VIVO-ISF>OBI>NCIT etc. I would avoid one-off avoid one-off content from domain specific sources, such as a flybase controlled vocabulary.

We should choose content that is resolvable and has definitions, synonyms, and is updated regularly.

Lets also think about the modules for import purposes - we can't maintain things very well if there is no modularity, and its also more useful to others if its modular.

need dbxref annotation property

all the imports brought in a lot of new annotation properties, but it appears we still do not have the dbxref annotation property.

Should we add it to the IAO imports?

Once we add it, we should add xrefs from the spreadsheet

Consider Medline pub types

https://www.nlm.nih.gov/mesh/pubtypes.html

decide between created_by vs dc:creator

HPO uses created_by (as of just recently), so the new term I just added to ROO (ROO_0000036) has the annotation created_by, whereas the other classes use dc:creator.

Is it okay if we use created_by instead of dc:creator?

Is there any easy way to update annotations on the other classes I created? If not, I can do it manually.

Add NISO documentation and attribution

It would be great to have the canonical information available regarding the NISO documentation of research output types. Can the final version be linked here for review?

requirements analysis and documentation for ROO

Does ROO need to be an ontology? or could it be a CV? How will it be used in our search engine? what kinds of classification will people want to be able to do?

Originally i had thought we did not need a ROO, because the instances of these classes would be part of the annotation model and would not need ontological characterization. I get that for search and discovery this could be helpful, but right now there is essentially a list - which still doesn't warrant an ontological approach.

Can we come up with some classification examples that you'd want to be able to do to help us understand the structure? Its totally fine too to have a very simple ontology if its useful.

Also see comments on #7

should terms be plural?

some of the terms I added are plural (because that is how they were written in the spreadsheet, but I just want to confirm that I should make them singular