Re: protege-discussion Digest, Vol 90, Issue 18
André Luiz Tietböhl Ramos <[email protected]> Thu, 30 Jan 2014 18:32:00 -0200
| Newsgroups | gmane.comp.misc.ontology.protege.general |
|---|---|
| Message-ID | <1391113920.4972.14.camel@sigmatech> |
--===============2933889085534837379== Content-Type: multipart/alternative; boundary="=-X0XS/fcrZSkiUpL/vhQZ" --=-X0XS/fcrZSkiUpL/vhQZ Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Dear Timothy, Thanks for the very good explanation. Read below please. On Ter, 2014-01-28 at 12:05 -0800, [email protected] wrote: > > Message: 2 > Date: Mon, 27 Jan 2014 13:12:12 -0800 > From: Timothy Redmond <[email protected]> > To: [email protected] > Hello, > > 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. > > > I do have an Individual (own#real) > > 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 > > http://www.w3.org/2002/07/owl#real In order to solve this issue I deleted the individual however the error still shows up. How so? Would there be a "hidden" individual somewhere as cleverly show below? > 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. > > > that does not exist in my ontology (it is not shown in Proteg?'s > > Indivuduals tab) but exists according to the reasoner (FACT++). > > 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. I run FACT++ from the GUI. The message shown is: ReasonerInternalException. Unsupported datatype 'http://www.w3.org/2002/07/owl#real' > 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. Ok, thanks! I will when I'm good enough using Protege for I still don't know how to accomplish it effectively. > > Version: 4.1 > > If by this you mean Protege 4.1, I would recommend that you upgrade to > Protege 4.2 if you can. Yes, it is Protege version 4.1. Using 4.2b or 4.3 doesn't help much either. Sincerely, Andre Luiz --=-X0XS/fcrZSkiUpL/vhQZ Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: 7bit <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8"> <META NAME="GENERATOR" CONTENT="GtkHTML/4.6.6"> </HEAD> <BODY> Dear Timothy,<BR> <BR> Thanks for the very good explanation. Read below please.<BR> <BR> <BR> On Ter, 2014-01-28 at 12:05 -0800, [email protected] wrote:<BR> <BR> <BLOCKQUOTE TYPE=CITE> <PRE> Message: 2 Date: Mon, 27 Jan 2014 13:12:12 -0800 From: Timothy Redmond <<A HREF="mailto:[email protected]">[email protected]</A>> To: <A HREF="mailto:[email protected]">[email protected]</A> Hello, 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. <FONT COLOR="#737373">> I do have an Individual (own#real)</FONT> 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 <A HREF="http://www.w3.org/2002/07/owl#real">http://www.w3.org/2002/07/owl#real</A> </PRE> </BLOCKQUOTE> <BR> In order to solve this issue I deleted the individual however the error still shows up. How so? Would there be a "hidden" individual somewhere as cleverly show below?<BR> <BR> <BLOCKQUOTE TYPE=CITE> <PRE> 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. <FONT COLOR="#737373">> that does not exist in my ontology (it is not shown in Proteg?'s </FONT> <FONT COLOR="#737373">> Indivuduals tab) but exists according to the reasoner (FACT++).</FONT> 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. </PRE> </BLOCKQUOTE> <BR> I run FACT++ from the GUI. The message shown is:<BR> <BR> ReasonerInternalException. Unsupported datatype '<A HREF="http://www.w3.org/2002/07/owl#real'">http://www.w3.org/2002/07/owl#real'</A><BR> <BR> <BLOCKQUOTE TYPE=CITE> <PRE> 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. </PRE> </BLOCKQUOTE> <BR> Ok, thanks! I will when I'm good enough using Protege for I still don't know how to accomplish it effectively. <BR> <BR> <BLOCKQUOTE TYPE=CITE> <PRE> <FONT COLOR="#737373">> Version: 4.1</FONT> If by this you mean Protege 4.1, I would recommend that you upgrade to Protege 4.2 if you can. </PRE> </BLOCKQUOTE> <BR> Yes, it is Protege version 4.1. Using 4.2b or 4.3 doesn't help much either.<BR> <BR> Sincerely,<BR> <BR> Andre Luiz <PRE> <TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%"> <TR> <TD> <BR> <BR> </TD> </TR> </TABLE> </PRE> </BODY> </HTML> --=-X0XS/fcrZSkiUpL/vhQZ-- --===============2933889085534837379== 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 --===============2933889085534837379==--