Showing:

Annotations
Attributes
Diagrams
Facets
Instances
Properties
Source
Used by
Main schema TicketRevalidationRS.xsd
Namespace No namespace
Properties
attribute form default: unqualified
element form default: qualified
[ top ]
Included schema CommonTypes.xsd
Namespace No namespace
Properties
attribute form default: qualified
element form default: qualified
[ top ]
Element TicketRevalidationRS
Namespace No namespace
Annotations
Ticket Revalidation Response Root Element 

Note: While in the case of failure only the couponnumber/ segmentnumber pair which caused the reject/failure is returned, all pairs as requested are returned in case of success.
Diagram
Diagram TicketRevalidationRS.tmp#InfoGroup TicketRevalidationRS.tmp#TicketRevalidationRS_Result
Properties
content: complex
Model InfoGroup{0,1} , Result
Children InfoGroup, Result
Instance
<TicketRevalidationRS>
  <InfoGroup>{0,1}</InfoGroup>
  <Result>{1,1}</Result>
</TicketRevalidationRS>
Source
<xsd:element name="TicketRevalidationRS">
  <xsd:annotation>
    <xsd:documentation>Ticket Revalidation Response Root Element Note: While in the case of failure only the couponnumber/ segmentnumber pair which caused the reject/failure is returned, all pairs as requested are returned in case of success.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element ref="InfoGroup" minOccurs="0"/>
      <xsd:element name="Result">
        <xsd:annotation>
          <xsd:documentation>Response if Revalidation request failed or succeeded</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:choice>
            <xsd:element name="Failure">
              <xsd:annotation>
                <xsd:documentation>A failure node will be returned at first occurence of a coupon/segment validation request failing. Only the coupon/segment causing the rejection is returned.</xsd:documentation>
              </xsd:annotation>
              <xsd:complexType>
                <xsd:sequence>
                  <xsd:element name="CouponNumber" type="xsd:int">
                    <xsd:annotation>
                      <xsd:documentation>The actual coupon number causing the (very first) reject by the target system.</xsd:documentation>
                    </xsd:annotation>
                  </xsd:element>
                  <xsd:element name="SegmentNumber" type="xsd:int">
                    <xsd:annotation>
                      <xsd:documentation>The actual segment number causing the (very first) reject by the target system</xsd:documentation>
                    </xsd:annotation>
                  </xsd:element>
                </xsd:sequence>
                <xsd:attribute name="TicketNumber" type="xsd:long" use="required">
                  <xsd:annotation>
                    <xsd:documentation>The 13-digit ticket number (no check digit) from the TicketValidationRQ holding the coupon(s) used in the request(s). Example: 1761234567890</xsd:documentation>
                  </xsd:annotation>
                </xsd:attribute>
                <xsd:attribute name="RecordLocator" type="xsd:string" use="required">
                  <xsd:annotation>
                    <xsd:documentation>Record locator from the TicketValidationRQ holding the flight segment requested to be validated. Example: R1A3SK</xsd:documentation>
                  </xsd:annotation>
                </xsd:attribute>
              </xsd:complexType>
            </xsd:element>
            <xsd:element name="Success" maxOccurs="unbounded">
              <xsd:annotation>
                <xsd:documentation>A success node is returned when entire revalidation request was successful. All validated coupon/segment pairs will be listed.</xsd:documentation>
              </xsd:annotation>
              <xsd:complexType>
                <xsd:sequence>
                  <xsd:element name="CouponNumber" type="xsd:int">
                    <xsd:annotation>
                      <xsd:documentation>Returns separate element for each validated coupon number. A sequential match with SegmentNumber of RecordLocator element</xsd:documentation>
                    </xsd:annotation>
                  </xsd:element>
                  <xsd:element name="SegmentNumber" type="xsd:int">
                    <xsd:annotation>
                      <xsd:documentation>Returns separate element for each PNR segment associated to the validated coupon number. A sequential match with CouponNumner of TicketNumber element</xsd:documentation>
                    </xsd:annotation>
                  </xsd:element>
                </xsd:sequence>
                <xsd:attribute name="TicketNumber" type="xsd:long" use="required">
                  <xsd:annotation>
                    <xsd:documentation>The 13-digit ticket number (no check digit) from the TicketValidationRQ holding the coupon(s) used in the request(s). Example: 1761234567890</xsd:documentation>
                  </xsd:annotation>
                </xsd:attribute>
                <xsd:attribute name="RecordLocator" type="xsd:string" use="required">
                  <xsd:annotation>
                    <xsd:documentation>Record locator from the TicketValidationRQ holding the flight segment requested to be validated. Example: R1A3SK</xsd:documentation>
                  </xsd:annotation>
                </xsd:attribute>
              </xsd:complexType>
            </xsd:element>
          </xsd:choice>
        </xsd:complexType>
      </xsd:element>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element InfoGroup
Namespace No namespace
Annotations
Error and information group
Diagram
Diagram TicketRevalidationRS.tmp#ForInfo TicketRevalidationRS.tmp#Error
Properties
content: complex
Used by
Model ForInfo{0,1} , Error*
Children Error, ForInfo
Instance
<InfoGroup>
  <ForInfo Source="" SourceRef="">{0,1}</ForInfo>
  <Error ErrorType="" Source="" SourceRef="">{0,unbounded}</Error>
</InfoGroup>
Source
<xsd:element name="InfoGroup">
  <xsd:annotation>
    <xsd:documentation>Error and information group</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element ref="ForInfo" minOccurs="0"/>
      <xsd:element ref="Error" minOccurs="0" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element ForInfo
Namespace No namespace
Annotations
Information group
Diagram
Diagram TicketRevalidationRS.tmp#Source TicketRevalidationRS.tmp#SourceRef TicketRevalidationRS.tmp#Text
Properties
content: complex
Used by
Element InfoGroup
Model Text+
Children Text
Instance
<ForInfo Source="" SourceRef="">
  <Text>{1,unbounded}</Text>
</ForInfo>
Attributes
QName Type Fixed Default Use Annotation
Source restriction of 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 restriction of xsd:string optional
PNR Record Locator associated to Source attribute.
Source
<xsd:element name="ForInfo">
  <xsd:annotation>
    <xsd:documentation>Information group</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element ref="Text" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation>Information text or error text. Example: Free flow text. Example: Invalid flight number</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
    </xsd:sequence>
    <xsd:attribute ref="Source" use="optional">
      <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 ref="SourceRef" use="optional"/>
  </xsd:complexType>
</xsd:element>
[ top ]
Element Text
Namespace No namespace
Annotations
Information text or error text. Example: Free flow text.
Diagram
Diagram
Type xsd:string
Properties
content: simple
Used by
Elements Error, ForInfo
Source
<xsd:element name="Text" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation>Information text or error text. Example: Free flow text.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element Error
Namespace No namespace
Annotations
Error group
Diagram
Diagram TicketRevalidationRS.tmp#Error_ErrorType TicketRevalidationRS.tmp#Source TicketRevalidationRS.tmp#SourceRef TicketRevalidationRS.tmp#Code TicketRevalidationRS.tmp#Text TicketRevalidationRS.tmp#CustomRequest
Properties
content: complex
Used by
Element InfoGroup
Model Code{0,1} , Text+ , CustomRequest{0,1}
Children Code, CustomRequest, Text
Instance
<Error ErrorType="" Source="" SourceRef="">
  <Code>{0,1}</Code>
  <Text>{1,unbounded}</Text>
  <CustomRequest>{0,1}</CustomRequest>
</Error>
Attributes
QName Type Fixed Default Use Annotation
ErrorType xsd:string required
Type of error.  Example: Air
Source restriction of 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 restriction of xsd:string optional
PNR Record Locator associated to Source attribute.
Source
<xsd:element name="Error">
  <xsd:annotation>
    <xsd:documentation>Error group</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element ref="Code" minOccurs="0"/>
      <xsd:element ref="Text" maxOccurs="unbounded"/>
      <xsd:element ref="CustomRequest" minOccurs="0"/>
    </xsd:sequence>
    <xsd:attribute name="ErrorType" type="xsd:string" use="required">
      <xsd:annotation>
        <xsd:documentation>Type of error. Example: Air</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:attribute ref="Source"/>
    <xsd:attribute ref="SourceRef"/>
  </xsd:complexType>
</xsd:element>
[ top ]
Element Code
Namespace No namespace
Annotations
Error code or equipment type code.  Example: 0104 (error code), 747 (equipment code)
Diagram
Diagram
Type xsd:string
Properties
content: simple
Used by
Element Error
Source
<xsd:element name="Code" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation>Error code or equipment type code. Example: 0104 (error code), 747 (equipment code)</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element CustomRequest
Namespace No namespace
Annotations
Mostly used when source specific additional input is needed and/or when QC (Quality Control) edits are processed and the POS needs instructions/options how to proceed.

Multiple sources may return a separate 'Error' node with their own CustomRequest request.

the UI must display one screen at a time and respond to each with a separate message.
Diagram
Diagram TicketRevalidationRS.tmp#CustomRequest_DialogTitle TicketRevalidationRS.tmp#CustomRequest_Instructions TicketRevalidationRS.tmp#Control TicketRevalidationRS.tmp#CustomRequest_Button TicketRevalidationRS.tmp#CustomRequest_OrigMsg TicketRevalidationRS.tmp#CustomRequest_Reference
Properties
content: complex
Used by
Element Error
Model DialogTitle , Instructions{0,1} , Control+ , Button+ , OrigMsg , Reference{0,1}
Children Button, Control, DialogTitle, Instructions, OrigMsg, Reference
Instance
<CustomRequest>
  <DialogTitle>{1,1}</DialogTitle>
  <Instructions>{0,1}</Instructions>
  <Control GUILabel="" Mandatory="" MaxChar="" MinChar="" MouseOverText="" Pattern="" PNRLabel="" SameLine="" Type="" Width="">{1,unbounded}</Control>
  <Button ButtonLabel="" MouseOverText="" Validate="" Width="">{1,unbounded}</Button>
  <OrigMsg>{1,1}</OrigMsg>
  <Reference>{0,1}</Reference>
</CustomRequest>
Source
<xsd:element name="CustomRequest">
  <xsd:annotation>
    <xsd:documentation>Mostly used when source specific additional input is needed and/or when QC (Quality Control) edits are processed and the POS needs instructions/options how to proceed. Multiple sources may return a separate 'Error' node with their own CustomRequest request. the UI must display one screen at a time and respond to each with a separate message.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="DialogTitle">
        <xsd:annotation>
          <xsd:documentation>Freeflow Text to be displayed in the Title Bar of the pop-up window</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
      <xsd:element name="Instructions" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation>Freeflow lines of text to be displayed inside of the pop-up window to explain or instruct the user of the necessary action(s)</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:sequence>
            <xsd:element name="Text" maxOccurs="unbounded">
              <xsd:annotation>
                <xsd:documentation>Individual line of freeflow text</xsd:documentation>
              </xsd:annotation>
            </xsd:element>
          </xsd:sequence>
        </xsd:complexType>
      </xsd:element>
      <xsd:element ref="Control" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation>Control(s) needed for this pop-up. Important: The UI is asked to build the Pop-Up controls in sequential order. Possible types are: TextBox ListBox DropDown w/values ComboBox OptionGroup CheckBox DateInput TimeInput TextArea</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
      <xsd:element name="Button" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation>The 1st button defined will be the default button for the window. All buttons will be positioned at the bottom of the forms and arranged from left to right (centered)</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:attribute name="ButtonLabel" use="required">
            <xsd:annotation>
              <xsd:documentation>The label to be used for the button. Example: Submit</xsd:documentation>
            </xsd:annotation>
          </xsd:attribute>
          <xsd:attribute name="Validate">
            <xsd:annotation>
              <xsd:documentation>Possible values Y or N (default) If "Y" this button will trigger the validation needed by the GUI prior to processing the screen. Note: Only a single button can have this attribute set to "Y". If multiple, the first instance will be used.</xsd:documentation>
            </xsd:annotation>
          </xsd:attribute>
          <xsd:attribute name="MouseOverText">
            <xsd:annotation>
              <xsd:documentation>Freeflow informational text designed to use as a 'mouseover' text or similar</xsd:documentation>
            </xsd:annotation>
          </xsd:attribute>
          <xsd:attribute name="Width">
            <xsd:annotation>
              <xsd:documentation>GUI normally autosizes based on width of label. A certain width may be defined here in pixels.</xsd:documentation>
            </xsd:annotation>
          </xsd:attribute>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="OrigMsg" type="MessageStructure">
        <xsd:annotation>
          <xsd:documentation>This is the message originally received by Company</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
      <xsd:element name="Reference" type="MessageStructure" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation>Reference node to be returned with CustomResponse node - mostly used as a linking reference between CustomRequest and CustomResponse</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element CustomRequest / DialogTitle
