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

Henrik Levkowetz <henrik@levkowetz.com> Thu, 04 October 2018 15:26 UTC

Return-Path: <henrik@levkowetz.com>
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 1B794130DFB for <xml2rfc-dev@ietfa.amsl.com>; Thu, 4 Oct 2018 08:26:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 EdvanuwGy99m for <xml2rfc-dev@ietfa.amsl.com>; Thu, 4 Oct 2018 08:26:00 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4591D130E48 for <xml2rfc-dev@ietf.org>; Thu, 4 Oct 2018 08:26:00 -0700 (PDT)
Received: from h-37-140.a357.priv.bahnhof.se ([94.254.37.140]:55498 helo=tannat.localdomain) by zinfandel.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1g85Vm-0002Df-Pc; Thu, 04 Oct 2018 08:25:59 -0700
To: Paul Hoffman <paul.hoffman@icann.org>
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> <1BA3E011-CEB3-4F56-9CB5-599C6D2D8A5D@icann.org> <2a71916e-4704-ef8c-b9bb-0cda1781c706@levkowetz.com> <2a06b7c8-5a84-60eb-c96e-25d07c61d67f@gmx.de> <4b49045f-49d7-2b01-bb57-087f8e014e5b@levkowetz.com> <32ef6fd2-058a-c44a-5129-26cd22343943@gmx.de> <a3d0816e-6cc0-dd11-9370-b391e3e71010@levkowetz.com> <c122b751-119d-9a10-a2b6-af90b140cfc8@gmx.de> <6c9785df-73c0-78ff-0c69-1ea1b369b0e0@levkowetz.com> <766a8834-4e7a-e819-6b76-2682eb99be9e@gmx.de> <81f488c3-1caf-a7cc-dc38-c39b3ca2ba5a@levkowetz.com> <2DE9A77A-0306-4F2E-B8D3-19D7915E73FC@icann.org> <6323b0e6-89bb-6cfa-866d-c4df7a42304d@levkowetz.com> <6DE6DADE-01EC-4978-9566-9D2250C408CC@icann.org> <5a12ef5f-06c8-8c68-a5d7-1e4ea255e8b3@levkowetz.com> <56828DC3-2038-450A-A98F-58D8F374B974@icann.org>
Cc: "xml2rfc-dev@ietf.org" <xml2rfc-dev@ietf.org>
From: Henrik Levkowetz <henrik@levkowetz.com>
Message-ID: <9fb8e2bb-13d5-1f9e-25cc-e13910fbbb29@levkowetz.com>
Date: Thu, 04 Oct 2018 17:25:50 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <56828DC3-2038-450A-A98F-58D8F374B974@icann.org>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="8fe75eq0CKEfSDALi5itJKghhM8GXq9I8"
X-SA-Exim-Connect-IP: 94.254.37.140
X-SA-Exim-Rcpt-To: xml2rfc-dev@ietf.org, paul.hoffman@icann.org
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on zinfandel.tools.ietf.org)
X-Clacks-Overhead: GNU Terry Pratchett
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/hASLfH3448T8uv4FyoXWmJ_zPuw>
Subject: Re: [xml2rfc-dev] [Ext] 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: Thu, 04 Oct 2018 15:26:05 -0000

On 2018-10-04 16:52, Paul Hoffman wrote:
> On Oct 4, 2018, at 7:34 AM, Henrik Levkowetz <henrik@levkowetz.com> wrote:
>> 
>> 
>> On 2018-10-04 16:25, Paul Hoffman wrote:
>>> On Oct 3, 2018, at 9:31 PM, Henrik Levkowetz <henrik@levkowetz.com> wrote:
>>>>> Because putting a <br> in running text prevents you from being able
>>>>> to search for the whole phrase. This was one of the explicit reasons
>>>>> to prevent them everywhere, and titles and section names are
>>>>> particularly important examples. You might search for a title of "of
>>>>> Generating Datagrams" but would never think of searching for "of
>>>>> Generating<br>Datagrams" or even . "of Generating <br>Datagrams"
>>>> 
>>>> I'm sorry, but I think this is incorrect.  In rendered context, whether
>>>> text/plain, text/html, or application/pdf, this would not be an issue --
>>>> the search tools would not see any <br> (in text and pdf because it
>>>> would not be part of the text; in html, because html search tools already
>>>> disregard html's <br>).
>>>> 
>>>> In the context of an editor, working on the xml, a phrase search is just
>>>> as likely to fail because the text has been broken across a line, and
>>>> contains multi-space indentation, which again would prevent an in-editor
>>>> phrase search.  This is a reality I live with every day ,:-)
>>> 
>>> Neither of those is what I was referring to: I was referring to searching the corpus of RFCs or Internet Drafts.
>> 
>> Using which search tool?
> 
> grep for now, hopefully something more formal later when the corpus has more XML.

In that case, if you want to do phrase searches, you'll still have to deal
with these elements embedded in the phrase: 

  bcp14, cref, em, eref, iref, list, relref, strong, sub, sup, tt, xref

(I've excluded some deprecated elements).  Adding <br> to the set doesn't
seem to make any difference to how you have to write your grep expression,
and the same thing would go for a future custom search tool.


	Henrik