W3C home > Mailing lists > Public > public-html-diffs@w3.org > January 2009

spec/Overview.html 1.1845 2675 Replace fake BNF with real ABNF. (whatwg

From: poot <cvsmail@w3.org>
Date: Fri, 16 Jan 2009 11:01:28 +0900 (JST)
To: public-html-diffs@w3.org
Message-Id: <20090116020128.802FE2BC9D@toro.w3.mag.keio.ac.jp>

Replace fake BNF with real ABNF. (whatwg r2675)

7.2.4 Interpreting an event stream
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1845.html#event-stream-interpretation
7.2.3 Parsing an event stream
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1845.html#parsing-an-event-stream
last event ID string
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1845.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.1845.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.1844&r2=1.1845&f=h
http://html5.org/tools/web-apps-tracker?from=2674&to=2675

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.1844
retrieving revision 1.1845
diff -u -d -r1.1844 -r1.1845
--- Overview.html	16 Jan 2009 01:45:40 -0000	1.1844
+++ Overview.html	16 Jan 2009 01:58:32 -0000	1.1845
@@ -8370,18 +8370,21 @@
   contents of the <code><a href=#script>script</a></code> element, if any, must be such
   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>documentation</code> production in the following ABNF. <a href=#references>[ABNF]</a></p><!-- XXX
+  <code title="">documentation</code> production in the following
+  ABNF. <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-star      ::= &lt; a single Unicode character other than a U+002A ASTERISK character &gt;
-not-slash     ::= &lt; a single Unicode character other than a U+002F SOLIDUS character &gt;
-not-newline   ::= &lt; a single Unicode character other than a U+000A LINE FEED character &gt;</pre><div class=example>
+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>
 
    <p>This allows authors to include documentation, such as license
    information or API information, inside their documents while still
@@ -35517,25 +35520,24 @@
   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 (in pseudo-BNF):<pre>&lt;stream&gt;          ::= &lt;bom&gt;? &lt;event&gt;*
-&lt;event&gt;           ::= [ &lt;comment&gt; | &lt;field&gt; ]* &lt;newline&gt;
-&lt;comment&gt;         ::= &lt;colon&gt; &lt;any-char&gt;* &lt;newline&gt;
-&lt;field&gt;           ::= &lt;name-char&gt;+ [ &lt;colon&gt; &lt;space&gt;? &lt;any-char&gt;* ]? &lt;newline&gt;
+  <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
+  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>
 
-# characters:
-&lt;bom&gt;             ::= a single U+FEFF BYTE ORDER MARK character
-&lt;space&gt;           ::= a single U+0020 SPACE character (' ')
-&lt;newline&gt;         ::= a U+000D CARRIAGE RETURN character
-                      followed by a U+000A LINE FEED character
-                      | a single U+000D CARRIAGE RETURN character
-                      | a single U+000A LINE FEED character
-                      | the end of the file
-&lt;colon&gt;           ::= a single U+003A COLON character (':')
-&lt;name-char&gt;       ::= a single Unicode character other than
-                      U+003A COLON, U+000D CARRIAGE RETURN and U+000A LINE FEED
-&lt;any-char&gt;        ::= a single Unicode character other than
-                      U+000D CARRIAGE RETURN and U+000A LINE FEED
-</pre><p>Event streams in this format must always be encoded as
+; 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
   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 02:02:06 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 06:13:57 GMT