Re: [I18ndir] [art] New Version Notification for draft-bray-unichars-05.txt

On 19. Sep 2023, at 19:57, Tim Bray <tbray@textuality.com> wrote:
> 
>     • So that a person who’s writing a protocol that uses JSON can say “The characters in object member names and string values MUST be limited to Useful Assignables [unichars]”

That would mean that the document provides a useful definition of “useful”.
Usefulness depends on the application though.
Please see [1] for a discussion that looks at the needs of applications.

[1]: https://www.ietf.org/archive/id/draft-bormann-dispatch-modern-network-unicode-03.html

[1] defines terms that might help in finding out what that useful set is.

Putting surrogate code points into the same bin as control characters (“problematic”) is a symptom of confusion, and exposing people who are looking to understand a non-trivial subject to additional confusion is not useful.

>     • So that when an early draft of an RFC doesn’t say anything about character repertoire, a reviewer can say “You need to specify a character repertoire, go read [unichars]”

That makes a lot of sense, if the document being pointed to is actually useful.
See above.

Grüße, Carsten

> 
> On Sep 19, 2023 at 10:52:24 AM, Carsten Bormann <cabo@tzi.org> wrote:
>> I’m sorry, even with more expertise pumped into the document, I don’t see the point of this document.
>> 
>> Would you care to write up who is the audience?  What problem are you trying to solve for them?
>> 
>> Grüße, Carsten
>> 
> _______________________________________________
> art mailing list
> art@ietf.org
> https://www.ietf.org/mailman/listinfo/art