Changeset 2115 for draft-ietf-httpbis/latest

Timestamp:

11/01/13 13:46:43 (10 years ago)

Author:

fielding@…

Message:

(editorial) product tokens listed in decreasng order; partly addresses #426

Location:

draft-ietf-httpbis/latest

Files:

• p2-semantics.html (modified) (2 diffs)
• p2-semantics.xml (modified) (2 diffs)

draft-ietf-httpbis/latest/p2-semantics.html

@@ -2118 +2118 @@
       <div id="rfc.figure.u.38"></div><pre class="inline"><span id="rfc.iref.g.36"></span>  <a href="#header.user-agent" class="smpl">User-Agent</a> = <a href="#header.user-agent" class="smpl">product</a> *( <a href="#imported.abnf" class="smpl">RWS</a> ( <a href="#header.user-agent" class="smpl">product</a> / <a href="#imported.abnf" class="smpl">comment</a> ) )
 </pre><p id="rfc.section.5.5.3.p.3">The User-Agent field-value consists of one or more product identifiers, each followed by zero or more comments (<a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.21"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>), which together identify the user agent software and its significant subproducts. By convention, the product identifiers
-         are listed in order of their significance for identifying the user agent software. Each product identifier consists of a name
-         and optional version.
+         are listed in decreasing order of their significance for identifying the user agent software. Each product identifier consists
+         of a name and optional version.
       </p>
       <div id="rfc.figure.u.39"></div><pre class="inline"><span id="rfc.iref.g.37"></span><span id="rfc.iref.g.38"></span>  <a href="#header.user-agent" class="smpl">product</a>         = <a href="#imported.abnf" class="smpl">token</a> ["/" <a href="#header.user-agent" class="smpl">product-version</a>]
@@ -3144 +3144 @@
       <div id="rfc.figure.u.61"></div><pre class="inline"><span id="rfc.iref.g.61"></span>  <a href="#header.server" class="smpl">Server</a> = <a href="#header.user-agent" class="smpl">product</a> *( <a href="#imported.abnf" class="smpl">RWS</a> ( <a href="#header.user-agent" class="smpl">product</a> / <a href="#imported.abnf" class="smpl">comment</a> ) )
 </pre><p id="rfc.section.7.4.2.p.3">The Server field-value consists of one or more product identifiers, each followed by zero or more comments (<a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.29"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>), which together identify the origin server software and its significant subproducts. By convention, the product identifiers
-         are listed in order of their significance for identifying the origin server software. Each product identifier consists of
-         a name and optional version, as defined in <a href="#header.user-agent" id="rfc.xref.header.user-agent.2" title="User-Agent">Section&nbsp;5.5.3</a>.
+         are listed in decreasing order of their significance for identifying the origin server software. Each product identifier consists
+         of a name and optional version, as defined in <a href="#header.user-agent" id="rfc.xref.header.user-agent.2" title="User-Agent">Section&nbsp;5.5.3</a>.
       </p>
       <p id="rfc.section.7.4.2.p.4">Example:</p>

draft-ietf-httpbis/latest/p2-semantics.xml

@@ -2498 +2498 @@
    each followed by zero or more comments (&header-fields;), which together
    identify the user agent software and its significant subproducts.
-   By convention, the product identifiers are listed in order of their
-   significance for identifying the user agent software. Each product
+   By convention, the product identifiers are listed in decreasing order of
+   their significance for identifying the user agent software. Each product
    identifier consists of a name and optional version.
 </t>
@@ -4072 +4072 @@
    followed by zero or more comments (&header-fields;), which together
    identify the origin server software and its significant subproducts.
-   By convention, the product identifiers are listed in order of their
-   significance for identifying the origin server software. Each product
+   By convention, the product identifiers are listed in decreasing order of
+   their significance for identifying the origin server software. Each product
    identifier consists of a name and optional version, as defined in
    <xref target="header.user-agent"/>.