Editing Metasyntax (section)

==Specific metasyntax conventions==

===The standard convention===
* '[[Backus–Naur form]]' denotes [[nonterminal symbol]]s by angle bracketing the name of the [[syntactic category]], while it denotes [[terminal symbol]]s by double quoting the terminal words. Terminals can never appear on the left-hand side of the metasymbol {{code|::{{=}}}} in a [[Parse tree|derivation]] rule. The body of the definition on the right-hand side may be composed with several alternative forms with each alternative syntactic construct being separated by the metasymbol {{code|{{!}}}}. Each of these alternative construct may be either terminal or nonterminal.
* '[[Extended Backus–Naur form]]' uses all facilities in BNF and introduces two more metasymbols for additional features. One of these two new features is applied to denote an optional phrase in a statement by square bracketing the optional phrase. The second feature is applied to denote a phrase that is to be repeated zero or more times by curly bracketing the phrase.
* '[[Wirth syntax notation]]' uses all facilities in EBNF except that the nonterminals are not necessarily angle bracketed but are always defined on the right-hand side of {{code|{{=}}}} in its production rule. It also does not require every nonterminal to be explicitly defined. Nonterminals such as {{code|<text>}} and {{code|<opt-whitespace>}} are implicitly defined as ASCII-character and optional white space respectively.
* '[[Augmented Backus–Naur form]]' denotes nonterminal symbols by starting a one-word-name with an alphabet as the name of the syntactic category. Angle brackets are not required. Terminal symbols are either denoted by double quoted words or denoted by the following numeric structure: a {{code|%}}, followed by {{code|b}} or {{code|x}} or {{code|d}}, followed by a numeric value or a ''concatenation of numeric values'' separated by {{code|.}}. Metasymbol {{code|-}} is placed between two numeric values to denote ''value range''. As that of BNF, the terminals of ABNF never occurs on the left-hand-side of the metasymbol {{code|{{=}}}} in the derivation rule. Metasymbol {{code|/}} denotes ''alternations''. White space is used to separate elements in the body of the definition. The metasyntax for ''repetition'' in ABNF has several forms. A {{code|*}} preceding an element denotes the element to be repeated zero or more times. Numeric value {{var|n1}} followed by {{code|*}} followed by numeric value {{var|n2}} followed by an element denotes the element to be repeated at least {{var|n1}} times and at most {{var|n2}} times. A single numeric value {{var|n}} preceding an element denotes the element to be repeated {{var|n}} times. ''Comments'' may be express after metasymbol {{code|;}}. As in EBNF, square bracketing a phrase denotes the phrase to be ''optional''.

===Variations===
The metasyntax convention of these formal metalanguages are not yet formalized. Many metasyntactic variations or extensions exist in the reference manual of various computer programming languages. One variation to the standard convention for denoting nonterminals and terminals is to remove metasymbols such as angle brackets and quotations and apply ''font types'' to the intended words. In [[Ada (programming language)|Ada]], for example, syntactic categories are denoted by applying lower case [[sans-serif font]] on the intended words or symbols. All terminal words or symbols, in Ada, consist of characters of code position between {{mono|16#20#}} and {{mono|16#7E#}} (inclusive). The definition for each character set is referred to the International Standard described by [[ISO/IEC]] 10646:2003. In [[C (programming language)|C]] and [[Java (programming language)|Java]], syntactic categories are denoted using [[italic font]] while terminal symbols are denoted by [[sans-serif|gothic]] font. In [[J (programming language)|J]], its metasyntax does not apply metasymbols to describe J's syntax at all. Rather, all syntactic explanations are done in a metalanguage very similar to English called Dictionary, which is uniquely documented for J.

===Advantage of the extensions===
The purpose of the new extensions is to provide a simpler and unambiguous metasyntax. In terms of simplicity, BNF's metanotation definitely does not help to make the metasyntax easier-to-read as the open-end and close-end metasymbols appear too abundantly. In terms of ambiguity, BNF's metanotation generates unnecessary complexity when quotation marks, apostrophes, less-than signs or greater-than signs come to serve as terminal symbols, which they often do. The extended metasyntax utilizes properties such as case, font, and code position of characters to reduce unnecessary aforementioned complexity. Moreover, some metalanguages use fonted separator categories to incorporate metasyntactic features for layout conventions, which are not formally supported by BNF.