Showing:

Annotations
Attributes
Diagrams
Facets
Instances
Properties
Source
Used by
Imported schema Messaging.xsd
Namespace http://www.fixm.aero/messaging/4.0
Annotations
Copyright (c) 2016 Airservices Australia, DSNA, EUROCONTROL, IATA, JCAB, NATS Limited, 
       NAV CANADA, SESAR Joint Undertaking & US FAA 
       =========================================== 
       All rights reserved. 
        
       Redistribution and use in source and binary forms, with or without modification, 
       are permitted provided that the following conditions are met: 
* Redistributions of source code must retain the above copyright notice, this list of conditions and the disclaimer.
* Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the disclaimer
  in the documentation and/or other materials provided with the distribution.
* Neither the names of Airservices Australia, DSNA, EUROCONTROL, IATA, JCAB, NATS Limited, NavCanada, SESAR Joint Undertaking
  & US FAA nor the names of their contributors may be used to endorse or promote products derived from this specification
  without specific prior written permission.
        
        
       DISCLAIMER 
        
       THIS SPECIFICATION IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" 
       AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 
       WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. 
       IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, 
       INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED 
       TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR 
       BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN 
       CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN 
       ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH 
       DAMAGE. 
        
       ========================================== 
       Editorial note: this license is an instance of the BSD license template as provided 
       by the Open Source Initiative: 
       http://www.opensource.org/licenses/bsd-license.php 
        
       The authoritative reference for FIXM is www.FIXM.aero. 
        
       Details on Airservices Australia: http://www.airservicesaustralia.com/ 
       Details on DSNA: http://www.developpement-durable.gouv.fr/-Navigation-aerienne-.html 
       
       Details on EUROCONTROL: http://www.eurocontrol.int/ 
       Details on IATA: http://www.iata.org/Pages/default.aspx 
       Details on JCAB: http://www.mlit.go.jp/en/koku/index.html 
       Details on NATS Limited: http://www.nats.co.uk/ 
       Details on NAV CANADA: http://www.navcanada.ca/ 
       Details on the SESAR JU and its members: http://www.sesarju.eu/discover-sesar/partnering-smarter-aviation/members 
       
       Details on the US FAA: http://www.faa.gov/
Defines elements needed to support messaging-related aspects required by the FF-ICE/1 
concept and guidance documents.
Properties
attribute form default: unqualified
element form default: qualified
version: 4.0.0
Element mesg:AbstractMessageType / mesg:extensions
Namespace http://www.fixm.aero/messaging/4.0
Annotations
Allow to add or redefine the Message elements and create regional scope extensions. 
This approach is not recommended, however as the preferred method is to extend individual 
classes and replace the core classes where appropriate as described in the FIXM Modeling 
Best Practices Guide. [FIXM]
Diagram
Diagram Extension_xsd.tmp#ExtensionType
Type fb:ExtensionType
Properties
content: complex
minOccurs: 0
maxOccurs: unbounded
Source
<element name="extensions" type="fb:ExtensionType" minOccurs="0" maxOccurs="unbounded">
  <annotation>
    <documentation>Allow to add or redefine the Message elements and create regional scope extensions. This approach is not recommended, however as the preferred method is to extend individual classes and replace the core classes where appropriate as described in the FIXM Modeling Best Practices Guide. [FIXM]</documentation>
  </annotation>
</element>
Element mesg:AbstractMessageType / mesg:messageDateTime
Namespace http://www.fixm.aero/messaging/4.0
Annotations
The time and date that the communication was sent. [ICAO Draft FF-ICE Implementation 
Guidance]
Diagram
Diagram Types_xsd.tmp#RestrictedTimeType Types_xsd.tmp#TimeType_timeReference Types_xsd.tmp#TimeType
Type fb:TimeType
Type hierarchy
Properties
content: complex
minOccurs: 0
maxOccurs: 1
Attributes
QName Type Fixed Default Use Annotation
timeReference string UTC required
Time reference specification.
Source
<element name="messageDateTime" type="fb:TimeType" minOccurs="0" maxOccurs="1">
  <annotation>
    <documentation>The time and date that the communication was sent. [ICAO Draft FF-ICE Implementation Guidance]</documentation>
  </annotation>
</element>
Element mesg:AbstractMessageType / mesg:messageOriginator
Namespace http://www.fixm.aero/messaging/4.0
Annotations
Sender of the message<sup>1</sup> [adapted from ICAO Draft FF-ICE Implementation 
Guidance]
Diagram
Diagram Organization_xsd.tmp#PersonOrOrganizationType_name Organization_xsd.tmp#PersonOrOrganizationType_participantType Organization_xsd.tmp#PersonOrOrganizationType_contact Organization_xsd.tmp#PersonOrOrganizationType
Type fb:PersonOrOrganizationType
Properties
content: complex
minOccurs: 0
maxOccurs: 1
Model fb:contact{0,1}
Children fb:contact
Instance
<mesg:messageOriginator name="" participantType="">
  <fb:contact name="" title="">{0,1}</fb:contact>
</mesg:messageOriginator>
Attributes
QName Type Fixed Default Use Annotation
name fb:TextNameType optional
The full official name of the Person, State, Organisation, Authority, aircraft operating 
agency, handling agency etc. [FIXM]
participantType fb:ParticipantTypeType optional
Type of participant, FF-ICE or NON_FF-ICE [FIXM]
Source
<element name="messageOriginator" type="fb:PersonOrOrganizationType" minOccurs="0" maxOccurs="1">
  <annotation>
    <documentation>Sender of the message<sup>1</sup> [adapted from ICAO Draft FF-ICE Implementation Guidance]</documentation>
  </annotation>
</element>
Element mesg:AbstractMessageType / mesg:recipient
Namespace http://www.fixm.aero/messaging/4.0
Annotations
The -one or more- intended recipients of the flight information. [adapted from ICAO 
Draft FF-ICE Implementation Guidance]
Diagram
Diagram Organization_xsd.tmp#PersonOrOrganizationType_name Organization_xsd.tmp#PersonOrOrganizationType_participantType Organization_xsd.tmp#PersonOrOrganizationType_contact Organization_xsd.tmp#PersonOrOrganizationType
Type fb:PersonOrOrganizationType
Properties
content: complex
minOccurs: 0
maxOccurs: 1
Model fb:contact{0,1}
Children fb:contact
Instance
<mesg:recipient name="" participantType="">
  <fb:contact name="" title="">{0,1}</fb:contact>
</mesg:recipient>
Attributes
QName Type Fixed Default Use Annotation
name fb:TextNameType optional
The full official name of the Person, State, Organisation, Authority, aircraft operating 
agency, handling agency etc. [FIXM]
participantType fb:ParticipantTypeType optional
Type of participant, FF-ICE or NON_FF-ICE [FIXM]
Source
<element name="recipient" type="fb:PersonOrOrganizationType" minOccurs="0" maxOccurs="1">
  <annotation>
    <documentation>The -one or more- intended recipients of the flight information. [adapted from ICAO Draft FF-ICE Implementation Guidance]</documentation>
  </annotation>
</element>
Element mesg:AbstractMessageType / mesg:recipientDeliveryResponsibility
Namespace http://www.fixm.aero/messaging/4.0
Annotations
The party responsible for ensuring everyone in the recipient list gets the flight 
data (either the filer or someone in the recipient list). [ICAO Draft FF-ICE Implementation 
Guidance]
Diagram
Diagram Organization_xsd.tmp#PersonOrOrganizationType_name Organization_xsd.tmp#PersonOrOrganizationType_participantType Organization_xsd.tmp#PersonOrOrganizationType_contact Organization_xsd.tmp#PersonOrOrganizationType
Type fb:PersonOrOrganizationType
Properties
content: complex
minOccurs: 0
maxOccurs: 1
Model fb:contact{0,1}
Children fb:contact
Instance
<mesg:recipientDeliveryResponsibility name="" participantType="">
  <fb:contact name="" title="">{0,1}</fb:contact>
</mesg:recipientDeliveryResponsibility>
Attributes
QName Type Fixed Default Use Annotation
name fb:TextNameType optional
The full official name of the Person, State, Organisation, Authority, aircraft operating 
agency, handling agency etc. [FIXM]
participantType fb:ParticipantTypeType optional
Type of participant, FF-ICE or NON_FF-ICE [FIXM]
Source
<element name="recipientDeliveryResponsibility" type="fb:PersonOrOrganizationType" minOccurs="0" maxOccurs="1">
  <annotation>
    <documentation>The party responsible for ensuring everyone in the recipient list gets the flight data (either the filer or someone in the recipient list). [ICAO Draft FF-ICE Implementation Guidance]</documentation>
  </annotation>
