[Cosmo-dev] Bad ICS already extant

[Bobby Rullo]

Well, I'm not sure if it IS an ical4j bug - they are adhering to the  
spec after all (the fact that it emits bad icalendar that itself  
can't parse however is a bug I think though)

I'll bring it up on their forum, check out the code, etc.

But I also wanted to bring it up in case it might help us migrate  
some of the stuff we weren't able to migrate.

Bobby
On Feb 1, 2007, at 12:17 PM, Brian Moseley wrote:

> 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
> _______________________________________________
> cosmo-dev mailing list
> cosmo-dev at lists.osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/cosmo-dev