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

</Item> </Results>

6.2.2 Addressing Interior Node child lists

Interior Node child lists are addressed in the same way as Node values. The list of children is returned as an unordered list of names. The individual names in the list are separated by the character “/”. A returned child list has the format node in the meta information of the result. Note that the “/” character MUST NOT be part of any Node names according to [RFC2396]. Example:

The following Get command:

<Get>

<CmdID>4</CmdID> <Item>

<Target>

<LocURI>Vendor/Ring_signals</LocURI> </Target> </Item> </Get>

could receive a response like this:

<Results>

<CmdRef>4</CmdRef> <CmdID>7</CmdID> <Item> <Meta>

<Format xmlns=’syncml:metinf’>node</Format> <Type xmlns=’syncml:metinf’>text/plain</Type> </Meta>

<Data>Default_ring/Ring1/Ring2/Ring3/Ring4</Data> </Item> </Results>

If a Get command is issued on an Interior Node that does not have any children the client MUST return an empty child list, e.g. <Data/>, and the status code (200) OK.

6.2.3 Permanent and Dynamic Nodes

Nodes in the Management Tree can be either permanent or dynamic.

Permanent Nodes are typically built in at device manufacture. Permanent Nodes can also be temporarily added to a device by, for instance, connecting new accessory hardware. However, a DM Server cannot create or delete permanent Nodes at runtime. An attempt by a DM Server to delete a permanent Node will return status (405) Command not allowed.The same status code will also be returned for all attempts to modify the Name property of a permanent Node.

Dynamic Nodes can be created and deleted at runtime by DM Servers. The Add command is used to create new Nodes. The Delete command is used to delete Dynamic Nodes and all their properties. If a deleted Node has children, i.e. is an Interior Node, the children MUST also be deleted.

The complete layout of the permanent Nodes in the Management Tree is reflected in the device description.

6.2.4 Adding Dynamic Nodes

As stated in the previous section the Add command is used to create new Nodes. The definition of the Add command in [DMPRO] states that the Node addressed MUST NOT exist in the tree. The name of the newly created Node SHALL be the last segment of the URI presented in the Target element of the Add command. Note that devices might have various