Releases: BroadbandForum/data-model-template
Releases · BroadbandForum/data-model-template
2024-07-23: TR-106 Amendment 14
TR-106 Document
- Added access type guidance
- Documented the dmr:noNameCheck attribute
- Documented the decimal datatype
- Documented the list value defaults
- Documented markdown syntax (and switch from MediaWiki)
- Cosmetic changes
DM Data Model Definition Schema (DM Schema)
- Starting from this version, the DM schema version will be the
same as the specification version - Removed the status attribute's default
- Supported virtual components
- Permitted changing the version of an existing parameter (sometimes
needed when using components to define multiple parameters)
Data Model Report Schema (DMR Schema)
- Added noNameCheck to suppress name checks (used for items
that knowingly disobey the rules)
Data Model Data Types
- Updated Alias component to be virtual (with different CWMP
and USP versions)
Data Model Bibliographic References
- Fixed IPDR reference links
- Added more bibrefs
Device Type Schema (DT Schema)
- Starting from this version, the DT schema version will be the
same as the specification version
2024-01-18: TR-106 Amendment 13
TR-106 Document
- Clarified the requirements regarding vendor-specific prefixes
Data Model Data Types
- Added an Alias component to reduce cut-and-paste in the data models
- Added an Order type to reduce cut-and-paste in the data models
Data Model Bibliographic References
- Added more bibrefs
2023-06-14: TR-106 Amendment 12
TR-106 Document
- Updated the Mountable Object and Mount Point descriptions to
indicate that all top-level objects (other than mount points) are
mountable - Updated path scoping rules to indicate that a path that starts
with a period (.
) is relative to its mount point (if mounted)
or to the Root or Service Object (otherwise) - Updated the hidden and secured attributes to clarify that they
can't both be set to true, and that for CWMP secured means
the same as hidden - Tightened the version attribute definition. It can only be
used when the version is later than the parent version,
except that it always has to be specified for Objects and
Profiles. Also added a new section on the use of the version
attribute - Clarified that defaults defined in components will be "promoted"
to parameter defaults when used in command or event arguments - Fixed the rules governing modifications of existing models. The
basic rule is that the value space can only be expanded, never
contracted - Added a new section on the DMR (Data Model Report) Schema
DM Data Model Definition Schema (DM Schema)
- Supported XSD v1.1, which allows more rigorous validation, e.g.,
use of appropriate attributes when creating and modifying items - Added defaults for various attributes, e.g. access, minEntries
and maxEntries default to readOnly, 1 and 1 respectively - Deprecated the mountType attribute's none and mountable
values, because mountable objects are now determined automatically - Made the uniqueKey/functional and the command/async
attributes mandatory - Relaxed rules governing the order of top-level elements such as
import, dataType and component; they can now occur in any
order - Tightened up the use of dmr: attributes, which can now only be
used on elements where they make sense - Fixed a few bugs, e.g., added a template element uniqueness check
Data Model Report Schema (DMR Schema)
- Added noUnitsTemplate to suppress "missing {{units}}
template" warnings - Added previousCommand and previousEvent attributes
Device Type Schema (DT Schema)
- Updated to reference latest published DM Schema version (v1.10)
- Note that the DT Schema is v1.10 to match the DM Schema (DT
Schema v1.7, v1.8 and v1.9 were skipped)
2022-01-27: TR-106 Amendment 11
Specification:
- Clarified
forcedEnabled
andforceDefaultEnabled
for USP - Clarified impact of deprecating or obsoleting profile items
- Documented new description templates
- Documented new
secured
attribute
DM Schema (cwmp-datamodel-1-9.xsd
):
- Allowed the
version
attribute in component references - Allowed
minEntries
andmaxEntries
in command and event argument objects - Allowed
status
attribute in profile command/event arguments - Added
secured
attribute
DM Report Schema (cwmp-datamodel-report-1-0.xsd):
- Changed version number to
1-0
, which indicates new markdown-friendly
wrapped descriptions - Added
customNumEntriesParameter
,noDiscriminatorParameter
and
noUnionObject
to suppress various warnings
DT Schema (cwmp-devicetype-1-6.xsd)
- Updated to reference
cwmp-datamodel-1-9.xsd
2020-11-05: TR-106 Amendment 10
- Converted document to markdown
- Various editorial improvements
2019-09-04: TR-106 Amendment 9
- Schema updates; document not updated
2018-05-10: TR-106 Amendment 8
- Added support of USP (mountable objects)
- Removed references to obsolete data models
- Moved device requirements to TR-069
2014-09-17: TR-106 Amendment 7+
- Support file updates; document not updated
2013-10-07: TR-106 Amendment 7
- Added descriptions of new features in DM Schema (v1.4 & v1.5) and DT Schema (v1.2 & v1.3)
- Added Annex defining additional requirements for BBF standard data models
2011-07-01: TR-106 Amendment 6
- Removed definition of proxying, now defined in TR-069
- Removed Common objects
- Alias Parameter Requirements added