Formats - owlcs/ont-api GitHub Wiki

Configuration

Both Apache Jena and OWL-API formats are supported by ONT-API. But standalone ONT-API(ver. 1.1.0) includes only formats from jena-arq project dependency. If you want to enable all known syntaxes please include jena-csv, owlapi-rio (with owlapi-parsers inside) and owlapi-oboformat dependencies to your maven pom.xml. Note: jena-csv is a very tolerant format: almost any text file could be treated as it, so without clarification any document source will be read as cvs in case no more suitable format syntax found.

Full list of supported formats

# Name Provider Read / Write
1 TURTLE Apache Jena yes / yes
2 RDF_XML Apache Jena yes / yes
3 RDF_JSON Apache Jena yes / yes
4 JSON_LD Apache Jena yes / yes
5 NTRIPLES Apache Jena yes / yes
6 NQUADS Apache Jena yes / yes
7 TRIG Apache Jena yes / yes
8 TRIX Apache Jena yes / yes
9 RDF_THRIFT Apache Jena yes / yes
10 CSV Apache Jena yes / no
11 OWL_XML OWL-API yes / yes
12 MANCHESTER_SYNTAX OWL-API yes / yes
13 FUNCTIONAL_SYNTAX OWL-API yes / yes
14 BINARY_RDF OWL-API yes / yes
15 RDFA OWL-API yes / no
16 OBO OWL-API yes / yes
17 KRSS OWL-API no / no
18 KRSS2 OWL-API yes / yes
19 DL OWL-API yes / yes
20 DL_HTML OWL-API no / yes
21 LATEX OWL-API no / yes

OWL-API (ver. 5.1.4) remarks

Some of the OWL-API formats do not work as expected, e.g. KRSS2, DL and OBO do not pass reload test: the list of significant axioms do not match after sequential saving and loading. KRSS was excluded deliberately to match OWL-API state.

See also