Namespace No namespace
Annotations
Freeflow Text to be displayed in the Title Bar of the pop-up window
Diagram
Diagram
Source
<xsd:element name="DialogTitle">
  <xsd:annotation>
    <xsd:documentation>Freeflow Text to be displayed in the Title Bar of the pop-up window</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element CustomRequest / Instructions
Namespace No namespace
Annotations
Freeflow lines of text to be displayed inside of the pop-up window to explain or instruct the user of the necessary action(s)
Diagram
Diagram TicketRevalidationRS.tmp#CustomRequest_CustomRequest_Instructions_Text
Properties
content: complex
minOccurs: 0
Model Text+
Children Text
Instance
<Instructions>
  <Text>{1,unbounded}</Text>
</Instructions>
Source
<xsd:element name="Instructions" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>Freeflow lines of text to be displayed inside of the pop-up window to explain or instruct the user of the necessary action(s)</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="Text" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation>Individual line of freeflow text</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element CustomRequest / Instructions / Text
Namespace No namespace
Annotations
Individual line of freeflow text
Diagram
Diagram
Properties
maxOccurs: unbounded
Source
<xsd:element name="Text" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation>Individual line of freeflow text</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element Control
Namespace No namespace
Annotations
The control(s) needed for this pop-up.a) Textbox

Possible types are:
a) TextBox
b) DropDown w/values
c) OptionGroup
Diagram
Diagram TicketRevalidationRS.tmp#Control_Type TicketRevalidationRS.tmp#Control_GUILabel TicketRevalidationRS.tmp#Control_PNRLabel TicketRevalidationRS.tmp#Control_MouseOverText TicketRevalidationRS.tmp#Control_Mandatory TicketRevalidationRS.tmp#Control_Width TicketRevalidationRS.tmp#Control_SameLine TicketRevalidationRS.tmp#Control_Pattern TicketRevalidationRS.tmp#Control_MinChar TicketRevalidationRS.tmp#Control_MaxChar TicketRevalidationRS.tmp#Control_Value
Properties
content: complex
Used by
Element CustomRequest
Model Value*
Children Value
Instance
<Control GUILabel="" Mandatory="" MaxChar="" MinChar="" MouseOverText="" Pattern="" PNRLabel="" SameLine="" Type="" Width="">
  <Value>{0,unbounded}</Value>
</Control>
Attributes
QName Type Fixed Default Use Annotation
GUILabel required
Label to describe this control. 
This label is usually placed in front or above the respective control. In case of a 'Button' it is the name of the button.
Mandatory optional
Allowed Values: Y or N

If 'Y' the UI needs to identify the control as mandatory input/selection, e.g. with an asteriks or different colored background
MaxChar optional
Maximum characters
MinChar optional
Minimum characters
MouseOverText optional
Freeflow informational text designed to use as a 'mouseover' text or similar
PNRLabel required
Description to be used to enter the returned value into a PNR General Remark element, if needed or desired.

This label is usually placed in front of the returned value as remark text.

Example:
"ProjectID: 105514"
Pattern optional
use a regular expression string
SameLine optional
Allowed Values: Y or N

If 'Y' the UI needs to position this control to the right of and on the same line as the preceding control.
Type required
Possible Values:

TextBox
ListBox
DropDown w/values
ComboBox
OptionGroup(radio)
CheckBox
DateInput
TimeInput
TextArea
Width optional
Width in pixels
Source
<xsd:element name="Control">
  <xsd:annotation>
    <xsd:documentation>The control(s) needed for this pop-up.a) Textbox Possible types are: a) TextBox b) DropDown w/values c) OptionGroup</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="Value" minOccurs="0" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation>Applicable to these control types: ListBox DropDown ComboBox OptionGroup CheckBox The provided values are used to provide a dynamically built list and/or single choice (OptionGroup) or multi-choice (CheckBox) labels. In case of 'OptionGroup' and 'CheckBox' the value is the description/label for each checkbox or radio button.</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
    </xsd:sequence>
    <xsd:attribute name="Type" use="required">
      <xsd:annotation>
        <xsd:documentation>Possible Values: TextBox ListBox DropDown w/values ComboBox OptionGroup(radio) CheckBox DateInput TimeInput TextArea</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:attribute name="GUILabel" use="required">
      <xsd:annotation>
        <xsd:documentation>Label to describe this control. This label is usually placed in front or above the respective control. In case of a 'Button' it is the name of the button.</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:attribute name="PNRLabel" use="required">
      <xsd:annotation>
        <xsd:documentation>Description to be used to enter the returned value into a PNR General Remark element, if needed or desired. This label is usually placed in front of the returned value as remark text. Example: "ProjectID: 105514"</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:attribute name="MouseOverText">
      <xsd:annotation>
        <xsd:documentation>Freeflow informational text designed to use as a 'mouseover' text or similar</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:attribute name="Mandatory">
      <xsd:annotation>
        <xsd:documentation>Allowed Values: Y or N If 'Y' the UI needs to identify the control as mandatory input/selection, e.g. with an asteriks or different colored background</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:attribute name="Width">
      <xsd:annotation>
        <xsd:documentation>Width in pixels</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:attribute name="SameLine">
      <xsd:annotation>
        <xsd:documentation>Allowed Values: Y or N If 'Y' the UI needs to position this control to the right of and on the same line as the preceding control.</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:attribute name="Pattern">
      <xsd:annotation>
        <xsd:documentation>use a regular expression string</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:attribute name="MinChar">
      <xsd:annotation>
        <xsd:documentation>Minimum characters</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:attribute name="MaxChar">
      <xsd:annotation>
        <xsd:documentation>Maximum characters</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
  </xsd:complexType>
</xsd:element>
[ top ]
Element Control / Value
Namespace No namespace
Annotations
Applicable to these control types:

ListBox
DropDown
ComboBox
OptionGroup
CheckBox

The provided values are used to provide a dynamically built list and/or single choice (OptionGroup) or multi-choice (CheckBox) labels.

In case of 'OptionGroup' and 'CheckBox' the value is the description/label for each checkbox or radio button.
Diagram
Diagram
Properties
minOccurs: 0
maxOccurs: unbounded
Source
<xsd:element name="Value" minOccurs="0" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation>Applicable to these control types: ListBox DropDown ComboBox OptionGroup CheckBox The provided values are used to provide a dynamically built list and/or single choice (OptionGroup) or multi-choice (CheckBox) labels. In case of 'OptionGroup' and 'CheckBox' the value is the description/label for each checkbox or radio button.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element CustomRequest / Button
Namespace No namespace
Annotations
The 1st button defined will be the default button for the window.

All buttons will be positioned at the bottom of the forms and arranged from left to right (centered)
Diagram
Diagram TicketRevalidationRS.tmp#CustomRequest_CustomRequest_Button_ButtonLabel TicketRevalidationRS.tmp#CustomRequest_CustomRequest_Button_Validate TicketRevalidationRS.tmp#CustomRequest_CustomRequest_Button_MouseOverText TicketRevalidationRS.tmp#CustomRequest_CustomRequest_Button_Width
Properties
content: complex
maxOccurs: unbounded
Attributes
QName Type Fixed Default Use Annotation
ButtonLabel required
The label to be used for the button.

Example: Submit
MouseOverText optional
Freeflow informational text designed to use as a 'mouseover' text or similar
Validate optional
Possible values Y or N (default)

If "Y" this button will trigger the validation needed by the GUI prior to processing the screen.

Note:  Only a single button can have this attribute set to "Y".  If multiple, the first instance will be used.
Width optional
GUI normally autosizes based on width of label.  A certain width may be defined here in pixels.
Source
<xsd:element name="Button" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation>The 1st button defined will be the default button for the window. All buttons will be positioned at the bottom of the forms and arranged from left to right (centered)</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:attribute name="ButtonLabel" use="required">
      <xsd:annotation>
        <xsd:documentation>The label to be used for the button. Example: Submit</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:attribute name="Validate">
      <xsd:annotation>
        <xsd:documentation>Possible values Y or N (default) If "Y" this button will trigger the validation needed by the GUI prior to processing the screen. Note: Only a single button can have this attribute set to "Y". If multiple, the first instance will be used.</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:attribute name="MouseOverText">
      <xsd:annotation>
        <xsd:documentation>Freeflow informational text designed to use as a 'mouseover' text or similar</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:attribute name="Width">
      <xsd:annotation>
        <xsd:documentation>GUI normally autosizes based on width of label. A certain width may be defined here in pixels.</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
  </xsd:complexType>
</xsd:element>
[ top ]
Element CustomRequest / OrigMsg
Namespace No namespace
Annotations
This is the message originally received by Company
Diagram
Diagram TicketRevalidationRS.tmp#MessageStructure
Type MessageStructure
Properties
content: complex
Model ANY element from ANY namespace
Attributes
QName Type Fixed Default Use Annotation
ANY attribute from ANY namespace
Source
<xsd:element name="OrigMsg" type="MessageStructure">
  <xsd:annotation>
    <xsd:documentation>This is the message originally received by Company</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element CustomRequest / Reference
Namespace No namespace
Annotations
Reference node to be returned with CustomResponse node - mostly used as a linking reference between CustomRequest and CustomResponse
Diagram
Diagram TicketRevalidationRS.tmp#MessageStructure
Type MessageStructure
Properties
content: complex
minOccurs: 0
Model ANY element from ANY namespace
Attributes
QName Type Fixed Default Use Annotation
ANY attribute from ANY namespace
Source
<xsd:element name="Reference" type="MessageStructure" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>Reference node to be returned with CustomResponse node - mostly used as a linking reference between CustomRequest and CustomResponse</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element TicketRevalidationRS / Result
Namespace No namespace
Annotations
Response if Revalidation request failed or succeeded
Diagram
Diagram TicketRevalidationRS.tmp#TicketRevalidationRS_TicketRevalidationRS_Result_Failure TicketRevalidationRS.tmp#TicketRevalidationRS_TicketRevalidationRS_Result_Success
Properties
content: complex
Model Failure | Success+
Children Failure, Success
Instance
<Result>
  <Failure RecordLocator="" TicketNumber="">{1,1}</Failure>
  <Success RecordLocator="" TicketNumber="">{1,unbounded}</Success>
