Skip to content

Releases: EBISPOT/efo

2018-12-17 EFO 3.2.0

17 Dec 11:00
Compare
Choose a tag to compare

2018-12-17 EFO 3.2.0 release

EFO 3 represents a change in how we build and publish EFO to better align it with ontologies we import from OBO. These changes include a harmonisation of how EFO represents synonyms, xrefs, term definitions and deprecated classes to be consistent with the OBO 1.4 specification and OWL in OWL syntax. More details on the specific changes to EFO can be found in the README file in the efo3 branch.

A VERY IMPORTANT NOTE: There was an issue in building the ontology diff and consequently the release notes for 3.2.0 are less detailed than usual. We apologise for this. If there are any questions regarding the changes between 3.1.0 and 3.2.0, please contact us.

As always, all existing EFO terms have retained the EFO ID. The MONDO ID for each mapped term is available within the annotations as a cross reference. Any new terms imported from MONDO have retained their MONDO IDs. All mapped terms (EFO terms and their MONDO mapped term) can be found in the mondo_efo_mappings.tsv file situated in the imports folder.

2018-12-17 EFO 2.103

17 Dec 10:14
Compare
Choose a tag to compare

EFO 2.103 December 2018 release

2018-11-15 EFO 3.1.0

15 Nov 14:07
Compare
Choose a tag to compare

2018-11-15 EFO 3.1.0 release

EFO 3 represents a change in how we build and publish EFO to better align it with ontologies we import from OBO. These changes include a harmonisation of how EFO represents synonyms, xrefs, term definitions and deprecated classes to be consistent with the OBO 1.4 specification and OWL in OWL syntax. More details on the specific changes to EFO can be found in the README file in the efo3 branch.

A VERY IMPORTANT NOTE: There was an issue in building the ontology diff and consequently the release notes for 3.1.0 are less detailed than usual. We apologise for this. If there are any questions regarding the changes between 3.0.0 and 3.1.0, please contact us.

The 2018-11-15 EFO 3.1.0 release contains a major bug fix. Object properties are now transferred to the final efo.owl file (attached to this release as an asset), providing richer axiomatisation. There has also been further restructuring to the disease branch in order to improve classification and align better with MONDO.

As always, all existing EFO terms have retained the EFO ID. The MONDO ID for each mapped term is available within the annotations as a cross reference. Any new terms imported from MONDO have retained their MONDO IDs. All mapped terms (EFO terms and their MONDO mapped term) can be found in the mondo_efo_mappings.tsv file situated in the imports folder.

2018-11-15 EFO 2.102

15 Nov 09:41
Compare
Choose a tag to compare

EFO 2.102 November 2018 release

2018-10-15 EFO 3.0.0

15 Oct 16:37
Compare
Choose a tag to compare

2018-10-15 EFO 3.0.0 release

EFO 3 represents a change in how we build and publish EFO to better align it with ontologies we import from OBO. These changes include a harmonisation of how EFO represents synonyms, xrefs, term definitions and deprecated classes to be consistent with the OBO 1.4 specification and OWL in OWL syntax. More details on the specific changes to EFO can be found in the README file in the efo3 branch.

The 2018-10-15 EFO 3.0.0 release contains major restructuring to the disease branch in order to improve classification based on current medical understanding and in alignment with existing domain ontologies. This has been achieved through mapping the EFO disease and disease staging branches to the Monarch Disease Ontology (MONDO) - using the Ontology X-ref Service (OxO) - and importing these mapped MONDO terms into EFO. All existing EFO terms have retained the EFO ID. The MONDO ID for each mapped term is available within the annotations as a cross reference. Any new terms imported from MONDO have retained their MONDO IDs.

All mapped terms (EFO terms and their MONDO mapped term) can be found in the mondo_efo_mappings.tsv file situated in the imports folder. This file contains on each line: the URI of the MONDO term, the URI of the EFO term, the MONDO label and the EFO label for each mapped pair. All terms that are mapped must be added to this file in order for the MONDO term to be extracted and merged into EFO. Additionally, all MONDO terms to be extracted that are listed in the mappings file are contained in the mondo_terms.txt file.

2018-10-15 EFO 2.101

15 Oct 10:19
Compare
Choose a tag to compare

EFO 2.101 October 2018 release

2018-09-17 EFO 2.100

17 Sep 09:45
Compare
Choose a tag to compare

EFO Release 2.100

2018-08-15 EFO 2.99

15 Aug 09:48
Compare
Choose a tag to compare
v2018-08-15

EFO release 2.99

2018-07-16 EFO 2.98

16 Jul 13:41
Compare
Choose a tag to compare

EFO 2.98 July 2018 release

2018-06-18 EFO 2.97

18 Jun 08:55
Compare
Choose a tag to compare

EFO 2.97 June 2018 release