John-Test-Document.html

<!DOCTYPE html>
<head>
  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  <title>Document Title</title>
  <meta charset="utf-8">
  <script src="http://openmobilealliance.github.io/Tools/builds/respec-oma-common.js" async class="remove"></script>
  <script class="remove">
    var respecConfig = {
                // for editor use
                docType: "BASE", // options are BASE, RD, AD, TS, SUP, ETS, ORG
                subtitle: "File_Name",
                shortName:  "shortName",
                otherLinks: [{
                  key: "Other Link",
                  data: [{
                    value: "Link Name",
                    href: "#location"
                  }]
                }],
                editors: [{
                  name:       "Editor Name",
                  url:        "http://example.com/",
                  company:    "Editor Company",
                  companyURL: "http://example.org/",
                  mailto:     "editor@example.com",
                  note:       "editor note"
                }],
    
                authors: [{
                  name:       "Author Name",
                  url:        "http://example.com/",
                  company:    "Author Company",
                  companyURL: "http://example.org/",
                  mailto:     "author@example.com",
                  note:       "author note"
                }],
    
                interactiveLinks: [{
                  name: "Link Name",
                  description: "Link Description",
                  uri: "http://example.com/",
                },{
                  name: "Second Link Name",
                  description: "Second Link Description",
                  uri: "http://example2.com/",
                }],
    
                // for staff only
                specStatus: "DRAFT", // options are Draft, Candidate, Approved, Historic
                publishDate: ""
              };
  </script>
