RE: [XSLT2.0] IBM-XSLT-117: How is value of select in xsl:analyze-string converted to string?

Thank you for pointing out this omission.

I propose to add the rule:

If the result of evaluating the select expression is not a string, it is
converted to a string by applying the *function conversion rules* [link
to definition in section 5.3].

(An alternative would be to appeal to the fn:string() function; but it
seems more natural to me to use the function conversion rules, which
mean that you will get stronger type checking)

Please confirm whether this resolution is acceptable.

Regards,

Michael Kay
(as XSL WG editor)

> -----Original Message-----
> From: public-qt-comments-request@w3.org 
> [mailto:public-qt-comments-request@w3.org] On Behalf Of Henry Zongaro
> Sent: 19 February 2004 16:53
> To: public-qt-comments@w3.org
> Subject: [XSLT2.0] IBM-XSLT-117: How is value of select in 
> xsl:analyze-string converted to string?
> 
> 
> 
> [With apologies that these comments are coming in after the 
> end of the 
> Last Call comment period.]
> 
> Section 15.1
> 
> The first paragraph beneath the syntax for the 
> xsl:non-matching-string 
> element states, in part, "The xsl:analyze-string instruction takes as 
> input a string (the result of evaluating the expression in the select 
> attribute)...."  This needs to specify how the value of the 
> expression is 
> converted to a string.
> 
> Thanks,
> 
> Henry
> [Speaking on behalf of reviewers from IBM.]
> ------------------------------------------------------------------
> Henry Zongaro      Xalan development
> IBM SWS Toronto Lab   T/L 969-6044;  Phone +1 905 413-6044
> mailto:zongaro@ca.ibm.com
>

Received on Friday, 20 February 2004 12:14:16 UTC