Modeling Address using Relational Theory

I've looked at a bunch of address models and am wondering if there is a
generally-agreed-upon relational model for the parts of the address
that are not city, state/province, country, or postcode.

There is a standard multivalue model for it that is exceedingly simple:
Name of attribute: AddressLine
Display size: 30 chars (or so)
Cardinality: multivalued, likely with constaints in the code (I know, I
know) to limit this to 3 lines

What I keep seeing in self-described relational models is Line1, Line2,
Line3. That just seems wrong. What would be the purest relational
approach to this? What percentage of the time is it used when the
implementation is an RDBMS (or SQL-DBMS)?

Thanks. --dawn

.