I'm trying to get some discussion going, concerning a "generic" format for recording/interchange of partnership agreements. First two posts, to this, go into some detail as to my rationale.
I've also created a "first try" version, using XML, of such a format. Subsequent posts go into some detail concerning this. Including both my reasons for "feeling" that entry of an entire "convention card" should be a fairly-simple process, and a few aspects with which I am far from entirely satisfied.
I'd really appreciate some feedback, concerning what I've accomplished to date.
Group URL: http://groups.yahoo.com/group/Bridge_Metho...ods_Disclosure/
Steven P Haver/602-242-9708/8330 n 19th av 1083 phx az 85021
Page 1 of 1
Methods Disclosure Database
#2
Posted 2003-December-15, 10:17
I like the idea a lot but complexity will kill it inmediately.
Agreements should be just free text indexed by the players names.
Player1 - Player2 - Agreements. Just that.
When you find a new pd, you see if you have agreements with him, if so you send him the URL to review the text, if not you just ask and add an entry to the database or modify the existing entry.
It must be so simple that you shouldn't notice you are doing something or wasting any energy or nobody will use it.
Agreements should be just free text indexed by the players names.
Player1 - Player2 - Agreements. Just that.
When you find a new pd, you see if you have agreements with him, if so you send him the URL to review the text, if not you just ask and add an entry to the database or modify the existing entry.
It must be so simple that you shouldn't notice you are doing something or wasting any energy or nobody will use it.
The legend of the black octogon.
#3
Posted 2003-December-15, 11:27
Form follows function.
Before doing anything else, its critical to have a firm understanding how we expect these convention files to be used. In particular, is this type of file expected to be used by casual players engaged in a pickup partnership? Alternatively, do we expect this to be a tool for a well-oiled partnership.
From my own perspective, I would prefer the design of the convention file is optimized for the use of established partnerships. Rather than supporting the needs of casual or pickup partnerships, I would prefer that those players either
(a) Made use of a "standard" convention file designed to support SAYC, 2/1, or what have you
(
Made use of traditional "manual" alerts.
Before doing anything else, its critical to have a firm understanding how we expect these convention files to be used. In particular, is this type of file expected to be used by casual players engaged in a pickup partnership? Alternatively, do we expect this to be a tool for a well-oiled partnership.
From my own perspective, I would prefer the design of the convention file is optimized for the use of established partnerships. Rather than supporting the needs of casual or pickup partnerships, I would prefer that those players either
(a) Made use of a "standard" convention file designed to support SAYC, 2/1, or what have you
(
Alderaan delenda est
#4
Posted 2004-January-11, 01:34
[FONT=Arial][SIZE=7][COLOR=purple]I like the concept very much. With KLPV13 we've evolved to understandings over agreements and conventions, and having a place to elucidate them will be a great progression for pard and I. As noted, form does follow function - and it like anything good in concept, must be tested and tinkered with until it fits for the masses. I for one will support this actively.
"Champions aren't made in gyms, champions are made from something they have deep inside them - a desire, a dream, a vision. They have to have last-minute stamina, they have to be a little faster, they have to have the skill and the will. But the will must be stronger than the skill. " - M. Ali
Page 1 of 1

Help
