MSPROV DTD Elements
4/8/2010
To enable continuous provisioning, MSPROV DTD introduces new attributes to the parm element defined in the OMA Client Provisioning specification. It also provides additional "query" and "remove" functionality. MSPROV DTD describes the Provisioning XML File, the document that is passed between the provisioning source and the device.
MSPROV DTD uses the following elements:
| Element | Description |
|---|---|
Allows you to group settings. |
|
Indicates that an error occurred while a characteristic element in the XML document is processing. When an error occurs, the erroneous element is changed to a characteristic-error element. |
|
Queries the setting values designated by the characteristic type attributes. |
|
Indicates that an error occurred while a characteristic-query element from the XML document was processed. When an error occurs, the erroneous element is changed to a characteristic-query-error element. |
|
In a request message, indicates the settings to be removed. In a response message, indicates the elements that do not exist. |
|
Indicates that an error occurred while a nocharacteristic element was processed. When an error occurs, the erroneous element is changed to a nocharacteristic-error element. |
|
In a request message, this element indicates the setting to be removed. In a response message, this element indicates that the corresponding parm identified by the name attribute does not exist. |
|
If an error occurs while a noparm element is processing, the erroneous element will be changed to a noparm-error element. |
|
This element contains metadata that describes how that data is to be viewed and edited by the Configuration Service Provider. |
|
If an error occurs while a parm element is processing, the erroneous element will be changed to a parm-error element. |
|
specifies a request for the current value of the setting designated by the name attribute. |
|
If an error occurs while a parm-query element is being processed, the erroneous element will be changed to a parm-query-error element. |
Remarks
For the majority of XML documents, the most common node types are element, attribute, and text. Attributes occupy a special place in the model because they are not considered child nodes of a parent and are treated more like properties of elements.
When all settings in one characteristic are processed in the same manner, you can use the following elements:
- characteristic
- nocharacteristic
- characteristic-query
The following list shows the setting elements that are nested below the characteristic element
- parm
- noparm
- parm-query
At present, sending the parm-query and characteristic-query elements over the air is not supported due to the lack of an over-the-air (OTA) response mechanism.
Each Configuration Service Provider lists the Microsoft custom elements that it supports. To gain a broader understanding of how to use the Microsoft custom elements, see the OMA Client Provisioning examples for the various Configuration Service Providers. For more information, see Configuration Service Provider Reference for Windows Mobile Devices.
See Also
Concepts
MSPROV DTD Format
Configuration Service Providers