Showing:

Annotations
Attributes
Diagrams
Facets
Instances
Properties
Source
Used by
Main schema NameListRS.xsd
Namespace No namespace
Properties
attribute form default: unqualified
element form default: unqualified
[ top ]
Included schema CommonTypes.xsd
Namespace No namespace
Properties
attribute form default: qualified
element form default: qualified
[ top ]
Element NameListRS
Namespace No namespace
Annotations
Name List response root element
Diagram
Diagram NameListRS.tmp#NameListRS_ActiveOnly NameListRS.tmp#InfoGroup NameListRS.tmp#ListHeader NameListRS.tmp#ListRS
Properties
content: complex
Model InfoGroup{0,1} , ListHeader , ListRS+
Children InfoGroup, ListHeader, ListRS
Instance
<NameListRS ActiveOnly="">
  <InfoGroup>{0,1}</InfoGroup>
  <ListHeader ActiveOnly="" AdvancedSearch="" MaxCount="">{1,1}</ListHeader>
  <ListRS>{1,unbounded}</ListRS>
</NameListRS>
Attributes
QName Type Fixed Default Use Annotation
ActiveOnly restriction of xsd:string optional
Y=Display Active PNR's only
N=Display all PNRs
Source
<xsd:element name="NameListRS">
  <xsd:annotation>
    <xsd:documentation>Name List response root element</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element ref="InfoGroup" minOccurs="0"/>
      <xsd:sequence minOccurs="0">
        <xsd:element ref="ListHeader">
          <xsd:annotation>
            <xsd:documentation>Request data mapped into the response to allow client app to redisplay search parameter for editing</xsd:documentation>
          </xsd:annotation>
        </xsd:element>
        <xsd:element ref="ListRS" maxOccurs="unbounded"/>
      </xsd:sequence>
    </xsd:sequence>
    <xsd:attribute name="ActiveOnly" use="optional">
      <xsd:annotation>
        <xsd:documentation>Y=Display Active PNR's only N=Display all PNRs</xsd:documentation>
      </xsd:annotation>
      <xsd:simpleType>
        <xsd:restriction base="xsd:string">
          <xsd:enumeration value="Y"/>
          <xsd:enumeration value="N"/>
        </xsd:restriction>
      </xsd:simpleType>
    </xsd:attribute>
  </xsd:complexType>
</xsd:element>
[ top ]
Element InfoGroup
Namespace No namespace
Annotations
Error and information group
Diagram
Diagram NameListRS.tmp#ForInfo NameListRS.tmp#Error
Properties
content: complex
Used by
Element NameListRS
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 NameListRS.tmp#Source NameListRS.tmp#SourceRef NameListRS.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 NameListRS.tmp#Error_ErrorType NameListRS.tmp#Source NameListRS.tmp#SourceRef NameListRS.tmp#Code NameListRS.tmp#Text NameListRS.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 NameListRS.tmp#CustomRequest_DialogTitle NameListRS.tmp#CustomRequest_Instructions NameListRS.tmp#Control NameListRS.tmp#CustomRequest_Button NameListRS.tmp#CustomRequest_OrigMsg NameListRS.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 NameListRS.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 NameListRS.tmp#Control_Type NameListRS.tmp#Control_GUILabel NameListRS.tmp#Control_PNRLabel NameListRS.tmp#Control_MouseOverText NameListRS.tmp#Control_Mandatory NameListRS.tmp#Control_Width NameListRS.tmp#Control_SameLine NameListRS.tmp#Control_Pattern NameListRS.tmp#Control_MinChar NameListRS.tmp#Control_MaxChar NameListRS.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 NameListRS.tmp#CustomRequest_CustomRequest_Button_ButtonLabel NameListRS.tmp#CustomRequest_CustomRequest_Button_Validate NameListRS.tmp#CustomRequest_CustomRequest_Button_MouseOverText NameListRS.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 NameListRS.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 NameListRS.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 ListHeader
Namespace No namespace
Diagram
Diagram NameListRS.tmp#ListHeader_ActiveOnly NameListRS.tmp#ListHeader_AdvancedSearch NameListRS.tmp#ListHeader_MaxCount NameListRS.tmp#Surname NameListRS.tmp#GivenName NameListRS.tmp#FrequentTravelerGroup NameListRS.tmp#ListHeader_GroupName NameListRS.tmp#AirlineCode NameListRS.tmp#ListHeader_FlightData NameListRS.tmp#ListHeader_OriginDestination NameListRS.tmp#Date NameListRS.tmp#ListHeader_TravelDates NameListRS.tmp#ListHeader_TicketData NameListRS.tmp#ListHeader_PNRCreationData NameListRS.tmp#ListHeader_CRS NameListRS.tmp#IATA NameListRS.tmp#ListHeader_Source
Properties
content: complex
Used by
Element NameListRS
Model ((Surname , GivenName{0,1}) | FrequentTravelerGroup | GroupName) , AirlineCode{0,1} , FlightData{0,1} , OriginDestination{0,1} , (Date{0,1} | TravelDates{0,1}) , TicketData{0,1} , PNRCreationData{0,1} , CRS* , IATA* , Source{0,1}
Children AirlineCode, CRS, Date, FlightData, FrequentTravelerGroup, GivenName, GroupName, IATA, OriginDestination, PNRCreationData, Source, Surname, TicketData, TravelDates
Instance
<ListHeader ActiveOnly="" AdvancedSearch="" MaxCount="">
  <Surname>{1,1}</Surname>
  <GivenName>{0,1}</GivenName>
  <FrequentTravelerGroup>{1,1}</FrequentTravelerGroup>
  <GroupName>{1,1}</GroupName>
  <AirlineCode>{0,1}</AirlineCode>
  <FlightData>{0,1}</FlightData>
  <OriginDestination>{0,1}</OriginDestination>
  <Date>{0,1}</Date>
  <TravelDates>{0,1}</TravelDates>
  <TicketData Status="">{0,1}</TicketData>
  <PNRCreationData Status="">{0,1}</PNRCreationData>
  <CRS>{0,unbounded}</CRS>
  <IATA>{0,unbounded}</IATA>
  <Source>{0,1}</Source>
</ListHeader>
Attributes
QName Type Fixed Default Use Annotation
ActiveOnly restriction of xsd:string optional
Specifies whether only active PNRs should be displayed (default value is 'Y' - active PNRs only).
AdvancedSearch optional
Identifies this request to be an Advanced PNR Search request.

