XML Schema
Schema Comments:
Processing Instructions
Schema has:
45element definitions,  0 global attribute definitions,  11 element attribute definitions,  1 datatype definitions.
Possible root elements: < GlobalAddress >  

Element list

Element AddressLine
 
diagram
description
attributes
uses Does not reference other elements.
 
used byAddressLines  
content sequence (default)
typexsd:string
 
source
 <xsd:element name="AddressLine" type="xsd:string" />

Element AddressLines
 
diagram
description The order of the AddressLine elements must be preserved
attributes
uses AddressLine (0 , unbounded )
 
used byGlobalAddress   Country   AdministrativeArea   LargeMailUser   PostOffice   PostBox   Organisation   Department   Street   Premise   SubPremise   PostalCode   TLocality  
content sequence
 
source
-<xsd:element name="AddressLines">
-<xsd:annotation>
 <xsd:documentation>The order of the AddressLine elements must be preserved</xsd:documentation>
 </xsd:annotation>
-<xsd:complexType>
-<xsd:sequence>
 <xsd:element ref="AddressLine" maxOccurs="unbounded" />
 </xsd:sequence>
 </xsd:complexType>
 </xsd:element>

Element AdministrativeArea
 
diagram
description Specification of an administrative area. Examples of administrative areas are provinces, bundesamts, etc. There are two places where the name of an administrative area can be specified. Use the following guidelines to choose one of these places: 1) If the name of the administrative area is known for all addresses in that area, then the area name should be stored in an AdministrativeArea element. This way, the name has to be specified only once, which reduces data redundancy. 2) If the name of the administrative area is known for only a few addresses in that area and is only used to make the name of a locality unique, then append the area name to the locality name and store the combination as a LocalityName element (within the Locality element). The name type of the LocalityName must be set to "Unique". Example: in Austria there are more then one localities with the name "Amstetten". To create a unique name, the name of the administrative area is appended to the official locality name: "Amstetten, NiederNiederosterreich".
attributes AdministrativeAreaType  
uses AddressLines, AdministrativeAreaName (0 , unbounded ) , SubAdministrativeArea ? , Locality, PostOffice
 
used byCountry  
content sequence
 
AttributeDatatypeUseValuesDefaultComments
AdministrativeAreaTypexsd:stringdefaultUnknownProvince or State or County or Kanton or Unknown
 
source
-<xsd:element name="AdministrativeArea">
-<xsd:annotation>
 <xsd:documentation xml:lang="en">Specification of an administrative area. Examples of administrative areas are provinces, bundesamts, etc. There are two places where the name of an administrative area can be specified. Use the following guidelines to choose one of these places: 1) If the name of the administrative area is known for all addresses in that area, then the area name should be stored in an AdministrativeArea element. This way, the name has to be specified only once, which reduces data redundancy. 2) If the name of the administrative area is known for only a few addresses in that area and is only used to make the name of a locality unique, then append the area name to the locality name and store the combination as a LocalityName element (within the Locality element). The name type of the LocalityName must be set to "Unique". Example: in Austria there are more then one localities with the name "Amstetten". To create a unique name, the name of the administrative area is appended to the official locality name: "Amstetten, NiederNiederosterreich". </xsd:documentation>
 </xsd:annotation>
-<xsd:complexType>
-<xsd:choice>
 <xsd:element ref="AddressLines" />
-<xsd:sequence>
 <xsd:element ref="AdministrativeAreaName" maxOccurs="unbounded" />
 <xsd:element ref="SubAdministrativeArea" minOccurs="0" />
-<xsd:choice>
 <xsd:element ref="Locality" />
 <xsd:element ref="PostOffice" />
 </xsd:choice>
 </xsd:sequence>
 </xsd:choice>
-<xsd:attribute name="AdministrativeAreaType" use="default" value="Unknown" type="xsd:string">
-<xsd:annotation>
 <xsd:documentation>Province or State or County or Kanton or Unknown</xsd:documentation>
 </xsd:annotation>
<!-- 
Possible values but not limited to: Province, State, County, Kanton, Unknown
 -->
 </xsd:attribute>
 </xsd:complexType>
 </xsd:element>

Element AdministrativeAreaName
 
diagram
description Specification of the name of an administrative area. Examples of administrative areas are provinces counties, special regions (such as "Rijnmond"), etc. Possible values of NameType not limited to: Official, Unique, Abbreviation, OldName, Synonym.
attributes
uses Does not reference other elements.
 
used byAdministrativeArea  
content sequence (default)
typeTName
 
source
-<xsd:element name="AdministrativeAreaName" type="TName">
-<xsd:annotation>
 <xsd:documentation xml:lang="en">Specification of the name of an administrative area. Examples of administrative areas are provinces counties, special regions (such as "Rijnmond"), etc. Possible values of NameType not limited to: Official, Unique, Abbreviation, OldName, Synonym. </xsd:documentation>
 </xsd:annotation>
 </xsd:element>

Element BuildingName
 
diagram
description Specification of the name of a building. See also the specification of the SinglePremise element. Possible values of NameType not limited to: Official, Unique, Abbreviation, OldName, Synonym.
attributes
uses Does not reference other elements.
 
used byLargeMailUser   Premise   SubPremise   TPremise  
content sequence (default)
typeTName
 
source
-<xsd:element name="BuildingName" type="TName">
-<xsd:annotation>
 <xsd:documentation xml:lang="en">Specification of the name of a building. See also the specification of the SinglePremise element. Possible values of NameType not limited to: Official, Unique, Abbreviation, OldName, Synonym. </xsd:documentation>
 </xsd:annotation>
 </xsd:element>

Element Country
 
diagram
description Specification of a country.
attributes
uses AddressLines, CountryCode (0 , unbounded ) , CountryName * , AdministrativeArea, Locality
 
used byGlobalAddress  
content sequence
 
source
-<xsd:element name="Country">
-<xsd:annotation>
 <xsd:documentation xml:lang="en">Specification of a country. </xsd:documentation>
 </xsd:annotation>
-<xsd:complexType>
-<xsd:choice>
-<xsd:sequence>
 <xsd:element ref="AddressLines" />
 </xsd:sequence>
-<xsd:sequence>
 <xsd:element ref="CountryCode" maxOccurs="unbounded" />
 <xsd:element ref="CountryName" minOccurs="0" maxOccurs="unbounded" />
-<xsd:choice>
 <xsd:element ref="AdministrativeArea" />
 <xsd:element ref="Locality" />
 </xsd:choice>
 </xsd:sequence>
 </xsd:choice>
 </xsd:complexType>
 </xsd:element>

Element CountryCode
 
diagram
description Country code scheme possible values, but not limited to: iso.3166-2, iso.3166-3 for two- and three-character country codes.
attributes
uses Does not reference other elements.
 
used byCountry  
content sequence (default)
typeTCode
 
source
-<xsd:element name="CountryCode" type="TCode">
-<xsd:annotation>
 <xsd:documentation xml:lang="en">Country code scheme possible values, but not limited to: iso.3166-2, iso.3166-3 for two- and three-character country codes. </xsd:documentation>
 </xsd:annotation>
 </xsd:element>

Element CountryName
 
diagram
description Specification of the name of a country. Possible values of NameType not limited to: Official, Unique, Abbreviation, OldName, Synonym.
attributes
uses Does not reference other elements.
 
used byCountry  
content sequence (default)
typeTName
 
source
-<xsd:element name="CountryName" type="TName">
-<xsd:annotation>
 <xsd:documentation xml:lang="en">Specification of the name of a country. Possible values of NameType not limited to: Official, Unique, Abbreviation, OldName, Synonym. </xsd:documentation>
 </xsd:annotation>
 </xsd:element>

Element DeliveryPointSuffix
 
diagram
description Examples are: 1234 (USA), 1G (UK), etc.
attributes
uses Does not reference other elements.
 
used byPostalCode  
content sequence (default)
typexsd:string
 
source
-<xsd:element name="DeliveryPointSuffix" type="xsd:string">
-<xsd:annotation>
 <xsd:documentation>Examples are: 1234 (USA), 1G (UK), etc. </xsd:documentation>
 </xsd:annotation>
 </xsd:element>

Element Department
 
diagram
description
attributes
uses AddressLines, DepartmentName (0 , unbounded ) , PostalCode ?
 
used byLargeMailUser   Organisation  
content sequence
 
source
-<xsd:element name="Department">
-<xsd:annotation>
 <xsd:documentation xml:lang="en" />
 </xsd:annotation>
-<xsd:complexType>
-<xsd:choice>
 <xsd:element ref="AddressLines" />
