complexType MessageType
diagram Nas_diagrams/Nas_p314.png
namespace http://www.fixm.aero/messaging/4.1
type extension of mesg:AbstractMessageType
properties
base mesg:AbstractMessageType
children fb:extension mesg:deliveryResponsibility mesg:extensions mesg:messageOriginator mesg:recipient mesg:uniqueMessageIdentifier mesg:flight mesg:flightPlanNegotiationStatus mesg:flightPlanVersion mesg:referenceMessage mesg:submissionStatus
used by
element Message
attributes
Name  Type  Use  Default  Fixed  Annotation
messageDateTime  fb:TimeType  optional      
documentation

                     The time and date that the communication was sent. [ICAO Draft FF-ICE Implementation
                     Guidance]
                     <deprecated>
<deletionVersion>Not specified yet.</deletionVersion>
<deprecationVersion>4.1.0</deprecationVersion>
<rationale>CR #28</rationale>
<replacement>N/A. See the FIXM Implementation guidance for recommendations about messages.</replacement>
</deprecated>
messageType  fb:CharacterStringType  optional      
documentation

                     Represents the type of FF-ICE message. [Appendix C, FF-ICE Messages, C-1 to C-13]
                    
                     <deprecated>
<deletionVersion>not specified yet</deletionVersion>
<deprecationVersion>4.1.0</deprecationVersion>
<rationale>CR #28</rationale>
<replacement>N/A. See the FIXM Implementation guidance for recommendations about messages.</replacement>
</deprecated>
annotation
documentation

            A communication sent from one location to another and comprising an integral number
            of fields. [ICAO Doc 9426]. The Message element is an entry point to the FIXM model.
           
            <deprecated>
<deletionVersion>Not specified yet.</deletionVersion>
<deprecationVersion>4.1.0</deprecationVersion>
<rationale>CR 28</rationale>
</deprecated>
source <complexType name="MessageType">
 
<annotation>
   
<documentation>
            A communication sent from one location to another and comprising an integral number
            of fields. [ICAO Doc 9426]. The Message element is an entry point to the FIXM model.
           
           
<deprecated>
       
<deletionVersion>Not specified yet.</deletionVersion>
       
<deprecationVersion>4.1.0</deprecationVersion>
       
<rationale>CR 28</rationale>
     
</deprecated>
   
</documentation>
 
</annotation>
 
<complexContent>
   
<extension base="mesg:AbstractMessageType">
     
<sequence>
       
<element name="flight" type="fx:FlightType" minOccurs="0" maxOccurs="1">
         
<annotation>
           
<documentation>
                        A flight associated with the message.
                    
</documentation>
         
</annotation>
       
</element>
       
<element name="flightPlanNegotiationStatus" type="mesg:FlightPlanNegotiationStatusType" minOccurs="0" maxOccurs="1">
         
<annotation>
           
<documentation>
                        The status of the flight plan, as perceived by each eASP and provided within the
                        Planning or Filing response, as applicable. [adapted from ICAO Draft FF-ICE Implementation
                        Guidance]
                       
<deprecated>
               
<deletionVersion>Not specified yet</deletionVersion>
               
<deprecationVersion>4.1.0</deprecationVersion>
               
<rationale>CR 28</rationale>
               
<replacement>N/A. See the FIXM Implementation guidance for recommendations about messages.</replacement>
             
</deprecated>
           
</documentation>
         
</annotation>
       
</element>
       
<element name="flightPlanVersion" type="mesg:FlightPlanVersionType" minOccurs="0" maxOccurs="1">
         
<annotation>
           
<documentation>
                        The flight plan version shall indicate uniquely the latest version of a flight plan.
                        Two different kinds of version can exist for a given flight plan: one from the AU
                        and one from the ASP. [adapted from ICAO Draft FF-ICE Implementation Guidance]
                       
<deprecated>
               
<deletionVersion>Not specified yet</deletionVersion>
               
<deprecationVersion>4.1.0</deprecationVersion>
               
<rationale>CR 28</rationale>
               
<replacement>N/A. See the FIXM Implementation guidance for recommendations about messages.</replacement>
             
</deprecated>
           
</documentation>
         
</annotation>
       
</element>
       
<element name="referenceMessage" type="mesg:FIXMUniqueMessageIdentifierType" minOccurs="0" maxOccurs="1">
         
<annotation>
           
<documentation>
                        The unique message identifier of the message being responded. [FIXM]
                       
<deprecated>
               
<deletionVersion>Not specified yet</deletionVersion>
               
<deprecationVersion>4.1.0</deprecationVersion>
               
<rationale>CR 28</rationale>
               
<replacement>N/A. See the FIXM Implementation guidance for recommendations about messages.</replacement>
             
</deprecated>
           
</documentation>
         
</annotation>
       
</element>
       
