[rfc-i] Is there a use case for 2119 keyword markup?

Dearlove, Christopher (UK) chris.dearlove at baesystems.com
Thu Jun 19 07:47:45 PDT 2014

They are linked. It's not unreasonable to say "fine if it's something easy like &must; or <must/>, but not fine if it's something cumbersome like <span class='rfc2119'>MUST</span>".

(There are of course intermediates like <keyword>MUST</keyword>.)

Christopher Dearlove
Senior Principal Engineer, Communications Group
Communications, Networks and Image Analysis Capability
BAE Systems Advanced Technology Centre
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
Tel: +44 1245 242194 |  Fax: +44 1245 242124
chris.dearlove at baesystems.com | http://www.baesystems.com

BAE Systems (Operations) Limited
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, Farnborough, Hants, GU14 6YU, UK
Registered in England & Wales No: 1996687

-----Original Message-----
From: rfc-interest [mailto:rfc-interest-bounces at rfc-editor.org] On Behalf Of Heather Flanagan (RFC Series Editor)
Sent: 19 June 2014 15:31
To: rfc-interest at rfc-editor.org
Subject: Re: [rfc-i] Is there a use case for 2119 keyword markup?

----------------------! WARNING ! ---------------------- This message originates from outside our organisation, either from an external partner or from the internet.
Consider carefully whether you should click on any links, open any attachments or reply.
Follow the 'Report Suspicious Emails' link on IT matters for instructions on reporting suspicious email messages.

On 6/19/14, 6:21 AM, Eliot Lear wrote:
> On 6/19/14, 3:10 PM, Joe Hildebrand (jhildebr) wrote:
>> If we mark up the 2119 words, it's trivial to change how they look using CSS or in the XML-to-text conversion.
> Sure.  I guess what I'm asking is whether we this is a discussion 
> about how or whether we will mark up 2119 keywords.  If it's how, then 
> as someone who writes drafts, I can live with <must /> or &must.

To be clear, the question is whether to mark up 2119 keywords.  How to do it is a different conversation; interesting, but different.


rfc-interest mailing list
rfc-interest at rfc-editor.org

This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.

More information about the rfc-interest mailing list