[abnf-discuss] Core Rules and References for ABNF: draft-seantek-abnf-more-core-rules-07.txt
Sean Leonard <dev+ietf@seantek.com> Wed, 28 September 2016 22:19 UTC
Return-Path: <dev+ietf@seantek.com>
X-Original-To: abnf-discuss@ietfa.amsl.com
Delivered-To: abnf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D1A2412B00D for <abnf-discuss@ietfa.amsl.com>; Wed, 28 Sep 2016 15:19:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KVRn7bQvmfUh for <abnf-discuss@ietfa.amsl.com>; Wed, 28 Sep 2016 15:19:08 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BD96012B0DE for <abnf-discuss@ietf.org>; Wed, 28 Sep 2016 15:19:08 -0700 (PDT)
Received: from [192.168.123.7] (unknown [75.83.2.34]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id AE71B509B6 for <abnf-discuss@ietf.org>; Wed, 28 Sep 2016 18:19:07 -0400 (EDT)
References: <147504900383.16692.17822159531322398069.idtracker@ietfa.amsl.com>
To: "abnf-discuss@ietf.org" <abnf-discuss@ietf.org>
From: Sean Leonard <dev+ietf@seantek.com>
X-Forwarded-Message-Id: <147504900383.16692.17822159531322398069.idtracker@ietfa.amsl.com>
Message-ID: <0946bd36-29a4-0787-8b3f-663549fa2406@seantek.com>
Date: Wed, 28 Sep 2016 15:20:49 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0
MIME-Version: 1.0
In-Reply-To: <147504900383.16692.17822159531322398069.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/abnf-discuss/Jd_CP6aNAWdJFp1cT3gq6Zseaek>
Subject: [abnf-discuss] Core Rules and References for ABNF: draft-seantek-abnf-more-core-rules-07.txt
X-BeenThere: abnf-discuss@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "General discussion about tools, activities and capabilities involving the ABNF meta-language" <abnf-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/abnf-discuss>, <mailto:abnf-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/abnf-discuss/>
List-Post: <mailto:abnf-discuss@ietf.org>
List-Help: <mailto:abnf-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/abnf-discuss>, <mailto:abnf-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Sep 2016 22:19:11 -0000
Hello ABNF-discuss: A new draft of Comprehensive Core Rules and References for ABNF has been posted. Thanks in advance to all those who have provided feedback thus far. In this draft-07 (and draft-06, which had some typos and unclear parts that have since been addressed), the syntax for a "referenced rule" is rulename@RULEREF, where RULEREF can be a document such as URI@[RFC3986] or a path such as name-part@<https://raw.githubusercontent.com/antlr/grammars-v4/master/abnf/examples/postal.abnf> . The syntax has evolved a similar way to how e-mail addresses have evolved (e.g., from RFC 733). There was material about doing Unicode in ABNF in draft-05 (Appendix B); that material has been forked to a different draft (under development). Comments and feedback are welcome. Best regards, Sean -------- Forwarded Message -------- Subject: New Version Notification for draft-seantek-abnf-more-core-rules-07.txt Date: Wed, 28 Sep 2016 00:50:03 -0700 From: internet-drafts@ietf.org A new version of I-D, draft-seantek-abnf-more-core-rules-07.txt has been successfully submitted by Sean Leonard and posted to the IETF repository. Name: draft-seantek-abnf-more-core-rules Revision: 07 Title: Comprehensive Core Rules and References for ABNF Document date: 2016-09-28 Group: Individual Submission Pages: 10 URL: https://www.ietf.org/internet-drafts/draft-seantek-abnf-more-core-rules-07.txt Status: https://datatracker.ietf.org/doc/draft-seantek-abnf-more-core-rules/ Htmlized: https://tools.ietf.org/html/draft-seantek-abnf-more-core-rules-07 Diff: https://www.ietf.org/rfcdiff?url2=draft-seantek-abnf-more-core-rules-07 Abstract: This document extends the base definition of ABNF (Augmented Backus- Naur Form) to include a reference syntax, along with core rules that provide comprehensive support for certain symbols related to ASCII. Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. The IETF Secretariat
- [abnf-discuss] Core Rules and References for ABNF… Sean Leonard
- Re: [abnf-discuss] Core Rules and References for … Paul Kyzivat
- Re: [abnf-discuss] Core Rules and References for … John Levine
- Re: [abnf-discuss] Core Rules and References for … Paul Kyzivat
- Re: [abnf-discuss] Core Rules and References for … John Levine
- Re: [abnf-discuss] Core Rules and References for … Julian Reschke