Changeset 1975 for draft-ietf-httpbis/latest/p1-messaging.xml

Timestamp:

Nov 4, 2012, 9:10:11 PM (7 years ago)

Author:

fielding@…

Message:

Update charset terminology to the latest BCPs and remove duplicate or antiquated references to IETF requirements

File:

• draft-ietf-httpbis/latest/p1-messaging.xml (modified) (2 diffs)

draft-ietf-httpbis/latest/p1-messaging.xml

@@ -20 +20 @@
   <!ENTITY cache-incomplete       "<xref target='Part6' x:rel='#response.cacheability' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
   <!ENTITY payload                "<xref target='Part2' x:rel='#payload' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
-  <!ENTITY media-types            "<xref target='Part2' x:rel='#media.types' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
+  <!ENTITY media-type            "<xref target='Part2' x:rel='#media.type' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
   <!ENTITY content-codings        "<xref target='Part2' x:rel='#content.codings' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
   <!ENTITY CONNECT                "<xref target='Part2' x:rel='#CONNECT' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
@@ -1310 +1310 @@
 <t>
    Historically, HTTP has allowed field content with text in the ISO-8859-1
-   <xref target="ISO-8859-1"/> character encoding and supported other
-   character sets only through use of <xref target="RFC2047"/> encoding.
+   <xref target="ISO-8859-1"/> charset, supporting other charsets only
+   through use of <xref target="RFC2047"/> encoding.
    In practice, most HTTP header field values use only a subset of the
-   US-ASCII character encoding <xref target="USASCII"/>. Newly defined
+   US-ASCII charset <xref target="USASCII"/>. Newly defined
    header fields &SHOULD; limit their field values to US-ASCII octets.
-   Recipients &SHOULD; treat other (obs-text) octets in field content as
+   Recipients &SHOULD; treat other octets in field content (obs-text) as
    opaque data.
 </t>