Allowed values: 
Y/N (default)
MaxCount optional
Value provided sets the maximum item count to be returned

Example: 2000
Source
<xsd:element name="ListHeader">
  <xsd:complexType>
    <xsd:sequence>
      <xsd:choice>
        <xsd:sequence>
          <xsd:element ref="Surname">
            <xsd:annotation>
              <xsd:documentation>Traveler Last Name. Example: SMITH</xsd:documentation>
            </xsd:annotation>
          </xsd:element>
          <xsd:element ref="GivenName" minOccurs="0"/>
        </xsd:sequence>
        <xsd:element ref="FrequentTravelerGroup">
          <xsd:annotation>
            <xsd:documentation>FrequentTravelerGroup</xsd:documentation>
          </xsd:annotation>
        </xsd:element>
        <xsd:element name="GroupName">
          <xsd:annotation>
            <xsd:documentation>Example: CASTLE TOUR not combinable with other search parameter exception: Source, OfficeCode, CRS)</xsd:documentation>
          </xsd:annotation>
        </xsd:element>
      </xsd:choice>
      <xsd:element ref="AirlineCode" minOccurs="0"/>
      <xsd:element name="FlightData" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation>Searchable Flight Data</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:sequence>
            <xsd:element name="Departure">
              <xsd:complexType>
                <xsd:sequence>
                  <xsd:element ref="AirportCode"/>
                </xsd:sequence>
              </xsd:complexType>
            </xsd:element>
            <xsd:element name="Arrival" minOccurs="0">
              <xsd:complexType>
                <xsd:sequence>
                  <xsd:element ref="AirportCode"/>
                </xsd:sequence>
              </xsd:complexType>
            </xsd:element>
            <xsd:element ref="FlightNumber"/>
          </xsd:sequence>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="OriginDestination" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation>Search by origin and/or destination - identified either by 2-letter country codes or 3-letter airport/city code</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:sequence>
            <xsd:element name="Origin">
              <xsd:annotation>
                <xsd:documentation>Either the 2 letter country code or the 3-letter city/airport code</xsd:documentation>
              </xsd:annotation>
              <xsd:complexType>
                <xsd:attribute name="Type">
                  <xsd:annotation>
                    <xsd:documentation>Allowed values: C = Country A = Airport/City</xsd:documentation>
                  </xsd:annotation>
                </xsd:attribute>
              </xsd:complexType>
            </xsd:element>
            <xsd:element name="Destination">
              <xsd:annotation>
                <xsd:documentation>Either the 2 letter country code or the 3-letter city/airport code</xsd:documentation>
              </xsd:annotation>
              <xsd:complexType>
                <xsd:attribute name="Type">
                  <xsd:annotation>
                    <xsd:documentation>Allowed values: C = Country A = Airport/City</xsd:documentation>
                  </xsd:annotation>
                </xsd:attribute>
              </xsd:complexType>
            </xsd:element>
          </xsd:sequence>
        </xsd:complexType>
      </xsd:element>
      <xsd:choice>
        <xsd:annotation>
          <xsd:documentation>Search parameters for actual travel dates</xsd:documentation>
        </xsd:annotation>
        <xsd:element ref="Date" minOccurs="0">
          <xsd:annotation>
            <xsd:documentation>(Deprecated) This node is kept for BACKWARDS compatibility. A date entered here is the equivalent to "TravelDates/StartDate" and no value in "TravelDates/EndDate" - effectively searching for a specific date ONLY If entered in connection with "Flight Data" this is the mandatory DEPARTURE date</xsd:documentation>
          </xsd:annotation>
        </xsd:element>
        <xsd:element name="TravelDates" minOccurs="0">
          <xsd:annotation>
            <xsd:documentation>Establishes the start and end date of the query as it relates to the Travel Dates as found in the applicable PNRS Dates to be entered in ISO 8601 format (yyyy-mm-dd). Example: 2009-12-25</xsd:documentation>
          </xsd:annotation>
          <xsd:complexType>
            <xsd:sequence>
              <xsd:element name="StartDate" minOccurs="0">
                <xsd:annotation>
                  <xsd:documentation>the starting date (ISO format yyyy-mm-dd) of travel. Only PNRs where the departure date of any flight/segment is EQUAL or HIGHER (after) to the date provided here are included in the result set. If entered in connection with "Flight Data" this is the mandatory DEPARTURE date</xsd:documentation>
                </xsd:annotation>
              </xsd:element>
              <xsd:element name="EndDate" minOccurs="0">
                <xsd:annotation>
                  <xsd:documentation>the last day of travel (ISO format yyyy-mm-dd). Only PNRs where the departure date of any flight/segment is EQUAL or LOWER (prior) to the date provided here are included in the result set.</xsd:documentation>
                </xsd:annotation>
              </xsd:element>
            </xsd:sequence>
          </xsd:complexType>
        </xsd:element>
      </xsd:choice>
      <xsd:element name="TicketData" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation>Search parameters for ticket issuance dates as found in: PNRViewRS/PNRIdentification/TicketInfo/TicketNumer/@Date"</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:sequence>
            <xsd:annotation>
              <xsd:documentation>Dates to be entered in ISO 8601 format (yyyy-mm-dd). Example: 2010-12-25</xsd:documentation>
            </xsd:annotation>
            <xsd:element name="StartDate" minOccurs="0">
              <xsd:annotation>
                <xsd:documentation>the earliest date of issuance. Only tickets issued on a date equal or higher (after) than this date will be included.</xsd:documentation>
              </xsd:annotation>
            </xsd:element>
            <xsd:element name="EndDate" minOccurs="0">
              <xsd:annotation>
                <xsd:documentation>the last date of issuance. Only tickets issued on a date equal or less (prior) than this date will be included.</xsd:documentation>
              </xsd:annotation>
            </xsd:element>
            <xsd:element name="TicketNumber" minOccurs="0">
              <xsd:annotation>
                <xsd:documentation>13-digit ticket number This searches the PNR database by ticket number as stored in PNRViewRS/PNRIdentification/TicketInfo/TicketNumer</xsd:documentation>
              </xsd:annotation>
            </xsd:element>
          </xsd:sequence>
          <xsd:attribute name="Status">
            <xsd:annotation>
              <xsd:documentation>Allowed values: "TICKETED" "REFUNDED" "VOIDED" "EXCHANGED" "ALL" (default)</xsd:documentation>
            </xsd:annotation>
          </xsd:attribute>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="PNRCreationData" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation>Search parameters for PNR creation parameters as found in: "PNRViewRS/PNRIdentification"</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:sequence minOccurs="0">
            <xsd:annotation>
              <xsd:documentation>Dates to be entered in ISO 8601 format (yyyy-mm-dd). Example: 2010-12-25</xsd:documentation>
            </xsd:annotation>
            <xsd:element name="StartDate" minOccurs="0">
              <xsd:annotation>
                <xsd:documentation>the earliest date of PNR creation. Only PNRs created on a date equal or higher (after) than this date will be included.</xsd:documentation>
              </xsd:annotation>
            </xsd:element>
            <xsd:element name="EndDate" minOccurs="0">
              <xsd:annotation>
                <xsd:documentation>the last date of PNR creation. Only PNRs created on a date equal or lower (prior) than this date will be included.</xsd:documentation>
              </xsd:annotation>
            </xsd:element>
            <xsd:element ref="CreationAgent" minOccurs="0"/>
          </xsd:sequence>
          <xsd:attribute name="Status">
            <xsd:annotation>
              <xsd:documentation>Allowed values: "TICKETED" "REFUNDED" "VOIDED" "EXCHANGED" "ALL" (default)</xsd:documentation>
            </xsd:annotation>
          </xsd:attribute>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="CRS" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>
      <xsd:element ref="IATA" minOccurs="0" maxOccurs="unbounded"/>
      <xsd:element name="Source" type="xsd:string" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation>Identifies the source of this element. In other words where the content oroginates. Not limited to GDS, applicable to direct conect as well. Example: 1A, 1V, or other.</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
    </xsd:sequence>
    <xsd:attribute name="ActiveOnly" use="optional">
      <xsd:annotation>
        <xsd:documentation>Specifies whether only active PNRs should be displayed (default value is 'Y' - active PNRs only).</xsd:documentation>
      </xsd:annotation>
      <xsd:simpleType>
        <xsd:restriction base="xsd:string">
          <xsd:length value="1"/>
          <xsd:enumeration value="Y"/>
          <xsd:enumeration value="N"/>
        </xsd:restriction>
      </xsd:simpleType>
    </xsd:attribute>
    <xsd:attribute name="AdvancedSearch">
      <xsd:annotation>
        <xsd:documentation>Identifies this request to be an Advanced PNR Search request. Allowed values: Y/N (default)</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:attribute name="MaxCount">
      <xsd:annotation>
        <xsd:documentation>Value provided sets the maximum item count to be returned Example: 2000</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
  </xsd:complexType>
