8.5 Device Description Framework 设备描述框架

8.5.1 Rationale for a Device Description Framework 设备描述框架的原理

In an ideal world all devices would display the same structure and behavior to a management system. But since different vendors are competing with each other on the market for various kinds of devices, it seems very unlikely that this would ever happen. But management systems still need to understand each individual device even though they do appear to have different internal structures and behaviors.
在理想的世界中，所有设备将向管理系统显示相同的结构和行为。 但是，由于不同的供应商在市场上与各种设备相互竞争，看起来不太可能发生这种情况。 但是管理系统仍然需要理解每个单独的设备，即使它们看起来具有不同的内部结构和行为。

To address this issue the concept of a device description framework is introduced. In short this framework prescribes a way for device vendors to describe their devices so that a management system can understand how to manage the device. The following figure illustrates the principle.
为了解决这个问题，引入了设备描述框架的概念。简而言之，该框架规定了设备供应商描述他们的设备的方式，使得管理系统可以理解如何管理设备。下图说明了原理。

By using a description framework we also make sure that the total management system based on OMA DM is flexible and easily extendible. And that it can accommodate not only the demands we put on it today but also the ones we might have tomorrow. We also avoid a situation where all future management needs would have to be standardized before they could be used in devices to simplify the use of these devices.
通过使用描述框架，我们还确保基于OMA DM的总管理系统是灵活的并且易于扩展。它不仅能适应我们今天提出的要求，而且能适应我们明天可能提出的要求。我们还避免了一种情况，即所有未来的管理需求必须标准化，然后才能用于设备，以简化这些设备的使用。

It is important to note that the description framework needs to co-exist with the existing standardized Management Objects, and that the borderline between the standardized Management Objects and Management Objects described by the framework will change over time. This will mainly happen when a standards body decides to create specifications on how their technology should be managed. It is in the interest of the OMA Device Management committee to encourage and support such initiatives from standard bodies active in wireless standardization, so that the set of standardized Management Objects increases.
重要的是要注意，描述框架需要与现有的标准化管理对象共存，并且框架所描述的标准化管理对象和管理对象之间的边界将随时间而改变。这将主要发生在标准机构决定创建关于如何管理其技术的规范时。符合OMA设备管理委员会的利益的是鼓励和支持活跃于无线标准化的标准机构的这些举措，以便增加标准化管理对象的集合。

8.5.2 The OMA DM Device Description Framework OMA DM设备描述框架

Today there exist a number of different description frameworks, but none of these seem to suit the purposes of OMA DM. There are also activities in other standards bodies that aim to develop new frameworks specifically for the wireless industry. With this in mind, OMA DM does currently not specify the use of any particular framework.
今天，存在许多不同的描述框架，但是这些框架似乎都不符合OMA DM的目的。其他标准机构也还有活动，旨在为无线行业开发新的框架。考虑到这一点，OMA DM目前没有规定使用任何特定的框架。

However, the need for a description framework remains and therefore OMA DM RECOMMEND using the following simple framework as an interim solution. This proposed description framework is defined by an XML DTD. Descriptions of Management Objects, or complete Management Trees, are valid XML documents. Device manufactures using the description framework MUST make the device descriptions available to DM Servers. The mechanism for this is currently not being standardized.
然而，描述框架是仍然需要的，因此OMA DM推荐使用以下简单框架作为临时解决方案。提出的这个描述框架由XML DTD定义。管理对象或完整管理树的描述是有效的XML文档。使用描述框架的设备制造商必须使设备描述可用于DM服务器。 其机制目前尚未标准化。

The OMA DM Device Description Framework DTD is defined in [DMDDFDTD].
OMA DM设备描述框架DTD在[DMDDFDTD]中定义。

8.5.3 XML usage XML用法

The OMA DM DDF information XML documents are specified using well-formed XML. However, they MAY not be valid XML. That is, they do not need to specify the XML prolog. They only need to specify properly identified name space element types from the OMA DM DDF information DTD. This restriction allows for the OMA DM DDF information to be specified with greater terseness than would be possible if a well-formed, valid XML document was REQUIRED.
使用格式良好的XML指定OMA DM DDF信息XML文档。但是，它们可能不是有效的XML。也就是说，他们不需要指定XML序言。他们只需要从OMA DM DDF信息DTD中指定正确标识的名称空间元素类型。这种限制允许以比如果需要格式良好的有效XML文档的情况下可能更严格地来指定OMA DM DDF信息。

This DTD makes heavy use of XML name spaces. Name spaces MUST be declared on the first element type that uses an element type from the name space.
此DTD大量使用XML名称空间。名称空间必须在使用名称空间中的元素类型的第一个元素类型上声明。

Names in XML are case sensitive. The element types in the OMA DM DDF information DTD are defined in [DMDDFDTD] or the URN syncml:dmddf.
XML中的名称区分大小写。OMA DM DDF信息DTD中的元素类型在[DMDDFDTD]或URN syncml：dmddf中定义。

