-----Original Message-----
From: Mike Haarman
And this is where I get hung up. XSLT v1.0 this is just crap
data that needs
proofreading. In XSLT v2.0, even for a Basic XSLT Processor,
this is a run-time
failure that I can't recover from. Somebody else must see
this a problem or I
am missing something big somewhere in the literature.
No, you're not alone Mike.
According to xml-dev old hands, we are playing at King Canute though.
The message that XSLT users don't want all this typing appears to fall
on deaf ears since its apparently vital to the xquery input to the working
group.
regards DaveP
-
NOTICE: The information contained in this email and any attachments is
confidential and may be legally privileged. If you are not the
intended recipient you are hereby notified that you must not use,
disclose, distribute, copy, print or rely on this email's content. If
you are not the intended recipient, please notify the sender
immediately and then delete the email and any attachments from your
system.
RNIB has made strenuous efforts to ensure that emails and any
attachments generated by its staff are free from viruses. However, it
cannot accept any responsibility for any viruses 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