Next: 1.8.4.1 <FormattedAddress>
Up: 1.8 Shared Elements
Previous: 1.8.3.1 <FormattedName>
Contents
Index
1.8.4 <Postal>
A <Postal> element contains either a structured or an unstructured
representation of a single snail mail postal address. Suppliers should
use the structured format where possible as it provides many more
possibilities for a Consumer to utilise the data geospatially.
Attributes
May Contain
- Choice
-
- Structured postal address
-
- <Address>
- Compulsory. The initial parts
of the Postal address. This may contain new lines if necessary. It
should not contain data that would normally be represented in <Town>,
<Region>, <CountryCode> or <PostalCode>. If it isn't possible to strip
out this data then it may be necessary to utilise a <FormattedAddress>
format instead.
- <Town>
- Compulsory. string
- <Region>
- Optional. string
- <CountryCode>
- Compulsory. 2 letter
upper case ISO 3166 country code.
- <PostalCode>
- Optional. string. The
<PostalCode> is optional to enable the modelling of addresses in countries
that don't always include a post code system. However it is strongly
recommended that it should be included where known.
- <FormattedAddress>
- Optional. This should
be included if the representation is more accurate than what one would
get from algorithmically generating the complete address from the
structured elements.
- Unstructured postal address
-
- <FormattedAddress>
- Compulsory
Contained Within
- shared Contact elements
-
Subsections
Next: 1.8.4.1 <FormattedAddress>
Up: 1.8 Shared Elements
Previous: 1.8.3.1 <FormattedName>
Contents
Index
Alex Fiennes
2010-04-13