complexType FlightPlanNegotiationStatusType
diagram Nas_diagrams/Nas_p303.png
namespace http://www.fixm.aero/messaging/4.1
type extension of fb:ExtensibleType
properties
base fb:ExtensibleType
children fb:extension mesg:filingStatus mesg:planningStatus
used by
elements FlightPlanNegotiationStatus MessageType/flightPlanNegotiationStatus
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 spefied 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 <complexType name="FlightPlanNegotiationStatusType">
 
<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 spefied 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>
 
<complexContent>
   
<extension base="fb:ExtensibleType">
     
<sequence>
       
<element name="filingStatus" type="mesg:FilingStatusType" minOccurs="0" maxOccurs="1">
         
<annotation>
           
<documentation>
                        The Filing Status provides information concerning the status of the route and trajectory,
                        as submitted.[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="planningStatus" type="mesg:PlanningStatusType" minOccurs="0" maxOccurs="1">
         
<annotation>
           
<documentation>
                        The reference of the Flight Plan Version to which the response pertains.
                       
<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 FlightPlanNegotiationStatusType/filingStatus
diagram Nas_diagrams/Nas_p304.png
namespace http://www.fixm.aero/messaging/4.1
type mesg:FilingStatusType
properties
minOcc 0
maxOcc 1
content complex
children fb:extension
attributes
Name  Type  Use  Default  Fixed  Annotation
status  mesg:FilingStatusValueType  optional      
documentation

                     Possible values of an operational acceptability status (ACCEPTABLE, NON_ACCEPTABLE)
                     [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/>
annotation
documentation

                        The Filing Status provides information concerning the status of the route and trajectory,
                        as submitted.[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="filingStatus" type="mesg:FilingStatusType" minOccurs="0" maxOccurs="1">
 
<annotation>
   
<documentation>
                        The Filing Status provides information concerning the status of the route and trajectory,
                        as submitted.[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 FlightPlanNegotiationStatusType/planningStatus
diagram Nas_diagrams/Nas_p305.png
namespace http://www.fixm.aero/messaging/4.1
type mesg:PlanningStatusType
properties
minOcc 0
maxOcc 1
content complex
children fb:extension
attributes
Name  Type  Use  Default  Fixed  Annotation
status  mesg:PlanningStatusValueType  optional      
documentation

                     The Planning Status provides information concerning the status of the route and trajectory,
                     as submitted.[adapted from ICAO Draft FF-ICE Implementation Guidance ]
                     <deprecated>
<deletionVersion>Not specified yet</deletionVersion>
<deprecationVersion>4.1.0</deprecationVersion>
<replacemnet>N/A. See the FIXM Implementation guidance for recommendations about messages.</replacemnet>
<rationale>CR 28</rationale>
</deprecated>
statusReason  fb:CharacterStringType  optional      
documentation

                     Textual explanation of the operational acceptability returned. [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

                        The reference of the Flight Plan Version to which the response pertains.
                        <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="planningStatus" type="mesg:PlanningStatusType" minOccurs="0" maxOccurs="1">
 
<annotation>
   
<documentation>
                        The reference of the Flight Plan Version to which the response pertains.
                       
<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