[Cosmo-dev] Bad ICS already extant

[Brian Moseley]

On 2/1/07, Mikeal Rogers <mikeal at osafoundation.org> wrote:

> The consensus seems to be that clients and servesr should start
> accepting and storeing any iCalendar data they don't understand and
> not remove it or fail.

as i mentioned in the comment to a bug yesterday:

in a recent trunk build, ical4j introduced a "relaxed parsing mode"
that won't barf on unknown component names like VAVAILABILITY and
VVENUE. merging the ical4j trunk into our local (patched) copy is
tentatively scheduled for 0.7. so hopefully for preview we'll be able
to play nice with ical, eventful and other vendors who are extending
icalendar in this way.

bobby, have you filed an ical4j bug about this, or looked at working
up a patch? :D