fred, on Dec 18 2008, 05:24 PM, said:
Cascade, on Dec 18 2008, 02:57 AM, said:
As a player this seems totally unsatisfactory to me.
It is not intended to satisfy you.
Just to get the context clear this is what I was responding to:
"The ACBL has gone the other way, describing in general, and sometimes vague, terms what is allowed and disallowed. Players and Directors are expected to infer the intent. "
Are you satisfied by the fuzzy rules and the problems they cause.
Quote
As I understand it, the GCC is meant to be used in bridge clubs and lower level tournaments in North America.
It is intended to satisfy the 100K+ who play in ACBL GCC games. Most of these people are what you would call "club players". You, being a player who has represented New Zealand in the World Championships, play better than almost all of them. You also happen to be much much more interested, knowledgable, and experienced in terms of systems then almost all of them - perhaps even all of them.
You are not one of them.
True but I have played in ACBL games.
Quote
I don't have hard data as usual. This may be difficult (since you are not one of them), but perhaps you can reflect on the time you spent as an ACBL TD and consider:
What % of the these GCC-types would you guess are interested in scouring the GCC for loopholes that they can exploit?
What % of these GCC-types would want to play the 1C=spades system if it was allowed?
What % of these GCC-types would want to play against this system or some of the other systems that live in the loopholes?
You know the answers to all these questions is "a very small percentage". Trust your judgment and experience even though you don't like what it says. You don't need hard data to know the answers.
Its not really relevant to my argument. You say "live in the loopholes" as if it is clear what is a loophole. The problem is that it is not clear whether a method is part of the "loopholes" or whether it is allowed by the chart.
Even if the percentages for the above are small there is another group of regular players that believe methods that there opponents legitimately play are not allowed and complain and sometimes cause an unnecessary fuss. The methods they complain about are things like: Polish Club; non-standard NT ranges; offshape NTs; 'multi' openings that are not multi etc.
However even if the percentages are small these problems could be easily eliminated if the convention chart was clear and therefore better for everyone not just those who wish to experiment with system.
Quote
IMO Rick Beye did exactly the right thing by closing the loophole.
He did no such thing. The loophole is not closed. The GCC is as ambiguous as it was before Rick Beye expressed an opinion.
Quote
He did the right thing for the 100K+ GCC players who don't want to deal with 1C=spades. He did the right thing for the bridge clubs and tournaments who won't have deal with the potential disruption that would have occurred if Rick's answer had been "I guess GCC really does say that - you can play 1C=spades and feel free to play Pass=strong-but-not-forcing while you are at it!".
The right thing would be to change the GCC properly. Issuing a document that allows certain actions and then allowing someone to override that on some whim (however valid or not you believe a particular decision is) is a very dangerous situation.
If it is right to disallow methods that the GCC allows then it is much better to ammend the GCC than expect players to "infer the intent".
How are players and directors on the ground supposed to know what Rick Beye said in some private correspondence?
Quote
As you probably know, the ACBL considers BBO to be a "bridge club". In fact, we are the ACBL's biggest bridge club! As one of the managers of that club (where, as you know, GCC is played in all our ACBL games), I am grateful that there is someone as sensible as Rick Beye dealing with such things. In my view it is 1000% that he made the right decision in this case.
By the way, I think any ACBL member clever enough to find this loophole and interested enough in the 1C=spades system to ask Rick Beye, should (and would) have known in advance what Rick's answer would be. That person would know from experience that what is exposed by the loophole is not of the flavor that ACBL tried to capture with GCC. It was probably not posed as a "serious question".
I am not trying to excuse bad wording or loopholes in documentation pertaining to system restrictions.
I am not trying to make a judgement on whether or not any particular decision is good or bad.
Nor am I trying to pick on the ACBL or its GCC. Similar problems occur elsewhere.
I simply believe that regulations should say what they mean and mean what they say.