ActionGroup 

The basic data used to define the action the action verb (the code and
the action name)

Attribute Group Information

Attributes

QName Type Fixed Default Use Inheritable Annotation
Code ActionCodeType required 
**************************************- The action code is used
in connection with the action purpose to define what the action should be.
Actions can be very diverse. The purpose corresponds to the verb (Do, Create...)
whereas the code is the name defining on what the action should take place.
Other information may be required for the action to be completely defined. All
codes cannot be combined with all purposes. All parties will not implement all
combinations. Some codes are directed more to the providers of information and
some are more related to intermediate processing or to describe actions within
conditional or recursive statements **************************************- List
of Codes for data management **************************************- AddOn: to
specify search or detail or booking of additional add on (excursions, diners
...) Availability: alone, without price information (otherwise use
QuotedAvailability) Booking: (Create, Delete, Search ...) Description: to
retrieve long description that where omitted in the first transaction for better
efficiency. List: to retrieve lists in general (products, bookings, possible Add
On) Quote: (Booking/Trip) QuotedAvailability: (combine Quote and Availability).
Used only with Get/Sort/Filter **************************************- List of
Codes for processing management **************************************-
Alternate: to request alternatives Cache: some third parties may provide caching
feature. Instructions about Adding data to cache or excluding/including cache
data can be requested in the messages Duplicates: to allow filtering duplicates,
(in case of multiple sources for instance) Source: of the data. For filtering
sources (if cache only should be used or certain source types)
**************************************-
Purpose ActionPurposeCodeType required 
**************************************- The action purpose is
used in connection with the action code to define what the action should be.
Actions can be very diverse. The purpose corresponds to the verb (Do, Create...)
whereas the code is the name defining on what the action should take place.
Other information may be required for the action to be completely defined. All
purposes cannot be combined with all codes. All parties will not implement all
combinations. Some purposes are directed more to the providers of information
and some are more related to intermediate processing or to describe actions
within conditional or recursive statements
**************************************- List of Purposes for data management
**************************************- AddTo (Booking, Basket, Product ...)
Create (Customer, Booking ...) Delete (Booking, Product, Traveller ...) Get
(Booking, Availability ...) Replace (Something with Something (a Segment by
another, a Telephone with another)) Replace (Something with something Update
(something): The difference between Replace and Update is that for Update,
elements to update is not given **************************************- List of
Purposes for processing management **************************************-
Exclude (Cache, Source ...) Exit (to exit Statements such as if, loop,
processing ...): this is used for Conditions and Actions in case complex
descriptions are required. Filter (responses, hosts ...): Connections to a
provider may be via several intermediate parties which could provide added
values. Filtering is one of the added values, sort is another. RestrictTo
(Cahce,Source ...) Sort (list ...) Stop (A statement ...): the difference
between Exit and Stop is that Exit exits the statement but not the whole
process, whereas Stop stops the process altogether.
**************************************-

Used By

Complex Type ActionType

Source 

<xs:attributeGroup name="ActionGroup">
  <xs:annotation>
    <xs:documentation>The basic data used to define the action the action verb (the code and the action name)</xs:documentation>
  </xs:annotation>
  <xs:attribute name="Code" type="ActionCodeType" use="required">
    <xs:annotation>
      <xs:documentation>**************************************- The action code is used in connection with the action purpose to define what the action should be. Actions can be very diverse. The purpose corresponds to the verb (Do, Create...) whereas the code is the name defining on what the action should take place. Other information may be required for the action to be completely defined. All codes cannot be combined with all purposes. All parties will not implement all combinations. Some codes are directed more to the providers of information and some are more related to intermediate processing or to describe actions within conditional or recursive statements **************************************- List of Codes for data management **************************************- AddOn: to specify search or detail or booking of additional add on (excursions, diners ...) Availability: alone, without price information (otherwise use QuotedAvailability) Booking: (Create, Delete, Search ...) Description: to retrieve long description that where omitted in the first transaction for better efficiency. List: to retrieve lists in general (products, bookings, possible Add On) Quote: (Booking/Trip) QuotedAvailability: (combine Quote and Availability). Used only with Get/Sort/Filter **************************************- List of Codes for processing management **************************************- Alternate: to request alternatives Cache: some third parties may provide caching feature. Instructions about Adding data to cache or excluding/including cache data can be requested in the messages Duplicates: to allow filtering duplicates, (in case of multiple sources for instance) Source: of the data. For filtering sources (if cache only should be used or certain source types) **************************************-</xs:documentation>
    </xs:annotation>
  </xs:attribute>
  <xs:attribute name="Purpose" type="ActionPurposeCodeType" use="required">
    <xs:annotation>
      <xs:documentation>**************************************- The action purpose is used in connection with the action code to define what the action should be. Actions can be very diverse. The purpose corresponds to the verb (Do, Create...) whereas the code is the name defining on what the action should take place. Other information may be required for the action to be completely defined. All purposes cannot be combined with all codes. All parties will not implement all combinations. Some purposes are directed more to the providers of information and some are more related to intermediate processing or to describe actions within conditional or recursive statements **************************************- List of Purposes for data management **************************************- AddTo (Booking, Basket, Product ...) Create (Customer, Booking ...) Delete (Booking, Product, Traveller ...) Get (Booking, Availability ...) Replace (Something with Something (a Segment by another, a Telephone with another)) Replace (Something with something Update (something): The difference between Replace and Update is that for Update, elements to update is not given **************************************- List of Purposes for processing management **************************************- Exclude (Cache, Source ...) Exit (to exit Statements such as if, loop, processing ...): this is used for Conditions and Actions in case complex descriptions are required. Filter (responses, hosts ...): Connections to a provider may be via several intermediate parties which could provide added values. Filtering is one of the added values, sort is another. RestrictTo (Cahce,Source ...) Sort (list ...) Stop (A statement ...): the difference between Exit and Stop is that Exit exits the statement but not the whole process, whereas Stop stops the process altogether. **************************************-</xs:documentation>
    </xs:annotation>
  </xs:attribute>
</xs:attributeGroup>