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-554

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

    XMLWordPrintable

    Details

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

      William Cox

    • Proposal:
      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).
    • Resolution:
      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.

      Description

      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.

        Attachments

          Activity

            People

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

              Dates

              • Created:
                Updated:
                Resolved: