[JMAP] Feedback on draft-ietf-jmap-filenode-01

[Mauro De Gennaro <[e-mail]>]

Hi Bron,

I've just finished implementing draft-ietf-jmap-filenode-01 in Stalwart, and I wanted to share a few comments and suggestions that came up during the process:

- mayAdmin permission: I think it would be clearer and more consistent with JMAP for Calendars and JMAP for Contacts if mayAdmin were renamed to mayShare. Also, just a gentle reminder that the mayDelete permission is still missing from this version of the draft (I know I mentioned it a few months ago, but I understand you’ve probably had plenty of other things on your plate since then).

- Sharable data types and isSubscribed: According to RFC 9670, a JMAP sharable data type MUST define the myRights, shareWith, and isSubscribed properties. However, I’m not sure isSubscribed makes much sense in the context of file storage. I’d like to hear your thoughts (and Neil’s too) on this. Personally, I think the best approach would be to update JMAP for Sharing so that isSubscribed is no longer a required property for sharable data types.

- FileNode/set destroy clarification: It might be worth clarifying in the draft that when deleting child file nodes as part of a destroy operation with onDestroyRemoveChildren = true, the Set response must include the IDs of all the deleted child file nodes.

- FileNode/query enhancement: I’d also like to propose adding a search property that allows searching inside file contents. For example, a server could index text documents and let users search within them. I think this would be a nice addition to the spec.

Lastly, I’d be happy to help move the JMAP for File Node draft closer to standardization. Please let me know if there’s anything I can do. I don’t think the current draft needs too much work, mostly finalizing the search/sort section and the minor permission changes mentioned above.

Thanks!


Best,
Mauro