New feature: Address Format

Description

We suggest to have address format in LDML specification, to deal with the
cultural diversity of address. The format can be as follows:

<address>
<addressSegments>
<addressSegment type="country">
<label>Country/Region</label>
<mandatory>yes</mandatory>
</addressSegment>
<addressSegment type="state">
...
</addressSegment>
<addressSegment type="city">
...
</addressSegment>
<addressSegment type="street">
...
</addressSegment>
<addressSegment type="zip">
...
</addressSegment>
</addressSegments>
<addressOrder>stcyspzpcr</addressOrder>
<addressPattern>%st%nn%cy%nn%sp%bk%zp%nn%cr</addressPattern>
<states>
<state>Alabama</state>
<state>Alaska</state>
<state>Arizona</state>
...
</states>
</address>

Explanation of each tag:
addressSegments contain the address items that compose an address.

addressOrder is the order that an address should be displayed. For example,
"stcyspzpcr" means the sequence: street, city, state, zip code, country.

addressPattern contains the address order and other format information of an
address. For example, in en_US locale, there is a new line for most of the
address items, while in zh_CN locale, most of the address items are put together
consecutively. In the pattern "%st%nn%cy%nn%sp%bk%zp%nn%cr", 'st', 'cy', 'sp',
'zp', 'cr' are the same meaning as in addressOrder, while 'nn' means a new line
and 'bk' means a blank.

states are the states/provinces of the country. Each country has their own state
lists.

xpath

None

locale

None

Activity

Show:
TracBot
May 9, 2019, 7:16 PM
Trac Comment by —2007-02-01T20:44:28.000Z

changed notes2

TracBot
May 9, 2019, 7:16 PM
Trac Comment by —2011-01-05T18:55:40.000Z

Blank milestone -> UNSCH per :

TracBot
May 9, 2019, 7:16 PM
Trac Comment 27 by —2015-04-24T18:48:39.807Z

component=future -> unknown, all such tickets are already milestone=UNSCH

Steven R. Loomis
March 18, 2020, 4:57 PM
Edited

Adding a link on teh site to https://opensource.google.com/projects/libphonenumber per CLDR-11437

mimckenna
November 2, 2020, 7:44 PM

I’d be more than happy to help on this initiative. Take a look at for a similar effort I’ve been leading at PayPal. This link only shows the transport schema, but we have been working on a number of issues related to context-sensitive layout, basic validations, and transforms between basic standards, and compatibility between HTML5 autocomplete fields and Google’s libaddressinput validation data.

Priority

minor

Assignee

Mark Davis

Reporter

TracBot

Reviewer

None

Labels

Components

None

Fix versions

None

Phase

None
Configure