OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

energyinterop message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


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


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

        


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]