Import OWL (error)

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

Import OWL (error)

Oscar Pereira-4

Hi,

 

 

When I try to import the following ontology from a file (c:\protege.owl”)

 

<rdf:RDF

    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"

    xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"

    xmlns:owl="http://www.w3.org/2002/07/owl#"

    xmlns:base="http://qqSitio/protege"

    xmlns="http://qqSitio/protege#"

    xmlns:daml="http://www.daml.org/2001/03/daml+oil#">

  <owl:Class rdf:ID="Country"/>

  <Country rdf:ID="Italy"/>

</rdf:RDF>

 

Into an empty ontology, Protege raises the following errors.

 

 

java.lang.ClassCastException: edu.stanford.smi.protegex.owl.model.impl.DefaultRDFUntypedResource

            at edu.stanford.smi.protegex.owl.model.factory.OWLJavaFactory.createSimpleInstance(OWLJavaFactory.java:233)

            at edu.stanford.smi.protegex.owl.model.factory.OWLJavaFactoryUpdater.createNewFrame(OWLJavaFactoryUpdater.java:62)

            at edu.stanford.smi.protegex.owl.model.factory.OWLJavaFactoryUpdater.<init>(OWLJavaFactoryUpdater.java:38)

            at edu.stanford.smi.protegex.owl.model.factory.OWLJavaFactoryUpdater.run(OWLJavaFactoryUpdater.java:134)

            at edu.stanford.smi.protegex.owl.jena.triplestore.JenaTripleStoreModel.endTripleStoreChanges(JenaTripleStoreModel.java:71)

            at edu.stanford.smi.protegex.owl.jena.parser.ProtegeOWLParser.run(ProtegeOWLParser.java:498)

            at edu.stanford.smi.protegex.owl.jena.parser.ProtegeOWLParser.run(ProtegeOWLParser.java:442)

            at edu.stanford.smi.protegex.owl.jena.parser.ProtegeOWLParser.run(ProtegeOWLParser.java:437)

            at edu.stanford.smi.protegex.owl.jena.parser.ProtegeOWLParser.run(ProtegeOWLParser.java:629)

            at edu.stanford.smi.protegex.owl.jena.JenaOWLModel.load(JenaOWLModel.java:196)

            at edu.stanford.smi.protegex.owl.jena.JenaOWLModel.load(JenaOWLModel.java:220)

            at edu.stanford.smi.protegex.owl.jena.JenaKnowledgeBaseFactory.loadKnowledgeBase(JenaKnowledgeBaseFactory.java:143)

            at edu.stanford.smi.protege.model.Project.loadDomainKB(Unknown Source)

            at edu.stanford.smi.protege.model.Project.createDomainKnowledgeBase(Unknown Source)

            at edu.stanford.smi.protege.model.Project.<init>(Unknown Source)

            at edu.stanford.smi.protege.model.Project.<init>(Unknown Source)

            at edu.stanford.smi.protege.model.Project.loadProjectFromURI(Unknown Source)

            at edu.stanford.smi.protege.ui.ProjectManager.loadProjectFromURI(Unknown Source)

            at edu.stanford.smi.protege.ui.ProjectManager.loadProject(Unknown Source)

            at edu.stanford.smi.protege.ui.ProjectMenuBar$1.actionPerformed(Unknown Source)

            at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)

            at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source)

            at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)

            at javax.swing.DefaultButtonModel.setPressed(Unknown Source)

            at javax.swing.AbstractButton.doClick(Unknown Source)

            at javax.swing.plaf.basic.BasicMenuItemUI.doClick(Unknown Source)

            at javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(Unknown Source)

            at java.awt.Component.processMouseEvent(Unknown Source)

            at javax.swing.JComponent.processMouseEvent(Unknown Source)

            at java.awt.Component.processEvent(Unknown Source)

            at java.awt.Container.processEvent(Unknown Source)

            at java.awt.Component.dispatchEventImpl(Unknown Source)

            at java.awt.Container.dispatchEventImpl(Unknown Source)

            at java.awt.Component.dispatchEvent(Unknown Source)

            at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)

            at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)

            at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)

            at java.awt.Container.dispatchEventImpl(Unknown Source)

            at java.awt.Window.dispatchEventImpl(Unknown Source)

            at java.awt.Component.dispatchEvent(Unknown Source)

            at java.awt.EventQueue.dispatchEvent(Unknown Source)

            at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)

            at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)

            at java.awt.EventDispatchThread.pumpEvents(Unknown Source)

            at java.awt.EventDispatchThread.pumpEvents(Unknown Source)

            at java.awt.EventDispatchThread.run(Unknown Source)

 