-<xsd:sequence>
 <xsd:element ref="DepartmentName" maxOccurs="unbounded" />
 <xsd:element ref="PostalCode" minOccurs="0" />
 </xsd:sequence>
 </xsd:choice>
 </xsd:complexType>
 </xsd:element>

Element DepartmentName
 
diagram
description Specification of the name of a department. Possible NameType values not limited to: Official, Unique, Abbreviation, OldName, Synonym.
attributes
uses Does not reference other elements.
 
used byDepartment  
content sequence (default)
typeTName
 
source
-<xsd:element name="DepartmentName" type="TName">
-<xsd:annotation>
 <xsd:documentation xml:lang="en">Specification of the name of a department. Possible NameType values not limited to: Official, Unique, Abbreviation, OldName, Synonym. </xsd:documentation>
 </xsd:annotation>
 </xsd:element>

Element DependentLocality
 
diagram
description Dependent localities are Districts within cities/towns, locality divisions, postal divisions of cities, suburbs, etc. DependentLocality is a recursive element, but no nesting deeper than two exists (Locality->DependentLocality->DependentLocality).
attributes LocalityType  
uses DependentLocalityName (0 , unbounded ) , DependentLocality ?
 
used byDependentLocality   TLocality  
content sequence
 
AttributeDatatypeUseValuesDefaultComments
LocalityTypexsd:stringdefaultUnknownCity or IndustrialEstate or Unknown When in use for DependentLocality: PostalZone
 
source
-<xsd:element name="DependentLocality">
-<xsd:annotation>
 <xsd:documentation>Dependent localities are Districts within cities/towns, locality divisions, postal divisions of cities, suburbs, etc. DependentLocality is a recursive element, but no nesting deeper than two exists (Locality->DependentLocality->DependentLocality). </xsd:documentation>
 </xsd:annotation>
-<xsd:complexType>
-<xsd:sequence>
 <xsd:element ref="DependentLocalityName" maxOccurs="unbounded" />
 <xsd:element ref="DependentLocality" minOccurs="0" />
 </xsd:sequence>
-<xsd:attribute name="LocalityType" use="default" value="Unknown" type="xsd:string">
-<xsd:annotation>
 <xsd:documentation>City or IndustrialEstate or Unknown When in use for DependentLocality: PostalZone</xsd:documentation>
 </xsd:annotation>
 </xsd:attribute>
 </xsd:complexType>
 </xsd:element>

Element DependentLocalityName
 
diagram
description
attributes
uses Does not reference other elements.
 
used byDependentLocality  
content sequence (default)
typeTName
 
source
 <xsd:element name="DependentLocalityName" type="TName" />

Element DependentStreet
 
diagram
description DependentStreet is related to a street; occurs in GB, IE, ES, PT
attributes
uses StreetName (0 , unbounded )
 
used byStreet  
content sequence
 
source
-<xsd:element name="DependentStreet">
-<xsd:annotation>
 <xsd:documentation>DependentStreet is related to a street; occurs in GB, IE, ES, PT </xsd:documentation>
 </xsd:annotation>
-<xsd:complexType>
-<xsd:sequence>
 <xsd:element ref="StreetName" maxOccurs="unbounded" />
 </xsd:sequence>
 </xsd:complexType>
 </xsd:element>

Element GlobalAddress
 
diagram
description Test for multiple documentation sections part one
- - - - -
Test for multiple documentation sections part two
- - - - -
Test for multiple documentation sections part three
attributes
uses Country, AddressLines
 
used byNot used by other elements. Possible root element.
content sequence
 
source
-<xsd:element name="GlobalAddress">
-<xsd:annotation>
 <xsd:documentation xml:lang="en">Test for multiple documentation sections part one </xsd:documentation>
 <xsd:documentation xml:lang="en">Test for multiple documentation sections part two </xsd:documentation>
 <xsd:documentation xml:lang="en">Test for multiple documentation sections part three </xsd:documentation>
 </xsd:annotation>
-<xsd:complexType>
-<xsd:sequence>
 <xsd:element ref="Country" />
 <xsd:element ref="AddressLines" />
 </xsd:sequence>
 </xsd:complexType>
 </xsd:element>

Element LargeMailUser
 
diagram
description Specification of a large mail user address. Examples of large mail users are postal companies, companies in France with a cedex number, hospitals and airports with their own post code. Large mail user addresses do not have a street name with premise name or premise number.
attributes LargeMailUserType  
uses AddressLines, LargeMailUserName * , LargeMailUserIdentifier ? , BuildingName * , Department ? , PostalCode ?
 
used byTLocality  
content sequence
 
AttributeDatatypeUseValuesDefaultComments
LargeMailUserTypexsd:stringdefaultLargeUser
 
source
-<xsd:element name="LargeMailUser">
-<xsd:annotation>
 <xsd:documentation xml:lang="en">Specification of a large mail user address. Examples of large mail users are postal companies, companies in France with a cedex number, hospitals and airports with their own post code. Large mail user addresses do not have a street name with premise name or premise number. </xsd:documentation>
 </xsd:annotation>
-<xsd:complexType>
-<xsd:choice>
 <xsd:element ref="AddressLines" />
-<xsd:sequence>
 <xsd:element ref="LargeMailUserName" minOccurs="0" maxOccurs="unbounded" />
 <xsd:element ref="LargeMailUserIdentifier" minOccurs="0" />
 <xsd:element ref="BuildingName" minOccurs="0" maxOccurs="unbounded" />
 <xsd:element ref="Department" minOccurs="0" />
 <xsd:element ref="PostalCode" minOccurs="0" />
 </xsd:sequence>
 </xsd:choice>
 <xsd:attribute name="LargeMailUserType" use="default" value="LargeUser" type="xsd:string" />
 </xsd:complexType>
 </xsd:element>

Element LargeMailUserIdentifier
 
diagram
description Specification of the identification number of a large mail user. An example are the Cedex codes in France.
attributes
uses Does not reference other elements.
 
used byLargeMailUser  
content sequence (default)
typexsd:string
 
source
-<xsd:element name="LargeMailUserIdentifier" type="xsd:string">
-<xsd:annotation>
 <xsd:documentation xml:lang="en">Specification of the identification number of a large mail user. An example are the Cedex codes in France. </xsd:documentation>
 </xsd:annotation>
 </xsd:element>

Element LargeMailUserName
 
diagram
description Specification of the name of a large mail user. Possible values of NameType not limited to: Official, Unique, Abbreviation, OldName, Synonym.
attributes
uses Does not reference other elements.
 
used byLargeMailUser  
content sequence (default)
typeTName
 
source
-<xsd:element name="LargeMailUserName" type="TName">
-<xsd:annotation>
 <xsd:documentation xml:lang="en">Specification of the name of a large mail user. Possible values of NameType not limited to: Official, Unique, Abbreviation, OldName, Synonym. </xsd:documentation>
 </xsd:annotation>
 </xsd:element>

Element Locality
 
diagram
description Specification of a locality. Examples of localities are cities, reservations and any other built-up areas.
attributes
uses Does not reference other elements.
 
used byCountry   AdministrativeArea  
content sequence (default)
typeTLocality
 
source
-<xsd:element name="Locality" type="TLocality">
-<xsd:annotation>
 <xsd:documentation xml:lang="en">Specification of a locality. Examples of localities are cities, reservations and any other built-up areas. </xsd:documentation>
 </xsd:annotation>
 </xsd:element>

Element LocalityName
 
diagram
description Specification of the name of a locality. Possible values of NameType not limited to: Official, Unique, Abbreviation, OldName, Synonym.
attributes
uses Does not reference other elements.
 
used byTLocality  
content sequence (default)
typeTName
 
source
-<xsd:element name="LocalityName" type="TName">
-<xsd:annotation>
 <xsd:documentation xml:lang="en">Specification of the name of a locality. Possible values of NameType not limited to: Official, Unique, Abbreviation, OldName, Synonym. </xsd:documentation>
 </xsd:annotation>
 </xsd:element>

Element Organisation
 
diagram
description Specification of a firm, company, organization, etc. It can be specified as part of an address that contains a street or a postbox. It is therefore different from a large mail user address, which contains neither a street nor a postbox.
attributes
uses AddressLines, OrganisationName (0 , unbounded ) , Department ? , PostalCode ?
 
used byPostBox   Street   Premise   SubPremise   TPremise  
content sequence
 
source
-<xsd:element name="Organisation">
-<xsd:annotation>
 <xsd:documentation xml:lang="en">Specification of a firm, company, organization, etc. It can be specified as part of an address that contains a street or a postbox. It is therefore different from a large mail user address, which contains neither a street nor a postbox. </xsd:documentation>
 </xsd:annotation>
