Showing:

Annotations
Attributes
Diagrams
Facets
Instances
Properties
Source
Used by
Imported schema Messaging.xsd
Namespace http://www.fixm.aero/messaging/4.1
Annotations
 
Copyright (c) 2017 Airservices Australia, DSNA, EUROCONTROL, GCAA UAE, IATA, 
       International Coordinating Council of Aerospace Industries Associations, 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, GCAA UAE, IATA, International Coordinating 
  Council of Aerospace Industries Associations, JCAB, NATS Limited, NAV CANADA, 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 UAE GCAA: https://www.gcaa.gov.ae 
       Details on the ICCAIA: www.iccaia.org 
       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 message metadata elements and some negotiation related elements in support 
of messaging-related aspects required by the FF-ICE/1 concept and guidance documents. 
Ambiguity regarding FF-ICE support by FIXM: the way elements are packaged and used 
is not, according to the ICAO SWIM concept, within the formal scope of FIXM.
Properties
attribute form default: unqualified
element form default: qualified
version: 4.1.0
Element mesg:AbstractMessageType / mesg:deliveryResponsibility
Namespace http://www.fixm.aero/messaging/4.1
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]<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>
Diagram
Diagram Extension_xsd.tmp#ExtensibleType_extension Extension_xsd.tmp#ExtensibleType Organization_xsd.tmp#PersonOrOrganizationType_name Organization_xsd.tmp#PersonOrOrganizationType_participantType Organization_xsd.tmp#PersonOrOrganizationType_contact Organization_xsd.tmp#PersonOrOrganizationType
Type fb:PersonOrOrganizationType
Type hierarchy
Properties
content: complex
minOccurs: 0
maxOccurs: 1
Model fb:extension{0,2000} , fb:contact{0,1}
Children fb:contact, fb:extension
Instance
 
<mesg:deliveryResponsibility name="" participantType="">
  <fb:extension>{0,2000}</fb:extension>
  <fb:contact name="" title="">{0,1}</fb:contact>
</mesg:deliveryResponsibility>
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="deliveryResponsibility" 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]
      <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 mesg:AbstractMessageType / mesg:extensions
Namespace http://www.fixm.aero/messaging/4.1
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]<deprecated>
  <deletionVersion>5.0.0</deletionVersion>
  <deprecatedVersion>4.1.0</deprecatedVersion>
  <rationale>CR #9 Revision of Extension Mechanism</rationale>
  <replacement>Revised extension mechanism</replacement>
</deprecated>
Diagram
Diagram Extension_xsd.tmp#ExtensionType
Type fb:ExtensionType
Properties
content: complex
minOccurs: 0
maxOccurs: 2000
Source
 
<element name="extensions" type="fb:ExtensionType" minOccurs="0" maxOccurs="2000">
  <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]
      <deprecated>
        <deletionVersion>5.0.0</deletionVersion>
        <deprecatedVersion>4.1.0</deprecatedVersion>
        <rationale>CR #9 Revision of Extension Mechanism</rationale>
        <replacement>Revised extension mechanism</replacement>
      </deprecated>
    </documentation>
  </annotation>
</element>
Element mesg:AbstractMessageType / mesg:messageOriginator
Namespace http://www.fixm.aero/messaging/4.1
Annotations
 
Sender of the message<sup>1</sup> [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>
Diagram
Diagram Extension_xsd.tmp#ExtensibleType_extension Extension_xsd.tmp#ExtensibleType Organization_xsd.tmp#PersonOrOrganizationType_name Organization_xsd.tmp#PersonOrOrganizationType_participantType Organization_xsd.tmp#PersonOrOrganizationType_contact Organization_xsd.tmp#PersonOrOrganizationType
Type fb:PersonOrOrganizationType
Type hierarchy
Properties
content: complex
minOccurs: 0
maxOccurs: 1
Model fb:extension{0,2000} , fb:contact{0,1}
Children fb:contact, fb:extension
Instance
 
<mesg:messageOriginator name="" participantType="">
  <fb:extension>{0,2000}</fb:extension>
  <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]
      <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 mesg:AbstractMessageType / mesg:recipient
Namespace http://www.fixm.aero/messaging/4.1
Annotations
 
