[rfc-i] draft-iab-xml2rfc-03, "2.32 <name>"

julian.reschke at gmx.de (Julian Reschke) Wed, 22 June 2016 08:18 UTC

From: julian.reschke at gmx.de (Julian Reschke)
Date: Wed, 22 Jun 2016 10:18:48 +0200
Subject: [rfc-i] draft-iab-xml2rfc-03, "2.32 <name>"
In-Reply-To: <49B921A8-4D48-4BBC-81F7-8BFA2BBA06F9@vpnc.org>
References: <03c5eca7-2cf5-b8ea-b179-399b15848ded@gmx.de> <49B921A8-4D48-4BBC-81F7-8BFA2BBA06F9@vpnc.org>
Message-ID: <99c9b09b-9ba6-7ca0-2d66-46c693609023@gmx.de>

On 2016-06-22 01:40, Paul Hoffman wrote:
> On 13 Jun 2016, at 0:37, Julian Reschke wrote:
>
>> <https://greenbytes.de/tech/webdav/draft-iab-xml2rfc-03.html#rfc.section.2.32>:
>>
>>
>> "The name of the section, note, figure, or texttable. This name can
>> have flow markup such as to make some characters use a fixed-width
>> font, or to include references."
>>
>> So it allows comments (<cref>), but not, for instance, <em>.
>>
>> Are we sure that this is the right set of elements to allow?
>
> As sure as we can be. We know that names will appear in section
> headings, and those might be rendered as italics or bold, so allowing
> things like <em> will cause surprise. Thus, allowing reference elements
> plus <tt> seems like the maximal non-surprising set.

Noted, but not convinced.

1) wrt to least surprise: I was surprised that we allow something 
esoteric like <cref>, but not simple things as <em>.

2) If styling inside an italicized context is the issue: this is 
trivially solved by styling <em> inside <em> differently. If this was an 
issue, we'd need to disallow it inside <blockquote> as well...

Best regards, Julian