[OASIS Issue Tracker] (WSCALENDAR-560) Priority needed in VavailabilityType

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

     [ https://issues.oasis-open.org/browse/WSCALENDAR-560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

William Cox updated WSCALENDAR-560:
-----------------------------------

    Resolution: 
Add AvailableType.priority: PriorityType [0..1] which is constrained integer
Values constrained to 0..9 with higher numbers lower priority to match 5545 and coordinate with resolution to WSCALENDAR-561

  was:
Add AvailableType.priority: int
Values constrained to 0..9 with higher numbers lower priority to match 5545 and coordinate with resolution to WSCALENDAR-561


> Priority needed in VavailabilityType
> ------------------------------------
>
>                 Key: WSCALENDAR-560
>                 URL: https://issues.oasis-open.org/browse/WSCALENDAR-560
>             Project: OASIS Web Services Calendar (WS-Calendar) TC
>          Issue Type: Sub-task
>          Components: PIM
>    Affects Versions: PIM CS01
>         Environment: Michael Douglass discussion with William Cox
>            Reporter: William Cox
>            Assignee: Michael Douglass
>             Fix For: PIM WD14
>
>
> Discussion around dtStart being optional for AvailTimeRangeType.
> Does it matter? Create with the current time, end wherever wanted. All you need.  Vav without time ranges is that it's the background. Nominal schedule - with recurrence rules.
> Without priority doesn't make sense. What you deliver is likely very simplified and time limited.
> Priority value comes directly out of 5545.  Undefined is background. Then decreasing priority numbers,  priority: integer - if not there, undefined, lowest priority. 0 is highest, 9 is lowest.  Consider consistency - so require presence, 10 is the equivalent of not present in 5545.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)