look at the contactmechtype for different types of electroninc addresses it is a one to many
BJ Freeman sent the following on 5/6/2009 3:34 PM: > there is information about a contact which is in the contact mech. > email is under electronic Address. > > then there is the event of the actual communications which you will find > under communication event modeling. > > Cimballi sent the following on 5/6/2009 2:47 PM: >> Hi, >> >> I was wondering was you didn't model the Email informations like Phone >> informations in ContactMech. >> Why is there no entity that model an Email, like the TelecomNumber entity ? >> >> My problem is, if I want to add another field to an Email informations, the >> possibilities are : >> - extending the ContactMech class, but it's not optimum because this class >> is used for a lot of other informations than Email >> - add a ContactMechAttribute related to the ContactMech entity representing >> the Email informations, but this imply more work to maintain the relation >> >> It would have been a lot easier to have an ElectronicAddress entity, no ? >> >> Cimballi >> > -- BJ Freeman http://www.businessesnetwork.com/automation http://bjfreeman.elance.com http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro Systems Integrator.
