Who is invited, what they answered, how clashes are detected and how times are renegotiated.
f-participant-role-and-response
Participant role and response state
Roles participants hold on an entry, their current response, and how delegation is represented.
Questions
- In which role does each participant appear on the entry?classification
Expected answer
- Role code
- Required or optional flag
- Role source vocabulary
- What is each participant's current response state, and when was it last updated?state
Expected answer
- Participation status code
- Status update timestamp
- Updating agent
- Is a reply expected from this participant, and by when?process
Expected answer
- Reply expected flag
- Reply deadline
- Reminder policy
- When a participant delegates, how are delegator and delegate linked on the entry?relationship
Expected answer
- Delegated-to reference
- Delegated-from reference
- Whether the delegator remains listed
Artifacts
- Participant rosterThe set of participants on an entry with roles, response states, reply expectations and delegation links.
f-conflict-detection-and-rescheduling
Conflict detection and rescheduling
Whether an entry consumes availability, how clashes are found, and how alternative times are proposed and recorded.
Questions
- Does this entry consume the participant's availability or leave them free?definition
Expected answer
- Transparency or free-busy status code
- Effect on availability computation
- How are overlapping commitments detected across separate calendars and plans?process
Expected answer
- Detection scope
- Overlap rule
- Detected conflict set
- How is an alternative time proposed, accepted or declined?decision
Expected answer
- Proposed alternative values
- Proposing party
- Decision outcome and decider
- When an entry moves, what records the previous time and the reason?provenance
Expected answer
- Previous start and end
- Reason code
- Deciding agent
- Decision and application timestamps
Artifacts
- Free/busy projectionAvailability-only view over a bounded horizon, disclosing busy intervals without entry content, used for conflict detection across parties.
f-scheduling-method-and-message-sequencing
Scheduling methods and message sequencing
iTIP methods are PUBLISH, REQUEST, REPLY, ADD, CANCEL, REFRESH, COUNTER and DECLINECOUNTER. Organizer may send PUBLISH, REQUEST, ADD, CANCEL and DECLINECOUNTER; Attendee may send REPLY, REFRESH, COUNTER and a delegation REQUEST. Correlation keys are UID, RECURRENCE-ID, SEQUENCE and DTSTAMP: higher SEQUENCE obsoletes lower for the same UID and recurrence id; matching SEQUENCE ties break on later DTSTAMP. SEQUENCE MUST increment when Organizer changes DTSTART, DTEND, DURATION, DUE, RRULE, RDATE, EXDATE or STATUS. JSCalendar sequence and method (lowercase iTIP method) carry the same semantics. Out-of-order replies must be discarded using persisted last SEQUENCE and DTSTAMP per attendee.
Questions
- Which scheduling method is being applied, who may send it, and is this a new object or a revision of an existing UID?process
Expected answer
- method (enum)
- originator_role (enum)
- is_new_uid (boolean)
- What SEQUENCE and stamp time identify this revision, and does it obsolete a previously stored component with the same UID and recurrence id?lifecycle
Expected answer
- sequence (integer)
- stamp_time (rfc3339-date-time)
- obsoletes_sequence (integer)
- If a reply arrives with a lower sequence or earlier stamp than the last persisted attendee response, should it be discarded?evidence
Expected answer
- last_persisted_sequence (integer)
- last_persisted_stamp (rfc3339-date-time)
- discard (boolean)
- What spoofing, unauthorized organizer-replacement or flood controls apply to this scheduling message, as warned in iTIP security considerations?access
Expected answer
- authenticated_originator (boolean)
- organizer_replacement_authorized (boolean)
Artifacts
- Scheduling messageOne iTIP-style method payload correlated by UID, recurrence id, sequence and stamp time.