-<xsd:complexType>
-<xsd:choice>
 <xsd:element ref="AddressLines" />
-<xsd:sequence>
 <xsd:element ref="OrganisationName" maxOccurs="unbounded" />
 <xsd:element ref="Department" minOccurs="0" />
 <xsd:element ref="PostalCode" minOccurs="0" />
 </xsd:sequence>
 </xsd:choice>
 </xsd:complexType>
 </xsd:element>

Element OrganisationName
 
diagram
description Specification of the name of a firm. Examples of a firm are companies and organizations. Possible values of NameType not limited to: Official, Unique, Abbreviation, OldName, Synonym.
attributes
uses Does not reference other elements.
 
used byOrganisation  
content sequence (default)
typeTName
 
source
-<xsd:element name="OrganisationName" type="TName">
-<xsd:annotation>
 <xsd:documentation xml:lang="en">Specification of the name of a firm. Examples of a firm are companies and organizations. Possible values of NameType not limited to: Official, Unique, Abbreviation, OldName, Synonym. </xsd:documentation>
 </xsd:annotation>
 </xsd:element>

Element PostalCode
 
diagram
description PostalCode is the container element for either simple or complex (extended) postal codes.
attributes
uses AddressLines, PostalCodeNumber, PostTown ? , SortingCode ? , DeliveryPointSuffix ?
 
used byLargeMailUser   PostOffice   PostBox   Organisation   Department   Street   Premise   SubPremise   TLocality   TPremise  
content sequence
 
source
-<xsd:element name="PostalCode">
-<xsd:annotation>
 <xsd:documentation>PostalCode is the container element for either simple or complex (extended) postal codes.</xsd:documentation>
 </xsd:annotation>
-<xsd:complexType>
-<xsd:choice>
 <xsd:element ref="AddressLines" />
-<xsd:sequence>
 <xsd:element ref="PostalCodeNumber" />
 <xsd:element ref="PostTown" minOccurs="0" />
 <xsd:element ref="SortingCode" minOccurs="0" />
 <xsd:element ref="DeliveryPointSuffix" minOccurs="0" />
 </xsd:sequence>
 </xsd:choice>
 </xsd:complexType>
 </xsd:element>

Element PostalCodeNumber
 
diagram
description Specification of a postcode. The postcode is formatted according to country-specific rules. Example: SW3 0A8-1A
attributes
uses Does not reference other elements.
 
used byPostalCode  
content sequence (default)
typexsd:string
 
source
-<xsd:element name="PostalCodeNumber" type="xsd:string">
-<xsd:annotation>
 <xsd:documentation xml:lang="en">Specification of a postcode. The postcode is formatted according to country-specific rules. Example: SW3 0A8-1A </xsd:documentation>
 </xsd:annotation>
 </xsd:element>

Element PostBox
 
diagram
description Specification of a postbox like mail delivery point. Only a single postbox number can be specified. Examples of postboxes are POBox, free mail numbers, etc. PostBoxType possible values are, not limited to: POBox and Freepost.
attributes PostBoxType  
uses AddressLines, PostBoxNumber, Organisation, PostalCode ?
 
used byPostOffice   TLocality  
content sequence
 
AttributeDatatypeUseValuesDefaultComments
PostBoxTypexsd:string optional (default)
 
source
-<xsd:element name="PostBox">
-<xsd:annotation>
 <xsd:documentation xml:lang="en">Specification of a postbox like mail delivery point. Only a single postbox number can be specified. Examples of postboxes are POBox, free mail numbers, etc. PostBoxType possible values are, not limited to: POBox and Freepost. </xsd:documentation>
 </xsd:annotation>
-<xsd:complexType>
-<xsd:choice>
 <xsd:element ref="AddressLines" />
-<xsd:sequence>
 <xsd:element ref="PostBoxNumber" />
 <xsd:element ref="Organisation" />
 <xsd:element ref="PostalCode" minOccurs="0" />
 </xsd:sequence>
 </xsd:choice>
 <xsd:attribute name="PostBoxType" type="xsd:string" />
 </xsd:complexType>
 </xsd:element>

Element PostBoxNumber
 
diagram
description Specification of the number of a postbox .
attributes
uses Does not reference other elements.
 
used byPostBox  
content sequence (default)
typexsd:string
 
source
-<xsd:element name="PostBoxNumber" type="xsd:string">
-<xsd:annotation>
 <xsd:documentation xml:lang="en">Specification of the number of a postbox . </xsd:documentation>
 </xsd:annotation>
 </xsd:element>

Element PostOffice
 
diagram
description Specification of a post office. Examples are a rural post office where post is delivered and a post office containing post office boxes.
attributes
uses AddressLines, PostOfficeName (0 , unbounded ) , PostBox, PostalCode ?
 
used byAdministrativeArea   TLocality  
content sequence
 
source
-<xsd:element name="PostOffice">
-<xsd:annotation>
 <xsd:documentation xml:lang="en">Specification of a post office. Examples are a rural post office where post is delivered and a post office containing post office boxes. </xsd:documentation>
 </xsd:annotation>
-<xsd:complexType>
-<xsd:choice>
 <xsd:element ref="AddressLines" />
-<xsd:sequence>
 <xsd:element ref="PostOfficeName" maxOccurs="unbounded" />
 <xsd:element ref="PostBox" />
 <xsd:element ref="PostalCode" minOccurs="0" />
 </xsd:sequence>
 </xsd:choice>
 </xsd:complexType>
 </xsd:element>

Element PostOfficeName
 
diagram
description Specification of the name of the post office. This can be a rural postoffice where post is delivered or a post office containing post office boxes. Possible values of NameType not limited to: Official, Unique, Abbreviation, OldName, Synonym.
attributes
uses Does not reference other elements.
 
used byPostOffice  
content sequence (default)
typeTName
 
source
-<xsd:element name="PostOfficeName" type="TName">
-<xsd:annotation>
 <xsd:documentation xml:lang="en">Specification of the name of the post office. This can be a rural postoffice where post is delivered or a post office containing post office boxes. Possible values of NameType not limited to: Official, Unique, Abbreviation, OldName, Synonym. </xsd:documentation>
 </xsd:annotation>
 </xsd:element>

Element PostTown
 
diagram
description Sub-element of the extended PostalCode, specification of a post town. A post town is not the same as a locality. A post town can encompass a collection of (small) localities. It can also be a subpart of a locality. An actual post town in Norway is "Bergen".
attributes
uses PostTownName (0 , unbounded )
 
used byPostalCode  
content sequence
 
source
-<xsd:element name="PostTown">
-<xsd:annotation>
 <xsd:documentation>Sub-element of the extended PostalCode, specification of a post town. A post town is not the same as a locality. A post town can encompass a collection of (small) localities. It can also be a subpart of a locality. An actual post town in Norway is "Bergen". </xsd:documentation>
 </xsd:annotation>
-<xsd:complexType>
-<xsd:sequence>
 <xsd:element ref="PostTownName" maxOccurs="unbounded" />
 </xsd:sequence>
 </xsd:complexType>
 </xsd:element>

Element PostTownName
 
diagram
description Specification of the name of a post town. A post town is not the same as a locality. A post town can encompass a collection of (small) localities. It can also be a subpart of a locality. Possible values of NameType not limited to: Official, Unique, Abbreviation, OldName, Synonym.
attributes
uses Does not reference other elements.
 
used byPostTown  
content sequence (default)
typeTName
 
source
-<xsd:element name="PostTownName" type="TName">
-<xsd:annotation>
 <xsd:documentation xml:lang="en">Specification of the name of a post town. A post town is not the same as a locality. A post town can encompass a collection of (small) localities. It can also be a subpart of a locality. Possible values of NameType not limited to: Official, Unique, Abbreviation, OldName, Synonym. </xsd:documentation>
 </xsd:annotation>
 </xsd:element>

Element Premise
 
diagram
description Specification of a single premise, for example a house or a building. The premise as a whole has a unique premise (house) number or a premise name. If the premise is divided into sub-premises (e.g. apartments), then specify the sub-premise number with a SubPremise element. If a premise can only be identified by a premise name, because it has no premise (house) number, then specify that name in the element PremiseName (and not in the BuildingName). If a premise can be identified by a premise (house) number, but also has a house or building name, then do not store that name in the element PremiseName, but store it instead in the element BuildingName. The elements BuildingName and SecondaryStreetString all represent extra information that is nice to know, but is not a required part of a formal post address.
attributes
uses AddressLines, PremiseNumber, PremiseName (0 , unbounded ) , BuildingName * , SubPremise, Organisation, PostalCode ?
 
