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

William Cox updated WSCALENDAR-549:
-----------------------------------

    Description: 
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. 

  was:Issue 3 of 3. Split for separate discussion. See WSCALEANDAR-547 for full issue and references.

       Proposal: 
AvailabilityIntervals paint the available times within the AvailTimeRangeType (interval). The timeRange attribute of the VavailabilityType describes the specific range of discussion. The CS01 semantics for AvailTimeRangeType address this use case, at the possible expense of an empty object.  But a schedule of availability for all time seems an edge use case as well.

Moreover, Vavailability does not seem the appropriate mechanism for this kind of schedule.

Reject: No change.

  was:
AvailabilityIntervals paint the available times within the AvailTimeRangeType (interval). The time being discussed IS defined in the timeRange attribute of the VavailabilityType.

Without timeRange the Vavailability would amount to a "for all time" ; combined with WSCALENDAR -547 makes the expressions at best indeterminate and at worst hard to understand. 

Commenter says that this is an inconvenience (minor) - and since Vavailability does not seem the appropriate mechanism recommend reject.

Recommend reject.


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)