IETF Logo Mail Archive

Re: [xml2rfc-dev] RFC 7991 issue #37: Schema Issue, RFC 7991, In Section 2.12, <br>

Miek Gieben <miek@miek.nl> Tue, 02 October 2018 18:03 UTC

Return-Path: <miek@miek.nl>
X-Original-To: xml2rfc-dev@ietfa.amsl.com
Delivered-To: xml2rfc-dev@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61C95130FF8 for <xml2rfc-dev@ietfa.amsl.com>; Tue, 2 Oct 2018 11:03:12 -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, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=miek-nl.20150623.gappssmtp.com
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 Rx-Tnt1u85no for <xml2rfc-dev@ietfa.amsl.com>; Tue, 2 Oct 2018 11:03:10 -0700 (PDT)
Received: from mail-wm1-x334.google.com (mail-wm1-x334.google.com [IPv6:2a00:1450:4864:20::334]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3169F130EF5 for <xml2rfc-dev@ietf.org>; Tue, 2 Oct 2018 11:03:09 -0700 (PDT)
Received: by mail-wm1-x334.google.com with SMTP id z25-v6so5910949wmf.1 for <xml2rfc-dev@ietf.org>; Tue, 02 Oct 2018 11:03:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=miek-nl.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=SL5tm/AtLDiHbwWAOoAILL+Qw8bbDjN3beMhVHAsCho=; b=eZnKd50j1SQxXAV/ZpbxRjYCKwIxp09Xpye6qMpv/hdOeBLyioajbV80ffl7RfVKTB jlL6H+t42JxOQ9/ZF/8GXl4nNdXtCObNtHcCIyx6a3Q49HCv6iVi6uOlXu3Z1SQ0XMgp 9iCYuBRjqyBWQUod+o3Rk264IfBwrz1qCA7lMh44RnCcDLD0HXvaiUxmOlfb/e7Se61A gPWjpotHqdWLkP/PcS6XGooC/+/TPVFWJKmfiHH/5ozqCdTEXAUMrsz+/b7t6i2KM/tI 8GcNom4+vtvppnsbidODrmnBQIJFpzqkJlpQ3JbKr0IE41Q/y4uuqDHr92HQhYTnN9uN zKFA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=SL5tm/AtLDiHbwWAOoAILL+Qw8bbDjN3beMhVHAsCho=; b=ABb7xMGOqweMk0AJ0zYQTfChFKwjMiZhWzbOVnhu+vx9yUr9Gc/lw2z/K8o2Q85pcb MQZpTmjcds25VGgwaPAhO1VcChFcspA7GFl9AXwQQtdmQcYhEWcpv6Dzto6ZghEG+Brq +flH8AYuVkY1wjSk8hYpCdW/enw4T9vckMC1hPBO9XphkhE8ssWR17sGUYBKtcGWFIVF NPt57bxMHy8ByxDmgmvHuUM5ALb/ciwyZ8gHEnVlpwh22yDIYTc1vliPCt5pol5FzaiC FwptY+aebqQncmOVYdhvgBD2xvHazmf6vwLcz3BxDS6t+D5/turUK0my6jjVWK/ft5CQ ZO6A==
X-Gm-Message-State: ABuFfogt+av4+STqXqje3ZYGwVpvjVHYVorYhkoWQnJHwEqC5Tqzu3lc 8I5EdfOxRDRs0BMFnX+CI9X8UAOTS24=
X-Google-Smtp-Source: ACcGV61KNqsl4AhmNAN9jMqrclxdg9iCW/kgITjUy8kMYYPQzR2cj76oHyzd3MbwvuuAz3khD9T/zA==
X-Received: by 2002:a1c:a90:: with SMTP id 138-v6mr2718641wmk.49.1538503387439; Tue, 02 Oct 2018 11:03:07 -0700 (PDT)
Received: from miek.nl (4.3.8.0.6.9.c.b.e.5.6.a.1.b.f.a.f.3.c.4.9.5.f.b.0.b.8.0.1.0.0.2.ip6.arpa. [2001:8b0:bf59:4c3f:afb1:a65e:bc96:834]) by smtp.gmail.com with ESMTPSA id o13sm4574103wrx.53.2018.10.02.11.03.06 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 02 Oct 2018 11:03:06 -0700 (PDT)
Date: Tue, 02 Oct 2018 19:03:04 +0100
From: Miek Gieben <miek@miek.nl>
To: Paul Hoffman <paul.hoffman@icann.org>
Cc: "xml2rfc-dev@ietf.org" <xml2rfc-dev@ietf.org>
Message-ID: <20181002180304.nsrwbvpcesb4ozrd@miek.nl>
References: <E1g6wQ8-00057n-85@durif.tools.ietf.org> <70ee4cff-7533-13e0-d71a-ffecf2dc56f0@gmx.de> <24828f94-dbbd-4c18-8d85-333487bda367@levkowetz.com> <3ac63652-2df2-03c7-eee6-bad2cbd326d8@levkowetz.com> <B63F3A7C-AAB6-4281-BC5F-BC28E9693E43@icann.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Disposition: inline
In-Reply-To: <B63F3A7C-AAB6-4281-BC5F-BC28E9693E43@icann.org>
User-Agent: Vim/Mutt/Linux
X-Home: http://www.miek.nl
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/pgwLF3Lor1uo8riGEt6QdruqkWE>
Subject: Re: [xml2rfc-dev] RFC 7991 issue #37: Schema Issue, RFC 7991, In Section 2.12, <br>
X-BeenThere: xml2rfc-dev@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." <xml2rfc-dev.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc-dev/>
List-Post: <mailto:xml2rfc-dev@ietf.org>
List-Help: <mailto:xml2rfc-dev-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Oct 2018 18:03:13 -0000

[ Quoting <paul.hoffman@icann.org> in "Re: [xml2rfc-dev] RFC 7991 issue #3..." ]
>I just thought of something different that might deal with Miek's issue: change the name of the element to <tbr>. That will prevent people who "know" what <br> "means" from expecting it to work because <br> doesn't exist.
>
>If, later, we want to add <br> for running text (with lots of description of what it will and will not do to displayed RFCs), we can do so then.

What's the problem for just allowing it ~everywhere (ala HTML); and go by the motto: garbage in; garbage out?

I wonder who can honestly say that they can write 7991 XML *without* having the 
spec next to them.

v2.23.0 | Report a Bug | By Email