used byStreet   TLocality  
content sequence
 
source
-<xsd:element name="Premise">
-<xsd:annotation>
 <xsd:documentation xml:lang="en">Specification of a single premise, for example a house or a building. The premise as a whole has a unique premise (house) number or a premise name. If the premise is divided into sub-premises (e.g. apartments), then specify the sub-premise number with a SubPremise element. If a premise can only be identified by a premise name, because it has no premise (house) number, then specify that name in the element PremiseName (and not in the BuildingName). If a premise can be identified by a premise (house) number, but also has a house or building name, then do not store that name in the element PremiseName, but store it instead in the element BuildingName. The elements BuildingName and SecondaryStreetString all represent extra information that is nice to know, but is not a required part of a formal post address. </xsd:documentation>
 </xsd:annotation>
-<xsd:complexType>
-<xsd:choice>
 <xsd:element ref="AddressLines" />
-<xsd:sequence>
-<xsd:choice>
 <xsd:element ref="PremiseNumber" />
 <xsd:element ref="PremiseName" maxOccurs="unbounded" />
 </xsd:choice>
 <xsd:element ref="BuildingName" minOccurs="0" maxOccurs="unbounded" />
-<xsd:choice minOccurs="0">
 <xsd:element ref="SubPremise" />
 <xsd:element ref="Organisation" />
 </xsd:choice>
 <xsd:element ref="PostalCode" minOccurs="0" />
 </xsd:sequence>
 </xsd:choice>
 </xsd:complexType>
 </xsd:element>

Element PremiseName
 
diagram
description Specification of the name of the premise (house, building, etc). A premise name is specified when the premise cannot be addressed using a street name plus premise (house) number. Possible values of NameType not limited to: Official, Unique, Abbreviation, OldName, Synonym.
attributes
uses Does not reference other elements.
 
used byPremise   TPremise  
content sequence (default)
typeTName
 
source
-<xsd:element name="PremiseName" type="TName">
-<xsd:annotation>
 <xsd:documentation xml:lang="en">Specification of the name of the premise (house, building, etc). A premise name is specified when the premise cannot be addressed using a street name plus premise (house) number. Possible values of NameType not limited to: Official, Unique, Abbreviation, OldName, Synonym. </xsd:documentation>
 </xsd:annotation>
 </xsd:element>

Element PremiseNumber
 
diagram
description Specification of the identifier of the premise (house, building, etc). Premises in a street are often uniquely identified by means of consecutive identifiers. The identifier can be a number, a letter or any combination of the two. This comment irrelevant: In the latter case, the identifier includes exactly one variable (range) part, which is either a number or a single letter that is surrounded by fixed parts at the left (prefix) or the right (postfix).
attributes
uses Does not reference other elements.
 
used byPremise   TPremise  
content sequence (default)
typexsd:string
 
source
-<xsd:element name="PremiseNumber" type="xsd:string">
-<xsd:annotation>
 <xsd:documentation xml:lang="en">Specification of the identifier of the premise (house, building, etc). Premises in a street are often uniquely identified by means of consecutive identifiers. The identifier can be a number, a letter or any combination of the two. This comment irrelevant: In the latter case, the identifier includes exactly one variable (range) part, which is either a number or a single letter that is surrounded by fixed parts at the left (prefix) or the right (postfix). </xsd:documentation>
 </xsd:annotation>
 </xsd:element>

Element SortingCode
 
diagram
description Values may for example be CEDEX 16 (France)
attributes
uses Does not reference other elements.
 
used byPostalCode  
content sequence (default)
typexsd:string
 
source
-<xsd:element name="SortingCode" type="xsd:string">
-<xsd:annotation>
 <xsd:documentation>Values may for example be CEDEX 16 (France) </xsd:documentation>
 </xsd:annotation>
 </xsd:element>

Element Street
 
diagram
description Specification of a street.
attributes
uses AddressLines, StreetName (0 , unbounded ) , DependentStreet ? , Premise, Organisation, PostalCode ?
 
used byTLocality  
content sequence
 
source
-<xsd:element name="Street">
-<xsd:annotation>
 <xsd:documentation xml:lang="en">Specification of a street. </xsd:documentation>
 </xsd:annotation>
-<xsd:complexType>
-<xsd:choice>
-<xsd:sequence>
 <xsd:element ref="AddressLines" />
 </xsd:sequence>
-<xsd:sequence>
 <xsd:element ref="StreetName" maxOccurs="unbounded" />
 <xsd:element ref="DependentStreet" minOccurs="0" />
-<xsd:choice>
 <xsd:element ref="Premise" />
 <xsd:element ref="Organisation" />
 <xsd:element ref="PostalCode" minOccurs="0" />
 </xsd:choice>
 </xsd:sequence>
 </xsd:choice>
 </xsd:complexType>
 </xsd:element>

Element StreetName
 
diagram
description Specification of the name of a street (also dependant street name). Possible values of NameType not limited to: Official, Unique, Abbreviation, OldName, Synonym.
attributes
uses Does not reference other elements.
 
used byStreet   DependentStreet  
content sequence (default)
typeTName
 
source
-<xsd:element name="StreetName" type="TName">
-<xsd:annotation>
 <xsd:documentation>Specification of the name of a street (also dependant street name). Possible values of NameType not limited to: Official, Unique, Abbreviation, OldName, Synonym. </xsd:documentation>
 </xsd:annotation>
 </xsd:element>

Element SubAdministrativeArea
 
diagram
description Specification of a sub-administrative area. An example of a sub-administrative areas is a county. There are two places where the name of an administrative area can be specified. See the specification of the AdministrativeArea element for more information.
attributes SubAdministrativeAreaType  
uses SubAdministrativeAreaName (0 , unbounded )
 
used byAdministrativeArea  
content sequence
 
AttributeDatatypeUseValuesDefaultComments
SubAdministrativeAreaTypexsd:stringdefaultUnknownProvince or State or County or Kanton or Unknown
 
source
-<xsd:element name="SubAdministrativeArea">
-<xsd:annotation>
 <xsd:documentation xml:lang="en">Specification of a sub-administrative area. An example of a sub-administrative areas is a county. There are two places where the name of an administrative area can be specified. See the specification of the AdministrativeArea element for more information. </xsd:documentation>
 </xsd:annotation>
-<xsd:complexType>
-<xsd:sequence>
 <xsd:element ref="SubAdministrativeAreaName" maxOccurs="unbounded" />
 </xsd:sequence>
-<xsd:attribute name="SubAdministrativeAreaType" use="default" value="Unknown" type="xsd:string">
-<xsd:annotation>
 <xsd:documentation>Province or State or County or Kanton or Unknown</xsd:documentation>
 </xsd:annotation>
<!-- 
Possible values but not limited to: Province, State, County, Kanton, Unknown
 -->
 </xsd:attribute>
 </xsd:complexType>
 </xsd:element>

Element SubAdministrativeAreaName
 
diagram
description Specification of the sub-administrative area name. Examples are county (Ireland) and concelho (Portugal). Possible values of NameType not limited to: Official, Unique, Abbreviation, OldName, Synonym.
attributes
uses Does not reference other elements.
 
used bySubAdministrativeArea  
content sequence (default)
typeTName
 
source
-<xsd:element name="SubAdministrativeAreaName" type="TName">
-<xsd:annotation>
 <xsd:documentation xml:lang="en">Specification of the sub-administrative area name. Examples are county (Ireland) and concelho (Portugal). Possible values of NameType not limited to: Official, Unique, Abbreviation, OldName, Synonym. </xsd:documentation>
 </xsd:annotation>
 </xsd:element>

Element SubPremise
 
diagram
description Specification of a single sub-premise. Examples of sub-premises are apartments and suites. Each sub-premise should be uniquely identifiable. SubPremiseType: Specification of the name of a sub-premise type. Possible values not limited to: Suite, Appartment, Floor, Unknown.
attributes SubPremiseType  
uses AddressLines, SubPremiseNumber, SubPremiseName (0 , unbounded ) , BuildingName * , Organisation ? , PostalCode ?
 
used byPremise   TPremise  
content sequence
 
AttributeDatatypeUseValuesDefaultComments
SubPremiseTypexsd:stringdefaultUnknownSubPremiseType may be Apartment, Lot, etc.
 
