Make VavailabilityType.busy attribute optional.

XMLWordPrintable

    • Type: Sub-task
    • Resolution: Fixed
    • Priority: Major
    • PIM WD14
    • Affects Version/s: PIM CS01
    • Component/s: PIM
    • None
    • Environment:
    • 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.

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

            Assignee:
            Michael Douglass (Inactive)
            Reporter:
            William Cox (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: