• Type: Improvement
    • Resolution: Applied
    • Priority: Major
    • wd21
    • Affects Version/s: pr02, CS01
    • Component/s: schema, spec
    • None
    • Environment:

      Toby Considine

      Granularity is a duration that offers some powerful features. Sometimes it means different things. It is not hard to imagine a WS-Calendar artifact that uses Granularity twice.

      A) Granularity of Scheduling.. With a granularity of one hour, intervals can only be scheduled one hour apart. But from what?

      Base case1: Granularity PT15M, Intervals can be scheduled at 8:00, 8:15, 8:30, 8:45.
      Base case2: Granularity PT1H, Intervals can be scheduled at 8:00, 9:00, 10:00, 11:00...
      Base case3: Granularity PT1H, Intervals can be scheduled at 8:30, 9:30, 10:30, 11:30...

      How do we distringuish between case 2 and case 3?

      B) Granularity of Duration.

      Base case1: Granularity PT15M, Intervals can be PT15M, PT30M, PT45M,... Is there a mamximum length?

      C) How do we distinguish between (A) and (B). Granularity is a propoerty. Properties can be applied to different components. Does the component determine the ontology? WHat are the rules?

      D) WHat section of the specification should this be added to?

            Assignee:
            Toby Considine (Inactive)
            Reporter:
            Toby Considine (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: