Re: [core] [Cbor] CBOR Tag 38 (in draft-ietf-core-problem-details)

[Christian Amsüss <[e-mail]>]

Hello Carsten,

picking up points from the interim meeting:

On Wed, May 11, 2022 at 02:17:15PM +0200, Carsten Bormann wrote:
> Oh, and while you read the W3C documents, please note that neither the
> existing tag 38 nor the various proposals to fix/complement it solve
> delimiting embedded runs; this would be getting a bit closer to
> creating a little markup language though.

Not doing anything markup-language-ish could guide our choice on
explicit vs. implicit null: As long as we don't have context, there's
nowhere to "inherit" the direction from yet, so true/false/null should
suffice as options.

The question of "do we need more extensibility" also came up:

I don't think we have to set up a registry here; when anyone defines how
boustrophedon or top-to-bottom-then-right-to-left interact with what is
now still called *bi*directional rendering, there'd just be a new
document that updates problem-details and thus has IANA change the
reference again. My heuristic here is that I wouldn't know what to check
for as an expert, let alone give guidance to the reviewing expert, so it
can be done in a document update just as well.

By the way, I know now how I erred when I noted that Hebrew did not
usually need a direction tag; I confused the direction with the script
type of the language (sub)tags, where the Hebr script is suppressed for
he (and explicit script), and only languages such as Azerbaijani
commonly get one.

BR
c

-- 
To use raw power is to make yourself infinitely vulnerable to greater powers.
  -- Bene Gesserit axiom