Re: [Last-Call] Genart last call review of draft-crocker-inreply-react-07
Ned Freed <ned.freed@mrochek.com> Sat, 30 January 2021 23:38 UTC
Return-Path: <ned.freed@mrochek.com>
X-Original-To: last-call@ietfa.amsl.com
Delivered-To: last-call@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D5A93A1240; Sat, 30 Jan 2021 15:38:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mrochek.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 eFMVsM3qDpct; Sat, 30 Jan 2021 15:38:09 -0800 (PST)
Received: from plum.mrochek.com (plum.mrochek.com [172.95.64.195]) (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 1F4763A123F; Sat, 30 Jan 2021 15:38:09 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01RUZTE9ZX8W00CROG@mauve.mrochek.com>; Sat, 30 Jan 2021 15:33:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mrochek.com; s=201712; t=1612049584; bh=HJ5V0OxE6csZvRf6EzzJcD0GnPTfHOkzYZeF+bl8kUQ=; h=Cc:Date:From:Subject:In-reply-to:References:To:From; b=juSHFBmMrYhNSmQV5ePMh+EiS9ozTbS/kPnXg2+tRjgQX3wxO84FSzJbMMiJ9q2mQ dj3OE166zo1wEVx9lFcRcNomunl7jJIP9hu8qqpJoAeKtvwlU2IsPWXW7W/pYyMsS1 uI91Dy3guciICk0GkOfW+IGC4QIi2bTYhGstPcX0=
MIME-version: 1.0
Content-transfer-encoding: 8bit
Content-type: TEXT/PLAIN; charset="utf-8"; format="flowed"
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01RUZSLBR3PC0085YQ@mauve.mrochek.com>; Sat, 30 Jan 2021 15:33:01 -0800 (PST)
Cc: Barry Leiba <barryleiba@computer.org>, Dale Worley <worley@ariadne.com>, draft-crocker-inreply-react.all@ietf.org, gen-art@ietf.org, last-call@ietf.org
Message-id: <01RUZTE7OB4K0085YQ@mauve.mrochek.com>
Date: Sat, 30 Jan 2021 15:13:25 -0800
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Wed, 27 Jan 2021 19:49:42 -0800" <51b83f83-a0dd-a52c-389f-01fc4b8df3e1@bbiw.net>
References: <161180116375.12497.14607504902519078003@ietfa.amsl.com> <d5a06ce9-31e7-ecd8-084b-a4ad92add744@bbiw.net> <CALaySJKrKKyQSBsihN2XsisRi9=z2hZFEC00=XTkWc72wa8A-g@mail.gmail.com> <51b83f83-a0dd-a52c-389f-01fc4b8df3e1@bbiw.net>
To: Dave Crocker <dcrocker@bbiw.net>
Archived-At: <https://mailarchive.ietf.org/arch/msg/last-call/sqCvtb15gKGUmIBiZa3L0YsrA8M>
Subject: Re: [Last-Call] Genart last call review of draft-crocker-inreply-react-07
X-BeenThere: last-call@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Last Calls <last-call.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/last-call>, <mailto:last-call-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/last-call/>
List-Post: <mailto:last-call@ietf.org>
List-Help: <mailto:last-call-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/last-call>, <mailto:last-call-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 30 Jan 2021 23:38:11 -0000
I'm having a little difficulty following the discussion of the text, so I took a look at the text itself. It currently (-07) says: The rule emoji_sequence is inherited from [Emoji-Seq]. It permits one or more bytes to form a single presentation image. The rule base-emojis MAY be used as a simple, common list, or 'vocabulary' of emojis. It was developed from some existing practice, in social networking, and is therefore intended for use. However support for it is not required. Having providers and consumers employ a common set will facilitate user interoperability, but different sets of users might want to have different, common (shared) sets. The emoji(s) express a recipient's summary reaction to the specific message referenced by the accompanying In-Reply-To header field. [Mail-Fmt]. Reference to unallocated code points SHOULD NOT be treated as an error; associated bytes SHOULD be processed using the system default method for denoting an unallocated or undisplayable code point. There are a few problems here. First, TR#51 actually uses the term "image" in an incompatible way - specifically, it's used to refer to emojis directly represented by actual images, not ones experssed in Unicode itself. I think the correct term to use here is "pictograph". Second, since I'm one of those "old DEC-10 people" and know what ILDB and IDPB mean, I think "octet" is a better term than "byte". But I can live with "byte" if that's the consensus. Third, as previously noted, you always need more than one octet to encode an emoji, and the text should reflect that. Fourth, there's a bit of awkwardness to the second paragraph. "intended for use" where? What does support mean? Finally, I think a couple of word choices could be better. So how about: The rule emoji_sequence is inherited from [Emoji-Seq]. It defines a set of octet sequences, each of which forms a single pictograph. The rule base-emojis MAY be used as a simple, common list, or 'vocabulary' of emojis. It was developed from some existing practice, in social networking, and is therefore intended for such use. However support for it as a base vocabulary is not required. Having providers and consumers employ a common set will facilitate user interoperability, but different sets of users might want to have different, common (shared) sets. The emoji(s) express a recipient's summary reaction to the specific message referenced by the accompanying In-Reply-To header field. [Mail-Fmt]. Reference to unallocated code points SHOULD NOT be treated as an error; the corresponding octets SHOULD be processed using the system default method for denoting an unallocated or undisplayable code point. Ned > On 1/27/2021 7:45 PM, Barry Leiba wrote: > > > > I thunk the text that Dave has is correct — certainly more correct than > > the suggestion, which would imply character composition rather than the > > image composition that’s being discussed here. > > > > I don’t think a change to the text will really help, but a “(for > > example, ...)” might. > Barry, thanks. > However to the extent that there's any misunderstanding of the text by > one thoughtful, experienced reader, there's likely to be more. I've no > idea how to make it clearer or more robust, though. > d/ > -- > Dave Crocker > Brandenburg InternetWorking > bbiw.net
- [Last-Call] Genart last call review of draft-croc… Dale Worley via Datatracker
- Re: [Last-Call] Genart last call review of draft-… Dave Crocker
- Re: [Last-Call] Genart last call review of draft-… Barry Leiba
- Re: [Last-Call] Genart last call review of draft-… Dave Crocker
- Re: [Last-Call] Genart last call review of draft-… Kjetil Torgrim Homme
- Re: [Last-Call] Genart last call review of draft-… Dave Crocker
- Re: [Last-Call] Genart last call review of draft-… John Levine
- Re: [Last-Call] Genart last call review of draft-… Dave Crocker
- Re: [Last-Call] Genart last call review of draft-… Ned Freed
- Re: [Last-Call] Genart last call review of draft-… worley
- Re: [Last-Call] Genart last call review of draft-… Dave Crocker
- Re: [Last-Call] Genart last call review of draft-… Dave Crocker
- Re: [Last-Call] Genart last call review of draft-… worley
- Re: [Last-Call] Genart last call review of draft-… Dave Crocker
- Re: [Last-Call] [Gen-art] Genart last call review… Alissa Cooper