Re: Issue with Problem Oriented Medical Record OWL Ontology

This seems to be a common problem with FOAF / ontologies importing FOAF and Protege, I have run into it several times. Honestly, I have not yet figured out the cause of this and almost suspect that Protege recognizes FOAF and tries to handle it in a special way (with unwanted side effects).

- Matthias


> Hi,
> 
> I'm new to Protege and ontologies, and I'm getting the following issue
> with
> the POMR ontology from Chimezie.
> 
> 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)
> The resource p1:chime has the rdf:type
> http://xmlns.com/foaf/0.1/Personwhich 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

-- 
"Feel free" - 10 GB Mailbox, 100 FreeSMS/Monat ...
Jetzt GMX TopMail testen: http://www.gmx.net/de/go/topmail

Received on Thursday, 12 April 2007 01:01:31 UTC