source
-<xsd:element name="SubPremise">
-<xsd:annotation>
 <xsd:documentation xml:lang="en">Specification of a single sub-premise. Examples of sub-premises are apartments and suites. Each sub-premise should be uniquely identifiable. SubPremiseType: Specification of the name of a sub-premise type. Possible values not limited to: Suite, Appartment, Floor, Unknown. </xsd:documentation>
 </xsd:annotation>
-<xsd:complexType>
-<xsd:choice>
 <xsd:element ref="AddressLines" />
-<xsd:sequence>
-<xsd:choice>
 <xsd:element ref="SubPremiseNumber" />
 <xsd:element ref="SubPremiseName" maxOccurs="unbounded" />
 </xsd:choice>
 <xsd:element ref="BuildingName" minOccurs="0" maxOccurs="unbounded" />
 <xsd:element ref="Organisation" minOccurs="0" />
 <xsd:element ref="PostalCode" minOccurs="0" />
 </xsd:sequence>
 </xsd:choice>
-<xsd:attribute name="SubPremiseType" use="default" value="Unknown" type="xsd:string">
-<xsd:annotation>
 <xsd:documentation>SubPremiseType may be Apartment, Lot, etc.</xsd:documentation>
 </xsd:annotation>
 </xsd:attribute>
 </xsd:complexType>
 </xsd:element>

Element SubPremiseName
 
diagram
description Possible values of NameType not limited to: Official, Unique, Abbreviation, OldName, Synonym.
attributes
uses Does not reference other elements.
 
used bySubPremise  
content sequence (default)
typeTName
 
source
-<xsd:element name="SubPremiseName" type="TName">
-<xsd:annotation>
 <xsd:documentation xml:lang="en"> Possible values of NameType not limited to: Official, Unique, Abbreviation, OldName, Synonym. </xsd:documentation>
 </xsd:annotation>
 </xsd:element>

Element SubPremiseNumber
 
diagram
description Specification of the identifier of a sub-premise. Examples of sub-premises are apartments and suites. sub-premises in a building are often uniquely identified by means of consecutive identifiers. The identifier can be a number, a letter or any combination of the two. In the latter case, the identifier includes exactly one variable (range) part, which is either a number or a single letter that is surrounded by fixed parts at the left (prefix) or the right (postfix).
attributes
uses Does not reference other elements.
 
used bySubPremise  
content sequence (default)
typexsd:string
 
source
-<xsd:element name="SubPremiseNumber" type="xsd:string">
-<xsd:annotation>
 <xsd:documentation xml:lang="en">Specification of the identifier of a sub-premise. Examples of sub-premises are apartments and suites. sub-premises in a building are often uniquely identified by means of consecutive identifiers. The identifier can be a number, a letter or any combination of the two. In the latter case, the identifier includes exactly one variable (range) part, which is either a number or a single letter that is surrounded by fixed parts at the left (prefix) or the right (postfix). </xsd:documentation>
 </xsd:annotation>
 </xsd:element>

Complex Type TCode
 
diagram
description
attributes Scheme   Code  
uses Does not reference other elements.
 
used byNot used by other elements. Probably an orphan.
content sequence (default)
 
AttributeDatatypeUseValuesDefaultComments
Schemexsd:stringrequired
Codexsd:stringrequired
 
source
-<xsd:complexType name="TCode">
 <xsd:attribute name="Scheme" use="required" type="xsd:string" />
 <xsd:attribute name="Code" use="required" type="xsd:string" />
 </xsd:complexType>

Complex Type TLocality
 
diagram
description
attributes LocalityType  
uses AddressLines, LocalityName (0 , unbounded ) , DependentLocality ? , Street, PostBox, LargeMailUser, PostOffice, Premise, PostalCode
 
used byNot used by other elements. Possible root element.
content sequence
 
AttributeDatatypeUseValuesDefaultComments
LocalityTypexsd:stringdefaultUnknownCity or IndustrialEstate or Unknown When in use for DependentLocality: PostalZone
 
source
-<xsd:complexType name="TLocality">
-<xsd:choice>
-<xsd:sequence>
 <xsd:element ref="AddressLines" />
 </xsd:sequence>
-<xsd:sequence>
 <xsd:element ref="LocalityName" maxOccurs="unbounded" />
 <xsd:element ref="DependentLocality" minOccurs="0" />
-<xsd:choice minOccurs="0">
 <xsd:element ref="Street" />
 <xsd:element ref="PostBox" />
 <xsd:element ref="LargeMailUser" />
 <xsd:element ref="PostOffice" />
 <xsd:element ref="Premise" />
 <xsd:element ref="PostalCode" />
 </xsd:choice>
 </xsd:sequence>
 </xsd:choice>
-<xsd:attribute name="LocalityType" use="default" value="Unknown" type="xsd:string">
-<xsd:annotation>
 <xsd:documentation>City or IndustrialEstate or Unknown When in use for DependentLocality: PostalZone</xsd:documentation>
 </xsd:annotation>
 </xsd:attribute>
 </xsd:complexType>

Complex Type TName derived by extension from xsd:string
 
diagram
description
attributes NameType   xml:lang  
uses Does not reference other elements.
 
used by See base element xsd:string  
substitution hierarchy TName
content simple content
 
AttributeDatatypeUseValuesDefaultComments
NameTypexsd:stringdefaultOfficialValues: Official, Unique, Abbreviation, OldName, Synonym.
xml:langxsd:string optional (default)
 
source
-<xsd:complexType name="TName">
-<xsd:simpleContent>
-<xsd:extension base="xsd:string">
-<xsd:attribute name="NameType" use="default" value="Official" type="xsd:string">
-<xsd:annotation>
 <xsd:documentation>Values: Official, Unique, Abbreviation, OldName, Synonym.</xsd:documentation>
 </xsd:annotation>
 </xsd:attribute>
 <xsd:attribute name="xml:lang" type="xsd:string" />
 </xsd:extension>
 </xsd:simpleContent>
 </xsd:complexType>

Complex Type TPremise
 
diagram
description
attributes
uses PremiseNumber, PremiseName (0 , unbounded ) , BuildingName * , SubPremise, Organisation, PostalCode ?
 
used byNot used by other elements. Possible root element.
content sequence
 
source
-<xsd:complexType name="TPremise">
-<xsd:sequence>
-<xsd:choice>
 <xsd:element ref="PremiseNumber" />
 <xsd:element ref="PremiseName" maxOccurs="unbounded" />
 </xsd:choice>
 <xsd:element ref="BuildingName" minOccurs="0" maxOccurs="unbounded" />
-<xsd:choice minOccurs="0">
 <xsd:element ref="SubPremise" />
 <xsd:element ref="Organisation" />
 </xsd:choice>
 <xsd:element ref="PostalCode" minOccurs="0" />
 </xsd:sequence>
 </xsd:complexType>

DataType definitions

Datatype DependentLocalityName   defined by restriction
 
dt base xsd:string

Original Schema Source
<!-- 
Generated by XML Authority. Conforms to w3c http://www.w3.org/2000/10/XMLSchema
 -->
-<xsd:schema>
<!-- 
Conforms to w3c http://www.w3.org/2000/10/XMLSchema
 -->
<!-- 
 AND Schema for Global Address information
 -->
<!-- 
 Version 1.2 - Last modified on March 2001 by Vincent Buller
 -->
<!-- 
 (C) 2000, 2001 AND Data Solutions - all rights reserved
 -->
<!-- 
 Use of this specification is bound to terms found at http://www.and.com/standards/repository.html
 -->
<!-- 
 For queries and requests mailto:xml@and.com
 -->
<!-- 
 Main elements
 -->
<!-- 
############################################################################
 -->
<!-- 
### Basic Types                                                                                                                                            ###
 -->
<!-- 
############################################################################
 -->
-<xsd:complexType name="TName">
-<xsd:simpleContent>
-<xsd:extension base="xsd:string">
-<xsd:attribute name="NameType" use="default" value="Official" type="xsd:string">
-<xsd:annotation>
 <xsd:documentation>Values: Official, Unique, Abbreviation, OldName, Synonym.</xsd:documentation>
 </xsd:annotation>
 </xsd:attribute>
 <xsd:attribute name="xml:lang" type="xsd:string" />
 </xsd:extension>
 </xsd:simpleContent>
 </xsd:complexType>
-<xsd:complexType name="TCode">
 <xsd:attribute name="Scheme" use="required" type="xsd:string" />
 <xsd:attribute name="Code" use="required" type="xsd:string" />
 </xsd:complexType>
<!-- 
############################################################################
 -->
<!-- 
### Element Definitions                                                                                                                              ###
 -->
<!-- 
############################################################################
 -->
