Tabular overview of all nodes, which may occur in this message. See legend below for description of table columns.
Note: Some sibling elements or complete sub-trees of the hierarchy may be defined as mutually exclusive alternative choices. This information cannot be expressed in this tabular overview. Please refer to schema diagram for a graphical representation of the message schema.
| Node | Description | Values | Occurs | Example |
|---|---|---|---|---|
<InterlineAgreementRQ> | Display interline agreements between a validating carrier and partner carriers. | 1 | ||
<ValidatingCarrierCode/> | 2 character airline code of the validating/issuing carrier to request agreements for. | 1 | LH | |
<InterlineAgreementRequest> | Include this element (without text content) to request interline agreements. This element is required, as the message may be extended in future to support other agreement types. | 1 | ||
<PartnerCarrierCode/> | 2 character airline code of the partner carrier to request agreements for. If not specified, all partner carriers, with whom the validating carrier has agreements, will be displayed. NOTE: The PartnerCarrierCode is mandatory for Sabre. | 0..1 | AF | |
</InterlineAgreementRequest> | ||||
</InterlineAgreementRQ> |
| Column | Description |
|---|---|
| Node | Name of message node (element or attribute). Nodes in bold type are mandatory, if their parent element occurs in the message. Point mouse cursor at table cell to view complete XPath. |
| Description | Description of meaning and usage of the node. |
| Values | List of predefined values (each in square brackets) or range of values ("[a] to [z]") allowed for the node, if formally defined in the schema. |
| Occurs | Minimum and maximum number of times the node must/may occur, if its parent element occurs in the message. Examples: 0..3 Node is optional and may occur up to 3 times. 1..N Node must occur at least one (mandatory) and may occur any number of times. 2 Node must occur exactly twice. |
| Example | Example value for the node. |
XML Schema documentation generated with XX/1 server