</element>
Element mesg:AbstractMessageType / mesg:uniqueMessageIdentifier
Namespace http://www.fixm.aero/messaging/4.0
Annotations
A unique message identifier for FIXM-based messages. [FIXM]
Diagram
Diagram Messaging_xsd.tmp#RestrictedFIXMUniqueMessageIdentifierType Messaging_xsd.tmp#FIXMUniqueMessageIdentifierType_codeSpace Messaging_xsd.tmp#FIXMUniqueMessageIdentifierType
Type mesg:FIXMUniqueMessageIdentifierType
Type hierarchy
Properties
content: complex
minOccurs: 0
maxOccurs: 1
Attributes
QName Type Fixed Default Use Annotation
codeSpace fb:CharacterStringType urn:uuid required
Code Space of the FIXM Message Identifier
Source
<element name="uniqueMessageIdentifier" type="mesg:FIXMUniqueMessageIdentifierType" minOccurs="0" maxOccurs="1">
  <annotation>
    <documentation>A unique message identifier for FIXM-based messages. [FIXM]</documentation>
  </annotation>
</element>
Element mesg:AbstractMessage
Namespace http://www.fixm.aero/messaging/4.0
Diagram
Diagram Messaging_xsd.tmp#AbstractMessageType_extensions Messaging_xsd.tmp#AbstractMessageType_messageDateTime Messaging_xsd.tmp#AbstractMessageType_messageOriginator Messaging_xsd.tmp#AbstractMessageType_recipient Messaging_xsd.tmp#AbstractMessageType_recipientDeliveryResponsibility Messaging_xsd.tmp#AbstractMessageType_uniqueMessageIdentifier Messaging_xsd.tmp#AbstractMessageType Messaging_xsd.tmp#Message Messaging_xsd.tmp#MessageCollection
Type mesg:AbstractMessageType
Properties
content: complex
Substitution Group
Model mesg:extensions* , mesg:messageDateTime{0,1} , mesg:messageOriginator{0,1} , mesg:recipient{0,1} , mesg:recipientDeliveryResponsibility{0,1} , mesg:uniqueMessageIdentifier{0,1}
Children mesg:extensions, mesg:messageDateTime, mesg:messageOriginator, mesg:recipient, mesg:recipientDeliveryResponsibility, mesg:uniqueMessageIdentifier
Instance
<mesg:AbstractMessage>
  <mesg:extensions>{0,unbounded}</mesg:extensions>
  <mesg:messageDateTime timeReference="UTC">{0,1}</mesg:messageDateTime>
  <mesg:messageOriginator name="" participantType="">{0,1}</mesg:messageOriginator>
  <mesg:recipient name="" participantType="">{0,1}</mesg:recipient>
  <mesg:recipientDeliveryResponsibility name="" participantType="">{0,1}</mesg:recipientDeliveryResponsibility>
  <mesg:uniqueMessageIdentifier codeSpace="urn:uuid">{0,1}</mesg:uniqueMessageIdentifier>
</mesg:AbstractMessage>
Source
<element name="AbstractMessage" type="mesg:AbstractMessageType"/>
Element mesg:FlightPlanNegotiationStatusType / mesg:operationalAcceptability
Namespace http://www.fixm.aero/messaging/4.0
Annotations
The Operational Acceptability provides information concerning the status of the route 
and trajectory, as submitted.[adapted from ICAO Draft FF-ICE Implementation Guidance 
]
Diagram
Diagram Messaging_xsd.tmp#OperationalAcceptabilityType_status Messaging_xsd.tmp#OperationalAcceptabilityType_statusReason Messaging_xsd.tmp#OperationalAcceptabilityType
Type mesg:OperationalAcceptabilityType
Properties
content: complex
minOccurs: 0
maxOccurs: 1
Attributes
QName Type Fixed Default Use Annotation
status mesg:OperationalAcceptabilityValueType optional
Possible values of a submission status (Ack, Reject or Manual) [adapted from ICAO 
Draft FF-ICE Implementation Guidance]
statusReason fb:CharacterStringType optional
A textual description of the reason a message was rejected. [ICAO Draft FF-ICE Implementation 
Guidance]
Source
<element name="operationalAcceptability" type="mesg:OperationalAcceptabilityType" minOccurs="0" maxOccurs="1">
  <annotation>
    <documentation>The Operational Acceptability provides information concerning the status of the route and trajectory, as submitted.[adapted from ICAO Draft FF-ICE Implementation Guidance ]</documentation>
  </annotation>
</element>
Element mesg:FlightPlanNegotiationStatusType / mesg:planningStatus
Namespace http://www.fixm.aero/messaging/4.0
Annotations
The reference of the Flight Plan Version to which the response pertains.
Diagram
Diagram Messaging_xsd.tmp#PlanningStatusType_status Messaging_xsd.tmp#PlanningStatusType_statusReason Messaging_xsd.tmp#PlanningStatusType
Type mesg:PlanningStatusType
Properties
content: complex
minOccurs: 0
maxOccurs: 1
Attributes
QName Type Fixed Default Use Annotation
status mesg:PlanningStatusValueType optional
The Planning Status provides information concerning the status of the route and trajectory, 
as submitted.[adapted from ICAO Draft FF-ICE Implementation Guidance ]
statusReason fb:CharacterStringType optional
Textual explanation of the operational acceptability returned. [ICAO Draft FF-ICE 
Implementation Guidance]
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.</documentation>
  </annotation>
</element>
Element mesg:FlightPlanNegotiationStatus
Namespace http://www.fixm.aero/messaging/4.0
Diagram
Diagram Messaging_xsd.tmp#FlightPlanNegotiationStatusType_operationalAcceptability Messaging_xsd.tmp#FlightPlanNegotiationStatusType_planningStatus Messaging_xsd.tmp#FlightPlanNegotiationStatusType
Type mesg:FlightPlanNegotiationStatusType
Properties
content: complex
Model mesg:operationalAcceptability{0,1} , mesg:planningStatus{0,1}
Children mesg:operationalAcceptability, mesg:planningStatus
Instance
<mesg:FlightPlanNegotiationStatus>
  <mesg:operationalAcceptability status="" statusReason="">{0,1}</mesg:operationalAcceptability>
  <mesg:planningStatus status="" statusReason="">{0,1}</mesg:planningStatus>
</mesg:FlightPlanNegotiationStatus>
Source
<element name="FlightPlanNegotiationStatus" type="mesg:FlightPlanNegotiationStatusType"/>
Element mesg:FlightPlanVersionType / mesg:referenceVersion
Namespace http://www.fixm.aero/messaging/4.0
Annotations
The reference of the Flight Plan Version to which the response pertains.
Diagram
Diagram Messaging_xsd.tmp#FlightPlanVersionTypeChoiceType_aspFlightPlanVersion Messaging_xsd.tmp#FlightPlanVersionTypeChoiceType_auFlightPlanVersion Messaging_xsd.tmp#FlightPlanVersionTypeChoiceType
Type mesg:FlightPlanVersionTypeChoiceType
Properties
content: complex
minOccurs: 0
maxOccurs: 1
Model mesg:aspFlightPlanVersion{0,1} | mesg:auFlightPlanVersion{0,1}
Children mesg:aspFlightPlanVersion, mesg:auFlightPlanVersion
Instance
<mesg:referenceVersion>
  <mesg:aspFlightPlanVersion>{0,1}</mesg:aspFlightPlanVersion>
  <mesg:auFlightPlanVersion>{0,1}</mesg:auFlightPlanVersion>
</mesg:referenceVersion>
Source
<element name="referenceVersion" type="mesg:FlightPlanVersionTypeChoiceType" minOccurs="0" maxOccurs="1">
  <annotation>
    <documentation>The reference of the Flight Plan Version to which the response pertains.</documentation>
  </annotation>
