This document contains a list of use cases/requirements for a W3C community-wide calendaring system. It will help the W3C community to organize itself and simplify their handling of meetings. It is intended for W3C Groups at large and to be viewable by a large set of calendar clients.

Use cases

  1. Schedule meetings for Working Groups, Interest Groups, Community Groups, Business Groups, Advisory Board, Task Forces
  2. Schedule joint meetings and meetings with observers/guests
  3. A chair or team contact schedule (video/phone/f2f) meetings at a specific time, or recurring time, within a specific timezone
  4. Provide joining instructions only visible to meeting participants
  5. Participants receive calendar invitations that can be added to their own calendar, in their own local timezone
  6. Participants may signal regrets or intent to participate
  7. A chair or team contact should be able to schedule ad-hoc variation in meeting occurrences:
    1. Cancel if it’s around holidays/f2f meetings/TPAC
    2. Shift by hours or days based on travels, meeting conflicts or UTC/DST
  8. Ability to schedule complex recurrence patterns:
    1. Regular meetings may alternate times within the same month to accommodate global participation (eg CSS)
  9. Attach additional information to each meeting occurrence:
    1. Agenda
    2. Minutes/Notes
  10. … provide a Web view of the calendar


  1. For a Group Chair/TC, using the W3C website
    1. Create, and view group meetings. Creating calendar entries needs to be easy, not idiosyncratic to some edge tool. Many people will need to do this frequently and it should not become an administrative burden.
    2. Use one-time or recurrence patterns:
      1. weekly, bi-weekly, monthly recurrence
        1. “nth XXX-day” (e.g. 1st and 3rd Monday) of the month as well as the Xth of each month.
      2. allow exception dates
      3. allow recurrence end date
    3. Update, move, delete each meeting occurrence at any time
    4. Associate the meeting to the group, a task force, or a subset of group individuals
    5. Add non-group participants to meeting occurrence/recurrence
    6. [nice to have] Create joint meetings (2+ groups)
    7. Anchor the meeting in a specific timezone (UTC by default). The system will provide automatically a link to a timezone converter
    8. [] Optionally, activate meeting invitations/reminders for participants
    9. Provide attendance instructions to meeting participants (with Member-only link for WebEx passcode/Hangout link, if any?)
    10. Link to agenda/notes/minutes for each meeting occurrence
    11. [] [nice to have] Optionally receive notification if a participant confirm/regret
      1. if so, ability to specify an alternate address or web dashboard for those notifications
    12. [] [nice to have] Write access from external clients (ical?)
  2. For meeting participants:
    1. View group meetings using the W3C website
    2. Add/access/synchronize group meetings to a local calendaring client, eg iCal, Google calendar, SOGo, mobile platform, etc. (use iCalendar? and
    3. View group meetings offline (sometime participants are offline when they try to join)
    4. From a meeting occurrence, navigate easily to attendance instructions, agenda, minutes/notes
    5. the meeting information should be easily discoverable in plain text, when receiving invitation (and not just ical)
    6. [] Regrets notifications should not be distributed to everybody else subscribed to the event.
    7. [] [nice to have] Confirm/Regret on calendar invitation
    8. [] [nice to have] Automatic meeting reminders need to be opt-in, and ability to easily opt-out if they have opted in.
  3. For W3C community users
    1. [nice to have] User tailored calendar ideally, e.g. (with all events of my groups, could be a redirect to another application, users can view the calendar or subscribe to one or a set of calendars), with ability to filter events
    2. [] [nice to have] Specific non-W3C users read access (such as family)
  4. For W3C staff
    1. Team members can use the same system to schedule side/non-group related meetings
  5. For W3C website
    1. Provide an organization calendar
    2. Accessible tooling support
    3. Internationalization support (timezones, non-english)
    4. TLS support, W3C account support
    5. Group database integration (DBWG). Support for any W3C groups such as WG, IG, AB, TAG, CG, and various task forces

NOTE: requirements may be met by a combination of off-the-shelf tools.

Guidelines / documentation

Off-the-shelf tools