element <reminder> (local)
Namespace:
http://schemas.microsoft.com/hs/2001/10/myCalendar
Type:
reminderBlueType
Content:
complex, 3 attributes, 6 elements
Defined:
locally within eventType complexType in myCalendar.xsd; see XML source
XML Representation Summary
<reminder
   
 = 
xsd:nonNegativeInteger
 = 
xsd:hexBinary
 = 
xsd:string
   
>
   
Content: 
</reminder>
Content model elements (6):
interruptability (type xsd:int), lastSentTime (type xsd:dateTime), nextTriggerTime (type xsd:dateTime), offset (type xsd:int), set (type xsd:boolean), to (type hs:localizableString)
Included in content model of elements (1):
event (in myCalendar)
Annotation
A user may optionally define a reminder for this appointment. Reminders for recurring appointments will be sent periodically before the appointment as per the rules defined in the reminder subschema. A non-recurring event may have the following: <li>Define no reminders</li> <li>Define a reminder with <set> = "true"</li> <li>Define a reminder with <set> = "false" (<b>useless</b>)</li><br/> A recurring meeting may have any of the following: <li>Define no reminders</li> <li>Define a recurring reminder with all instances receiving reminders</li> <li>To define no reminders by default, but to define reminders for particular meeting instances in the exception body: Create a reminder <set> = "false", and turn it on and/or modify it for particular instances.</li> <li>To define a recurring reminder, but turn it off for particular meeting instances: Create a reminder <set> = "true", and turn it off for particular instances.</li><br/> If the event's reminder subschema is non-existent, yet the exception body has a reminder blob, then the exception reminder is ignored. The alternative is to require 1..1.
XML Source (see within schema source)
<xsd:element maxOccurs="1" minOccurs="0" name="reminder" type="reminderBlueType">
<xsd:annotation>
<xsd:documentation>
A user may optionally define a reminder for this appointment. Reminders
for recurring appointments will be sent periodically before the appointment
as per the rules defined in the reminder subschema. A non-recurring event may
have the following:
<li>Define no reminders</li>
<li>Define a reminder with &lt;set&gt; = "true"</li>
<li>
Define a reminder with &lt;set&gt; = "false" (
<b>useless</b>
)
</li>
<br/>
A recurring meeting may have any of the following:
<li>Define no reminders</li>
<li>
Define a recurring reminder with all instances receiving reminders
</li>
<li>
To define no reminders by default, but to define reminders for particular
meeting instances in the exception body: Create a reminder &lt;set&gt; = "false", and turn it on
and/or modify it for particular instances.
</li>
<li>
To define a recurring reminder, but turn it off for particular meeting instances: Create a
reminder &lt;set&gt; = "true", and turn it off for particular instances.
</li>
<br/>
If the event's reminder subschema is non-existent, yet the exception body has a reminder blob,
then the exception reminder is ignored. The alternative is to require 1..1.
</xsd:documentation>
</xsd:annotation>
<!--
<xsd:annotation>
<xsd:documentation>
A user may optionally define 1 to 4 reminders for this event for
each device type.
Reminders are hosted on .NET Calendar, but they use .NET Alerts as
a gateway to deliver the actual notification. Client-support
for reminders is also included in the base schema. The user
may define any or all of the four kinds of reminders:
<br/><br/>
<table cellpadding="1" cellspacing="1" border="1">
<tr>
<td align="center"><b>Value</b></td>
<td align="center"><b>Description</b></td>
</tr>
<tr>
<td>client</td>
<td>Client performs the reminder</td>
</tr>
<tr>
<td>email</td>
<td>.NET Calendar sends an email to the specified address (via??)</td>
</tr>
<tr>
<td>messenger</td>
<td>.NET Calendar sends a messenger alert to the user (via .NET Alerts)</td>
</tr>
<tr>
<td>mobile</td>
<td>.NET Calendar sends a mobile alert to the user (via .NET Alerts)</td>
</tr>
</table>
</xsd:documentation>
</xsd:annotation>
-->
</xsd:element>
Attribute Detail (all declarations; 3/3)
changeNumber
Type:
hs:changeNumberType
Use:
required
Defined:
locally within hs:standardBlueAttributeGroup attributeGroup
XML Source (see within schema source)
<xsd:attribute name="changeNumber" type="changeNumberType" use="required"/>
creator
Type:
hs:creatorType
Use:
required
Defined:
locally within hs:standardBlueAttributeGroup attributeGroup
XML Source (see within schema source)
<xsd:attribute name="creator" type="creatorType" use="required"/>
id
Type:
hs:idType
Use:
required
Defined:
locally within hs:standardBlueAttributeGroup attributeGroup
XML Source (see within schema source)
<xsd:attribute name="id" type="idType" use="required"/>
Content Element Detail (all declarations; 6/6)
interruptability
Type:
xsd:int, predefined, simple content
Defined:
locally within reminderType complexType
This optional element defines how interruptible this event is and it is used by notification routing software to make decisions about the relay and deferral of notifications that might occur while this meeting is active. The value contained in this element is a numeric value between 1 - 10. Low values represent a high cost of disruption, high values represent a low cost of disruption.
XML Source (see within schema source)
<xsd:element maxOccurs="1" minOccurs="0" name="interruptability" type="xsd:int">
<xsd:annotation>
<xsd:documentation>
This optional element defines how interruptible this event is and it is
used by notification routing software to make decisions about the relay
and deferral of notifications that might occur while this meeting is
active. The value contained in this element is a numeric value between
1 - 10. Low values represent a high cost of disruption, high values
represent a low cost of disruption.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
lastSentTime
Type:
xsd:dateTime, predefined, simple content
Defined:
locally within reminderType complexType
Required by reminder engine.
XML Source (see within schema source)
<xsd:element name="lastSentTime" type="xsd:dateTime">
<xsd:annotation>
<xsd:documentation>
Required by reminder engine.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
nextTriggerTime
Type:
xsd:dateTime, predefined, simple content
Defined:
locally within reminderType complexType
Determines the next time to trigger reminder.
XML Source (see within schema source)
<xsd:element name="nextTriggerTime" type="xsd:dateTime">
<xsd:annotation>
<xsd:documentation>
Determines the next time to trigger reminder.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
offset
Type:
xsd:int, predefined, simple content
Defined:
locally within reminderType complexType
Specifies the offset, in minutes, of how long before the event the user should be reminded. Recommended values are the following: <table border="1" cellpadding="1" cellspacing="1"> <tr> <td align="center"><b>Value</b></td> <td align="center"><b>Description</b></td> </tr> <tr> <td>5, 10, 20, 30, 45</td> <td>5, 10, 20, 30, 45 minutes before the event</td> </tr> <tr> <td>60, 120, 180,</td> <td>1, 2, 3 hours before the event</td> </tr> <tr> <td>startTime - startDay</td> <td>The day of the event (reminder sent at 12:00am)</td> </tr> <tr> <td>startTime - (startDay - (1440 * x))</td> <td>"x" days before the event (reminder sent at 12:00am "x" days before)</td> </tr> </table>
XML Source (see within schema source)
<xsd:element name="offset" type="xsd:int">
<xsd:annotation>
<xsd:documentation>
Specifies the offset, in minutes, of how long before the
event the user should be reminded. Recommended values
are the following:
<table border="1" cellpadding="1" cellspacing="1">
<tr>
<td align="center">
<b>Value</b>
</td>
<td align="center">
<b>Description</b>
</td>
</tr>
<tr>
<td>5, 10, 20, 30, 45</td>
<td>5, 10, 20, 30, 45 minutes before the event</td>
</tr>
<tr>
<td>60, 120, 180,</td>
<td>1, 2, 3 hours before the event</td>
</tr>
<tr>
<td>startTime - startDay</td>
<td>The day of the event (reminder sent at 12:00am)</td>
</tr>
<tr>
<td>startTime - (startDay - (1440 * x))</td>
<td>
"x" days before the event (reminder sent at 12:00am "x" days before)
</td>
</tr>
</table>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
set
Type:
xsd:boolean, predefined, simple content
Defined:
locally within reminderType complexType
Boolean flag that indicates whether the reminder is active for this event. In most cases, this will be true, but in the case of a recurring appointment, this flag may default to true with specific instances not to be reminded, or default to false, with specific instances to be reminded.
XML Source (see within schema source)
<xsd:element name="set" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Boolean flag that indicates whether the reminder is active for this
event. In most cases, this will be true, but in the case of a recurring
appointment, this flag may default to true with specific instances not to
be reminded, or default to false, with specific instances to be reminded.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
to
Type:
hs:localizableString, simple content
Defined:
locally within reminderType complexType
Friendly name that this reminder is being sent to.
XML Source (see within schema source)
<xsd:element name="to" type="hs:localizableString">
<xsd:annotation>
<xsd:documentation>
Friendly name that this reminder is being sent to.
</xsd:documentation>
</xsd:annotation>
</xsd:element>