If I remove the “Italy” individual, there are no errors raised, and the source code shown by protégé is

 

<?xml version="1.0"?>

<rdf:RDF

    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"

    xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"

    xmlns:owl="http://www.w3.org/2002/07/owl#"

    xmlns:p1="file:/C:/protege.owl#"

    xmlns="http://qqSitio/protege#"

    xmlns:daml="http://www.daml.org/2001/03/daml+oil#"

  xml:base="http://qqSitio/protege">

  <owl:Ontology rdf:about=""/>

  <owl:Class rdf:about="file:/C:/protege.owl#Country"/>

</rdf:RDF>

 

Any help?

 

 

Thank you.

 

_________________________________

 

   Oscar Pereira

_________________________________

        Universidade de Aveiro - IEETA

        3810-193 Aveiro, Portugal

                 Tlf. 234 370 500, ext: 24129   

 

Reply | Threaded
Open this post in threaded view
|

Re: Import OWL (error)

Hai Wang
Hi Oscar,
I just tried it. It works fine. Could you update to the latest Protege?

Regards
Hai

On 30 Jan 2006, at 11:59, Oscar Pereira wrote:

> Hi,
>
>
>
>
>
> When I try to import the following ontology from a file (c:
> \protege.owl”)
>
>
>
> <rdf:RDF
>
>     xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
>
>     xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
>
>     xmlns:owl="http://www.w3.org/2002/07/owl#"
>
>     xmlns:base="http://qqSitio/protege"
>
>     xmlns="http://qqSitio/protege#"
>
>     xmlns:daml="http://www.daml.org/2001/03/daml+oil#">
>
>   <owl:Class rdf:ID="Country"/>
>
>   <Country rdf:ID="Italy"/>
>
> </rdf:RDF>
>
>
>
> Into an empty ontology, Protege raises the following errors.
>
>
>
>
>
> java.lang.ClassCastException:  
> edu.stanford.smi.protegex.owl.model.impl.DefaultRDFUntypedResource
>
>             at  
> edu.stanford.smi.protegex.owl.model.factory.OWLJavaFactory.createSimpl
> eInstance(OWLJavaFactory.java:233)
>
>             at  
> edu.stanford.smi.protegex.owl.model.factory.OWLJavaFactoryUpdater.crea
> teNewFrame(OWLJavaFactoryUpdater.java:62)
>
>             at  
> edu.stanford.smi.protegex.owl.model.factory.OWLJavaFactoryUpdater.<ini
> t>(OWLJavaFactoryUpdater.java:38)
>
>             at  
> edu.stanford.smi.protegex.owl.model.factory.OWLJavaFactoryUpdater.run(
> OWLJavaFactoryUpdater.java:134)
>
>             at  
> edu.stanford.smi.protegex.owl.jena.triplestore.JenaTripleStoreModel.en
> dTripleStoreChanges(JenaTripleStoreModel.java:71)
>
>             at  
> edu.stanford.smi.protegex.owl.jena.parser.ProtegeOWLParser.run
> (ProtegeOWLParser.java:498)
>
>             at  
> edu.stanford.smi.protegex.owl.jena.parser.ProtegeOWLParser.run
> (ProtegeOWLParser.java:442)
>
>             at  
> edu.stanford.smi.protegex.owl.jena.parser.ProtegeOWLParser.run
> (ProtegeOWLParser.java:437)
>
>             at  
> edu.stanford.smi.protegex.owl.jena.parser.ProtegeOWLParser.run
> (ProtegeOWLParser.java:629)
>
>             at edu.stanford.smi.protegex.owl.jena.JenaOWLModel.load
> (JenaOWLModel.java:196)
>
>             at edu.stanford.smi.protegex.owl.jena.JenaOWLModel.load
> (JenaOWLModel.java:220)
>
>             at  
> edu.stanford.smi.protegex.owl.jena.JenaKnowledgeBaseFactory.loadKnowle
> dgeBase(JenaKnowledgeBaseFactory.java:143)
>
>             at edu.stanford.smi.protege.model.Project.loadDomainKB
> (Unknown Source)
>
>             at  
> edu.stanford.smi.protege.model.Project.createDomainKnowledgeBase
> (Unknown Source)
>
>             at edu.stanford.smi.protege.model.Project.<init>
> (Unknown Source)
>
>             at edu.stanford.smi.protege.model.Project.<init>
> (Unknown Source)
>
>             at  
> edu.stanford.smi.protege.model.Project.loadProjectFromURI(Unknown  
> Source)
>
>             at  
> edu.stanford.smi.protege.ui.ProjectManager.loadProjectFromURI
> (Unknown Source)
>
>             at  
> edu.stanford.smi.protege.ui.ProjectManager.loadProject(Unknown Source)
>
>             at edu.stanford.smi.protege.ui.ProjectMenuBar
> $1.actionPerformed(Unknown Source)
>
>             at javax.swing.AbstractButton.fireActionPerformed
> (Unknown Source)
>
>             at javax.swing.AbstractButton$Handler.actionPerformed
> (Unknown Source)
>
>             at javax.swing.DefaultButtonModel.fireActionPerformed
> (Unknown Source)
>
>             at javax.swing.DefaultButtonModel.setPressed(Unknown  
> Source)
>
>             at javax.swing.AbstractButton.doClick(Unknown Source)
>
>             at javax.swing.plaf.basic.BasicMenuItemUI.doClick
> (Unknown Source)
>
>             at javax.swing.plaf.basic.BasicMenuItemUI
> $Handler.mouseReleased(Unknown Source)
>
>             at java.awt.Component.processMouseEvent(Unknown Source)
>
>             at javax.swing.JComponent.processMouseEvent(Unknown  
> Source)
>
>             at java.awt.Component.processEvent(Unknown Source)
>
>             at java.awt.Container.processEvent(Unknown Source)
>
>             at java.awt.Component.dispatchEventImpl(Unknown Source)
>
>             at java.awt.Container.dispatchEventImpl(Unknown Source)
>
>             at java.awt.Component.dispatchEvent(Unknown Source)
>
>             at java.awt.LightweightDispatcher.retargetMouseEvent
> (Unknown Source)
>
>             at java.awt.LightweightDispatcher.processMouseEvent
> (Unknown Source)
>
>             at java.awt.LightweightDispatcher.dispatchEvent(Unknown  
> Source)
>
>             at java.awt.Container.dispatchEventImpl(Unknown Source)
>
>             at java.awt.Window.dispatchEventImpl(Unknown Source)
>
>             at java.awt.Component.dispatchEvent(Unknown Source)
>
>             at java.awt.EventQueue.dispatchEvent(Unknown Source)
>
>             at java.awt.EventDispatchThread.pumpOneEventForHierarchy
> (Unknown Source)
>
>             at java.awt.EventDispatchThread.pumpEventsForHierarchy
> (Unknown Source)
>
>             at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
>
>             at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
>
>             at java.awt.EventDispatchThread.run(Unknown Source)
>
>
>
> If I remove the “Italy” individual, there are no errors raised, and  
> the source code shown by protégé is
>
>
>
> <?xml version="1.0"?>
>
> <rdf:RDF
>
>     xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
>
>     xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
>
>     xmlns:owl="http://www.w3.org/2002/07/owl#"
>
>     xmlns:p1="file:/C:/protege.owl#"
>
>     xmlns="http://qqSitio/protege#"
>
>     xmlns:daml="http://www.daml.org/2001/03/daml+oil#"
>
>   xml:base="http://qqSitio/protege">
>
>   <owl:Ontology rdf:about=""/>
>
>   <owl:Class rdf:about="file:/C:/protege.owl#Country"/>
>
> </rdf:RDF>
>
>
>
> Any help?
>
>
>
>
>
> Thank you.
>
>
>
> _________________________________
>
>
>
>    Oscar Pereira
>
> _________________________________
>
>         Universidade de Aveiro - IEETA
>
>         3810-193 Aveiro, Portugal
>
>                  Tlf. 234 370 500, ext: 24129
>
>
>
>

