Re: [Xml-sg-cmt] Proposed message to rfc-interest about <postal>

John R Levine <johnl@taugh.com> Thu, 10 June 2021 23:43 UTC

Return-Path: <johnl@taugh.com>
X-Original-To: xml-sg-cmt@ietfa.amsl.com
Delivered-To: xml-sg-cmt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0AFD43A1F3F for <xml-sg-cmt@ietfa.amsl.com>; Thu, 10 Jun 2021 16:43:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=wO6F0Coz; dkim=pass (2048-bit key) header.d=taugh.com header.b=FzIG0Ah2
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 YV2lth8ys8sN for <xml-sg-cmt@ietfa.amsl.com>; Thu, 10 Jun 2021 16:43:34 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 D8DAB3A1F3C for <xml-sg-cmt@ietf.org>; Thu, 10 Jun 2021 16:43:33 -0700 (PDT)
Received: (qmail 10850 invoked from network); 10 Jun 2021 23:43:30 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:references:mime-version:content-type; s=2a60.60c2a3a2.k2106; bh=NSQvWqQV4b9b/3k2nwm4iwHodKaHAuJhfnF5HxZaJkc=; b=wO6F0Coz7Hh1Q84laop3hwVT60xc43z1aLtq7g3IqP8oFPo77hP90cb8MpzxqPJ1FL/H3Ncce8ibKAl8QeQhTvE40OzGJxpTNvmwBUQoPo0TWNdu+Jrr9nXsofqcu22eTRKFYFSwJgkgqJ5VNxBwfdVjStYYgBUANvtp1piGkdUZumQosLdnnZgt1DN9qDV/c6nKhq63TgoFwPKNYsp2gRLihU8Bpyup9jxpWazBfkPl2m1tPGWgunogb+6mW5l+oTreLiK5aQVVTCuYGt51Tb4J5uLUzXxTPJxuiTm9QNFgjpfwddCGI0/nRWwrRmS3DawcFrD6HVawKAsECH28Jw==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:references:mime-version:content-type; s=2a60.60c2a3a2.k2106; bh=NSQvWqQV4b9b/3k2nwm4iwHodKaHAuJhfnF5HxZaJkc=; b=FzIG0Ah21+d/H9QYXB0n8skDmEKUljqebM6SLquCts6ogRsWc0rNhAujaKpNyaakLvk/zo6X1bNlbIn7fKvGGHpdUvHD7bvMSxtwe+Kju2MJS0bRVWx1GF/eJ1VzGTuh3xrv7tjkDnHuPlo/AiSgDziauLW2vcUT0SDQ7LjTqPziBzpYMTDphi5TrmCuewu5U2nTqH7LqDCiJGXlYAffzVFsaXklBn82bA39EW/77It4N3Go7MCyIC24sx6LfEa3uZCn81TB8ndpMJi0I2kQkHK/jyxHZkz/xsB5HafHPzEWiSv0StQ7Yatp7Td3n1ADW76SbZfRt6SDicGqBHcn8Q==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 10 Jun 2021 23:43:30 -0000
Received: by ary.qy (Postfix, from userid 501) id BA2A3ECB560; Thu, 10 Jun 2021 19:43:29 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by ary.qy (Postfix) with ESMTP id 67149ECB540; Thu, 10 Jun 2021 19:43:29 -0400 (EDT)
Date: Thu, 10 Jun 2021 19:43:29 -0400
Message-ID: <7bd32d5e-7015-c74-2166-409bbe86ce3f@taugh.com>
From: John R Levine <johnl@taugh.com>
To: Peter Saint-Andre <stpeter@mozilla.com>, XML weed whackers <xml-sg-cmt@ietf.org>
X-X-Sender: johnl@ary.qy
In-Reply-To: <2b5e77dc-908d-7474-6da2-62e69156efd9@mozilla.com>
References: <3e9aa251-9e18-69cf-be4c-94b63532db7e@taugh.com> <96fac2e8-5a65-eb13-33f6-f52ef582a411@levkowetz.com> <2b5e77dc-908d-7474-6da2-62e69156efd9@mozilla.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml-sg-cmt/ZiHkBoJBIj-36RKxB0KZUAEZly8>
Subject: Re: [Xml-sg-cmt] Proposed message to rfc-interest about <postal>
X-BeenThere: xml-sg-cmt@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Working list for the xml and style guide change management team <xml-sg-cmt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml-sg-cmt>, <mailto:xml-sg-cmt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml-sg-cmt/>
List-Post: <mailto:xml-sg-cmt@ietf.org>
List-Help: <mailto:xml-sg-cmt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml-sg-cmt>, <mailto:xml-sg-cmt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Jun 2021 23:43:40 -0000

> After discussion on Monday I think that's no longer the direction we'd
> prefer. :-)
>
> John, your message looks good to me.

OK, will send it.

>
> Peter
>
> On 6/7/21 9:49 AM, Henrik Levkowetz wrote:
>> Hi John,
>>
>> I believe we also said we'd permit <country/> as a sibling to <postal/> in
>> the schema, so that we later could deprecate and remove <postal/> entirely,
>> but still keep <country/>.
>>
>> 	Henrik
>>
>> On 2021-06-06 23:56, John R Levine wrote:
>>> Here's what I plan to send out, with bits borrowed from Peter:
>>>
>>> One of the changes to the xml v3 grammar since RFC 7991 is a new <postal>
>>> element with a set of subfields such as <street>, <region>, and <code>. To
>>> render addresses we use a python library that depends on an open source address
>>> database originally from Google.  While tracking down a rendering bug, we found
>>> that the rendering database is not actively maintained and has a long list of
>>> unresolved pull requests.  We don't know of any other source of rendering
>>> patterns.
>>>
>>> But we don't see a strong reason for readers to need the full postal address
>>> for RFC authors. Anecdotally, on rare occasions readers have used the postal
>>> address but (a) the email address is primary since <postal/> is optional and
>>> (b) readers likely have better ways to find contact information for RFC
>>> authors.
>>>
>>> The one part we care most about from <postal/> is <country/>.  This enables
>>> people to do things like gather statistics about where RFCs originate, such as
>>> https://www.arkko.com/tools/rfcstats/d-countrydistr.html
>>>
>>> Our proposal is to deprecate all of the <postal> elements other than the
>>> <country/> element.  Authors can include them if they want, but they won't be
>>> rendered and the RPC won't ask for them.  We think this leaves the useful bit
>>> of info while avoiding a lot of work for minimal benefit.
>>>
>>> If there are issues we've missed, please let us know.
>>>
>>> R's,
>>> John
>>>
>>
>>
>
>

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly