Re: [Alldispatch] Proposed discussion topic for ALLDISPATCH: draft-bray-unichars

 Not expressing an opinion as to how to handle Carsten's
modern-network-unicode draft, but I want to disagree strongly with the
assertion that it addresses “the same problem area" as the unichars draft.
Unichars addresses exactly one issue: Here are several subsets of Unicode
code points you might want to specify in your protocol or data format.

Modern-network-unicode extends into a discussion of the syntax and
semantics of “lines of text” and line separators, and considers other
issues such as normalization forms, byte order marks, and appropriate use
of ABNF.  I agree with some of it and disagree with other parts, but once
again, it just isn’t the same thing.

On Mar 1, 2024 at 6:17:25 PM, Carsten Bormann <cabo@tzi.org> wrote:

> I wrote a draft addressing the same problem area a while ago.
> Most of the discussion happened in 2019.
>
> I believe this draft is a much better document to use for the purpose
> listed below, and for use in the actual design phase of a protocol that
> uses text in various forms.
>
>
> https://www.ietf.org/archive/id/draft-bormann-dispatch-modern-network-unicode-04.html
>
> So if we discuss draft-bray-unichars, I believe we also should discuss
> this document.
>
> Grüße, Carsten
>
>
>
> On Mar 2, 2024, at 00:59, Tim Bray <tbray@textuality.com> wrote:
>
>
> Paul Hoffman and I would like to request ALLDISPATCH input on
> draft-bray-unichars-07:
> https://www.ietf.org/archive/id/draft-bray-unichars-07.html
>
> The goal of this draft is:
>
>     •
>
> When someone submits an I-D that mentions Unicode, at least one reviewer
> says “you need to think about character repertoires, go check out
> [Unichars].”
>
>     • When they’ve thought about it and figured out which character
> repertoire they like, they have a convenient reference-able document that
> explains the issues and includes ABNF for that repertoire.
>
>
> This fell out of a conversation originally provoked by an errata report,
> https://www.rfc-editor.org/errata/eid7603 - which revealed a distressing
> lack of consensus about Unicode characters and code points and character
> repertoires. I feel personally bad because I am the editor of a couple of
> documents that are open to criticism on this front.
>
>
> Per recommendations from ADs Francesca Palombini and Murray Kucherawy, we
> took the -00 draft to ie18ndir@ and art@ and had really outstanding
> high-energy feedback that got us to the -07 draft.  Here are some of the
> threads: https://mailarchive.ietf.org/arch/browse/i18ndir/  and
> https://mailarchive.ietf.org/arch/browse/art/?qdr=y&q=unichars
>
> I would estimate that this draft has already enjoyed a level of discussion
> that would be about what you’d expect for a similarly-small draft in a
> typical Working Group.
>
>
> We can see a variety of paths forward for this draft and ALLDISPATCH seems
> a good place to explore those options.
>
>
> --
>
> Alldispatch mailing list
>
> Alldispatch@ietf.org
>
> https://www.ietf.org/mailman/listinfo/alldispatch
>
>
>