</xsd:element>
[ top ]
Element Surname
Namespace No namespace
Annotations
Traveler family (last) name.  Example: SMITH
Diagram
Diagram
Type xsd:string
Properties
content: simple
Used by
Element ListHeader
Source
<xsd:element name="Surname" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation>Traveler family (last) name. Example: SMITH</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element GivenName
Namespace No namespace
Annotations
Traveler given (first) name.  Example: JANE
Diagram
Diagram
Type xsd:string
Properties
content: simple
Used by
Element ListHeader
Source
<xsd:element name="GivenName" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation>Traveler given (first) name. Example: JANE</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element FrequentTravelerGroup
Namespace No namespace
Annotations
FrequentTravelerGroup
Diagram
Diagram NameListRS.tmp#FFCompanyCode NameListRS.tmp#FFNumber
Properties
content: complex
Used by
Element ListHeader
Model FFCompanyCode , FFNumber
Children FFCompanyCode, FFNumber
Instance
<FrequentTravelerGroup>
  <FFCompanyCode>{1,1}</FFCompanyCode>
  <FFNumber>{1,1}</FFNumber>
</FrequentTravelerGroup>
Source
<xsd:element name="FrequentTravelerGroup">
  <xsd:annotation>
    <xsd:documentation>FrequentTravelerGroup</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element ref="FFCompanyCode"/>
      <xsd:element ref="FFNumber"/>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element FFCompanyCode
Namespace No namespace
Annotations
Frequent flyer company code.  Example: AF
Diagram
Diagram
Type xsd:string
Properties
content: simple
Used by
Source
<xsd:element name="FFCompanyCode" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation>Frequent flyer company code. Example: AF</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element FFNumber
Namespace No namespace
Annotations
Frequent flyer number.  Example: 0956301007
Diagram
Diagram
Type xsd:string
Properties
content: simple
Used by
Source
<xsd:element name="FFNumber" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation>Frequent flyer number. Example: 0956301007</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element ListHeader / GroupName
Namespace No namespace
Annotations
Example: CASTLE TOUR

not combinable with other search parameter exception: Source, OfficeCode, CRS)
Diagram
Diagram
Source
<xsd:element name="GroupName">
  <xsd:annotation>
    <xsd:documentation>Example: CASTLE TOUR not combinable with other search parameter exception: Source, OfficeCode, CRS)</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element AirlineCode
Namespace No namespace
Annotations
Airline code.  Example: AA
Diagram
Diagram
Type xsd:string
Properties
content: simple
Used by
Element ListHeader
Source
<xsd:element name="AirlineCode">
  <xsd:annotation>
    <xsd:documentation>Airline code. Example: AA</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string"/>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element ListHeader / FlightData
Namespace No namespace
Annotations
Searchable Flight Data
Diagram
Diagram NameListRS.tmp#ListHeader_ListHeader_FlightData_Departure NameListRS.tmp#ListHeader_ListHeader_FlightData_Arrival NameListRS.tmp#FlightNumber
Properties
content: complex
minOccurs: 0
Model Departure , Arrival{0,1} , FlightNumber
Children Arrival, Departure, FlightNumber
Instance
<FlightData>
  <Departure>{1,1}</Departure>
  <Arrival>{0,1}</Arrival>
  <FlightNumber Suffix="">{1,1}</FlightNumber>
