[OASIS Issue Tracker] Updated: (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:all-tabpanel ]

Toby Considine updated WSCALENDAR-420:
--------------------------------------

        Parent: WSCALENDAR-453
    Issue Type: Sub-task  (was: Bug)

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