[OASIS Issue Tracker] (WSCALENDAR-549) Make VavailabilityType.timeRange attribute optional

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

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

William Cox commented on WSCALENDAR-549:
----------------------------------------

Does it matter? Create with the current time, end wherever wanted. All you need.  Vav without time ranges is that it's the background. Nominal schedule - with recurrence rules.

Without priority doesn't make sense. What you deliver is likely very simplified and time limited.

Priority value comes directly out of 5545.  Undefined is background. Then decreasing priority numbers,  priority: integer - if not there, undefined, lowest priority. 0 is highest, 9 is lowest.

Try required priority 1..9 with higher numbers lower priority. Created new item, copied this comment.

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