RFC 4234, "Augmented BNF for Syntax Specifications: ABNF", October 2005
Note: This RFC has been obsoleted by RFC 5234Source of RFC: IETF - NON WORKING GROUP
Area Assignment: app
Errata ID: 783
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2005-10-13
Rejected by: Peter Saint-Andre
Date Rejected: 2010-11-18
The following clarifications apply to the meta-grammar in section 4. a) Near the bottom of page 10, the rule: repetition = [repeat] element should say: | repetition = ( [repeat] element ) / option At the top of page 11, the rule: element = rulename / group / option / char-val / num-val / prose-val should say: | element = rulename / group / char-val / num-val / prose-val These changes have the effect to formally disallow a <repeat> element in front of an <option> -- a senseless construct formerly unexpectedly allowed. b) On page 11, the last rule: prose-val = "<" *(%x20-3D / %x3F-7E) ">" ; bracketed string of SP and VCHAR ; without angles ; prose description, to be used as ; last resort should say: prose-val = "<" *(%x20-3D / %x3F-7E) ">" | ; bracketed string of: | ; SP and VCHAR without closing angle ; prose description, to be used as ; last resort This change aligns the comment with the formal rule.
It should say:
Peter: The authors have consensus that these are stylistic issues and therefore are not errors.