spec/Overview.html 1.1848 2678 Use the %x... syntax in ABNF. (credit: j

Use the %x... syntax in ABNF. (credit: jr) (whatwg r2678)

7.2.4 Interpreting an event stream
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1848.html#event-stream-interpretation
7.2.3 Parsing an event stream
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1848.html#parsing-an-event-stream
last event ID string
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1848.html#concept-event-stream-last-event-id
4.3.1.2 Inline documentation for external scripts
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1848.html#inline-documentation-for-external-scripts

http://people.w3.org/mike/diffs/html5/spec/Overview.diff.html
http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.1847&r2=1.1848&f=h
http://html5.org/tools/web-apps-tracker?from=2677&to=2678

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.1847
retrieving revision 1.1848
diff -u -d -r1.1847 -r1.1848
--- Overview.html 16 Jan 2009 21:07:19 -0000 1.1847
+++ Overview.html 16 Jan 2009 22:44:56 -0000 1.1848
@@ -8368,20 +8368,23 @@
   that the value of the DOM <code title=dom-script-text><a href=#dom-script-text>text</a></code>
   attribute, which is derived from the element's contents, matches the
   <code title="">documentation</code> production in the following
-  ABNF. <a href=#references>[ABNF]</a></p><!-- XXX
+  ABNF, the character set for which is Unicode. <a href=#references>[ABNF]</a></p><!-- XXX
   ftp://ftp.rfc-editor.org/in-notes/std/std68.txt --><pre>documentation = *( *( space / tab / comment ) [ line-comment ] newline )
 comment       = slash star *( not-star / star not-slash ) 1*star slash
 line-comment  = slash slash *not-newline
 
 ; characters
-space         = &lt; a U+0020 SPACE character &gt;
-tab           = &lt; a U+0009 TAB character &gt;
-newline       = &lt; a U+000A LINE FEED character &gt;
-star          = &lt; a U+002A ASTERISK character &gt;
-slash         = &lt; a U+002F SOLIDUS character &gt;
-not-newline   = &lt; a single Unicode character other than U+000A LINE FEED &gt;
-not-star      = &lt; a single Unicode character other than U+002A ASTERISK &gt;
-not-slash     = &lt; a single Unicode character other than U+002F SOLIDUS &gt;</pre><div class=example>
+tab           = %x0009 ; U+0009 TAB
+newline       = %x000A ; U+000A LINE FEED
+space         = %x0020 ; U+0020 SPACE
+star          = %x002A ; U+002A ASTERISK
+slash         = %x002F ; U+002F SOLIDUS
+not-newline   = %x0000-0009 / %x000B-%10FFFF
+                ; a Unicode character other than U+000A LINE FEED
+not-star      = %x0000-0029 / %x002B-%10FFFF
+                ; a Unicode character other than U+002A ASTERISK
+not-slash     = %x0000-002E / %x0030-%10FFFF
+                ; a Unicode character other than U+002F SOLIDUS</pre><div class=example>
 
    <p>This allows authors to include documentation, such as license
    information or API information, inside their documents while still
@@ -35517,24 +35520,25 @@
   Internal Server Error, 501 Not Implemented, 502 Bad Gateway, 503
   Service Unavailable, 504 Gateway Timeout, and 505 HTTP Version Not
   Supported responses --><p>For non-HTTP protocols, UAs should act in equivalent ways.<h4 id=parsing-an-event-stream><span class=secno>7.2.3 </span>Parsing an event stream</h4><!-- XXX Wladimir Palant pointed out problems with HTTP chunking with server-sent-events --><p>This event stream format's MIME type is
-  <code>text/event-stream</code>.<p>The event stream format is as described by the <code title="">stream</code> production of the following ABNF. <a href=#references>[ABNF]</a></p><!-- XXX
+  <code>text/event-stream</code>.<p>The event stream format is as described by the <code title="">stream</code> production of the following ABNF, the
+  character set for which is Unicode. <a href=#references>[ABNF]</a></p><!-- XXX
   ftp://ftp.rfc-editor.org/in-notes/std/std68.txt --><pre>stream        = [ bom ] *event
 event         = *( comment / field ) end-of-line
 comment       = colon *any-char end-of-line
 field         = 1*name-char [ colon [ space ] *any-char ] end-of-line
 end-of-line   = ( cr lf / cr / lf / eof )
-eof           = &lt; matches repeatedly at the end of the stream &gt;</pre>
+eof           = &lt; matches repeatedly at the end of the stream &gt;
 
 ; characters
-bom           = &lt; a single U+FEFF BYTE ORDER MARK character &gt;
-space         = &lt; a single U+0020 SPACE character &gt;
-colon         = &lt; a single U+003A COLON character &gt;
-cr            = &lt; a single U+000D CARRIAGE RETURN character &gt;
-lf            = &lt; a single U+000A LINE FEED character &gt;
-name-char     = &lt; a single Unicode character other than U+003A COLON, U+000D CARRIAGE RETURN and U+000A LINE FEED &gt;
-any-char      = &lt; a single Unicode character other than U+000D CARRIAGE RETURN and U+000A LINE FEED &gt;
-
-  <p>Event streams in this format must always be encoded as
+lf            = %x000A ; U+000A LINE FEED
+cr            = %x000D ; U+000D CARRIAGE RETURN
+space         = %x0020 ; U+0020 SPACE
+colon         = %x003A ; U+003A COLON
+bom           = %xFEFF ; U+FEFF BYTE ORDER MARK
+name-char     = %x0000-0009 / %x000B-000C / %x000E-0039 / %x003B-10FFFF
+                ; a Unicode character other than U+000A LINE FEED, U+000D CARRIAGE RETURN, or U+003A COLON
+any-char      = %x0000-0009 / %x000B-000C / %x000E-10FFFF
+                ; a Unicode character other than U+000D CARRIAGE RETURN or U+003A COLON</pre><p>Event streams in this format must always be encoded as
   UTF-8.<p>Lines must be separated by either a U+000D CARRIAGE RETURN U+000A
   LINE FEED (CRLF) character pair, a single U+000A LINE FEED (LF)
   character, or a single U+000D CARRIAGE RETURN (CR) character.<h4 id=event-stream-interpretation><span class=secno>7.2.4 </span>Interpreting an event stream</h4><p>Bytes or sequences of bytes that are not valid UTF-8 sequences

Received on Friday, 16 January 2009 22:48:34 UTC