-<xsd:element name="GlobalAddress">
-<xsd:annotation>
 <xsd:documentation xml:lang="en">Test for multiple documentation sections part one </xsd:documentation>
 <xsd:documentation xml:lang="en">Test for multiple documentation sections part two </xsd:documentation>
 <xsd:documentation xml:lang="en">Test for multiple documentation sections part three </xsd:documentation>
 </xsd:annotation>
-<xsd:complexType>
-<xsd:sequence>
 <xsd:element ref="Country" />
 <xsd:element ref="AddressLines" />
 </xsd:sequence>
 </xsd:complexType>
 </xsd:element>
<!-- 
############################################################################
 -->
-<xsd:element name="Country">
-<xsd:annotation>
 <xsd:documentation xml:lang="en">Specification of a country. </xsd:documentation>
 </xsd:annotation>
-<xsd:complexType>
-<xsd:choice>
-<xsd:sequence>
 <xsd:element ref="AddressLines" />
 </xsd:sequence>
-<xsd:sequence>
 <xsd:element ref="CountryCode" maxOccurs="unbounded" />
 <xsd:element ref="CountryName" minOccurs="0" maxOccurs="unbounded" />
-<xsd:choice>
 <xsd:element ref="AdministrativeArea" />
 <xsd:element ref="Locality" />
 </xsd:choice>
 </xsd:sequence>
 </xsd:choice>
 </xsd:complexType>
 </xsd:element>
<!-- 
############################################################################
 -->
-<xsd:element name="AdministrativeArea">
-<xsd:annotation>
 <xsd:documentation xml:lang="en">Specification of an administrative area. Examples of administrative areas are provinces, bundesamts, etc. There are two places where the name of an administrative area can be specified. Use the following guidelines to choose one of these places: 1) If the name of the administrative area is known for all addresses in that area, then the area name should be stored in an AdministrativeArea element. This way, the name has to be specified only once, which reduces data redundancy. 2) If the name of the administrative area is known for only a few addresses in that area and is only used to make the name of a locality unique, then append the area name to the locality name and store the combination as a LocalityName element (within the Locality element). The name type of the LocalityName must be set to "Unique". Example: in Austria there are more then one localities with the name "Amstetten". To create a unique name, the name of the administrative area is appended to the official locality name: "Amstetten, NiederNiederosterreich". </xsd:documentation>
 </xsd:annotation>
-<xsd:complexType>
-<xsd:choice>
 <xsd:element ref="AddressLines" />
-<xsd:sequence>
 <xsd:element ref="AdministrativeAreaName" maxOccurs="unbounded" />
 <xsd:element ref="SubAdministrativeArea" minOccurs="0" />
-<xsd:choice>
 <xsd:element ref="Locality" />
 <xsd:element ref="PostOffice" />
 </xsd:choice>
 </xsd:sequence>
 </xsd:choice>
-<xsd:attribute name="AdministrativeAreaType" use="default" value="Unknown" type="xsd:string">
-<xsd:annotation>
 <xsd:documentation>Province or State or County or Kanton or Unknown</xsd:documentation>
 </xsd:annotation>
<!-- 
Possible values but not limited to: Province, State, County, Kanton, Unknown
 -->
 </xsd:attribute>
 </xsd:complexType>
 </xsd:element>
<!-- 
############################################################################
 -->
-<xsd:element name="SubAdministrativeArea">
-<xsd:annotation>
 <xsd:documentation xml:lang="en">Specification of a sub-administrative area. An example of a sub-administrative areas is a county. There are two places where the name of an administrative area can be specified. See the specification of the AdministrativeArea element for more information. </xsd:documentation>
 </xsd:annotation>
-<xsd:complexType>
-<xsd:sequence>
 <xsd:element ref="SubAdministrativeAreaName" maxOccurs="unbounded" />
 </xsd:sequence>
-<xsd:attribute name="SubAdministrativeAreaType" use="default" value="Unknown" type="xsd:string">
-<xsd:annotation>
 <xsd:documentation>Province or State or County or Kanton or Unknown</xsd:documentation>
 </xsd:annotation>
<!-- 
Possible values but not limited to: Province, State, County, Kanton, Unknown
 -->
 </xsd:attribute>
 </xsd:complexType>
 </xsd:element>
<!-- 
############################################################################
 -->
-<xsd:element name="Locality" type="TLocality">
-<xsd:annotation>
 <xsd:documentation xml:lang="en">Specification of a locality. Examples of localities are cities, reservations and any other built-up areas. </xsd:documentation>
 </xsd:annotation>
 </xsd:element>
<!-- 
############################################################################
 -->
-<xsd:element name="DependentLocality">
-<xsd:annotation>
 <xsd:documentation>Dependent localities are Districts within cities/towns, locality divisions, postal divisions of cities, suburbs, etc. DependentLocality is a recursive element, but no nesting deeper than two exists (Locality->DependentLocality->DependentLocality). </xsd:documentation>
 </xsd:annotation>
-<xsd:complexType>
-<xsd:sequence>
 <xsd:element ref="DependentLocalityName" maxOccurs="unbounded" />
 <xsd:element ref="DependentLocality" minOccurs="0" />
 </xsd:sequence>
-<xsd:attribute name="LocalityType" use="default" value="Unknown" type="xsd:string">
-<xsd:annotation>
 <xsd:documentation>City or IndustrialEstate or Unknown When in use for DependentLocality: PostalZone</xsd:documentation>
 </xsd:annotation>
 </xsd:attribute>
 </xsd:complexType>
 </xsd:element>
<!-- 
############################################################################
 -->
<!-- 
############################################################################
 -->
-<xsd:element name="LargeMailUser">
-<xsd:annotation>
 <xsd:documentation xml:lang="en">Specification of a large mail user address. Examples of large mail users are postal companies, companies in France with a cedex number, hospitals and airports with their own post code. Large mail user addresses do not have a street name with premise name or premise number. </xsd:documentation>
 </xsd:annotation>
-<xsd:complexType>
-<xsd:choice>
 <xsd:element ref="AddressLines" />
-<xsd:sequence>
 <xsd:element ref="LargeMailUserName" minOccurs="0" maxOccurs="unbounded" />
 <xsd:element ref="LargeMailUserIdentifier" minOccurs="0" />
 <xsd:element ref="BuildingName" minOccurs="0" maxOccurs="unbounded" />
 <xsd:element ref="Department" minOccurs="0" />
 <xsd:element ref="PostalCode" minOccurs="0" />
 </xsd:sequence>
 </xsd:choice>
 <xsd:attribute name="LargeMailUserType" use="default" value="LargeUser" type="xsd:string" />
 </xsd:complexType>
 </xsd:element>
<!-- 
############################################################################
 -->
-<xsd:element name="PostOffice">
-<xsd:annotation>
 <xsd:documentation xml:lang="en">Specification of a post office. Examples are a rural post office where post is delivered and a post office containing post office boxes. </xsd:documentation>
 </xsd:annotation>
-<xsd:complexType>
-<xsd:choice>
 <xsd:element ref="AddressLines" />
-<xsd:sequence>
 <xsd:element ref="PostOfficeName" maxOccurs="unbounded" />
 <xsd:element ref="PostBox" />
 <xsd:element ref="PostalCode" minOccurs="0" />
 </xsd:sequence>
 </xsd:choice>
 </xsd:complexType>
 </xsd:element>
<!-- 
############################################################################
 -->
-<xsd:element name="PostBox">
-<xsd:annotation>
 <xsd:documentation xml:lang="en">Specification of a postbox like mail delivery point. Only a single postbox number can be specified. Examples of postboxes are POBox, free mail numbers, etc. PostBoxType possible values are, not limited to: POBox and Freepost. </xsd:documentation>
 </xsd:annotation>
-<xsd:complexType>
-<xsd:choice>
 <xsd:element ref="AddressLines" />
-<xsd:sequence>
 <xsd:element ref="PostBoxNumber" />
 <xsd:element ref="Organisation" />
 <xsd:element ref="PostalCode" minOccurs="0" />
 </xsd:sequence>
 </xsd:choice>
 <xsd:attribute name="PostBoxType" type="xsd:string" />
 </xsd:complexType>
 </xsd:element>
<!-- 
############################################################################
 -->
-<xsd:element name="Organisation">
-<xsd:annotation>
 <xsd:documentation xml:lang="en">Specification of a firm, company, organization, etc. It can be specified as part of an address that contains a street or a postbox. It is therefore different from a large mail user address, which contains neither a street nor a postbox. </xsd:documentation>
 </xsd:annotation>
-<xsd:complexType>
-<xsd:choice>
 <xsd:element ref="AddressLines" />