Regards
Hai


Research Associate
Department of Computer Science
Kilburn Building
University of Manchester
Oxford Road
Manchester M13 9PL
UK
Homepage: http://www.cs.man.ac.uk/~hwang



-------------------------------------------------------------------------
To unsubscribe go to http://protege.stanford.edu/community/subscribe.html

Reply | Threaded
Open this post in threaded view
|

BUG_in_type_float

Ronnie Valkky
Hi Natalya & all,

Backgroud info about type float:
1. float corresponds to the IEEE single-precision 32-bit floating point type
[ieee754].
The basic value space of float consists of the values m × 2^e,
where m is an integer whose absolute value is less than 2^24, and
 e is an integer between -149 and 104, inclusive

2. http://java.sun.com/j2se/1.5.0/docs/api/java/lang/Float.html :
max float value:A constant holding the largest positive finite value of type
float, (2-2-23)·2127
minimum float value: a constant holding the smallest positive nonzero value
of type float, 2-149

3. Test / own test with Proge OWL version 3.2 build 241
~ with several values including minimun ja maximum
~ result: PROTEGE OWL FAILED TO MEET MINUMUM AND MAXIMUM for float
and even with easier values!

Conclusion:
Looks a BUG and a SERIOUS ONE !!!
Perhaps extreme tests with minimum and maximu should be done
systematically!?

