Specification Name: OASIS EDXL extensible Address Language (xAL) profile ver 1.0
Description: Defines the W3C schema for the EDXL Profile for representing addresses
(Using XML Schema based standard code list/enumeration mechanism - OPTION 1 AND DEFAULT)
Produced by: Emergency Management Infrastructure Framework Subcommittee
URL: http://docs.oasis-open.org
Version: 1.0
Status: Committee Specification Draft
Copyright: 2010, OASIS, http://www.oasis-open.org
Last Modified: 12 July 2011
Last Modified by: Don McGarry - The MITRE Corp.
Update 23 July, 2014 (by Werner Joerg): for compliance with EDXL Naming and Capitalization Guidelines (EM-TC 12/18/2012)
Profile Developed From:
Specification Name: OASIS CIQ TC - extensible Address Language (xAL)
Description: Defines the W3C schema for representing addresses
(Using XML Schema based standard code list/enumeration mechanism - OPTION 1 AND DEFAULT)
Produced by: OASIS Customer Information Quality Technical Committee
URL: http://www.oasis-open.org/committees/ciq
Version: 3.0
Status: Committee Specification CS02
Copyright: 2007-09, OASIS, http://www.oasis-open.org
Last Modified: 20 September 2008
Last Modified by: Ram Kumar, Chair, OASIS CIQ TC
Top level element for address with geocode details
Complex type that defines the structure of an address with geocode details for reuse
Container for free text address elements where address elements are not parsed
Free format address representation. An address can have more than one line.
The order of the AddressLine elements must be preserved.
Country details
Details of the top-level area division in the country, such as state, district,
province, island, region, etc. Note that some countries do not have this
Data associated with the Administrative Area. e.g. Full name of administrative
area or part of it. eg. MI in USA, NSW in Australia, reference location to the
administrative area
The next level down division of the area. E.g. state / county, province /
reservation. Note that not all countries have a subadministrative area
Data associated with the SubAdministrative Area. e.g. Full name of
sub administrative area or part of it.
Details of Locality which is a named densiliy populated area (a place) such as town,
village, suburb, etc. A locality composes of many individual addresses. Many localities
exist in an administrative area or a sub adminisrative area. A locality can also have sub
localities. For example, a municipality locality can have many villages associated with
it which are sub localities. Example: Tamil Nadu State, Erode District, Bhavani Taluk,
Paruvachi Village is a valid address in India. Tamil Nadu is the Administrative Area,
Erode is the sub admin area, Bhavani is the locality, and Paruvachi is the sub locality
Data associated with the locality. e.g. Full name of the locality or part
of it, reference location to the locality
A locality that is smaller and is contained within the boundaries of its
parent locality. Note that not all localities have sub locality. For example,
many areas within a locality where each area is a sub locality
Data associated with the sub locality. e.g. Full name of the
locality or part of it, reference location to the locality
Details of the Access route along which buildings/lot/land are located, such as
street, road, channel, crescent, avenue, etc. This also includes canals/banks on
which houses/boat houses are located where people live
A container for a single free text or structured postcode. Note that not all
countries have post codes
The postcode is formatted according to country-specific rules.
Example: SW3 0A8-1A, 600074, 2067. This element can also be used to
define the semantics of what each code in the post code means
Complex type that defines the name of the country and is reused in other CIQ specs
Data associated with the name of the country in whatever form available,
e.g. full, abbreviation, common use, code of the country, etc.
Complex type for internal reuse
Indicates which part of number or identifier this element contains.
Some "numbers" are as simple as 42 and some "numbers" are more like
complex aplhanumberic identifiers as Postcodes in UK or Canada, e.g.
M2H 2S5. It may be necessary to separate the "number" into sub-elements
and indicate what type of information each of them contains.
Complex type for internal reuse
Data associated with the thoroughfare details. e.g. Full thoroughfare name
or part of it, type of thoroughfare, old name, new name, reference data in
support of the thoroughfare
Describes the type / part of name this element contains.
Data associated with the number of the thoroughfare. E.g. 39 in 39 Baker
Street, street range, street suffix
Type of thoroughfare. eg. primary road, secondary road, road branch (e.g. Lane 14),
road sub branch (e.g. Alley 21), adjourning street, cross street, closest street, etc