Comment 6 for bug 1411478

I think that we have odd behavior on either side: with or without the fix.

Either the deployer has mapped an attribute assuming it gets converted to a Boolean or they have not used a "Boolean" strong anywhere in name or description because of this issue

It is likely the more correct route is to be explicit about where things are converted to Boolean vs always assuming "true" or "false" strings are meant o be booleans