Continuation:
This bug fixed + maths + extreme min/max tests ?
Note: this is the third feedback including yours with no answers!

Cheers,
Ronnie

----- Original Message -----
From: "Natalya Keberle" <[hidden email]>
To: <[hidden email]>
Sent: Friday, January 27, 2006 9:43 AM
Subject: [protege-owl] Difference in datatypes for Protege 3.1.1 216 and
3.2.beta 236
> Hi All,
>
> the problem is as follows:
> There is an owl/rdf project, created in Protege 3.1.1 build 216.
> When I open it in its "native" version of Protege, I can see a big list of
allowed datatypes, corresponding to xsd namespace, and, particularly,
xsd:double, xsd:float.
>
> When I re-open the project in Protege 3.2. beta 236, and try to add new
datatype properties,  the list of allowed datatypes contains only basic
datatypes (boolean, int, float, string, date, dateTime, time, Any),
datatypes, which were used in my project(double),and no more.
> When I create a new project in Protege 3.2. beta 236, the list of allowed
datatypes is reduced to basic datatypes, and I cannot define the range of a
property as double.
>
> This particularly leads to the situation, when all instances, having
datatype properties of xsd:double, are in "red box", when open the Instances
Tab.
>
> Moreover, the precision of float is smaller then declared in XMLSchema, so
I can declare 2E38, but 2E39 leads to "infinity" value, but the declared
bounds for E in float are [-149,+104].
>
> Is this a bug?
> Should I convert all properties with "double" range into "float"?
>
> Cheers,
> Natalya



-------------------------------------------------------------------------
To unsubscribe go to http://protege.stanford.edu/community/subscribe.html

Reply | Threaded
Open this post in threaded view
|

Re: BUG_in_type_float

Matthew Horridge
Ronnie,

> Backgroud info about type float:
> 1. float corresponds to the IEEE single-precision 32-bit floating  
> point type
> [ieee754].
> The basic value space of float consists of the values m × 2^e,
> where m is an integer whose absolute value is less than 2^24, and
>  e is an integer between -149 and 104, inclusive
> 2. http://java.sun.com/j2se/1.5.0/docs/api/java/lang/Float.html :
> max float value:A constant holding the largest positive finite  
> value of type
> float, (2-2-23)·2127
> minimum float value: a constant holding the smallest positive  
> nonzero value
> of type float, 2-149
>
> 3. Test / own test with Proge OWL version 3.2 build 241
> ~ with several values including minimun ja maximum
> ~ result: PROTEGE OWL FAILED TO MEET MINUMUM AND MAXIMUM for float
> and even with easier values!

Wrong.

> Conclusion:
> Looks a BUG and a SERIOUS ONE !!!

This is the second incorrect, misleading and slanderous post of yours  
in this thread. You ought to read the specs more carefully before  
posting such inflammatory e-mails

I've posted a reply to Natalya's original message which explains floats.

> Perhaps extreme tests with minimum and maximu should be done
> systematically!?
>
> Continuation:
> This bug fixed + maths + extreme min/max tests ?
> Note: this is the third feedback including yours with no answers!

Sorry for not replying to your posts the instant they appear on this  
list - I will endeavour to do better in the future, thereby perhaps  
minimising the number of hysterical responses to what were originally  
reasonable questions.

Matthew






