C2MS13 — There Should be No Optional Boolean Fields in Messages

In the next major revision (2.0), when backwards-compatibility is not an anchor, we need to update all Boolean fields in messages to be either required or dependent, and in the latter case to make clear what it is dependent upon.

No boolean field should be optional... They should all be present with either TRUE or FALSE values.

This is because it is ambiguous how a message receiver should interpret a non-present Boolean field. They must simply chose whether to treat it as TRUE or FALSE.