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

William Cox edited comment on WSCALENDAR-549 at 2/28/15 10:18 PM:
------------------------------------------------------------------

This amounts to a style difference - a mandatory interval with optional start and duration, versus the proposed optional interval in the case where there is neither a specific start nor duration.

tZ seems a distraction for infinite intervals.

CS01 adheres to Internet Draft 5. Given that Commenter says this failing to alter this is an inconvenience only, rejection (no action) is the appropriate decision.


was (Author: william.cox):
This amounts to a style difference - a mandatory interval with optional start and duration, versus the proposed optional interval in the case where there is neither a specific start nor duration.

tZ seems a distraction for infinite intervals.

CS01 adheres to Internet Draft 5.

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