Re: [abnf-discuss] Core Rules and References for ABNF: draft-seantek-abnf-more-core-rules-07.txt

"John Levine" <johnl@taugh.com> Thu, 29 September 2016 22:09 UTC

Return-Path: <johnl@taugh.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 3C44712B2F2 for <abnf-discuss@ietfa.amsl.com>; Thu, 29 Sep 2016 15:09:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_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 vnm-pF0ikZBu for <abnf-discuss@ietfa.amsl.com>; Thu, 29 Sep 2016 15:09:36 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2D5BC12B23B for <abnf-discuss@ietf.org>; Thu, 29 Sep 2016 15:09:36 -0700 (PDT)
Received: (qmail 43510 invoked from network); 29 Sep 2016 22:09:33 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 29 Sep 2016 22:09:33 -0000
Date: Thu, 29 Sep 2016 22:09:13 -0000
Message-ID: <20160929220913.13571.qmail@ary.lan>
From: John Levine <johnl@taugh.com>
To: abnf-discuss@ietf.org
In-Reply-To: <4b7a37a5-2bc3-1991-1b6f-8d9e79636626@alum.mit.edu>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/abnf-discuss/iw6w9zydB57oRxpgZAY0xw0c51w>
Cc: pkyzivat@alum.mit.edu
Subject: Re: [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: Thu, 29 Sep 2016 22:09:38 -0000

>How is:
>
>	URI = URI@[RFC3986]
>
>more "glopped up" than:
>
>	URI = <URI defined in RFC3986>

It's not.  I want the XML to say something like this:

<abnf name="URI" source="RFC3986" />

and the way it's displayed depends on the output medium.

>If you want to literally include the external ABNF, and have it 
>displayed in the document, then you can use an xml include.

I suppose so, but that's not what I was trying to say.

>But the semantics we are going for here are not that. It is important 
>for the *reader* to understand what is being imported, and from where. 
>If you stick it in the XML then it isn't visible to the reader.

You're making some unwarranted assumptions about the way the XML is
processed.  Most of what's in the XML is visible to the reader.

R's,
John