The -one or more- intended recipients of the flight information. [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>
Diagram
Diagram Extension_xsd.tmp#ExtensibleType_extension Extension_xsd.tmp#ExtensibleType Organization_xsd.tmp#PersonOrOrganizationType_name Organization_xsd.tmp#PersonOrOrganizationType_participantType Organization_xsd.tmp#PersonOrOrganizationType_contact Organization_xsd.tmp#PersonOrOrganizationType
Type fb:PersonOrOrganizationType
Type hierarchy
Properties
content: complex
minOccurs: 0
maxOccurs: 2000
Model fb:extension{0,2000} , fb:contact{0,1}
Children fb:contact, fb:extension
Instance
 
<mesg:recipient name="" participantType="">
  <fb:extension>{0,2000}</fb:extension>
  <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="2000">
  <annotation>
    <documentation>The -one or more- intended recipients of the flight information. [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 mesg:AbstractMessageType / mesg:uniqueMessageIdentifier
Namespace http://www.fixm.aero/messaging/4.1
Annotations
 
A unique message identifier for FIXM-based messages. [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>
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<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>
Source
 
<element name="uniqueMessageIdentifier" type="mesg:FIXMUniqueMessageIdentifierType" minOccurs="0" maxOccurs="1">
  <annotation>
    <documentation>A unique message identifier for FIXM-based messages. [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 mesg:AbstractMessage
Namespace http://www.fixm.aero/messaging/4.1
Diagram
Diagram Extension_xsd.tmp#ExtensibleType_extension Extension_xsd.tmp#ExtensibleType Messaging_xsd.tmp#AbstractMessageType_messageDateTime Messaging_xsd.tmp#AbstractMessageType_messageType Messaging_xsd.tmp#AbstractMessageType_deliveryResponsibility Messaging_xsd.tmp#AbstractMessageType_extensions Messaging_xsd.tmp#AbstractMessageType_messageOriginator Messaging_xsd.tmp#AbstractMessageType_recipient Messaging_xsd.tmp#AbstractMessageType_uniqueMessageIdentifier Messaging_xsd.tmp#AbstractMessageType Extension_xsd.tmp#Extensible
Type mesg:AbstractMessageType
Type hierarchy
Properties
content: complex
Substitution Group Affiliation
Model fb:extension{0,2000} , mesg:deliveryResponsibility{0,1} , mesg:extensions{0,2000} , mesg:messageOriginator{0,1} , mesg:recipient{0,2000} , mesg:uniqueMessageIdentifier{0,1}
Children fb:extension, mesg:deliveryResponsibility, mesg:extensions, mesg:messageOriginator, mesg:recipient, mesg:uniqueMessageIdentifier
Instance
 
<mesg:AbstractMessage messageDateTime="" messageType="">
  <fb:extension>{0,2000}</fb:extension>
  <mesg:deliveryResponsibility name="" participantType="">{0,1}</mesg:deliveryResponsibility>
  <mesg:extensions>{0,2000}</mesg:extensions>
  <mesg:messageOriginator name="" participantType="">{0,1}</mesg:messageOriginator>
  <mesg:recipient name="" participantType="">{0,2000}</mesg:recipient>
  <mesg:uniqueMessageIdentifier codeSpace="urn:uuid">{0,1}</mesg:uniqueMessageIdentifier>
</mesg:AbstractMessage>
Attributes
QName Type Fixed Default Use Annotation
messageDateTime fb:TimeType optional 
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 
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>
Source
 
<element name="AbstractMessage" type="mesg:AbstractMessageType" substitutionGroup="fb:Extensible"/>
Element mesg:FilingStatus
Namespace http://www.fixm.aero/messaging/4.1
Diagram
Diagram Extension_xsd.tmp#ExtensibleType_extension Extension_xsd.tmp#ExtensibleType Messaging_xsd.tmp#FilingStatusType_status Messaging_xsd.tmp#FilingStatusType_statusReason Messaging_xsd.tmp#FilingStatusType Extension_xsd.tmp#Extensible
Type mesg:FilingStatusType
Type hierarchy
Properties
content: complex
Substitution Group Affiliation
Model fb:extension{0,2000}
Children fb:extension
Instance
 
<mesg:FilingStatus status="" statusReason="">
  <fb:extension>{0,2000}</fb:extension>
</mesg:FilingStatus>
Attributes
QName Type Fixed Default Use Annotation
status mesg:FilingStatusValueType optional 
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 
A textual description of the reason a message was rejected. [ICAO Draft FF-ICE Implementation 
Guidance]<deprecated/>
Source
 
<element name="FilingStatus" type="mesg:FilingStatusType" substitutionGroup="fb:Extensible"/>
Element mesg:FlightPlanNegotiationStatusType / mesg:filingStatus
Namespace http://www.fixm.aero/messaging/4.1
Annotations
 
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>
Diagram
Diagram Extension_xsd.tmp#ExtensibleType_extension Extension_xsd.tmp#ExtensibleType Messaging_xsd.tmp#FilingStatusType_status Messaging_xsd.tmp#FilingStatusType_statusReason Messaging_xsd.tmp#FilingStatusType
Type mesg:FilingStatusType
Type hierarchy
Properties
content: complex
minOccurs: 0
maxOccurs: 1
Model fb:extension{0,2000}
Children fb:extension
Instance
 
<mesg:filingStatus status="" statusReason="">
  <fb:extension>{0,2000}</fb:extension>
</mesg:filingStatus>
Attributes
QName Type Fixed Default Use Annotation
status mesg:FilingStatusValueType optional 
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 
A textual description of the reason a message was rejected. [ICAO Draft FF-ICE Implementation 
Guidance]<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 mesg:FlightPlanNegotiationStatusType / mesg:planningStatus
Namespace http://www.fixm.aero/messaging/4.1
Annotations
 
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>
Diagram
Diagram Extension_xsd.tmp#ExtensibleType_extension Extension_xsd.tmp#ExtensibleType Messaging_xsd.tmp#PlanningStatusType_status Messaging_xsd.tmp#PlanningStatusType_statusReason Messaging_xsd.tmp#PlanningStatusType
Type mesg:PlanningStatusType
Type hierarchy
Properties
content: complex
minOccurs: 0
maxOccurs: 1
Model fb:extension{0,2000}
Children fb:extension
Instance
 
<mesg:planningStatus status="" statusReason="">
  <fb:extension>{0,2000}</fb:extension>
</mesg:planningStatus>
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 ]<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 
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>
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>
Element mesg:FlightPlanNegotiationStatus
Namespace http://www.fixm.aero/messaging/4.1
Diagram
Diagram Extension_xsd.tmp#ExtensibleType_extension Extension_xsd.tmp#ExtensibleType Messaging_xsd.tmp#FlightPlanNegotiationStatusType_filingStatus Messaging_xsd.tmp#FlightPlanNegotiationStatusType_planningStatus Messaging_xsd.tmp#FlightPlanNegotiationStatusType Extension_xsd.tmp#Extensible
Type mesg:FlightPlanNegotiationStatusType
Type hierarchy
Properties
content: complex
Substitution Group Affiliation
Model fb:extension{0,2000} , mesg:filingStatus{0,1} , mesg:planningStatus{0,1}
Children fb:extension, mesg:filingStatus, mesg:planningStatus
Instance
 
<mesg:FlightPlanNegotiationStatus>
  <fb:extension>{0,2000}</fb:extension>
  <mesg:filingStatus status="" statusReason="">{0,1}</mesg:filingStatus>
  <mesg:planningStatus status="" statusReason="">{0,1}</mesg:planningStatus>
</mesg:FlightPlanNegotiationStatus>
Source
 
<element name="FlightPlanNegotiationStatus" type="mesg:FlightPlanNegotiationStatusType" substitutionGroup="fb:Extensible"/>
Element mesg:FlightPlanVersionType / mesg:referenceVersion
Namespace http://www.fixm.aero/messaging/4.1
Annotations
 
The reference of the Flight Plan Version to which the response pertains.<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>
Diagram
Diagram Extension_xsd.tmp#ExtensibleType_extension Extension_xsd.tmp#ExtensibleType Messaging_xsd.tmp#FlightPlanVersionTypeChoiceType_aspFlightPlanVersion Messaging_xsd.tmp#FlightPlanVersionTypeChoiceType_auFlightPlanVersion Messaging_xsd.tmp#FlightPlanVersionTypeChoiceType
Type mesg:FlightPlanVersionTypeChoiceType
Type hierarchy
Properties
content: complex
minOccurs: 0
maxOccurs: 1
Model fb:extension{0,2000} , (mesg:aspFlightPlanVersion{0,1} | mesg:auFlightPlanVersion{0,1})
Children fb:extension, mesg:aspFlightPlanVersion, mesg:auFlightPlanVersion
Instance
 
<mesg:referenceVersion>
  <fb:extension>{0,2000}</fb:extension>
  <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.
      <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>
    </documentation>
  </annotation>
</element>
Element mesg:FlightPlanVersionTypeChoiceType / mesg:aspFlightPlanVersion
Namespace http://www.fixm.aero/messaging/4.1
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]. The identifier 
should begin at one and increase by one with each revision.<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>
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]. The identifier should begin at one and increase by one with each revision.
      <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 mesg:FlightPlanVersionTypeChoiceType / mesg:auFlightPlanVersion
Namespace http://www.fixm.aero/messaging/4.1
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]. The identifier should begin 
at one and increase by one with each revision.<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>
Diagram
Diagram Messaging_xsd.tmp#AuFlightPlanVersionTypeType
Type mesg:AuFlightPlanVersionTypeType
Type hierarchy
Properties
content: simple
minOccurs: 0
maxOccurs: 1
Facets
minInclusive 1
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]. The identifier should begin at one and increase by one with each revision.
      <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>
    </documentation>
  </annotation>
</element>
Element mesg:FlightPlanVersionType / mesg:version
Namespace http://www.fixm.aero/messaging/4.1
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]<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>
Diagram
Diagram Extension_xsd.tmp#ExtensibleType_extension Extension_xsd.tmp#ExtensibleType Messaging_xsd.tmp#FlightPlanVersionTypeChoiceType_aspFlightPlanVersion Messaging_xsd.tmp#FlightPlanVersionTypeChoiceType_auFlightPlanVersion Messaging_xsd.tmp#FlightPlanVersionTypeChoiceType
Type mesg:FlightPlanVersionTypeChoiceType
Type hierarchy
Properties
content: complex
minOccurs: 0
maxOccurs: 1
Model fb:extension{0,2000} , (mesg:aspFlightPlanVersion{0,1} | mesg:auFlightPlanVersion{0,1})
Children fb:extension, mesg:aspFlightPlanVersion, mesg:auFlightPlanVersion
Instance
 
<mesg:version>
  <fb:extension>{0,2000}</fb:extension>
  <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]
      <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 mesg:FlightPlanVersion
Namespace http://www.fixm.aero/messaging/4.1
Diagram
Diagram Extension_xsd.tmp#ExtensibleType_extension Extension_xsd.tmp#ExtensibleType Messaging_xsd.tmp#FlightPlanVersionType_referenceVersion Messaging_xsd.tmp#FlightPlanVersionType_version Messaging_xsd.tmp#FlightPlanVersionType Extension_xsd.tmp#Extensible
Type mesg:FlightPlanVersionType
Type hierarchy
Properties
content: complex
Substitution Group Affiliation
Model fb:extension{0,2000} , mesg:referenceVersion{0,1} , mesg:version{0,1}
Children fb:extension, mesg:referenceVersion, mesg:version
Instance
 
<mesg:FlightPlanVersion>
  <fb:extension>{0,2000}</fb:extension>
  <mesg:referenceVersion>{0,1}</mesg:referenceVersion>
  <mesg:version>{0,1}</mesg:version>
</mesg:FlightPlanVersion>
Source
 
<element name="FlightPlanVersion" type="mesg:FlightPlanVersionType" substitutionGroup="fb:Extensible"/>
Element mesg:FlightPlanVersionTypeChoice
Namespace http://www.fixm.aero/messaging/4.1
Diagram
Diagram Extension_xsd.tmp#ExtensibleType_extension Extension_xsd.tmp#ExtensibleType Messaging_xsd.tmp#FlightPlanVersionTypeChoiceType_aspFlightPlanVersion Messaging_xsd.tmp#FlightPlanVersionTypeChoiceType_auFlightPlanVersion Messaging_xsd.tmp#FlightPlanVersionTypeChoiceType Extension_xsd.tmp#Extensible
Type mesg:FlightPlanVersionTypeChoiceType
Type hierarchy
Properties
content: complex
Substitution Group Affiliation
Model fb:extension{0,2000} , (mesg:aspFlightPlanVersion{0,1} | mesg:auFlightPlanVersion{0,1})
Children fb:extension, mesg:aspFlightPlanVersion, mesg:auFlightPlanVersion
Instance
 
<mesg:FlightPlanVersionTypeChoice>
  <fb:extension>{0,2000}</fb:extension>
  <mesg:aspFlightPlanVersion>{0,1}</mesg:aspFlightPlanVersion>
  <mesg:auFlightPlanVersion>{0,1}</mesg:auFlightPlanVersion>
</mesg:FlightPlanVersionTypeChoice>
Source
 
<element name="FlightPlanVersionTypeChoice" type="mesg:FlightPlanVersionTypeChoiceType" substitutionGroup="fb:Extensible"/>
Element mesg:MessageType / mesg:flight
Namespace http://www.fixm.aero/messaging/4.1
Annotations
 
