Showing:

Annotations
Attributes
Diagrams
Facets
Instances
Properties
Source
Used by
Main schema FSNViewRS.xsd
Namespace No namespace
Properties
attribute form default: unqualified
element form default: qualified
[ top ]
Element FSNViewRS
Namespace No namespace
Annotations
Subscription view.
Diagram
Diagram FSNViewRS.tmp#FSNViewRS_InfoGroup FSNViewRS.tmp#FSNViewRS_RecordLocator FSNViewRS.tmp#FSNViewRS_FSNSubscription
Properties
content: complex
Model InfoGroup{0,1} , RecordLocator{0,1} , FSNSubscription*
Children FSNSubscription, InfoGroup, RecordLocator
Instance
<FSNViewRS>
  <InfoGroup>{0,1}</InfoGroup>
  <RecordLocator>{0,1}</RecordLocator>
  <FSNSubscription>{0,unbounded}</FSNSubscription>
</FSNViewRS>
Source
<xsd:element name="FSNViewRS">
  <xsd:annotation>
    <xsd:documentation>Subscription view.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:annotation>
        <xsd:documentation>One of the two child elements at least will be always present in the response.</xsd:documentation>
      </xsd:annotation>
      <xsd:element name="InfoGroup" minOccurs="0">
        <xsd:complexType>
          <xsd:sequence>
            <xsd:element name="ForInfo" minOccurs="0" maxOccurs="unbounded">
              <xsd:complexType>
                <xsd:sequence>
                  <xsd:element name="Text" type="xsd:string" maxOccurs="unbounded">
                    <xsd:annotation>
                      <xsd:documentation>Information text</xsd:documentation>
                    </xsd:annotation>
                  </xsd:element>
                </xsd:sequence>
                <xsd:attribute name="Source" type="xsd:string">
                  <xsd:annotation>
                    <xsd:documentation>Identifies the source of this element. In other words where the content originates from. Not limited to GDS, applicable to direct connect as well. Example: 1A, 1V, or other.</xsd:documentation>
                  </xsd:annotation>
                </xsd:attribute>
                <xsd:attribute name="SourceRef" type="xsd:string">
                  <xsd:annotation>
                    <xsd:documentation>PNR Record Locator associated to Source attribute.</xsd:documentation>
                  </xsd:annotation>
                </xsd:attribute>
              </xsd:complexType>
            </xsd:element>
            <xsd:element name="Error" minOccurs="0" maxOccurs="unbounded">
              <xsd:complexType>
                <xsd:sequence>
                  <xsd:element name="Code" type="xsd:string">
                    <xsd:annotation>
                      <xsd:documentation>Error Code</xsd:documentation>
                    </xsd:annotation>
                  </xsd:element>
                  <xsd:element name="Text" type="xsd:string">
                    <xsd:annotation>
                      <xsd:documentation>Error text</xsd:documentation>
                    </xsd:annotation>
                  </xsd:element>
                </xsd:sequence>
                <xsd:attribute name="ErrorType">
                  <xsd:annotation>
                    <xsd:documentation>Type of error. Example: Air</xsd:documentation>
                  </xsd:annotation>
                </xsd:attribute>
                <xsd:attribute name="Source" type="xsd:string">
                  <xsd:annotation>
                    <xsd:documentation>Identifies the source of this element. In other words where the content originates from. Not limited to GDS, applicable to direct connect as well. Example: 1A, 1V, or other.</xsd:documentation>
                  </xsd:annotation>
                </xsd:attribute>
                <xsd:attribute name="SourceRef" type="xsd:string">
                  <xsd:annotation>
                    <xsd:documentation>PNR Record Locator associated to Source attribute.</xsd:documentation>
                  </xsd:annotation>
                </xsd:attribute>
              </xsd:complexType>
            </xsd:element>
          </xsd:sequence>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="RecordLocator" type="xsd:string" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation>Experimental. FUTURE USE. Record locator of the PNR for wich the FSN service is being requested.</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
      <xsd:element name="FSNSubscription" minOccurs="0" maxOccurs="unbounded">
        <xsd:complexType>
          <xsd:complexContent>
            <xsd:extension base="FSNSubscriptionDataType">
              <xsd:sequence>
                <xsd:element name="Subscription">
                  <xsd:complexType>
                    <xsd:sequence>
                      <xsd:element name="ConfirmationID">
                        <xsd:annotation>
                          <xsd:documentation>F16FC2F9</xsd:documentation>
                        </xsd:annotation>
                      </xsd:element>
                      <xsd:element name="TransactionID" minOccurs="0">
                        <xsd:annotation>
                          <xsd:documentation>7529</xsd:documentation>
                        </xsd:annotation>
                      </xsd:element>
                    </xsd:sequence>
                  </xsd:complexType>
                </xsd:element>
              </xsd:sequence>
            </xsd:extension>
          </xsd:complexContent>
        </xsd:complexType>
      </xsd:element>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element FSNViewRS / InfoGroup
Namespace No namespace
Diagram
Diagram FSNViewRS.tmp#FSNViewRS_FSNViewRS_InfoGroup_ForInfo FSNViewRS.tmp#FSNViewRS_FSNViewRS_InfoGroup_Error
Properties
content: complex
minOccurs: 0
Model ForInfo* , Error*
Children Error, ForInfo
Instance
<InfoGroup>
  <ForInfo Source="" SourceRef="">{0,unbounded}</ForInfo>
  <Error ErrorType="" Source="" SourceRef="">{0,unbounded}</Error>
