Principle: Common Format (principle 2)
- Overview
- Open (principle 1)
- Common Format (principle 2)
- URI/Identifier Space (principle 3)
- Versioning (principle 4)
- Scope (principle 5)
- Textual Definitions (principle 6)
- Relations (principle 7)
- Documentation (principle 8)
- Documented Plurality of Users (principle 9)
- Commitment To Collaboration (principle 10)
- Locus of Authority (principle 11)
- Naming Conventions (principle 12)
- Notification of Changes (principle 13)
- Maintenance (principle 16)
- Responsiveness (principle 20)
GO TO: Recommendations/Requirements | Implementation | Examples/Counter‑Examples | Criteria for Review | Feedback/Discussion
Summary
The ontology is made available in a common formal language in an accepted concrete syntax.
Purpose
A common format allows the maximum number of people to access and reuse an ontology.
Recommendations and Requirements
All ontologies MUST have at least one OWL product whose name corresponds to the registered prefix (e.g., ‘GO’ –> go.owl, ‘OBI’ –> obi.owl). Thus the ontology whose IRI is http://purl.obolibrary.org/obo/ro.owl (known to the OBO Foundry as ‘RO’), must have at least the product ro.owl. Developers are free to use whatever combination of technologies and formats is appropriate for development. However, the official OWL PURL (see Principle 3) for the ontology MUST resolve to a syntactically valid OWL file using the RDF-XML syntax.
Developers can OPTIONALLY produce ontologies in other formats. These are conventionally the same IRI as the owl, but with .owl changed to the relevant extension (e.g., ‘.obo’, ‘.json’). Note that such products are not listed by default. If you produce an additional format product, you should register it under the ‘products’ field in the appropriate metadata file found in this folder.
Implementation
ROBOT offers functionality to convert a variety of formats, including OBO, to RDF/XML. Protégé allows you to save ontologies in RDF/XML, as well. The Ontology 101 Tutorial has directions on starting and saving in Protégé.
Examples
-
The Gene Ontology is maintained as OBO-Format. It is automatically converted to OWL and is available in both OBO and OWL via the OBO Foundry.
-
The ChEBI ontology is maintained in a relational database using a custom schema, but makes an OBO-Format file available that is automatically converted to OWL. It is available in both OBO and OWL via the OBO Foundry.
-
OBI is maintained as an OWL ontology.
Counter-Examples
An ontology that is in Frames format, OWL/XML, or OWL Manchester Syntax.
Criteria for Review
The ontology MUST be available in RDF/XML format.
This check is automatically validated. The automatic check fully covers the requirements for this principle.
Feedback and Discussion
To suggest revisions or begin a discussion pertaining to this principle, please create an issue on GitHub.
To suggest revisions or begin a discussion pertaining to the automated validation of this principle, please create an issue on GitHub.