> Cheers,
> Ronnie
>
> ----- Original Message -----
> From: "Natalya Keberle" <[hidden email]>
> To: <[hidden email]>
> Sent: Friday, January 27, 2006 9:43 AM
> Subject: [protege-owl] Difference in datatypes for Protege 3.1.1  
> 216 and
> 3.2.beta 236
>> Hi All,
>>
>> the problem is as follows:
>> There is an owl/rdf project, created in Protege 3.1.1 build 216.
>> When I open it in its "native" version of Protege, I can see a big  
>> list of
> allowed datatypes, corresponding to xsd namespace, and, particularly,
> xsd:double, xsd:float.
>>
>> When I re-open the project in Protege 3.2. beta 236, and try to  
>> add new
> datatype properties,  the list of allowed datatypes contains only  
> basic
> datatypes (boolean, int, float, string, date, dateTime, time, Any),
> datatypes, which were used in my project(double),and no more.
>> When I create a new project in Protege 3.2. beta 236, the list of  
>> allowed
> datatypes is reduced to basic datatypes, and I cannot define the  
> range of a
> property as double.
>>
>> This particularly leads to the situation, when all instances, having
> datatype properties of xsd:double, are in "red box", when open the  
> Instances
> Tab.
>>
>> Moreover, the precision of float is smaller then declared in  
>> XMLSchema, so
> I can declare 2E38, but 2E39 leads to "infinity" value, but the  
> declared
> bounds for E in float are [-149,+104].
>>
>> Is this a bug?
>> Should I convert all properties with "double" range into "float"?
>>
>> Cheers,
>> Natalya
>
>
>
> ----------------------------------------------------------------------
> ---
> To unsubscribe go to http://protege.stanford.edu/community/ 
> subscribe.html
>

-------------------------------------------------------------------------
To unsubscribe go to http://protege.stanford.edu/community/subscribe.html

Reply | Threaded
Open this post in threaded view
|

simple_question

Ronnie Valkky
Hi,

How does the type float specification in ProtegeOWL relate to IEEE754
float specification and to Java 1.5 Float specifications ?

Ronnie

-------------------------------------------------------------------------
To unsubscribe go to http://protege.stanford.edu/community/subscribe.html

Reply | Threaded
Open this post in threaded view
|

Re: simple_question

Rinke Hoekstra-3
Hi Ronnie,

As Matthew pointed out, it complies with the OWL/RDF(S)/XML
specification. You can find those at the website of the W3C:
http://www.w3.org

-Rinke


Ronnie Valkky wrote:

> Hi,
>
> How does the type float specification in ProtegeOWL relate to IEEE754
> float specification and to Java 1.5 Float specifications ?
>
> Ronnie
>
> -------------------------------------------------------------------------
> To unsubscribe go to http://protege.stanford.edu/community/subscribe.html
>
>

--
--------------------------------------
Rinke Hoekstra         [hidden email]
T: +31-20-5253499    F: +31-20-5253495
Leibniz Center for Law,    Law Faculty
University of Amsterdam,   PO Box 1030
1000 BA  Amsterdam,    The Netherlands
--------------------------------------

-------------------------------------------------------------------------
To unsubscribe go to http://protege.stanford.edu/community/subscribe.html

Reply | Threaded
Open this post in threaded view
|

Re: simple_question

Ronnie Valkky
Hi Rinke,

Thanks for your answer.

When one enters allowed range values In Protege OWL using property editor
and keys in a too big number such as 6.80564734E38 (=2**129)  Protege
interpreters it as Infinity.

Is it so that  the keyed value mathematically is a finite value = just is
too big to current system to calculate
=  an undefined value from computer's point of view ?

If an allowed range value is Infinite,  what does it mean in Protege OWL?
- any float value ?
- any float value, which Java can handle without overflow ?
- that there are no range limits for values unless they are within the
limits Java can handle ?

-Ronnie

----- Original Message -----
From: "Rinke Hoekstra" <[hidden email]>
To: <[hidden email]>
Sent: Tuesday, January 31, 2006 12:15 PM
Subject: [protege-owl] Re: simple_question


> Hi Ronnie,
>
> As Matthew pointed out, it complies with the OWL/RDF(S)/XML
> specification. You can find those at the website of the W3C:
> http://www.w3.org
>
> -Rinke
>
>
> Ronnie Valkky wrote:
> > Hi,
> >
> > How does the type float specification in ProtegeOWL relate to IEEE754
> > float specification and to Java 1.5 Float specifications ?
> >
> > Ronnie
> >
>
> -------------------------------------------------------------------------
> > To unsubscribe go to
http://protege.stanford.edu/community/subscribe.html

