http://www.w3.org/Bugs/Public/show_bug.cgi?id=5316 ------- Comment #2 from mike@saxonica.com 2007-12-17 18:51 ------- My preferred solution would be to remove the option of supplying the new name as a string, and insist that it be supplied as a QName. We have a number of ways of getting a QName, including the xs:QName, fn:QName(), and fn:node-name() functions, and I think that allowing a simple string as a short-cut is not worth the ambiguities it creates. An alternative would be to interpret a string differently depending on whether the node being renamed is an element or an attribute.Received on Monday, 17 December 2007 18:51:11 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:14:22 GMT