[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (WSCALENDAR-543) Replace external reference to xcal:rrule in AvailabilityType
[ https://issues.oasis-open.org/browse/WSCALENDAR-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
William Cox updated WSCALENDAR-543:
-----------------------------------
Assignee: Michael Douglass (was: William Cox)
Environment:
William Cox
Steve Ray
https://lists.oasis-open.org/archives/ws-calendar-comment/201501/msg00001.html
was:William Cox
Description:
AvailabilityType has rRule: xcal:Rrule as an attribute.
An external-to-the-PIM reference (even if it were correct) is not useful in a Platform-Independent Model. The data value should be changed to a conformed string with the string definition as in RFC 5545.
Steve Ray: from emal
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.
was:
AvailabilityType has rRule: xcal:Rrule as an attribute.
An external-to-the-PIM reference (even if it were correct) is not useful in a Platform-Independent Model. The data value should be changed to a conformed string with the string definition as in RFC 5545.
Resolution:
Change AvailabilityType::rRule from "xcal:rrule" to pim:RRuleType which contains an attribute of type "String" with conformance rules taken from RFC 5545.
Change cardinality of rRule to [0..1].
RFC5545 3.3.10 on Recurrence Rule says that FREQ part is REQUIRED.So if an rrule is included at all, it must have FREQ (in the constraintedstring), but if there is no rrule, cardinality [0..1] for pim:RRuleType seems correct. The multiplicity is inside the specific rrule conformed string.
I don't see a reason to delve further into PIMming the rrules.
Verify with Mike.
> Replace external reference to xcal:rrule in AvailabilityType
> ------------------------------------------------------------
>
> Key: WSCALENDAR-543
> URL: https://issues.oasis-open.org/browse/WSCALENDAR-543
> Project: OASIS Web Services Calendar (WS-Calendar) TC
> Issue Type: Sub-task
> Components: PIM
> Affects Versions: PIM CS01
> Environment: William Cox
> Steve Ray
> https://lists.oasis-open.org/archives/ws-calendar-comment/201501/msg00001.html
> Reporter: William Cox
> Assignee: Michael Douglass
>
> AvailabilityType has rRule: xcal:Rrule as an attribute.
> An external-to-the-PIM reference (even if it were correct) is not useful in a Platform-Independent Model. The data value should be changed to a conformed string with the string definition as in RFC 5545.
> Steve Ray: from emal
> 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]