StatusGroup 

The Status is represented by a code. The associated Quantity
corresponds to the number of available items. 0 = item not available. The way to
process a booking in that case would depend on the status (Request / Waitlist /
Closed)

Attribute Group Information

Attributes

QName Type Fixed Default Use Inheritable Annotation
Apply ApplyType optional 
**************************************- 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 ...) **> 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 **************************************-
 
**************************************- Maintenance:
DF/2003-11-13: Comment copied from type definition
**************************************-
As AsCodeType optional 
This attribute is used to express the fact that the
associated element is either en envelope or an item. If omitted, the element is
considered an item (default behaviour). *An item contains the information
directly in itself. *An envelope would group items of the same nature, but the
informaton would in fact be in the child items.
Debug xs:string optional 
This attribute is used to hold any information that would be relevant for debug purposes
It should not be present in regular exchanges, except when debug flags are positioned.
Guaranteed GuaranteedCodeType optional 
§Description: This attribute can be used to define that the corresponding parent element is Guaranteed. It may hold three values:
* true (xs:boolean)
* false (xs:boolean)
* Unknown (xft:UnknownCodeType, therefore the uppercase)

§Usage: Up to now, the usage correpsonds to  th epossibility to express taht a given departure is guaranteed for a given date.
If Guaranteed is false, it may be associated to a guarantee rule that explains how the guarantee may be optianed (like a minimum number of persons.
A guaranteed that is not provided does not correspond to a false value, but to an Unknown value.
Override OverrideType optional
Status StatusCodeType optional 
**>A = Available **>C = Confirm / Confirmed **>N = Not
applicable / no action **> O = Option **> R = Request **> U = Unable to
confirm **> W = Waitlist **> X = Closed If there is a quantity, Status can
be omitted. If Quantity is positive Status = A If Quantity is negative or null
Status = X

Used By

Complex Type AtomType

Source 

<xs:attributeGroup name="StatusGroup">
  <xs:annotation>
    <xs:documentation>The Status is represented by a code. The associated Quantity corresponds to the number of available items. 0 = item not available. The way to process a booking in that case would depend on the status (Request / Waitlist / Closed)</xs:documentation>
  </xs:annotation>
  <xs:attribute name="Status" type="StatusCodeType" use="optional">
    <xs:annotation>
      <xs:documentation>**>A = Available **>C = Confirm / Confirmed **>N = Not applicable / no action **> O = Option **> R = Request **> U = Unable to confirm **> W = Waitlist **> X = Closed If there is a quantity, Status can be omitted. If Quantity is positive Status = A If Quantity is negative or null Status = X</xs:documentation>
    </xs:annotation>
  </xs:attribute>
  <xs:attribute name="Apply" type="ApplyType" use="optional">
    <xs:annotation>
      <xs:documentation>**************************************- 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 ...) **> 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:documentation>**************************************- Maintenance: DF/2003-11-13: Comment copied from type definition **************************************-</xs:documentation>
    </xs:annotation>
  </xs:attribute>
  <xs:attribute name="Override" type="OverrideType" use="optional"/>
  <xs:attribute name="As" type="AsCodeType" use="optional">
    <xs:annotation>
      <xs:documentation xml:lang="EN">This attribute is used to express the fact that the associated element is either en envelope or an item. If omitted, the element is considered an item (default behaviour). *An item contains the information directly in itself. *An envelope would group items of the same nature, but the informaton would in fact be in the child items.</xs:documentation>
    </xs:annotation>
  </xs:attribute>
  <xs:attribute name="Guaranteed" type="GuaranteedCodeType" use="optional">
    <xs:annotation>
      <xs:documentation xml:lang="EN">§Description: This attribute can be used to define that the corresponding parent element is Guaranteed. It may hold three values: * true (xs:boolean) * false (xs:boolean) * Unknown (xft:UnknownCodeType, therefore the uppercase) §Usage: Up to now, the usage correpsonds to th epossibility to express taht a given departure is guaranteed for a given date. If Guaranteed is false, it may be associated to a guarantee rule that explains how the guarantee may be optianed (like a minimum number of persons. A guaranteed that is not provided does not correspond to a false value, but to an Unknown value.</xs:documentation>
      <xs:appinfo>DF+2011-09-20+Create: For Nouvelles Frontieres</xs:appinfo>
    </xs:annotation>
  </xs:attribute>
  <xs:attribute name="Debug" type="xs:string" use="optional">
    <xs:annotation>
      <xs:documentation xml:lang="EN">This attribute is used to hold any information that would be relevant for debug purposes It should not be present in regular exchanges, except when debug flags are positioned.</xs:documentation>
      <xs:appinfo>§Action+DF+2011-10-12+Add: Afidium requested that to differnetiate debug data from regular data</xs:appinfo>
    </xs:annotation>
  </xs:attribute>
</xs:attributeGroup>