OASIS Energy Interoperation TCIcon indicating the project type

OASIS Energy Interoperation TC

Uploaded image for project: 'OASIS Energy Interoperation TC'
  1. OASIS Energy Interoperation TC
  2. ENERGYINTEROP-396 Collector for Ws-Calendar or EMIX Constraints
  3. ENERGYINTEROP-368

Use EMIX:BusinessScheduleType in OptOut & OptIn Schedule creates some ambiguity

    Details

    • Type: Sub-task
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: wd22
    • Fix Version/s: wd24
    • Component/s: schema
    • Labels:
      None
    • Environment:

      Bruce Bartell

    • Proposal:
      Hide

      Create (or find? tried to but couldn't find) an element or datatype that has only start, end, duration. This is used in multiple places beside opt schedule.

      Show
      Create (or find? tried to but couldn't find) an element or datatype that has only start, end, duration. This is used in multiple places beside opt schedule.
    • Resolution:
      Hide

      EMIX:BusinessScheduleType is no longer present.

      EiOpt service has been rewritten to directly use xcal:VavailabilityType.

      Show
      EMIX:BusinessScheduleType is no longer present. EiOpt service has been rewritten to directly use xcal:VavailabilityType.

      Description

      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?

        Attachments

          Activity

          Descending order - Click to sort in ascending order
          Hide
          Permalink
          ahendry Anne Hendry (Inactive) added a comment -

          Also see http://tools.oasis-open.org/issues/browse/EMIX-389.
          (use of Schedule and BusinessSchedule in EMIX)

          Show
          ahendry Anne Hendry (Inactive) added a comment - Also see http://tools.oasis-open.org/issues/browse/EMIX-389 . (use of Schedule and BusinessSchedule in EMIX)
          Hide
          Permalink
          toby.considine Toby Considine (Inactive) added a comment -

          I agree

          http://www.oasis-open.org/apps/org/workgroup/energyinterop/email/archives/201105/msg00124.html

          Show
          toby.considine Toby Considine (Inactive) added a comment - I agree http://www.oasis-open.org/apps/org/workgroup/energyinterop/email/archives/201105/msg00124.html
          Hide
          Permalink
          gghatikar Girish Ghatikar (Inactive) added a comment -

          If Business Schedule in EMIX is exactly the wscalendar vavailability, let's use the WS-Cal Vaavailability directly. This is an ongoing issue and needs resolution at high level (of using WS-Cal directly as opposed to use through other mechanisms). We should use the elements needed directly from WS-Cal. It may also need simplification.

          Show
          gghatikar Girish Ghatikar (Inactive) added a comment - If Business Schedule in EMIX is exactly the wscalendar vavailability, let's use the WS-Cal Vaavailability directly. This is an ongoing issue and needs resolution at high level (of using WS-Cal directly as opposed to use through other mechanisms). We should use the elements needed directly from WS-Cal. It may also need simplification.
          Hide
          Permalink
          bbartell Bruce Bartell (Inactive) added a comment -

          Guidance is not an EMIX issue. This is an EI issue.
          The schedule elements should be directly from WS-Calendar, not from EMIX.

          Show
          bbartell Bruce Bartell (Inactive) added a comment - Guidance is not an EMIX issue. This is an EI issue. The schedule elements should be directly from WS-Calendar, not from EMIX.
          Hide
          Permalink
          toby.considine Toby Considine (Inactive) added a comment -

          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.

          Show
          toby.considine Toby Considine (Inactive) added a comment - 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.
          4 older comments

            People

            • Assignee:
              william.cox William Cox (Inactive)
              Reporter:
              bbartell Bruce Bartell (Inactive)
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: