This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
These two examples use a source document (ftbookexample) with a schema (ftbookexamplexsd). The document element (book) is complex content, so the boundary whitespace shouldn't be appearing in the expected results. examples-222-q2 examples-222-q3
Personal response: I disagree. The whitespace comes from the content, not from an XQuery constructor, so boundary whitespace setting is irrelevant. There is no reason to believe that the whitespace is stripped from the content or from the serialization.
I'm not referring to the XQuery boundary whitespace setting (which is indeed irrelevant). The source document (ftbookexample) contains whitespace. When the content is parsed and validated, the (insignificant) whitespace is discarded in the (element-only) book element. It should therefore not appear in the expected results.
There is a similar problem in examples-23-q3 - specifically examples-23-q3-alt.txt.