At 6:18 PM -0700 4/11/07, Holger Knublauch wrote:
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
yes Holger, (and if he wanted a free, open source editor that could
handle it I would recommend SWOOP [1])
However, I think the bigger issue here is that there were (and I
believe still are) some weirdnesses in the machine readability of the
FOAF namespace ( http://xmlns.com/foaf/0.1 ) and that a number of
systems have problems with it (I notice if I try to load it directly
into SWOOP I still get XML parsing errors). Lots of systems have
done various work arounds for this -- so when you report your error
to the Protege mailing list, you might also send it to the FOAF one,
we've been complaining about this for a couple years now, maybe if
some other folks yell as well we can get it so that the most used
Semantic Web vocabulary will actually conform to the standards it
promotes :-)
-JH
[1] http://code.google.com/p/swoop/
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
--
How can you be in two places at once if you're not anywhere at all?
(Firesign Theatre, 1969)
Prof James Hendler http://www.cs.rpi.edu/~hendler
Tetherless World Constellation Chair 301-405-2696 (work)
Computer Science Dept 301-405-6707 (Fax)
Rensselaer Polytechnic Institute, Troy NY 12180