</element>
Element mesg:FlightPlanVersionTypeChoiceType / mesg:aspFlightPlanVersion
Namespace http://www.fixm.aero/messaging/4.0
Annotations
A unique identifier for the latest version of a flight plan as distributed by the 
sending ASP. A flight plan version should be operationally usable for verification 
that the pilot or operator and ATM personnel are using the same information for the 
flight. [adapted from ICAO Draft FF-ICE Implementation Guidance]
Diagram
Diagram Messaging_xsd.tmp#AspFlightPlanVersionTypeType
Type mesg:AspFlightPlanVersionTypeType
Type hierarchy
Properties
content: simple
minOccurs: 0
maxOccurs: 1
Facets
minLength 0
maxLength 4096
Source
<element name="aspFlightPlanVersion" type="mesg:AspFlightPlanVersionTypeType" minOccurs="0" maxOccurs="1">
  <annotation>
    <documentation>A unique identifier for the latest version of a flight plan as distributed by the sending ASP. A flight plan version should be operationally usable for verification that the pilot or operator and ATM personnel are using the same information for the flight. [adapted from ICAO Draft FF-ICE Implementation Guidance]</documentation>
  </annotation>
</element>
Element mesg:FlightPlanVersionTypeChoiceType / mesg:auFlightPlanVersion
Namespace http://www.fixm.aero/messaging/4.0
Annotations
A unique identifier for the latest version of a flight plan submitted by an Airspace 
User. A flight plan version should be operationally usable for verification that 
the pilot or operator and ATM personnel are using the same information for the flight. 
[adapted from ICAO Draft FF-ICE Implementation Guidance]
Diagram
Diagram Messaging_xsd.tmp#AuFlightPlanVersionTypeType
Type mesg:AuFlightPlanVersionTypeType
Type hierarchy
Properties
content: simple
minOccurs: 0
maxOccurs: 1
Facets
minLength 0
maxLength 4096
Source
<element name="auFlightPlanVersion" type="mesg:AuFlightPlanVersionTypeType" minOccurs="0" maxOccurs="1">
  <annotation>
    <documentation>A unique identifier for the latest version of a flight plan submitted by an Airspace User. A flight plan version should be operationally usable for verification that the pilot or operator and ATM personnel are using the same information for the flight. [adapted from ICAO Draft FF-ICE Implementation Guidance]</documentation>
  </annotation>
</element>
Element mesg:FlightPlanVersionType / mesg:version
Namespace http://www.fixm.aero/messaging/4.0
Annotations
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]
Diagram
Diagram Messaging_xsd.tmp#FlightPlanVersionTypeChoiceType_aspFlightPlanVersion Messaging_xsd.tmp#FlightPlanVersionTypeChoiceType_auFlightPlanVersion Messaging_xsd.tmp#FlightPlanVersionTypeChoiceType
Type mesg:FlightPlanVersionTypeChoiceType
Properties
content: complex
minOccurs: 0
maxOccurs: 1
Model mesg:aspFlightPlanVersion{0,1} | mesg:auFlightPlanVersion{0,1}
Children mesg:aspFlightPlanVersion, mesg:auFlightPlanVersion
Instance
<mesg:version>
  <mesg:aspFlightPlanVersion>{0,1}</mesg:aspFlightPlanVersion>
  <mesg:auFlightPlanVersion>{0,1}</mesg:auFlightPlanVersion>
</mesg:version>
Source
<element name="version" type="mesg:FlightPlanVersionTypeChoiceType" 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]</documentation>
  </annotation>
</element>
Element mesg:FlightPlanVersion
Namespace http://www.fixm.aero/messaging/4.0
Diagram
Diagram Messaging_xsd.tmp#FlightPlanVersionType_referenceVersion Messaging_xsd.tmp#FlightPlanVersionType_version Messaging_xsd.tmp#FlightPlanVersionType
Type mesg:FlightPlanVersionType
Properties
content: complex
Model mesg:referenceVersion{0,1} , mesg:version{0,1}
Children mesg:referenceVersion, mesg:version
Instance
<mesg:FlightPlanVersion>
  <mesg:referenceVersion>{0,1}</mesg:referenceVersion>
  <mesg:version>{0,1}</mesg:version>
</mesg:FlightPlanVersion>
Source
<element name="FlightPlanVersion" type="mesg:FlightPlanVersionType"/>
Element mesg:FlightPlanVersionTypeChoice
Namespace http://www.fixm.aero/messaging/4.0
Diagram
Diagram Messaging_xsd.tmp#FlightPlanVersionTypeChoiceType_aspFlightPlanVersion Messaging_xsd.tmp#FlightPlanVersionTypeChoiceType_auFlightPlanVersion Messaging_xsd.tmp#FlightPlanVersionTypeChoiceType
Type mesg:FlightPlanVersionTypeChoiceType
Properties
content: complex
Model mesg:aspFlightPlanVersion{0,1} | mesg:auFlightPlanVersion{0,1}
Children mesg:aspFlightPlanVersion, mesg:auFlightPlanVersion
Instance
<mesg:FlightPlanVersionTypeChoice>
  <mesg:aspFlightPlanVersion>{0,1}</mesg:aspFlightPlanVersion>
  <mesg:auFlightPlanVersion>{0,1}</mesg:auFlightPlanVersion>
</mesg:FlightPlanVersionTypeChoice>
Source
<element name="FlightPlanVersionTypeChoice" type="mesg:FlightPlanVersionTypeChoiceType"/>
Element mesg:MessageType / mesg:flight
Namespace http://www.fixm.aero/messaging/4.0
Annotations
A flight associated with the message.
Diagram
Diagram FlightData_xsd.tmp#FlightType_flightType FlightData_xsd.tmp#FlightType_remarks FlightData_xsd.tmp#FlightType_agreed FlightData_xsd.tmp#FlightType_aircraft FlightData_xsd.tmp#FlightType_arrival FlightData_xsd.tmp#FlightType_current FlightData_xsd.tmp#FlightType_dangerousGoods FlightData_xsd.tmp#FlightType_departure FlightData_xsd.tmp#FlightType_desired FlightData_xsd.tmp#FlightType_destination FlightData_xsd.tmp#FlightType_emergency FlightData_xsd.tmp#FlightType_enRoute FlightData_xsd.tmp#FlightType_extensions FlightData_xsd.tmp#FlightType_filed FlightData_xsd.tmp#FlightType_flightIdentification FlightData_xsd.tmp#FlightType_flightPlanOriginator FlightData_xsd.tmp#FlightType_flightPlanSubmitter FlightData_xsd.tmp#FlightType_gufi FlightData_xsd.tmp#FlightType_negotiating FlightData_xsd.tmp#FlightType_operator FlightData_xsd.tmp#FlightType_radioCommunicationFailure FlightData_xsd.tmp#FlightType_rankedTrajectories FlightData_xsd.tmp#FlightType_specialHandling FlightData_xsd.tmp#FlightType_supplementaryData FlightData_xsd.tmp#FlightType
Type fx:FlightType
Properties
content: complex
minOccurs: 0
maxOccurs: 1
Model fx:agreed{0,1} , fx:aircraft{0,1} , fx:arrival{0,1} , fx:current{0,1} , fx:dangerousGoods* , fx:departure{0,1} , fx:desired{0,1} , fx:destination{0,1} , fx:emergency{0,1} , fx:enRoute{0,1} , fx:extensions* , fx:filed{0,1} , fx:flightIdentification{0,1} , fx:flightPlanOriginator{0,1} , fx:flightPlanSubmitter{0,1} , fx:gufi{0,1} , fx:negotiating{0,1} , fx:operator{0,1} , fx:radioCommunicationFailure{0,1} , fx:rankedTrajectories* , fx:specialHandling{0,1} , fx:supplementaryData{0,1}
Children 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:negotiating, fx:operator, fx:radioCommunicationFailure, fx:rankedTrajectories, fx:specialHandling, fx:supplementaryData
Instance
<mesg:flight flightType="" remarks="">
  <fx:agreed>{0,1}</fx:agreed>
  <fx:aircraft aircraftAddress="" aircraftApproachCategory="" numberOfAircraft="" registration="" significantMarkings="" wakeTurbulence="">{0,1}</fx:aircraft>
  <fx:arrival runwayDirection="">{0,1}</fx:arrival>
  <fx:current>{0,1}</fx:current>
  <fx:dangerousGoods aircraftLimitation="" guidebookNumber="" onboardLocation="" shipment="">{0,unbounded}</fx:dangerousGoods>
  <fx:departure runwayDirection="">{0,1}</fx:departure>
  <fx:desired identifier="">{0,1}</fx:desired>
  <fx:destination runwayDirection="">{0,1}</fx:destination>
  <fx:emergency actionTaken="" emergencyDescription="" otherInformation="" phase="">{0,1}</fx:emergency>
  <fx:enRoute>{0,1}</fx:enRoute>
  <fx:extensions>{0,unbounded}</fx:extensions>
  <fx:filed>{0,1}</fx:filed>
  <fx:flightIdentification aircraftIdentification="">{0,1}</fx:flightIdentification>
  <fx:flightPlanOriginator name="" participantType="">{0,1}</fx:flightPlanOriginator>
  <fx:flightPlanSubmitter name="" participantType="">{0,1}</fx:flightPlanSubmitter>
  <fx:gufi codeSpace="urn:uuid">{0,1}</fx:gufi>
  <fx:negotiating>{0,1}</fx:negotiating>
  <fx:operator designatorIcao="">{0,1}</fx:operator>
  <fx:radioCommunicationFailure radioFailureRemarks="" remainingComCapability="">{0,1}</fx:radioCommunicationFailure>
  <fx:rankedTrajectories identifier="">{0,unbounded}</fx:rankedTrajectories>
  <fx:specialHandling>{0,1}</fx:specialHandling>
  <fx:supplementaryData fuelEndurance="" personsOnBoard="">{0,1}</fx:supplementaryData>
</mesg:flight>
Attributes
QName Type Fixed Default Use Annotation
flightType fx:TypeOfFlightType optional
Indication of the rule under which an air traffic controller provides categorical 
handling of a flight. [FIXM]
remarks fb:CharacterStringType optional
Plain language remarks providing additional information about the flight (e.g., requested 
flight level changes after takeoff).
Source
<element name="flight" type="fx:FlightType" minOccurs="0" maxOccurs="1">
  <annotation>
    <documentation>A flight associated with the message.</documentation>
  </annotation>
</element>
Element mesg:MessageType / mesg:flightPlanNegotiationStatus
Namespace http://www.fixm.aero/messaging/4.0
Annotations
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]
Diagram
Diagram Messaging_xsd.tmp#FlightPlanNegotiationStatusType_operationalAcceptability Messaging_xsd.tmp#FlightPlanNegotiationStatusType_planningStatus Messaging_xsd.tmp#FlightPlanNegotiationStatusType
Type mesg:FlightPlanNegotiationStatusType
Properties
content: complex
minOccurs: 0
maxOccurs: 1
Model mesg:operationalAcceptability{0,1} , mesg:planningStatus{0,1}
Children mesg:operationalAcceptability, mesg:planningStatus
Instance
<mesg:flightPlanNegotiationStatus>
  <mesg:operationalAcceptability status="" statusReason="">{0,1}</mesg:operationalAcceptability>
  <mesg:planningStatus status="" statusReason="">{0,1}</mesg:planningStatus>
</mesg:flightPlanNegotiationStatus>
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]</documentation>
  </annotation>
</element>
Element mesg:MessageType / mesg:flightPlanVersion
Namespace http://www.fixm.aero/messaging/4.0
Annotations
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]
Diagram
Diagram Messaging_xsd.tmp#FlightPlanVersionType_referenceVersion Messaging_xsd.tmp#FlightPlanVersionType_version Messaging_xsd.tmp#FlightPlanVersionType
Type mesg:FlightPlanVersionType
Properties
content: complex
minOccurs: 0
maxOccurs: 1
Model mesg:referenceVersion{0,1} , mesg:version{0,1}
Children mesg:referenceVersion, mesg:version
Instance
<mesg:flightPlanVersion>
  <mesg:referenceVersion>{0,1}</mesg:referenceVersion>
  <mesg:version>{0,1}</mesg:version>
</mesg:flightPlanVersion>
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]</documentation>
  </annotation>
</element>
Element mesg:MessageType / mesg:referenceMessage
Namespace http://www.fixm.aero/messaging/4.0
Annotations
The unique message identifier of the message being responded. [FIXM]
Diagram
Diagram Messaging_xsd.tmp#RestrictedFIXMUniqueMessageIdentifierType Messaging_xsd.tmp#FIXMUniqueMessageIdentifierType_codeSpace Messaging_xsd.tmp#FIXMUniqueMessageIdentifierType
Type mesg:FIXMUniqueMessageIdentifierType
Type hierarchy
Properties
content: complex
minOccurs: 0
maxOccurs: 1
Attributes
QName Type Fixed Default Use Annotation
codeSpace fb:CharacterStringType urn:uuid required
Code Space of the FIXM Message Identifier
Source
<element name="referenceMessage" type="mesg:FIXMUniqueMessageIdentifierType" minOccurs="0" maxOccurs="1">
  <annotation>
    <documentation>The unique message identifier of the message being responded. [FIXM]</documentation>
  </annotation>
</element>
Element mesg:MessageType / mesg:submissionStatus
Namespace http://www.fixm.aero/messaging/4.0
Annotations
A status indicating if a message could be processed and acted on. [adapted from ICAO 
Draft FF-ICE Implementation Guidance]
Diagram
Diagram Messaging_xsd.tmp#SubmissionStatusType_status Messaging_xsd.tmp#SubmissionStatusType_statusReason Messaging_xsd.tmp#SubmissionStatusType
Type mesg:SubmissionStatusType
Properties
content: complex
minOccurs: 0
maxOccurs: 1
Attributes
QName Type Fixed Default Use Annotation
status mesg:SubmissionStatusValueType optional
Possible values of a submission status (Ack, Reject or Manual) [adapted from ICAO 
Draft FF-ICE Implementation Guidance]
statusReason fb:CharacterStringType optional
A textual description of the reason a message was rejected. [ICAO Draft FF-ICE Implementation 
Guidance]
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]</documentation>
  </annotation>
</element>
Element mesg:Message
Namespace http://www.fixm.aero/messaging/4.0
Diagram
Diagram Messaging_xsd.tmp#AbstractMessageType_extensions Messaging_xsd.tmp#AbstractMessageType_messageDateTime Messaging_xsd.tmp#AbstractMessageType_messageOriginator Messaging_xsd.tmp#AbstractMessageType_recipient Messaging_xsd.tmp#AbstractMessageType_recipientDeliveryResponsibility Messaging_xsd.tmp#AbstractMessageType_uniqueMessageIdentifier Messaging_xsd.tmp#AbstractMessageType Messaging_xsd.tmp#MessageType_flight Messaging_xsd.tmp#MessageType_flightPlanNegotiationStatus Messaging_xsd.tmp#MessageType_flightPlanVersion Messaging_xsd.tmp#MessageType_referenceMessage Messaging_xsd.tmp#MessageType_submissionStatus Messaging_xsd.tmp#MessageType Messaging_xsd.tmp#AbstractMessage
Type mesg:MessageType
Type hierarchy
Properties
content: complex
Substitution Group Affiliation
Model mesg:extensions* , mesg:messageDateTime{0,1} , mesg:messageOriginator{0,1} , mesg:recipient{0,1} , mesg:recipientDeliveryResponsibility{0,1} , mesg:uniqueMessageIdentifier{0,1} , mesg:flight{0,1} , mesg:flightPlanNegotiationStatus{0,1} , mesg:flightPlanVersion{0,1} , mesg:referenceMessage{0,1} , mesg:submissionStatus{0,1}
Children mesg:extensions, mesg:flight, mesg:flightPlanNegotiationStatus, mesg:flightPlanVersion, mesg:messageDateTime, mesg:messageOriginator, mesg:recipient, mesg:recipientDeliveryResponsibility, mesg:referenceMessage, mesg:submissionStatus, mesg:uniqueMessageIdentifier
Instance
<mesg:Message>
  <mesg:extensions>{0,unbounded}</mesg:extensions>
  <mesg:messageDateTime timeReference="UTC">{0,1}</mesg:messageDateTime>
  <mesg:messageOriginator name="" participantType="">{0,1}</mesg:messageOriginator>
  <mesg:recipient name="" participantType="">{0,1}</mesg:recipient>
  <mesg:recipientDeliveryResponsibility name="" participantType="">{0,1}</mesg:recipientDeliveryResponsibility>
  <mesg:uniqueMessageIdentifier codeSpace="urn:uuid">{0,1}</mesg:uniqueMessageIdentifier>
  <mesg:flight flightType="" remarks="">{0,1}</mesg:flight>
  <mesg:flightPlanNegotiationStatus>{0,1}</mesg:flightPlanNegotiationStatus>
  <mesg:flightPlanVersion>{0,1}</mesg:flightPlanVersion>
  <mesg:referenceMessage codeSpace="urn:uuid">{0,1}</mesg:referenceMessage>
  <mesg:submissionStatus status="" statusReason="">{0,1}</mesg:submissionStatus>
</mesg:Message>
Source
<element name="Message" type="mesg:MessageType" substitutionGroup="mesg:AbstractMessage"/>
Element mesg:MessageCollectionType / mesg:message
Namespace http://www.fixm.aero/messaging/4.0
Annotations
Each of the messages grouped in a Message Collection [FIXM]
Diagram
Diagram Messaging_xsd.tmp#AbstractMessageType_extensions Messaging_xsd.tmp#AbstractMessageType_messageDateTime Messaging_xsd.tmp#AbstractMessageType_messageOriginator Messaging_xsd.tmp#AbstractMessageType_recipient Messaging_xsd.tmp#AbstractMessageType_recipientDeliveryResponsibility Messaging_xsd.tmp#AbstractMessageType_uniqueMessageIdentifier Messaging_xsd.tmp#AbstractMessageType
Type mesg:AbstractMessageType
Properties
content: complex
minOccurs: 0
maxOccurs: unbounded
Model mesg:extensions* , mesg:messageDateTime{0,1} , mesg:messageOriginator{0,1} , mesg:recipient{0,1} , mesg:recipientDeliveryResponsibility{0,1} , mesg:uniqueMessageIdentifier{0,1}
Children mesg:extensions, mesg:messageDateTime, mesg:messageOriginator, mesg:recipient, mesg:recipientDeliveryResponsibility, mesg:uniqueMessageIdentifier
Instance
<mesg:message>
  <mesg:extensions>{0,unbounded}</mesg:extensions>
  <mesg:messageDateTime timeReference="UTC">{0,1}</mesg:messageDateTime>
  <mesg:messageOriginator name="" participantType="">{0,1}</mesg:messageOriginator>
  <mesg:recipient name="" participantType="">{0,1}</mesg:recipient>
  <mesg:recipientDeliveryResponsibility name="" participantType="">{0,1}</mesg:recipientDeliveryResponsibility>
  <mesg:uniqueMessageIdentifier codeSpace="urn:uuid">{0,1}</mesg:uniqueMessageIdentifier>
</mesg:message>
Source
<element name="message" type="mesg:AbstractMessageType" minOccurs="0" maxOccurs="unbounded">
  <annotation>
    <documentation>Each of the messages grouped in a Message Collection [FIXM]</documentation>
  </annotation>
</element>
Element mesg:MessageCollection
Namespace http://www.fixm.aero/messaging/4.0
Diagram
Diagram Messaging_xsd.tmp#AbstractMessageType_extensions Messaging_xsd.tmp#AbstractMessageType_messageDateTime Messaging_xsd.tmp#AbstractMessageType_messageOriginator Messaging_xsd.tmp#AbstractMessageType_recipient Messaging_xsd.tmp#AbstractMessageType_recipientDeliveryResponsibility Messaging_xsd.tmp#AbstractMessageType_uniqueMessageIdentifier Messaging_xsd.tmp#AbstractMessageType Messaging_xsd.tmp#MessageCollectionType_message Messaging_xsd.tmp#MessageCollectionType Messaging_xsd.tmp#AbstractMessage
Type mesg:MessageCollectionType
Type hierarchy
Properties
content: complex
Substitution Group Affiliation
Model mesg:extensions* , mesg:messageDateTime{0,1} , mesg:messageOriginator{0,1} , mesg:recipient{0,1} , mesg:recipientDeliveryResponsibility{0,1} , mesg:uniqueMessageIdentifier{0,1} , mesg:message*
Children mesg:extensions, mesg:message, mesg:messageDateTime, mesg:messageOriginator, mesg:recipient, mesg:recipientDeliveryResponsibility, mesg:uniqueMessageIdentifier
Instance
<mesg:MessageCollection>
  <mesg:extensions>{0,unbounded}</mesg:extensions>
  <mesg:messageDateTime timeReference="UTC">{0,1}</mesg:messageDateTime>
  <mesg:messageOriginator name="" participantType="">{0,1}</mesg:messageOriginator>
  <mesg:recipient name="" participantType="">{0,1}</mesg:recipient>
  <mesg:recipientDeliveryResponsibility name="" participantType="">{0,1}</mesg:recipientDeliveryResponsibility>
  <mesg:uniqueMessageIdentifier codeSpace="urn:uuid">{0,1}</mesg:uniqueMessageIdentifier>
  <mesg:message>{0,unbounded}</mesg:message>
</mesg:MessageCollection>
Source
<element name="MessageCollection" type="mesg:MessageCollectionType" substitutionGroup="mesg:AbstractMessage"/>
Element mesg:OperationalAcceptability
Namespace http://www.fixm.aero/messaging/4.0
Diagram
Diagram Messaging_xsd.tmp#OperationalAcceptabilityType_status Messaging_xsd.tmp#OperationalAcceptabilityType_statusReason Messaging_xsd.tmp#OperationalAcceptabilityType
Type mesg:OperationalAcceptabilityType
Properties
content: complex
Attributes
QName Type Fixed Default Use Annotation
status mesg:OperationalAcceptabilityValueType optional
Possible values of a submission status (Ack, Reject or Manual) [adapted from ICAO 
Draft FF-ICE Implementation Guidance]
statusReason fb:CharacterStringType optional
A textual description of the reason a message was rejected. [ICAO Draft FF-ICE Implementation 
Guidance]
Source
<element name="OperationalAcceptability" type="mesg:OperationalAcceptabilityType"/>
Element mesg:PlanningStatus
Namespace http://www.fixm.aero/messaging/4.0
Diagram
Diagram Messaging_xsd.tmp#PlanningStatusType_status Messaging_xsd.tmp#PlanningStatusType_statusReason Messaging_xsd.tmp#PlanningStatusType
Type mesg:PlanningStatusType
Properties
content: complex
Attributes
QName Type Fixed Default Use Annotation
status mesg:PlanningStatusValueType optional
The Planning Status provides information concerning the status of the route and trajectory, 
as submitted.[adapted from ICAO Draft FF-ICE Implementation Guidance ]
statusReason fb:CharacterStringType optional
Textual explanation of the operational acceptability returned. [ICAO Draft FF-ICE 
Implementation Guidance]
Source
<element name="PlanningStatus" type="mesg:PlanningStatusType"/>
Element mesg:SubmissionStatus
Namespace http://www.fixm.aero/messaging/4.0
Diagram
Diagram Messaging_xsd.tmp#SubmissionStatusType_status Messaging_xsd.tmp#SubmissionStatusType_statusReason Messaging_xsd.tmp#SubmissionStatusType
Type mesg:SubmissionStatusType
Properties
content: complex
Attributes
QName Type Fixed Default Use Annotation
status mesg:SubmissionStatusValueType optional
Possible values of a submission status (Ack, Reject or Manual) [adapted from ICAO 
Draft FF-ICE Implementation Guidance]
statusReason fb:CharacterStringType optional
A textual description of the reason a message was rejected. [ICAO Draft FF-ICE Implementation 
Guidance]
Source
<element name="SubmissionStatus" type="mesg:SubmissionStatusType"/>
Complex Type mesg:AbstractMessageType
Namespace http://www.fixm.aero/messaging/4.0
Annotations
An abstract class that specializes into Message or Message Collection and holds their 
common properties. [FIXM]
Diagram
Diagram Messaging_xsd.tmp#AbstractMessageType_extensions Messaging_xsd.tmp#AbstractMessageType_messageDateTime Messaging_xsd.tmp#AbstractMessageType_messageOriginator Messaging_xsd.tmp#AbstractMessageType_recipient Messaging_xsd.tmp#AbstractMessageType_recipientDeliveryResponsibility Messaging_xsd.tmp#AbstractMessageType_uniqueMessageIdentifier
Properties
abstract: true
Used by
Model mesg:extensions* , mesg:messageDateTime{0,1} , mesg:messageOriginator{0,1} , mesg:recipient{0,1} , mesg:recipientDeliveryResponsibility{0,1} , mesg:uniqueMessageIdentifier{0,1}
Children mesg:extensions, mesg:messageDateTime, mesg:messageOriginator, mesg:recipient, mesg:recipientDeliveryResponsibility, mesg:uniqueMessageIdentifier
Source
<complexType abstract="true" name="AbstractMessageType">
  <annotation>
    <documentation>An abstract class that specializes into Message or Message Collection and holds their common properties. [FIXM]</documentation>
  </annotation>
  <sequence>
    <element name="extensions" type="fb:ExtensionType" minOccurs="0" maxOccurs="unbounded">
      <annotation>
        <documentation>Allow to add or redefine the Message elements and create regional scope extensions. This approach is not recommended, however as the preferred method is to extend individual classes and replace the core classes where appropriate as described in the FIXM Modeling Best Practices Guide. [FIXM]</documentation>
      </annotation>
    </element>
    <element name="messageDateTime" type="fb:TimeType" minOccurs="0" maxOccurs="1">
      <annotation>
        <documentation>The time and date that the communication was sent. [ICAO Draft FF-ICE Implementation Guidance]</documentation>
      </annotation>
    </element>
    <element name="messageOriginator" type="fb:PersonOrOrganizationType" minOccurs="0" maxOccurs="1">
      <annotation>
        <documentation>Sender of the message<sup>1</sup> [adapted from ICAO Draft FF-ICE Implementation Guidance]</documentation>
      </annotation>
    </element>
    <element name="recipient" type="fb:PersonOrOrganizationType" minOccurs="0" maxOccurs="1">
      <annotation>
        <documentation>The -one or more- intended recipients of the flight information. [adapted from ICAO Draft FF-ICE Implementation Guidance]</documentation>
      </annotation>
    </element>
    <element name="recipientDeliveryResponsibility" type="fb:PersonOrOrganizationType" minOccurs="0" maxOccurs="1">
      <annotation>
        <documentation>The party responsible for ensuring everyone in the recipient list gets the flight data (either the filer or someone in the recipient list). [ICAO Draft FF-ICE Implementation Guidance]</documentation>
      </annotation>
    </element>
    <element name="uniqueMessageIdentifier" type="mesg:FIXMUniqueMessageIdentifierType" minOccurs="0" maxOccurs="1">
      <annotation>
        <documentation>A unique message identifier for FIXM-based messages. [FIXM]</documentation>
      </annotation>
    </element>
  </sequence>
</complexType>
Complex Type mesg:FIXMUniqueMessageIdentifierType
Namespace http://www.fixm.aero/messaging/4.0
Annotations
A reference that uniquely identifies a specific FIXM message and that is independent 
of any particular system.
Diagram
Diagram Messaging_xsd.tmp#RestrictedFIXMUniqueMessageIdentifierType Messaging_xsd.tmp#FIXMUniqueMessageIdentifierType_codeSpace
Type extension of mesg:RestrictedFIXMUniqueMessageIdentifierType
Type hierarchy
Used by
Attributes
QName Type Fixed Default Use Annotation
codeSpace fb:CharacterStringType urn:uuid required
Code Space of the FIXM Message Identifier
Source
<complexType name="FIXMUniqueMessageIdentifierType">
  <annotation>
    <documentation>A reference that uniquely identifies a specific FIXM message and that is independent of any particular system.</documentation>
  </annotation>
  <simpleContent>
    <extension base="mesg:RestrictedFIXMUniqueMessageIdentifierType">
      <attribute name="codeSpace" type="fb:CharacterStringType" fixed="urn:uuid" use="required">
        <annotation>
          <documentation>Code Space of the FIXM Message Identifier</documentation>
        </annotation>
      </attribute>
    </extension>
  </simpleContent>
</complexType>
Simple Type mesg:RestrictedFIXMUniqueMessageIdentifierType
Namespace http://www.fixm.aero/messaging/4.0
Annotations
Helper type for restrictions on FIXMUniqueMessageIdentifierType
Diagram
Diagram Types_xsd.tmp#CharacterStringType
Type restriction of fb:CharacterStringType
Type hierarchy
Facets
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}
Used by
Source
<simpleType name="RestrictedFIXMUniqueMessageIdentifierType">
  <annotation>
    <documentation>Helper type for restrictions on FIXMUniqueMessageIdentifierType</documentation>
  </annotation>
  <restriction base="fb:CharacterStringType">
    <pattern value="[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}"/>
  </restriction>
</simpleType>
Simple Type mesg:AspFlightPlanVersionTypeType
Namespace http://www.fixm.aero/messaging/4.0
Annotations
A unique identifier for an ASP flight plan. [FIXM]
Diagram
Diagram Types_xsd.tmp#CharacterStringType
Type fb:CharacterStringType
Type hierarchy
Facets
minLength 0
maxLength 4096
Used by
Source
<simpleType name="AspFlightPlanVersionTypeType">
  <annotation>
    <documentation>A unique identifier for an ASP flight plan. [FIXM]</documentation>
  </annotation>
  <restriction base="fb:CharacterStringType"/>
</simpleType>
Simple Type mesg:AuFlightPlanVersionTypeType
Namespace http://www.fixm.aero/messaging/4.0
Annotations
A unique identifier for an AU flight plan. [FIXM]
Diagram
Diagram Types_xsd.tmp#CharacterStringType
Type fb:CharacterStringType
Type hierarchy
Facets
minLength 0
maxLength 4096
Used by
Source
<simpleType name="AuFlightPlanVersionTypeType">
  <annotation>
    <documentation>A unique identifier for an AU flight plan. [FIXM]</documentation>
  </annotation>
  <restriction base="fb:CharacterStringType"/>
</simpleType>
Complex Type mesg:FlightPlanNegotiationStatusType
Namespace http://www.fixm.aero/messaging/4.0
Annotations
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]
Diagram
Diagram Messaging_xsd.tmp#FlightPlanNegotiationStatusType_operationalAcceptability Messaging_xsd.tmp#FlightPlanNegotiationStatusType_planningStatus
Used by
Model mesg:operationalAcceptability{0,1} , mesg:planningStatus{0,1}
Children mesg:operationalAcceptability, mesg:planningStatus
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]</documentation>
  </annotation>
  <sequence>
    <element name="operationalAcceptability" type="mesg:OperationalAcceptabilityType" minOccurs="0" maxOccurs="1">
      <annotation>
        <documentation>The Operational Acceptability provides information concerning the status of the route and trajectory, as submitted.[adapted from ICAO Draft FF-ICE Implementation Guidance ]</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.</documentation>
      </annotation>
    </element>
  </sequence>
</complexType>
Complex Type mesg:OperationalAcceptabilityType
Namespace http://www.fixm.aero/messaging/4.0
Annotations
The Operational Acceptability provides information concerning the status of the route 
and trajectory, as submitted. [adapted from ICAO Draft FF-ICE Implementation Guidance 
]
Diagram
Diagram Messaging_xsd.tmp#OperationalAcceptabilityType_status Messaging_xsd.tmp#OperationalAcceptabilityType_statusReason
Used by
Attributes
QName Type Fixed Default Use Annotation
status mesg:OperationalAcceptabilityValueType optional
Possible values of a submission status (Ack, Reject or Manual) [adapted from ICAO 
Draft FF-ICE Implementation Guidance]
statusReason fb:CharacterStringType optional
A textual description of the reason a message was rejected. [ICAO Draft FF-ICE Implementation 
Guidance]
Source
<complexType name="OperationalAcceptabilityType">
  <annotation>
    <documentation>The Operational Acceptability provides information concerning the status of the route and trajectory, as submitted. [adapted from ICAO Draft FF-ICE Implementation Guidance ]</documentation>
  </annotation>
  <attribute name="status" type="mesg:OperationalAcceptabilityValueType" use="optional">
    <annotation>
      <documentation>Possible values of a submission status (Ack, Reject or Manual) [adapted from ICAO Draft FF-ICE Implementation Guidance]</documentation>
    </annotation>
  </attribute>
  <attribute name="statusReason" type="fb:CharacterStringType" use="optional">
    <annotation>
      <documentation>A textual description of the reason a message was rejected. [ICAO Draft FF-ICE Implementation Guidance]</documentation>
    </annotation>
  </attribute>
</complexType>
Simple Type mesg:OperationalAcceptabilityValueType
Namespace http://www.fixm.aero/messaging/4.0
Annotations
The applicable operational acceptability status values of the route and trajectory, 
as submitted. [adapted from ICAO Draft FF-ICE Implementation Guidance ]
Diagram
Diagram
Type restriction of string
Facets
enumeration ACCEPTABLE
enumeration NOT_ACCEPTABLE
Used by
Source
<simpleType name="OperationalAcceptabilityValueType">
  <annotation>
    <documentation>The applicable operational acceptability status values of the route and trajectory, as submitted. [adapted from ICAO Draft FF-ICE Implementation Guidance ]</documentation>
  </annotation>
  <restriction base="xs:string">
    <enumeration value="ACCEPTABLE"/>
    <enumeration value="NOT_ACCEPTABLE"/>
  </restriction>
