rfc2119 - Revision history

Tantek: redirect from this variant to better name per naming conventions

2007-08-26T21:28:02Z

redirect from this variant to better name per naming conventions

← Older revision		Revision as of 21:28, 26 August 2007
Line 1:		Line 1:
	~~=RFC2119=~~		#REDIRECT[[rfc-2119]]

	~~==Definitions==~~
	~~RFC2119 gives the following definitions:~~

	# ~~'''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.)

	~~==On this wiki==~~

	Often, microformat specifications (and their drafts) will use the key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL". These are to be interpreted as described in [~~http://www.ietf.org/rfc/rfc2119.txt RFC2119] and '''MAY''' include a link to this page, or directly to~~ [~~http://www.ietf.org/~~rfc~~/rfc2119.txt the RFC].~~

	~~=== Templates ===~~

	~~The following templates are available for use on this wiki:~~

	*<nowiki>{{rfc2119-intro}}</nowiki> - ~~see [[template:rfc2119-intro]]~~

	*<nowiki>{{must}}</nowiki> = {{must}}
	*<nowiki>{{must-not}}</nowiki> = {{must-not}}
	*<nowiki>{{required}}</nowiki> = {{required}}
	*<nowiki>{{shall}}</nowiki> = {{shall}}
	*<nowiki>{{shall-not}}</nowiki> = {{shall-not}}
	*<nowiki>{{should}}</nowiki> = {{should}}
	*<nowiki>{{should-not}}</nowiki> = {{should-not}}
	*<nowiki>{{recommended}}</nowiki> = {{recommended}}
	*<nowiki>{{may}}</nowiki> = {{may}}
	*<nowiki>{{optional}}</nowiki> = {{optional}}

	~~These adhere to the [http://www.w3.org/2001/06/manual/#RFC W3C Manual of Style guidelines for RFC2119].~~

	~~==On other web pages==~~

	~~=== Markup suggestions ===~~

	~~When using RFC~~ 2119 ~~terms on your own web pages, consider re-using the [http://www.w3.org/2001/06/manual/#RFC mark-up pattern from the W3C Manual of Style~~] ~~(in particular <code>class="RFC2119"</code> - <strong>note capitalization</strong>), and perhaps their suggested style rule as well.~~

	~~In addition, see [http://edward.oconnor.cx/2007/08/marking-up-rfc2119-text Edward O’Connor POSH suggestion for marking up the commonly used initial paragraph declaring RFC 2119 terms~~] ~~in documents.~~

	~~=== Microformat proposal ===~~

	~~Some have suggested considering a new microformat for marking up use of RFC 2119 terms.~~

	~~It appears there is no need for such a new microformat however. Following W3C's established practice, and Edward O'Connor's POSH suggestion for the initial paragraph, appears to be sufficient.~~

AndyMabbett: /* Definitions */ intro

2007-08-26T19:15:11Z

Definitions: intro

← Older revision		Revision as of 19:15, 26 August 2007
Line 2:		Line 2:

	==Definitions==		==Definitions==
			RFC2119 gives the following definitions:

	# '''MUST''' This word, or the terms "'''REQUIRED'''" or "'''SHALL'''", mean that the definition is an absolute requirement of the specification.		# '''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.		# '''MUST NOT''' This phrase, or the phrase "'''SHALL NOT'''", mean that the definition is an absolute prohibition of the specification.

AndyMabbett: merging from dupilicate page; distinguish between this wiki and general web pages

2007-08-26T19:13:16Z

merging from dupilicate page; distinguish between this wiki and general web pages

@@ Line 1: / Line 1: @@
 =RFC2119=
 ==Definitions==
@@ Line 13: / Line 7: @@
 # '''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.)

AndyMabbett at 21:23, 27 March 2007

2007-03-27T21:23:20Z

← Older revision		Revision as of 21:23, 27 March 2007
Line 1:		Line 1:
	~~<!-- This is correct AFAICT; please correct if not -->~~

	=RFC2119=		=RFC2119=

Line 6:		Line 4:

	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].		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].

			<!-- The above is correct AFAICT; please correct if not -->

	==Definitions==		==Definitions==

AndyMabbett: This is correct AFAICT; please correct if not

2007-03-27T21:22:47Z

This is correct AFAICT; please correct if not

← Older revision		Revision as of 21:22, 27 March 2007
Line 1:		Line 1:
			<!-- This is correct AFAICT; please correct if not -->

	=RFC2119=		=RFC2119=

AndyMabbett at 17:58, 27 March 2007

2007-03-27T17:58:10Z

← Older revision		Revision as of 17:58, 27 March 2007
Line 1:		Line 1:
			=RFC2119=

	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.		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.

	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].		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].

			==Definitions==
	# '''MUST''' This word, or the terms "'''REQUIRED'''" or "'''SHALL'''", mean that the definition is an absolute requirement of the specification.		# '''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.		# '''MUST NOT''' This phrase, or the phrase "'''SHALL NOT'''", mean that the definition is an absolute prohibition of the specification.

AndyMabbett at 17:57, 27 March 2007

2007-03-27T17:57:41Z

← Older revision		Revision as of 17:57, 27 March 2007
Line 4:		Line 4:

	# '''MUST''' This word, or the terms "'''REQUIRED'''" or "'''SHALL'''", mean that the definition is an absolute requirement of the specification.		# '''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.		# '''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''' 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.		# '''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.)		# '''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.)

AndyMabbett at 17:57, 27 March 2007

2007-03-27T17:57:22Z

New page

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.

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.)