<element name="submissionStatus" type="mesg:SubmissionStatusType" minOccurs="0" maxOccurs="1">
         
<annotation>
           
<documentation>
                        A status indicating if a message could be processed and acted on. [adapted from ICAO
                        Draft FF-ICE Implementation Guidance]
                       
<deprecated>
               
<deletionVersion>Not specified yet</deletionVersion>
               
<deprecationVersion>4.1.0</deprecationVersion>
               
<rationale>CR 28</rationale>
               
<replacement>N/A. See the FIXM Implementation guidance for recommendations about messages.</replacement>
             
</deprecated>
           
</documentation>
         
</annotation>
       
</element>
     
</sequence>
   
</extension>
 
</complexContent>
</complexType>

element MessageType/flight
diagram Nas_diagrams/Nas_p315.png
namespace http://www.fixm.aero/messaging/4.1
type fx:FlightType
properties
minOcc 0
maxOcc 1
content complex
children fb:extension fx:agreed fx:aircraft fx:arrival fx:current fx:dangerousGoods fx:departure fx:desired fx:destination fx:emergency fx:enRoute fx:extensions fx:filed fx:flightIdentification fx:flightPlanOriginator fx:flightPlanSubmitter fx:gufi fx:gufiOriginator fx:negotiating fx:operator fx:radioCommunicationFailure fx:rankedTrajectories fx:specialHandling fx:supplementaryData
attributes
Name  Type  Use  Default  Fixed  Annotation
flightType  fx:TypeOfFlightType  optional      
documentation

                     Indication of the rule under which an air traffic controller provides categorical
                     handling of a flight. [FIXM]
                 
remarks  fb:CharacterStringType  optional      
documentation

                     Any other plain-language remarks when required by the appropriate ATS authority or
                     deemed necessary, by the pilot-in-command for the provision of air traffic services.
                    
                 
annotation
documentation

                        A flight associated with the message.
                    
source <element name="flight" type="fx:FlightType" minOccurs="0" maxOccurs="1">
 
<annotation>
   
<documentation>
                        A flight associated with the message.
                    
</documentation>
 
</annotation>
</element>

element MessageType/flightPlanNegotiationStatus
diagram Nas_diagrams/Nas_p316.png
namespace http://www.fixm.aero/messaging/4.1
type mesg:FlightPlanNegotiationStatusType
properties
minOcc 0
maxOcc 1
content complex
children fb:extension mesg:filingStatus mesg:planningStatus
annotation
documentation

                        The status of the flight plan, as perceived by each eASP and provided within the
                        Planning or Filing response, as applicable. [adapted from ICAO Draft FF-ICE Implementation
                        Guidance]
                        <deprecated>
<deletionVersion>Not specified yet</deletionVersion>
<deprecationVersion>4.1.0</deprecationVersion>
<rationale>CR 28</rationale>
<replacement>N/A. See the FIXM Implementation guidance for recommendations about messages.</replacement>
</deprecated>
source <element name="flightPlanNegotiationStatus" type="mesg:FlightPlanNegotiationStatusType" minOccurs="0" maxOccurs="1">
 
<annotation>
   
<documentation>
                        The status of the flight plan, as perceived by each eASP and provided within the
                        Planning or Filing response, as applicable. [adapted from ICAO Draft FF-ICE Implementation
                        Guidance]
                       
<deprecated>
       
<deletionVersion>Not specified yet</deletionVersion>
       
<deprecationVersion>4.1.0</deprecationVersion>
       
<rationale>CR 28</rationale>
       
<replacement>N/A. See the FIXM Implementation guidance for recommendations about messages.</replacement>
     
</deprecated>
   
</documentation>
 
</annotation>
</element>

element MessageType/flightPlanVersion
diagram Nas_diagrams/Nas_p317.png
namespace http://www.fixm.aero/messaging/4.1
type mesg:FlightPlanVersionType
properties
minOcc 0
maxOcc 1
content complex
children fb:extension mesg:referenceVersion mesg:version
annotation
documentation

                        The flight plan version shall indicate uniquely the latest version of a flight plan.
                        Two different kinds of version can exist for a given flight plan: one from the AU
                        and one from the ASP. [adapted from ICAO Draft FF-ICE Implementation Guidance]
                        <deprecated>
<deletionVersion>Not specified yet</deletionVersion>
<deprecationVersion>4.1.0</deprecationVersion>
<rationale>CR 28</rationale>
<replacement>N/A. See the FIXM Implementation guidance for recommendations about messages.</replacement>
</deprecated>
source <element name="flightPlanVersion" type="mesg:FlightPlanVersionType" minOccurs="0" maxOccurs="1">
 
<annotation>
   
<documentation>
                        The flight plan version shall indicate uniquely the latest version of a flight plan.
                        Two different kinds of version can exist for a given flight plan: one from the AU
                        and one from the ASP. [adapted from ICAO Draft FF-ICE Implementation Guidance]
                       
