Why was there a change of specific behaviour for JAXB 2.0 default validation?

Can anybody of the Java EE crowd tell me, what were the reasons in those days to make the validation more lenient and don't fail on erroneous XMLs?

Found a description in the docs, but no background information...

Since unmarshalling invalid XML content is defined in JAXB 2.0, the Unmarshaller default validation event handler was made more lenient than in JAXB 1.0. When schema-derived code generated by JAXB 1.0 binding compiler is registered with JAXBContext, the default unmarshal validation handler is DefaultValidationEventHandler and it terminates the marshal operation after encountering either a fatal error or an error. For a JAXB 2.0 client application, there is no explicitly defined default validation handler and the default event handling only terminates the unmarshal operation after encountering a fatal error. from: Interface Unmarshaller