AD review issue #4: Supporting both VTODO and VEVENT in thesame iCalendar stream (was: Re: [Ietf-calsify] Re: AD review on2445bis )

Reinhold Kainhofer reinhold at
Mon Sep 8 15:46:27 PDT 2008

Hash: SHA1

Am Dienstag, 9. September 2008 schrieb Tim Hare:
> I thought the very definiton of x-properties was that they were
> 'experimental' and as such not "properly" part of the specification which
> needed to be handled by all conforming pieces of software.  I think that
> they should be ignored, but not necessarily discarded - if a CUA creates an
> iCalendar object with x- properties and asks a CS to store it, AND the CS
> does not recognize those x-properties it should still, in opinion, store
> them but take no action on them or because of them.

I completely agree, that's why I find the word "ignore" not ideal.
I just wanted to point out that "ignore" might possibly be misunderstood 
as "feel free to discard them". It makes a difference if you ignore a 
property/parameter on reading (i.e. don't parse it at all and thus also not 
save it) or ignore it on processing (i.e. it's there but you don't do 
anything with it).
This also applies to the issues #79 of my review of rfc2446bis-07.

- -- 
- ------------------------------------------------------------------
Reinhold Kainhofer, Vienna University of Technology, Austria
email: reinhold at,
 * Financial and Actuarial Mathematics, TU Wien,
 * K Desktop Environment,, KOrganizer maintainer
 * Chorvereinigung "Jung-Wien",
Version: GnuPG v1.4.6 (GNU/Linux)


More information about the Ietf-calsify mailing list