Problem:
While testing edge cases and alternate flows the system exhibited inconsistent behavior in the way it handled white space characters while parsing what otherwise would be valid unsigned integers.

Details:
The following value "999" is valid and used for the control for the error tests

Attempting to parse "999 " generates:
[Parse Error: Convert to Unsigned Int (for xs:unsignedInt): Unable to parse '999 ' (using up all characters).

Attempting to parse " 999" and "9 99"
Expected error. Didn't get one. Actual result was <uI_03 xmlns="http://example.com">999</uI_03>

Conclusion:
I'm not entirely sure which behavior is the proper behavior. Whether or not the system should trim white space but I do think the behavior should be consistent.

Applicable Test Cases:
Section05
test_whiteSpaceAfterValidValue
test_whiteSpaceBeforeValidValue
test_whiteSpaceDuringValidValue