ActionCodeType

<xs:simpleType name="ActionCodeType">
  <xs:annotation>
    <xs:documentation>**************************************- Maintenance: DF/2003-11-13: Comment corrected DF/2003-11-13: Comment copied to Action attribute DF/2004-05-25: Option added to have a more direct access to confirm or delete options. **************************************- 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) Option: to delete or confirm options without using the Option tag from the segments. May require a reference though 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:restriction base="xs:string">
    <xs:enumeration value="Accomodation"/>
    <xs:enumeration value="AddOn"/>
    <xs:enumeration value="Agency"/>
    <xs:enumeration value="Airport"/>
    <xs:enumeration value="Alternate"/>
    <xs:enumeration value="Availability"/>
    <xs:enumeration value="Application"/>
    <xs:enumeration value="Booking"/>
    <xs:enumeration value="Brochure"/>
    <xs:enumeration value="Cache"/>
    <xs:enumeration value="Code"/>
    <xs:enumeration value="Company"/>
    <xs:enumeration value="Contract"/>
    <xs:enumeration value="Customer"/>
    <xs:enumeration value="CustomField"/>
    <xs:enumeration value="Description"/>
    <xs:enumeration value="Dictionnary"/>
    <xs:enumeration value="Document"/>
    <xs:enumeration value="Duplicates"/>
    <xs:enumeration value="Entity"/>
    <xs:enumeration value="Error"/>
    <xs:enumeration value="Fare">
      <xs:annotation>
        <xs:documentation xml:lang="EN">A complete fare grid by opposition to a precise price or tariff (which would be price in that case). this corresponds usualy to a fare grid displayed in catalogues or a negotiated contract</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="Fee"/>
    <xs:enumeration value="File"/>
    <xs:enumeration value="Flight"/>
    <xs:enumeration value="Help"/>
    <xs:enumeration value="History"/>
    <xs:enumeration value="Information"/>
    <xs:enumeration value="Inventory"/>
    <xs:enumeration value="Invoice"/>
    <xs:enumeration value="Issue"/>
    <xs:enumeration value="List"/>
    <xs:enumeration value="Location"/>
    <xs:enumeration value="Log"/>
    <xs:enumeration value="Newsletter"/>
    <xs:enumeration value="News"/>
    <xs:enumeration value="Notification">
      <xs:annotation>
        <xs:documentation xml:lang="EN">This code can be used to signal that an asynchroneous process has been completed (with @Purpose=Send)</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="Option"/>
    <xs:enumeration value="OSI"/>
    <xs:enumeration value="Password"/>
    <xs:enumeration value="Payment"/>
    <xs:enumeration value="Permission"/>
    <xs:enumeration value="Person"/>
    <xs:enumeration value="Policy"/>
    <xs:enumeration value="Preference"/>
    <xs:enumeration value="Price"/>
    <xs:enumeration value="Product"/>
    <xs:enumeration value="Profile"/>
    <xs:enumeration value="Quote"/>
    <xs:enumeration value="QuotedAvailability"/>
    <xs:enumeration value="Rank"/>
    <xs:enumeration value="Receipt"/>
    <xs:enumeration value="Request"/>
    <xs:enumeration value="Requester"/>
    <xs:enumeration value="Rule"/>
    <xs:enumeration value="Seat">
      <xs:annotation>
        <xs:appinfo>§Hist+DF+2012-03-12+add: to manage air seats.</xs:appinfo>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="Segment"/>
    <xs:enumeration value="Source"/>
    <xs:enumeration value="Session"/>
    <xs:enumeration value="SSR"/>
    <xs:enumeration value="Statistics"/>
    <xs:enumeration value="Status"/>
    <xs:enumeration value="Stock"/>
    <xs:enumeration value="System"/>
    <xs:enumeration value="Task"/>
    <xs:enumeration value="Tax"/>
    <xs:enumeration value="Ticket"/>
    <xs:enumeration value="Till"/>
    <xs:enumeration value="Time"/>
    <xs:enumeration value="Travel"/>
    <xs:enumeration value="Traveller"/>
    <xs:enumeration value="Trip"/>
    <xs:enumeration value="Update"/>
    <xs:enumeration value="URL"/>
    <xs:enumeration value="User"/>
    <xs:enumeration value="Vendor"/>
    <xs:enumeration value="Voucher"/>
  </xs:restriction>
</xs:simpleType>