</simpleType>
Complex Type mesg:PlanningStatusType
Namespace http://www.fixm.aero/messaging/4.0
Annotations
The Planning Status provides information concerning the status of the route and trajectory, 
as submitted.[adapted from ICAO Draft FF-ICE Implementation Guidance ]
Diagram
Diagram Messaging_xsd.tmp#PlanningStatusType_status Messaging_xsd.tmp#PlanningStatusType_statusReason
Used by
Attributes
QName Type Fixed Default Use Annotation
status mesg:PlanningStatusValueType optional
The Planning Status provides information concerning the status of the route and trajectory, 
as submitted.[adapted from ICAO Draft FF-ICE Implementation Guidance ]
statusReason fb:CharacterStringType optional
Textual explanation of the operational acceptability returned. [ICAO Draft FF-ICE 
Implementation Guidance]
Source
<complexType name="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 ]</documentation>
  </annotation>
  <attribute name="status" type="mesg:PlanningStatusValueType" use="optional">
    <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 ]</documentation>
    </annotation>
  </attribute>
  <attribute name="statusReason" type="fb:CharacterStringType" use="optional">
    <annotation>
      <documentation>Textual explanation of the operational acceptability returned. [ICAO Draft FF-ICE Implementation Guidance]</documentation>
    </annotation>
  </attribute>
</complexType>
Simple Type mesg:PlanningStatusValueType
Namespace http://www.fixm.aero/messaging/4.0
Annotations
The applicable planning status values of the route and trajectory, as submitted. 
[adapted from ICAO Draft FF-ICE Implementation Guidance ]
Diagram
Diagram
Type restriction of string
Facets
enumeration CONCUR
enumeration NON_CONCUR
enumeration NEGOTIATE
Used by
Source
<simpleType name="PlanningStatusValueType">
  <annotation>
    <documentation>The applicable planning status values of the route and trajectory, as submitted. [adapted from ICAO Draft FF-ICE Implementation Guidance ]</documentation>
  </annotation>
  <restriction base="xs:string">
    <enumeration value="CONCUR"/>
    <enumeration value="NON_CONCUR"/>
    <enumeration value="NEGOTIATE"/>
  </restriction>
</simpleType>
Complex Type mesg:FlightPlanVersionType
Namespace http://www.fixm.aero/messaging/4.0
Annotations
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]
Diagram
Diagram Messaging_xsd.tmp#FlightPlanVersionType_referenceVersion Messaging_xsd.tmp#FlightPlanVersionType_version
Used by
Model mesg:referenceVersion{0,1} , mesg:version{0,1}
Children mesg:referenceVersion, mesg:version
Source
<complexType name="FlightPlanVersionType">
  <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]</documentation>
  </annotation>
  <sequence>
    <element name="referenceVersion" type="mesg:FlightPlanVersionTypeChoiceType" minOccurs="0" maxOccurs="1">
      <annotation>
        <documentation>The reference of the Flight Plan Version to which the response pertains.</documentation>
      </annotation>
    </element>
    <element name="version" type="mesg:FlightPlanVersionTypeChoiceType" 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]</documentation>
      </annotation>
    </element>
  </sequence>
</complexType>
Complex Type mesg:FlightPlanVersionTypeChoiceType
Namespace http://www.fixm.aero/messaging/4.0
Annotations
The FlightPlanVersionChoice class allows specifying an AU flight plan version or 
an ASP flight plan version. [FIXM]
Diagram
Diagram Messaging_xsd.tmp#FlightPlanVersionTypeChoiceType_aspFlightPlanVersion Messaging_xsd.tmp#FlightPlanVersionTypeChoiceType_auFlightPlanVersion
Used by
Model mesg:aspFlightPlanVersion{0,1} | mesg:auFlightPlanVersion{0,1}
Children mesg:aspFlightPlanVersion, mesg:auFlightPlanVersion
Source
<complexType name="FlightPlanVersionTypeChoiceType">
  <annotation>
    <documentation>The FlightPlanVersionChoice class allows specifying an AU flight plan version or an ASP flight plan version. [FIXM]</documentation>
  </annotation>
  <choice>
    <element name="aspFlightPlanVersion" type="mesg:AspFlightPlanVersionTypeType" minOccurs="0" maxOccurs="1">
      <annotation>
        <documentation>A unique identifier for the latest version of a flight plan as distributed by the sending ASP. A flight plan version should be operationally usable for verification that the pilot or operator and ATM personnel are using the same information for the flight. [adapted from ICAO Draft FF-ICE Implementation Guidance]</documentation>
      </annotation>
    </element>
    <element name="auFlightPlanVersion" type="mesg:AuFlightPlanVersionTypeType" minOccurs="0" maxOccurs="1">
      <annotation>
        <documentation>A unique identifier for the latest version of a flight plan submitted by an Airspace User. A flight plan version should be operationally usable for verification that the pilot or operator and ATM personnel are using the same information for the flight. [adapted from ICAO Draft FF-ICE Implementation Guidance]</documentation>
      </annotation>
    </element>
  </choice>
</complexType>
Complex Type mesg:MessageType
Namespace http://www.fixm.aero/messaging/4.0
Annotations
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.
Diagram
Diagram Messaging_xsd.tmp#AbstractMessageType_extensions Messaging_xsd.tmp#AbstractMessageType_messageDateTime Messaging_xsd.tmp#AbstractMessageType_messageOriginator Messaging_xsd.tmp#AbstractMessageType_recipient Messaging_xsd.tmp#AbstractMessageType_recipientDeliveryResponsibility Messaging_xsd.tmp#AbstractMessageType_uniqueMessageIdentifier Messaging_xsd.tmp#AbstractMessageType Messaging_xsd.tmp#MessageType_flight Messaging_xsd.tmp#MessageType_flightPlanNegotiationStatus Messaging_xsd.tmp#MessageType_flightPlanVersion Messaging_xsd.tmp#MessageType_referenceMessage Messaging_xsd.tmp#MessageType_submissionStatus
Type extension of mesg:AbstractMessageType
Type hierarchy
Used by
Element mesg:Message
Model mesg:extensions* , mesg:messageDateTime{0,1} , mesg:messageOriginator{0,1} , mesg:recipient{0,1} , mesg:recipientDeliveryResponsibility{0,1} , mesg:uniqueMessageIdentifier{0,1} , mesg:flight{0,1} , mesg:flightPlanNegotiationStatus{0,1} , mesg:flightPlanVersion{0,1} , mesg:referenceMessage{0,1} , mesg:submissionStatus{0,1}
Children mesg:extensions, mesg:flight, mesg:flightPlanNegotiationStatus, mesg:flightPlanVersion, mesg:messageDateTime, mesg:messageOriginator, mesg:recipient, mesg:recipientDeliveryResponsibility, mesg:referenceMessage, mesg:submissionStatus, mesg:uniqueMessageIdentifier
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.</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]</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]</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]</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]</documentation>
          </annotation>
        </element>
      </sequence>
    </extension>
  </complexContent>
</complexType>
Complex Type mesg:SubmissionStatusType
Namespace http://www.fixm.aero/messaging/4.0
Annotations
A status indicating if a message could be processed and acted on. [adapted from ICAO 
Draft FF-ICE Implementation Guidance]
Diagram
Diagram Messaging_xsd.tmp#SubmissionStatusType_status Messaging_xsd.tmp#SubmissionStatusType_statusReason
Used by
Attributes
QName Type Fixed Default Use Annotation
status mesg:SubmissionStatusValueType optional
Possible values of a submission status (Ack, Reject or Manual) [adapted from ICAO 
Draft FF-ICE Implementation Guidance]
statusReason fb:CharacterStringType optional
A textual description of the reason a message was rejected. [ICAO Draft FF-ICE Implementation 
Guidance]
Source
<complexType name="SubmissionStatusType">
  <annotation>
    <documentation>A status indicating if a message could be processed and acted on. [adapted from ICAO Draft FF-ICE Implementation Guidance]</documentation>
  </annotation>
  <attribute name="status" type="mesg:SubmissionStatusValueType" use="optional">
    <annotation>
      <documentation>Possible values of a submission status (Ack, Reject or Manual) [adapted from ICAO Draft FF-ICE Implementation Guidance]</documentation>
    </annotation>
  </attribute>
  <attribute name="statusReason" type="fb:CharacterStringType" use="optional">
    <annotation>
      <documentation>A textual description of the reason a message was rejected. [ICAO Draft FF-ICE Implementation Guidance]</documentation>
    </annotation>
  </attribute>
