[Ietf-calsify] Issue 26: BYHOUR, BYMINUTE,
and BYSECOND recurrence rules where value type is DATE
sroberts at uniserve.com
Fri Sep 29 15:12:10 PDT 2006
On Fri, Sep 29, 2006 at 04:25:21PM +0200, Eliot Lear wrote:
> NEW TEXT:
> of hours of the day. Valid values are 0 to 23. Implementations
> MUST NOT generate BYHOUR, BYMINUTE, OR BYSECOND when the associated
> DTSTART uses VALUE=DATE. Similarly, Implementations MUST ignore
> such constructs when see, optionally logging an error.
Are you sure you want to tell people that they MUST accept as valid
files that were generated in violation of a MUST? Seems odd to me to be
in the business of telling people what to do with invalid data, its
hard enough to specify what to do with valid data.
Anyhow, its not clear to me what it means to ignore the "construct". Is
it the entire calendar, the VEVENT, the RRULE, the "BYMINUTE=..." that
shouldn't be there?
If there is concern about apps out there generating data like this,
maybe say "Some implementations are known to generate these fields when
DTSTART uses VALUE=DATE, implementations SHOULD treat any BYHOUR,
BYMINUTE, or BYSECOND as not being present in this case."
More information about the Ietf-calsify