Tollef Fog HeenWhy is calendar software so inflexible when it comes to larger events? I’m at #GitHubGalaxy in London and just have a big lump in the calendar instead of it knowing about the structure of the day. Workarounds like putting the structure in the description are just that: workarounds. This is even worse for multi day events.
Asbjørn Ulsberg@tfheen Yeah, it would be nice if an event could be divided into sub-events with individual titles, times, and other metadata. An alternative now is to only add the sub-events directly.
@bitbear sure, that works if I’m adding it myself. If I’m inviting folks for a three day event with a number of sub-events, they should probably be able to say “I’m going to all of it” or “I’m going to just the events on Monday” or “only these individual events”. Similarly, I’d like to have richer ways of responding to invitations and be able to say “I can only attend the first 30 minutes of the meeting” or similar. What surprises me is the lack of innovation in the space.
@tfheen It seems like a market ripe for innovation for sure.
Perhaps the `Related-To` header (which is meant for declaration of parent/child relationships) is usable for something like this?
I don’t think it’s well supported, but it definitely should be.
https://datatracker.ietf.org/doc/html/rfc5545#section-3.8.4.5
RFC 5545: Internet Calendaring and Scheduling Core Object Specification (iCalendar)
This document defines the iCalendar data format for representing and exchanging calendaring and scheduling information such as events, to-dos, journal entries, and free/busy information, independent of any particular calendar service or protocol. [STANDARDS-TRACK]