Commit 257c5dff authored by Laurent Velez's avatar Laurent Velez

Initial upload

parents
This source diff could not be displayed because it is too large. You can view the blob instead.
This diff is collapsed.
This diff is collapsed.
<?xml version="1.0" encoding="UTF-8"?>
<!--
TR-069 Device:2 Root Object Model with oneM2M extensions
Notice:
Copyright Notification
The oneM2M Partners authorize you to copy this document, provided that you retain all copyright and other proprietary notices contained in the original materials on any copies of the materials and that you comply strictly with these terms. This copyright permission does not constitute an endorsement of the products or services, nor does it encompass the granting of any patent rights. The oneM2M Partners assume no responsibility for errors or omissions in this document.
© 2014, oneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TTA, TTC). All rights reserved.
Notice of Disclaimer & Limitation of Liability
The information provided in this document is directed solely to professionals who have the appropriate degree of experience to understand and interpret its contents in accordance with generally accepted engineering or other professional standards and applicable regulations.
No recommendation as to products or vendors is made or should be implied.
NO REPRESENTATION OR WARRANTY IS MADE THAT THE INFORMATION IS TECHNICALLY ACCURATE OR SUFFICIENT OR CONFORMS TO ANY STATUTE,
GOVERNMENTAL RULE OR REGULATION, AND FURTHER, NO REPRESENTATION OR WARRANTY IS MADE OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR AGAINST INFRINGEMENT OF INTELLECTUAL PROPERTY RIGHTS.
NO oneM2M PARTNER TYPE 1 SHALL BE LIABLE, BEYOND THE AMOUNT OF ANY SUM RECEIVED IN PAYMENT BY THAT PARTNER FOR THIS DOCUMENT, WITH RESPECT TO ANY CLAIM, AND IN NO EVENT SHALL oneM2M BE LIABLE FOR LOST PROFITS OR OTHER INCIDENTAL OR CONSEQUENTIAL DAMAGES.
oneM2M EXPRESSLY ADVISES ANY AND ALL USE OF OR RELIANCE UPON THIS INFORMATION PROVIDED IN THIS DOCUMENT IS AT THE RISK OF THE USER.
Editors:
Timothy Carey Alcatel-Lucent
Issue History:
* April 2014: tr-181-2-99-0.xml:
Initial
* July 2014: tr-181-2-99-0.xml:
Updated Notice and Editors
* January 2015: tr-181-2-99-0.xml:
Updated to ts-0006-1-1-0
Updated device model to reference latest BBF specificatons
* August 2015: tr-181-2-99-0.xml:
Updated to ts-0006-1-2-0
Publication Date:
* August 2015
-->
<dm:document xmlns:dm="urn:broadband-forum-org:cwmp:datamodel-1-5"
xmlns:dmr="urn:broadband-forum-org:cwmp:datamodel-report-0-1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:broadband-forum-org:cwmp:datamodel-1-5
http://www.broadband-forum.org/cwmp/cwmp-datamodel-1-5.xsd
urn:broadband-forum-org:cwmp:datamodel-report-0-1
http://www.broadband-forum.org/cwmp/cwmp-datamodel-report.xsd"
spec="urn:broadband-forum-org:tr-181-2-99-0" file="tr-181-2-99-0.xml">
<description>
oneM2M Data Model based on TR-181i2 Device:2.8. Includes oneM2M extensions
</description>
<import file="tr-181-2-8.xml" spec="urn:broadband-forum-org:tr-181-2-8">
<model name="Device:2.8"/>
</import>
<import file="ts-0006-1-2.xml" spec="http://www.onem2m.org/xml/protocols">
<component name="oneM2M"/>
</import>
<model name="Device:2.99" base="Device:2.8">
<component ref="oneM2M"/>
</model>
</dm:document>
This diff is collapsed.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment