On Sat, Apr 19, 2014 at 3:45 PM, Michael Kay <mike(_at_)saxonica(_dot_)com>
wrote:
By way of background to this, it was realised at a fairly late stage that if
all built-in types from XSD 1.1
were to be supported in XPath 3.0, then this included xs:error and t would be
a good idea
to say something about how xs:error should behave; the only alternative was
to specifically exclude it.
Everything the specs say about xs:error is a consequence of the fact that (a)
xs:error is a built-in type,
and (b) it is defined as a union type with no member types. There is no
special treatment of xs:error,
merely explanations of the consequences of its existence and the way it is
defined.
Thank you, Michael,
Is it then a logical conclusion to try to avoid (never use) the
xs:error type in XPath?
Cheers,
Dimitre Novatchev
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--