</head>
<body>
  <section id="toc"></section>
  <section id="tof"></section>
  <section id="tot"></section>
  <!-- /end table of content & table of figures -->
  <p>&nbsp;</p>
  <!-- start scope -->
  <section>
    <h2>Scope</h2>
    <aside class="example">
      <p>Define as it relates to Open Mobile Alliance Activity. If it adds clarity, define what is not in the scope.</p>
      <strong>DELETE THIS COMMENT.</strong></aside>
    <aside class="example">
      <p>This clause defines the scope and applicability of the RD.</p>
      <strong>DELETE THIS COMMENT</strong></aside>
    <p>[Enter text here]</p>
    <aside class="example">This clause acts as a reminder to contributors of the RD:
      <ul>
        <li>The RD has to provide a prose description illustrating what the release is about.</li>
        <li>The RD has to provide the requirements necessary for the service release technical specification activity.</li>
        <li>The RD has to provide only the requirements in the scope of the work item under which it is created.</li>
        <li>Use cases in the Appendix of the RD are additional to the main text in the RD and facilitate clarification of the requirements.</li>
      </ul>
      <strong>DELETE THIS COMMENT</strong></aside>
    <p>[Enter text here]</p>
  </section>
  <!-- /end scope -->
  <p>&nbsp;</p>
  <!-- start terminology and conventions -->
  <section>
    <h2>Terminology and Conventions</h2>
    <!-- start conventions -->
    <section>
      <h2>Conventions</h2>
      <p>The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in RFC2119.</p>
      <p>All sections and appendixes, except “Scope” and “Introduction”, are normative, unless they are explicitly indicated to be informative.</p>
    </section>
    <!-- /end conventions --> <!-- start definitions -->
    <section>
      <h2>Definitions</h2>
      <!-- start to be deleted -->
      <aside class="example">
        <p>Add definitions in new rows of the following description list as needed. The following examples show how dictionary references should be made as well as locally defined terms. This description list should be maintained in sorted alphabetic order based on the labels of the terms.</p>
        <br>
         <strong>DELETE THIS COMMENT</strong></aside>
      <!-- /end to be deleted -->
      <dl>
        <dt><dfn>Term 1</dfn></dt>
        <dd>Definition Description Term 1.</dd>
        <dt><dfn>Term 2</dfn></dt>
        <dd>Definition Description Term 2.</dd>
      </dl>
      <p>Kindly consult for more definitions used in this document.</p>
    </section>
    <!-- /end definitions --> <!-- start abbreviations -->
    <section>
      <h2>Abbreviations</h2>
      <!-- start to be deleted -->
      <aside class="example">
        <p>Add abbreviations as needed to the following description list. No special notation should be made regarding terms copied from the Dictionary. This table should be maintained in alphabetic order.</p>
        <br>
         <strong>DELETE THIS COMMENT.</strong></aside>
      <!-- /end to be deleted -->
      <dl>
        <dt><abbr title="Title Abbreviation 1">Abbreviation 1</abbr></dt>
        <dd>Definition Data for Abbreviation 1.</dd>
      </dl>
      <dl>
        <dt><abbr title="Title Abbreviation 2">Abbreviation 2</abbr></dt>
        <dd>Definition Data for Abbreviation 2.</dd>
      </dl>
      <p>Kindly consult for more abbreviations used in this document.</p>
    </section>
    <!-- /end definitions --></section>
  <!-- /end terminology and conventions -->
  <p>&nbsp;</p>
  <!-- start introduction -->
  <section class="informative">
    <h2>Introduction</h2>
    <aside class="example">
      <p>From a market perspective...</p>
      <ul>
        <li>What can you do with this specification?</li>
        <li>What problem does this solve?</li>
        <li>How can this specification be applied?</li>
        <li>Consider the target audience and provide deployment examples as possible.</li>
      </ul>
      <strong>DELETE THIS COMMENT. </strong></aside>
    <!-- start version 1.0 -->
    <section>
      <h2>Version 1.0</h2>
      <aside class="example">
        <p>This section provides a high level, concise and informative description of the main functionality supported in the initial version of the specification.</p>
        <p>The description should be brief, target length should be a few paragraphs. When the enabler or reference release is finished, this description should be aligned with the final functionality.</p>
        <strong>DELETE THIS COMMENT.</strong></aside>
    </section>
    <!-- /end Version 1.0--> <!-- start Version x.y -->
    <section>
      <h2>Version x.y</h2>
      <aside class="example">
        <p>This section should be included for each new major or minor version of the specifications. It should provide a high level, concise and informative description of the <strong>new or modified functionality</strong> introduced in this version of the specification, compared to the previous version.</p>
        <p>The description should be brief, target length should be a few paragraphs. When the enabler or reference release is finished, this description should be aligned with the final functionality differences.</p>
        <strong>DELETE THIS COMMENT.</strong></aside>
    </section>
    <!-- /end Version x.y --> <!-- start Version x.y.z -->
    <section>
      <h2>Version x.y.z</h2>
      <aside class="example">
        <p>This section should be included for each new service release of the specification.</p>
        <p>It should describe at at high level the main changes made to the specification compared to the previous version. The description should be brief, target length should be one paragraph.</p>
        <strong>DELETE THIS COMMENT</strong></aside>
    </section>
    <!-- /end Version x.y.z --></section>
  <!-- /end introduction -->
  <p>&nbsp;</p>
  <!-- start sections as needed -->
  <section>
    <h2>Sections As Needed</h2>
    <aside class="example">
      <p>Sections for the normative specification text. Fill in as needed.</p>
      <p>The following validates the styles used for the headers.</p>
      <strong>DELETE THIS COMMENT.</strong></aside>
    <!-- start Example Level 2 -->
    <section>
      <h2>Example Level 2</h2>
      <p>Text goes here.</p>
      <!-- start Example Level 3 -->
      <section>
        <h2>Example Level 3</h2>
        <p>Text goes here.</p>
        <!-- start example level 4 -->
        <section>
          <h2>Example Level 4</h2>
          <p>Text goes here.</p>
          <figure id="fig1_example"><img src="images/fig1_example.png" data-mce-src="images/fig1_example.png"> 
            <figcaption>Example Figure</figcaption>
          </figure>
          <!-- start example table -->
          <table class="mce-item-table"><caption>Example Table</caption>
            <thead>
              <tr>
                <td>&nbsp;</td>
                <td>Column1</td>
                <td>Column2</td>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td>Row1</td>
                <td>Grid 1,1 data</td>
                <td>Grid 1,2 data</td>
              </tr>
              <tr>
                <td>Row2</td>
                <td>Grid 2,1 data</td>
                <td>Grid 2,2 data</td>
              </tr>
            </tbody>
          </table>
          <!-- /end example table --></section>
        <!-- /end Example Level 4 --></section>
      <!-- /end Start Example Level 3 --></section>
    <!-- /end Start Example Level 2 --></section>
  <!-- /end sections as needed -->
  <p>&nbsp;</p>
  <!-- start another section -->
  <section>
    <h2>Another Section</h2>
    <p>Text goes here.</p>
    <!-- start Another Sub-section -->
    <section>
      <h2>Another Sub-section</h2>
      <p>More text goes here.</p>
    </section>
    <!-- /end Another Sub-section --></section>
  <!-- /end another section -->
  <p>&nbsp;</p>
  <!-- start appendix -->
  <section class="appendix">
    <h2>Appendix</h2>
    <aside class="example">
      <p>If needed, add annex to provide additional information to support the document.</p>
      <p>In general, this information should be informative, as normative material should be contained in the primary body of the document.</p>
      <p>Note that the styles for the headers in the appendix (App1, App2, App3) are different than the main body. The use below is intended to validate the styles to be used. Remove if not needed.</p>
      <strong>DELETE THIS COMMENT.</strong></aside>
    <!-- start App Headers -->
    <section>
      <h2>App Headers</h2>
      <p>Text goes here.</p>
      <!-- start More Headers -->
      <section>
        <h2>More Headers</h2>
        <p>More text goes here.</p>
        <!-- start Even More Headers -->
        <section>
          <h2>Even More Header</h2>
          <p>More text goes here.</p>
        </section>
        <!-- end Even More Headers --></section>
      <!-- /end More Headers --></section>
    <!-- /end App Headers --></section>
  <!-- /end appendix -->
  <p>&nbsp;</p>
  <!-- start scr requirements -->
  <p>&nbsp;</p>
  <!-- note that there is no need for appendix class -->
  <section>
    <h2>Static Conformance Requirements (Normative)</h2>
    <p>The notation used in this appendix is specified in [SCRRULES].</p>
    <aside class="example">
      <p>This section is composed using the SCR Tool Editor.</p>
      <ul>
        <li>This tool is still under development.</li>
      </ul>
      <strong>DELETE THIS COMMENT.</strong></aside>
    <!-- start example client scr tables to be deleted -->
    <aside class="example"><!-- start scr for xyz client -->
      <section>
        <h2>SCR for XYZ Client - TO BE DELETED</h2>
        <table class="mce-item-table"><caption>SCR for XYZ Client</caption>
          <thead>
            <tr>
              <td>Item</td>
              <td>Function</td>
              <td>Reference</td>
              <td>Requirement</td>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>XYZ-C-001-M</td>
              <td>Something mandatory</td>
              <td>Section x.y</td>
              <td>(XYZ-C-004-O OR XYZ-C-003-M) AND XYZ-C-002-O</td>
            </tr>
            <tr>
              <td>XYZ-C-002-O</td>
              <td>Something optional</td>
              <td>Section x.y</td>
              <td>&nbsp;</td>
            </tr>
            <tr>
              <td>XYZ-C-003-M</td>
              <td>Dependencies on ZYX</td>
              <td>Section x.y</td>
              <td>ZYX:MCF</td>
            </tr>
            <tr>
              <td>XYZ-C-004-O</td>
              <td>Dependencies on ZYX</td>
              <td>Section x.y</td>
              <td>ZYX:MCF</td>
            </tr>
          </tbody>
        </table>
      </section>
    </aside>
    <!-- /end example client scr table to be deleted --> <!-- start example server scr table to be deleted -->
    <aside class="example">
      <section>
        <h2>SCR for XYZ Server - TO BE DELETED</h2>
        <table class="mce-item-table" data-mce-selected="1"><caption>SCR for XYZ Server</caption>
          <thead>
            <tr>
              <td>Item</td>
              <td>Function</td>
              <td>Reference</td>
              <td>Requirement</td>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>XYZ-S-001-M</td>
              <td>Something mandatory</td>
              <td>Section x.y</td>
              <td>(XYZ-S-004-O OR XYZ-S-003-M) AND XYZ-S-002-O</td>
            </tr>
            <tr>
              <td>XYZ-S-002-O</td>
              <td>Something optional</td>
              <td>Section x.y</td>
              <td>&nbsp;</td>
            </tr>
            <tr>
              <td>XYZ-S-003-M</td>
              <td>Dependencies on ZYX</td>
              <td>Section x.y</td>
              <td>ZYX:MSF</td>
            </tr>
            <tr>
              <td>XYZ-S-004-O</td>
              <td>Dependencies on ZYX</td>
              <td>Section x.y</td>
              <td>ZYX:OSF</td>
            </tr>
          </tbody>
        </table>
      </section>
      <!-- /end scr for xyz server --></aside>
    <!-- /end example to be deleted --></section>
  <!-- /end scr requirements -->
  <div data-mce-style="display:none" style="display:none">[RFC2119].</div>
  <div data-mce-style="display:none" style="display:none">RFC2119</div>
  <div data-mce-style="display:none" style="display:none">RFC2119</div>
  <div data-mce-style="display:none" style="display:none">RFC2119</div>
  <div data-mce-style="display:none" style="display:none">RFC2119</div>
  <div data-mce-style="display:none" style="display:none">RFC2119</div>
</body>