OMA DM also makes use of XML standard attributes, such as xml:lang. Any XML standard attribute can be used in a XML document conforming to this DTD.
OMA DM还使用XML标准属性，如xml：lang。任何XML标准属性都可以在符合此DTD的XML文档中使用。

8.5.4 Framework Elements 框架元素

This section explains the elements used in the description framework DTD.
本节介绍在描述框架DTD中使用的元素。

8.5.4.1 Structural elements 结构元素

These elements provide various kinds of structural information of the described Management Object.
这些元素提供所描述的管理对象的各种结构信息。

8.5.4.1.1 MgmtTree

Usage: Container for one or more described Management Objects.
用法：一个或多个描述的管理对象的容器。

Parent Elements: none
父元素：无

Restrictions: This MUST be the root element of all descriptions.
限制：这必须是所有描述的根元素。

Content Model:(VerDTD, Man?, Mod?, Node+)
内容模型：(VerDTD, Man?, Mod?, Node+)

8.5.4.1.2 VerDTD

Usage: Specifies the major and minor version identifier of the OMA DM Description Framework specification used to represent the OMA DM description.
用法：指定用于表示OMA DM描述的OMA DM描述框架规范的主要和次要版本标识符。

Parent Elements: MgmtTree
父元素：MgmtTree

Restrictions: Major revisions of the specification create incompatible changes that will generally require a new parser. Minor revisions involve changes that do not impact basic compatibility of the parser. When the XML document conforms to this revision of the OMA DM Device Description Framework the value MUST be 1.2. The element type MUST be included in the MgmtTree.
限制：规范的主要修订版创建不兼容的更改，这通常需要一个新的解析器。 次要修订涉及不影响解析器的基本兼容性的更改。当XML文档符合OMA DM设备描述框架的此版本时，值必须为1.2。元素类型必须包含在MgmtTree中。

