D. Crocker, and P. Overell. RFC, 2234. Internet Engineering Task Force, (November 1997)
Abstract
Internet technical specifications often need to define a
format syntax and are free to employ whatever notation their authors
deem useful. Over the years, a modified version of Backus-Naur Form
(BNF), called Augmented BNF (ABNF), has been popular among many Internet
specifications. It balances compactness and simplicity, with reasonable
representational power. In the early days of the Arpanet, each
specification contained its own definition of ABNF. This included the
email specifications, RFC733 and then RFC822 which have come to be the
common citations for defining ABNF. The current document separates out
that definition, to permit selective reference.
%0 Report
%1 rfc2234
%A Crocker, D.
%A Overell, P.
%D 1997
%K imported
%N 2234
%P 14
%T Augmented BNF for Syntax Specifications: ABNF
%U http://www.rfc-editor.org/rfc/rfc2234.txt
%X Internet technical specifications often need to define a
format syntax and are free to employ whatever notation their authors
deem useful. Over the years, a modified version of Backus-Naur Form
(BNF), called Augmented BNF (ABNF), has been popular among many Internet
specifications. It balances compactness and simplicity, with reasonable
representational power. In the early days of the Arpanet, each
specification contained its own definition of ABNF. This included the
email specifications, RFC733 and then RFC822 which have come to be the
common citations for defining ABNF. The current document separates out
that definition, to permit selective reference.
@techreport{rfc2234,
abstract = {Internet technical specifications often need to define a
format syntax and are free to employ whatever notation their authors
deem useful. Over the years, a modified version of Backus-Naur Form
(BNF), called Augmented BNF (ABNF), has been popular among many Internet
specifications. It balances compactness and simplicity, with reasonable
representational power. In the early days of the Arpanet, each
specification contained its own definition of ABNF. This included the
email specifications, RFC733 and then RFC822 which have come to be the
common citations for defining ABNF. The current document separates out
that definition, to permit selective reference.},
added-at = {2007-05-29T15:45:23.000+0200},
author = {Crocker, D. and Overell, P.},
biburl = {https://www.bibsonomy.org/bibtex/202f0847efffdf3eb0ab24584e5cbcc78/yeah},
days = {15},
description = {My Master Thesis bibliography},
institution = {Internet Engineering Task Force},
interhash = {641c56a7c9a5a7cf046f4ee41c318f76},
intrahash = {02f0847efffdf3eb0ab24584e5cbcc78},
keywords = {imported},
month = {November},
number = 2234,
pages = 14,
timestamp = {2007-05-29T15:45:24.000+0200},
title = {Augmented {BNF} for Syntax Specifications: {ABNF}},
type = {RFC},
url = {http://www.rfc-editor.org/rfc/rfc2234.txt},
year = 1997
}