[JMAP] Re: Call for adoption: draft-gondwana-jmap-object-history-00 (Ends 2026-08-06)

[Ben Bucksch <[e-mail]>]

This sounds intriguing. Generally, file history is very interesting for file
services like NextCloud, for Wiki systems, and generally anything where I store
documents that I modify. So, it's a nice addition to FileNode in particular.

So, I'm in favor of this, as a concept.

A few thoughts:

 * The server may want to keep history only for some data types, e.g. only allow
   to restore deleted emails, but not allow to restore deleted files.

 * For conserving disk space, you may want to keep history only for some
   directories. E.g. video files with meeting recordings of the weekly/daily
   team meetings should not be kept forever, but the disk space be recycled.
   OTOH, I may want to keep a fine-grained file history of the .odt files with
   our specifications.

 * The user may want to really delete files. E.g. because some confidential or
   sensitive information was uploaded accidentally and needs to be purged. JMAP
   verb "destroy" implies that it's really completely ungone, impossible to
   recover. If you now can recover something that was "destroyed", that may
   violate expectations from users.





> This message starts a jmap WG Call for Adoption of:
> draft-gondwana-jmap-object-history-00
> 
> This Working Group Call for Adoption ends on 2026-08-06
> 
> Abstract:
> The JMAP base protocol (RFC8620) provides methods for synchronizing
> the current state of data objects between client and server. This
> extension adds the ability to retrieve historical versions of
> objects, including objects that have been destroyed, by extending the
> standard Foo/get method.
> 
> Please reply to this message and indicate whether or not you support adoption
> of this Internet-Draft by the jmap WG. Comments to explain your preference
> are greatly appreciated. Please reply to all recipients of this message and
> include this message in your response.
> 
> Authors, and WG participants in general, are reminded of the Intellectual
> Property Rights (IPR) disclosure obligations described in BCP 79 [2].
> Appropriate IPR disclosures required for full conformance with the provisions
> of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any.
> Sanctions available for application to violators of IETF IPR Policy can be
> found at [3].
> 
> Thank you.
> [1] https://datatracker.ietf.org/doc/bcp78/
> [https://datatracker.ietf.org/doc/bcp78/]
> [2] https://datatracker.ietf.org/doc/bcp79/
> [https://datatracker.ietf.org/doc/bcp79/]
> [3] https://datatracker.ietf.org/doc/rfc6701/
> [https://datatracker.ietf.org/doc/rfc6701/]
> 
> The IETF datatracker status page for this Internet-Draft is:
> https://datatracker.ietf.org/doc/draft-gondwana-jmap-object-history/
> [https://datatracker.ietf.org/doc/draft-gondwana-jmap-object-history/]
> 
> There is also an HTMLized version available at:
> https://datatracker.ietf.org/doc/html/draft-gondwana-jmap-object-history-00
> [https://datatracker.ietf.org/doc/html/draft-gondwana-jmap-object-history-00]
> 
> --------------------------------------------------------------------------------
> 
> JMAP mailing list -- [e-mail] [[e-mail]]
> To unsubscribe send an email to [e-mail] [[e-mail]]





--
Beonex GmbH
Taunusstein bei Wiesbaden, Germany
CEO / Geschäftsführer: Ben Bucksch
Handelsregister: Amtsgericht Wiesbaden, HRB 30065
parula.app [https://parula.app]