</InfoGroup>
Source
<xsd:element name="InfoGroup" minOccurs="0">
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="ForInfo" minOccurs="0" maxOccurs="unbounded">
        <xsd:complexType>
          <xsd:sequence>
            <xsd:element name="Text" type="xsd:string" maxOccurs="unbounded">
              <xsd:annotation>
                <xsd:documentation>Information text</xsd:documentation>
              </xsd:annotation>
            </xsd:element>
          </xsd:sequence>
          <xsd:attribute name="Source" type="xsd:string">
            <xsd:annotation>
              <xsd:documentation>Identifies the source of this element. In other words where the content originates from. Not limited to GDS, applicable to direct connect as well. Example: 1A, 1V, or other.</xsd:documentation>
            </xsd:annotation>
          </xsd:attribute>
          <xsd:attribute name="SourceRef" type="xsd:string">
            <xsd:annotation>
              <xsd:documentation>PNR Record Locator associated to Source attribute.</xsd:documentation>
            </xsd:annotation>
          </xsd:attribute>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="Error" minOccurs="0" maxOccurs="unbounded">
        <xsd:complexType>
          <xsd:sequence>
            <xsd:element name="Code" type="xsd:string">
              <xsd:annotation>
                <xsd:documentation>Error Code</xsd:documentation>
              </xsd:annotation>
            </xsd:element>
            <xsd:element name="Text" type="xsd:string">
              <xsd:annotation>
                <xsd:documentation>Error text</xsd:documentation>
              </xsd:annotation>
            </xsd:element>
          </xsd:sequence>
          <xsd:attribute name="ErrorType">
            <xsd:annotation>
              <xsd:documentation>Type of error. Example: Air</xsd:documentation>
            </xsd:annotation>
          </xsd:attribute>
          <xsd:attribute name="Source" type="xsd:string">
            <xsd:annotation>
              <xsd:documentation>Identifies the source of this element. In other words where the content originates from. Not limited to GDS, applicable to direct connect as well. Example: 1A, 1V, or other.</xsd:documentation>
            </xsd:annotation>
          </xsd:attribute>
          <xsd:attribute name="SourceRef" type="xsd:string">
            <xsd:annotation>
              <xsd:documentation>PNR Record Locator associated to Source attribute.</xsd:documentation>
            </xsd:annotation>
          </xsd:attribute>
        </xsd:complexType>
      </xsd:element>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element FSNViewRS / InfoGroup / ForInfo
Namespace No namespace
Diagram
Diagram FSNViewRS.tmp#FSNViewRS_FSNViewRS_InfoGroup_FSNViewRS_FSNViewRS_InfoGroup_ForInfo_Source FSNViewRS.tmp#FSNViewRS_FSNViewRS_InfoGroup_FSNViewRS_FSNViewRS_InfoGroup_ForInfo_SourceRef FSNViewRS.tmp#FSNViewRS_FSNViewRS_InfoGroup_FSNViewRS_FSNViewRS_InfoGroup_ForInfo_Text
Properties
content: complex
minOccurs: 0
maxOccurs: unbounded
Model Text+
Children Text
Instance
<ForInfo Source="" SourceRef="">
  <Text>{1,unbounded}</Text>
</ForInfo>
Attributes
QName Type Fixed Default Use Annotation
Source xsd:string optional
Identifies the source of this  element. In other words where the content originates from. Not limited to GDS, applicable to direct connect as well. Example: 1A, 1V, or other.
SourceRef xsd:string optional
PNR Record Locator associated to Source attribute.
Source
<xsd:element name="ForInfo" minOccurs="0" maxOccurs="unbounded">
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="Text" type="xsd:string" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation>Information text</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
    </xsd:sequence>
    <xsd:attribute name="Source" type="xsd:string">
      <xsd:annotation>
        <xsd:documentation>Identifies the source of this element. In other words where the content originates from. Not limited to GDS, applicable to direct connect as well. Example: 1A, 1V, or other.</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:attribute name="SourceRef" type="xsd:string">
      <xsd:annotation>
        <xsd:documentation>PNR Record Locator associated to Source attribute.</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
  </xsd:complexType>
</xsd:element>
[ top ]
Element FSNViewRS / InfoGroup / ForInfo / Text
Namespace No namespace
Annotations
Information text
Diagram
Diagram
Type xsd:string
Properties
content: simple
maxOccurs: unbounded
Source
<xsd:element name="Text" type="xsd:string" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation>Information text</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element FSNViewRS / InfoGroup / Error
Namespace No namespace
Diagram
Diagram FSNViewRS.tmp#FSNViewRS_FSNViewRS_InfoGroup_FSNViewRS_FSNViewRS_InfoGroup_Error_ErrorType FSNViewRS.tmp#FSNViewRS_FSNViewRS_InfoGroup_FSNViewRS_FSNViewRS_InfoGroup_Error_Source FSNViewRS.tmp#FSNViewRS_FSNViewRS_InfoGroup_FSNViewRS_FSNViewRS_InfoGroup_Error_SourceRef FSNViewRS.tmp#FSNViewRS_FSNViewRS_InfoGroup_FSNViewRS_FSNViewRS_InfoGroup_Error_Code FSNViewRS.tmp#FSNViewRS_FSNViewRS_InfoGroup_FSNViewRS_FSNViewRS_InfoGroup_Error_Text
Properties
content: complex
minOccurs: 0
maxOccurs: unbounded
Model Code , Text
Children Code, Text
Instance
<Error ErrorType="" Source="" SourceRef="">
  <Code>{1,1}</Code>
  <Text>{1,1}</Text>
</Error>
Attributes
QName Type Fixed Default Use Annotation
ErrorType optional
Type of error.  Example: Air
Source xsd:string optional
Identifies the source of this  element. In other words where the content originates from. Not limited to GDS, applicable to direct connect as well. Example: 1A, 1V, or other.
SourceRef xsd:string optional
PNR Record Locator associated to Source attribute.
Source
<xsd:element name="Error" minOccurs="0" maxOccurs="unbounded">
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="Code" type="xsd:string">
        <xsd:annotation>
          <xsd:documentation>Error Code</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
      <xsd:element name="Text" type="xsd:string">
        <xsd:annotation>
          <xsd:documentation>Error text</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
    </xsd:sequence>
    <xsd:attribute name="ErrorType">
      <xsd:annotation>
        <xsd:documentation>Type of error. Example: Air</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:attribute name="Source" type="xsd:string">
      <xsd:annotation>
        <xsd:documentation>Identifies the source of this element. In other words where the content originates from. Not limited to GDS, applicable to direct connect as well. Example: 1A, 1V, or other.</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:attribute name="SourceRef" type="xsd:string">
      <xsd:annotation>
        <xsd:documentation>PNR Record Locator associated to Source attribute.</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
  </xsd:complexType>
</xsd:element>
[ top ]
Element FSNViewRS / InfoGroup / Error / Code
Namespace No namespace
Annotations
Error Code
Diagram
Diagram
Type xsd:string
Properties
content: simple
Source
<xsd:element name="Code" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation>Error Code</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element FSNViewRS / InfoGroup / Error / Text
Namespace No namespace
Annotations
Error text
Diagram
Diagram
Type xsd:string
Properties
content: simple
Source
<xsd:element name="Text" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation>Error text</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element FSNViewRS / RecordLocator
Namespace No namespace
Annotations
Experimental. FUTURE USE.

