Ontology parser breaks if definitions are out of order
This extract from the FOAF vocabulary...
foaf:aimChatID
a rdf:Property, owl:DatatypeProperty, owl:InverseFunctionalProperty ;
rdfs:comment "An AIM chat ID" ;
rdfs:domain foaf:Agent ;
rdfs:isDefinedBy <http://xmlns.com/foaf/0.1/> ;
rdfs:label "AIM chat ID" ;
rdfs:range rdfs:Literal ;
rdfs:subPropertyOf foaf:nick ;
vs:term_status "testing" .
foaf:nick
a rdf:Property, owl:DatatypeProperty ;
rdfs:comment "A short informal nickname characterising an agent (includes login identifiers, IRC and other chat nicknames)." ;
rdfs:isDefinedBy <http://xmlns.com/foaf/0.1/> ;
rdfs:label "nickname" ;
vs:term_status "testing" .
... raises the following error:
(tracker endpoint:36678): Tracker-CRITICAL **: 17:07:31.015: file:///.../10-foaf.ontology: Unknown property http://xmlns.com/foaf/0.1/nick
I don't think this is correct behaviour. The workaround is to reorder the definition of foaf:nick
before the foaf:aimChatId
. (Or delete the aimChatId altogether since AIM no longer matters to anyone :)