Public | Automated Build

Last pushed: 6 months ago
Short Description server loaded with the VFB.owl ontology
Full Description

To run:
docker run -d --name aberowl-vfb -p 31337:31337 virtualflybrain/aberowl-vfb

Note: to keep the container small loading latest ontology is done at runtime and takes a few minutes before the server is started hence no response will be given on port 31337 until the server is ready to go.

readiness test:

For full spects of the api see: (no longer available)

Copy of AberOWL documentation:

[This is Google's cache of It is a snapshot of the page as it appeared on 13 Nov 2017 15:55:09 GMT.]

AberOWL Help
AberOWL (pronounced /藢忙b蓹藞ra蕣l/) is a framework for ontology-based access to biological data. It consists of a repository of bio-ontologies, a set of webservices which provide access to OWL(-EL) reasoning over the ontologies, and several frontends which utilise the ontology repository and reasoning services to provide access to specific biological datasets.

Web Repository
The web-based repository front-end provides many features underpinned by reasoned access to ontologies.

Upload and immediate classification of ontologies.
Semantic querying of ontologies using Manchester OWL Syntax.
Query Pubmed and PubMed central articles using ontology terms.
Ontology-based access to RDF/Linked data through SPARQL integration.
Uploading ontologies
To do this you must first create an account, then fill out the form on the upload page. It is probably a good idea to check whether an ontology exists first. You can also upload new versions of an existing ontology once you have claimed it.

Claiming ontologies
To claim an ontology, and gain the ability to manage it and upload new versions, you should send an email to Luke or

Querying ontologies
Class Query
AberOWL provides semantic access to ontologies. It performs OWL-EL reasoning over a repository of ontologies using the ELK reasoner and answers queries over single ontologies or the full AberOWL ontology repository. Ontologies in AberOWL are identified by their name, and queries are performed in Manchester OWL Syntax. Class names in Manchester OWL syntax are rendered using the rdfs:label property of the class, and class names containing a space are surrounded by single quotes. To query an OWL class description, type the class description in Manchester OWL syntax in the query box. Make sure to select the kind of query: retrieve subclasses, equivalent classes, or superclasses of the class description.

PubMed Query
AberOWL: Pubmed is a semantic search engine for Pubmed and Pubmed Central. We maintain an index of Medline abstracts and fulltext articles in Pubmed Central. AberOWL: Pubmed takes an OWL query as input, an ontology, and query type (subclass, superclass, equivalent), retrieves all classes satisfying the query from AberOWL, and constructs a query based on the disjunction of class names. Relevant documents are then retrieved from a local Apache Lucene-based repository of abstracts and articles. PubMed queries can be accessed on the frontpage or for each ontology. When the PubMed tab in an ontology view is opened, a PubMed query is automatically executed to retrieve documents from PubMed and PubMed Central in which the queried concept occurs.

AberOWL: SPARQL provides semantic access to Linked Data by incorporating OWL reasoning within the SPARQL syntax. In particular, AberOWL: SPARQL performs query expansion based on SPARQL syntax extended by the following construct:

OWL [querytype] [<AberOWL service URI>] [<ontology name>] { [OWL query] }
For example, the query
OWL subclass <GO> { part_of some 'apoptotic process' }
will return a set of class URIs that satisfy the query part_of some 'apoptotic process' in the Gene Ontology.
There are two main forms in which the OWL statement can be embedded within a SPARQL query. The first is the VALUES form, in which the results of the OWL query are bound to a variable using the SPARQL VALUES statement. For example,

VALUES ?ontid {
OWL subclass <> { part_of some 'apoptotic process' }
will bind the ontology URIs resulting from the OWL query (part_of some 'apoptotic process') to the variable ?ontid.
The second use of the OWL statement is in the form of a FILTER statement. For example, the query

?ontid IN ( OWL subclass { arrhythmia } )
will filter the results of a SPARQL query such that the values of ?ontid must be in the result list of the OWL query.
As many SPARQL endpoints use different IRIs to refer to classes in ontologies, we have added the possibility to redefine prefixes for the

resulting ontology classes such that they match the IRI scheme used by a particular SPARQL endpoint. To use this feature, the "Use OBO-style URIs" checkbox must be selected. This will transform the class IRIs resulting from an OWL query into OBO-style prefix form and will add the appropriate prefix to the SPARQL query if it has not been defined in the query itself. For example, the UniProt SPARQL endpoint ( uses the URI pattern "<id>" to refer to Gene Ontology classes (instead of the standard "<id>". Adding the prefix definition
to the SPARQL query and selecting the "Use OBO-style URIs" option will perform the query over UniProt.
The API root is
This runs a Manchester OWL Syntax query against the server.
A query for subclasses and equivalent classes in GO for 'part of' some 'apoptotic process':'part of' some 'apoptotic process'&ontology=GO&labels=true,

The same query using IRIs instead of labels: some
Name Type Optional Default Description
query string no None The Manchester OWL Syntax query
type string yes subeq The classes to return related to the query. One of subclass, superclass, subeq, supeq, equivalent.
ontology string yes An ontology to run the query against. If not provided, query will be run against all ontologies in the repository.
labels boolean yes false Whether to allow labels in the query. By default, URIs must be used.
direct boolean yes false Whether to retrieve only direct subclasses or superclasses. Ignored for equivalent queries.
This provides partial matches on labels.
A query for 'ventricular' in the Human Phenotype Ontology:

and the same query over all ontologies:
Name Type Optional Default Description
term string no None A partial class name.
ontology string yes An ontology to run the query against. If not provided, query will be run against all ontologies in the repository.
Retrieve one particular class from an ontology, by label name.
Name Type Optional Default Description
query string no None A label of the class to retrieve.
ontology string no None An ontology to run the query against.
Given a reference to a particular class by label and ontology, retrieve a route back to the root of the ontology.
Name Type Optional Default Description
query string no None A label of the class to retrieve.
ontology string no None An ontology to run the query against.
This provides stats on either one ontology, or all ontologies in the database.
Name Type Optional Default Description
ontology string yes An ontology to retrieve stats for. If not provided, total stats will be returned for the whole repository.
Return a list of all the ontologies in the repository.
Return a list of all the ontologies in the repository, with associated load statuses.
Frequently Asked Questions
Where can I read more?
You can read the paper about AberOWL here.

What technology does AberOWL use?
The AberOWL server is built using the Groovy programming language, and builds on the OWL-API library. Reasoning is performed using the ELK reasoner.

The ontology repository is built using NodeJS, and, er, HTML (Jade) and shares a Redis instance with the AberOWL server backend.

Where is the source?
Check it at GitHub

Where to get more help or send feature requests/suggesetions?
You can open an issue on our GitHub or ask questions on our mailing list.

Can I get a log of the queries performed on AberOWL, and their execution time?
Yes, you can find a log at The log is updated in real time and shows the query that is run, the type of query (empty means subeq), the ontology that is queries (empty means all ontologies), a flag that shows whether only direct sub- or superclasses are queried (empty means false), whether labels are used in the query (empty means false), the number of classes returned, and the execution time of the query..

Who works on AberOWL?
George Gkoutos (Aberystwyth University)
Luke Slater (King Abdullah University of Science and Technology)
Paul Schofield (University of Cambridge)
Robert Hoehndorf (King Abdullah University of Science and Technology)
Can you show me all the unsatisfiable classes across all ontologies?

How do I cite AberOWL?
To cite AberOWL, please use the following reference:

AberOWL: a framework for ontology-based data access in biology. Hoehndorf, R; Slater, L; Schofield, PN; Gkoutos, Georgios V. BMC Bioinformatics 16:26, 2015.

AberOWL is jointly developed by researchers from King Abdullah University of Science and Technology, the University of Birmingham, and the University of Cambridge.

Docker Pull Command