Changeset 812 for draft-ietf-httpbis/latest

Timestamp:

28/04/10 14:23:52 (12 years ago)

Author:

julian.reschke@…

Message:

add BCP14 markup

Location:

draft-ietf-httpbis/latest

Files:

• p2-semantics.html (modified) (5 diffs)
• p2-semantics.xml (modified) (1 diff)

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

@@ -403 +403 @@
       <meta name="dct.creator" content="Reschke, J. F.">
       <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest">
-      <meta name="dct.issued" scheme="ISO8601" content="2010-04-01">
+      <meta name="dct.issued" scheme="ISO8601" content="2010-04-28">
       <meta name="dct.replaces" content="urn:ietf:rfc:2616">
       <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 2 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 2 defines the semantics of HTTP messages as expressed by request methods, request-header fields, response status codes, and response-header fields.">
@@ -434 +434 @@
             </tr>
             <tr>
-               <td class="left">Expires: October 3, 2010</td>
+               <td class="left">Expires: October 30, 2010</td>
                <td class="right">HP</td>
             </tr>
@@ -487 +487 @@
             <tr>
                <td class="left"></td>
-               <td class="right">April 1, 2010</td>
+               <td class="right">April 28, 2010</td>
             </tr>
          </tbody>
@@ -514 +514 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire in October 3, 2010.</p>
+      <p>This Internet-Draft will expire in October 30, 2010.</p>
       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
       <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
@@ -1624 +1624 @@
       </p>
       <p id="rfc.section.9.6.p.3">If the request-target was obtained from a source that does not have its own URI (e.g., input from the user keyboard), the
-         Referer field MUST either be sent with the value "about:blank", or not be sent at all. Note that this requirement does not
-         apply to sources with non-HTTP URIs (e.g., FTP).
+         Referer field <em class="bcp14">MUST</em> either be sent with the value "about:blank", or not be sent at all. Note that this requirement does not apply to sources with
+         non-HTTP URIs (e.g., FTP).
       </p>
       <div id="rfc.figure.u.21"></div><pre class="inline"><span id="rfc.iref.g.22"></span><span id="rfc.iref.g.23"></span>  <a href="#header.referer" class="smpl">Referer</a>        = "Referer" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.referer" class="smpl">Referer-v</a>

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

@@ -2142 +2142 @@
 <t>
    If the request-target was obtained from a source that does not have its own
-   URI (e.g., input from the user keyboard), the Referer field MUST either be
+   URI (e.g., input from the user keyboard), the Referer field &MUST; either be
    sent with the value "about:blank", or not be sent at all. Note that this
    requirement does not apply to sources with non-HTTP URIs (e.g., FTP).