- From: Michael Kay <mhk@mhk.me.uk>
- Date: Thu, 27 Jan 2005 12:44:22 -0000
- To: "'Kenneth Stephen'" <marvin.the.cynical.robot@gmail.com>, <public-qt-comments@w3.org>
Thanks for pointing out this inconsistency. In fact this text is going to change: the XSL WG has decided that a basic XSLT processor should recognize all the built-in types defined in XML Schema. Michael Kay > -----Original Message----- > From: public-qt-comments-request@w3.org > [mailto:public-qt-comments-request@w3.org] On Behalf Of > Kenneth Stephen > Sent: 24 January 2005 01:51 > To: public-qt-comments@w3.org > Subject: [XSLT]Built-in types > > > Hi, > > In section 3.13 of the XSLT 2.0 spec I see : > > <quote> > All the primitive atomic types defined in [XML Schema] (Part 2), with > the exception of xs:NOTATION. That is: xs:string, xs:boolean, > xs:integer, xs:decimal, xs:double, xs:float, xs:date, xs:time, > xs:dateTime, xs:duration, xs:QName, xs:anyURI, xs:gDay, xs:gMonthDay, > xs:gMonth, xs:gYearMonth, xs:gYear, xs:base64Binary, xs:hexBinary, and > xs:QName. > > The derived atomic type xs:integer defined in [XML Schema] > (Part 2).</quote> > > Surely xs:integer cannot be both a primitive atomic type as well > as a derived atomic type? An examination of the referenced XML Schema > spec shows that it is a type derived from xs:decimal. > > Regards, > Kenneth > > >
Received on Thursday, 27 January 2005 12:45:04 UTC