[Jmap] Tasks (draft-ietf-jmap-tasks-04) and recurrence

[Ricardo Signes <[e-mail]>]

Hi all,

I'm a bit late to the game here, but have tried to find and read past discussion before posting.  I hope I'm not rehashing anything, here.

Last night, I was giving a read to draft-ietf-jmap-tasks-04 and thinking about the way that it divides its features up into a larger number of capabilities than JMAP for Calendars.  The splitting off of "recurrence" gave me pause.

I know that not all todo systems have every feature, specified in the draft, but I'm not sure I see what this one is meant to fix.  It's either meant for the server or the client, right?  If it's to allow a server to say "I do not support recurrence," then I think it will work fine.  But by existing, it also allows the client to omit the recurrence capability from requests.  I think that means this scenario is possible:
 * the server supports recurrence
 * client A connects to the server, puts recurrence in its request's "using", and makes Tasks with recurrence rules
 * client B connects to the server and looks at the Tasks available
What do they see?  They can't see the recurrence rules.  They also (presumably) can't use expandRecurrences, so they can't treat the recurrences more or less like many individual events.  I think in this scenario, client B is likely to be impossible to use well.

I don't have a clearly ideal solution to suggest at the moment.  But is this even a problem, as I think it is?

-- 
rjbs