requirements analysis and documentation for ROO

[mellybelly]

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

[nicolevasilevsky]

So far in ROO, we haven't bothered to apply any classification of terms, as we were just trying to get the terms in (except some classes were imported along with small hierarchies), but the intention was always to apply some classification to the terms in ROO