Record locator of the PNR for wich the FSN service is being requested.
Diagram
Diagram
Type xsd:string
Properties
content: simple
minOccurs: 0
Source
<xsd:element name="RecordLocator" type="xsd:string" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>Experimental. FUTURE USE. Record locator of the PNR for wich the FSN service is being requested.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element FSNViewRS / FSNSubscription
Namespace No namespace
Diagram
Diagram FSNViewRS.tmp#FSNSubscriptionDataType_TravelerElementNumber FSNViewRS.tmp#FSNSubscriptionDataType_NickName FSNViewRS.tmp#FSNSubscriptionDataType_Departure FSNViewRS.tmp#FSNSubscriptionDataType_Arrival FSNViewRS.tmp#FSNSubscriptionDataType_Carrier FSNViewRS.tmp#FSNSubscriptionDataType_NotifyByText FSNViewRS.tmp#FSNSubscriptionDataType_NotifyByVoice FSNViewRS.tmp#FSNSubscriptionDataType_NotifyByEMail FSNViewRS.tmp#FSNSubscriptionDataType_NotificationScope FSNViewRS.tmp#FSNSubscriptionDataType_Schedule FSNViewRS.tmp#FSNSubscriptionDataType FSNViewRS.tmp#FSNViewRS_FSNViewRS_FSNSubscription_Subscription
Type extension of FSNSubscriptionDataType
Type hierarchy
Properties
content: complex
minOccurs: 0
maxOccurs: unbounded
Model TravelerElementNumber{0,1} , NickName{0,1} , Departure , Arrival , Carrier , (NotifyByText | NotifyByVoice | NotifyByEMail) , NotificationScope , Schedule , Subscription
Children Arrival, Carrier, Departure, NickName, NotificationScope, NotifyByEMail, NotifyByText, NotifyByVoice, Schedule, Subscription, TravelerElementNumber
Instance
<FSNSubscription>
  <TravelerElementNumber>{0,1}</TravelerElementNumber>
  <NickName>{0,1}</NickName>
  <Departure>{1,1}</Departure>
  <Arrival>{1,1}</Arrival>
  <Carrier>{1,1}</Carrier>
  <NotifyByText>{1,1}</NotifyByText>
  <NotifyByVoice>{1,1}</NotifyByVoice>
  <NotifyByEMail>{1,1}</NotifyByEMail>
  <NotificationScope>{1,1}</NotificationScope>
  <Schedule>{1,1}</Schedule>
  <Subscription>{1,1}</Subscription>
</FSNSubscription>
Source
<xsd:element name="FSNSubscription" minOccurs="0" maxOccurs="unbounded">
  <xsd:complexType>
    <xsd:complexContent>
      <xsd:extension base="FSNSubscriptionDataType">
        <xsd:sequence>
          <xsd:element name="Subscription">
            <xsd:complexType>
              <xsd:sequence>
                <xsd:element name="ConfirmationID">
                  <xsd:annotation>
                    <xsd:documentation>F16FC2F9</xsd:documentation>
                  </xsd:annotation>
                </xsd:element>
                <xsd:element name="TransactionID" minOccurs="0">
                  <xsd:annotation>
                    <xsd:documentation>7529</xsd:documentation>
                  </xsd:annotation>
                </xsd:element>
              </xsd:sequence>
            </xsd:complexType>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
</xsd:element>
[ top ]
Element FSNSubscriptionDataType / TravelerElementNumber
Namespace No namespace
Annotations
Element number of traveler associated to this item.  Example: 1
Diagram
Diagram
Properties
minOccurs: 0
Source
<xsd:element name="TravelerElementNumber" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>Element number of traveler associated to this item. Example: 1</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element FSNSubscriptionDataType / NickName
Namespace No namespace
Annotations
Subscription nickname
Example: MY TRIP TO LAX
Diagram
Diagram
Type xsd:string
Properties
content: simple
minOccurs: 0
Source
<xsd:element name="NickName" type="xsd:string" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>Subscription nickname Example: MY TRIP TO LAX</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element FSNSubscriptionDataType / Departure
Namespace No namespace
Annotations
Departure point definition of the flight. Consists of the departure airport code (3-letter IATA) and departure date (YYYY-MM-DD)
Diagram
Diagram FSNViewRS.tmp#FSNSubscriptionDataType_FSNSubscriptionDataType_Departure_AirportCode FSNViewRS.tmp#FSNSubscriptionDataType_FSNSubscriptionDataType_Departure_Date
Properties
content: complex
Model AirportCode , Date
Children AirportCode, Date
Instance
<Departure>
  <AirportCode>{1,1}</AirportCode>
  <Date>{1,1}</Date>
</Departure>
Source
<xsd:element name="Departure">
  <xsd:annotation>
    <xsd:documentation>Departure point definition of the flight. Consists of the departure airport code (3-letter IATA) and departure date (YYYY-MM-DD)</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="AirportCode">
        <xsd:annotation>
          <xsd:documentation>3-letter IATA airport code. Example: MIA</xsd:documentation>
        </xsd:annotation>
        <xsd:simpleType>
          <xsd:restriction base="xsd:string">
            <xsd:length value="3"/>
            <xsd:pattern value="[A-Z|0-9]{3}"/>
          </xsd:restriction>
        </xsd:simpleType>
      </xsd:element>
      <xsd:element name="Date" type="xsd:date">
        <xsd:annotation>
          <xsd:documentation>Departure date of the flight. format to be used: YYYY-MM-DD. Example: 2010-12-24</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element FSNSubscriptionDataType / Departure / AirportCode
Namespace No namespace
Annotations
3-letter IATA airport code.
Example: MIA
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
Facets
length 3
pattern [A-Z|0-9]{3}
Source
<xsd:element name="AirportCode">
  <xsd:annotation>
    <xsd:documentation>3-letter IATA airport code. Example: MIA</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:length value="3"/>
      <xsd:pattern value="[A-Z|0-9]{3}"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element FSNSubscriptionDataType / Departure / Date
Namespace No namespace
Annotations
Departure date of the flight. format to be used: YYYY-MM-DD.
Example: 2010-12-24
Diagram
Diagram
Type xsd:date
Properties
content: simple
Source
<xsd:element name="Date" type="xsd:date">
  <xsd:annotation>
    <xsd:documentation>Departure date of the flight. format to be used: YYYY-MM-DD. Example: 2010-12-24</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element FSNSubscriptionDataType / Arrival
