Uploaded image for project: 'OASIS Web Services Calendar (WS-Calendar) TC'
  1. OASIS Web Services Calendar (WS-Calendar) TC
  2. WSCALENDAR-541 Vavailability types need to be fully sychronized with Internet Draft 05
  3. WSCALENDAR-548

Make VavailabilityType.busy attribute optional.

    XMLWordPrintable

    Details

    • Type: Sub-task
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: PIM CS01
    • Fix Version/s: PIM WD14
    • Component/s: PIM
    • Labels:
      None
    • Environment:
    • Proposal:
    • Resolution:
      Hide

      AvailabilityIntervals paint the available times within an otherwise BUSY AvailTimeRangeType (interval). See WSCALENDAR-541 comments.

      For some purposes the semantic distinction between "busy", "busyUnavailable" (== really not available), and "busyTentative" may not be required.

      busytype is optional with no more than one occurrence; the absence busytype is treated as if "busy-unavailable" were the explicit value.

      Show
      AvailabilityIntervals paint the available times within an otherwise BUSY AvailTimeRangeType (interval). See WSCALENDAR-541 comments. For some purposes the semantic distinction between "busy", "busyUnavailable" (== really not available), and "busyTentative" may not be required. busytype is optional with no more than one occurrence; the absence busytype is treated as if "busy-unavailable" were the explicit value.

      Description

      2. VavailabilityType.busy – we don’t have a defined need to use “busy”, “busyUnavailable” and “busyTentative”, so would rather have this attribute as optional.

        Attachments

          Activity

            People

            • Assignee:
              douglm Michael Douglass (Inactive)
              Reporter:
              william.cox William Cox (Inactive)
            • Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: