#obo #ontology #validation

bin+lib fastobo-validator

Faultess validation tool for OBO products

9 releases

✓ Uses Rust 2018 edition

0.2.4 Feb 13, 2020
0.2.3 Aug 7, 2019
0.2.2 Jul 23, 2019
0.2.0 Jun 13, 2019
0.1.2 May 25, 2019

#196 in Science

Download history 1/week @ 2020-02-29 20/week @ 2020-03-07 10/week @ 2020-03-14 27/week @ 2020-03-21 10/week @ 2020-03-28 11/week @ 2020-04-04 55/week @ 2020-04-11 2/week @ 2020-04-18 1/week @ 2020-04-25 1/week @ 2020-05-02 1/week @ 2020-05-16 10/week @ 2020-05-23 18/week @ 2020-05-30 9/week @ 2020-06-06 9/week @ 2020-06-13

67 downloads per month

MIT and MPL-2.0 licenses


fastobo-validator Star me

Faultess validation tool for OBO products.

TravisCI License Source Binaries Crate Changelog GitHub issues


fastobo-validator is a command-line tool to validate an OBO file in format version 1.4 against the latest specification.


fastobo-validator is distributed as a pre-built binary for the following platforms:

Simply download the archive, and unpack the fastobo-validator binary somewhere in your $PATH. For other OS (notably Windows), you'll need to build the binary from source. Make sure to have the Rust compiler installed (check the installation methods) and simply run cargo install fastobo-validator to install the binary in your $CARGO_HOME folder.




The syntax of the OBO format version 1.4 has been made more restrictive compared to the format version 1.2, but files produces by modern tools (such as ROBOT) should already be compliant with this version.


ISBN validation (-I)

ISBN identifiers embed a validation digit which can be used to validate a given code without querying an external database. Enabling this validation check will process all ISBN-prefixed identifiers for a valid ISBN. It will not check ISBN10 or ISBN13-prefixed identifiers.


Simply run the binary against one or more OBO files:

$ fastobo-validator go.obo

The validator will then parse and validate each OBO product, and return with a non-null error code if any error was detected, displaying a small report for each error.


Found a bug ? Have an enhancement request ? Head over to the GitHub issue tracker of the project if you need to report or ask something. If you are filling in on a bug, please include as much information as you can about the issue, and try to recreate the same bug in a simple, easily reproducible situation.


This project is currently being developed by Martin Larralde as part of a Master's Degree internship in the BBOP team of the Lawrence Berkeley National Laboratory, under the supervision of Chris Mungall.


~136K SLoC