[calsify] New JSCalendar I-Ds and missing iCalendar conversion

[Robert Stepanek <[e-mail]>]

At last calext session I decided to work on a new JSCalendar I-D that will add new properties to RFC 8984. However, it now is unclear to me how to proceed with this, given that no standard conversion for JSCalendar and iCalendar currently exists.

Work on draft-ietf-calext-jscalendar-icalendar  <https://datatracker.ietf.org/doc/draft-ietf-calext-jscalendar-icalendar/>has stalled since over a year which is meant to define iCalendar conversion for the contents of RFC 8984. And by our charter, any JSCalendar extension "must include a representation in both formats, and define a robust mapping between them". That means to me that the current JSCalendar spec does not live up our requirements, and any new JSCalendar I-D without iCalendar conversion wouldn't either.

Are we going to require draft-ietf-calext-jscalendar-icalendar be published together with any new JSCalendar I-D, or are we fine adding new JSCalendar properties without standard iCalendar conversion?

As the author of both the iCalendar conversion and that new I-D I prefer to get both iCalendar conversion and new JSCalendar properties done at the same time. That's the only way we can be sure to not have missed a thing.

I do understand that the "scheduleId" property is holding back JMAP Calendars, so if that I-D should need to get published before my planned I-D, I suggest the "scheduleId" property should be defined as part of the JMAP spec, including a clear description to calext how this is going to help with converting iCalendar scheduling properties to JSCalendar.

Regards,
Robert