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

constraints as to the lengths of the URI used to address the Management Tree. These constraints MUST be recorded in the ./DevDetailManagement Object as specified in [DMSTDOBJ]. Example:

The following Add command:

<Add>

<CmdID>5</CmdID> <Item> <Meta>

<Format xmlns=’syncml:metinf’>b64</Format>

<Type xmlns=’syncml:metinf’>audio/myMelodyType</Type> </Meta> <Target>

<LocURI>Vendor/Ring_signals/My_beep</LocURI> </Target>

<Data>jkhdsfKJhdsf89374h</Data> </Item> </Add>

would create a previously non-existing Node called My_beep as a child Node to the Interior Node Vendor/Ring_signals.

When a Node is created, all the properties that this Node supports are automatically created by the client. Those property values that depend on information present in the Add or Replace command, e.g. Name, are assigned these values. Properties with a default value (e.g. Name) or a value that is automatically updated by the client (e.g. Size) are also assigned appropriate value at Node creation. Other properties will have no value.

Interior Nodes are created in the same way. The difference is that the server MUST explicitly say that the new Node is an Interior Node by including a Meta element with a Format value of node.Example:

<Add>

<CmdID>5</CmdID> <Item>

<Target>

<LocURI>Vendor/Ring_signals/MyOwnSongs</LocURI> </Target> <Meta>

<Format xmlns=’syncml:metinf’>node</Format> </Meta> </Item> </Add>

6.2.5 Protecting Dynamic Nodes

Some Dynamic Nodes can be part of a larger context, and only have meaning in this context. Alternatively, the context (a Management Object) might become useless if a detail is lost, e.g. by the deletion of a dynamic Leaf Node. This could for instance be the address of an SMTP server for an e-mail Management Object. To protect this kind of Node from deletion and thus maintain the integrity of the context, the DDF property AccessTypecan be set so that the Delete command is excluded. This means that a Delete command will fail with status (405) Command not allowed.

Note that this is not the same thing as a permanent Node. A Node protected by the AccessTypeproperty can still be

deleted if it is part of a sub-tree that is being deleted. The Delete command acts strictly on the Node it is addressed at, and if that Node is a dynamic Interior Node it will be deleted along with all its child Nodes. If any of these child Nodes have the AccessTypeproperty set to exclude Delete they will be deleted anyway. The following table summarizes the protection mechanisms for Dynamic Nodes.