Re: Issue with Problem Oriented Medical Record OWL Ontology

Noah Cohen wrote:
> Hi,
> 
> I'm new to Protege and ontologies, and I'm getting the following issue 
> with the POMR ontology from Chimezie.

You may want to address the protege-owl mailing list with this problem.

Also note that Protege is not the only ontology editor in the world. 
For example TopBraid Composer [1] can open this file without problems. 
While this is a commercial tool, you can exploit a free 30 days 
evaluation period.

Holger

[1] http://www.topbraidcomposer.com


> I have protege version 3.2.1 build 365 and JDK 1.5.0
> 
> If I run this ontology through a verifier, it verifies the ontology 
> seemingly without a problem. 
> 
> If i try to load the ontology directly from 
> http://metacognition.info/ontologies/problem-oriented-medical-record.owl 
> I get some very interesting error:
> 
> WARNING: [ProtegeOWLParser] Warning: Trying to add import for external 
> resource:
>  http://purl.org/dc/elements/1.1/ -- 
> DefaultProtegeOWLParserLogger.logWarning()
> INFO: [ProtegeOWLParser] Importing http://purl.org/dc/elements/1.1/ 
> (from Redire
> ct to http://protege.stanford.edu/plugins/owl/dc/protege-dc.owl 
> <http://protege.stanford.edu/plugins/owl/dc/protege-dc.owl>)
> The resource p1:chime has the rdf:type http://xmlns.com/foaf/0.1/Person 
> which is
>  not a class but a 
> edu.stanford.smi.protegex.owl.model.impl.DefaultRDFUntypedRes
> ource
> Suggestion: In many cases the problem is a missing owl:imports statement 
> to the
> classes file which defines the correct type of 
> http://xmlns.com/foaf/0.1/Person
> 
> 
> It seems to me that it cannot distinguish the foaf Person class, with or 
> without the foaf imports statement. 
>  
> If someone could please assist here, it would be of great help.  Thank 
> you in advance,
> Noah
>

Received on Thursday, 12 April 2007 01:18:38 UTC