[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] RE: New to XSL - invalid token error
No, XQuery still differs from true XML in some subtle ways. For example, it's valid in XQuery to write <book authorCount=" { count($authors[name="Kay"]) } "/> (note the nested double quotes). Michael Kay Software AG home: Michael.H.Kay@xxxxxxxxxxxx work: Michael.Kay@xxxxxxxxxxxxxx > -----Original Message----- > From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx > [mailto:owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of > Francis Norton > Sent: 31 January 2003 23:54 > To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx > Subject: Re: New to XSL - invalid token error > > > Well I'll be blowed. > > Michael Kay wrote: > > >Recent drafts of XQuery are closer to real XML syntax. You now write > > > > return <book authorCount="{ count($authors) }"/> > > > I'm way out of touch, it's all there on the site. I'm still > looking at > it. Does it mean that an XQuery statement is essentially a > well-formed > mixed-content XML fragment? I bet I'm not the only one who's noticed > that the sometimes puzzling distinction in XSLT between the > root *node* > and the root *element* means that XSLT would need no formal > changes to > accept (multiple root-element) XML Fragments as input instead > of (single > root-element) XML Documents, if only the underlying parsers > would parse > them. > > Time for XML 1.1 to treat XML Documents as simply a special > case of XML > Fragments, and both to be considered well-formed. One day > maybe. Equal > rights for fragment types? > > Francis. > > > > XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list > XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|