Template:Infobox networking protocol

From Wikipedia, the free encyclopedia
Jump to: navigation, search
{{{title}}}
Communications protocol
Purpose {{{purpose}}}
Developer(s) {{{developer}}}
Introduced {{{date}}}
Based on {{{based on}}}
Influenced {{{influenced}}}
OSI layer {{{osilayer}}}
Port(s) {{{ports}}}
RFC(s) {{{rfcs}}}
Hardware {{{hardware}}}
Template documentation[view] [edit] [history] [purge]

Usage[edit]

You can copy and paste the following empty skeleton template into the article and fill it in as you see fit, in case you wish to use source editor instead of VisualEditor. |logo caption= is deliberately omitted to discourage the use of this oft-abused parameter.

{{{title}}}
Communications protocol
[[File:{{{logo}}}|{{{logo size}}}|alt={{{logo alt}}}|{{{logo alt}}}]]
{{{logo caption}}}
[[File:{{{image}}}|{{{image size}}}|alt={{{image alt}}}|{{{image alt}}}]]
{{{caption}}}
Purpose {{{purpose}}}
Developer(s) {{{developer}}}
Introduced {{{date}}}
Based on {{{based on}}}
Influenced {{{influenced}}}
OSI layer {{{osilayer}}}
Port(s) {{{ports}}}
RFC(s) {{{rfcs}}}
Hardware {{{hardware}}}
{{Infobox networking protocol
|       title = 
|        logo = 
|    logo alt = 
|       image = 
|   image alt = 
|     caption = 
|    is stack = 
|     purpose = 
|   developer = 
|        date = {{Start date and age|    |  |  }}<!--Fill in: Year (4 digits), month and day (2 digits)-->
|    based on = 
|  influenced = 
|    osilayer = 
|       ports = 
|        rfcs = 
|    hardware = 
}}

Syntax[edit]

This is the TemplateData documentation for this template used by VisualEditor and other tools.

See the monthly error report for this template.

TemplateData for Infobox networking protocol

This infobox helps display important preliminary details about a protocol in an article.

Template parameters

Parameter Description Type Status
Title or name titlename

Title or name of the subject of infobox focus.

Default
empty
Example
empty
Auto value
empty
String required
Is stack? is stack

If set to "yes" specifies whether the article is about a protocol stack, instead of a communications protocol

Default
empty
Example
empty
Auto value
yes
Boolean optional
Logo logo

Name of the image pertaining the logo of the protocol or suite. A file name is enough.

Default
empty
Example
empty
Auto value
File optional
Logo size logo size

Size of the logo. Number and a CSS unit of measurement is accepted. e.g. 250px, x64px or 250x64px.

Default
empty
Example
empty
Auto value
empty
String optional
Logo's alternative text logo alt

Alternative text in case the logo cannot be displayed by the target web browser or cannot be seen by the target user.

Default
empty
Example
empty
Auto value
empty
String optional
Logo's caption text logo caption

A text caption to be displayed under the logo. Use of this field is discouraged, unless there is something of monumental importance to be said. Deletion notification templates go here as well.

Default
empty
Example
empty
Auto value
empty
Unbalanced wikitext optional
Image image

Name of an image pertaining the protocol or suite, such as a diagram. A file name is enough. Use only when absolutely necessary.

Default
empty
Example
empty
Auto value
empty
File optional
Image size image size

Size of the image. Number and a CSS unit of measurement is accepted. e.g. 250px, x64px or 250x64px. Defualts to 300px. Use only when absolutely necessary and try to keep it with in the vicinity of 300 pixels in width. Smaller images are hard to see and larger images resize the infobox.

Default
empty
Example
empty
Auto value
empty
String optional
Image's alternative text image alt

Alternative text in case the image cannot be displayed by the target web browser or cannot be seen by the target user.

Default
empty
Example
empty
Auto value
empty
String optional
Image caption caption

Caption text for the image. Must be present when the image is present.

Default
empty
Example
empty
Auto value
empty
String optional
Purpose purpose

A short sentence explaining the purpose of the protocol or stack succintly. Use only when absolutely needed.

Default
empty
Example
empty
Auto value
empty
String optional
Developer(s) developer

Names of entities who developed the protocol or worked in concert with the developers for publicizing the protocol.

Default
empty
Example
empty
Auto value
empty
String optional
Introduction date date

The date in which the protocol is introduced. Use {{start date and age}} template.

Default
empty
Example
empty
Auto value
empty
String optional
Based on based on

Names of protocols, standards or specification from which the protocol in question is derived.

Default
empty
Example
empty
Auto value
empty
String optional
Influenced influenced

Name of protocols that derive from this protocol

Default
empty
Example
empty
Auto value
empty
String optional
RFC(s) rfcs

RFC(s) describing this protocol

Default
empty
Example
empty
Auto value
empty
String optional
Port(s) ports

TCP/UDP ports if used by the protocol

Default
empty
Example
empty
Auto value
empty
String optional
OSI layer osilayer

OSI layer this protocol works in

Default
empty
Example
empty
Auto value
empty
String optional
Associated hardware hardware

Name of the hardware created specifically to work with this protocol.

Default
empty
Example
empty
Auto value
empty
String optional

Example[edit]

WebDAV
Communications protocol
Purpose Allows clients to perform remote Web content authoring operations
Developer(s) Jim Whitehead, Internet Engineering Task Force (IETF)
Introduced 1996; 21 years ago (1996)
Based on Hypertext Transfer Protocol (HTTP)
Influenced Delta-V, CalDAV, GroupDAV
OSI layer Application layer
Port(s) 80, 443
RFC(s) RFC 2518, RFC 4918
{{Infobox networking protocol
|title      = WebDAV
|is stack   = no
|purpose    = Allows clients to perform remote Web content authoring operations
|developer  = [[Jim Whitehead]], [[Internet Engineering Task Force]] (IETF)
|date       = {{Start date and age|1996}}
|based on   = [[Hypertext Transfer Protocol]] (HTTP)
|influenced = [[Delta-V]], [[CalDAV]], [[GroupDAV]]
|osilayer   = [[Application layer]]
|ports      = 80, 443
|rfcs       = RFC 2518, RFC 4918
}}

See also[edit]