<deprecated>
       
<deletionVersion>Not specified yet</deletionVersion>
       
<deprecationVersion>4.1.0</deprecationVersion>
       
<rationale>CR 28</rationale>
       
<replacement>N/A. See the FIXM Implementation guidance for recommendations about messages.</replacement>
     
</deprecated>
   
</documentation>
 
</annotation>
</element>

element MessageType/referenceMessage
diagram Nas_diagrams/Nas_p318.png
namespace http://www.fixm.aero/messaging/4.1
type mesg:FIXMUniqueMessageIdentifierType
properties
minOcc 0
maxOcc 1
content complex
facets
Kind Value Annotation
minLength 0
maxLength 4096
pattern [0-9|aA-fF]{8}-[0-9|aA-fF]{4}-4[0-9|aA-fF]{3}-[89aAbB]{1}[0-9|aA-fF]{3}-[0-9|aA-fF]{12}
attributes
Name  Type  Use  Default  Fixed  Annotation
codeSpace  fb:CharacterStringType  required    urn:uuid  
documentation

                     Code Space of the FIXM Message Identifier
                     <deprecated>
<deletionVersion>not decided yet</deletionVersion>
<deprecationVersion>4.1.0</deprecationVersion>
<rationale>CR #28</rationale>
<replacement>N/A. See the FIXM Implementation guidance for recommendations about messages.</replacement>
</deprecated>
annotation
documentation

                        The unique message identifier of the message being responded. [FIXM]
                        <deprecated>
<deletionVersion>Not specified yet</deletionVersion>
<deprecationVersion>4.1.0</deprecationVersion>
<rationale>CR 28</rationale>
<replacement>N/A. See the FIXM Implementation guidance for recommendations about messages.</replacement>
</deprecated>
source <element name="referenceMessage" type="mesg:FIXMUniqueMessageIdentifierType" minOccurs="0" maxOccurs="1">
 
<annotation>
   
<documentation>
                        The unique message identifier of the message being responded. [FIXM]
                       
<deprecated>
       
<deletionVersion>Not specified yet</deletionVersion>
       
<deprecationVersion>4.1.0</deprecationVersion>
       
<rationale>CR 28</rationale>
       
<replacement>N/A. See the FIXM Implementation guidance for recommendations about messages.</replacement>
     
</deprecated>
   
</documentation>
 
</annotation>
</element>

element MessageType/submissionStatus
diagram Nas_diagrams/Nas_p319.png
namespace http://www.fixm.aero/messaging/4.1
type mesg:SubmissionStatusType
properties
minOcc 0
maxOcc 1
content complex
children fb:extension
attributes
Name  Type  Use  Default  Fixed  Annotation
status  mesg:SubmissionStatusValueType  optional      
documentation

                     Possible values of a submission status (Ack, Reject or Manual) [adapted from ICAO
                     Draft FF-ICE Implementation Guidance]
                     <deprecated>
<deletionVersion>Not specified yet</deletionVersion>
<deprecationVersion>4.1.0</deprecationVersion>
<rationale>CR 28</rationale>
<replacement>N/A. See the FIXM Implementation guidance for recommendations about messages.</replacement>
</deprecated>
statusReason  fb:CharacterStringType  optional      
documentation

                     A textual description of the reason a message was rejected. [ICAO Draft FF-ICE Implementation
                     Guidance]
                     <deprecated>
<deletionVersion>not decided yet</deletionVersion>
<deprecationVersion>4.1.0</deprecationVersion>
<rationale>CR #28</rationale>
<replacement>N/A. See the FIXM Implementation guidance for recommendations about messages.</replacement>
</deprecated>
annotation
documentation

                        A status indicating if a message could be processed and acted on. [adapted from ICAO
                        Draft FF-ICE Implementation Guidance]
                        <deprecated>
<deletionVersion>Not specified yet</deletionVersion>
<deprecationVersion>4.1.0</deprecationVersion>
<rationale>CR 28</rationale>
<replacement>N/A. See the FIXM Implementation guidance for recommendations about messages.</replacement>
</deprecated>
source <element name="submissionStatus" type="mesg:SubmissionStatusType" minOccurs="0" maxOccurs="1">
 
<annotation>
   
<documentation>
                        A status indicating if a message could be processed and acted on. [adapted from ICAO
                        Draft FF-ICE Implementation Guidance]
                       
<deprecated>
       
<deletionVersion>Not specified yet</deletionVersion>
       
<deprecationVersion>4.1.0</deprecationVersion>
       
<rationale>CR 28</rationale>
       
<replacement>N/A. See the FIXM Implementation guidance for recommendations about messages.</replacement>
     
</deprecated>
   
</documentation>
 
</annotation>
</element>


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