whitespace after validation

[Vinayak R. Borkar]

SchemaImport/FLWORExprSI/ForExprType038
SchemaImport/FLWORExprSI/ForExprType039

[Matthias Brantner (matthias-brantner)]

The title is not correct anymore. There is quite a tricky bug in the two tests now. Other people also ran into that problem (see http://www.w3.org/Bugs/Public/show_bug.cgi?id=5534).

Our result:
<InterleaveType xmlns="http://typedecl">
<integer>10</integer>
<decimal>20</decimal>
</InterleaveType>

Expected Result:
<InterleaveType xmlns="http://typedecl"><integer>10</integer><decimal>20</decimal></InterleaveType>

The whitespaces should have been stripped when reading the input document during schema
validation, because InterleaveType has element-only content.

[Cezar Andrei (cezar-andrei)]

XQ XP Datamodel Spec: http://www.w3.org/TR/xpath-datamodel/ is probably what we're looking for:

6.7.4 Construction from a PSVI

For Text Nodes constructed from the [schema normalized value] of elements, content contains the value of the [schema normalized value].

Otherwise, construction from a PSVI is the same as construction from the Infoset except for the content property. When constructing the content property, [element content whitespace] is not used to test if whitespace is collapsed. Instead, if the resulting Text Node consists entirely of whitespace and the character information items used to construct this node have a parent and that parent is an element and its {content type} is not “mixed”, then the content of the Text Node is the zero-length string.

[Cezar Andrei (cezar-andrei)]

Fixed with rev 7719. Tests are passing.