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

<!--
    FILE INFORMATION

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

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

    NORMATIVE INFORMATION

    This File provides guidance on Application Characteristic (AC) 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 2010 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 - Application Characteristic (AC)</title>
	<meta name="description" content="Guidelines for Support Files - Application Characteristic (AC)">
	<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
	<meta http-equiv="content-style-type" content="text/css">
	<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 - Application Characteristic (AC)</p>
<p class=docfile>OMA-INF-HTM_SupportFiles_AC-20100414-I</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>AC</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>Application Characteristic (AC) Files</h1>

<p>

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

<hr class=1>
<a name="desc"><h2>Description of AC docs</h2></a>
Application Characteristic (AC) files provide a mechanism to declare configuration elements associated with an enabler or other control entity as supported by the Client Provisioning enabler.  The AC files are made available through an OMNA registry where the APPID values are registered.
<p>
The AC registry where these links are available at:
<pre>
<a href="http://www.openmobilealliance.org/tech/omna/omna-dm_ac.htm">http://www.openmobilealliance.org/tech/omna/omna-dm_ac.htm</a>
</pre>


<hr class=1>
<a name="namesp"><h2>OMNA Registration Items for OMA AC Files</h2>
The OMNA registration for AC files is based on the assigned AppID value and includes a derived namespace.
The namespace value is structured on the AppID and enabler names.
<p>
Due to the lack of versioning information in the AC file itself, it is not possible to differentiate different versions with a single assigned AppID value.  This could be problematic.  Therefore, new AppID values need to be registered when changes to the AC are needed to support a new version.  This will permit the elements to have awareness of the specific configuration set being used.  Thus, though the namespace value includes version - that is not intended to differentiate but merely assist with the version awareness.
<p>
</pre>
The format of these namespaces is
<pre>
<b>urn:oma:ac:</b><i>{AppId}</i><b>_</b><i>{EnablerName}</i><b>:</b><i>{VersionText}</i>
</pre>
Example namespaces are:
<pre>
<b>urn:oma:ac:<font color=red>ap0094_foo</font>:<font color=blue>1.0</font></b>
<b>urn:oma:ac:<font color=red>ap0121_bar</font>:<font color=blue>1.0</font></b>
</pre>


<hr class=1>
<a name="naming"><h2>Naming of AC docs</h2></a>
The public reachable AC 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-AC_</b><i>{AppID}</i><b>_</b><i>{enablerName}</i><b>-V</b><i>{versionNumbers}</i><b>-{DateStr}-{State}.txt</b>
Public   - <b>ac_</b><i>{AppID}</i>-<i>{enablerName}</i><b>-v</b><i>{versionNumbers}</i><b>.txt</b>
</pre>
Examples:
<pre>
<b>OMA-SUP-AC_<font color=red>ap0094_foo</font>-V<font color=red>1_0</font>-20060123-C.txt ==> ac_<font color=red>ap0094_foo</font>-v<font color=red>1_0</font>.txt</b><br>
<b>OMA-SUP-AC_<font color=red>ap0121_bar</font>-V<font color=red>1_0</font>-20060321-C.txt ==> ac_<font color=red>ap0121_bar</font>-v<font color=red>1_0</font>.txt</b>
</pre>


<hr class=1>
<a name="handling"><h2>Handling of AC docs</h2></a>
The AC 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 AC SUP file will result in an updated file with the appropriate date associated.
<p>
The AC SUP file should be treated as if it has the ".txt" file extension.
<p>
References to OMA defined ACs 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>
<tr><td><font size=1 style=bold>[FOO_AC]&nbsp;&nbsp;&nbsp;</font></td><td><font size=1>AC for FOO Enabler, Version 1.0, Open Mobile Alliance,<br>OMA-SUP-AC_ap0094_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>AC docs in Enabler Releases</h2></a>
As with Specifications, ACs are normally components of an Enabler Release.
So, similar to how Specifications are released, ACs 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 AC entry in the ERELD:
<center>
<table border=1>
<tr bgcolor=cyan>
  <td colspan=3><font size=1 style=bold>Supporting Files</font></td>
</tr>
<tr>
  <td><font size=1 style=bold>[FOO_AC]&nbsp;&nbsp;&nbsp;&nbsp;</font></td>
  <td><font size=1>OMA-SUP-AC_ap0094_foo-V1_0-20060123-C&nbsp;&nbsp;&nbsp;&nbsp;</font></td>
  <td><font size=1>
This AC describes the configuration for the FOO Enabler.<br>
Working file in OMNA AC directory:<br>
&nbsp;&nbsp;&nbsp;file: ac_ap0094_foo-v1_0.txt<br>
&nbsp;&nbsp;&nbsp;path: http://www.openmobilealliance.org/tech/omna/dm_ac/&nbsp;&nbsp;&nbsp;&nbsp;</font>
  </td>
</tr>
</table>
</center>
<p>

<hr class=1>
<a name="public"><h2>Getting AC docs into Public Directory</h2></a>
The primary means of publishing the AC file into the public directory is the advancement of the enabler release to Candidate.
At that time, the DSO will review the ERELD and if an AC file is listed, copy the material in the listed SUP file to the named version of the public AC file.  This will also result in the OMNA AC 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-AC_ap0094_foo-V1_0-20060123-C.txt</b><br>
       to <b>http://www.openmobilealliance.org/tech/omna/dm_ac/ac_ap0094_foo-v1_0.txt</b>
</pre>
<p>


<hr class=1>
<a name="header"><h2>Embedded Header in OMA AC Files</h2></a>
The public AC 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 ACs, 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>
    FILE INFORMATION

    OMA Permanent Document
       File: OMA-SUP-AC_<font color=red>ap0094_foo-V1_0-20060123-C</font>
       Type: Text

    Public Reachable Information
       Path: http://www.openmobilealliance.org/tech/omna/dm_ac/
       Name: <font color=red>ac_ap0094_foo-v1_0</font>.txt

    NORMATIVE INFORMATION

    Information about this file can be found in the specification
    <font color=red>OMA-TS-FOO_BAR-V1_0-20060111-C</font> 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&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
    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 20<font color=red>10</font> Open Mobile Alliance Ltd.  All Rights Reserved.
    Used with the permission of the Open Mobile Alliance Ltd. under the
    terms set forth above.</font></pre></td></tr></table>
</center>
<p>
This header information would normally be inserted in the AC near the beginning.


<!--  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>