This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
styleweb [2012/06/18 14:50] rsewikiadmin created |
styleweb [2012/10/12 13:45] (current) rsewikiadmin [Capitalization of file types] |
||
---|---|---|---|
Line 6: | Line 6: | ||
As new recommendations are being tested or updated to reflect current usage, this site will change. | As new recommendations are being tested or updated to reflect current usage, this site will change. | ||
- | |||
- | ===== Referencing Wikipedia ===== | ||
- | |||
- | Because Wikipedia pages change, references to Wikipedia should be avoided. | ||
- | |||
- | References to Wikipedia should include the date that the page was visited and the URL specific to the version available on that date. For example: | ||
- | |||
- | [TwoGenerals] "The Two Generals' | ||
- | < | ||
- | index.php? | ||
- | 417855753> | ||
- | |||
Line 25: | Line 13: | ||
//Someone will need to take proper ownership for this citation library// | //Someone will need to take proper ownership for this citation library// | ||
+ | |||
===== Referencing BCP, STD and associated individual RFC ===== | ===== Referencing BCP, STD and associated individual RFC ===== | ||
Line 51: | Line 40: | ||
With this convention, the documents that comprise the STD number at that time of pub are documented and the text is clear where it is referring to a specific document vs the suite of protocols (e.g., "RFC 3412 [STD62] discusses Message Processing Dispatching..." | With this convention, the documents that comprise the STD number at that time of pub are documented and the text is clear where it is referring to a specific document vs the suite of protocols (e.g., "RFC 3412 [STD62] discusses Message Processing Dispatching..." | ||
+ | ===== Referencing I-D in an RFC ===== | ||
+ | //This advice is itself a Work in Progress// | ||
+ | (From the Citation Committee - http:// | ||
+ | We RECOMMEND that " | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | |||
+ | If a specific version of the I-D is being referenced, reference should also include the full file name in order to capture the revision number. | ||
===== Judging the stability of a website reference ===== | ===== Judging the stability of a website reference ===== | ||
Line 59: | Line 59: | ||
* the URL provided should point to the original document or site when possible for both stability and potential copyright issues | * the URL provided should point to the original document or site when possible for both stability and potential copyright issues | ||
* the URL provided should point to a reliable and credible source (note that sites like Wikipedia do not consider their content consistently reliable or credible) | * the URL provided should point to a reliable and credible source (note that sites like Wikipedia do not consider their content consistently reliable or credible) | ||
+ | |||
Line 66: | Line 67: | ||
* capitalization may remain at the author' | * capitalization may remain at the author' | ||
- | | + | * use of capitalization must be consistent for an author across all RFCs |
- | | + | |
+ | |||
+ | ===== Capitalization of file types and compression formats ===== | ||
Line 96: | Line 99: | ||
Collector | Collector | ||
+ | |||
+ | ===== References ===== | ||
+ | |||
+ | //Consider allowing for " | ||
===== RFC physical format ===== | ===== RFC physical format ===== | ||
- | //Was Appendix B of the RFC Style Guide.// | + | //Was Appendix B of the RFC Style Guide Draft. |
| |