Andrew said:
How does your suggestion solve the kind of issues arising with
<mySillyDate>Fred</mySillyDate>
and
<myNotQuiteSoSillyDate>25th December 2010</myNotQuiteSoSillyDate>
GIGO? What's new.
You are proposing that XSLT stylesheet authors continue to
pfaff around
with multiple string-related functions to manipulate dates
.... ? Oops I
mean strings that happen to look like dates. :)
If you really want that functionality, I'd suggest moving
to xquery. For me its not required.
So, correct me if I am misunderstanding you here, you are
saying you will
forego the date / time / duration functions in XPath 2.0 /
XSLT 2.0 if it
means you having to learn even a very little about W3C XML Schema?
If XSD ever gets off the ground maybe.
Today I simply don't need it and don't want XSLT with the XSD albatross
round its neck.
There are some really good additions in xslt 2. Many of them
requested on this list.
There's a whole host of other stuff that I've never seen mentioned on
this list.
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