Re: ContactMechPurposeType bad design

2010-02-02 Thread Ruth Hoffman
Hi Hans: Yes, this is used in other places. What exactly do you mean by "change"? Regards, Ruth Hans Bakker wrote: If we change that and can still select a "primary email" then that sounds pretty good...however isn't this often used in the system? On Mon, 2010-02-01 at 15:23 -0600, Adam Heath w

Re: ContactMechPurposeType bad design

2010-02-01 Thread Hans Bakker
If we change that and can still select a "primary email" then that sounds pretty good...however isn't this often used in the system? On Mon, 2010-02-01 at 15:23 -0600, Adam Heath wrote: > There is currently a PRIMARY_EMAIL, PRIMARY_LOCATION, BILLING_EMAIL, > BILLING_LOCATION, etc. Why can't that

Re: ContactMechPurposeType bad design

2010-02-01 Thread Nicolas Malin
Cimballi a écrit : Not sure about the original idea, but from my point of view this helps to know what kind of contact mech is behind the purpose type. For example, if you have a party and you want to get its primary email contact mech, you search for PRIMARY_EMAIL and you know you will have only

Re: ContactMechPurposeType bad design

2010-02-01 Thread Adam Heath
Cimballi wrote: > Not sure about the original idea, but from my point of view this helps > to know what kind of contact mech is behind the purpose type. > For example, if you have a party and you want to get its primary email > contact mech, you search for PRIMARY_EMAIL and you know you will have >

Re: ContactMechPurposeType bad design

2010-02-01 Thread Cimballi
Not sure about the original idea, but from my point of view this helps to know what kind of contact mech is behind the purpose type. For example, if you have a party and you want to get its primary email contact mech, you search for PRIMARY_EMAIL and you know you will have only emails (well, if you

ContactMechPurposeType bad design

2010-02-01 Thread Adam Heath
There is currently a PRIMARY_EMAIL, PRIMARY_LOCATION, BILLING_EMAIL, BILLING_LOCATION, etc. Why can't that just be PRIMARY, BILLING, etc?