Search Mailing List Archives


Limit search to: Subject & Body Subject Author
Sort by: Reverse Sort
Limit to: All This Week Last Week This Month Last Month
Select Date Range     through    

[protege-owl] FAQ: How do I create numeric value restrictions such as

Achim Kramer ai08080 at informatik.dhbw-stuttgart.de
Tue Nov 23 02:18:02 PST 2010



This error does still occur with Protege 4.1 Build 213. 

I have the same reasoner error with a similar ontology and also integer data
properties. 

Alternatively I tried Protege 4.0.2 Build 115, which works fine with this
ontology. Seems to be Protege 4.1. Bug ?!


Regards ~Ak









Timothy Redmond wrote:
> 
> 
> I believe that if you update to the latest Protege 4 (it came out pretty 
> recently) your problem will go away.  I am not sure how long this bug 
> has been there but I am wondering if it has been there for a while and 
> the reasoners essentially discovered it.
> 
> Let me know if this doesn't work.
> 
> -Timothy
> 
> 
> 
> 
> On 10/28/2010 11:23 AM, Tri Datta wrote:
>>
>> Hi All,
>>
>> I'm running through the standard PIZZA ontology, and I'm a little 
>> confused by the discrepancy between what it's telling me to do (create 
>> a numerical comparison) and one of the FAQs, stating "How do I create 
>> numeric value restrictions such as "wheels with diameter over 10"?" -- 
>> which appears to suggest that we simply can't do that...
>>
>> In particular, I'm trying to define a HighCaloriePizza with 
>> "hasCalorificContentValue some integer[>= 400]", and unfortunately, 
>> I'm getting an error as follows upon classifying:
>>
>> _______________
>>
>> IllegalArgumentException: Attempt to constrain 
>> datatype(com.clarkparsia.pellet.datatype.types.real.XSDInteger at 61882bfd) 
>> using constraining facet('MIN_INCLUSIVE') with an unsupported value 
>> ('literal(400,(),http://www.w3.org/1999/02/22-rdf-syntax-ns#PlainLiteral)')
>>
>> _______________
>>
>> This seems to be suggesting that it's interpreting the 400 value as a 
>> string literal and is therefore unwilling to accept it for comparison. 
>> I also tried:
>>
>> hasCalorificContentValue some integer[>= "400"^^integer]
>>
>> hasCalorificContentValue some integer[>= "400"^^xsd::integer]
>>
>> to try to somehow artificially cast the type, but no luck..
>>
>> This seems to be asking me to do precisely what the FAQ is telling me 
>> not to do, so I was wondering if this was a problem with a feature in 
>> the last beta release,..except it looks like the tutorial that I'm 
>> using is a good bit older. I'm seeing a couple bugs that seem somewhat 
>> related, but as I'm just ripping off the tutorial at this point, I'm 
>> suspecting this is less as a "bug" than "me missing something quite 
>> obvious".
>>
>> Any help would be hugely appreciated.
>>
>> Thanks so much.
>>
>> Tri
>>
>>
>> _______________________________________________
>> protege-owl mailing list
>> protege-owl at lists.stanford.edu
>> https://mailman.stanford.edu/mailman/listinfo/protege-owl
>>
>> Instructions for unsubscribing:
>> http://protege.stanford.edu/doc/faq.html#01a.03
> 
> 
> _______________________________________________
> protege-owl mailing list
> protege-owl at lists.stanford.edu
> https://mailman.stanford.edu/mailman/listinfo/protege-owl
> 
> Instructions for unsubscribing:
> http://protege.stanford.edu/doc/faq.html#01a.03
> 
> 

-- 
View this message in context: http://protege-ontology-editor-knowledge-acquisition-system.136.n4.nabble.com/FAQ-How-do-I-create-numeric-value-restrictions-such-as-wheels-with-diameter-over-10-tp3017858p3055127.html
Sent from the Protege OWL mailing list archive at Nabble.com.



More information about the protege-owl mailing list