</FlightData>
Source
<xsd:element name="FlightData" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>Searchable Flight Data</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="Departure">
        <xsd:complexType>
          <xsd:sequence>
            <xsd:element ref="AirportCode"/>
          </xsd:sequence>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="Arrival" minOccurs="0">
        <xsd:complexType>
          <xsd:sequence>
            <xsd:element ref="AirportCode"/>
          </xsd:sequence>
        </xsd:complexType>
      </xsd:element>
      <xsd:element ref="FlightNumber"/>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element ListHeader / FlightData / Departure
Namespace No namespace
Diagram
Diagram NameListRS.tmp#AirportCode
Properties
content: complex
Model AirportCode
Children AirportCode
Instance
<Departure>
  <AirportCode>{1,1}</AirportCode>
</Departure>
Source
<xsd:element name="Departure">
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element ref="AirportCode"/>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element AirportCode
Namespace No namespace
Annotations
Airport code.  Example: MIA
Diagram
Diagram
Type xsd:string
Properties
content: simple
Used by
Source
<xsd:element name="AirportCode">
  <xsd:annotation>
    <xsd:documentation>Airport code. Example: MIA</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string"/>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element ListHeader / FlightData / Arrival
Namespace No namespace
Diagram
Diagram NameListRS.tmp#AirportCode
Properties
content: complex
minOccurs: 0
Model AirportCode
Children AirportCode
Instance
<Arrival>
  <AirportCode>{1,1}</AirportCode>
</Arrival>
Source
<xsd:element name="Arrival" minOccurs="0">
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element ref="AirportCode"/>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element FlightNumber
Namespace No namespace
Annotations
Flight number - an integer value within the range of [0,9999].

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

Example: A
Source
<xsd: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 ListHeader / OriginDestination
Namespace No namespace
Annotations
Search by origin and/or destination - identified either by 2-letter country codes or 3-letter airport/city code
Diagram
Diagram NameListRS.tmp#ListHeader_ListHeader_OriginDestination_Origin NameListRS.tmp#ListHeader_ListHeader_OriginDestination_Destination
Properties
content: complex
minOccurs: 0
Model Origin , Destination
Children Destination, Origin
Instance
<OriginDestination>
  <Origin Type="">{1,1}</Origin>
  <Destination Type="">{1,1}</Destination>
</OriginDestination>
Source
<xsd:element name="OriginDestination" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>Search by origin and/or destination - identified either by 2-letter country codes or 3-letter airport/city code</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="Origin">
        <xsd:annotation>
          <xsd:documentation>Either the 2 letter country code or the 3-letter city/airport code</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:attribute name="Type">
            <xsd:annotation>
              <xsd:documentation>Allowed values: C = Country A = Airport/City</xsd:documentation>
            </xsd:annotation>
          </xsd:attribute>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="Destination">
        <xsd:annotation>
          <xsd:documentation>Either the 2 letter country code or the 3-letter city/airport code</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:attribute name="Type">
            <xsd:annotation>
              <xsd:documentation>Allowed values: C = Country A = Airport/City</xsd:documentation>
            </xsd:annotation>
          </xsd:attribute>
        </xsd:complexType>
      </xsd:element>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element ListHeader / OriginDestination / Origin
Namespace No namespace
Annotations
Either the 2 letter country code or the 3-letter city/airport code
Diagram
Diagram NameListRS.tmp#ListHeader_ListHeader_OriginDestination_ListHeader_ListHeader_OriginDestination_Origin_Type
Properties
content: complex
Attributes
QName Type Fixed Default Use Annotation
Type optional
Allowed values:

C = Country
A = Airport/City
Source
<xsd:element name="Origin">
  <xsd:annotation>
    <xsd:documentation>Either the 2 letter country code or the 3-letter city/airport code</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:attribute name="Type">
      <xsd:annotation>
        <xsd:documentation>Allowed values: C = Country A = Airport/City</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
  </xsd:complexType>
</xsd:element>
[ top ]
Element ListHeader / OriginDestination / Destination
Namespace No namespace
Annotations
Either the 2 letter country code or the 3-letter city/airport code
Diagram
Diagram NameListRS.tmp#ListHeader_ListHeader_OriginDestination_ListHeader_ListHeader_OriginDestination_Destination_Type
Properties
content: complex
Attributes
QName Type Fixed Default Use Annotation
Type optional
Allowed values:

C = Country
A = Airport/City
Source
<xsd:element name="Destination">
  <xsd:annotation>
    <xsd:documentation>Either the 2 letter country code or the 3-letter city/airport code</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:attribute name="Type">
      <xsd:annotation>
        <xsd:documentation>Allowed values: C = Country A = Airport/City</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
  </xsd:complexType>
</xsd:element>
[ top ]
Element Date
Namespace No namespace
Annotations
The travel date.
Diagram
Diagram NameListRS.tmp#Day NameListRS.tmp#Month NameListRS.tmp#Year
Properties
content: complex
Used by
Element ListHeader
Model Day{0,1} , Month , Year
Children Day, Month, Year
Instance
<Date>
  <Day>{0,1}</Day>
  <Month>{1,1}</Month>
  <Year>{1,1}</Year>
</Date>
Source
<xsd:element name="Date">
  <xsd:annotation>
    <xsd:documentation>The travel date.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element ref="Day" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation>The day of travel in format DD</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
      <xsd:element ref="Month">
        <xsd:annotation>
          <xsd:documentation>The Month of travel in format MM</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
      <xsd:element ref="Year">
        <xsd:annotation>
          <xsd:documentation>The year of travel in format YYYY</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element Day
Namespace No namespace
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
Facets
length 2
Used by
Element Date
Source
<xsd:element name="Day">
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:length value="2"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element Month
Namespace No namespace
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
Facets
length 2
Used by
Element Date
Source
<xsd:element name="Month">
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:length value="2"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element Year
Namespace No namespace
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
Facets
length 4
Used by
Element Date
Source
<xsd:element name="Year">
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:length value="4"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element ListHeader / TravelDates
Namespace No namespace
Annotations
Establishes the start and end date of the query as it relates to the Travel Dates 
as found in the applicable PNRS

Dates to be entered in ISO 8601 format (yyyy-mm-dd). Example: 2009-12-25
Diagram
Diagram NameListRS.tmp#ListHeader_ListHeader_TravelDates_StartDate NameListRS.tmp#ListHeader_ListHeader_TravelDates_EndDate
Properties
content: complex
minOccurs: 0
Model StartDate{0,1} , EndDate{0,1}
Children EndDate, StartDate
Instance
<TravelDates>
  <StartDate>{0,1}</StartDate>
  <EndDate>{0,1}</EndDate>
