IETF Logo Mail Archive

Re: [Xml-sg-cmt] contact element

Peter Saint-Andre <stpeter@mozilla.com> Mon, 10 May 2021 21:56 UTC

Return-Path: <stpeter@mozilla.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 248E53A2C87 for <xml-sg-cmt@ietfa.amsl.com>; Mon, 10 May 2021 14:56:24 -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, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mozilla.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 PvWqPAYZjiCV for <xml-sg-cmt@ietfa.amsl.com>; Mon, 10 May 2021 14:56:22 -0700 (PDT)
Received: from mail-io1-xd2e.google.com (mail-io1-xd2e.google.com [IPv6:2607:f8b0:4864:20::d2e]) (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 448FB3A2C85 for <xml-sg-cmt@ietf.org>; Mon, 10 May 2021 14:56:21 -0700 (PDT)
Received: by mail-io1-xd2e.google.com with SMTP id d24so6393753ios.2 for <xml-sg-cmt@ietf.org>; Mon, 10 May 2021 14:56:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mozilla.com; s=google; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=EsROb9e6n1XBuqjEdw58QLYwZeSbljo6FMYVKDbQ2Vc=; b=Im7S1xwF0XXwa4mQrqXBFRoNPt8TjPz4TenhDEALbTVHUltlQCzeiABO7x0afNRIeh KX3UYYVhHH/+yTpMoh2clcM3WeBhQt6h7H5b/uteduLBVFeQrnLZOumAZT025rJfnAkC ctyuBAHwCLi8fn1ftMmncWs/71lVjR9y6iKGE=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=EsROb9e6n1XBuqjEdw58QLYwZeSbljo6FMYVKDbQ2Vc=; b=EUZX7xHJccQ6GXr9OrDmDUaGe7MWNpScpAabmpIXcXN9/sZTt1q9TfyRTK3hn9rq2k iTPcB3mACZtKIK1CzbK20SYZNIahtteMWPAnTjJpxmUzAO4f3g/NuU71B92ZWi/NhFaF 0B6tH+Gq0LYRO20gfB6+JRpj0qvX0gssi4zdd56rtOQAAk2E1SqrwsB/NVvVDfVxHRtj lg5ntm5xs5vlUpaKK3b+f+IJ+reHr9bDwiU07tn1MsCadcuNegG5Q8M8V4oJeMLYBTo3 xWZTZgNCCfPSKRdiYWYMtA0LB3U4gPSI5XeB+mxk7oHzTpCAiebw/GW/zTIEqrJbgHNj FJlA==
X-Gm-Message-State: AOAM530bdbEEVCLlBNr0QAKor/TlSfdhCFQ7wSqJJlhYe1pKBihVoc0E /M+K66g23cXmB3F4lh7yAooI2Q==
X-Google-Smtp-Source: ABdhPJxoIlvCT8uiW7vP9rSlgr7EiKH/QW3FFVUdtloe1YLEmKzbIoVJ8o4HE+pq+mAldybTlgJf+Q==
X-Received: by 2002:a02:a388:: with SMTP id y8mr13354934jak.26.1620683780528; Mon, 10 May 2021 14:56:20 -0700 (PDT)
Received: from dragon.local (c-73-78-113-156.hsd1.co.comcast.net. [73.78.113.156]) by smtp.gmail.com with ESMTPSA id f11sm7053691iov.9.2021.05.10.14.56.19 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 10 May 2021 14:56:20 -0700 (PDT)
To: Sandy Ginoza <sginoza@amsl.com>
Cc: XML weed whackers <xml-sg-cmt@ietf.org>, John R Levine <johnl@taugh.com>
References: <777df480-1462-ea6d-2d40-deae7db4256b@mozilla.com> <fa413435-7154-2f6d-88ef-9036ed356c46@taugh.com> <237CB7B6-C6A7-43BE-BFD6-349C3B7B74CE@amsl.com> <39d4d6eb-db7f-63db-e505-6c69268f543e@mozilla.com> <A2ED6098-6AB8-4D25-8859-92A7E36DCEA5@amsl.com> <AC4643E5-6A74-4838-8E79-8C7633E55585@amsl.com> <44541e6d-ce08-d531-424d-7d57fb5195d1@mozilla.com> <05F2AB3A-EEB5-412E-89CE-681B328D50FB@amsl.com>
From: Peter Saint-Andre <stpeter@mozilla.com>
Message-ID: <0a8914d2-12c5-4d71-5429-8859fde3ca4c@mozilla.com>
Date: Mon, 10 May 2021 15:56:18 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.10.1
MIME-Version: 1.0
In-Reply-To: <05F2AB3A-EEB5-412E-89CE-681B328D50FB@amsl.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml-sg-cmt/aX7ljKBpJZFugKF_dFtXsoAZzvU>
Subject: Re: [Xml-sg-cmt] contact element
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: Mon, 10 May 2021 21:56:24 -0000

On 5/10/21 3:13 PM, Sandy Ginoza wrote:
> You’re still incredibly fast with your replies! 

I'm either incredibly fast or incredibly slow. Not much in between. :-)

>> On May 10, 2021, at 1:30 PM, Peter Saint-Andre <stpeter@mozilla.com> wrote:
>>
>> That's a lot of contacts. :-)
>>
>> Do we even have contact information for everyone who submitted position
>> papers?
> 
> No, but we don’t necessarily have contact info for the individuals listed in the other sections either.
> That said, I’m thinking that not using <contact> here makes sense in that a reader could go to the relevant reference and get the info from the paper directly. 

True.

>  One problem with this approach might be if we need to use <contact> for names with non-ASCII characters.  Based on my quick spot check, I don’t think this is problematic for this document; the names seem to match what appears in the docs.  RFC 8980 included Stéphane Bortzmeyer, Moritz Müller, and Jörg Ott. 
> 
> Does it make sense to use <contact> in this section only for the names that contain non-ASCII chars?  Is it problematic that use of <contact> would be inconsistent? 

Hmm, well, <contact> is used for two purposes:

1. Flagging that we have contact information for a person or entity.

2. Kludging support for non-ASCII characters in the name of a person or
entity.

:-)

Given that these purposes aren't consistent, I'm not sure that
consistency in tagging is critically important.

Peter

v2.23.0 | Report a Bug | By Email