Re: [calsify] Updated JSCalendar draft calext-01

[Adrian Apthorp <[e-mail]>]

Robert,

Thanks - a couple of comments below:

> On 5 Mar 2018, at 6:51 PM, Robert Stepanek <[e-mail]> wrote:
> 
> 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.

Understood. However, 5545 does not describe the purpose to indicate the scheduling status of a task. I was suggesting to reword the purpose.

> 
>>> The scheduling status (Section 4.4) 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.

I think the only comment I have is not to define the rules for how a participant progress propagates to the task status. These are likely to be business rules that are determined by the organiser or defined for a specific type of task. They can be manually applied or automated.

> 
>> 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?

Yes, I didn’t complete the thought in my original message. What I was thinking was to rename this property (status-changed) and then it becomes applicable to all status changes. Presumably it can still be mapped to 5545 COMPLETED when that status is achieved.

Cheers

Adrian