diagram | |||
namespace | http://www.fixm.aero/ext/nas/4.3 | ||
children | nas:flightCoding nas:revision nas:routeAcknowledgement | ||
used by |
|
||
annotation |
|
||
source | <xs:complexType name="NasRouteApprovalStatusType"> <xs:annotation> <xs:documentation>Compound route approval information composed of the current flight coding (e.g., high priority) and revision information (whether acknowledged and current revision number, if any).</xs:documentation> </xs:annotation> <xs:sequence> <xs:element name="flightCoding" type="nas:NasFlightCodingType" nillable="true" minOccurs="0" maxOccurs="1"> <xs:annotation> <xs:documentation>Current flight coding; if this is anything other than NOT_READ then it takes display precendence over the route data. If it is NOT_READ, then the routeAcknowledgement and revision data controls the display.</xs:documentation> </xs:annotation> </xs:element> <xs:element name="revision" type="nas:NasRevisionInformationType" nillable="true" minOccurs="0" maxOccurs="1"> <xs:annotation> <xs:documentation>Current revision data (if any); not provided if flight has no revisions.</xs:documentation> </xs:annotation> </xs:element> <xs:element name="routeAcknowledgement" type="nas:NasRouteAcknowledgementType" nillable="true" minOccurs="0" maxOccurs="1"> <xs:annotation> <xs:documentation>Indicates whether or not a user has acknowledged the current routing revision (if no revision is provided, and this is set to ACKNOWLEDGED, then the flight is "cleared as filed").</xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:complexType> |
diagram | ||||||||||||||||||||||||
namespace | http://www.fixm.aero/ext/nas/4.3 | |||||||||||||||||||||||
type | nas:NasFlightCodingType | |||||||||||||||||||||||
properties |
|
|||||||||||||||||||||||
facets |
|
|||||||||||||||||||||||
annotation |
|
|||||||||||||||||||||||
source | <xs:element name="flightCoding" type="nas:NasFlightCodingType" nillable="true" minOccurs="0" maxOccurs="1"> <xs:annotation> <xs:documentation>Current flight coding; if this is anything other than NOT_READ then it takes display precendence over the route data. If it is NOT_READ, then the routeAcknowledgement and revision data controls the display.</xs:documentation> </xs:annotation> </xs:element> |
diagram | |||||||||
namespace | http://www.fixm.aero/ext/nas/4.3 | ||||||||
type | nas:NasRevisionInformationType | ||||||||
properties |
|
||||||||
children | nas:number nas:source | ||||||||
annotation |
|
||||||||
source | <xs:element name="revision" type="nas:NasRevisionInformationType" nillable="true" minOccurs="0" maxOccurs="1"> <xs:annotation> <xs:documentation>Current revision data (if any); not provided if flight has no revisions.</xs:documentation> </xs:annotation> </xs:element> |
diagram | ||||||||||||||
namespace | http://www.fixm.aero/ext/nas/4.3 | |||||||||||||
type | nas:NasRouteAcknowledgementType | |||||||||||||
properties |
|
|||||||||||||
facets |
|
|||||||||||||
annotation |
|
|||||||||||||
source | <xs:element name="routeAcknowledgement" type="nas:NasRouteAcknowledgementType" nillable="true" minOccurs="0" maxOccurs="1"> <xs:annotation> <xs:documentation>Indicates whether or not a user has acknowledged the current routing revision (if no revision is provided, and this is set to ACKNOWLEDGED, then the flight is "cleared as filed").</xs:documentation> </xs:annotation> </xs:element> |