Why remove To Dos and Journals from RFC 2445?

Journal specifications were an easy hit – almost no vendor provides interoperable capabilities within the format and weblogs have now become the preferred standard.

Removing To Do’s had a more heated discussions, in the end two themes seem to prevail: first, the issue with the current iCalendar standard is that it tried to do everything and may have short-changed the To Do schema. The message here was not to repeat the same mistake. The second theme was that with extensions, it would be simple to add a new To Do spec – hopefully with a better model.

That’s it on the major changes from RFC 2445 to ICAL-BASIC

Comments appreciated here and on the ietf-calsify mailing list

Leave a Reply

You must be logged in to post a comment.