OMA-TS-DM_TND-V1_2_1-20080617-A(18)

7.7.1.6 ACL Example

Consider the following Management Tree:

Figure 2: Example Management Tree with ACLs

The following statements about this Management Tree are true:

Any server can Get the value of ./NodeA/Node1,but only ServerC can modify ./NodeA/Node1?prop=ACL in one operation.No server can directly Delete or Replace the value of ./NodeA/Node1.AGet request on ./NodeA/Node1?prop=ACL will return

Get=*.

AGet request on ./NodeB/Node3/Node4?prop=ACL will return no value, e.g.

<Data/>.

AReplace request on ./NodeB/Node3/Node5by ServerA will be successful.

7.7.2 Format

The Format property always maintains information about the data format of the current Node value. Allowed formats are defined in [META].

The entity setting the value MUST supply the format information in the same command that is used to set the value. The format information is carried (in the SyncML message) by the Format tag within the Meta element [META] of the Item that has the data to be set. The property value is represented by a string. See section 7.7.7.1 for an example. Note that Interior Nodes MUST have node as the Format value.

When a Node’s native value is B64-encoded binary, the value b64 is used as the node Format property and a Meta Format [META] value of “b64” MAY be used when sent over DM protocol. When data has a binary form (as indicated by the Mime Type in the Meta Type), and the data is sent over XML, then the Meta Format MUST be b64. The recipient of this data