container Element

Article
05/23/2014

This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release.

This multi-use element can be used to request the addition or removal of contacts from a given presence level access container. As part of an event returned as the result of logon, the container element is the envelope that holds an access control list.

Syntax

<container id="integer value"/>

Attributes

Attribute	Data Type	Description
Id	Integer	The container ID that identifies the container. The id values can be in the range of 1 to 32767. This is required attribute.

Element Information

Parent Element

Element	Description
updateContainer	Adds members to or removes members from a container. This is a request element.
containers	Returns a list of containers, with a full list of the membership for each container. This is an event element.

Child Elements

Element	Occurrences	Description
addMember	0 or more	The member to be added to the container. This member is only allowed when the container element is part of an updateContainer request
deleteMember	0 or more	The member to be deleted from the container. This member is only allowed when the container element is part of an updateContainer request.
member	O or more	This element is present when the container element is returned as part of an asynchronous event. A member represents an entity added to a container.

Remarks

Containers are used to control user access to category data. Container Ids map the logged-on users individual contacts into presence access levels. Office Communicator uses the following standard container identities:

100 Public
200 Workplace
300 Team
400 Personal
32000 Block

Containers 0, 1, 2, and 3 map a given users presence information into presence access levels. For example, container 3 holds all user presence information available to any contact assigned to container 400. For more information, see Publish And Subscribing To Presence.

Examples

The container element below is an example of the element used as a request element. The domain contoso.com and an individual user are being added to the container with the highest presence access level of the logged-on user.

<container id="400">
   <addMember type="domain" value="contoso.com" />
   <addMember type="uri" value="sip:jessicaa@contoso.com"/>
</container>

The following XML tree fragment is returned when a user has logged on to Unified Communications. The containers element would envelope all of the presence information for the user and their contacts. The container Ids shown are actual well-known containers, which are Unified Communications standards for containing categorized data.

<containers eid="3">
   <container id="32000" version="0" />
   <container id="400" version="0" />
   <container id="300" version="0" />
   <container id="200" version="1">
<member type="sameEnterprise" />
   </container>
   <container id="100" version="1">
      <member type="federated" />
   </container>
   <container id="3" version="0" />
   <container id="2" version="0" />
   <container id="1" version="0" />
   <container id="0" version="0">
      <member type="everyone" />
   </container>
</containers>