AnnotationProperty -- member of ontology subset

[zhengj2007]

From @zhengj2007 on July 31, 2015 20:42

From [email protected] on February 01, 2011 11:50:22

Please indicate the label for the new term member of ontology subset Please provide a textual definition connects an information artefact to an ontology subset to which it is a member of. comments: the range of this property should be individuals of the class ontology subset (we cannot declare this for annotation properties) Please add an example of usage for that term Please provide any additional information below. (e.g., proposed position in the IAO hierarchy) xref: obo-format:subset

Original issue: http://code.google.com/p/information-artifact-ontology/issues/detail?id=93

Copied from original issue: information-artifact-ontology/IAO#93

[zhengj2007]

From [email protected] on March 10, 2011 06:44:55

Background

It is sometimes useful, for all sorts of purposes, to be able to define arbitrary subsets of the set of all terms in an ontology. Here are three examples

1. Defining a slim version of an ontology (GO has several).
2. Temporarily filtering out embargoed terms, defined based on unpublished work, from the public version of an ontology. This is something I've had to do a couple of times.
3. Defining subsets of terms that are allowed for curation. Databases often have internal rules for this that cut across the class hierarchy in ways that can't be supported by reasoner queries. Subsets can provide a useful way to reflect these rules so that appropriate terms can be extracted from an ontology for use in tool or pre-load checking of curation.

There are many other possible uses. It's the arbitrariness that makes this so useful.

Propoesed def

def: "An information artifact that specifies membership of a fiat set of ontology terms that share the same namespace. No common properties are implied by membership of such a set."

Note, ideally the implementation of this term and the related subsetdef, which defines sets, would be outside of the OWL reasoning system - at least when these are used as annotation properties in an ontology. Can this all be done with nested annotation properties?