Re: Find and changa an Individual in a .owl file
Timothy Redmond <[email protected]> Mon, 27 Jan 2014 13:12:12 -0800
| Newsgroups | gmane.comp.misc.ontology.protege.general |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format.
--===============7386615294037439938==
Content-Type: multipart/alternative;
boundary="------------050202010001050805050500"
This is a multi-part message in MIME format.
--------------050202010001050805050500
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Hello,
My guess is that with a little more detail we will be able to quickly=20
figure this out. First, if possible it would be nice to see the ontology=
.
> I do have an Individual (own#real)
What is the full name of this individual? If for example, you meant=20
that the name is owl:real so that the full name is
http://www.w3.org/2002/07/owl#real
then this is probably the source of your problem. Using reserved names=20
(such as the names of datatypes) for your own use can lead to ambiguous=20
parsing by different owl parsers. It is possible that the parser used=20
by FaCT++ generated a different in memory version of your ontology than=20
the Protege parser did. It may be a bit tricky to tell by looking at=20
the rdf what the full name of the resource is.
> that does not exist in my ontology (it is not shown in Proteg=E9's=20
> Indivuduals tab) but exists according to the reasoner (FACT++).
By what means did FaCT++ tell you that the individual exists. Did you=20
run FaCT++ from the command line or otherwise? This may not be=20
important if my guess about your ontology is correct.
> The only similar Individual I have is called Real (notice the CAPS). =20
> I cannot use a DL SELECT command either because the reasoner complies=20
> about this issue. Thus, I opened the .owl file and found several=20
> owl#real occurrences. My question is: can i simply change real by Real=20
> in the .owl file with no side affects?
This may have to be done carefully. If the name of the "individual" in=20
question is
http://www.w3.org/2002/07/owl#real
then some of these references may represent the real datatype. You=20
would want to only change those that occur as the individual. You=20
should also at some point (maybe after getting this ontology to parse in=20
Protege as you expect it) change the namespace of these individuals so=20
that they are not in the owl: namespace.
> Version: 4.1
If by this you mean Protege 4.1, I would recommend that you upgrade to=20
Protege 4.2 if you can.
-Timothy
>
> TIA,
>
> Andre Luiz
>
> Version: 4.1
> OS: ubuntu 13.10
>
>
> _______________________________________________
> protege-discussion mailing list
> [email protected]
> https://mailman.stanford.edu/mailman/listinfo/protege-discussion
>
> Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.htm=
l#01a.03
--------------050202010001050805050500
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix"><br>
Hello,<br>
<br>
My guess is that with a little more detail we will be able to
quickly figure this out. First, if possible it would be nice to
see the ontology.<br>
<br>
</div>
<blockquote cite="mid:1390854549.5066.12.camel@sigmatech"
type="cite">
I do have an Individual (own#real)</blockquote>
<br>
What is the full name of this individual? If for example, you meant
that the name is owl:real so that the full name is<br>
<br>
<blockquote>
<pre><a class="moz-txt-link-freetext" href="http://www.w3.org/2002/07/owl#real">http://www.w3.org/2002/07/owl#real</a></pre>
</blockquote>
<br>
then this is probably the source of your problem. Using reserved
names (such as the names of datatypes) for your own use can lead to
ambiguous parsing by different owl parsers. It is possible that the
parser used by FaCT++ generated a different in memory version of
your ontology than the Protege parser did. It may be a bit tricky
to tell by looking at the rdf what the full name of the resource is.<br>
<br>
<blockquote cite="mid:1390854549.5066.12.camel@sigmatech"
type="cite"> that does not exist in my ontology (it is not shown
in Protegé's Indivuduals tab) but exists according to the reasoner
(FACT++). <br>
</blockquote>
<br>
By what means did FaCT++ tell you that the individual exists. Did
you run FaCT++ from the command line or otherwise? This may not be
important if my guess about your ontology is correct.<br>
<br>
<blockquote cite="mid:1390854549.5066.12.camel@sigmatech"
type="cite"> The only similar Individual I have is called Real
(notice the CAPS). I cannot use a DL SELECT command either
because the reasoner complies about this issue. Thus, I opened the
.owl file and found several owl#real occurrences. My question is:
can i simply change real by Real in the .owl file with no side
affects?<br>
</blockquote>
<br>
This may have to be done carefully. If the name of the "individual"
in question is <br>
<br>
<pre> <a class="moz-txt-link-freetext" href="http://www.w3.org/2002/07/owl#real">http://www.w3.org/2002/07/owl#real</a></pre>
<br>
then some of these references may represent the real datatype. You
would want to only change those that occur as the individual. You
should also at some point (maybe after getting this ontology to
parse in Protege as you expect it) change the namespace of these
individuals so that they are not in the owl: namespace.<br>
<br>
<blockquote type="cite">Version: 4.1</blockquote>
<br>
If by this you mean Protege 4.1, I would recommend that you upgrade
to Protege 4.2 if you can.<br>
<br>
-Timothy<br>
<br>
<br>
<blockquote cite="mid:1390854549.5066.12.camel@sigmatech"
type="cite">
<br>
TIA,<br>
<br>
Andre Luiz<br>
<br>
Version: 4.1<br>
OS: ubuntu 13.10
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
protege-discussion mailing list
<a class="moz-txt-link-abbreviated" href="mailto:[email protected]">[email protected]</a>
<a class="moz-txt-link-freetext" href="https://mailman.stanford.edu/mailman/listinfo/protege-discussion">https://mailman.stanford.edu/mailman/listinfo/protege-discussion</a>
Instructions for unsubscribing: <a class="moz-txt-link-freetext" href="http://protege.stanford.edu/doc/faq.html#01a.03">http://protege.stanford.edu/doc/faq.html#01a.03</a>
</pre>
</blockquote>
<br>
</body>
</html>
--------------050202010001050805050500--
--===============7386615294037439938==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
protege-discussion mailing list
[email protected]
https://mailman.stanford.edu/mailman/listinfo/protege-discussion
Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03
--===============7386615294037439938==--