11669 2011-01-05 09:41:28 +0000 Section: "Parsing an event stream" It looks like their is a mistake in this ABNF description, "end-of-line" is repeated: stream = [ bom ] *event event = *( comment / field ) end-of-line comment = colon *any-char end-of-line field 2011-02-07 22:37:11 +0000 1 1 1 Unclassified WebAppsWG HISTORICAL - Server-Sent Events (editor: Ian Hickson) unspecified Other other RESOLVED WONTFIX http://www.whatwg.org/specs/web-apps/current-work/#top P3 normal --- 1 contributor ian alexandre.morgaut ian mike public-webapps alexandre.morgaut oldest_to_newest 43818 0 contributor 2011-01-05 09:41:28 +0000 Specification: http://dev.w3.org/html5/eventsource/ Section: http://www.whatwg.org/specs/web-apps/current-work/complete.html#top Comment: Section: "Parsing an event stream" It looks like their is a mistake in this ABNF description, "end-of-line" is repeated: 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 = < matches repeatedly at the end of the stream > If "end-of-line" is set at the end of the "event" description, it shouldn't be repeated at the end of the "comment" and "field" descriptions. "eof" could be proposed as an alternative of "end-of-line" instead of being part of the "end-of-line" description Update proposal: stream = [ bom ] *event event = *( comment / field ) (end-of-line / eof) comment = colon *any-char field = 1*name-char [ colon [ space ] *any-char ] end-of-line = ( cr lf / cr / lf ) eof = < matches repeatedly at the end of the stream > Posted from: 81.57.192.30 45200 1 ian 2011-02-07 22:37:11 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: no spec change Rationale: It's repeated because <event>s are separated from each other by a blank line. Your proposed BNF puts all the comments and fields on one line, which is unparseable.