Hi,
2 remarks:
- This change has the disadvantage of losing the reference to iCal/xCal. Shouldn’t we add somewhere a reference table for mapping of iCal/xCal and WS-Calendar ? I cannot find it, maybe it is already there ?
- Is it 100% true that an interval is part of a sequence. Is it forbidden to bind an interval directly to a gluon, without an intermediate Sequence element ?
Regards
Benoît LEPEUPLE
Product Manager
ARC Informatique
2 avenue de la cristallerie - 92310 SEVRES - FRANCE
Tel: +33 1 41 14 36 00 - Mobile: +33 6 87 80 20 43
Email : b.lepeuple@arcinfo.com
De : Toby Considine [mailto:tobyconsidine@gmail.com] De la part de Toby Considine
Envoyé : mercredi 11 mai 2011 17:11
À : ws-calendar@lists.oasis-open.org
Objet : [ws-calendar] Defining the Interval - critical
Table 1-3 defines Interval as follows
The Interval is a single Duration derived from the common calendar Components as defined in iCalendar ([RFC5545]) and refined in [XCAL]. In Calendar systems, it is similar to the Component VTODO, but the constraints and conformance are different.
New verbiage, which should go somewhere
Note: An Interval is part of a Sequence. An entire sequence can be scheduled by scheduling a single Interval in a sequence. A Sequence can be scheduled multiple times through repeated reference by different Gluons. For this reason, of the three primary temporal elements (dtStart, dtEnd, and Duration) in a component, the Duration has primacy in Intervals. Within a Sequence, a maximum of a single Interval MAY have a dtStart or a dtEnd.
(where do we put this?)
If we agree to this language, many Jira comments can be addressed.
tc
“The single biggest problem in communication is the illusion that it has taken place.”
– George Bernard Shaw.
Toby Considine TC Chair: oBIX & WS-Calendar TC Editor: EMIX, EnergyInterop U.S. National Inst. of Standards and Tech. Smart Grid Architecture Committee | | Email: Toby.Considine@gmail.com http://www.tcnine.com/ |