</Result>
Source
<xsd:element name="Result">
  <xsd:annotation>
    <xsd:documentation>Response if Revalidation request failed or succeeded</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:choice>
      <xsd:element name="Failure">
        <xsd:annotation>
          <xsd:documentation>A failure node will be returned at first occurence of a coupon/segment validation request failing. Only the coupon/segment causing the rejection is returned.</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:sequence>
            <xsd:element name="CouponNumber" type="xsd:int">
              <xsd:annotation>
                <xsd:documentation>The actual coupon number causing the (very first) reject by the target system.</xsd:documentation>
              </xsd:annotation>
            </xsd:element>
            <xsd:element name="SegmentNumber" type="xsd:int">
              <xsd:annotation>
                <xsd:documentation>The actual segment number causing the (very first) reject by the target system</xsd:documentation>
              </xsd:annotation>
            </xsd:element>
          </xsd:sequence>
          <xsd:attribute name="TicketNumber" type="xsd:long" use="required">
            <xsd:annotation>
              <xsd:documentation>The 13-digit ticket number (no check digit) from the TicketValidationRQ holding the coupon(s) used in the request(s). Example: 1761234567890</xsd:documentation>
            </xsd:annotation>
          </xsd:attribute>
          <xsd:attribute name="RecordLocator" type="xsd:string" use="required">
            <xsd:annotation>
              <xsd:documentation>Record locator from the TicketValidationRQ holding the flight segment requested to be validated. Example: R1A3SK</xsd:documentation>
            </xsd:annotation>
          </xsd:attribute>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="Success" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation>A success node is returned when entire revalidation request was successful. All validated coupon/segment pairs will be listed.</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:sequence>
            <xsd:element name="CouponNumber" type="xsd:int">
              <xsd:annotation>
                <xsd:documentation>Returns separate element for each validated coupon number. A sequential match with SegmentNumber of RecordLocator element</xsd:documentation>
              </xsd:annotation>
            </xsd:element>
            <xsd:element name="SegmentNumber" type="xsd:int">
              <xsd:annotation>
                <xsd:documentation>Returns separate element for each PNR segment associated to the validated coupon number. A sequential match with CouponNumner of TicketNumber element</xsd:documentation>
              </xsd:annotation>
            </xsd:element>
          </xsd:sequence>
          <xsd:attribute name="TicketNumber" type="xsd:long" use="required">
            <xsd:annotation>
              <xsd:documentation>The 13-digit ticket number (no check digit) from the TicketValidationRQ holding the coupon(s) used in the request(s). Example: 1761234567890</xsd:documentation>
            </xsd:annotation>
          </xsd:attribute>
          <xsd:attribute name="RecordLocator" type="xsd:string" use="required">
            <xsd:annotation>
              <xsd:documentation>Record locator from the TicketValidationRQ holding the flight segment requested to be validated. Example: R1A3SK</xsd:documentation>
            </xsd:annotation>
          </xsd:attribute>
        </xsd:complexType>
      </xsd:element>
    </xsd:choice>
  </xsd:complexType>
</xsd:element>
[ top ]
Element TicketRevalidationRS / Result / Failure
Namespace No namespace
Annotations
A failure node will be returned at first occurence of a coupon/segment validation request failing. Only the coupon/segment causing the rejection is returned.
Diagram
Diagram TicketRevalidationRS.tmp#TicketRevalidationRS_TicketRevalidationRS_Result_TicketRevalidationRS_TicketRevalidationRS_Result_Failure_TicketNumber TicketRevalidationRS.tmp#TicketRevalidationRS_TicketRevalidationRS_Result_TicketRevalidationRS_TicketRevalidationRS_Result_Failure_RecordLocator TicketRevalidationRS.tmp#TicketRevalidationRS_TicketRevalidationRS_Result_TicketRevalidationRS_TicketRevalidationRS_Result_Failure_CouponNumber TicketRevalidationRS.tmp#TicketRevalidationRS_TicketRevalidationRS_Result_TicketRevalidationRS_TicketRevalidationRS_Result_Failure_SegmentNumber
Properties
content: complex
Model CouponNumber , SegmentNumber
Children CouponNumber, SegmentNumber
Instance
<Failure RecordLocator="" TicketNumber="">
  <CouponNumber>{1,1}</CouponNumber>
  <SegmentNumber>{1,1}</SegmentNumber>
</Failure>
Attributes
QName Type Fixed Default Use Annotation
RecordLocator xsd:string required
Record locator from the TicketValidationRQ holding the flight segment requested to be validated.
Example: R1A3SK
TicketNumber xsd:long required
The 13-digit ticket number (no check digit) from the TicketValidationRQ holding the coupon(s) used in the request(s).  
Example: 1761234567890
Source
<xsd:element name="Failure">
  <xsd:annotation>
    <xsd:documentation>A failure node will be returned at first occurence of a coupon/segment validation request failing. Only the coupon/segment causing the rejection is returned.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="CouponNumber" type="xsd:int">
        <xsd:annotation>
          <xsd:documentation>The actual coupon number causing the (very first) reject by the target system.</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
      <xsd:element name="SegmentNumber" type="xsd:int">
        <xsd:annotation>
          <xsd:documentation>The actual segment number causing the (very first) reject by the target system</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
    </xsd:sequence>
    <xsd:attribute name="TicketNumber" type="xsd:long" use="required">
      <xsd:annotation>
        <xsd:documentation>The 13-digit ticket number (no check digit) from the TicketValidationRQ holding the coupon(s) used in the request(s). Example: 1761234567890</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:attribute name="RecordLocator" type="xsd:string" use="required">
      <xsd:annotation>
        <xsd:documentation>Record locator from the TicketValidationRQ holding the flight segment requested to be validated. Example: R1A3SK</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
  </xsd:complexType>
</xsd:element>
[ top ]
Element TicketRevalidationRS / Result / Failure / CouponNumber
Namespace No namespace
Annotations
The actual coupon number causing the (very first) reject by the target system.
Diagram
Diagram
Type xsd:int
Properties
content: simple
Source
<xsd:element name="CouponNumber" type="xsd:int">
  <xsd:annotation>
    <xsd:documentation>The actual coupon number causing the (very first) reject by the target system.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element TicketRevalidationRS / Result / Failure / SegmentNumber
Namespace No namespace
Annotations
The actual segment number causing the (very first) reject by the target system
Diagram
Diagram
Type xsd:int
Properties
content: simple
Source
<xsd:element name="SegmentNumber" type="xsd:int">
  <xsd:annotation>
    <xsd:documentation>The actual segment number causing the (very first) reject by the target system</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element TicketRevalidationRS / Result / Success
Namespace No namespace
Annotations
A success node is returned when entire revalidation request was successful.  All validated coupon/segment pairs will be listed.
Diagram
Diagram TicketRevalidationRS.tmp#TicketRevalidationRS_TicketRevalidationRS_Result_TicketRevalidationRS_TicketRevalidationRS_Result_Success_TicketNumber TicketRevalidationRS.tmp#TicketRevalidationRS_TicketRevalidationRS_Result_TicketRevalidationRS_TicketRevalidationRS_Result_Success_RecordLocator TicketRevalidationRS.tmp#TicketRevalidationRS_TicketRevalidationRS_Result_TicketRevalidationRS_TicketRevalidationRS_Result_Success_CouponNumber TicketRevalidationRS.tmp#TicketRevalidationRS_TicketRevalidationRS_Result_TicketRevalidationRS_TicketRevalidationRS_Result_Success_SegmentNumber
Properties
content: complex
maxOccurs: unbounded
Model CouponNumber , SegmentNumber
Children CouponNumber, SegmentNumber
Instance
<Success RecordLocator="" TicketNumber="">
  <CouponNumber>{1,1}</CouponNumber>
  <SegmentNumber>{1,1}</SegmentNumber>
</Success>
Attributes
QName Type Fixed Default Use Annotation
RecordLocator xsd:string required
Record locator from the TicketValidationRQ holding the flight segment requested to be validated.
Example: R1A3SK
TicketNumber xsd:long required
The 13-digit ticket number (no check digit) from the TicketValidationRQ holding the coupon(s) used in the request(s).  
Example: 1761234567890
Source
<xsd:element name="Success" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation>A success node is returned when entire revalidation request was successful. All validated coupon/segment pairs will be listed.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="CouponNumber" type="xsd:int">
        <xsd:annotation>
          <xsd:documentation>Returns separate element for each validated coupon number. A sequential match with SegmentNumber of RecordLocator element</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
      <xsd:element name="SegmentNumber" type="xsd:int">
        <xsd:annotation>
          <xsd:documentation>Returns separate element for each PNR segment associated to the validated coupon number. A sequential match with CouponNumner of TicketNumber element</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
    </xsd:sequence>
    <xsd:attribute name="TicketNumber" type="xsd:long" use="required">
      <xsd:annotation>
        <xsd:documentation>The 13-digit ticket number (no check digit) from the TicketValidationRQ holding the coupon(s) used in the request(s). Example: 1761234567890</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:attribute name="RecordLocator" type="xsd:string" use="required">
      <xsd:annotation>
        <xsd:documentation>Record locator from the TicketValidationRQ holding the flight segment requested to be validated. Example: R1A3SK</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
  </xsd:complexType>
</xsd:element>
[ top ]
Element TicketRevalidationRS / Result / Success / CouponNumber
Namespace No namespace
Annotations
Returns separate element for each validated coupon number.  A sequential match with SegmentNumber of RecordLocator element
Diagram
Diagram
Type xsd:int
Properties
content: simple
Source
<xsd:element name="CouponNumber" type="xsd:int">
  <xsd:annotation>
    <xsd:documentation>Returns separate element for each validated coupon number. A sequential match with SegmentNumber of RecordLocator element</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element TicketRevalidationRS / Result / Success / SegmentNumber
Namespace No namespace
Annotations
Returns separate element for each PNR segment associated to the validated coupon number.  A sequential match with CouponNumner of TicketNumber element
Diagram
Diagram
Type xsd:int
Properties
content: simple
Source
<xsd:element name="SegmentNumber" type="xsd:int">
  <xsd:annotation>
    <xsd:documentation>Returns separate element for each PNR segment associated to the validated coupon number. A sequential match with CouponNumner of TicketNumber element</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element FiledIn
Namespace No namespace
Annotations
This group represents fares filed in a currency different from the currency of a point of sale. The content elements represent the original currency and amount as filed.
Diagram
Diagram TicketRevalidationRS.tmp#CurrencyCode TicketRevalidationRS.tmp#FiledIn_Amount
Properties
content: complex
Used by
Complex Type BaseFareType
Model ALL(CurrencyCode Amount)
Children Amount, CurrencyCode
Instance
<FiledIn>
  <CurrencyCode NumberOfDecimals="">{1,1}</CurrencyCode>
  <Amount BulkMask="">{1,1}</Amount>
</FiledIn>
Source
<xsd:element name="FiledIn">
  <xsd:annotation>
    <xsd:documentation>This group represents fares filed in a currency different from the currency of a point of sale. The content elements represent the original currency and amount as filed.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:all>
      <xsd:element ref="CurrencyCode"/>
      <xsd:element name="Amount">
        <xsd:annotation>
          <xsd:documentation>Base Fare Amount as originally filed.</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:simpleContent>
            <xsd:extension base="xsd:integer">
              <xsd:attribute name="BulkMask">
                <xsd:annotation>
                  <xsd:documentation>This mask applies to IT/BT tickets where the masked value may be "BT" or "IT" instead of the true amount. Note: this mask is ALWAYS used for the passenger ticket image.</xsd:documentation>
                </xsd:annotation>
              </xsd:attribute>
            </xsd:extension>
          </xsd:simpleContent>
        </xsd:complexType>
      </xsd:element>
    </xsd:all>
  </xsd:complexType>
