[Cosmo-dev] candidate protocol/interop bugs for 0.8

[Brian Moseley]

On 7/18/07, Mikeal Rogers <mikeal at osafoundation.org> wrote:
> The other CalDAV server implementations seemed to have started
> thinking it's a good idea to simply store iCalendar components you
> don't recognize rather than rejecting them outright, while still
> failing on unrecognized attributes of recognized components. This is
> due to the rate at which components are being added, most of them
> being used in the wild before even a draft specification has been
> released to the public.

i'm not opposed to that.

> I heard that part of the benefit to moving to the newest iCal4j was
> that we could not use "strict" mode and we might be to able to do
> this. I know we have a bunch of bugs for this but are we planning to
> go down this road in 0.8?

we're already using relaxed parsing and validation in 0.7, but this
only covers properties and parameters, not entire components. i'll
talk to randy and ben about it. we're tracking the issue with bug
9628.