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:

      William Cox (based on re-examining implications of Steve Ray comments)

    • Resolution:
      Hide

      LEAVE VavailabilityType AS VavailabilityType
      CHANGE AvailabilityType TO AvailableType

      to reflect the container and contained in Calendar-Availability.

      Also
      CHANGE AvailIntervalType TO AvailableIntervalType to maintain consistentcy with AvailableType.

      Show
      LEAVE VavailabilityType AS VavailabilityType CHANGE AvailabilityType TO AvailableType to reflect the container and contained in Calendar-Availability. Also CHANGE AvailIntervalType TO AvailableIntervalType to maintain consistentcy with AvailableType.

      Description

      Coordinate container class names VavailabilityType and AvailabilityType with those in Calendar Availability Internet Draft 05.

      The containing interval is described in PIM by timeRange: AvailTimeRangeType which is fully bound. This timeRange is "busy-unavailable" for the specific interaction/parties of interest. (see p5) except for "except for any time periods corresponding to "AVAILABLE" sub-components." So the VavailabilityType in PIM CS01 corresponds to the VAVAILABILITY Component.

      The AVAILABLE sub-components indicate periods of free times within the enclosing VAVAILABILITY...and may contain recurrence properties...

        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: