This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 1044 - Case of RFC2119 terms
Summary: Case of RFC2119 terms
Status: RESOLVED REMIND
Alias: None
Product: QA
Classification: Unclassified
Component: QASpec-GL (show other bugs)
Version: LC-2004-11-22
Hardware: All All
: P2 minor
Target Milestone: ---
Assignee: Karl Dubost
QA Contact: Karl Dubost
URL: http://lists.w3.org/Archives/Public/w...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-01-21 09:40 UTC by Dominique Hazael-Massieux
Modified: 2005-04-28 11:53 UTC (History)
0 users

See Also:

Attachments

Description Dominique Hazael-Massieux 2005-01-21 09:40:52 UTC 
"3.2 Requirement A: Use a consistent style for conformance
requirements and explain how to distinguish them." mentions that
RFC2119 terms are uppercase, but it should be noted that nothing in
RFC2119 (other than consistent usage as such) requires them to be used
in uppercase, despite specifications frequently explicitly mentioning
that they use lowercase variants instead.
Comment 1 Karl Dubost 2005-03-03 19:43:03 UTC 
http://lists.w3.org/Archives/Public/www-qa-wg/2005Feb/0028.html

       http://www.w3.org/Bugs/Public/show_bug.cgi?id=1044
       KD will rewrite the text [AI-20050214-4] and send
       it to the QA WG list. Due date is February 21.
Comment 2 Dominique Hazael-Massieux 2005-03-21 14:03:32 UTC 
http://www.w3.org/mid/7b37d825183d6e974d0b0bc3a64c0999@w3.org

Text clarifies that using distinctive appearance (markup or font weight) is only
the usual practice, rather than mandated.
Comment 3 Dominique Hazael-Massieux 2005-04-28 11:53:52 UTC 
setting version to LC in case of future use