Clarify VavailabilityType default "busy-unavailable" and semantics for other values

XMLWordPrintable

    • Type: Sub-task
    • Resolution: Fixed
    • Priority: Major
    • PIM WD15
    • Affects Version/s: PIM CS01
    • Component/s: PIM
    • None
    • Environment:

      William Cox

    • Hide

      PIM:AvailBusyType enumeration should contain

      busy
      busyUnavailable
      busyTentative
      x-name
      iana-token

      (see 5545 3.2.9 and CA ID05 3.1)

      State in specification

      (1) Label all time periods in AvailTimeRangeType (name is subject to another item) with the value of busyType in the VavailabilityType object.

      (2) If the busyType attribute is missing, use busyUnavailable.

      (3) State that any time period indicated in an AvailableType SHALL be considered available. (bottom of IDraft p5).

      Show
      PIM:AvailBusyType enumeration should contain busy busyUnavailable busyTentative x-name iana-token (see 5545 3.2.9 and CA ID05 3.1) State in specification (1) Label all time periods in AvailTimeRangeType (name is subject to another item) with the value of busyType in the VavailabilityType object. (2) If the busyType attribute is missing, use busyUnavailable. (3) State that any time period indicated in an AvailableType SHALL be considered available. (bottom of IDraft p5).
    • Hide

      PIM:AvailabilityBusyType enumeration should contain

      busy
      busyUnavailable
      busyTentative

      State in specification

      (1) Label all time periods in AvailTimeRangeType (name is subject to another item) with the value of busyType in the VavailabilityType object.

      (2) If the busyType attribute is missing, use busyUnavailable.

      (3) State that any time period indicated in an AvailableType SHALL be considered available. (bottom of IDraft p5).

      (4) Indicate that in the PIM all types of busy are treated the same.

      Show
      PIM:AvailabilityBusyType enumeration should contain busy busyUnavailable busyTentative State in specification (1) Label all time periods in AvailTimeRangeType (name is subject to another item) with the value of busyType in the VavailabilityType object. (2) If the busyType attribute is missing, use busyUnavailable. (3) State that any time period indicated in an AvailableType SHALL be considered available. (bottom of IDraft p5). (4) Indicate that in the PIM all types of busy are treated the same.

      The text in Internet Draft 05 Calendar Availability seems ambiguous in part.

      First, the VavailabiityType object indicates a bound interval in which everything "defaults to" "busy-unavailable" whether or not busytype is present.

      Then busyness is not indicated "...for any time periods corresponding to "AVAILABLE" subcomponents."

      What is busyType used for then, if the Vavailability "defaults" to busy-unavailable? There's no clear semantics of any other busyType value.

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

              Created:
              Updated:
              Resolved: