<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>

<!--
    FILE INFORMATION

    OMA Permanent Document
       File: OMA-INF-HTM_SupportFiles_MO-20100414-I
       Type: Text

    Private Reachable Information
       Path: http://www.openmobilealliance.org/ftp/REL/P-n-G
       Name: SupportFiles_MO.html

    NORMATIVE INFORMATION

    This File provides guidance on Management Object (MO) DDF-format
    SUP files.  There is no associated normative material.
	
    LEGAL DISCLAIMER

    Use of this document is subject to all of the terms and conditions
    of the Use Agreement located at
	http://www.openmobilealliance.org/UseAgreement.html

    You may use this document or any part of the document for internal
    or educational purposes only, provided you do not modify, edit or
    take out of context the information in this document in any manner.
    Information contained in this document may be used, at your sole
    risk, for any purposes.

    You may not use this document in any other manner without the prior
    written permission of the Open Mobile Alliance.  The Open Mobile
    Alliance authorizes 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.  The
    Open Mobile Alliance assumes no responsibility for errors or
    omissions in this document.

    Each Open Mobile Alliance member has agreed to use reasonable
    endeavors to inform the Open Mobile Alliance in a timely manner of
    Essential IPR as it becomes aware that the Essential IPR is related
    to the prepared or published specification.  However, the members
    do not have an obligation to conduct IPR searches.  The declared
    Essential IPR is publicly available to members and non-members of
    the Open Mobile Alliance and may be found on the "OMA IPR
    Declarations" list at http://www.openmobilealliance.org/ipr.html.
    The Open Mobile Alliance has not conducted an independent IPR review
    of this document and the information contained herein, and makes no
    representations or warranties regarding third party IPR, including
    without limitation patents, copyrights or trade secret rights.  This
    document may contain inventions for which you must obtain licenses
    from third parties before making, using or selling the inventions.
    Defined terms above are set forth in the schedule to the Open Mobile
    Alliance Application Form.

    NO REPRESENTATIONS OR WARRANTIES (WHETHER EXPRESS OR IMPLIED) ARE
    MADE BY THE OPEN MOBILE ALLIANCE OR ANY OPEN MOBILE ALLIANCE MEMBER
    OR ITS AFFILIATES REGARDING ANY OF THE IPR'S REPRESENTED ON THE "OMA
    IPR DECLARATIONS" LIST, INCLUDING, BUT NOT LIMITED TO THE ACCURACY,
    COMPLETENESS, VALIDITY OR RELEVANCE OF THE INFORMATION OR WHETHER OR
    NOT SUCH RIGHTS ARE ESSENTIAL OR NON-ESSENTIAL.

    THE OPEN MOBILE ALLIANCE IS NOT LIABLE FOR AND HEREBY DISCLAIMS ANY
    DIRECT, INDIRECT, PUNITIVE, SPECIAL, INCIDENTAL, CONSEQUENTIAL, OR
    EXEMPLARY DAMAGES ARISING OUT OF OR IN CONNECTION WITH THE USE OF
    DOCUMENTS AND THE INFORMATION CONTAINED IN THE DOCUMENTS.

    Copyright 2007 Open Mobile Alliance Ltd.  All Rights Reserved.
    Used with the permission of the Open Mobile Alliance Ltd. under the
    terms set forth above.
-->

<head>
  	<title>Guidelines for Support Files - Management Object (MO) Files</title>
	<meta name="description" content="Guidelines for Support Files - Management Object (MO) Files">
	<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
	<link rel="stylesheet" href="../../GI_template/accessible_StaticPages.css" type="text/css">
	<link rel="stylesheet" href="ProcStyle.css" type="text/css">
</head>

<body>

<!--  Document Header  -->

<table border=0 width=100% cellspacing=0 cellpadding=0>
<tr>
<td align=left><img src="imgOMAlogo.gif"></td>
<td align=right>
<p class=dochead>Guidelines for Support Files - Management Object (MO)</p>
<p class=docfile>OMA-INF-HTM_SupportFiles_MO-20090917-D</p>
</td>
</tr></table>

<!--  Navigation Bar  -->

<table width=100% cellspacing=0 cellpadding=0>
<tr><td colspan=2><img height=5 width=100% src="imgBitWht.gif"></tr>
<tr><td colspan=2><img height=5 width=100% src="imgBitSep.gif"></tr>
<tr>
<td class=navbar>
<a href="Procs-n-Guides.htm">Procs-n-Guides</a>&nbsp;>>
<a href="SupportFiles.htm">SupportFiles</a>&nbsp;>>
<b>MO</b>
</td>
<td class=navbar align=right>Updated: 14 Apr 2010</td>
</tr>
<tr><td colspan=2><img height=5 width=100% src="imgBitSep.gif"></tr>
<tr><td colspan=2><img height=5 width=100% src="imgBitWht.gif"></tr>
</table>

<!--  Start of Document  -->

<h1>Management Object (MO) DDF-format Support Files</h1>

<p>

<h3>Contents</h3>
<ul>
<li><a href="#desc">Description of MO DDF docs</a></li>
<li><a href="#namesp">OMNA Registration Items for OMA MO DDF Files</a></li>
<li><a href="#naming">Naming of MO DDF docs</a></li>
<li><a href="#handling">Handling of MO DDF docs</a></li>
<li><a href="#package">MO DDF docs in Enabler Releases</a></li>
<li><a href="#public">Getting MO DDF docs into Public Directory</a></li>
<li><a href="#header">Embedded Header in OMA MO DDF Files</a></li>
</ul>

<hr class=1>
<a name="desc"><h2>Description of MO DDF docs</h2></a>
Management Objects (MO) DDF-format files provide a mechanism to declare configuration elements associated with an enabler or other control entity as supported by the Device Management (DM) enabler.  The MO DDF-format files are made available through an OMNA registry.
<p>
The MO registry where these files are available is located at:
<pre>
<a href="http://www.openmobilealliance.org/tech/omna/omna-dm_mo.htm">http://www.openmobilealliance.org/tech/omna/omna-dm_mo.htm</a>
</pre>


<hr class=1>
<a name="namesp"><h2>OMNA Registration Items for OMA MO DDF Files</h2></a>
The OMNA registration for MO DDF files records the name for the MO in two of three name schemes.  The three defined name schemes are:

<center>
<table border=1 cellpadding=6>
<tr bgcolor=#CCFFCC><th>MO Label</th><th>Description</th></tr>
<tr><th>oma_<i>label</i></th><td>Assignments of values to MOs defined by OMA Work Groups<br><i>These will have namespaces assigned by OMNA (see below)</i></td></tr>
<tr><th>ext_<i>label</i></th><td>Assignments of values to MOs defined by external entities<br><i>These will have namespaces assigned by the external group</i></td></tr>
<tr><th>x_<i>label</i></th><td>Values that are used for testing or private use<br><i>These will not be recorded by OMNA</i></td></tr>
</table>
</center>

<p>
</pre>
The format of the namespaces registered by OMA Work Groups is
<pre>
<b>urn:oma:mo:</b>oma_</b><i>{Label}</i><b>:</b><i>{VersionText}</i>
</pre>
Example namespaces are:
<pre>
<b>urn:oma:mo:<font color=red>oma_foo</font>:<font color=blue>1.0</font></b>
<b>urn:oma:mo:<font color=red>oma_bar</font>:<font color=blue>1.0</font></b>
</pre>


<hr class=1>
<a name="naming"><h2>Naming of MO DDF docs</h2></a>
The public reachable MO DDF file names are generally shorter and simpler than the names of the OMA permanent documents used for change management.  There is generally no need to have superfluous text in the public file names and it is quite expected to avoid constructs like date strings and status values as well.  As a consequence, the following file name construction scheme is used for the 'SUP' files in the permanent document area and public file names.
<pre>
Perm Doc - <b>OMA-SUP-MO_oma_</b><i>{Label}</i><b>-V</b><i>{versionNumbers}</i><b>-{DateStr}-{State}.txt</b>
Public   - <b>oma_</b><i>{Label}</i><b>-v</b><i>{versionNumbers}</i><b>.ddf</b>
</pre>
Examples:
<pre>
<b>OMA-SUP-MO_<font color=red>oma_foo</font>-V<font color=red>1_0</font>-20070123-C.txt ==> <font color=red>oma_foo</font>-v<font color=red>1_0</font>.ddf</b><br>
<b>OMA-SUP-MO_<font color=red>oma_bar</font>-V<font color=red>1_0</font>-20070321-C.txt ==> <font color=red>oma_bar</font>-v<font color=red>1_0</font>.ddf</b>
</pre>