</xsd:element>
[ top ]
Element CurrencyCode
Namespace No namespace
Annotations
Currency code.  Example: USD
Diagram
Diagram TicketRevalidationRS.tmp#CurrencyCodeType_NumberOfDecimals TicketRevalidationRS.tmp#CurrencyCodeType TicketRevalidationRS.tmp#CurrencyCode_NumberOfDecimals
Type restriction of CurrencyCodeType
Type hierarchy
Properties
content: complex
Used by
Element FiledIn
Attributes
QName Type Fixed Default Use Annotation
NumberOfDecimals xsd:integer required
Decimal position in fare amount.  Example: 2
Source
<xsd:element name="CurrencyCode">
  <xsd:annotation>
    <xsd:documentation>Currency code. Example: USD</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:simpleContent>
      <xsd:restriction base="CurrencyCodeType">
        <xsd:pattern value="[A-Z0-9]{3}"/>
        <xsd:attribute name="NumberOfDecimals" type="xsd:integer" use="required">
          <xsd:annotation>
            <xsd:documentation>Decimal position in fare amount. Example: 2</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
      </xsd:restriction>
    </xsd:simpleContent>
  </xsd:complexType>
</xsd:element>
[ top ]
Element FiledIn / Amount
Namespace No namespace
Annotations
Base Fare Amount as originally filed.
Diagram
Diagram TicketRevalidationRS.tmp#FiledIn_FiledIn_Amount_BulkMask
Type extension of xsd:integer
Properties
content: complex
Attributes
QName Type Fixed Default Use Annotation
BulkMask optional
This mask applies to IT/BT tickets where the masked value may be "BT" or "IT" instead of the true amount.

Note: this mask is ALWAYS used for the passenger ticket image.
Source
<xsd:element name="Amount">
  <xsd:annotation>
    <xsd:documentation>Base Fare Amount as originally filed.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:simpleContent>
      <xsd:extension base="xsd:integer">
        <xsd:attribute name="BulkMask">
          <xsd:annotation>
            <xsd:documentation>This mask applies to IT/BT tickets where the masked value may be "BT" or "IT" instead of the true amount. Note: this mask is ALWAYS used for the passenger ticket image.</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
      </xsd:extension>
    </xsd:simpleContent>
  </xsd:complexType>
</xsd:element>
[ top ]
Element NVA
Namespace No namespace
Annotations
Identifies "not valid after" date for a fare.Date in ISO 8601 format (yyyy-mm-dd).  Example: 2001-12-25
Diagram
Diagram
Type xsd:date
Properties
content: simple
Source
<xsd:element name="NVA" type="xsd:date">
  <xsd:annotation>
    <xsd:documentation>Identifies "not valid after" date for a fare.Date in ISO 8601 format (yyyy-mm-dd). Example: 2001-12-25</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element NVB
Namespace No namespace
Annotations
Identifies "not valid befoe" date for a fare. Date in ISO 8601 format (yyyy-mm-dd).  Example: 2001-12-25
Diagram
Diagram
Type xsd:date
Properties
content: simple
Source
<xsd:element name="NVB" type="xsd:date">
  <xsd:annotation>
    <xsd:documentation>Identifies "not valid befoe" date for a fare. Date in ISO 8601 format (yyyy-mm-dd). Example: 2001-12-25</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element HistoricalPricingInfo
Namespace No namespace
Annotations
DEPRECATED.
Please use definitions in PricingInfo: ReservationsDateTime, HistoricPricingDate, AltTicketingDate.

Historical pricing group. Required if OriginDestination group includes past date segments.
Diagram
Diagram TicketRevalidationRS.tmp#HistoricalPricingInfo_ReservationDateTime TicketRevalidationRS.tmp#HistoricalPricingInfo_TicketedDateTime TicketRevalidationRS.tmp#HistoricalPricingInfo_RecordLocator
Properties
content: complex
Model (ReservationDateTime{0,1} , TicketedDateTime) | RecordLocator{0,0}
Children RecordLocator, ReservationDateTime, TicketedDateTime
Instance
<HistoricalPricingInfo>
  <ReservationDateTime>{0,1}</ReservationDateTime>
  <TicketedDateTime>{1,1}</TicketedDateTime>
  <RecordLocator>{0,0}</RecordLocator>
</HistoricalPricingInfo>
Source
<xsd:element name="HistoricalPricingInfo">
  <xsd:annotation>
    <xsd:documentation>DEPRECATED. Please use definitions in PricingInfo: ReservationsDateTime, HistoricPricingDate, AltTicketingDate. Historical pricing group. Required if OriginDestination group includes past date segments.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:choice>
      <xsd:sequence>
        <xsd:element name="ReservationDateTime" minOccurs="0">
          <xsd:annotation>
            <xsd:documentation>This timestamp indetifies when PNR was created client application requests historical pricing for.</xsd:documentation>
          </xsd:annotation>
          <xsd:complexType>
            <xsd:sequence>
              <xsd:element name="Date" type="Date">
                <xsd:annotation>
                  <xsd:documentation>Specifies departure or arrival date in ISO 8601 format (yyyy-mm-dd). Example: 2001-12-25</xsd:documentation>
                </xsd:annotation>
              </xsd:element>
              <xsd:element name="Time" type="Time" minOccurs="0">
                <xsd:annotation>
                  <xsd:documentation>Departure or arrival time in ISO 8601 twenty-four hour clock format. Example: 14:00</xsd:documentation>
                </xsd:annotation>
              </xsd:element>
            </xsd:sequence>
          </xsd:complexType>
        </xsd:element>
        <xsd:element name="TicketedDateTime">
          <xsd:annotation>
            <xsd:documentation>Timestamp of ticket issuance for past date segments in OriginDestination section.</xsd:documentation>
          </xsd:annotation>
          <xsd:complexType>
            <xsd:sequence>
              <xsd:element name="Date" type="Date">
                <xsd:annotation>
                  <xsd:documentation>Specifies departure or arrival date in ISO 8601 format (yyyy-mm-dd). Example: 2001-12-25</xsd:documentation>
                </xsd:annotation>
              </xsd:element>
              <xsd:element name="Time" type="Time" minOccurs="0">
                <xsd:annotation>
                  <xsd:documentation>Departure or arrival time in ISO 8601 twenty-four hour clock format. Example: 14:00</xsd:documentation>
                </xsd:annotation>
              </xsd:element>
            </xsd:sequence>
          </xsd:complexType>
        </xsd:element>
      </xsd:sequence>
      <xsd:element name="RecordLocator" type="xsd:string" minOccurs="0" maxOccurs="0">
        <xsd:annotation>
          <xsd:documentation>FUTURE USE. NOT SUPPORTED.</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
    </xsd:choice>
  </xsd:complexType>
</xsd:element>
[ top ]
Element HistoricalPricingInfo / ReservationDateTime
Namespace No namespace
Annotations
This timestamp indetifies when PNR was created client application requests historical pricing for.
Diagram
Diagram TicketRevalidationRS.tmp#HistoricalPricingInfo_HistoricalPricingInfo_ReservationDateTime_Date TicketRevalidationRS.tmp#HistoricalPricingInfo_HistoricalPricingInfo_ReservationDateTime_Time
Properties
content: complex
minOccurs: 0
Model Date , Time{0,1}
Children Date, Time
Instance
<ReservationDateTime>
  <Date>{1,1}</Date>
  <Time>{0,1}</Time>
</ReservationDateTime>
Source
<xsd:element name="ReservationDateTime" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>This timestamp indetifies when PNR was created client application requests historical pricing for.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="Date" type="Date">
        <xsd:annotation>
          <xsd:documentation>Specifies departure or arrival date in ISO 8601 format (yyyy-mm-dd). Example: 2001-12-25</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
      <xsd:element name="Time" type="Time" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation>Departure or arrival time in ISO 8601 twenty-four hour clock format. Example: 14:00</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element HistoricalPricingInfo / ReservationDateTime / Date
Namespace No namespace
Annotations
Specifies departure or arrival date in ISO 8601 format (yyyy-mm-dd). Example: 2001-12-25
Diagram
Diagram TicketRevalidationRS.tmp#Date
Type Date
Properties
content: simple
Source
<xsd:element name="Date" type="Date">
  <xsd:annotation>
    <xsd:documentation>Specifies departure or arrival date in ISO 8601 format (yyyy-mm-dd). Example: 2001-12-25</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element HistoricalPricingInfo / ReservationDateTime / Time
Namespace No namespace
Annotations
Departure or arrival time in ISO 8601 twenty-four hour clock format. Example: 14:00
Diagram
Diagram TicketRevalidationRS.tmp#Time
Type Time
Properties
content: simple
minOccurs: 0
Facets
length 5
pattern ([0-1][0-9]|2[0-3]):[0-5][0-9]
Source
<xsd:element name="Time" type="Time" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>Departure or arrival time in ISO 8601 twenty-four hour clock format. Example: 14:00</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element HistoricalPricingInfo / TicketedDateTime
Namespace No namespace
Annotations
Timestamp of ticket issuance  for past date segments in OriginDestination section.
Diagram
Diagram TicketRevalidationRS.tmp#HistoricalPricingInfo_HistoricalPricingInfo_TicketedDateTime_Date TicketRevalidationRS.tmp#HistoricalPricingInfo_HistoricalPricingInfo_TicketedDateTime_Time
Properties
content: complex
Model Date , Time{0,1}
Children Date, Time
Instance
<TicketedDateTime>
  <Date>{1,1}</Date>
  <Time>{0,1}</Time>
</TicketedDateTime>
Source
<xsd:element name="TicketedDateTime">
  <xsd:annotation>
    <xsd:documentation>Timestamp of ticket issuance for past date segments in OriginDestination section.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="Date" type="Date">
        <xsd:annotation>
          <xsd:documentation>Specifies departure or arrival date in ISO 8601 format (yyyy-mm-dd). Example: 2001-12-25</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
      <xsd:element name="Time" type="Time" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation>Departure or arrival time in ISO 8601 twenty-four hour clock format. Example: 14:00</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element HistoricalPricingInfo / TicketedDateTime / Date
Namespace No namespace
Annotations
Specifies departure or arrival date in ISO 8601 format (yyyy-mm-dd). Example: 2001-12-25
Diagram
Diagram TicketRevalidationRS.tmp#Date
Type Date
Properties
content: simple
Source
<xsd:element name="Date" type="Date">
  <xsd:annotation>
    <xsd:documentation>Specifies departure or arrival date in ISO 8601 format (yyyy-mm-dd). Example: 2001-12-25</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element HistoricalPricingInfo / TicketedDateTime / Time
Namespace No namespace
Annotations
Departure or arrival time in ISO 8601 twenty-four hour clock format. Example: 14:00
Diagram
Diagram TicketRevalidationRS.tmp#Time
Type Time
Properties
content: simple
minOccurs: 0
Facets
length 5
pattern ([0-1][0-9]|2[0-3]):[0-5][0-9]
Source
<xsd:element name="Time" type="Time" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>Departure or arrival time in ISO 8601 twenty-four hour clock format. Example: 14:00</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element HistoricalPricingInfo / RecordLocator
Namespace No namespace
Annotations
FUTURE USE.
NOT SUPPORTED.
Diagram
Diagram
Type xsd:string
Properties
content: simple
minOccurs: 0
maxOccurs: 0
Source
<xsd:element name="RecordLocator" type="xsd:string" minOccurs="0" maxOccurs="0">
  <xsd:annotation>
    <xsd:documentation>FUTURE USE. NOT SUPPORTED.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element NegoRateCode
