2. My understanding is that the use of base64binary in a schema will cause a validating parser to callapse any whitespace during validation.
This is true as long as data type normalization is turned on. Most parsers let you turn it off. This is required to verify signatures over base64 elements when validating.
Or I suppose the other option would be to make sure you validate prior to sign. If I could think of some fancy way to do it, we could even mark base64binary elements somehow and have the security library convert them to normalised form as part of signing.
This also sucks, but it's the only workaround if you want to validate. Most people don't, and Xerces itself has so many schema-related bugs going unfixed lately that it's becoming nearly impossible to keep doing it as an implementer.
:<.
Cheers,
Berin
