Plant Environmental Ontology
Developed in United States
Created in 2008
Scope and data types
How to cite this record FAIRsharing.org: PECO; Plant Environmental Ontology; DOI: 10.25504/FAIRsharing.w7a76x; Last edited: Feb. 22, 2018, 2:04 p.m.; Last accessed: Jul 20 2018 7:18 a.m.
Record updated: May 9, 2017, 2:34 p.m. by The FAIRsharing Team.
Edits to 'https://fairsharing.org/FAIRsharing.w7a76x' by 'The FAIRsharing Team' at 17:38, 19 Jul 2018 (approved): 'description' has been modified: Before: "plant Environmental conditions Ontology" is a standard, specialising in the fields described under "scope and data types", below. Until this entry is claimed, more information on this project can be found at http://purl.bioontology.org/ontology/EO. This text was generated automatically. If you work on the project responsible for "plant Environmental conditions Ontology" then please consider helping us by claiming this record and updating it appropriately. After: The Plant Environment Ontology describes the treatments,growing conditions, and/or study types used in various types of plant biology experiments.
Edits to 'https://fairsharing.org/FAIRsharing.w7a76x' by 'The FAIRsharing Team' at 17:38, 19 Jul 2018 (approved): 'name' has been modified: Before: plant Environmental conditions Ontology After: Plant Environmental conditions Ontology Countries have changed: Previous values: USA New values: United States of America Organisations have changed: Previous values: EO administrators Oregon State University New values: EO administrators Oregon State University|USA
Edits to 'https://fairsharing.org/FAIRsharing.w7a76x' by 'The FAIRsharing Team' at 17:38, 19 Jul 2018 (approved): 'homepage' has been modified: Before: http://purl.bioontology.org/ontology/PECO After: http://browser.planteome.org/amigo/term/EO:0007359#display-lineage-tab
No XSD schemas defined
Conditions of UseApplies to: Data use
No publications available
No guidelines defined
No semantic standards defined
Models and Formats
No syntax standards defined
No identifier schema standards defined
The Golm Metabolome Database (GMD) provides gas chromatography (GC) mass spectrometry (MS) reference spectra, reference metabolite profiles and tools for one of the most widespread routine technologies applied to the large scale screening and discovery of novel metabolic biomarkers.
Gramene, a comparative mapping resource for grains
Gramene's purpose is to provide added value to data sets available within the public sector, which will facilitate researchers' ability to understand the grass genomes and take advantage of genomic sequence known in one species for identifying and understanding corresponding genes, pathways and phenotypes in other grass species.
Genome Database for Rosaceae
The Genome Database for Rosaceae (GDR) is a curated and integrated web-based relational database providing centralized access to Rosaceae genomics and genetics data and analysis tools to facilitate cross-species utilization of data.
A resource providing data on bioentities and their associated ontology terms for Plant Biology. The database provides access to ontology-based annotations of genes, phenotypes and germplasms from about 90 plant species. A number of internal and external ontologies are used to annotate the biological data available from this resource.
The Open Biological and Biomedical Ontology (OBO) Foundry is a collective of ontology developers that are committed to collaboration and adherence to shared principles. The mission of the OBO Foundry is to develop a family of interoperable ontologies that are both logically well-formed and scientifically accurate. To achieve this, OBO Foundry participants voluntarily adhere to and contribute to the development of an evolving set of principles including open use, collaborative development, non-overlapping and strictly-scoped content, and common syntax and relations, based on ontology models that work well, such as the Gene Ontology (GO). The OBO Foundry is overseen by an Operations Committee with Editorial, Technical and Outreach working groups.
This record is not implemented by any policy.