Search results

From phenoscape
  • ...to answer [[Driving Research Questions]] and for advanced [[Phenoscape use cases]]. The following tools which are under various stages of development, will ...for our user-oriented Phenoscape web application. These web services make use of mostly standard SQL queries and present a [http://en.wikipedia.org/wiki/
    6 KB (808 words) - 22:14, 10 November 2012
  • ====Issues and special cases==== #If there are multiple specimens listed for a taxon, use the β€˜+’ button to add another row, and select cells in the second row t
    8 KB (1,303 words) - 20:56, 26 November 2012
  • * Fernando, P. (presenter, poster), E. Zeng, P. Mabee. (2018) The integrative use of anatomy ontology and protein-protein interaction networks to study evolu * Mabee, P.M. (2018) Phenoscape: use case, tools, and outcomes. Explorer of Taxon Concepts and Authors Projects
    52 KB (6,895 words) - 22:42, 17 November 2023
  • ...tuting the Phenoscape KB are ultimately loaded into an RDF triplestore for use as a database back-end for the KB web application. The SPARQL query languag ** Any logical inferences which we wish to make use of in the web application interface must be precomputed and asserted into t
    9 KB (1,386 words) - 13:53, 20 March 2014
  • ...countered in the systematics literature, and provide discussion of special cases and issues in their annotation. ...omplex phenotypes, particularly those describing shape variation. In these cases, annotations are made to 'attribute' level PATO terms (e.g., PATO: shape).
    38 KB (5,768 words) - 05:13, 16 November 2016
  • When describing rules below, we use the following notations: ...just some of the many constructs from first order logic which find common use in the Phenoscape project. There is a more full-fledged introduction to [h
    15 KB (2,339 words) - 22:13, 25 May 2018
  • [[Category:Use Cases]]
    4 KB (599 words) - 16:19, 4 June 2013
  • * 11:15-11:45 Group discussion on use cases
    8 KB (989 words) - 20:15, 17 August 2012
  • ...strategy originally designed for the [[OBD Reasoner]], which we no longer use. The relationships and inferences laid out here have since been refined and Use cases:
    33 KB (5,448 words) - 22:33, 25 May 2018
  • ...be empty. We expect these necessarily empty intersections would lead the use of subsuming intersection for set propagation to overestimation of variatio ...es, for example, round and triangular are subsumed by 2-D shape. However, use of a consistent set of subsuming qualities simplifies the matching process.
    16 KB (2,382 words) - 17:40, 16 July 2012
  • ...ticipants_in” [input/output has participants in it] so might not want to use participates_in -- need to define subproperties * Planning to use single tracker (VTO tracker - link]
    31 KB (4,773 words) - 20:15, 13 March 2012
  • Textual term definitions facilitate the consistent use of a term in annotation of different data types by curators. We follow the ...is used in cases where the curator created a basic definition without the use of external references.
    5 KB (707 words) - 16:42, 9 January 2012
  • ...development are being guided by [http://en.wikipedia.org/wiki/Use_case use cases], or driving research questions, defined by the devo-evo community. These
    6 KB (922 words) - 18:05, 2 November 2011