W3C home > Mailing lists > Public > public-dap-commits@w3.org > November 2012

dap commit: Way too many difinitions of 'user agent'.

From: Mercurial notifier <cvsmail@w3.org>
Date: Fri, 23 Nov 2012 15:17:37 +0000
Message-Id: <E1Tbv0b-0005us-Rj@mcbain.w3.org>
To: public-dap-commits@w3.org
changeset:   284:b0cd8eac91d7
tag:         tip
user:        Mounir Lamouri <mounir.lamouri@gmail.com>
date:        Fri Nov 23 15:17:07 2012 +0000
files:       network-api/Overview.html
description:
Way too many difinitions of 'user agent'.


diff -r 17da00aa9160 -r b0cd8eac91d7 network-api/Overview.html
--- a/network-api/Overview.html	Fri Nov 23 15:14:23 2012 +0000
+++ b/network-api/Overview.html	Fri Nov 23 15:17:07 2012 +0000
@@ -84,10 +84,9 @@
       <section>
         <h2>Outstanding issues</h2>
         <p>
-          The specification currently requests the <dfn>user agent</dfn> to
-          expose two properties: <code>bandwidth</code> and
-          <code>metered</code>. The working group currently does not have
-          consensus on these.
+          The specification currently requests the <a>user agent</a> to expose
+          two properties: <code>bandwidth</code> and <code>metered</code>. The
+          working group currently does not have consensus on these.
         </p>
         <p>
           One concern is that <code>bandwidth</code> may be hard to implement,
@@ -96,7 +95,7 @@
           the server.<br>
           A solution to fix this would be to return non absolute values that
           couldn't be easily abused and would be more simple to produce for the
-          <dfn>user agent</dfn>. For example, having a set of values like
+          <a>user agent</a>. For example, having a set of values like
           <code>very-slow</code>, <code>slow</code>, <code>fast</code> and
           <code>very-fast</code>. Another solution would be to have only values
           like <code>very-slow</code>, <code>slow</code> and the empty string."
@@ -105,7 +104,7 @@
           <code>metered</code> may also be hard to implement as there is
           currently no standard way for the OS to know if the current connection
           is metered.  The approach of the specification is to leave the
-          implementation details to the <dfn>user agent</dfn>. That way, the
+          implementation details to the <a>user agent</a>. That way, the
           attribute could return a value based on a heuristic, on knowledge of
           the current connection status or even by directly asking the user for
           the information.<br>
@@ -124,8 +123,9 @@
 
     <section id='conformance'>
       <p>
-        This specification defines conformance criteria that apply to a single product: the <dfn>user agent</dfn> that
-        implements the interfaces that it contains.
+        This specification defines conformance criteria that apply to a single
+        product: the <dfn>user agent</dfn> that implements the interfaces that
+        it contains.
       </p>
       <p>
         Implementations that use ECMAScript to expose the APIs defined in this specification must implement them in a manner
Received on Friday, 23 November 2012 15:17:46 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 23 November 2012 15:17:46 GMT