Could you provide a bit more background. My first instinct on this is to continue the storage as is (address1, address2) in freeform and to have services that read/transform that freeform into local conventions rather than storing them in local conventions.
--- BJ Freeman <[EMAIL PROTECTED]> wrote: > I am enhancing the PostalAddress. > there are two parts > 1)postal address specified by country. > This can be used to generate a screen to that country and do the > layout > for a mailing peice. > it also specifies how to store the address information. > > 2)storing the address informaion. > this is a free form system that lets the complete address be stored > in > the components that make up an address. > > the basic part is the Addressline > it has then name of the address line that is freefrom, this would be > used to show on the UI and or the mailing piece. > there is a linenumber and lineposition. The line position lets > complex > addresses be define as separate components. > Like the BR address line > Postal Area--Postal District--Postal Sector--delivery Point > with is you can also specify the separator and where to to put it. > > there are services that read the country formation information on a > Create and put in a map for a UI. > Service that Stores the data, win the free form format. > > These would override most of the data currently stored in the > PostalAddress entity. > > any input? > >
