Loving the momentum which is building up and excited to see JMAP inplementations in both Cyrus and Dovecot - it is less of a chicken and egg scenario now.
The one thing which remains to be discussed in the spec is how shared resources will be handled - ie. mailboxes in a 'shared' namespace, mailboxes belonging to other users, made viewable to other users in the 'other users' namespace and the same going for calendars and contacts. Whilst different services like Fastmail, Google, Kolab al have different sharing allowances, like some across domain, and some across multi-domain, as well as others which allow a more fine-grained control to sharing like Fastmail (per-folder basis). Essentially, with JMAP clients springing up soon, there will need to be some concept of how shared resources are handled, so that users have the choice to match whatever client to server as they please. Whilst this could all get complicated quickly, there needs to be a common way of displaying shared objects client-side. Though different services allow for a variety for different things, there needs to be an api to manage this. -- You received this message because you are subscribed to the Google Groups "JMAP" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jmap-discuss/14b3a1ca-f752-4685-8172-a0bc60dbb20f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