</TravelDates>
Source
<xsd:element name="TravelDates" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>Establishes the start and end date of the query as it relates to the Travel Dates as found in the applicable PNRS Dates to be entered in ISO 8601 format (yyyy-mm-dd). Example: 2009-12-25</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="StartDate" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation>the starting date (ISO format yyyy-mm-dd) of travel. Only PNRs where the departure date of any flight/segment is EQUAL or HIGHER (after) to the date provided here are included in the result set. If entered in connection with "Flight Data" this is the mandatory DEPARTURE date</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
      <xsd:element name="EndDate" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation>the last day of travel (ISO format yyyy-mm-dd). Only PNRs where the departure date of any flight/segment is EQUAL or LOWER (prior) to the date provided here are included in the result set.</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element ListHeader / TravelDates / StartDate
Namespace No namespace
Annotations
the starting date (ISO format yyyy-mm-dd) of travel. Only PNRs where the departure date of any flight/segment is EQUAL or HIGHER (after) to the date provided here are included in the result set.

If entered in connection with "Flight Data" this is the mandatory DEPARTURE date
Diagram
Diagram
Properties
minOccurs: 0
Source
<xsd:element name="StartDate" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>the starting date (ISO format yyyy-mm-dd) of travel. Only PNRs where the departure date of any flight/segment is EQUAL or HIGHER (after) to the date provided here are included in the result set. If entered in connection with "Flight Data" this is the mandatory DEPARTURE date</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element ListHeader / TravelDates / EndDate
Namespace No namespace
Annotations
the last day of travel (ISO format yyyy-mm-dd). Only PNRs where the departure date of any flight/segment is EQUAL or LOWER (prior) to the date provided here are included in the result set.
Diagram
Diagram
Properties
minOccurs: 0
Source
<xsd:element name="EndDate" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>the last day of travel (ISO format yyyy-mm-dd). Only PNRs where the departure date of any flight/segment is EQUAL or LOWER (prior) to the date provided here are included in the result set.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element ListHeader / TicketData
Namespace No namespace
Annotations
Search parameters for ticket issuance dates as found in: PNRViewRS/PNRIdentification/TicketInfo/TicketNumer/@Date"
Diagram
Diagram NameListRS.tmp#ListHeader_ListHeader_TicketData_Status NameListRS.tmp#ListHeader_ListHeader_TicketData_StartDate NameListRS.tmp#ListHeader_ListHeader_TicketData_EndDate NameListRS.tmp#ListHeader_ListHeader_TicketData_TicketNumber
Properties
content: complex
minOccurs: 0
Model StartDate{0,1} , EndDate{0,1} , TicketNumber{0,1}
Children EndDate, StartDate, TicketNumber
Instance
<TicketData Status="">
  <StartDate>{0,1}</StartDate>
  <EndDate>{0,1}</EndDate>
  <TicketNumber>{0,1}</TicketNumber>
</TicketData>
Attributes
QName Type Fixed Default Use Annotation
Status optional
Allowed values:

"TICKETED"
"REFUNDED"
"VOIDED"
"EXCHANGED" 
"ALL" (default)
Source
<xsd:element name="TicketData" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>Search parameters for ticket issuance dates as found in: PNRViewRS/PNRIdentification/TicketInfo/TicketNumer/@Date"</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:annotation>
        <xsd:documentation>Dates to be entered in ISO 8601 format (yyyy-mm-dd). Example: 2010-12-25</xsd:documentation>
      </xsd:annotation>
      <xsd:element name="StartDate" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation>the earliest date of issuance. Only tickets issued on a date equal or higher (after) than this date will be included.</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
      <xsd:element name="EndDate" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation>the last date of issuance. Only tickets issued on a date equal or less (prior) than this date will be included.</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
      <xsd:element name="TicketNumber" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation>13-digit ticket number This searches the PNR database by ticket number as stored in PNRViewRS/PNRIdentification/TicketInfo/TicketNumer</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
    </xsd:sequence>
    <xsd:attribute name="Status">
      <xsd:annotation>
        <xsd:documentation>Allowed values: "TICKETED" "REFUNDED" "VOIDED" "EXCHANGED" "ALL" (default)</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
  </xsd:complexType>
</xsd:element>
[ top ]
Element ListHeader / TicketData / StartDate
Namespace No namespace
Annotations
the earliest date of issuance. Only tickets issued on a date equal or higher (after) than this date will be included.
Diagram
Diagram
Properties
minOccurs: 0
Source
<xsd:element name="StartDate" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>the earliest date of issuance. Only tickets issued on a date equal or higher (after) than this date will be included.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element ListHeader / TicketData / EndDate
Namespace No namespace
Annotations
the last date of issuance. Only tickets issued on a date equal or less (prior) than this date will be included.
Diagram
Diagram
Properties
minOccurs: 0
Source
<xsd:element name="EndDate" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>the last date of issuance. Only tickets issued on a date equal or less (prior) than this date will be included.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element ListHeader / TicketData / TicketNumber
Namespace No namespace
Annotations
13-digit ticket number

This searches the PNR database by ticket number as stored in PNRViewRS/PNRIdentification/TicketInfo/TicketNumer
Diagram
Diagram
Properties
minOccurs: 0
Source
<xsd:element name="TicketNumber" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>13-digit ticket number This searches the PNR database by ticket number as stored in PNRViewRS/PNRIdentification/TicketInfo/TicketNumer</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element ListHeader / PNRCreationData
Namespace No namespace
Annotations
Search parameters for PNR  creation parameters as found in: "PNRViewRS/PNRIdentification"
Diagram
Diagram NameListRS.tmp#ListHeader_ListHeader_PNRCreationData_Status NameListRS.tmp#ListHeader_ListHeader_PNRCreationData_StartDate NameListRS.tmp#ListHeader_ListHeader_PNRCreationData_EndDate NameListRS.tmp#CreationAgent
Properties
content: complex
minOccurs: 0
Model StartDate{0,1} , EndDate{0,1} , CreationAgent{0,1}
Children CreationAgent, EndDate, StartDate
Instance
<PNRCreationData Status="">
  <StartDate>{0,1}</StartDate>
  <EndDate>{0,1}</EndDate>
  <CreationAgent>{0,1}</CreationAgent>
