Search Mailing List Archives
[protege-owl] default namespace ssue
tredmond at stanford.edu
Wed Oct 8 15:11:32 PDT 2008
I am not sure that I replicated your scenario. The closest that I
came was to open an owl ontology that did not have an xml base or a
default namespace. In this case, Protege used the location of the
ontology as the xml base and as the name of the ontology. This is non-
optimal but there is no information to the contrary. Also this is
what the w3 specifications state. New classes are then also created
using this inferred xml-base.
If this is what happened then it can be fixed in the Metadata tab.
First the ontology should be given a more meaningful name. Second, a
default namespace can be added by clicking the + button in the
Namespace prefixes box. The reason that the default namespace box is
not editable is that we wanted to save that until we had written the
refactor routines. In other words, we believe that it will often be
the case that when a user changes the default namespace the user also
wants to change the name of all the entities in the ontology that use
that namespace in their full name. We have not written these
routines though I believe that these do exist in Protege 4.
So as a general rule the default namespace can be added or changed in
the Namespace Prefixes box.
On Oct 8, 2008, at 1:25 AM, Bert Van Nuffelen wrote:
> the last builds of protege 3.4 (50xx) have a bug in the default
> namespace resolution.
> On the metadata tab the default namespace is always greyed and empty.
> When saving the file the default namespace is set to "file://xxx/yy/xx/
> In combination with the SWRL editor the default namespace
> e.g. "http://www.myapp.com/app/myont.owl" is
> interpreted as a file reference, where myont.owl is the file name and
> "http://www.myapp.com/app/" is the prefix which becomes
> the default namespace.
> As a consequence new instance (e.g. variable) refer to the wrong
> namespace and everything
> goes out of sync.
> protege-owl mailing list
> protege-owl at lists.stanford.edu
> Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03
More information about the protege-owl