[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (WSCALENDAR-549) Make VavailabilityType.timeRange attribute optional
[ https://issues.oasis-open.org/browse/WSCALENDAR-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58769#comment-58769 ] William Cox commented on WSCALENDAR-549: ---------------------------------------- Later update to busy behavior (absence is treated as busyUnavailable) opens the door to reconsideration of this item. Discuss at an upcoming TC meeting. > Make VavailabilityType.timeRange attribute optional > --------------------------------------------------- > > Key: WSCALENDAR-549 > URL: https://issues.oasis-open.org/browse/WSCALENDAR-549 > 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 > Reporter: William Cox > Assignee: Michael Douglass > > Issue 3 of 3. Split for separate discussion. See WSCALENDAR-547 for full issue and references. > 3. VavailabilityType.timeRange – we would like this attribute to be optional since we are talking in general about an abstract billing interval. We don’t want to bound it to a finite time range. -- 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]