A flight associated with the message.
Diagram
Diagram Extension_xsd.tmp#ExtensibleType_extension Extension_xsd.tmp#ExtensibleType 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_gufiOriginator 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
Type hierarchy
Properties
content: complex
minOccurs: 0
maxOccurs: 1
Model fb:extension{0,2000} , fx:agreed{0,1} , fx:aircraft{0,1} , fx:arrival{0,1} , fx:current{0,1} , fx:dangerousGoods{0,2000} , fx:departure{0,1} , fx:desired{0,1} , fx:destination{0,1} , fx:emergency{0,1} , fx:enRoute{0,1} , fx:extensions{0,2000} , fx:filed{0,1} , fx:flightIdentification{0,1} , fx:flightPlanOriginator{0,1} , fx:flightPlanSubmitter{0,1} , fx:gufi{0,1} , fx:gufiOriginator{0,1} , fx:negotiating{0,1} , fx:operator{0,1} , fx:radioCommunicationFailure{0,1} , fx:rankedTrajectories{0,2000} , fx:specialHandling{0,1} , fx:supplementaryData{0,1}
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
Instance
 
<mesg:flight flightType="" remarks="">
  <fb:extension>{0,2000}</fb:extension>
  <fx:agreed>{0,1}</fx:agreed>
  <fx:aircraft aircraftAddress="" aircraftApproachCategory="" numberOfAircraft="" registration="" significantMarkings="" wakeTurbulence="">{0,1}</fx:aircraft>
  <fx:arrival actualTimeOfArrival="" airportSlotIdentification="" runwayDirection="">{0,1}</fx:arrival>
  <fx:current>{0,1}</fx:current>
  <fx:dangerousGoods aircraftLimitation="" guidebookNumber="" onboardLocation="" shipment="">{0,2000}</fx:dangerousGoods>
  <fx:departure actualTimeOfDeparture="" airportSlotIdentification="" estimatedOffBlockTime="" 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 currentModeACode="">{0,1}</fx:enRoute>
  <fx:extensions>{0,2000}</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:gufiOriginator name="" participantType="">{0,1}</fx:gufiOriginator>
  <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,2000}</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 
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.
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.1
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]<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>
Diagram
Diagram Extension_xsd.tmp#ExtensibleType_extension Extension_xsd.tmp#ExtensibleType Messaging_xsd.tmp#FlightPlanNegotiationStatusType_filingStatus Messaging_xsd.tmp#FlightPlanNegotiationStatusType_planningStatus Messaging_xsd.tmp#FlightPlanNegotiationStatusType
Type mesg:FlightPlanNegotiationStatusType
Type hierarchy
Properties
content: complex
minOccurs: 0
maxOccurs: 1
Model fb:extension{0,2000} , mesg:filingStatus{0,1} , mesg:planningStatus{0,1}
Children fb:extension, mesg:filingStatus, mesg:planningStatus
Instance
 
<mesg:flightPlanNegotiationStatus>
  <fb:extension>{0,2000}</fb:extension>
  <mesg:filingStatus status="" statusReason="">{0,1}</mesg:filingStatus>
  <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]
      <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 mesg:MessageType / mesg:flightPlanVersion
Namespace http://www.fixm.aero/messaging/4.1
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]<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>
Diagram
Diagram Extension_xsd.tmp#ExtensibleType_extension Extension_xsd.tmp#ExtensibleType Messaging_xsd.tmp#FlightPlanVersionType_referenceVersion Messaging_xsd.tmp#FlightPlanVersionType_version Messaging_xsd.tmp#FlightPlanVersionType
Type mesg:FlightPlanVersionType
Type hierarchy
Properties
content: complex
minOccurs: 0
maxOccurs: 1
Model fb:extension{0,2000} , mesg:referenceVersion{0,1} , mesg:version{0,1}
Children fb:extension, mesg:referenceVersion, mesg:version
Instance
 
<mesg:flightPlanVersion>
  <fb:extension>{0,2000}</fb:extension>
  <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]
      <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 mesg:MessageType / mesg:referenceMessage
Namespace http://www.fixm.aero/messaging/4.1
Annotations
 
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>
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<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>
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 mesg:MessageType / mesg:submissionStatus
Namespace http://www.fixm.aero/messaging/4.1
Annotations
 
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>
Diagram
Diagram Extension_xsd.tmp#ExtensibleType_extension Extension_xsd.tmp#ExtensibleType Messaging_xsd.tmp#SubmissionStatusType_status Messaging_xsd.tmp#SubmissionStatusType_statusReason Messaging_xsd.tmp#SubmissionStatusType
Type mesg:SubmissionStatusType
Type hierarchy
Properties
content: complex
minOccurs: 0
maxOccurs: 1
Model fb:extension{0,2000}
Children fb:extension
Instance
 
<mesg:submissionStatus status="" statusReason="">
  <fb:extension>{0,2000}</fb:extension>
</mesg:submissionStatus>
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]<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 
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>
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>
Element mesg:Message
Namespace http://www.fixm.aero/messaging/4.1
Diagram
Diagram Extension_xsd.tmp#ExtensibleType_extension Extension_xsd.tmp#ExtensibleType Messaging_xsd.tmp#AbstractMessageType_messageDateTime Messaging_xsd.tmp#AbstractMessageType_messageType Messaging_xsd.tmp#AbstractMessageType_deliveryResponsibility Messaging_xsd.tmp#AbstractMessageType_extensions Messaging_xsd.tmp#AbstractMessageType_messageOriginator Messaging_xsd.tmp#AbstractMessageType_recipient 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 Extension_xsd.tmp#Extensible
Type mesg:MessageType
Type hierarchy
Properties
content: complex
Substitution Group Affiliation
Model fb:extension{0,2000} , mesg:deliveryResponsibility{0,1} , mesg:extensions{0,2000} , mesg:messageOriginator{0,1} , mesg:recipient{0,2000} , 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 fb:extension, mesg:deliveryResponsibility, mesg:extensions, mesg:flight, mesg:flightPlanNegotiationStatus, mesg:flightPlanVersion, mesg:messageOriginator, mesg:recipient, mesg:referenceMessage, mesg:submissionStatus, mesg:uniqueMessageIdentifier
Instance
 
<mesg:Message messageDateTime="" messageType="">
  <fb:extension>{0,2000}</fb:extension>
  <mesg:deliveryResponsibility name="" participantType="">{0,1}</mesg:deliveryResponsibility>
  <mesg:extensions>{0,2000}</mesg:extensions>
  <mesg:messageOriginator name="" participantType="">{0,1}</mesg:messageOriginator>
  <mesg:recipient name="" participantType="">{0,2000}</mesg:recipient>
  <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>
Attributes
QName Type Fixed Default Use Annotation
messageDateTime fb:TimeType optional 
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 
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>
Source
 
<element name="Message" type="mesg:MessageType" substitutionGroup="fb:Extensible"/>
Element mesg:MessageCollectionType / mesg:message
Namespace http://www.fixm.aero/messaging/4.1
Annotations
 
Each of the messages grouped in a Message Collection [FIXM]
Diagram
Diagram Extension_xsd.tmp#ExtensibleType_extension Extension_xsd.tmp#ExtensibleType Messaging_xsd.tmp#AbstractMessageType_messageDateTime Messaging_xsd.tmp#AbstractMessageType_messageType Messaging_xsd.tmp#AbstractMessageType_deliveryResponsibility Messaging_xsd.tmp#AbstractMessageType_extensions Messaging_xsd.tmp#AbstractMessageType_messageOriginator Messaging_xsd.tmp#AbstractMessageType_recipient Messaging_xsd.tmp#AbstractMessageType_uniqueMessageIdentifier Messaging_xsd.tmp#AbstractMessageType
Type mesg:AbstractMessageType
Type hierarchy
Properties
content: complex
minOccurs: 0
maxOccurs: 2000
Model fb:extension{0,2000} , mesg:deliveryResponsibility{0,1} , mesg:extensions{0,2000} , mesg:messageOriginator{0,1} , mesg:recipient{0,2000} , mesg:uniqueMessageIdentifier{0,1}
Children fb:extension, mesg:deliveryResponsibility, mesg:extensions, mesg:messageOriginator, mesg:recipient, mesg:uniqueMessageIdentifier
Instance
 
<mesg:message messageDateTime="" messageType="">
  <fb:extension>{0,2000}</fb:extension>
  <mesg:deliveryResponsibility name="" participantType="">{0,1}</mesg:deliveryResponsibility>
  <mesg:extensions>{0,2000}</mesg:extensions>
  <mesg:messageOriginator name="" participantType="">{0,1}</mesg:messageOriginator>
  <mesg:recipient name="" participantType="">{0,2000}</mesg:recipient>
  <mesg:uniqueMessageIdentifier codeSpace="urn:uuid">{0,1}</mesg:uniqueMessageIdentifier>
</mesg:message>
Attributes
QName Type Fixed Default Use Annotation
messageDateTime fb:TimeType optional 
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 
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>
Source
 
<element name="message" type="mesg:AbstractMessageType" minOccurs="0" maxOccurs="2000">
  <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.1
Diagram
Diagram Extension_xsd.tmp#ExtensibleType_extension Extension_xsd.tmp#ExtensibleType Messaging_xsd.tmp#AbstractMessageType_messageDateTime Messaging_xsd.tmp#AbstractMessageType_messageType Messaging_xsd.tmp#AbstractMessageType_deliveryResponsibility Messaging_xsd.tmp#AbstractMessageType_extensions Messaging_xsd.tmp#AbstractMessageType_messageOriginator Messaging_xsd.tmp#AbstractMessageType_recipient Messaging_xsd.tmp#AbstractMessageType_uniqueMessageIdentifier Messaging_xsd.tmp#AbstractMessageType Messaging_xsd.tmp#MessageCollectionType_message Messaging_xsd.tmp#MessageCollectionType Extension_xsd.tmp#Extensible
Type mesg:MessageCollectionType
Type hierarchy
Properties
content: complex
Substitution Group Affiliation
Model fb:extension{0,2000} , mesg:deliveryResponsibility{0,1} , mesg:extensions{0,2000} , mesg:messageOriginator{0,1} , mesg:recipient{0,2000} , mesg:uniqueMessageIdentifier{0,1} , mesg:message{0,2000}
Children fb:extension, mesg:deliveryResponsibility, mesg:extensions, mesg:message, mesg:messageOriginator, mesg:recipient, mesg:uniqueMessageIdentifier
Instance
 
<mesg:MessageCollection messageDateTime="" messageType="">
  <fb:extension>{0,2000}</fb:extension>
  <mesg:deliveryResponsibility name="" participantType="">{0,1}</mesg:deliveryResponsibility>
  <mesg:extensions>{0,2000}</mesg:extensions>
  <mesg:messageOriginator name="" participantType="">{0,1}</mesg:messageOriginator>
  <mesg:recipient name="" participantType="">{0,2000}</mesg:recipient>
  <mesg:uniqueMessageIdentifier codeSpace="urn:uuid">{0,1}</mesg:uniqueMessageIdentifier>
  <mesg:message messageDateTime="" messageType="">{0,2000}</mesg:message>
</mesg:MessageCollection>
Attributes
QName Type Fixed Default Use Annotation
messageDateTime fb:TimeType optional 
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 
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>
Source
 
<element name="MessageCollection" type="mesg:MessageCollectionType" substitutionGroup="fb:Extensible"/>
Element mesg:PlanningStatus
Namespace http://www.fixm.aero/messaging/4.1
Diagram
Diagram Extension_xsd.tmp#ExtensibleType_extension Extension_xsd.tmp#ExtensibleType Messaging_xsd.tmp#PlanningStatusType_status Messaging_xsd.tmp#PlanningStatusType_statusReason Messaging_xsd.tmp#PlanningStatusType Extension_xsd.tmp#Extensible
Type mesg:PlanningStatusType
Type hierarchy
Properties
content: complex
Substitution Group Affiliation
Model fb:extension{0,2000}
Children fb:extension
Instance
 
