[rfc-i] Is there a use case for 2119 keyword markup?
touch at isi.edu
Sat Jun 21 21:31:19 PDT 2014
Note that this logic requires there be no markup for code, ABNF, or any other semantic content.
Otherwise the same process that defines those markings should be applied to 2119 marking.
Sauce for the goose.
> On Jun 21, 2014, at 8:50 PM, Larry Masinter <masinter at adobe.com> wrote:
> Based on feedback I'd propose not adding 2119 keyword markup at this time.
> The RFC-editor could say that the IETF can request additional markup capabilities (new entities, elements, markup, tags), if IETF changes to processes so they can be useful.
> Any proposed additional markup should explain the semantics, how it affects the text, html, pdf, etc. renditions of the document, and the process by which correctness of the markup is validated.
> So far the proposals for additional markup require changes to IETF processes, policies, conventions, before they would be really useful. And we shouldn't clutter the XML with features on speculation, as they are likely to be incomplete.
> (For example, if you typeset MUST, MAY, and SHOULD in small-caps in the HTML and PDF and as uppercase in text, you might want to have a standard 2119 boilerplate in the intro that notes the typesetting convention as referring to 2119. )
> rfc-interest mailing list
> rfc-interest at rfc-editor.org
More information about the rfc-interest