[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Created: (WSCALENDAR-223) All uses ofgranularity are not clear
All uses of granularity are not clear ------------------------------------- Key: WSCALENDAR-223 URL: http://tools.oasis-open.org/issues/browse/WSCALENDAR-223 Project: OASIS Web Services Calendar (WS-Calendar) TC Issue Type: Improvement Affects Versions: pr02 Environment: Toby Considine Reporter: Toby Considine Assignee: 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 1 and case 2? 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? -- 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]