7.7.7.1 Leaf objects
The Type property of a leaf object is always the MIME type of the current object value. Allowed types are defined in [AMT]. The entity setting the value MUST supply the type information in the same command that is used to set the value. The Type tag in the Meta information carries the MIME type information for the Item. The property value is represented by a string. An object’s description MAY specify that the object can store more than one MIME type. Consequently, a server that modifies an object’s value MUST supply the MIME type of the data when the object value is set. Example:
The following Add command illustrates how the Type and Format properties are set:
<Add>
<CmdID>4</CmdID> <Item>
<Target>
<LocURI>Vendor/ISP/yyy/GWName</LocURI> </Target> <Meta>
<Format xmlns=’syncml:metinf’>chr</Format> <Type xmlns=’syncml:metinf’>text/plain</Type> </Meta>
<Data>www.yyy.se</Data> </Item> </Add>
7.7.7.2 Interior objects
The Type property of an interior object is represented by a string. The property MAY have no value. When the property does have a value, it MUST represent the Management Object Identifier of the collection of objects rooted at the current object.
The Management Object Identifier SHOULD be a URI. When the Management Object Identifier is registered by the Open Mobile Naming Authority [OMNA], the identifier will most likely be a URN. Some examples are: urn:oma:mo:oma-fumo:1.0, or urn:oma:mo:oma-imps:1.0.
Management Object Identifiers not registered by the Open Mobile Naming Authority MAY use the following reversed domain name scheme:
Reversed Domain Management Object Identifiers
Areversed domain Management Object Identifier is formed by combining the reversed domain name of the owner with the name and version of the object, e.g. “panyx/1.2/ProductY”. The syntax is as follows:
<management_object_name> ::= <reversed-domain>/<major>.<minor>/<name>[/<name>]*
<reversed-domain> ::= “reversed internet domain name”<major> ::= [1-9][0-9]*<minor> ::= 0 | [1-9][0-9]*<name> ::= alphanum
Notes:
1. The reversed domain is as used in some programming languages to name classes uniquely, and MAY include sub-domains, e.g. “panyx.producty” (a fictional example).