Skip to content


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time



Yam Trait Ontology is maintained by and

Request new traits/variables by submitting a new issue in this github repo, or by filling the trait request form

Crop specific trait ontologies enhance the interoperability and effectiveness of data exchange between the data sources which adopt it, by providing standard concepts that are use to describe phenotypes stored in those sources. As one of them, the Yam Ontology is actively used and shared in different databases used by RTB such as the BMS (Breeding Management system) of the IBP or YamBase. Phenotypes of other RTB crops such as Banana, Sweet Potato, and Cassava are stored in these RTB databases. It is thus of prime importance to agree on and share a common methodology to maintain these ontologies. This requires regular interactions between the people using it and the developers of the Crop Ontology project, who participated from the beginning of the building and the curation of those ontologies.

The following guidelines are the result of the collaboration between Crop Ontology, Bioversity, and YamBase. It is important to follow these guidelines in order to maintain one ontology which is compatibel with all databases.

Cross product terms and variable: Variable is a notion that has been introduced recently in the Crop Ontology. A variable is composed by the unique combination of one Trait, one Method and one Scale and will annotate the measurement in a database. Therefore, there is now a clear distinction between the trait and the variable. The introduction of the notion of variables as consequences on the current version of the Yam Ontology. We agreed on: Normalization of variable names Variable names should be unique, and not the same as the trait name. A good variable name should have the method and scale as part of its name, an explicit definition which includes all aspects of measuring the variable. The name should be easy to interpret by the users (breeders in the field). Breeders may use acronyms, or concatenation of the name of the trait, the method and the scale. Such names are best implemented as synonyms of the variable, since these might not be self-explanatory to other users of the ontology.

Requesting new terms to avoid overloading the same ontology IDs- only curators should add new terms

To request new terms please use the GitHub issue tracker of this repository or by filling the trait request form