4528 2007-05-04 23:25:02 +0000 [UPD] Sections 2.4.1 insert/3.1.4 upd:insertIntoAsFirst: inconsistent ordering rules 2008-05-15 19:40:30 +0000 1 1 1 Unclassified XPath / XQuery / XSLT Update Facility Working drafts PC Windows XP CLOSED FIXED P2 critical --- 4527 1 mrys andrew.eisenberg public-qt-comments oldest_to_newest 15004 0 mrys 2007-05-04 23:25:02 +0000 as first/as last: same as bug 4527. Also note that 3.1.4 upd:insertIntoAsFirst and ff is preserving order... inconsistency in spec. 15138 1 mrys 2007-05-22 17:20:28 +0000 To clarify this bug: 2.4.1 currently says: "If as first (or as last) is specified, the inserted nodes become the first (or last) children of the target node. If multiple nodes are inserted as first (or as last) in the same snapshot, the ordering among these nodes is implementation-dependent." As in bug 4527, this contradicts the wording in 3.1.4 and 3.1.5 where we correctly say: The children property of $target is changed to include the nodes in $content as the first/last children, preserving their order. Please clarify the meaning in 2.4.1 in a way that the behaviour of 3.1.4 and 3.1.5 is preserved. Here are some examples: let the context be <z><d/></z> do insert (<a/>,<b/>,<c/>) as first into /z should be <z><a/><b/><c/><d/></z> only (no other order) (do insert <a/> as first into /z),(do insert <b/> as first into /z) could be <z><a/><b/><d/></z> or <z><b/><a/><d/></z>. (do insert (<a/>,<b id="1"/>) as first into /z),(do insert (<b id="2"/>,<c/>) as first into /z) could be <z><a/><b id="1"/><b id="2"/><c/><d/></z> or <z><b="2"/><c/><a/><b id="1"/><d/></z> but does not allow interleaving of the sequences. 15365 2 chamberl 2007-06-11 23:22:39 +0000 Michael, I believe that this bug has been resolved by the spec changes that were agreed upon to resolve Bug 4527. Please examine these changes and change the status of this bug report to "Closed" if you agree. Regards, Don Chamberlin (for the Query Working Group)