-<xsd:sequence>
 <xsd:element ref="OrganisationName" maxOccurs="unbounded" />
 <xsd:element ref="Department" minOccurs="0" />
 <xsd:element ref="PostalCode" minOccurs="0" />
 </xsd:sequence>
 </xsd:choice>
 </xsd:complexType>
 </xsd:element>
<!-- 
############################################################################
 -->
-<xsd:element name="Department">
-<xsd:annotation>
 <xsd:documentation xml:lang="en" />
 </xsd:annotation>
-<xsd:complexType>
-<xsd:choice>
 <xsd:element ref="AddressLines" />
-<xsd:sequence>
 <xsd:element ref="DepartmentName" maxOccurs="unbounded" />
 <xsd:element ref="PostalCode" minOccurs="0" />
 </xsd:sequence>
 </xsd:choice>
 </xsd:complexType>
 </xsd:element>
<!-- 
############################################################################
 -->
-<xsd:element name="Street">
-<xsd:annotation>
 <xsd:documentation xml:lang="en">Specification of a street. </xsd:documentation>
 </xsd:annotation>
-<xsd:complexType>
-<xsd:choice>
-<xsd:sequence>
 <xsd:element ref="AddressLines" />
 </xsd:sequence>
-<xsd:sequence>
 <xsd:element ref="StreetName" maxOccurs="unbounded" />
 <xsd:element ref="DependentStreet" minOccurs="0" />
-<xsd:choice>
 <xsd:element ref="Premise" />
 <xsd:element ref="Organisation" />
 <xsd:element ref="PostalCode" minOccurs="0" />
 </xsd:choice>
 </xsd:sequence>
 </xsd:choice>
 </xsd:complexType>
 </xsd:element>
<!-- 
############################################################################
 -->
-<xsd:element name="DependentStreet">
-<xsd:annotation>
 <xsd:documentation>DependentStreet is related to a street; occurs in GB, IE, ES, PT </xsd:documentation>
 </xsd:annotation>
-<xsd:complexType>
-<xsd:sequence>
 <xsd:element ref="StreetName" maxOccurs="unbounded" />
 </xsd:sequence>
 </xsd:complexType>
 </xsd:element>
<!-- 
############################################################################
 -->
<!-- 
############################################################################
 -->
-<xsd:element name="Premise">
-<xsd:annotation>
 <xsd:documentation xml:lang="en">Specification of a single premise, for example a house or a building. The premise as a whole has a unique premise (house) number or a premise name. If the premise is divided into sub-premises (e.g. apartments), then specify the sub-premise number with a SubPremise element. If a premise can only be identified by a premise name, because it has no premise (house) number, then specify that name in the element PremiseName (and not in the BuildingName). If a premise can be identified by a premise (house) number, but also has a house or building name, then do not store that name in the element PremiseName, but store it instead in the element BuildingName. The elements BuildingName and SecondaryStreetString all represent extra information that is nice to know, but is not a required part of a formal post address. </xsd:documentation>
 </xsd:annotation>
-<xsd:complexType>
-<xsd:choice>
 <xsd:element ref="AddressLines" />
-<xsd:sequence>
-<xsd:choice>
 <xsd:element ref="PremiseNumber" />
 <xsd:element ref="PremiseName" maxOccurs="unbounded" />
 </xsd:choice>
 <xsd:element ref="BuildingName" minOccurs="0" maxOccurs="unbounded" />
-<xsd:choice minOccurs="0">
 <xsd:element ref="SubPremise" />
 <xsd:element ref="Organisation" />
 </xsd:choice>
 <xsd:element ref="PostalCode" minOccurs="0" />
 </xsd:sequence>
 </xsd:choice>
 </xsd:complexType>
 </xsd:element>
<!-- 
############################################################################
 -->
-<xsd:element name="SubPremise">
-<xsd:annotation>
 <xsd:documentation xml:lang="en">Specification of a single sub-premise. Examples of sub-premises are apartments and suites. Each sub-premise should be uniquely identifiable. SubPremiseType: Specification of the name of a sub-premise type. Possible values not limited to: Suite, Appartment, Floor, Unknown. </xsd:documentation>
 </xsd:annotation>
-<xsd:complexType>
-<xsd:choice>
 <xsd:element ref="AddressLines" />
-<xsd:sequence>
-<xsd:choice>
 <xsd:element ref="SubPremiseNumber" />
 <xsd:element ref="SubPremiseName" maxOccurs="unbounded" />
 </xsd:choice>
 <xsd:element ref="BuildingName" minOccurs="0" maxOccurs="unbounded" />
 <xsd:element ref="Organisation" minOccurs="0" />
 <xsd:element ref="PostalCode" minOccurs="0" />
 </xsd:sequence>
 </xsd:choice>
-<xsd:attribute name="SubPremiseType" use="default" value="Unknown" type="xsd:string">
-<xsd:annotation>
 <xsd:documentation>SubPremiseType may be Apartment, Lot, etc.</xsd:documentation>
 </xsd:annotation>
 </xsd:attribute>
 </xsd:complexType>
 </xsd:element>
<!-- 
############################################################################
 -->
<!-- 
############################################################################
 -->
-<xsd:element name="PostalCodeNumber" type="xsd:string">
-<xsd:annotation>
 <xsd:documentation xml:lang="en">Specification of a postcode. The postcode is formatted according to country-specific rules. Example: SW3 0A8-1A </xsd:documentation>
 </xsd:annotation>
 </xsd:element>
<!-- 
############################################################################
 -->
-<xsd:element name="PostTown">
-<xsd:annotation>
 <xsd:documentation>Sub-element of the extended PostalCode, specification of a post town. A post town is not the same as a locality. A post town can encompass a collection of (small) localities. It can also be a subpart of a locality. An actual post town in Norway is "Bergen". </xsd:documentation>
 </xsd:annotation>
-<xsd:complexType>
-<xsd:sequence>
 <xsd:element ref="PostTownName" maxOccurs="unbounded" />
 </xsd:sequence>
 </xsd:complexType>
 </xsd:element>
<!-- 
############################################################################
 -->
-<xsd:element name="SortingCode" type="xsd:string">
-<xsd:annotation>
 <xsd:documentation>Values may for example be CEDEX 16 (France) </xsd:documentation>
 </xsd:annotation>
 </xsd:element>
<!-- 
############################################################################
 -->
-<xsd:element name="DeliveryPointSuffix" type="xsd:string">
-<xsd:annotation>
 <xsd:documentation>Examples are: 1234 (USA), 1G (UK), etc. </xsd:documentation>
 </xsd:annotation>
 </xsd:element>
<!-- 
############################################################################
 -->
-<xsd:element name="CountryName" type="TName">
-<xsd:annotation>
 <xsd:documentation xml:lang="en">Specification of the name of a country. Possible values of NameType not limited to: Official, Unique, Abbreviation, OldName, Synonym. </xsd:documentation>
 </xsd:annotation>
 </xsd:element>
<!-- 
############################################################################
 -->
-<xsd:element name="AdministrativeAreaName" type="TName">
-<xsd:annotation>
 <xsd:documentation xml:lang="en">Specification of the name of an administrative area. Examples of administrative areas are provinces counties, special regions (such as "Rijnmond"), etc. Possible values of NameType not limited to: Official, Unique, Abbreviation, OldName, Synonym. </xsd:documentation>
 </xsd:annotation>
 </xsd:element>
<!-- 
############################################################################
 -->
-<xsd:element name="SubAdministrativeAreaName" type="TName">
-<xsd:annotation>
 <xsd:documentation xml:lang="en">Specification of the sub-administrative area name. Examples are county (Ireland) and concelho (Portugal). Possible values of NameType not limited to: Official, Unique, Abbreviation, OldName, Synonym. </xsd:documentation>
 </xsd:annotation>
 </xsd:element>
<!-- 
############################################################################
 -->
-<xsd:element name="LocalityName" type="TName">
-<xsd:annotation>
 <xsd:documentation xml:lang="en">Specification of the name of a locality. Possible values of NameType not limited to: Official, Unique, Abbreviation, OldName, Synonym. </xsd:documentation>
 </xsd:annotation>
 </xsd:element>
<!-- 
############################################################################
 -->
<!-- 
############################################################################
 -->
<!-- 
############################################################################
 -->
-<xsd:element name="StreetName" type="TName">
-<xsd:annotation>
 <xsd:documentation>Specification of the name of a street (also dependant street name). Possible values of NameType not limited to: Official, Unique, Abbreviation, OldName, Synonym. </xsd:documentation>
 </xsd:annotation>
 </xsd:element>
