Difference between revisions of "rfc2119"

From Microformats Wiki
rfc2119
Jump to navigation Jump to search
 
m (redirect from this variant to better name per naming conventions)
 
(6 intermediate revisions by one other user not shown)
Line 1: Line 1:
Often. microformat specifications (and their drafts) will use terms like '''MUST''', '''MUST NOT''', '''SHOULD'''. '''SHOULD NOT''', and '''MAY''' in the manner described in [http://www.ietf.org/rfc/rfc2119.txt RFC2119], as set out below.
+
#REDIRECT[[rfc-2119]]
 
 
They '''SHOULD''' do so in this manner, with CAPITALISATION and '''emboldening''', and '''MAY''' include a link to this page, or directly to [http://www.ietf.org/rfc/rfc2119.txt the RFC].
 
 
 
# '''MUST''' This word, or the terms "'''REQUIRED'''" or "'''SHALL'''", mean that the definition is an absolute requirement of the specification.
 
 
 
# '''MUST NOT''' This phrase, or the phrase "'''SHALL NOT'''", mean that the definition is an absolute prohibition of the specification.
 
 
 
# '''SHOULD''' This word, or the adjective "'''RECOMMENDED'''", mean that there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications must be understood and carefully weighed before choosing a different course.
 
 
 
# '''SHOULD NOT''' This phrase, or the phrase "'''NOT RECOMMENDED'''" mean that there may exist valid reasons in particular circumstances when the particular behavior is acceptable or even useful, but the full implications should be understood and the case carefully weighed before implementing any behavior described with this label.
 
 
 
# '''MAY''' This word, or the adjective "'''OPTIONAL'''", mean that an item is truly optional. One vendor may choose to include the item because a particular marketplace requires it or because the vendor feels that it enhances the product while another vendor may omit the same item. An implementation which does not include a particular option '''MUST''' be prepared to interoperate with another implementation which does include the option, though perhaps with reduced functionality. In the same vein an implementation which does include a particular option '''MUST''' be prepared to interoperate with another implementation which does not include the option (except, of course, for the feature the option provides.)
 

Latest revision as of 21:28, 26 August 2007

Redirect to: