The following recommendations from the Steering Committee (to use the RFC 2119 keywords along with the following restrictions in the specifications) were accepted unanimously:
a) All RFC 2119 keywords will be of the uppercase form (for example, RFC 2119 keywords MUST be capitalized)
b) Use of lower-case 2119 keywords will not be used in the spec. When the use of 2119 keyword is needed, without having the implications wrt conformance, a suitable synonym will be found.
c) RFC 2119 defines keywords that are synonyms of each other. For example 'SHALL' and 'MUST' mean the same thing. The TC should not use multiple forms to mean the same. Therefore the TC should use 'MUST' instead of 'SHALL' and 'MUST NOT' instead of 'SHALL NOT' through out the spec.
Kaanu Joshi[02/Oct/07 11:22 AM]
The following recommendations from the Steering Committee (to use the RFC 2119 keywords along with the following restrictions in the specifications) were accepted unanimously:
a) All RFC 2119 keywords will be of the uppercase form (for example, RFC 2119 keywords MUST be capitalized)
b) Use of lower-case 2119 keywords will not be used in the spec. When the use of 2119 keyword is needed, without having the implications wrt conformance, a suitable synonym will be found.
c) RFC 2119 defines keywords that are synonyms of each other. For example 'SHALL' and 'MUST' mean the same thing. The TC should not use multiple forms to mean the same. Therefore the TC should use 'MUST' instead of 'SHALL' and 'MUST NOT' instead of 'SHALL NOT' through out the spec.
Task
Closed
Trivial
Use of RFC 2119 keywords in the spec
a) All RFC 2119 keywords will be of the uppercase form (for example, RFC 2119 keywords MUST be capitalized)
b) Use of lower-case 2119 keywords will not be used in the spec. When the use of 2119 keyword is needed, without having the implications wrt conformance, a suitable synonym will be found.
c) RFC 2119 defines keywords that are synonyms of each other. For example 'SHALL' and 'MUST' mean the same thing. The TC should not use multiple forms to mean the same. Therefore the TC should use 'MUST' instead of 'SHALL' and 'MUST NOT' instead of 'SHALL NOT' through out the spec.