|
1 | 1 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> |
2 | 2 | <html lang="en"> |
3 | | -<!-- $Id: conform.src,v 2.1 1998-02-07 02:00:20 ijacobs Exp $ --> |
| 3 | +<!-- $Id: conform.src,v 2.2 1998-02-09 23:13:38 ijacobs Exp $ --> |
4 | 4 | <HEAD> |
5 | 5 | <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> |
6 | 6 | <TITLE>Conformance: requirements and recommendations</TITLE> |
@@ -246,6 +246,26 @@ href="syndata.html#parsing-errors">rules for handling parsing errors</a>. |
246 | 246 | <P>Since user agents may vary in how they handle error conditions, |
247 | 247 | authors and users must not rely on specific error recovery behavior. |
248 | 248 |
|
| 249 | + |
| 250 | +<H2><span class="index-def" title="text/css"><a |
| 251 | +name="text-css">The text/css content type</a></span></H2> |
| 252 | + |
| 253 | +<p>CSS style sheets that exist in separate |
| 254 | +files are sent over the Internet as a sequence of bytes accompanied by |
| 255 | +encoding information (see <a rel="biblioentry" |
| 256 | +href="./refs.html#ref-HTML40">[HTML40]</a>, chapter 5). The structure |
| 257 | +of the transmission, termed a <span class="index-def" title="message |
| 258 | +entity"><a name="message-entity"><dfn>message entity,</dfn></a></span> |
| 259 | +is defined by <a rel="biblioentry" href="./refs.html#ref-RFC2045" |
| 260 | +class="normref">[RFC2045]</a> and <a rel="biblioentry" |
| 261 | +href="refs.html#ref-RFC2068" class="normref">[RFC2068]</a>. A message |
| 262 | +entity with a content type of "text/css" represents an independent CSS |
| 263 | +document. |
| 264 | + |
| 265 | +<P>The text/css content type is defined in ???. |
| 266 | + |
| 267 | +<!-- To be completed by an RFC -IJ --> |
| 268 | + |
249 | 269 | </BODY> |
250 | 270 | </html> |
251 | 271 | <!-- Keep this comment at the end of the file |
|
0 commit comments