However, the latest specs have aligned casting with XML
Schema validation, which means that ('non-roman' cast as
xs:float) should fail, and "castable as" should therefore
return false.
Thanks Mike. That will be much appreciated.
I'll update the software to match. Meanwhile,
I suspect that what you really want is "castable as
xs:decimal", which should work OK in the current Saxon.
Not being a types type, I hadn't sought out the difference,
if its possible in the specs.
Alternatively, you could use a regex to test whether the
value is numeric, which might be more efficient anyway
("castable as" in its current implementation involves
throwing and catching an exception, which is very expensive
in Java).
and falls over badly when all the other cases are tested for :-)
Thanks again, I'll look at that option,
hopefully I can get terms from non match
targets from the matches!
regards DaveP
-
DISCLAIMER:
NOTICE: The information contained in this email and any attachments is
confidential and may be privileged. If you are not the intended
recipient you should not use, disclose, distribute or copy any of the
content of it or of any attachment; you are requested to notify the
sender immediately of your receipt of the email and then to delete it
and any attachments from your system.
RNIB endeavours to ensure that emails and any attachments generated by
its staff are free from viruses or other contaminants. However, it
cannot accept any responsibility for any such which are transmitted.
We therefore recommend you scan all attachments.
Please note that the statements and views expressed in this email and
any attachments are those of the author and do not necessarily represent
those of RNIB.
RNIB Registered Charity Number: 226227
Website: http://www.rnib.org.uk
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list