From Evolutionary Informatics Working Group
Revision as of 14:22, 10 March 2009 by Dpc13 (talk) (Software and Data Sets)
Jump to: navigation, search

Scope and Purposes

This page provides a concise summary of the outputs and interactions of the evoinfo working group, to be used for purposes of reporting outcomes to funding agencies, and for related purposes.

The products or outputs listed below should be information products that can be disseminated for the good of the evolutionary analysis community. It should not include intangible outcomes or products that will not be of use to anyone.


The categories of products are those used by NESCent for generating its internal reports to NSF.


Recommended Format: Use reference format for The American Naturalist (

  • Prosdocimi, F., B. Chisham, E. Pontelli, J.D. Thompson, and A. Stoltzfus, Initial Implementation of a Comparative Data Analysis Ontology. (in review, BMC Evolutionary Biology)


  • Chisham, B., E. Pontelli, F. Prosdocimi, A. Stoltzfus, J.D. Thompson, Framework for a comparative data analysis ontology. Evolution 2008, University of Minnesota, June 20-24.
  • Prosdocimi, F., B. Chisham, E. Pontelli, J.D. Thompson, and A. Stoltzfus, CDAO: an evolutionary framework for comparative data analysis. Data Integration in the Life Sciences 2008, Paris, France, June 25-27.
  • Prosdocimi, F. Framework for a comparative data analysis ontology (CDAO). 12th Evolutionary Biology Meeting Marseille 2008, France, September 24-26.

Proposals & Grants

Recommended Format: PI names. Year. Institution. Proposal title. Funding Agency. Duration. Award amount.

  • revision of 2007 proposal to be submitted Nov 5: Stolzfus, A., E. Pontelli and G. Gupta. Workflow Environment for Evolutionary Comparative Analysis. NIH. 2009 to 2013. $1M direct.

Software and Data Sets

Recommended Format: Author names. Year. Title. Web url.


Recommended Format: Collaborator names. Year. Title. Web url.

News coverage

Recommended Format: Author names. Date. Title. News organization.

Other Products

For our wiki documents below, Arlin suggests to look at the document history, then list all the authors in order of effort (as estimated by the number of revisions)