Cart
[Home] [By Thread] [By Date] [Recent Entries]
At 2010-02-04 16:46 +0000, Andrew Welch wrote:
> As has been told, "castable as" is not correct for this use case. As > Mike suggests, I'll also go for a regex solution. If an element name were only the prefix and local name, then sure ... but one isn't creating an element name, one is creating an element expanded name using an element qualified name. However, it's not possible because of the (imho) unnecessary restriction in the spec, so you are forced to fall back to a regex based solution. Note that I included an NCName literal string in my illustration and it passed ... or are you referring to a string with an NCName value? A string with an NCName value would still be based on the default namespace of the unspecified node for context. In my illustration the default namespace was effectively null since there was no default namespace declaration. Hopefully this could be looked at for 2.1...? What would be the details of your proposal for a change? Would simply using the context node (and an error if the context item isn't a node) be enough? . . . . . . . . . . . Ken
|
