Use of namespace prefixes in import statements for Turtle documents causes failures when using OWLAPI

Question

If an ontology being saved (using OWLAPI) in Turtle format uses a set of prefixes, the import statements for the imported ontologies, use the declared prefixes. The ontology thus saved using the prefixes cannot be read back by the OWLAPI Turtle parser. The import statement is flagged as source of the problem.

Lets say Onto2 imports Onto1 and Onto3 (see below for declarations). Saving Onto2 results in following:

@prefix : <http://example.com/ontology/Onto2#> .
@prefix OT1: <http://example.com/ontology/Onto1> .
@prefix OT2: <http://example.com/ontology/Onto2> .
@prefix OT3: <http://example.com/ontology/Onto3> .

<http://example.com/ontology/Onto2> rdf:type owl:Ontology ;
                                     owl:imports OT1:# ,
                                                 OT3:# .

When Onto2 is read back by the OWLAPI Turtle parser, it complains

org.openrdf.rio.RDFParseException: Expected '.', found 'O' [line 13]

The import statement is on line 13.

Please share enough code for us to reproduce the problem. See [mcve] for more information. — Sumurai8, Sep 09 '16 at 13:45
Thanks. This was indeed the problem - incorrect use of API resulting in the invalid Turtle. — Nilesh, Sep 19 '16 at 17:46

score 1 · Accepted Answer · answered Sep 10 '16 at 10:41

1

From the Turtle language specs, I think the problem is the hash character. It is not allowed in that position, where it will be interpreted as the start of a comment. See here for details.

answered Sep 10 '16 at 10:41

Ignazio

10,504
1
14
25

Use of namespace prefixes in import statements for Turtle documents causes failures when using OWLAPI

1 Answers1