Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
Export (0) Print
Expand All

4.1.4.1 Interpreting a Precise Date Value

The mail app requests the MeetingSuggestion known entities on a message. The client checks the value of the PidNameExtractedMeetings property (section 2.2.2.4) and finds the following value for the StartTime element, as described in section 2.2.3.1.29.

0040-01-13T20:00:00Z

Because January 13, 0040, is before June 15, 1436, the value is an encoded date. The client interprets the value according to the rules described in section 3.1.4.4.1.

  1. The client determines that the number of days from January 1, 0001, to January 13, 0040, is 14256.

  2. In 18-bit binary form, this value is 000011011110110000.

  3. The 3 most significant bits are 000, which indicates that the encoded date is a precise date.

Because this is a precise date, the 15 least significant bits (011011110110000) are interpreted according to the rules described in section 3.1.4.4.1.1.

  1. The value is split into two values. The 3 most significant bits (011) represent the type, and the 12 remaining bits (011110110000) represent the value.

  2. Since the type bits are 011, the value represents a month and day. The 4 most significant bits (0111) are converted to decimal (7) to determine the month (July). The next 5 most significant bits (10110) are converted to decimal (22) to determine the day.

The precise date value is July 22.

Show:
© 2015 Microsoft