<hr class=1>
<a name="handling"><h2>Handling of MO DDF docs</h2></a>
The MO SUP file is maintained in the OMA Portal Permanent Document area as with the specifications in the enabler.  It is subject to revision using the normal CR process.  Application of CRs to the MO SUP file will result in an updated file with the appropriate date associated.
<p>
The MO SUP DDF permanent document file should be treated as if it has the ".txt" file extension.  When the public reachable file is loaded, it will be loaded with the ".ddf" extension.
<p>
References to OMA defined MO DDFs in specifications should be done <i><font color=blue>(This needs to be aligned with the Referencing Policy)</font></i> to the developed SUP file.  This will permit easy reference and retrieval of current or past versions using the normal PD file mechanisms.  An example reference would look like:
<center>
<table border=1 cellpadding=2>
<tr><td><font size=1 style=bold>[FOO_MO_DDF]&nbsp;&nbsp;&nbsp;</font></td><td><font size=1>MO DDF for FOO Enabler, Version 1.0, Open Mobile Alliance,<br>OMA-SUP-MO_oma_foo-V1_0, URL:http://www.openmobilealliance.org/&nbsp;&nbsp;&nbsp;&nbsp;</font></td></tr>
</table>
</center>
<p>

<hr class=1>
<a name="package"><h2>MO DDF docs in Enabler Releases</h2></a>
As with Specifications, the MO DDF files are normally components of an Enabler Release.
So, similar to how Specifications are released, the MO DDF files are packaged in the Enabler Release Package to be made available.
This packaging also includes appropriate linkages in the ERELD.
<p>
The following is an example MO DDF file entry in the ERELD:
<center>
<table border=1 cellpadding=2>
<tr bgcolor=cyan>
  <td colspan=3><font size=1 style=bold>Supporting Files</font></td>
</tr>
<tr>
  <td><font size=1 style=bold>[FOO_MO_DDF]&nbsp;&nbsp;&nbsp;&nbsp;</font></td>
  <td><font size=1>OMA-SUP-MO_oma_foo-V1_0-20070123-C&nbsp;&nbsp;&nbsp;&nbsp;</font></td>
  <td><font size=1>
This MO DDF describes the configuration for the FOO Enabler.<br>
Working file in OMNA MO directory:<br>
&nbsp;&nbsp;&nbsp;file: oma_foo-v1_0.ddf<br>
&nbsp;&nbsp;&nbsp;path: http://www.openmobilealliance.org/tech/omna/dm_mo/&nbsp;&nbsp;&nbsp;&nbsp;</font>
  </td>
</tr>
</table>
</center>
<p>

<hr class=1>
<a name="public"><h2>Getting MO DDF docs into Public Directory</h2></a>
The primary means of publishing the MO DDF file into the public directory is the advancement of the enabler release to Candidate.
At that time, the DSO will review the ERELD and for each MO DDF file listed, will copy the material in the listed SUP file to the named version of the public MO DDF file.  This will also result in the OMNA MO registry getting a link to this file if it had not been present in a previous release.
<p>
The DSO would perform the needed copy action like:
<pre>
Copy from <b>OMA-SUP-MO_oma_foo-V1_0-20070123-C.txt</b><br>
       to <b>http://www.openmobilealliance.org/tech/omna/dm_mo/oma_foo-v1_0.ddf</b>
</pre>
<p>


<hr class=1>
<a name="header"><h2>Embedded Header in OMA MO DDF Files</h2></a>
The public MO DDF files are the products of OMA and should properly represent the associated terms and conditions.
This is done by providing information in the file itself that can be viewed by users.
For MO DDF files, the material is just text in the file..
<p>
The following is an example header.

<center>
<table border=1 bgcolor=#DDEEFF><tr><td><pre><font size=-1>
&lt;?xml version="1.0" encoding="UTF-8"?&gt;

&lt;!DOCTYPE MgmtTree PUBLIC "-//OMA//DTD-DM-DDF 1.2//EN"
             "http://www.openmobilealliance.org/tech/DTD/DM_DDF-V1_2.dtd"
             [&lt;?oma-dm-ddf-ver supported-versions="1.2"?&gt;]&gt;

&lt;!--

Foo Barcodes Management Object

   version - 1.0
   date    - 23 Jan 2007

This DDF represents the BarCodes Management Object for the Foo service
according to the OMA DM Device Description Framework

