Constrained ABNF
draft-seantek-constrained-abnf-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Sean Leonard , Paul Kyzivat | ||
| Last updated | 2017-09-14 (Latest revision 2017-03-13) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document extends the base definition of ABNF (Augmented Backus- Naur Form) to express a rule that is constrained by another rule. If a rule B is constrained by rule A, then every production generated by rule B must also be generated by rule A. By creating subordinate production forms, ABNF-using specifications can formally denote the relationship between a general rule and specific subsets of that rule, while preserving ABNF's context-free nature.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)