well so much for sounding like I know what I am talking about.
I meant expand the POSTADDRESS entitiy.
BJ Freeman sent the following on 7/21/2006 10:19 AM:
Currently there is only one service to validate Postal Addresses.
I am looking at expanding this but having a universal address validation
that can call different validating services, such as usps, based on
geocode, and services available.
This would allow those in other countries that have different postal
code formats to use different external or internal services.
I have something similar model implemented in my online DB environment.
The first layer is just to have a services that frame work that allows
for a single entry point with that looks up a parm for the country codes
covered and the service to call. this is open for discussion.
it would pass the information included in the CONTACTMECH entity with
Type postaladdress.
the CONTACTMECH entity would be modified to store the expanded
information. how is open for discussion.
different from the current OUT information it would be expanded to show
an new data that provides more comprehensive address information. if
this is of interest I will post the info in a jira.
This is something I am implementing, just thought I would see if anyone
had thoughts that might effect my coding.