FILE INFORMATION

  OMA Permanent Document
    File: OMA-SUP-MO_foo_barcodes-V1_0-20070123-A
    Type: Text

  Public Reachable Information
    Path: http://www.openmobilealliance.org/tech/omna/dm_mo
    Name: foo_barcodes-v1_0.ddf

NORMATIVE INFORMATION

  Information about this file can be found in the specification

    OMA-TS-FOO_BAR-V1_0

  available at http://www.openmobilealliance.org/

  Send comments to technical-comments@mail.openmobilealliance.org

LEGAL DISCLAIMER

  Use of this document is subject to all of the terms and conditions
  of the Use Agreement located at
    http://www.openmobilealliance.org/UseAgreement.html

  You may use this document or any part of the document for internal
  or educational purposes only, provided you do not modify, edit or
  take out of context the information in this document in any manner.
  Information contained in this document may be used, at your sole
  risk, for any purposes.

  You may not use this document in any other manner without the prior
  written permission of the Open Mobile Alliance.  The Open Mobile
  Alliance authorizes 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.  The
  Open Mobile Alliance assumes no responsibility for errors or
  omissions in this document.

  Each Open Mobile Alliance member has agreed to use reasonable
  endeavors to inform the Open Mobile Alliance in a timely manner of
  Essential IPR as it becomes aware that the Essential IPR is related
  to the prepared or published specification.  However, the members
  do not have an obligation to conduct IPR searches.  The declared
  Essential IPR is publicly available to members and non-members of
  the Open Mobile Alliance and may be found on the "OMA IPR
  Declarations" list at http://www.openmobilealliance.org/ipr.html.
  The Open Mobile Alliance has not conducted an independent IPR review
  of this document and the information contained herein, and makes no
  representations or warranties regarding third party IPR, including
  without limitation patents, copyrights or trade secret rights.  This
  document may contain inventions for which you must obtain licenses
  from third parties before making, using or selling the inventions.
  Defined terms above are set forth in the schedule to the Open Mobile
  Alliance Application Form.

  NO REPRESENTATIONS OR WARRANTIES (WHETHER EXPRESS OR IMPLIED) ARE
  MADE BY THE OPEN MOBILE ALLIANCE OR ANY OPEN MOBILE ALLIANCE MEMBER
  OR ITS AFFILIATES REGARDING ANY OF THE IPR'S REPRESENTED ON THE "OMA
  IPR DECLARATIONS" LIST, INCLUDING, BUT NOT LIMITED TO THE ACCURACY,
  COMPLETENESS, VALIDITY OR RELEVANCE OF THE INFORMATION OR WHETHER OR
  NOT SUCH RIGHTS ARE ESSENTIAL OR NON-ESSENTIAL.

  THE OPEN MOBILE ALLIANCE IS NOT LIABLE FOR AND HEREBY DISCLAIMS ANY
  DIRECT, INDIRECT, PUNITIVE, SPECIAL, INCIDENTAL, CONSEQUENTIAL, OR
  EXEMPLARY DAMAGES ARISING OUT OF OR IN CONNECTION WITH THE USE OF
  DOCUMENTS AND THE INFORMATION CONTAINED IN THE DOCUMENTS.

  Copyright 2010 Open Mobile Alliance Ltd.  All Rights Reserved.
  Used with the permission of the Open Mobile Alliance Ltd. under the
  terms set forth above.

--&gt;


&lt;MgmtTree&gt;
  &lt;VerDTD&gt;1.2&lt;/VerDTD&gt;
  &lt;Node&gt;
    ...
</font></pre></td></tr></table>
</center>
<p>
This information would normally be at the beginning of the MO DDF file.
<p>
An <a href='http://member.openmobilealliance.org/ftp/ops/Templates/OMA-Template-MO_example-20070221-I.txt'>example MO DDF file</a>, which includes this material, is available from the templates page.


<!--  Document Footer  -->

<p>
<table width=100% cellspacing=0 cellpadding=0>
<tr><td colspan=2><img height=5 width=100% src="imgBitWht.gif"></tr>
<tr><td colspan=3><img height=5 width=100% src="imgBitSep.gif"></tr>
<tr>
<td class=footer align=left>&copy; 2010 Open Mobile Alliance, Ltd.<br>All Rights Reserved</td>
<td class=footer align=right>
<a href="http://www.openmobilealliance.org/AboutOMA/useterms.aspx">Website Terms of Use</a>
</td>
</tr>
</table>

</body>
</html>