Hi Michael & all, Here are few new thoughts I've about these issues, and writing them to list here for records.
The XSD type xs:dateTime has the parent type as xs:anyAtomicType. So if an XDM node reference already has a type annotation as xs:dateTime, I see no good value to do an explicit cast on such a node reference (except as a user-opted lexical style). A probably interesting analogy wrt explicit casts for type xs:dateTime, can be made with the following example, The type xs:long has the parent type as xs:integer. So if an XDM item reference has a type annotation as xs:long (let's call it $x), then I definitely see value in doing an explicit case like xs:integer($x), since the value space of xs:long is a subset of value space of xs:integer and we could use the expression xs:integer($x) in contexts where an xs:integer value is expected. And I do find, these scenarios to be working fine with PsychoPath XPath2 engine. I do agree, that the inability to do explicit casts on xs:dateTime references is probably a bug, but as I wrote above I see almost no use-case value of making this fix. On Thu, May 24, 2012 at 1:32 PM, Michael Glavassevich <mrgla...@ca.ibm.com> wrote: > Hi Mukul, > > Regardless of the severity I agree with Jorge that it's a pain if you can't > write an XPath expression which works with both (Xerces and Saxon) > implementations. Can this issue with the explicit cast be fixed in > PsychoPath? > > Thanks. > > Michael Glavassevich > XML Technologies and WAS Development > IBM Toronto Lab > E-mail: mrgla...@ca.ibm.com > E-mail: mrgla...@apache.org -- Regards, Mukul Gandhi --------------------------------------------------------------------- To unsubscribe, e-mail: j-users-unsubscr...@xerces.apache.org For additional commands, e-mail: j-users-h...@xerces.apache.org
