[OASIS Issue Tracker] Commented: (WSCALENDAR-420) Line 2678 -"Intervals SHALL NOT include an END time."

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

    [ http://tools.oasis-open.org/issues/browse/WSCALENDAR-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=27050#action_27050 ] 

Bruce Bartell commented on WSCALENDAR-420:
------------------------------------------

from Committee Specification Draft 04 /
Public Review Draft 03:

4.2.5 Conformance of Intervals 

4.2.5.1 Intervals 

WS-Calendar Intervals SHALL have a Duration. 

Intervals MAY have a Start Time. 

Intervals SHALL have a Duration AND a dtStart OR a dtEnd. If a non-compliant Interval is received with both a dtStart and a dtEnd, then the dtEnd SHALL be ignored. Within a Sequence, a maximum of a single Interval MAY have a dtStart or a dtEnd.



> Line 2678 - "Intervals SHALL NOT include an END time."
> ------------------------------------------------------
>
>                 Key: WSCALENDAR-420
>                 URL: http://tools.oasis-open.org/issues/browse/WSCALENDAR-420
>             Project: OASIS Web Services Calendar (WS-Calendar) TC
>          Issue Type: Sub-task
>          Components: spec
>    Affects Versions: pr02
>         Environment: Marty Burns
>            Reporter: Toby Considine
>            Assignee: Toby Considine
>             Fix For: wd20
>
>
> Exclusion of dtEnd in 5.2.3.1 Why is this requirement of Interval and not of Gluon? CIM currently has only start and end. Enabling consistency with this body of work is simplified if two out of three start, end, duration are supported. Suggest using rule in 5.2.3.2 and state that dtStart, duration are preferred.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira