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] Loading the OWL version in protege 3.4 RC1

Allyson Lister a.l.lister at
Mon Mar 9 00:53:40 PDT 2009

Hi Thomas,

Thanks very much for your thoughts. Indeed, I am only wanting to import this
file into another ontology, so I don't need to be doing any editing of the
MathML sections.

I've done a global search and replace of all "<math>" tags (opening and
closing), replacing with mathml:math - and adding an xmlns:mathml to the
header. This has meant that the default namespace is now being read
correctly. However, I have what seems to be a related problem.

When I try to import the ontology into another one, with my repository file
as so:

[Dublin Core DL Redirect]

then I get an error from Protege telling me that it cannot find the
namespace Even if I try to tell it that file
explicitly, it still says it cannot find that namespace. Do you have any

Why would Protege give such an error when reading in this file for an

Thanks very much!

2009/3/6 Thomas Russ <tar at>

> On Mar 6, 2009, at 10:09 AM, Allyson Lister wrote:
> > Hi all,
> >
> > I downloaded today's sbo OWL file (attached) and opened it in
> > protege 3.4 RC1 on a machine running ubuntu intrepid 64 bit.
> >
> > As you can see from the attached screenshot, for some reason the
> > default namespace is set to MathML - and this is with having the
> > default namespace *actually* set to SBO, as the excerpt of the OWL
> > file below prooves:
> >
> > <rdf:RDF
> >     xmlns=""
> >     xmlns:rdf=""
> >     xmlns:owl=""
> >     xmlns:daml=""
> >     xmlns:rdfs=""
> >   xml:base="">
> >
> > So, why is Protege doing this? Do you have any idea? I've sent to
> > both protege owl and SBO. Perhaps somehow I've managed to set
> > something incorrectly?
> I suspect that somehow the parsing is getting confused by encountering
> the MathML markup tags, which look like
>  <math xmlns="">
> and introduce their own default namespace.  Now, according to the XML
> parsing rules, that should be a local effect, valid only inside the
> scope of the tag, but perhaps there is a bug in the parser or
> namespace handler used by Protege that ends up keeping the last such
> namespace encountered, instead of properly respecting the namespace
> scoping rules.
> As a work-around, perhaps what you need to do is to introduce a math:
> prefix and use that for the MathML parts.  Since they have structured
> parts with their own sub-tags, this could get a bit tedious, although
> it may be possible to do this using some sort of editor script.
> I'm not quite sure how Protege will handle the RDF literal parses of
> the MathML objects, though.
> _______________________________________________
> protege-owl mailing list
> protege-owl at
> Instructions for unsubscribing:


Allyson Lister

Newcastle University
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the protege-owl mailing list