complexType "attendeeResponseType"
Namespace:
http://schemas.microsoft.com/hs/2001/10/myCalendar
Content:
complex, 6 elements
Defined:
globally in myCalendar.xsd; see XML source
Used:
at 1 location
XML Representation Summary
<...>
   
Content: 
</...>
Content Model Elements (6):
counterProposeEndTime (type xsd:dateTime), counterProposeLocation (type xsd:string), counterProposeStartTime (type xsd:dateTime), responseBody (type hs:longText), responseTime (type xsd:dateTime), responseType (type attendeeAcceptEnum)
All Direct / Indirect Based Elements (1):
respondRequest
Known Usage Locations
XML Source (see within schema source)
<xsd:complexType name="attendeeResponseType">
<xsd:group ref="attendeeResponseGroup"/>
</xsd:complexType>
Content Element Detail (all declarations; 6/6)
counterProposeEndTime
Type:
xsd:dateTime, predefined, simple content
Defined:
locally within attendeeResponseGroup group
If responseType=[counterPropose], then either the {startTime, endTime}, or location, or both can be present. This is the invitee's counterProposal for a new end time for the meeting. This is stored in UTC.
XML Source (see within schema source)
<xsd:element maxOccurs="1" minOccurs="0" name="counterProposeEndTime" type="xsd:dateTime">
<xsd:annotation>
<xsd:documentation>
If responseType=[counterPropose], then either the {startTime, endTime}, or
location, or both can be present. This is the invitee's counterProposal
for a new end time for the meeting. This is stored in UTC.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
counterProposeLocation
Type:
xsd:string, predefined, simple content
Defined:
locally within attendeeResponseGroup group
If responseType=[counterPropose], then either the {startTime, endTime}, or location, or both can be present. This is the invitee's counterProposal for a location for the meeting.
XML Source (see within schema source)
<xsd:element maxOccurs="1" minOccurs="0" name="counterProposeLocation" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
If responseType=[counterPropose], then either the {startTime, endTime}, or
location, or both can be present. This is the invitee's counterProposal
for a location for the meeting.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
counterProposeStartTime
Type:
xsd:dateTime, predefined, simple content
Defined:
locally within attendeeResponseGroup group
If responseType=[counterPropose], then either the {startTime, endTime}, or location, or both can be present. This is the invitee's counterProposal for a new start time for the meeting. This is stored in UTC.
XML Source (see within schema source)
<xsd:element maxOccurs="1" minOccurs="0" name="counterProposeStartTime" type="xsd:dateTime">
<xsd:annotation>
<xsd:documentation>
If responseType=[counterPropose], then either the {startTime, endTime}, or
location, or both can be present. This is the invitee's counterProposal
for a new start time for the meeting. This is stored in UTC.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
responseBody
Type:
hs:longText, simple content
Defined:
locally within attendeeResponseGroup group
Optional message for invitees to include along with the response.
XML Source (see within schema source)
<xsd:element maxOccurs="1" minOccurs="0" name="responseBody" type="hs:longText">
<xsd:annotation>
<xsd:documentation>
Optional message for invitees to include along with the response.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
responseTime
Type:
xsd:dateTime, predefined, simple content
Defined:
locally within attendeeResponseGroup group
The reply time on each attendee is set to the current time (Now) when the organizer sends a meeting invitation. When the attendee responds, they always update their responseTime. When the organizer receives responses, they will honor only those that have a higher responseTime than what s/he maintains in his/her own copy of the event for each attendee. While processing the response, the organizer will update their responseTime. This guarantees that the organizer honors only the most recent response from the attendee. This is stored in UTC. <br/><b>ICAL Equivalent</b>: reply time on message.
XML Source (see within schema source)
<xsd:element maxOccurs="1" minOccurs="0" name="responseTime" type="xsd:dateTime">
<xsd:annotation>
<xsd:documentation>
The reply time on each attendee is set to the current time (Now) when the organizer
sends a meeting invitation. When the attendee responds, they always update their
responseTime. When the organizer receives responses, they will honor only those that
have a higher responseTime than what s/he maintains in his/her own copy of the event for
each attendee. While processing the response, the organizer will update their
responseTime. This guarantees that the organizer honors only the most recent response
from the attendee. This is stored in UTC.
<br/>
<b>ICAL Equivalent</b>
: reply time on message.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
responseType
Type:
attendeeAcceptEnum, simple content
Defined:
locally within attendeeResponseGroup group
The accept status indicates the valid types of responses that an attendee can reply with {accept, decline, tentative, counterpropose}. The absense of this field indicates that no response has been recorded (either the invitation has not been sent, or that a reply has not been received).
XML Source (see within schema source)
<xsd:element maxOccurs="1" minOccurs="0" name="responseType" type="attendeeAcceptEnum">
<xsd:annotation>
<xsd:documentation>
The accept status indicates the valid types of responses that an attendee
can reply with {accept, decline, tentative, counterpropose}. The absense
of this field indicates that no response has been recorded (either the
invitation has not been sent, or that a reply has not been received).
</xsd:documentation>
</xsd:annotation>
</xsd:element>