Tuesday 2024-11-05 15:00-16:00 GMT
Neil: nothing much to talk about. Sharing will publish very soon, in
Auth 48. Comments on calendars to address with IESG review, then to
editors. Contacts with editors already.
Joris:
Motivation - make it easy to move data over generic API. JMAP is a
good fit. ALSO very powerful.
Rest - even lower entry barrier.
Extensions for migration.
Essential: hopefully ready in 4 weeks' time for WGLC.
Hans-Joerg: for JMAPACCESS (OAuth context) - cross check what's needed
for session. We'll discuss on the mailing list.
ACTION: Joris to publish new minimal profile document in the next few
weeks.
Integrate comments from list plus internal TODOs.
Bron: waiting on CALEXT, or other work?
Last IETF, asked for other task vendors, still don't have feedback.
Also things on own TODO list.
(has progressed second-most after essential)
Hans-Joerg: one major distinction between tasks - tasks are MORE diverse
in world outside. Also looked at issue tracking systems. But these
communities don't follow this discussion. If we want to get adoption in
these communities, need to reach out to them. No portability data format
for these systems beyond CSV files.
Have a draft of email to send out - collecting contacts. If you know
somebody at vendors; please get in touch.
Bron: also ask on the mailing list.
Joris: this spec adds a bunch of new properties to the JSCalendar
object; that may be seen as more than just API; bit likely not worth
doing in a separate document.
Bron: might be worth bringing up in CALEXT too.
ACTION: Joris to update other three specs as well.
Neil:
Can only opt to recieve messages when you want to show a notification.
Pass a filter to the server; only send a push if it matches this filter.
Can also ask for properties to be added with the push.
ACTION: Neil to publish emailpush doc, then Bron call for adoption.
Neil: do now? Maybe. If people are interested now, not entirely
convinced. Eventually yes.
Important that we support thing that WebDAV does. No way to have every
feature in Dropbox, etc. Need custom extensions for extra things.
Change blobId for same id. What can you do with filesystems now? If
you could, could do revision history for that node.
Calculated properties: not covered by /changes - we can do that. Also,
not in default set.
Ben: there's metadata as well, so.
Hans-Joerg: migration and data portability enthusiast. Already using it!
Have a client/server quite overlapping already. Already built on
Fastmail API(ish) - could easily adopt this.
Ability to set modification time.
Hashes for files; also an issue right now. (Bron: already covered by
Blob)
Special use folders; might make sense to support.
Share link; many services offer a share link. Tricky/impossible to
migrate right now, but blocking people from migrating.
Bron: subobject "FileInfo" for things that are related for only
resource/files: blobId/type/size? Neil sees maybe. To discuss after
adoption.
ACTION: Jim to do call for adoption
none
Updated.