]> Parameter active notify support. Built-in or derived type name. Bibliographic reference ID; SHOULD uniquely identify this reference across all instance documents. For BBF DM Instances, the bibliographic reference ID rules specified in A.2.4 MUST be used. For example, to reference TR-106 Issue 1 Amendment 2, the value of this attribute would be TR-106a2. Built-in type name. The type hierarchy is as for XML Schema, with "any" and "base64" mapping to the "anySimpleType" and "base64Binary" XML Schema types respectively. Component name; the same as xs:NCName except that dots are not permitted. Data type name; the same as xs:NCName except that cannot start with lower-case letter (to avoid conflict with built-in data type names) and dots are not permitted. Type of default. Default from standard, e.g. RFC. Also applies on object creation. Default on object creation. Description action. Positive integer or "unbounded". Model name, including major and minor versions. The name part is the same as xs:NCName except that dots are not permitted. Object name (maximum length 256). Each component is the same as xs:NCName except that dots are not permitted. This name MUST in addition follow the vendor-specific object name requirements of section 3.3. Object path that cannot contain "{i}" placeholders and that therefore references a single object. The path MUST follow the requirements of A.2.3.4 (its scope will typically be specified via an attribute of type PathScope). Object path that can contain "{i}" placeholders and that can therefore references multiple objects. The path MUST follow the requirements of A.2.3.4 (its scope will typically be specified via an attribute of type PathScope). List of object paths, each of which can contain "{i}" placeholders. Opaque ID. Parameter name (maximum length 256); the same as xs:NCName except that dots are not permitted. This name MUST in addition follow the vendor-specific parameter name requirements of section 3.3. Parameter path that cannot contain "{i}" placeholders and that therefore references a single parameter. The path MUST follow the requirements of A.2.3.4 (its scope will typically be specified via an attribute of type PathScope). Object / parameter path name scope (A.2.3.4). Profile name, including version. The name part is the same as xs:NCName except that dots are not permitted. List of profile names. Object access (within profile). Read-write access. Reference type (A.2.3.6). Item status (applies to most types of item). (Reference) target type (used in path references). Units string. All built-in data types. Length is that of the actual string, not the base64-encoded string. See A.2.3.3. Length is that of the actual string, not the hexBinary-encoded string. See A.2.3.3. All facets. Size facets, taken together, define the valid size ranges, e.g. (0:0) and (6:6) mean that the size has to be 0 or 6. The size facet MUST NOT be specified for non-string data types, i.e. data types that are not derived from base64, hexBinary or string. InstanceRef facets specify how a parameter can reference an object instance (table row) via its instance number. The instanceRef facet MUST NOT be specified for data types that are not derived from int or unsignedInt. PathRef facets specify how a parameter can reference a parameter or object via its path name. The pathRef facet MUST NOT be specified for data types that are not derived from string. Range facets, taken together, define the valid value ranges, e.g. [-1:-1] and [1:4094] mean that the value has to be -1 or 1:4094 (it cannot be 0). The range facet MUST NOT be specified for non-numeric data types, i.e. data types that are not derived from one of the integer types. Enumeration facets, taken together, define the valid values, e.g. "a" and "b" mean that the value has to be a or b. The enumeration facet MUST NOT be specified for data types that are not derived from string. Derived types MAY add additional enumeration values. See A.2.5. EnumerationRef facets allow a parameter's valid values to be obtained from another parameter. The enumerationRef facet MUST NOT be specified for data types that are not derived from string. Pattern attributes, taken together, define valid patterns, e.g. "" and "[0-9A-Fa-f]{6}" means that the value has to be empty or a 6 digit hex string. The pattern facet MUST NOT be specified for data types that are not derived from string. Pattern syntax is the same as for XML Schema regular expressions. See http://www.w3.org/TR/xmlschema-2/#regexs. Multiple units facets MUST NOT be specified. The units facet MUST NOT be specified for data types that are not numeric, i.e. data types that are not derived from one of the integer types. Base facet (status attribute). Base facet (access, status and optional attributes). Bibliography definition. Name by which the referenced document is usually known, e.g. TR-069, RFC 2863. Organization that published the referenced document, e.g. BBF, IEEE, IETF. Document category, e.g. TR (BBF), RFC (IETF). Publication date. Uniquely identifies the reference (this is checked by schema validation). Can be referenced from descriptions by using the {{bibref}} template. See A.2.2.4. Component definition. MUST be unique within the document, including imported components (this is checked by schema validation). Component reference. Name of component to be referenced (included). If specified, is relative path between point of reference (inclusion) and the component's items. If not specified, behavior is as if an empty relative path was specified. Parameter data type definition. Facets MUST NOT be specified if the base attribute is omitted. A built-in data type element MUST NOT be specified if the base attribute is present. See tns:AllFacets for notes and requirements on individual facets. MUST be unique within the document, including imported data types (this is checked by schema validation). Cannot begin with a lower-case letter, in order to avoid confusion with built-in data types. MUST be present if and only if deriving from a non-built-in data type. See A.2.3.1. Parameter data type reference or anonymous restriction / extension. If specified, content MUST be empty. If specified, content MUST NOT be empty. Default facet. Value MUST be valid for the data type. Description: free text which MAY contain a limited amount of mediawiki-like markup as specified in A.2.2. For example, use "*" at the start of a line to indicate a bulleted list. To avoid confusion, the description SHOULD NOT contain tab characters. For BBF standards, the character set MUST be restricted to printable characters in the Basic Latin Unicode block, i.e. to characters whose decimal ASCII representations are in the (inclusive) ranges 9-10 and 32-126. This MUST be specified when the description modifies that of a previously defined item. Specify "prefix" to prefix to the previous description, "append" to append to the previous description, or "replace" to replace the previous description. Enumeration facet. Enumeration reference facet. MUST reference a list-valued parameter. Specifies the point in the naming hierarchy relative to which targetParam applies (A.2.3.4). Specifies the value that indicates that none of the values of the referenced parameter currently apply. Import data types, components and models (Root and Service Objects) from external documents. All such items MUST be imported (this is checked by schema validation). The optional ref attribute MAY be used in order to avoid name conflicts between imported and locally-defined items. If omitted, data type is known by the same name in both this and the referenced document. If omitted, component is known by the same name in both this and the referenced document. If omitted, model is known by the same name in both this and the referenced document. MUST be used to locate the DM Instance (A.2.1). If specified, processing tools MUST regard a mismatch between this and the external document's spec attribute as an error. Instance number reference facet. Specifies the type of reference (A.2.3.6). MUST reference a multi-instance object (table) (A.2.3.4). Specifies the point in the naming hierarchy relative to which targetParent applies (A.2.3.4). List facet. This specifies the size of the TR-069 list-valued parameter, not of the individual list items. Model (Root or Service Object) definition and reference. MUST be unique within the document, including imported models (this is checked by schema validation). MUST be present if and only if extending an existing model. See A.2.10. Object definition and reference. See A.2.8.1 for details of how tables are represented. MUST NOT be present if the object is not a table (see maxEntries). The parameters referenced by each unique key element MUST constitute a unique key. For a non-functional key, or if the table has no enableParameter, the uniqueness requirement always applies. For a functional key, and if the table has an enableParameter, the uniqueness requirement applies only to enabled table entries. Indicates whether this is a functional (true) or non-functional (false) key. MUST be unique within the component or model (this is checked by schema validation). MUST be present if and only if defining a new object. If the object is a table (see maxEntries), the final part of the name MUST be "{i}.". MUST be present if and only if modifying an existing object. minEntries MUST be less than or equal to maxEntries (all values are regarded as being less than "unbounded"). minEntries and maxEntries indicate whether the object is a table: * minEntries=0, maxEntries=1 : single-instance object which might not be allowed to exist, e.g. because only one of it and another object can exist at the same time * minEntries=1, maxEntries=1 : single-instance object that is always allowed to exist * all other cases : object is a table MUST be specified for a table with a variable number of entries, i.e. for which maxEntries is greater than minEntries ("unbounded" is regarded as being greater than all values). MUST be specified for a table in which the ACS can create entries and which has one or more uniqueKey elements that define functional keys. Parameter definition and reference. MUST be unique within the parent object (this is checked by schema validation). MUST be present if and only if defining a new parameter. MUST be present if and only if modifying an existing parameter. Path name reference facet. Specifies the type of reference (A.2.3.6). If the list is non-empty, this parameter MUST only reference immediate children of matching objects (A.2.3.4). Specifies the point in the naming hierarchy relative to which targetParent applies (A.2.3.4). Specifies the type of item that can be referenced. Specifies the valid data types for a referenced parameter. Pattern facet (pattern syntax is as in XML Schema). Profile definition and reference. If the extends attribute is insufficient to express general profile requirements, any additional requirements MUST be specified here. MUST be unique within the model (this is checked by schema validation). MUST be present if and only if defining a new profile. MUST specify base if modifying an existing profile or if the profile version is greater than 1. MUST specify extends if the profile extends other profile(s). Profile object definition. If the requirement attribute is insufficient to express the requirement, any additional requirements MUST be specified here and MAY override the attribute. Profile parameter definition. If the requirement attribute is insufficient to express the requirement, any additional requirements MUST be specified here and MAY override the attribute. Range facet. Size facet. Units facet. Parameter syntax specification. For lists, the TR-069 parameter is always a string and the data type specification applies to individual list items, not to the parameter value. See section 3.2 for comma-separated list formatting rules. Direct use of built-in data type, possibly modified via use of facets. Use of named data type, possibly modified via use of facets. If true, MUST always read back as the null value for the parameter's base data type (A.2.3.5). If true, setting this parameter triggers a CPE action. Such a parameter is not part of the device configuration and MUST always read back as the null value for the parameter's base data type (A.2.3.5). CWMP Data Model Definition XML Schema (DM Schema) instance documents can contain any or all of the following: * Data type definitions * Root Object definitions (including profiles) * Service Object definitions (including profiles) * Component definitions * Vendor extension definitions Top-level description. Imported data types, components and models (Root and Service Objects). Top-level data type definitions. Bibliographic references. Component definitions. Model (Root and Service Object) definitions. URI of the associated specification document, e.g. the BBF Technical Report. This URI SHOULD uniquely identify the specification. More than one DM Schema instance document MAY reference the same specification. Where the specification is a BBF document, the URI naming rules specified in A.2.1.1 MUST be used. For example, to reference TR-106 Issue 1 Amendment 2, the value of this attribute would be urn:broadband-forum-org:tr-106-1-2-0. File name (omitting directory name) of this document. Where the specification is a BBF document, the file naming rules specified in A.2.1.1 MUST be used. For example, for the data model defined in TR-106 Issue 1 Amendment 2, the value of this attribute would be tr-106-1-2-0.xml.