<xs:simpleType name="ActionPurposeCodeType">
<xs:annotation>
<xs:documentation>**************************************- Maintenance: DF/2003-11-13: Comment corrected DF/2003-11-13: Comment copied to Action attribute DF/2004-02-12: Send added to be used in TransactionDataHandOff for unsollited transactions DF/2004-05-25: Confirm added to be used for bookings and options, changes, updates... **************************************- 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 ...) Confirm (Booking, Option ...) 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 Send (Something such as Booking data, passenger...) 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 (Cache,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:restriction base="xs:string">
<xs:enumeration value="Add"/>
<xs:enumeration value="Apply"/>
<xs:enumeration value="Associate"/>
<xs:enumeration value="Authenticate"/>
<xs:enumeration value="Balance"/>
<xs:enumeration value="Calculate"/>
<xs:enumeration value="Cancel"/>
<xs:enumeration value="Check"/>
<xs:enumeration value="Close"/>
<xs:enumeration value="Connect"/>
<xs:enumeration value="Confirm"/>
<xs:enumeration value="ConfirmTo"/>
<xs:enumeration value="Count"/>
<xs:enumeration value="Create"/>
<xs:enumeration value="Decode"/>
<xs:enumeration value="Delete"/>
<xs:enumeration value="Dematerialise"/>
<xs:enumeration value="Disconnect"/>
<xs:enumeration value="Dissociate"/>
<xs:enumeration value="Do"/>
<xs:enumeration value="Encode"/>
<xs:enumeration value="Exclude"/>
<xs:enumeration value="Execute"/>
<xs:enumeration value="Exit"/>
<xs:enumeration value="Extend"/>
<xs:enumeration value="Filter"/>
<xs:enumeration value="Format">
<xs:annotation>
<xs:documentation xml:lang="EN">Format a document for instance</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Get"/>
<xs:enumeration value="Ignore"/>
<xs:enumeration value="Issue"/>
<xs:enumeration value="List"/>
<xs:enumeration value="Load"/>
<xs:enumeration value="Manage"/>
<xs:enumeration value="Open"/>
<xs:enumeration value="Override"/>
<xs:enumeration value="Poll"/>
<xs:enumeration value="Prepare">
<xs:annotation>
<xs:documentation xml:lang="EN">Known Usage: * Prepare Document: before a document is issued and during the creation phase, it is sometimes necessary to format a number of values (like dates, amounts, add labels and texts). A part of the preparation could be a transcoding of the codes.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Print"/>
<xs:enumeration value="Process"/>
<xs:enumeration value="Propose"/>
<xs:enumeration value="Purchase"/>
<xs:enumeration value="Receive"/>
<xs:enumeration value="Refund"/>
<xs:enumeration value="Refuse"/>
<xs:enumeration value="Release"/>
<xs:enumeration value="Replace"/>
<xs:enumeration value="Require"/>
<xs:enumeration value="Restore"/>
<xs:enumeration value="RestrictTo"/>
<xs:enumeration value="Search"/>
<xs:enumeration value="Sell"/>
<xs:enumeration value="Send"/>
<xs:enumeration value="Simulate">
<xs:annotation>
<xs:appinfo>§Hist+DF+2012-03-12+add: to allow simulating an action without actually doing the action (created for PV).</xs:appinfo>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Sort"/>
<xs:enumeration value="Split"/>
<xs:enumeration value="Stop"/>
<xs:enumeration value="Synchronize"/>
<xs:enumeration value="Transcode"/>
<xs:enumeration value="Update"/>
<xs:enumeration value="Use"/>
<xs:enumeration value="Validate"/>
</xs:restriction>
</xs:simpleType> |