Namespace No namespace
Annotations
Negotiated rate code.
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
Facets
minLength 1
Source
<xsd:element name="NegoRateCode">
  <xsd:annotation>
    <xsd:documentation>Negotiated rate code.</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:minLength value="1"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element Latitude
Namespace No namespace
Annotations
Geographical information for latitude. If sign attribute is missing, positive values stand for North, negative values for South. Example: 49.9856
Diagram
Diagram TicketRevalidationRS.tmp#Latitude_Sign
Type extension of xsd:decimal
Properties
content: complex
Used by
Element GeoCoded
Attributes
QName Type Fixed Default Use Annotation
Sign restriction of xsd:string optional
Latitude Indicator.  Values are: N = North of Equator S = South of Equator  Example: S
Source
<xsd:element name="Latitude">
  <xsd:annotation>
    <xsd:documentation>Geographical information for latitude. If sign attribute is missing, positive values stand for North, negative values for South. Example: 49.9856</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:simpleContent>
      <xsd:extension base="xsd:decimal">
        <xsd:attribute name="Sign">
          <xsd:annotation>
            <xsd:documentation>Latitude Indicator. Values are: N = North of Equator S = South of Equator Example: S</xsd:documentation>
          </xsd:annotation>
          <xsd:simpleType>
            <xsd:restriction base="xsd:string">
              <xsd:enumeration value="S"/>
              <xsd:enumeration value="N"/>
            </xsd:restriction>
          </xsd:simpleType>
        </xsd:attribute>
      </xsd:extension>
    </xsd:simpleContent>
  </xsd:complexType>
</xsd:element>
[ top ]
Element Longitude
Namespace No namespace
Annotations
Geographical information for longitude. If sign attribute is missing, positive values stand for East, negative values for West. Example: 9.1220
Diagram
Diagram TicketRevalidationRS.tmp#Longitude_Sign
Type extension of xsd:decimal
Properties
content: complex
Used by
Element GeoCoded
Attributes
QName Type Fixed Default Use Annotation
Sign restriction of xsd:string optional
Longitude indicator.  Values are: E = East of Meridian, W = West of Meridian  Example: E
Source
<xsd:element name="Longitude">
  <xsd:annotation>
    <xsd:documentation>Geographical information for longitude. If sign attribute is missing, positive values stand for East, negative values for West. Example: 9.1220</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:simpleContent>
      <xsd:extension base="xsd:decimal">
        <xsd:attribute name="Sign">
          <xsd:annotation>
            <xsd:documentation>Longitude indicator. Values are: E = East of Meridian, W = West of Meridian Example: E</xsd:documentation>
          </xsd:annotation>
          <xsd:simpleType>
            <xsd:restriction base="xsd:string">
              <xsd:enumeration value="E"/>
              <xsd:enumeration value="W"/>
            </xsd:restriction>
          </xsd:simpleType>
        </xsd:attribute>
      </xsd:extension>
    </xsd:simpleContent>
  </xsd:complexType>
</xsd:element>
[ top ]
Element GeoCoded
Namespace No namespace
Annotations
Geographical position information. 
Allows search by geographical longitude and latitude and to define a search radius around the specified geo location.
Diagram
Diagram TicketRevalidationRS.tmp#Radius TicketRevalidationRS.tmp#DistanceUnit TicketRevalidationRS.tmp#Longitude TicketRevalidationRS.tmp#Latitude
Properties
content: complex
Model ALL(Longitude Latitude)
Children Latitude, Longitude
Instance
<GeoCoded DistanceUnit="K" Radius="">
  <Longitude Sign="">{1,1}</Longitude>
  <Latitude Sign="">{1,1}</Latitude>
</GeoCoded>
Attributes
QName Type Fixed Default Use Annotation
DistanceUnit restriction of xsd:string K optional
Unit of distance.
Values:
M = Miles
K = Kilometers
Example: K
Radius xsd:unsignedLong optional
Radius around the specified location, within which results should be included.
Example: 0.5
Source
<xsd:element name="GeoCoded">
  <xsd:annotation>
    <xsd:documentation>Geographical position information. Allows search by geographical longitude and latitude and to define a search radius around the specified geo location.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:all>
      <xsd:element ref="Longitude"/>
      <xsd:element ref="Latitude"/>
    </xsd:all>
    <xsd:attribute ref="Radius"/>
    <xsd:attribute ref="DistanceUnit" default="K">
      <xsd:annotation>
        <xsd:documentation>Unit of distance in which Radius is specified. Values: M = Miles K = Kilometers Defaults to kilometers, if left out. Example: M</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
  </xsd:complexType>
</xsd:element>
[ top ]
Element TravelerIDRef
Namespace No namespace
Annotations
Unique association ID reference of the traveler associated to this item. No comma separeted lists and no ranges allowed.        Example: T1
Diagram
Diagram
Type xsd:string
Properties
content: simple
Source
<xsd:element name="TravelerIDRef" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation>Unique association ID reference of the traveler associated to this item. No comma separeted lists and no ranges allowed. Example: T1</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element SegmentIDRef
Namespace No namespace
Annotations
ID reference used to asscociate this item to a segment.  No comma separeted lists and no ranges supported.    Example: F1
Diagram
Diagram
Type xsd:string
Properties
content: simple
Source
<xsd:element name="SegmentIDRef" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation>ID reference used to asscociate this item to a segment. No comma separeted lists and no ranges supported. Example: F1</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element FareRefKey
Namespace No namespace
Annotations
Unique fare reference key. If present in pricing response messages, must be included in FareRulesRQ.
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
Facets
minLength 1
Source
<xsd:element name="FareRefKey">
  <xsd:annotation>
    <xsd:documentation>Unique fare reference key. If present in pricing response messages, must be included in FareRulesRQ.</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:minLength value="1"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element HotelRating
Namespace No namespace
Annotations
Rating of this hotel. Note that this element will eventually supercede the AAARating element definition. The latter will be deprecated soon.
Example: NTM3  CROWN
Diagram
Diagram TicketRevalidationRS.tmp#HotelRating_RatingSystem
Type extension of xsd:string
Properties
content: complex
Attributes
QName Type Fixed Default Use Annotation
RatingSystem restriction of xsd:string optional
Identifies the rating system used to rate the hotel. Values are: 
AAA - AAA in US
GUESTS - Guest rating
HRS - Hotel Reservation System 'stars' rating
NTM - North Star Media 'crown' rating.
HBC - Booking.com rating
UNK - unknown.
Source
<xsd:element name="HotelRating">
  <xsd:annotation>
    <xsd:documentation>Rating of this hotel. Note that this element will eventually supercede the AAARating element definition. The latter will be deprecated soon. Example: NTM3 CROWN</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:simpleContent>
      <xsd:extension base="xsd:string">
        <xsd:attribute name="RatingSystem">
          <xsd:annotation>
            <xsd:documentation>Identifies the rating system used to rate the hotel. Values are: AAA - AAA in US GUESTS - Guest rating HRS - Hotel Reservation System 'stars' rating NTM - North Star Media 'crown' rating. HBC - Booking.com rating UNK - unknown.</xsd:documentation>
          </xsd:annotation>
          <xsd:simpleType>
            <xsd:restriction base="xsd:string">
              <xsd:enumeration value="AAA"/>
              <xsd:enumeration value="GUESTS"/>
              <xsd:enumeration value="HRS"/>
              <xsd:enumeration value="NTM"/>
              <xsd:enumeration value="UNK"/>
              <xsd:enumeration value="HBC"/>
            </xsd:restriction>
          </xsd:simpleType>
        </xsd:attribute>
      </xsd:extension>
    </xsd:simpleContent>
  </xsd:complexType>
</xsd:element>
[ top ]
Element POIDistance
Namespace No namespace
Annotations
Distance to a point of interest. Will somewhen replace DistanceToAirport. Example: 5.5
Diagram
Diagram TicketRevalidationRS.tmp#POIDistance_POIType TicketRevalidationRS.tmp#POIDistance_POIName
Type extension of xsd:decimal
Properties
content: complex
Attributes
QName Type Fixed Default Use Annotation
POIName xsd:string optional
Point of interest name.
Example: FRANKFURT/MAIN
POIType restriction of xsd:string required
Point of interest type. Example: AIRPORT
Source
<xsd:element name="POIDistance">
  <xsd:annotation>
    <xsd:documentation>Distance to a point of interest. Will somewhen replace DistanceToAirport. Example: 5.5</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:simpleContent>
      <xsd:extension base="xsd:decimal">
        <xsd:attribute name="POIType" use="required">
          <xsd:annotation>
            <xsd:documentation>Point of interest type. Example: AIRPORT</xsd:documentation>
          </xsd:annotation>
          <xsd:simpleType>
            <xsd:restriction base="xsd:string">
              <xsd:enumeration value="AIRPORT"/>
              <xsd:enumeration value="TRAIN STATION"/>
              <xsd:enumeration value="CITY CENTER"/>
              <xsd:enumeration value="HIGHWAY"/>
              <xsd:enumeration value="SHOPPING"/>
              <xsd:enumeration value="PETROL STATION"/>
              <xsd:enumeration value="THEATER"/>
              <xsd:enumeration value="CINEMA"/>
              <xsd:enumeration value="CAR RENTAL STATION"/>
              <xsd:enumeration value="UNKNOWN"/>
              <xsd:enumeration value="LOCATION"/>
            </xsd:restriction>
          </xsd:simpleType>
        </xsd:attribute>
        <xsd:attribute name="POIName" type="xsd:string">
          <xsd:annotation>
            <xsd:documentation>Point of interest name. Example: FRANKFURT/MAIN</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
      </xsd:extension>
    </xsd:simpleContent>
  </xsd:complexType>
</xsd:element>
[ top ]
Element CarLocation / CityCode
Namespace No namespace
Annotations
IATA 3-letter city/airport code for location. In case of non-airport location Category and Number need to be present. Example: NYC
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
Facets
length 3
Source
<xsd:element name="CityCode">
  <xsd:annotation>
    <xsd:documentation>IATA 3-letter city/airport code for location. In case of non-airport location Category and Number need to be present. Example: NYC</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:length value="3"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element CarLocation / Category
Namespace No namespace
Annotations
Location category:
T = Airport terminal
O = Off-airport
C = City location 
P = Port 
X = Rail
N = North suburban
E = East suburban
S = South suburban
W = West suburban
A = All suburban locations 
R = Resort location
Example: C
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
Facets
length 1
Source
<xsd:element name="Category">
  <xsd:annotation>
    <xsd:documentation>Location category: T = Airport terminal O = Off-airport C = City location P = Port X = Rail N = North suburban E = East suburban S = South suburban W = West suburban A = All suburban locations R = Resort location Example: C</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:length value="1"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element CarLocation / Number
Namespace No namespace
Annotations
Location number used to identify specific rental location within a location category.  Example: 001
Diagram
Diagram
Type xsd:string
Properties
content: simple
Source
<xsd:element name="Number" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation>Location number used to identify specific rental location within a location category. Example: 001</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element RequestForCarLocation / CityCode
Namespace No namespace
Annotations
IATA 3-letter city/airport code for location. In case of non-airport location Category need to be present (Number for particular locaction). Example: NYC
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
Facets
length 3
Source
<xsd:element name="CityCode">
  <xsd:annotation>
    <xsd:documentation>IATA 3-letter city/airport code for location. In case of non-airport location Category need to be present (Number for particular locaction). Example: NYC</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:length value="3"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element RequestForCarLocation / Category
Namespace No namespace
Annotations
Location category:
T = Airport terminal
O = Off-airport
C = City location 
P = Port 
X = Rail
N = North suburban
E = East suburban
S = South suburban
W = West suburban 
D = default location for the city.
R = Resort location
Example: C
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
Facets
length 1
Source
<xsd:element name="Category">
  <xsd:annotation>
    <xsd:documentation>Location category: T = Airport terminal O = Off-airport C = City location P = Port X = Rail N = North suburban E = East suburban S = South suburban W = West suburban D = default location for the city. R = Resort location Example: C</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:length value="1"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element RequestForCarLocation / Number
Namespace No namespace
Annotations
Location number used to identify specific rental location within a location category.  Example: 001
Diagram
Diagram
Type xsd:string
Properties
content: simple
minOccurs: 0
Source
<xsd:element name="Number" type="xsd:string" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>Location number used to identify specific rental location within a location category. Example: 001</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element BasicEndorsement / Text
Namespace No namespace
Annotations
Endorsement text.
Diagram
Diagram TicketRevalidationRS.tmp#FreeFormTextField
Type FreeFormTextField
Properties
content: simple
Facets
minLength 1
Source
<xsd:element name="Text" type="FreeFormTextField">
  <xsd:annotation>
    <xsd:documentation>Endorsement text.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element BaseFareType / Surcharges
Namespace No namespace
Annotations
Surcharges group
Diagram
Diagram TicketRevalidationRS.tmp#SurchargesType_Amount TicketRevalidationRS.tmp#SurchargesType_Surcharge TicketRevalidationRS.tmp#SurchargesType
Type SurchargesType
Properties
content: complex
minOccurs: 0
Model Surcharge+
Children Surcharge
Instance
<Surcharges Amount="">
  <Surcharge Amount="" Segment="">{1,unbounded}</Surcharge>
</Surcharges>
Attributes
QName Type Fixed Default Use Annotation
Amount xsd:integer required
Total surcharges amount.  Example: 2000
Source
<xsd:element name="Surcharges" type="SurchargesType" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>Surcharges group</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element SurchargesType / Surcharge
Namespace No namespace
Annotations
Surcharges break down information.
Diagram
Diagram TicketRevalidationRS.tmp#SurchargeTypeBasic_Amount TicketRevalidationRS.tmp#SurchargeTypeBasic_Designator TicketRevalidationRS.tmp#SurchargeTypeBasic_Description TicketRevalidationRS.tmp#SurchargeTypeBasic TicketRevalidationRS.tmp#SurchargeType_Segment TicketRevalidationRS.tmp#SurchargeType
Type SurchargeType
Type hierarchy
Properties
content: complex
maxOccurs: unbounded
Model Designator , Description{0,1}
Children Description, Designator
Instance
<Surcharge Amount="" Segment="">
  <Designator>{1,1}</Designator>
  <Description>{0,1}</Description>
</Surcharge>
Attributes
QName Type Fixed Default Use Annotation
Amount xsd:integer required
Individual surcharge amount.  Example: 270
Segment xsd:integer required
Segment number to which the surcharge applies.  Example: 1
Source
<xsd:element name="Surcharge" type="SurchargeType" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation>Surcharges break down information.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element SurchargeTypeBasic / Designator
Namespace No namespace
Annotations
Surcharge designator.
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
Facets
minLength 1
Source
<xsd:element name="Designator">
  <xsd:annotation>
    <xsd:documentation>Surcharge designator.</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:minLength value="1"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element SurchargeTypeBasic / Description
Namespace No namespace
Annotations
Surcharge descriptions as free form text.
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
minOccurs: 0
Facets
minLength 1
Source
<xsd:element name="Description" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>Surcharge descriptions as free form text.</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:minLength value="1"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element Children / Child
Namespace No namespace
Annotations
Child elements - one per requested child.
Diagram
Diagram TicketRevalidationRS.tmp#Children_Children_Child_Age TicketRevalidationRS.tmp#Children_Children_Child_ExtraBed
Properties
content: complex
maxOccurs: unbounded
Model Age , ExtraBed{0,1}
Children Age, ExtraBed
Instance
<Child>
  <Age>{1,1}</Age>
  <ExtraBed>{0,1}</ExtraBed>
</Child>
Source
<xsd:element name="Child" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation>Child elements - one per requested child.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="Age">
        <xsd:annotation>
          <xsd:documentation>Age of child in years (allowed values are 0-17).</xsd:documentation>
        </xsd:annotation>
        <xsd:simpleType>
          <xsd:restriction base="xsd:int">
            <xsd:minInclusive value="0"/>
            <xsd:maxInclusive value="17"/>
          </xsd:restriction>
        </xsd:simpleType>
      </xsd:element>
      <xsd:element name="ExtraBed" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation>Defines if child will need its own bed ('Y') or sleep in parents bed ('N'). If omitted no extra bed is required.</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 Children / Child / Age
Namespace No namespace
Annotations
Age of child in years (allowed values are 0-17).
Diagram
Diagram
Type restriction of xsd:int
Properties
content: simple
Facets
maxInclusive 17
minInclusive 0
Source
<xsd:element name="Age">
  <xsd:annotation>
    <xsd:documentation>Age of child in years (allowed values are 0-17).</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:int">
      <xsd:minInclusive value="0"/>
      <xsd:maxInclusive value="17"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element Children / Child / ExtraBed
Namespace No namespace
Annotations
Defines if child will need its own bed ('Y') or sleep in parents bed ('N'). If omitted no extra bed is required.
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
minOccurs: 0
Facets
enumeration Y
enumeration N
Source
<xsd:element name="ExtraBed" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>Defines if child will need its own bed ('Y') or sleep in parents bed ('N'). If omitted no extra bed is required.</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 MediaType / Url
Namespace No namespace
Annotations
Hyperlink defining the location of the referenced media (e.g. location of a JPG file).
Diagram
Diagram
Type xsd:string
Properties
content: simple
Source
<xsd:element name="Url" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation>Hyperlink defining the location of the referenced media (e.g. location of a JPG file).</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element MediaType / Width
Namespace No namespace
Annotations
Width of media content in specified units.
Diagram
Diagram TicketRevalidationRS.tmp#MediaType_MediaType_Width_Unit
Type extension of xsd:int
Properties
content: complex
Attributes
QName Type Fixed Default Use Annotation
Unit MediaSizeUnitType required
Unit used to specify dimensions of media content.

Example:
mm (millimeter) 
px (pixel)
Source
<xsd:element name="Width">
  <xsd:annotation>
    <xsd:documentation>Width of media content in specified units.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:simpleContent>
      <xsd:extension base="xsd:int">
        <xsd:attribute name="Unit" type="MediaSizeUnitType" use="required">
          <xsd:annotation>
            <xsd:documentation>Unit used to specify dimensions of media content. Example: mm (millimeter) px (pixel)</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
      </xsd:extension>
    </xsd:simpleContent>
  </xsd:complexType>
</xsd:element>
[ top ]
Element MediaType / Height
Namespace No namespace
Annotations
Height of media content in specified units.
Diagram
Diagram TicketRevalidationRS.tmp#MediaType_MediaType_Height_Unit
Type extension of xsd:int
Properties
content: complex
Attributes
QName Type Fixed Default Use Annotation
Unit MediaSizeUnitType required
Unit used to specify dimensions of media content.

Example:
mm (millimeter) 
px (pixel)
Source
<xsd:element name="Height">
  <xsd:annotation>
    <xsd:documentation>Height of media content in specified units.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:simpleContent>
      <xsd:extension base="xsd:int">
        <xsd:attribute name="Unit" type="MediaSizeUnitType" use="required">
          <xsd:annotation>
            <xsd:documentation>Unit used to specify dimensions of media content. Example: mm (millimeter) px (pixel)</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
      </xsd:extension>
    </xsd:simpleContent>
  </xsd:complexType>
</xsd:element>
[ top ]
Element MediaType / Type
Namespace No namespace
Annotations
Type of media content. 

Example:
image
webcam
video 
360 (panorama view)
Diagram
Diagram TicketRevalidationRS.tmp#MediaTypeType
Type MediaTypeType
Properties
content: simple
Facets
enumeration image
enumeration webcam
enumeration 360
enumeration video
enumeration logo
enumeration map
Source
<xsd:element name="Type" type="MediaTypeType">
  <xsd:annotation>
    <xsd:documentation>Type of media content. Example: image webcam video 360 (panorama view)</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element Media / Preview
Namespace No namespace
Annotations
Preview of the referenced media content (e.g. thumbnail of the picture).
Diagram
Diagram TicketRevalidationRS.tmp#MediaType_Url TicketRevalidationRS.tmp#MediaType_Width TicketRevalidationRS.tmp#MediaType_Height TicketRevalidationRS.tmp#MediaType_Type TicketRevalidationRS.tmp#MediaType
Type MediaType
Properties
content: complex
minOccurs: 0
maxOccurs: unbounded
Model Url , Width , Height , Type
Children Height, Type, Url, Width
Instance
<Preview>
  <Url>{1,1}</Url>
  <Width Unit="">{1,1}</Width>
  <Height Unit="">{1,1}</Height>
  <Type>{1,1}</Type>
</Preview>
Source
<xsd:element name="Preview" type="MediaType" minOccurs="0" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation>Preview of the referenced media content (e.g. thumbnail of the picture).</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element Media / Description
Namespace No namespace
Annotations
Media content description (e.g. exterior view).
Diagram
Diagram
Type xsd:string
Properties
content: simple
minOccurs: 0
Source
<xsd:element name="Description" type="xsd:string" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>Media content description (e.g. exterior view).</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element ReservationsDateTime
Namespace No namespace
Annotations
Date/time when the entire booking was reserved.  Alternatively this date/time may be set independently for each flight - see ReservationsDateTime element in the Flight element of the OriginDestination element(s).
Diagram
Diagram TicketRevalidationRS.tmp#ReservationsDateTime_Date TicketRevalidationRS.tmp#ReservationsDateTime_Time
Properties
content: complex
Model Date , Time{0,1}
Children Date, Time
Instance
<ReservationsDateTime>
  <Date>{1,1}</Date>
  <Time>{0,1}</Time>
</ReservationsDateTime>
Source
<xsd:element name="ReservationsDateTime">
  <xsd:annotation>
    <xsd:documentation>Date/time when the entire booking was reserved. Alternatively this date/time may be set independently for each flight - see ReservationsDateTime element in the Flight element of the OriginDestination element(s).</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="Date" type="Date">
        <xsd:annotation>
          <xsd:documentation>Specifies date in ISO 8601 format (yyyy-mm-dd). Example: 2001-12-25</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
      <xsd:element name="Time" type="Time" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation>Specifies time in ISO 8601 twenty-four hour clock format. Example: 14:00</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element ReservationsDateTime / Date
Namespace No namespace
Annotations
Specifies date in ISO 8601 format (yyyy-mm-dd). Example: 2001-12-25
Diagram
Diagram TicketRevalidationRS.tmp#Date
Type Date
Properties
content: simple
Source
<xsd:element name="Date" type="Date">
  <xsd:annotation>
    <xsd:documentation>Specifies date in ISO 8601 format (yyyy-mm-dd). Example: 2001-12-25</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element ReservationsDateTime / Time
Namespace No namespace
Annotations
Specifies time in ISO 8601 twenty-four hour clock format. Example: 14:00
Diagram
Diagram TicketRevalidationRS.tmp#Time
Type Time
Properties
content: simple
minOccurs: 0
Facets
length 5
pattern ([0-1][0-9]|2[0-3]):[0-5][0-9]
Source
<xsd:element name="Time" type="Time" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>Specifies time in ISO 8601 twenty-four hour clock format. Example: 14:00</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element HistoricPricingDate
Namespace No namespace
Annotations
Date for which a historical pricing is requested.  When used for ticket reissue in BSP markets this is commonly the issuance date of the original ticket.
Diagram
Diagram TicketRevalidationRS.tmp#HistoricPricingDate_Date
Properties
content: complex
Model Date
Children Date
Instance
<HistoricPricingDate>
  <Date>{1,1}</Date>
</HistoricPricingDate>
Source
<xsd:element name="HistoricPricingDate">
  <xsd:annotation>
    <xsd:documentation>Date for which a historical pricing is requested. When used for ticket reissue in BSP markets this is commonly the issuance date of the original ticket.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="Date" type="Date">
        <xsd:annotation>
          <xsd:documentation>Specifies the date in ISO 8601 format (yyyy-mm-dd). Example: 2008-05-02</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element HistoricPricingDate / Date
Namespace No namespace
Annotations
Specifies the date in ISO 8601 format (yyyy-mm-dd). Example: 2008-05-02
Diagram
Diagram TicketRevalidationRS.tmp#Date
Type Date
Properties
content: simple
Source
<xsd:element name="Date" type="Date">
  <xsd:annotation>
    <xsd:documentation>Specifies the date in ISO 8601 format (yyyy-mm-dd). Example: 2008-05-02</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element AltTicketingDate
Namespace No namespace
Annotations
This date stamp specifies a future or historic alternative date validation for ticketing.
Diagram
Diagram TicketRevalidationRS.tmp#AltTicketingDate_Date
Properties
content: complex
Model Date
Children Date
Instance
<AltTicketingDate>
  <Date>{1,1}</Date>
</AltTicketingDate>
Source
<xsd:element name="AltTicketingDate">
  <xsd:annotation>
    <xsd:documentation>This date stamp specifies a future or historic alternative date validation for ticketing.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="Date" type="Date">
        <xsd:annotation>
          <xsd:documentation>Specifies date in ISO 8601 format (yyyy-mm-dd). Example: 2001-12-25</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element AltTicketingDate / Date
Namespace No namespace
Annotations
Specifies date in ISO 8601 format (yyyy-mm-dd). Example: 2001-12-25
Diagram
Diagram TicketRevalidationRS.tmp#Date
Type Date
Properties
content: simple
Source
<xsd:element name="Date" type="Date">
  <xsd:annotation>
    <xsd:documentation>Specifies date in ISO 8601 format (yyyy-mm-dd). Example: 2001-12-25</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element ClassOfService
Namespace No namespace
Annotations
Class of service.  Example: B
Diagram
Diagram TicketRevalidationRS.tmp#COSType
Type COSType
Properties
content: simple
Facets
minLength 1
maxLength 1
pattern [A-Z]
Source
<xsd:element name="ClassOfService" type="COSType">
  <xsd:annotation>
    <xsd:documentation>Class of service. Example: B</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element BookingSource
Namespace No namespace
Annotations
Agency booking source number.  Example: 99199
Diagram
Diagram
Type xsd:string
Properties
content: simple
Used by
Source
<xsd:element name="BookingSource" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation>Agency booking source number. Example: 99199</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element CarHotelSupplementalInformationType / CorporateRateOverride
Namespace No namespace
Annotations
Corporate rate override.  Example: 25900
Diagram
Diagram
Type xsd:integer
Properties
content: simple
minOccurs: 0
Source
<xsd:element name="CorporateRateOverride" type="xsd:integer" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>Corporate rate override. Example: 25900</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element CarHotelSupplementalInformationType / CorporateDiscountNumber
Namespace No namespace
Annotations
Corporate discount number.  Example: 5643356
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
minOccurs: 0
Facets
minLength 1
Source
<xsd:element name="CorporateDiscountNumber" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>Corporate discount number. Example: 5643356</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:minLength value="1"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element CarHotelSupplementalInformationType / PaymentGuarantee
Namespace No namespace
Diagram
Diagram TicketRevalidationRS.tmp#CarHotelSupplementalInformationType_CarHotelSupplementalInformationType_PaymentGuarantee_Type TicketRevalidationRS.tmp#CarHotelSupplementalInformationType_CarHotelSupplementalInformationType_PaymentGuarantee_CreditCard TicketRevalidationRS.tmp#CarHotelSupplementalInformationType_CarHotelSupplementalInformationType_PaymentGuarantee_Other
Properties
content: complex
minOccurs: 0
Model CreditCard | Other
Children CreditCard, Other
Instance
<PaymentGuarantee Type="G">
  <CreditCard>{1,1}</CreditCard>
  <Other>{1,1}</Other>
</PaymentGuarantee>
Attributes
QName Type Fixed Default Use Annotation
Type restriction of xsd:string G optional
Type of payment.  Values are:
G = Guarantee
D = Deposit
Example: G
Source
<xsd:element name="PaymentGuarantee" minOccurs="0">
  <xsd:complexType>
    <xsd:choice>
      <xsd:element name="CreditCard">
        <xsd:complexType>
          <xsd:complexContent>
            <xsd:extension base="BasicCreditCardType">
              <xsd:sequence minOccurs="0">
                <xsd:element name="CardholderFirstName" minOccurs="0">
                  <xsd:annotation>
                    <xsd:documentation>FirstName on card.</xsd:documentation>
                  </xsd:annotation>
                  <xsd:simpleType>
                    <xsd:restriction base="xsd:string">
                      <xsd:minLength value="1"/>
                    </xsd:restriction>
                  </xsd:simpleType>
                </xsd:element>
                <xsd:element name="CardholderLastName">
                  <xsd:annotation>
                    <xsd:documentation>Name on card.</xsd:documentation>
                  </xsd:annotation>
                  <xsd:simpleType>
                    <xsd:restriction base="xsd:string">
                      <xsd:minLength value="1"/>
                    </xsd:restriction>
                  </xsd:simpleType>
                </xsd:element>
              </xsd:sequence>
            </xsd:extension>
          </xsd:complexContent>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="Other">
        <xsd:simpleType>
          <xsd:restriction base="xsd:string">
            <xsd:minLength value="1"/>
          </xsd:restriction>
        </xsd:simpleType>
      </xsd:element>
    </xsd:choice>
    <xsd:attribute name="Type" use="optional" default="G">
      <xsd:annotation>
        <xsd:documentation>Type of payment. Values are: G = Guarantee D = Deposit Example: G</xsd:documentation>
      </xsd:annotation>
      <xsd:simpleType>
        <xsd:restriction base="xsd:string">
          <xsd:enumeration value="G">
            <xsd:annotation>
              <xsd:documentation>Guarantee</xsd:documentation>
            </xsd:annotation>
          </xsd:enumeration>
          <xsd:enumeration value="D">
            <xsd:annotation>
              <xsd:documentation>Deposit</xsd:documentation>
            </xsd:annotation>
          </xsd:enumeration>
        </xsd:restriction>
      </xsd:simpleType>
    </xsd:attribute>
  </xsd:complexType>
</xsd:element>
[ top ]
Element CarHotelSupplementalInformationType / PaymentGuarantee / CreditCard
Namespace No namespace
Diagram
Diagram TicketRevalidationRS.tmp#BasicCreditCardType_CCCode TicketRevalidationRS.tmp#BasicCreditCardType_CCNumber TicketRevalidationRS.tmp#BasicCreditCardType_CCExpiration TicketRevalidationRS.tmp#BasicCreditCardType TicketRevalidationRS.tmp#CarHotelSupplementalInformationType_CarHotelSupplementalInformationType_PaymentGuarantee_CarHotelSupplementalInformationType_CarHotelSupplementalInformationType_PaymentGuarantee_CreditCard_CardholderFirstName TicketRevalidationRS.tmp#CarHotelSupplementalInformationType_CarHotelSupplementalInformationType_PaymentGuarantee_CarHotelSupplementalInformationType_CarHotelSupplementalInformationType_PaymentGuarantee_CreditCard_CardholderLastName
Type extension of BasicCreditCardType
Type hierarchy
Properties
content: complex
Model CCCode , CCNumber , CCExpiration , CardholderFirstName{0,1} , CardholderLastName
Children CCCode, CCExpiration, CCNumber, CardholderFirstName, CardholderLastName
Instance
<CreditCard>
  <CCCode>{1,1}</CCCode>
  <CCNumber>{1,1}</CCNumber>
  <CCExpiration>{1,1}</CCExpiration>
  <CardholderFirstName>{0,1}</CardholderFirstName>
  <CardholderLastName>{1,1}</CardholderLastName>
</CreditCard>
Source
<xsd:element name="CreditCard">
  <xsd:complexType>
    <xsd:complexContent>
      <xsd:extension base="BasicCreditCardType">
        <xsd:sequence minOccurs="0">
          <xsd:element name="CardholderFirstName" minOccurs="0">
            <xsd:annotation>
              <xsd:documentation>FirstName on card.</xsd:documentation>
            </xsd:annotation>
            <xsd:simpleType>
              <xsd:restriction base="xsd:string">
                <xsd:minLength value="1"/>
              </xsd:restriction>
            </xsd:simpleType>
          </xsd:element>
          <xsd:element name="CardholderLastName">
            <xsd:annotation>
              <xsd:documentation>Name on card.</xsd:documentation>
            </xsd:annotation>
            <xsd:simpleType>
              <xsd:restriction base="xsd:string">
                <xsd:minLength value="1"/>
              </xsd:restriction>
            </xsd:simpleType>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
</xsd:element>
[ top ]
Element BasicCreditCardType / CCCode
Namespace No namespace
Annotations
Credit card vendor code.
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
Facets
length 2
pattern [A-Z0-9]{2}
Source
<xsd:element name="CCCode">
  <xsd:annotation>
    <xsd:documentation>Credit card vendor code.</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:length value="2"/>
      <xsd:pattern value="[A-Z0-9]{2}"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element BasicCreditCardType / CCNumber
Namespace No namespace
Annotations
Credit card number.  Example: 4011236654652341

Can be returned encrypted by GDS/CRS.
Example: XXXXXXXXXXXXXXXX
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
Facets
minLength 1
Source
<xsd:element name="CCNumber">
  <xsd:annotation>
    <xsd:documentation>Credit card number. Example: 4011236654652341 Can be returned encrypted by GDS/CRS. Example: XXXXXXXXXXXXXXXX</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:minLength value="1"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element BasicCreditCardType / CCExpiration
Namespace No namespace
Annotations
Credit card expiration group
Diagram
Diagram TicketRevalidationRS.tmp#BasicCreditCardType_BasicCreditCardType_CCExpiration_Month TicketRevalidationRS.tmp#BasicCreditCardType_BasicCreditCardType_CCExpiration_Year
Properties
content: complex
Model Month , Year
Children Month, Year
Instance
<CCExpiration>
  <Month>{1,1}</Month>
  <Year>{1,1}</Year>
</CCExpiration>
Source
<xsd:element name="CCExpiration">
  <xsd:annotation>
    <xsd:documentation>Credit card expiration group</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="Month">
        <xsd:annotation>
          <xsd:documentation>Credit card expiration month. Example: 02 Can be returned encrypted by GDS/CRS. Example: XX</xsd:documentation>
        </xsd:annotation>
        <xsd:simpleType>
          <xsd:restriction base="xsd:string">
            <xsd:pattern value="0[1-9]|1[0-2]|[^0-9]*"/>
          </xsd:restriction>
        </xsd:simpleType>
      </xsd:element>
      <xsd:element name="Year">
        <xsd:annotation>
          <xsd:documentation>Last two digits of the credit card expiration year. Example: 06 Can be returned encrypted by GDS/CRS. Example: XX</xsd:documentation>
        </xsd:annotation>
        <xsd:simpleType>
          <xsd:restriction base="xsd:string">
            <xsd:pattern value="[0-9][0-9]|[^0-9]*"/>
          </xsd:restriction>
        </xsd:simpleType>
      </xsd:element>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element BasicCreditCardType / CCExpiration / Month
