[XSL-LIST Mailing List Archive Home]
[By Thread]
[By Date]
Re: [xsl] are all strings in a sequence valid potential QNames
Subject: Re: [xsl] are all strings in a sequence valid potential QNames From: Andrew Welch <andrew.j.welch@xxxxxxxxx> Date: Thu, 4 Feb 2010 10:24:28 +0000 |
On 4 February 2010 09:53, G. Ken Holman <gkholman@xxxxxxxxxxxxxxxxxxxx> wrote: > At 2010-02-04 09:45 +0000, Andrew Welch wrote: >> >> Doesn't that restriction then make "castable as xs:QName" pretty >> useless? I can't see when you would need it... > > I think many specifications end up with useless vestiges resulting from the > product of two concepts where most of the combinations make sense but the > odd one here or there end up not being very useful. On the left operand you > have all of the different operands of literals and values, and on the right > operand you have all of the different types, and that produces a myriad of > combinations that need to be considered and implemented. Without the restriction it's definitely useful, and intuitive :) ...but with the odd requirement that it will return false unless it's given a hard-coded string, then it is a really subtle and annoying gotcha... I'm sure one that's got me in the past. -- Andrew Welch http://andrewjwelch.com Kernow: http://kernowforsaxon.sf.net/
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] are all strings in a sequ, G. Ken Holman | Thread | Re: [xsl] are all strings in a sequ, G. Ken Holman |
Re: [xsl] are all strings in a sequ, G. Ken Holman | Date | Re: [xsl] are all strings in a sequ, G. Ken Holman |
Month |