- From: Karl Dubost <karl@w3.org>
- Date: Thu, 10 Mar 2005 15:44:34 -0500
- To: 'www-qa-wg@w3.org' <www-qa-wg@w3.org>
- Message-Id: <26ae2fbd9d2c1f611e281802d9d6ce51@w3.org>
Issue:1044 - Case of RFC2119 terms
http://www.w3.org/Bugs/Public/show_bug.cgi?id=1044
"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.
Old Text:
[[[Using RFC 2119 [RFC2119] Keywords (MUST, SHOULD, MAY, ...) makes it
easy to spot conformance requirements, due to their specific uppercase
formatting; according to the RFC itself, they should be used only to
establish interoperation [WIKI-RFC-KEYWORDS];]]]
New Text:
Using RFC 2119 [RFC2119] Keywords (MUST, SHOULD, MAY, ...) makes it
easy to spot conformance requirements; according to the RFC itself,
they should be used only to establish interoperation
[WIKI-RFC-KEYWORDS]. They may be written with an uppercase formatting
and/or a specific markup (See the Manual of Style).
--
Karl Dubost - http://www.w3.org/People/karl/
W3C Conformance Manager
*** Be Strict To Be Cool ***
Received on Friday, 11 March 2005 04:46:11 UTC