[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (WSCALENDAR-546) Make AvailabiityType.rRule attribute optional
[ https://issues.oasis-open.org/browse/WSCALENDAR-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Cox updated WSCALENDAR-546: ----------------------------------- Resolution: Change cardinality of AvailabilityType.rRule FROM [1..1] TO [0..1]. Coordinate with other type changes under the WSCALENDAR-541 container. was: Change cardinality of AvailabilityType.rRule FROM [1..1] TO [0..1]. Coordinate with other type changes under the WSCALDAR-541 container. > Make AvailabiityType.rRule attribute optional > --------------------------------------------- > > Key: WSCALENDAR-546 > URL: https://issues.oasis-open.org/browse/WSCALENDAR-546 > Project: OASIS Web Services Calendar (WS-Calendar) TC > Issue Type: Sub-task > Components: PIM > Affects Versions: PIM CS01 > Environment: Steve Ray > https://lists.oasis-open.org/archives/ws-calendar-comment/201501/msg00001.html > Reporter: William Cox > Assignee: Michael Douglass > Fix For: PIM WD14 > > > In considering the use of the AvailabiityType instance to specify a single, non-recurring interval of availability, my understanding is that this would be specified using the AvailabilityType.availInterval attribute. In this case, I would have no need to specify any kind of recurrence using AvailabilityType.rRule. > Therefore, I am requesting the committee consider making the rRule attribute optional. > The alternative, I suppose, would be to have an empty string as the value of a mandatory rRule, but this seems less elegant. -- This message was sent by Atlassian JIRA (v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]