JSON

Bioinformatics operations, data types, formats, identifiers and topics

EDAM is a simple ontology of well established, familiar concepts that are prevalent within bioinformatics, including types of data and data identifiers, data formats, operations and topics. EDAM provides a set of terms with synonyms and definitions - organised into an intuitive hierarchy for convenient use.

Ontology info

Ontology IRI: http://edamontology.org
Ontology id: edam
Version: 01-01-2018
Number of terms: 3327
Last loaded: Mon Jan 01 02:01:16 GMT 2018

idspace

EDAM_data http://edamontology.org/data_ "EDAM types of data"

EDAM_format http://edamontology.org/format_ "EDAM data formats"

EDAM http://edamontology.org/ "EDAM relations and concept properties"

EDAM_operation http://edamontology.org/operation_ "EDAM operations"

EDAM_topic http://edamontology.org/topic_ "EDAM topics"

hasSubset

topics "EDAM topics"

operations "EDAM operations"

data "EDAM types of data"

formats "EDAM data formats"

edam "EDAM"

concept_properties "EDAM concept properties"

identifiers "EDAM types of identifiers"

relations "EDAM relations"

date

30.12.2017 14:14 GMT

creator

Jon Ison

Hervé Ménager

Matúš Kalaš

isDefinedBy

EDAM.owl

Version

1.20

format

application/rdf+xml

remark

EDAM editors: Jon Ison, Matus Kalas, Herve Menager and Veit Schwämmle. Contributors: see http://edamontologydocs.readthedocs.io/en/latest/contributors.html. License: see http://edamontologydocs.readthedocs.io/en/latest/license.html.

EDAM is an ontology of well established, familiar concepts that are prevalent within bioinformatics, including types of data and data identifiers, data formats, operations and topics. EDAM is a simple ontology - essentially a set of terms with synonyms and definitions - organised into an intuitive hierarchy for convenient use by curators, software developers and end-users. EDAM is suitable for large-scale semantic annotations and categorisation of diverse bioinformatics resources. EDAM is also suitable for diverse application including for example within workbenches and workflow-management systems, software distributions, and resource registries.

page

page

savedBy

Jon Ison, Matus Kalas, Hervé Ménager

next id

3840