[OASIS Issue Tracker] (WSCALENDAR-548) Make VavailabilityType.busy attribute optional.

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

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

William Cox updated WSCALENDAR-548:
-----------------------------------

    Proposal: 



  was:
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 of busytype is treated as if "busy-unavailable" were the explicit value.



> Make VavailabilityType.busy attribute optional.
> -----------------------------------------------
>
>                 Key: WSCALENDAR-548
>                 URL: https://issues.oasis-open.org/browse/WSCALENDAR-548
>             Project: OASIS Web Services Calendar (WS-Calendar) TC
>          Issue Type: Sub-task
>          Components: PIM
>    Affects Versions: PIM CS01
>         Environment: Steve Ray comment 20150227
> https://lists.oasis-open.org/archives/ws-calendar-comment/201501/msg00004.html
> Issue 2 of 3. Split for separate discussion. See also WSCALEANDAR-547
>            Reporter: William Cox
>            Assignee: Michael Douglass
>             Fix For: PIM WD14
>
>
> 2. VavailabilityType.busy – we don’t have a defined need to use “busy”, “busyUnavailable” and “busyTentative”, so would rather have this attribute as optional. 



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