Namespace No namespace
Annotations
Arrival point definition of the  flight.
Diagram
Diagram FSNViewRS.tmp#FSNSubscriptionDataType_FSNSubscriptionDataType_Arrival_AirportCode FSNViewRS.tmp#FSNSubscriptionDataType_FSNSubscriptionDataType_Arrival_Date
Properties
content: complex
Model AirportCode , Date
Children AirportCode, Date
Instance
<Arrival>
  <AirportCode>{1,1}</AirportCode>
  <Date>{1,1}</Date>
</Arrival>
Source
<xsd:element name="Arrival">
  <xsd:annotation>
    <xsd:documentation>Arrival point definition of the flight.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="AirportCode">
        <xsd:annotation>
          <xsd:documentation>3-letter IATA airport code. Example: MIA</xsd:documentation>
        </xsd:annotation>
        <xsd:simpleType>
          <xsd:restriction base="xsd:string">
            <xsd:length value="3"/>
            <xsd:pattern value="[A-Z|0-9]{3}"/>
          </xsd:restriction>
        </xsd:simpleType>
      </xsd:element>
      <xsd:element name="Date" type="xsd:date">
        <xsd:annotation>
          <xsd:documentation>Departure date of the flight. format to be used: YYYY-MM-DD. Example: 2010-12-24</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element FSNSubscriptionDataType / Arrival / AirportCode
Namespace No namespace
Annotations
3-letter IATA airport code.
Example: MIA
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
Facets
length 3
pattern [A-Z|0-9]{3}
Source
<xsd:element name="AirportCode">
  <xsd:annotation>
    <xsd:documentation>3-letter IATA airport code. Example: MIA</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:length value="3"/>
      <xsd:pattern value="[A-Z|0-9]{3}"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element FSNSubscriptionDataType / Arrival / Date
Namespace No namespace
Annotations
Departure date of the flight. format to be used: YYYY-MM-DD.
Example: 2010-12-24
Diagram
Diagram
Type xsd:date
Properties
content: simple
Source
<xsd:element name="Date" type="xsd:date">
  <xsd:annotation>
    <xsd:documentation>Departure date of the flight. format to be used: YYYY-MM-DD. Example: 2010-12-24</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element FSNSubscriptionDataType / Carrier
Namespace No namespace
Annotations
Defines airline code and the flight number for which status notofication is being requested.
Diagram
Diagram FSNViewRS.tmp#FSNSubscriptionDataType_FSNSubscriptionDataType_Carrier_AirlineCode FSNViewRS.tmp#FSNSubscriptionDataType_FSNSubscriptionDataType_Carrier_FlightNumber
Properties
content: complex
Model AirlineCode , FlightNumber
Children AirlineCode, FlightNumber
Instance
<Carrier>
  <AirlineCode>{1,1}</AirlineCode>
  <FlightNumber Suffix="">{1,1}</FlightNumber>
</Carrier>
Source
<xsd:element name="Carrier">
  <xsd:annotation>
    <xsd:documentation>Defines airline code and the flight number for which status notofication is being requested.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="AirlineCode">
        <xsd:annotation>
          <xsd:documentation>2-letter IATA airline code. Example: AA</xsd:documentation>
        </xsd:annotation>
        <xsd:simpleType>
          <xsd:restriction base="xsd:string">
            <xsd:length value="2"/>
            <xsd:pattern value="[A-Z|0-9]{2}"/>
          </xsd:restriction>
        </xsd:simpleType>
      </xsd:element>
      <xsd:element name="FlightNumber" type="FlightNumberWithSuffixType"/>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element FSNSubscriptionDataType / Carrier / AirlineCode
Namespace No namespace
Annotations
2-letter IATA airline code.
Example: AA
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
Facets
length 2
pattern [A-Z|0-9]{2}
Source
<xsd:element name="AirlineCode">
  <xsd:annotation>
    <xsd:documentation>2-letter IATA airline code. Example: AA</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:length value="2"/>
      <xsd:pattern value="[A-Z|0-9]{2}"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element FSNSubscriptionDataType / Carrier / FlightNumber
Namespace No namespace
Diagram
Diagram FSNViewRS.tmp#FlightNumberType FSNViewRS.tmp#FlightNumberWithSuffixType_Suffix FSNViewRS.tmp#FlightNumberWithSuffixType
Type FlightNumberWithSuffixType
Type hierarchy
Properties
content: complex
Attributes
QName Type Fixed Default Use Annotation
Suffix restriction of xsd:string optional
Flight number alpha qualifier.  
Values are:
A
B
C
D

Example: A
Source
<xsd:element name="FlightNumber" type="FlightNumberWithSuffixType"/>
[ top ]
Element FSNSubscriptionDataType / NotifyByText
Namespace No namespace
Annotations
Will result in a short text message (SMS) sent to the specified phone number.
Diagram
Diagram FSNViewRS.tmp#FSNSubscriptionDataType_FSNSubscriptionDataType_NotifyByText_Address
Properties
content: complex
Model Address
Children Address
Instance
<NotifyByText>
  <Address>{1,1}</Address>
</NotifyByText>
Source
<xsd:element name="NotifyByText">
  <xsd:annotation>
    <xsd:documentation>Will result in a short text message (SMS) sent to the specified phone number.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="Address">
        <xsd:annotation>
          <xsd:documentation>The format is phonenumber@telcosuffix Example: 305868686@txt.att.net (AT@T) or 3838383@vtext.com (Verizon) Other US carrier examples: @messaging.nextel.com - NEXTEL @messaging.sprintpcs.com - Sprint @tmomail.net T-Mobile</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element FSNSubscriptionDataType / NotifyByText / Address
Namespace No namespace
Annotations
The format is phonenumber@telcosuffix

Example: 305868686@txt.att.net (AT@T)

or

3838383@vtext.com (Verizon)

Other US carrier examples:

@messaging.nextel.com - NEXTEL

@messaging.sprintpcs.com - Sprint

@tmomail.net T-Mobile
Diagram
Diagram
Source
<xsd:element name="Address">
  <xsd:annotation>
    <xsd:documentation>The format is phonenumber@telcosuffix Example: 305868686@txt.att.net (AT@T) or 3838383@vtext.com (Verizon) Other US carrier examples: @messaging.nextel.com - NEXTEL @messaging.sprintpcs.com - Sprint @tmomail.net T-Mobile</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element FSNSubscriptionDataType / NotifyByVoice
Namespace No namespace
Annotations
Will result in call or a voice message (if not answered) to the specified phone number.
Diagram
Diagram FSNViewRS.tmp#FSNSubscriptionDataType_FSNSubscriptionDataType_NotifyByVoice_PhoneNumber
Properties
content: complex
Model PhoneNumber
Children PhoneNumber
Instance
<NotifyByVoice>
  <PhoneNumber>{1,1}</PhoneNumber>
</NotifyByVoice>
Source
<xsd:element name="NotifyByVoice">
  <xsd:annotation>
    <xsd:documentation>Will result in call or a voice message (if not answered) to the specified phone number.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="PhoneNumber"/>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element FSNSubscriptionDataType / NotifyByVoice / PhoneNumber
Namespace No namespace
Diagram
Diagram
Source
<xsd:element name="PhoneNumber"/>
[ top ]
Element FSNSubscriptionDataType / NotifyByEMail
Namespace No namespace
Annotations
Will result in an e-mail that will be sent to the specified e-mail address.
Diagram
Diagram FSNViewRS.tmp#FSNSubscriptionDataType_FSNSubscriptionDataType_NotifyByEMail_Address
Properties
content: complex
Model Address
Children Address
Instance
<NotifyByEMail>
  <Address>{1,1}</Address>
</NotifyByEMail>
Source
<xsd:element name="NotifyByEMail">
  <xsd:annotation>
    <xsd:documentation>Will result in an e-mail that will be sent to the specified e-mail address.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="Address">
        <xsd:annotation>
          <xsd:documentation>e-Mail address. Example: some.thing@there-dot.com</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element FSNSubscriptionDataType / NotifyByEMail / Address
Namespace No namespace
Annotations
e-Mail address.

Example: some.thing@there-dot.com
Diagram
Diagram
Source
<xsd:element name="Address">
  <xsd:annotation>
    <xsd:documentation>e-Mail address. Example: some.thing@there-dot.com</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element FSNSubscriptionDataType / NotificationScope
Namespace No namespace
Annotations
Defines what kind of notifications are requested.
Diagram
Diagram FSNViewRS.tmp#FSNSubscriptionDataType_FSNSubscriptionDataType_NotificationScope_DepartureStatus FSNViewRS.tmp#FSNSubscriptionDataType_FSNSubscriptionDataType_NotificationScope_ArrivalStatus FSNViewRS.tmp#FSNSubscriptionDataType_FSNSubscriptionDataType_NotificationScope_ConnectionStatus FSNViewRS.tmp#FSNSubscriptionDataType_FSNSubscriptionDataType_NotificationScope_GateStatus
Properties
content: complex
Model DepartureStatus , ArrivalStatus , ConnectionStatus{0,1} , GateStatus
Children ArrivalStatus, ConnectionStatus, DepartureStatus, GateStatus
Instance
<NotificationScope>
  <DepartureStatus>{1,1}</DepartureStatus>
  <ArrivalStatus>{1,1}</ArrivalStatus>
  <ConnectionStatus>{0,1}</ConnectionStatus>
  <GateStatus>{1,1}</GateStatus>
</NotificationScope>
Source
<xsd:element name="NotificationScope">
  <xsd:annotation>
    <xsd:documentation>Defines what kind of notifications are requested.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="DepartureStatus" default="Y">
        <xsd:annotation>
          <xsd:documentation>Departure information to be inlcuded in the notification messages. To request this information use the positive value. Possible values are: Y = provide info N = don't povide info Example: Y</xsd:documentation>
        </xsd:annotation>
        <xsd:simpleType>
          <xsd:restriction base="xsd:string">
            <xsd:length value="1"/>
            <xsd:enumeration value="Y"/>
            <xsd:enumeration value="N"/>
          </xsd:restriction>
        </xsd:simpleType>
      </xsd:element>
      <xsd:element name="ArrivalStatus" default="Y">
        <xsd:annotation>
          <xsd:documentation>Arrival information to be included in the notification messages. To request this information use the positive value. Possible values are: Y = provide info N = don't povide info Example: Y</xsd:documentation>
        </xsd:annotation>
        <xsd:simpleType>
          <xsd:restriction base="xsd:string">
            <xsd:enumeration value="Y"/>
            <xsd:enumeration value="N"/>
          </xsd:restriction>
        </xsd:simpleType>
      </xsd:element>
      <xsd:element name="ConnectionStatus" default="Y" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation>Future Use (experimental) Always set to "N" (or omit node) until future support is implemented A "Y" value will be ignored at this time Requests notification for connections status (changes) this info would be inlcuded at the arrival in a connection scenario so that must current information about connecting flight is provided in the notification. Possible values are: Y = provide info N = don't povide info Example: Y</xsd:documentation>
        </xsd:annotation>
        <xsd:simpleType>
          <xsd:restriction base="xsd:string">
            <xsd:enumeration value="Y"/>
            <xsd:enumeration value="N"/>
          </xsd:restriction>
        </xsd:simpleType>
      </xsd:element>
      <xsd:element name="GateStatus" default="Y">
        <xsd:annotation>
          <xsd:documentation>Gate information (such as gate changes) to be included in the notification messages. To request this information use the positive value. Possible values are: Y = provide info N = don't povide info Example: Y</xsd:documentation>
        </xsd:annotation>
        <xsd:simpleType>
          <xsd:restriction base="xsd:string">
            <xsd:enumeration value="Y"/>
            <xsd:enumeration value="N"/>
          </xsd:restriction>
        </xsd:simpleType>
      </xsd:element>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element FSNSubscriptionDataType / NotificationScope / DepartureStatus
Namespace No namespace
Annotations
Departure information to be inlcuded in the notification messages. To request this information use the positive value.
Possible values are:
Y = provide info
N = don't povide info

Example: Y
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
default: Y
Facets
length 1
enumeration Y
enumeration N
Source
<xsd:element name="DepartureStatus" default="Y">
  <xsd:annotation>
    <xsd:documentation>Departure information to be inlcuded in the notification messages. To request this information use the positive value. Possible values are: Y = provide info N = don't povide info Example: Y</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:length value="1"/>
      <xsd:enumeration value="Y"/>
      <xsd:enumeration value="N"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element FSNSubscriptionDataType / NotificationScope / ArrivalStatus
Namespace No namespace
Annotations
Arrival information to be included in the notification messages. To request this information use the positive value.
Possible values are:
Y = provide info
N = don't povide info