</complexType>
Simple Type mesg:SubmissionStatusValueType
Namespace http://www.fixm.aero/messaging/4.0
Annotations
Possible values of a submission status (Ack, Reject or Manual) [adapted from ICAO 
Draft FF-ICE Implementation Guidance]
Diagram
Diagram
Type restriction of string
Facets
enumeration ACK
A submission status of "Ack" shall indicate that a message could be processed and 
acted on. [ICAO Draft FF-ICE Implementation Guidance]
enumeration REJECT
A submission status of "Reject" shall indicate that a message could not be processed 
and acted on, and was not retained by the receiving system. [ICAO Draft FF-ICE Implementation 
Guidance]
enumeration MANUAL
A submission status of "Manual" shall indicate that a message could not be processed 
and acted on, and the receiving unit is attempting manual handling of the message. 
[ICAO Draft FF-ICE Implementation Guidance]
Used by
Source
<simpleType name="SubmissionStatusValueType">
  <annotation>
    <documentation>Possible values of a submission status (Ack, Reject or Manual) [adapted from ICAO Draft FF-ICE Implementation Guidance]</documentation>
  </annotation>
  <restriction base="xs:string">
    <enumeration value="ACK">
      <annotation>
        <documentation>A submission status of "Ack" shall indicate that a message could be processed and acted on. [ICAO Draft FF-ICE Implementation Guidance]</documentation>
      </annotation>
    </enumeration>
    <enumeration value="REJECT">
      <annotation>
        <documentation>A submission status of "Reject" shall indicate that a message could not be processed and acted on, and was not retained by the receiving system. [ICAO Draft FF-ICE Implementation Guidance]</documentation>
      </annotation>
    </enumeration>
    <enumeration value="MANUAL">
      <annotation>
        <documentation>A submission status of "Manual" shall indicate that a message could not be processed and acted on, and the receiving unit is attempting manual handling of the message. [ICAO Draft FF-ICE Implementation Guidance]</documentation>
      </annotation>
    </enumeration>
  </restriction>
</simpleType>
Complex Type mesg:MessageCollectionType
Namespace http://www.fixm.aero/messaging/4.0
Annotations
A structure allowing multiple messages to be sent together. [FIXM] The MessageCollection 
element is an entry point to the FIXM model.
Diagram
Diagram Messaging_xsd.tmp#AbstractMessageType_extensions Messaging_xsd.tmp#AbstractMessageType_messageDateTime Messaging_xsd.tmp#AbstractMessageType_messageOriginator Messaging_xsd.tmp#AbstractMessageType_recipient Messaging_xsd.tmp#AbstractMessageType_recipientDeliveryResponsibility Messaging_xsd.tmp#AbstractMessageType_uniqueMessageIdentifier Messaging_xsd.tmp#AbstractMessageType Messaging_xsd.tmp#MessageCollectionType_message
Type extension of mesg:AbstractMessageType
Type hierarchy
Used by
Model mesg:extensions* , mesg:messageDateTime{0,1} , mesg:messageOriginator{0,1} , mesg:recipient{0,1} , mesg:recipientDeliveryResponsibility{0,1} , mesg:uniqueMessageIdentifier{0,1} , mesg:message*
Children mesg:extensions, mesg:message, mesg:messageDateTime, mesg:messageOriginator, mesg:recipient, mesg:recipientDeliveryResponsibility, mesg:uniqueMessageIdentifier
Source
<complexType name="MessageCollectionType">
  <annotation>
    <documentation>A structure allowing multiple messages to be sent together. [FIXM] The MessageCollection element is an entry point to the FIXM model.</documentation>
  </annotation>
  <complexContent>
    <extension base="mesg:AbstractMessageType">
      <sequence>
        <element name="message" type="mesg:AbstractMessageType" minOccurs="0" maxOccurs="unbounded">
          <annotation>
            <documentation>Each of the messages grouped in a Message Collection [FIXM]</documentation>
          </annotation>
        </element>
      </sequence>
    </extension>
  </complexContent>
</complexType>
Attribute mesg:FIXMUniqueMessageIdentifierType / @codeSpace
Namespace No namespace
Annotations
Code Space of the FIXM Message Identifier
Type fb:CharacterStringType
Properties
use: required
fixed: urn:uuid
Facets
minLength 0
maxLength 4096
Used by
Source
<attribute name="codeSpace" type="fb:CharacterStringType" fixed="urn:uuid" use="required">
  <annotation>
    <documentation>Code Space of the FIXM Message Identifier</documentation>
  </annotation>
</attribute>
Attribute mesg:OperationalAcceptabilityType / @status
Namespace No namespace
Annotations
Possible values of a submission status (Ack, Reject or Manual) [adapted from ICAO 
Draft FF-ICE Implementation Guidance]
Type mesg:OperationalAcceptabilityValueType
Properties
use: optional
Facets
enumeration ACCEPTABLE
enumeration NOT_ACCEPTABLE
Used by
Source
<attribute name="status" type="mesg:OperationalAcceptabilityValueType" use="optional">
  <annotation>
    <documentation>Possible values of a submission status (Ack, Reject or Manual) [adapted from ICAO Draft FF-ICE Implementation Guidance]</documentation>
  </annotation>
</attribute>
Attribute mesg:OperationalAcceptabilityType / @statusReason
Namespace No namespace
Annotations
A textual description of the reason a message was rejected. [ICAO Draft FF-ICE Implementation 
Guidance]
Type fb:CharacterStringType
Properties
use: optional
Facets
minLength 0
maxLength 4096
Used by
Source
<attribute name="statusReason" type="fb:CharacterStringType" use="optional">
  <annotation>
    <documentation>A textual description of the reason a message was rejected. [ICAO Draft FF-ICE Implementation Guidance]</documentation>
  </annotation>
</attribute>
Attribute mesg:PlanningStatusType / @status
Namespace No namespace
Annotations
The Planning Status provides information concerning the status of the route and trajectory, 
as submitted.[adapted from ICAO Draft FF-ICE Implementation Guidance ]
Type mesg:PlanningStatusValueType
Properties
use: optional
Facets
enumeration CONCUR
enumeration NON_CONCUR
enumeration NEGOTIATE
Used by
Source
<attribute name="status" type="mesg:PlanningStatusValueType" use="optional">
  <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 ]</documentation>
  </annotation>
</attribute>
Attribute mesg:PlanningStatusType / @statusReason
Namespace No namespace
Annotations
Textual explanation of the operational acceptability returned. [ICAO Draft FF-ICE 
Implementation Guidance]
Type fb:CharacterStringType
Properties
use: optional
Facets
minLength 0
maxLength 4096
Used by
Source
<attribute name="statusReason" type="fb:CharacterStringType" use="optional">
  <annotation>
    <documentation>Textual explanation of the operational acceptability returned. [ICAO Draft FF-ICE Implementation Guidance]</documentation>
  </annotation>
</attribute>
Attribute mesg:SubmissionStatusType / @status
Namespace No namespace
Annotations
Possible values of a submission status (Ack, Reject or Manual) [adapted from ICAO 
Draft FF-ICE Implementation Guidance]
Type mesg:SubmissionStatusValueType
Properties
use: optional
Facets
enumeration ACK
A submission status of "Ack" shall indicate that a message could be processed and 
acted on. [ICAO Draft FF-ICE Implementation Guidance]
enumeration REJECT
A submission status of "Reject" shall indicate that a message could not be processed 
and acted on, and was not retained by the receiving system. [ICAO Draft FF-ICE Implementation 
Guidance]
enumeration MANUAL
A submission status of "Manual" shall indicate that a message could not be processed 
and acted on, and the receiving unit is attempting manual handling of the message. 
[ICAO Draft FF-ICE Implementation Guidance]
Used by
Source
<attribute name="status" type="mesg:SubmissionStatusValueType" use="optional">
  <annotation>
    <documentation>Possible values of a submission status (Ack, Reject or Manual) [adapted from ICAO Draft FF-ICE Implementation Guidance]</documentation>
  </annotation>
</attribute>
Attribute mesg:SubmissionStatusType / @statusReason
Namespace No namespace
Annotations
A textual description of the reason a message was rejected. [ICAO Draft FF-ICE Implementation 
Guidance]
Type fb:CharacterStringType
Properties
use: optional
Facets
minLength 0
maxLength 4096
Used by
Source
<attribute name="statusReason" type="fb:CharacterStringType" use="optional">
  <annotation>
    <documentation>A textual description of the reason a message was rejected. [ICAO Draft FF-ICE Implementation Guidance]</documentation>
  </annotation>
</attribute>