<mesg:PlanningStatus status="" statusReason="">
  <fb:extension>{0,2000}</fb:extension>
</mesg:PlanningStatus>
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 ]<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 
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>
Source
 
<element name="PlanningStatus" type="mesg:PlanningStatusType" substitutionGroup="fb:Extensible"/>
Element mesg:SubmissionStatus
Namespace http://www.fixm.aero/messaging/4.1
Diagram
Diagram Extension_xsd.tmp#ExtensibleType_extension Extension_xsd.tmp#ExtensibleType Messaging_xsd.tmp#SubmissionStatusType_status Messaging_xsd.tmp#SubmissionStatusType_statusReason Messaging_xsd.tmp#SubmissionStatusType Extension_xsd.tmp#Extensible
Type mesg:SubmissionStatusType
Type hierarchy
Properties
content: complex
Substitution Group Affiliation
Model fb:extension{0,2000}
Children fb:extension
Instance
 
<mesg:SubmissionStatus status="" statusReason="">
  <fb:extension>{0,2000}</fb:extension>
</mesg:SubmissionStatus>
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]<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 
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>
Source
 
<element name="SubmissionStatus" type="mesg:SubmissionStatusType" substitutionGroup="fb:Extensible"/>
Complex Type mesg:AbstractMessageType
Namespace http://www.fixm.aero/messaging/4.1
Annotations
 
An abstract class that specializes into Message or Message Collection and holds their 
common properties. [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>
Diagram
Diagram Extension_xsd.tmp#ExtensibleType_extension Extension_xsd.tmp#ExtensibleType Messaging_xsd.tmp#AbstractMessageType_messageDateTime Messaging_xsd.tmp#AbstractMessageType_messageType Messaging_xsd.tmp#AbstractMessageType_deliveryResponsibility Messaging_xsd.tmp#AbstractMessageType_extensions Messaging_xsd.tmp#AbstractMessageType_messageOriginator Messaging_xsd.tmp#AbstractMessageType_recipient Messaging_xsd.tmp#AbstractMessageType_uniqueMessageIdentifier
Type extension of fb:ExtensibleType
Type hierarchy
Properties
abstract: true
Used by
Model fb:extension{0,2000} , mesg:deliveryResponsibility{0,1} , mesg:extensions{0,2000} , mesg:messageOriginator{0,1} , mesg:recipient{0,2000} , mesg:uniqueMessageIdentifier{0,1}
Children fb:extension, mesg:deliveryResponsibility, mesg:extensions, mesg:messageOriginator, mesg:recipient, mesg:uniqueMessageIdentifier
Attributes
QName Type Fixed Default Use Annotation
messageDateTime fb:TimeType optional 
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 
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>
Source
 
<complexType abstract="true" name="AbstractMessageType">
  <annotation>
    <documentation>An abstract class that specializes into Message or Message Collection and holds their common properties. [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>
  <complexContent>
    <extension base="fb:ExtensibleType">
      <sequence>
        <element name="deliveryResponsibility" 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]
              <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="extensions" type="fb:ExtensionType" minOccurs="0" maxOccurs="2000">
          <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]
              <deprecated>
                <deletionVersion>5.0.0</deletionVersion>
                <deprecatedVersion>4.1.0</deprecatedVersion>
                <rationale>CR #9 Revision of Extension Mechanism</rationale>
                <replacement>Revised extension mechanism</replacement>
              </deprecated>
            </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]
              <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="recipient" type="fb:PersonOrOrganizationType" minOccurs="0" maxOccurs="2000">
          <annotation>
            <documentation>The -one or more- intended recipients of the flight information. [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="uniqueMessageIdentifier" type="mesg:FIXMUniqueMessageIdentifierType" minOccurs="0" maxOccurs="1">
          <annotation>
            <documentation>A unique message identifier for FIXM-based messages. [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>
      </sequence>
      <attribute name="messageDateTime" type="fb:TimeType" use="optional">
        <annotation>
          <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>
          </documentation>
        </annotation>
      </attribute>
      <attribute name="messageType" type="fb:CharacterStringType" use="optional">
        <annotation>
          <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>
          </documentation>
        </annotation>
      </attribute>
    </extension>
  </complexContent>
</complexType>
Complex Type mesg:FIXMUniqueMessageIdentifierType
Namespace http://www.fixm.aero/messaging/4.1
Annotations
 
A reference that uniquely identifies a specific FIXM message and that is independent 
of any particular system.<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>
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<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>
Source
 
<complexType name="FIXMUniqueMessageIdentifierType">
  <annotation>
    <documentation>A reference that uniquely identifies a specific FIXM message and that is independent of any particular system.
      <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>
  <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
            <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>
          </documentation>
        </annotation>
      </attribute>
    </extension>
  </simpleContent>
</complexType>
Simple Type mesg:RestrictedFIXMUniqueMessageIdentifierType
Namespace http://www.fixm.aero/messaging/4.1
Annotations
 
Helper type for restrictions on FIXMUniqueMessageIdentifierType<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>
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
      <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>
  <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.1
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]. The identifier 
should begin at one and increase by one with each revision.<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>
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 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]. The identifier should begin at one and increase by one with each revision.
      <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>
  <restriction base="fb:CharacterStringType"/>
</simpleType>
Simple Type mesg:AuFlightPlanVersionTypeType
Namespace http://www.fixm.aero/messaging/4.1
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]. The identifier should begin 
at one and increase by one with each revision.<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>
Diagram
Diagram Types_xsd.tmp#CountType
Type restriction of fb:CountType
Type hierarchy
Facets
minInclusive 1
Used by
Source
 
<simpleType name="AuFlightPlanVersionTypeType">
  <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]. The identifier should begin at one and increase by one with each revision.
      <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>
  <restriction base="fb:CountType">
    <minInclusive value="1"/>
  </restriction>
</simpleType>
Complex Type mesg:FilingStatusType
Namespace http://www.fixm.aero/messaging/4.1
Annotations
 
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>
Diagram
Diagram Extension_xsd.tmp#ExtensibleType_extension Extension_xsd.tmp#ExtensibleType Messaging_xsd.tmp#FilingStatusType_status Messaging_xsd.tmp#FilingStatusType_statusReason
Type extension of fb:ExtensibleType
Type hierarchy
Used by
Model fb:extension{0,2000}
Children fb:extension
Attributes
QName Type Fixed Default Use Annotation
status mesg:FilingStatusValueType optional 
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 
A textual description of the reason a message was rejected. [ICAO Draft FF-ICE Implementation 
Guidance]<deprecated/>
Source
 
<complexType name="FilingStatusType">
  <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>
  <complexContent>
    <extension base="fb:ExtensibleType">
      <attribute name="status" type="mesg:FilingStatusValueType" use="optional">
        <annotation>
          <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>
          </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]
            <deprecated/>
          </documentation>
        </annotation>
      </attribute>
    </extension>
  </complexContent>
</complexType>
Simple Type mesg:FilingStatusValueType
Namespace http://www.fixm.aero/messaging/4.1
Annotations
 
Possible values of an operational filing 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>
Diagram
Diagram
Type restriction of string
Facets
enumeration ACCEPTABLE
enumeration NOT_ACCEPTABLE
Used by
Source
 
<simpleType name="FilingStatusValueType">
  <annotation>
    <documentation>Possible values of an operational filing 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>
    </documentation>
  </annotation>
  <restriction base="xs:string">
    <enumeration value="ACCEPTABLE"/>
    <enumeration value="NOT_ACCEPTABLE"/>
  </restriction>
</simpleType>
Complex Type mesg:FlightPlanNegotiationStatusType
Namespace http://www.fixm.aero/messaging/4.1
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]<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>
Diagram
Diagram Extension_xsd.tmp#ExtensibleType_extension Extension_xsd.tmp#ExtensibleType Messaging_xsd.tmp#FlightPlanNegotiationStatusType_filingStatus Messaging_xsd.tmp#FlightPlanNegotiationStatusType_planningStatus
Type extension of fb:ExtensibleType
Type hierarchy
Used by
Model fb:extension{0,2000} , mesg:filingStatus{0,1} , mesg:planningStatus{0,1}
Children fb:extension, mesg:filingStatus, 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]
      <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>
Complex Type mesg:PlanningStatusType
Namespace http://www.fixm.aero/messaging/4.1
Annotations
 
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>
  <rationale>CR 28</rationale>
  <replacement>N/A. See the FIXM Implementation guidance for recommendations about messages.</replacement>
</deprecated>
Diagram
Diagram Extension_xsd.tmp#ExtensibleType_extension Extension_xsd.tmp#ExtensibleType Messaging_xsd.tmp#PlanningStatusType_status Messaging_xsd.tmp#PlanningStatusType_statusReason
Type extension of fb:ExtensibleType
Type hierarchy
Used by
Model fb:extension{0,2000}
Children fb:extension
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 ]<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 
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>
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 ]
      <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>
  <complexContent>
    <extension base="fb:ExtensibleType">
      <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 ]
            <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>
          </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]
            <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>
          </documentation>
        </annotation>
      </attribute>
    </extension>
  </complexContent>
</complexType>
Simple Type mesg:PlanningStatusValueType
Namespace http://www.fixm.aero/messaging/4.1
Annotations
 
The applicable planning status values 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>
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 ]
      <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>
  <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.1
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]<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>
Diagram
Diagram Extension_xsd.tmp#ExtensibleType_extension Extension_xsd.tmp#ExtensibleType Messaging_xsd.tmp#FlightPlanVersionType_referenceVersion Messaging_xsd.tmp#FlightPlanVersionType_version
Type extension of fb:ExtensibleType
Type hierarchy
Used by
Model fb:extension{0,2000} , mesg:referenceVersion{0,1} , mesg:version{0,1}
Children fb:extension, 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]
      <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>
  <complexContent>
    <extension base="fb:ExtensibleType">
      <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.
              <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>
            </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]
              <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>
Complex Type mesg:FlightPlanVersionTypeChoiceType
Namespace http://www.fixm.aero/messaging/4.1
Annotations
 
The FlightPlanVersionChoice class allows specifying an AU flight plan version or 
an ASP flight plan version. [FIXM]
Diagram
Diagram Extension_xsd.tmp#ExtensibleType_extension Extension_xsd.tmp#ExtensibleType Messaging_xsd.tmp#FlightPlanVersionTypeChoiceType_aspFlightPlanVersion Messaging_xsd.tmp#FlightPlanVersionTypeChoiceType_auFlightPlanVersion
Type extension of fb:ExtensibleType
Type hierarchy
Used by
Model fb:extension{0,2000} , (mesg:aspFlightPlanVersion{0,1} | mesg:auFlightPlanVersion{0,1})
Children fb:extension, 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>
  <complexContent>
    <extension base="fb:ExtensibleType">
      <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]. The identifier should begin at one and increase by one with each revision.
              <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="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]. The identifier should begin at one and increase by one with each revision.
              <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>
            </documentation>
          </annotation>
        </element>
      </choice>
    </extension>
  </complexContent>
</complexType>
Complex Type mesg:MessageType
Namespace http://www.fixm.aero/messaging/4.1
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.<deprecated>
  <deletionVersion>Not specified yet.</deletionVersion>
  <deprecationVersion>4.1.0</deprecationVersion>
  <rationale>CR 28</rationale>
</deprecated>
Diagram
Diagram Extension_xsd.tmp#ExtensibleType_extension Extension_xsd.tmp#ExtensibleType Messaging_xsd.tmp#AbstractMessageType_messageDateTime Messaging_xsd.tmp#AbstractMessageType_messageType Messaging_xsd.tmp#AbstractMessageType_deliveryResponsibility Messaging_xsd.tmp#AbstractMessageType_extensions Messaging_xsd.tmp#AbstractMessageType_messageOriginator Messaging_xsd.tmp#AbstractMessageType_recipient 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 fb:extension{0,2000} , mesg:deliveryResponsibility{0,1} , mesg:extensions{0,2000} , mesg:messageOriginator{0,1} , mesg:recipient{0,2000} , 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 fb:extension, mesg:deliveryResponsibility, mesg:extensions, mesg:flight, mesg:flightPlanNegotiationStatus, mesg:flightPlanVersion, mesg:messageOriginator, mesg:recipient, mesg:referenceMessage, mesg:submissionStatus, mesg:uniqueMessageIdentifier
Attributes
QName Type Fixed Default Use Annotation
messageDateTime fb:TimeType optional 
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 
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>
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>
Complex Type mesg:SubmissionStatusType
Namespace http://www.fixm.aero/messaging/4.1
Annotations
 
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>
Diagram
Diagram Extension_xsd.tmp#ExtensibleType_extension Extension_xsd.tmp#ExtensibleType Messaging_xsd.tmp#SubmissionStatusType_status Messaging_xsd.tmp#SubmissionStatusType_statusReason
Type extension of fb:ExtensibleType
Type hierarchy
Used by
Model fb:extension{0,2000}
Children fb:extension
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]<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 
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>
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]
      <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>
  <complexContent>
    <extension base="fb:ExtensibleType">
      <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]
            <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>
      </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]
            <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>
          </documentation>
        </annotation>
      </attribute>
    </extension>
  </complexContent>
</complexType>
Simple Type mesg:SubmissionStatusValueType
Namespace http://www.fixm.aero/messaging/4.1
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.1
Annotations
 
A structure allowing multiple messages to be sent together. [FIXM] The MessageCollection 
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>
Diagram
Diagram Extension_xsd.tmp#ExtensibleType_extension Extension_xsd.tmp#ExtensibleType Messaging_xsd.tmp#AbstractMessageType_messageDateTime Messaging_xsd.tmp#AbstractMessageType_messageType Messaging_xsd.tmp#AbstractMessageType_deliveryResponsibility Messaging_xsd.tmp#AbstractMessageType_extensions Messaging_xsd.tmp#AbstractMessageType_messageOriginator Messaging_xsd.tmp#AbstractMessageType_recipient Messaging_xsd.tmp#AbstractMessageType_uniqueMessageIdentifier Messaging_xsd.tmp#AbstractMessageType Messaging_xsd.tmp#MessageCollectionType_message
Type extension of mesg:AbstractMessageType
Type hierarchy
Used by
Model fb:extension{0,2000} , mesg:deliveryResponsibility{0,1} , mesg:extensions{0,2000} , mesg:messageOriginator{0,1} , mesg:recipient{0,2000} , mesg:uniqueMessageIdentifier{0,1} , mesg:message{0,2000}
Children fb:extension, mesg:deliveryResponsibility, mesg:extensions, mesg:message, mesg:messageOriginator, mesg:recipient, mesg:uniqueMessageIdentifier
Attributes
QName Type Fixed Default Use Annotation
messageDateTime fb:TimeType optional 
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 
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>
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.
      <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="message" type="mesg:AbstractMessageType" minOccurs="0" maxOccurs="2000">
          <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<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>
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
      <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>
    </documentation>
  </annotation>
</attribute>
Attribute mesg:AbstractMessageType / @messageDateTime
Namespace No namespace
Annotations
 
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>
Type fb:TimeType
Properties
use: optional
Facets
pattern -?([1-9][0-9]{3,}|0[0-9]{3})-(0[1-9]|1[0-2])-(0[1-9]|[12][0-9]|3[01])T(([01][0-9]|2[0-3]):[0-5][0-9]:[0-5][0-9](\.[0-9]+)?|(24:00:00(\.0+)?))Z
Used by
Source
 
<attribute name="messageDateTime" type="fb:TimeType" use="optional">
  <annotation>
    <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>
    </documentation>
  </annotation>
</attribute>
Attribute mesg:AbstractMessageType / @messageType
Namespace No namespace
Annotations
 
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>
Type fb:CharacterStringType
Properties
use: optional
Facets
minLength 0
maxLength 4096
Used by
Source
 
<attribute name="messageType" type="fb:CharacterStringType" use="optional">
  <annotation>
    <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>
    </documentation>
  </annotation>
</attribute>
Attribute mesg:FilingStatusType / @status
Namespace No namespace
Annotations
 
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>
Type mesg:FilingStatusValueType
Properties
use: optional
Facets
enumeration ACCEPTABLE
enumeration NOT_ACCEPTABLE
Used by
Complex Type mesg:FilingStatusType
Source
 
<attribute name="status" type="mesg:FilingStatusValueType" use="optional">
  <annotation>
    <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>
    </documentation>
  </annotation>
</attribute>
Attribute mesg:FilingStatusType / @statusReason
Namespace No namespace
Annotations
 
A textual description of the reason a message was rejected. [ICAO Draft FF-ICE Implementation 
Guidance]<deprecated/>
Type fb:CharacterStringType
Properties
use: optional
Facets
minLength 0
maxLength 4096
Used by
Complex Type mesg:FilingStatusType
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]
      <deprecated/>
    </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 ]<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>
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 ]
      <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>
    </documentation>
  </annotation>
</attribute>
Attribute mesg:PlanningStatusType / @statusReason
Namespace No namespace
Annotations
 
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>
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]
      <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>
    </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]<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>
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]
      <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>
</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]<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>
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]
      <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>
    </documentation>
  </annotation>
</attribute>
XML Schema documentation generated by ® XML Editor.