
Silverston c07.tex V2 - 11/20/2008 5:44pm Page 391
Contact Mechanism with Flexible Address Parts Pattern 391
or even in creating separate entities for each of these. The GEOGRAPHIC
BOUNDARY entity maintains any type of encompassing area, such as, but not
limited to, a COUNTY, CITY, STATE, POSTAL CODE, PROVINCE, CANTON,
PREFECTURE, or TERRITORY.
Each CONTACT MECHANISM may have several GEOGRAPHIC
BOUNDARY(s) via the associative entity CONTACT MECHANISM
BOUNDARY. For example, a POSTAL ADDRESS may need a GEOGRAPHIC
BOUNDARY of both a postal code and a city. Geographic boundaries may
apply to more than just postal addresses. Phone numbers have a country
telephone code that is an attribute of a COUNTRY s ubtype of GEOGRAPHIC
BOUNDARY. Electronic addresses may also have different geographic bound-
aries. For example ‘‘info@XYZ.com’’ may be an electronic address for XYZ
Corporation, but so could ‘‘info@XYZ.co.uk,’’ ‘‘info@XYZ.co.hk,’’ and
‘‘info@XYZ.ie.’’ The ‘‘.co.uk’’ designates the United Kingdom, ‘‘.co.hk’’ des-
ignates the Hong Kong region, and ‘‘.ie’’ designates Ireland. Thus, each
ELECTRONIC ADDRESS subtype of CONTACT MECHANISM may be
related to a GEOGRAPHIC BOUNDARY attribute of geographic internet
region code in order to show that an email is for a country, such as ‘‘India,’’
which has an ‘‘.in’’ geographic internet region code.
This pattern is a very flexible data model solution that accommodates ...