4171 2007-01-09 18:32:20 +0000 [UPD] Merging adjacent text nodes and node identity 2007-02-07 09:50:24 +0000 1 1 1 Unclassified XPath / XQuery / XSLT Update Facility Working drafts PC Linux CLOSED FIXED P2 normal --- 1 john.snelson andrew.eisenberg dengovatov public-qt-comments oldest_to_newest 13388 0 john.snelson 2007-01-09 18:32:20 +0000 What happens to node identity when adjacent text nodes are merged? What about variable references that point to one of the original text nodes - do they need to be identified and updated? 13427 1 andrew.eisenberg 2007-01-10 22:33:07 +0000 We've tackled this once is bug 2983. In section 3.2.2 upd:applyUpdates, Semantics, bullet 3, we now say, "If, as a net result of the above steps, the children property of some node contains adjacent text nodes, these adjacent text nodes are merged into a single text node. The string-value of the resulting text node is the concatenated string-values of the adjacent text nodes, with no intervening space added. The nodeid of the resulting text node is implementation-dependent." In my opinion, this is a somewhat loose statement. One implementation might create a new text node, with new identity, as a result of the merge, and the disconnect the original text nodes from their parent node. Another implementation might add the content of the second text node to the first text node, and then disconnect the second text node from its parent node. 13915 2 dengovatov 2007-02-07 01:19:35 +0000 We have reviewed this issue: comment #1 answers the question stated in the bug description. No further changes are necessary.