Toggle menu
310,1 tis.
44
18
525,6 tis.
Hrvatska internetska enciklopedija
Toggle preferences menu
Toggle personal menu
Niste prijavljeni
Your IP address will be publicly visible if you make any edits.

Predložak:Cite IETF

Izvor: Hrvatska internetska enciklopedija

 

== Uporaba ==

Napomena: Svi parametri moraju biti malim slovima.

Copy a blank version to use. Remember to use the "|" (pipe) character between each parameter. Please delete any unused parameters to avoid clutter in the edit window.

Full version (copy and paste text below and delete parameters you don't need)
{{cite IETF |title= |rfc= |std= |bcp= |fyi= |draft= |ien= |rtr= |sectionname= |section= |sections= |appendix= |referenceid= |page= |pages= |last1= |first1= |authorlink1= |last2= |first2= |authorlink2= |authormask= |coauthors= |editor1-last= |editor1-first= |editor1-link= |others= |date= |year= |month= |origyear= |publisher=[[Internet Engineering Task Force|IETF]] |location= |language= |format= |accessdate= |url= |section-url= |page-url= |autolink= |id= |idanchor= |idlink= |idlinktype= |doi= |doi_brokendate= |issn= |archiveurl= |archivedate= |quote= |nopp= |nosec= |ref= |laysummary= |laydate= |separator= |postscript= |lastauthoramp= }}
Most commonly used parameters (use this and you won't have to delete as much)
{{cite IETF |title= |rfc= |sectionname= |section= |page= |last= |first= |authorlink= |coauthors= |year= |month= |publisher=[[Internet Engineering Task Force|IETF]] |accessdate= |doi= }}
Example 1

{{cite IETF |title=The Tao of IETF: A Novice's Guide to the Internet Engineering Task Force |rfc=4677 |fyi=17 |last1=Hoffman |first1=P. |authorlink1=Paul Hoffman (VPNC) |last2=Harris |first2=S. |year=2006 |month=September |publisher=[[Internet Engineering Task Force|IETF]] |accessdate=October 20, 2009 |doi=10.17487/RFC4677}}

Hoffman, P.; Harris, S. (rujan 2006). The Tao of IETF: A Novice's Guide to the Internet Engineering Task Force. IETF. doi:10.17487/RFC4677. FYI 17. RFC 4677. https://tools.ietf.org/html/rfc4677 Pristupljeno 20. listopad 2009. 

Example 2
{{cite IETF
| title = Telnet protocol specification
| rfc = 854
| std = 8
| sectionname = Are You There (AYT)
| page = 8
| last1 = Postel
| first1 = J.
| authorlink1 = Jon Postel
| last2 = Reynolds
| first2 = J.
| authorlink2 = Joyce K. Reynolds
| year = 1983
| month = May
| publisher = [[Internet Engineering Task Force|IETF]]
| accessdate = October 20, 2009
| doi = 10.17487/RFC0854
}}

Postel, J.; Reynolds, J. (svibanj 1983). "Are You There (AYT)". Telnet protocol specification. IETF. p. 8. doi:10.17487/RFC0854. STD 8. RFC 854. https://tools.ietf.org/html/rfc854#page-8 Pristupljeno 20. listopad 2009. 

Vertical list Prerequisites Brief instructions
{{cite IETF
| title       = 
| rfc         = 
| std         = 
| bcp         = 
| fyi         = 
| draft       = 
| ien         = 
| rtr         = 
| sectionname = 
| section     = 
| sections    = 
| appendix    = 
| referenceid = 
| page        = 
| pages       = 
| last        = 
| first       = 
| authorlink  = 
| authormask  = 
| coauthors   = 
| lastN       = 
| firstN      = 
| authorN-link = 
| editor      = 
| editorN     = 
| editorN-last = 
| editorN-first = 
| editor-link = 
| editorN-link = 
| others      = 
| date        = 
| year        = 
| month       = 
| origyear    = 
| publisher   = 
| location    = 
| language    = 
| format      = 
| accessdate  = 
| url         = 
| section-url = 
| page-url    = 
| autolink    = 
| id          = 
| idanchor    = 
| idlink      = 
| idlinktype  = 
| doi         = 
| doi_brokendate = 
| issn        = 
| archiveurl  = 
| archivedate = 
| quote       = 
| nopp        = 
| nosec       = 
| ref         = 
| laysummary  = 
| laydate     = 
| separator   = 
| postscript  = 
| lastauthoramp = 
}}
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
last
last
 
last
 
lastN
 
 
 
 
editorN-last
editor or editor-last
editorN or editorN-last
 
 
 
year
year or date
 
publisher
 
 
rfc, std, bcp, fyi, draft, ien, rtr, or url
 
sectionname
sectionname
rfc, std, bcp, fyi, draft, ien, rtr, or url
 
id, rfc, std, bcp, fyi, draft, ien, or rtr
id, rfc, std, bcp, fyi, draft, ien, or rtr
idanchor or idlink
 
doi
 
url, rfc, std, bcp, fyi, draft, ien, or rtr
archiveurl
 
page or pages
section, sections, or appendix
 
 
laysummary
 
 
coauthors or >1 lastN
 
 
 
(no wikilink) RFC number; 4677
(no wikilink) STD number
(no wikilink) BCP number
(no wikilink) FYI number; 17
(no wikilink) I-D (internet draft) name
(no wikilink) IEN number
(no wikilink) RTR number
 
(no wikilink) section number; 3.3
(no wikilink) section range (can be used together with the section parameter)
(no wikilink) appendix number; A.1
(no wikilink) reference id
(no wikilink) page number
(no wikilink) page range (can be used together with the page parameter)
 
(no wikilink)
(no wikilink)
 
 
alternative to first2, last2...first9, last9
(no wikilink) N=1 through 9
N=1 through 9
N=1 through 9
 
N=1 through 4
N=1 through 4
N=1 through 4
 
N=1 through 4
 
preferred (no wikilink) This is the preferred parameter with its alternates listed below.
alternative to date
 
 
should be [[Internet Engineering Task Force|IETF]] for IETF documents.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
hides automatic 'p.' or 'pp.'
hides automatic 'sec.'
 
 
 
 
 
 
 

Examples

  • {{cite IETF | title = Hypertext Transfer Protocol -- HTTP/1.1 | rfc = 2616 | first1 = R. | last1 = Fielding | authorlink1 = Roy Fielding | first2 = J. | last2 = Gettys | authorlink2 = Jim Gettys | first3 = J. | last3 = Mogul | first4 = H. | last4 = Frystyk | authorlink4 = Henrik Frystyk Nielsen | first5 = L. | last5 = Masinter | first6 = P. | last6 = Leach | first7 = T. | last7 = Berners-Lee | authorlink7 = Tim Berners-Lee | year = 1999 | month = June | publisher = [[Internet Engineering Task Force|IETF]] | doi = 10.17487/RFC2616 }}
    Fielding, R.; Gettys, J.; Mogul, J.; Frystyk, H.; Masinter, L.; Leach, P.; Berners-Lee, T. (lipanj 1999). Hypertext Transfer Protocol -- HTTP/1.1. IETF. doi:10.17487/RFC2616. RFC 2616. https://tools.ietf.org/html/rfc2616 
  • {{cite IETF | title = Domain names - concepts and facilities | rfc = 1034 | sectionname = Name space specifications and terminology | section = 3.1 | author = P. Mockapetris | authorlink = Paul Mockapetris | year = 1987 | month = November | publisher = [[Internet Engineering Task Force|IETF]] | accessdate = August 3, 2008 | doi = 10.17487/RFC1034 | quote = A domain is a subdomain of another domain if it is contained within that domain. This relationship can be tested by seeing if the subdomain's name ends with the containing domain's name. For example, A.B.C.D is a subdomain of B.C.D, C.D, D, and ' '. }}
    P. Mockapetris (studeni 1987). "Name space specifications and terminology". Domain names - concepts and facilities. IETF. sec. 3.1. doi:10.17487/RFC1034. RFC 1034. https://tools.ietf.org/html/rfc1034#section-3.1 Pristupljeno 3. kolovoz 2008.. "A domain is a subdomain of another domain if it is contained within that domain. This relationship can be tested by seeing if the subdomain's name ends with the containing domain's name. For example, A.B.C.D is a subdomain of B.C.D, C.D, D, and ' '." 

Parameters

Syntax

Nested parameters rely on their parent parameters:

  • parent
  • OR: parent2—may be used instead of parent
    • child—may be used with parent (and is ignored if parent is not used)
    • OR: child2—may be used instead of child (and is ignored if parent2 is not used)
Where aliases are listed, only one of the parameters may be defined; if multiple aliased parameters are defined, then only one will show.

This template embeds COinS metadata in the HTML output, allowing reference management software to retrieve bibliographic metadata. See: Wikipedia:COinS. As a general rule, only one data item per parameter. Do not include explanatory or alternate text: Use of templates within the citation template, is discouraged because many of these templates will add extraneous HTML or CSS that will be rendered in the metadata. Also, HTML entities (e.g.  , –) should not be used in parameters that contribute to the metadata. Do not include Wiki markup '' (italic font) or ''' (bold font) because these markup characters will contaminate the metadata.


}}