simpleType NamespaceDomainType

namespace	http://www.fixm.aero/base/4.3
type	restriction of xs:string
properties	base  xs:string
used by	attribute  GloballyUniqueFlightIdentifierType/@namespaceDomain
facets	Kind  Value  Annotation enumeration  FULLY_QUALIFIED_DOMAIN_NAME documentation An organisation can be identified by its registered Fully Qualified Domain Name (FQDN). The domain name used should uniquely identify the organisation, and it could be from either the organisation's email or from the organisation's website. For example, for the website https://www.example.com/ and email person@example.com, the domain name used for the namespace would be "example.com". The namespace can also include subdomains as needed to ensure proper uniqueness and allow for the best implementation. This could be done by adding a numeric or regional subdomain. For example, "east.example.com" or "region1.example.com". enumeration  LOCATION_INDICATOR documentation An ATM unit can be identified by its corresponding four-letter Location Indicator (LOCID as determined in ICAO Doc. 7910). A LOCID is available for each FIR or ACC, as well as for airport locations that operators are tied into. For example, the ATM unit "Washington ATC Center", LOCID KZDC, might use the namespace "KZDC". enumeration  OPERATING_AGENCY_DESIGNATOR documentation An operating agency can be identified by its three-letter Operating Agency Designator (ICAO Doc. 8585).
annotation	documentation Identifies the particular type of namespace used by the originator of a GUFI.
source	<xs:simpleType name="NamespaceDomainType">   <xs:annotation>     <xs:documentation>Identifies the particular type of namespace used by the originator of a GUFI.</xs:documentation>   </xs:annotation>   <xs:restriction base="xs:string">     <xs:enumeration value="FULLY_QUALIFIED_DOMAIN_NAME">       <xs:annotation>         <xs:documentation>An organisation can be identified by its registered Fully Qualified Domain Name (FQDN). The domain name used should uniquely identify the organisation, and it could be from either the organisation's email or from the organisation's website. For example, for the website https://www.example.com/ and email person@example.com, the domain name used for the namespace would be "example.com". The namespace can also include subdomains as needed to ensure proper uniqueness and allow for the best implementation. This could be done by adding a numeric or regional subdomain. For example, "east.example.com" or "region1.example.com".</xs:documentation>       </xs:annotation>     </xs:enumeration>     <xs:enumeration value="LOCATION_INDICATOR">       <xs:annotation>         <xs:documentation>An ATM unit can be identified by its corresponding four-letter Location Indicator (LOCID as determined in ICAO Doc. 7910). A LOCID is available for each FIR or ACC, as well as for airport locations that operators are tied into. For example, the ATM unit "Washington ATC Center", LOCID KZDC, might use the namespace "KZDC".</xs:documentation>       </xs:annotation>     </xs:enumeration>     <xs:enumeration value="OPERATING_AGENCY_DESIGNATOR">       <xs:annotation>         <xs:documentation>An operating agency can be identified by its three-letter Operating Agency Designator (ICAO Doc. 8585).</xs:documentation>       </xs:annotation>     </xs:enumeration>   </xs:restriction> </xs:simpleType>

XML Schema documentation generated by XMLSpy Schema Editor http://www.altova.com/xmlspy