<xs:simpleType name="ApplyCodeType">
<xs:annotation>
<xs:documentation>Usage: Can be used both in requests and responses. In request, this would be used to filter or specify information (like filter optional data). In responses, this would correspond to information on whether data is applicable and under which conditions (complement in rules in certain cases), whether data is included in price or not ... Description:Advisable:The element is not mandatory but it is advised to include it (like in case of access to a lodging by Car, excursion is not mandatory but it would be a pity not to take it 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 ...) Free : No additional price is induced by the element, but other elements, such as the duration may need to be added. Gift: Same as free + notion of actual gift Included: parent element is present without extra price: price is included in quotaiton. IN case of multiple quotation, reference would be required. Mandatory:The element must be used, but is not included in the parent element (price must be added, duration may be added ...) NonIncluded: Parent element apply, but price is not included in quotation. Price information may be present in the parent element. NotApplicable: self explanatory 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, Refused:Parent element was explicitly refused by either requester or host Requested: Parent element was explicitly requested by requester or host Valid:Parent element can be used (like a payment transaction, a combination of rooms, an air segment ... Possible amendements : There is a need to qualify the use: once, several times, within a list... For instance can select 2 add-ons within a list of 4. Must investigate if rules would not work.</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="Advisable"/>
<xs:enumeration value="Applicable"/>
<xs:enumeration value="Automatic">
<xs:annotation>
<xs:appinfo>§DF+2012-11-30+Add:for PV</xs:appinfo>
<xs:documentation xml:lang="EN">To express the fact that the associated parent is automatically applied (like a rule, a promotion)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="BlackListed"/>
<xs:enumeration value="Blocked"/>
<xs:enumeration value="Conditional"/>
<xs:enumeration value="Exonerated"/>
<xs:enumeration value="Free"/>
<xs:enumeration value="Gift"/>
<xs:enumeration value="Included"/>
<xs:enumeration value="Invalid"/>
<xs:enumeration value="Mandatory"/>
<xs:enumeration value="NonIncluded"/>
<xs:enumeration value="NotApplicable"/>
<xs:enumeration value="NotFound"/>
<xs:enumeration value="Optional"/>
<xs:enumeration value="Refused"/>
<xs:enumeration value="Requested"/>
<xs:enumeration value="Test">
<xs:annotation>
<xs:appinfo>DF+2010-02-22+Added: to pass the information that the parent element is present as test, even though possibly in a production transaction, for instance to test in real life environment with test products.</xs:appinfo>
<xs:documentation xml:lang="EN">To express the fact that the parent element is test data to be used for instance in a production environment (test property, test product, test card, test person...)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Undeliverable">
<xs:annotation>
<xs:appinfo>DF+2008-11-06+Added: To allow to mark an email for instance as undeliverable.</xs:appinfo>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Unknown"/>
<xs:enumeration value="Valid"/>
</xs:restriction>
</xs:simpleType> |