7.3 Property addressing
The properties of a Node are addressed by appending ?prop=<property_name>to the Node’s URI. For instance, to access the ACL of an OMA DM account a DM Server could use one of these URIs;
./DMAcc/xyzInc?prop=ACLDMAcc/xyzInc?prop=ACL
If a server addresses an unsupported property in a device, an error is returned in the form of an (406) Optional feature not supportedstatus
7.4 Property values
Property values MUST be transported by OMA DM as UTF-8 encoded strings. Numerical property values MUST be converted to numerical strings, expressed in decimal. It is NOT RECOMMENDED to use a <Meta> element for property values.
It is unnecessary to use a <Meta> element for property values because they are all strings. This means that they would all have the same <Meta>, like this:
<Meta>
<Format xmlns=’syncml:metinf’>chr</Format> <Type xmlns=’syncml:metinf’>text/plain</Type> </Meta>
7.5 Operations on properties
The following table defines the allowed operations for each property. An operation on a property is equivalent to an OMA DM command that is performed by a server on the URI of the property. Property ACL
Applicable Commands Get, Replace
Comment
Get and Replace are the only valid commands for ACL manipulation. Note that Replace always replaces the complete ACL.
Automatically updated by Add and Replace commands on the associated Node.
A Replace is equivalent to a rename of the Node. Automatically updated by the device.
Only updated by server actions or software version changes.
Automatically updated by the device. Automatically updated by Add and Replace commands on the associated Leaf Node. Automatically updated by the device.
Format Name Size Title TStamp Type VerNo
Get Get, Replace Get Get, Replace Get Get Get
Table 4: Allowed operations on properties
Properties do not support the Add command. All mandatory properties, and those optional properties that a device
implements, MUST be automatically created when a new Node is created. The values of the newly created Node properties