Optional YesNo types display 'Maybe' as option, which is not always semantically correct

(Incomplete Feature, Investigate , Priority: Medium, Test Status: No automated tests yet , Reported By Bad Link: Thing 3y284oe not found, )
Summary: I'm creating Models which have YesNo data items only relevant in certain circumstances - so I create them as Optional. The UI for them then shows "Maybe" in addition to "Yes" and "No", which is semantically all wrong - when the value isn't present, that's because it's meaningless / not applicable.
It also would lead me to believe that 'Maybe' is an explicit value I can check for, whereas from following the dev blog I think (?) that when an Optional value isn't present it's just Empty (can't remember exact syntax).
Justin: not clear to me what the correct answer here is. I suppose we could make the label of the "None" button configurable. In many circumstances, "Maybe" is exactly right, because the semantics are "no decision has been made".