Parameter active notify support (based on dm:activeNotify).
Nested list escaping support (based on dm:ListNesting).
No information (for DM="permitted", Controller can't infer support).
Not supported (not valid for DM="required"; for DM="permitted", Controller can't infer support).
Supported (not valid for DM="legacy").
Object access (based on dm:ProfileObjectAccess).
All built-in data types.
All facets.
Annotation.
Base facet (access attribute).
Base facet (no attributes).
Bibliography definition.
The description element is DEPRECATED because it was added in error. The annotation element SHOULD be used instead.
Default facet.
Value MUST be valid for the data type.
Enumeration facet.
Import data types and models (Root and Service Objects) from DM Instances. All such items MUST be imported (this is checked by schema validation).
The DT Instance SHOULD NOT import more than one DM model. This is because a DT Instance can't reference more than one DM model, so there is no reason to import more than DM model.
MUST be used to locate the DM Instance (B.2.1).
If specified, processing tools MUST regard a mismatch between this and the external document's spec attribute as an error.
List facet.
This specifies the size of the TR-069 list-valued parameter, not of the individual list items.
Model (Root and Service Object) support details.
Object support details
minEntries MUST be greater than or equal to minEntries(DM), and less than or equal to maxEntries (all values are regarded as being less than "unbounded").
maxEntries MUST be less than or equal to maxEntries(DM) (all values are regarded as being less than "unbounded").
Parameter support details.
Path name reference facet.
Pattern facet (pattern syntax is as in XML Schema).
Range facet.
Size facet.
Parameter data type reference or anonymous restriction / extension.
If specified, content MUST be empty.
If specified, content MUST NOT be empty.
Parameter syntax support details.
Direct use of built-in data type (which MUST be the same data type as that in the referenced DM Instance), possibly modified via use of facets.
Use of named data type (which MUST be the same data type as that in the referenced DM Instance), possibly modified via use of facets.
A default MUST NOT be specified if the DM Instance has already specified a factory or object default.
Top-level feature.
CWMP Device Type XML Schema (DT Schema) instance documents can contain the following:
* Imports (from DM Schema instance documents) of Root or Service Object definitions
* Declarations of which features of imported Root or Service Objects are supported
Top-level annotation.
Imported models (Root and Service Objects).
Bibliographic references.
Top-level features.
Details of support for model (Root and Service Object).
URI indicating the device type associated with this DT Instance.
UUID that MUST uniquely identify this DT instance, e.g. RFC 4122 version 5 UUID derived from the instance text.