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

XMLWordPrintable

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

      Bruce Bartell

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

      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?

            Assignee:
            William Cox (Inactive)
            Reporter:
            Bruce Bartell (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: