Here's the ontology in question: <a href="http://www.dayf.de/2004/owl/beer.owl">http://www.dayf.de/2004/owl/beer.owl</a><br>
<br>
The fact that it redefined &quot;Hops&quot; at line line 169 causes redland to
produce incorrect triples. Changing that like to rdf:about=&quot;#Hope&quot;
allows redland to proceed as normal.<br>
<br>
These are the triples resulting from the original file<br>
<br>
<span style="font-family: courier new,monospace;">&lt;<a href="http://www.purl.org/net/ontology/beer#Hops">http://www.purl.org/net/ontology/beer#Hops</a>&gt;
&lt;<a href="http://www.w3.org/1999/02/22-rdf-syntax-ns#type">http://www.w3.org/1999/02/22-rdf-syntax-ns#type</a>&gt;
&lt;<a href="http://www.w3.org/2002/07/owl#Class">http://www.w3.org/2002/07/owl#Class</a>&gt; .</span><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;">_:r1r1 &lt;<a href="http://www.w3.org/1999/02/22-rdf-syntax-ns#type">http://www.w3.org/1999/02/22-rdf-syntax-ns#type</a>&gt; &lt;<a href="http://www.w3.org/2000/01/rdf-schema#label">
http://www.w3.org/2000/01/rdf-schema#label</a>&gt; .</span><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;">&lt;<a href="http://www.purl.org/net/ontology/beer#Hops">http://www.purl.org/net/ontology/beer#Hops</a>&gt; &lt;<a href="http://www.w3.org/2002/07/owl#Class">http://www.w3.org/2002/07/owl#Class
</a>&gt; _:r1r1 .</span><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;">_:r1r1 &lt;<a href="http://www.w3.org/1999/02/22-rdf-syntax-ns#type">http://www.w3.org/1999/02/22-rdf-syntax-ns#type</a>&gt; &lt;<a href="http://www.w3.org/2000/01/rdf-schema#subClassOf">
http://www.w3.org/2000/01/rdf-schema#subClassOf</a>&gt; .</span><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;">_:r1r1 &lt;<a href="http://www.w3.org/1999/02/22-rdf-syntax-ns#resource">http://www.w3.org/1999/02/22-rdf-syntax-ns#resource
</a>&gt; &quot;#Ingredient&quot; .</span><br>
<br>
</span>And these are triples with a change to rdf:about=&quot;#Hops&quot;<br>
<span style="font-family: courier new,monospace;"><br>
&lt;<a href="http://www.purl.org/net/ontology/beer#Hops">http://www.purl.org/net/ontology/beer#Hops</a>&gt;
&lt;<a href="http://www.w3.org/1999/02/22-rdf-syntax-ns#type">http://www.w3.org/1999/02/22-rdf-syntax-ns#type</a>&gt;
&lt;<a href="http://www.w3.org/2002/07/owl#Class">http://www.w3.org/2002/07/owl#Class</a>&gt; .</span><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;">&lt;<a href="http://www.purl.org/net/ontology/beer#Hops">http://www.purl.org/net/ontology/beer#Hops</a>&gt; &lt;<a href="http://www.w3.org/2000/01/rdf-schema#label">http://www.w3.org/2000/01/rdf-schema#label
</a>&gt; &quot;Hops&quot;@en .</span><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;">&lt;<a href="http://www.purl.org/net/ontology/beer#Hops">http://www.purl.org/net/ontology/beer#Hops</a>&gt;
&lt;<a href="http://www.w3.org/2000/01/rdf-schema#subClassOf">http://www.w3.org/2000/01/rdf-schema#subClassOf</a>&gt;
&lt;<a href="http://www.purl.org/net/ontology/beer#Ingredient">http://www.purl.org/net/ontology/beer#Ingredient</a>&gt; .</span><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;">&lt;<a href="http://www.purl.org/net/ontology/beer#Hops">http://www.purl.org/net/ontology/beer#Hops</a>&gt; &lt;<a href="http://www.w3.org/2000/01/rdf-schema#label">http://www.w3.org/2000/01/rdf-schema#label
</a>&gt; &quot;Vine&quot;@en .</span><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;">&lt;<a href="http://www.purl.org/net/ontology/beer#Hops">http://www.purl.org/net/ontology/beer#Hops</a>&gt; &lt;<a href="http://www.w3.org/2000/01/rdf-schema#label">http://www.w3.org/2000/01/rdf-schema#label
</a>&gt; &quot;Hopfen&quot;@de .</span><br>
<br>
Is there a way to get the parser to deal with this on its own? I can't
seem to think of a way that I could work around this. I know its a
problem with a file, but I know for a fact that other OWL parsers
(particularly Jena and OWLAPI) handle this gracefully. I'll poke around
some more, but your help would be greatly appreciated!<br>-- <br>- Boris