Fig. 2

The building of an XPO term. XAO terms for phenotypes are selected (1) and entered in TSV files matched to specific design patterns (2). A partial uPheno design pattern YAML file example (3) shows the description of the pattern ‘Abnormally decreased size of anatomical entity’, and templates for generating names, synonyms, definitions, and equivalent classes for the pattern. The ‘%’ characters are substituted with the appropriate terms, in this case ‘anatomical entity’, from the TSV source tables during the ontology building process (4). The pipeline builds the new term from the specified component term and pattern and integrates it into the ontology (5), this shows the built equivalent classes with the XAO term variable filled. Once the new XPO build is complete with the new term it is made available on Xenbase (6)