Ensure ontology subsets are fully documented

[cmungall]

We should have concise but informative documentation on the different subset products offered by the different ontologies. This could be in the yaml or in the dc:description of the subset or both.

Examples: go-basic, uberon subsets

As far as possible this documentation should rely on a shared terminology, TBD here, examples include:

• class subset: a subset based on a set of classes of interest. E.g. classic GO "slims"
  • by domain of interest
  • by level of specificity
  • editorial criteria, e.g. heavily vetted (obi core; chebi 3-stars)
• property subset: a subset based on a set of OPs of interest, e.g. isa/partof (with all axioms that refer to OPs not in subset removed)
• axiom type or expressivity subset, e.g. obo basic, classic OWL profiles

Related discussion: ontodev/robot#183 (comment)

[nlharris]

Has this been done? If not, and it's still relevant, can it be assigned to someone else?

[nlharris]

is this still needed?

[matentzn]

Low priority, nice to have. This requires real manual labour; I personally think it's not worth it, but we could encourage it better for new ontologies moving forward.