Search Mailing List Archives


Limit search to: Subject & Body Subject Author
Sort by: Reverse Sort
Limit to: All This Week Last Week This Month Last Month
Select Date Range     through    

[protege-owl] bug in the processing of import statements in protege?

Allyson Lister a.l.lister at newcastle.ac.uk
Mon Jan 21 02:23:08 PST 2008


Hi all,

The developers of OBI (http://obi.sf.net) think we may have found a bug in
the way protege 3.3.* handles imports.

The syntax
<owl:imports
rdf:resource="http://protege.stanford.edu/plugins/owl/protege"/>

works fine, the syntax

   <owl:imports>
     <owl:Ontology rdf:about="http://purl.org/obo/owl/OBO_REL"/>
   </owl:imports>

doesn't :-)

What happens is that, irrespective of how you set the rdfs:label to be the
default view for the classes, not all of the class names are displayed
properly. The version that doesn't work in 3.3 and 3.3.1 *does* work in
Protege 4 Alpha. Weird... Does anyone know what's happening?

The attached file is one that loads, with the "working" import statement:
see how the annotations of the ontology are now displayed beautifully :-)
(creators etc). With this version it should also retrieve the
defaultLanguage value, and thus display the labels properly. The
defaultLanguage is set, but doesn't seem to be being picked up.

The file seems to be syntactically correct, but it would just be nice to
have protege displaying it correctly.


-- 
Thanks,
Allyson :)

Allyson Lister
Research Associate
Centre for Integrated Systems Biology for Ageing and Nutrition
Newcastle University
http://www.cisban.ac.uk
School of Computing Science
Newcastle University
Newcastle upon Tyne, NE1 7RU
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.stanford.edu/pipermail/protege-owl/attachments/20080121/3b566cf8/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OBI.owl
Type: application/octet-stream
Size: 835520 bytes
Desc: not available
URL: <http://mailman.stanford.edu/pipermail/protege-owl/attachments/20080121/3b566cf8/attachment.owl>


More information about the protege-owl mailing list