[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:all-tabpanel ]

William Cox updated WSCALENDAR-554:
-----------------------------------

    Proposal: 
PIM:AvailBusyType enumeration should contain

busy
busyUnavailable
busyTentative
x-name
iana-token

(see 5545 3.2.9 and CA ID05 3.1)

State in specification

(1) Label all time periods in AvailTimeRangeType (name is subject to another item) with the value of busyType in the VavailabilityType object.

(2) If the busyType attribute is missing, use busyUnavailable.

(3) State that any time period indicated in an AvailableType SHALL be considered available. (bottom of IDraft p5). 

  was:
PIM:AvailBusyType enumeration should contain

busy
busyUnavailable
busyTentative
x-name
iana-token

(see 5545 3.2.9 and CA ID05 3.1)

State in specification

(1) Label all time periods in AvailTimeRangeType (name is subject to another item) with the value of busyType in the VavailabilityType object.

(2) Clarify that any time period indicated in an AvailableType SHALL be considered available. (bottom of ID p5). 


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