Re: [Rfc-markdown] How to cite this DOI?

[John Levine <[e-mail]>]

It appears that Carsten Bormann  <[e-mail]> said:
>On 15. Oct 2021, at 12:36, Lars Eggert <[e-mail]> wrote:
>> 
>> I have no idea. The whole DOI thing seems pretty sloppily put together; unfortunately it's what the publishing industry adopted though.
>
>That was easy:
>
>https://www.doi.org/doi_handbook/2_Numbering.html#2.2.1
>
>>> The DOI name is case-insensitive and can incorporate any printable characters from the legal graphic characters of Unicode. Further constraints on
>character use (e.g. use of language-specific alphanumeric characters) can be defined for an application by the ISO 26324 Registration Authority.
>
>You can’t make this stuff up.

How soon they forget.  DOIs are an instance of the handle system, whose syntax is defined in RFC 3651.  It does indeed allow any UTF-8 encoded
Unicode 2.0 character, but since the handle system also had its own retrieval protocol, quoting wasn't a problem.

Except that nobody ever used the handle protocol so the only popular application of handles, DOI, made an expedient
choice to use http instead, turning the handles into URLs.  Unfortunately, the DOI people are librarians, not
computer standards experts and may have missed the fine points of what goes into a URL.

Having said that, what's the problem with that URL?  RFC 1738 specifically says that unencoded parentheses in a URL are allowed.
I tried pasting it into Brave (based on Chrome), Safari, and Firefox, and it worked fine.  If you have some tool that barfs
on them, you can always percent encode them.

R's,
John