</PNRCreationData>
Attributes
QName Type Fixed Default Use Annotation
Status optional
Allowed values:

"TICKETED"
"REFUNDED"
"VOIDED"
"EXCHANGED" 
"ALL" (default)
Source
<xsd:element name="PNRCreationData" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>Search parameters for PNR creation parameters as found in: "PNRViewRS/PNRIdentification"</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence minOccurs="0">
      <xsd:annotation>
        <xsd:documentation>Dates to be entered in ISO 8601 format (yyyy-mm-dd). Example: 2010-12-25</xsd:documentation>
      </xsd:annotation>
      <xsd:element name="StartDate" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation>the earliest date of PNR creation. Only PNRs created on a date equal or higher (after) than this date will be included.</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
      <xsd:element name="EndDate" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation>the last date of PNR creation. Only PNRs created on a date equal or lower (prior) than this date will be included.</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
      <xsd:element ref="CreationAgent" minOccurs="0"/>
    </xsd:sequence>
    <xsd:attribute name="Status">
      <xsd:annotation>
        <xsd:documentation>Allowed values: "TICKETED" "REFUNDED" "VOIDED" "EXCHANGED" "ALL" (default)</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
  </xsd:complexType>
</xsd:element>
[ top ]
Element ListHeader / PNRCreationData / StartDate
Namespace No namespace
Annotations
the earliest date of PNR creation. Only PNRs created on a date equal or higher (after) than this date will be included.
Diagram
Diagram
Properties
minOccurs: 0
Source
<xsd:element name="StartDate" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>the earliest date of PNR creation. Only PNRs created on a date equal or higher (after) than this date will be included.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element ListHeader / PNRCreationData / EndDate
Namespace No namespace
Annotations
the last date of PNR creation. Only PNRs created on a date equal or lower (prior) than this date will be included.
Diagram
Diagram
Properties
minOccurs: 0
Source
<xsd:element name="EndDate" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>the last date of PNR creation. Only PNRs created on a date equal or lower (prior) than this date will be included.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element CreationAgent
Namespace No namespace
Annotations
Agent ID.  Example: RI17
Diagram
Diagram
Type xsd:string
Properties
content: simple
Used by
Source
<xsd:element name="CreationAgent" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation>Agent ID. Example: RI17</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element ListHeader / CRS
Namespace No namespace
Diagram
Diagram
Type xsd:string
Properties
content: simple
minOccurs: 0
maxOccurs: unbounded
Source
<xsd:element name="CRS" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>
[ top ]
Element IATA
Namespace No namespace
Annotations
Agent iata number.  Example: 123456
Diagram
Diagram
Type xsd:string
Properties
content: simple
Used by
Element ListHeader
Complex Type Item
Source
<xsd:element name="IATA" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation>Agent iata number. Example: 123456</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element ListHeader / Source
Namespace No namespace
Annotations
Identifies the source of this  element. In other words where the content oroginates. Not limited to GDS, applicable to direct conect as well. Example: 1A, 1V, or other.
Diagram
Diagram
Type xsd:string
Properties
content: simple
minOccurs: 0
Source
<xsd:element name="Source" type="xsd:string" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>Identifies the source of this element. In other words where the content oroginates. Not limited to GDS, applicable to direct conect as well. Example: 1A, 1V, or other.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element ListRS
Namespace No namespace
Annotations
List of Responses
Diagram
Diagram NameListRS.tmp#Index
Properties
content: complex
Used by
Element NameListRS
Model Index
Children Index
Instance
<ListRS>
  <Index ItemCount="">{1,1}</Index>
</ListRS>
Source
<xsd:element name="ListRS">
  <xsd:annotation>
    <xsd:documentation>List of Responses</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element ref="Index"/>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element Index
Namespace No namespace
Annotations
Group of PNR-Items
Diagram
Diagram NameListRS.tmp#Index_ItemCount NameListRS.tmp#Index_Item
Properties
content: complex
Used by
Element ListRS
Model Item+
Children Item
Instance
<Index ItemCount="">
  <Item Status="">{1,unbounded}</Item>
</Index>
Attributes
QName Type Fixed Default Use Annotation
ItemCount xsd:integer required
Count of Items returned
Source
<xsd:element name="Index">
  <xsd:annotation>
    <xsd:documentation>Group of PNR-Items</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="Item" type="Item" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation>PNR-Item</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
    </xsd:sequence>
    <xsd:attribute name="ItemCount" type="xsd:integer" use="required">
      <xsd:annotation>
        <xsd:documentation>Count of Items returned</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
  </xsd:complexType>
</xsd:element>
[ top ]
Element Index / Item
Namespace No namespace
Annotations
PNR-Item
Diagram
Diagram NameListRS.tmp#Item_Status NameListRS.tmp#Item_Number NameListRS.tmp#Item_Name NameListRS.tmp#NumberInParty NameListRS.tmp#Item_ItineraryStartDate NameListRS.tmp#Item_DepartureCode NameListRS.tmp#Item_ArrivalCode NameListRS.tmp#Item_ODDepartureCode NameListRS.tmp#Item_ODArrivalCode NameListRS.tmp#Item_Vendor NameListRS.tmp#Item_RecordLocator NameListRS.tmp#Item_CreationDate NameListRS.tmp#Item_CreationTime NameListRS.tmp#Item_CreationAgent NameListRS.tmp#OfficeCode NameListRS.tmp#IATA NameListRS.tmp#Item
Type Item
Properties
content: complex
maxOccurs: unbounded
Model Number , Name , NumberInParty{0,1} , ItineraryStartDate{0,1} , DepartureCode{0,1} , ArrivalCode{0,1} , ODDepartureCode{0,1} , ODArrivalCode{0,1} , Vendor{0,1} , RecordLocator{0,1} , CreationDate{0,1} , CreationTime{0,1} , CreationAgent{0,1} , OfficeCode{0,1} , IATA{0,1}
Children ArrivalCode, CreationAgent, CreationDate, CreationTime, DepartureCode, IATA, ItineraryStartDate, Name, Number, NumberInParty, ODArrivalCode, ODDepartureCode, OfficeCode, RecordLocator, Vendor
Instance
<Item Status="">
  <Number>{1,1}</Number>
  <Name>{1,1}</Name>
  <NumberInParty>{0,1}</NumberInParty>
  <ItineraryStartDate>{0,1}</ItineraryStartDate>
  <DepartureCode>{0,1}</DepartureCode>
  <ArrivalCode>{0,1}</ArrivalCode>
  <ODDepartureCode>{0,1}</ODDepartureCode>
  <ODArrivalCode>{0,1}</ODArrivalCode>
  <Vendor>{0,1}</Vendor>
  <RecordLocator>{0,1}</RecordLocator>
  <CreationDate>{0,1}</CreationDate>
  <CreationTime>{0,1}</CreationTime>
  <CreationAgent>{0,1}</CreationAgent>
  <OfficeCode>{0,1}</OfficeCode>
  <IATA>{0,1}</IATA>
