[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: 
AvailabilityIntervals paint the available times within the AvailTimeRangeType (interval).  For some purposes the semantic distinction between "busy", "busyUnavailable" (== really not available), and "busyTentative" may not be required.  

Propose changing cardinality of busy to [0..1]  where the absence of an attribute value is treated as if "busy" were the explicit value.

Note that Vavailability does not seem the appropriate mechanism for the commenter's purpose. However, the increased clarity around AvailBusyType simplification (beyond simply using "busy" when the other semantics are not needed) seems useful.


  was:
AvailabilityIntervals paint the available times within the AvailTimeRangeType (interval).  For some purposes the semantic distinction between "busy", "busyUnavailable" (== really not available), and "busyTentative" may not be required.  

Propose changing cardinality of busy to [0..1]  where the absence of an attribute value is defined as "busy".


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