complexType PlanningStatusType

diagram
namespace	http://www.fixm.aero/app/ffice/1.0
children	ffice:explanation ffice:extension ffice:value
used by	element  FficeMessageType/planningStatus complexTypes  FficePS_PlanningStatusType FficeTRP_PlanningStatusType
annotation	documentation The Planning Status provides information concerning the status of the route and trajectory, as submitted.[adapted from ICAO Draft FF-ICE Implementation Guidance ]
source	<xs:complexType name="PlanningStatusType">   <xs:annotation>     <xs:documentation>The Planning Status provides information concerning the status of the route and trajectory, as submitted.[adapted from ICAO Draft FF-ICE Implementation Guidance ]</xs:documentation>   </xs:annotation>   <xs:sequence>     <xs:element name="explanation" type="fb:CharacterStringType" minOccurs="0" maxOccurs="2000">       <xs:annotation>         <xs:documentation>Textual explanation of the operational acceptability returned. [ICAO Draft FF-ICE Implementation Guidance]</xs:documentation>       </xs:annotation>     </xs:element>     <xs:element name="extension" type="ffice:PlanningStatusExtensionType" minOccurs="0" maxOccurs="2000">       <xs:annotation>         <xs:documentation>An extension hook for attaching extension (non-core) classes.</xs:documentation>       </xs:annotation>     </xs:element>     <xs:element name="value" type="ffice:PlanningStatusValueType" minOccurs="0" maxOccurs="1">       <xs:annotation>         <xs:documentation>The applicable planning status values (CONCUR, NON_CONCUR, NEGOTIATE) of the route and trajectory, as submitted. [FF-ICE]</xs:documentation>       </xs:annotation>     </xs:element>   </xs:sequence> </xs:complexType>

element PlanningStatusType/explanation

diagram
namespace	http://www.fixm.aero/app/ffice/1.0
type	fb:CharacterStringType
properties	minOcc  0 maxOcc  2000 content  simple
facets	Kind  Value  Annotation minLength  0 maxLength  4096
annotation	documentation Textual explanation of the operational acceptability returned. [ICAO Draft FF-ICE Implementation Guidance]
source	<xs:element name="explanation" type="fb:CharacterStringType" minOccurs="0" maxOccurs="2000">   <xs:annotation>     <xs:documentation>Textual explanation of the operational acceptability returned. [ICAO Draft FF-ICE Implementation Guidance]</xs:documentation>   </xs:annotation> </xs:element>

element PlanningStatusType/extension

diagram
namespace	http://www.fixm.aero/app/ffice/1.0
type	ffice:PlanningStatusExtensionType
properties	minOcc  0 maxOcc  2000 content  complex
annotation	documentation An extension hook for attaching extension (non-core) classes.
source	<xs:element name="extension" type="ffice:PlanningStatusExtensionType" minOccurs="0" maxOccurs="2000">   <xs:annotation>     <xs:documentation>An extension hook for attaching extension (non-core) classes.</xs:documentation>   </xs:annotation> </xs:element>

element PlanningStatusType/value

diagram
namespace	http://www.fixm.aero/app/ffice/1.0
type	ffice:PlanningStatusValueType
properties	minOcc  0 maxOcc  1 content  simple
facets	Kind  Value  Annotation enumeration  CONCUR documentation The flight plan and in particular the route and trajectory is acceptable without the need for modification.  This should mean that if the flight plan were to be filed, it would be accepted. [FF-ICE] enumeration  NON_CONCUR documentation The flight plan does not comply with published airspace/route availability or published restrictions and would result in a rejection or an unacceptable status if the flight plan were to be filed. [FF-ICE] enumeration  NEGOTIATE documentation The flight plan and in particular the route and trajectory is acceptable and would be accepted if filed. However the trajectory determined by the eASP has included additional constraints and/or has applied ATM configuration factors such as runway-in-use or Met data which may have resulted in a different trajectory. The operator is expected to assess the feedback and determine whether or not it wishes to amend it's Desired trajectory. [FF-ICE]
annotation	documentation The applicable planning status values (CONCUR, NON_CONCUR, NEGOTIATE) of the route and trajectory, as submitted. [FF-ICE]
source	<xs:element name="value" type="ffice:PlanningStatusValueType" minOccurs="0" maxOccurs="1">   <xs:annotation>     <xs:documentation>The applicable planning status values (CONCUR, NON_CONCUR, NEGOTIATE) of the route and trajectory, as submitted. [FF-ICE]</xs:documentation>   </xs:annotation> </xs:element>

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