[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (ENERGYINTEROP-368) UseEMIX:BusinessScheduleType in OptOut & OptIn Schedule creates some ambiguity
[ http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25225#action_25225 ]
Toby Considine commented on ENERGYINTEROP-368:
----------------------------------------------
Business Schedule in EMIX is exactly the wscalendar vavailability
<xs:element name="businessSchedule" type="emix:BusinessScheduleType"/>
<xs:complexType name="BusinessScheduleType" mixed="false">
<xs:annotation>
<xs:documentation>iCalendar-derived business schedule, more variant than allowed in sequences</xs:documentation>
</xs:annotation>
<xs:complexContent mixed="false">
<xs:extension base="xcal:VavailabilityType"/>
</xs:complexContent>
</xs:complexType>
Duration is, howver, the next element named.
There as been a recurring issue of those who want one-time wrapping of ws-calendar into EMIX, and those who want native ws-calendar types. I have waffled myself. Guidance and comments to possible EMIX PR are apropriate.
> Use EMIX:BusinessScheduleType in OptOut & OptIn Schedule creates some ambiguity
> -------------------------------------------------------------------------------
>
> 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
> Environment: Bruce Bartell
> 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]