[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (WSCALENDAR-545) Consider Vavailability attributes for AvailabilityType
[ https://issues.oasis-open.org/browse/WSCALENDAR-545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
William Cox updated WSCALENDAR-545:
-----------------------------------
Fix Version/s: PIM WD14
Environment:
Steve Ray WS-Calendar-Comment 20150120
https://lists.oasis-open.org/archives/ws-calendar-comment/201501/msg00000.html
was:Wiilliam Cox
Description:
The ASHRAE SPC201 committee would like to make use of the exDate attribute within the Availability class of the WS-Calendar PIM. This is used to exclude specific dates that would otherwise be included within a recurrence rule. The exDate attribute is part of RFC5545, and since our committee is striving to remain compatible with other standards, including WS-Calendar, we would respectfully request that the exDate attribute be added.
Extended WTC:
Consider (e.g. from Page 5) the following:
exdate
uid (for parallel with IntervalType, if PIM needs this)
comment (for parallel with IntervalType)
Note that dtstart, duration, and tz are already present.
was:
Re-analyze Vavailability Internet Draft 5 for important attributes for the PIM.
Consider (e.g. from Page 5) the following:
exdate
uid (for parallel with IntervalType, if PIM needs this)
comment (for parallel with IntervalType)
Note that dtstart, duration, and tz are already present.
Proposal:
Add attributes exdate and comment to AvailabilityType.
Create pim:ExdateType which has a single attribute of type "String" which takes conformance from the exdate availableProp description in Vavailability/RFC5545.
Coordinate with resolution to WSCALENDAR-543
was:
Add attributes exdate and comment to AvailabilityType.
Create pim:ExdateType which has a single attribute of type "String" which takes conformance from the exdate availableProp description in Vavailability/RFC5545.
Coordinate with resolution to WSCALENDAR-543
Resolution:
Add attributes exdate and comment to AvailabilityType.
Create pim:ExdateType which has a single attribute of type "String" which takes conformance from the exdate availableProp description in Vavailability/RFC5545. This is consistent with NIEM approach.
Coordinate with resolution to WSCALENDAR-541 subtasks
was:
Add attributes exdate and comment to AvailabilityType.
Create pim:ExdateType which has a single attribute of type "String" which takes conformance from the exdate availableProp description in Vavailability/RFC5545.
Coordinate with resolution to WSCALENDAR-543
> Consider Vavailability attributes for AvailabilityType
> ------------------------------------------------------
>
> Key: WSCALENDAR-545
> URL: https://issues.oasis-open.org/browse/WSCALENDAR-545
> Project: OASIS Web Services Calendar (WS-Calendar) TC
> Issue Type: Sub-task
> Components: PIM
> Affects Versions: PIM CS01
> Environment: Steve Ray WS-Calendar-Comment 20150120
> https://lists.oasis-open.org/archives/ws-calendar-comment/201501/msg00000.html
> Reporter: William Cox
> Assignee: William Cox
> Fix For: PIM WD14
>
>
> The ASHRAE SPC201 committee would like to make use of the exDate attribute within the Availability class of the WS-Calendar PIM. This is used to exclude specific dates that would otherwise be included within a recurrence rule. The exDate attribute is part of RFC5545, and since our committee is striving to remain compatible with other standards, including WS-Calendar, we would respectfully request that the exDate attribute be added.
> Extended WTC:
> Consider (e.g. from Page 5) the following:
> exdate
> uid (for parallel with IntervalType, if PIM needs this)
> comment (for parallel with IntervalType)
> Note that dtstart, duration, and tz are already present.
--
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]