[OASIS Issue Tracker] (WSCALENDAR-532) Vavailability is not fully synchronized with Vavailability Internet Draft 05

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

     [ https://issues.oasis-open.org/browse/WSCALENDAR-532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

William Cox updated WSCALENDAR-532:
-----------------------------------

    Description: 
See sub-tasks.

Time range for Vavailability is implicitly defined in ID05 and in WS-Calendar 1.0, but must be explicit in the PIM. The constraints differ from a fully bound interval, and the semantics must be described in the PIM.

Add text describing the overview of Availability, the semantics of Time Range, and of Availability Intervals.

  was:
See sub-tasks.

Time range for Vavailability is implicitly defined in ID05, but must be explicit in the PIM. The constraints differ from a fully bound interval, and the semantics must be described in the PIM.

Add text describing the overview of Availability, the semantics of Time Range, and of Availability Intervals.


> Vavailability is not fully synchronized with Vavailability Internet Draft 05
> ----------------------------------------------------------------------------
>
>                 Key: WSCALENDAR-532
>                 URL: https://issues.oasis-open.org/browse/WSCALENDAR-532
>             Project: OASIS Web Services Calendar (WS-Calendar) TC
>          Issue Type: Bug
>          Components: PIM
>    Affects Versions: PIM WD11
>         Environment: William Cox
>            Reporter: William Cox
>            Assignee: William Cox
>             Fix For: PIM WD12
>
>
> See sub-tasks.
> Time range for Vavailability is implicitly defined in ID05 and in WS-Calendar 1.0, but must be explicit in the PIM. The constraints differ from a fully bound interval, and the semantics must be described in the PIM.
> Add text describing the overview of Availability, the semantics of Time Range, and of Availability Intervals.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)