Namespace No namespace
Annotations
Credit card expiration month.  Example: 02

Can be returned encrypted by GDS/CRS.
Example: XX
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
Facets
pattern 0[1-9]|1[0-2]|[^0-9]*
Source
<xsd:element name="Month">
  <xsd:annotation>
    <xsd:documentation>Credit card expiration month. Example: 02 Can be returned encrypted by GDS/CRS. Example: XX</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:pattern value="0[1-9]|1[0-2]|[^0-9]*"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element BasicCreditCardType / CCExpiration / Year
Namespace No namespace
Annotations
Last two digits of the credit card expiration year.  Example: 06

Can be returned encrypted by GDS/CRS.
Example: XX
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
Facets
pattern [0-9][0-9]|[^0-9]*
Source
<xsd:element name="Year">
  <xsd:annotation>
    <xsd:documentation>Last two digits of the credit card expiration year. Example: 06 Can be returned encrypted by GDS/CRS. Example: XX</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:pattern value="[0-9][0-9]|[^0-9]*"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element CarHotelSupplementalInformationType / PaymentGuarantee / CreditCard / CardholderFirstName
Namespace No namespace
Annotations
FirstName on card.
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
minOccurs: 0
Facets
minLength 1
Source
<xsd:element name="CardholderFirstName" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>FirstName on card.</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:minLength value="1"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element CarHotelSupplementalInformationType / PaymentGuarantee / CreditCard / CardholderLastName
Namespace No namespace
Annotations
Name on card.
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
Facets
minLength 1
Source
<xsd:element name="CardholderLastName">
  <xsd:annotation>
    <xsd:documentation>Name on card.</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:minLength value="1"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element CarHotelSupplementalInformationType / PaymentGuarantee / Other
Namespace No namespace
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
Facets
minLength 1
Source
<xsd:element name="Other">
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:minLength value="1"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element CarHotelSupplementalInformationType / FrequentGuest
Namespace No namespace
Annotations
Frequent Guest Group
Diagram
Diagram TicketRevalidationRS.tmp#CarHotelSupplementalInformationType_CarHotelSupplementalInformationType_FrequentGuest_FGCode TicketRevalidationRS.tmp#CarHotelSupplementalInformationType_CarHotelSupplementalInformationType_FrequentGuest_FGNumber
Properties
content: complex
minOccurs: 0
Model FGCode{0,1} , FGNumber
Children FGCode, FGNumber
Instance
<FrequentGuest>
  <FGCode>{0,1}</FGCode>
  <FGNumber>{1,1}</FGNumber>
</FrequentGuest>
Source
<xsd:element name="FrequentGuest" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>Frequent Guest Group</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="FGCode" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation>Frequent guest code. Example: MC</xsd:documentation>
        </xsd:annotation>
        <xsd:simpleType>
          <xsd:restriction base="xsd:string">
            <xsd:length value="2"/>
          </xsd:restriction>
        </xsd:simpleType>
      </xsd:element>
      <xsd:element name="FGNumber">
        <xsd:annotation>
          <xsd:documentation>Frequent guest number. Example: 123456</xsd:documentation>
        </xsd:annotation>
        <xsd:simpleType>
          <xsd:restriction base="xsd:string">
            <xsd:minLength value="1"/>
          </xsd:restriction>
        </xsd:simpleType>
      </xsd:element>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element CarHotelSupplementalInformationType / FrequentGuest / FGCode
Namespace No namespace
Annotations
Frequent guest code.  Example: MC
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
minOccurs: 0
Facets
length 2
Source
<xsd:element name="FGCode" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>Frequent guest code. Example: MC</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:length value="2"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element CarHotelSupplementalInformationType / FrequentGuest / FGNumber
Namespace No namespace
Annotations
Frequent guest number.  Example: 123456
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
Facets
minLength 1
Source
<xsd:element name="FGNumber">
  <xsd:annotation>
    <xsd:documentation>Frequent guest number. Example: 123456</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:minLength value="1"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element CarHotelSupplementalInformationType / FrequentFlyer
Namespace No namespace
Annotations
Frequent Flyer Group
Diagram
Diagram TicketRevalidationRS.tmp#CarHotelSupplementalInformationType_CarHotelSupplementalInformationType_FrequentFlyer_FFCode TicketRevalidationRS.tmp#CarHotelSupplementalInformationType_CarHotelSupplementalInformationType_FrequentFlyer_FFNumber
Properties
content: complex
minOccurs: 0
Model FFCode{0,1} , FFNumber
Children FFCode, FFNumber
Instance
<FrequentFlyer>
  <FFCode>{0,1}</FFCode>
  <FFNumber>{1,1}</FFNumber>
</FrequentFlyer>
Source
<xsd:element name="FrequentFlyer" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>Frequent Flyer Group</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="FFCode" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation>Frequent flyer code. Example: DL</xsd:documentation>
        </xsd:annotation>
        <xsd:simpleType>
          <xsd:restriction base="xsd:string">
            <xsd:length value="2"/>
          </xsd:restriction>
        </xsd:simpleType>
      </xsd:element>
      <xsd:element name="FFNumber">
        <xsd:annotation>
          <xsd:documentation>Frequent flyer number. Example: 0956301007</xsd:documentation>
        </xsd:annotation>
        <xsd:simpleType>
          <xsd:restriction base="xsd:string">
            <xsd:minLength value="1"/>
          </xsd:restriction>
        </xsd:simpleType>
      </xsd:element>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element CarHotelSupplementalInformationType / FrequentFlyer / FFCode
Namespace No namespace
Annotations
Frequent flyer code.  Example: DL
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
minOccurs: 0
Facets
length 2
Source
<xsd:element name="FFCode" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>Frequent flyer code. Example: DL</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:length value="2"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element CarHotelSupplementalInformationType / FrequentFlyer / FFNumber
Namespace No namespace
Annotations
Frequent flyer number.  Example: 0956301007
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
Facets
minLength 1
Source
<xsd:element name="FFNumber">
  <xsd:annotation>
    <xsd:documentation>Frequent flyer number. Example: 0956301007</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:minLength value="1"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element CarHotelSupplementalInformationType / AdditionalInformation
Namespace No namespace
Annotations
Optional additional information.  Example: Traveler on wheelchair
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
minOccurs: 0
Facets
minLength 1
Source
<xsd:element name="AdditionalInformation" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>Optional additional information. Example: Traveler on wheelchair</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:minLength value="1"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element FlightNumber
Namespace No namespace
Annotations
Flight number - an integer value within the range of [0,9999].

Example: 1234
Diagram
Diagram TicketRevalidationRS.tmp#FlightNumberType TicketRevalidationRS.tmp#FlightNumberWithSuffixType_Suffix TicketRevalidationRS.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">
  <xsd:annotation>
    <xsd:documentation>Flight number - an integer value within the range of [0,9999]. Example: 1234</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element ReferenceData
Namespace No namespace
Annotations
Displays generic refence data such as aiport code, GEO coordinates, names, car, hotel other.
Diagram
Diagram TicketRevalidationRS.tmp#ReferenceData_Airport
Properties
content: complex
Model Airport
Children Airport
Instance
<ReferenceData>
  <Airport Code="" Lat="" Long="" Name="">{1,1}</Airport>
</ReferenceData>
Source
<xsd:element name="ReferenceData">
  <xsd:annotation>
    <xsd:documentation>Displays generic refence data such as aiport code, GEO coordinates, names, car, hotel other.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="Airport">
        <xsd:annotation>
          <xsd:documentation>Aiport code and associated GEO coordinates (latitude and longitude).</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:attribute name="Code" use="required">
            <xsd:annotation>
              <xsd:documentation>IATA 3-letter airport code. Example: MIA</xsd:documentation>
            </xsd:annotation>
            <xsd:simpleType>
              <xsd:restriction base="xsd:string">
                <xsd:length value="3"/>
              </xsd:restriction>
            </xsd:simpleType>
          </xsd:attribute>
          <xsd:attribute name="Long" type="xsd:double" use="required">
            <xsd:annotation>
              <xsd:documentation>Longitude. Example: -80.277922</xsd:documentation>
            </xsd:annotation>
          </xsd:attribute>
          <xsd:attribute name="Lat" type="xsd:double" use="required">
            <xsd:annotation>
              <xsd:documentation>Latitude. Example: 25.795343</xsd:documentation>
            </xsd:annotation>
          </xsd:attribute>
          <xsd:attribute name="Name" type="xsd:string">
            <xsd:annotation>
              <xsd:documentation>Airport name</xsd:documentation>
            </xsd:annotation>
          </xsd:attribute>
        </xsd:complexType>
      </xsd:element>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element ReferenceData / Airport
Namespace No namespace
Annotations
Aiport code and associated GEO coordinates (latitude and longitude).
Diagram
Diagram TicketRevalidationRS.tmp#ReferenceData_ReferenceData_Airport_Code TicketRevalidationRS.tmp#ReferenceData_ReferenceData_Airport_Long TicketRevalidationRS.tmp#ReferenceData_ReferenceData_Airport_Lat TicketRevalidationRS.tmp#ReferenceData_ReferenceData_Airport_Name
Properties
content: complex
Attributes
QName Type Fixed Default Use Annotation
Code restriction of xsd:string required
IATA 3-letter airport code.
Example: MIA
Lat xsd:double required
Latitude.
Example: 25.795343
Long xsd:double required
Longitude.
Example: -80.277922
Name xsd:string optional
Airport name
Source
<xsd:element name="Airport">
  <xsd:annotation>
    <xsd:documentation>Aiport code and associated GEO coordinates (latitude and longitude).</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:attribute name="Code" use="required">
      <xsd:annotation>
        <xsd:documentation>IATA 3-letter airport code. Example: MIA</xsd:documentation>
      </xsd:annotation>
      <xsd:simpleType>
        <xsd:restriction base="xsd:string">
          <xsd:length value="3"/>
        </xsd:restriction>
      </xsd:simpleType>
    </xsd:attribute>
    <xsd:attribute name="Long" type="xsd:double" use="required">
      <xsd:annotation>
        <xsd:documentation>Longitude. Example: -80.277922</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:attribute name="Lat" type="xsd:double" use="required">
      <xsd:annotation>
        <xsd:documentation>Latitude. Example: 25.795343</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:attribute name="Name" type="xsd:string">
      <xsd:annotation>
        <xsd:documentation>Airport name</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
  </xsd:complexType>
</xsd:element>
[ top ]
Element CustomResponse
Namespace No namespace
Annotations
This node is used to return custom data previously requested via an error response using the InfoGroup/Error/ CustomRequest node of any supporting RS message.
Diagram
Diagram TicketRevalidationRS.tmp#Source TicketRevalidationRS.tmp#Response TicketRevalidationRS.tmp#CustomResponse_Button TicketRevalidationRS.tmp#CustomResponse_Reference
Properties
content: complex
Model Response+ , Button , Reference{0,1}
Children Button, Reference, Response
Instance
<CustomResponse Source="">
  <Response PNRLabel="">{1,unbounded}</Response>
  <Button PNRLabel="">{1,1}</Button>
  <Reference>{0,1}</Reference>
</CustomResponse>
Attributes
QName Type Fixed Default Use Annotation
Source restriction of xsd:string required
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.
Source
<xsd:element name=