3.8.5.3 Creation of workingHours category

 This section describes behaviors supported in versions described by endnote <46>.

An enhanced presence server creates a workingHours category instance by extracting working hours information from the instance zero of the calendarData category in container 1, as specified in the following diagram.

Figure 11: Creating a workingHours category instance

SIP protocol client: The SIP protocol client MUST publish instance zero of the calendarData category into container 1. Although the server does not prevent it, the SIP protocol client MUST NOT add any members to container 1. When publishing the calendarData category instance, the SIP protocol client MUST compare existing data with the new data to avoid publication if there are no changes.

Computing function: The computing function in the server MUST be triggered if there are any publications to the calendarData category in container 1. The computing function MUST extract the WorkingHours element from instance zero of the calendarData category in container 1 to create and publish instance zero of the workingHours category in container 1. If calendarData category is unpublished from container 1 or workingHours element is removed from calendarData category, computing function MUST unpublish the workingHours category from container1. The computing function MUST compare existing data with new data to avoid publication if there are no changes. For examples of the workingHours category instance generation, see section 4.3.3.