[OASIS Issue Tracker] (WSCALENDAR-554) Clarify VavailabilityType default "busy-unavailable" and semantics for other values

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

    [ https://issues.oasis-open.org/browse/WSCALENDAR-554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59217#comment-59217 ] 

William Cox commented on WSCALENDAR-554:
----------------------------------------

On further thought, I don't see why the PIM should distinguish. A PSM MAY further distinguish busyTypes in the AvailabilityBusyType enumeration.

Proposed wording:

busy defaults to "busy" (the wording gets convoluted - the attribute is busy, probably should become availabilityBusy).

Other values of the attribute are not defined in the PIM - so PSMs can if they wish define an extension to busyUnavailable and busyTentative.

Thoughts?

> Clarify VavailabilityType default "busy-unavailable" and semantics for other values
> -----------------------------------------------------------------------------------
>
>                 Key: WSCALENDAR-554
>                 URL: https://issues.oasis-open.org/browse/WSCALENDAR-554
>             Project: OASIS Web Services Calendar (WS-Calendar) TC
>          Issue Type: Sub-task
>          Components: PIM
>    Affects Versions: PIM CS01
>         Environment: William Cox
>            Reporter: William Cox
>            Assignee: Michael Douglass
>
> 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.



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