From: Timothy R. <tre...@st...> - 2008-03-05 23:53:23
|
I have replicated the problem on a small owl file. The example could probably be made smaller but it is pretty small. Opening top.owl in Protege 4 leads to the same funny results described below. -Timothy On Wed, 2008-03-05 at 14:48 -0800, Timothy Redmond wrote: > When one tries to load the birnlex annotation properties ontology [1] > into the Protege 4 owl editor some strange things happen. For some > reason the annotation properties annotationPropertyDomain and > annotationPropertyRange both appear as Datatype properties. Presumably > because of this annotation properties (hasCurationStatus) appear in the > individuals tab. The obvious theories are > > 1. the birnlex ontology has a bug > 2. the owlapi has a bug > 3. Protege has a bug. > > We did some looking in the birnlex ontology and didn't see what was > causing the problem. There is a broken import but this doesn't seem to > cause the problem. It is not caused by the Protege3 annotation + > datatype property declarations. In fact the birnlex group has gone to > some trouble to root these out. There are several annotation properties > being applied to annotation properties but this seemed to work on small > examples. We were unable to figure out where things went wrong and did > not succeed in making a smaller example of the problem. > > Even if (1) is the case it would be nice if something good could happen > in this case so that these users could continue to use the owl api. > > -Timothy > > > [1] > http://purl.org/nbirn/birnlex/ontology/annotation/BIRNLex_annotation_properties.owl > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Owlapi-developer mailing list > Owl...@li... > https://lists.sourceforge.net/lists/listinfo/owlapi-developer |