Example: Y
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
default: Y
Facets
enumeration Y
enumeration N
Source
<xsd:element name="ArrivalStatus" default="Y">
  <xsd:annotation>
    <xsd:documentation>Arrival information to be included in the notification messages. To request this information use the positive value. Possible values are: Y = provide info N = don't povide info Example: Y</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:enumeration value="Y"/>
      <xsd:enumeration value="N"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element FSNSubscriptionDataType / NotificationScope / ConnectionStatus
Namespace No namespace
Annotations
Future Use (experimental)
Always set to "N" (or omit node) until future support is implemented

A "Y" value will be ignored at this time

Requests notification for connections status (changes) this info would be inlcuded at the arrival in a connection scenario so that must current information about connecting flight is provided in the notification.
Possible values are:
Y = provide info
N = don't povide info

Example: Y
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
minOccurs: 0
default: Y
Facets
enumeration Y
enumeration N
Source
<xsd:element name="ConnectionStatus" default="Y" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>Future Use (experimental) Always set to "N" (or omit node) until future support is implemented A "Y" value will be ignored at this time Requests notification for connections status (changes) this info would be inlcuded at the arrival in a connection scenario so that must current information about connecting flight is provided in the notification. Possible values are: Y = provide info N = don't povide info Example: Y</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:enumeration value="Y"/>
      <xsd:enumeration value="N"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element FSNSubscriptionDataType / NotificationScope / GateStatus
Namespace No namespace
Annotations
Gate information (such as gate changes) to be included in the notification messages. To request this information use the positive value.
Possible values are:
Y = provide info
N = don't povide info

Example: Y
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
default: Y
Facets
enumeration Y
enumeration N
Source
<xsd:element name="GateStatus" default="Y">
  <xsd:annotation>
    <xsd:documentation>Gate information (such as gate changes) to be included in the notification messages. To request this information use the positive value. Possible values are: Y = provide info N = don't povide info Example: Y</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:enumeration value="Y"/>
      <xsd:enumeration value="N"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element FSNSubscriptionDataType / Schedule
Namespace No namespace
Annotations
Defines possible alternative notification timing modes that can be subscribed to.
Diagram
Diagram FSNViewRS.tmp#FSNSubscriptionDataType_FSNSubscriptionDataType_Schedule_Timing
Properties
content: complex
Model Timing
Children Timing
Instance
<Schedule>
  <Timing>{1,1}</Timing>
</Schedule>
Source
<xsd:element name="Schedule">
  <xsd:annotation>
    <xsd:documentation>Defines possible alternative notification timing modes that can be subscribed to.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:choice>
      <xsd:element name="Timing">
        <xsd:annotation>
          <xsd:documentation>Idenifies how far in advance the notfications selected above will be provided. Enumerated values in MINUTES. Possible values are: 30 60 120 180 240 Example: 60</xsd:documentation>
        </xsd:annotation>
        <xsd:simpleType>
          <xsd:restriction base="xsd:integer"/>
        </xsd:simpleType>
      </xsd:element>
    </xsd:choice>
  </xsd:complexType>
</xsd:element>
[ top ]
Element FSNSubscriptionDataType / Schedule / Timing
Namespace No namespace
Annotations
Idenifies how far in advance the notfications selected above will be provided. Enumerated values in MINUTES. Possible values are:
30
60
120
180
240

Example: 60
Diagram
Diagram
Type xsd:integer
Properties
content: simple
Source
<xsd:element name="Timing">
  <xsd:annotation>
    <xsd:documentation>Idenifies how far in advance the notfications selected above will be provided. Enumerated values in MINUTES. Possible values are: 30 60 120 180 240 Example: 60</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:integer"/>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element FSNViewRS / FSNSubscription / Subscription
Namespace No namespace
Diagram
Diagram FSNViewRS.tmp#FSNViewRS_FSNViewRS_FSNSubscription_FSNViewRS_FSNViewRS_FSNSubscription_Subscription_ConfirmationID FSNViewRS.tmp#FSNViewRS_FSNViewRS_FSNSubscription_FSNViewRS_FSNViewRS_FSNSubscription_Subscription_TransactionID
Properties
content: complex
Model ConfirmationID , TransactionID{0,1}
Children ConfirmationID, TransactionID
Instance
<Subscription>
  <ConfirmationID>{1,1}</ConfirmationID>
  <TransactionID>{0,1}</TransactionID>
</Subscription>
Source
<xsd:element name="Subscription">
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="ConfirmationID">
        <xsd:annotation>
          <xsd:documentation>F16FC2F9</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
      <xsd:element name="TransactionID" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation>7529</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element FSNViewRS / FSNSubscription / Subscription / ConfirmationID
Namespace No namespace
Annotations
F16FC2F9
Diagram
Diagram
Source
<xsd:element name="ConfirmationID">
  <xsd:annotation>
    <xsd:documentation>F16FC2F9</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element FSNViewRS / FSNSubscription / Subscription / TransactionID
