Add reference/base vs application distinction

[cmungall]

1. Some KGs are aggregates of KGs, ready for off the shelf use
2. Some are "reference" or building blocks (generally correspond to base files in OBO speak). These are mostly of interest for people who have targeted use cases, want to make their own KG from smaller parts, or for transparency

We should have some way of distinguishing

Of course there is a continuum, which makes it hard. I propose something simple like allowing for assignment in both categories

[matentzn]

Very much agreed, also to put a stronger incentive on publishing components.

[justaddcoffee]

+1 this distinction would be useful

[caufieldjh]

I'm thinking about this as a tagging system, to keep the annotation flexible. The tagging would also include collection membership like Translator, etc