It looks like the CLP of DB2 gives you the behaviour you are asking for http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/index.jsp?topic=%2Fcom.ibm.db2.luw.xml.doc%2Fdoc%2Fxqrserial.html
But as mentioned before this is outside XQuery itself it's the environment , API , or processor that adds this bit I personally feel it would have been a better choice to have used new lines ( whatever they are ) instead of spaces as the default XDM serialization separator for sequences but that's really a tiny thing in the grand scheme of things. Xmlsh does this but it's vastly more useful to NOT serialize sequences but rather keep them in internal form so You can pick them apart Before handing them off to a non XDM aware process. Hence the suggestion of using an API that can get at the results of XQuery aka XDM before serialization. Xmlsh also supports this .. Getting the results of any XDM process in an internal form without serialization. But that's again the province of the processor and/or API. Not XQuery itself. Again back to the unanswered questions What processor are you using What results do you expect and why What is your end goal Maybe there is a better way to accomplish your end goals then text serialization tweaks to XDM Sent from my iPad (excuse the terseness) David A Lee [email protected] On Mar 10, 2012, at 10:24 PM, "[email protected]" <[email protected]> wrote: > OK, I submitted https://www.w3.org/Bugs/Public/show_bug.cgi?id=16311 > However as I have a rather hard time expressing myself, > perhaps those who know what I am saying could add some detail to the > bug. In the rare case the detail is wrong, I will chime in there. Thanks. > _______________________________________________ > [email protected] > http://x-query.com/mailman/listinfo/talk > _______________________________________________ [email protected] http://x-query.com/mailman/listinfo/talk