Content Model: (#PCDATA)
内容模型：(#PCDATA)

8.5.4.1.3 Man

Usage: Specifies the manufacturer of the device.
用法：指定设备的制造商

Parent Elements: MgmtTree
父元素：MgmtTree

Restrictions: This element is OPTIONAL.
限制：此元素是可选的。

Content Model: (#PCDATA)
内容模型：(#PCDATA)

8.5.4.1.4 Mod

Usage: Specifies the model number of the device.
用法：指定设备的型号。

Parent Elements: MgmtTree
父元素：MgmtTree

Restrictions: This element is OPTIONAL.
限制：此元素是可选的。

Content Model: (#PCDATA)
内容模型：(#PCDATA)

8.5.4.1.5 Node

Usage: Specifies a Node.
用法：指定一个节点。

Parent Elements: MgmtTree
父元素：MgmtTree

Restrictions: This element is recursive. A Node with a Value element MUST always terminate the recursion. It is possible for a Node to omit both the next recursive Node and a Value, this means that the hierarchy of Nodes continues elsewhere. This can be used to increase readability of very deep trees. In the continuation, the Path element MUST contain a full URI that specifies the insertion point in the tree.
限制：此元素是递归的。具有Value元素的节点必须始终终止递归。节点可以省略下一个递归节点和值，这意味着节点的层次结构在其他地方继续。这可以用于增加非常深的树的可读性。在继续中，Path元素必须包含指定树中插入点的完整URI。

ContentModel:(NodeName, Path?, RTProperties?, DFProperties?, (Node*|Value?))
内容模型：(NodeName, Path?, RTProperties?, DFProperties?, (Node*|Value?))

Example: The following XML is a description of a number of Nodes that form the URI Vendor/ISP/GWInfo/GWName. Note that all the details of DFProperties are deliberately left out.
示例：以下XML是形成URI Vendor/ISP/GWInfo/GWName的多个节点的描述。请注意，DFProperties的所有详细信息都会被故意忽略。

<MgmtTree>
  <Node>
    <NodeName>Vendor</NodeName>
     <DFProperties>...</DFProperties>
     <Node>
       <NodeName>ISP</NodeName>
       <DFProperties>...</DFProperties>
       <Node>
        <NodeName>GWInfo</NodeName>
        <DFProperties>...</DFProperties>
        <Node>
          <NodeName>GWName</NodeName>
          <DFProperties>...</DFProperties>
          <Value>gw.yyy.se</Value>
        </Node>
      </Node>
     </Node>
  </Node>
</MgmtTree>

8.5.4.1.6 NodeName

Usage: Specifies the name of the described Node.
用法：指定描述的节点的名称。

Parent Elements: Node
父元素：Node

Restrictions: See [RFC2396] for general restrictions on URI. The NodeName element MAY be empty. If empty, this means that the name of the Node MUST be assigned when the Node is created. When the Node name is assigned at Node creation time, the value for the name is set to the last segment of the URI specified as Target for the command that results in the Node being created. See also section 8.4.7.3.
限制：有关URI的一般限制，请参阅[RFC2396]。NodeName元素可以为空。如果为空，这意味着在创建节点时必须分配节点的名称。当节点名称在节点创建时分配时，名称的值将设置为指定为目标的URI的最后一个段，用于创建节点的命令。参见8.4.7.3节。

Content Model: (#PCDATA) 内容模型：(#PCDATA)

8.5.4.1.7 Path

Usage: Specifies the URI up to, but not including, the described Node.
用法：指定URI，但不包括描述的节点。

Parent Elements: Node
父元素：Node

Restrictions: OPTIONAL element. If omitted, the URI for the Node MUST be constructed by concatenating all ancestral NodeName and Path values. This concatenated value MUST form the correct URI. Path SHOULD only be used inside Node elements that are child elements to the MgmtTree element. For general restrictions, see [RFC2396].
限制：可选元素。如果省略，则节点的URI必须通过连接所有祖先NodeName和Path值来构造。这个连接的值必须形成正确的URI。路径应该只在作为MgmtTree元素的子元素的Node元素中使用。有关一般限制，请参见[RFC2396]。

Content Model: (#PCDATA)
内容模型：(#PCDATA)

Example: The following XML is an alternative way to describe the same Management Objects as in the example in section 8.5.4.1.5. This description specifies the same URI as the other example: Vendor/ISP/GWInfo/GWName. Note that all the details of DFProperties are deliberately left out.
示例：以下XML是描述与第8.5.4.1.5节中的示例相同的管理对象的另一种方法。此描述指定与另一个示例相同的URI：Vendor/ISP/GWInfo/GWName。 请注意，DFProperties的所有详细信息都会被故意忽略。

<MgmtTree>
  <Node>
    <NodeName>Vendor</NodeName>
    <DFProperties>...</DFProperties>
  </Node>
  <Node>
    <NodeName>ISP</NodeName>
    <Path>Vendor</Path>
    <DFProperties>...</DFProperties>
  </Node>
  <Node>
    <NodeName>GWInfo</NodeName>
    <Path>Vendor/ISP</Path>
    <DFProperties>...</DFProperties>
  </Node>
  <Node>
    <NodeName>GWName</NodeName>
    <Path>Vendor/ISP/GWInfo</Path>
    <DFProperties>...</DFProperties>
    <Value>gw.yyy.se</Value>
  </Node>
</MgmtTree>

8.5.4.1.8 Value

Usage: Specifies a default value for Nodes that are instantiated using the current description.
用法：指定使用当前描述实例化的节点的默认值。

Parent Elements: Node
父元素：Node

Restrictions: OPTIONAL element. If omitted, the Node description does not specify any default value for the Node. In this case the initial value of new Nodes are undefined.
限制：可选元素。如果省略，节点描述不会为节点指定任何默认值。在这种情况下，新节点的初始值是未定义的。

8.5.4.1.9 RTProperties

Usage: Aggregating element for run-time properties, i.e. properties that the Nodes have in a device at run-time. Used to specify which properties the described Node supports at run-time. Can also be used to supply default values for supported run-time properties.
用法：聚合运行时属性的元素，即节点在运行时在设备中具有的属性。用于指定所描述的节点在运行时支持的属性。也可以用于为支持的运行时属性提供默认值。

Parent Elements: Node
父元素：Node

Restrictions: OPTIONAL element. If omitted, the Node MUST only support the mandatory run-time properties ACL, Format, Name and Type. If any optional properties are supported, they MUST be specified by using this element.
限制：可选元素。如果省略，节点必须只支持强制运行时属性ACL，格式，名称和类型。如果支持任何可选属性，则必须使用此元素指定它们。

Content Model: (ACL?, Format?, Name?, Size?, Title?, TStamp?, Type, VerNo?)
内容模型：（ACL？，Format？，Name？，Size？，Title？，TStamp？，Type，VerNo？）

8.5.4.1.10 DFProperties

Usage: Aggregating element for description framework properties, i.e. properties that Nodes have in the description framework and that are not explicitly present at run-time.
用法：聚合描述框架属性的元素，即节点在描述中具有的属性框架，并且没有在运行时显式存在。

Parent Elements: Node
父元素：Node

Restrictions: This is a REQUIRED element.
限制：这是一个必须元素。

Content Model:(AccessType, DefaultValue?, Description?, DFFormat, Occurrence?, Scope?, DFTitle?, DFType, CaseSense?)
内容模型：（AccessType，DefaultValue ?, Description？，DFFormat，Occurrence？，Scope，DFTitle，DFType，CaseSense？）

8.5.4.2 Run-time property elements 运行时属性元素

The usage of the run-time properties in the description framework reflects the mandatory/optional status of the corresponding run-time property. These elements can also be used to describe default values for the supported properties. Since these properties can change at run-time, the values of these properties in the description and in a real device will differ.
在描述框架中运行时属性的使用反映了相应运行时属性的强制/可选状态。这些元素也可用于描述支持的属性的默认值。由于这些属性在运行时可能会更改，因此这些属性在描述中和实际设备中的值会有所不同。

The RTProperties element,which encapsulates the run-time properties,is OPTIONAL within its parent element Node. The purpose of this is to make it possible to omit the RTProperties element if only the mandatory propertiesare supported and there is no need to specify any default values.If the RTProperties element is used in a description,all the mandatory run-time properties MUST be specified.
RTProperties元素（封装运行时属性）在其父元素Node中是可选的。这样做的目的是如果只支持强制属性，则RTProperties元素可以省略，并且不需要指定任何默认值。如果在描述中使用RTProperties元素，则所有强制运行时属性必须被指定。

8.5.4.2.1 ACL

Usage: Specifies support for the ACL property. MAY be used to specify a default value for the property.
用法：指定对ACL属性的支持。可用于指定属性的默认值。

Parent Elements: RTProperties
父元素：RTProperties

Restrictions: If a value is specified it MUST be formatted according to section 8.3.7.1.5.
限制：如果指定了值，则必须根据8.5.7.1.5节进行格式化。

Content Model: (#PCDATA)
内容模型：(#PCDATA)

8.5.4.2.2 Format

Usage: Specifies support for the Format property. MAY be used to specify a default value for the property.
用法：指定对Format属性的支持。 可用于指定属性的默认值。

Parent Elements: RTProperties 父元素：RTProperties

Restrictions: If a default value is specified for the described Node, the Format property MUST specify the correct format of the Node value.
限制：如果为描述的节点指定了默认值，则Format属性必须指定Node值的正确格式。

Content Model: (b64 | bin | bool | chr | int | node | null | xml | date |time |float)
内容模型：（b64 | bin | bool | chr | int | node | null | xml | date | time | float）

8.5.4.2.3 Name

Usage: Specifies support for the Name property. MAY be used to specify a default value for the property.
用法：指定对Name属性的支持。可用于指定属性的默认值。

Parent Elements: RTProperties
父元素：RTProperties

Restrictions: See [RFC2396]. If a default property value is specified, it SHOULD be the same as the value of the NodeName element.
限制：参见[RFC2396]。如果指定了默认属性值，则它应该与NodeName的值相同。

Content Model: (#PCDATA)
内容模型：(#PCDATA)

8.5.4.2.4 Size

Usage: Specifies support for the Size property. MAY be used to specify a default value for the property. Within its parent element, the Size element is defined as optional. Size MUST NOT be used for Interior Nodes. In Node elements describing Leaf Nodes the Size element MAY be used within RTProperties.
用法：指定对Size属性的支持。可用于指定属性的默认值。在其父元素中，Size元素被定义为可选。 Size不能用于内部节点。在描述叶节点的节点元素中，可以在RTProperties中使用Size元素。

Parent Elements: RTProperties
父元素：RTProperties

Restrictions: If a value is specified it MUST be formatted according to section 8.3.4.
限制：如果指定了值，则必须根据第8.3.4节进行格式化。

Content Model: (#PCDATA)
内容模型：(#PCDATA)

8.5.4.2.5 Title

Usage: Specifies support for the Title property. MAY be used to specify a default value for the property.
用法：指定对Title属性的支持。可用于指定属性的默认值。

Parent Elements: RTProperties
父元素：RTProperties

Restrictions: If a value is specified it MUST be formatted according to section 8.3.4.
限制：如果指定了值，则必须根据第8.3.4节进行格式化。

Content Model: (#PCDATA)
内容模型：(#PCDATA)

8.5.4.2.6 TStamp

Usage: Specifies support for the TStamp property. MAY be used to specify a default value for the property.
用法：指定对TStamp属性的支持。可用于指定属性的默认值。

Parent Elements: RTProperties
父元素：RTProperties

Restrictions: If a value is specified it MUST be formatted according to section 8.3.4.
限制：如果指定了值，则必须根据第8.3.4节进行格式化。

Content Model: (#PCDATA)
内容模型：（#PCDATA）

8.5.4.2.7 Type

Usage: Specifies support for the Type property. MAY be used to specify a default value for the property.
用法：指定对Type属性的支持。可用于指定属性的默认值。

Parent Elements: RTProperties
父元素：RTProperties

Restrictions: For Leaf Nodes, if a default value is specified for the described Node, the Type property MUST be used to specify the correct MIME type of the Node’s present value using a single MIME element. For Interior Nodes a DDFName element MUST be present and specify a valid Management Object identifier, which MAY be empty.
限制：对于叶节点，如果为描述的节点指定了默认值，则必须使用Type属性来使用单个MIME元素指定节点的当前值的正确MIME类型。对于内部节点，一个DDFName元素必须存在，并指定一个有效的管理对象标识符，它可以是空的。

Content Model:(MIME | DDFName) 内容模型：(MIME | DDFName)

8.5.4.2.8 VerNo

Usage: Specifies support for the VerNo property. MAY be used to specify a default value for the property.
用法：指定对VerNo属性的支持。可用于指定属性的默认值。

Parent Elements: RTProperties
父元素：RTProperties

Restrictions: If a value is specified it MUST be formatted according to section 8.3.4.
限制：如果指定了值，则必须根据第8.3.4节进行格式化。

Content Model: (#PCDATA)
内容模型：（#PCDATA）

8.5.4.2.9 b64

Usage: OMA DM format description. Specifies that the Node value is Base64 encoded.
用法：OMA DM格式描述。指定Node值为Base64编码。

Parent Elements:Format, DFFormat 父元素：Format, DFFormat

Restrictions: None. 限制：无

Content Model: EMPTY 内容模型：EMPTY

8.5.4.2.10 bin

Usage: OMA DM format description. Specifies that the Node value is binary data.
用法：OMA DM格式描述。指定Node值是二进制数据。

ParentElements:Format, DFFormat
父元素：Format, DFFormat

Restrictions: None.
限制：无

Content Model: EMPTY 内容模型：EMPTY

8.5.4.2.11 bool

Usage: OMA DM format description. Specifies that the Node value is a Boolean.
用法：OMA DM格式描述。指定Node值是布尔值。

Parent Elements:Format, DFFormat
父元素：Format, DFFormat

Restrictions: None.
限制：无。

Content Model: EMPTY 内容模型：EMPTY

8.5.4.2.11 bool

Usage: OMA DM format description. Specifies that the Node value is a Boolean.
用法：OMA DM格式描述。 指定Node值是布尔值。

Parent Elements:Format, DFFormat
父元素：Format, DFFormat

Restrictions: None.
限制：无。

Content Model: EMPTY
内容模型：EMPTY

8.5.4.2.12 chr

Usage: OMA DM format description. Specifies that the Node value is text.
用法：OMA DM格式描述。 指定Node值为文本。

Parent Elements:Format, DFFormat
父元素：Format, DFFormat

Restrictions: The character set used is specified either by the transport protocol, MIME content type header or XML prologue.
限制：使用的字符集由传输协议，MIME内容类型标头或XML序列指定。

Content Model: EMPTY
内容模型：EMPTY

8.5.4.2.13 int

Usage: OMA DM format description. Specifies that the Node value is a 32-bit signed integer.
用法：OMA DM格式描述。指定Node值是32位有符号整数。

Parent Elements:Format, DFFormat 父元素：Format, DFFormat

Restrictions: None.
限制：无

Content Model: EMPTY
内容模型：EMPTY

8.5.4.2.14 node

Usage: OMA DM format description. Specifies that the Node is an Interior Node.
用法：OMA DM格式描述。指定节点是内部节点。

Parent Elements:Format, DFFormat
父元素：Format, DFFormat

Restrictions: This Format MUST only be used for Interior Nodes.
限制：此格式必须只用于内部节点。

Content Model: EMPTY
内容模型：EMPTY

8.5.4.2.15 null

Usage: OMA DM format description. Specifies that the Node value is null.
用法：OMA DM格式描述。指定Node值为null。

Parent Elements:Format, DFFormat
父元素：Format, DFFormat

Restrictions: None.
限制：无

Content Model: EMPTY
内容模型：EMPTY

8.5.4.2.16 xml

Usage: OMA DM format description. Specifies that the Node value is XML data.
用法：OMA DM格式描述。 指定Node值是XML数据。

ParentElements:Format, DFFormat
父元素：Format, DFFormat

Restrictions: None.
限制：无

Content Model: EMPTY
内容模型：EMPTY

8.5.4.2.17 date

Usage: OMA DM format description. Specifies that the Node value is a date in ISO 8601 format with the century being included in the year [ISO8601].
用法：OMA DM格式描述。指定Node值是ISO 8601格式的日期，其中包括年份[ISO8601]中的世纪。

ParentElements:Format, DFFormat
父元素：Format, DFFormat

Restrictions: None.
限制：无

Content Model: EMPTY
内容模型：EMPTY

8.5.4.2.18 time

Usage: OMA DM format description. Specifies that the Node value is a time in ISO 8601 format [ISO8601].
用法：OMA DM格式描述。指定Node值是ISO 8601格式[ISO8601]中的时间。

Parent Elements:Format, DFFormat
父元素：Format, DFFormat

Restrictions: None.
限制：无

Content Model: EMPTY
内容模型：EMPTY

8.5.4.2.19 float

Usage: OMA DM format description. Specifies that the Node value is a real number corresponding to a single precision 32 bit floating point type as defined in XML Schema 1.0 as the float primitive type [XMLSCHEMADT].
用法：OMA DM格式描述。指定Node值是与XML模式1.0中定义的浮点型类型[XMLSCHEMADT]对应的单精度32位浮点类型的实数。

Parent Elements:Format, DFFormat
父元素：Format, DFFormat

Restrictions: None.
限制：无

Content Model: EMPTY
内容模型：EMPTY

8.5.4.2.20 MIME

Usage: Specifies the MIME type of the current Node value.
用法：指定当前Node值的MIME类型。

Parent Elements:Type, DFType
父元素：Type, DFType

Restrictions: MUST only contain valid MIME type identifiers. See [META].
限制：必须只包含有效的MIME类型标识符。参见[META]。

Content Model: (#PCDATA)
内容模型：(#PCDATA)

8.5.4.2.21 DDFName

Usage: Specifies the Management Object Identifier of the Management Object rooted at this Node, or is empty. 用法：指定以此节点为根的管理对象的管理对象标识符，或为空。

Parent Elements:Type, DFType 父元素：Type, DFType

Restrictions: MUST only contain a valid Management Object Identifier or be empty. See 8.3.7.7.2. 限制：务必只包含有效的管理对象标识符或为空。见8.3.7.7.2。

Content Model: (#PCDATA) 内容模型：(#PCDATA)

8.5.4.3 Framework property elements 框架属性元素

The properties that described Nodes have in the description framework are specified with framework property elements. These are not the same as the run-time properties of an instantiated Node in a device. These properties express other information about Nodes that DM Servers might need. The framework properties MUST NOT change at run-time since such a change might introduce discrepancies between the run-time Node and the corresponding description. The following table defines the framework Node properties.
描述框架中描述节点的属性是使用框架属性元素指定的。这些与设备中实例化的节点的运行时属性不同。这些属性表示有关DM服务器可能需要的节点的其他信息。框架属性在运行时不能改变，因为这样的改变可能引入运行时节点和相应描述之间的差异。下表定义了框架的节点属性。

Element/Property 元素／属性 Explanation 解释 Usage 用法
AccessType Specifies which commands are allowed on the Node.
指定节点上允许哪些命令。		 MUST 必须
DefaultValue The Node value used in a device unless specifically set to a different value.
在设备中使用的节点值，除非特别设置为不同的值。		 MAY 可选
Description The human readable description of the Node.
节点的人可读的描述。		 MAY 可选
DFFormat The data format of the described Node.
所描述的节点的数据格式。		 MUST 必须
Occurrence Specifies the number of instances that MAY occur of the Node.
指定可能发生的节点的实例数。		 MAY 可选
Scope Specifies whether this is a permanent or Dynamic Node.
指定这是永久还是动态节点。		 MAY 可选
DFTitle The human readable name of the Node.
节点的人可读名称。		 MAY 可选
DFType For Leaf Nodes, the MIME type of the Node value. For Interior Nodes, a Management Object Identifier or empty.
对于叶节点，节点值的MIME类型。对于内部节点，管理对象标识符或空。		 MUST 必须
CaseSense Specifies whether the Node name and names of descendant Nodes in the tree below should be treated as case sensitive or case insensitive.
指定节点名称和下面树中的后代节点的名称是否应被视为区分大小写或不区分大小写。		 MAY 可选

8.5.4.3.1 AccessType

Usage: Specifies which commands are supported for the described Node. This property is independent of the ACL run-time property.
用法：指定对所描述的节点支持哪些命令。此属性独立于ACL运行时属性。

Parent Elements: DFProperties
父元素：DFProperties

Restrictions: The value of this property MUST be an unordered list of the valid OMA DM commands.
限制：此属性的值必须是有效的OMA DM命令的无序列表。

Content Model: (Add?, Copy?, Delete?, Exec?, Get?, Replace?)
内容模型：(Add?, Copy?, Delete?, Exec?, Get?, Replace?)

8.5.4.3.2 DefaultValue

Usage: Specifies the “factory default” value of the Node, if such a value exists.
用法：如果存在此值，则指定节点的“出厂默认值”值。

Parent Elements: DFProperties
父元素：DFProperties

Restrictions: The MIME type of the value MUST correspond with the MIME type specified by the DFType property.
限制：值的MIME类型必须与DFType属性指定的MIME类型相对应。

Content Model: (#PCDATA)
内容模型：(#PCDATA)

8.5.4.3.3 Description

Usage: A human readable description of the described Node. This is used to convey any relevant information regarding the Node that is not explicitly given by the other properties.
用法：对所描述的节点的人可读的描述。这用于传达关于未由其他属性明确给出的关于节点的任何相关信息。

Parent Elements: DFProperties
父元素：DFProperties

Restrictions: Descriptions SHOULD be kept as short as possible.
限制：说明应尽可能短。

Content Model: (#PCDATA)
内容模型：(#PCDATA)

8.5.4.3.4 DFFormat

Usage: Specifies the data format of the described Node.
用法：指定描述的节点的数据格式。

Parent Elements: DFProperties
父元素：DFProperties

Restrictions: For Interior Nodes the Format MUST be node.
限制：对于内部节点，格式必须为节点。

ContentModel:(b64 | bin | bool | chr | int | node | null | xml | date | time | float)
内容模型：(b64 | bin | bool | chr | int | node | null | xml | date | time | float)

8.5.4.3.5 Occurrence

Usage: Specifies the potential number of instances that MAY occur of the described Node.
用法：指定所描述的节点可能发生的实例的可能数量。

Parent Elements: DFProperties
父元素：DFProperties

Restrictions: If the property is omitted the Node occurrence is exactly one.
限制：如果省略属性，则节点出现正好一次。

Content Model:(One | ZeroOrOne | ZeroOrMore | OneOrMore | ZeroOrN | OneOrN)
内容模型：(One | ZeroOrOne | ZeroOrMore | OneOrMore | ZeroOrN | OneOrN)

8.5.4.3.6 Scope

Usage: Specifies whether the described Node is Permanent or Dynamic.
用法：指定描述的节点是永久还是动态。

Parent Elements: DFProperties
父元素：DFProperties

Restrictions: The value is indicated by the tags Permanent and Dynamic in the description framework. This property is OPTIONAL, if omitted the described Node is Dynamic.
限制：值由描述框架中的“永久”和“动态”标签指示。如果省略所描述的节点是动态的则此属性是可选的。

ContentModel: (Permanent | Dynamic)
内容模型：(Permanent | Dynamic)

8.5.4.3.7 DFTitle

Usage: A human readable name for the Node description.
用法：节点描述的可读名称。

Parent Elements: DFProperties
父元素：DFProperties

Restrictions: Titles SHOULD be kept as short and informative as possible.
限制：标题应尽可能短，内容丰富。

Content Model: (#PCDATA) 内容模型：(#PCDATA)

8.5.4.3.8 DFType

Usage: For Leaf Nodes, one or more elements specify the MIME types the described Node supports. For Interior Nodes, a single MIME element MUST specify be present and specify a valid Management Object Identifier, which MAY be empty.
用法：对于叶节点，一个或多个元素指定所描述的节点支持的MIME类型。对于内部节点，单个MIME元素必须指定存在，并且指定有效的管理对象标识符，它可以是空的。

Parent Elements: DFProperties
父元素：DFProperties

Restrictions: Note that a Leaf Node can support multiple MIME types, e.g. a ring signal Node might support both audio/mpeg and audio/MP4-LATM. The values of the DFType property MUST be registered MIME types.
限制：注意，叶节点可以支持多种MIME类型，例如。 环形信号节点可能支持音频/ mpeg 和音频/ MP4-LATM。 DFType属性的值必须是注册的MIME类型。

ContentModel: (MIME+ | DDFName) 内容模型：(MIME+ | DDFName)

8.5.4.3.9 Add

Usage: Specifies support for the OMA DM Add command.
用法：指定对OMA DM Add命令的支持。

Parent Elements: AccessType 父元素：AccessType

Restrictions: None.
限制：无

Content Model: EMPTY
内容模型：EMPTY

8.5.4.3.10 Copy

Usage: Specifies support for the OMA DM Copy command.
用法：指定对OMA DM Copy命令的支持。

Parent Elements: AccessType
父元素：AccessType

Restrictions: None.
限制：无

Content Model: EMPTY
内容模型：EMPTY

8.5.4.3.11 Delete

Usage: Specifies support for the OMA DM Delete command.
用法：指定对OMA DM Delete命令的支持。

Parent Elements: AccessType
父元素：AccessType

Restrictions: None.
限制：无

Content Model: EMPTY
内容模型：EMPTY

8.5.4.3.12 Exec

Usage: Specifies support for the OMA DM Exec command.
用法：指定对OMA DM Exec命令的支持。

Parent Elements: AccessType
父元素：AccessType

Restrictions: None.
限制：无

Content Model: EMPTY
内容模型：EMPTY

8.5.4.3.13 Get

Usage: Specifies support for the OMA DM Get command.
用法：指定对OMA DM Get命令的支持。

Parent Elements: AccessType
父元素：AccessType

Restrictions: None.
限制：无

Content Model: EMPTY
内容模型：EMPTY

8.5.4.3.14 Replace

Usage: Specifies support for the OMA DM Replace command.
用法：指定对OMA DM Replace命令的支持。

Parent Elements: AccessType
父元素：AccessType

Restrictions: None.
限制：无

Content Model: EMPTY
内容模型：EMPTY

8.5.4.3.15 One

Usage: Specifies that the described Node can occur exactly one (1) time.
用法：指定所描述的节点可以正好出现一（1）次。

Parent Elements: Occurrence
父元素：Occurrence

Restrictions: None.
限制：无

Content Model: EMPTY
内容模型：EMPTY

8.5.4.3.16 ZeroOrOne

Usage: Specifies that the described Node can occur either one (1) time or not at all.
用法：指定描述的节点可以发生一（1）次，也可以不发生。

Parent Elements: Occurrence
父元素：Occurrence

Restrictions: None.
限制：无

Content Model: EMPTY
内容模型：EMPTY

8.5.4.3.17 ZeroOrMore

Usage: Specifies that the described Node can occur an unspecified number of times, or not occur at all.
用法：指定描述的节点可能发生未指定的次数，或根本不发生。

Parent Elements: Occurrence
父元素：Occurrence

Restrictions: None.
限制：无

Content Model: EMPTY
内容模型：EMPTY

8.5.4.3.18 ZeroOrN

Usage: Specifies that the described Node can occur any number times up to N times, or not occur at all.
用法：指定描述的节点可以发生任意N次，或根本不发生。

Parent Elements: Occurrence
父元素：Occurrence

Restrictions: N MUST be specified as a character string representing a positive integer value between 2 and 65536.
限制：N必须指定为表示介于2和65536之间的正整数值的字符串。

Content Model: (#PCDATA)
内容模型：(#PCDATA)

8.5.4.3.19 OneOrMore

Usage: Specifies that the described Node can occur an unspecified number of times, but MUST occur at least once.
用法：指定描述的节点可能发生未指定的次数，但务必发生至少一次。

Parent Elements: Occurrence
父元素：Occurrence

Restrictions: None.
限制：无

Content Model: EMPTY
内容模型：EMPTY

8.5.4.3.20 OneOrN

Usage: Specifies that the described Node can occur any number times up to N times but MUST occur at least once.
用法：指定描述的节点可以发生任意次数，最多N次，但必须至少发生一次。

Parent Elements: Occurrence
父元素：Occurrence

Restrictions: N MUST be specified as a character string representing a positive integer value between 2 and 65536.
限制：N必须指定为表示介于2和65536之间的正整数值的字符串。

Content Model: (#PCDATA)
内容模型：(#PCDATA)

8.5.4.3.21 Dynamic

Usage: Specifies that the described Node is Dynamic.
用法：指定描述的节点是动态的。

Parent Elements: Scope
父元素：Scope

Restrictions: None.
限制：无

Content Model: EMPTY
内容模型：EMPTY

8.5.4.3.22 Permanent

Usage: Specifies that the described Node is Permanent.
用法：指定描述的节点为永久。

Parent Elements: Scope
父元素：Scope

Restrictions: None.
限制：无

Content Model: EMPTY
内容模型：EMPTY

8.5.4.3.23 CaseSense

Usage: Specifies whether the Node name and names of descendant Nodes in the tree below SHOULD be treated as case sensitive or case insensitive.
用法：指定节点名称和下面树中的后代节点的名称是否应被视为区分大小写或不区分大小写。

Parent Elements: DFProperties
父元素：DFProperties

Restrictions: MUST only contain value CS or CIS.
限制：必须只包含值CS或CIS。

ContentModel:(CS | CIS)
内容模型：(CS | CIS)

8.5.4.3.24 CS

Usage: Case sensitivity declaration. Specifies that child Node names MUST be treated as case sensitive.
用法：区分大小写。指定子节点名称必须被视为区分大小写。

Parent Elements: CaseSense
父元素：CaseSense

Restrictions: None.
限制：无

Content Model: EMPTY
内容模型：EMPTY

8.5.4.3.24 CIS

Usage: Case insensitivity declaration. Specifies that child Node names MUST be treated as case insensitive.
用法：不区分大小写声明。指定子节点名称必须被视为不区分大小写。

Parent Elements: CaseSense
父元素：CaseSense

Restrictions: None.
限制：无

Content Model: EMPTY
内容模型：EMPTY

8.5.5 Shortcomings of the OMA DM description framework OMA DM描述框架的缺点

It is not possible to specify that only one Node of an allowed set can be instantiated at a time. Compare with the DTD construct ( A | B ), this is currently described by making both A and B optional, but there is no way to represent that they are mutually exclusive. However, this is mostly a problem that occurs when mapping existing Management Objects onto the description framework. When new Management Objects are designed for the framework, this situation can be avoided.
不可能指定只允许一组的一个节点一次实例化。与DTD结构（A | B）比较，目前通过使A和B都是可选的来描述，但是没有办法表示它们是互斥的。但是，这主要是将现有管理对象映射到描述框架时发生的问题。当为框架设计新的管理对象时，可以避免这种情况。

results matching ""

    No results matching ""