</Item>
Attributes
QName Type Fixed Default Use Annotation
Status restriction of xsd:string optional
Status, if Item is active or cancelled
Source
<xsd:element name="Item" type="Item" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation>PNR-Item</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element Item / Number
Namespace No namespace
Annotations
Item number in the index
Diagram
Diagram
Type xsd:integer
Properties
content: simple
Source
<xsd:element name="Number" type="xsd:integer">
  <xsd:annotation>
    <xsd:documentation>Item number in the index</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element Item / Name
Namespace No namespace
Annotations
Namegroup
Diagram
Diagram NameListRS.tmp#Item_Item_Name_Surname NameListRS.tmp#Item_Item_Name_GivenName NameListRS.tmp#Item_Item_Name_TravelerElementNumber
Properties
content: complex
Model Surname , GivenName , TravelerElementNumber{0,1}
Children GivenName, Surname, TravelerElementNumber
Instance
<Name>
  <Surname>{1,1}</Surname>
  <GivenName>{1,1}</GivenName>
  <TravelerElementNumber>{0,1}</TravelerElementNumber>
</Name>
Source
<xsd:element name="Name">
  <xsd:annotation>
    <xsd:documentation>Namegroup</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="Surname" type="xsd:string"/>
      <xsd:element name="GivenName" type="xsd:string"/>
      <xsd:element name="TravelerElementNumber" minOccurs="0"/>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element Item / Name / Surname
Namespace No namespace
Diagram
Diagram
Type xsd:string
Properties
content: simple
Source
<xsd:element name="Surname" type="xsd:string"/>
[ top ]
Element Item / Name / GivenName
Namespace No namespace
Diagram
Diagram
Type xsd:string
Properties
content: simple
Source
<xsd:element name="GivenName" type="xsd:string"/>
[ top ]
Element Item / Name / TravelerElementNumber
Namespace No namespace
Diagram
Diagram
Properties
minOccurs: 0
Source
<xsd:element name="TravelerElementNumber" minOccurs="0"/>
[ top ]
Element NumberInParty
Namespace No namespace
Annotations
Number of travelers in PNR.
Example: 3
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
Facets
length 2
Used by
Complex Type Item
Source
<xsd:element name="NumberInParty">
  <xsd:annotation>
    <xsd:documentation>Number of travelers in PNR. Example: 3</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:length value="2"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element Item / ItineraryStartDate
Namespace No namespace
Annotations
Itinerary start date in ISO 8601 format.  Example: 2001-12-25
Diagram
Diagram
Type xsd:date
Properties
content: simple
minOccurs: 0
Source
<xsd:element name="ItineraryStartDate" type="xsd:date" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>Itinerary start date in ISO 8601 format. Example: 2001-12-25</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element Item / DepartureCode
Namespace No namespace
Annotations
3LC for Departure in first segment
Diagram
Diagram
Type xsd:string
Properties
content: simple
minOccurs: 0
Source
<xsd:element name="DepartureCode" type="xsd:string" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>3LC for Departure in first segment</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element Item / ArrivalCode
Namespace No namespace
Annotations
3LC for Arrival in first segment
Diagram
Diagram
Type xsd:string
Properties
content: simple
minOccurs: 0
Source
<xsd:element name="ArrivalCode" type="xsd:string" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>3LC for Arrival in first segment</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element Item / ODDepartureCode
Namespace No namespace
Annotations
3LC for Departure for first OriginDestination node
Diagram
Diagram
Type xsd:string
Properties
content: simple
minOccurs: 0
Source
<xsd:element name="ODDepartureCode" type="xsd:string" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>3LC for Departure for first OriginDestination node</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element Item / ODArrivalCode
Namespace No namespace
Annotations
3LC for Arrival for first OriginDestination node
Diagram
Diagram
Type xsd:string
Properties
content: simple
minOccurs: 0
Source
<xsd:element name="ODArrivalCode" type="xsd:string" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>3LC for Arrival for first OriginDestination node</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element Item / Vendor
Namespace No namespace
Annotations
Vendor data for first segment
Diagram
Diagram NameListRS.tmp#Item_Item_Vendor_Code NameListRS.tmp#Item_Item_Vendor_FlightNumber NameListRS.tmp#Item_Item_Vendor_Name NameListRS.tmp#Item_Item_Vendor_Type
Properties
content: complex
minOccurs: 0
Model Code , FlightNumber{0,1} , Name , Type
Children Code, FlightNumber, Name, Type
Instance
<Vendor>
  <Code>{1,1}</Code>
  <FlightNumber>{0,1}</FlightNumber>
  <Name>{1,1}</Name>
  <Type>{1,1}</Type>
</Vendor>
Source
<xsd:element name="Vendor" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>Vendor data for first segment</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="Code" type="xsd:string">
        <xsd:annotation>
          <xsd:documentation>Vendor Code e.g. LH=Lufthansa</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
      <xsd:element name="FlightNumber" type="xsd:string" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation>Flight number when vendor type = A (Airline)</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
      <xsd:element name="Name" type="xsd:string">
        <xsd:annotation>
          <xsd:documentation>Vendor Name e.g. United Airlines</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
      <xsd:element name="Type">
        <xsd:annotation>
          <xsd:documentation>Vendor Type: A=Airline, C=Car, H=Hotel, X=Unrecognized</xsd:documentation>
        </xsd:annotation>
        <xsd:simpleType>
          <xsd:restriction base="xsd:string">
            <xsd:length value="1"/>
            <xsd:enumeration value="A"/>
            <xsd:enumeration value="C"/>
            <xsd:enumeration value="H"/>
            <xsd:enumeration value="X"/>
          </xsd:restriction>
        </xsd:simpleType>
      </xsd:element>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element Item / Vendor / Code
