2009/dap/system-info Overview.html,1.8,1.9

Update of /sources/public/2009/dap/system-info
In directory hutz:/tmp/cvs-serv12433

Modified Files:
	Overview.html 
Log Message:
Fix RFC2119 keywords, and some markup


Index: Overview.html
===================================================================
RCS file: /sources/public/2009/dap/system-info/Overview.html,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -d -r1.8 -r1.9
--- Overview.html	24 Nov 2009 12:27:02 -0000	1.8
+++ Overview.html	24 Nov 2009 12:50:08 -0000	1.9
@@ -27,8 +27,8 @@
 <!--***************************************Power*************************************************-->
 	<section>
 		<h2>Power</h2>
-			This power specification is a set of APIs that exposes available power sources such as: batteries, 
-            wall outlet, ..etc. It also expose if the device is on battery power and its charge level.
+		<p>This power specification is a set of APIs that exposes available power sources such as: batteries, 
+    wall outlet, etc. It also expose if the device is on battery power and its charge level.</p>
 		<dl title='[NoInterfaceObject] interface Power' class='idl'>
 			<dt>readonly attribute boolean usingExternalPowerSource</dt>
 			<dd>The <code>usingExternalPowerSource</code> attribute must be <code>true</code> if 
@@ -2267,26 +2267,26 @@
       <section>
         <h3>Connection</h3>
         <ul>
-          <li> A conforming implementation <em title="must" class="rfc2119">must</em> provide a method to detect the technology that a network bearer uses (e.g. 802.11a, CDMA, WiMAX, etc.)</li>
-          <li>A conforming implementation <em title="must" class="rfc2119">must</em> provide a method to detect the quality of the connection to the network bearer.</li>
-          <li>A conforming implementation <em title="must" class="rfc2119">must</em> provide a method to detect whether a specified service is available. This method <em title="should" class="rfc2119">should</em> be asynchronous.</li>
-          <li>A conforming implementation <em title="must" class="rfc2119">must</em> provide a events about the availability of a specified service.</li>
-          <li>A conforming implementation <em title="must" class="rfc2119">must</em> provide a method to detect the quality of the connection to a specified service.</li>
-          <li>A conforming implementation <em title="must" class="rfc2119">must</em> provide a method to detect whether the device currently has a valid network connection. This method <em title="should" class="rfc2119">should</em> be synchronous.</li>
-          <li>A conforming implementation <em title="must" class="rfc2119">must</em> provide a method to detect changes in the devices network status (e.g. radio turned on or signal no longer available).</li>
-          <li>A conforming implementation <em title="must" class="rfc2119">must</em> provide information about the current network bearer.</li>
-          <li>A conforming implementation <em title="may" class="rfc2119">may</em> provide information about the default network bearer.</li>
-          <li>A conforming implementation <em title="may" class="rfc2119">may</em> provide information about the preferred network bearer.</li>
-          <li>A conforming implementation <em title="may" class="rfc2119">may</em> provide a method to change the current network bearer.</li>
-          <li>A conforming implementation <em title="should" class="rfc2119">should</em> provide a method to detect whether a device that is using a cellular network is currently roaming.</li>
-          <li>A conforming implementation <em title="may" class="rfc2119">may</em> provide a method to detect geolocation based on cell tower triangulation calculations.</li>
-          <li>A conforming implementation <em title="should" class="rfc2119">should</em> provide a method to detect the ID of the current network bearer.</li>
-          <li>A conforming implementation <em title="should" class="rfc2119">should</em> provide a method to detect the type of encryption in use by a network bearer.</li>
-          <li>A conforming implementation <em title="should" class="rfc2119">should</em> provide a method to detect the operator, MMC, and MNC of a PLM Network.</li>
-          <li>A conforming implementation <em title="should" class="rfc2119">should</em> provide IP Address Table change events.</li>
-          <li>A conforming implementation <em title="should" class="rfc2119">should</em> provide Route Table change events.</li>
-          <li>A conforming implementation <em title="must" class="rfc2119">must</em> provide connected events.</li>
-          <li>A conforming implementation <em title="must" class="rfc2119">must</em> provide disconnected events.</li>
+          <li> A conforming implementation MUST provide a method to detect the technology that a network bearer uses (e.g. 802.11a, CDMA, WiMAX, etc.)</li>
+          <li>A conforming implementation MUST provide a method to detect the quality of the connection to the network bearer.</li>
+          <li>A conforming implementation MUST provide a method to detect whether a specified service is available. This method SHOULD be asynchronous.</li>
+          <li>A conforming implementation MUST provide a events about the availability of a specified service.</li>
+          <li>A conforming implementation MUST provide a method to detect the quality of the connection to a specified service.</li>
+          <li>A conforming implementation MUST provide a method to detect whether the device currently has a valid network connection. This method SHOULD be synchronous.</li>
+          <li>A conforming implementation MUST provide a method to detect changes in the devices network status (e.g. radio turned on or signal no longer available).</li>
+          <li>A conforming implementation MUST provide information about the current network bearer.</li>
+          <li>A conforming implementation MAY provide information about the default network bearer.</li>
+          <li>A conforming implementation MAY provide information about the preferred network bearer.</li>
+          <li>A conforming implementation MAY provide a method to change the current network bearer.</li>
+          <li>A conforming implementation SHOULD provide a method to detect whether a device that is using a cellular network is currently roaming.</li>
+          <li>A conforming implementation MAY provide a method to detect geolocation based on cell tower triangulation calculations.</li>
+          <li>A conforming implementation SHOULD provide a method to detect the ID of the current network bearer.</li>
+          <li>A conforming implementation SHOULD provide a method to detect the type of encryption in use by a network bearer.</li>
+          <li>A conforming implementation SHOULD provide a method to detect the operator, MMC, and MNC of a PLM Network.</li>
+          <li>A conforming implementation SHOULD provide IP Address Table change events.</li>
+          <li>A conforming implementation SHOULD provide Route Table change events.</li>
+          <li>A conforming implementation MUST provide connected events.</li>
+          <li>A conforming implementation MUST provide disconnected events.</li>
           
         </ul>
       </section>
@@ -2310,12 +2310,11 @@
           <li>A conforming implementation MUST provide a list of audio codecs
           available on the device</li>
           <li>A conforming implementation MUST provide a list of audio output
-					devices (speakers etc)</li>
+					devices (speakers etc.)</li>
           <li>A conforming implementation MUST provide a list of audio input
 					devices (microphones, software)</li>
           <li>A conforming implementation SHOULD provide audio architecture
           information.</li>
-          <li>A conforming implementation MAY xyz</li>
         </ul>
       </section>
       <section>

Received on Tuesday, 24 November 2009 12:50:20 UTC