[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=59449#comment-59449 ] 

William Cox edited comment on WSCALENDAR-554 at 4/22/15 10:04 PM:
------------------------------------------------------------------

Note that this is an argument for an enumeration with a single element, "busy" or "busyUnavailable."  Should consider for WD16.

RFC5545 says
"Description: This parameter specifies the free or busy time type.
The value FREE indicates that the time interval is free for
scheduling. The value BUSY indicates that the time interval is
busy because one or more events have been scheduled for that
interval. The value BUSY-UNAVAILABLE indicates that the time
interval is busy and that the interval can not be scheduled. The
value BUSY-TENTATIVE indicates that the time interval is busy
because one or more events have been tentatively scheduled for
that interval. If not specified on a property that allows this
parameter, the default is BUSY. Applications MUST treat x-name
and iana-token values they don’t recognize the same way as they
would the BUSY value."

It is not clear whether the apparent reason behind a time being busy is useful or appropriate at the abstraction level of a PIM; issues of who is making the assertion and the value of having the assertions in an abstract model are problematic.


was (Author: william.cox):
RFC5545 says
"Description: This parameter specifies the free or busy time type.
The value FREE indicates that the time interval is free for
scheduling. The value BUSY indicates that the time interval is
busy because one or more events have been scheduled for that
interval. The value BUSY-UNAVAILABLE indicates that the time
interval is busy and that the interval can not be scheduled. The
value BUSY-TENTATIVE indicates that the time interval is busy
because one or more events have been tentatively scheduled for
that interval. If not specified on a property that allows this
parameter, the default is BUSY. Applications MUST treat x-name
and iana-token values they don’t recognize the same way as they
would the BUSY value."

It is not clear whether the apparent reason behind a time being busy is useful or appropriate at the abstraction level of a PIM.

> 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: William Cox
>             Fix For: PIM WD15
>
>
> 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)