complexType GloballyUniqueFlightIdentifierType
diagram FficeTemplates_diagrams/FficeTemplates_p1108.png
namespace http://www.fixm.aero/base/4.3
type extension of fb:UniversallyUniqueIdentifierType
properties
base fb:UniversallyUniqueIdentifierType
used by
elements FlightType/gufi FficeFFP_FlightType/gufi FficeFS_FlightType/gufi FficeFA_FlightType/gufi FficeFC_FlightType/gufi FficeFDRQ_FlightType/gufi FficeFDRP_FlightType/gufi FficeFD_FlightType/gufi FficeFPU_FlightType/gufi FficePS_FlightType/gufi FficePFP_FlightType/gufi FficeSR_FlightType/gufi FficeTRQ_FlightType/gufi FficeTRP_FlightType/gufi
facets
Kind Value Annotation
minLength 0
maxLength 4096
pattern [a-fA-F0-9]{8}-[a-fA-F0-9]{4}-4[a-fA-F0-9]{3}-[89abAB][a-fA-F0-9]{3}-[a-fA-F0-9]{12}
attributes
Name  Type  Use  Default  Fixed  Annotation
codeSpace  xs:string  required    urn:uuid  
documentation
Code Space of the UUID
creationTime  fb:DateTimeUtcType  required      
documentation
The time at which the GUFI was created.  Used to reduce the likelihood of GUFI collisions and ensure GUFIs remain perpetually unique.
namespaceDomain  fb:namespaceDomainType  required      
documentation
Identifies the particular type of namespace used by the originator of a GUFI.
namespaceIdentifier  fb:NamespaceIdentifierType  required      
documentation
The namespace chosen by the GUFI originator.  Used to reduce the likelihood of GUFI collisions and provide traceability as to which entity generated a particular GUFI.
annotation
documentation
An immutable identifier associated with a flight that allows all eligible members of the ATM community to unambiguously refer to information pertaining to the flight.
source <xs:complexType name="GloballyUniqueFlightIdentifierType">
 
<xs:annotation>
   
<xs:documentation>An immutable identifier associated with a flight that allows all eligible members of the ATM community to unambiguously refer to information pertaining to the flight.</xs:documentation>
 
</xs:annotation>
 
<xs:complexContent>
   
<xs:extension base="fb:UniversallyUniqueIdentifierType">
     
<xs:attribute name="creationTime" type="fb:DateTimeUtcType" use="required">
       
<xs:annotation>
         
<xs:documentation>The time at which the GUFI was created.  Used to reduce the likelihood of GUFI collisions and ensure GUFIs remain perpetually unique.</xs:documentation>
       
</xs:annotation>
     
</xs:attribute>
     
<xs:attribute name="namespaceDomain" type="fb:namespaceDomainType" use="required">
       
<xs:annotation>
         
<xs:documentation>Identifies the particular type of namespace used by the originator of a GUFI.</xs:documentation>
       
</xs:annotation>
     
</xs:attribute>
     
<xs:attribute name="namespaceIdentifier" type="fb:NamespaceIdentifierType" use="required">
       
<xs:annotation>
         
<xs:documentation>The namespace chosen by the GUFI originator.  Used to reduce the likelihood of GUFI collisions and provide traceability as to which entity generated a particular GUFI.</xs:documentation>
       
</xs:annotation>
     
</xs:attribute>
   
</xs:extension>
 
</xs:complexContent>
</xs:complexType>

attribute GloballyUniqueFlightIdentifierType/@creationTime
type fb:DateTimeUtcType
properties
use required
facets
Kind Value Annotation
pattern -?([1-9][0-9]{3,}|0[0-9]{3})-(0[1-9]|1[0-2])-(0[1-9]|[12][0-9]|3[01])T((([01][0-9]|2[0-3]):[0-5][0-9]:[0-5][0-9])|24:00:00)Z
annotation
documentation
The time at which the GUFI was created.  Used to reduce the likelihood of GUFI collisions and ensure GUFIs remain perpetually unique.
source <xs:attribute name="creationTime" type="fb:DateTimeUtcType" use="required">
 