> >
> >
>
> --
> --------------------------------------
> Rinke Hoekstra         [hidden email]
> T: +31-20-5253499    F: +31-20-5253495
> Leibniz Center for Law,    Law Faculty
> University of Amsterdam,   PO Box 1030
> 1000 BA  Amsterdam,    The Netherlands
> --------------------------------------
>
> -------------------------------------------------------------------------
> To unsubscribe go to http://protege.stanford.edu/community/subscribe.html
>
>


-------------------------------------------------------------------------
To unsubscribe go to http://protege.stanford.edu/community/subscribe.html

Reply | Threaded
Open this post in threaded view
|

Re: simple_question

Rinke Hoekstra-3
Hi Ronnie,

I can only imagine that its seen as an undefined value from the
computer's point of view. OWL/RDF does not syntactically restrict the
range of integers/floats as these values are stored as literals (i.e.
strings). However, Protege tests for this range and whenever an
exception is caught wrt the range the value is substituted with the
literal "Infinity". This is part of the specification of xsd:float :

--quote--
"The value space of xsd:float is "float," 32-bit floating-point numbers
as defined by the IEEE. The lexical space uses a decimal format with
optional scientific notation. The match between lexical (powers of 10)
and value (powers of 2) spaces is approximate and maps to the closest value.

This datatype differentiates positive (0) and negative (-0) zeros, and
includes the special values -INF (negative infinity), INF (positive
infinity), and NaN (Not a Number).

Note that the lexical spaces of xsd:float and xsd:double are exactly the
same; the only difference is the precision used to convert the values in
the value space."
--quote--

Hope that helps?

-Rinke

Ronnie Valkky wrote:

> Hi Rinke,
>
> Thanks for your answer.
>
> When one enters allowed range values In Protege OWL using property editor
> and keys in a too big number such as 6.80564734E38 (=2**129)  Protege
> interpreters it as Infinity.
>
> Is it so that  the keyed value mathematically is a finite value = just is
> too big to current system to calculate
> =  an undefined value from computer's point of view ?
>
> If an allowed range value is Infinite,  what does it mean in Protege OWL?
> - any float value ?
> - any float value, which Java can handle without overflow ?
> - that there are no range limits for values unless they are within the
> limits Java can handle ?
>
> -Ronnie
>
> ----- Original Message -----
> From: "Rinke Hoekstra" <[hidden email]>
> To: <[hidden email]>
> Sent: Tuesday, January 31, 2006 12:15 PM
> Subject: [protege-owl] Re: simple_question
>
>
>> Hi Ronnie,
>>
>> As Matthew pointed out, it complies with the OWL/RDF(S)/XML
>> specification. You can find those at the website of the W3C:
>> http://www.w3.org
>>
>> -Rinke
>>
>>
>> Ronnie Valkky wrote:
>>> Hi,
>>>
>>> How does the type float specification in ProtegeOWL relate to IEEE754
>>> float specification and to Java 1.5 Float specifications ?
>>>
>>> Ronnie
>>>
>> -------------------------------------------------------------------------
>>> To unsubscribe go to
> http://protege.stanford.edu/community/subscribe.html
>>>
>> --
>> --------------------------------------
>> Rinke Hoekstra         [hidden email]
>> T: +31-20-5253499    F: +31-20-5253495
>> Leibniz Center for Law,    Law Faculty
>> University of Amsterdam,   PO Box 1030
>> 1000 BA  Amsterdam,    The Netherlands
>> --------------------------------------
>>
>> -------------------------------------------------------------------------
>> To unsubscribe go to http://protege.stanford.edu/community/subscribe.html
>>
>>
>
>
> -------------------------------------------------------------------------
> To unsubscribe go to http://protege.stanford.edu/community/subscribe.html
>
>


--
--------------------------------------
Rinke Hoekstra         [hidden email]
T: +31-20-5253499    F: +31-20-5253495
Leibniz Center for Law,    Law Faculty
University of Amsterdam,   PO Box 1030
1000 BA  Amsterdam,    The Netherlands
--------------------------------------

-------------------------------------------------------------------------
To unsubscribe go to http://protege.stanford.edu/community/subscribe.html