Namespace No namespace
Annotations
7529
Diagram
Diagram
Properties
minOccurs: 0
Source
<xsd:element name="TransactionID" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>7529</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Complex Type FSNSubscriptionDataType
Namespace No namespace
Diagram
Diagram FSNViewRS.tmp#FSNSubscriptionDataType_TravelerElementNumber FSNViewRS.tmp#FSNSubscriptionDataType_NickName FSNViewRS.tmp#FSNSubscriptionDataType_Departure FSNViewRS.tmp#FSNSubscriptionDataType_Arrival FSNViewRS.tmp#FSNSubscriptionDataType_Carrier FSNViewRS.tmp#FSNSubscriptionDataType_NotifyByText FSNViewRS.tmp#FSNSubscriptionDataType_NotifyByVoice FSNViewRS.tmp#FSNSubscriptionDataType_NotifyByEMail FSNViewRS.tmp#FSNSubscriptionDataType_NotificationScope FSNViewRS.tmp#FSNSubscriptionDataType_Schedule
Used by
Model TravelerElementNumber{0,1} , NickName{0,1} , Departure , Arrival , Carrier , (NotifyByText | NotifyByVoice | NotifyByEMail) , NotificationScope , Schedule
Children Arrival, Carrier, Departure, NickName, NotificationScope, NotifyByEMail, NotifyByText, NotifyByVoice, Schedule, TravelerElementNumber
Source
<xsd:complexType name="FSNSubscriptionDataType">
  <xsd:sequence>
    <xsd:element name="TravelerElementNumber" minOccurs="0">
      <xsd:annotation>
        <xsd:documentation>Element number of traveler associated to this item. Example: 1</xsd:documentation>
      </xsd:annotation>
    </xsd:element>
    <xsd:element name="NickName" type="xsd:string" minOccurs="0">
      <xsd:annotation>
        <xsd:documentation>Subscription nickname Example: MY TRIP TO LAX</xsd:documentation>
      </xsd:annotation>
    </xsd:element>
    <xsd:element name="Departure">
      <xsd:annotation>
        <xsd:documentation>Departure point definition of the flight. Consists of the departure airport code (3-letter IATA) and departure date (YYYY-MM-DD)</xsd:documentation>
      </xsd:annotation>
      <xsd:complexType>
        <xsd:sequence>
          <xsd:element name="AirportCode">
            <xsd:annotation>
              <xsd:documentation>3-letter IATA airport code. Example: MIA</xsd:documentation>
            </xsd:annotation>
            <xsd:simpleType>
              <xsd:restriction base="xsd:string">
                <xsd:length value="3"/>
                <xsd:pattern value="[A-Z|0-9]{3}"/>
              </xsd:restriction>
            </xsd:simpleType>
          </xsd:element>
          <xsd:element name="Date" type="xsd:date">
            <xsd:annotation>
              <xsd:documentation>Departure date of the flight. format to be used: YYYY-MM-DD. Example: 2010-12-24</xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:complexType>
    </xsd:element>
    <xsd:element name="Arrival">
      <xsd:annotation>
        <xsd:documentation>Arrival point definition of the flight.</xsd:documentation>
      </xsd:annotation>
      <xsd:complexType>
        <xsd:sequence>
          <xsd:element name="AirportCode">
            <xsd:annotation>
              <xsd:documentation>3-letter IATA airport code. Example: MIA</xsd:documentation>
            </xsd:annotation>
            <xsd:simpleType>
              <xsd:restriction base="xsd:string">
                <xsd:length value="3"/>
                <xsd:pattern value="[A-Z|0-9]{3}"/>
              </xsd:restriction>
            </xsd:simpleType>
          </xsd:element>
          <xsd:element name="Date" type="xsd:date">
            <xsd:annotation>
              <xsd:documentation>Departure date of the flight. format to be used: YYYY-MM-DD. Example: 2010-12-24</xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:complexType>
    </xsd:element>
    <xsd:element name="Carrier">
      <xsd:annotation>
        <xsd:documentation>Defines airline code and the flight number for which status notofication is being requested.</xsd:documentation>
      </xsd:annotation>
      <xsd:complexType>
        <xsd:sequence>
          <xsd:element name="AirlineCode">
            <xsd:annotation>
              <xsd:documentation>2-letter IATA airline code. Example: AA</xsd:documentation>
            </xsd:annotation>
            <xsd:simpleType>
              <xsd:restriction base="xsd:string">
                <xsd:length value="2"/>
                <xsd:pattern value="[A-Z|0-9]{2}"/>
              </xsd:restriction>
            </xsd:simpleType>
          </xsd:element>
          <xsd:element name="FlightNumber" type="FlightNumberWithSuffixType"/>
        </xsd:sequence>
      </xsd:complexType>
    </xsd:element>
    <xsd:choice>
      <xsd:element name="NotifyByText">
        <xsd:annotation>
          <xsd:documentation>Will result in a short text message (SMS) sent to the specified phone number.</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:sequence>
            <xsd:element name="Address">
              <xsd:annotation>
                <xsd:documentation>The format is phonenumber@telcosuffix Example: 305868686@txt.att.net (AT@T) or 3838383@vtext.com (Verizon) Other US carrier examples: @messaging.nextel.com - NEXTEL @messaging.sprintpcs.com - Sprint @tmomail.net T-Mobile</xsd:documentation>
              </xsd:annotation>
            </xsd:element>
          </xsd:sequence>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="NotifyByVoice">
        <xsd:annotation>
          <xsd:documentation>Will result in call or a voice message (if not answered) to the specified phone number.</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:sequence>
            <xsd:element name="PhoneNumber"/>
          </xsd:sequence>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="NotifyByEMail">
        <xsd:annotation>
          <xsd:documentation>Will result in an e-mail that will be sent to the specified e-mail address.</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:sequence>
            <xsd:element name="Address">
              <xsd:annotation>
                <xsd:documentation>e-Mail address. Example: some.thing@there-dot.com</xsd:documentation>
              </xsd:annotation>
            </xsd:element>
          </xsd:sequence>
        </xsd:complexType>
      </xsd:element>
    </xsd:choice>
    <xsd:element name="NotificationScope">
      <xsd:annotation>
        <xsd:documentation>Defines what kind of notifications are requested.</xsd:documentation>
      </xsd:annotation>
      <xsd:complexType>
        <xsd:sequence>
          <xsd:element name="DepartureStatus" default="Y">
            <xsd:annotation>
              <xsd:documentation>Departure information to be inlcuded in the notification messages. To request this information use the positive value. Possible values are: Y = provide info N = don't povide info Example: Y</xsd:documentation>
            </xsd:annotation>
            <xsd:simpleType>
              <xsd:restriction base="xsd:string">
                <xsd:length value="1"/>
                <xsd:enumeration value="Y"/>
                <xsd:enumeration value="N"/>
              </xsd:restriction>
            </xsd:simpleType>
          </xsd:element>
          <xsd:element name="ArrivalStatus" default="Y">
            <xsd:annotation>
              <xsd:documentation>Arrival information to be included in the notification messages. To request this information use the positive value. Possible values are: Y = provide info N = don't povide info Example: Y</xsd:documentation>
            </xsd:annotation>
            <xsd:simpleType>
              <xsd:restriction base="xsd:string">
                <xsd:enumeration value="Y"/>
                <xsd:enumeration value="N"/>
              </xsd:restriction>
            </xsd:simpleType>
          </xsd:element>
          <xsd:element name="ConnectionStatus" default="Y" minOccurs="0">
            <xsd:annotation>
              <xsd:documentation>Future Use (experimental) Always set to "N" (or omit node) until future support is implemented A "Y" value will be ignored at this time Requests notification for connections status (changes) this info would be inlcuded at the arrival in a connection scenario so that must current information about connecting flight is provided in the notification. Possible values are: Y = provide info N = don't povide info Example: Y</xsd:documentation>
            </xsd:annotation>
            <xsd:simpleType>
              <xsd:restriction base="xsd:string">
                <xsd:enumeration value="Y"/>
                <xsd:enumeration value="N"/>
              </xsd:restriction>
            </xsd:simpleType>
          </xsd:element>
          <xsd:element name="GateStatus" default="Y">
            <xsd:annotation>
              <xsd:documentation>Gate information (such as gate changes) to be included in the notification messages. To request this information use the positive value. Possible values are: Y = provide info N = don't povide info Example: Y</xsd:documentation>
            </xsd:annotation>
            <xsd:simpleType>
              <xsd:restriction base="xsd:string">
                <xsd:enumeration value="Y"/>
                <xsd:enumeration value="N"/>
              </xsd:restriction>
            </xsd:simpleType>
          </xsd:element>
        </xsd:sequence>
      </xsd:complexType>
    </xsd:element>
    <xsd:element name="Schedule">
      <xsd:annotation>
        <xsd:documentation>Defines possible alternative notification timing modes that can be subscribed to.</xsd:documentation>
      </xsd:annotation>
      <xsd:complexType>
        <xsd:choice>
          <xsd:element name="Timing">
            <xsd:annotation>
              <xsd:documentation>Idenifies how far in advance the notfications selected above will be provided. Enumerated values in MINUTES. Possible values are: 30 60 120 180 240 Example: 60</xsd:documentation>
            </xsd:annotation>
            <xsd:simpleType>
              <xsd:restriction base="xsd:integer"/>
            </xsd:simpleType>
          </xsd:element>
        </xsd:choice>
      </xsd:complexType>
    </xsd:element>
  </xsd:sequence>