<!-- 
############################################################################
 -->
<!-- 
############################################################################
 -->
-<xsd:element name="PostOfficeName" type="TName">
-<xsd:annotation>
 <xsd:documentation xml:lang="en">Specification of the name of the post office. This can be a rural postoffice where post is delivered or a post office containing post office boxes. Possible values of NameType not limited to: Official, Unique, Abbreviation, OldName, Synonym. </xsd:documentation>
 </xsd:annotation>
 </xsd:element>
<!-- 
############################################################################
 -->
-<xsd:element name="BuildingName" type="TName">
-<xsd:annotation>
 <xsd:documentation xml:lang="en">Specification of the name of a building. See also the specification of the SinglePremise element. Possible values of NameType not limited to: Official, Unique, Abbreviation, OldName, Synonym. </xsd:documentation>
 </xsd:annotation>
 </xsd:element>
<!-- 
############################################################################
 -->
-<xsd:element name="PremiseName" type="TName">
-<xsd:annotation>
 <xsd:documentation xml:lang="en">Specification of the name of the premise (house, building, etc). A premise name is specified when the premise cannot be addressed using a street name plus premise (house) number. Possible values of NameType not limited to: Official, Unique, Abbreviation, OldName, Synonym. </xsd:documentation>
 </xsd:annotation>
 </xsd:element>
<!-- 
############################################################################
 -->
-<xsd:element name="PremiseNumber" type="xsd:string">
-<xsd:annotation>
 <xsd:documentation xml:lang="en">Specification of the identifier of the premise (house, building, etc). Premises in a street are often uniquely identified by means of consecutive identifiers. The identifier can be a number, a letter or any combination of the two. This comment irrelevant: In the latter case, the identifier includes exactly one variable (range) part, which is either a number or a single letter that is surrounded by fixed parts at the left (prefix) or the right (postfix). </xsd:documentation>
 </xsd:annotation>
 </xsd:element>
<!-- 
############################################################################
 -->
-<xsd:element name="SubPremiseName" type="TName">
-<xsd:annotation>
 <xsd:documentation xml:lang="en"> Possible values of NameType not limited to: Official, Unique, Abbreviation, OldName, Synonym. </xsd:documentation>
 </xsd:annotation>
 </xsd:element>
<!-- 
############################################################################
 -->
-<xsd:element name="SubPremiseNumber" type="xsd:string">
-<xsd:annotation>
 <xsd:documentation xml:lang="en">Specification of the identifier of a sub-premise. Examples of sub-premises are apartments and suites. sub-premises in a building are often uniquely identified by means of consecutive identifiers. The identifier can be a number, a letter or any combination of the two. In the latter case, the identifier includes exactly one variable (range) part, which is either a number or a single letter that is surrounded by fixed parts at the left (prefix) or the right (postfix). </xsd:documentation>
 </xsd:annotation>
 </xsd:element>
<!-- 
############################################################################
 -->
-<xsd:element name="PostTownName" type="TName">
-<xsd:annotation>
 <xsd:documentation xml:lang="en">Specification of the name of a post town. A post town is not the same as a locality. A post town can encompass a collection of (small) localities. It can also be a subpart of a locality. Possible values of NameType not limited to: Official, Unique, Abbreviation, OldName, Synonym. </xsd:documentation>
 </xsd:annotation>
 </xsd:element>
<!-- 
############################################################################
 -->
-<xsd:element name="PostBoxNumber" type="xsd:string">
-<xsd:annotation>
 <xsd:documentation xml:lang="en">Specification of the number of a postbox . </xsd:documentation>
 </xsd:annotation>
 </xsd:element>
<!-- 
############################################################################
 -->
-<xsd:element name="LargeMailUserName" type="TName">
-<xsd:annotation>
 <xsd:documentation xml:lang="en">Specification of the name of a large mail user. Possible values of NameType not limited to: Official, Unique, Abbreviation, OldName, Synonym. </xsd:documentation>
 </xsd:annotation>
 </xsd:element>
<!-- 
############################################################################
 -->
-<xsd:element name="OrganisationName" type="TName">
-<xsd:annotation>
 <xsd:documentation xml:lang="en">Specification of the name of a firm. Examples of a firm are companies and organizations. Possible values of NameType not limited to: Official, Unique, Abbreviation, OldName, Synonym. </xsd:documentation>
 </xsd:annotation>
 </xsd:element>
<!-- 
############################################################################
 -->
-<xsd:element name="DepartmentName" type="TName">
-<xsd:annotation>
 <xsd:documentation xml:lang="en">Specification of the name of a department. Possible NameType values not limited to: Official, Unique, Abbreviation, OldName, Synonym. </xsd:documentation>
 </xsd:annotation>
 </xsd:element>
<!-- 
############################################################################
 -->
<!-- 
############################################################################
 -->
-<xsd:element name="CountryCode" type="TCode">
-<xsd:annotation>
 <xsd:documentation xml:lang="en">Country code scheme possible values, but not limited to: iso.3166-2, iso.3166-3 for two- and three-character country codes. </xsd:documentation>
 </xsd:annotation>
 </xsd:element>
<!-- 
############################################################################
 -->
<!-- 
### Simple Element Types                                                                                                                         ###
 -->
<!-- 
############################################################################
 -->
-<xsd:element name="LargeMailUserIdentifier" type="xsd:string">
-<xsd:annotation>
 <xsd:documentation xml:lang="en">Specification of the identification number of a large mail user. An example are the Cedex codes in France. </xsd:documentation>
 </xsd:annotation>
 </xsd:element>
-<xsd:element name="AddressLines">
-<xsd:annotation>
 <xsd:documentation>The order of the AddressLine elements must be preserved</xsd:documentation>
 </xsd:annotation>
-<xsd:complexType>
-<xsd:sequence>
 <xsd:element ref="AddressLine" maxOccurs="unbounded" />
 </xsd:sequence>
 </xsd:complexType>
 </xsd:element>
 <xsd:element name="AddressLine" type="xsd:string" />
-<xsd:element name="PostalCode">
-<xsd:annotation>
 <xsd:documentation>PostalCode is the container element for either simple or complex (extended) postal codes.</xsd:documentation>
 </xsd:annotation>
-<xsd:complexType>
-<xsd:choice>
 <xsd:element ref="AddressLines" />
-<xsd:sequence>
 <xsd:element ref="PostalCodeNumber" />
 <xsd:element ref="PostTown" minOccurs="0" />
 <xsd:element ref="SortingCode" minOccurs="0" />
 <xsd:element ref="DeliveryPointSuffix" minOccurs="0" />
 </xsd:sequence>
 </xsd:choice>
 </xsd:complexType>
 </xsd:element>
-<xsd:complexType name="TLocality">
-<xsd:choice>
-<xsd:sequence>
 <xsd:element ref="AddressLines" />
 </xsd:sequence>
-<xsd:sequence>
 <xsd:element ref="LocalityName" maxOccurs="unbounded" />
 <xsd:element ref="DependentLocality" minOccurs="0" />
-<xsd:choice minOccurs="0">
 <xsd:element ref="Street" />
 <xsd:element ref="PostBox" />
 <xsd:element ref="LargeMailUser" />
 <xsd:element ref="PostOffice" />
 <xsd:element ref="Premise" />
 <xsd:element ref="PostalCode" />
 </xsd:choice>
 </xsd:sequence>
 </xsd:choice>
-<xsd:attribute name="LocalityType" use="default" value="Unknown" type="xsd:string">
-<xsd:annotation>
 <xsd:documentation>City or IndustrialEstate or Unknown When in use for DependentLocality: PostalZone</xsd:documentation>
 </xsd:annotation>
 </xsd:attribute>
 </xsd:complexType>
-<xsd:complexType name="TPremise">
-<xsd:sequence>
-<xsd:choice>
 <xsd:element ref="PremiseNumber" />
 <xsd:element ref="PremiseName" maxOccurs="unbounded" />
 </xsd:choice>
 <xsd:element ref="BuildingName" minOccurs="0" maxOccurs="unbounded" />
-<xsd:choice minOccurs="0">
 <xsd:element ref="SubPremise" />
 <xsd:element ref="Organisation" />
 </xsd:choice>
 <xsd:element ref="PostalCode" minOccurs="0" />
 </xsd:sequence>
 </xsd:complexType>
-<xsd:simpleType name="DependentLocalityName">
 <xsd:restriction base="xsd:string" />
 </xsd:simpleType>
 <xsd:element name="DependentLocalityName" type="TName" />
 </xsd:schema>