DateDurationStartCodeType

**************************************- The event from which to count
a duration to get a date. Used in option relases, validity...
**************************************- **>AfterBooking= The date of the booking
is the starting point. This is usually used for an option or to receive a payment
**>AfterBegin = The date of the beginning of the associated entity. It could be
used to define the number of nights a room is kept in case of no show... In that
case if payment if not directly within entity, a reference can be used to clarify
the reference. **>AfterEnd= The date of the end of the associated entity. It
could be used for stops. **>AfterFirstUse= For Open products (segmentss, pass...)
validity begins after its first use (usually done within a certain date range)
**>AfterLastUse= For segments with repetitive use, actions may be possible for a
certain time afterwards (like complaints) **>AfterTrip= The date of the end of
the trip. It is often used to describe the maximum period for complaints.
**>BeforeBegin= The date of the beginning of the associated entity. It could be
the arrival date at a hotel, the beginning of the trip... This is often used for
cancellation policy. In that case if payment if not directly within entity, a
reference can be used to clarify the reference. **>BeforeTrip= The date of the
beginning of the whole trip. It is usually used to pay the full payment or for
cancellation or rebates. **************************************-

Simple Type Information

Used By

Source

<xs:simpleType name="DateDurationStartCodeType">
  <xs:annotation>
    <xs:documentation>**************************************- The event from which to count a duration to get a date. Used in option relases, validity... **************************************- **>AfterBooking= The date of the booking is the starting point. This is usually used for an option or to receive a payment **>AfterBegin = The date of the beginning of the associated entity. It could be used to define the number of nights a room is kept in case of no show... In that case if payment if not directly within entity, a reference can be used to clarify the reference. **>AfterEnd= The date of the end of the associated entity. It could be used for stops. **>AfterFirstUse= For Open products (segmentss, pass...) validity begins after its first use (usually done within a certain date range) **>AfterLastUse= For segments with repetitive use, actions may be possible for a certain time afterwards (like complaints) **>AfterTrip= The date of the end of the trip. It is often used to describe the maximum period for complaints. **>BeforeBegin= The date of the beginning of the associated entity. It could be the arrival date at a hotel, the beginning of the trip... This is often used for cancellation policy. In that case if payment if not directly within entity, a reference can be used to clarify the reference. **>BeforeTrip= The date of the beginning of the whole trip. It is usually used to pay the full payment or for cancellation or rebates. **************************************-</xs:documentation>
  </xs:annotation>
  <xs:restriction base="xs:string">
    <xs:enumeration value="AfterBooking"/>
    <xs:enumeration value="BeforeBooking"/>
    <xs:enumeration value="WhenBooking"/>
    <xs:enumeration value="AfterBegin"/>
    <xs:enumeration value="BeforeBegin"/>
    <xs:enumeration value="AfterEnd"/>
    <xs:enumeration value="BeforeEnd"/>
    <xs:enumeration value="AfterFirstUse"/>
    <xs:enumeration value="AfterLastUse"/>
    <xs:enumeration value="AfterArrival"/>
    <xs:enumeration value="AtArrival"/>
    <xs:enumeration value="BeforeArrival"/>
    <xs:enumeration value="AfterDeparture"/>
    <xs:enumeration value="AtDeparture"/>
    <xs:enumeration value="BeforeDeparture"/>
    <xs:enumeration value="AfterTrip"/>
    <xs:enumeration value="BeforeTrip"/>
    <xs:enumeration value="Now"/>
  </xs:restriction>
</xs:simpleType>