</xsd:complexType>
[ top ]
Complex Type FlightNumberWithSuffixType
Namespace No namespace
Annotations
A flight number with optional suffix letter. Flight numbers are integer values within the range of [0,9999]. 

Example: 1234
Diagram
Diagram FSNViewRS.tmp#FlightNumberType FSNViewRS.tmp#FlightNumberWithSuffixType_Suffix
Type extension of FlightNumberType
Type hierarchy
Used by
Attributes
QName Type Fixed Default Use Annotation
Suffix restriction of xsd:string optional
Flight number alpha qualifier.  
Values are:
A
B
C
D

Example: A
Source
<xsd:complexType name="FlightNumberWithSuffixType">
  <xsd:annotation>
    <xsd:documentation>A flight number with optional suffix letter. Flight numbers are integer values within the range of [0,9999]. Example: 1234</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleContent>
    <xsd:extension base="FlightNumberType">
      <xsd:attribute name="Suffix" use="optional">
        <xsd:annotation>
          <xsd:documentation>Flight number alpha qualifier. Values are: A B C D Example: A</xsd:documentation>
        </xsd:annotation>
        <xsd:simpleType>
          <xsd:restriction base="xsd:string">
            <xsd:enumeration value="A"/>
            <xsd:enumeration value="B"/>
            <xsd:enumeration value="C"/>
            <xsd:enumeration value="D"/>
          </xsd:restriction>
        </xsd:simpleType>
      </xsd:attribute>
    </xsd:extension>
  </xsd:simpleContent>
</xsd:complexType>
[ top ]
Simple Type FlightNumberType
Namespace No namespace
Annotations
A flight number. Flight numbers are integer values within the range of [0-9999]. Example: 1234
Diagram
Diagram
Type restriction of xsd:integer
Facets
maxInclusive 9999
minInclusive 0
Used by
Source
<xsd:simpleType name="FlightNumberType">
  <xsd:annotation>
    <xsd:documentation>A flight number. Flight numbers are integer values within the range of [0-9999]. Example: 1234</xsd:documentation>
  </xsd:annotation>
  <xsd:restriction base="xsd:integer">
    <xsd:minInclusive value="0"/>
    <xsd:maxInclusive value="9999"/>
  </xsd:restriction>
</xsd:simpleType>
[ top ]
Attribute FSNViewRS / InfoGroup / ForInfo / @Source
Namespace No namespace
Annotations
Identifies the source of this  element. In other words where the content originates from. Not limited to GDS, applicable to direct connect as well. Example: 1A, 1V, or other.
Type xsd:string
Properties
content: simple
Used by
Source
<xsd:attribute name="Source" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation>Identifies the source of this element. In other words where the content originates from. Not limited to GDS, applicable to direct connect as well. Example: 1A, 1V, or other.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
[ top ]
Attribute FSNViewRS / InfoGroup / ForInfo / @SourceRef
Namespace No namespace
Annotations
PNR Record Locator associated to Source attribute.
Type xsd:string
Properties
content: simple
Used by
Source
<xsd:attribute name="SourceRef" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation>PNR Record Locator associated to Source attribute.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
[ top ]
Attribute FSNViewRS / InfoGroup / Error / @ErrorType
Namespace No namespace
Annotations
Type of error.  Example: Air
Used by
Source
<xsd:attribute name="ErrorType">
  <xsd:annotation>
    <xsd:documentation>Type of error. Example: Air</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
[ top ]
Attribute FSNViewRS / InfoGroup / Error / @Source
Namespace No namespace
Annotations
Identifies the source of this  element. In other words where the content originates from. Not limited to GDS, applicable to direct connect as well. Example: 1A, 1V, or other.
Type xsd:string
Properties
content: simple
Used by
Source
<xsd:attribute name="Source" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation>Identifies the source of this element. In other words where the content originates from. Not limited to GDS, applicable to direct connect as well. Example: 1A, 1V, or other.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
[ top ]
Attribute FSNViewRS / InfoGroup / Error / @SourceRef
Namespace No namespace
Annotations
PNR Record Locator associated to Source attribute.
Type xsd:string
Properties
content: simple
Used by
Source
<xsd:attribute name="SourceRef" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation>PNR Record Locator associated to Source attribute.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
[ top ]
Attribute FlightNumberWithSuffixType / @Suffix
Namespace No namespace
Annotations
Flight number alpha qualifier.  
Values are:
A
B
C
D

Example: A
Type restriction of xsd:string
Properties
use: optional
Facets
enumeration A
enumeration B
enumeration C
enumeration D
Used by
Source
<xsd:attribute name="Suffix" use="optional">
  <xsd:annotation>
    <xsd:documentation>Flight number alpha qualifier. Values are: A B C D Example: A</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:enumeration value="A"/>
      <xsd:enumeration value="B"/>
      <xsd:enumeration value="C"/>
      <xsd:enumeration value="D"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:attribute>
[ top ]