rfc-2119: Difference between revisions

From Microformats Wiki
Jump to navigation Jump to search
m (→‎On this wiki: expose URL)
(restored synthetic h1 heading to eliminate unnecessary TOC level, simplified headings)
Line 1: Line 1:
=RFC 2119=
<h1><nowiki>RFC 2119</nowiki></h1>


==Definitions==
Microformat specifications (and their drafts) use the key words "{{must}}", "{{must-not}}", "{{required}}", "{{shall}}", "{{shall-not}}", "{{should}}", "{{should-not}}", "{{recommended}}", "{{not-recommended}}", "{{may}}", and "{{optional}}". These are to be interpreted as described in [http://www.ietf.org/rfc/rfc2119.txt RFC 2119] and {{may}} include a link to this page, or directly to http://www.ietf.org/rfc/rfc2119.txt.
 
== Definitions ==
RFC 2119 gives the following definitions:
RFC 2119 gives the following definitions:


Line 10: Line 12:
# '''{{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.)


==On this wiki==
== Templates ==
 
Often, microformat specifications (and their drafts) will use the key words "{{must}}", "{{must-not}}", "{{required}}", "{{shall}}", "{{shall-not}}", "{{should}}", "{{should-not}}", "{{recommended}}", "{{not-recommended}}", "{{may}}", and "{{optional}}". These are to be interpreted as described in [http://www.ietf.org/rfc/rfc2119.txt RFC 2119] and {{may}} include a link to this page, or directly to http://www.ietf.org/rfc/rfc2119.txt.
 
=== Templates ===
 
The following templates are available for use on this wiki:
The following templates are available for use on this wiki:


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


*<nowiki>{{must}}</nowiki> = {{must}}
*<nowiki>{{must}}</nowiki> = {{must}}
Line 34: Line 31:
These adhere to the [http://www.w3.org/2001/06/manual/#RFC W3C Manual of Style guidelines for RFC 2119].
These adhere to the [http://www.w3.org/2001/06/manual/#RFC W3C Manual of Style guidelines for RFC 2119].


==On other web pages==


=== Markup suggestions ===
== Markup suggestions ==
When using RFC 2119 terms on 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.


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.
On this wiki, the above templates help facilitate the use of the markup pattern from the W3C Manual of Style.


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.
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 ===
== microformat thoughts ==
 
Some have suggested considering a new microformat for marking up use of RFC 2119 terms.
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.
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.

Revision as of 01:32, 27 August 2007

RFC 2119

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

Definitions

RFC 2119 gives the following definitions:

  1. MUST This word, or the terms "REQUIRED" or "SHALL", mean that the definition is an absolute requirement of the specification.
  2. MUST NOT This phrase, or the phrase "SHALL NOT", mean that the definition is an absolute prohibition of the specification.
  3. 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.
  4. 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.
  5. 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.)

Templates

The following templates are available for use on this wiki:

  • {{must}} = MUST
  • {{must-not}} = MUST NOT
  • {{required}} = REQUIRED
  • {{shall}} = SHALL
  • {{shall-not}} = SHALL NOT
  • {{should}} = SHOULD
  • {{should-not}} = SHOULD NOT
  • {{recommended}} = RECOMMENDED
  • {{not-recommended}} = NOT RECOMMENDED
  • {{may}} = MAY
  • {{optional}} = OPTIONAL

These adhere to the W3C Manual of Style guidelines for RFC 2119.


Markup suggestions

When using RFC 2119 terms on web pages, consider re-using the mark-up pattern from the W3C Manual of Style (in particular class="RFC2119" - note capitalization), and perhaps their suggested style rule as well.

On this wiki, the above templates help facilitate the use of the markup pattern from the W3C Manual of Style.

In addition, see Edward O'Connor POSH suggestion for marking up the commonly used initial paragraph declaring RFC 2119 terms in documents.

microformat thoughts

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.

Retrieved from "http://microformats.org/wiki/index.php?title=rfc-2119&oldid=20411"