Required for Hijri calendar support. @advanceHijriValue ranges from {-3,-2,-1,1,2,3} and is added to the current date, but the day of the week stays the same. For example, if today is the 24th and @advanceHijriValue is set to be +2, then the user sees the date as being the 26th. Typically @advanceHijriValue is +/-1, and this suffices in most cases. Theoretically it can be any number, but the worst case scenario is +/-3.

This element contains attachment metadata, name, content-type and id's, and may also contain the attachmentBody.

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.