Lax vs Strict on read

Your interop experience with Indigo (especially the upcoming drop or if you have been on one of the interop workshops) may lead you to say “man this thing is strict:”. Indigo rejects many invalid messages that other toolkits would accept.  

The key reason for being strict on read is to keep the protocols architecture simple and viable long term. Look at the browsers world - so much invalid html can be happily accepted, that it is simply impossible to describe the established profile. And therefore it is very hard to build a new implementation/fix existing implementations that would not break someone's page. We should make web services future cleaner. 

If you really need Indigo to consume some invalid message, Vipul shared a great post here that will help.