2.1.3.1.1.1 Property: METHOD

RFC Reference: [RFC2445] section 4.7.2

Number of Instances Allowed: 0, 1

Format: Text ([RFC2445] section 4.3.11)

Brief Description: Distinguishes normal appointments from meeting requests, responses, and cancellations.

Importing to Calendar objects

The METHOD property SHOULD<2> be imported as the PidTagMessageClass ([MS-OXPROPS] section 2.788) and PidLidAppointmentCounterProposal ([MS-OXPROPS] section 2.10) of all imported Calendar objects, as specified in the table later in this section. In the case where the METHOD property is set to 'REPLY', the PidTagMessageClass has several possible values depending on the PARTSTAT parameter (as specified in section 2.1.3.1.1.20.2.3) of the ATTENDEE property (as specified in section 2.1.3.1.1.20.2) of the VEVENT component (as specified in section 2.1.3.1.1.20). If the METHOD property is set to 'REPLY' or 'COUNTER', the iCalendar MUST have exactly one ATTENDEE property and exactly one such PARTSTAT parameter.

In the case where the METHOD property is set to 'REQUEST', 'REPLY', or 'CANCEL', the VCALENDAR component MUST define exactly one appointment.<3>

Exporting from Calendar objects

For exports of calendars, the METHOD property MUST be left unset or set to 'PUBLISH'. For exports of individual Calendar objects, the PidTagMessageClass and PidLidAppointmentCounterProposal of the Calendar object SHOULD<4> be exported as the METHOD property as specified in the table earlier in this section.