<xs:annotation>
   
<xs:documentation>The time at which the GUFI was created.  Used to reduce the likelihood of GUFI collisions and ensure GUFIs remain perpetually unique.</xs:documentation>
 
</xs:annotation>
</xs:attribute>

attribute GloballyUniqueFlightIdentifierType/@namespaceDomain
type fb:namespaceDomainType
properties
use required
facets
Kind Value Annotation
enumeration AIRCRAFT_ADDRESS
documentation
A namespace can be derived from an aircraft's ICAO address. The 24-bit ICAO address information should be represented via six hexadecimal digits. For example: ABC123.
enumeration AIRCRAFT_REGISTRATION
documentation
An individual aircraft is to be identified by its aircraft registration. For example, the aircraft with registration N1234 might use a namespace of: N1234.
enumeration ATM_UNIT
documentation
An ATM unit is to 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, assuming just one system generates GUFIs, might use the following namespace "KZDC".
It does not seem likely that any ATM unit would have more than one source of GUFIs, but if that were the case a numeric station identifier can be added as well. Example: KZDC-2.
enumeration MAC_ADDRESS
documentation
A MAC address is a unique identifier assigned to a network interface controller (NIC) of the device by which the flight plan is submitted, formed according to the Institute of Electrical and Electronics Engineers (IEEE) Guidelines for 48-Bit Global Identifier (EUI-48).
If an originator generates GUFIs from several stations, it might be appropriate to use the MAC addresses of the devices submitting the flight plan information to properly distinguish the stations. The 48-bit MAC address should be represented via twelve hexadecimal digits. For example: ABCDEF123456.
Note: Use of the MAC address of the originating device will leak information about the hardware of the originating device (at least the manufacturer of the NIC and possibly the manufacturer and model of the device itself) outside the originator's organisation, and may thus increase security risk.
enumeration OPERATING_AGENCY
documentation
An operating agency is to be identified by its three letter Operating Agency Designator (ICAO Doc. 8585). A flight planning service provider's namespace content is composed of their Doc. 8585 designator. Example: ABC.
If the provider files from different locations, a four letter Location Indicator (LOCID as determined in ICAO Doc. 7910) can be used to indicate from which station the flight plan is filed. For example, operator ABC filing from Austin, Texas, U.S.A. (LOCID KAUS) might use: ABC-KAUS.
If an operating agency generates GUFIs from more than one station, a numeric station identifier can be added as well. Example: ABC-12 or ABC-KAUS-3.
enumeration PILOT
documentation
A pilot is identified by a pilot license number. For example: ABCD1234.
annotation
documentation
Identifies the particular type of namespace used by the originator of a GUFI.
source <xs:attribute name="namespaceDomain" type="fb:namespaceDomainType" use="required">
 
<xs:annotation>
   
<xs:documentation>Identifies the particular type of namespace used by the originator of a GUFI.</xs:documentation>
 
</xs:annotation>
</xs:attribute>

attribute GloballyUniqueFlightIdentifierType/@namespaceIdentifier
type fb:NamespaceIdentifierType
properties
use required
facets
Kind Value Annotation
minLength 0
maxLength 12
annotation
documentation
The namespace chosen by the GUFI originator.  Used to reduce the likelihood of GUFI collisions and provide traceability as to which entity generated a particular GUFI.
source <xs:attribute name="namespaceIdentifier" type="fb:NamespaceIdentifierType" use="required">
 
<xs:annotation>
   
<xs:documentation>The namespace chosen by the GUFI originator.  Used to reduce the likelihood of GUFI collisions and provide traceability as to which entity generated a particular GUFI.</xs:documentation>
 
</xs:annotation>
</xs:attribute>


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