SegmentTransportationType

**************************************- This is used to qualify
whether elements can apply in certain circumstances (Restrictions Apply, VTA
apply ...) or to know how something should apply (Excursion apply but is
optional, Taxes apply and are mandatory, Surcharge apply but only if a condition
is true... The roles can therefore either be a Boolean (Apply/do not Apply) or
qualified by one of the Apply Codes. **************************************-
**> True: the element applies, without any other detail. In some cases, true
and Optional could be used in the same way. If no information on how an Add-on
applies (true) it should be considered as Optional. This use of true should be
avoided. **> False: the element does not apply **> Conditional: a Rule is
attached to the elements with Me.Apply='Conditional'. In that case, if the rule
is validated, the element should apply (add the price, use the segment ...)
otherwise, it does not. **> Included: The element is already included in the
main element (included in price, duration ...) **> Mandatory: The element
must be used, but is not included in the parent element (price must be added,
duration may be added ...) **> Optional: The element can be used. Usually
Add-ons are provided as a list of optional segments. Fees could be listed in the
same way, Included, Mandatory, Optional or Conditional. Can be used both in
requests and responses **************************************-

**************************************- Maintenance:
DF/2003-11-13: Comment copied from type definition
**************************************-

This attribute is used to express the fact that the
associated element is either en envelope or an item. If omitted, the element is
considered an item (default behaviour). *An item contains the information
directly in itself. *An envelope would group items of the same nature, but the
informaton would in fact be in the child items.

This attribute is used to hold any information that would be relevant for debug purposes
It should not be present in regular exchanges, except when debug flags are positioned.

If specified, this value corresponds to the default/optimum number
of units (default number of passengers in a Vehicle, default occupancy in a
room, ...)

**************************************- used to qualify
transportation segments (both in Requests and Responses) or application rules
(such as for stops) Types and direction are tightly linked together: One Ways
are always Outbound (but it is not required to specify it) The other types can
combine Outbound and Inbound sub segments. If all segments are expressed on the
same level, the tree can still be created through the use of references.
**************************************-

**************************************- Maintenance:
DF/2003-11-13: Comment copied from type definition
**************************************-

To store the name value, but encrypted in a format and alogrithm
to be known by both extremities

**************************************- When a range is provided
with a Min - Max, boundaries may or may not be included in the range. How
extremities should be handled is provided here:
**************************************- **> None: ]Min,Max[ **> Left:
]Min,Max] **> Right: [Min,Max[ **> Both: [Min,Max] Default or omitted =
Both **************************************-

**************************************- Maintenance:
DF/2003-11-13: Comment copied from type definition
**************************************-

**************************************-
***************************************** In a request :
***************************************** used in conjunction with Match. **>
If Match is omitted, or Match=false and Filter is used, Filter does not need to
be enforced, but MAY be and is rather considered as a preference. The Match
attribute in the response may indicate whether the filter has been applied or
not. **> if Match=true, the Filter and the Rules MUST be applied
*****************************************
***************************************** In a response :
***************************************** The associated information corresponds
to data that should (Include) or should not (Exclude) be used (flight number
restrictions, black out dates, ...) **> Omitted : Filter=Include
*****************************************
**************************************-

**************************************- Maintenance:
DF/2003-11-13: Comment copied from type definition
**************************************-

This is non validated free text. ==>Composite Data : Used in
conjunction with Indexes to create composite Ids. ==>Naming groups of data :
Used to name groups of individual data such as to group the differnt memebers of
a family, different sub-trips within a trip,...

§Description: This attribute can be used to define that the corresponding parent element is Guaranteed. It may hold three values:
* true (xs:boolean)
* false (xs:boolean)
* Unknown (xft:UnknownCodeType, therefore the uppercase)

§Usage: Up to now, the usage correpsonds to  th epossibility to express taht a given departure is guaranteed for a given date.
If Guaranteed is false, it may be associated to a guarantee rule that explains how the guarantee may be optianed (like a minimum number of persons.
A guaranteed that is not provided does not correspond to a false value, but to an Unknown value.

A unique ID within an XML file. That ID can exist outside the xml
file or not.

The version for the server application. This version is different
from the XFT versin (@Version). The same XFT version may be used in different
implementations.

==>Composite Data : to order the data with the group. In that
case, Group should be used to actual define the group, except if all the items
are used to define the group. ==>A list of items : Index is used to order
them.

A passive segment is a segment that isusually present in GDS PNRs
as a placeholder for an item in the itinerary that does not result ina ticket
being issued by the GDS and for reservation that was not made directly in the
GDS. By extension, all segments that were booked in another system and added to
a booking for centralised management or system synchronisation can be marked as
passive (@IsPassive="true"). This may impact or rigger specific synchronisation
processes. To ensure that a segment is not passive, this attribute should be
set to true. If this attribute is not set, passive information remains unknown
or is not relevant because all segments are of the same
type.

Contains a technical identifier (like a database primary key, a GUID
...) by opposition to a business oriented value, like a booking reference or a
product code, which are in @Value.

***************************************** In a request :
***************************************** **> true : response MUST match
input parameters exactly. Otherwise it should not be present. **> false :
response MAY match input parameters. **> omitted : Accuracy is left at the
disposal of the hosts. Match criteria can be further defined through limits and
rules. *****************************************
***************************************** In a response :
***************************************** **> true : response matches input
parameters exactly. true can be present in a response whatever the value in the
request. **> false : response does not match input parameters. false can only
be present if Match was false or omitted in the request. **> omitted:no
information is provided by host *****************************************

Maximum number of units .

Minimum number of units associated with the
quantity

A value for the associated entity, usually more technically
oriented. Free text should be in a CDATA section

A reference to a parent object in case of hierarchical trees. This
is used to create complex tree like hierarchies

**************************************-
***************************************** In a request :
***************************************** mentions that the associated element
is the preferred choice. This can also be achieved through the Index
attribute.*****************************************
***************************************** In a response :
***************************************** information only : preferred choice
has been returned. This is for easier parsing purposes
*****************************************
**************************************-

**************************************- Maintenance:
DF/2003-11-13: Comment copied from type definition
**************************************-

Request: the requested quantity Response: the actual quantity
associated with the component This value can be used in complement with the
other attributes to provided additional information (min, max, preference,
...)

To define a position within a list without providing the extact
value. Currently it can be Left, Right or Mean. For a value, use the @Index
instead.

A reference to a valid ID within an XML file. External links are
not supported. Usually the referenced object is of the same type or the type is
obvious within the context. If several references are required, other attributed
with Ref suffix will be present. xxxcould investigate xLinks

Whether a product can be sold alone or must be sold in connection
with others.

**>A = Available **>C = Confirm / Confirmed **>N = Not
applicable / no action **> O = Option **> R = Request **> U = Unable to
confirm **> W = Waitlist **> X = Closed If there is a quantity, Status can
be omitted. If Quantity is positive Status = A If Quantity is negative or null
Status = X

**************************************- to express in Requests or
Responses whether transportation is One way, return or more complex Type and
Direction are tightly linked data : A return flight has 2 directions for
instance. **> OneWay and return are obvious **> Circular is a multi leg
circular trip **> Complex is a multi leg trip in general (From To From To2
From To3 To4 From) would qualify for a complex non circular trip **> World is
for Round the World trips **************************************-

**************************************- Maintenance:
DF/2003-11-13: Comment copied from type definition
**************************************-

EN: = Usage = This version attribute corresponds to
the version of the associated element. * For a transaction element, it
corresponds to the xft version that can be used to validate the schema. This
field being free text, it can contain either minor or major versions. Actual
schema reference can be passed in the xml stream directly to help validation.
However, the XFT schema can always be validated against the current version
available on the http://www.ExchangeForTravel.org site * When present on other
elements, it corresponds to the version of the associated element, in case the
system allows saving succesive versions. As a consequence, a version associated
to a booking would correspond to the booking version (and may even be used to
retrieve a previous version if the host allows it. = Description = This
attribute contains free text but should be a valid version (usual format is
%number%.%Number[.%Number%] but versions of different types may be used by
different service providers. = Warning = @Version vs @Implementation: * @Version
is the version of the element itself * @Implementation is the version of the
implementation of the program on the host, used to provide the
service.