<xs:simpleType name="CodeRoleCodeType">
<xs:annotation>
<xs:documentation>**************************************- Maintenance: DF/2003-11-13: Comment corrected DF/2003-11-13: Comment copied to SeatGroup **************************************- Codes are widely spread in the travel industry. The xft proposes a list of standard code but does not prevent users to pass their own codes either at the same time as the xft codes for transcoding purposes, instead of the XFT codes or for information that have no direct equivalent in the XFT (typically, product codes are user specific and cannot be standardised) TO be able to automatically recognise what is the use for a given code, Roles can be used. The roles list a number of usual codes For The code roles are xft specific codes. For host/vendor/entity specific roles, use Me.Role="Specific" and the actual role in the Me.Name **>Product = the code is a product code **>Promotion = a promotion code to access a special rate **>Status = the code is a status code (not xft) This list can be amended in time.</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="Account"/>
<xs:enumeration value="Alert"/>
<xs:enumeration value="Booking"/>
<xs:enumeration value="Cancel">
<xs:annotation>
<xs:documentation xml:lang="EN">To qualify a refernce code for a cancellation reference that would be different from the standard reference. In that case both reference would be present at the same time. It can be used for bookings, documents, financial transactions ...</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Category"/>
<xs:enumeration value="Channel"/>
<xs:enumeration value="Child"/>
<xs:enumeration value="Context"/>
<xs:enumeration value="Customer"/>
<xs:enumeration value="Dictionnary"/>
<xs:enumeration value="Error"/>
<xs:enumeration value="Index">
<xs:annotation>
<xs:documentation>Index can be used to qualify a numeric value to be used in a Code item instead of in the @Index attribute ob the Code parent entity. This can be useful in case lists of codes are preferred to using semantic related attributes and elements.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Invoice"/>
<xs:enumeration value="Key"/>
<xs:enumeration value="Keyword"/>
<xs:enumeration value="Linked"/>
<xs:enumeration value="Member"/>
<xs:enumeration value="Name"/>
<xs:enumeration value="Next"/>
<xs:enumeration value="Number"/>
<xs:enumeration value="Offer"/>
<xs:enumeration value="Parent"/>
<xs:enumeration value="Password"/>
<xs:enumeration value="Policy"/>
<xs:enumeration value="Previous"/>
<xs:enumeration value="Product"/>
<xs:enumeration value="Profile"/>
<xs:enumeration value="Promotion"/>
<xs:enumeration value="Reason"/>
<xs:enumeration value="Rebate"/>
<xs:enumeration value="Relation"/>
<xs:enumeration value="Reference"/>
<xs:enumeration value="Session"/>
<xs:enumeration value="Sibling"/>
<xs:enumeration value="Sort"/>
<xs:enumeration value="Specific"/>
<xs:enumeration value="Statistics"/>
<xs:enumeration value="Status"/>
<xs:enumeration value="System"/>
<xs:enumeration value="Target"/>
<xs:enumeration value="Ticket"/>
<xs:enumeration value="Transaction"/>
<xs:enumeration value="Type"/>
<xs:enumeration value="User"/>
<xs:enumeration value="Vendor"/>
<xs:enumeration value="Version"/>
<xs:enumeration value="Warning">
<xs:annotation>
<xs:appinfo>DF+2011-04-03+Create</xs:appinfo>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType> |