RE: Xquery Functions and Operators: Section 14.1.4 fn:number

My apologies - I found the values for the variables in the example, I hadn't backtraced far enough. 
I would suggest a  link be added, so that backwards scanning isn't necessary. 
regards
Margaret Gruen
 
... Margaret A. Gruen-Kerr
... Quality Assurance Engineer
... Altova GmbH - markup your mind!

-----Original Message-----
From: Margaret Grün-Kerr 
Sent: 30 December 2003 14:35
To: public-qt-comments@w3.org
Subject: Xquery Functions and Operators: Section 14.1.4 fn:number



In the examples section for fn:number the values for $item1 and $item2 are missing. 


	14.1.4.1 Examples 


*	fn:number($item1/quantity) returns 5. 

*	fn:number($item2) returns NaN. 


Happy New Year - Margaret Gruen- 
... Margaret A. Gruen-Kerr
... Quality Assurance Engineer
... Altova GmbH - markup your mind!

===================================================================
xmlspy® 2004 - mapforce(tm) 2004 - authentic(tm) 2004 - stylevision(tm) 2004
Award-winning tools for developers - web designers - business-users
NEW: XML-to-XML and DB-to-XML Mapping, XML Differencing, XPath 2.0,
Microsoft Visual Studio® .NET Integration, Borland C# Builder, Mono
Auto-Calculation,  Business Logic Validation, Rich Input Formatting
Visit   <file://www.altova.com> www.altova.com  to download your free evaluation copy today!
===================================================================

The information transmitted in this message and/or as an attachment
to it  is intended  only for the  person or  entity to  which it is
addressed and may contain confidential  and/or privileged material.
Any  review,  retransmission,  dissemination  or  other use of,  or
taking of any action in reliance upon,  this information by persons
or entities other than the intended recipient is prohibited. If you
received this in error,  please contact  the sender  and delete the
material from any computer.  Altova GmbH  and  Altova, Inc.  do not
accept legal responsibility  for the contents of this message.  Any
views or opinions  presented are solely  those of the author and do
not  necessarily  represent those of  Altova GmbH and  Altova, Inc.
unless otherwise specifically stated. Thank you!