Re: [calsify] Updated JSCalendar draft calext-01

[Robert Stepanek <[e-mail]>]

Hi Adrian,

I just uploaded a new draft.

On Sat, Mar 3, 2018, at 11:56, Adrian Apthorp wrote:
> Robert,
> 
>  I just noticed that the description of 5.2.8 status is incorrect.

It was defined to be backwards-compatible with iCalendar RFC 5545.
Considering the RFC updates in draft-apthorp-ical-tasks I agree it makes
sense to redefine them also in JSCalendar.
>> The scheduling status (Section 4.4[1]) of a JSTask defaults to "needs-
>> action" if omitted.> 
> Given the possible values it should actually be the overall progress
> status of a JSTask. Of course the distinction with "5.2.7 progress"
> needs to be clear as the individual participants progress.
Done. Please note that my changes are more a basis for discussion than a
final decision, considering the deadline for IETF 101 today.
>  With this is there the opportunity to include the two new task status
>  values as per draft-apthorp-ical-tasks-01.txt and also revise
>  "completed" to be a general purpose status change timestamp.
I'm not sure what change you have in mind for the COMPLETED property? I
could imagine it to be confusing to track general update time-stamps
given the property name?
Cheers,
Robert

Links:

  1. https://tools.ietf.org/html/draft-ietf-calext-jscalendar-01#section-4.4