Hi John, John Snelson <[EMAIL PROTECTED]> writes:
> Note that XPath 2.0 implementations ought to be able to give meaningful > results to a request for any of the resultType enumerations types. Hm, this looks like a pretty hard thing to achieve since the models are so different. I initially thought about mapping XPath 2 result types to XPath 1 ones but that does not seem possible (e.g., you cannot map ITERATOR_RESULT to, say, UNORDERED_NODE_ITERATOR_TYPE because the latter can only contain nodes and the former can result in a sequence with various types). So I simply added the XPath 2 result types into the enum and marked the old ones as XPath 1 and the new ones as XPath 2. I think it is ok for an XPath 2 implementation not to support the XPath 1 result types. (BTW, I just noticed the _TYPE suffix inconsistency so I am going to add it to the XPath 2 enumerators). > isNode() is needed because the DOMTypeInfo does not provide a way to > distinguish between a node of type xs:string and a value of type > xs:string. Ok, I will add isNode(). Thanks, Boris -- Boris Kolpackov, Code Synthesis Tools http://codesynthesis.com/~boris/blog Open source XML data binding for C++: http://codesynthesis.com/products/xsd Mobile/embedded validating XML parsing: http://codesynthesis.com/products/xsde --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
