Share via

3.1.4.2.3 Writing Category List

  • Article

The client MUST read any existing settings from the configuration data message, as specified in section 3.1.4.1. If any existing settings are found, the client MUST parse the XML document, as specified in section 2.2.5.2.

When clients encounter unknown tags or attributes, they SHOULD ignore them, but they SHOULD also rewrite them as-is when they rewrite the category list back to the configuration data message.

The client MUST generate the XML document as specified in section 2.2.5.2 and save it to the configuration data message as specified in section 3.1.4.2.

Each category in the category list, as specified in section 2.2.5.2.2, contains the following attributes:

  • lastTimeUsed

  • lastTimeUsedMail

  • lastTimeUsedCalendar

  • lastTimeUsedContacts

  • lastTimeUsedTasks

  • lastTimeUsedNotes

  • lastTimeUsedJournal

The lastTimeUsed attribute MUST be set on all categories. All others are optional and depend on whether the client shows different message types in separate windows or panes.

All times MUST be stored relative to UTC. When a category is applied to a message, as specified in section 3.1.4.7, or the user visible properties of the category are changed (such as color or shortcut key), the client SHOULD update the lastTimeUsed attribute and, depending on whether the client separates different message types, SHOULD replace the appropriate type-specific time stamp with the current time.