[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (WSCALENDAR-554) Clarify VavailabilityType default "busy-unavailable" and semantics for other values
William Cox created WSCALENDAR-554: -------------------------------------- Summary: 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 Environment: William Cox Reporter: William Cox Assignee: Toby Considine 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)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]