[Pellet-users] Error in datavalue property restriction not signaled

[Evren Sirin]

Can you send us the exact ontology that is causing the problem? I was 
not able to reproduce this problem on my side.

Thanks,
Evren

On 7/4/08 6:13 AM, Stefanos Koukoulas wrote:
> Hi,
>
> I have defined a hasValue restriction on a functional datatype (xsd:int) 
> property in Protege that this property can only take values 0 and 1. 
> Then I created an individual of this class and gave some values for 
> testing. I noticed that if the values are from -128 to 127 (and of 
> course different than 0 or 1) Pellet signals the error, but beyond this 
> range the error is not signaled! At the beginning I thought that the 
> range of xsd:int is from -128 to 127, but then I read that it has 32 
> bits so its range is much broader. Can you tell me what I am doing wrong 
> and the reasoner does not signal the error?
> I have tested with direct Pellet reasoning inside Protege and with 
> Pellet as a stand alone reasoner and the results are always the same.
> _______________________________________________
> Pellet-users mailing list
> Pellet-users at lists.owldl.com
> http://lists.owldl.com/mailman/listinfo/pellet-users
> _______________________________________________
>
> Sponsored by Clark & Parsia, LLC http://clarkparsia.com/
>