- From: Howard Katz <howardk@fatdog.com>
- Date: Thu, 11 Aug 2005 11:11:22 -0700
- To: "'Eric Prud'hommeaux'" <eric@w3.org>, "'Seaborne, Andy'" <andy.seaborne@hp.com>
- Cc: <public-rdf-dawg@w3.org>
> On Behalf Of Eric Prud'hommeaux ... > > And for: > > > > 'XXI'^^:romanNumeral != 21 > > > > If that is false (not known to be the same value) and not > an evaluation > > failure, how does it work for incompatible types? is it > the case that > > there is no possible evaluation failure based on > incompatible types? > > I think it's a type error. That is, the != operator takes any of a > defined set of parameters and :romanNumeral is not in the list. I > pestered Liam about this (text below), but I haven't gotten anything > back from him. He and others are all probably distracted by > extreme. I'm re-posting my question to Don Chamberlin. Hi Eric, It's my understanding if you can't go up or down the type hierarchy to convert one operand into the type of the other, it's an error. Did you get an answer from Don? Howard
Received on Thursday, 11 August 2005 18:11:40 UTC