Trinidad, on 2013-March-31, 02:30, said:
In your model, there is 1 non-alertable meaning and there are many alertable meanings. I only stated that it is not a disaster if for some situations there are 0 non-alertable meanings and many+1 alertable meanings. I have never said that it would be good, let alone best, to have 2 or more non-alertable meanings.
I don't even mind multiple non-Alertable meanings, provided they are all "common" and "expected". The ACBL in its wisdom have *many* such situations, some of which I don't like (because I don't think they're "expected" enough; 1
♣-2
♣ showing any of majors (usually), spades and diamonds (sometimes) or hearts and diamonds (for the pair that plays 2NT for the majors. Yes there is at least one), for instance). 1NT-something-double, in the ACBL, neither penalty or takeout ("negative") are Alertable.
I would prefer that there be 1 non-Alertable meaning; but I'd rather have multiple non-Alertable meanings than a common Alertable meaning and at least one "sort of common" Alertable meaning. Back when Transfers were Alerted, our "real Alert" of 2
♦ was frequently ignored. (When Announcements came in, we frequently got "Alert" "you just have to Announce transfers now, not Alert" "Thank you. Alert." "But, But..." "Maybe you should ask". But it worked out in time.) If there are multiple common non-Alertable meanings, you have to ask. If there's one very common Alertable meaning, people tend not to ask.
Continuing down my path, if there are zero non-Alertable meanings for a common call, the Alert is a meaningless noise; if there were no Alerts for anything for that call, people would either know to ask (if it was say "takeout is Alertable because it's conventional, penalty is Alertable because it's unexpected, but still happens fairly often"), or not bother (in the EBU preAnnouncement Stayman, or ACBL preAnnouncement Transfer case). Since everything is Alertable, instead of nonAlertable, the same thing will happen, because the same information is transmitted (either there's enough people playing different things that you should always ask, or "everybody plays it as X", in which case nobody asks). Therefore, there is no information being passed by the Alert. Yeah "you should ask", but 99% of the time, you'll get "it's Stayman, just like everybody else plays it".
Quote
Other posters have argued that alerting all meanings amounts to the same as alerting none, since the alert doesn't carry any information. I argued that this is true in the sense that the alert doesn't say anything about the meaning of the call. But the intent of an alert is NOT to tell something about the meaning of a call. It is saying: "You may need to ask" or (when there is no alert) "Normally no need to ask".
Yeah, but when it's 100% Alertable, and 99+% of the time, the opponents know the answer to the question, they don't "need to ask". So either it's Alertable because it has to be to make the Alert procedure sane; or it's not Alertable because the Alert Procedure is "these, expected, conventions are so expected as to be exceptions to 'alert convention' meta-rule"); or it gets turned into an Announcement, because that solution to this issue seems to acceptably solve that problem (with the caveats above).
Quote
When your partner makes a call where the alertability of all meanings is equal you want to tell the opponents: "You may need to ask". Therefore, in such a situation, all meanings should be alertable, rather than having all non-alertable.
The problem is that the Alertability of all meanings are *not* equal; one meaning is Alertable because it's conventional, the other meaning is Alertable because it's *unexpected*. The binary switch is one for both cases, but the Alertability is not equal. And that's the problem with a binary system such as Alerts.
When I go to sea, don't fear for me, Fear For The Storm -- Birdie and the Swansong (tSCoSI)