First problem - what to import?
Simple question, but no immediately obvious answer. BTW has something changed here recently - as I seem to remember this being simple in the past??
I'm now importing OK from...
- SKOS: http://www.w3.org/2004/02/skos/core/owl-dl/skos-core-owl-dl.owl
- foaf:
http://xmlns.com/foaf/spec/index.rdf
I wouldn't expect too much drama here as these are well travelled paths?
foaf won't import...
INFO: Loading triplesCurious that I get different behaviour (on my OSX leopard system) depending on how I start Protege.
INFO: Start processing ontology: http://xmlns.com/foaf/spec/20070524.rdf Time: Thu Apr 03 11:42:43 NZDT 2008
WARNING: [ProtegeOWLParser] Warning: No default namespace found in file. Will use http://xmlns.com/foaf/spec/20070524.rdf -- DefaultProtegeOWLParserLogger.logWarning()
INFO: [ProtegeOWLParser] Completed triple loading after 646 ms
INFO: [TripleChangePostProcessor] Completed lists after 0 ms
java.lang.ClassCastException: edu.stanford.smi.protegex.owl.model.impl.DefaultRDFSNamedClass
at edu.stanford.smi.protegex.owl.model.triplestore.impl.OWLAnonymousClassPostProcessor.convertNamedEnumeratedClasses(Unknown Source)
at edu.stanford.smi.protegex.owl.model.triplestore.impl.OWLAnonymousClassPostProcessor.(Unknown Source)
at edu.stanford.smi.protegex.owl.model.triplestore.impl.TripleChangePostProcessor.postProcess(Unknown Source)....
...lots more
- from the protege.app the ontology loads, but the properties tab is broken (red box)
- from run_protoge.sh I get the error output above and the ontology doesn't load
And finally protege 4.0 (alpha) build 61, which Does work - however it's a completely new UI experience.
0 comments:
Post a Comment