Namespace No namespace
Annotations
Vendor Code e.g. LH=Lufthansa
Diagram
Diagram
Type xsd:string
Properties
content: simple
Source
<xsd:element name="Code" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation>Vendor Code e.g. LH=Lufthansa</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element Item / Vendor / FlightNumber
Namespace No namespace
Annotations
Flight number when vendor type = A (Airline)
Diagram
Diagram
Type xsd:string
Properties
content: simple
minOccurs: 0
Source
<xsd:element name="FlightNumber" type="xsd:string" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>Flight number when vendor type = A (Airline)</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element Item / Vendor / Name
Namespace No namespace
Annotations
Vendor Name e.g. United Airlines
Diagram
Diagram
Type xsd:string
Properties
content: simple
Source
<xsd:element name="Name" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation>Vendor Name e.g. United Airlines</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element Item / Vendor / Type
Namespace No namespace
Annotations
Vendor Type:
A=Airline, 
C=Car, 
H=Hotel, X=Unrecognized
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
Facets
length 1
enumeration A
enumeration C
enumeration H
enumeration X
Source
<xsd:element name="Type">
  <xsd:annotation>
    <xsd:documentation>Vendor Type: A=Airline, C=Car, H=Hotel, X=Unrecognized</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:length value="1"/>
      <xsd:enumeration value="A"/>
      <xsd:enumeration value="C"/>
      <xsd:enumeration value="H"/>
      <xsd:enumeration value="X"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element Item / RecordLocator
Namespace No namespace
Annotations
RecordLocator of the PNR Item. Will be returned for all CRS except Sabre.

For Sabre, the RecordLocator will not be returned except for those PNR, which are at the same time retrieved as a whole as /NameListRS/PNRViewRS elements (because they lie within the range specified with /NameListRQ/@Begin and /NameListRQ/@End). This is a Sabre system limitation.
Diagram
Diagram
Type xsd:string
Properties
content: simple
minOccurs: 0
Source
<xsd:element name="RecordLocator" type="xsd:string" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>RecordLocator of the PNR Item. Will be returned for all CRS except Sabre. For Sabre, the RecordLocator will not be returned except for those PNR, which are at the same time retrieved as a whole as /NameListRS/PNRViewRS elements (because they lie within the range specified with /NameListRQ/@Begin and /NameListRQ/@End). This is a Sabre system limitation.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element Item / CreationDate
Namespace No namespace
Annotations
Specifies date in which PNR was created in ISO 8601 format (yyyy-mm-dd).  Example: 2001-12-25
Diagram
Diagram
Type xsd:date
Properties
content: simple
minOccurs: 0
Source
<xsd:element name="CreationDate" type="xsd:date" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>Specifies date in which PNR was created in ISO 8601 format (yyyy-mm-dd). Example: 2001-12-25</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element Item / CreationTime
Namespace No namespace
Annotations
Creation time in ISO 8601 format.  Example: 12:35
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
minOccurs: 0
Facets
pattern ([0-1][0-9]|2[0-4]):[0-5][0-9]
Source
<xsd:element name="CreationTime" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>Creation time in ISO 8601 format. Example: 12:35</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:pattern value="([0-1][0-9]|2[0-4]):[0-5][0-9]">
        <xsd:annotation>
          <xsd:documentation>
          </xsd:documentation>
        </xsd:annotation>
      </xsd:pattern>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element Item / CreationAgent
Namespace No namespace
Annotations
Agent ID.  
Example: RI17
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
minOccurs: 0
Facets
pattern ([0-1][0-9]|2[0-4]):[0-5][0-9]
Source
<xsd:element name="CreationAgent" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>Agent ID. Example: RI17</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:pattern value="([0-1][0-9]|2[0-4]):[0-5][0-9]">
        <xsd:annotation>
          <xsd:documentation>
          </xsd:documentation>
        </xsd:annotation>
      </xsd:pattern>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element OfficeCode
Namespace No namespace
Annotations
PseudoCityCode (PCC).  Example: AAL0
Diagram
Diagram
Type xsd:string
Properties
content: simple
Used by
Complex Type Item
Source
<xsd:element name="OfficeCode" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation>PseudoCityCode (PCC). Example: AAL0</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element ItemCount
Namespace No namespace
Annotations
Count of items returned
Diagram
Diagram
Type xsd:integer
Properties
content: simple
Source
<xsd:element name="ItemCount" type="xsd:integer">
  <xsd:annotation>
    <xsd:documentation>Count of items returned</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 NameListRS.tmp#CurrencyCode NameListRS.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 NameListRS.tmp#CurrencyCodeType_NumberOfDecimals NameListRS.tmp#CurrencyCodeType NameListRS.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 NameListRS.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 NameListRS.tmp#HistoricalPricingInfo_ReservationDateTime NameListRS.tmp#HistoricalPricingInfo_TicketedDateTime NameListRS.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 NameListRS.tmp#HistoricalPricingInfo_HistoricalPricingInfo_ReservationDateTime_Date NameListRS.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 NameListRS.tmp#NO_NAMESPACE_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 NameListRS.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 NameListRS.tmp#HistoricalPricingInfo_HistoricalPricingInfo_TicketedDateTime_Date NameListRS.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 NameListRS.tmp#NO_NAMESPACE_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 NameListRS.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 NameListRS.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 NameListRS.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 NameListRS.tmp#Radius NameListRS.tmp#DistanceUnit NameListRS.tmp#Longitude NameListRS.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 NameListRS.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 NameListRS.tmp#POIDistance_POIType NameListRS.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 NameListRS.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 NameListRS.tmp#SurchargesType_Amount NameListRS.tmp#SurchargesType_Surcharge NameListRS.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 NameListRS.tmp#SurchargeTypeBasic_Amount NameListRS.tmp#SurchargeTypeBasic_Designator NameListRS.tmp#SurchargeTypeBasic_Description NameListRS.tmp#SurchargeTypeBasic NameListRS.tmp#SurchargeType_Segment NameListRS.tmp#SurchargeType
Type SurchargeType
Type hierarchy
Properties
content: complex
maxOccurs: unbounded
Model Designator , Description{0,1}
Children