2.2.2.4 Data Model for Requests
-
provisioningGroupList | |-- provisioningGroup
The following XML schema definition (XSD)<20> fragment defines the requirements to which a provisioningGroupList XML document SHOULD conform.
-
<xs:complexType name="ProvisioningGroupListType"> <xs:sequence> <xs:element name="provisioningGroup" type="ProvisioningGroupType" maxOccurs="unbounded"/> <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> <xs:attribute name="subnet" type="IPAddress" use="optional"/> <xs:anyAttribute namespace="##other" processContents="lax"/> </xs:complexType> <xs:complexType name="ProvisioningGroupType"> <xs:sequence> <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> <xs:attribute name="name" type="xs:string" use="required"/> <xs:attribute name="opaque" type="xs:string" use="optional"/> <xs:anyAttribute namespace="##other" processContents="lax"/> </xs:complexType> <xs:element name="provisioningGroupList" type="ProvisioningGroupListType"/>
-
provisioningGroupList: A list of available provisioningGroup elements.
-
provisioningGroup: A set of configuration data requested by the sending entity. The name attribute indicates the type of configuration data being requested. The following valid values are defined for the name attribute:
ServerConfiguration: Global Server Configuration and Provisioning Data.
meetingPolicy: Global Conferencing Policy Data, which is used for multi-party conferencing.
ucPolicy: Global Unified Communications Policy Data.
publicationGrammar: Grammar describing the publication of presence information, including presence containers and membership information based on rules defined by server administrators.
userSetting: User-specific configuration data.
endpointConfiguration: Client endpoint-specific configuration data. It controls the behavior of specific features of the client.<21>
locationPolicy: Location related configuration applied to users.<22>
mediaConfiguration: Media-related configuration data.<23>
presencePolicyV2: Presence-related configuration data.<24>
privacyPublicationGrammar: Privacy-related grammar describing presence containers and membership information based on rules defined by server administrators. <25>
publicProviders: Data on currently supported public providers.<26>
The following XSD schema<27> fragment defines the requirements to which a provisioningGroupList XML document SHOULD conform.
-
<xs:complexType name="ProvisioningGroupListType"> <xs:sequence> <xs:element name="provisioningGroup" type="ProvisioningGroupType" maxOccurs="unbounded" ms:propertyName="ProvisioningGroups"/> <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> <xs:attribute name="subnet" type="IPAddress" use="optional" ms:propertyName="Subnet"/> <xs:anyAttribute namespace="##other" processContents="lax"/> </xs:complexType> <xs:complexType name="ProvisioningGroupType" ms:className="ProvisioningGroupXmlDocumentResult"> <xs:sequence> <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> <xs:attribute name="name" type="xs:string" use="required" ms:propertyName="Name"/> <xs:attribute name="opaque" type="xs:string" use="optional" ms:propertyName="Opaque"/> <xs:anyAttribute namespace="##other" processContents="lax"/> </xs:complexType> <xs:element name="provisioningGroupList" type="ProvisioningGroupListType" ms:className="CProvisioningGroupListXmlDocumentRoot"/>