[OASIS Issue Tracker] Commented: (ENERGYINTEROP-368) UseEMIX:BusinessScheduleType in OptOut & OptIn Schedule creates some amiguity

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

    [ http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24998#action_24998 ] 

Bruce Bartell commented on ENERGYINTEROP-368:
---------------------------------------------

The main point in the Proposed resolution is to find or create the closest element/datatype defined in ws-calendar and use it directly.

> Use EMIX:BusinessScheduleType in OptOut & OptIn Schedule creates some amiguity
> ------------------------------------------------------------------------------
>
>                 Key: ENERGYINTEROP-368
>                 URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-368
>             Project: OASIS Energy Interoperation TC
>          Issue Type: Bug
>          Components: schema
>    Affects Versions: wd22
>            Reporter: Bruce Bartell
>            Assignee: William Cox
>
> Re: Use of  EMIX:BusinessScheduleType
> This type contains xcal:properties (contains dtStart, dtEnd, duration; each optional - needs rule on which to use end or duration
> xcal:components - BaseComponentType also has start,end,duration. Why do we need both properties and components to convey a schedule? Which one is the actual schedule?
> wsCal Extensions:interval contains start,end,duration and a bunch of other stuff we don't need. Why can't we just use the element that contains only what  we need?

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