**************************************- Maintenance: DF/2003-11-13: Comment corrected DF/2003-11-13: Comment copied from ApplyCodeType and amended DF/2003-11-13: Comment copied to StatusGroup **************************************- This is used to qualify whether elements can apply in certain circumstances (Restrictions Apply, VTA apply ...) or to know how something should apply (Excursion apply but is optional, Taxes apply and are mandatory, Surcharge apply but only if a condition is true... The roles can therefore either be a Boolean (Apply/do not Apply) or qualified by one of the Apply Codes. **************************************- **> True: the element applies, without any other detail. In some cases, true and Optional could be used in the same way. If no information on how an Add-on applies (true) it should be considered as Optional. This use of true should be avoided. **> False: the element does not apply **> 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. **> Mandatory: The element must be used, but is not included in the parent element (price must be added, duration may be added ...) **> 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, Mandatory, Optional or Conditional. Can be used both in requests and responses **************************************- |
| Attribute | StatusGroup/@Apply |
<xs:simpleType name="ApplyType"> <xs:annotation> <xs:documentation>**************************************- Maintenance: DF/2003-11-13: Comment corrected DF/2003-11-13: Comment copied from ApplyCodeType and amended DF/2003-11-13: Comment copied to StatusGroup **************************************- This is used to qualify whether elements can apply in certain circumstances (Restrictions Apply, VTA apply ...) or to know how something should apply (Excursion apply but is optional, Taxes apply and are mandatory, Surcharge apply but only if a condition is true... The roles can therefore either be a Boolean (Apply/do not Apply) or qualified by one of the Apply Codes. **************************************- **> True: the element applies, without any other detail. In some cases, true and Optional could be used in the same way. If no information on how an Add-on applies (true) it should be considered as Optional. This use of true should be avoided. **> False: the element does not apply **> 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. **> Mandatory: The element must be used, but is not included in the parent element (price must be added, duration may be added ...) **> 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, Mandatory, Optional or Conditional. Can be used both in requests and responses **************************************-</xs:documentation> </xs:annotation> <xs:union memberTypes="xs:boolean ApplyCodeType"/> </xs:simpleType> |